Skip to content
Quality, standards & compliancePlastics & PackagingAutomotive SuppliersTextiles

Car interiors: emissions and fogging per article

demi keeps the odour, emission and fogging results of every article and shows which approval a raw material change could put at risk.

Today

Car makers approve fabrics, nonwovens and coated textiles for the interior only once odour, emissions and fogging meet their standards: VDA 270 for odour, VDA 278 for VOC and FOG, DIN 75201 for fogging, plus each maker's own limits. Test reports arrive from the lab as PDFs in the inbox, recipes sit in recipe management, raw material batches in the ERP. When a supplier changes a plasticiser or a yarn finish, nobody can quickly say which approvals depend on it. And from 6 August 2027 the EU caps formaldehyde in the interior air of new vehicles at 0.062 mg/m³.

An example

At Fibrana, the supplier of a plasticiser for the PVC coating announces a new formulation. The agent finds 14 articles containing it, among them cover material for seats and door trims for three car makers. Eleven have FOG values to VDA 278 far below the limit, but three already sit between 210 and 230 µg/g against a limit of 250, and one of them last scored grade 3 in the VDA 270 odour test, the customer's maximum. The head of quality has only these three articles pre-tested with the new plasticiser, and the change notification to customers is ready as a draft.
Fictional company, typical workflow.

Your data, wherever it lives

Today your odour, emission and fogging results sit in lab reports as PDFs, in the inbox and in the lab system, the limits in each customer's standards, recipes in recipe management and raw material batches in the ERP. demi reads, understands and links them per article and batch, with your access rights. When a raw material changes, the AI shows in minutes which approvals could fail, and your head of quality decides what gets retested.

Where the data lives today

  • Databases
  • PDFs
  • E-mails
  • QM system
  • PLM
  • 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

    Data sources in this case: the lab system, PDF test reports, e-mail, the QM system, recipe management and the ERP. demi replaces nothing and links every test result to article, production batch, recipe version and the raw material batches used, and to each customer's standard and limit. So every article shows which values each approval rests on.

  2. 2 · PermitPermission Layer

    Test results and recipes are visible to quality and development; sales sees the approval status per customer, not the recipe. Change notifications go to customers only after release by the head of quality, and every release is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads values, method and test conditions from every lab report and compares them with the limit of each customer standard. When a raw material changes, it follows recipes and batches to every article containing it and shows where the margin to the limit is thin. Limits and standards are fixed and stored; the language model only explains why an article could fail.

How it runs

  1. 1

    A test report arrives from the lab, or a supplier announces a change to a raw material.

  2. 2

    The agent reads odour grade, VOC and FOG values and fogging and assigns them to article, batch and recipe version.

  3. 3

    It compares each value with the limit of every customer standard and shows the margin.

  4. 4

    When a raw material changes, it lists every article affected and marks where an approval could fail.

  5. 5

    The head of quality decides on new tests and releases the change notification to customers.

What changes

  • Each article's approval status for every customer at a glance

  • Raw material changes without surprises at the car maker

  • Targeted retesting instead of testing everything again

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 assigns every test report to article, batch and customer standard and flags thin margins; you decide.

30 min → 18 min per case

How does it run today?

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

How we calculate

40 test reports × 30 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

Which vehicle interior test standards does demi know?

The standards your customers test to, such as VDA 270 for odour, VDA 277 and VDA 278 for emissions, DIN 75201 for fogging and ISO 12219 for interior air, plus the car makers' in-house standards with their limits. Your quality team stores them per customer; when a standard changes, the new version applies from then on.

How does demi know which raw material is in which article?

From recipes, bills of materials and the batches that went into each production batch. The agent follows a raw material from goods receipt to the article and the customer. Where a link is missing, such as an old recipe on paper, it shows the gap.

Does every raw material change mean retesting everything?

Not necessarily. demi shows per article how much margin the existing values have to the limit and which values depend on the changed raw material. Your head of quality decides which articles are retested and which customers are informed, often as the customer requires.

Can demi prepare the change notification to the car maker?

Yes. The agent drafts the notification with the articles affected, old and new test values and the test plan, and attaches the reports. What the customer then asks for, such as new samples, is set out in its requirements. The notification goes out only after your 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