What is OTAP?
OTAP stands for Development, Test, Acceptance and Production (in Dutch: Ontwikkeling, Test, Acceptatie, Productie) and is a widely used methodology for rolling out software and system changes in a controlled and structured way. Within industrial automation, OTAP is applied when implementing changes in SCADA systems, PLC software or Historian configurations, for example.
The aim of OTAP is to verify and validate changes before they affect the production environment, in order to minimise the risk of errors and downtime.
🧠 How does the OTAP model work?
- Development (O)
- Designing and programming software, scripts or configurations
- Testing in an isolated development environment
- Version control via Version Control (e.g. Git)
- Test (T)
- Technical testing such as syntax, logic and IO simulations
- Hardware-in-the-loop simulations where applicable
- Acceptance (A)
- Functional testing by end users or engineers
- Validation against specifications and standards
- Often includes Change Management approval
- Production (P)
- Final rollout on the operational OT network
- Monitoring and logging during the first production cycle
- Rollback plan in case of issues
Each phase has its own environment, permissions and documentation requirements.
🏭 OTAP in industrial automation
- PLC programs are first tested in the development environment
- SCADA screens or scripts move from test and acceptance to production
- Historian modifications or new alarm logic are validated in advance
- Software updates on HMIs or Firewalls follow the OTAP cycle
- A mandatory part of GAMP, FDA or ISA-88-based environments
Applications:
- Machine control, batch logic, visualisation, alarm management
- Recipe management, reporting, network configurations
🔍 OTAP vs. DevOps vs. direct change
| Change model | Structure | Risk of errors | Manageability |
|---|---|---|---|
| OTAP | Structured, phased | Low | High |
| DevOps | Fast, automated | Variable | High when properly set up |
| Direct change | Straight into production | High | Low |
🔐 Security considerations
- Access management per OTAP phase (Access Control)
- Only authorised deployment to production
- Audit and logging mandatory in acceptance and production
- Immutable Backup before production rollout
- Test and acceptance environments physically or logically separated from production
- Change Management with an authorisation and rollback plan
The OTAP model contributes to manageable and safe changes in OT environments.
📌 In summary
OTAP is a structured method for rolling out changes safely and in a controlled manner in industrial networks. By testing and validating every change before production, the risk of downtime, errors and security issues is greatly reduced.