The short answer
Fiber Schedules
A fiber schedule lists every fiber cable and every strand in it: the cable identifier, its type as single-mode or a multimode grade, the strand count, the buffer tube and strand color by the standard sequence, the patch panel and port at each end, the connector type, the splice points along the route, the length, the use of each strand or its status as spare, and the test results for each strand with the date. It is what a technician uses to find which strand a link is on and which strands are free, what the network drawing references for each fiber link, what the link budget is checked against, and what the reflectometer trace from commissioning is compared with when a link degrades. Patch panels are labeled to match it, and every new link or splice is a change that updates it.
Key points
- One row per strand: cable, tube and strand color, panel and port at each end, use, and test results.
- The standard twelve-color sequence identifies strands; the schedule says which color is which strand number.
- Single-mode and multimode grades are not interchangeable; the type is on every row and every panel label.
- Splices are recorded with their location and loss; the link budget adds them up.
- Test results at commissioning are the baseline; a later trace is compared with them.
- Dark strands are the future; the schedule is where anyone finds out that they exist.
Why fiber gets its own schedule
A copper cable has a handful of conductors that end at terminals with numbers. A fiber cable has twelve, twenty-four, or more strands, each ending at a patch panel port, each usable for a separate link, each tested individually, and each identified by a color inside a colored tube. Two buildings a mile apart may be joined by one cable whose strands serve the SCADA, the telemetry, the cameras, and the phone system, with most of them dark. Without a schedule, nobody knows which strand carries what, which are free, and whether the strand that was just patched is the one the historian depends on.
The columns
| Column | Content |
|---|---|
| Cable identifier | Per the cable numbering convention; on the cable and the panels |
| Fiber type | Single-mode, or multimode by grade; core size |
| Strand count and construction | Total strands, tubes, strands per tube, loose or tight buffer, armor |
| Tube and strand | Tube color and number, strand color and number within the tube, and the overall strand number |
| A end | Building, room, patch panel name, port number, connector type |
| B end | The same for the far end |
| Splices | Location of each splice enclosure and the splice tray position, with the loss measured |
| Length | Cable length from the reflectometer, and the route |
| Use | The link the strand carries, the equipment at each end, and the wavelength; or spare, or dark |
| Test results | Insertion loss at each wavelength, reflectometer trace reference, date, tester |
| Status and notes | In service, spare, damaged; bend radius or handling notes |
The color sequence
| Position | Color | Position | Color |
|---|---|---|---|
| 1 | Blue | 7 | Red |
| 2 | Orange | 8 | Black |
| 3 | Green | 9 | Yellow |
| 4 | Brown | 10 | Violet |
| 5 | Slate | 11 | Rose |
| 6 | White | 12 | Aqua |
The sequence is the same for tubes and for strands within a tube, so strand 15 of a 24-strand cable is the green strand in the orange tube. The schedule states the overall strand number and the tube and strand colors so that a technician at a splice tray and a technician at a patch panel agree. Cables with different constructions, such as ribbon fiber, follow their own marking, which the schedule states.
Testing and the link budget
Each strand is tested at commissioning with a light source and power meter for insertion loss at the wavelengths the links use, and with a reflectometer for a trace that shows the length, each splice and connector as an event with its loss, and any bend or break. The results are recorded per strand in the schedule, and the trace files are kept with it. The link budget for a given link, the transmitter power minus the receiver sensitivity, is compared with the measured loss plus a margin; a link with insufficient margin is a link that will fail in the cold. When a link later shows errors, a new trace compared with the commissioning trace shows what changed: a new bend, a dirty connector, a splice that degraded.
Patch panels and labels
- Every patch panel is named, and every port is numbered, on the panel and in the schedule.
- The panel label states the cable identifier and the far end, and the fiber type.
- Port labels state the strand number and, where a link is patched, the link name.
- Patch cords are labeled at both ends with the link name; a patch cord with no label is the one that gets pulled.
- Spare ports are labeled as spare; dark strands are landed and labeled so they can be used without a splice.
Keeping it current
Fiber changes rarely and disastrously: a new link patched onto the wrong strand, a splice case opened for a repair and reclosed with two strands swapped, a new cable added without a record. Every patch, splice, and addition is a change record that updates the schedule, and the annual verification includes a look at each patch panel against the schedule. The schedule and the trace files live with the network documentation, and a copy is on paper in the communications room where the technician opens the panel.
Frequently asked questions
- Can the fiber schedule be part of the cable schedule?
- The cable can be a row in the cable schedule; the strands need their own table, one row per strand, with the test results. Most projects keep a separate fiber schedule that references the cable number, because the strand detail does not fit the cable schedule columns.
- How much loss is acceptable?
- It depends on the link: the transmitter and receiver specifications give the budget, and the measured loss plus a margin of a few decibels must fit inside it. Single-mode links over plant distances have budgets that are hard to exceed; multimode links at higher speeds have small budgets and are the ones to check.
- Who tests the fiber?
- The installing contractor at commissioning, with results submitted per strand as a deliverable, and the utility or its integrator when a link is repaired or a new link is lit. A reflectometer is worth owning for a utility with fiber between sites; a light source and power meter are inexpensive.
- What is a dark strand?
- A strand that is installed, terminated at both ends, and tested, but carries no link. It is the spare capacity of the cable, and the schedule is the only place anyone learns it exists. Utilities that run out of strands usually have dark ones nobody recorded.
Related topics
- Cable SchedulesThe list of every cable with what it is, where it runs, and where it lands: the columns, the numbering convention, types and signal classes, routes through conduits and trays, lengths, terminations, spares, and status from design through as-built.
- Network DrawingsThe two drawings every control network needs: a logical drawing of zones, subnets, VLANs, firewalls, and conduits, and a physical drawing of switches, ports, cables, fiber, radios, and sites. What each shows and why they are sensitive.
- Network SchedulesThe tables behind the network drawings: the address schedule of every device, the switch port schedule of every port, the VLAN table, and the conduit list of what the firewalls permit. How they are built, kept as the single source of truth, and protected.
- How to Test FiberTest a fiber link at acceptance and at fault: inspect and clean every connector, measure end-to-end loss with a light source and power meter in both directions and at the operating wavelengths, and record everything with the fiber schedule.
- How to Troubleshoot an Ethernet ConnectionWork an Ethernet problem one layer at a time: link light and cable, then speed, duplex, and VLAN on the switch port, then address, mask, and gateway, then the application port through the firewall. Each layer has a one-minute test that rules it in or out.
- Commissioning ChecklistFrom energization to handover: the sequence of commissioning activities for a control system, the prerequisites and records for each, who signs what, and the checklist that keeps a project from being declared finished while half of it has never been tested.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.