SystemMulti-Site Manufacturing

Lessons Learned Across Sites

A lessons learned system for multi-plant manufacturing: one investigation's root cause lifted to a general pattern, each machine's limits read against its validation report, and each plant's answer held to its own records.

Follow one alarm-limit lesson to all four plants ↓
Watch with transcript →
The problem

The CAPA covered three granulators, and a freeze dryer had the same weakness

An investigation finds why a batch went wrong, and the CAPA fixes that machine and, at best, its sister machines. The general cause behind it, such as a software update that quietly widened a validated alarm limit, can sit in a dryer, a filler or a freezer that looks nothing like the machine that failed.

When a lesson memo goes round, the easy reply is that it does not apply, and nothing proves the plant looked. Some plants compare against the equipment qualification range, which is wider than the product's validated range and hides the gap. Replies drift for weeks, and nobody signs that all of them have answered.

Built forHeads of qualityQA systems leadsSite quality leadsAutomation leads

The Problem Today

A fix stays on the machine that failed, while other plants reply with an opinion and nothing attached.

164
FDA 483 citations of 21 CFR 211.192, fiscal 2025 published

Pulled together per lesson

  • Root causes
  • Changes
  • Settings
  • Validation
  • The lesson ends at the sister machinesA freeze dryer does not hear what a granulator taught
  • Not applicable, with nothing attachedNo record shows the plant opened its own register

The Solution

  1. The cause becomes a patternLifted until it reaches machines of any kind that could fail the same way
  2. Each machine read before anyone is askedConfigured limits set beside the product's validated range
  3. Each plant answers in fixed fieldsAn answer its own document contradicts goes back to the plant
  4. Closed by the head of qualityOnly once all plants are accepted and each document was opened

Built-in controls

  • Each plant answers only for itself
  • Whoever wrote a lesson cannot close it
  • Control systems are read, never written

What You Get

Inspectors and clients can follow each plant's answer to the configuration export and validation report behind it.

  • Gaps found on unlike machinesA lyophilizer caught by a granulator's root cause
  • A lesson becomes a standing checkLater control software changes run it, once approved
  • Limits kept beside validated valuesReusable at the next audit, plant by plant
Features

Lessons learned features that carry one root cause to four plants

A granulator ran past its validated torque and no alarm sounded, because a software update had set the alarm limit higher. The QA systems lead turns that root cause into a lesson for four plants, and each plant's quality lead answers it.

demoPlants, clients, people, machines and records shown here are sample data.

  1. 01Abstraction ladder

    Root cause lifted to a general failure pattern, each rung cited

    • Four rungs, each with its source. What happened, why, the general pattern and where it can live each open the deviation, investigation or change record they came from.
    • Only the approved root cause is lifted. A local cause, such as a worn seal, is marked as staying with its CAPA, so the lesson carries only what applies elsewhere.
    • Nothing shown before the run. The pattern and the pre-check are blank on a fresh lesson; they fill as the agents read the records, so nobody reads a verdict before it exists.
  2. 02Inspector's questions

    Extent of condition widened by an inspector's question

    • Scope widened past the sister machines. Asked about the other machines whose limits sit in control software, the lesson grows from three granulators to all such machines at all four plants.
    • A wrong comparison caught. One plant's checker had compared a freeze dryer with its equipment tolerance; the challenger sends it back to the product's validated range.
    • Panel access left for a person. Whether an operator account can edit an alarm limit at the panel goes to the automation lead, answered per plant in fixed fields.
  3. 03Machine configurations

    Alarm and interlock limits read against each product's validation report

    • Configuration exports read first. Each machine's software version, last change and limits are set beside the report that validated them, before any plant is asked.
    • Product range, not qualification range. The comparison basis is locked to what the product was validated at, so a machine's wider capability cannot hide a gap.
    • Narrowed to one plant or client. A site quality lead can narrow the table to their own machines and to one client's products.
  4. 04Post

    A lesson posted to each plant with fixed answers and a reply clock

    • Four answers, each with its evidence. Gap found needs the deviation or CAPA, no gap needs the configuration exports, does not apply needs the equipment register, already fixed needs the change record.
    • Posting waits for the pre-check. The QA systems lead cannot post until the agents have read all four plants, so no plant is asked a question without the evidence in front of it.
  5. 05Proposed cover

    A plant's answer held while the CAPA it rests on awaits approval

    • Send locked until the record is opened. The plant's quality lead attaches the plant's own CAPA and must open it before the answer can go.
    • Unapproved actions are proposed cover. A CAPA plan the review board has not approved cannot clear a plant or a lesson, and once approved the machine still reads as an open gap the CAPA owns.
  6. 06Sent back

    Does not apply refused when the plant's own register says otherwise

    • The plant's own register, opened. The plant with no granulators attaches its equipment register, and the reply checker reads it against the pre-check.
    • A stated reason, and the clock keeps running. The answer goes back with the machines that hold limits in software named, so the plant answers again from evidence instead of opinion.
  7. 07Finding

    Configuration export, validation report and change record side by side

    • Three documents, each opened in full. Confirm stays locked until the plant's QA head has read the export, the validation table and the change record, so the confirmation rests on what was read.
    • The change that set it, named. The change record shows the patch was verified on screens and reports while recipe alarm values went uncompared, which is the lesson's pattern.
  8. 08Deviation

    A confirmed gap opened as its own deviation in the QMS

    • Fields come from the records read. Equipment, limits, the change and the cycles run since are carried over, and nothing is typed into the deviation by an agent.
    • Classification is the plant's call. The QA head picks major or minor, and the deviation owner tells the client as its quality agreement asks.
  9. 09Closure

    Lesson closure that waits for every plant's accepted answer

    • All answers accepted before signing. Closure stays locked while any plant is waiting, held or refused, so a closed lesson means each plant has shown its records.
    • Each plant's evidence opened by the signer. The head of quality opens each document before signing, and reopening any answer later clears the signature.

