Siedlerstraße 7 | 68623 Lampertheim, Germany

info@zamann-pharma.com

GMP Equipment Qualification Case Study: Fixing Critical URS and Traceability Gaps

Zamann Pharma Support was engaged by a German pharmaceutical manufacturer facing recurring equipment qualification gaps.

The company had extensive IQ, OQ, and PQ documentation. However, EMA inspectors questioned the testing logic, while FDA reviewers could not clearly confirm that the equipment was fit for intended use.

Our assessment found the root cause: incomplete, vague, or missing User Requirements Specifications (URS).

Because URS defines intended use, these weaknesses affected testing, traceability, data integrity, and qualification decisions.

Our team assessed the qualification environment, identified the URS gaps, and defined a remediation approach.

Challenges Faced

A detailed GAP analysis in Quality Management Systems is essential for identifying process deficiencies effectively.
  • Late and Vague URS: The URS was often created too late and lacked measurable requirements.
  • Missing Critical Requirements: CQAs, CPPs, safety, cleaning, and data integrity needs were not clearly defined.
  • Weak Qualification Logic: Unclear URS requirements weakened IQ, OQ, and PQ testing.
  • Poor Traceability: Qualification tests did not always match URS requirements, creating gaps and “N/A” entries.
  • Regulatory Scrutiny: The gaps reflected FDA and EMA concerns around intended use, acceptance criteria, risk, and traceability.
  • Compliance Impact: Risks included FDA 483s, remediation, requalification, and a five-month project delay.

Zamann Pharma Support’s Approach

  • Qualification Assessment: Reviewed intended use, URS, and qualification testing to find recurring gaps.
  • Regulatory Comparison: Compared practices with FDA and EMA expectations for risk, criteria, and traceability.
  • URS Testability Review: Replaced vague wording with measurable, testable requirements.
  • Cross-Functional URS Development: Involved Engineering, QA, Manufacturing, Safety, CSV/Validation, and the vendor.
  • Risk-Based Requirements: Linked requirements to quality, safety, data integrity, and reliability using ICH Q9.
  • Data Integrity Integration: Included audit trails, user roles, backup, security, metadata, and alarm logging.
  • Improved Traceability: Linked URS requirements to measurable IQ, OQ, and PQ tests.
  • Lifecycle Management: Updated URS through change control when systems, products, or risks changed.
  • URS Self-Diagnostic: Used seven checks to classify URS strength as strong, moderate risk, or high risk.

Results Achieved

  • Root Cause Identified: The assessment confirmed that weak URS practices were driving the recurring qualification problems.
  • Qualification Gaps Exposed: The review showed where OQ and PQ testing lacked corresponding URS requirements.
  • Traceability Weaknesses Clarified: The team identified why the traceability matrix contained many “N/A” entries.
  • Regulatory Risks Identified: Linked the gaps to FDA and EMA concerns on intended use, data integrity, and traceability.
  • Remediation Framework Defined: Defined actions for testable URS, risk control, traceability, and change management.
  • URS Value Clarified: Strong URS practices support faster qualification, better control, stronger data integrity, and fewer compliance issues.
Laboratory
GMP qualification and lifecycle validation activities including IQ, OQ, and PQ supporting inspection readiness in pharmaceutical manufacturing.
Services

Qualification and Validation for GMP Systems

Our team supports the planning, execution, and maintenance of qualification and validation activities, including IQ, OQ, and PQ, to keep GMP-regulated systems compliant and under control.

Contact Us

Need help? Don't hesitate to get in touch
Zamann pharma support is committed to protecting and respecting your privacy, and we’ll use your personal information to administer your account and to provide the products and services you requested from us.

FAQ

1. Can equipment qualification remain compliant if the URS was written after equipment purchase?

Creating the URS after equipment purchase, installation, use, or qualification creates a major weakness. The source identified post-purchase URS creation as an FDA inspection concern. It also prevents the URS from guiding equipment decisions and defining intended use before qualification starts.

2. Which data integrity requirements should a URS define before OQ testing?

The source identifies audit trails, access control, backup and restore, electronic signatures, alarm handling, and data transfer validation. It also recommends defining user roles, metadata, raw data preservation, system security, and alarm logging when developing the URS.

3. Why does a vague URS break IQ, OQ, PQ, and traceability?

A vague requirement cannot provide a measurable acceptance criterion. Therefore, qualification tests cannot reliably verify it. This can make IQ unclear, cause OQ to miss critical functions, prevent PQ from demonstrating intended use, and create gaps or “N/A” entries in the traceability matrix.