Skip to content
Quality, standards & complianceMetal & MachiningPlastics & PackagingTool & Mould MakingAutomotive Suppliers+2

Assemble a complete first-article report

Report, material data and evidence match the customer's rules, and gaps show up before you submit.

Today

First-article and production part approvals need many documents in customer-specific formats. They are compiled by hand from the QMS, PLM and file shares. One missing element delays the approval and the start of production.

An example

For a new PA6 GF30 housing, part number AG-4410, the agent at Arnstein assembles the 14 elements of a PPAP level 3 submission. It finds the entry in the industry's material data portal still open and two drawing characteristics without a value in the dimensional report. The quality engineer has them measured and then submits a complete package.
Fictional company, typical workflow.

Your data, wherever it lives

Drawings and characteristics sit today in the PLM and CAD system, measurement reports in the QM system or as PDFs from the measuring machine, material data and certificates in the ERP and in e-mails, each customer's requirements in its portal. demi reads, understands and links them per part and drawing revision, with your rights. The AI assembles the package in hours instead of days and reports every gap before submission, and quality assurance decides what goes out.

Where the data lives today

  • PLM
  • CAD & drawings
  • QM system
  • PDFs
  • ERP
  • E-mails
  • Web & portals
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 QMS, PLM, ERP and portal. demi replaces nothing and links drawings and characteristics, measurement results, process and material data, earlier approvals and each customer's requirements; every part knows its drawing revision and valid approval. demi records the customer approval with its validity in the QMS.

  2. 2 · PermitPermission Layer

    Quality compiles and approves the package. The customer receives exactly the approved package by portal or e-mail, and every submission is recorded.

  3. 3 · ActIntelligence Layer

    The agent assembles the package against the customer's element list and checks each element exactly for completeness, for example every drawing characteristic against the measurement report. After an engineering change it derives the scope for re-submission, each gap with its source.

How it runs

  1. 1

    Choose the customer and submission level; the agent loads the required element list

  2. 2

    It collects drawing, measurement report, material data and process evidence

  3. 3

    It checks every element and characteristic and lists the gaps

  4. 4

    Quality closes the gaps and releases the package

  5. 5

    The package goes to the customer and the approval is logged with its validity

What changes

  • Faster customer approvals

  • Complete packages on the first submission

  • Scope after changes clear at once

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 assembles report, material data and evidence to the customer's rules and shows gaps; you submit.

8 h → 5.6 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 first-article packages × 8 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

Can it follow customer-specific requirements?

Yes. For each customer it is stored which elements are required at which submission level and in which format. The agent assembles the package accordingly and fills in the customer's forms. When a customer changes its rules, you update them once and every new package follows.

How is the scope after a change derived?

demi compares the old and new drawing revisions and sees which characteristics, materials or processes have changed. From that the agent proposes which elements must be redone and which remain valid. Quality makes the call.

Does it track approval validity?

Yes. Every approval is stored with part, drawing revision and validity. When one is about to expire or a change invalidates it, the agent says so in good time, together with the scope that needs re-submission.

Which systems does the first article inspection report need?

Your QMS with measurement reports, the PLM with drawings, the ERP with parts and suppliers and the customer portals you submit through. demi replaces nothing and writes back only after approval. How the data from these systems gets to demi, we clarify in a conversation.

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