Which tenants, halls and racks sit on the lost feed, and how much of each customer's load is exposed.
Facilities and vendor technicians on call, who has been paged, and who is on the way in.
One tap to the network operations center, from the same screen the alert opened on.
Fuel deliveries and vendor requests, with the generator runtime clock counting down beside them.
SLA exposure by tenant, plus the Uptime, NFPA 110 and SOC 2 clocks the event has started.
The tenant roster and contacts, so the ones affected hear from you before they open a ticket.
Customers out by feeder and substation, and how much load is at risk as the footprint grows.
The dispatch board: which crews are assigned, en route, and on site, feeder by feeder.
One tap to the system operations center, from the same screen the alert opened on.
Request and track crews from neighboring utilities when the storm outruns your own.
Regulatory and outage-reporting clocks, including NERC CIP, running from the moment the event starts.
Hospitals, water plants and other priority-restoration accounts, flagged on the list and the map.
Satellite view of the service territory or facility with feeders, substations, the power chain, and the outage footprint drawn live.
Outage notifications with a pending count, the affected assets, and who has acknowledged.
Reach the operations center over the same link the alerts use, with a CORP or OT pill on every message.
Send a photo, a note, or a file from the field straight into the outage record.
The field guide, in the app, for the operations director who was handed the phone thirty seconds ago.
Lock keeps the session and hides the screen. Log out clears the key, the session, and any OT grant.
The map lights the affected feeders, the alert fires, the outage list fills. Then the corporate link goes with the power.
One tap requests OT. ADMIN accepts and the phone switches to the control network. Same app, same session, red theme so nobody mistakes the network.