Field operations
What a splice closure knows that your GIS does not
The tray layout, the loss budget and the reason someone re-spliced tray 3 at 02:00 all live in different systems. Here is what it costs when they stay there.
The record and the reality drift apart one truck roll at a time
A splice closure is the most information-dense object in a fiber network, and almost none of what it knows survives the trip back to the office. The GIS has a point on a map. The closure has a tray layout, a fiber assignment, an OTDR trace from the day it was commissioned, and a laminated card someone updated with a marker pen in 2023.
None of that is negligence. It is what happens when the field capture tool, the design tool and the asset register are three different systems with three different ideas of what a closure is.
Three things that go missing between the closure and the record
- Why the deviation happened
- The as-built shows tray 3 instead of tray 2. The reason, a damaged buffer tube, exists only in a technician's memory.
- The evidence that proved it
- Photos and OTDR results land in a folder named after a date, not attached to the fiber they describe.
- What it means for capacity
- Six fibers were consumed. Planning still shows them available, and quotes them to a customer four months later.
We did not have a data problem. We had five accurate systems that disagreed.
Attach the evidence to the object, not the date
The fix is unglamorous. When a technician closes a task, the photo, the measurement and the deviation attach to the fiber, the tray and the closure, not to a work order that gets archived.
Capacity then reflects what is physically spliced, and the next person to open that closure sees why tray 3 was used before they cut anything.