IFC (Industry Foundation Classes) is the open file format used to exchange BIM models between different software. It is developed by buildingSMART International and published by ISO as ISO 16739-1: the latest version is IFC 4.3, ISO 16739-1:2024. An IFC file describes objects, geometry, relationships and properties in a neutral way, so the recipient can read and check it without using the same software as the author.
In Italian public tenders an open format is not optional, and most international clients ask for one too. This article explains how an IFC file is structured, which version to use, what MVDs and IDS are, and which data most often gets lost on export, with the rules we apply when validating models for our clients.
What IFC is and what openBIM means
IFC is a data schema: a vocabulary that defines classes of objects (IfcWall, IfcSlab, IfcDoor, IfcPipeSegment, IfcSpace), their relationships (what contains what, which storey an element belongs to, which opening cuts which wall) and sets of properties called property sets, such as Pset_WallCommon. The most common file is plain-text STEP with the .ifc extension; compressed (.ifczip) and XML variants also exist.
openBIM is the approach, promoted by buildingSMART, in which project participants collaborate through open standards rather than through a single software. Besides IFC the family includes BCF for coordination issues, IDS for information requirements and bSDD for property and classification dictionaries. The definitions are in our glossary.
One point to settle early: IFC is an exchange format, not an authoring format. The native model remains the designer's tool. IFC is for coordination, checking, delivery and archiving.
IFC versions: where things stand in 2026
| Version | Standard | Scope | Typical use today |
|---|---|---|---|
| IFC2x3 | ISO/PAS 16739:2005 | Buildings | Still required by many clients and supported by all software |
| IFC4 | ISO 16739-1:2018 | Buildings | Recommended for buildings where the supply chain supports it |
| IFC 4.3 | ISO 16739-1:2024 | Buildings and infrastructure: roads, rail, bridges, ports | Infrastructure projects; software support growing |
| IFC5 | Under development at buildingSMART | Schema redesign | Not yet usable for contractual deliveries |
ISO approved version 4.3 in early 2024, and buildingSMART documents it on its IFC standard page. The main changes concern infrastructure: alignments, rail and road elements, marine works. For a building the differences from IFC4 are modest.
The version is not chosen on paper. Check that the authoring software exports that version well and that the recipient's software imports it well. On a building project, picking IFC 4.3 just because it is the newest, with a supply chain that handles it poorly, gives worse files than a good IFC4.
Why Italian tenders require open formats
Article 43 of Legislative Decree 36/2023 made digital information management methods mandatory from 1 January 2025 for the design and construction of new works and of interventions on existing buildings above €2 million, with exclusions for maintenance. The framework is explained in our article on the BIM mandate in Italian public contracts.
Annex I.9, as amended by the corrective Legislative Decree 209/2024, states that contracting authorities use interoperable platforms based on open, non-proprietary formats. Among the minimum contents of the capitolato informativo it lists the specifications that ensure the interoperability of information systems over time. The text in force is on Normattiva.
The law does not name IFC, but for BIM models it is the only international open standard recognised by ISO. The reasons are practical, and they apply outside Italy too:
- competition: no bidder has to buy a specific software;
- checking: the client verifies models with its own tools, without depending on the supplier;
- longevity: a public asset lasts decades, and a proprietary format may not be readable in fifteen years;
- operations: as-built data has to reach facility management systems, which rarely read native files.
The capitolato informativo turns the principle into rules: IFC version, MVD, required property sets, naming rules, coordinates. It is section 4 of our list in 10 things to write in the capitolato informativo.
MVDs: which subset of IFC is exchanged
The IFC schema is very large and no exchange uses all of it. A Model View Definition (MVD) defines the subset of classes and rules needed for a specific purpose, and it is also the basis for software certification.
- IFC2x3 Coordination View 2.0: the long-standing view for coordination between disciplines, still widely used.
- IFC4 Reference View: designed for coordination and reference. Geometry is simplified into tessellated shapes or extrusions, and models are not meant to be edited by the recipient. It is the most requested view for buildings in IFC4.
- IFC4 Design Transfer View: designed to transfer more editable geometry, but with limited software support.
- For IFC 4.3 buildingSMART keeps the IFC4 Reference View and is developing infrastructure-specific views such as the Alignment Based View.
In the requirements, state the version and the MVD together, for example "IFC4 Reference View", not just "IFC".
IDS: information requirements in a checkable file
For years information requirements were written in Word or Excel tables that the author has to interpret and the recipient has to check by hand. IDS (Information Delivery Specification) fixes this. It is an XML file, approved by buildingSMART as a final standard in version 1.0 in June 2024, that describes in machine-readable form which properties, classifications and values the elements of an IFC file must have.
An IDS requirement has a simple structure: which elements it applies to (for example all IfcDoor) and what they must have (for example the FireRating property in Pset_DoorCommon, with allowed values EI30, EI60, EI120). The same file tells the modeller what to fill in and lets the checker verify the model automatically. IDS does not describe geometry: tolerances and geometric detail still need other rules.
In the requirements it pays to attach one IDS per delivery stage, rather than a table to be interpreted.
The most common data losses on export
A bad IFC is rarely a corrupt file. It is almost always a valid file that says the wrong things. These are the problems we find most often during checks:
| Problem | Effect | How to avoid it |
|---|---|---|
| Elements exported as IfcBuildingElementProxy | The recipient cannot tell what they are; filters and quantities fail | Map every native category to a specific IFC class |
| Custom parameters not exported | Codes, materials and operations data missing | Define export property sets and check them on the IFC, not in the native file |
| Missing spaces (IfcSpace) | No room areas, no data for facility management | Enable space export and check room volumes |
| Inconsistent coordinates and origin | Discipline models that do not overlay | Fix a shared reference point and check federation at every delivery |
| No georeferencing | The model cannot be placed on the map | In IFC4 and 4.3 use IfcMapConversion and state the coordinate reference system |
| Mixed units | Dimensions and quantities off by a factor of 10 or 1,000 | State units in the requirements and check them on receipt |
| Simplified materials and layers | Wall build-ups read as a single material | Export material layers and check a sample |
| Disconnected MEP systems | Pipes and ducts not assigned to any system | Check IfcSystem assignments and connections before delivery |
| Lost classification | The classification code never reaches the recipient | Export classification as IfcClassificationReference |
| Duplicates or linked files included by mistake | Doubled quantities, heavy files | Export one file per discipline, exclude links |
Checklist before delivering an IFC file
- Version and MVD match the requirements.
- Every category maps to a specific IFC class; proxies are few and justified.
- Required property sets and properties are present, filled in and within allowed values, checked against the IDS.
- Storeys, spaces and spatial structure (IfcSite, IfcBuilding, IfcBuildingStorey) are correct.
- Coordinates, orientation and georeferencing match the other disciplines.
- Units and base quantities are consistent.
- The file opens in at least one software other than the one that produced it.
- File name and coding follow the requirements.
For point 7 a browser is enough: our IFC Viewer opens the model on your device, without uploading it to a server, and shows the classes and properties of every element. It is the quickest way to see what the person reading your file will actually get.
BIMON's experience
At Fiumicino Airport, under framework agreements with Aeroporti di Roma, we handle BIM process management and model validation on airport projects: models from different teams have to follow the same rules to be federated and managed. For SEA, after designing the Malpensa VIP Lounge in BIM, we supported the airport operator's BIM implementation with design validation assignments. At the Ciampino General Aviation Terminal, discipline models were federated into a single model for clash management: federation only works if coordinates and spatial structure are consistent from the first export.
What BIMON does
Through our BIM validation service we check delivered IFC files against the requirements, with IDS rules and automated checks, and return a report per element. Through BIM management we write the export rules and information requirements before problems appear. If you want a model checked or need the IFC requirements for a tender, get in touch.





