Ledger / #717
cancel planned work on planned work 143
T2 asked a person- incident
- planned work collision inc_95bbe361a6b8
- when
- Sat 20:57
- call
- PUT /planning/planned-outages/143/postpone
- decided by
- rules
- definition
- planned_work_collision v1
- why
- Booked work would take supply off while its own feeder has a fault: postpone it; a person approves.
- controller
- Needs a person: cancel_planned_work is tier 2 (ask first) in the policy. Postpone booked planned work that would collide with a fault; planning re-books and re-notifies customers.
- outcome
- Needs a person: cancel_planned_work is tier 2 (ask first) in the policy. Postpone booked planned work that would collide with a fault; planning re-books and re-notifies customers. · on-call notified (draft)
- at stake
- booked work on a feeder carrying 171 customers, with no backup supply while the fault lasts
Evidence
| customer_minutes | None |
|---|---|
| customers_at_stake | 171 |
| fault_feeder_ids | [484] |
| fault_outage_ids | [679] |
| feed | network |
| feeder_id | 484 |
| hours_to_start | 10.1 |
| planned_outage_id | 143 |
| priority_at_stake | None |
| reason | new connection works |
| same_feeder | True |
| stake_note | booked work on a feeder carrying 171 customers, with no backup supply while the fault lasts |
| started_at | 2026-11-14T20:57:05 |
| work_ends_at | 2026-11-15 12:00:00 |
| work_starts_at | 2026-11-15 07:00:00 |
Arguments
| planned_outage_id | 143 |
|---|---|
| reason | open fault on its own feeder (feeders [484]); work starts in 10.1 h |