The term “OTDR mapping” refers to software-supported association of OTDR measurement data (Optical Time Domain Reflectometer) with a real fiber route or network topology. The goal is to represent OTDR traces and detected events (e.g., connectors, splices, loss points, fiber end) in a location- and structure-aware way - often as a schematic link view, a topology diagram, or a map (e.g., combined with GIS data). OTDR mapping supports documentation, commissioning, acceptance testing, faster fault localization, and efficient troubleshooting in fiber networks.
Import and management of OTDR traces: Ingesting, versioning, and organizing traces (e.g., by site, fiber, port, date, technician).
Automatic event detection (event table): Identifying and classifying events such as connectors, splices, macrobends, reflections, and fiber end, including distance and loss values.
Link and topology association: Linking OTDR measurements to links, fibers, cable sections, closures, cabinets, ODFs, and ports within a network structure.
Georeferencing / GIS integration: Assigning events to coordinates or route segments (e.g., via GIS, map layers, or route chainage).
Visual map/diagram representation: Map-based or schematic visualization of the route with event symbols, segments, distances, and quality metrics.
Baseline and comparison measurements: Comparing current traces to reference (baseline) traces to detect changes (e.g., added loss, new reflections).
Thresholds, alarms, and quality rules: Pass/fail criteria, event- or segment-specific thresholds, and alerting on deviations.
Link documentation and compliance reporting: Automated creation of test protocols, acceptance reports, and audit-ready documentation (including event lists and loss budgets).
Ticketing and workflow integration: Handing over localized fault positions to operational processes (e.g., work orders, field service, NMS/OSS).
Multi-user and role-based features: Permissions, approvals, history/audit trail for measurement data and network objects.
A network operator links OTDR acceptance tests of a new backbone route to closure and splice locations in the topology view to complete documentation.
An operations team uses a map view to pinpoint which route section shows added attenuation and dispatches a repair crew to a specific handhole or cabinet.
In FTTH deployments, OTDR traces are assigned to individual customer fibers and distribution ports to document installation quality per connection.
After a repair, new traces are automatically compared to the baseline, and deviations are flagged as “change events” in the mapped view.
A service provider generates an audit-ready acceptance report from OTDR data and route information, including event table, route length, and segment loss budget.