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.
Revit model setup is the foundation that either enables or undermines coordination. Shared coordinates ensure discipline models align in federation. Worksets control collaboration and link visibility. File structure determines what can be worked on in parallel. Get these wrong at the start, and the project inherits problems that compound over months.
Why setup matters more on DC projects
Data-center projects involve dense MEP coordination across large floor plates and multiple levels. A misaligned electrical model produces thousands of false clashes. A poorly structured mechanical model that cannot be worked on in parallel becomes a bottleneck. These are not theoretical risks — they are common project failures with known causes and known prevention.
Project base point and survey point
Revit has two origin markers: Project Base Point (PBP) and Survey Point (SP). Understanding their purpose prevents coordinate confusion:
Revit origin points
| Point | Purpose | Typical use |
|---|---|---|
| Project Base Point | Defines the project coordinate system origin | Set at a meaningful building location (corner, grid intersection) |
| Survey Point | Locates the project in real-world coordinates | Set to match survey data (national grid, site survey) |
| Internal Origin | Revit internal origin (0,0,0) | Should be near PBP to avoid precision issues far from origin |
For most data-center projects, the PBP is placed at a building corner or grid intersection. The SP is set to match survey coordinates if survey data is provided. The internal origin (which cannot be moved) should be close to the PBP — modelling far from the internal origin causes precision drift.
Shared coordinates workflow
For discipline models to align in federation, they must share a common coordinate system. The standard workflow:
- Designate a host model — typically architectural or a dedicated coordination host — as the coordinate authority.
- Set the host model PBP and SP to the agreed project origin and survey coordinates.
- Other disciplines link the host model and Acquire Coordinates from it (Manage > Coordinates > Acquire Coordinates).
- Each discipline model now shares the host coordinate system. Export using Shared Coordinates.
- Federation tools (Navisworks, ACC) receive models in the same coordinate space.
If the coordinate host is updated (e.g. survey refinement), disciplines must re-acquire. Communicate coordinate changes clearly — an undocumented origin shift will misalign all exports.
Worksets: structure and discipline
Worksets enable worksharing — multiple users working on the same model file. Workset structure should reflect what can be worked on independently:
- System-based worksets for MEP: Electrical Power, Electrical Lighting, Mechanical HVAC, Mechanical Piping, Fire Protection, Plumbing, Controls.
- Zone-based worksets for large floor plates: Hall A, Hall B, Plant Room North, etc.
- Linked model worksets: separate workset for each linked file to control visibility.
- Coordination worksets: clearance envelopes, temporary construction elements, coordination markers.
File structure and linking
Decide how many model files the project needs. Options:
Model file structure options
| Structure | When to use | Considerations |
|---|---|---|
| Single MEP model | Small DC, limited team | Simple; risk of checkout conflicts with larger teams |
| Discipline-split models | Medium DC, clear discipline boundaries | Electrical, mechanical, plumbing as separate files; linked for coordination |
| Zone-split models | Large campus, multiple buildings | Per-building or per-hall models; linked into site federation |
| Hybrid | Complex programmes | Zone split for halls, discipline split within zones |
Linking strategy: link other disciplines as reference (not overlay unless needed for printing). Use Shared Coordinates positioning. Manage links via a dedicated workset for easy visibility control.
Setup checklist
Coordinate setup
Workset structure
File structure
FAQ
- What if the survey data arrives late?
- Start with an assumed origin documented in the BEP. When survey data arrives, update the SP and communicate the delta to all disciplines so they can re-acquire or adjust.
- Can we use different units across disciplines?
- Technically yes — Revit handles unit conversion. Practically, it causes confusion. Agree on project units (metric or imperial) in the BEP and enforce them.
- How do we handle vendor models with different origins?
- Vendors should receive the coordinate strategy before modelling. If a vendor model arrives misaligned, reposition it to match shared coordinates before linking — do not adjust the shared coordinate system to fit the vendor.
Sources
- 1. Autodesk, About Shared Coordinates (2023). https://help.autodesk.com/cloudhelp/2023/ENU/Revit-Collaborate/files/GUID-B82147D6-7EAB-48AB-B0C3-3B160E2DCD17.htm. Accessed 2026-09-03.
- 2. Autodesk, Workflow: Setting up a Workshared Project (2025). https://help.autodesk.com/cloudhelp/2025/ENU/Revit-Collaborate/files/GUID-D9797137-09C7-4F92-AFC3-670202D043E2.htm. Accessed 2026-09-03.
- 3. ISO, ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Part 1: Concepts and principles (2018). https://www.iso.org/standard/68078.html. Accessed 2026-09-03.