Eén interface.
Vijf agents.

Not October 20. October 23 holds, if the binder is ordered today.

1. MaterialSO-25 needs 42 kg of binder B-30. Stores hold 24 kg, so 18 kg is short until the open order lands. Ordering 20 kg covers the gap with a small buffer.
2. CapacityRMG-150 is booked for PLN-12 until October 18. PLN-13 can take the granulator from October 19 without moving anything else.
3. ReleaseQC usually needs two and a half days for this product, so packing on October 21 means release on October 23.

I checked SO-25 against stock, open purchase orders, the RMG-150 booking and your usual QC turnaround. Only the binder and the granulator slot stand in the way. Everything else is ready for October 20.

Four lots. Two can still be used if they move up the plan.

1. Expiring stockLOT-2291 and LOT-2304 expire before the plans that use them. PLN-13 runs next week and needs both materials, so moving them in uses both in time.
2. RetestLOT-2187 needs a retest by Thursday. Without a QC slot it is blocked from issue on Friday, and PLN-14 depends on it.
3. QuarantineLOT-2312 has waited six days for sampling. The request is assigned to QC but not started.

I compared every lot's expiry and retest date with the plans that will use it, and each lot's time in quarantine with your usual wait. Moving the two expiring lots into PLN-13 saves both from being written off.

One cause. Filling line FL-03 ran two batches after its calibration was due.

1. What changedFL-03 passed its calibration date on October 1 and still ran on October 2 and October 3.
2. What it affectsBoth batches were filled on FL-03. Their fill weight and seal checks are in limits, but the equipment record is not.
3. What holds the scoreGAP-0040 stays open until an impact assessment is signed for both batches. Recalibrating FL-03 alone will not close it.

Readiness fell on October 2, the first day FL-03 ran past its calibration date. Nothing else in the unit changed this week, so the score will not recover until both batches are assessed.

Yes. Once, in March, on the same line and for the same reason.

1. The patternBoth deviations were on FL-03, and both started with a calibration reminder that nobody acted on.
2. Why the fix did not holdCAPA-0034 sent the reminder to one supervisor. That supervisor moved to Line 2 in August, and the reminder went with them.
3. What would holdA missed calibration should block the line in Factro, instead of relying on someone reading a reminder.

I matched DEV-0447 against every deviation on FL-03 and every CAPA linked to calibration. The March fix depended on one person seeing a reminder. This time it went to the wrong person, so the root cause was never really closed.

Two of the eleven in the queue. The other nine have clean evidence.

1. ReadyNine batches have complete records, results in limits and no open events. They can be reviewed today.
2. HeldBID-0008-09-25-01 and -02 were filled on FL-03 during the calibration gap. DEV-0447 is still open against both.
3. Your decisionPrism prepares the review pack and points to the evidence. Release still needs an authorised QA signature.

I read the batch record, test results and open deviations for every batch in the queue. The two held batches have results in limits, so the impact assessment is the only thing standing between them and release.