Skip to main content

Cable containment

Cable Containment BIM Coordination for Data Centers

The model shows routes. The specification shows fill ratios. Neither replaces the other.

Ardaron editorial · Updated 3 September 2026 · Named technical review pending

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.

Cable containment in a data centre is not incidental routing — it is a primary system that consumes significant ceiling void and floor void space, competes with mechanical services for route priority, and carries cables whose separation rules are set by codes and manufacturer requirements. BIM coordination must treat containment as a first-class discipline, not an afterthought sketched after ductwork is placed.

Why containment coordination matters in data centres

A typical office building has modest cabling density. A data centre has power feeds from multiple switchboards to PDUs, redundant distribution paths (A/B or 2N), control and monitoring cables, fibre backbones and inter-cabinet copper. The volume is high, the separation requirements are strict, and the routes must remain accessible for future adds and changes.

  • Power vs data separation — codes and manufacturers specify physical or barrier separation between power and data cables.
  • Redundant path independence — 2N or 2(N+1) designs need A and B routes to avoid common-mode failure.
  • Fill ratio compliance — containment must not exceed fill limits that affect thermal performance and cable pulling.
  • Accessibility — routes must remain reachable for inspection, replacement and future cable addition.

Containment types and when to use each

Common containment types in DC projects

TypeTypical useCoordination notes
Ladder rackHeavy power cables, large cable bundlesWide spans require frequent supports; coordinate with structure.
Cable tray (solid/perforated)General distribution, lighter loadsPerforated allows ventilation; solid for EMC shielding where required.
Wire basketLighter data/comms cablesCheaper, faster to install; not suitable for heavy power cables.
Conduit/trunkingPoint-to-point protection, floor penetrationsModel critical runs; minor conduits may be indicative only.
Raised floor cable managementUnder-floor distribution to racksCoordinate with floor tiles, floor voids and airflow paths.

The choice affects model complexity. Ladder rack and tray are modelled as continuous systems. Wire basket is often represented as simplified routes. Conduit detail depends on the project scope and level of information need.

Routing principles

Routes should be planned before modelling begins, not discovered during clash detection. Key principles:

  1. Reserve corridors — define containment corridors in section before detailed modelling. Agree priority with mechanical services.
  2. Maintain headroom — under containment must remain above required clearances for access and other services.
  3. Plan for bends — cables have minimum bend radii; containment geometry must accommodate them without forcing sharp angles.
  4. Future capacity — routes should include reserve space for future cable additions; specify how much reserve in the BEP.
  5. Vertical transitions — risers, floor penetrations and vertical drops require coordination with structure, fire compartments and other risers.

Separation and segregation

Separation requirements depend on local codes, cable types and manufacturer specifications. The BIM model must reflect the agreed separation strategy, not invent universal rules.

  • Power/data separation — typically achieved by vertical or horizontal spacing, separate containment runs, or metal barriers. The required distance depends on code and cable type; do not assume a universal figure.
  • A/B path separation — redundant paths must be physically separate to avoid common-mode failure. Model A and B routes distinctly.
  • Fire-rated vs non-rated zones — containment crossing fire compartments requires fire stopping; model penetrations for coordination with fire strategy.
  • EMC considerations — where shielding is required, containment type and bonding affect performance; coordinate with electrical designer.

Support coordination

Containment supports connect to structure — ceiling soffits, steel beams, trapeze hangers from slab. Support locations must be coordinated with:

  • Structural grid and slab reinforcement — avoid clashes with rebar, post-tensioned tendons, embedded items.
  • Other MEP hangers — trapezes often carry multiple services; ensure load distribution and hanger spacing work.
  • Ceiling and raised floor systems — supports must not interfere with ceiling tiles, floor tile lift access or airflow paths.
  • Maintenance access — supports should not block access to valves, dampers or other service points.

Support spacing and load capacity are manufacturer- and cable-load-specific. The coordination model should show support locations at the level of information need — indicative for early design, accurate positions for fabrication-ready models.

