A discussion with Rijkswaterstaat

A discussion with Rijkswaterstaat

In one of the previous articles, we introduced PortlinQ and outlined its key functions: PortlinQ: Built on Collaboration | DiVINE – Digitalisation Vision Inland Navigation Europe. Given the strong relevance of PortlinQ, we conducted an interview with Martijn van Hengstum, Program Manager Digitalisation of Inland Shipping at Rijkswaterstaat, to further explore the topic. Building on the previous article about PortlinQ, here is what emerged:

 

  1. What is your role in Rijkswaterstaat? What is the role of Rijkswaterstaat in PortlinQ living lab?

As a program manager digitalisation of inland shipping at Rijkswaterstaat, I am responsible for coordinating the PortlinQ program, ensuring alignment between stakeholders, and guiding both the technical development (Track 2) and the organisational and governance aspects (Track 1).

Rijkswaterstaat plays a facilitating and coordinating role in the PortlinQ Living Lab. We do not develop applications ourselves, but we create the conditions for collaboration by defining the framework, bringing stakeholders together, and ensuring alignment with national and European policy initiatives.

In the Living Lab, Rijkswaterstaat acts as a neutral orchestrator: connecting inland ports, service providers, and app developers, while ensuring that the solutions being tested are scalable, interoperable, and aligned with public values such as data sovereignty, EU-data policies, security, and interoperability.

 

  1. In practice, what challenges in data sharing or coordination does PortlinQ aim to solve for inland navigation stakeholders?

Digitalisation is becoming increasingly important for inland ports, but in practice many ports and service providers still operate in relatively fragmented and locally optimised systems. This makes it difficult to exchange data, align processes, and scale solutions beyond a single port or region.

PortlinQ addresses this by introducing a shared set of agreements and standards for data exchange. A key principle is federated data sharing: data remains with the source and can be shared securely and in a controlled way when needed. This avoids central data storage, gives parties control over their own data, and lowers the barrier to participate. For ports and service providers, this means they can connect once and interact with multiple parties. For skippers, it leads to a more consistent and user-friendly experience across different ports.

 

  1. How does PortlinQ work in practice for stakeholders? Can you share a concrete example of how it improves data exchange or operations?

A simple example is a skipper using an app. The skipper selects a port, sees available services, and chooses one. After giving consent, the process runs largely automatically. The app, ports, service and billing can be executed by different organisations, cooperating through PortlinQ.

For instance, when a vessel enters a port area, a geofence event can trigger the start of a service or notify the port system. This reduces manual actions and ensures that all parties work with the same information.

 

  1. What have been the main challenges in implementing PortlinQ (e.g. technical, organisational, or stakeholder-related), and what barriers to wider adoption still remain?

The biggest challenge is not technical, but organisational. Getting different parties to agree on standards, roles, and responsibilities takes time.

Other challenges are defining common standards (for services, APIs, data) and setting up a workable identity and consent model. For wider adoption, key steps are still needed around governance, a clear business model, and scaling up the number of participants and to integrate existing solutions into an interoperable eco-system, including financial en organizational arrangements.

 

  1. Based on your experience with PortlinQ, what key aspects should the DiVINE project prioritise when developing a digitalisation vision for inland navigation and why?

Based on our experience, a few things are essential:

  • Focus on federated data sharing rather than central platforms
  • Invest in common standards (APIs, data models, service definitions)
  • Develop a solid identity and trust framework
  • Pay attention to governance and collaboration, not just technology
  • Test solutions in practice through living labs
  • Promote cooperation between different stakeholders

Digitalisation in inland navigation will only work if technical solutions and organisational agreements go hand in hand.

Related Posts