Delivering a cabling project: from requirements to handover

The earlier lessons covered the parts of a cabling plant one at a time: spaces and topology, media, copper performance, fibre physics, transceivers, high-density fibre, testing, pathways, AI clusters, cabinets and administration, and the outside plant. This final lesson puts them together in the sequence a real project follows, from the first requirements meeting to the handover of a documented, tested plant, and works through the main design calculations for a complete data hall. It also covers coordination with the other trades, quality control during installation, and the life of the plant after handover.

Project phases

Data centre cabling is designed and built as part of the larger facility project, and follows its phases:

• Requirements and concept: the owner's network architecture, cabinet counts, densities, redundancy level, growth plan and standards. The cabling designer turns these into a topology, space plan and media strategy.
• Design development: locations of every space (entrance rooms, MDA, HDAs), pathway routes and sizes, cabinet layouts, fibre counts and connector types, and coordination with structural, electrical, mechanical and fire protection designs.
• Construction documents: drawings, schedules and a specification precise enough for contractors to price and build without guessing.
• Tender and award: contractors price the work; the designer reviews bids and clarifies questions.
• Construction: submittals, installation, inspections, testing and correction of defects.
• Handover: as-built records, test results, warranty registration, training and operation and maintenance documents.

Cabling is often treated as a late, minor trade, but its pathways, spaces and power and cooling for network racks must be fixed early. A pathway that clashes with a cooling pipe found during construction costs far more to fix than one found in design.

Design deliverables

A complete cabling design package usually includes:

• A topology or riser diagram showing every space and the cabling between them, with fibre and copper counts.
• Floor plans with pathway routes, sizes and heights, cabinet positions with grid identifiers, and the locations of entrance facilities.
• Cabinet elevations for each cabinet type: panels, managers, PDUs and equipment positions.
• Schedules: trunk cables with identifiers, fibre counts, connector types and lengths; panel and cassette schedules; copper link schedules.
• Details: firestopping, bonding, tray supports, cabinet entry, building entrance.
• A specification: products (or performance requirements), installation methods, testing (Lesson 7), labelling (Lesson 10), submittals, warranty and acceptance.

Increasingly, the design is built as a 3D building information model (BIM), in which cable trays, busway, pipes and ducts can be checked for clashes automatically, and from which trunk lengths can be measured directly.

Worked design: a 160-cabinet data hall

The following example draws the main calculations together. An operator is fitting out a data hall for general-purpose cloud computing:

• 160 server cabinets in eight rows of twenty, 600 mm wide, at 10 kW each, with hot-aisle containment.
• A network row in the centre of the hall acting as the main distribution area, with spine and aggregation switches; leaf switches are top-of-rack in each server cabinet.
• Each server cabinet connects to the network row with two 144-fibre single-mode trunks (one to each of two redundant network cabinets), terminated in MPO-16 cassettes or panels at both ends.
• Each cabinet also needs two Category 6A links for out-of-band management.

Step 1: Trunk lengths and quantities

Each trunk runs along its row's tray to the main cross tray, across to the network row, and down to the panels, plus slack. Because every cabinet is in a different position, trunk lengths vary; ordering them to length (rounded up to a standard increment) avoids large slack coils.

import math
from collections import Counter

# Trunk lengths and bill of materials for one data hall.
# Cabinets on a 0.6 m grid; network row (MDA/HDA) at the centre of the hall.
rows, cabs_per_row = 8, 20
cab_width, row_pitch = 0.6, 3.6       # metres: cabinet width, row-to-row spacing
mda_row = rows / 2 - 0.5              # network row sits between rows 4 and 5
mda_x = cabs_per_row * cab_width / 2  # network cabinets at mid-row
drops, slack = 2 * 2.5, 3.0           # down to the panels at each end, plus slack

lengths = Counter()
for r in range(rows):
    for c in range(cabs_per_row):
        x = (c + 0.5) * cab_width
        run = abs(x - mda_x) + abs(r - mda_row) * row_pitch + drops + slack
        lengths[5 * math.ceil(run / 5)] += 2      # two 144-fibre trunks per cabinet

