Export IFC for open BIM coordination
Configure IFC schema, container, model view, coordinates, semantics and validation, then verify the result in the receiving workflow.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- IFC4 on Free; IFC2X3 and ifcZIP on Core; ifcXML on Pro
- For
- BIM coordinators and information managers
- Last reviewed
Choose schema and container
| Choice | Use when | Important limit |
|---|---|---|
| IFC4 ADD2 TC1 STEP | The receiver accepts modern IFC4 open BIM exchange. | Default and widest Prism IFC validation path. |
| IFC2X3 TC1 STEP | A project or legacy receiver explicitly requires IFC2X3. | Older schema; do not choose only because it is familiar. |
| ifcZIP | The delivery contract accepts compressed IFC packaging. | Keep the archive intact; the payload remains IFC STEP. |
| ifcXML | An XML-based IFC consumer requires it. | Native path only; structural/schema checks do not include STEP-only deep checks. |
| IFC4X3 | Not available for export. | Unsupported schemas are rejected without automatic substitution. |
Configure the IFC target
- Give the IFC project, site and building meaningful approved names; blank site/building values use the documented defaults.
- Choose a Model View Definition compatible with the selected schema and receiving requirement.
- Use the Navisworks coordinate frame for ordinary coordination, or enter a verified IFC4 map conversion when project georeferencing requires it.
- For manual mapping, confirm EPSG code, eastings, northings, height, source origin and true north against project survey control.
- Choose combined or one file per source model. Per-model results share the federation alignment.
- Select Original or Persistent overrides for appearance according to whether live Navisworks colors/transparency are part of the deliverable.
Semantics, properties and quality
Baseline deterministic semantics are always active. Add only the required property families, storeys, systems and classifications. Pro can enable advisory smart classification, Conservative geometry recognition, IDS checking, company profiles and full reports; Ultra adds Aggressive recognition and managed signed profiles.
Verify IFC before delivery
Read the Prism report
Resolve configuration, schema, GUID, geometry, property and unit errors; assess every warning.
Open it in the receiver
Use the actual application and version named in the exchange contract.
Check coordinates
Compare at least one control point, extents, up direction and federation alignment.
Inspect representative objects
Verify class, name, geometry, materials and required properties across disciplines.
Run the project rule set
Apply the approved IDS or model-checking workflow and retain its version with the result.
Common IFC problems
| Symptom | Check first | Fix |
|---|---|---|
| Receiver rejects schema | Selected schema/container and receiver support | Use the explicitly supported schema; do not rename the file extension. |
| Model is misplaced | Origin, map conversion, EPSG and true north | Correct project control values and retest a small known scope. |
| Objects are generic proxies | Source evidence, mapping profile and classification report | Improve mapping/source data or test smart classification; do not force a class without evidence. |
| Properties are missing | Selected property families, profile, scope and Fast/Standard mode | Include the required family; compare Standard when Fast best-effort data is insufficient. |
| ifcXML fails while STEP works | Native component and scope compatibility | Repair the native component or use STEP if the delivery contract permits it. |