REACH/ELV material traceability — an undeclared SVHC is not an incident, it is a suspended order.

The problem

The right declaration is the intersection of three data sets that are almost never in the same place.

The quality manager at an automotive supplier knows it by heart: the IMDS datasheet sent to the OEM is the intersection of three realities that live in three parallel worlds.

1. The supplier's declaration — a PDF that arrived by email, an IMDS form, an Excel sheet the sales rep updated last week and nobody forwarded to quality.
2. The BOM of the finished product — the bill of materials that lives in the ERP or the PLM, with its revisions, its equivalent alternates and its emergency substitutions.
3. The actual plant record — which part number was bought and assembled in each batch, which almost never matches 100% what the list said, because of silent supplier changes.

The classic system (a PDF in a folder, a person cross-checking it by hand every time the OEM asks) works 99% of the time. That 1% is the one that reaches the OEM portal as a non-conformity — and every non-conformity means the order is held until it is closed. And the SVHC candidate list grows twice a year: every update turns a once-correct declaration into an insufficient one.

How it fits the IRIS system

iLEAN does not add a fourth system — it seals the cracks between supplier, BOM and plant.

The REACH/ELV problem is not a lack of information: it is information split into islands and declarations arriving in mixed formats that nobody ever had time to unify. iLEAN acts as the putty that fills those gaps, without asking you to change your ERP, your PLM or the OEM's IMDS portal.

Connect captures every declaration through whichever channel the supplier uses. Tracer keeps the batch-by-batch link with the BOM. Writer prepares the IMDS datasheet, signed by a person — never the other way round.

The three iLEAN pieces applied to REACH/ELV traceability:

• Connect — listens to everything coming in from suppliers. A PDF by email, a photo of the datasheet over WhatsApp, a web form, an IMDS declaration. It digitizes it at second zero and extracts the declared substances into a structured field. If a supplier writes “coating change on the M6 screw”, iLEAN sees the new datasheet and triggers the cross-check without anyone forwarding anything.
• Tracer — maintains the link supplier declaration ↔ purchased part ↔ batch ↔ finished product. When a substance enters the candidate list, Tracer walks up the tree and flags every product where that substance appears. Nothing has to be rebuilt by hand when the OEM asks about a batch from two years ago.
• Writer — an agent that prepares the IMDS datasheet or the SCIP declaration when it is due, using the freshest data Connect has captured and the cross-reference Tracer maintains. The person validates and signs; nothing goes out without a human signature. If the agent detects an inconsistency (an SVHC present in a purchased component that is not declared further up), it holds the submission and raises the alert.

See the full IRIS architecture →

Before and after

Manual declaration vs. cross-referenced traceability with iLEAN

Aspect	Manual declaration + PDF in a folder	With iLEAN Tracer + Connect + Writer
Capturing the supplier declaration	Manual email, forwarded when someone remembers	Email/WhatsApp/IMDS read at second zero
Cross-check with the BOM	A spreadsheet rebuilt whenever the OEM asks	Live batch-by-batch link, always up to date
Change in the SVHC candidate list	Discovered when the datasheet is rejected	Automatic walk up the tree, alert before submission
Silent supplier change	Discovered by chance	Connect sees the new PDF, triggers the cross-check
Preparing the IMDS datasheet	Quality does it by hand, nervously	Writer prepares, the person signs
File for the OEM audit	Rebuilt by hand, weeks	Per-product dossier, automatic

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the specific data of your plant. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Tier-1 with 50-150 active suppliers, a mix of mature IMDS declarants and small suppliers sending PDFs by email. Multi-OEM (at least two customers with different CSRs).
• Connect + Tracer pilot on one product family and its 10-20 main suppliers. First value expected within a few weeks — the first time saving is measured on the next IMDS datasheet you prepare.
• Indicative payback between 4 and 9 months, depending on the average cost of an IMDS non-conformity and on the hours quality spends rebuilding files by hand.
• Hard lever: avoiding a single order suspension caused by a documentation failure. One suspension pays for the pilot, before counting the recurring saving in quality hours.
• Expected reduction in the time needed to prepare each IMDS datasheet and SCIP entry of over 30%, recurring.

And the quality director's reasonable doubt

“What if the AI gets the declared substance wrong when it reads the supplier's PDF?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely recontextualizes a piece of data from one system into another (reading the supplier datasheet and populating the IMDS format), the best models brought error below 1.5%^[2]. And even so, what is critical is never decided alone: the agent prepares, iLEAN holds the submission if there is an inconsistency, and the person signs. The three safety rings exist precisely for this.

^[1] Reference automotive quality standard on the order of 25 PPM (parts per million). Symestic.

^[2] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.