One project. One spatial truth.

We assemble discipline models on a verified coordinate system and project grid. The result is a controlled federated model built for repeatable coordination.

Separate models cannot coordinate themselves.

Model federation brings architectural, structural, civil and MEP information into a common review environment without collapsing ownership of the source files. Each discipline remains responsible for its model while the combined view exposes how the systems occupy the same space.

The work depends on more than appending files. Coordinate systems, units, levels, grids, file versions and model breakdown must align, or apparently precise clash results will be based on misplaced or outdated geometry.

CNE defines a federation cadence suited to the design and construction programme. At each agreed exchange, we verify incoming revisions, rebuild the combined model and issue a known coordination baseline for the next clash cycle.

A federation process with control

01
Federation strategy

We define included disciplines, model segmentation, exchange formats, revision rules and the cadence for coordination updates.

02
Spatial alignment

Shared coordinates, project grids, levels, units and rotations are checked before discipline files are combined.

03
File and revision control

Incoming models are logged by source, status and revision so superseded information does not return to the coordination set.

04
Native and IFC assembly

Revit, Navisworks, Solibri and IFC inputs are combined using a workflow appropriate to the project and authoring platforms.

05
Federated model package

The team receives the combined review model, an index of included files and a clear record of the coordination baseline.

06
Federation update log

Each refresh records additions, removals and changed revisions, allowing later results to be traced to the correct model set.

Navisworks ManageSolibriAutodesk RevitIFCIFC-SG

Alignment is verified, not assumed.

A controlled spatial reference

We check every discipline against the project origin and grid before accepting it into the combined environment.

A dependable review rhythm

Planned federation drops give teams a stable baseline instead of a moving collection of ad hoc files.

Open-format capability

We coordinate native and IFC information without treating software compatibility as proof that the geometry is correct.

Bring every discipline onto the same grid.

Share your model register, exchange formats and coordination programme. CNE will set up a federation workflow that keeps the combined model current and auditable.