BIM for Data Center Prefabrication: Getting the Model Ready for the Factory

This is a delivery-method resource, not project-specific design. Electrical protection, cable sizing, cooling capacity, fire strategy and structural loads require the appointed designers and the applicable codes. Technical review of this cluster by a named senior BIM/MEP lead is pending; do not treat it as sealed guidance.

Prefabrication raises the cost of late coordination. When MEP skids, modular power trains, containment assemblies or cooling modules are manufactured off-site, the geometry is committed before installation. A clash discovered during fit-out is no longer a drawing revision — it is a factory re-work, a schedule delay, or an on-site adaptation that breaks the prefab logic.

Why prefabrication changes BIM workflow

On a traditional site, minor clashes can be resolved with field routing. Prefabrication removes that buffer. The model must be coordination-complete before the freeze date that triggers fabrication. That means: earlier vendor engagement, stricter interface definitions, and a BEP that specifies when vendor models enter and who owns the clash resolution at interfaces.

What typically gets prefabricated on DC projects

• MEP skids — pump sets, heat exchangers, valve assemblies, controls panels.
• Modular power trains — transformer/switchgear assemblies delivered as containerised units.
• Containment assemblies — pre-routed tray sections, ladder racks with pre-punched supports.
• Cooling modules — factory-built chiller plants, modular cooling units.
• Rack and containment systems — hot-aisle/cold-aisle modules, overhead busway sections.
• Structural steel and concrete pre-cast elements — not strictly MEP, but they set the envelope prefab must fit.

The list varies by project, contractor capability and supply-chain strategy. The BIM question is consistent: does the model define the interface before the factory freezes?

Model readiness for prefabrication

A design-intent model is not a fabrication model. Different information need at different stages. What a prefab model requires:

Interface control

The boundary between a prefab module and the site-installed work is the interface. Pipe flanges, electrical terminations, structural connections, containment entries. These must be defined, frozen and coordinated separately from the internal module geometry.

• Document interface locations in the model as explicit objects (connection points, interface markers).
• Freeze interface geometry before internal module detail — modules can develop inside a fixed envelope.
• Test interfaces against site models (clash detection at boundary, not inside the module).
• Clarify ownership: who updates the interface if site conditions change?

Tolerances and fit

Prefabricated modules have manufacturing tolerances (factory accuracy) and site tolerances (as-built slab levels, structural deviations). The model must accommodate both. Typical approach:

1. Define nominal geometry in the model (ideal positions).
2. Agree adjustment zones at interfaces (e.g. plus or minus 25 mm for flexible connections).
3. Document tolerance assumptions in the BEP — do not assume everyone is working to the same numbers.
4. Where available, incorporate survey or scan data to validate site conditions before module delivery.

Vendor model integration

Prefab suppliers provide their own models — often in native Revit, IFC or simplified STEP/DWG. Those models must enter the federation under the same rules as internal discipline models.

• Same coordinate origin — acquire shared coordinates from the project host.
• Same naming convention — or a documented mapping.
• Same exchange milestone — models arrive before freeze, not after.
• Ownership clarity — vendor model is for information vs vendor model is the contractual container.

Common prefab BIM failures

FAQ

Should the design team or the prefab supplier own the model?

Depends on the contract. The design team typically owns the coordination model; the prefab supplier owns their fabrication model and delivers a representation (not necessarily the fabrication file) for coordination. The BEP should clarify what each party provides.

What file format should vendor models use?

Native Revit is easiest for Revit-based federations. IFC works for open exchange but may lose parameters. Agree the format in the BEP and test it early — do not discover format issues at freeze.

How do we handle prefab schedule changes?

The BEP should define the process for late changes: who is notified, what impact assessment is required, who approves revised interfaces. Prefab modules may have long lead times; late changes are expensive.