Kit 9 · Turbine 7 · job aid for the control-room wall · one page, prints on A4 · fictional case, illustrative figures
Before any restart after an alarm, name the pattern and the evidence that puts it there. If you cannot name it, hold or escalate.
| Pattern | What you see | Where the evidence is | Call |
|---|---|---|---|
| Cleared with a logged inspection | Reading back inside the band and settling; someone was up-tower and wrote it down | Inspection card or work order on the part; the maintenance log | Restart. Hand over a watch item |
| External cause, turbine nominal | Trip from the grid or the weather; every turbine reading normal | Trip record; the sister turbines on the same feeder; the met mast | Restart. Nothing on the turbine needs a look |
| Rising trend, no inspection yet | The value is still climbing over the last 20 minutes; nobody has looked | The 20-minute trend, not the alarm text | Hold for inspection. Restarting or derating is the critical error |
| Fault came back after a reset | The same fault, reset once, back again | Reset history on the component log | Hold for inspection. A reset silenced it; it did not fix it |
Give the number, the risk and the next step, in that order:
"Vibration is 4.8 mm/s against a 2.0 baseline and still climbing. If the gearbox goes, that is a jack-up vessel and weeks, not a night. The inspection is booked for first light."
Not the rulebook ("policy says no"), and never "I'll restart and keep an eye on it".
The call, the reading or log entry that decided it (with its number or time), and what happens next (who, when).
Figures are illustrative. This card summarises the patterns practised in the Turbine 7 simulator; it does not replace the OEM's alarm procedures or your site's escalation boundary.
Prefer the source? Download the raw markdown.