These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Power Plant Operations
- Features
- Operational events
Operational events
Follow plant interruptions from first report through recovery.
OverviewMaintenance Due×
Power Plant Operations · Operational events
New
Maintenance Due
Maintenance tasks
| Id | Task | Due date | Status | Site | Assigned to | |
|---|---|---|---|---|---|---|
| IDD-240 | TSK-290 | 07 Oct | Open | STS-8896 | ||
| IDD-527 | TSK-140 | 11 Oct | Approved | STS-4247 | ||
| IDD-648 | TSK-660 | 04 Oct | In progress | STS-1335 | ||
| IDD-737 | TSK-517 | 07 Oct | Completed | STS-9272 | ||
| IDD-449 | TSK-146 | 08 Oct | Open | STS-4897 |
6 of 6 records
IDD-240Maintenance tasks · MT-10605
OpenTaskTSK-290
Due date07 Oct
SiteSTS-8896
What you can do
Operational events in daily work
Operational events identify outages, maintenance, alarms and curtailments at a site. Each event has the time it began, an optional recovery time, a description and a status that moves through Open, Acknowledged and Resolved. The Business Overview brings open and assigned work into one portfolio view. A plant operator can raise the event; an Operations Manager then acknowledges the response and decides whether a maintenance task is needed.
The actual start time is important because an event can be reported after it begins. The end time records recovery, rather than the moment a person happened to edit the record. Acknowledgment tells the next shift that the issue has been seen. Resolution should follow a check of recovery and any intended response work. The operational event also anchors a generating unit, giving staff the reason and site context when they inspect unit state.
How the work is organized
- First report. Record the actual start time, site and event type when the operator raises an event.
- Response. Use Open and Acknowledged to separate unreviewed events from work the manager has taken on.
- Recovery. Record the actual end time and inspect site work before marking the event Resolved.
What to agree during setup
- Event categories. Agree when a condition is recorded as an outage, alarm, curtailment or maintenance event.
- Response ownership. Name the manager who acknowledges events and decides when site work is needed.
- Recovery evidence. Decide which staff confirm the recovery time and whether related tasks should be checked before resolution.
Check the handoff on an actual case
An alarm starts during the evening shift and is entered when the operator reaches the desk. The operator records when it actually began, its site and description. The manager sees the Open event, acknowledges it and asks for a task if a technician must inspect equipment. When the condition ends, the manager records the recovery time and reviews the task outcome before marking the event Resolved. The board preserves the distinction between newly raised, acknowledged and closed events across shifts. The task and event both identify the site; the manager checks them together during handover. The event record keeps the actual start and end times, while the task records its own due and completion times. The Operations Manager should confirm both records before declaring the response complete, especially when an alarm was reported after it began.
The manager can use the Business Overview to see the open event portfolio alongside assigned maintenance work. This gives the shift lead a starting point for review, while the event record carries the precise type, start time and response status. Ask the incoming operator to explain which events still need acknowledgment and which have a confirmed recovery time.
What your team sees
- Open Operational Events — New site events needing an initial response.
- Operational Events Board — Events grouped by response status.
Follow the work through
See the related operating process and data model when agreeing who records each step.
What it keeps track of
Data model- Operational events
- Outages, maintenance, alarms and curtailments with response and recovery.
- Sites
- Generating sites and their operating status.
- Generating units
- Generating units attached to an operational record, with rated capacity and fuel type.
- Maintenance tasks
- Assigned maintenance work arising from operational events.
Who uses it
Permissions- Plant Operator
- , Operations Manager, Maintenance Technician.
Set up Power Plant Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.