7 Checks for a SPUN Commissioning Checklist
A useful SPUN commissioning checklist does more than confirm that a PVD system powers on. It verifies project readiness, installation, controls, safety, functional testing, process performance, quality records, training, and formal handover. Use the framework below to organize the work, then confirm technical requirements against the applicable manufacturer documentation, site procedures, and qualified technical oversight.
1. Confirm the project scope and site are ready
Begin by defining what commissioning must prove. A prototype installation may need to demonstrate controlled operation and an initial coating process. A production installation may also require repeatability, operator readiness, documented inspection, and a production-release decision.
Identify the equipment owner, commissioning lead, quality representative, operators, maintenance contacts, and authorized acceptance representative. Establish which activities belong to Sputtek, the installation contractor, and the customer. Record the intended parts, fixtures, coating applications, production volumes, and inspection methods where they have been approved.
Review the installation location, service access, material flow, environmental conditions, and open site risks. Sputtek provides information about its PVD system range, but the project team should confirm requirements for the selected configuration.
Record: approved scope, responsibility matrix, site-readiness review, open-risk list, applicable technical documents, and acceptance criteria.
Pause when: intended use is unclear, approvals are missing, the installation area is not ready, or responsibility for unresolved risks has not been assigned.
2. Verify installation, connections, and supporting systems
Compare the installed equipment with approved drawings, specifications, and equipment identification. Check the chamber, fixtures, racks, controls, labels, cables, piping, access panels, and visible interfaces. Each inspection should identify what was checked, by whom, and when.
Review electrical supply, gases, vacuum equipment, cooling, ventilation, drainage, facility interfaces, and other utilities against the technical documentation for the particular SPUN system. Do not insert universal utility values into a generic checklist. Confirm that service connections are identified, accessible, protected, and consistent with approved drawings.
Record every installation change and obtain the required technical review before functional testing.
Record: equipment identification, drawings, inspection results, connection checks, utility verification, approved changes, and outstanding actions.
Pause when: a connection does not match the documentation, a required service is unverified, visible damage is present, or an installation change has not been reviewed.
3. Check system function, controls, and safety readiness
Before running a process cycle, verify control-panel functions, status indications, alarms, interlocks, instrumentation, chamber access controls, fixture condition, and communication between relevant subsystems. The exact checks depend on the system configuration and manufacturer documentation.
Safety verification must follow equipment manuals, site risk assessments, applicable procedures, and qualified personnel. Confirm that emergency provisions, operating boundaries, warning labels, and access controls have been reviewed by responsible site personnel.
Check the verification or calibration status of instruments required for commissioning, where applicable. Confirm that alarms are understood and that responses to faults are documented.
Record: control and alarm tests, interlock checks, instrumentation status, safety sign-off, risk-control actions, and identified faults.
Pause when: a safeguard is unavailable, an alarm or interlock fails, instrument status is unknown, or a fault cannot be explained and controlled.
4. Run documented dry cycles and functional tests
Dry runs bridge installation checks and process validation. Use them to verify operating sequences, subsystem communication, loading and unloading steps, alarm behavior, operator prompts, and record generation. Each dry run should have a defined objective and named observer.
Capture the test date, equipment status, configuration, personnel, expected result, observed result, deviations, corrective actions, and approval. If the system uses recipe management or electronic records, verify that the correct version is identifiable and retrievable.
Do not insert universal temperature, pressure, timing, speed, or cycle values into a generic checklist. Those parameters are system- and application-specific. This stage confirms controlled function using approved settings; it does not create an unapproved coating recipe.
Record: dry-run protocol, sequence results, alarm responses, recordkeeping checks, deviations, corrective actions, and retest approvals.
Pause when: the sequence cannot be completed as documented, subsystem communication is unreliable, records are incomplete, or repeated deviations remain unexplained.
5. Validate the process with representative work
After functional testing, use representative parts, fixtures, or test pieces with an approved process. The work should reflect the materials, geometry, loading method, application, and inspection needs the project is intended to support.
Define inspection methods before the run. Depending on the approved project plan, these may include visual inspection, dimensional checks, adhesion assessment, thickness measurement, or other quality tests. Acceptance methods and thresholds must come from application requirements and approved technical documentation.
Trace the result from load configuration through inspection. Stop if defects are unexplained, results are unstable, the work is not representative, or a recipe changes without approval. Sputtek supports PVD work from prototyping through high-volume manufacturing, but acceptance remains a project-specific qualification decision. Review the PVD coating overview for broader application context.
Record: approved process reference, load configuration, part identification, inspection method, results, deviations, corrective actions, and process approval.
Pause when: representative work cannot be identified, acceptance criteria are undefined, results are inconsistent, or a process change is unreviewed.
6. Assemble quality, compliance, and acceptance records
Assemble evidence as commissioning progresses rather than recreating it at the end. Use one controlled acceptance file connecting every check to its evidence, owner, status, deviation, corrective action, and approval.
| Area | Suggested evidence | Decision |
|---|---|---|
| Scope and site | Approved scope, responsibility list, site review, risk register | Proceed or act |
| Installation | Drawings, inspection records, connection checks, approved changes | Accept or correct |
| Controls and safety | Alarm and interlock tests, safety review, instrument status | Test or pause |
| Functional tests | Protocol, results, deviations, retest approval | Function demonstrated or investigate |
| Process validation | Load record, process reference, inspection results, nonconformance actions | Accept defined scope or continue work |
| Handover | Training sign-offs, operating documents, open actions, acceptance signature | Release or hold |
Sputtek identifies ISO 9001:2015 certification and Nuclear N299.3 vendor approval among its qualifications. These credentials may be relevant when assessing a supplier, but they do not replace project-specific acceptance criteria, customer requirements, site controls, or required records.
Record: the evidence matrix, inspection and test results, quality records, nonconformance dispositions, approvals, and final commissioning acceptance record.
Pause when: evidence cannot be traced to the activity, a deviation has no disposition, or acceptance criteria changed without authorization.
7. Complete training and formal handover
Handover should demonstrate readiness to operate the SPUN system within the approved scope. Review operating instructions, loading and unloading, process-record requirements, routine checks, maintenance responsibilities, escalation routes, and abnormal-condition responses.
Training records should identify the subject, participant, trainer, date, and follow-up requirements. Include operators, maintainers, inspectors, and managers as appropriate. Attendance alone is not evidence of operational readiness.
Finish with a formal decision stating what the system is accepted for, what limitations apply, which actions remain open, who owns them, and who authorized release. Resolve technical questions about operation, configuration, or documentation before declaring full handover.
Record: operating documents, training sign-offs, maintenance and escalation responsibilities, open actions, release limitations, and acceptance signatures.
Pause when: required operators are untrained, essential documents are unavailable, open actions affect controlled operation, or no authorized person has accepted the scope.
How SPUN 2,000, SPUN 4,000, and custom systems affect the checklist
Sputtek lists the SPUN 2,000, SPUN 4,000, and custom-designed PVD systems. Published information states that the SPUN 2,000 supports loads up to 1,200 kg per cycle and the SPUN 4,000 supports loads up to 3,000 kg per cycle.
These capacities help frame a project, but they do not determine every commissioning requirement. Load range, chamber arrangement, fixtures, process, automation, inspection plan, and site interfaces can all change the scope. Custom systems require careful review of approved design, interfaces, controls, and acceptance tests.
Use model-specific information as a starting point, then request the applicable technical documentation and acceptance requirements. The objective is a checklist that reflects the installed system and intended work, not a claim that one model is universally superior.
Frequently asked questions
Does every SPUN system use the same commissioning checklist?
No. The seven areas provide a consistent framework, but evidence and acceptance boundaries should be adapted to the SPUN 2,000, SPUN 4,000, or custom configuration, its interfaces, and its intended application.
What belongs in a SPUN commissioning acceptance record?
Include scope, responsibilities, installation checks, utility verification, control and safety tests, dry-run results, process-validation evidence, deviations, corrective actions, training records, approvals, and open actions.
When should a team contact Sputtek during commissioning?
Contact the technical team when documentation is unclear, an installation change affects the system, a fault or unstable result remains unexplained, or the project needs system-specific acceptance requirements. Use Sputtek’s contact page for technical follow-up.
Conclusion: turn the checklist into a signed acceptance record
The strongest SPUN commissioning checklist follows the whole readiness path: define the scope, verify installation, confirm controls and safety, complete dry runs, validate representative work, assemble quality evidence, and finish training and handover. Each check should produce an identifiable record and a clear decision.
Convert these seven checks into a system-specific acceptance record with evidence, owners, deviations, corrective actions, approvals, and open items. Confirm that it matches the selected SPUN 2,000, SPUN 4,000, or custom configuration and intended application. For technical follow-up on Sputtek PVD systems, use the Sputtek contact page.
