top of page

Why interoperability matters for urban mobility

Digital tools are now part of many everyday transport services. Passengers use apps to check routes, plan trips and access different mobility options, while operators use digital systems to manage fleets, monitor services and organise routes. Cities also receive information from a growing number of transport providers and platforms.


These systems are often developed for a specific purpose, which means they do not necessarily exchange information with other tools already in use. A public transport platform, for example, may use a different data format from a shared mobility service, while a logistics operator may depend on systems that are separate from those used by the city.


Interoperability refers to the ability of these different systems to exchange and use information. In practice, it affects how easily services can be connected and how information can move between operators, public authorities and digital platforms.


Connected transport services depend on systems that can exchange information and work together
Connected transport services depend on systems that can exchange information and work together

How this affects transport services


For passengers, limited integration can be visible when different parts of the same journey require different apps or platforms. Planning a route, checking the availability of a shared vehicle and accessing another transport service may all involve separate systems.


The situation can be more complex for transport operators and public authorities. Information may come from several providers and technologies, using different formats and processes. Combining these sources can require additional work, particularly when cities want to compare information or coordinate services.


As more providers and digital tools become part of urban transport, these connections need to be considered when new systems are introduced. Public transport authorities, private operators, shared mobility providers, logistics companies and technology providers may all use different platforms while operating within the same urban transport network.


This is also relevant for pilots. A digital solution may initially be developed for a limited number of vehicles, users or operators, but its requirements can change if the project is expanded. At that stage, the system may need to exchange information with other operators, public platforms or existing data sources. Decisions made during the initial development can influence how difficult that integration will be later.


Interoperability also depends on coordination


Technical compatibility is one part of the process. Organisations also need to agree on the information that can be shared, the standards that will be used and the responsibilities of the different organisations involved. Data ownership, privacy and system maintenance can also influence how information is exchanged.


Some of these questions have already appeared in UEMI projects working with digital mobility.


In Buenos Aires, interoperability was among the implementation considerations discussed during ACCESS workshops on digital solutions for urban logistics. The workshops brought together stakeholders to examine how proposed solutions could work under local conditions and what would be needed for their implementation.


GEMINI has also addressed interoperability in the context of shared mobility, including discussions around common standards, open interfaces and mobility data sharing between cities and service providers.


Although the projects focus on different areas of mobility, both involve digital services that need to operate alongside existing systems and organisations.


Considering interoperability during development


When a new platform or service is being designed, project teams can already identify which systems it may need to communicate with and what information will need to be exchanged. They can also check whether existing standards can be used and consider how additional operators or services could be included if the project expands.


These decisions are particularly relevant for projects that begin as pilots but are intended to continue or grow. A system that works well within a limited project may require changes when it is introduced in a larger network with more users, operators and data sources.


For cities and mobility projects, including interoperability in these early discussions can help identify technical and organisational requirements before the system is already in operation.

Comments


Urban Electric Mobility Initiative (UEMI) gGmbH

Kopenhagener Straße 31E 10437 Berlin, Germany

 

Mobility Hub of the Urban Living Lab Center (ULLC) 

ULLC Mobility Hub @UEMI I Gutenbergstr. 71-72, 14469 Potsdam, Germany

secretariat@uemi.net

 

©2025 by UEMI

bottom of page