From the metrology spreadsheet to the ERP, no retyping

The problem

The real measurements and the official ones live in different worlds.

two parallel worlds — the real spreadsheet (live dimensions) and the official ERP (data retyped days later by someone who spends recurring time copy-pasting and makes errors on critical dimensions).

• Every lot, the quality lead fills a spreadsheet with CMM dimensions, surface roughness, hardness and the Cpk of the critical dimensions agreed in the PPAP. That is the number the OEM reviews in the PPAP and at every capability review.
• That spreadsheet sits in a shared folder the ERP never sees, so the official record lags reality by days. By the time the ERP shows a problem, the lot has already shipped.
• Days later someone copies it into the quality module, and the errors land exactly on the critical dimensions where a decimal decides whether a lot is in or out. Those errors are found, if at all, when a customer asks for the data.
• Meanwhile the plant pays for several quality-module seats whose main job is retyping what already exists in a file. Few people question that cost because it has always been there.

How it fits the IRIS system

Connect listening inward — it watches the metrology folder, not the person.

Connect's "listen inward" mode — it watches the shared folder, not the person: reads the delta the moment the file saves, parses it with a grounded model, validates on screen, and pushes to the ERP via API.

The quality lead keeps their spreadsheet and their method. What disappears is the copy-paste afterwards, and with it most of the reason for paying several seats in the quality module. The CFO sees the license line drop; quality sees SPC that is finally current. Nobody in quality has to learn a new tool to make it happen.

See the full IRIS architecture →

Before and after

The CMM spreadsheet today versus the spreadsheet that flows

Aspect	Today	With iLEAN Connect
Lag from measurement to ERP	Days	Instant, after validation
Recurring retyping	Every lot	Zero
Errors on critical dimensions	Typos in the decimal	Read from the source file
SPC and Cpk in the ERP	Out of date	Fed lot by lot
Quality-module seats	Several	The single validator
The quality lead's workflow	—	Same spreadsheet, same folder

days of lag between real measurement and ERP data → instant. Recurring transcription time → zero.

Impact estimate

Impact estimate — to be validated against your license invoice.

The block below is an estimate to be validated against your plant's actual data. We put it forward so the committee has an order of magnitude; we refine it during the assessment.

• Estimated payback 4-9 months, mostly from the license line.
• Typically a 50-80% reduction in quality/metrology module licenses, from several seats down to the one validator.
• Lag between real measurement and ERP data goes from days to instant, so a drifting Cpk is visible while the lot is still on the lathe.
• And recurring transcription time drops to zero, along with the typing errors on critical dimensions.

CFO angle — typically a 50-80% reduction in quality/metrology module licenses (from several seats down to the one validator), estimated payback 4-9 months. *Estimate to be validated*.

And the fair question from the production manager

“What if it picks up the wrong column of a messy spreadsheet?” — parsing a sheet whose structure repeats every lot is an anchored task, where the best models drop below 1.5% error [1]. And nothing reaches the ERP until the validator sees the parsed values on screen, next to the drawing tolerance, and approves them.

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