80%of requests cleared as routine
The problem
Crews ask the control center tens of thousands of times a year to put protective devices in non-reclose before they work. A dispatcher traces each one by hand, checks it against active switching and other holds, and confirms the crew is authorized. A missed upstream device or an overlapping hold is a safety event.
What we ran
A day of crew requests generated on a large network model, with planted conflicts: a device upstream of the wrong section, an overlapping hold, an unauthorized crew.
What the agent did
For each request it traces from the work location to every device that must be in non-reclose, confirms the device state, checks for conflicts with active switching orders and holds, and checks crew authorization. Routine requests reach the dispatcher as one-click approvals. Conflicts arrive flagged with the reason.
Results
| Measure | Today | With Evardi |
|---|---|---|
| Minutes per routine request | 6 | 1.5 |
| Requests cleared as routine | None | 80% |
| Planted conflicts caught | Depends on the dispatcher | Reported as a count per 100 requests |
What it is worth
- Utility cash: requests a year × minutes saved × loaded dispatcher hour × share realized
- Safety conflicts caught are reported as counts, never as dollars
* Study simulated with partners on public data.
Run it on your network
One shift of reclose-off requests and the feeder model. We re-check every request and list what the agent would have flagged.
Book a demoSee Field operations on the platform
Full study
Request the full study.
The complete write-up of “Every reclose-off request checked against live switching and crew authorization”: method, data, results and assumptions, as a PDF. Leave your work email and we'll send it.
