Generation Availability Reporting demo
Outage events coded right for GADS and the board. 1:14
What the demo shows
A workflow solution for availability analysts that codes outage events and files reports.
Each unit's year is one strip of states. Six agents build every outage and derate from the historian signals, read the shift log and the work order, propose the event type and the cause code with their reasons, and check every record before the quarter is filed. The analyst confirms each code; the reporting lead signs.
Transcript
- Generation Availability Reporting codes every outage to its cause and files the quarter.
- Every outage needs the right code by the deadline, from logs never written for reporting.
- Each unit's year is one strip.
- Outages, derates, and what is still uncoded.
- Harrow Point 3 came off on the 20th of September.
- 88 hours, uncoded. The agents read the shift log and the work order, a water wall tube leak.
- The proposed code, boiler tube leak, 1000, checked nine ways.
- Ines confirms, before filing, 12 checks, catch an extension that was really a forced outage.
- Coded to the fail part, this year's three leaks read as one problem.
- Every outage coded right and checked before it is filed.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.