BIM capability
Configured IFC exports, COBie asset data packages and openBIM validation supporting cross-platform information exchange, contractor integration and operational handover.
IFC and COBie deliverables enable information exchange between heterogeneous BIM platforms, contractor systems and facility management databases. Export configuration maps Revit element categories, parameters and property sets to IFC entities and COBie worksheets with documented mapping tables validated before each issue.
openBIM exchange is not a simple file export — it requires schema selection, model view definition alignment, property mapping verification and post-export validation against reference requirements. Poorly configured exports produce geometrically correct but information-empty files that fail handover acceptance.
COBie deliverables structure asset data for operational import: equipment names, types, locations, warranties, spare parts and maintenance attributes extracted from production models with field requirements defined in employer information requirements or asset information requirements.
Each export issue includes validation reports comparing delivered data against mapping documentation and client field requirements. buildingSMART validation tools, custom audit scripts and manual spot-checks confirm that exchanged information meets contractual deliverable specifications.
Contractors and FM operators frequently cannot access native Revit files. IFC provides the neutral exchange format for coordination, quantity take-off and asset import. COBie provides the structured asset register that bridges BIM data to computerised maintenance management systems.
Export requirements are defined at project outset in the BIM execution plan with schema version, model view definition, property set requirements and COBie field mapping. Late-stage export configuration produces rework when mapping gaps are discovered at handover.
IFC exports support federation where contractor platforms differ from design authoring tools. Validated IFC models enable clash detection and coordination without proprietary link dependencies, though geometric fidelity and parameter completeness depend on export configuration quality.
Revit export setup with category mapping, property sets and schema version.
Export scoped to agreed model view definition — Reference View or Coordination View.
Shared parameters mapped to IFC property sets per BEP mapping table.
Post-export geometric and data validation against reference requirements.
Revit parameters mapped to COBie worksheet fields per handover specification.
Asset data populated from production models with completeness audit.
Export configuration recorded for reproducibility across issue cycles.
Validated IFC models for contractor coordination platforms.
IFC, COBie and supporting documentation combined for employer acceptance.
Automated verification against information delivery specification where required.
Export issues tracked in CDE with mapping version reference.
COBie format aligned to client CMMS import requirements.
Confirm IFC schema, MVD, property sets and COBie fields in BEP.
Document Revit to IFC and COBie parameter mapping with data types.
Configure Revit IFC export with mapping table and test on sample model.
Export representative model section and validate against requirements.
Correct mapping gaps identified in pilot validation before production export.
Export full model at milestone with documented configuration version.
Run validation tools and issue export validation report with findings.
Assemble IFC, COBie, mapping docs and validation report for employer.
IFC export uses schema version specified in EIR — IFC 2x3 or IFC 4.
Exported entities within agreed model view definition scope.
Required property sets populated for all in-scope element categories.
Exported geometry represents source model within agreed tolerance.
Required COBie fields populated per handover specification field list.
Asset tags and GUIDs consistent between Revit, IFC and COBie outputs.
Mapping table version matches export configuration version.
Export passes buildingSMART or client-specified validation without critical errors.
Export file navigable on target recipient platform within performance limits.
Uniclass, OmniClass or project codes exported to IFC and COBie fields.
IFC spatial hierarchy — site, building, storey, space — correctly structured.
Export issue date, author and model revision recorded in deliverable package.
Sample plant room
Full MEP model IFC
COBie asset data
Record model IFC
| Milestone | Element | Purpose | Responsible | Geometric | Alphanumeric | Documentation | LOD / LOIN | Control | Acceptance |
|---|---|---|---|---|---|---|---|---|---|
| Pilot export | Sample plant room | Validate mapping configuration | BIM manager | Representative equipment and distribution | Mapped property sets and COBie fields | Pilot validation report | LOIN 3–4 per handover spec | Validation tool and spot-check | Mapping approved for production |
| Construction issue | Full MEP model IFC | Contractor coordination exchange | MEP BIM coordinator | LOD 350 MEP geometry | Coordination property sets | IFC export with validation report | MVD Reference View | Automated validation | Contractor acceptance test |
| Handover | COBie asset data | FM system import | BIM manager | N/A — data deliverable | Full COBie field set per AIR | COBie spreadsheet or IFC with COBie properties | LOIN 5 / AIR requirements | Field completeness audit | FM import test successful |
| As-built | Record model IFC | Operational asset register update | MEP BIM lead | Field-verified geometry | Serial numbers, warranty data | As-built IFC and COBie package | LOIN 5 record information | Site data comparison | Employer handover sign-off |
IFC and COBie mapping is established during production modelling so that shared parameters carry export-ready data from authoring. Retroactive parameter population at handover is costly and error-prone — export fields must be defined in the shared parameter file at project outset.
Equipment schedules, valve lists and panel schedules in Revit are the authoritative source for COBie Component and Type worksheets. Schedule-model consistency is verified before each export issue.
Contractor fabrication models may be received as IFC for coordination verification. Import validation confirms geometric position and attribute completeness before overlaying with design intent models.
ISO 16739
buildingSMART IFC
buildingSMART IDS
COBie
ISO 19650-2
ISO 12006-2
BS 1192-4
Uniclass 2015
buildingSMART BCF
| Standard / Reference | Full title | Organization | Application area | Relevance | Edition status |
|---|---|---|---|---|---|
| ISO 16739 | Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries | ISO | IFC schema | Core schema for openBIM model exchange. | Published — confirm edition at project start |
| buildingSMART IFC | IFC Model View Definitions and Documentation | buildingSMART | IFC MVD | Reference View, Coordination View and Design Transfer View specifications. | buildingSMART specification |
| buildingSMART IDS | Information Delivery Specification | buildingSMART | Exchange requirements | Machine-readable export validation requirements. | buildingSMART specification |
| COBie | Construction Operations Building Information Exchange | buildingSMART / NIBS | Asset handover | COBie worksheet structure and field definitions. | Published — confirm edition at project start |
| ISO 19650-2 | Organization and digitization of information about buildings and civil engineering works — Delivery phase | ISO | Information exchange | Exchange information container requirements. | Published — confirm edition at project start |
| ISO 12006-2 | Building construction — Organization of information about construction works — Part 2: Framework for classification | ISO | Classification export | Classification codes in IFC and COBie deliverables. | Published — confirm edition at project start |
| BS 1192-4 | Collaborative production of information — Part 4: Collaborative exchange of COBie | BSI | COBie exchange | UK COBie delivery protocol. | Published — confirm edition at project start |
| Uniclass 2015 | Unified Classification for the Construction Industry | NBS | Classification | Classification codes exported to IFC and COBie fields. | Published — confirm edition at project start |
| buildingSMART BCF | BIM Collaboration Format | buildingSMART | Issue exchange | Complementary open standard for issue data alongside IFC. | buildingSMART specification |
Applicable standards depend on the project jurisdiction, information requirements, contract documents, delivery method and authority requirements. The adopted editions shall be confirmed at project commencement.
Documented Revit to IFC entity and property set configuration.
Revit parameter to COBie worksheet field mapping documentation.
Versioned IFC files at milestone issues with schema and MVD documented.
Spreadsheet or IFC-embedded COBie data per handover specification.
Automated and manual validation results for each export issue.
Sample export with validation for mapping approval before production.
Combined IFC, COBie, mapping docs and validation for employer.
Information delivery specification verification where contract requires.
Evidence of successful COBie import to client CMMS.
CDE records with revision, configuration version and approval status.
Independent review of IFC and COBie mapping before pilot export.
Production exports blocked until pilot validation passes.
buildingSMART or client validation tool executed on every export issue.
Manual verification of critical property sets on representative elements.
Required fields checked for population rate before handover issue.
Asset identifiers consistent across Revit, IFC and COBie outputs.
IFC hierarchy correctly represents building spatial organisation.
Export tested on contractor or FM recipient platform before formal issue.
Export configuration version matches mapping documentation version.
Employer formal acceptance of openBIM deliverable package.
Exports passing validation without critical errors at first issue.
>= 90%
Required COBie fields populated across all in-scope assets.
>= 98%
Required IFC property sets populated per mapping table.
>= 95%
COBie import to client CMMS without manual correction.
First-pass success
Mapping gaps identified post-pilot per export cycle.
Decreasing trend
No. IFC is an exchange format for cross-platform use. The native Revit model remains the authoritative authoring source. IFC is issued as an exchange container per EIR requirements.
Schema version is defined in the EIR or BEP — typically IFC 4 with Reference View MVD for current projects. Legacy contracts may specify IFC 2x3 Coordination View.
Where EIR or AIR specifies COBie, it remains the required asset data format. Some projects accept IFC with embedded properties or custom schemas instead — requirements are project-specific.
Data loss occurs when export mapping is not configured — Revit parameters must be explicitly mapped to IFC property sets. Mapping tables and pilot validation prevent this at production export.
Yes. Validated IFC exports support federation and clash detection on contractor platforms. Geometric fidelity and element identification depend on export configuration quality.
Let's plan the BIM scope, information requirements, delivery standards and coordination process in line with your project lifecycle.