Documentation written the next morning is often missing the detail that would make it valuable. Capture facts during the breakdown, then convert them into a clean maintenance record after restart.
Five Principles to Use in the Field
- Record timestamps. When the fault occurred, when tests were made, when parts were replaced, and when production resumed can reveal sequence and recurrence.
- Record measurements, not adjectives. “Voltage low” is weaker than “24 V supply measured 18.6 V under coil load.”
- Record failed and passed tests. Knowing what was proven healthy prevents future technicians from repeating the same work.
- Record configuration changes. Parameters, software edits, forces, temporary wiring, calibration values, and replacement device settings must be traceable.
- Write the root cause as a mechanism. “Sensor failed” is vague. “Sensor cable conductor fractured inside drag chain, causing intermittent loss of input during axis travel” is reusable knowledge.
Pressure Mistakes to Avoid
- Documenting only the replaced part.
- Omitting measurements because the repair “was obvious.”
- Forgetting temporary settings after the machine restarts.
- Writing a long narrative with no clear cause or action.
A Practical Breakdown Method
- Keep a rough timeline during diagnosis.
- Note significant measurements and alarm codes.
- List any changes made.
- After restart, write a concise cause-correction-verification summary.
- Create follow-up tasks for unresolved contributing factors.
- Update drawings or knowledge base where required.
Scenario: A filler restarts after tightening a terminal. A weak note would say “tightened wire.” A useful note says: “03:41 intermittent loss of 24 V at valve bank; measured 24.2 V no load and 10.7 V during actuation; found loose 0 V terminal X14-6 with heat discoloration; replaced ferrule and retorqued terminal; verified 50 cycles and 23.9-24.1 V under load.” The second note can prevent future downtime.
Train This Before the Next Callout
Choose one critical machine you know and apply the ideas from this chapter while it is healthy. For document while the breakdown is still fresh, write down the normal sequence, the key evidence you would want to preserve, and the first three checks you would make if the machine stopped. Then compare your plan with the electrical drawings, PLC diagnostics, maintenance history, and the experience of another technician. A ten-minute rehearsal in daylight can remove several minutes of confusion at night.
3 AM Rule: Document enough that another technician can understand the failure mechanism without calling you.
Chapter Checklist
- Can I describe the symptom without naming an unproven cause?
- Have I preserved the evidence that could disappear after a reset or restart?
- Do I know which system boundary I am testing next and why?
- Have I kept safety controls and temporary changes visible and controlled?
- Can I explain my current facts, hypothesis, and next action in under thirty seconds?