Operator training compliance on one screen: every system operator, every reliability-related task, verified with its dated record
Audit-ready proof of every operator's training.
See one case, screen by screen ↓PER-005 asks a Reliability Coordinator, Balancing Authority or Transmission Operator for more than trained people. It asks for a company-specific list of real-time reliability-related tasks, reviewed every calendar year, and a dated record that each system operator was verified as capable on each task assigned to them — again within six months whenever a task is new or modified. That proof sits in five places: the learning system, the simulator's session files, scanned check sheets, sign-in sheets and shift logs. Before an audit, the training team rebuilds the operator-by-task matrix and the binders by hand.
And not every record counts. An attendance sheet shows training was delivered, not that the operator can do the task. Auditors fault utilities that cannot show task-by-task training and competency verification: daily operator logs were rejected as evidence in a WECC case, and task lists missing critical tasks were cited. Too often the gaps are found by the auditor, not by the team.
Estimated split for one audit request such as RFI-07, in working days, by hand and with the solution.
Five agents read every training record into its cell and build the audit binder; the training manager decides what counts.
Lumina Utilities runs the Harrow Ridge Control Centre, with 38 system operators — five crews of seven and three relief operators — against task list v14: 64 tasks in six areas. Granite Plains Reliability Council audits on site from 2 to 6 November 2026. It is Tuesday 13 October. Here is what happens next, screen by screen, in the working solution.
Operators run down the side by crew, the 64 tasks across the top by area, and each cell is verified, inside the six-month window or a gap. Overnight the agents read 412 new records from the learning system, simulator and document library, filed 409 to operator and task and set 3 course sign-ups aside. The grid reads 1,838 verified, 23 inside the window and 6 gaps — 98.4 % of 1,867 assignments.
06:03 · “New gap: Grace Whitfield, task 19 — check sheet CS-2026-0877 has no verifier signature”
Yesterday at 15:40 the auditor, Dana Whitcombe, sent RFI-07: evidence verifying each system operator on task 42, “Shed firm load in a Level 3 energy emergency”, after its change on 14 May 2026 (PER-005-2 R2, R2.1). Hannah opens task 42 in the grid. Its record list reads 34 verified, 3 booked and 1 gap, and the window to re-verify closes on 14 Nov 2026.
“…the capability of each System Operator to perform task 42 … as modified, with dated records.” — Dana Whitcombe, auditor
Malik transferred from the Corran Vale backup centre. His only record for task 42 is LOG-2026-0911 of 11 Sep 2026, verified by nobody. Ethan Marsh, Priya Natarajan and Liam O’Rourke of crew D are already booked on SIM-2026-33; Malik is not.
“Why it is a gap. His only record for task 42 is a shift log entry: it says an event happened, not that a verifier assessed him against OP-118 rev 6.” (rule E-2)
The record opens at the line: “M. Osei walked through OP-118 rev 6 load shed blocks with Y. Karim. No issues.” The margin notes say why it fails: an event, not an assessment; the initials “MO” are the operator's own, so Yusuf Karim did not sign as verifier. Name and date are present, after the 14 May change.
“The records reader checks the fields M2 asks for. Hannah Lindqvist decides what counts; changing a verdict needs a reason and is on the audit trail.”
Hannah books Malik on SIM-2026-33, Wed 28 Oct, 07:30–16:00 on the Harrow Ridge simulator with the rest of crew D: assessor Colm Brennan, verifier Yusuf Karim. The other choice on screen is a supervisor check sheet on shift on Thu 15 Oct. Malik and Yusuf are told by email and in the roster system.
“The booking is on the audit trail.”
Malik's page shows 52 of 54 tasks verified, 0 gaps and 2 inside the window, and 24 of 32 hours of emergency operations training this year. His training history shows why: he was on annual leave for SIM-2026-24 in August, and the OP-118 rev 6 classroom briefing counts for delivery only.
“Task 42 booked … It stays amber until the signed record is filed.”
The binder builder matches RFI-07 to R2 and R2.1, collects 38 operator records for task 42, checks each against M2 and adds the dated task list v14 with change record MOC-2026-07. It writes the response narrative and bookmarks every page at the line naming the operator, task and verifier. The four open verifications are in the binder on pages 39–42, each with its booking.
“Open items are disclosed with their dates, never left out.”
Hannah sends the binder to Marcus with a note: 34 verified; Ethan, Priya, Liam and Malik are on SIM-2026-33 on 28 Oct, before the 14 Nov window closes. Marcus reviews it, and only he can release it to Granite Plains Reliability Council. RFI-07 is due Fri 23 Oct.
“Nothing leaves Lumina until Marcus Adeyemi releases it.”
Line L-3417 Harrow Ridge–Ashby 345 kV comes out at 22:30 under switching order SO-26-1184, on Grace Whitfield's desk — and her task 19 check sheet is unsigned. The coverage checker suggests Hugo Lindahl, verified on task 19 (CS-2024-1765), takes the switching order and Grace monitors Transmission South. Tomás decides.
“The agent advises; Tomás Reyes decides who works which desk.”
OP-131 rev 2, on voltage collapse actions, was published on 6 Oct. The task list keeper shows the difference: operators now act on a second trigger, within 5 minutes. If Hannah treats it as a modification to task 45, all 38 operators must be re-verified by 6 Apr 2027; rewording alone is not a modification.
“The agent proposes; the training manager decides.”
The same audit request, seen by the four people it touches — what their month looked like, and what it looks like now.
Five agents read every training record into its cell and build the audit binder; the training manager decides what counts.
Reads every training record — learning-system exports, simulator assessments, scanned check sheets, sign-in sheets and logs — and files it to operator and task with the fields M2 asks for: operator, date, task, procedure revision, method, result and verifier, each with the line it came from.
Compares new procedure revisions and event reviews with the task list, shows what the operator does before and after, and proposes new or modified tasks; it opens the six-month window once the training manager agrees.
Re-scores all 1,867 cells nightly and on every new record, checks each crew against the tasks its desks perform, and sends reminders before a window closes.
Answers an audit request with a binder in the audit worksheet's order: response narrative, dated task list and change record, and every record bookmarked to the page and line.
Drafts the annual programme evaluation from course evaluations, instructor observations, supervisor feedback, simulator sessions, event reviews and the year's gaps, with the changes they lead to.
Decides what counts as evidence; the compliance lead alone releases to the auditor. The agents propose; a named person decides.
Ask in plain words about an operator, a task or an audit request — or say what to change. Every answer points to its records.
Who can’t show valid evidence for task 42?
One operator: Malik Osei, crew D. His only record is a shift log entry of 11 Sep — it records a walk-through, with no criteria, result or verifier, so it fails M2. Three more in crew D are booked on SIM-2026-33 on 28 Oct, before the window closes on 14 Nov. The other 34 hold simulator assessments from May to September.
Is tonight’s crew C verified for every desk task?
Not yet. Grace Whitfield is on Transmission South, where line L-3417 (345 kV) comes out at 22:30, and her task 19 check sheet has no verifier signature. Hugo Lindahl is verified on task 19, so I suggest he takes SO-26-1184. Four of the crew are inside the window on new task 63, which is allowed until 2 Jan.
What changed in the task list this year?
Three changes in 2026: task 42 modified on 14 May (OP-118 rev 6, 34 of 38 verified), task 63 added on 2 Jul (ride-through alarms, 9 of 23), and task 27 modified on 3 Sep (Corran Vale bus, 17 of 23). One more is waiting for your decision: OP-131 rev 2 looks like a modification to task 45. If you agree, 38 operators must be re-verified by 6 Apr 2027.
Build the evidence binder for RFI-07
Building it now: every task 42 record checked against M2, the dated task list and change record MOC-2026-07, the response narrative, and the open items disclosed with their dates. Nothing goes to Granite Plains until Marcus Adeyemi releases it.
13 screens from the working solution, on its sample data. Pick one to see it large.
What counts as evidence, the clocks and who decides are settings, chosen by the training manager.
| Setting | Default | Choose from |
|---|---|---|
| What counts as a capability verification | Three kinds | Supervisor check sheet signed by a qualified verifier · simulator assessment with assessor and result · learning assessment at or above the pass mark |
| Pass mark | 80 % | 70 % to 95 %, in steps of 5 · applies to new assessments |
| E-1 · Attendance or sign-in sheet counts for delivery only | On | On · Off — when on, never counted as capability (R1.3, not R2) |
| E-2 · A shift log entry is not a verification on its own | On | On · Off — when on, flags it red with the reason |
| E-3 · An unsigned check sheet does not count | On | On · Off — when on, sends it to the verifier to sign |
| Verify within six months of a new or modified task | 6 months | Fixed by PER-005-2 R2.1 · cannot be changed |
| Re-verify every task every 36 months | On | On · Off — a company rule, stricter than “at least once” |
| Remind the shift supervisor before a window closes | 60 and 14 days | On · Off |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample control-centre data · “target” = the design goal, measured in the pilot · “estimated” = our estimate (the working-days split for one audit request) · “typical” = published figures, from NERC PER-005-1's severity table (for R2, 90 % to under 100 % of operators verified is a Moderate violation, 70 % to under 90 % High; missing the six-month window after a task change is High). Requirements named as context: NERC PER-005-2 and its draft audit worksheet (RSAW; M2: records with the employee name, date and task). The WECC case in which daily operator logs were rejected is from a published law-firm summary of NERC case notes. Lumina Utilities, Granite Plains Reliability Council and the people, sites, procedures and records named on this page are fictional — characters and sample data in the working solution.
Software that shows, for every system operator and every real-time reliability-related task they perform, a dated record that they were verified as capable — and finds the gaps. Operator Training Compliance puts it on one grid, with agents that read each training record into its cell, check tonight's crew and build the evidence binder an audit request asks for.
The records reader files every record from the learning system, simulator, check sheets, sign-in sheets and logs to its operator and task, and applies your evidence rules. The coverage checker re-scores every cell overnight and on each new record. When an auditor asks, the binder builder assembles the response; the training manager decides what counts and the compliance lead releases it.
It is built around PER-005-2's requirements: the company-specific task list reviewed each year (R1.1), capability verification on each assigned task and within six months of a change (R2, R2.1), emergency simulation training (R3) and the annual programme evaluation (R1.4). Compliance stays your programme's and your people's; the solution shows the evidence and the gaps.
A sign-in sheet shows training was delivered, not that the operator can do the task, so it counts under R1.3 but not R2. A shift log entry says an event happened, not that a verifier assessed the operator. The solution marks both red with the reason and books a real verification.
For RFI-07 the binder builder matched the request to R2 and R2.1, collected all 38 operator records for task 42, checked each against M2, added the dated task list and change record, wrote the response narrative and bookmarked 46 pages to the line. Open items are disclosed with their bookings, never left out.
Yes. The coverage checker lays the roster over the grid and checks each desk against the tasks it performs tonight. When Grace Whitfield's task 19 check sheet was unsigned before a 345 kV line outage on her desk, it suggested Hugo Lindahl take the switching order. The shift supervisor decides.
Yes. The training manager owns the evidence rules, the task list and the annual review; shift supervisors sign check sheets and decide desks; only the compliance lead releases anything to the auditor. Agents propose and draft; the coverage checker never changes a record, and the binder builder never leaves out an open item.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your task list and the method behind it, positions, evidence rules and a sample of training records — and it goes live once every quality gate has passed. We will walk you through it on your own operators first.
We'll run Operator Training Compliance on your own task list and a sample of your training records.