GAMP 5 validation:
Will your inspection system pass the next audit?

An inspection system in pharmaceutical production has to do two things: inspect reliably – and prove that it inspects reliably. The first takes engineering. The second takes a validation according to GAMP 5 that stands up in the audit.

In practice, validation is not decided at acceptance. It is decided when the system is selected. Anyone who buys an inspection system that is delivered without a specification, without a risk assessment and without test documentation starts validation from zero.

INTREX develops inspection and marking systems for regulated production environments according to GAMP 5 and Annex 11 from the very beginning. From the user requirements specification (URS) through to performance qualification (PQ). Engineering, software and validation from a single source.

Datenintegrität-GMP-Intrex-Deutschland-3

What is GAMP 5 – and why does it matter so much for inspection systems?

GAMP 5 stands for “Good Automated Manufacturing Practice” and is the ISPE (International Society for Pharmaceutical Engineering) guide for validating computerized systems in a GxP environment. The current Second Edition was published in July 2022.

GAMP 5 is not a law. It is well known, however, that inspectors use the guide as a benchmark nonetheless – together with Annex 11 of the EU GMP Guide and, for the US market, 21 CFR Part 11. Anyone who validates according to GAMP 5 speaks the same language as the authority during an audit.

This is particularly relevant for inspection systems on the line. Camera systems, code readers and inspection stations make GMP-relevant decisions: good or bad, reject or release.

That makes them computerized systems within the meaning of Annex 11 – and they must be validated just as traceably as a LIMS or an MES.

Which basic principles are behind GAMP 5?

GAMP 5 follows a small number of consistent principles:

  • 01 Risk-based approach

    The validation effort is based on the risk to patient safety, product quality and data integrity.

  • 02 Lifecycle thinking

    Validation starts with the concept and ends only with decommissioning.

  • 03 Specification and verification

    Every requirement gets a matching piece of evidence.

  • 04 Supplier involvement

    The manufacturer’s documentation and tests can be used for validation.

  • 2nd Edition 05 Critical thinking

    The Second Edition puts critical thinking first. Not more paper, but better evidence.

Which software categories does GAMP 5 distinguish?

GAMP 5 classifies software into categories. They help to scale the validation effort:

  • 1
    Category 1 – Infrastructure software

    Operating systems, databases, network components.

    Validation effort
  • 3
    Category 3 – Non-configured products

    Standard software that is used without modification.

    Validation effort
  • 4
    Category 4 – Configured products Inspection systems

    Standard software that is adapted to the process via parameters.

    Validation effort
  • 5
    Category 5 – Custom software Inspection systems

    Individually developed applications and inspection logic.

    Validation effort

The former Category 2 (firmware) is no longer used.

Important: The category alone does not determine the scope of testing. What matters is the risk of the specific function in the process.

Inspection systems with their own software logic typically fall into Categories 4 and 5. This is exactly where the effort is greatest – and where clean manufacturer documentation is most valuable.

How does a validation according to GAMP 5 work?

The best-known tool of GAMP 5 is the V-model. The specifications are on the left, the matching tests on the right. Every specification has its counterpart in verification.

  1. Validation plan

    Scope, responsibilities and approach are defined.

  2. User requirements (URS)

    What must the system deliver – technically, from a regulatory view, and at line speed?

  3. Risk assessment

    Which functions are GMP-critical, and where are the sources of error?

  4. Design qualification (DQ)

    Does the planned design meet the requirements?

  5. Installation qualification (IQ)

    Is the system installed correctly and documented?

  6. Operational qualification (OQ)

    Do all functions work as specified – including limit and error cases, audit trail and access rights?

  7. Performance qualification (PQ)

    Does the system meet the requirements in the real production process?

  8. Validation report and release

    Results, deviations and release for GMP operation.

Traceability via the traceability matrix

Traceability between requirement and test result is ensured through a traceability matrix. After release, change control and periodic review keep the system in its validated state.

Why is more paper not automatically more safety?

A common misunderstanding: GAMP 5 supposedly demands documentation that is as extensive as possible. The opposite is true. Risk-based means differentiating, not reducing. Less effort where the risk is low. Deeper tests where critical inspection decisions are made.

For a camera system this means: the user interface needs different evidence than the inspection logic that decides whether a vial is rejected. Anyone who takes this into account at the specification stage saves time in qualification – and has better answers in the audit.

Test depth by risk – example camera system
User interfaceLow risk
Lean evidence
Inspection logic: vial rejectionGMP-critical
In-depth tests incl. limit and error cases

What does GAMP 5 look like using a code inspection as an example?

Take an inline inspection that reads data matrix codes on folding cartons and rejects faulty packs. The URS states which codes are read, which read quality is required and what happens in the event of a read error. The risk assessment shows: what is critical is not the camera, but the decision logic and the reliable rejection.

In the OQ, testing is therefore carried out specifically with faulty patterns: unreadable codes, wrong content, missing codes. In the PQ, the system runs under real conditions at production speed. Every test case is assigned to a requirement via the traceability matrix. This turns an inspection that works into an inspection that demonstrably works.

Practical example: data matrix inspection
  1. URS Define requirements

    Which codes, which read quality, what happens in the event of a read error?

  2. RISK Identify what is critical

    Decision logic and reliable rejection, not the camera.

  3. OQ Test with faulty patterns
    unreadablewrong contentmissing
  4. PQ At real production speed

    Proof under real conditions on the line.

