15. Example Exercise Reports¶
End exercise and score produces a Markdown report: the score, each objective with its result, counts of what happened, and the full timeline. This page shows real reports from the two-stage separation plant, so an instructor knows what to expect and a trainee can see how a score is built.
What is here
- Two reports of the same scenario: nobody at the panel, and an operator who acted in time
- How to read the objective lines and the timeline
- Where the report is saved and how to keep records
The scenario¶
3. Gas blow-by on ots_two_stage_separation.dwxmz: the level transmitter LT-100 fails high at 01:30, LIC-100 believes the separator is full and opens LV-100 wide, the true level falls, and unless someone catches it the low level trip closes LV-100 at 06:40. Four objectives: no HH pressure in V-200 (25 points), no low level trip (15), take LIC-100 to manual within 7 minutes (10), and keep the true level between 0.7 and 1.8 m for 70 % of the time (20). 70 points in all.
Both reports below were produced with the batch script of page 16, which runs the session exactly as the Instructor Station does; the second one lets a scripted operator take LIC-100 to manual at 20 % four minutes in and hold it at 50 % once the level is back.
Report 1: nobody at the panel¶
examples/reports/gas-blow-by-no-operator.md
The head of the report:
# Operator training exercise report
- Scenario: 3. Gas blow-by
- Simulated duration: 00:40:00 (480 steps)
- Score: **25 / 70** (36%)
| Objective | What | Result | Points | Detail |
|---|---|---|---:|---|
| No HH pressure in V-200 | avoid PIT-200 HH alarm | Passed | 25 / 25 | never happened |
| No low level trip | avoid interlock 'V-100 low level trip' tripped | Failed | 0 / 15 | interlock 'V-100 low level trip' tripped happened at 00:06:30 |
| Take LIC-100 to manual | operator does 'LIC-100 mode -> MANUAL' within 420 s | Failed | 0 / 10 | no matching action before 00:07:00 |
| Hold the HP level | keep LIT-100.Monitored Value in [0.7, 1.8] for 70% of the time | Failed | 0 / 20 | 27.1% of the time inside the range (required 70%), 20 points lost |
Read it like this:
- The trip did the operator's job: it closed LV-100, so the LP separator never saw the blow-by and the first objective passed by luck. The second objective is the one that says what happened.
- The level objective failed twice over: first the level fell out of range, then, with LV-100 closed by the trip and nobody resetting it, the separator filled up to HH. Twenty-seven percent of the time inside the range is the number that tells that story.
- The timeline shows the LL alarm 100 seconds after the L alarm and the trip five seconds after LL. In the debriefing, that is the number to discuss.
Report 2: the operator acts at 04:00¶
examples/reports/gas-blow-by-operator.md
- Score: **70 / 70** (100%)
| Objective | What | Result | Points | Detail |
|---|---|---|---:|---|
| No HH pressure in V-200 | avoid PIT-200 HH alarm | Passed | 25 / 25 | never happened |
| No low level trip | avoid interlock 'V-100 low level trip' tripped | Passed | 15 / 15 | never happened |
| Take LIC-100 to manual | operator does 'LIC-100 mode -> MANUAL' within 420 s | Passed | 10 / 10 | 'LIC-100 mode -> MANUAL' at 00:04:00 |
| Hold the HP level | keep LIT-100.Monitored Value in [0.7, 1.8] for 70% of the time | Passed | 20 / 20 | 100% of the time inside the range (required 70%) |
The operator took LIC-100 to manual at 20 % before the L alarm, the level stopped falling and recovered, and at 10:00 the output went to 50 % to hold it. The timeline has the three operator lines (LIC-100 mode -> MANUAL, LIC-100 manual output -> 20, LIC-100 manual output -> 50) between the malfunction line and the end, which is the sequence you want to see from a trainee.
What the rest of the report holds¶
After the objectives table:
- Counts: operator actions, alarms raised, interlock trips, faults injected, failed steps. A high count of operator actions with a low score is a trainee who reacted without a plan; zero failed steps is the plant behaving.
- Timeline: every journal line with its simulated time, in order. It is the same list as the Journal tab, so the report stands on its own after the session is closed.
Keeping records¶
- One folder per trainee, one file per session, named by date and scenario:
2026-09-19_gas-blow-by.md. - The report is Markdown: it opens in any editor, renders in the browser, and pastes into a course management system.
- Export the journal as CSV when the course needs the timeline in a spreadsheet; the report already has it as text.
The next page automates all of this.