Skip to content
Service & spare partsPumps & ValvesMachinery & Plant EngineeringConveying & IntralogisticsConstruction & Building Services+3

Commissioning report finished on site

Missing readings and wrong values show up while the technician is still at the machine.

Today

Commissioning reports are filled in on site on paper or in spreadsheets and typed up later in the office. Missing readings or out-of-tolerance values surface only after the engineer has left. Customer acceptance is delayed.

An example

When commissioning an HP-250 press rated at 250 kN, the agent sets up 64 checks for Ebert & Lorenz Maschinenbau. It flags that the insulation test on the main drive is missing and that the measured ram stopping time exceeds the stored limit. After a new measurement and adjustment, it produces the report for signature.
Fictional company, typical workflow.

Your data, wherever it lives

Checklists and target values sit today in spreadsheets and documents in the DMS, the unit's configuration in the ERP, and on site there are paper sheets, phone photos and notes that someone types up in the office later. demi reads, understands and links them per unit and checkpoint, with your rights. The AI flags missing readings and out-of-tolerance values while the commissioning engineer is still at the machine, not after they have left, and the engineer and the customer sign the finished report.

Where the data lives today

  • ERP
  • Office files
  • DMS & archive
  • Scans & paper
  • Photos, video & audio
  • 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 ERP, DMS, chat and spreadsheets. demi replaces nothing and links the project, unit configuration, checklists, target values and readings; photos and notes attach to the matching check. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    The commissioning engineer fills in the report, and both the engineer and the customer sign it. The customer receives only the signed version, and any later change creates a new, recorded version.

  3. 3 · ActIntelligence Layer

    The agent prefills the report for the configuration and checks every reading exactly against its stored target, citing where the target comes from. It flags gaps while the engineer is still on site and produces the document for signature only once everything is complete.

How it runs

  1. 1

    demi sets up the report with the checks for exactly this configuration.

  2. 2

    The engineer enters readings or sends photos and notes by chat.

  3. 3

    The agent checks every value against its target and flags missing readings at once.

  4. 4

    Once complete, demi produces the report; engineer and customer sign.

  5. 5

    The signed report goes back only after approval.

What changes

  • Complete reports while still on site

  • Deviations caught while the engineer is still there

  • Faster customer acceptance

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

+192 hfreed per year

Assumptions and calculation

demi builds the record from checklist, readings and photos and checks each target value; you sign.

2 h → 1.2 h per case

How does it run today?

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

How we calculate

20 commissionings × 2 h × 40% × 1.0 (manual) × 12 months = 192 h

Value per year, before demi costs

Freed per year+192 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€12,480

gained per year

192 h ÷ 1,760 h per role = 0.1 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

Can demi prepare the checklist for each configuration?

Yes. Once demi has the configuration, such as options, drives and safety functions, it builds the matching checks from it. How the configuration gets from the ERP to demi, we clarify in a conversation. Checks for options that are not fitted are left out. You keep maintaining the templates yourselves.

Where do the target values come from?

From your own documents: design data, data sheets, test instructions and the standard values your experts have stored. The agent compares against exactly that value and names the source. It never sets limits itself.

Can the customer sign the report digitally?

Yes. The customer receives the finished report for review and signs it digitally, on site or later through the portal. The signature and the version signed are recorded.

Do our engineers have to learn a new app?

No. They use what they already have: spreadsheets, phone photos and chat messages. demi assigns readings and photos to the right check. If an entry is unclear, the agent asks the engineer directly.

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