Own the loop and its utilities, read each cycle, and raise sanitization and pipework changes
- A forecast date before any result crosses
- The pipe behind a change in regrowth
- Safer steps that start the moment they sign
Purified water trend analysis that lays each water result on its own sanitization cycle, forecasts the first sample over alert, and traces faster regrowth to the pipe that changed.
Follow one user point's regrowth back to its pipe ↓A purified water loop is sanitized on a fixed day, sampled on a rota and plated for five days, and each count is judged on its own against the levels in the water system plan. Once a month the results are exported and charted by calendar date for the site quality review. Nobody lays them over the sanitization cycle, so a point that grows back a little faster after every hot flush reads as within limits, plate after plate.
The day one result crosses, every charge of a client's active since the rise has drawn that water. The investigator pulls change controls, work orders, sanitization records, drawings and batch records by hand, and may find a small branch approved as no impact because its valve stays closed. A planned fix has become a hold and a shutdown nobody chose.
Built forWater-system ownersQA microbiology leadsQC microbiologistsPlant QA heads
A point whose counts grow back faster each cycle passes every check, because each result is read alone against its level.
Joined by hand at investigation
Built-in controls
Clients and inspectors find a water system that saw its biofilm coming and named the pipe behind it.
The water-system owner, the QC lab and QA follow one point on an ambient loop whose regrowth climbed for eight cycles while each count passed.
demoSample data throughout: the loop and its points, the client, people, results, batches and dates.
Engineering, the QC lab and QA each work the same point from their side of the loop.
Own the loop and its utilities, read each cycle, and raise sanitization and pipework changes
Approve impact statements, water-system changes and any looser level or schedule
Read and second-read the water plates, and ask for identifications
Approve learned rules and client notices, and disposition the plant's batches
The day-one count after each hot flush climbed with the day-five count, while TOC and conductivity stayed flat and each plate passed.
The point upstream of the tee stayed at its baseline, and the organisms moved from skin cocci to water rods, which argues against sampling.
A hose-station branch passed change control as no impact on water quality; as built, it was three times the plant's own length rule.
Before the agents read, the upstream check, the safer step, the client's notice, the rule left behind and the report.
demoSample data, from the working solution.
Nobody signs before opening the records behind the signature, and each signer uses a personal PIN.
Purified water trend analysis reads a water system's microbial, TOC and conductivity results across months to catch a drift before a result reaches its alert or action level. Here each count is also placed on its own sanitization cycle, so faster regrowth between hot flushes, an early sign of biofilm, shows while each result still passes.
The water system plan sets each point's levels and says where they come from: here the action level follows the compendial recommendation, and the alert level was set at half of it. The solution shows that basis beside a data-based level from the point's own flat cycles. A tighter level applies at once, and a looser one needs the QA microbiology lead's signature.
It traces a change in regrowth through change controls, work orders and as-built drawings, and measures a new branch's length against its tube diameter and the plant's own design rule. The investigator sees the branch on the loop drawing with each record that placed it there, and QA microbiology decides the cause.
People do. The agents list each charge drawn from the point with the water result for that charge, or the results either side where none was taken, and the final-active counts. Disposition is the QA head's decision; release to market is for the client's Qualified Person.
Yes, under the quality agreement. After the impact statement is approved, the agents draft the notice from approved record values only, and the QA head decides whether it is sent as drafted.
Every engineer sees what the best batches knew, and each explained difference becomes a watch.
1-min demoYield Loss AnalysisEvery lost tablet traced to the record that explains it, and recurring losses fixed once, on every line.
1-min demoRecurring Loss AnalysisSlow leaks found across four record streams, priced and owned before they become a major deviation.
1-min demoSend one loop's water results for a year, with its sanitization records and recent change controls, and we will lay each point on its cycles and forecast its first alert.