Modelling guidance

Level of information need

Early coordination: route centrelines with approximate widths and heights, sufficient for corridor reservation. Detailed coordination: accurate tray/ladder profiles, fittings (bends, tees, reducers), support locations. Fabrication models may require additional detail (exact fitting part numbers, cut lengths) depending on the prefabrication strategy.

Families and standards

Use manufacturer families where available and the BEP permits. Generic families should be parametric — adjustable width, height, bend radius. Naming should follow project standards. Avoid mixing metric and imperial families in the same model.

Data to carry

  • System — identifies which distribution (e.g. A-feed, B-feed, comms backbone).
  • Tray type and size — width, height, material.
  • Fill ratio — current and design-maximum percentage fill.
  • Fire rating — where applicable, indicates rated or non-rated status.

Common coordination failures

Containment modelled after ductwork claims the space

Why it happens. Mechanical discipline started first; containment treated as secondary.

Impact. Containment forced into awkward routes; bend radii violated; maintenance access lost.

Mitigation. Reserve containment corridors in section before detailed modelling begins.

A and B paths share a congested corridor

Why it happens. No explicit separation rule enforced in model.

Impact. Single-point-of-failure risk remains despite 2N design intent.

Mitigation. Model A and B as distinct systems; test separation in clash detection.

Fill ratio exceeded

Why it happens. More cables added without checking fill limits.

Impact. Thermal issues, difficult pulling, code non-compliance.

Mitigation. Track fill ratio as a model parameter; review at each coordination cycle.

Support clashes with structure discovered late

Why it happens. Supports not modelled or not tested.

Impact. Site rework; delays to containment installation.

Mitigation. Model supports at appropriate detail; include in clash tests against structure.

FAQ

Should we model every cable or just the containment?
Model containment — tray, ladder, basket — to the required level of detail. Individual cables are typically not modelled geometrically; cable schedules and fill calculations are handled in documentation. Exception: critical high-voltage or fibre runs may warrant indicative routing for coordination.
What separation distance should we use between power and data?
The project electrical specification and applicable codes define the requirement. Common practice varies (e.g. 150 mm, 300 mm or physical barrier) depending on cable type and shielding. Do not assume a universal rule — verify with the electrical engineer.
How do we coordinate containment with raised-floor voids?
Define the floor void depth, airflow plenum requirements and cable routing zones in section. Containment running under the floor must not block cooling airflow or obstruct tile lift points. Coordinate with mechanical for plenum clearances.
When should supports be modelled?
Indicative supports at coordination stage to reserve structural fixings. Accurate support positions when the design is sufficiently frozen for fabrication or when support clashes are critical (e.g. congested plant rooms).

Sources

  1. 1. CIBSE, KS18: Data Centres: An Introduction to Concepts & Design (2012). https://www.cibse.org/knowledge-research/knowledge-portal/ks18-data-centres-an-introduction-to-concepts-design/. Accessed 2026-09-03.
  2. 2. ASHRAE, ASHRAE Data Center Resources / TC 9.9 Datacom Series (2024). https://www.ashrae.org/technical-resources/bookstore/datacom-series. Accessed 2026-09-03.
  3. 3. Autodesk, Overview of Clash Detective Tool (2026). https://help.autodesk.com/cloudhelp/2026/ENU/Navisworks-Clash-Detective/files/GUID-36D9904E-12F3-4F82-8DD3-C2103DB0BC29.htm. Accessed 2026-09-03.
  4. 4. 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.
  5. 5. 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.

Continue

Have a delivery constraint?

Three ways to start a conversation.

Engineering capacity issue?

Tell us the discipline, the software environment and the capacity you need.

Procurement bottleneck?

Tell us where the team is constrained — enquiries, follow-up, comparison or reporting.

Difficult sourcing requirement?

Send us the specification, the quantity and the date you need it on site.