Existing records disagree
Combine authorized drawings, models, surveys, scans and field records into a baseline with visible source and verification status.
Owner + facility information support
Define the operational decision before the handover model.
We help owners, developers and FM teams turn available project, survey and asset records into scoped existing-condition models, record information and digital handover packages—with source and verification status kept visible.
Start with one operational use case, the available records and the system or team expected to receive the information.
01 · Captured spatial context
02 · Whole-floor coverage viewWhere owners lose information value
Make the next asset decision the organizing principle.
Maximum geometry is not the goal. The useful information set is the one a named person can trust, find, import, review or maintain for a defined task.
Close-out is approaching
Define the model, document, asset-data and issue evidence needed before the project team disperses.
Renovation needs a dependable base
Scope existing-condition information around the design, quantity, coordination or survey decision it must support.
Operational data has nowhere to land
Map required identifiers, fields, documents and validation to the actual receiving workflow before demanding a platform label.
From requirement to usable record
Design the handover from operations backward.
The owner names the decision and authority. The delivery route then connects source records, verification, model information, documents and acceptance.
- 01↗
Name the use case
Identify the user, asset decision, required frequency, receiving system and value of the information.
- 02↗
Define information requirements
Specify spaces, systems, maintainable assets, identifiers, fields, documents, formats and responsibility.
- 03↗
Establish the source baseline
Inventory drawings, models, scans, surveys and field records; distinguish verified, inferred and missing conditions.
- 04↗
Prepare + validate the package
Develop the scoped model and data, run named checks, record exceptions and test representative exchanges.
- 05↗
Accept, archive + govern change
Record acceptance, limitations, source files, permissions, restore route and responsibility for future updates.
Operational purpose, authority and acceptance.
- Asset and organizational information requirements.
- Authoritative source, field-verification and reliance decisions.
- Receiving-system, cybersecurity and access requirements.
- Acceptance of model, data, documents and known limitations.
- Operational procedures, maintenance decisions and update ownership.
Structured BIM and handover outputs with visible provenance.
- Existing-condition and record-model development.
- Approved change and field-record incorporation.
- Asset-information schedules and document-link preparation.
- Model health, field and exchange validation checks.
- Organized native, exchange, record and close-out packages.
Related owner + FM work
See existing-condition, model and handover information in context.
Reality capture · Bengaluru, India
Workplace reality-capture study — Bengaluru
Existing conditionsReview reality-capture support
Reality capture · Hyderabad, India
Workplace dollhouse capture — Hyderabad
Existing conditionsBuild a Scan-to-BIM scope
Model + documentation · Bengaluru, India
Residential LOD 400 documentation set
LOD 400Open residential case study
Model + documentation · Bengaluru, India
Airport terminal flooring-plan package
LOD 350 / 400Open airport case study
An owner brief worth testing
Send the receiving condition, not “LOD 500” alone.
One representative asset class, room or model zone can expose whether the required information is available, verifiable, importable and maintainable.
- 01
Operational use — who needs to decide, locate, inspect, maintain or plan what.
- 02
Asset scope — buildings, floors, spaces, systems, equipment and exclusions.
- 03
Source authority — models, drawings, surveys, scans, O&M records and field verification.
- 04
Information structure — IDs, classifications, fields, documents, units and naming.
- 05
Receiving route — people, CDE, CAFM/CMMS, archive or future-project workflow.
- 06
Acceptance + upkeep — tests, exceptions, approver, update trigger and record owner.
Choose the starting condition
Existing asset, live handover or information-readiness review.
Begin with the smallest bounded outcome that can be verified. Wider rollout follows only after the first exchange works for its intended recipient.
Existing-condition baseline
Useful when
Authorized CAD, PDF, scan, point-cloud or field records must become a scoped model or drawing base for renovation and review.
Scope the baseline ↗Project handover package
Useful when
Approved construction records, asset fields, documents and open issues must be reconciled into a stated close-out output.
Review handover support ↗Information-readiness review
Useful when
The owner needs to test use cases, available records, receiving systems and acceptance before procuring a larger model or platform.
Request a review ↗BIM resources for owners + FM teams
Find handover, information-management, digital-twin and sourcing guidance in one route.
Browse resources ↗Plain-language guideDigital Twin 101
Separate a static model, connected view and governed operational twin.
Read the guide ↗Management playbookDigital handover + asset information
Work backward from use cases, required fields, acceptance and upkeep.
Use the playbook ↗COBie, AIM + digital-twin boundaries
Choose an exchange because the receiver can use it.
COBie can structure maintainable-asset information, but it is not a universal substitute for an owner’s requirements, model files, documents, system mapping or acceptance. The current project should define the applicable edition, required fields, responsibility and validation.
An Asset Information Model is an information resource governed around asset use; it is not proven by a filename. A live twin additionally needs maintained systems, connections, permissions, synchronization and operational ownership.
For an official COBie starting point, see the National Institute of Building Sciences COBie module ↗.
Owner + FM questions
What to settle before commissioning the information.
01What can a building owner or FM team ask ZX Collabs to deliver?+
A scope can include existing-condition or record-model development, verified change incorporation, asset-information schedules, drawing and model reconciliation, close-out issue tracking, model health review and a client-format handover package. The required use, source authority, verification, fields, formats and acceptance tests must be named.
02Is an as-built BIM model the same as a verified survey?+
No. A dependable record distinguishes captured, measured, verified, inferred and client-supplied information. Survey method, coordinate basis, tolerance, inaccessible conditions and approval route must be stated. A model label alone does not prove field accuracy.
03Does every owner need COBie?+
No. COBie is one structured exchange approach for maintainable-asset information. The owner should begin with operational use cases, required fields, identifiers and the receiving system, then select the smallest exchange that those workflows can accept and maintain.
04Can you connect BIM directly to our CAFM, CMMS or BMS?+
We can prepare, map and validate structured BIM and handover information for an agreed import or integration route. Live sensor connections and ongoing platform operation need a separate, specifically agreed scope.
05Is a handover model automatically a digital twin?+
No. A static record or asset-information model may support a future twin, but a live digital twin needs governed identifiers, maintained source systems, integrations, synchronization, access, validation and accountable operational ownership.
06Can ZX rescue an incomplete handover near project close-out?+
A bounded review can inventory models, drawings, documents, asset fields, open issues and missing authority, then separate repairable gaps from decisions or evidence the project parties must supply. Recovery feasibility depends on the available records, access, programme and acceptance route.
07Can an owner begin with one building, floor or asset system?+
Yes. A representative area or asset class can test the information requirement, source reliability, model setup, data structure, review route and receiving-system assumptions before wider rollout.
Start with the deliverable
What must the asset team be able to trust or do next?
Send the operational use case, asset scope, available records, verification status, required fields, receiving system and target date. We will identify missing information controls before proposing a model or handover package.