Delta Works: Testing for Safety in a Critical Infrastructure Upgrade
Testing the Operating Software for the Maeslant Storm Barrier
Customer
The Maeslant storm barrier, part of the Netherlands’ world‑renowned Delta Works, managed by Dutch authorities. As the world’s largest moving structure—and effectively the world’s largest robot—it can close the Nieuwe Waterweg to protect the Randstad from catastrophic flooding.
Challenge
The Maeslant barrier is a one‑of‑a‑kind structure. There is no industry standard for designing or testing its operating software, and the consequences of failure are immeasurable.
Developing new operating software required:
- extremely high quality standards
- a robust, risk‑based testing framework
- validation under all conceivable operational and environmental conditions
The challenge was to ensure absolute reliability for one of the most critical flood protection systems in the world.
Technology & Approach
To meet these requirements, a structured and methodical testing strategy was implemented using:
TMap (Test Management Approach)
A risk‑based testing framework ensuring that high‑risk components received the most intensive testing.
DTAP (Development, Testing, Acceptance, Production)
A controlled environment strategy enabling predictable, traceable, and safe software progression.
SCRUM Methodology
Introducing SCRUM into the industrial automation domain brought:
- iterative development
- improved planning
- faster feedback loops
- better alignment between developers, testers, and stakeholders
This was a significant innovation for the sector.
Solution
Our test specialist played a central role in validating the new operating software through a comprehensive, collaborative, and risk‑driven approach:
1. Structured Test Design
- Tests were defined based on risk levels and client requirements
- High‑risk scenarios received deeper, more intensive testing
- TMap and DTAP ensured consistency and traceability
2. Introducing SCRUM to Industrial Automation
- Brought agility to a traditionally waterfall‑driven environment
- Enabled iterative testing and continuous improvement
- Improved communication between all disciplines
3. Close Collaboration with Stakeholders
- Frequent consultations ensured alignment on goals, risks, and methods
- Stakeholder involvement increased ownership and transparency
4. End‑User Testing
- Blocking administrators (end users) executed tests under guidance
- Testing occurred not only on the final product but also during the creation of the A‑environment
- External influences were simulated to mimic real‑world conditions
5. Comprehensive Scenario Testing
- The barrier was tested against every conceivable operational scenario
- Unit and system testing methods were evaluated and refined
- The test strategy evolved continuously based on findings
Result
The structured, collaborative, and risk‑based approach delivered significant improvements in software quality and operational reliability:
High‑Quality, Reliable Software
The new operating software met the highest safety and reliability standards, capable of handling extreme and unpredictable conditions.
Effective Multi‑Stakeholder Collaboration
Continuous communication ensured a smooth, coordinated testing process.
Innovative Testing Practices
Introducing SCRUM into industrial automation set a new benchmark for agile testing in critical infrastructure.
Realistic Testing Environment
Simulated real‑world conditions in the A‑environment ensured the software was fully prepared for deployment.
Conclusion
The Maeslant storm barrier project demonstrates the power of combining structured, risk‑based testing with agile methodologies. Through innovation, collaboration, and rigorous validation, our test specialist ensured the delivery of high‑quality, dependable operating software for one of the world’s most critical flood protection systems.
This project highlights Nekst IT’s ability to support complex, safety‑critical infrastructure with modern testing practices and deep domain expertise.