A maintenance SOP the technician actually uses

Two technicians replace the same mechanical seal, on the same pump, in different ways. One of them is going to cause rework. A standard operating procedure (SOP) exists so the job comes out right no matter who's assigned, which shift it is or how rushed everyone is.

The problem is that many procedures are written for the audit, not for the technician: ten pages, standards language, kept in a binder nobody opens. A procedure that isn't used changes nothing. This article is about how to write one that gets used.

What the SOP needs

1. Task and equipment: what it is, on which asset or family of assets.
2. When to use it: frequency or situation ("when replacing the seal", "every 2,000 h").
3. Hazards and lockout: which energies to isolate (electrical, pneumatic, hydraulic, thermal), where to lock out and tag out, and how to verify zero energy. Follow the electrical and machine safety rules that apply to your site; the SOP points out which of them apply to the task.
4. PPE.
5. Tools, parts and materials: with part numbers, to stage them before heading out. It saves a second trip to the storeroom.
6. Numbered steps: in order, with the values (torque, clearance, pressure, temperature).
7. Done criteria: the test that says the job is finished.
8. What to record on the work order: measurements, parts replaced, what was found.

How to write a step

• One step, one action. "Loosen the 4 cover bolts" instead of "remove the cover and check the condition of the impeller and seals".
• Start with the verb: measure, tighten, clean, check.
• A number instead of an adjective. "Tighten well" becomes "tighten to 45 N·m in a cross pattern". "Proper clearance" becomes "clearance of 0.10 to 0.15 mm".
• A photo wherever there's doubt: the position of the alignment mark, the direction of the seal, the lockout point.
• Highlight what's critical: the step that, if skipped, hurts someone or damages the equipment.
• Does it fit on a phone screen? If it doesn't fit on one or two pages, split it into more than one procedure.

Short example: replacing electric motor bearings

1. Mark the position of the end shields and the coupling before taking them apart.
2. Remove the coupling with a puller. Don't hammer on the shaft.
3. Remove the bearings with a bearing puller, pulling on the inner ring.
4. Measure the shaft seat at two points 90° apart. Out of tolerance: stop and report it.
5. Heat the new bearing on the induction heater to no more than 110 °C. Don't use a torch.
6. Mount it against the shaft shoulder; hold it until it cools enough not to slide.
7. Add the specified amount of grease (in grams) and close the end shields on the marks.
8. Refit the coupling and align with a dial indicator: maximum deviation as given in the assembly's table.
9. Remove the lockout according to the procedure and run for 30 minutes.

Done when: bearing housing temperature is stable, there's no abnormal noise and vibration is within the equipment's limit. Record on the work order: shaft measurements, alignment values, bearing part numbers, photo and condition of the removed bearings.

How to roll it out without drowning in paperwork

1. Start with what causes rework. Look at reopened work orders and failures that come back. The first procedures should cover those tasks, not all of them.
2. Write it with whoever does it best. The most experienced technician on the task dictates; someone else puts it in the format.
3. Test it with someone who's never done it. If a new technician can carry out the job with only the procedure, it's good.
4. Keep it where the work happens. The procedure should be attached to the work order, on the technician's phone, not in a binder in the office.
5. Review it when something changes: a new part, modified equipment, a failure that happened even though the steps were followed. At least one review a year.

A good procedure cuts rework, shortens training for new hires and protects the know-how of people about to retire. It's also the action that closes many recurring failure analyses: when the latent cause is "everyone does it their own way", the fix is a procedure.

In taskfield, the procedure becomes a checklist inside the work order: the technician checks off each step, fills in the measured values and attaches photos, even with no signal. What was measured stays in the asset history.