00Production record review · 21 CFR 211.192
That sentence has been in the Code of Federal Regulations since 1978. It is why a single deviation turns into a three-to-five week paper exercise across every batch of the same product. encompass360 makes it one screen.
2,755 FDA citations against §211.192 across 1,776 sites, and FY2025 was the highest count since 2011.
01Trusted on production lines at
02The same review, before and after
03Stated by an engineer, unprompted
“Ignition’s built-in historian doesn’t provide a way to attach context to a record (like a batch ID). I could use the built-in historian and use table joins and timestamp comparisons, but to me that’s worse… Is there a best practice for storing ‘contextualized’ timeseries data?”
Inductive Automation forum, March 2022Two years later, on the same forum, a senior engineer answers the same question bluntly: the historian “isn’t designed to correlate your batch-active tag with any other tag. Or any tag with any other tag.” The workaround is always the same: transaction groups writing to conventional SQL tables, hand-building the context the historian will not hold.
And the failure mode is precise: if the batch-active flag is written a millisecond before the process value, that final reading falls outside the query window and silently never appears in the batch view at all. Nobody sees a gap. There is nothing to see.
Forum threads from 2022 and 2024 land on the same workaround: transaction groups writing to conventional SQL tables, because the historian will not hold a batch ID next to a tag.
A historian excels at numeric time-series and handles text badly (audit trails, batch information, user records) because of its long, narrow data structure. A relational database is the exact inverse.
Two independent groups reached the same conclusion. Neither system is wrong; neither is sufficient alone. encompass360 layers both, which is why the batch view holds the trend and the audit trail and the recipe and the genealogy on one axis, instead of making a reviewer join them by timestamp and hope.
04The problem
The historian holds the trend. The SCADA system holds the alarms. The batch system holds the phases. The MES holds the recipe and its limits. The LIMS holds the result. The BMS holds the room. Each one is correct, and none of them talk to each other.
So when the Quality Control Unit has to review a production record before release, somebody assembles all of it by hand. That is the three weeks. Not the analysis. The assembly.
§211.192 requires investigation of any unexplained discrepancy, and names theoretical yield outside its established range as an example.
The investigation must extend to other batches of the same product. One deviation becomes a campaign-wide review.
All of this happens before a batch is released or distributed. The review sits on the critical path to shipping product.
05The product
Batch at a Glance layers six independent sources onto a single contextualised view. Nothing is copied, nothing is transformed, and the source records stay exactly where they are. Each row below is one layer of the figure beside it.
06What customers say when they see it
“We currently have no idea what’s going on in our batches.”
That is the reaction, reported by the engineer who has demonstrated this software for thirty years. Not “this is faster”, but this is what we need to see.
And the review does not happen in one place. A quality reviewer investigating a batch that ran three weeks ago sits at a workstation with a large screen and compares batches side by side. Maintenance carries a tablet. Both are looking at the same record; neither should be told to use the other one’s tool.
07The platform, the reason, the company
One contextualised view is the foundation. On top of it: one-touch batch comparison, multivariate analytics, twelve families of audit-ready reports, and a verification engine that audits its own data.
Your data decides whether a batch ships and whether an audit clears. We hold every record to ALCOA+ and 21 CFR Part 11, prove it, and take recurring cost out of the line as we do. A validated path to the Unified Namespace.
Three brand eras and twenty years of live production behind one platform. Thirty-plus years in life-sciences manufacturing, expertise across every layer of the floor, teams in New Jersey, Oregon and Puerto Rico.
08For the evaluation
A regulated purchase is reviewed by a committee, and every seat reads this site for something different. The first question each one asks, and where it is answered.
| Seat | First question | Where it is answered |
|---|---|---|
| QA batch record reviewer8 to 15 records a week | Can I review by exception without opening six systems, and without being told what to disposition? | The live demo opens on disposition, CQA result and CPP departures, lists every exception with its discrepancy state in §211.192’s words, and extends the investigation to other batches in one control. On 1,005 real batches. |
| Controls and automationPI, Ignition, Rockwell | What does it read, and what happens at 3 am when store-and-forward backs up? | Connections: OSI/AVEVA PI, Proficy, FactoryTalk, Ignition, MES and LIMS. Redundancy, store-and-forward and health alerts on Data Matters. |
| CSV and validationtheir answer gates the purchase | How do we validate it, and which technical controls does it give us under Part 11? | A read-only review layer with an audit trail throughout, and the sources’ own audit trails read in place; the ALCOA+ mapping to §11.10(b), §11.10(d) and §211.68(b) is on Data Matters. Supplier questions go to the engineers who built it. |
| Plant IT and OT securitynothing touches the process network unsigned | What connects to what, in which direction, and who can see it? | Source records stay where they are and are never rewritten; the review layer reads each source and writes nothing back. SSO / SAML, role-based access, thin client, virtualised or browser delivery, stand-alone or enterprise. Where it runs. |
| Procurement and vendor riskdiligence on a two-principal vendor | Who is behind it, what has it run on, and what happens to us if that changes? | Thirty-plus years in life-sciences manufacturing, three brand eras and twenty years of live production, teams in New Jersey, Oregon and Puerto Rico. The company. Continuity questions go to the founders directly. |
| The linethe people who run it | What did it actually change on a line like ours? | One ibuprofen line: the review that took three to five weeks, and what it took after. Figures are the client’s own. |
09Review by exception
A reviewer needs to know one thing first: does this batch need my attention? Batch at a Glance opens with the disposition, the CQA result against specification, whether theoretical yield tripped its §211.192 trigger, and how many critical process parameters departed from the golden master.
Everything else is one click away, and stays out of the way until it is asked for.
The comparison band is computed from the distribution of released batches at the same strength, not one hand-picked reference run.
The trend is shown against what the batch actually produced: dissolution, weight variation, yield, impurities. Cause and consequence on one screen.
On 25 August 2026, after the records plotted above, the FDA cited a manufacturer under §211.192 as violation number one: “failed to thoroughly investigate any unexplained discrepancy.” This is current enforcement, not a historical example.
The demo runs on published production data: 1,005 batches and 4,720,208 process samples from a real solid-dose line, released under CC BY 4.0. No customer records are used anywhere on this site.
