Run an investigation with Machine Doctor

Describe the problem, let InduQT read the machine’s data, manuals and history, then add evidence until the cause is confirmed.

Training video
A low-water investigation on a boiler: diagnose, add a photo and a measurement, diagnose again, confirm.

Start an investigation

  1. Open Machine Doctor and click New investigation (or Investigate on a machine page).
  2. Choose the machine. InduQT loads what it will analyse: the last two hours of readings, alarms from the last seven days, earlier investigations and their files.
  3. Describe the symptom in plain words: what happened, when, any codes on the display. You can add photos, a trend screenshot, a CSV or a PDF now or later.
  4. Click Start investigation, then Diagnose.
New investigation form
The machine’s readings, alarms and history loaded for the analysis
The symptom described in plain words

Read the diagnosis

While it works you see each step: connected data, your evidence, the search of the knowledge base, your manuals and work orders and your team’s confirmed fixes, then the reasoning.

The summary gives the likely cause, confidence, key evidence with times, first actions and the next best check. Top hypotheses ranks the alternatives. Causes and checks taken from your manual cite the file and page.

Diagnosis steps as they run
Likely cause, key evidence and first actions

Check the manual

The Manual tab lists the machine’s manuals with the pages the diagnosis cited. Click a page to open it beside the list.

The machine manual open at the cited pages

Add evidence and diagnose again

Add what you find: a photo of the alarm screen, a measurement, a data export. Photos are read straight away and alarm codes appear for you to confirm.

Add a technician note for checks you made (for example “strainer dP 8.5 psid”). Then click Diagnose again: the summary and first actions update to the new evidence.

An HMI photo read as F21 LOW WATER and a technician note
The updated diagnosis after the new evidence

Confirm and close

When the fix is done, confirm the cause under Teach the engine. The case is marked confirmed, the confidence shows 100 and the fix becomes part of your team’s history for future investigations.

Use ⋯ for the report, sharing and the full replay.