Solve cross-functional problems without turning them into turf battles.
What to understand
Maintenance owns equipment condition, but many faults sit at the boundary between equipment, process, material, operation, and design. Collaboration is often faster than proving whose department is “responsible.”
Start by turning the idea into an observable question. What should the machine, component, person, or process be doing at this moment, and what evidence would prove that it is doing it? Defining normal first gives your troubleshooting a reference point and prevents you from reacting to the first unusual thing you notice.
How to apply it
When the equipment is functioning as designed but the process result is wrong, document what you verified and involve the correct owner.
Apply the idea one boundary at a time. Confirm one condition, record what you learned, and only then move to the next point in the chain. This makes your work easier to explain and greatly reduces the temptation to swap parts or change several variables at once.
What good work looks like
Engineering changes need controlled documentation. A clever field modification becomes tomorrow’s mystery if drawings, software, parts, and standards are not updated.
Good maintenance work leaves a trail of evidence. Measurements, alarm times, verified states, photos where permitted, and clear work-order notes let another technician understand why you made the repair and whether the same failure mechanism returns later.
Field scenario
A vision system rejects more product after a lighting change. Maintenance verifies camera trigger, network connection, and image capture. Quality confirms the product is acceptable. Engineering then adjusts the validated inspection parameters through the approved change process. Each group contributes evidence instead of passing the problem around.
After the immediate repair, capture the point in the sequence where the expected condition was lost and what evidence proved the cause. That small discipline turns a one-time fix into knowledge the whole maintenance team can reuse.
Field checklist
Common mistakes to avoid
Using maintenance as a dumping ground for process issues
Changing controlled parameters informally
Making undocumented wiring changes
Treating cross-functional disagreement as personal conflict
Ask yourself: If this machine failed again on the next shift, what information could I leave behind that would make the next diagnosis faster and safer?
90-day action
Before moving on, choose one task from this chapter and perform it during normal work. Record what you learned in your plant notebook. The value of the first 90 days comes from turning concepts into repeatable behavior, not from reading alone.
CHAPTER 25