The model shows the design, not the site.
Ducts moved, walls shifted and openings changed. The drawings never caught up.
As-built (LOD 500), COBie & Asset Handover The building as it was really built, handed over with every asset on record.
We check the finished building against a laser scan, correct the model to LOD 500, and hand it over with COBie data, O&M manuals and warranties linked to every asset, ready for your CAFM.
AIM United · In short
What is an as-built BIM model?
An as-built BIM model is a LOD 500 record of the building as it was built, checked against site measurement. AIM United verifies the model against a laser scan and hands it over with COBie data, O&M manuals and warranties linked to each asset. Under ISO 19650-3 that handover becomes the asset information model (AIM) for the operational phase, built to the owner's asset information requirements (AIR). We deliver as-built models and handover for owners and facility teams in Saudi Arabia, the UAE and the GCC.
"As-built" means the last revision. Nobody checked the building.
The asset register is a spreadsheet nobody owns.
Serial numbers and warranties live in a contractor's inbox.
The manuals arrive in boxes.
Hundreds of PDFs with no link to the equipment they describe.
The FM team starts from zero.
Day one of operation begins with a survey of the building you just paid for.
Stage 1 · Model against the scan
Every wall, slab, duct and pipe checked against the building.
The design model sits inside the registered laser scan. Each element is shaded by how far its surfaces sit from the scanned points. Set the tolerance: everything outside it joins the deviation register, then the model is corrected to the building.
View
± 10 mm
± 5 mm± 50 mm
Deviation from the scan
- 0 to 5 mm
- 5 to 10
- 10 to 25
- Over 25
0Elements checked
0%Within tolerance
0To update
Deviation registerBy discipline · tap a row to find it
Deviations are drawn ten times larger on the model so they can be seen. Tolerances are agreed per element class in the BIM execution plan, not one number for the whole building.
Stage 2 · LOD 500 asset model
Tap an asset. Read its COBie record.
Every maintainable asset in the as-built model carries a tag in the project's naming convention, a Uniclass 2015 classification and its COBie data: type, model, serial number, installation date, warranty, maintenance, space, system and the approved submittal. The same tag is printed on the equipment label.
Discipline
Maintainable assets 19
Structure carries no maintainable assets. Its columns, beams, slab and core walls are verified against the scan in Stage 1.
Click an asset on the model or in the list to open its card. Drag the model to turn it.
The same records, sheet by sheet, ready for your CAFM.
COBie is the spreadsheet the facility team imports. Every row below comes from the asset model above: open an asset card and its Component, Type and System rows are highlighted. Before issue, every sheet passes the same checks you see here.
COBie 2.4 · B01 · Unit A-01 ·
What COBie contains
Who fills each sheet, and when.
The design team sets up the spaces, systems and types during design. The contractor adds what only the site knows: manufacturers, serial numbers, installation dates, warranties, spares and documents. We check it all against the as-built model and the asset information requirements, then hand it over as one file.
- ContactEveryone named in the file, by emailAll parties
- Facility · FloorThe building, its levels and unitsDesigner
- Space · ZoneRooms with areas, grouped for FM and securityDesigner
- TypeProduct types, model, warranty and expected lifeDesigner, then contractor
- ComponentEach installed asset: tag, serial, installation dateContractor
- SystemComponents grouped into the systems they serveDesigner
- Spare · Resource · JobSpares, tools and planned maintenance tasksContractor
- Document · AttributeO&M manuals, certificates and extra propertiesContractor
Stage 4 · ISO 19650 handover
Accepted line by line, ready for the FM team.
The handover is complete when each deliverable the asset information requirements ask for is accepted and published in the common data environment, Autodesk Construction Cloud. Tap a line to tick it off.
0/ 80%
From the site scan to the FM team's first day.
Site scanning
Terrestrial and mobile laser scanning of the finished building, registered and checked.
Scan-to-model verification
Every modelled element compared with the point cloud, with a deviation heatmap and register by discipline. XLSX, PDF and BCF.
LOD 500 as-built model
The design model corrected to the building, field-verified, in RVT and IFC.
As-built drawings
Plans, sections, elevations and schedules cut from the as-built model.
COBie and asset data
Facility, floors, spaces, types, components and systems, with serial, warranty and maintenance data, checked before issue. COBie 2.4 XLSX and IFC.
O&M handover
Manuals, warranties and the asset register, linked to the model and ready for CAFM.
Capture, model, automate, deploy, evolve.
- 01
Capture
Laser scans of the finished floors, registered to site control, plus a nameplate survey of every maintainable asset.
- 02
Model
The design model corrected to the scan, element by element, to LOD 500 and your naming and classification rules.
- 03
Automate
Our own scripts run the deviation check on every element and the COBie checks on every sheet before anything is issued.
- 04
Deploy
Model, drawings, COBie and documents published in the CDE, Autodesk Construction Cloud, and imported into your CAFM.
- 05
Evolve
The asset information model stays live: changes, replacements and new assets update the same records in operation.
Handover to ISO 19650
The handover your FM team can actually use.
Owners in Saudi Arabia, the UAE and the GCC increasingly ask for handover in the terms of ISO 19650. The asset information requirements (AIR) say what the facility team needs, the BIM execution plan says who supplies it and when, and the as-built model, COBie data and documents arrive in the common data environment as the asset information model for the operational phase described in ISO 19650-3.
AIM United delivers that handover from the same model we verify on site. We follow your naming and classification rules (Uniclass 2015 or OmniClass where the project names one), check every COBie sheet for missing fields and duplicate names before issue, and agree field tolerances per element class in the BEP instead of quoting one number for the whole building. On public projects in the Kingdom we align the handover with EXPRO's BIM requirements.
The point cloud comes from our scan to BIM team and the model from BIM modelling at LOD 500. After handover the same asset tags carry into a digital twin for facility management. AIM United is certified to ISO 19650 for information management and ISO 41001 for facility management.
Handed over at LOD 500.
- Lucid Motors Manufacturing PlantKAEC · LOD 300 → 500Full BIM lifecycle for a 1,043,476 m² automotive plant, finishing with a LOD 500 as-built model for facility management.Projects →
- Qiddiya Speed ParkQiddiya · LOD 400 → 500Mechanical and electrical BIM, from LOD 400 fabrication models to LOD 500 as-built documentation for handover.Projects →
- Bank AlJazira HQJeddah · scan-to-BIM LOD 5003D laser scan-to-BIM of the headquarters to a validated LOD 500 as-built model, with an MEP and security review against SAMA standards.Projects →
FAQ
What is a LOD 500 as-built model?
A model checked against the building as it was actually built, not as it was designed. Elements are field-verified, usually against a laser scan, and carry the information facility management needs.
What is COBie?
Construction Operations Building information exchange: a structured way to hand over the spaces, systems, types and components of a building, with manufacturers, serial numbers, warranties and maintenance data, in a spreadsheet any CAFM system can read.
Can you work from the contractor's redlines?
Yes, as a starting point. We then check them against a site scan, because redlines miss what nobody wrote down.
What does the FM team receive?
The LOD 500 model, as-built drawings, COBie data, O&M manuals, warranties and an asset register ready to import, all linked to the same asset tags.
What happens after handover?
The same model can go live as a digital twin: sensors on the same assets, and maintenance planned from the same records.
What is the difference between LOD 500 and a record model?
A record model is the design model updated from the contractor's redlines and site instructions. LOD 500 goes further: the size, location and orientation of each element are verified on site, usually against a laser scan, and the element carries its operational data. A record model shows what was meant to be built; a LOD 500 model shows what is there.
What is an asset information model?
Under ISO 19650 it is the information an owner needs to run the building: the model, the asset register, the documents and the maintenance data. At handover the project information model becomes the asset information model, and it has to answer the owner's asset information requirements. We set those fields up at the start so the handover delivers them.
Can you deliver COBie for an occupied building?
Yes. We scan out of hours or around occupied zones, survey the plant, tag each maintainable asset and build the COBie data from nameplates, the O&M records you hold and site checks. Where a nameplate or document is missing, the record says so, so the gap can be closed instead of guessed.
How long does as-built verification take?
It depends on the floor area, how dense the services are and the access we get. Scanning is quick; most of the time goes into comparing the model with the point cloud and updating it. We plan the work floor by floor, so verified floors reach you as they finish instead of in one file at the end.
Which COBie version and sheets do you deliver?
COBie 2.4 as an XLSX workbook, and in IFC when the project asks for it. We fill the sheets the asset information requirements call for, usually Facility, Floor, Space, Zone, Type, Component, System, Spare, Job, Document and Attribute, and check every sheet for missing fields, duplicate names and components without a space or system before issue.
Will the handover import into our CAFM?
Yes. COBie is a neutral format that CAFM and CMMS systems import. We agree the asset tags, classification and field mapping with your FM team at the start, run a trial import, and fix anything the system rejects before the final handover.