OdysseyGPT

Standards explainer

GAMP 5 for equipment suppliers: software categories, specifications and what to check in a URS

What GAMP 5 means for a maker of automated process equipment answering a customer's User Requirement Specification: your role as supplier, how your software is classed, and the documents and tests you are asked for.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

GAMP 5 is ISPE's guide to a risk-based approach for computerised systems in regulated (GxP) environments. It is a guide, not a regulation. For an equipment supplier it shapes what the customer's URS asks for: a software category for the control system, a set of specifications, documented supplier testing and evidence of a sound quality system.

Key Takeaways

  • GAMP 5 is good-practice guidance from ISPE. It applies to you when the URS or contract calls it up.
  • The regulated company stays responsible for validation. The supplier provides documents and test evidence it can rely on.
  • Software is placed in categories 1, 3, 4 and 5. The category drives how much documentation and testing is expected.
  • Custom control code attracts the most: design specifications, code review and structured testing.
  • Agree the category and the document list at bid stage. Changing them after award is expensive.

See how OdysseyGPT reviews a tender. Tell us how your team reviews tenders today. We can walk through an example together. Book a call

What is GAMP 5?

GAMP stands for Good Automated Manufacturing Practice. GAMP 5 is a guide published by ISPE, the International Society for Pharmaceutical Engineering, with the full title "A Risk-Based Approach to Compliant GxP Computerized Systems". The second edition was published in July 2022. ISPE describes it as a framework of good practice to make sure computerised systems are effective and of high quality, written for regulated companies, suppliers and regulators.

It is not a regulation and no authority issues a GAMP certificate. The legal requirements sit elsewhere, for example in EU GMP Annex 11 on computerised systems and in the US rule on automatic, mechanical and electronic equipment, 21 CFR 211.68. Drug manufacturers use GAMP 5 as their method for meeting those requirements, and they pass parts of it to suppliers through the URS and the contract.

The supplier's role under GAMP 5

The drug manufacturer, the regulated company, stays responsible for showing that a system is fit for its intended use. GAMP 5 encourages that company to make full use of supplier knowledge, experience and documentation where it can, and ISPE says the second edition gives more weight to service providers. ISPE's description counts equipment makers among suppliers, alongside software, hardware, system integration and IT service providers.

The customer can only rely on your documents and tests if it can show they are trustworthy. EU GMP Annex 11 says the regulated user should take reasonable steps to confirm a system was developed under an appropriate quality management system, and that the supplier should be assessed appropriately. In practice that means a supplier questionnaire or an audit, and URS lines about your quality system, your software development procedures and your change control.

  • What you do: design and build to the URS, write the specifications, test the system and record the results.
  • What the customer does: assess you as a supplier, review and approve your documents, decide how much of your testing it can reuse, and carry out its own qualification.
  • What the URS response must make clear: which documents and tests are in your standard scope and which are extra.

Software categories and what they mean for your equipment

GAMP 5 sorts software into categories by how much it is configured or custom-built. The category guides how much specification and testing is expected. Four categories are in use. Category 2, once used for firmware, is no longer used.

