Each time a person uses a transport service they can create a trail of data behind them. This trail is particularly rich when technology is used as either the medium for purchasing (e.g. a credit card or online payment service) or when used for the actual transportation (e.g. a ride sharing app, a smartcard, etc.). …
Continue reading “Creating a joined-up picture of customer mobility”
Following recent contribution from transport subject-matter-experts (SMEs) and technical specialists, we have now update the draft API Specification. This draft is currently at version 0.2https://app.swaggerhub.com/apis/open-transport/p-customer-account/1.0.2 Note: This API Specification is not yet at a peer review stage. If you would like to be involved please contact us
We believe that the use of an Open transport API will facilitate the standardisation of digital account integration for transport providers. Which will in-turn help to bring true interoperability of data, such as ticketing/purchase and journey information. But the private sector transport cannot implement this initiative alone. It requires universal support to make the change …
Mobility-As-A-Service (“MaaS”) is the concept that users of transport or transit services migrate away from personally owned means of transportation and adopt an on-demand & pay-per-use service instead. This shift in behaviour (and potentially billing) means a user can then choose their preferred trip based on: cost, time, environmental factors, convenience or a combination of …
Continue reading “How does an Open Transport API support the aims of MaaS?”
An Open Transport account standard can potentially be used for many different purposes (some of which we may not even know about yet). Some examples of account interoperability could include: Enable a customer to view the details of a joint rail & subway or a combined bus & ferry ticket Presentation of all transport permutations …
Continue reading “What is the purpose of integrating Transport Accounts?”
In this site we have explained the concept behind our Open Transport API and it helps different accounts integrate with each other via a common a API standard. To communicate this better, we thought we would also create this diagram to help describe how things will work. As you can see below, different online accounts …
Hayden’s recent article on LinkedIn explains that some USA public transit operators are using loyalty schemes to try to shift customers to their less congested (and often more environmentally friendly) modes of transportation. https://www.linkedin.com/pulse/supporting-loyalty-rewards-fragmented-transport-hayden-sutherland But how could such a scheme work in those areas where transportation services are fragmented, deregulated, privatised or just provided by …
Continue reading “Supporting loyalty in fragmented transport ecosystems”
We are pleased to announce that we have created and published an initial draft Open Transport Application Programming Interface (API). This can be found on SwaggerHub here: https://app.swaggerhub.com/apis/open-transport/p-customer-account/1.0.1 The aim with any open standard is to: Give it away, so that it can be adopted as widely as possible Encourage feedback and suggestions Allow it …
What problem are we trying to solve? Well… Providing a self-service digital/online presence is a necessary requirement for any transport solution. Regular customers and visiting tourists alike expect this, plus the amount of understanding & insight that can be gained from a single source of online customer data has multiple benefits for operators and authorities. …
Open Transport - Transport & Mobility Data Interoperability 