The term “fiber route management” refers to software-supported planning, documentation, and tracing of the physical routes of fiber-optic infrastructure - from the duct/route (e.g., conduits, cable ducts, pole lines) through cables, splice closures, and distribution points down to the individual fiber. The goal is to make connectivity, occupancy, and capacity transparent, implement changes in a controlled way, and localize faults faster (this is about the physical route in a fiber network, not IP routing).
Route & infrastructure inventory: Modeling routes, segments, manholes, buildings, duct banks, micro-ducts, distribution and handover points.
Cable and fiber inventory: Managing cables, bundles, tubes, and individual fibers incl. labeling, color codes, length, ownership/status, and documentation completeness.
End-to-end connectivity management: Representing the physical connection from site/PoP to endpoint incl. ODF/patch panels and ports.
Splice & closure management: Documenting splice closures, splice plans, splice relationships, slack/reserve, and revision history.
Route tracing / path calculation: Determining and visualizing the actual path of a connection; often includes automated path finding and schematic views.
Occupancy & capacity management: Tracking used/free fibers and duct occupancy, reserve concepts, bottleneck analysis, and expansion planning.
Reservation & provisioning support: Reserving/assigning fibers for customers, services, or projects; conflict checks and usage tracking.
Planning & build support: Comparing route options, generating bills of material, linking to build phases/projects, and capturing as-built documentation.
Service/technology mapping (optional): Linking services or transmission technologies (e.g., PON/WDM) to fibers/connections for operational visibility.
GIS/map integration & reporting: Map-based visualization, thematic layers, analytics, and reports (e.g., occupancy, capacity, outage impact).
A provider traces a circuit from the central office to a business customer to identify which splice closures and splices are impacted by an outage.
A municipal utility plans a new FTTH drop and checks available micro-duct and fiber capacity along alternative routes.
For a new order, two fibers are reserved on a defined path, a splice plan is created, and ODF patching is documented.
A capacity report highlights congested duct sections and supports prioritizing network expansion investments.
After construction, as-built data (actual route, closure locations, fiber occupancy) is updated so operations and troubleshooting work with current information.
