BIM and IFC file exchange: pin the schema on export
Someone emails "site-model-final.ifc" at project closeout, your structural viewer renders half the MEP runs as untyped bounding boxes, and three years later a maintenance team discovers nobody recorded which exporter profile or schema edition produced the file. "Send the IFC" is not an engineering specification—it is how spatial metadata quietly disappears between handoffs.
Author: Escherbridge. Published . Last reviewed: , America/Denver.
The National Institute of Building Sciences hosts the National BIM Standard–United States (NBIMS-US™) to give built-environment teams "consensus-based standards" and unambiguous exchange documentation. In NBIMS-US Version 3 chapter 2.2, the approved neutral STEP/XML exchange format is pinned explicitly to Industry Foundation Class (IFC) 2X3 (February 2006), authored by buildingSMART International—including its technical corrigendum line naming "2X3-TC1" as that edition's baseline.
A building file that cannot be inspected reliably by the next custodian is not a handoff; it is an archive trap. We trace how schema drift happens on real jobs in The file opened. It wasn't the building..
Why naming the edition prevents silent data loss
Every BIM exporter carries subtle assumptions about coordinate origins, property-set mappings, and geometry fallbacks. When two teams agree only on "IFC" in the contract—while NBIMS-US lists distinct major editions such as V3 and V4—nobody knows whether a missing thermal zone or structural parameter came from field omission or parser mismatch.
Recording the schema edition alongside the deliverable is basic operational hygiene, similar to pinning dependencies in software engineering. An open exchange file is also only one piece of a digital twin—geometry export alone does not evaluate live facility state—though both rely on the same custody discipline across construction programs.
What to put in every handover manifest
Include four plain facts next to every delivered model: the exact NBIMS-US edition and schema identifier (such as IFC 2X3 / 2X3-TC1 when following V3 §2.2), the exporter software build, the project coordinate reference, and a checksummed copy verified to open outside the authoring tool.
Scope and source boundaries
This guide cites strictly from the published NBIMS-US landing page and NBIMS-US Version 3 chapter 2.2 specification; downstream ISO and buildingSMART catalogue editions are excluded rather than extrapolated from memory. They are not cited here. PrimusNeo does not claim a model repository or a certification, and does not invent universal interchange pass rates.
A situation like this
A subcontractor handoff drops an unlabelled ".ifc" archive into shared storage with zero manifest. Eighteen months later a retrofit crew opens it in a different toolchain, loses property sets, and cannot tell whether the omissions are field reality or translation loss.
Sources
- National Institute of Building Sciences, National BIM Standard–United States landing. https://www.nibs.org/nbims
- NBIMS-US Version 3, chapter 2.2, "ISO 16739, Industry Foundation Class 2X3 – February 2006." https://nibs.org/wp-content/uploads/2025/04/NBIMS-US_V3_2.2_Industry_Foundation_Class_2X3.pdf
Also in this section
- What is a digital twinan electronic representation you can evaluate.
- Idempotent HTTP requestsa retry is safe only if the effect is the same.
- What is local-first softwarethe copy you can still open later.
- Architecture decision records: write down why it was decidedan interface or a dependency is often the thing being decided.
The useful next step is to name the schema on the file, or to read the construction industry page. If something on this page is wrong, write to us.