COTS or Custom: A Specifier’s Comparative Guide to IQ/OQ/PQ Verification for Medical Contract Manufacturing

by David
0 comments

Picking between off‑the‑shelf components (COTS) and fully custom builds changes everything about how you verify installation and performance. At Medtec trade floors and sourcing meetings — think Medtec China 2026 in Shanghai — buyers and engineers run through the same checklist: supplier capability, validation protocol, and the practical limits of on‑site testing. Medtec China 2026 and the wider trade circuit — represented by events like China medical expo 2026 — are where those conversations go from abstract to actionable.

Why a comparative lens matters

COTS parts reduce lead time and unit cost but increase verification scope for integration risks. Custom manufacturing shrinks integration uncertainty but demands deeper supplier qualification and design transfer checks. Both paths require strict adherence to IQ/OQ/PQ: installation qualification (IQ), operational qualification (OQ), and performance qualification (PQ). Treat these not as paperwork but as measurable checkpoints tied to risk controls and clinical use.

IQ/OQ/PQ: the verification playbook

Break verification into three concrete steps. IQ confirms the equipment, utilities, and environment match design drawings. OQ proves the device operates across defined ranges, exercising failure modes and alarm logic. PQ demonstrates the device meets clinical performance under expected use. For each step, embed acceptance criteria into the validation protocol and assign a responsible verifier — supplier personnel alone is rarely sufficient.

What to test and how to specify it

Keep test plans tight and evidence-focused. Typical items include functional tests, software version checks, biocompatibility review, sterilization cycle validation, and bioburden assessments. Specify retention sample testing periods explicitly: bioburden — 14‑day incubation limit; sterility challenge — 14‑day observation for growth; and long‑term retention per contract, commonly two years or per regulatory requirements. Include traceable records for raw materials and lot numbers for any COTS components used in the assembly.

Common verification pitfalls on COTS vs custom builds

Suppliers often assume COTS means “low risk.” That assumption hides mismatches in electrical interfaces, firmware revisions, and user‑interface expectations. With custom builds, the usual issue is incomplete design transfer — missing test vectors or undocumented tolerance stacks. A mid‑project change in a connector type can cascade into repeated OQ runs — annoying and costly. — Plan for change control early and reserve time for regression testing.

Sourcing lessons from Shanghai and the show floor

Real‑world experience at Medtec China 2026 makes a point plain: factory tours plus sampling tests shorten qualification timelines more than remote audits alone. Shanghai’s ecosystem bundles suppliers, contract manufacturers, and test labs within short logistical cycles, so on‑site IQ verification and witness OQ runs are practical and informative. Use a short, physical sampling protocol during site visits to validate COTS components before large buys.

Practical checklist for field verification

Use this compact checklist during supplier qualification and pre‑production verification:- Confirm component traceability and supplier quality system certification.- Map IQ items: power, environment, utilities, documentation.- Run OQ test vectors across expected and edge conditions, logging telemetry.- Execute PQ with representative clinical load and operator training.- Archive retention samples and test results per agreed periods (bioburden 14‑day incubation).

Three golden rules for selecting the right path

1) Match verification depth to clinical risk: higher patient impact equals deeper PQ scenarios and expanded traceability. 2) Lock acceptance criteria into the contract: pass/fail thresholds, software baselines, and sample retention periods must be unambiguous. 3) Prioritize witnessed runs: have your engineers witness at least one full IQ/OQ/PQ cycle on site or at a certified witness lab; remote packets alone are insufficient.

These rules shorten approval cycles and reduce surprises in transfer to scale — and they reflect what professionals tested at trade events like Medtec know works in practice.

Medtec — practical sourcing, tested verification, and fewer surprises on launch day. —

You may also like