Phased Restoration Schedule¶
Schedule — instantiates Recovery Trajectory Management
A time-phased plan that pins the restoration sequence to dates and loads each phase with the crews, materials, and capacity it needs — so recovery moves as fast as resources actually allow.
A Phased Restoration Schedule is the mechanism that binds what order to when and with what. It takes an already-decided restoration sequence and lays it across a calendar, then loads each phase with the concrete capacity it consumes — crews, equipment, materials, mutual-aid resources — so the plan is paced by what the recovery can actually resource rather than by wishful dates. Its distinctive concern is feasibility over time: recovery is itself a load on a damaged system, and a schedule that ignores crew fatigue, material lead times, and staging bottlenecks will promise a restoration date it cannot hit. The schedule exists to make the resource constraint visible and to prevent the recovery process from overloading the very system it is repairing.
Example¶
A hurricane knocks out power to 1.2 million customers across a utility's territory. The restoration order is already set by dependency — the system cannot energize neighborhoods before the transmission backbone and substations are live. The phased restoration schedule turns that order into an executable timeline. It begins from the units that must come first, then loads each phase with resource reality: how many line crews are staged (including mutual-aid crews arriving from three states away on day two), how much wire and how many transformers are in inventory versus on order, how many bucket trucks can reach flooded areas. The schedule reveals that transformer stock, not crew count, is the binding constraint for phase three — so procurement is expedited and the schedule is re-paced around delivery dates rather than around optimism.
The result is a defensible restoration curve: X percent of customers back by day 3, Y by day 7, each milestone backed by the crews and materials actually committed to it. When leaders ask "why not faster?", the schedule answers with the binding resource, not a shrug.
How it works¶
- Inherit the sequence. Take the dependency-ordered restoration order as a given input and place its steps on a timeline; the schedule does not re-decide priority, it times it.
- Load each phase with capacity. Attach the crews, equipment, materials, and rebuilt capacity each phase consumes, drawn from a live inventory of what is available and inbound.
- Find the binding constraint. Compute where the schedule is limited — labor, materials, staging, or access — and pace the plan to it, expediting or resequencing to relieve the true bottleneck.
- Treat recovery as a load. Budget for the fact that restoration work itself taxes the damaged system, so the pace does not trigger secondary overload.
Tuning parameters¶
- Phase length — short, tightly-milestoned phases versus longer ones. Short phases give frequent re-planning points but multiply scheduling overhead and hand-offs.
- Resource buffer — how much slack crews and materials carry above the plan. Buffer absorbs surprises and prevents overload but slows the headline restoration date.
- Aggressiveness — how close the schedule runs to maximum feasible pace. Aggressive schedules restore faster but leave no margin and risk crew burnout and rework.
- Constraint-relief lever — whether to relieve the binding constraint by adding resources, resequencing, or accepting a later date. Each trades cost, risk, and time differently.
- Re-baseline cadence — how often the schedule is re-cut against actuals. Frequent re-baselining keeps the plan honest but can churn commitments downstream.
When it helps, and when it misleads¶
Its strength is that it converts a priority order into a committed, resourced timeline and surfaces the one thing that actually governs speed — the binding resource constraint — so pace debates attach to reality rather than pressure.[n1]
Its failure mode is the schedule that is optimistic about resources: it publishes dates the crews and materials cannot support, and because a restoration date is politically load-bearing, the gap is hidden until it is missed. Running the schedule at maximum aggressiveness invites the archetype's secondary collapse — the recovery overloads the damaged system, causing rework and relapse that make the whole effort slower. The guarding discipline is to pace to the binding constraint with honest buffer, treat recovery itself as a capacity load, and re-baseline against actuals instead of defending a date that reality has already overtaken.
How it implements the components¶
restoration_sequence— takes the dependency-ordered restoration order and renders it as a concrete, milestoned timeline across a calendar.resource_and_capacity_rebuild_plan— loads each phase with the crews, equipment, materials, and rebuilt capacity it consumes, and paces the whole plan to the binding resource constraint.
It times and resources the order but does not decide the priority ranking that sets that order — critical_function_priority_map is Critical Function Triage Matrix's — nor does it verify at each step that the restored function actually works, which is recovery_validation_signal in Service Restoration Runbook. The schedule answers *when and with what, not which first or did it work.*
Related¶
- Instantiates: Recovery Trajectory Management — this schedule paces the restoration sequence against real resources over time.
- Consumes: Critical Function Triage Matrix supplies the priority-ordered sequence the schedule places on a calendar.
- Sibling mechanisms: Critical Function Triage Matrix · Service Restoration Runbook · Incident Recovery Plan · Recovery Dashboard · Community Recovery Plan
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Phased Restoration Schedule operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it a time-phased plan that pins the restoration sequence to dates and loads each phase with the crews, materials, and capacity it needs — so recovery moves as fast as resources actually allow.
Independent corroboration: The frozen evidence defines Phased Restoration Schedule as 'A time-phased plan that pins the restoration sequence to dates and loads each phase with the crews, materials, and capacity it needs — so recovery moves as fast as resources actually allow', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Phased Restoration Schedule is rooted in disaster management and risk reduction: Emergency recovery and black-start practice restore interdependent functions in resource-constrained order.
Related originating lineages:
- Engineering & Design — Engineering and design materially shaped Phased Restoration Schedule through reliability, physical systems, safety, and mistake-proof design. Infrastructure repair dependencies and technical commissioning shape phase order.
- Logistics & Supply Chain Management — Crew, material, and capacity loading supply the executable restoration sequence.
- Operations Research — Operations research materially shaped Phased Restoration Schedule through optimization, graph reachability, scheduling, and decision analysis.
Review resolution: Both blind reviewers agree that emergency and disaster-risk management is the primary origin. Reconciliation resolves alternate_origin_disagreement, domain_reach_disagreement, encyclopedia_synthesis_disagreement. Formative alternate lineages are retained as engineering_design, operations_research, logistics_supply_chain; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A power system with no external supply is restored by black start — energizing a self-starting generator, then bootstrapping the grid outward through a strict dependency order under tight resource and stability limits. It is a vivid case of why restoration must be sequenced and resource-paced rather than switched on all at once. ↩