Every test case ↔ one requirement (traceability matrix)

Why is an inspection system developed for GAMP 5 worthwhile?

Because validation is then no longer a downstream project, but part of the solution. It is well known that a large part of the validation effort arises when documentation is missing or has to be created after the fact. A system delivered without a specification causes exactly this effort.

An inspection system that was developed according to GAMP 5 and Annex 11 from the start brings the evidence with it:

  • Shorter qualification

    Specifications, risk assessment and test protocols are available when the system goes onto the line.

  • Audit readiness

    Inspection parameters, results, events and system states are documented traceably.

  • Data integrity

    Audit trail, user management and change control are part of the software logic, not added afterwards.

  • Planning certainty

    Your quality assurance knows early on which evidence is coming and how it fits together.

  • Process reliability

    Reproducible inspection decisions reduce scrap, downtime and recall risk.

AI-assisted inspection

Does GAMP 5 also apply to AI-assisted inspections?

Yes – and this is where it gets more demanding. AI models make inspection decisions based on trained patterns. For these decisions to remain validatable, the model version, training and test data and acceptance criteria must be controlled just like classic inspection rules.

INTREX therefore implements AI-assisted image processing according to GAMP 5 and Annex 11 and additionally takes the draft EU GMP Annex 22 into account: static, versioned models, separate training and test data, predefined acceptance criteria and logged confidence values.

Draft EU GMP Annex 22 This is how AI stays validatable
  1. Static, versioned models
  2. Separate training and test data
  3. Predefined acceptance criteria
  4. Logged confidence values

How does INTREX support your GAMP 5 validation?

INTREX is not a validation consultant. We are the manufacturer that delivers an inspection system that can be validated – with the documentation your quality assurance needs for it.

What exactly does INTREX deliver?

  1. Design
    System design based on your URS

    The inspection task, requirements and risk analysis according to Annex 11 and GAMP 5 form the basis of the design.

  2. Software
    GAMP 5-compliant software logic

    With our own image processing software KUPvision, inspections are controlled, results are logged and data is passed via interfaces to MES, ERP or higher-level systems.

  3. Data integrity
    Audit trail and access rights

    Changes to inspection parameters are traceable, and user roles are clearly separated.

  4. Documentation
    Qualification documentation

    DQ, IQ, OQ and PQ protocols based on your user requirements, implemented in accordance with Annex 11.

  5. Integration
    Line integration

    Mechanical, electrical and software integration into your existing production.

  6. Operation
    Operation across the lifecycle

    Change control, remote maintenance and spare parts supply, so that the system stays in its validated state.

Which systems does this apply to?

To the computerized systems that INTREX develops for regulated production environments: inline inspection and vision systems, code reading including 360-degree inspection on round containers, AI-assisted glass breakage inspection, as well as marking, serialization and tamper-evident solutions. We integrate proven components into our solutions – for example cameras from Cognex and printers or lasers from Domino.

Where does INTREX come in – and where not?

So that you know where you stand: INTREX does not validate third-party IT landscapes and does not offer CSV consulting, training or audits for ERP, LIMS or MES systems. Our contribution begins and ends with the inspection and marking systems that we develop and deliver ourselves. There we take on the technical responsibility – in full.

30+Years of experience

What sets INTREX apart from standard providers?

Large providers come with product catalogs. INTREX starts with the inspection task. With more than 30 years of experience, we combine engineering, industrial image processing, in-house software development and pharma validation. Direct access to experts, short paths, one contact for hardware, software and documentation.

Which questions do pharma manufacturers ask about GAMP 5 validation?

Is GAMP 5 required by law?

No. GAMP 5 is an ISPE guide, not a legal standard. The binding requirements are regulatory ones such as Annex 11 or 21 CFR Part 11. However, GAMP 5 is regarded as a recognized standard for meeting these requirements in a traceable way.

Qualification (DQ, IQ, OQ, PQ) proves that a system is correctly designed, installed and functional. Validation goes further and covers the entire lifecycle – from planning through to operation in a validated state.

Typically a validation plan, URS, risk assessment, specifications, DQ, IQ, OQ and PQ protocols, traceability matrix and validation report. INTREX supplies the system-related documents; the validation plan and release remain with your quality assurance.

Responsibility lies with the regulated company. However, GAMP 5 explicitly provides for including supplier documentation and tests. The better the manufacturer documentation, the less effort you have yourself.

Every change goes through change control. This assesses whether and to what extent requalification is necessary. For AI models, this also applies to every new model version.

GAMP 5 and data integrity belong together. A validated system must capture data completely, traceably and unalterably – in line with the ALCOA+ principles. Audit trail, user management and data backup are therefore a fixed part of every specification and every OQ.

How do you start your GAMP 5-compliant inspection project?

It starts with your inspection task – and your URS. Which product, which defect types, which line speed, which documentation requirements?

URS available If you already have a URS, we will review it together.
No URS yet If you do not have one yet, we will clarify the requirements in the first conversation.

Whether it is a new inspection system or an extension of an existing line: together we define which functions are GMP-critical, which evidence you receive from us and how it fits into your validation concept. This way your quality assurance and your production know where they stand from the very beginning.

Talk to our experts about your critical inspection task. We will show you how your inspection system becomes validatable from the start.