Winsen One
← The Winsen Blog
Industry · 10 min read · July 21, 2026

The scope of AI nativity in manufacturing.

Lighthouse factories, predictive maintenance, vision QC: the shop floor got the budget. The batch records, deviations, and supplier documents behind it are still read by hand. The last mile of manufacturing AI is paperwork.

W
The Winsen Team
Published July 21, 2026

Manufacturing has spent a decade proving that AI works on the shop floor. Vibration data feeds models that call a bearing failure days before it happens. Cameras inspect welds, fills, and solder joints at line speed, catching defects no tired human eye would. Digital twins let engineers rehearse a line in software before anyone touches the physical one, and Siemens has spent years demonstrating plants where the product, the process, and the factory itself exist digitally before they exist in metal. The World Economic Forum turned the showcase into an institution: its Global Lighthouse Network of the world's most advanced factories passed two hundred sites in 2025, each one a public argument that predictive maintenance, machine vision, and simulation pay. On the floor, the argument is settled. The machines got smart.

Then take the stairs to the quality office, and the decade disappears. A batch record, sometimes hundreds of pages of it, is reviewed page by page by a person with a highlighter before the batch can ship. A deviation opened in March is still open in June, waiting on an investigation that is mostly document retrieval. Supplier certificates arrive as email attachments and get chased by more email when they do not. Invoices sit in a queue waiting for a three-way match against a purchase order and a goods receipt that live in two different systems. The plant that can predict a bearing failure a week out cannot tell you, today, which of its open deviations are waiting on a single missing signature. The shop floor got the budget. The paperwork did not.

Two floors, two decades apart

The gap is not stupidity. Budgets went to the floor because the floor is where the return was measurable and the data was structured. A sensor produces clean time series. A camera produces frames against a fixed spec in controlled light. Overall equipment effectiveness moves, and everyone sees it move. The paperwork produced no dashboard anyone was rewarded for improving, and the people who carried it, quality reviewers, deviation owners, buyers chasing certificates, accounts payable clerks, were scattered across cost centers with no shared budget line and no lobby. So the same plant now runs two eras at once: a production line from this decade, documented by an office from the last one.

The cost hides in cycle time rather than in any single line item, which is exactly why it survived. Finished batches wait on record review, so working capital sits in quarantine for days that have nothing to do with chemistry. Deviations age, and aging deviations are precisely what an inspector reads as a quality system losing its grip. Month-end stretches because matches fail and nobody knows which of the three documents is wrong. None of this ever appeared on the OEE dashboard, and what the dashboard does not show, the capital plan does not fix.

The paper supply chain

The document burden does not stop at the plant gate. Every incoming lot arrives with a certificate of analysis or conformance that someone must check against the specification before the material can be used, and every supplier audit generates findings that someone must chase to closure. Aerospace runs on first article inspection reports and certifications that trace a part back through every tier of its supply chain. Food plants live under HACCP records and supplier guarantees. Medical device makers hold device history records that must reconcile with the device master record, unit by unit. The vocabulary changes by industry, but the grammar is identical: a regulated promise on paper, checked by a person, filed against the day an auditor asks for it. Multiply that by every lot, every part, and every batch, and the checking becomes a workload that scales with production while the tools for it never did.

Three-way matching sits at the tame end of the same spectrum. A purchase order, a goods receipt, and an invoice are three documents that agree far less often than anyone admits, and in most plants the disagreements are still worked by hand, one email thread at a time. It is the least regulated document queue in the building and often the largest, which makes it a fair measure of how far the office fell behind the floor.

Why documents are the hard last mile

It is worth being honest about why the paperwork resisted automation this long. Documents are the opposite of sensor data. They are unstructured: scans, handwriting, stamps, attachments, tables that lie about their own headers. They are judgment-heavy: reviewing a batch record is not checking that fields are filled, it is holding the record against the SOP, the master recipe, and the specification, and deciding whether the anomaly on page 141 is a footnote or a problem. And the work itself is regulated. In a GMP plant, the reading is a controlled activity, and getting it wrong has consequences measured in recalls and warning letters.

The regulatory record says the quiet part. Documentation and data integrity issues are consistently among the most cited categories in FDA Form 483 observations, and the agency's 2018 data integrity guidance made explicit that it expects audit trails to be reviewed, not merely retained. In an environment like that, a black-box classifier that stamps records as passed is worse than useless. Any automation of checking work has to produce evidence of its own reading, or it fails the very standard it was hired to uphold. That bar, more than the technology, is what kept the document side manual. Until the machines could show their work, they could not be allowed to do it. The machines can now show their work. That is the change that makes this essay worth writing.

It also explains why the earlier generation of document technology never closed the gap. OCR and template-based extraction could lift a field from a form, and plants bought plenty of both. But a batch record review is not field extraction. It is comparison and judgment across documents: this entry against that limit, this signature against that role, this timestamp against the step before it. Template tools broke every time the form changed and could never say why a record was acceptable, only what it contained. The plants that tried them concluded, reasonably, that the paperwork was unautomatable. What they had actually learned was narrower: it was unautomatable by tools that could not read.

