Genealogy of a sterile fill-finish batch — the dossier your auditor asks for is not reconstructed, it is composed.

The problem

A sterile fill-finish batch is not a process — it is a constellation of systems and people that the dossier has to reconstruct.

A sterile fill-finish batch touches at least five systems and two shifts. When the EMA or FDA inspection arrives, the QA team reconstructs the genealogy by hand, cross-referencing:

1. The pharma MES — which batch was active, which materials went in, which manufacturing order was followed.
2. The BMS / HVAC — what classification the room held at each moment (Grade A/B/C/D), whether there were particle or differential-pressure deviations.
3. Access control — which operators entered the room, in which time window, on which shift.
4. The manual intervention log — the intervention in a Grade A zone, a thousand times over the weakest point of the audit, recorded on paper or on an unfriendly tablet.
5. The preceding CIP/SIP — what cleaning and sterilisation in place was performed before the batch, with what validation.

The QA team knows it. The maintenance team knows it. The plant manager knows it. But between those five systems there are gaps filled in by hand weeks later — and the Annex 1 reviewer knows exactly where to look to find them. A critical observation for incomplete traceability of a manual intervention in Grade A can cost the batch release and leave an inspection report that is hard to close.

How it fits the IRIS system

iLEAN Tracer does not add a sixth system — it seals the cracks between the five you already have.

The problem with sterile fill-finish genealogy is not a lack of data: it is that the data lives on five separate islands and nobody cross-references it at second zero. iLEAN Tracer is the piece of the IRIS category that acts as filler between the MES, the BMS, access control, the shift plan and the intervention log — without asking you to change any of them.

Edge sees the room. Connect reads badge, MES, BMS, shift and interventions wherever they live. The agent composes the signed genealogy. A person signs every critical close — never the other way round.

How the work is split between the iLEAN pieces for this case:

• Edge — a terminal in each critical room (Grade A/B). It reads the sterile zone camera and records the manual intervention event with photo and local timestamp. It works without a network: the event is signed locally and syncs when the network comes back.
• Connect — captures the room access badge, the batch phase from the MES, the live classification from the BMS, the shift planning and the operator's declaration (tablet, earpiece). It also captures what arrives from outside (a procedure review email, an alert from the vial supplier) at second zero.
• Tracer agent — composes the signed event with shift + room + operator + phase + intervention + reason. If the intervention was not authorised for that phase, or the room lost classification during the opening, it leaves the batch "under review" and alerts the QA manager. The person validates — release is never signed on its own.

See the full IRIS architecture →

Before and after

Reconstructed genealogy vs. genealogy composed with iLEAN Tracer

Aspect	Manual post-batch reconstruction	With iLEAN Tracer
MES + BMS + badge cross-reference	QA spreadsheet, weeks	At second zero, automatic
Grade A manual intervention	Paper or unfriendly tablet	Edge photo + voice + badge, signed
Live room classification	BMS curve exported by hand	Cross-referenced with every batch event
Shift + operator	Manual note by the shift leader	Shift plan + badge, automatic
Dossier for EMA/FDA	Weeks of QA, risk of gaps	Self-contained, ready in hours
Critical close signature	Manual, needs coordination	A person signs, the system does not decide alone

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 set it out so the committee has an order of magnitude; we refine it during the diagnostic.

• Pharma plant with 1-3 Grade A/B sterile fill-finish rooms, MES installed, BMS operational, badge access control.
• Tracer pilot in one room (Edge in the cabinet + integration with MES, BMS, badge and shift plan). First value expected within a few weeks: the first genealogy composed at batch close.
• Indicative payback between 4 and 9 months, depending on the documented frequency of batches with an audit observation and the average QA team time spent preparing dossiers.
• Expected reduction in batch dossier preparation time of ≥ 30%. The hard lever is avoiding a critical observation in an Annex 1 inspection over traceability of a manual intervention in Grade A.

And the QA manager's reasonable doubt

"What if the AI introduces noise into the genealogy and the inspection rejects it?" — hallucination is a problem of free generation, not of anchored tasks. Composing an event from MES + BMS + badge + camera is exactly an anchored task, where the best models brought the error below 1.5% ^[1]. And even so, nothing critical is signed on its own: Tracer leaves the batch "under review" and the person signs. The three iLEAN security rings are designed precisely so the OT network only accepts what has been validated, packaged, signed and approved by a person.

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