RoomScene 3D
Download

Patch panel documentation: labelling, schedules and tracing

A cable record is only useful if someone can stand in front of a rack at night and follow a signal with it. That takes a labelling scheme people actually apply, a schedule with the right columns, and patch panels documented as two-sided devices.

Published

Start with a labelling scheme

The scheme matters less than everyone using the same one. TIA-606 describes a full administration scheme for structured cabling, and it is worth reading. Many broadcast facilities use a simpler local version, because their racks hold as much coax and fibre as copper and the people patching are not always network engineers.

Three kinds of identifier cover most of it:

IdentifierPatternExampleMeaning
Port positionrack-panel-portA07-PP1-05Rack A07, first patch panel, port 5
Patch or device cabletype-numberNW-0001Network cable number 1
TrunkTR-from-to-numberTR-A07-A01-05Fifth trunk from rack A07 to rack A01

A few rules that keep a scheme alive:

  • The same label at both ends. A cable has one ID, printed on a sleeve or flag near each connector. Do not label one end with the A port and the other with the B port; the schedule holds that.
  • Prefixes by signal type. NW- for network, FO- for fibre, SDI- for video coax, AU- for audio. An engineer who sees the prefix knows what kind of patch cord to reach for.
  • Numbers are never reused. When NW-0412 is removed, the number retires with it. Reuse is how a record ends up describing two cables.
  • Rack names come from the floor. Use the names painted on the racks, such as A07 or B12, not a room drawing's internal numbering.
  • Panels are named after their rack. PP-A07-1 is the first panel in A07, counted from the top. When it moves, it gets a new name.

Patch panels have two sides

The most common documentation mistake is to treat a patch panel as one row of ports. It is two rows joined back to back. Front port 5 is where the patch cord plugs in; rear port 5, written R5, is where the permanent cable terminates. The panel connects them internally.

If the record only has front ports, a trace stops at the panel. If it has both sides but no pairing, a trace cannot know that R5 continues to port 5 rather than port 6. Document panels with front ports 1…N, rear ports R1…RN, and an explicit pair between each front and its rear. Then a path goes through the panel the way the copper does.

Fibre adds two details. An MPO trunk often lands on a cassette that breaks it out into LC ports on the front; record the trunk to the cassette and the cassette ports to their positions. And polarity matters: note whether a link is straight or crossed so that whoever patches it does not have to find out with a light meter.

Video jackfields need their own note. Many are normalled: with nothing plugged in, the rear connections pass the signal straight through. Record the normalled path as the default and any patch cords as overrides, otherwise the schedule shows a gap where the signal actually flows.

Trunks between racks

Trunks are the permanent cables between racks: copper bundles, fibre trunks, multicore coax. They usually run from the rear of a panel in one rack to the rear of a panel in another, along the overhead tray or under the floor.

  • Give each conductor or pair its own record, not just the bundle. TR-A07-A01-05 is one link between PP-A07-1 R5 and PP-A01-1 R12.
  • Record the length. When a 10GBASE-T link misbehaves, the first question is how long the whole channel is.
  • Note the route if there is more than one tray. It saves a lot of ceiling tiles during a fault.
  • Mark spares as spares. A trunk with eight cores and six in use has two free paths that the next project will want.

The cable schedule

The schedule is a table with one row per cable. Every column should be something an engineer can check against the physical cable.

LabelA deviceA portB deviceB portTypeLength
NW-0001ARC-SRV-01iDRACPP-A07-15Cat6A2 m
TR-A07-A01-05PP-A07-1R5PP-A01-1R12Cat6A18.5 m
NW-0002PP-A01-112NET-A02Gi1/0/12Cat6A3 m
SDI-0215PO-SRV-04SDI OUT 1PP-B03-27Coax 75 Ω1.5 m

Keep port names exactly as the device labels them: Gi1/0/12, not “port 12”, SDI OUT 1, not “out1”. Use device names that match the inventory and monitoring, so a cable record, a Zabbix host and a rack position all point to the same box. The same columns work for copper, fibre and coax; only the type changes.

Tracing a path, hop by hop

With paired panels and consistent names, a trace is mechanical. Start at a device port, follow the cable to its other end, and if that end is a panel, cross to the paired port on the other side and continue. Using the rows above:

  1. ARC-SRV-01 iDRAC, rack A07 U21
  2. NW-0001, Cat6A, 2 m, to PP-A07-1 port 5, then through the panel to R5
  3. TR-A07-A01-05, Cat6A, 18.5 m, to PP-A01-1 R12, then through the panel to port 12
  4. NW-0002, Cat6A, 3 m, to NET-A02 Gi1/0/12, rack A02

Three cables, 23.5 m, two patch panels. In a spreadsheet you do this with filters and a finger on the screen. It works for one path. It does not work when a switch is replaced and someone needs to know every server behind its 48 ports.

Live records, drafts and audits

Rack layouts change through plans: a draft, an approval, a move. Cables are different. A cable record describes what is plugged in now, so it should change when the cable does, not when a project closes. Planned cabling belongs in the work order; the record changes when the engineer reports the patch as done. Keep a change log with who and when for every edit, because the first question after an outage is what changed.

Records drift anyway. An audit catches it before a fault does:

  1. Pick one or two racks per week instead of the whole room once a year.
  2. For every cable in the rack, read the label and check both ends against the schedule.
  3. Look for unlabelled cables and for labels the schedule does not know.
  4. Fix the record the same day. A list of discrepancies left for later is a second schedule.

Doing this in RoomScene 3D

RoomScene 3D keeps cables on the same device records as the rack layout. Patch panels are created with front ports 1…N and rear ports R1…RN, paired, so a trace passes through the panel. Press Trace on any port and the card lists each hop with cable label, type and length, while the 3D scene draws the route through the racks: down the side channel inside a rack, over the overhead tray between racks. The cable tracing page shows the example above step by step.

The cable list imports from Excel with exactly the schedule columns above: label, A device, A port, B device, B port, type, length. Missing ports are created, “R12” on a patch panel is read as rear port 12, and a label that already exists with other ends is moved, not duplicated. Conflicts show in a preview before anything is written. Cables are live records, not part of a layout draft, and every change goes to the change log. Fibre and coax/SDI are documented the same way as copper. There is no automatic discovery: cables come from your list or the device card.

For the racks themselves, see how to document broadcast racks and the rack elevation page. To try it with your own schedule, the 30-day trial imports a cable list on the first day.

Try it on your own rooms

RoomScene 3D is a 30-day trial with every feature on. Install it on a test server and import one room.

Download the 30-day trial Ask for a quote

contact@roomscene3d.com · tahirfeyzioglu@gmail.com