Orchestrate

The motor that left without an order

Break-fix drill · Procurement · about 8 minutes · starts after stage 11 of 11, "Pay and close the month", and the Maintenance chapter up to "Order the repair" in "Repair the hoist motor" (hoist motor HM-1 10000111 out of the crane unserviceable, its repair order released with the rewind CP-SV-HM10R bought for it from Orrin at 1,180.00, the requisition not yet converted)

What the user reports

Monday at Rockford. Orrin's driver came for hoist motor HM-1 while the rewind's requisition was still waiting in the buyer's list, so the technician let the motor go and marked it In repair by hand. Today the motor is back on the dock, rewound, with Orrin's report and an invoice for 1,180.00 that quotes no purchase order. The technician goes to take HM-1 back into the pool. It is refused.

The error: Back from repair refused on 10000111: it is marked in repair by hand, on no purchase order: nothing records where it went, what the repair costs or which order pays.

What you'll do

  1. See the problem as the maintenance technician: On Equipment, under Repairable units, take 10000111 back from repair with Orrin's report: Orrin's report: stator winding burnt by overheating from repeated inching under near-full load; rewound, both bearings replaced, insulation and load tested.
  2. Find the cause: The motor is physically back and rewound. Why won't the lab take it back into the pool?
  3. Fix it as the buyer.
  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: HM-1 went on no purchase order: the requisition was never converted, so nothing ties the motor to the order, the price or the promised date; the buyer converts it, the motor is recorded as sent on it and the repair is received, then it comes back.

A unit in repair is tied to its repair by the purchase order: it says what Orrin does, at what price, by when, and which maintenance order pays. Marking the status by hand skipped all of that, so there is nothing to receive the repair on and nothing to put Orrin's 1,180.00 on the order. Setting it serviceable by hand would hide the repair from HM-1's history and leave the invoice with no order to match. The invoice comes after the receipt, and the crane already has HM-2.

Why it broke

The motor moved faster than the paper. The repair was planned properly on HM-1's order, but the requisition sat unconverted when Orrin's driver arrived, and the technician let the motor go and wrote the status by hand. A hand-set status says nothing about where the unit is, what the repair costs or when it is due, so the lab has no repair to receive and no order to put Orrin's price on.

How teams prevent it

No repairable unit leaves the plant without the purchase order it travels on: the shipping paper names it, and the driver waits or comes back. The buyer works requisitions charged to maintenance orders on repairable units first, because an unconverted one means a machine without cover. In repair is set by Send for repair, not by hand.

Across teams

The planner raised the order, the buyer owns the requisition and the agreement with Orrin, the technician hands the motor over, the warehouse receives the repair, and accounts payable is holding an invoice it can't match. One missing step in purchasing stopped all of them.

Where AI fits

A rule is enough to catch this: list units marked in repair with no purchase order, and requisitions for repairs older than a day. A model could read Orrin's invoice and propose which open repair order it belongs to, citing the unit's serial number from the report, for the buyer to confirm; it doesn't create purchase orders after the fact on its own.

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