Revit for Data Center Projects: A Practical Delivery Workflow

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.

A practical Revit workflow for data-center delivery is: one coordinate strategy, named file ownership, worksharing via local copies of a central (or cloud worksharing), disciplined links, and issue of drawings from a healthy model. Autodesk’s own help on shared coordinates and worksharing is the software authority; the BEP is the project authority.

Model setup

• Client template, title blocks, units, view templates.
• Agreed workset (or equivalent) strategy — by system or by zone, not both ad hoc.
• Family strategy: when to use client content, when to request a new family, when a placeholder is enough.
• View discipline so electrical sheets do not leak mechanical annotation.

Shared coordinates and linking

Autodesk: when several models must know their position relative to each other, use shared coordinates, derived from one defining file — typically acquire from a site/building host, or publish from the host to links. Mixing internal origins across electrical and mechanical files is how false clashes are born. After each new link, verify positioning (including Auto — By Shared Coordinates where that is the project rule) before modelling proceeds.

Worksharing

Autodesk’s worksharing workflow: enabling worksharing creates a central model that stores changes and ownership; team members work in local copies and publish/load changes from that central. Do not edit the central as if it were a single-user file. Cloud worksharing changes where the central lives; it does not remove the need for ownership discipline. On data-centre files, sync cadence is a coordination tool: stale locals create phantom clashes.

Model health, schedules, federation

• Warnings, unused links, imported CAD, in-place families that should have been content.
• Schedules only where the parameters actually exist — a quantity schedule is not a take-off certificate.
• Federation in Navisworks or ACC from Published or Shared states defined in the BEP, not from whoever last saved a local.
• Clash Detective, where used, on a test matrix — not as a substitute for model hygiene.