DeCaris2007 RiskBasedEquipQual
DeCaris2007 RiskBasedEquipQual
DeCaris2007 RiskBasedEquipQual
PHARMACEUTICAL ENGINEERING
holistic risk-based
approach covering
business, safety,
and quality risks
involvement of
the supplier in the
risk management
process and risk
analysis
support from the
supplier in the
C&Q activities
(risk-based)
team building
time savings
trends
good engineering
practice
Figure 1. Standard
equipment development
Life Cycle.
www.ispe.org/PE_Online_Exclusive
GAMP Francophone).
The Equipment Validation Group is the first
working group started within GAMP Italia and
is composed of members coming from equipment manufacturers, consultants, end users
(pharmaceutical companies), and academia.
The group is currently preparing document
templates useful for supporting qualification of
different standard and non-standard equipment.
Background
Most equipment currently available on the
market is the result of a very long and uninterrupted improvement process that started many
years ago and brought to the current design.
There is a significant difference between the
purchase of a standard system, as opposed to
the development of a bespoke or custom
made
equipment.
Pharmaceutical users
in most cases are just
buying and installing
standard pieces of
equipment. The design
of new parts or new
functionality is often
negligible, or limited to
a small part of the process. Nonetheless, users are currently spending significant human
efforts and financial
resources in commissioning and qualification activities that are
sometimes excessive
and redundant, quite often including a mere
repetition of verifications already performed
by the manufacturer.
Equipment Categories
To simplify the management of equipment qualification/
www.ispe.org/PE_Online_Exclusive
Basic Concepts
Good practices help ensure high quality products.
Properly designed and manufactured products are safe, robust and reliable, well documented; therefore, they should be
easy to qualify and/or validate.
This is true for both pharmaceutical products and the equipment used to manufacture the products.
Safety
Business
Business Aspects
In this case, what matters is the evaluation of the potential
damage for the business caused by system malfunctions or
lack of availability. The business hazard impact can be
evaluated according to:
cost of components to be replaced and workmanship (direct damage)
Risk Analysis
The results of the analysis depends largely on the impact that
the customer assigns to each identified source of risk. The
same function could be potentially critical in a specific application and non-critical in a different one. Cooperation between customer and supplier is essential to properly manage
risks.
www.ispe.org/PE_Online_Exclusive
User Requirements
To properly implement a holistic risk-based approach, it is
necessary to start defining critical items from the beginning
of the process. The user should provide the supplier with the
identification of different hazards (quality, safety, and business) and the relevant impact evaluation.
The following are some specific suggestions:
The User Requirements Specification (URS) should be
treated as a contractual document, avoiding conflicts with
other technical specification documents. The URS should
not be considered a mere part of the validation documentation, but rather the main - and possibly only - specification document for the equipment.
Ideally, the requirements should be independent from the
suppliers product and express customer needs without
addressing specific design solutions.
MAY/JUNE 2007 PHARMACEUTICAL ENGINEERING On-Line Exclusive
www.ispe.org/PE_Online_Exclusive
Detailed technical requirements which are typically produced by the user may be included if appropriate in an
annex of the URS, as this document usually specifies
design solutions rather than equipment performances.
Ideally, all requirements should be identified with a unique
code for easy and unambiguous traceability and classified
according to the impact. If possible, impact should be
defined in more than one level (e.g., high/medium/low).
Business requirements should be classified according to
their priority (e.g., mandatory or nice to have.)
Generic requirements like the software shall be 21 CFR
Part 11 compliant should be avoided. High level identification of GxP critical data which are expected to be
handled by the system should be done at this stage of the
process.
The main issue for the customer during the requirement
phase is to identify the most appropriate supplier and the
most appropriate equipment model that can satisfy all the
requirements.
Validation Plan
The Validation Plan should be developed by the user considering the actual life cycle of the manufacturer that changes
significantly depending on the amount of design activities
Supplier Maturity
The supplier maturity should be evaluated with a detailed
analysis of the design, manufacturing, and support processes
of the supplier. The supplier audit is the best tool to achieve
this goal and its an important part of the process. To facilitate sharing and comparison of information, the use of standard checklists is highly recommended, such as the one
proposed in the Appendix M2 of the GAMP Guide.3
Re-use of previously performed supplier audits is encouraged, especially within large organizations, thus, avoiding
repetitions and redundancy. A secrecy agreement with the
supplier may be necessary.
Product Maturity
Product maturity should be carefully evaluated, considering
the level of standardization achieved for the specific equipment. This may require an investigation with the supplier,
and a standard survey may prove useful when selecting
among different suppliers. Standard and robust products
should be preferred to custom solutions, unless strictly necessary. Custom (bespoke) systems normally exhibit much
higher risks and should be handled with extra care.
Functional Specifications
Functional Specifications (FS) are documents commonly produced by the manufacturer. FS for a standard equipment can
be structured in a standardized validation package that
often includes Design Specification (DS), plus Installation
Qualification (IQ) and Operational Qualification (OQ) protocols - Figure 6.
The main issue here is to map variable User Requirements with standard elements (components or functionalities)
of the equipment. This is normally done by the supplier
during the User Requirements evaluation phase. Different
situations may arise when analyzing each User Requirement:
Traceability Matrix
Producing a Traceability Matrix (TM) is very important for
C&Q activities. It can help to trace all user requirements,
thus, ensuring both complete coverage of URS and test
coverage of the critical functions.
Following the GAMP suggestions, TM should report the
criticality level of each function. This can help the quick
identification of critical functions. Safety and/or business
critical functions also should be properly identified in the TM
to achieve a holistic system criticality understanding.
In addition to the recommendations from the GAMP
Guide,4 additional information should be included in the TM
regarding the level of standardization of the function. Higher
risk non-standard functionality can be quickly located in this
way.
Design Specifications
Check-Out Testing
Consolidated software versions installed on each equipment
are tested by the manufacturer according to the development
life cycle.
The check-out internal testing phase at the suppliers
premises has the purpose to ensure that the equipment is
properly built and functioning in all of its components (mechanical, electrical, electronic, and software) and that it
satisfies the specific user requirements provided by the
customer. The focus of testing activities before the delivery of
a standard equipment to a specific user is the proper configuration (selection of items and parameters that satisfy the
user requirements), and proper integration in the equipment. These testing activities can be optimized. For instance,
if a software algorithm has already been tested during the
development process, it is not always necessary to include it
www.ispe.org/PE_Online_Exclusive
Design specifications for standard equipment should describe the equipment, rather than fit specific User Requirements. The main purpose of the documentation is to provide
the user with useful information for the operation and maintenance of the equipment. Normally, the supplier is able to
demonstrate traceability between standard DS and the relevant standard FS. This traceability also may be included in
the standard Qualification/Validation Package.
However, design solutions that are arranged specifically
for the user should be identified. Non-standard solutions
should be managed with additional care and specific details,
especially when they cover critical aspects of the system.
The supplier should provide all the required documents
for the parts included in the final equipment. As-built docu-
in the check-out.
Quite often the equipment check-out is ignored during the
subsequent steps of the commissioning and qualification,
while the evidence of these tests could provide sufficient
information and avoid test redundancy.
FAT
A Factory Acceptance Testing (FAT) phase can be executed to
check congruence of the system to the purchase order and its
proper functioning with the actual customer products. FATs
are mainly intended to allow the customer to verify proper
construction and operation of the equipment at the suppliers
premises; therefore, authorizing delivery to the users plant.
The documentation produced during the FAT may be in part
re-used during the subsequent Site Acceptance Test (SAT).
When the supplier has been properly qualified, a significant reduction in testing activities can be done. FAT should
concentrate on critical items identified in the previous steps
of the process. Testing of standard parts can be evidenced by
the internal test results of the supplier, including the final
check-out documents.
The execution of FAT may be skipped for standard equipment produced by well-known suppliers, while the user may
require the testing documentation (e.g., final checkout results) before authorizing delivery.
training
SOPs
business continuity/disaster recovery planning
maintenance planning and action procedures
Training
Training is another important part of the commissioning and
qualification phases. Specific sessions for the different roles
involved in the usage of the equipment should be designed by
the supplier in order to explain the right things to the right
people. The supplier should prepare a suitable risk-based
training package with specific instructions about the manMAY/JUNE 2007 PHARMACEUTICAL ENGINEERING On-Line Exclusive
Decommissioning
The supplier may support the user even in the final stage of
the equipments life. At system retirement, it may be necessary to safeguard important information that is kept in the
system, because the mere backup or recovery procedures
could not fit for data migration to a new, different, equipment.
The supplier role, in the case, may be helpful in many aspects,
including managing obsolete mass storage devices or coding
specific software filters.
Quality Audits
10
Conclusions
To save time and money in the commissioning and qualification activities still guaranteeing the final proper quality level
of the equipment and the relevant production, it is basilar to
use a risk-based approach that focuses on critical items of the
equipment and critical activities of the life-cycle.
The knowledge of the actual manufacturing life cycle may
aid in the identification of critical steps in the process,
distinguishing the production and assembling of standard
parts from the design of custom parts.
Supplier involvement from the early stages of the process
can further improve savings. Building a trustworthy relationship between the user and supplier can reduce redundancies and provide significant advantages for both parties.
C&Q efforts can be significantly reduced using mature
products and mature suppliers. Using best practices in the
design and manufacturing bring the mature supplier closer
to the sphere of Quality by Design, improving their products
and services.
Glossary
C&Q
CQA
DS
FAT
FMEA
FS
FTA
GAMP
GEP
GMP
GPG
HMI
IQ
MES
OQ
PAT
PLC
PQ
QbD
SAT
SCADA
SOP
TM
URS
References
1. GAMP 4 Good Automated Manufacturing Practice
(GAMP) Guide for Validation of Automated Systems,
International Society for Pharmaceutical Engineering
(ISPE), Fourth Edition, December 2001.
www.ispe.org/PE_Online_Exclusive
www.ispe.org/PE_Online_Exclusive
11
12
Marco Silvestri received the Laurea Degree in mechanical engineering from the
University of Parma, Italy in 1999. After
collaborating with the Industrial Engineering Department of the same university, he
was employed as researcher by Computes
s.r.l. (Niviano di Rivergaro, PC), a software
house that produces CAD/CAM for mechanical industry. During 2001-2002, he was head of research and
development of Tecnomec s.r.l. (Vignola, MO), a manufacturer of machines and plants for the meat industry. In this
role, he developed innovative solutions for plants of Campofrio
(Burgos, Spain) and Rovagnati (Biassono, Italia). Silvestri
also was involved in vision system projects for industrial
automation, collaborating with Vicivision s.r.l. (Fidenza, PR)
on developing automated control machines for pharmaceutical (GlaxoSmithKline) and medical device (B.Braun) industries. Since October 2002, he has held the position of Assistant Professor at University of Parma, lecturing on actuators
mechanics at the mechanical engineering laurea degree, on
www.ispe.org/PE_Online_Exclusive