Modern mobility needs account interoperability

The way that people now travel in rural areas, suburbs and cities has changed (and will change further and more quickly) as customer needs have evolved and mobile technologies have gained increasing acceptance. Transportation users have become more used to mixing modes that combine mass transit such as rail, subway and bus services with more private services, such as car & bike sharing, scooter and other micro-mobility initiatives.

Each of these services now typically provides an online account to plan, book, view and manage each mode of transportation separately. Rail tickets and journeys can be viewed in a user’s train account, bus journeys are stored in an online bus account and individual car hire websites just show the bookings made for their vehicles. There are exceptions (such as Uber, which now allows other services such as electric scooters to also be booked within their App), but the usual situation is still “one mode, once account”.

However, as transport increasingly moves to more of an on-demand proposition, which should ideally provide the best end-to-end (door-to-door) solution in the cheapest, easiest or greenest way… the old data silos created for each mode are going to be an issue.

Data about a user’s complete journey therefore either needs to sit in a central (aggregated) account, or the individual accounts need to find a way to integrate between themselves (federated) and share the necessary data to provide a single joined-up view.

%d bloggers like this: