An incident record should connect what the system observed with what people checked and did. Linking SCADA events, shift notes and maintenance records helps reviewers reconstruct an operating event without relying on memory.
Create a common event reference
Record facility, equipment, time and event identifier. Link relevant alerts, trends, laboratory results and work orders. Keep source records available so a summary can be checked against the underlying evidence.
Record responsibility at each step
Identify who received the alert, performed the inspection, approved an action and confirmed its outcome. Separate acknowledgement from resolution. An event can remain open while follow-up maintenance is still required.
Preserve context and changes
Retain operating mode, signal quality and known data gaps. Log changes to settings, equipment or records with time and responsible person. Revised notes should retain a visible history rather than replace the original account without explanation.
Review the record for future improvements
Use a completed event to check whether warning, response and handover worked. Identify missing evidence and recurring causes. Assign follow-up work and review dates, then test whether another user can reconstruct the same sequence.
Records to check
| Record group | Evidence to review |
|---|---|
| Observation | Time, source, quality and context |
| Response | Person, inspection and approved action |
| Outcome | Verification, evidence and follow-up work |
Prepare an assessment with X-IRIS
Bring representative incidents, shift records and maintenance forms to agree the required links and responsibilities. Review the implementation roadmap and request an assessment to agree a scope that can be tested.
