Mobility systems across Europe are investing heavily in data, standards and interfaces. This work is essential. It allows information to move between organisations and gives technical systems a common language. Yet technical interoperability represents only part of the journey towards services that work across operators, regions and national borders.

Technology connects systems. Travellers experience services.

Data can describe a timetable. A standard can define how that timetable is exchanged. An interface can make it available to a journey planner or sales platform. Each layer reduces technical friction and creates valuable possibilities.

The traveller, however, experiences the combined service: which journeys can be found, which products can be bought, what conditions apply, whether tickets are recognised throughout the journey and who takes responsibility when plans change.

These questions reach beyond data formats and interfaces. They touch products, commercial models, passenger rights, operational routines and the relationships between organisations.

Six questions shape the mobility ecosystem

A useful way to understand the system is to separate six questions. Each question belongs to a different layer, and each layer needs to connect to the others.

Why?

Policy sets the purpose and the shared direction.

Who?

Authorities and regulation define roles, mandates and responsibilities.

What do we share?

Data makes relevant information available.

How do we describe it?

Standards create common definitions and technical languages.

What do we offer?

Products and services create the experience and the customer value.

How do we work together?

Governance connects the layers through coordination and shared decisions.

The optimisation problem

Every organisation has legitimate objectives. Operators optimise their operations and commercial position. Authorities optimise public value within their mandate and budget. Platforms optimise reach, conversion and the customer relationship. Technology providers optimise their solutions.

The combined result can still underperform. A technically correct exchange may support products that remain difficult to combine. A common interface may be implemented differently by different actors. A regulatory requirement may be fulfilled in ways that add friction elsewhere in the journey.

System performance therefore depends on the relationships between the layers, not only on the efficiency within each one.

Governance turns possibilities into practice

Governance provides a practical structure for the work that sits between organisations. It creates forums for coordination, clarifies where shared decisions are needed and establishes how those decisions are implemented consistently.

In mobility, this can include agreeing how common obligations will be applied, aligning product conditions, managing dependencies between sales and operations, and resolving issues that fall between formal responsibilities. It also creates the repeated interaction through which trust grows.

The aim is shared value for the traveller while each organisation retains its own mandate, commercial freedom and accountability.

“Governance is the infrastructure of cooperation.”

A better question for interoperability programmes

Technology programmes often begin with the data to be shared and the standards to be used. Those are necessary questions. A broader programme also asks:

  • Which customer outcome are we collectively trying to create?
  • Which decisions need to be shared, and who has the mandate to make them?
  • How will products, conditions and responsibilities work across organisational boundaries?
  • How will implementation remain coherent as actors and technologies change?

These questions move interoperability from a technical delivery to a system capability. Data and standards provide the language. Governance gives the ecosystem a way to use it together.