total_trunks = sum(lengths.values())
total_m = sum(k * v for k, v in lengths.items())
print("trunk length  quantity")
for k in sorted(lengths):
    print(f"{k:8d} m  {lengths[k]:6d}")
print(f"trunks {total_trunks}, cable {total_m} m, fibres {total_trunks * 144}")
cassettes = total_trunks * 144 // 16 * 2         # MPO-16 cassettes at both ends
print(f"MPO-16 connections to terminate (both ends): {cassettes}")

trunk length  quantity
      15 m      96
      20 m     104
      25 m      96
      30 m      24
trunks 320, cable 6640 m, fibres 46080
MPO-16 connections to terminate (both ends): 5760

The result: 320 trunks in four lengths, 6.6 km of cable and 46,080 fibres, with 5,760 MPO-16 connections to terminate or to buy pre-terminated. Pre-terminated, factory-tested trunks are the obvious choice at this scale, ordered from the schedule and labelled at the factory.

Step 2: Loss budget

Step 3: Pathway sizing

Step 4: Redundancy and entrances

Each server cabinet has two trunks to two network cabinets on separate routes along the tray (or on trays on opposite sides of the row), so a single cut does not isolate it. Carriers enter through two entrance rooms at opposite corners of the building, with diverse conduit routes to the network row (Lesson 11). Network cabinets A and B are fed from separate power paths. Together these meet the redundancy requirements typical of a TIA-942 Rated-3 facility.

Step 5: Labelling and records

Every trunk, cassette, panel and port gets an identifier from the site scheme (Lesson 10), printed at the factory on the pre-terminated trunks. The schedule produced in Step 1 becomes the initial record in the DCIM system, and test results are attached to each link at acceptance.

Coordination with other trades

Cabling shares space with power, cooling and fire protection. Typical coordination points:

• Heights: overhead space is layered, for example lighting and sprinklers highest, then cable trays, then busway, with liquid-cooling pipes routed so that leaks cannot drip onto cabling.
• Separation from power: distances between data trays and power busway or cables, which depend on the shielding and the power circuits (Lesson 8).
• Supports: cable trays may share strut supports with other services only if the supports are designed for the combined load.
• Firestopping: every penetration of a fire-rated wall or floor needs a listed firestop system that can be reopened for new cables.
• Bonding: trays, cabinets and network equipment connect to the telecommunications bonding backbone and the building grounding electrode system.
• Cooling: blanking, cable entry seals and the location of network cabinets in the containment design.

Clash detection in a shared BIM model, and regular coordination meetings, catch most conflicts before installation.

Quality during installation

The specification sets the requirements; the construction phase checks they are met:

• Submittals: the contractor submits product data, certifications, test equipment calibration and installer qualifications for approval before ordering.
• Mock-up: one cabinet and a section of tray installed first and inspected, to agree the standard of workmanship.
• Inspections at key stages: pathways and supports before cable is pulled, firestopping before it is covered, cabinets after dressing.
• Testing as work proceeds, area by area, with results reviewed promptly so problems are not repeated.
• A deficiency list (punch list) of items to be corrected before acceptance.

Common defects found at inspection include exceeded bend radius at tray drops, crushed cables under ties, missing firestopping, missing labels or labels that do not match the records, unbonded trays and dirty connectors.

Handover and the life of the plant

At handover the owner receives as-built drawings, schedules, test results in native and summary form, warranty certificates, product data and maintenance guidance, and the DCIM records loaded and verified. A structured cabling warranty, typically 20 to 25 years from the manufacturer, usually requires installation by a certified installer and test results meeting the manufacturer's criteria.

The plant then lives through many changes:

• Daily moves, adds and changes under change control (Lesson 10).
• Equipment refreshes every three to five years, which may change optics and connector types, and ideally reuse the trunks.
• Expansions into new halls, connected through the backbone.
• Eventual decommissioning, when abandoned cables are removed and materials recovered. Copper and fibre cables, metal trays and cabinets can be recycled; sustainability reporting increasingly counts the embodied carbon of cabling materials as well as the energy of the equipment it connects.

A plant designed with clear topology, enough pathway space, single-mode fibre to every cabinet and good records will serve several generations of equipment. A plant without those will be rebuilt, at much higher cost, while the data centre is running.