6D BIM: Turning the Model Into Facility and Asset Management Data

What 6D BIM actually means

Most teams stop caring about the model the day the building opens. The drawings are printed, the handover box is ticked, and the Revit file goes to an archive folder that nobody opens again. 6D BIM is the discipline that refuses to let that happen. It is the practice of building a model that carries structured asset and lifecycle data, so the people who operate the building for the next 40 years can actually use it.

The shorthand definition is simple: 6D BIM is the model plus operations and asset management data. Where 3D is geometry, 4D adds time, and 5D adds cost, 6D adds the information a facility manager needs to run, maintain, and eventually replace every serviceable asset in the building. Think warranties, serial numbers, maintenance schedules, spare-part references, and the responsible manufacturer for every air handling unit, pump, and door closer.

The word “dimension” here is a loose analogy, not a mathematical one. Nothing about 6D changes the geometry. What changes is the depth and structure of the non-graphical data attached to that geometry, and the process that keeps it trustworthy from design through construction and into the operational phase.

Where 6D sits in the BIM dimensions

It helps to see 6D as one link in a chain rather than a standalone deliverable. Each dimension layers structured information onto the same coordinated model.

Dimension	Adds	Primary user
3D	Geometry and coordination	Designers, coordinators
4D	Time and sequencing	Planners, site teams
5D	Cost and quantities	Estimators, QS
6D	Operations and asset data	Facility managers, owners
7D	Sustainability and energy	Sustainability leads

The dimensions are not strictly sequential, and a project rarely runs all of them at full depth. But 6D depends on the discipline you built earlier. If your 3D model has clean object naming and reliable classification, populating asset data is straightforward. If your model is a mess of unnamed generic families, 6D becomes a data-cleansing project rather than a data-capture one. This is the same lesson that shows up in 4D BIM work: the value at the later dimension is set by the quality of the model underneath it.

The information chain: from OIR to AIM

6D BIM is not really a Revit feature. It is an information management process, and the cleanest way to understand it is through the ISO 19650 information requirements chain. If you have read our guide to ISO 19650, this will feel familiar.

The chain works backwards from what the owner needs:

• OIR (Organisational Information Requirements): what the owner’s business needs to know. For a hospital trust, that might be “we need to plan preventive maintenance and track asset lifecycles across our estate.”
• AIR (Asset Information Requirements): the specific data fields required for each asset type to meet the OIR. This is the master specification for 6D. It defines exactly which properties every pump, valve, and luminaire must carry.
• EIR (Exchange Information Requirements): what the owner asks the delivery team to produce, including the AIR translated into a project deliverable.
• AIM (Asset Information Model): the final, verified information model the owner receives and maintains through operations.

The delivery team produces a PIM (Project Information Model) during design and construction. At handover, the relevant, verified subset of that PIM becomes the AIM. 6D BIM is the work of making sure the PIM contains the right asset data, structured to the AIR, so the AIM handover is a filter-and-verify exercise rather than a scramble.

The single most important consequence of this chain: if the AIR does not exist at the start of the project, your 6D deliverable has no target. You cannot capture the right data if nobody has said what “right” means. Chasing an AIR after the model is built is the most common way 6D projects fail.

What asset data belongs in a 6D model

A 6D model does not need data on every object. Nobody maintains a stud wall or a skirting board. The data lives on the maintainable and replaceable assets: equipment, systems, and components that have a service life, a manufacturer, and a maintenance regime.

Typical fields captured against each asset:

• Identity: asset tag or mark, type, classification code (Uniclass or OmniClass)
• Manufacturer data: make, model, serial number, product URL
• Commercial: supplier, installation date, warranty start and expiry
• Maintenance: service interval, expected service life, spare-part references
• Performance: rated capacity, power draw, flow rate, or the equivalent for the asset type
• Location: the space or zone the asset serves, and the room it physically sits in

In Revit, most of this lives in shared parameters so the fields schedule cleanly and export in a predictable structure. If you are unclear on why shared parameters matter for structured data, our guide on Revit shared parameters and schedules covers the reasoning. The rule of thumb: any field the owner will filter, report, or import into a maintenance system must be a shared parameter, not a text note buried in a comment field.

COBie: the handover format that ties it together

You cannot hand an owner a Revit file and call it asset data. Most facility teams do not run Revit, and their maintenance systems do not read .rvt. The industry answer is COBie (Construction Operations Building Information Exchange), a structured, software-neutral schema for delivering asset information.

COBie is, in practice, a spreadsheet with defined worksheets: Facility, Floor, Space, Zone, Type, Component, System, and so on. It captures the what and where of every asset without the geometry. A door type is a row on the Type sheet. Every individual door instance is a row on the Component sheet, linked back to its type and to the space it belongs to.

The strength of COBie is that it is a contract-friendly, checkable deliverable. An owner can validate it, a maintenance system can import it, and it does not depend on any single vendor’s file format. The weakness is that a COBie sheet is only as good as the model behind it. Export a poorly populated model and you get a valid-looking spreadsheet full of blanks, which is worse than no deliverable because it looks complete.

COBie can be exported directly from Revit (through the COBie extension or IFC-based tools) or built up in dedicated software. Either way, the data should originate in the model, not in a separate spreadsheet maintained by hand. The moment your asset data lives in two places, they drift apart.

The 6D workflow, step by step

Here is how a 6D deliverable comes together on a real project when it is done properly.

