Two CIP and SIP quotations can name the same vessels, pumps and controller while covering very different projects. One may include the return arrangement, recipe development and usable qualification evidence; another may exclude site piping, critical software functions and support after commissioning. Comparing purchase prices before reconciling these boundaries produces a ranking that can be commercially precise and technically misleading.
Supplier selection should establish whether the proposed system can support the actual cleaning and sterilisation strategy throughout its intended life. This article covers the request for proposal, technical bid evaluation, documentation, service, contractual interfaces and total cost of ownership. It is vendor-neutral. Its matrices and example are GuideGxP recommendations; the project must define its own priorities, acceptance criteria and commercial conditions.
Define the procurement object before approaching suppliers
Start from the approved or controlled user requirements, equipment register and intended operating scenarios. Identify products and residues, shared or dedicated use, campaign patterns, required flexibility and the interfaces with manual cleaning or cleaning out of place. Separate established requirements from development questions. A supplier should know which conditions are fixed, which ranges need investigation and which future uses remain outside the initial scope.
Define the physical boundary across the skid, process equipment, supply, return, drain and utility connections. Include temporary hoses, valve matrices, instruments, chemical containers and recovery tanks. Define the digital boundary too: controller, HMI, supervisory system, historian, recipe storage, interfaces, licenses and records. A missing digital responsibility can delay acceptance just as effectively as a missing return pump.
Specify the required outcome precisely. Cleaning removes residues; sanitisation and disinfection provide defined microbial control; sterilisation requires its own objective and evidence. A supplier offering a steam-capable skid has not thereby demonstrated a SIP sterilisation process. Likewise, a machine described as “validated” does not establish that the site's products, cleaning procedures and sampling strategy have been validated.
Keep regulatory responsibilities and supplier evidence distinct
For human medicinal manufacturing, EU GMP Annex 15, effective since October 2015, connects user requirements, qualification, validation and changes. Chapters 3 and 5 address equipment and contamination controls. Annex 11, revision 2011, applies to relevant computerised systems. Current versions are listed in EudraLex Volume 4; revision proposals are assessed separately from current requirements.
Supplier documentation can support the manufacturer's evidence package when its scope, execution and records are suitable. It does not transfer the manufacturer's responsibility for intended use, quality oversight or release decisions. State who prepares, reviews, witnesses and approves each deliverable. Technical standards and industry guidance should be identified by edition and application; a conformity statement is not a universal GMP certificate.
Build an RFP that makes differences visible
Issue the same controlled information to all bidders. Include the URS, equipment and circuit schedules, utility conditions, layout constraints, relevant product knowledge, data requirements, test expectations and delivery milestones. Provide enough process information to obtain a meaningful proposal while using appropriate confidentiality arrangements. Maintain a common clarification register so competing offers do not silently rely on different assumptions.
Require a response against every requirement: compliant as offered, compliant with a stated option, deviation, or clarification needed. Ask for the proposed solution and evidence, not only a yes/no mark. Every exception should identify its impact on performance, qualification, cost and schedule. Unpriced options and statements such as “by others” need a named responsible party before comparison.
Request a boundary drawing and an explicit exclusions list. Ask the bidder to identify site work, civil supports, insulation, drains, utility upgrades, chemical handling, permits and integration tasks assumed outside the package. Commercial evaluation should reconcile these items into a complete installed scope. Otherwise, the least expensive quotation may simply contain the largest unassigned interface.
Evaluate process knowledge through relevant evidence
Ask how the supplier develops cleaning circuits for comparable geometry and residues. Relevant experience concerns the mechanism, not merely the pharmaceutical label on a reference project. Examine how it identifies difficult locations, evaluates delivery and drainage, chooses cleaning devices and handles product or detergent changes. Request examples with protected customer information removed rather than accepting unsupported claims about past success.
For SIP, examine steam access, air removal, condensate paths, boundary valves, cooling protection and the relationship between study sensors and routine controls. A supplier should explain what its package can demonstrate and what requires site-specific development or validation. Treat confident universal answers about temperature, pressure, hold time or lethality as a reason to examine the underlying assumptions.
Review engineering capability across materials, fabrication, welding, seals, instrumentation and maintenance access. Ask how the proposed configuration will be controlled from design to installation. A catalogue drawing may describe a family of systems, while qualification depends on the actual supplied configuration. Changes during fabrication should be visible through documented design review and the agreed change process.
| Evaluation area | Evidence to request | Decision before award |
|---|---|---|
| Cleaning process fit | Circuit concept, residue assumptions, development plan and difficult-location assessment | Can the proposed capability support the intended products and equipment? |
| SIP capability | Boundary, venting, drainage, instrumentation and cooling concept | Are thermal and post-cycle protection responsibilities explicit? |
| Automation and records | Recipe model, access design, report examples and failure behaviour | Can execution and changes be reconstructed? |
| Documentation and verification | Deliverable register, traceability approach and proposed tests | Will the site receive usable evidence for its qualification strategy? |
| Lifecycle support | Service scope, spare-parts plan and software support policy | Can the installed configuration remain supportable? |
Inspect automation deliverables before choosing the platform
Define recipe creation, approval, deployment, adjustment and retirement. Ask how a completed record retains the actual recipe version and values after later changes. Review user roles, privileged access, audit trails where applicable, time synchronisation, backup, restoration and data export. Request an example of an interrupted cycle, not only a polished successful-cycle report.
Clarify licenses, ownership, access to configuration, required engineering tools and responsibilities for interfaces. Determine what happens when a server, communication link or support subscription becomes unavailable. Remote support needs approved access, accountability and a method to control changes; permanent unrestricted supplier access is not a substitute for a support process. Review cybersecurity and infrastructure expectations with the site's responsible functions.
ISPE GAMP 5, Second Edition, is industry guidance supporting a risk-based lifecycle. It does not certify the supplier or remove the need to evaluate the installation. Ask the bidder to explain how its development records, testing and configuration management support the site's validation approach, including changes and restoration after failure.
Agree what FAT, site testing and qualification will prove
Define test objectives before agreeing a FAT date. A factory test may demonstrate routing logic, instrument functions, alarms, recipe execution and records under specified conditions. It may not reproduce installed piping, actual utility variation or the site's product residues. Record these limitations and allocate the remaining verification to the appropriate site activity.
SAT and commissioning establish relevant aspects of delivered and installed performance. IQ, OQ and PQ follow the site's approved qualification strategy; justified supplier evidence may contribute without unnecessary repetition. Cleaning validation and sterilisation validation still require their own intended-use conclusions. The contract should identify who supplies engineering support, development trials, mapping assistance, methods and reports.
Specify deliverable formats, revision status and acceptance review periods. Include as-built drawings, component lists, certificates, weld records where required, calibration information, software configuration, operating instructions, maintenance procedures and training. “Documentation supplied at completion” is inadequate if the site needs approved drawings and test plans before manufacturing or installation proceeds.
Compare total cost through transparent scenarios
Total cost of ownership includes more than equipment and freight. Consider installation, utility modifications, integration, qualification support, training, chemicals, water, energy, waste handling, maintenance, calibration, spares, software licenses and expected replacement. Include the operational consequences of cleaning duration, scheduling constraints and downtime when the assumptions can be supported.
Use the same evaluation horizon, operating scenarios and costing conventions across offers. Distinguish supplier guarantees from estimates and site assumptions. Demand evidence for proposed savings: reduced rinse water is credible only under a comparable duty with acceptable cleaning performance. Recovery can reduce consumption while adding testing, inventory control, maintenance or contamination-control requirements.
Present uncertainty as scenarios rather than a falsely exact lifetime price. Compare plausible production demand, utility prices, maintenance effort and component replacement patterns. If discounting or accounting treatment affects the decision, agree the approach with the site's finance function. Do not conceal critical capability gaps inside a favourable financial average.
| Cost or risk driver | Question for both bids | Evidence or assumption to retain |
|---|---|---|
| Installed scope | Which site works and interfaces are included? | Boundary drawing, exclusions and comparable completion estimate |
| Cleaning resources | What duty supports chemical, water and energy figures? | Cycle assumptions, measured basis and production scenario |
| Downtime and service | How quickly can the system be diagnosed and restored? | Response commitment, parts availability and recovery procedure |
| Software lifecycle | Which fees, upgrades and dependencies continue after delivery? | License schedule, support policy and obsolescence plan |
| Future changes | What modifications are permitted and what evidence must be repeated? | Operating envelope, expansion limits and change responsibilities |
Make the award decision traceable
Agree the evaluation method before reviewing prices. First identify requirements whose absence prevents the intended use or an acceptable control strategy. Keep those conditions distinct from features that can legitimately be weighted, such as maintainability, delivery flexibility or additional reporting tools. Do not treat an unanswered requirement as compliant. Record the evidence still needed and the person responsible for resolving it.
Engineering, production, quality, automation and procurement should assess their relevant interfaces together. A technically attractive solution can still create an unsupported operating responsibility for the site. Where reviewers disagree, record the assumption causing the disagreement and request a focused clarification. A numerical score should express a reasoned comparison; it should not replace the underlying explanation or hide uncertainty about a critical function.
Transfer the accepted clarification register into the controlled purchasing baseline. Identify conditional commitments, supporting documents and the milestone at which each must be verified. If the selected configuration changes during negotiation, reassess affected tests, utilities, costs and responsibilities. Preserve the final comparison so later project decisions can distinguish an accepted trade-off from a requirement that was accidentally omitted.
Practical example: the cheaper bid excludes the return
A facility compares two offers for a CIP skid serving several process vessels. Both quotations list the same nominal supply capacity. The first includes an assessed return concept, route verification, site integration and an abnormal-cycle test package. The second excludes the return pump, field instruments and historian integration. Its lower purchase price therefore does not describe the same installed outcome.
The evaluation team reconciles boundaries and asks both bidders to assess the same remote circuit and simultaneous-demand scenario. It requests comparable cycle assumptions and identifies the owner of each remaining interface. The site estimates the omitted installation and integration work, including the additional qualification effort. No arbitrary score is assigned to compensate for a missing critical capability.
The decision may still favour either offer. A site with strong integration capability may accept a clearly defined split contract; another may value single-point coordination. The award records the selected model, unresolved conditions, acceptance milestones and commercial allocation. The essential result is an explicit, supportable decision rather than an apparent saving produced by incomplete scope.
Service, spares and obsolescence are design inputs
Ask which components are standard, which require supplier-specific replacement and which have long lead times. Identify critical seals, cleaning devices, instruments and controller components. Replacement equivalence should consider material, geometry, software and performance, not only dimensions. Define the documentation and change assessment required when an original part becomes unavailable.
Service commitments should distinguish response, remote diagnosis, site attendance and restoration. A rapid telephone response does not guarantee a restored process. Define escalation, geographic coverage, language, training and responsibilities during a quality-impacting failure. Preserve the knowledge needed for the site to understand and maintain its system after individual supplier personnel change.
Checklist and red flags before award
- Reconcile every requirement, assumption, option and exclusion against the same installed scope.
- Separate mandatory quality and safety conditions from weighted commercial preferences.
- Assess cleaning and SIP competence through relevant evidence and justified limitations.
- Confirm data, software, documentation, testing and training deliverables with named owners.
- Compare resource and cost estimates under equivalent operating scenarios.
- Define service, critical spares, remote access, change support and obsolescence arrangements.
- Link acceptance milestones to reviewed evidence and close critical gaps before unrestricted use.
Red flags include a universal cycle offered without product questions, undocumented deviations, a coverage test presented as cleaning validation, an online endpoint presented as residue acceptance, inaccessible configuration and undefined “validation support”. Resolve material gaps through clarification, design changes or a different offer. A high aggregate score should never erase an unmet mandatory condition.
Key takeaways and references
Select the supplier whose defined scope, evidence and lifecycle support fit the intended operation. Use a transparent evaluation that connects process capability, responsibilities and comparable ownership costs. Coordinate requirements, qualification and maintenance decisions through Cleaning, CIP & SIP Systems and utility interfaces through Pharmaceutical Water & WFI Systems.
- European Commission, EudraLex Volume 4: current Chapters 3 and 5, Annex 15 and Annex 11.
- ICH Q9(R1) and Q10: quality risk management and lifecycle quality-system context.
- ISPE GAMP 5, Second Edition, 2022: industry guidance; publisher metadata only, with no protected procedures reproduced.
Related decisions
- URS for Cleaning, CIP & SIP Systems: Requirements, Structure and Checklist
- Qualification of CIP & SIP Systems: FAT, SAT, IQ, OQ and PQ
Explore all decisions in Cleaning, CIP & SIP Systems.