Four plants answer a lesson, and only the head of quality can close it

One person runs the lessons program, a quality lead answers for each plant, and a different person closes each lesson.

QA systems leads

Turn approved root causes into lessons, post them and chase the replies

  • A pattern written from the investigation
  • Each plant pre-checked before posting
  • Reminders and escalation that run themselves
Site quality leads

Answer each lesson for their own plant, with their own records

  • Their plant's machines already read
  • Fixed answers instead of a memo
  • A gap opened as a deviation in the QMS
Heads of quality

Close lessons and approve standing checks and loosened settings

  • Each plant's evidence to open before signing
  • Lessons that close only when all plants answered
  • Standing checks that wait for approval
Automation and control systems leads

Hold configuration exports and access matrices across plants

  • Panel access questions answered per plant
  • Exports read without a write to any controller
  • Software changes flagged for limit comparison

The reply checker may refuse on evidence but cannot accept typed text

Each agent proposes or checks; a named person posts, answers, confirms, approves and closes.

Lesson generalizer

Starts at the investigation's approved root cause, climbs to the general pattern and names the machines where it can live.

  • Lifts no cause the investigation did not approve
  • Opens no record outside manufacturing and quality
  • Posts nothing
Inspector challenger

Tests the draft lesson's scope, and the agents' pre-check, with the questions an investigator would put.

  • Edits no lesson
  • Leaves open points to a named person
Configuration checkers

One per plant: reads each machine's configuration export against the product's validation report and the change record.

  • Changes no setting
  • Compares against no qualification range
Thread poster

Sends the structured request to each plant once the lessons lead posts, keeps the clocks and sends reminders.

  • Answers for no plant
Reply checker

Checks each reply carries the plant's own document, opened, and compares it with the pre-check.

  • Takes no typed sentence as evidence
  • Closes no lesson
Standing check keeper

Turns an approved pattern into a check on future control software changes, and learns from rulings.

  • Applies nothing without the quality head's approval
More screens

One plant's unproven no aggregation cameras reply became the checker's rule

The answers that passed, the memory the agents keep, and the queue, library, trail and settings around a lesson.

A plant cleared on its own comparisonThe second plant attaches its engineering team's limit comparison; it shows all 9 machines matching their validation reports, and the reply checker accepts it.
Standing checks and the reply checker's rulesEarlier lessons already run as checks on change controls; this lesson's check is proposed, and a learned rule says does not apply needs the equipment register extract.
Replies due, overdue firstEach open plant reply across four lessons, with business days late, automatic reminders and escalation to the plant head shown row by row.
Lessons learned library, searchable by patternEach past lesson by its pattern, the plant it came from, how many plants answered and how many machines it found elsewhere.
Answers, refusals and confirmations in the order madeWho answered for each plant, which agent accepted or refused and why, and the session behind each entry; the lesson's evidence pack downloads from here.
Settings that drive the clock and the checkerReply clock, reminder day, escalation and the evidence each answer needs; the comparison basis and who closes a lesson are locked by procedure.

demoSample data, from the working solution.

A plant's no stands only on its own register, and the author never signs

Closing a lessonThe head of quality closes it after opening each plant's evidence; whoever wrote or posted the lesson is refused.
Answering for a plantEach site quality lead answers only for their own plant, and another plant's reply box is read-only.
Confirming a gapThe plant's QA head confirms after opening the export, the validation report and the change record, then opens the deviation.
A standing check or a looser settingBoth wait on the head of quality's signature, and nobody signs a change they asked for.
Batches run since a changeThey belong to the deviation's impact assessment; the lesson draws no conclusion about them, and the assistant names who decides on held product.

Configuration exports are read, and no controller is written to

Approved investigations, deviations and CAPAsFrom the QMS, read for the approved root cause and the records it names.
Change controlsWhat each software change verified, and what it left out.
Control system configuration exportsAlarm and interlock limits per machine and recipe, read without any write back.
Validation and qualification reportsThe product's validated range, from the document management system.
Equipment registers and access matricesWhich machines each plant holds, and who can edit a limit at the panel.

Questions quality leaders ask about lessons learned across plants

What is lessons learned in pharmaceutical manufacturing?

Lessons learned turns what one investigation found into a check other plants must answer. Here the approved root cause is lifted to a general pattern, each plant's machines are read against their validation reports, and each plant answers with its own records; only then can the quality head close the lesson.

How is this different from a CAPA extension to sister equipment?

An extension looks for the same cause on the same kind of machine. A lesson is lifted to the pattern behind the cause, so it reaches a freeze dryer or a filler that holds a limit in software the same way a granulator does.

What does extent of condition mean for a multi-site CAPA?

It is the question of where else a cause found once can exist. The agents answer it from configuration exports and validation reports before asking, and each plant confirms or rejects their reading with its own evidence.

Which rules does a lessons learned program help meet?

FDA's investigation rule asks that an investigation extend to other batches and other drug products that may be tied to the failure, and EU GMP asks for computerized system configuration changes made in a controlled manner. ICH names knowledge management as an enabler of the quality system. The controls are designed for these; your quality unit decides compliance.

Can a plant answer that a lesson does not apply?

Yes, with its own equipment register extract attached and opened. If the register lists machines where the pattern can live, the answer is refused with that reason and the clock keeps running.

Does it change settings on our control systems?

No. Configuration exports are read only. A gap becomes a deviation or CAPA owned by the plant, and any change goes through that plant's change control.

Bring the root cause you
fixed on one machine.

Send one approved investigation and your plants' configuration exports, and we will show where else its pattern lives.