**IQ answers “what was installed, where, how, and against which approved requirement?”** It verifies the actual equipment identity, options, utilities, physical interfaces, environment, control-system configuration, safety provisions, measurement assets, and document set. Each result should link to a requirement and objective evidence such as a tag, measurement, drawing, certificate, configuration export, inspection record, or approved calculation. Installation qualification should not become a generic checklist copied between tools. A plasma etcher, scanner, wet station, furnace, implanter, CMP system, inspection platform, tester, and automated material-handling module have different boundaries, hazards, utilities, contamination sensitivities, and configuration risks. Build the protocol from the approved user requirements, purchase specification, facilities data, design review, risk assessment, and site quality system. | Lifecycle activity | Core question | Typical evidence | What it does not prove | |---|---|---|---| | Design qualification/review | Is the proposed design suitable? | Requirements, risk/design reviews | That delivered hardware matches design | | Factory acceptance test (FAT) | Did supplier tests pass before shipment? | Supplier test records, punch list | Site hookups or final configuration | | Site acceptance test (SAT) | Did agreed site acceptance checks pass? | Receipt, setup, functional checks | Complete controlled IQ unless scope says so | | Installation qualification (IQ) | Is the approved system correctly installed and documented? | As-built identity, utility, config, calibration records | Full operating-range or product performance | | Operational qualification (OQ) | Do functions operate across intended/challenged ranges? | Functional, alarm, interlock, range tests | Routine product capability by itself | | Performance/process qualification (PQ) | Does the integrated process perform reproducibly? | Product/process results under defined conditions | Permanent control without lifecycle maintenance | The names FAT, SAT, IQ, OQ, and PQ vary by company and industry. Avoid arguing about labels; define the scope, acceptance criteria, evidence, ownership, prerequisites, and handoffs. A supplier SAT result can be leveraged when traceable and approved, but site-specific location, utilities, facilities, configuration, records, and interfaces still require verification. **Define the system boundary before writing tests.** Identify the mainframe, process modules, load ports, abatement, pumps, chillers, gas cabinets, chemical delivery, exhaust, controls, servers, terminals, recipes, robots, metrology, fixtures, and supplier skids included. Mark interfaces owned by facilities, equipment engineering, IT/OT, EHS, automation, metrology, vendor, and production. A boundary drawing should show process and facility sides of electrical power, grounding, exhaust, vacuum, cooling water, process water, compressed dry air, nitrogen, specialty gases, chemicals, drains, abatement, network, fire protection, and building automation. Undefined handoffs create duplicated assumptions: both teams may believe the other verified valve orientation, cable shielding, leak test, alarm routing, or drain compatibility. Define modes covered by IQ: installed but de-energized, utility-ready, initial power-up, software-loaded, and safe maintenance state. Hazardous functional challenges usually belong in approved commissioning or OQ procedures, but IQ must verify that required safety hardware, labels, guards, sensors, final elements, drawings, certifications, and test prerequisites are installed and traceable. **Start with identity and pedigree.** Record asset number, manufacturer, model, serial number, module serials, major option codes, chamber or stage identity, controller and drive types, pump/chiller/abatement identity, and location. Compare delivered bill of material and configuration to purchase documents and approved changes. Photograph or scan tags where allowed, but retain structured identifiers that can be searched and reconciled. Inspect shipping and receiving condition. Record shock/tilt indicators, packaging damage, preservation, missing parts, contamination controls, lifting records, and nonconformances. Confirm storage requirements and expiry of sensitive components. A tool can pass supplier FAT yet arrive misaligned, contaminated, corroded, or with substituted hardware. Verify layout, orientation, service clearances, egress, maintenance envelopes, load paths, floor loading, anchoring, leveling, vibration isolation, seismic restraints where applicable, access panels, overhead constraints, and material-flow interfaces. Confirm robots, doors, panels, hoists, filter access, pump removal, and chemical-container exchange can be serviced safely without conflicting with adjacent tools. **Facilities verification needs measured values and operating context.** Compare each hookup to approved drawings and equipment requirements: source, destination, material, size, rating, identification, flow direction, isolation, regulator, filter, sensor, drain, support, bonding, leak/pressure test status, and certification. Verify actual as-built routing, not only design intent. Electrical checks may include supply voltage, phase, frequency, available capacity, protective devices, conductor identification, grounding/bonding, disconnects, uninterruptible or emergency-power scope, power quality, and panel labeling. Testing and energization must be performed by authorized qualified personnel under site electrical-safety procedures. For a utility with available capacity $C_{avail}$ and qualified maximum equipment demand $D_{max}$, an engineering margin can be expressed as $$M=\frac{C_{avail}-D_{max}}{D_{max}}$$ but the acceptance limit must come from approved facility design and dynamic behavior. Average demand does not capture startup inrush, pulsed RF load, simultaneous chamber operation, pressure transient, or loss of redundant capacity. Cooling verification should reconcile supply temperature, pressure, flow, quality, return constraints, connection materials, alarms, and heat rejection. A basic heat-removal relation is $$\dot Q=\dot m c_p(T_{return}-T_{supply})$$ where $\dot m$ is coolant mass flow and $c_p$ its heat capacity. This estimate supports capacity review, but measured tool behavior, control-valve authority, fouling, minimum flow, condensation risk, and facility upset cases still require qualification. Process gases and chemicals require approved material compatibility, delivery pressure/flow, purity, filtration, purge architecture, valve and regulator identity, labeling, leak-test evidence, exhaust/abatement interfaces, detection, and emergency response. Do not introduce hazardous materials merely to complete IQ; use authorized commissioning protocols, simulation, inert media, or controlled handoff to later testing as defined by risk assessment. Exhaust verification should address branch identity, construction, static pressure/flow range, monitoring, balancing, corrosive/flammable compatibility, treatment, and interaction with enclosure containment. Facility vacuum, house nitrogen, compressed dry air, ultrapure water, process cooling water, drains, and waste segregation need equivalent interface-specific evidence. **Cleanroom installation protects both tool and fab.** Confirm move-in cleaning, packaging removal, wipe-down, allowed materials, gowning, ceiling/floor restoration, raised-floor penetrations, utility labels, housekeeping, and foreign-material exclusion. Inspect tool interior and wafer path for shipping debris, construction dust, lubricants, loose fasteners, protective films, and temporary fixtures. Verify environmental classification or site monitoring relevant to the asset: temperature, humidity, particles, pressure cascade, vibration, electromagnetic environment, magnetic field, acoustic limits, and floor stability. Requirements differ: an e-beam tool may be vibration and field sensitive; lithography may require tight thermal stability; wet tools and abatement may affect room pressure and humidity. Cross-contamination controls should identify allowed materials, dedicated pumps or lines, chamber history, wafer carriers, backside risk, chemical compatibility, and release after construction. Installation completion is not contamination qualification, but IQ should establish that the physical segregation, materials, filters, carriers, and sampling points required for later proof are present. **Safety installation is more than checking an emergency button exists.** Reconcile the site/equipment hazard analysis with installed guarding, access panels, interlocks, emergency-off devices, disconnects, pressure protection, gas detection, fire interfaces, exhaust monitoring, chemical containment, seismic restraints, labels, light curtains, grounding, and energy-isolation points. Verify identity, location, setpoint basis, wiring/piping reference, calibration/status, and required certification. Functional safety validation may be executed under SAT, commissioning, or OQ, but IQ must preserve traceability to the installed sensor, logic solver, software revision, final element, and proof-test requirement. A signed supplier certificate should be checked for equipment serial/revision and scope; it is not automatically evidence for site-specific hookup or facility response. Review hazardous-energy-control provisions and maintenance access. Identify electrical, pneumatic, hydraulic, vacuum, pressure, thermal, gravitational, RF, laser, radiation, gas, and chemical energy. Confirm isolation points and documentation are installed as designed. Do not treat a control-system stop or interlock as physical energy isolation. **Instrumentation and calibration establish measurement readiness.** Create an instrument index for sensors and standards that affect safety, process control, product quality, utility acceptance, or qualification decisions. Record tag, manufacturer, model, serial, range, resolution, location, calibration status, certificate, traceability, due date, tolerance, and intended use. Check that calibration range and uncertainty support the acceptance criterion. A pressure sensor calibrated only near atmosphere may not establish a low-vacuum threshold. A flowmeter can be correctly calibrated but incorrectly installed with insufficient straight run, wrong orientation, mixed gas correction, or unsuitable temperature/pressure compensation. IQ enrolls instruments in the calibration and maintenance systems; it does not prove the process measurement is capable under every operating condition. OQ/PQ may need loop checks, correlation, measurement-system analysis, matching, and product-based validation. Preserve initial “as found/as left” data where it helps diagnose later drift. **Software is part of the installed asset.** Inventory operating system, application, PLC/safety code, firmware, drive parameters, robot program, HMI, recipes, libraries, databases, drivers, communication modules, licenses, and cybersecurity components. Record exact versions, checksums or signed package identifiers where available, approved deviations, and compatibility matrix. Verify server/industrial-PC identity, storage, redundancy, backup destination, restore media, network address, VLAN/zone, switch port, firewall path, time synchronization, host name, certificates, service accounts, and remote-access configuration. Confirm default credentials are removed or controlled and roles align with site policy. Do not expose the tool to production or remote networks before security prerequisites are met. Create a controlled baseline backup after approved installation. Demonstrate that backup artifacts are readable and associated with the correct asset/revision; a full restore challenge may occur later under an approved test. Document who can change safety parameters, recipes, calibration constants, host communications, and software, and how changes are logged. For factory integration, verify installed SECS/GEM or other communication interface version, physical/network connection, equipment identifier, time source, message/configuration files, and required host prerequisites. Functional message behavior and production scenarios generally belong to OQ/SAT, but IQ should prove that the intended interface and baseline are present. **Documents are configuration items, not attachments collected at the end.** The IQ package commonly references approved requirements, purchase specification, supplier data, facilities data package, layout, P&IDs, utility matrix, wiring diagrams, panel schedules, network architecture, software list, bill of material, spare-parts list, manuals, safety documentation, calibration certificates, FAT/SAT records, leak/pressure tests, material certificates, permits, training prerequisites, maintenance plans, and as-built drawings. Check document number, title, revision, approval, applicability, asset identity, and storage location. Redline drawings should be incorporated into controlled as-builts or tracked as deviations with closure ownership. A correct physical installation paired with obsolete drawings is not a qualified baseline because future maintenance will recreate the error. Supplier documentation should state scope and assumptions. A generic manual covering several options may not identify the installed configuration. Link option-specific drawings and certificates. Capture proprietary documentation access and retention arrangements so the site can maintain the tool throughout its expected life. ```flowchart Approve user requirements, purchase specification, risk assessment, facilities data, and qualification strategy → Define equipment, module, software, utility, automation, safety, documentation, and organizational boundaries → Write protocol with traceable prerequisites, test method, acceptance criteria, evidence, roles, and deviation rules → Verify receipt, damage status, identity, serials, options, and supplier records → Inspect location, orientation, anchoring, leveling, clearance, maintenance access, and contamination controls → Reconcile electrical, ground, exhaust, cooling, gases, chemicals, vacuum, UPW, drains, abatement, fire, and network hookups to as-builts → Confirm environmental and cleanroom prerequisites → Verify guards, safety devices, isolation points, labels, and test/certification status → Inventory instruments and establish calibration/maintenance status → Record software, firmware, parameters, licenses, accounts, network, time sync, cybersecurity, and controlled backup → Reconcile drawings, manuals, FAT/SAT, certificates, parts, training, spares, PM, and support records → Log every mismatch as a deviation; assess risk and impact on later tests → Correct, retest, or approve a documented concession through change control → Review traceability and unresolved punch items → Approve IQ report and freeze as-installed baseline → Authorize only the defined OQ/commissioning scope → Maintain baseline through calibration, maintenance, backup, document control, and configuration management → Perform targeted re-IQ after relocation, utility, hardware, software, safety, facility, or major-maintenance change ``` **A protocol needs predetermined acceptance criteria.** Each test should identify requirement, object, method, instrument, expected result, evidence, executor, reviewer, and handling of exceptions. Avoid “verify correct” without defining correct. If acceptance depends on a drawing, specification, code, or calculation, cite its controlled revision. Use a traceability matrix to connect requirements to IQ, OQ, PQ, or another verification. Not every requirement belongs in IQ: serial number and hookup material do; chamber pressure control across range usually belongs in OQ; process uniformity and defectivity belong in process qualification. Explicit allocation prevents both gaps and repeated testing. Preconditions may include approved protocol, completed construction turnover, safe utility availability, cleanroom release, instrument calibration, software package approval, required training, supplier attendance, and energy-control plan. Record actual execution date and personnel. Never backfill evidence from memory after the tool has changed. Photographs can document tags, connections, routing, and condition but need asset/location/date context and secure retention. Screen captures can document versions or settings but should be supported by exported configuration when possible. A green status icon is not evidence of physical utility capacity or final-element state. **Deviation control preserves truth.** Record every departure from requirement, method, or expected result when discovered. Describe observed state, requirement, immediate containment, affected tests, risk, root cause as appropriate, correction, retest, product/tool impact, and approval. Do not silently edit the protocol to match the installed condition. Classify punch-list items by whether they block safe testing, affect intended function, invalidate traceability, or can be closed later under controlled conditions. Temporary hoses, jumpers, overrides, default passwords, construction filters, bypasses, or redline drawings need explicit disposition before release. “Vendor to fix later” is not a controlled baseline. A concession accepts a known deviation for a defined rationale and scope; it does not change the requirement everywhere. If the as-installed state is the desired future design, update requirements, drawings, risk assessment, spare parts, maintenance, software/configuration, and training through change control before qualification closure. **IQ-to-OQ handoff should be explicit.** The final report summarizes scope, executed tests, deviations, unresolved restrictions, installed configuration, calibration status, backup location, document package, and recommendation. Approval authorizes only the next declared activity—not unrestricted production. Provide OQ with the exact baseline and known risks. Identify setpoints, alarms, interlocks, utilities, operating ranges, recipes, software, and modules to challenge. If OQ changes a parameter or configuration, update the baseline or record the change so the final qualified state remains reproducible. Operational tests can expose installation defects missed by static inspection. A cooling-pressure transient, noisy ground, swapped network path, undersized exhaust branch, unstable gas pressure, or wrong firmware option may appear only under load. Feed those findings back into IQ/as-built records rather than treating phases as isolated binders. **Maintain the qualified installation over its lifecycle.** Link the IQ baseline to asset management, preventive maintenance, calibration, software/configuration management, backups, cybersecurity, spares, documents, and change control. Track major components by serial or revision when replacement can affect safety, process, matching, or supportability. Evaluate requalification after relocation, chamber addition, utility reroute, facilities capacity change, pump/chiller/abatement replacement, controller or software upgrade, safety-system modification, floor/anchor work, network architecture change, major repair, long shutdown, contamination event, or unexplained performance shift. Risk assessment determines whether targeted checks or full re-IQ/OQ are needed. Periodic review should confirm documents remain retrievable, calibration and PM are current, backups can be associated with the asset, software remains supported, deviations are closed, utility requirements still match site capability, and changes were assessed. IQ is a point-in-time demonstration whose value survives only through configuration control. **Use industry documents within their actual scope.** SEMI announced F122 as a guide for facilities data packages supporting manufacturing-equipment installation and building information modeling, and identifies E6, E51, and E76 among related installation-scope standards under review. Obtain current licensed documents and map them to site requirements rather than assuming one guide defines the complete IQ protocol. ISO/ASTM TS 52930:2021 is an example of a published IQ/OQ/PQ qualification framework for powder-bed-fusion additive equipment; it is not a semiconductor-equipment standard. Its public scope nonetheless illustrates an important distinction: validation planning, process mapping, and risk assessment are prerequisites, while machine installation, operation, and performance qualification answer different lifecycle questions. Apply only standards governing the actual tool, jurisdiction, product, and quality system. Regulated pharmaceutical or medical-device sites may impose formal GMP validation, electronic-record, signature, and data-integrity requirements that do not automatically apply to every semiconductor fab. Conversely, semiconductor installations have specialized EHS, facilities, contamination, automation, and equipment-interface requirements. State the governing framework in the plan rather than mixing terminology without scope. Through the as-designed-to-as-installed traceability and controlled-baseline lens, installation qualification is not a signature on a hookup checklist. It is the evidence-backed reconciliation of the delivered tool, facility interfaces, environment, safety provisions, metrology, software, cybersecurity, and records to approved requirements—creating the only credible starting point for operational challenge, process qualification, and long-term change control.