Systems involved
| System | Role |
|---|---|
| OTDR monitoring system | Source alarm with distance-to-fault. |
| Fibre GIS (QGIS / OSPInsight) | Convert distance to GPS coordinates and road access. |
| Google Maps / Routing API | Splicer ETA from current position. |
| Splicer dispatch | Field ops team and equipment. |
| Twilio SMS | Subscriber outbound notifications. |
| Splynx | Subscriber list affected by the broken segment. |
| Local municipality liaison | Road permit / access for trenching. |
| Atlassian Statuspage | Public status page. |
Slack #fiber-ops | Operational channel. |
Walkthrough
Lock in the fault location
Copilot pulls the OTDR trace, converts 14.3 km along the fibre path into GPS coordinates using the GIS overlay, and places a pin on a map artifact. Two candidate road accesses appear — one is closer by truck, one is closer by foot across a paddock.
Identify affected subscribers
Query the GIS + Splynx join: subscribers on the downstream side of the break. 312 households, 8 commercial, 2 on SLA-backed service tiers.
Dispatch the splicer
Copilot finds the nearest splicer with a van and OTDR, sends them the coordinates, the access notes, the splice records for that segment, and the two SLA-backed customers to prioritize after restoration. The ETA comes back at 47 minutes.
Subscriber SMS
Twilio connector sends an SMS to the 320 contacts: fibre damage, splicer dispatched, ETA to restoration, status page URL. Cost preview shown, approval, send.
Coordinate road access
The break is on a council verge. Copilot drafts the incident notice through Gmail to the municipal roads liaison with the coordinates, the expected splicer arrival, and the work that may be needed.
Statuspage and Slack
Publish an Identified incident on Statuspage. Open the
#fiber-ops thread with the map, the subscriber count, the splicer, the ETA.Splicer on site
The splicer confirms the break location via chat, sends a photo to the thread, starts the splice. Copilot tracks elapsed time and posts the progress into
#fiber-ops and Statuspage.Restoration and validation
Splice complete. OTDR re-trace shows clean continuity. Copilot runs ping against a sample of downstream subscriber CPEs through LibreNMS, confirms restoration, fires the all-clear SMS.
Where Studio earns its keep
- OTDR distance becomes GPS coordinates in the same workspace where the splicer is dispatched — no engineer reading off one map and typing into another.
- The SMS list comes from the GIS join, so every subscriber in the affected segment gets told and no one outside it does.
- The municipality and the splicer see the same location evidence, which makes the road-access conversation five minutes instead of thirty.
- The restoration evidence — OTDR trace, sample pings, timestamps — is the post-mortem artifact without anyone writing it.
Related
Connectors and MCP
OTDR monitoring, GIS, Maps, Twilio, and Splynx as connector calls.
Shared sessions
Bring the splicer into the thread with presence and photo sharing.