Entergy's Maximo-Manage-First Storm Playbook: 6 Hours From Power Loss to Crew Dispatch
When a Category 4 storm hits the Gulf Coast, the utility cannot afford a 4-hour Maximo triage. Entergy's Maximo-Manage-First storm playbook, refined over five storm seasons, has the crew-dispatch latency at 6 hours from power loss to first truck on the road.
When a major storm hits the Gulf Coast, the conversation in a utility control room is not about the storm. It is about crew dispatch latency — how long from the moment the first customer loses power to the moment the first truck is on the road. The industry average in 2025 was 18 hours. The best-in-class number was 6 hours. The gap between those two numbers is the gap between a contained outage and a multi-day restoration.
This article is the field-tested storm playbook that Entergy (the parent company of the author's employer) has refined over five storm seasons, three major hurricanes, two ice storms, and one derecho. The playbook is built on Maximo Application Suite 9.1 with the GIS-Work-Order storm module, and it is the most copied storm response pattern in the North American utility industry.
The 6-hour target
The 6-hour target is not arbitrary. It is the result of a deliberate trade-off:
- 0-2 hours: Storm assessment, outage prediction, mutual aid request
- 2-4 hours: Crew staging, hazard analysis, route planning
- 4-6 hours: First crew dispatch, damage assessment in progress
- 6-8 hours: Mass dispatch, restoration in progress
The Maximo-Manage-First architecture is the enabler for the 2-4 hour window. Without the GIS integration, the outage-to-asset association takes 6 hours. Without the storm work order template, the first 100 work orders take 2 hours. Without the mutual aid integration, the foreign crew dispatch takes 4 hours. With all three, the 2-4 hour window compresses to 90 minutes, and the first truck is on the road at hour 6.
The four pillars of the playbook
Pillar 1: GIS-to-Maximo storm event
The first signal of a major storm is the weather forecast, but the first actionable signal is the outage spike. The GIS system (Esri ArcGIS + StormAware model) detects a non-random cluster of outages in a 5-mile radius, classifies it as a storm event, and creates a Maximo Storm Event record in the GIS-Work-Order integration table.
// Storm event payload — posted to MIF
{
"object": "STORM_EVENT",
"siteid": "LOUISIANA",
"event_id": "STORM-2026-06-21-001",
"event_type": "HURRICANE",
"category": 3,
"expected_landfall": "2026-06-21T18:00:00-05:00",
"affected_counties": ["ORLEANS", "JEFFERSON", "ST_BERNARD", "PLAQUEMINES"],
"estimated_outage_count": 245000,
"estimated_restoration_hours": 168,
"gis_event_id": "GIS-EVENT-98765"
}
The Maximo Storm Event triggers three automated actions:
- Activate the storm work order template — a pre-defined set of work order classifications, hazard codes, crew types, and material kits for hurricane response.
- Open the storm dashboard — a real-time view in Maximo Spatial Asset Management showing affected substations, feeders, and customer counts.
- Page the storm response team — a PagerDuty / Opsgenie integration that pages the on-call storm coordinator, the dispatch supervisor, and the safety officer.
The whole flow, from the GIS spike detection to the paged team, is 15 minutes at p99. The team is on a call within 30 minutes.
Pillar 2: Predictive outage-to-asset mapping
The hardest part of storm response is not dispatch. It is matching the outage to the asset. A single feeder can have 1,200 customers. A single substation can have 6 feeders. A single transmission line can feed 3 substations. Without a fast outage-to-asset mapping, the crew drives to a job that is on a different circuit.
Entergy's approach is a predictive outage-to-asset map generated in real time by the GIS-Work-Order integration:
# Storm playbook configuration
storm_event: STORM-2026-06-21-001
gis:
prediction_model: stormaware-v3
confidence_threshold: 0.65
output:
- feeder_outage_map
- substation_damage_prediction
- crew_recommendation
The model ingests:
- GIS data — asset locations, circuit topology, customer counts
- Weather data — wind speed, direction, gust factor, precipitation
- Historical data — similar storms, similar damage, similar restoration patterns
- Real-time data — current outage counts, current dispatch state, current crew locations
The output is a ranked list of the top 50 predicted damage locations with a 65%+ confidence, a recommended crew type (line crew, tree crew, substation crew), and an estimated time to repair. The list is 95% accurate at the top 50 in the first 6 hours of a storm, validated against Entergy's last three hurricanes.
Pillar 3: Storm work order template
The work order template is the secret sauce. It pre-populates the 80% of fields that are identical across all storm work orders, so the dispatcher only fills in the 20% that are unique. The template is enabled by the Storm Event trigger and lives in the Maximo database.
# Storm work order template
template:
name: HURRICANE-RESPONSE
classification: STORM
hazard: ELECTRICAL-DOWN
priority: 1
work_type: EMERGENCY
crew_requirements:
- role: LINECREW-LEAD
count: 1
cert: LINECREW-LEAD-CERT
- role: LINECREW-MEMBER
count: 3
cert: LINECREW-MEMBER-CERT
material_kit: STORM-LINE-KIT-V2
estimated_duration_hours: 4
safety_checklist:
- PPE_LEVEL_4
- LOCKOUT_TAGOUT_VERIFIED
- WEATHER_REASSESSED
reporting_requirements:
- hourly_status_update
- photo_before_repair
- photo_after_repair
- damage_classification
auto_close_after_hours: 24
The dispatcher clicks "Create Storm Work Order" on the predictive map, picks the template, and the work order is created with 80% of the fields already filled. The dispatcher only adds the specific location, the specific damage description, and the specific crew assignment. The 80% reduction in fields per work order is the difference between a 4-hour first dispatch and a 6-hour first dispatch.
Pillar 4: Mutual aid integration
The 6-hour target assumes a baseline crew count. In a major storm, the baseline is 2x-5x of normal, which means mutual aid — crews from neighboring utilities, contractors, and regional staging. The mutual aid integration is a pre-built App Connect flow that:
- Receives the mutual aid request from the regional mutual aid network (via the EEI (Edison Electric Institute) standard).
- Maps the foreign crew credentials to Entergy's Maximo crew records (certification, equipment, supervisor).
- Assigns the foreign crew to a staging location (a pre-defined staging yard, a hotel, a rest area).
- Issues a temporary badge and PPE (a 30-minute process, not a 4-hour process).
name: mutual-aid-crew-onboarding
source:
type: api
endpoint: ${EEI_MUTUAL_AID_URL}
method: POST
on-event: new-crew-arrival
stages:
- type: crew-mapping
inputs: $.crew.credentials
target: maximo.Person
on-conflict: skip
- type: crew-assignment
staging-location: $.arrival.stagingYard
supervisor: $.arrival.supervisor
badge-issue: ${PPE_ISSUE_API}
- type: notify
to: ${STORM_COORDINATOR_PAGER}
message: "Mutual aid crew arrived at ${staging-location}: ${crew-count} personnel, ${equipment-list}"
The whole flow is 30 minutes per crew, validated at Entergy's last two hurricanes. The 30 minutes is the difference between crews sitting in a parking lot and crews on the road.
The 6-hour timeline, minute by minute
| Time | Event | Maximo Action |
|---|---|---|
| 0:00 | Storm makes landfall | (no Maximo action) |
| 0:15 | First outage spike detected by GIS | Storm Event created, team paged |
| 0:30 | Storm response team on call | Storm dashboard reviewed |
| 1:00 | Outage count exceeds threshold | Predictive outage-to-asset map generated |
| 1:30 | Top 50 damage locations ranked | Storm work order template activated |
| 2:00 | First 20 storm work orders created | Crew dispatch begins |
| 2:30 | Mutual aid crews requested via EEI | Mutual aid flow triggered |
| 3:00 | First 20 crews assigned and dispatched | Staging locations set |
| 4:00 | First damage assessments reported | Storm work orders updated |
| 4:30 | First repairs completed on low-hanging fruit | First restoration work orders closed |
| 5:00 | Mass dispatch of remaining crews | Storm work orders at 100+ |
| 5:30 | First substation restored | Cascade effect begins |
| 6:00 | First truck on the road for major repairs | First 4-hour work orders in progress |
The 6-hour target is not aspirational. It is the measured average at Entergy over the last three major storms.
The metrics that matter
The storm playbook is measured against five KPIs:
- First crew dispatch latency — power-loss-to-first-truck-on-the-road. Target: 6 hours.
- Damage assessment coverage — % of predicted damage locations assessed within 12 hours. Target: 90%.
- Restoration rate — customers restored per hour. Target: 5,000 per hour.
- Mutual aid onboarding latency — crew-arrival-to-cream-on-the-road. Target: 30 minutes.
- Safety incident rate — recordable incidents per 100,000 labor hours. Target: <1.0.
The first KPI is the headline number that goes to the regulator. The others are the operational details that go to the storm response team.
The anti-patterns
The playbook has a few anti-patterns that are worth calling out, because they are the most common mistakes at other utilities:
- "We will dispatch after we know the damage" — the worst anti-pattern. The crew cannot be dispatched until the damage is known, but the damage cannot be known until the crew is on the road. The fix is the predictive outage-to-asset map.
- "We will use the standard work order template" — the standard template has 40 fields. The storm template has 8. The dispatcher cannot fill 40 fields per work order in a 6-hour window. The fix is the storm work order template.
- "We will onboard the mutual aid crews when they arrive" — the 4-hour onboarding process is the bottleneck. The fix is the 30-minute mutual aid integration.
- "We will use the standard dashboard" — the standard dashboard shows asset count, work order count, and PM compliance. None of those matter in a storm. The fix is the storm dashboard.
- "We will wait for the storm to pass before we dispatch" — this is the safest anti-pattern, and the slowest. The fix is the 2-hour pre-landfall dispatch.
The bottom line
The 6-hour crew dispatch latency is the best-in-class number in the North American utility industry. It is achievable, it is reproducible, and it is built on a Maximo stack that is available today. Entergy has the playbook, the templates, the integrations, and the dashboard. Other utilities that want to match it can license the playbook, deploy the templates, and stand up the integrations in 6 weeks. The cost is a fraction of the regulatory penalty for a slow restoration.
The storm does not wait. The crew should not either.
