Emergency Restoration

# Why Emergency Fiber Restoration Needs a Plan Before the Storm

TLDR

A restoration plan written before storm season fixes the slow parts in advance: **standing agreements**, **pre-staged spares** matched to installed cable, current as-builts, and an agreed **escalation path**.

Last updated October 20, 202612 min read

Plan before the storm because the slowest parts of restoration are contractual and informational, not technical. Splicing is a predictable task. Finding matching cable, executing a contract, getting site access, and locating a splice point are not, and each can stall a crew. A plan settles those items in advance so crews spend event time working instead of searching.

## Why does the plan have to exist before the event?

Restoration time is mostly non-technical. Preparing two cable ends and fusing them is a known quantity that scales with fiber count. What varies wildly is everything upstream: knowing which span failed, reaching it, getting permission to work, and having material that matches. Those are decisions and documents, and decisions made under outage pressure are worse and slower than the same decisions made in March.

The asymmetry is severe. An hour spent in advance confirming that a spare reel matches the installed cable construction can remove a long sourcing delay from a restoration. An hour spent in advance agreeing emergency rates removes a procurement cycle. None of that work is glamorous, and all of it is repayable at a very high multiple.

There is also a capacity argument. In a regional event, contractors, materials, and equipment are allocated to the operators who already have agreements and staged material. Planning is not only about internal efficiency, it is about position in the queue.

## What does criticality mapping do for you?

Criticality mapping answers the first question a crew will ask during a multi-failure event: what do we fix first? Without a pre-agreed answer, that question travels up two organizations while crews wait. With one, dispatch is immediate.

The mapping does not need to be elaborate. Identify the segments whose loss takes out the most customers or the most sensitive customers, the segments with no diverse path, and the segments serving public safety, healthcare, or critical infrastructure. Rank them. Record the ranking somewhere a field supervisor can read it without a login.

Diversity analysis belongs in the same exercise. Two circuits sold as diverse routinely share a duct bank, a bridge attachment, or a single pole line for part of their path. A storm finds those shared segments efficiently. Identifying them before the season lets you either fix the diversity or, at minimum, know in advance which protected services are actually exposed.

## How accurate do as-builts have to be?

Accurate enough to convert an optical distance into a shovel location. That is the working standard, and it sets specific requirements. The record needs splice point locations with footages, slack quantities stored at each point, cable sheath sequential ranges, depth and offset for underground segments, and duct occupancy where conduit exists.

Slack documentation is the piece most often missing and the piece that costs the most time. Fiber length exceeds route length by every loop and coil, so an OTDR distance without a slack record leaves the crew guessing. A simple table of splice point, footage, and stored slack turns that guess into arithmetic.

Records also decay. Every repair, every relocation, every new lateral changes the plant, and if redlines never get merged into the network of record, the map quietly becomes fiction. Making as-built merge a condition of closeout on every job, including emergency work, is the only mechanism that keeps records current at scale.

## What spares belong in pre-staged inventory?

A spare inventory is a deliberate short list, not a warehouse. It should cover the failures that are common, the materials that are slow to source, and the items that make a temporary restoration possible while the permanent material is ordered.

- Cable in the fiber counts and constructions actually deployed, including armored and dielectric variants where both are in the plant
- Enough temporary cable to bridge the longest realistic distance between accessible splice points on critical routes
- Splice closures matching the installed families, with the correct trays, grommets, and sealing kits
- Fusion splice sleeves, cleaver blades, fiber cleaning supplies, and spare electrodes
- Conduit, couplings, end caps, duct plugs, and tracer wire with connectors
- Handhole lids and covers, since a damaged or missing lid frequently blocks a permanent closeout
- Aerial hardware: strand clamps, dead ends, suspension hardware, lashing wire, and bonding materials
- Warning tape, marker posts, and restoration materials the permitting agency requires

## Which pre-storm tasks fail loudest when skipped?

Every item on a readiness list has a specific failure mode during an event. Naming the failure makes the task easier to prioritize and easier to justify to a budget owner.

| Pre-storm task | What goes wrong when it is skipped |
| --- | --- |
| Execute a standing emergency agreement with rates | Restoration waits on a quote, a purchase order, and an approver who is not reachable |
| Match spare cable to installed counts and constructions | The reel on hand cannot be spliced into the damaged run, and sourcing takes days |
| Merge redlines into the network of record | Optical distance cannot be converted to a dig location, so crews search instead of splice |
| Document access to gated and private locations | Crews arrive and cannot reach the splice point until a property contact is found |
| Agree restoration priority for critical circuits | Field supervisors wait for a decision that has to travel through two organizations |
| Confirm permit and restoration standards by agency | Repairs get done and then reopened to meet a backfill, sod, or pavement requirement |
| Publish a contact tree with after-hours numbers | The first hour is spent finding people rather than dispatching crews |

## How do permits and restoration standards work in an emergency?

Emergency work does not remove the permit obligation, it changes the sequence. Many right of way agencies allow emergency repairs with prompt notification and a permit filed after the fact, but the notice method and filing window differ by agency. The important part for planning is knowing, in advance, which agency governs each segment of your route and what that agency requires.

