TIA-942 spaces: ER, MDA, HDA, ZDA and EDA

On Jamal's second day, Nadia hands him a floor plan of Hall A with colored boxes drawn on it and asks him to find each box in the hall. The boxes are labeled ER, MDA, HDA and EDA, and two small ones are labeled ZDA. By lunchtime he has walked every row, and the letters have stopped being an alphabet soup. They are the names that the data center cabling standards give to the spaces where cabling is terminated and cross-connected, and every drawing, ticket and label at Stonebridge uses them.

Where the names come from

ANSI/TIA-942 is the North American standard for data center telecommunications infrastructure. Its current edition, TIA-942-C, was published in 2024. Alongside it, ISO/IEC 11801-5 covers the same ground internationally, with slightly different names, and the ANSI/BICSI 002 design practice adds detailed guidance. Canadian data centers generally follow TIA-942 directly, as most specifications in Quebec and Ontario name it. A technician does not need to know the standards clause by clause, but needs the vocabulary, because the design drawings and the labels are built on it.

TIA-942 describes the data center as a set of functional spaces connected by backbone cabling and horizontal cabling, exactly as LVT-120 described a building: backbone between the main rooms, horizontal to the work area. In a data center the work area is a cabinet full of equipment, and the spaces are mostly rows of cabinets rather than rooms.

The spaces one by one

Colocation operators also use a name the standard does not: the meet-me room, which is usually the entrance room or a room next to it where cross-connects between carriers and customers are made. At Stonebridge the meet-me room is a secured part of the campus MDA. Its job is different enough that Lesson 9 is about it alone.

Backbone and horizontal

Cabling between the ER, MDA, IDA and HDA is backbone cabling. It is mostly single-mode fiber trunks, because these links are long and carry the highest speeds, with some multimode fiber and a little copper for management. Cabling from an HDA to the EDA, through a ZDA if there is one, is horizontal cabling. In Hall A it is a mix of Category 6A copper and multimode or single-mode fiber; in the newer halls it is almost all fiber. The standards limit the length of horizontal copper channels to 328 ft including cords, as LVT-130 explained, and the optical reach depends on the speed and the fiber type, as Lesson 5 shows.

Two rules about the hierarchy matter to technicians. First, there should be no more than one cross-connect level of each kind in a path, so that a link does not wander through a chain of panels, each adding loss and each a place to make a mistake. Second, a ZDA has no active equipment: it is just a panel or a box where horizontal cables can be consolidated near a group of cabinets, so that the cabinets can be added or moved without re-cabling back to the HDA.

What TIA-942-C changed

Nadia points out a few changes in the 2024 edition that show up in the newest halls. Cabinets in the MDA, IDA and HDA must be at least 31.5 in wide, which gives room for vertical cable managers beside the panels. At the equipment outlet the standard still calls for LC and MPO connectors, while elsewhere any optical connector that meets TIA-568.3 is permitted, which opens the door to the very small form factor connectors some manufacturers now make. Horizontal and backbone optical cabling should have at least two fibers, and single-pair balanced copper is now recognized as a horizontal cabling type. The edition also brings in the latest ASHRAE thermal envelope and adds material on edge data centers and immersion cooling.

For Jamal, the practical change is that Hall D's network rows were built to the new edition: wider cabinets, more room for managers, and MPO connectors on everything. Hall A, built in 2014, still has 24 in network cabinets crammed with panels, and its managers are always full.

Reading the hall plan

Every Stonebridge hall has a cabling plan showing each space, the trays between them and the identifier of every cabinet. Identifiers follow the scheme Jamal learned in DCT-130, campus, hall, row and cabinet, with the space type added for network cabinets:

• YUL2-A-MDA-02 is the second cabinet of Hall A's main distribution area.
• YUL2-A-HDA-31 is the network cabinet at the end of row 31, serving the cabinets in that row.
• YUL2-A-ZDA-2 is the second zone box under the floor of Hall A.
• YUL2-A-31-03 is an equipment cabinet, an EDA cabinet, in row 31.

At IAD-3 the same identifiers start with IAD3. A panel inside a cabinet adds a panel number, as in YUL2-A-HDA-31-PP4, and a port adds a port number. Lesson 11 shows how these identifiers become labels and records.

Following a path

Nadia gives Jamal a challenge: trace the path a Bayview Credit Union server in cabinet A-31-03 takes to reach the carrier that serves its branch network. He writes it out space by space.

