> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fiber cut response: OTDR alarm to restored service

> An OTDR fires a fibre-break alarm mid-morning. Identify the segment, dispatch a splicer to the GPS coordinates, notify affected subscribers by SMS, coordinate road access with the municipality, and track the repair to the restoration.

At 11:04 the OTDR on the northern backbone fires a fibre-break alarm 14.3 km from the POP, in a segment that serves 312 residential subscribers. The NOC needs a splicer at the right coordinates within the hour, subscribers informed before they call, and the municipality notified if roadworks are needed.

## 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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Statuspage and Slack">
    Publish an Identified incident on Statuspage. Open the `#fiber-ops` thread with the map, the subscriber count, the splicer, the ETA.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Close">
    Statuspage marked Resolved with the restoration time. `#fiber-ops` gets the incident timeline as a closing note. Post-mortem task auto-created in the PSA for the engineering review.
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Connectors and MCP" icon="plug" href="../../connectors-and-mcp" arrow="true" cta="GIS and SMS">
    OTDR monitoring, GIS, Maps, Twilio, and Splynx as connector calls.
  </Card>

  <Card title="Shared sessions" icon="users" href="../../shared-sessions" arrow="true" cta="Splicer live">
    Bring the splicer into the thread with presence and photo sharing.
  </Card>
</CardGroup>