← Back to turbine-7 case
turbine-7 · deliverable

Action Map — Turbine 7

Kit 9 · Turbine 7 · deliverable · designed and built by I Wayan Usada · fictional case

The goal

In this fictional brief: no restart into a rising trend or a recurring fault without an inspection, while healthy turbines still go back to service quickly. The proposed audit measure is the share of post-alarm restarts whose handover note names the deciding pattern (see the evaluation plan on the case page; nothing has been measured).

What people do instead

Technicians know every alarm threshold. When the production desk argues for megawatts and the data is ambiguous, the restart happens anyway. The discipline fails, not the knowledge.

The actions that close the gap

#BehaviourWhat it looks like on shiftWhere the build practises it
1Open the evidence before calling ittrend, inspection record and reset history checked; sister turbines compared2D and 3D: the call stays locked until the part holding the deciding evidence is opened
2Name the patterncleared-with-inspection / rising-no-inspection / recurrence-after-reset / external-causepattern question after every call, scored separately
3Hold rising trends and recurrences regardless of production costhold + inspection request loggedcases 092, 098 (rising) and 094, 105 (recurrence); restart is a critical error
4Restart healthy turbines without hesitationrestart with a watch item in the handovercases 087, 079 (cleared) and 101, 110 (external); holding or escalating costs production and scores 0
5Defend the safe call with the number, the risk and the next stepreply to the production desk; the handover notepushback on the rising and recurrence cases; handover note at the end of every shift (rubric)

What this training will not do

It will not re-teach alarm thresholds, and it cannot fix how alarms are displayed or how the production desk is measured. Those are recommended separately on the case page (trend on the alarm card; an agreed escalation boundary; production incentives flagged to operations).

How the build scores the actions

Call 2 / 1 / 0, pattern 1, pushback reply 1; 14 maximum per shift (four cases, one per pattern, from a bank of eight); pass = 12 or more and no critical error. The handover note is scored 0–6 against its rubric and is formative.

Prefer the source? Download the raw markdown.