Turn a classified stop into a work order in the same step

A machine stop becomes maintenance work without a phone call when the operator who classifies the stop opens the work order in the same step. The stop already holds the machine, its start time and its duration. The operator adds the reason and a note, so the work order starts from the machine’s own record while the machine is still down, not from somebody’s memory at the end of the shift.

This guide is for maintenance leads and production supervisors who want breakdowns reported from the machine. It covers which stops should become work orders, what each one must carry, who triages them, and how to check that the repair held.

What is a work order from a stop?#

A work order from a stop is a maintenance job opened from a recorded machine stop, at the moment someone puts a reason on it.

A work order is one unit of maintenance work on one machine, as the glossary entry defines it. What changes here is where it starts. Without the link, a stop reaches maintenance by word of mouth: the operator tells a supervisor, who calls or leaves a note, and the start time is whatever somebody remembers.

The gap is measurable. NIST researchers built a list of work order data elements from real maintenance records at several manufacturers. The first timestamp on it is the machine down time-stamp, the date and time the machine goes down.^[1] They call the gap from machine down to the work order being issued the time to issue work order.^[1]

On a phone path, that gap runs from minutes to a whole shift, and the down time is a guess. Opened from the classified stop, the gap is the time the operator took to classify, and the down time is the machine’s own. A night-shift tool crash, reported both ways, shows the difference on one stop.

Which stops should become work orders?#

A stop should become a work order when fixing it needs a maintenance skill or a part, or when it will come back until something on the machine changes. Everything else belongs in the downtime report, not the backlog.

For example, a 40-minute changeover on a CNC lathe needs a setter, not a technician. A work order for it adds a job that somebody has to close for nothing.

The repeat rule is the one most plants miss. One 4-minute jam on a 200-ton press is an operator task. The third in a shift points at a worn guide or a misfeeding coil, and nobody reports it, because each jam alone looked minor.

A short reason list makes this work. Which downtime reason codes to log covers the 8 to 12 codes operators pick from, and which stops a rule should classify instead.

What must the work order carry?#

A work order from a stop must carry five things: the machine, the stop reason, the time the machine went down, how long it has been down, and the operator’s note.

Add a photo when the cause is visible: a leak, a broken guard, a nest of chips around the chuck. Write the title as what is wrong, not what to do. “Coolant pressure low, pump noisy” lets the technician judge urgency, and “Fix lathe” doesn’t.

The down time is the field a phone call loses first, and every repair measure depends on it. NIST’s list runs from machine down through technician arrival, problem found, parts ordered and received, problem solved and machine up, to work order completion.^[1] Each repair metric is the gap between two of them. Time to dispatch, for example, runs from machine down to the technician arriving.^[1]

The same paper notes that work order completion time, from issue to close, is often used to approximate time to repair.^[1] In the figure, the repair took 45 minutes, from 10:02 to 10:47. The work order stayed open 61 minutes, because the technician closed it after cleanup and the close-out note.

Report repair time from the machine’s down and up times. Use the work order’s own dates for the backlog: how much is open, and for how long.

Who triages a work order from a stop?#

One named person triages each shift’s work orders from stops: the maintenance lead or planner on day shift, and the senior technician on call at night. Triage is four decisions, made within minutes of the work order landing: is it maintenance, how urgent is it, who takes it, and does it need parts.

Set urgency from two facts the work order already carries: whether the machine is still down, and how much an hour of that machine’s downtime costs.

Three rules keep triage from becoming a second phone call:

• Assign before you diagnose. A work order with an owner moves; a well-described one with no owner waits.
• Close, don’t delete, what isn’t maintenance. Write why in the note and correct the stop’s reason, so the downtime report stays honest.
• Let operators open work orders. Limiting creation to the maintenance office puts the handoff, and the guessed start time, back in the path.

How do you close the loop?#

You close the loop when the stop reason that opened the work order stops recurring on that machine, and you check that in the downtime data, not in the work order’s status. Done means the technician finished. It doesn’t mean the cause is gone.

The loop has four links:

1. Stop reason. The operator classifies the stop.
2. Work order. It opens in the same step, with the five fields.
3. Repair. The technician fixes the cause and writes what they found in the close-out note.
4. Trend. Somebody reads the same reason on the same machine every week for four weeks.

Each repeat stop fixed at its cause is a breakdown that stops coming back. In a NIST survey of 71 US manufacturing establishments, the half that relied more heavily on preventive and predictive maintenance had 52.7% less unplanned downtime than the half that relied most on reactive repairs.^[2] A loop that turns repeat stops into repairs is how a plant starts moving work from reactive to planned.

When a reason stays high after the repair, take it to the weekly downtime review, which works a reason down to its cause and checks the fix per shift. When the same reason returns after two repairs, the machine needs a different trigger, such as run hours or a condition limit: see how to choose a maintenance strategy.

Open a work order from Classify Downtime#

In IoTFlows, the operator opens the work order from the same Classify Downtime dialog that puts the reason on the stop. A sensor detects the stop in seconds, with no PLC. The operator picks the reason, types the note and clicks Create Maintenance Workorder.

The work order comes prefilled, with the reason as its title, the note as its description and the machine already set. Submit Request, then Classify, and both save from one dialog. The work order lands in the Maintain backlog as Open.

RNPSA, a mining equipment manufacturer in Matehuala, Mexico, works this way. Before, an operator told the shift supervisor, who wrote a note, which the next shift supervisor read before calling maintenance. Now the “operator logs downtime and creates work order in one action,” and RNPSA halved its maintenance response time, as RNPSA’s story describes. See how Maintain works.

Set it up in one week#

1. Mark the maintenance reasons

   Pick the 3 to 6 reasons in your list that always need a technician, such as Tool crash, Hydraulic leak and Electrical fault. Tell every shift that these reasons open a work order.

2. Require a note on each one

   Make the note mandatory on those reasons. Ask for what the operator saw and heard, in one line: “Pump loud, gauge at 0 bar.”

3. Set the repeat threshold

   Agree that the third stop with the same reason on the same machine in one shift opens a work order, whatever the reason.

4. Name the triage owner for each shift

   Write down who triages on days and on nights, and the response window for each priority.

5. Read the reason after every repair

   For four weeks after a work order closes, read its stop reason on that machine each week. If the reason is back, reopen the work order with the next question for the technician.

6. Review closed work orders every month

   Count work orders closed as not maintenance, by reason. A reason with many is mislabeled, or too close to a production reason in the list.