Skip to content
Service & spare partsPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringPlastics & Packaging+2

From error code to cause, step by step

With the manual, wiring diagram and past cases, even a junior technician knows what to check next.

Today

Troubleshooting depends on the experience of a few senior technicians. Juniors spend hours in manuals or call the experts. Whatever a case taught is not written down anywhere.

An example

A Wallner+Hardt Sensortechnik frequency inverter built in 2021 shows E-214 at a customer site. The agent uses the documents for the EtherCAT variant and points to the temperature sensor first, the cause in 7 of 9 similar cases. It also shows the terminal in the wiring diagram and the expected reading.
Fictional company, typical workflow.

Your data, wherever it lives

Today error code lists and manuals sit as PDFs in the DMS, wiring diagrams and software versions in the PLM, service reports in the CMMS, and what helped last time is in chats or only in the heads of a few experts. demi reads, understands and links documents and cases per unit and variant, with your rights. The AI shows the most likely causes with checks and sources in minutes, instead of someone searching manuals for hours, and the technician confirms cause and fix.

Where the data lives today

  • PDFs
  • DMS & archive
  • CAD & drawings
  • PLM
  • Tickets
  • Chats
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the DMS, CMMS, PLM and chat. demi replaces nothing and maps error code lists, manuals, wiring diagrams, software versions and service reports to the configuration of every unit. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Technicians see the documents for the units they service, and customer information stays with the case. The technician confirms cause and fix before they are saved, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent loads the documents for exactly this variant, ranks likely causes from recorded past cases and guides the check step by step. Every check cites the manual page or the case it comes from.

How it runs

  1. 1

    Enter the error code and serial number, in chat or on a tablet

  2. 2

    demi loads the documents for exactly this variant

  3. 3

    Review likely causes with checks and their sources

  4. 4

    Work through the checks and enter the readings

  5. 5

    Cause and fix are saved to the case

What changes

  • Faster fixes on site

  • Junior technicians work more independently

  • Expert knowledge stays in the company

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+338 hfreed per year

Assumptions and calculation

demi guides you check by check to the cause with manual, wiring diagram and past cases; you fix it.

45 min → 33.75 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

150 fault cases × 45 min × 25% × 1.0 (manual) × 12 months = 20,250 min = 338 h

Value per year, before demi costs

Freed per year+338 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$21,970

gained per year

338 h ÷ 1,760 h per role = 0.2 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Does it know which variant the customer has?

Yes, through the serial number. From delivery and service records demi knows the configuration and software version of that unit. So the agent shows the wiring diagram and manual that match it, not simply the latest edition.

Which sources does the agent use?

Your own documents: error code lists, manuals, wiring diagrams, release notes and solved service cases. Every check cites its source so the technician can look it up. If there is no source, the agent says so.

Does it learn from new cases?

Yes. Every confirmed cause is stored with the case and shapes the order of future suggestions. A senior technician can mark a fix as verified.

Does it replace the call to the expert?

Not always, but the call is needed less often. When the agent gets stuck, it hands the case to the expert with every check and reading so far. Nobody has to start from the beginning.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases