Pharma automation commissioning: complete 2026 guide

Commissioning an automated pharmaceutical production line is not an engineering project like any other. Where a food or logistics line can be validated in a few weeks of functional testing, a pharma line requires an end-to-end documented journey, signed, traceable, and reconcilable with a regulatory dossier that will be audited by Swissmedic, FDA or EMA throughout the entire commercial life of the manufactured product.

We support Swiss pharma sites, both German and French speaking, on this journey. This guide gathers what we have learned in the field: the URS, FDS, HDS, FAT, SAT, IQ, OQ, PQ sequence, the pitfalls that turn a three-month plan into a nine-month project, and the regulatory minimum to master before signing a validation protocol.

The goal is not to replace a four-day GAMP5 course. It is to give a project manager, a production manager or a buyer of [industrial automation services](/services/automation) a clear view of what they are buying, what they should require from their integrator, and the deliverables they must receive.

Overview of the pharma commissioning cycle

The complete cycle of an automated pharma line follows a V-model adapted to the regulated world. The descending branch defines needs and specifications, the ascending branch verifies them through structured testing.

On the left, we descend from business needs (URS) to functional design (FDS), then detailed design (HDS, software design). On the right, we ascend through unit testing, FAT at the integrator workshop, SAT on site, then IQ, OQ and PQ qualifications. Each test on the right validates a deliverable on the left. If traceability is broken, the audit will see it.

For a weighing skid project or a sterile filling line, count between three and nine months between URS signature and release of the first commercial batch. The variables that shift the schedule are process complexity, presence or not of new equipment vs. revamping, and above all the quality of the input dossier provided by the client.

Our [CQV (Commissioning, Qualification, Validation)](/services/cqv) approach consists of anticipating the documentary chain from the URS phase, rather than rebuilding it at the end of the project under audit pressure.

Upstream phase: URS, FDS, HDS

URS (User Requirements Specification)

The URS is the contract. It is the document that production drafts (with help from quality, automation and validation) to express what the equipment must do, under what conditions, with what regulatory constraints. A typical pharma URS runs between 30 and 120 pages depending on criticality.

Essential sections: process description, critical quality attributes (CQA), critical process parameters (CPP), GxP requirements, 21 CFR Part 11 requirements (electronic signatures, audit trail, account management), MES/ERP connectivity requirements, integration requirements with existing DCS or SCADA, OT security requirements (often forgotten in 2026 even though IEC 62443 has become the de facto standard).

A well-written URS is testable. Each requirement carries an identifier (URS-001, URS-002...) that will be traced down to the corresponding OQ protocol. If a requirement is not testable, it does not exist.

FDS and HDS

The FDS (Functional Design Specification) translates the URS into the integrator's or OEM's functional response. This is where recipes, states, transitions, permissives, alarms, HMI screens, reports, Active Directory tree are described.

The HDS (Hardware Design Specification) lists the controllers, drives, sensors, actuators, valves, calibrated instruments, industrial network, electrical cabinets. It includes P&ID diagrams, electrical schematics, and the complete BOM.

For multi-recipe or multi-product projects, we strongly recommend an [ISA-88 compliant architecture](/services/architecture). This structures the FDS, simplifies PLC code, and drastically accelerates the OQ and PQ phases.

FAT: Factory Acceptance Test

The FAT is the acceptance test at the integrator's workshop, before shipping the equipment to the client site. It validates that the equipment, as it leaves the workshop, meets the FDS and HDS specifications.

In pharma, the FAT typically covers: point-to-point I/O testing, functional sequence testing, recipe testing (with substitute product if necessary), alarm testing, safety testing (E-stops, interlocks), HMI interface testing, DCS/MES communication testing, OT cybersecurity testing, verification of documentary deliverables.

A pharma FAT lasts between three days and three weeks depending on complexity. The client sends a team (production, automation, quality, sometimes validation) that executes the protocols with the integrator, signs the test sheets, and clears non-conformities before shipment.

We cover FAT in depth in our [practical FAT and SAT pharma guide](/blog/fat-sat-pharma-guide-pratique), with downloadable checklists.

SAT: Site Acceptance Test

The SAT replays part of the FAT tests, but on site, after installation and connection to utilities (electricity, compressed air, purified water, steam, vacuum, process gases). This is the moment when we verify that nothing has shifted during transport, that all connections are compliant, and that the equipment functions in its real environment.

The SAT is also the moment when the equipment is integrated into the existing ecosystem: OT network connection, integration with the central SCADA, data exchanges with the MES, exchanges with the LIMS for quality control results. A well-prepared SAT takes three to ten days. Poorly prepared, it can stall over several weeks because of a single misconfigured firewall or a missing VLAN.

IQ: Installation Qualification

The IQ is the first of the three regulatory qualifications. It verifies in a documented way that the equipment is installed in accordance with specifications, under conditions that will allow GMP operation.

The IQ protocol covers: verification of conformity to as-built P&ID and electrical drawings, verification of serial numbers, models and firmware, verification of material certificates for product-contact parts, verification of initial calibrations of critical instruments, verification of connected utilities (water quality, air class, pressure), verification of on-site documentation (manuals, certificates, procedures), verification of logical access (creation of user accounts, allocation of rights according to the URS-defined matrix).

IQ deliverables are signed by the executor, verified by a second technician, approved by quality. Any deviation is tracked in a deviation management system (typically the site QMS). The IQ is closed only when all deviations are closed or justified.

OQ: Operational Qualification

The OQ demonstrates, through structured tests, that the equipment functions correctly across all operational ranges defined in the URS.

