Documentation, labelling and records

Fibre is invisible inside the cable, and a cable is invisible inside the ground: without records, nobody knows which of 144 fibres carries the hospital's link, where closure 14 is buried or which port on the panel goes to which building. Restoration time, change safety and the value of the plant as an asset depend on documentation more than on any component. This page lists the record set a fibre plant needs, the identifier and labelling rules that keep it usable, the standards that define them, the tools that hold the records and the process that keeps them true.

The record set

Record	Content	Who needs it
Route drawings / GIS	cable routes with coordinates, depth, offsets from landmarks, duct and microduct occupancy, manholes, poles, closures, slack loops; as-built, not as-designed	restoration crews, other utilities, planners
Cable schedule	cable ID, type, fibre count and type, manufacturer, reel and fibre data sheets, installation date, length by metre marks at both ends	budget checks, ageing decisions (Cable construction)
Splice schedules and diagrams	per closure: incoming and outgoing cables, tube and fibre colours, tray and position, fibre-to-fibre mapping, splice loss, express (uncut) tubes	the person opening the closure at 3 a.m.
Panel and port maps	rack, panel, port → cable, fibre number, far end; connector type and polish (UPC/APC), MPO polarity	patching, troubleshooting
Fibre assignment matrix	circuit or service → fibre numbers end to end through every panel and closure	change control, capacity planning
Test records	OTDR traces (.sor, both directions, all wavelengths) and insertion-loss results per fibre at commissioning, plus the instrument, launch cord and index used; the DDM link passport	baselines for every future comparison (Testing & measurement)
Connectivity (patching) records	which patch cord connects which ports, with dates	the sad reality of patch fields
Spare inventory	spare fibres per cable, spare ports, spare cable on reels, closures, cords	restoration kit (Maintenance & restoration)
Change log	who changed what, when, with which ticket; links to the updated records	audits, root-cause analysis
Safety file	hazard-level labels per site, APR procedures, emergency contacts	anyone opening an amplified site (Safety & handling)

Identifier scheme

Rule	Example / reasoning
Hierarchical and unique	site – building – room – rack – panel – port: `DC1-B2-R07-PP03-P12`; readable by a human, parsable by a script
Cables named by both ends	`CBL-0042 DC1/PP03 ↔ POP7/ODF02`, plus fibre count and type in the record, not in the name
Fibres numbered, not only coloured	fibre 37 = tube 4 (brown), fibre 1 (blue) under TIA-598; write the number and the colour scheme, because schemes differ between cables
Closures with coordinates	`SC-014` with WGS-84 coordinates, depth and marker post; a fibre length from the OTDR is not a location (Reading an OTDR trace)
Circuits separate from fibres	a service ID maps to fibre numbers; when fibres are re-spliced the service keeps its ID
No meaning overload	do not encode speed, customer or vendor in the identifier — they change; keep them as attributes
Stable over the life	renaming a plant is a project; pick the scheme before the first cable is pulled

Labelling

Item	Where and how	Material
Outdoor cables	at every manhole, closure entry and building entrance; both sides of a closure; every 100–200 m in ducts where accessible	embossed stainless, brass or UV-stable engraved plastic tags on cable ties
Closures	closure ID outside; splice schedule copy inside in a sealed pocket	engraved plate, laminated paper inside
Indoor cables	both ends and at every pass-through; within 300 mm of the termination	self-laminating vinyl wrap labels, printed
Patch panels and ports	panel ID on the front; port numbers printed by the manufacturer; far-end ID per port or per group	printed label strips
Patch cords	both ends, identical text: from and to	self-laminating wrap or flag labels; never handwritten on tape
Racks and rooms	at eye level, both sides of the row	rigid plates
Hazard and laser labels	at every ODF, closure and amplifier site with accessible power above Class 1	standardised laser warning labels (IEC 60825)
Colour coding (optional, TIA-606)	e.g., orange for demarcation, green for network connections, blue for horizontal	label background colour, not cable jacket

Labels must stay legible for the life of the plant: UV, temperature, moisture and the cleaning solvent used on panels all destroy cheap labels within a year. Print, do not write.

Standards

Standard	Scope
ANSI/TIA-606-C	administration of telecommunications infrastructure: identifier classes 1–4 (single room to multi-campus), label durability (UL 969), record requirements
ISO/IEC 14763-2 and TR 14763-2-1	planning and installation of cabling, including documentation and identifiers; European equivalent EN 50174-1
ANSI/TIA-568.3-D, ISO/IEC 14763-3	what a test record for optical cabling must contain (Fibre characterization)
ANSI/TIA-598-D, IEC 60304	fibre and tube colour codes
Telcordia SR-4731	the .sor OTDR trace file format — keep native files, not only PDFs
GOST R 53246-2008, GOST R 53245-2008	Russian structured cabling standards: design and administration; installation and testing
RD 45.156-2000	Russian industry document on the composition of as-built documentation for fibre-optic lines
Full list	Standards map

Tools

Tool	Fits	Notes
Spreadsheets	one building, a few cables	breaks at the first many-to-many relation (a fibre through five closures)
Fibre management / GIS-based OSP systems	outside plant of any size	cable, fibre, splice, closure and coordinate model; restoration search "which services are on cable 42 between km 3 and 4"
DCIM with fibre modelling	data centres	rack, panel, port, trunk and polarity model; integration with tickets
Network inventory / NMS	operators	services on fibres, alarms per fibre
Trace archive	every plant	.sor files named by cable-fibre-direction-wavelength-date; baseline flagged
Photo archive	closures, panels, manholes	a photograph of the opened closure is worth a page of diagram
Offline copy	every restoration truck	the network may be down while you need the records

Process

Step	Rule
Before construction	identifier scheme, label specification and record templates written into the contract; handover package defined
During construction	daily as-built updates; splice schedules filled at the closure, not later from memory
Handover package	drawings (native + PDF), cable schedule with data sheets, splice schedules, port maps, OTDR .sor both directions at 2–3 wavelengths, insertion-loss results, endface inspection images, label list, warranty and contact list
Every change	ticket → work → update records → re-test affected fibres → new baseline → close ticket; no "temporary" patch without a record
Restoration	the incident report includes the new splice schedules and traces; the "temporary" fix gets a date to be replaced
Audit	annual sample of closures and panels against records; full audit every 3–5 years
Access	records readable by the night crew without a specialist; versioned; backed up off-site

Common failures

Failure	Consequence	Fix
Labels on one end only	wrong fibre cut, wrong port patched	both ends, always
Records not updated after restoration	the next fault is located on the old drawing	restoration ticket cannot close without records
Buried closures without coordinates	an OTDR distance and a shovel	GPS every closure and marker post; metre marks at both ends
Different colour or numbering conventions per contractor	fibre 7 is not fibre 7	scheme in the contract; state the scheme in each splice schedule
OTDR traces saved as PDF only, without launch cord and index data	no re-analysis possible	keep .sor files with settings
Patch cords labelled by hand on tape	unreadable in a year	printed self-laminating labels
Records in one person's head	leaves with the person	the process above

In CodingBox

The module is part of the record: its vendor, part number and serial number identify what sits in each port, and its commissioning DDM values are the baseline of the link passport. CodingBox reads the identity and the DDM on the bench and keeps notes and photographs per part number in the code database, so the port map can say which module, not just which fibre (Check transceiver, Code database, DDM in the app).