The basic principle.
An investigation begins by describing the symptom accurately: what happened, when, where and under which load or operating conditions. A reported fault code is evidence, not automatically a diagnosis.
The engineer relates the symptom to the system sequence and compares commands, feedback and physical results. Documentation and history help distinguish an isolated event from a repeating pattern.
A lift reports a door fault.
The cause may involve an obstruction, mechanical resistance, a locking condition, signal wiring or control behaviour. Replacing the first named component without evidence can leave the cause unresolved.
Follow the relationship.
- Establish the symptomRecord context and available evidence.
- Investigate the causeRelate signals and behaviour to the design.
- Verify the outcomeCheck the repair and record findings.
Connect it to the lift.
Electrical, mechanical and hydraulic effects interact. The aim is a supported explanation followed by suitable verification, not repeated resets or bypassing a protective condition. Detailed reporting records findings, work completed and follow-up needs.
A closer look
Useful client information includes the time, floor, direction, visible message and whether the issue repeats. Recording observations is helpful; accessing machinery or attempting a reset procedure without authorisation is a different activity.
Check your understanding
Does a fault code naming a component prove that component must be replaced?
Reveal the explanation
No. It can describe an observed condition caused elsewhere in the system.
Further reading.
From principles to practical decisions.
Explore our Advice & guides for support, maintenance and equipment options.