Skip to content
Knowledge & documentationPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringConveying & Intralogistics+3

An operating manual for every variant

The manual covers only the options the customer actually got and is ready at delivery.

Today

Manuals are copied from old projects and adapted by hand for each variant. They are finished late and describe options the customer does not have. What service knows about typical faults never reaches the manual.

An example

For order 25-118, an HP-400 press with 9 options, the agent at Ebert & Lorenz Maschinenbau assembles the operating manual from 140 approved modules. It leaves out 4 options that are not delivered and takes the 400 kN press force from the engineering data. It proposes a clearer cleaning step based on recent service tickets; the technical writer adopts it and releases the manual.
Fictional company, typical workflow.

Your data, wherever it lives

The BOM and configuration of every order sit today in the ERP and PLM, illustrations and design values in CAD, text modules and safety notices in the authoring system, old manuals as Word files and PDFs in the DMS, and typical faults in the service tickets. demi reads, understands and links all of it, with your rights. In minutes the AI assembles the manual for exactly the variant delivered, without options the customer does not have, and technical writing checks and approves it.

Where the data lives today

  • ERP
  • PLM
  • CAD & drawings
  • DMS & archive
  • Office files
  • PDFs
  • Tickets
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, PLM, DMS and authoring system. demi replaces nothing and links the BOM and configuration with approved text modules, safety notices, illustrations and the service cases of the same product line. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Technical writing approves every manual, and only authorized staff change safety texts. Every approval is recorded with revision and person.

  3. 3 · ActIntelligence Layer

    The agent selects modules by the actual configuration and fills in technical values exactly from engineering data; it uses safety texts only unchanged. From frequent service questions it proposes improvements, every passage with its source.

How it runs

  1. 1

    Take over the order's BOM and configuration

  2. 2

    Select the matching modules and safety texts

  3. 3

    Fill in values from engineering data and leave out options not delivered

  4. 4

    Technical writing reviews the draft and the proposals from service

  5. 5

    The released manual ships with the machine

What changes

  • Manual ready at delivery

  • Only content that fits the machine

  • Fewer questions to service

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

+384 hfreed per year

Assumptions and calculation

demi assembles the manual for the options delivered from approved modules; you approve it.

8 h → 4.8 h per case

How does it run today?

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

How we calculate

10 operating manuals × 8 h × 40% × 1.0 (manual) × 12 months = 384 h

Value per year, before demi costs

Freed per year+384 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

+$24,960

gained per year

384 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

Can demi use our existing text modules?

Yes, that is the normal case. Your modules live in the authoring system, the DMS or as templates on the file share; how they get to demi, we sort out in a conversation. Where there are no modules yet, the agent breaks existing manuals into proposed modules for technical writing to approve.

How are safety texts protected?

Safety and warning notices come only from approved modules and are never reworded. Only authorized staff may change them, and every change is recorded. If an option has no safety text, the agent reports the gap instead of writing one itself.

Does it work in several languages?

Yes. If the modules are already translated, the agent assembles the manual directly in every language. New passages go through translation with your terminology and are released per language.

Who is responsible for the content?

Your technical writing team, as before. The agent delivers a draft in which every section shows where it comes from: module, revision, engineering value. The team reviews and releases it; no manual leaves the company without that release.

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