A vision model inspects a part in milliseconds. Nobody inspected the paperwork behind the part, because the paperwork could not be inspected at machine speed. Now it can.

What document-side nativity looks like

Picture the same plant with the office staffed the way the floor is. The batch record is read the moment it closes, in full, against the SOPs and the specification, with every check citing the page and the clause it rests on. The review does not end in a verdict. It ends in a short list of exceptions, each with the evidence attached, sitting in a queue for the quality reviewer, who now judges findings instead of hunting for them. A deviation is drafted the day the event occurs, with the timeline assembled from the record, the affected batches identified, and the relevant SOP paragraphs quoted, so the investigator starts from a case file instead of a blank template. Supplier certificates are checked on arrival against the specification and chased automatically when they are missing or expiring. The three-way match runs on every invoice, and mismatches arrive as explained discrepancies rather than as a queue of unexplained failures.

The constant across all of it is the shape of the control. The AI reads, extracts, drafts, and flags. A named person approves. Every action, every page pulled, every conclusion drawn is journaled. Nothing releases a batch, closes a deviation, or pays an invoice on its own. Approval-first is not caution theater in this industry. It is the rule the plant already applies to its own people, where production reviews the record and quality reviews it again, and nobody signs their own work. An AI employee that drafts and never signs is not a novelty in a GMP environment. It is a new colleague operating under the oldest rule in the building.

For the people, the change is the ratio of judgment to clerical motion. A batch record reviewer today spends most of the shift confirming that completed pages are, in fact, complete. In the staffed version, that reviewer starts the day with the exceptions: the entries that deviate, the values that trend, the pages where the machine's confidence dropped and it said so. Deviation owners start from assembled case files instead of blank templates. Buyers stop being collection agents for certificates. Quality professionals did not join the profession to turn pages, and the plants that move first tend to find that the reviewers are the easiest people in the building to convince.

The compliance dividend

Something unexpected falls out of doing this properly: the plant becomes audit-ready by default. Today, preparing for an inspection is an archaeology project. Records are retrieved, timelines are reconstructed, and the review of the review is performed in the anxious weeks before the auditor arrives. When the checking work is done by a system that journals every read, the evidence is a byproduct of the work rather than a project after it. Which records were reviewed, against which SOP versions, what was flagged, who approved, and when: the answers exist the moment the question is asked, because the work and its documentation were never separate activities.

There is a second-order dividend. Review-by-exception, the operating model quality organizations have wanted for years, finally becomes honest. The reason exception-based review makes regulators nervous is the fear of what the sampling missed. When coverage is total and the machine's reading is cited line by line, exception review stops being a bet on a sample and becomes a documented reallocation of human attention to the places the evidence says it is needed. That is a conversation a quality head can have with an inspector and win.

Sequencing for a plant

The way in is narrow. Pick one document queue with ground truth. Closed deviations are a good candidate: the plant holds years of them, and each one is a worked example of what a complete investigation looked like. Historical batch record reviews are another, because the findings the human reviewers logged are an answer key. Run the AI in shadow. Let it read what the humans read, and compare its findings with theirs. The disagreements are the education, in both directions. Some are the machine misreading a handwritten entry or a mangled table. Some are things the sampled, tired, human process genuinely missed, and every plant that runs this exercise honestly finds some of those.

Measure the pilot on three numbers and resist the urge to add more. Agreement with the historical human outcome, because that is the trust number. Findings the human process missed, because that is the value number. And cycle time from record close to disposition, because that is the number the plant manager feels. A pilot that moves all three is a program. A pilot that moves none of them deserves to be shut down, and shutting it down quickly is itself evidence the plant is running the exercise honestly.

Then go live on that one queue, approval-first, with the quality team approving every output, and let the record accumulate. Expand only when the record justifies it, one queue at a time: record review, then deviation drafting, then supplier documents, then the match. The sequencing rule is to follow the ground truth, not the pain. The hairiest problem in the plant makes a terrible first project. The most repetitive one makes an excellent one, because repetition is where the evidence accumulates fastest and where the office feels the relief first.

This is the work Winsen One was built to staff. Its AI employees hire into document roles, quality record review, deviation drafting, supplier document control, invoice matching, and work the way this essay describes: index-first reading, a page citation on every finding, a journal on every action, and a named approver on every output. The floor has its machines and has had them for a decade. Winsen One is how the office gets its own, without giving up the signatures that make a plant a regulated plant.

Hire an AI employee for one role, watch it work a visible queue, and approve every output before it counts.

The command center for AI employees.

Get in touch and put an employee on your queue.

See it in action
Don't take our word for it

Work is better with Winsen.

Ask your favorite AI for a summary on Winsen. It opens with the question ready, so you get an honest read in one click.

Powered by winsen.ai/llms.txt