Remote diagnosis: knowing what is broken before anyone drives out

The four routes to remote diagnosis

First, telemetry: the machine sends operating and condition data from which the cause can be derived. Second, reading the fault memory, either remotely or by the customer through an app. Third, remote access to the controller, letting a specialist check specifically and sometimes even intervene. Fourth — and frequently underestimated — structured enquiry: a guided dialogue that gets the customer or technician to make the right observations.

The fourth route works without sensors, without connectivity and without any hardware investment. That makes it the only one that also applies to the already installed base — which at most manufacturers is orders of magnitude larger than what ships new and connected.

What it achieves economically

Four effects, in that order of magnitude. Some cases get resolved entirely remotely — no visit, no travel. For the rest, the first-time fix rate rises because the right part and the right skill come along. Spare-parts stock can fall because less is carried on suspicion. And the customer gets a reliable statement on duration and cost instead of waiting for an appointment only to learn a second one is needed.

What it requires

Access to machine data, a clean equipment master with variant and software levels, documented fault knowledge in structured form — and a process that actually passes the diagnosis through to dispatch. The last point fails most often: the diagnosis exists, but it never reaches the person deciding on technician and part.

Data protection and access rights

Remote access to a plant at a customer site is a contractual and security question, not purely a technical one. Clarify it late and you lose months in rollout. Clarify it early and you often get more access than expected — because the operator has their own interest in a faster resolution.