How to Build a Daily Shift Log in PI Vision Using Events Table+ and Vision Report+
Build one shift record from recurring Event Frames, let operators complete it in PI Vision, and distribute the finished handover as a repeatable report.
A useful shift log connects the record, the operator, and the handover.
A paper form or spreadsheet can collect notes, but it often separates those notes from the PI System context. A digital shift log should answer three questions without making the next shift assemble the story again: Which shift does this belong to? What happened during it? Who needs the result?
1. Define the shift
Use a recurring Event Frame to create the time boundary and connect the shift to the relevant plant, area, unit, or line.
2. Complete the record
Use Events Table+ to review events and edit the configured comments, reasons, totals, and observations.
3. Share the result
Use Vision Report+ to generate the same handover report on a schedule or Event Frame trigger and deliver it to the next team.
Use one recurring Event Frame for each shift.
The Event Frame is the record that gives the handover its time range and operating context. A 12-hour schedule is only an example; use the shift boundaries defined by your facility, including the correct time zone and daylight-saving behavior.
Create the template
In PI System Explorer, create an Event Frame Template for the shift log, such as Shift Log.
Generate the records
Use PI Analysis Event Frame Generation or the scheduling method already approved for your PI System.
Attach the context
Associate the template with the AF Elements used by the report: plant, area, unit, production line, or another operating scope.
Define editable fields
Add the attributes that the operator or supervisor must complete, such as comments, safety notes, production totals, and downtime reasons.
Put the handover fields where operators already review the events.
Events Table+ turns the Event Frame list into an interactive PI Vision workspace. It can filter and search events, group them by configured attributes, show child-event context, and allow supported attributes to be edited or commented on directly in the table.
For a shift log, configure the table around the fields the next team needs. Do not expose every available attribute just because it exists in AF; keep the primary view focused on decisions and follow-up.
- Create a PI Vision display and add Events Table+.
- Filter the table to the shift Event Frame Template and the required element context.
- Show the start time, end time, operator, comments, production total, safety note, and downtime reason columns.
- Enable editing only for the fields operators are expected to change, then verify the mapping to the Event Frame attributes.
Turn the completed Event Frame into a repeatable handover report.
Build a report display from the same PI Vision context. Include the completed shift Event Frame, production totals, downtime events, operator comments, and any trends or KPIs that the next team needs. Then configure Vision Report+ to create the output on the schedule or trigger that fits the operation.
Schedule it
Generate the report at the end of each shift or at another recurring time.
Trigger it
Use an Event Frame start or completion event when the report should follow the operating record.
Deliver and retain it
Send PDFs or images by email, print them, and keep report executions available for review, download, or rerun.
Use permissions and a controlled recipient list. A report is part of the operating process, so the administrator should know which configuration generates it, who receives it, and where the execution history can be reviewed.
Keep the primary log focused on the next decision.
The right fields depend on the facility, but the table below is a practical starting point. Add fields only when they change an action, explain an event, or provide a value the report must carry forward.
| Field | Why it belongs in the log | Typical data |
|---|---|---|
| Shift start and end | Defines the handover time window and report context. | Event Frame times |
| Operator comments | Carries observations, actions, and open issues to the next team. | String attribute |
| Production total | Connects the handover narrative to the measured result. | Numeric attribute or PI value |
| Downtime reason | Provides a consistent category for follow-up and loss analysis. | Dropdown or string attribute |
| Safety or maintenance note | Keeps open risks and required work visible to supervisors. | String attribute |
Test the complete handover, not just the display.
Confirm the schedule
Check shift boundaries, time zone, AF context, and the Event Frame generated for the expected interval.
Test an edit
Change a test comment, reason, or value in Events Table+ and verify that the intended Event Frame attribute changes.
Test missing and invalid input
Check required fields, invalid values, denied writes, unavailable data, and what the operator sees when a save fails.
Test the report output
Confirm that the report selects the completed shift, renders the expected fields, and remains readable as a PDF or printed copy.
Test delivery and history
Verify recipients, storage or execution history, rerun behavior, and the ownership of the report configuration.
Document the handover
Record the Event Frame template, display, report, recipient list, permissions, and the person responsible for future changes.
Daily shift-log FAQ
Do I need Event Frames for a shift log?
Event Frames provide the time-bounded record and context that make a shift log repeatable. You can adapt the same pattern to the shift schedule and AF structure used by your facility.
Can operators edit Event Frame information in PI Vision?
Events Table+ supports editing and commenting on configured event attributes. Configure only the fields operators should change, confirm the mapping, and test the permissions in your environment.
How can the report run automatically?
Vision Report+ supports scheduled and Event Frame-triggered report generation, as well as on-demand execution. Choose the trigger that matches the handover process and verify the resulting execution history.
What should be in a daily shift report?
Start with the shift time window, operator comments, production totals, downtime reasons, and safety or maintenance notes. Add trends, KPIs, or related Event Frames when they support a decision made during handover.