GAMP 5 software categories (own summary; the equipment examples reflect common practice and the customer's classification governs)
CategoryWhat it isOften applied to on a process skidWhat the customer tends to ask for
1Infrastructure softwareOperating systems, database engines and similar platform softwareA record of what is installed and its version
3Non-configured productsStandard devices and packages used as supplied, with only run-time parameters setVersion and parameter records, and tests against the user requirements
4Configured productsStandard control or SCADA and HMI packages configured for the project without custom codeA configuration specification, and risk-based testing of the configuration
5Custom applicationsControl code written for the project, such as bespoke PLC logic and custom scriptsFunctional and design specifications, code review and structured testing through the life cycle

One control system often spans several categories: a standard operating system, a configured visualisation package and custom logic. A URS that states a single category for the whole system is worth a clarification. So is a URS that gives none, because the customer may later ask for category 5 documents on software you priced as a standard product.

Specifications the supplier is asked for

GAMP 5 is often drawn as a V. Specifications run down one side: user requirements, then functional specification, then design specifications. Verification runs up the other, with each level of testing checking one level of specification. ISPE says the approach is not inherently linear and also supports iterative and incremental development. For equipment, the customer writes the URS and the supplier usually writes the rest.

Documents a URS commonly asks an equipment supplier for (own summary; names and scope vary by customer)
DocumentWhat it saysWho usually writes it
Quality and project planHow the project will be run, documented and testedSupplier
Functional specificationWhat the system does, in answer to each user requirementSupplier, approved by the customer
Hardware and software design specificationsHow the system is built: architecture, modules, interfaces, I/OSupplier
Configuration specificationThe settings chosen in configurable productsSupplier
Traceability matrixLinks each user requirement to the specification and the test that covers itSupplier, customer or both
Test specifications and reportsModule, integration and acceptance tests, with resultsSupplier, often witnessed at the FAT
Code review recordsEvidence that custom code was reviewed against standardsSupplier
Version, backup and change control recordsWhat was delivered, and how changes are controlledSupplier

Testing the supplier is asked for

Customers want to reuse supplier testing rather than repeat it. EU GMP Annex 15 allows documentation review and some tests done at the FAT to stand without being repeated at IQ or OQ, where that is appropriate and justified and transport and installation do not affect the function. That only works if your test records meet the customer's standard: approved protocols, expected results stated before the test, signed and dated entries, calibrated instruments and recorded deviations.

  • Software module and integration testing before the FAT, with records.
  • Factory acceptance testing of the hardware and software together, against an approved protocol. See FAT vs SAT.
  • Site acceptance testing after installation.
  • Tests of alarms, interlocks, access control, audit trail, data backup and recovery, where the URS asks for them.
  • Support for the customer's IQ and OQ, sometimes by supplying draft protocols.

What to check in a tender or URS against GAMP 5

GAMP 5 requirements to check before you quote
CheckWhy it matters
Which edition of GAMP 5 the URS names, and any ISPE good practice guides it addsThe second edition differs from the first, and each extra guide adds expectations
The software category the customer assigns to each part of the control systemThe category sets the documents and tests, and so the engineering hours
The list of life cycle documents, and which need customer approvalEach approval round adds time before you can start building
Whether custom code is expected, or the customer's standard libraries must be usedUsing customer libraries changes the category mix and the test effort
Code review, coding standards and the evidence requiredNot every maker keeps formal code review records as standard
Traceability matrix: who owns it and in what formatBuilding it at the end from finished documents is slow and error-prone
Supplier assessment: questionnaire, remote audit or site audit, and whenAn audit before award can decide the bid, and findings need closing
Test record standards for the FAT and SAT, including witness and review periodsRecords that fall short cannot be reused in qualification
Audit trail, electronic records and signature requirements, and the regulation namedThese can need a different HMI or SCADA package or licence
User access levels, password rules and time synchronisationOften set by the customer's IT standards, which differ from your default
Backup, restore and disaster recovery testsExtra test steps at the FAT or SAT
Change control after the FAT, and who approves changesLate software changes can force a retest
Whether you supply IQ and OQ protocols, execute them, or only supportA large difference in scope that is easy to leave unpriced

OdysseyGPT's Document Review checks the URS and the customer's automation and documentation specifications against your own functional specification, standard document list and quality plan. It drafts the compliance matrix and the deviations and clarifications list, with a quote from both sides on each row. The Customer Specification Review (beta) lists the documentation and test requirements in the package, each with its clause.

Where OdysseyGPT falls short

  • It is not validated software under GAMP 5, and we do not offer it as a GxP system. Its output is a draft for your engineers to check.
  • It does not perform computerised system validation, write test scripts or execute tests.
  • It does not classify your software. It reports what the URS says about categories and what your documents say, with quotes.
  • It does not hold a copy of GAMP 5 and does not judge your documents against the guide. It compares the documents you upload.
  • It does not read source code, PLC programs, P&IDs or other drawings.
  • It does not replace a validation lifecycle system or a quality management system. See equipment qualification software compared.

Talk through your tender review

See how OdysseyGPT reviews a tender

Tell us how your team reviews tenders today. We can walk through an example together.

Book a call

Frequently asked questions

What is GAMP 5?

GAMP 5 is ISPE's guide to a risk-based approach for compliant GxP computerised systems. The second edition was published in July 2022. It is good-practice guidance for regulated companies and their suppliers, not a regulation.

What are the GAMP 5 software categories?

Category 1 is infrastructure software. Category 3 is non-configured products. Category 4 is configured products. Category 5 is custom applications. Category 2, once used for firmware, is no longer used. The higher the category, the more specification and testing is expected.

Is GAMP 5 mandatory for equipment suppliers?

Not by law. It is guidance. It becomes a contract requirement when the customer's URS or purchase order calls it up, which is common for automated process equipment sold to drug manufacturers.

Can a supplier be GAMP 5 certified?

No authority issues a GAMP 5 certificate for a company or a product. A supplier can state that it follows GAMP 5 and show the procedures and records behind that statement. The customer checks them through supplier assessment.

Is PLC code GAMP category 5?

Control code written for one project is commonly treated as category 5, custom software. Standard, configured function blocks or libraries may be treated differently. The customer decides the classification, so agree it at bid stage.

Who is responsible for validation, the supplier or the customer?

The regulated company. The supplier provides specifications, test records and support. The customer assesses the supplier, decides how much of that evidence it can rely on and performs its own qualification.

References

ISPE GAMP 5: A Risk-Based Approach to Compliant GxP Computerized Systems (Second Edition)

ISPE

Paid guide, published July 2022. ISPE's description read 15 Nov 2026.

Visit source

EudraLex Volume 4, Annex 11: Computerised Systems

European Commission

2011 text, sections on user requirements and supplier assessment. A draft revision was published in 2025; check the current version.

Visit source

EudraLex Volume 4, Annex 15: Qualification and Validation

European Commission

Sections on FAT, SAT, IQ and OQ.

Visit source

21 CFR 211.68: Automatic, mechanical, and electronic equipment

US Food and Drug Administration, via eCFR

Visit source

What is GAMP 5?

Kneat

Public summary of the software categories and the V-model.

Visit source

Related Pages