--- title: "Fibre networks and outside plant | Nexus Observatory" description: "Fibre runs under roads, railways and fields where diggers, floods and thieves find it. Distributed sensing on the fibre itself…" url: https://observatory.global/industries/telecom/fibre-networks/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Telecom](https://observatory.global/industries/telecom/) / [Specialized fields](https://observatory.global/industries/telecom/fields/) / **Fibre networks and outside plant** # Fibre routes, listening along their length. Fibre runs under roads, railways and fields where diggers, floods and thieves find it. Distributed sensing on the fibre itself, with sensors in chambers and cabinets, reports to one record that warns of digging near the route and finds faults before customers lose service. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Telecom **Measurements**: 5 **Sources cited**: 3 1. Telecom · Fibre networks and outside plant The digger finds the cable first Most fibre cuts come from someone digging where they should not. The operator learns about it when customers lose service, and a crew spends the night splicing. A fibre that listens along its length hears the digger first, and the operator can stop the work before the cut. 2. What is measured Vibration, loss, water and gas A distributed sensing interrogator turns a spare fibre into thousands of vibration and strain sensors along the route. Reflectometry locates faults in working fibres, level and gas sensors watch chambers at low points and risk points, and contacts and climate sensors watch cabinets. InstrumentsDistributed fibre sensing · Reflectometry · Chamber level and gas · Cabinet sensors 3. The base node Digging, told from traffic The edge node beside the interrogator classifies every vibration along the route, telling digging from traffic and trains, and locates it to a stretch of route tied to the ground. Alerts leave with the map location while the digger is still working. 4. Radio and links The route carries its own data The route's own fibre carries the sensing and returns the data to the exchange. Battery sensors in chambers and cabinets reach gateways on poles or exchanges over LoRaWAN, and remote gateways use cellular where no exchange is near. Each gateway is supervised. LinksFibre · LoRaWAN · Public cellular 5. How it works From a vibration to a patrol An excavator starts work beside a road. The interrogator hears the pattern on the spare fibre, the node classifies it as digging and locates it, and the operations centre receives the alert with a map. A patrol arrives and the works move the trench before the cable is cut. 6. From order to operation · Order Scope the routes and the risks The scope reads the route records, dig-in history, flooded chambers, cabinet incidents and spare fibres available for sensing. Nexus Observatory Inc. returns the sensing plan by route, chamber and cabinet points, the integration with operations and a price per route length and per point. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Walk the route and test the fibre Crews walk the route with the operator's records: chambers at low points, crossings, cabinets and the stretches where digging is common. They test the spare fibre for sensing, check gateway coverage along the route, and record access to chambers and exchanges. 8. From order to operation · Permits Chambers, roads and data Chamber work follows confined-space rules and road works permits. Sharing dig-in warnings with utilities and road authorities is agreed in writing, so warnings reach the people on site. Every agreement is kept with the route's record. Crews entering chambers always test the air first, whatever the fixed sensors show. 9. From order to operation · Build Build the interrogator and the points Interrogators, edge nodes, chamber and cabinet sensors, endpoints and gateways are built, tested together and enrolled with their identities. The route's map is loaded so every alert is located on the ground, and every part is labelled with its route and chamber. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install at the exchange and in chambers Crews connect the interrogator to the spare fibre at the exchange, fit level and gas sensors in chambers with confined-space procedures, and door and climate sensors in cabinets. Gateways go on poles or exchanges, and every point is located and photographed. 11. From order to operation · Commission Calibrate the route Each device proves its identity. A tap test along the route ties fibre distance to ground location, a controlled dig near the route tests detection, and chamber and cabinet sensors are checked. Alerts are tested to the operations centre and the dig-in team. 12. From order to operation · Operate Stop the digger before the cut The operations centre sees digging along every route as it happens, with its location, and sends a patrol or calls the works before the cable is cut. Flooded chambers and gas are flagged, cabinets watched, and every incident kept on the record. 13. From order to operation · Maintain Keep the map true When routes change, the map and the location calibration are updated, chamber sensors are checked during routine visits, and batteries changed on plan. Every change is recorded, so alerts stay located on the ground where crews will find them. Spares are kept at the exchanges. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For operations, maintenance and field crews Operations centres and patrols receive dig-in warnings with location; fibre maintenance teams receive fault locations; field crews receive chamber flooding and gas alerts; security and field teams receive cabinet access and climate. Each product carries its route and ground location. [See the data products](https://observatory.global/data-products/) 15. Evidence Routes on record Every event, alert, patrol and repair is signed and kept. Sensing follows the international fibre optic sensor standard, maintenance follows ITU practice for optical cable networks, and cabinets follow the European telecom environmental classes, so incidents can be traced and costs recovered from those who caused them. Drawn againstIEC 61757 · ITU-T L.25 · ETSI EN 300 019 16. What you get Transport and logistics corridor sensing Road weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends. Delivered as managed service and data licence, for transport agencies, rail and port operators, logistics firms. Scale: Corridor to network. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan fibre networks and outside plant with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for fibre networks and outside plant. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextFibre operators maintain long routes of cable in ducts, chambers and cabinets. Most damage comes from third-party digging, and chambers flood or collect gas. Maintenance follows recognised practice for optical cable networks, distributed fibre sensing turns a fibre into a line of sensors, and operators must manage the resilience of their networks. Hazards - Third-party digging cutting the cable - Flooded chambers and ducts - Gas in chambers endangering crews - Cabinet break-ins and overheating - Faults located only after customers call **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Vibration and strain along the route | A dark or spare fibre in the cable, read by a distributed sensing interrogator | Continuous along the whole route | 1 | | Optical loss and fault location | The working fibres, by reflectometry | Continuous or scheduled | 2 | | Water level in chambers | Chambers at low points and river crossings | Continuous | 2 | | Gas in chambers | Chambers before crew entry and continuously at risk points | Continuous at risk points | 2 | | Cabinet access and climate | Street and roadside cabinets | On event and continuous | 3 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A route sensor: the interrogator on a fibre at the exchange, or a chamber or cabinet sensor on a LoRaWAN endpoint. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A route: the interrogator at each end, chamber and cabinet points, gateways along the way and the route's own fibre home. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every route of an operator run as one fleet, with one record. [Managed offers →](https://observatory.global/industries/telecom/solutions/) 4. **04** Network Operators, utilities and road authorities exchange dig-in warnings and records through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** Water level gauge - **02** Gas detector (industrial) - **03** LPWAN endpoint - **04** LoRaWAN gateway - **05** Edge node (Wedge) - **06** Fibre terminal - **07** Battery case Radio and links ### Fibre The route's own fibre carries the sensing and returns the data to the exchange. Radio and links ### LoRaWAN Battery sensors in chambers and cabinets reach gateways on poles or exchanges along the route. Radio and links ### Public cellular Remote gateways use cellular where no exchange is near. Edge computeThe edge node beside the interrogator classifies vibration along the route, telling digging from traffic and trains, locates it to a stretch of the route and alerts the operator with the location while the digger is still working. PowerThe interrogator and node run at the exchange; chamber and cabinet sensors run on batteries for years. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Fibre networks and outside plant: data path – of 08 01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products IEC 61757ITU-T L.25OGC SensorThings API 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment Distributed fibre sensing interrogator Not in the reference kit 01 Water level gauge SDI-12 · RS-485 · Ethernet 02 Gas detector (industrial) Analogue I/O · RS-485 · Ethernet 03 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 04 LoRaWAN gateway Ethernet · RF · GNSS antenna 05 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 06 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Dig-in warnings with location Fault location Chamber flooding and gas alerts Cabinet access and climate 07 Battery case USB Ethernet SDI-12 Analogue I/O LoRaWAN Ethernet Fibre Fibre From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **Water level gauge** Radar, pressure or float gauge for river, lake, reservoir or tide level. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **Gas detector (industrial)** Fixed detector for flammable or toxic gas in industrial areas, with alarm outputs. | Analogue I/ORS-485Ethernet | Modbus, OPC UA, MQTT 5 | 24 V DC | | 03 | **LPWAN endpoint** Battery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors. | Analogue I/OSDI-12RS-485 | LoRaWAN, OMA LwM2M, CoAP | Internal battery, Energy harvesting | | 04 | **LoRaWAN gateway** Multi-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits. | EthernetRFGNSS antenna | LoRaWAN, MQTT 5 | PoE, 12 V DC | | 05 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains | | 06 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains | | 07 | **Battery case** Portable battery pack with DC outputs for field kits. | USB | Modbus | AC mains, HV DC, USB PD | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope the routes and the risks The scope reads the route records, dig-in history, flooded chambers, cabinet incidents and spare fibres available for sensing. Nexus Observatory Inc. returns the sensing plan by route, chamber and cabinet points, the integration with operations and a price per route length and per point. 2 2. 02 Survey Walk the route and test the fibre Crews walk the route with the operator's records: chambers at low points, crossings, cabinets and the stretches where digging is common. They test the spare fibre for sensing, check gateway coverage along the route, and record access to chambers and exchanges. 3. 03 Permits Chambers, roads and data Chamber work follows confined-space rules and road works permits. Sharing dig-in warnings with utilities and road authorities is agreed in writing, so warnings reach the people on site. Every agreement is kept with the route's record. Crews entering chambers always test the air first, whatever the fixed sensors show. 4. 04 Build Build the interrogator and the points Interrogators, edge nodes, chamber and cabinet sensors, endpoints and gateways are built, tested together and enrolled with their identities. The route's map is loaded so every alert is located on the ground, and every part is labelled with its route and chamber. 5. 05 Install Install at the exchange and in chambers Crews connect the interrogator to the spare fibre at the exchange, fit level and gas sensors in chambers with confined-space procedures, and door and climate sensors in cabinets. Gateways go on poles or exchanges, and every point is located and photographed. 6. 06 Commission Calibrate the route Each device proves its identity. A tap test along the route ties fibre distance to ground location, a controlled dig near the route tests detection, and chamber and cabinet sensors are checked. Alerts are tested to the operations centre and the dig-in team. 7. 07 Operate Stop the digger before the cut The operations centre sees digging along every route as it happens, with its location, and sends a patrol or calls the works before the cable is cut. Flooded chambers and gas are flagged, cabinets watched, and every incident kept on the record. 12 8. 08 Maintain Keep the map true When routes change, the map and the location calibration are updated, chamber sensors are checked during routine visits, and batteries changed on plan. Every change is recorded, so alerts stay located on the ground where crews will find them. Spares are kept at the exchanges. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Dig-in warnings with location** Operations centres and patrols - **Fault location** Fibre maintenance teams - **Chamber flooding and gas alerts** Field crews - **Cabinet access and climate** Security and field teams Integration - **Operations centre** Warnings and faults reach the operator's fault management system with map locations. - **Dig-before-you-dig services** Warnings are compared with registered works and shared with utilities where agreed. - **Network records** Incidents are linked to route, chamber and cabinet records. Exchanged through IEC 61757, ITU-T L.25, OGC SensorThings API. **07** Questions buyers ask ## Before you scope it. Do we need new cable? No. A spare fibre in the existing cable becomes the sensor. Can it tell digging from traffic? The node classifies vibration patterns, and the calibration test confirms it. How precisely are events located? To a stretch of route tied to ground locations by the tap test. Is chamber gas monitored for crews? Yes, at risk points continuously and before entry. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [IEC 61757: Fibre optic sensors](https://webstore.iec.ch/) International Electrotechnical Commission 2. **2** [ITU-T L.25: Optical fibre cable network maintenance](https://www.itu.int/) International Telecommunication Union 3. **3** [ETSI EN 300 019: Environmental conditions and environmental tests for telecommunications equipment](https://www.etsi.org/) European Telecommunications Standards Institute **09** Related ## Use cases and solutions. [Solution Transport and logistics corridor sensingRoad weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#corridor-sensing) [Solution National observing network programmesBuild-operate-transfer of national observing infrastructure as digital public infrastructure, with transfer of skills and records.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#national-networks) **10** Telecom: specialized fields ## Other fields of this industry. [Specialized field Mobile network sitesPower and batteries, shelter climate, tower movement, intrusion and site weather at every mobile site, with an out-of-band path that reports when the site itself is down.The full field →](https://observatory.global/industries/telecom/mobile-sites/) [Specialized field Edge data centresPower and energy, cooling and air, leaks and vibration in edge and regional data centres, on an industrial network behind a security gateway, with efficiency indicators to the standard.The full field →](https://observatory.global/industries/telecom/edge-data-centres/) [Specialized field Satellite ground stationsRain, wind and lightning at the antennas, antenna drive condition, timing and site security at satellite ground stations, on the site's fibre, so passes are planned around the weather and faults are caught between passes.The full field →](https://observatory.global/industries/telecom/ground-stations/) [Specialized field Spectrum monitoring and interferenceFixed and mobile receivers that measure occupancy, find interference and locate its source by direction finding and time difference, with GNSS timing, so regulators and operators clear the bands they depend on.The full field →](https://observatory.global/industries/telecom/spectrum-monitoring/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Telecom** . Towers that compute, sense and connect.[Talk to us](https://observatory.global/contact/) Telecom - [Overview](https://observatory.global/industries/telecom/) - [Explainer](https://observatory.global/industries/telecom/explainer/) - [Specialized fields](https://observatory.global/industries/telecom/fields/) - [Use cases](https://observatory.global/industries/telecom/use-cases/) - [Solutions](https://observatory.global/industries/telecom/solutions/) - [Platforms](https://observatory.global/industries/telecom/platforms/) - [Resources](https://observatory.global/industries/telecom/resources/) - [Contact](https://observatory.global/industries/telecom/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)