Orchestrate

The order released before the rule

Break-fix drill · Production · about 6 minutes · starts after stage 11 of 11, "Pay and close the month", and the Maintenance chapter through "Plan the overhaul" and the Environment, health and safety chapter up to "Ask for a lockout permit on the bench" in "Permit to work" (permit types LOTO and HOT set up; the test bench area's assessment approved with LOTO for maintenance work on 10000101 at 09:00, after the drill's order was released)

What the user reports

Monday at Rockford. At 07:30 the maintenance planner released an order to replace the flow meter's sensor on test bench TB-1; the meter reads 4% low. At 09:00 the safety manager approved the bench's reviewed risk assessment, which now asks for a lockout permit for maintenance work on the bench. At 10:00 the technician has the new sensor in his hand and the order says released, so he goes to book his hour and a half on it. The confirmation is refused.

The error: Confirmation refused on the flow meter's order: the order is on 10000102, and the test bench area's risk assessment asks for a LOTO permit for maintenance work on it: confirming work on it needs an issued permit.

What you'll do

  1. See the problem as the maintenance technician: On Maintenance orders, confirm operation 0010 on the flow meter's order (equipment 10000102) with 1.5 h.
  2. Find the cause: The order was released this morning without any complaint. Why is its confirmation refused now?
  3. Fix it as the maintenance planner.
  4. Prove it: run the step that failed again.

Start the drill

The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.

Answer and explanation (open after the drill)

The fix: The release checked the permit rule before 09:00, when no assessment asked for one; the assessment approved since asks for LOTO on the bench and everything installed in it, so the work itself now waits for an issued permit valid today.

A rule only acts where it is checked. The release at 07:30 came before the requirement existed, so the order went out without a permit. That is why the lab checks again when work is confirmed: the meter sits inside the bench, the assessment asks for LOTO on the bench, and nobody may open its pressurized circuit without the isolations written, checked and issued. Releasing again changes nothing, the order itself needs no approval, and TB-OPS is asked for at the production work center TEST1, not for maintenance work.

Why it broke

Two right steps landed in the wrong order. The planner released the job at 07:30 under the rules of 07:30; the safety manager tightened the rules at 09:00. Nothing reached back to the orders already out, so a released order sat on a machine that now needs a lockout permit, and only the confirmation caught it.

How teams prevent it

When an assessment starts asking for a permit, look at Permits to work the same morning: it lists every open order on the machine and anything installed in it, with what each is missing. Request the permits for the released ones before the technicians pick them up, and tell the planners what changed.

Across teams

The safety manager owns the assessment and issues the permit, the planner released the order and requests the permit, the technician does the work, and production waits for its flow meter. The bench is one machine, and the rule belongs to all of them.

Where AI fits

When an assessment's new revision is approved, plain automation can list the released orders it now stops, and a model can draft each permit's isolations from the machine's earlier permits, citing them, for the planner to edit. Issuing the permit and checking it on the machine stay with people; the check at confirmation stays a rule.

Learn more: Maintain to settle: plant maintenance and assets

All drills · Back to the lab

Sign in to track your progress

We'll email you a one-time sign-in link. No password needed.

or

Tell us a little about you

Optional, every field. It helps us pitch answers to your questions at the right level and decide which topics to write next. It is never shown publicly, and you can change or clear it anytime from the account menu.

SAP areas you work in