400G Readiness Review: OM5 Trunks, a Single Conduit, and an 800G Roadmap
A hospital is building a 4-row, 160-rack data hall. Maximum intra-row run is 20 m; the row MDA to the entrance room is 110 m. The 10-year roadmap calls for 400G server uplinks and an 800G refresh after that. The incumbent integrator proposes OM5 24-fiber MPO-12 trunks to every rack, 400GBASE-SR8 optics, and one 4-inch conduit per row from the MDA, sized at 40% fill against a proposed trunk outside diameter of 6.5 mm. Single-mode backbone from the entrance room to each MDA already exists for the building management system, with 60% spare strands. The electrical contractor offers a change adding two 2-inch conduits per row. The cabling RFP must be released in four weeks; MPO trunk lead time is 10 weeks, and the owner wants the design fixed before release to avoid change orders during construction.
1. Compare the proposed SR8/OM5 rack trunk against single-mode alternatives on fiber count and scalability.
Read the worked answer
Count fibers per link, because that is what drives trunk size, tray fill, and panel density. 400GBASE-SR8 uses 8 lanes over 16 fibers per link. At two uplinks per rack across 160 racks - 320 links - that is 5,120 fibers, or roughly 427 twelve-fiber trunk equivalents, all inside a 20 m row. 400GBASE-DR4 is 8 fibers per link over single-mode (500 m reach): 2,560 fibers. 400GBASE-FR4 is duplex, 2 km: 640 fibers total.
SR8 over OM5 is defensible only where runs exceed copper and single-mode does not exist. Here the run is 20 m and the MDA already has spare single-mode. The scalability problem is decisive: 800G multimode options multiply lane count again, while single-mode 800G generations reuse duplex or 8-fiber MPO physical plants. Recommend single-mode from the rack to the row MDA, FR4 where duplex density matters, DR4 where 8-fiber MPO is already the standard. Keep multimode DAC/AOC for the 3 m top-of-rack case if cost demands it.
2. Is the 40% fill calculation on one 4-inch conduit per row a sufficient pathway design?
Read the worked answer
The arithmetic may close while the design still fails. A 4-inch conduit at 40% fill has roughly 3,200 mm² of usable area; a 6.5 mm cable occupies about 33 mm², so the fill rule appears to permit nearly 100 cables. Fill is not the binding constraint here - bend radius, pull tension over a 20 m run with multiple sweeps, termination space at the MDA, and the ability to add cable later without disturbing live trunks are.
The decisive objection is diversity. One conduit per row means a single pathway serves every rack uplink in that row; a firestop breach, a pulled cable, or a construction strike takes the row down with no alternate path. Accept the contractor's two additional 2-inch conduits per row, and designate them as physically separated paths - separate trays or separate sleeves at the wall penetration, not two conduits strapped to the same Unistrut. Then re-run fill on the remaining conduit after the design peak, not the day-one count.
3. What must be written into the RFP now to protect the 800G refresh?
Read the worked answer
Specify the physical layer as single-mode, OS2, with connector polish and ferrule matched to the optic generation you expect (APC for outside plant and long-reach, UPC where the MPO ecosystem requires it), and state that mixing is prohibited so nobody substitutes mid-project. Specify fiber count per rack based on the roadmap, not the first build: at minimum two duplex pairs per rack plus 100% spare, or 8-fiber MPO if DR4 is the target architecture.
Require polarity method, mapping tables, and as-built documentation as deliverables, plus 100% OLTS with bidirectional results and 100% end-face inspection with records - the warranty will demand them and retro-testing costs far more than testing during installation. Require factory-terminated MPO trunks with measured loss per fiber, not per trunk. Finally, write an explicit growth clause: the pathway must accommodate the 800G fiber count at 40% fill without new construction, and the RFP should require the bidder to demonstrate that calculation.