PI VISION DOWNTIME GUIDE
Downtime Management in PI Vision with Events Table+
Create a consistent downtime record, let operators add context in PI Vision, and use the resulting Event Frames to see where production losses repeat.
Downtime analysis usually fails for a simple reason: the record contains the duration, but not enough information to explain the loss. If one event is tagged as an equipment failure, another as a stop, and a third only has an operator comment, the team cannot compare them reliably.
A better workflow keeps the time range, affected asset, reason, impact, and operator context in the same PI System record. Events Table+ gives PI Vision users a configurable table for reviewing, creating, editing, filtering, grouping, and commenting on those Event Frames. The result is a downtime display that supports both the immediate correction and the later analysis.
Define the record
Use one Event Frame template with consistent fields for time, asset, reason, impact, and notes.
Complete it in PI Vision
Use Events Table+ to review events, create missing records, correct attributes, and add context.
Find repeat losses
Use filters, KPIs, charts, and event details to decide which downtime pattern needs attention.
Step 1 · Event Frame model
Give every downtime event the same shape
Start with the questions your operators and improvement team ask every day: what stopped, when did it stop, why did it stop, and what was done? Those questions should become the required or recommended attributes of the downtime Event Frame template.
| Field | What it supports | Example |
|---|---|---|
| Start and end | Duration, overlap, and time-based comparison. | 08:15–10:45 |
| Affected asset or line | Grouping losses by the equipment that needs attention. | Line 1 / Filler 04 |
| Reason code | Consistent categories for recurring-cause analysis. | Equipment failure |
| Impact or severity | Prioritization by production effect or agreed severity. | Unplanned / high |
| Operator comment | Context that a fixed reason code cannot capture. | Conveyor jam; waiting for parts |
Keep the model usable: do not add fields simply because they are available. If an attribute is not used during handover, troubleshooting, or analysis, leave it out of the first version.
Step 2 · Operator workflow
Complete the downtime record where the work happens
Displaying an Event Frame is useful, but it does not solve the data-quality problem if operators must leave PI Vision to correct the reason or add a note. Events Table+ provides the interactive surface for the configured Event Frame model. The exact actions available depend on the PI System permissions and the symbol configuration.
Show the right events
Configure the event search, time range, affected elements, and attributes that the user needs for the current area or line.
Make the context visible
Place timing, asset, reason, impact, severity, and comment fields next to each other so a user can understand an event without opening several screens.
Enable controlled editing
Configure the fields that may be changed and use the permissions appropriate for your environment. Test the edit path with a non-production record first.
Create missing events
When a downtime record was not created automatically, use the configured creation action to select the template, set the time range, and enter the initial context.
Leave a useful note
Use comments for observations, temporary workarounds, and follow-up information that should travel with the event into the next review.
Step 3 · Analysis
Use the same records to find the next improvement
Once the records are consistent, the display can answer more than “how much downtime did we have?” It can show which reason, line, shift, or asset accounts for the largest share and let the user trace a summary back to the underlying events.
Filter the scope
Narrow the view by time range, line, asset, shift, reason, or another field that matters to the investigation.
Measure the loss
Show event count, total duration, average duration, or another agreed KPI for the selected records.
Compare causes
Use a chart or distribution view to see whether equipment, changeover, waiting, or another category dominates.
Trace the detail
Keep the event table available so a summary can be checked against the actual time range and operator context.
Rollout and verification
Test the complete workflow before relying on it
A downtime display is ready when a user can follow one event from creation or detection through editing, analysis, and review. Test the actions with the same permissions and Event Frame templates that production users will have.
Check the template
Confirm the Event Frame template, attribute names, time zone, and affected-element context.
Test a new event
Create a non-production downtime record, enter the required fields, and confirm that the time range is correct.
Test an edit and comment
Change a reason or severity, add a comment, and verify that the updated values remain with the Event Frame.
Test the analysis
Filter to the test event and confirm that the KPI and chart change with the selected records.
Review with operators
Remove fields that slow down the workflow and document which edits require which permissions.
FAQ
Downtime management questions
Why use Event Frames for downtime?
Event Frames provide a time-bounded record that can carry the reason, affected asset, impact, severity, and notes. That structure is easier to search and compare than an isolated duration value.
Can Events Table+ create and edit every Event Frame?
It works with the configured Event Frame model and the permissions available to the user. Confirm the required templates, write access, and site governance before enabling production edits.
Which fields should be required?
Start with the fields needed for daily decisions: time range, affected asset or line, reason, impact or severity, and a concise operator note. Add more only when the team knows how it will use them.
How do I compare downtime causes?
Use consistent reason values, then filter the Event Table and summarize the selected records with a KPI, chart, or distribution view. Keep the underlying events visible so the summary can be checked.
Make downtime data useful at the point of work
Events Table+ is part of Vision Library+, the custom symbol and extension library for AVEVA PI Vision. Use it to connect Event Frame records, operator input, and analysis in one display.
