On this page
An ozone system can be completely assembled and still contain a problem that will not become obvious until startup: a reversed signal, an incorrect alarm limit, a valve that does not respond as expected, a network point that is mapped incorrectly, or an interlock that does not shut the system down when it should.
Finding those issues after equipment is installed at a treatment plant is expensive. The system may already be connected to plant utilities, the contractor may be mobilized, operators may be waiting for training, and the startup schedule may depend on successful commissioning.
Factory acceptance testing, or FAT, is intended to move as much of that discovery as possible into the factory, where the equipment is accessible, the engineering team is available, and corrections can usually be made before shipment.
For an ozone system, a strong FAT should verify more than whether the ozone generator turns on. It should test the engineered system: mechanical configuration, electrical construction, controls, I/O, alarms, permissives, shutdown logic, HMI operation, communications, instrumentation, documentation, and the interfaces that will connect the package to the plant.
The purpose of FAT is not to prove every condition that can only exist at the jobsite. It is to remove as much uncertainty as practical before the system leaves the factory.
What Is a Factory Acceptance Test?
A factory acceptance test is a planned verification of equipment and automation before shipment. The test is normally based on approved project documents, specifications, control narratives, drawings, I/O lists, and an agreed test procedure.
The objective is to demonstrate that the supplied system has been built and programmed in accordance with the applicable project requirements and to identify discrepancies while they can still be corrected efficiently.
ANSI/ISA-62381-2026 / IEC 62381:2024 provides a structured framework for factory acceptance testing, site acceptance testing, and site integration testing of automation systems. For ozone projects, the exact FAT scope should still be defined by the project specification and the agreed test plan.
FAT Is Not the Same as Startup or Commissioning
One of the most important distinctions is understanding what FAT can and cannot prove.
At the factory, the system may not have the final process water, plant SCADA, permanent electrical service, final oxygen source, installed injection piping, contact basin, or field instruments. Some interfaces therefore have to be simulated.
FAT can verify how the ozone package is built and how it is intended to respond. Site acceptance testing and commissioning verify how that package performs after it has been installed and connected to the actual facility.
A good FAT therefore does not try to imitate the entire treatment plant. It identifies the functions that can be meaningfully proven before shipment and documents the functions that must be completed in the field.
Start With an Approved Test Plan
The quality of a FAT depends heavily on preparation. Testing should not begin with people standing around the equipment deciding what to check.
Before the FAT, the project team should establish the documents that define the expected system configuration and behavior. Depending on the project, these may include:
- Approved P&IDs and general arrangement drawings
- Electrical schematics and panel drawings
- I/O list and network point list
- Control narrative or sequence of operations
- Alarm, permissive, and interlock matrix
- Equipment datasheets and instrumentation schedules
- Approved submittals and scope of supply
- Factory test procedure and acceptance criteria
The FAT should test against the approved design. If the documents and the equipment disagree, the team needs to determine whether the equipment should change, the documents should change, or the difference is an approved project revision.
Mechanical Verification
Before software testing begins, the physical system should be reviewed against the approved drawings and bill of material.
Mechanical verification may include checking:
- Equipment arrangement and accessibility
- Valve type, orientation, tagging, and normal position
- Piping size, material, and connection locations
- Drain, vent, and sample-point locations
- Ozone-compatible wetted and gas-side materials
- Flow direction and check-valve orientation
- Cooling-water connections and isolation points
- Analyzer and instrumentation installation
- Backflow-protection devices and moisture safeguards
This review is particularly valuable for packaged ozone equipment because process, gas, cooling, instrumentation, and electrical systems are physically integrated into a relatively compact assembly. A small construction error can affect several disciplines at once.
Electrical and Panel Verification
The electrical portion of the FAT should confirm that the system has been built in accordance with the approved electrical design and that the panel construction, devices, identification, and field interfaces are complete.
Typical checks may include:
- Supply voltage and equipment ratings
- Circuit protection and disconnects
- Panel labels and device identification
- Terminal numbering and field wiring points
- Power supplies and control voltage
- Motor starters or variable-frequency drives where applicable
- Emergency-stop circuits
- Panel alarms and status indication
Where a UL 508A labeled panel is required by the project, FAT is also an opportunity to confirm that the delivered panel markings and project documentation match the approved design.
I/O Testing: Prove the Signals
I/O testing is one of the highest-value parts of an ozone-system FAT because many field startup problems are not failures of major equipment. They are interface problems.
Digital and analog points should be exercised so that the team can verify the entire signal path from the simulated field condition to the PLC, HMI, output command, alarm, or shutdown response.
Testing may include:
- Digital input state changes
- Digital output commands
- Analog input simulation at low, normal, and high values
- Analog output range and scaling
- Engineering units and display scaling
- Fail-state behavior for lost or invalid signals
- Remote start/stop and permissive interfaces
- Networked data points where practical
A stable value on an HMI is not proof that the value is correct. The simulated source, PLC scaling, engineering units, alarm limits, and displayed value should agree.
Permissives, Interlocks, and Shutdowns
Ozone systems depend on operating permissives and protective interlocks. These functions should be deliberately challenged during FAT rather than assumed to work because the PLC program compiled successfully.
Depending on the system design, the FAT may simulate conditions such as:
- Loss of cooling-water flow
- Low or high feed-gas pressure
- Oxygen-system fault
- Chiller fault
- Loss of process or injection flow
- Ambient ozone alarm
- Backflow or moisture detection
- Off-gas destruct not available
- Emergency-stop activation
- Loss of a critical instrument or communication signal
The test should confirm not only that an alarm appears, but also that the system responds correctly. Some conditions may generate a warning. Others may prevent startup, remove generator enable, close a valve, stop auxiliary equipment, or require a manual reset before operation can resume.
HMI and Sequence-of-Operation Testing
The HMI is where the operator sees the system, but the screens must reflect the actual control philosophy.
FAT should verify that equipment status, alarm text, process values, operating modes, setpoints, permissive status, and manual commands are represented correctly. Startup and shutdown sequences should also be exercised through their expected steps.
This is a good time to ask practical operator questions: Can the operator tell why the system will not start? Is a shutdown cause obvious? Are setpoint limits reasonable? Can local and remote modes be distinguished? Does the HMI show a failed instrument differently from a legitimate low process value?
Good controls do not only execute logic. They help the operator understand the logic.
Communications and Plant Interfaces
Many ozone systems exchange data with plant SCADA, a distributed control system, remote I/O, or other packaged equipment. Those interfaces should be reviewed before shipment even if the final plant network is not available at the factory.
Where practical, FAT can verify:
- Communication protocol and addressing
- Point names and data types
- Read/write permissions
- Remote commands and setpoints
- Alarm and status mapping
- Loss-of-communication behavior
- Network architecture and interface responsibility
The most important outcome is clarity. The ozone-system supplier, electrical contractor, plant integrator, and owner should understand who is responsible for each interface and what remains to be completed during site integration.
Instrumentation and Analyzer Checks
Instrumentation should be checked for correct installation, range, tag, units, and signal behavior. Where analyzers can be meaningfully operated or simulated at the factory, their outputs and associated control logic should be verified.
For ozone systems, this may include oxygen flow, gas pressure, temperature, ozone concentration, ambient ozone monitoring, cooling flow, and other project-specific measurements.
If a process analyzer cannot be fully validated without site water or final sample conditioning, the FAT should document that limitation and define the required field check. A simulated signal can prove the control logic, but it cannot prove that the final sample system will produce a representative measurement.
Ozone Generation and Functional Performance
Where the factory setup allows safe and representative operation, the ozone generator itself should be functionally tested across the conditions defined by the project test procedure.
The exact performance checks depend on the equipment and contract. They may include generator enable, power response, ozone concentration, feed-gas flow, cooling behavior, alarms, output control, and operation of multiple generator modules.
A factory ozone-production test should not be confused with proving the complete treatment process. Transfer efficiency, dissolved ozone residual, contaminant removal, CT, and other water-side performance depend on the installed injection, contact, hydraulics, water quality, and process conditions at the plant.
The Punch List Is Part of the Test
A successful FAT does not mean that no issues were found. One of the reasons to conduct the test is to find issues early.
When a discrepancy is identified, it should be documented with a clear owner and disposition. Items can then be corrected, retested, accepted for field completion, or formally incorporated into the project documentation.
The goal is to avoid vague statements such as “fix before startup.” The project team should know what was observed, what action is required, who owns the action, and how completion will be verified.
ISA guidance for FAT and SAT specifically emphasizes structured test planning, defined completion criteria, and punch-list tracking. That discipline is valuable because acceptance is ultimately a documentation process as well as a technical process.
FAT, SAT, Loop Checks, and Commissioning Are Different
These activities are related, but they should not be treated as interchangeable.
- FAT: verifies the system at the manufacturer or integrator before shipment.
- SAT: verifies the installed system at the project site.
- Loop checks: verify the complete electrical and instrumentation path after field installation.
- Commissioning: places the complete installed process into operation and verifies functional performance under site conditions.
ANSI/ISA-62382-2026 / IEC 62382:2024 addresses electrical and instrumentation loop checks after installation and before cold commissioning. That distinction is important: a factory simulation can verify PLC logic, but field loop checks must still confirm the actual wiring, installed instruments, junction boxes, terminations, and signal path at the plant.
What Engineers Should Ask Before Witnessing FAT
A productive FAT starts before the witness arrives at the factory. Engineers and owners should ask:
- Is there an approved FAT procedure and acceptance criteria?
- Which drawings and revisions govern the test?
- Which equipment and interfaces will be physically available?
- Which external signals will be simulated?
- Will every critical permissive and shutdown be challenged?
- How will analog inputs and outputs be simulated and documented?
- Will plant communication points be tested or only reviewed?
- What generator-performance checks are included?
- How will punch-list items be tracked and closed?
- Which items are explicitly deferred to SAT, loop checks, or commissioning?
These questions keep the FAT focused on proving the project requirements rather than simply demonstrating that equipment can run.
The Pinnacle Engineering Perspective
At Pinnacle Ozone Solutions, ozone-system engineering spans ozone generation, oxygen supply, cooling, injection, instrumentation, electrical design, controls, safety logic, and plant integration. Factory testing is where those disciplines are brought together before the system reaches the field.
A strong FAT provides value to everyone involved in the project. The manufacturer gains a structured final verification. The consulting engineer can confirm that the approved design has been implemented. The integrator can review interfaces. The owner gains visibility into how the system will operate. The startup team receives equipment that has already been challenged under controlled conditions.
The objective is not a perfect factory demonstration. The objective is a field-ready system with fewer unanswered questions.
Conclusion
Factory acceptance testing is one of the best opportunities to reduce startup risk before an ozone system reaches the jobsite.
The most valuable FATs go beyond a basic power-up. They verify the physical build, electrical construction, I/O, control logic, alarms, permissives, protective shutdowns, HMI behavior, communications, instrumentation, and the project documentation that ties those elements together.
They also recognize the limits of factory testing. Water-side process performance, final field wiring, plant-network integration, and site operating conditions still require SAT, loop checks, startup, and commissioning.
When FAT is planned around the approved engineering documents and executed with clear acceptance criteria, it becomes more than a witness test. It becomes a risk-reduction step between design and operation.
The best time to discover an interface problem is while the equipment is still in the factory, not while the plant is waiting to start.
Technical Source Notes
- ANSI/ISA-62381-2026 / IEC 62381:2024, Automation Systems in the Process Industry – Factory Acceptance Test (FAT), Site Acceptance Test (SAT), and Site Integration Test (SIT). ISA describes the standard as a structured methodology for pre-test planning, execution, documentation, punch-list tracking, and acceptance of industrial automation systems.
- ANSI/ISA-62382-2026 / IEC 62382:2024, Control Systems in the Process Industry – Electrical and Instrumentation Loop Check. The standard addresses verification of electrical and instrumentation loops after installation and before cold commissioning.
- Pinnacle Ozone Solutions, “Reading an Ozone System P&ID: Where Process, Safety, and Controls Come Together.” The article identifies P&IDs as key verification documents during factory testing and commissioning.
- Pinnacle Ozone Solutions, “Engineering the Interface: Why I/O Matters in an Ozone System.” The article discusses simulated analog inputs, digital permissives and interlocks, alarm and shutdown verification, remote start/stop logic, HMI checks, and communication mapping during FAT.
- Pinnacle Ozone Solutions, “Engineering Confidence: Inside the Pinnacle Process for Turnkey Ozone System Excellence.” Pinnacle describes pre-shipment QA/QC, factory verification, controls integration, commissioning, and field support as parts of the complete system-delivery process.