# Trace a path through the TIA-942 spaces and check the cross-connect levels
path = [
    ("A-31-03", "EDA", "server, then a cord to panel PP1 at the top of the cabinet"),
    ("A-HDA-31", "HDA", "horizontal trunk from PP1 ends here; cord to the row access switch"),
    ("A-MDA-02", "MDA", "backbone trunk from the access switch uplink; cord to the hall core"),
    ("CMP-MDA-01", "MDA", "campus MDA and meet-me room: cross-connect to the carrier panel"),
    ("ER-N", "ER", "carrier's outside plant cable, spliced to the building trunk"),
]
levels = {}
for cab, space, what in path:
    levels[space] = levels.get(space, 0) + 1
    print(f"{space:4} {cab:11} {what}")
print("Spaces passed:", ", ".join(f"{s} x{n}" for s, n in levels.items()))
extra = [s for s, n in levels.items() if n > 1 and s not in ("MDA",)]
print("Path follows the hierarchy" if not extra else "Check: repeated levels " + ", ".join(extra))

EDA  A-31-03     server, then a cord to panel PP1 at the top of the cabinet
HDA  A-HDA-31    horizontal trunk from PP1 ends here; cord to the row access switch
MDA  A-MDA-02    backbone trunk from the access switch uplink; cord to the hall core
MDA  CMP-MDA-01  campus MDA and meet-me room: cross-connect to the carrier panel
ER   ER-N        carrier's outside plant cable, spliced to the building trunk
Spaces passed: EDA x1, HDA x1, MDA x2, ER x1
Path follows the hierarchy

The path passes two MDAs because Stonebridge has a hall MDA in each hall and a campus MDA for the whole site, an arrangement the standard allows in large multi-hall data centers. It does not pass through two HDAs or two ZDAs, which would mean someone had cabled around the plan.

Distances in the hierarchy

The spaces are placed so that the cabling between them stays within the limits of the media. Copper horizontal channels must stay within 328 ft; 10GBASE-T over Category 6A has the same limit. Multimode fiber links at 400 and 800 Gb/s are limited to tens of meters, so the HDA serving a row of high-speed equipment must be close to it. Single-mode backbone links can be hundreds of meters or more. A technician sees these limits in practice when a ticket asks for a link that the design never intended, for example a customer who wants a multimode link from a cage at the far end of Hall A to the campus MDA. The answer is a single-mode link or a different path, not a longer cord.

# Check whether a requested link stays within its medium's reach
reach_m = {"Cat 6A 10GBASE-T": 100, "OM4 100G-SR4": 100, "OM4 400G-SR4": 100, "OS2 400G-DR4": 500, "OS2 800G-DR8": 500}
requests = [("A-31-03 to A-HDA-31", "Cat 6A 10GBASE-T", 38), ("A-31-03 to CMP-MDA-01", "OM4 400G-SR4", 212),
            ("B-12-09 to B-HDA-12", "OM4 400G-SR4", 46), ("D-3-07 to D-4-02", "OS2 800G-DR8", 61)]
for name, medium, meters in requests:
    ok = meters <= reach_m[medium]
    print(f"{name:22} {medium:17} {meters * 3.281:5.0f} ft  {'within reach' if ok else 'too long: choose another medium or path'}")

A-31-03 to A-HDA-31    Cat 6A 10GBASE-T    125 ft  within reach
A-31-03 to CMP-MDA-01  OM4 400G-SR4        696 ft  too long: choose another medium or path
B-12-09 to B-HDA-12    OM4 400G-SR4        151 ft  within reach
D-3-07 to D-4-02       OS2 800G-DR8        200 ft  within reach

The second request fails, which is exactly the kind of thing Nadia wants a technician to catch before ordering cords. The reach values in the code are the typical figures; the real limit for a link is set by its loss budget, as Lesson 11 shows.

Spaces outside the computer room

Not every cabling space is in a hall. Each Stonebridge campus also has the telecommunications rooms that serve the office floors, the security control room, the network operations room and the building management system, and each of them is cabled back to the campus MDA by backbone cabling, just as an office building would be. The standards treat them as ordinary building spaces, with the building cabling rules from LVT-120. Jamal learns to recognize the difference in the labels: anything in a TR follows the building scheme, and anything in a hall follows the data center scheme. A ticket that asks for a link from an office floor to a hall always passes through the campus MDA, never through a shortcut between a TR and a hall HDA, because the MDA is where Stonebridge's network team can see and secure every connection between the two worlds.

How customers fit into the hierarchy

In a colocation hall, the customer's cage is an EDA from Stonebridge's point of view, but inside the cage the customer often builds its own small hierarchy: a customer MDA cabinet with its routers and firewalls, its own HDA cabinets, and its server cabinets. Stonebridge's responsibility ends at its panel at the top of the customer's first cabinet, the demarcation point, and the ticket for any work inside the cage must come from the customer. A technician who understands both hierarchies can explain to a new customer exactly where Stonebridge's cabling stops and theirs begins, which is one of the questions Nadia hears most often from new tenants.