Skip to content

Case SRE 1: Lock Eefde

Around 2014–2015, Rijkswaterstaat was confronted with a structurally growing problem on the Twente Canal:
the existing lock at Eefde had become a capacity bottleneck for inland navigation. Vessel sizes had increased, traffic volumes were steadily growing, and the lock’s availability had become critical for the economic accessibility of the Twente region.

At that time, Rijkswaterstaat initiated the process of defining requirements for a second lock chamber, to be constructed next to the existing lock. The objective was explicitly not to replace the old lock, but to strengthen the system as a whole by adding capacity, robustness, and future-proofing to the canal corridor.

From a systems perspective, this marked a clear shift:

  • from a single-point-of-failure asset,
  • to a redundant, scalable lock complex supporting long-term network performance.


Seen through the IMPULS3 lens, the development around 2015 can be characterized as follows:

  • Stakeholder need
    Ensure reliable, future-proof inland navigation on the Twente Canal.
  • System function (stable)
    Enable controlled vertical transfer of inland vessels across water-level differences.
  • Solution evolution (variable)
    From a single lock chamber → to a dual-chamber lock complex, increasing capacity and resilience.

Crucially, the function remained unchanged, while the physical realization evolved. This distinction is central in IMPULS3 and explains why the requirements work at Rijkswaterstaat focused on capacity, availability, and performance, rather than on prescribing a specific design.


For this use case we start at the Analysis process step.

From a systems-engineering perspective, Lock Eefde is a critical enabling function within the Dutch inland-waterway transport system:

The second part of the Analysis process step establishes the properties and constraints of the primary function and identifies the secondary functions and their properties and constraints.

1. Primary Function

Properties of the Primary Function

(Once quantified, these become requirements in IMPULS3.)

2. Secondary Functions




3. System Properties (not tied to a single function)


4. System Constraints (overarching)

In the actual situation we would need to identify the properties and constraints for the secondary functions too. For this SRE case we limit the Analysis to the above.
In addition, we take the primary function definition as the first requirement as it does not need further quantification:

Quantified requirements derived from properties

  • Type: Requirement
  • Category: Functional property (capacity)
  • Rationale: Enables the intended vessel class on the Twente Canals and supports logistics to Twente.
  • Type: Requirement
  • Category: Functional property (hydraulic capacity)
  • Notes: This is the public figure stated by Rijkswaterstaat for the new chamber.
  • Type: Requirement
  • Category: System property (geometric envelope)
  • Type: Requirement
  • Category: System property (geometric envelope)

Vertical transfer capability

  • Type: Requirement
  • Category: Functional property (transfer height)

Throughput and network capacity contribution

  • Type: Requirement (system contribution / context requirement)
  • Category: Performance (capacity contribution)
  • Rationale: This is an explicitly stated Rijkswaterstaat capacity objective linked to the second chamber.

Note (IMPULS3 discipline): this is a system contribution requirement; it is measurable, but it is influenced by external factors (fleet demand, canal restrictions, traffic management). Still valid as a top-level quantified objective.


Operating window (service provision)

  • Type: Requirement
  • Category: Operational constraint (service window)
  • Type: Requirement
  • Category: Operational constraint (calendar exceptions)

Here’s a challenge for you: can you find sufficient (publicly available) information to quantify the following properties?

Properties that still require quantification (TBD)

  • Needs: the contractual/service-level target (e.g., annual availability %, max downtime per year) from Rijkswaterstaat’s service-level regime or the DBFM performance requirements. (Public sources confirm DBFM uses performance requirements aligned to Rijkswaterstaat, but not the numeric threshold.) Rijksoverheid+1
  • Needs: operational KPI definition (average/95th percentile lockage duration by vessel type and traffic condition).
  • Needs: quantified safety targets (incident rate, collision probability, acceptable risk criteria), typically from safety case / RAMS documentation.
  • Needs: the formal queueing KPI (e.g., “95% of vessels wait < X minutes”), commonly part of network service objectives or contract KPIs.

Below you find the information in the Configueres app. The information is visualized and structured according to the semantic principles (Nodes and Edges). You can follow the links by double-clicking on a rectangle (this is setting the viewpoint / perspective). The rectangle that is selected as viewpoint gets a red background. Top-down traces are usually made visible by selecting the “inverse” relations. But this depends entirely how the user has defines the relations of course. Try to follow the instructions below and see what happens. Have fun!

Top-down traces: start by selecting “Lock Eefde” as viewpoint.
Then select the inverse relations:
– (inverse) defines;
– (inverse) defines function;
– (inverse) constrains function;
– (inverse) specifies;
– (inverse) quantifies;


References

Rijkswaterstaat. (2020). Nieuwe sluis Eefde vergroot capaciteit Twentekanalen.
https://www.rijkswaterstaat.nl/water/waterbeheer/nieuwe-sluis-eefde

Rijkswaterstaat. (n.d.). Twentekanalen.
https://www.rijkswaterstaat.nl/water/waterbeheer/twentekanalen

Ministerie van Infrastructuur en Waterstaat. (2019). Ontwikkeling hoofdvaarwegennet.
https://www.rijksoverheid.nl/onderwerpen/vaarwegen

Rijkswaterstaat. (n.d.). Sluizencomplex Eefde.
https://www.rijkswaterstaat.nl/water/waterbeheer/bescherming-tegen-het-water/waterkeringen/dammen-sluizen-en-stuwen/sluizencomplex-eefde

Rijkswaterstaat. (2020). Sluis Eefde: Zo werkt de nieuwe sluiskolk (factsheet).
https://open.rijkswaterstaat.nl/@205704/sluis-eefde-werkt-nieuwe-sluiskolk/

Binnenvaartkennis. (2021). Twentekanaal (PDF).
https://www.binnenvaartkennis.nl/wp-content/uploads/2021/02/Twentekanaal.pdf

Rijksoverheid. (2025). J Deltafonds Rijksbegroting 2026 (PDF).
https://www.rijksoverheid.nl/binaries/rijksoverheid/documenten/begrotingen/2025/09/16/j-deltafonds-rijksbegroting-2026/J_Deltafonds.pdf


Loading