Labeling and documentation (TIA-606)

A cabling system that cannot be identified cannot be managed. Every cable in a building looks like every other cable of its type, and without labels and records nobody can tell which port in the telecommunications room serves which desk, which fiber strands are spare or which cable can be removed. ANSI/TIA-606, the administration standard, now in its D revision of 2021, sets out how to identify every element of the infrastructure, how to label it and what records to keep. Cobalt Line treats administration as part of the installation, not as paperwork after it: no link is complete until it is labeled at both ends, tested and entered in the records.

What is administered

TIA-606 covers far more than horizontal cables. It assigns identifiers to the spaces of the system, such as telecommunications rooms and equipment rooms; to racks and cabinets; to patch panels and their ports; to horizontal links; to backbone cables and their individual pairs or strands; to pathways such as conduits and sleeves; to firestopping locations; and to the bonding and grounding system's busbars and conductors. Each identifier is unique within its scope, and each is linked in the records to the things it connects. The cable from panel A, port 12 in room 2B to the outlet in classroom 214 is one record, holding its identifier, both ends, its category, its route and its test result.

Classes of administration

The standard scales administration to the size of the system with four classes.

• Class 1 serves a single telecommunications space that serves the whole building, such as a small office with one room. Identifiers are needed for the space, the horizontal links and the bonding busbar.
• Class 2 serves one building with several telecommunications spaces. It adds identifiers for backbone cables, their pairs and strands, the bonding system and firestopping.
• Class 3 serves a campus of several buildings, adding building identifiers and campus backbone cables.
• Class 4 serves several sites, such as an owner with campuses in several cities, adding site identifiers.

Riverside school, with three telecommunications rooms and a separate gymnasium building, is a Class 3 system. The Kellerman Building's ninth-floor tenant space, with its own small room, is Class 1 within the tenant's scope, but it must fit into the building owner's Class 2 records for the building's backbone and risers.

The identifier format

TIA-606 builds identifiers from short codes for each level, joined by separators. Within a building, a telecommunications space is identified by the floor number and a letter for the space: 2B is the second space on floor 2. Patch panels in the space get letters, and ports get two-digit numbers. A horizontal link takes its identifier from the panel port where it terminates in the telecommunications room, written in the form fs-an: floor and space, a hyphen, the panel letter and the port number. Link 2B-A12 terminates on port 12 of panel A in room 2B, and the outlet at the other end carries the same identifier.

Backbone cables are identified by the two spaces they connect and a sequence number, written with a slash: 1A/2B-1 is the first backbone cable between room 1A and room 2B. Individual pairs or strands add a number after a dot: 1A/2B-1.07 is strand 7 of that cable. In Class 3 and 4 systems, a building or site code is added in front, such as RSS for Riverside's main building and GYM for the gymnasium, so that the campus cable RSS-1A/GYM-1A-1 runs from the main building's room 1A to the gymnasium's room. Other elements follow the same logic, with their own letters: a rack identified by its floor-grid location in the room, a bonding busbar as the primary or secondary bonding busbar of its space, a firestop location by its space and number.

Owners often adapt the format. A university may use its own building numbers, a hospital its own room numbers instead of the floor-and-letter scheme, and a school board may require the room number of the outlet on the faceplate as well. Where the owner's standard differs from TIA-606, the owner's standard governs, but Sanjay always checks that it still makes every identifier unique and still lets a technician find both ends of a link from either end.

# Generate and check horizontal link identifiers in the fs-an format
import re
PATTERN = re.compile(r"(?P<floor>\d{1,2})(?P<space>[A-Z])-(?P<panel>[A-Z]{1,2})(?P<port>\d{2})")

def make_ids(floor, space, panel, first, count):
    return [f"{floor}{space}-{panel}{port:02d}" for port in range(first, first + count)]

ids = make_ids(2, "B", "A", 13, 4)
print("outlet faceplate in classroom 214:", ", ".join(ids))
for tag in ids + ["2b-A7", "2B-A100", "12C-AB04"]:
    m = PATTERN.fullmatch(tag)
    if m:
        print(f"{tag:9} ok: floor {m['floor']}, space {m['space']}, panel {m['panel']}, port {int(m['port'])}")
    else:
        print(f"{tag:9} not a valid fs-an identifier")

