Skip to content
Quality, standards & complianceAutomotive Suppliers

Find OEM requirements with section and revision

demi answers what a specific customer requires for sampling, labelling or escalation, quoting section and revision.

Today

Every automotive customer adds its own requirements manuals on top of the standards, and they keep changing. Anyone with a question about sampling, labelling or escalation searches long PDFs or asks the one colleague who knows. A missed revision ends as a complaint.

An example

At Arnstein the shipping manager asks what an OEM customer requires on the label for the safety-relevant AH-2210 bracket in AlSi10Mg. The agent quotes section 6.4 of revision 7 of the customer manual and points out that revision 7 added the batch number in plain text. It links the affected packaging instruction straight away.
Fictional company, typical workflow.

Your data, wherever it lives

Your automotive customers' requirement manuals sit today as long PDFs in customer portals, the DMS or the mailbox, often in several revisions; your processes, work instructions and inspection plans live in the QMS. demi reads, understands and links them per customer, section and revision, with your rights. The AI answers your questions in seconds instead of twenty minutes of leafing through, with section and revision, and quality decides how to apply it.

Where the data lives today

  • PDFs
  • Web & portals
  • DMS & archive
  • E-mails
  • QM system
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

    Data sources in this case: the DMS, QMS and customer portals. demi replaces nothing and links each customer's requirement documents to their revisions, your released documents and the processes they affect. That makes it clear which section applies to which customer right now.

  2. 2 · PermitPermission Layer

    Quality maintains the requirements library and approves new revisions, and staff see the requirements of the customers they work for. Every approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent answers questions with the exact section and revision and quotes verbatim where the wording matters. It flags changes between revisions and lists the processes and documents a new revision affects.

How it runs

  1. 1

    Clarify the data sources: requirement manuals per customer from the DMS and customer portal

  2. 2

    Compare a new revision with the previous one and show the changes

  3. 3

    List the affected processes and documents

  4. 4

    Have quality approve the new revision

  5. 5

    Answer day-to-day questions with section and revision

What changes

  • Customer rules applied correctly

  • Revision changes no longer missed

  • Fewer complaints from formal errors

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

+96 hfreed per year

Assumptions and calculation

demi finds what the customer requires, with section and revision; you put it into practice.

20 min → 12 min per case

How does it run today?

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

How we calculate

60 OEM questions × 20 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 96 h

Value per year, before demi costs

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

+€6,240

gained per year

96 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

What happens when a new revision arrives?

It comes as a download from the customer portal, from the DMS or by e-mail; how it gets to demi, we clarify in a call. The agent compares it with the old revision section by section and shows every change in substance with both passages. Quality confirms that the new revision applies. From then on the agent answers from it, and older revisions stay on record.

Does demi link the requirements to our processes?

Yes, to process descriptions, work instructions, inspection plans and forms from your QMS. For each requirement you see where you meet it, and for each process which customers ask for something. Gaps show up before the audit, not during it.

What if the agent cannot answer a question with certainty?

Then it says so and shows the passages that might apply. It never makes up a rule. Every answer carries section and revision so you can check it at a glance.

Do customer documents stay confidential?

Yes. Access follows your org chart. Only the teams working for a customer see its manual, and someone who handles one customer does not see the requirements of the others.

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