Reference Formats
IFC
An open, vendor-neutral data schema for Building Information Modeling (BIM), designed so architecture, engineering, and construction software from different vendors can exchange building models without data loss.
Extension
.ifc
Full name
Industry Foundation Classes
Introduced
1997 (IFC 1.0, released by the IAI)
Vendor
buildingSMART (formerly the International Alliance for Interoperability, IAI)
What is inside the container
IFC defines a structured object model — walls, spaces, doors, MEP components — with typed properties and explicit relationships between them, serialized most commonly as a plain-text STEP (.ifc) file, though XML (ifcXML) and compressed (ifcZIP) encodings also exist. Unlike a mesh format, it carries semantic building data (material, fire rating, manufacturer, spatial containment) alongside geometry, and because its schema is published and maintained by a nonprofit standards body rather than one vendor, any compliant application can read and write it without licensing the format itself.
How to open it
For archives
IFC is the format of choice for long-term BIM archival precisely because it is open and vendor-neutral: a model stored as IFC will remain readable by future software the way a proprietary RVT file may not, since IFC's schema is published by buildingSMART rather than locked to one company's product roadmap. A DAM serving AEC clients should treat IFC exports as the durable archival and cross-firm exchange copy, keeping the native authoring file (RVT, ArchiCAD PLN, etc.) only as the live editable source.
IFC traces back to 1994, when Autodesk invited twelve US companies to advise on a common set of C++ classes for building software interoperability — the effort that became the International Alliance for Interoperability (IAI), opened to all members in 1995. The IAI published IFC 1.0 in 1997, and the standard has been revised through IFC2x, IFC4, and the current IFC4.3 (which added infrastructure — roads, bridges, rail — to the original buildings-only scope). In 2005 the organization renamed itself buildingSMART, which still maintains IFC today as an ISO standard (ISO 16739) alongside its own certification program for software vendors.
What makes IFC matter for a DAM is precisely what makes it different from a proprietary CAD format: no single vendor controls it, so a model exported to IFC from Revit can be opened, checked, and coordinated in ArchiCAD, Solibri, or a free viewer without licensing Autodesk software. AEC firms are a real DAM vertical distinct from photo or video asset management — architecture and engineering teams need the same governed storage, versioning, and search applied to building models, drawings, and site documentation — and IFC is the format that lets a DAM store one archival copy of a building model that stays usable regardless of which authoring tool produced it or which tool a downstream consultant uses.
Frequently asked
Why is IFC recommended over RVT for long-term archival?
IFC's schema is open and published by buildingSMART, a nonprofit standards body, so any compliant software can read it indefinitely; RVT's schema is proprietary to Autodesk and undocumented, which puts long-term readability at risk if the format changes or a subscription lapses.
Can a DAM preview an IFC file without commercial BIM software?
Yes. Free tools like BIMvision, or the open-source IfcOpenShell library, can parse and render IFC geometry and metadata without any paid license, making it far more DAM-friendly than proprietary formats like RVT.
Is IFC a geometry-only format like OBJ or PLY?
No. IFC carries semantic building data — material properties, fire ratings, spatial containment, manufacturer info — attached to typed objects and their relationships, not just raw mesh geometry.
What's the difference between .ifc, ifcXML, and ifcZIP?
.ifc is the standard plain-text STEP-based encoding; ifcXML represents the same schema in XML for easier integration with XML-based workflows; ifcZIP is simply a compressed .ifc file for smaller transfer size.
Does every BIM tool support the same version of IFC?
No — support varies by version (IFC2x3, IFC4, IFC4.3) and by how completely a given vendor implements the schema, so a DAM handling IFC files should track the schema version in metadata to flag compatibility issues downstream.
Who maintains the IFC standard today?
buildingSMART International, the nonprofit successor to the International Alliance for Interoperability (IAI) that published the original IFC 1.0 in 1997; IFC is also an ISO standard, ISO 16739.
Why do AEC firms need a DAM at all if they already use BIM software?
BIM authoring tools manage active project models, but AEC firms also accumulate drawings, renders, site photos, and superseded model versions across many projects — the kind of governed, searchable, access-controlled asset library a DAM provides, with IFC as the shareable, tool-neutral archival format.
Can IFC replace RVT entirely in a Revit-based workflow?
Not for active authoring — Revit's parametric editing relies on its native RVT schema — but IFC export is the standard way to hand off or archive a model outside the Autodesk ecosystem without losing the structured building data.
Sources
- IFC 1.0 was released by the International Alliance for Interoperability (IAI) in 1997; the IAI itself grew from a 1994 Autodesk-convened group of twelve companies and was renamed buildingSMART in 2005. checked 2026-08-07 — Wikipedia — Industry Foundation Classes
- IFC continues to be developed and maintained by buildingSMART International, now at version IFC4.3, which extended the schema to infrastructure. checked 2026-08-07 — buildingSMART Technical — Industry Foundation Classes (IFC)