1. Agree the AIR early. The owner (or their information manager) defines the asset data required per asset type, before design work is far along. This goes into the EIR.
2. Set up the parameter structure. The BIM lead maps the AIR fields to shared parameters and a classification system, then builds them into templates and library families so data capture is native, not retrofitted.
3. Assign responsibility. Decide who populates what. Designers set type-level data; contractors and subcontractors add the installed reality (actual manufacturer, serial number, install date) during construction.
4. Capture during construction, not after. The installed asset data is captured as the work happens, ideally via field tools that write back to the model or a linked database. Capturing it at practical completion, from memory, is how data quality collapses.
5. Validate against the AIR. Run automated checks. Every asset that must carry a warranty field should have one populated. Tools like Solibri or model checkers can flag missing or malformed data before handover.
6. Export and verify COBie. Generate the COBie deliverable, run it through a validator, and fix the gaps at source in the model.
7. Hand over the AIM. Deliver the verified information model and COBie to the owner, who imports it into their CAFM or CMMS (computer-aided facility management or computerised maintenance management system).

The theme running through all seven steps is that 6D is captured incrementally, by many hands, against a fixed specification. It is a rhythm, not a final task.

Tools that support 6D BIM

No single tool owns 6D. It spans authoring, checking, and operations software.

Tool	Role in 6D
Revit	Authoring, shared parameters, schedules, COBie export
IFC	Neutral exchange of asset data between platforms
Solibri	Data validation, checking rules against the AIR
Autodesk Construction Cloud	CDE, field data capture, asset tracking
COBie toolkit / extensions	Structuring and exporting the handover schema
CAFM / CMMS (e.g. Maximo, Archibus)	Operational home for the asset data

The choice matters less than the discipline. A well-run 6D process with plain Revit schedules and a validated COBie export beats a poorly governed one running expensive asset-management software. The software does not create good data. Your specification and your checks do.

Modeling rules: LOD, LOI, and classification

6D lives or dies on two things people often confuse. LOD (Level of Development) describes how reliable the geometry is. LOI (Level of Information) describes how complete the attached data is. For 6D, LOI is what you care about. A schematic-looking pump with fully populated manufacturer and maintenance data is more valuable at handover than a beautifully detailed pump with empty parameters. If levels of development are new to you, our guide on BIM LOD levels sets the foundation.

Three practical modeling rules keep 6D data clean:

• Classify everything consistently. Use one classification system (Uniclass 2015 or OmniClass) across the whole model. Facility systems group and report assets by classification code, so an inconsistent scheme breaks their filtering.
• Model maintainable assets as identifiable objects. If a facility manager will service it, it needs to be a discrete, taggable object with a stable ID, not part of a merged generic element.
• Keep the asset ID stable. The tag that identifies an asset in the model should match the tag on the physical equipment and in the maintenance system. When those three disagree, the whole point of 6D collapses.

Who owns 6D, and when to start

6D fails most often because of an ownership gap. Designers assume the contractor will handle asset data. Contractors assume it was specified in the model. The owner assumes they will receive something usable. Nobody is accountable for the whole chain.

On a well-run project, an information manager owns the 6D process end to end, working to the owner’s AIR. The owner defines the requirements. Designers populate type-level data. Contractors and their supply chain populate installed-asset data. The information manager validates and coordinates the handover. This is a natural extension of the coordination discipline covered in our guide on BIM coordination that works: the same rigour that catches clashes catches missing asset data.

Start at project inception. The AIR belongs in the EIR, which belongs in the tender. Bolting 6D on at handover means reverse-engineering asset data from as-built drawings and submittals, which is slow, expensive, and unreliable. The cost of 6D done early is a small overhead on data entry. The cost of 6D done late is a separate project.

Common mistakes to avoid

• No AIR, no target. Starting 6D without the owner’s Asset Information Requirements. You cannot hit a specification that does not exist.
• Capturing data at the end. Waiting until practical completion to populate installed-asset data. By then the subcontractors have left and the information is lost.
• Data in two places. Maintaining asset data in a separate spreadsheet alongside the model. The two versions drift, and nobody knows which is correct.
• Modeling everything to high LOD, ignoring LOI. Spending effort on geometry the facility team will never use while leaving the data fields blank.
• Treating COBie as an export button. A COBie file is a validation deliverable, not a one-click export. If you have not checked it against the AIR, you have delivered a spreadsheet, not asset data.
• Ignoring the operational tool. Building 6D data the owner’s CAFM or CMMS cannot import. Confirm the target system’s format before you structure the handover.

How to start with 6D on your next project

You do not need to run a full 6D programme to begin building the muscle. Start small and specific:

1. Pick one asset type, such as mechanical equipment or doors, and define the exact data fields the owner would want.
2. Build those fields as shared parameters into your project template so the data has a home from day one.
3. Populate them as you model, not as a final push, and schedule them so gaps are visible.
4. Export a COBie sample for that asset type and validate it. Seeing the structure early teaches the whole team what “good” looks like.
5. Scale to more asset types once the process is proven on one.

6D BIM is where BIM stops being a design tool and becomes a lifecycle asset. For a building that will operate for decades, the operational data is arguably the most valuable thing the delivery team produces. The professionals who understand how to capture and structure it are the ones owners keep calling back.

If you want to build the underlying skills that 6D depends on, from clean model structure to shared parameters, schedules, and coordination workflows, our BIM courses at Archgyan Academy teach the real workflows firms use, all in one subscription.