Skip to content
Quality, standards & compliancePumps & ValvesWater & EnvironmentMachinery & Plant EngineeringConveying & Intralogistics+3

Compile the order documentation per plant

Collect manuals, certificates, drawings and test reports per order and check them against the customer's documentation list.

Today

At handover the customer asks for a binder of manuals, certificates, drawings, test reports and declarations, often over a thousand pages. The documents are scattered across design, purchasing, quality and commissioning. Collecting them ties up weeks, and a certificate is still missing at the end.

An example

For a conveyor system, the customer of Vogelsang Anlagentechnik GmbH lists 163 documents. The agent finds 148 in the DMS and QMS and files them in the order of the list. For 15 it reports gaps: three material certificates are missing, and four drawings are older than the bill of materials.
Fictional company, typical workflow.

Your data, wherever it lives

Manuals sit in the DMS, drawings in the PLM, test reports and certificates in the QMS and in project folders, and the customer's wishes in the order. demi reads, understands and links them, with your rights. The AI matches the documents with the documentation list, files them and reports gaps and old versions. Project management checks the binder and releases it to the customer.

Where the data lives today

  • PDFs
  • Office files
  • DMS & archive
  • PLM
  • QM system
  • ERP
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

    Documents sit in the DMS, PLM, QMS and project folders, and the customer's documentation list is in the order or specification. demi replaces nothing and links both with the bill of materials, supplier certificates and test reports. The items of the list become single records, linked to the order.

  2. 2 · PermitPermission Layer

    Project management and quality see the state of the binder. What goes to the customer is released by project management, and certificates and declarations stay with quality.

  3. 3 · ActIntelligence Layer

    The agent reads the documentation list, looks for the matching file for each item and checks order number, revision and validity. It builds the binder in the order of the list and reports what is missing or outdated.

How it runs

  1. 1

    Pick the order and the customer's documentation list; clarify the data sources: DMS, PLM and QMS.

  2. 2

    The agent splits the list into single items.

  3. 3

    It looks for the documents and checks revision and assignment to the order.

  4. 4

    It reports gaps to the people responsible and follows up what arrives.

  5. 5

    The binder is ready as a draft, and project management releases it.

What changes

  • Handover documentation ordered and traceable

  • Missing certificates noticed early, not at acceptance

  • Less searching in project folders

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

+288 hfreed per year

Assumptions and calculation

demi collects the documents and checks them against the customer's list; your project team closes the gaps.

20 h → 14 h per case

How does it run today?

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

How we calculate

4 orders × 20 h × 30% × 1.0 (manual) × 12 months = 288 h

Value per year, before demi costs

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

+€18,720

gained per year

288 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

What belongs in such a binder?

The customer's documentation list decides: for example manuals, drawings, test reports, certificates and declarations of conformity. The agent follows that list and your templates.

Does the agent also create documents that do not exist yet?

It can draft from existing data, such as a table of contents or a bill of materials as a document. Certificates and declarations are created and signed by your quality team.

How does it handle changes after compiling?

If a document changes in the DMS, it shows the difference to the binder and proposes the new version. You decide whether it goes into the binder.

Is this the CE file?

No. The CE file is one part of it. This covers the whole handover documentation of the order that the customer asks for in the list.

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