outlet faceplate in classroom 214: 2B-A13, 2B-A14, 2B-A15, 2B-A16
2B-A13    ok: floor 2, space B, panel A, port 13
2B-A14    ok: floor 2, space B, panel A, port 14
2B-A15    ok: floor 2, space B, panel A, port 15
2B-A16    ok: floor 2, space B, panel A, port 16
2b-A7     not a valid fs-an identifier
2B-A100   not a valid fs-an identifier
12C-AB04  ok: floor 12, space C, panel AB, port 4

Generating labels from the design, rather than typing them on site, is what keeps a large job consistent. Sanjay's design database produces the label files for the label printers, the panel elevations and the outlet schedule from the same list, so the identifier on a faceplate, a panel and a test result can never disagree unless someone types one by hand.

Labels

TIA-606 requires labels to be durable, legible and machine-printed. Handwritten labels fade, smear and are misread. Each horizontal cable is labeled at both ends, within about 12 in of its termination, with wrap-around self-laminating labels whose clear tail covers the printing; each panel port and each outlet jack or faceplate is labeled with the same identifier. Backbone cables are labeled at each end and, in long risers, where they pass through each floor. Labels must suit their environment: outdoor and high-temperature labels are made of different materials, and labels on pathways and firestops must be visible without opening anything.

Many systems also use color to identify the function of termination fields in a cross-connect. TIA-606 assigns colors to fields by long convention: orange for the demarcation point, green for the customer side of network connections, purple for common equipment such as switches and telephone systems, white for first-level backbone, gray for second-level backbone, blue for horizontal cabling, brown for interbuilding backbone, yellow for auxiliary and alarm circuits and red for key telephone systems. The colors appear on the label strips of the termination fields, not necessarily on the cable jackets, which owners color for their own purposes. Riverside's board standard, for example, uses blue jackets for data and white for the security network, while its termination field labels follow TIA-606.

Records

Labels identify things; records connect them. TIA-606 calls for records that, for each element, hold its identifier, its type, its location and the identifiers of everything it connects to. For a horizontal link, the record holds the panel port, the outlet location, the cable type and category, the length and the test result. For a backbone cable, it holds both ends, the cable type and count, and the status of each strand or pair: in use, spare or damaged. For pathways, it holds the route and fill.

On small systems, records may be a spreadsheet and a set of marked-up drawings. On large ones, they are kept in cable management software that links the records to floor plans and rack elevations and updates them as changes are made. Either way, the deliverables at the end of a Cobalt Line job are the same: as-built drawings showing every outlet with its identifier and every pathway; rack and panel elevations; the cable records; and the test reports for every link. Many owners also require the records in a particular file format so that they can be imported into their own systems.

Records are only valuable if they are kept current. Every move, add and change must update them, and an owner who lets the records drift for a few years ends up with a system that is again unidentifiable. Cobalt Line's service technicians close a change order only after the records are updated, and Dev reminds Maya that the record update is part of the work, not something to do later.

Administration during construction

On a large job, administration starts on the first day, not the last. Cobalt Line's crews receive their labels printed in batches by area, with a marked-up drawing showing each outlet and its identifier. As cables are pulled, each is labeled at both ends before it is dressed into the tray or the rack, because an unlabeled cable in a bundle of two hundred is almost impossible to identify later without a tester. As outlets are terminated and tested, the foreman marks them complete on the drawing, and the test results are uploaded daily so that failures are found while the crew is still in the area.

Changes during construction are recorded as they happen. When a tenant moves an outlet or adds one, the change is given an identifier from the design list, the label is printed from the same source and the change is marked on the drawings that will become the as-builts. A field change that bypasses the list, with a handwritten label, is exactly how records drift from the building, and Colette's project closeout checks for it.

Pathway and firestop administration often gets less attention than cable records, and it matters as much. A firestop identifier, placed on a label beside each sealed penetration, lets an inspector find the record of the listed system used, the installer and the date. A conduit or sleeve identifier tells the next contractor where a pathway goes and how full it is. The bonding busbar in each room, covered in LVT-330, is identified and recorded too, with each bonding conductor labeled at both ends so that a missing or loose conductor can be traced.

At handover, the owner receives everything needed to keep the system identifiable: the records in the required format, the label files so that replacement labels can be printed in the same style, the as-built drawings and the test reports. Dev's test of a good handover is the one from Lesson 1: a stranger, five years later, should be able to find both ends of any link from the records alone.

Maya keeps one more habit from Dev: when she finds a label that is wrong, damaged or missing on any job, even one outside her own work, she reports it rather than ignoring it. A record system is only as reliable as its least reliable label.