Event to resolution

From logging an outage, alarm or curtailment to resolving it with real start and end times.

Step by step

Log event Operations Engineer

The operations engineer opens an operational event on the affected site as soon as it is known, with its type (outage, alarm, curtailment or maintenance) and a description.
- Event opened on the site
- Updates Operational events, Sites
Acknowledge event Operations Engineer

The operations engineer takes ownership, records the real start time and moves the event to acknowledged. If the event needs a response, a maintenance task is raised on the same site. An event cannot be acknowledged with a missing start time.
- Owner and real start recorded; task raised if needed
- Updates Operational events, Maintenance tasks
Approve maintenance Site Manager

The site manager approves the maintenance task before any work starts.
- Task approved for work
- Updates Maintenance tasks
ApprovalA person approves before the work moves on.
Complete maintenance Maintenance Technician

The assigned technician starts the task, does the work and completes it with the completion date.
- Work done and dated
- Updates Maintenance tasks
Resolve event Operations Engineer

Once the site has recovered, the operations engineer records the real end time and resolves the event.
- Real end recorded; event resolved
- Updates Operational events

And how to keep it from happening.

The event is logged hours later with the logging time as its start, and availability figures for the day are wrong.
A curtailment is recorded as an outage, so the owner is told the site failed when it was held back by the grid.
Work starts before the task is approved, and nobody can say later who agreed to take the turbine out.
The event is resolved when the technician leaves site, not when production has actually recovered.

Start free, then use Proto to change fields, steps and approvals before your team goes live.