Long focused on buildings, IFC formally grew into infrastructure — bridges, roads, rail and ports & waterways — with IFC4.3. As BIM/CIM adoption spreads across civil works, it’s a pivotal update. This article sorts out what actually changed.

Key points

IFC4.3 covers infrastructure as well as buildings (bridges, roads, rail, ports & waterways)
The key idea is alignment — civil works are built "along a line"
Standardised as ISO 16739-1; adoption is growing in public procurement
Tool support is still maturing — confirm version and coverage before exchanging

Why infrastructure support was needed

A building “stands on a site.” A road, railway or bridge instead “stretches along an alignment (a route).” Because of this fundamental difference, the building-oriented IFC of earlier generations couldn’t represent civil structures well.

As countries push BIM/CIM for infrastructure (joining design, construction and maintenance digitally), demand grew to “hand over infrastructure models in a vendor-neutral common format, just like buildings.” IFC4.3 answers that.

What IFC4.3 now covers

🌉 Bridges

Girders, piers, bearings and other bridge-specific elements.

🛣️ Roads

Carriageways, pavement layers and markings placed along an alignment.

🚆 Rail

Track, switches and facilities for railway infrastructure.

🚢 Ports & waterways

Harbours, quays and navigable waterways (marine facilities).

Beyond these, the extension also reaches toward terrain and surveying, plus the civil elements common across domains. (Tunnels are not part of IFC4.3 — a dedicated tunnel schema is on the roadmap for a later release.) Picture the openBIM world — once buildings only — widening to social infrastructure as a whole.

The key concept: alignment

The centrepiece of IFC4.3 is alignment — the centreline of a road or track defined as a combination of horizontal curves, vertical gradients and cant (superelevation).

Civil structures are positioned as “from here to here along this alignment.” Where buildings place elements by XYZ coordinates, infrastructure speaks in terms of “distance (station) along the alignment.” Grasping that shift in mindset is the first step to understanding IFC4.3.

🧭

Different from the building mindset: buildings organise elements by storey; infrastructure organises by position along an alignment. Same IFC, different structural logic.

IFC4 vs IFC4.3

IFC4 (building-centric)

Optimised for buildings

Centred on walls, slabs, columns
Storey-based spatial structure
Little notion of alignment

IFC4.3 (infra extension)

Buildings + civil works

Adds bridge, road, rail, ports & waterway elements
Introduces alignment
Standardised as ISO 16739-1

What to watch for in practice

Tool support is still maturing: compared with IFC2x3/IFC4 for buildings, IFC4.3 read/write support varies by tool. Confirm how far the other party’s software handles IFC4.3 before exchanging.
Be explicit about the version: say “IFC4.3,” not just “IFC.” A version mismatch silently drops elements and alignment data.
No rush for pure building projects: for buildings alone, IFC2x3 or IFC4 is usually still enough. IFC4.3 earns its keep on projects that include infrastructure.

Summary

IFC4.3 is the newest generation, extending IFC to infrastructure.
Its central concept is alignment — civil works are built along a line.
Standardised as ISO 16739-1, with growing use in public procurement.
Tool support is maturing, so confirm version and coverage when exchanging.

If you work on infrastructure, understanding IFC4.3 and alignment makes data-exchange conversations far smoother.