Define the DQ, FAT, SAT, IQ, OQ and PQ support boundary for a configured cold-form blister project—before documentation, test responsibilities and site activities become assumptions.
URS response firstConfiguration traceabilityObjective acceptanceBuyer and supplier roles
Project reference. The final protocols, tests and records depend on the approved URS, machine configuration and contracted support scope.
RequirementApproved URS, intended use, risks and acceptance intent
ConfigurationMachine, tooling, controls, options, interfaces and revision
MethodPrerequisites, samples, instruments, challenge and sampling
EvidenceRaw results, deviations, approvals and retained records
Start with the project boundary
Qualification is not a generic certificate attached to a machine
A useful qualification package connects the buyer’s approved requirements to the actual Alu‑Alu machine configuration, test methods, acceptance criteria and retained evidence. It also separates equipment-supplier support from the buyer’s quality-system responsibilities.
The practical buying question is not “Is the machine validated?” Ask: “Which requirements will be tested, with which product and material, by whom, at which location, against what limits, and what record will prove the result?”
Freeze the approved machine, tooling and control-system revision before qualification evidence is executed.
Inputs before quotation
Freeze six decisions before anyone promises a validation package
These inputs determine the real document index, test effort, samples, instruments, site work and acceptance boundary. If they remain open, two suppliers can quote very different scopes under the same “IQ/OQ/PQ included” label.
01
Intended use and products
Name dosage forms, dimensions, fragility, dust or static behavior, product families, batch conditions and representative challenge products.
02
Pack construction
Confirm forming and lidding grades, cavity drawing, web widths, artwork, registration, seal criteria and finished-card limits.
03
Equipment baseline
Identify machine model, tooling revision, feeder, inspection, rejection, coding, controls, recipes, utilities and line interfaces.
04
Accepted output
Define good cards at discharge and how start-up waste, rejects, stops, splices, interventions and restarts will be counted.
05
Test conditions
Agree prerequisites, materials and lot identity, sampling, instruments, challenge cases, run duration and deviation workflow.
06
Responsibility and records
Name who authors, reviews, approves, executes and retains each protocol, raw result, certificate, deviation and report.
Lifecycle map
Use one traceable chain from design decision to production evidence
The labels below are useful only when their deliverables and approval points are defined. The exact sequence can vary with the buyer’s validation plan, project risk and contracted division of responsibilities.
01 · DQ
Confirm design
Trace URS requirements to the proposed configuration, options, documents and declared gaps.
02 · FAT
Test before shipment
Execute an approved factory protocol using agreed materials, challenge cases and acceptance limits.
03 · SAT
Confirm arrival
Verify delivered scope, condition, utilities, installation readiness and open-item disposition at site.
04 · IQ
Record installation
Identify installed equipment, components, drawings, utilities, calibration status and controlled documents.
05 · OQ
Challenge operation
Test functions, alarms, interlocks, recipes and operating ranges defined by the approved protocol.
06 · PQ
Prove the process
Demonstrate repeatable performance under the buyer’s approved production and quality conditions.
Important: FAT and supplier qualification documents can support the buyer’s qualification work, but they do not replace the facility quality system, process validation, product release or regulatory assessment.
Contracted document scope
Replace “validation documentation included” with a line-by-line matrix
Availability, format, language, revision, approval status, customization, execution and site support can change the project scope. Put each deliverable and exclusion in the quotation and contract.
Before purchase order
Define: URS response, scope and exclusion list, preliminary configuration, document index, responsibility matrix and proposed acceptance strategy.
During design
Define: approved drawings and specifications, component and option list, control description, software boundary, risk-review inputs and change control.
Before FAT and shipment
Define: approved FAT protocol, prerequisites, samples, instruments, results, deviations, configuration baseline, manuals, certificates and open items.
At site and in operation
Define: installation records, IQ/OQ support or templates, training, SAT, handover, service access, backups, calibration and software-support boundaries.
Qualification decision matrix
Approve the method and evidence—not only the document title
Use this matrix to expose missing assumptions before execution. Final tests and limits must be approved for the configured project; the examples below are planning prompts, not universal acceptance criteria.
Decision
Method to approve
Evidence to retain
Question answered
Web handling
Exact reels, setup, splice, tension and tracking observations.
Material identity, settings, observations, events and deviations.
Can the approved web feed consistently?
Forming repeatability
Approved drawing, cavity measurements, samples and defect classification.
Tooling revision, settings, measurements, samples and defect log.
Does the web form the approved geometry?
Seal process
Named material pair, settings and agreed seal or package-integrity method.
Recorded settings, identified samples and test results.
Is there a usable operating window for this pack?
Registration and cutting
Artwork controls, print mark, code, perforation and cut-position limits.
Printed samples, measurements, code results and disposition.
Does the finished card match approved controls?
Inspection and rejection
Defined challenge defects, detection logic, reject confirmation and segregation.
Challenge set, detection results, reject record and reconciliation.
Are specified defects detected and controlled?
Sustained run
Agreed duration, product, materials, staffing and accepted-output definition.
Total output, accepted cards, rejects, waste, stops and interventions.
Can the process meet the agreed accepted-output target?
Evidence package
Make every result traceable to the exact tested configuration
A report without identifiable inputs is difficult to reuse. Retain the context needed to understand what was tested, whether a deviation occurred and which approved decision followed.
Requirement IDApproved statement, owner and acceptance intent.
Configuration IDMachine, tooling, software, recipe and option revisions.
Material identityProduct, forming web, lidding and representative lot details.
Method identityProtocol version, instruments, sampling and procedure.
Raw resultCounts, measurements, observations, stops and interventions.
DispositionDeviation, corrective action, approval and retained record.
Site support and execution responsibilities must be named in the contracted project boundary.
Supplier and buyer responsibilities
Separate equipment evidence from the buyer’s complete validation program
The cleanest projects state who supplies information, who approves it and who owns the final decision. The exact split below must be confirmed in the URS response and contract.
Workstream
Potential supplier contribution
Buyer responsibility
URS and design
Respond to requirements, declare configuration, options, assumptions, exclusions and supporting documents.
Prepare the agreed machine, tooling, protocol inputs, test environment, raw results and deviation records.
Approve the protocol and samples, witness as contracted, review evidence and accept or disposition open items.
Installation and IQ
Provide installation instructions, drawings, component data and contracted installation or execution support.
Provide qualified utilities and facility conditions, approve site records and control local procedures.
OQ
Support machine-function challenges, operating-range tests and troubleshooting within the agreed boundary.
Approve risk-based tests, limits, instruments, deviations and release to the next stage.
PQ and product release
Provide machine knowledge and contracted technical support during buyer-approved runs.
Own product, batches, sampling, laboratory testing, process validation, quality approval and commercial release.
Lifecycle
Provide change notifications, service records and revision-controlled technical updates when contracted.
Own periodic review, requalification decisions, calibration and maintenance program, data governance and regulatory assessment.
Contract checkpoint: mark every document and activity as included, optional, buyer-supplied, third-party or excluded. Avoid assuming that “support” means authorship, execution, approval and site attendance are all included.
Tooling and material revisions belong in the qualification baseline.Protocol scope should follow the approved process risks and configured equipment.
What to send for a useful review
Give engineering enough evidence to return a testable scope
A qualified inquiry is easier to answer and compare. Send the files and decisions below; HIJ can then respond with the proposed machine boundary, open questions and documentation or test options.
A
Product and pack
Product dimensions and samples, cavity or card drawing, forming and lidding grades, artwork, seal criteria and proposed quality tests.
B
URS and data needs
URS or requirement list, intended markets, user roles, recipes, electronic-record expectations, reports, backups and interface requirements.
C
Acceptance and site plan
Accepted-output target, FAT duration, challenge defects, retained evidence, site utilities, installation, training and qualification-support expectations.
What is included in Alu-Alu blister machine validation support?
The scope can include URS response, design review, FAT planning and records, installation information, IQ or OQ templates or execution support, training and handover documents. The exact document list, format, language, approval status, site attendance and exclusions must be named in the quotation and contract.
Are DQ, IQ, OQ and PQ automatically included with the machine?
Do not assume they are. Ask for a document-and-responsibility matrix that marks each item as included, optional, buyer-supplied, third-party or excluded, and states whether the supplier authors, customizes, executes or only supports it.
What is the difference between FAT, SAT, IQ, OQ and PQ?
FAT tests the approved factory scope before shipment. SAT confirms the delivered equipment and site readiness. IQ records installation against approved information. OQ challenges defined functions and operating ranges. PQ is performed under the buyer’s approved production and quality conditions to demonstrate repeatable process performance.
How many PQ batches are required?
There is no universal batch count that a machine supplier should impose. The buyer should approve a risk-based PQ strategy, including the number of runs or batches, products, materials, sampling, tests and acceptance criteria, within its validation plan and applicable requirements.
Does supplier documentation make the machine FDA, EU GMP or WHO GMP compliant?
No supplier document or machine label alone establishes a facility’s regulatory compliance. Equipment documents can support the buyer’s assessment and qualification work, while the buyer remains responsible for its quality system, intended use, process validation, data governance and product release.
What should an Alu-Alu blister machine FAT prove?
The approved FAT should test the contracted configuration with identified tooling, materials and challenge conditions. It should retain objective results for web handling, forming, feeding, sealing, coding, inspection, rejection, safety, sustained operation and deviation handling as applicable to the project.
What information is needed before the qualification scope is quoted?
Send the product and pack definition, URS or requirement list, machine and line boundary, accepted-output target, data and interface needs, proposed FAT conditions, site utilities, document expectations and the requested division of supplier, buyer and third-party responsibilities.
Can existing templates be customized for our quality system?
Customization should be confirmed before purchase. Agree the source format, language, branding, requirement traceability, approval workflow, acceptance criteria, revision control and who owns later changes. A generic template is only a starting point until it is approved for the configured project.
Continue the decision
Review the machine, process and evidence routes together
Turn your URS into a reviewable qualification scope
Send the product and pack definition, machine boundary, accepted-output target, documentation expectations and proposed test conditions. HIJ can review the requested supplier support and identify the information still needed for a quotation.