Restoration standards vary meaningfully between a state road, a county road, and a municipal street. Backfill material and compaction, sod versus seed, sidewalk panel replacement rules, and asphalt patch dimensions and overlays are all specified. A crew that patches to the wrong standard will be back, and the second visit is under a schedule set by the agency rather than by the operator.

Sunshine 811 fits the same pattern. The emergency ticket class exists for outages and hazardous conditions and shortens the standard notice period, but marks are still required and conflicts still have to be exposed carefully before mechanical excavation. Recording the ticket number in the closeout is what protects the operator if a damage claim follows.

## What belongs in the contact tree and escalation path?

A contact tree is only useful if it is current and reachable. It should list the operator's on-call engineer and their backup, the person authorized to approve emergency spend, the contractor's on-call dispatcher, and the named single point of contact for the event.

Escalation needs a trigger and a timer, not just names. Define what happens if the on-call number is not answered within a set interval, who gets called next, and who can authorize work if the primary approver is unreachable. Storms take out cell sites and power along with fiber, so include an alternate channel that does not depend on a single carrier.

Add the boring operational details that always get improvised: gate codes and property contacts, staging areas where equipment can be parked safely, and the credentialing arrangements that let crews back into an evacuated or restricted area. Re-entry credentials in particular are issued by local emergency management on a schedule that starts long before the storm.

## How do you test the plan before it is tested for you?

Run a tabletop exercise on a plausible scenario: a backbone segment cut in a location with poor access, at night, during a regional event. Walk it end to end. Who gets the alarm, who calls whom, who places the 811 ticket, where does the matching cable come from, who approves the spend, who talks to the customer, and what does the closeout look like.

The exercise almost always surfaces the same categories of gaps: a phone number that belongs to someone who left, a spare reel that does not match anything installed, a splice point nobody can locate, and an approval chain that requires a person who will be evacuating. All of those are cheap to fix in advance and expensive to discover live.

Then verify the physical assumptions. Open a handhole on a critical route and confirm the slack is present and the record is right. Shoot a baseline OTDR trace on critical spans and archive it so the next event has something to compare against. A plan that has been walked and spot-checked is a plan. One that has only been written is a document.

## Who should own the restoration plan?

One named person on the operator side should own the plan, even though several groups contribute to it. Engineering supplies criticality and diversity data, operations supplies contacts and access details, finance supplies spending authority, and the contractor supplies its own contacts, equipment and spare inventory. Without a single owner, each group assumes another one updated it.

Ownership means a review date on the calendar and a trigger list for unscheduled updates: a new route, a new cable construction, a change of contractor, or a key person leaving. It also means deciding where the plan lives. A shared drive is fine for editing, but a printed copy in each response vehicle and at the operations desk keeps it readable when power, cell service or a login is not available.

## How should emergency spending be set up in advance?

Set up the money before the event so that nobody has to find an approver at night. That means a named person with authority to release emergency spend up to a set amount, a backup for that person, and a purchase mechanism that works outside business hours, such as a blanket purchase order tied to the standing agreement.

Agree the record format at the same time. Decide which cost codes the event will use, how the contractor will report labor, equipment and materials, and what photos and logs must accompany the invoice. Insurers and any public recovery program will ask for the same records later, and they are far easier to capture during the work than to rebuild from memory afterward.

## Key takeaways

- The slowest parts of a fiber restoration are contractual and informational, and both can be settled before storm season begins.
- An as-built is accurate enough when a technician can convert an OTDR distance into a shovel location using it.
- Criticality mapping decides which segment gets the first crew, and it only works if a field supervisor can read it without a login.
- A plan that has been walked in a tabletop exercise and spot-checked in the field is far more reliable than one that has only been written.

## Key terms

**Criticality mapping**: Ranking network segments by the impact of losing them, such as customer count, public safety circuits and lack of a diverse path. The ranking tells restoration crews which segment to work first when several fail at once.

**Route diversity**: Two network paths that share no physical segment, so one cut cannot take down both. Circuits sold as diverse sometimes share a duct bank, bridge attachment or pole line, which a pre-season review should find and record.

**Network of record**: The owner's master map and database of the plant as it actually exists: routes, splice points, slack, depths and fiber assignments. It stays accurate only if redlines from every job, including emergency repairs, are merged into it.

**Re-entry credential**: Authorization issued through local emergency management that lets utility and contractor crews enter an evacuated or restricted area after a storm. The arrangements are made well before the season, not during the event.

*A pre-season readiness calendar for fiber restoration planning*

| When | Task | Owner |
| --- | --- | --- |
| Early spring | Review the agreement, rates and the contact tree on both sides | Operator and contractor |
| Spring | Reconcile the spare inventory against installed cable types and closure families | Contractor, reviewed by the operator |
| Spring | Merge outstanding redlines into the network of record | Operator records team |
| Late spring | Run a tabletop exercise on one critical segment | Both organizations |
| Before June 1 | Shoot and archive baseline OTDR traces on critical spans | Contractor |
| After every event | Update the plan with what the event exposed | Plan owner |

