Guides · Reference
MDF/IDF cabling schedules
A cabling schedule is the contract between the design and the crew that pulls it: every cable, where it starts and ends, how long it runs, and what it is called. Here is what belongs on one, the standards behind it, and how to keep it in sync with the design.
One drop, documented
- Cable
- type and rating, plenum or riser
- Endpoints
- closet · panel · port → device
- Distance
- validated against TIA-568
- Label
- TIA-606-D administration format
The row an installer pulls to and an inspector checks.
The closets
MDF, IDF, and the tiers between them
A cabling schedule only makes sense against the topology it serves. Cabling homes to closets, and closets sit in a tiered network.
The MDF is the building’s main distribution frame — the primary telecom room where the carrier hands off and the core switching lives. Each IDF is an intermediate closet serving a floor or a zone, cabled back to the MDF over a backbone. Horizontal runs go from a closet to the devices; backbone runs tie the IDFs to the MDF.
WAN
The carrier hand-off and edge routing.
Perimeter
Firewall and the security boundary.
Core
High-speed switching between distribution blocks.
Distribution
Aggregation, usually one block per IDF.
Access
The edge ports every device homes to.
The document
What a cabling schedule contains
An illustrative example — the format, not a real project. Each row is one cable: identified, typed, endpointed, measured, and labelled.
| Cable ID | Type | From (closet · panel · port) | To (device) | Length | PoE |
|---|---|---|---|---|---|
| A-101 | Cat6A U/UTP | IDF-2 · PP-A · 01 | CAM-LOBBY-01 | 42 m | bt Type 3 |
| A-102 | Cat6A U/UTP | IDF-2 · PP-A · 02 | AP-OPEN-04 | 31 m | bt Type 4 |
| A-118 | Cat6 U/UTP | IDF-2 · PP-B · 06 | ACS-DOOR-12 | 58 m | at |
| F-01 | OM4 · 12f MPO | MDF · FDP-1 | IDF-2 · FDP-2 | 77 m | — |
Copper rows carry the run distance so the 100-metre channel limit can be checked; the fibre row (F-01) carries its strand or MPO group and colour coding instead. Both sides of every patch-panel port are tracked, so nothing is double-booked when the crew terminates.
The standards
What governs the schedule
A schedule is only useful if everyone reads it the same way. Four standards make that possible.
ANSI/TIA-568
Cabling and distance — the 100 m balanced-twisted-pair channel (90 m permanent link + cords).
ANSI/TIA-606-D
Administration: how every cable, port, and closet is identified and labelled.
ANSI/TIA-598
Optical-fibre colour coding for strands, buffer tubes, and connectors.
BICSI TDMM
Design and rack-placement practice — pathways, closets, and cabinet order.
On the platform
Derived from the model, not typed twice
The schedule is not a document you maintain alongside the design — it is a projection of it.
Every device on the plan is a drop. The cable-path optimizer assigns each one to a closet and a pathway, run lengths come off the anchored plan scale and are validated against the TIA-568 limit, PoE classes come from the datasheet, and labels follow TIA-606-D. Rack elevations for the MDF and each IDF order themselves to BICSI placement conventions — heavy gear low, distribution logical, patching where hands can reach it. Change the design and the schedule, the topology, and the bill of materials all re-derive together.
Cabling schedule questions
What is the difference between an MDF and an IDF?
The MDF — main distribution frame — is the building’s primary telecom room, where the carrier hands off and the core lives. An IDF — intermediate distribution frame — is a satellite closet that serves a floor or a zone and homes back to the MDF. In cabling terms, horizontal runs go from an IDF (or the MDF acting as one) to the devices, and backbone runs tie the IDFs to the MDF.
What belongs in a cabling schedule?
At minimum: a unique cable ID, the cable type and rating, the from and to endpoints (closet, patch panel, and port on one side; device on the other), the run length, the PoE class where it applies, and the label per the administration standard. Fibre backbones add strand or MPO group assignments and their colour coding. The schedule is what an installer pulls to and an inspector checks against.
How long can a horizontal cable run be?
ANSI/TIA-568 sets the balanced-twisted-pair channel at 100 metres — a 90 metre permanent link from the patch panel to the outlet, plus up to 10 metres of patch and equipment cords combined. Design past that and the link is out of spec regardless of what the cable tests at, which is why the run length belongs in the schedule and gets validated, not eyeballed.
How does SiteOps Command produce the schedule?
It derives from the model. Every device you place is a drop; the cable-path optimizer assigns each one to a closet and pathway, run lengths come off the real plan scale, PoE classes come from the datasheet, and labels follow TIA-606-D — so the per-closet schedule, the topology, and the bill of materials all describe the same design. Change the plan and the schedule re-derives instead of being re-typed.
Get the schedule from the design, not a spreadsheet
Place the devices once — the cable schedule, the labels, and the pull plan follow, validated against the standards. Talk to us about what your team documents.