Classic OQ tests for an automated line: functional testing of each sequence (start, normal stop, emergency stop, restart), testing of all defined recipes (with placebo or real product depending on strategy), testing of operational ranges (min/max temperatures, min/max pressures, min/max flows, min/max times), testing of all alarms (triggering, acknowledgment, recording in audit trail), testing of safety interlocks, testing of failure handling (loss of communication, loss of power, restart), testing of the 21 CFR Part 11 audit trail (creation, modification, deletion of critical records), testing of batch report generation.

The OQ is often the longest phase: three to eight weeks for a complex line. It is also the phase where good ISA-88 architecture saves considerable time, because unit and phase tests run in sequence without recompilation or redeployment.

PQ: Performance Qualification

The PQ demonstrates that the equipment, in its real environment and with its real product, produces in a reproducible manner conforming to defined quality attributes.

The PQ runs with the final process, the final product, trained personnel, under routine operational conditions. We typically run three consecutive batches (or a statistically justified number), varying parameters within the design space boundaries (Design Space defined in ICH Q8).

Statistical analyses (Cpk, process capability, trend analyses) are produced and reviewed by quality. PQ batches can be commercialized if compliant, which rapidly pays back the phase. Once the PQ is approved and the validation report signed, the equipment enters routine operation under continuous monitoring (Continuous Process Verification, ICH Q8).

Regulatory framework

GMP

GMP (Good Manufacturing Practice) is the general framework. In Switzerland, the OAMéd aligns with EU GMP (Eudralex Volume 4). Annex 11 specifically covers computerized systems and is the reference for everything related to automation and software validation.

GAMP5

GAMP5 (Good Automated Manufacturing Practice, edition 2 of 2022) is the ISPE guide that structures the validation of computerized systems into four criticality categories. A controller running a critical recipe is typically category 4 (configured software) or 5 (custom software), with documentation and testing levels proportionate to risk.

21 CFR Part 11

For any site exporting to the United States (the majority of Swiss pharma sites), 21 CFR Part 11 compliance is non-negotiable: electronic signatures linked to identity, tamper-evident audit trail, strict account management, traceability of all modifications to critical data.

ISO 13485 and ICH Q7

ISO 13485 applies to medical devices (drug-device combinations, for example auto-injectors). ICH Q7 governs APIs (active ingredients). These standards may stack onto the GMP base depending on the nature of the manufactured product.

Swiss specificities

Swissmedic is the competent authority. Swiss sites benefit from de facto alignment with EMA requirements (via MRAs) and FDA (via cross inspections). Concretely, a system validated according to EU GMP Annex 11 and 21 CFR Part 11 satisfies Swissmedic. The reverse is not true: a purely Swissmedic validation may need supplements to export to the United States.

Our work in the [Swiss pharma sector](/secteurs/pharma) consists precisely of anticipating these multi-jurisdiction alignments from the URS phase, to avoid having to requalify a system two years after commissioning.

Teams and roles

A pharma commissioning typically mobilizes: a client project manager, an integrator project manager, one or two automation engineers, one or two process engineers, a validation lead (CSV, Computerized System Validation), a quality lead (QA), an IT/OT referent for network and MES integrations, sometimes an OT cybersecurity referent, and production who will be the end user.

Governance happens in weekly project reviews, with monthly steering. The RACI must be clear from kickoff, particularly on ownership of validation protocols (often a grey zone between integrator and client).

Typical schedule

To set orders of magnitude:

• Simple skid (weighing, mixing, transfer): 3 to 5 months
• Sterile filling line: 6 to 9 months
• Complete line with MES: 9 to 18 months
• Revamping of an existing line: 4 to 8 months (depending on what is kept)

These durations include URS, FDS, FAT, SAT, IQ, OQ, PQ and documentary closure. They do not include the acquisition phase (ITT, contract negotiation) nor the writing of the product registration dossier.

Classic mistakes

The deviations we see most often in the field:

• URS drafted by production alone, without quality or validation review. Consequence: missing regulatory requirements, reworked in OQ phase under pressure.
• FAT rushed to meet a shipping date. Consequence: defects surface at SAT, on site, with cost multiplied by five.
• 21 CFR Part 11 audit trail added at the end of the project rather than architected from the FDS. Consequence: heavy refactoring or audit non-compliance.
• OT cybersecurity (IEC 62443) treated as optional. Consequence: network segmentation impossible to fix after go-live.
• Absence of ISA-88 reference in software design. Consequence: monolithic code impossible to maintain, every change triggers requalification.
• Underestimation of MES, ERP, LIMS integrations. Consequence: SAT slipping by several weeks.

Our [pharma references feedback](/references) and our commissioning checklists cover these points in detail. If you are starting a project, [contact us](/contact) for a URS review session before official kickoff.

FAQ

How much does a complete pharma commissioning cost?

Cost varies from 50,000 CHF for a simple skid to several million for a complete aseptic line. The validation share (CQV) typically represents 15 to 25% of the total equipment cost.

Can a FAT be done remotely?

Yes since 2020. Remote FAT (eFAT) is accepted by Swissmedic and FDA under conditions: multi-angle video streaming, HMI screen sharing, electronically signed protocol execution, physical presence of at least one client representative (or supplementary audit on arrival).

What is the difference between commissioning and qualification?

Commissioning covers all engineering activities to start up the equipment (power-up, functional testing, fine-tuning). Qualification is the documented and signed demonstration that the equipment meets its specifications within a regulatory framework. The ASTM E2500 approach allows integrating both to reduce duplication.

Who writes the IQ, OQ, PQ protocols?

Ideally the client (validation team) with contribution from the integrator. In practice, the integrator often provides the drafts, the client reviews and approves them. Final ownership and signature of protocols remain with the client (marketing authorization holder).

Is requalification required after a software modification?

It depends on impact. An impact analysis (Change Control) must be performed systematically. According to GAMP5, a non-critical parameter change can be documented without retests. A critical sequence logic change requires partial requalification (targeted OQ).