*Preventive maintenance cycle*

## What this means for your project

A restoration plan is cheap insurance against the part of an outage you control. The storm is not yours to manage, but the contract, the spare reel, the as-built and the approval chain are. Each one settled in advance takes a known delay out of the next event and gives you a firmer answer when leadership asks how long service will be down.

Treat readiness as recurring maintenance with a budget line, not a one-time project. The plan decays as the network changes, so the review, the inventory reconciliation and the redline merge belong on the same yearly calendar as other preventive work.

Keep the paper trail from day one. Records captured during the event support insurance claims, cost review and any recovery program, and they cost far less to collect while crews are on site than to rebuild weeks later.

## Related reading

- [Storm response servicesAssessment, temporary service and rebuild after a regional event.](https://strillacommunications.com/services/emergency-service-restoration/storm-response)
- [Preventive maintenance programsRecurring inspection and testing that keeps the plan honest.](https://strillacommunications.com/services/system-maintenance/preventive-maintenance)
- [Keeping as-builts currentWhy redlines must reach the network of record on every job.](https://strillacommunications.com/blog/the-importance-of-as-built-documentation)
- [Storm season and fiber risk in FloridaHow hurricane season changes the way networks fail.](https://strillacommunications.com/blog/how-storm-season-changes-fiber-network-risk-in-florida)
- [Ongoing network supportA standing relationship for repairs, moves and readiness reviews.](https://strillacommunications.com/services/system-maintenance/ongoing-network-support)
- [For maintenance and operations managersHow outside plant support fits an operations team.](https://strillacommunications.com/industries-we-service/maintenance-and-operations-managers)

## Frequently Asked Questions

**How large should a pre-staged spare inventory be?**: Size it to the failures you expect to handle simultaneously on critical routes, not to the whole network. A practical starting point is enough cable to restore the longest realistic exposure on your highest priority segments, plus closures and consumables for several concurrent splice locations. The goal is to remove sourcing from the critical path for the first day or two, after which normal supply channels usually reopen.

**Does an emergency permit process delay restoration?**: Usually not for the initial repair, provided the agency's emergency rules are known in advance. Many right of way agencies accept emergency work with prompt notification and a permit filed afterward, each on its own terms. The delay risk sits with the permanent repair, where full permitting, restoration standards, and sometimes make-ready apply. Planning for two stages, a fast temporary restoration followed by a scheduled permanent repair, keeps expectations accurate for everyone reading the outage report.

**What is the most common gap found in restoration planning?**: Stale as-built data. Networks change constantly through repairs, relocations, and new laterals, and redlines that never get merged into the network of record leave crews working from a map that no longer matches the ground. The fix is procedural rather than technical: make as-built merge a completion condition on every job, including emergency repairs, so records stay current without a separate cleanup project.

**Should the plan cover aerial and underground differently?**: Yes, because they fail differently and their repairs depend on different third parties. Aerial restoration often waits on the electric utility to clear energized conductors and on pole replacement through make-ready. Underground restoration waits on locates, potholing, and permits. Each path has different spares, different equipment, and different lead times, so the plan should carry separate sequences and separate escalation contacts.

**Who should keep the restoration plan current?**: One named person on the operator side should own it, with the contractor responsible for its own sections such as contacts, equipment and spare inventory. Shared ownership without a named owner means nobody updates it. Tie the review to a fixed date before storm season and to network changes such as new routes or cable types, and keep a printed copy in each response vehicle in case systems are down.

**Does a restoration plan need to cover small cuts or only storms?**: Both, because the same weak points slow a single backhoe cut and a regional storm. Missing slack records, unmatched spare cable and an unsigned agreement add time to any event. Storms add scale, competition for crews and outside dependencies such as the electric utility. Write the plan for a single cut first, then add storm sections for priority ranking, re-entry credentials and multi-day reporting.

## Related services

- [Storm ResponseHurricane and severe weather response for fiber networks in Volusia County and Central Florida: pre-storm staging, damage assessment, and aerial rebuild.](https://strillacommunications.com/services/emergency-service-restoration/storm-response)
- [Emergency Service RestorationUnplanned repair work that puts a damaged fiber or conduit network back in service after a cut, a storm, or a failure, followed by permanent repair and a documented closeout.](https://strillacommunications.com/services/emergency-service-restoration)
- [Preventive MaintenanceScheduled preventive maintenance for fiber plant in Florida. Aerial and underground inspection cycles, OTDR trending, defect lists, and seasonal passes.](https://strillacommunications.com/services/system-maintenance/preventive-maintenance)
- [As-Built DocumentationAccurate as-built records captured in the field during construction, not reconstructed afterward. Coordinates, depths, photos and reconciled footage.](https://strillacommunications.com/services/supporting-services/as-built-documentation)
- [Ongoing Network SupportOngoing network support for Florida fiber owners. Reserved crew capacity for adds, moves, relocations, small placements, and daily reporting on open work.](https://strillacommunications.com/services/system-maintenance/ongoing-network-support)

---
Source: https://strillacommunications.com/blog/why-emergency-fiber-restoration-needs-a-plan-before-the-storm