Use case: Troubleshooting

Reduce machine downtime with guided troubleshooting

findIQ guides technicians and operators from symptom to root cause, right at the machine. Each step is calculated from your experts’ knowledge, so every shift fixes faults the way your best technician would.

findIQ Service Guide: troubleshooting a fault step by step, with the next check, likely causes and confirmation

Trusted by manufacturers and machine builders

  • Phoenix Contact
  • Siemens
  • Kulicke & Soffa
  • Holmer
  • Clarios
  • enercity

In short

Guided troubleshooting at a glance

  • Guided troubleshooting turns expert knowledge into a step-by-step diagnosis path that any technician can follow at the machine.
  • findIQ calculates each step from a structured model of your experts’ knowledge, so the same fault leads to the same validated answer every time.
  • Technicians get from fault to fix in about 6 clicks. A knowledge base for one machine type takes about 4 hours to build.
  • In a field test at an energy company, troubleshooting time dropped from 40 to 10 minutes.
  • Every confirmed fix flows back into the knowledge base, so the guidance improves after about 10 uses.
  • 40 → 10

    minutes of troubleshooting time

    Field test, service department of an energy company

  • 50%

    of machine faults solved by operators

    Siemens Bad Neustadt

  • up to 96%

    shorter diagnosis time in individual cases

    Kulicke & Soffa

  • 6 clicks

    from fault to fix

    findIQ customer data

The problem

Why does troubleshooting take so long?

Most of the time is not spent on the repair itself. It is spent finding the cause: waiting for the right expert, searching manuals and testing parts by trial and error.

  • Knowledge sits with a few experts

    When a fault is new to the shift, technicians wait for the one colleague who has seen it before.

  • Manuals describe the machine, not the fault

    Documents explain how a machine should run. They rarely show the path from a symptom to its cause.

  • Trial and error costs uptime

    Without a proven path, technicians swap parts and repeat checks while the line stands still.

How it works

How does guided troubleshooting work?

findIQ turns your experts’ knowledge into a model of causes and checks. At the machine, it asks for the next most useful check until the cause is clear.

  1. 01

    Capture

    Manuals, service tickets and guided interviews with your experts become a structured knowledge base. About 4 hours per machine type.

  2. 02

    Diagnose

    The technician starts from the symptom they see. findIQ asks for the next most useful check and narrows down the cause, about 6 clicks from fault to fix.

  3. 03

    Fix

    Step-by-step instructions with photos and context lead to the solution. The technician confirms what solved the problem.

  4. 04

    Improve

    Confirmed fixes flow back into the knowledge base, reviewed by an editor before they go live. After about 10 uses the guidance gets sharper.

Every fix makes the next one faster.

The feedback loop is what sets findIQ apart: knowledge from the field returns to the model instead of staying in one technician’s head.

Book a demo →

At the machine

What technicians get at the machine

  • Calculated, not guessed

    findIQ reasons from symptom to cause with a structured model. The same fault leads to the same validated path, every time.

  • Transparent decisions

    Every recommendation shows which symptoms and checks led to it, so technicians can follow and verify the result.

  • Works offline

    The click-based diagnosis also runs without a connection, on smartphones and tablets.

  • In the technician’s language

    The whole app is multilingual, so teams across sites follow the same path.

  • Hands-free with Quinn

    Technicians describe the problem by voice and get the next step read out at the machine.

  • Recurring faults made visible

    The Insights Panel shows which faults come back and how long they take, so the root cause can be fixed for good.

findIQ Service Guide: troubleshooting a fault step by step, with the next check, likely causes and confirmation
Service Guide: next check, likely causes and confirmation in one view

Compared

Guided troubleshooting compared with other approaches

Every approach finds the cause eventually. The difference is how long it takes, and whether the next technician can repeat it.

findIQGuided troubleshootingTrial and errorManuals and document searchDocuments plus a language model
Path from symptom to causeCalculated step by stepDepends on the personNot includedVaries between sessions
Same fault, same answer✓ YesNoYes, if foundNo
Shows how the answer was reached✓ YesNoPartlyNo
Works offline at the machine✓ Yes, click-based diagnosisYesPartlyNo
Learns from every fix✓ Yes, reviewed by an editorNoNoNo

Customers

Faster diagnosis in real production

Eugen Edelmann, Head of Technology & Service at Siemens Bad Neustadt

50%of machine faults solved by operators

“I’ve never seen a faster, more systematic approach to building globally scalable knowledge systems.”

Eugen Edelmann

Head of Technology & Service, Siemens Bad Neustadt

From a one-day workshop for two machines to a six-month pilot and a global rollout: today, operators diagnose and fix half of all machine faults themselves.

More customers

  • Phoenix Contact
  • Kulicke & Soffa
  • Holmer
  • Clarios
  • enercity

Who it is for

Who uses guided troubleshooting

  • Maintenance technicians

    Solve unfamiliar faults without waiting for the expert on the next shift.

  • Machine operators

    Fix routine faults themselves before they turn into a call for maintenance.

  • Service technicians at machine builders

    Arrive with the right diagnosis and fix the fault on the first visit.

  • First-level support

    Guide customers through the diagnosis instead of escalating every case.

Fits your operation

Start without IT project or machine connection

  • No machine connection needed

    findIQ starts from your experts’ knowledge and documents.

  • Mobile and offline

    Smartphones and tablets, click-based diagnosis without a connection.

  • EU data residency

    Hosted in the EU. Your knowledge stays yours.

  • Human in the loop

    Changes to the knowledge base are reviewed before they go live.

FAQ

Questions about guided troubleshooting

What is guided troubleshooting?

Guided troubleshooting leads a technician from a symptom to the root cause with a fixed sequence of checks, instead of trial and error. findIQ builds that sequence from your experts’ knowledge and calculates the next most useful check at every step, so less experienced staff reach the same fix as your best technician.

How can guided troubleshooting reduce machine downtime?

Most downtime during a fault goes into finding the cause, not into the repair. Guided troubleshooting shortens that search. In a field test in the service department of an energy company, troubleshooting time dropped from 40 to 10 minutes. Kulicke & Soffa reduced diagnosis time by up to 96% in individual cases.

How does findIQ find the root cause of a machine fault?

findIQ works with a structured model of causes, symptoms and checks built from your experts’ knowledge. It asks the technician for the observation that narrows down the cause most, then the next one, until the cause is clear. The result is deterministic: the same fault leads to the same validated answer, and the path to it stays visible.

Can machine operators fix faults themselves?

Yes, for many routine faults. At Siemens Bad Neustadt, 50% of machine faults can now be diagnosed and fixed directly by the operator. Complex cases still go to maintenance, but they arrive with the diagnosis already done.

Does findIQ work offline at the machine?

Yes. The click-based diagnosis runs offline on smartphones and tablets, so technicians have guidance in areas without reliable connectivity. Voice features with Quinn need a connection.

Do we need to connect our machines or PLC data?

No. findIQ starts from your experts’ knowledge, manuals and service records. No machine connection is required to begin troubleshooting with findIQ.

How long does it take to get started?

About four hours to build a usable knowledge base for one machine type. You start with one machine and one expert, test it on real faults and expand from there.

More use cases

Start with one machine.

Pick the machine that costs you the most downtime, identify your expert, and see what findIQ builds from it.