Feeder Vellmoor Distribution · control room Synthetic data Sun 02:00

Ledger

Every action the operator took or proposed, newest first: the incident, the call it made, its tier, who decided, and what is at stake in customers. Open a row for the evidence, the definition version it ran on, and the undo.

every kind1,020 crew to restored area8estimated bill57housekeeping148outage cluster500planned work collision20priority customer in outage113reverse flow unregistered32transformer overload53voltage out of band10wrong feeder meter39zero consumption40
every status approved38done916declined18asked a person38failed9undone1

Showing 17 rows. Housekeeping rows are tickets the operator closed itself once their meters sent a restore.

#timeincidentsubjectcalltierstatusat stake
970Sun 00:15outage cluster feeder 1125POST /notifications/outage outage=983 estimate=+13.0 h T2asked a person22 customers off supply for 108 min (2,383 customer-minutes so far)
932Sat 23:11outage cluster feeder 1027POST /notifications/outage outage=979 estimate=+13.0 h T2asked a person66 customers off supply for 4 min (231 customer-minutes so far)
907Sat 22:51outage cluster feeder 1020POST /notifications/outage outage=974 estimate=+13.0 h T2asked a person12 customers off supply for 3 min (38 customer-minutes so far)
897Sat 22:41outage cluster feeder 886POST /notifications/outage outage=972 estimate=+13.0 h T2asked a person73 customers off supply for 3 min (241 customer-minutes so far), 1 on the priority register
843Sat 22:00outage cluster feeder 1067POST /notifications/outage outage=958 estimate=+13.0 h T2asked a person16 customers off supply for 3 min (51 customer-minutes so far), 1 on the priority register
839Sat 22:00outage cluster feeder 1024POST /notifications/outage outage=957 estimate=+13.0 h T2asked a person14 customers off supply for 4 min (49 customer-minutes so far)
804Sat 21:44outage cluster feeder 1109POST /notifications/outage outage=948 estimate=+13.0 h T2asked a person43 customers off supply for 4 min (150 customer-minutes so far)
789Sat 21:43outage cluster feeder 1042POST /notifications/outage outage=941 estimate=+13.0 h T2asked a person15 customers off supply for 4 min (56 customer-minutes so far)
700Sat 20:42outage cluster feeder 1150POST /notifications/outage outage=917 estimate=+13.0 h T2asked a person30 customers off supply for 3 min (102 customer-minutes so far)
691Sat 20:41outage cluster transformer 5799POST /oms/outages feeder=1183 transformer=5799 meters=7 T2asked a person7 customers off supply for 4 min (24 customer-minutes so far)
660Sat 20:19outage cluster feeder 1143POST /notifications/outage outage=905 estimate=+13.0 h T2asked a person25 customers off supply for 4 min (92 customer-minutes so far), 1 on the priority register
639Sat 20:10outage cluster transformer 1716POST /notifications/outage outage=900 estimate=+13.0 h T2asked a person106 customers off supply for 4 min (371 customer-minutes so far)
611Sat 19:55outage cluster feeder 1163POST /notifications/outage outage=891 estimate=+13.0 h T2asked a person54 customers off supply for 3 min (184 customer-minutes so far), 1 on the priority register
565Sat 19:31outage cluster feeder 1012POST /notifications/outage outage=875 estimate=+13.0 h T2asked a person38 customers off supply for 4 min (133 customer-minutes so far)
556Sat 19:26outage cluster feeder 1100POST /notifications/outage outage=871 estimate=+13.0 h T2asked a person18 customers off supply for 4 min (63 customer-minutes so far)
526Sat 19:10outage cluster feeder 1034POST /notifications/outage outage=862 estimate=+13.0 h T2asked a person16 customers off supply for 3 min (54 customer-minutes so far)
521Sat 19:07outage cluster feeder 1014POST /notifications/outage outage=860 estimate=+12.5 h T2asked a person11 customers off supply for 3 min (34 customer-minutes so far), 1 on the priority register