The innovative aspect has always been quintessential to the development of the TMaaS platform. From day one, TMaaS wanted to offer a forward-thinking alternative to the traditional traffic control room. TMaaS is aimed at small and medium sized cities, . The goal of TMaaS is to become a new, user-driven and future-proof concept for the analysis, management and communication of mobility data. An element vital to the success of TMaaS is that the innovative character of the project should always go hand in hand with a performant business model. But what exactly sets us apart from the numerous existing systems that integrate mobility data?
TMaaS wants to go beyond the ad-hoc development for the integration of local mobility data. Therefore, a high degree of flexibility in data governance will be necessary. There will be a choice between centralized and decentralized data and between external data (e.g. that belong to the providers) and proprietary data. We want to combine the data sources and find new ways to work with the data, to enable connected analysis (“One road for all mobility”). It is not sufficient merely to have data available; they have to be managed, connected and integrated, in various ways. Furthermore, it is important they can be compared to each other. Public transport data has to be linked to car and bike data, so all users get the same insights into what is happening on the road.
The aim of TMaaS is to improve upon the existing closed systems for mobility data processing. TMaaS wants to break out of this concept. We will look for ways to connect different providers in order to move away from the single-system practice. This could for example be done by installing API that allow third parties to offer new services to the platform. The idea is to transfer all available data to the providers, so they can use them in turn. For all of this we bear in mind that we do not use data that we are not allowed to work with. The main challenge will lie in the safeguarding and propagating of data licensing, privacy and data governance.
A key element to the success of TMaaS is its economic viability. How will we market our ‘product’ and what will the business model look like? In a way, this is as important as the development of the dashboard itself. The use of the term ‘marketplace’ has been deliberately chosen in order to stress the ‘economic’ aspect of the project. The idea is to provide local authorities with a tool that enables them to work with local stakeholders. Thus they can co-create urban mobility solutions and find new business models in connected urban traffic management. For example, they may ask a local app developer to develop an app for the TMaaS framework. In this way we will stimulate open innovation in traffic management, where various stakeholders can intervene and add to the system. This will lead to a greater degree of innovation when compared to working with closed systems. This is interesting for cities because it offers them the opportunity to develop new ideas with their citizens, local businesses, etc. It will also mean an economic boost for the region involved.