Benchmark MaaS - Entretien Peter Theyskens
Description en une ligne : Cet entretien avec Peter Theyskens a été réalisé le 15 décembre 2021 dans le cadre du Benchmark MaaS. Il a été mené par Ghislain Delabie et Marguerite Grandjean. Il a été réalisé en anglais.
He just finished his job with Department of Transport of Flandres. H2020 Research in mobility data EU Program.
Call for funding around smart mobility
We do matchmaking. Talking to Imec (Belgian org grouping different universities)
→ https://www.imec-int.com/en Can be a city or a transport authority in Belgium.
What's the use of EU project ? Lots of project but not much being done around standard - it's a problem and an opportunity...
Yes, very scattered and fragmented. E.g. MaaS Alliance: Ertico does a lot of the matchmaking. I’ve been working on a lot of MaaS projects, e.g. Scale Up about MaaS governance → https://www.scale-up-project.eu/about → http://www.maas4eu.eu/
Last 10 years has seen lots of activity around smart cities, starting with IoT architecture. The MaaS ecosystem hasn’t found the right business model yet. The original idea of one MaaS app that will rule it all (MaaS 1.0, B2C) is not happening. Got subsidized but didn’t reach maturity (e.g. MaaS Global). I’ve been working in MaaS for 4 years. Low maturity. Market focused on supply side (top-down) and not customer-centric side (simply what the user needs).
In Flanders, I worked on standards with OSLO (Open Standards for Linked Organisations). Mobility standard that is a semantic ontology, using ‘linked open data’. Started translating in English. Launched early 2020. Syncing with ESA and other SDOs. A MaaS technology architecture roadmap, that is not happening today. Links with TOMP API ?
A lot of other standards are available. e.g. GBFS, Datex, … We studied all of them and with MaaS Alliance and OASC, we’re leading activities this year. OASC = Open Agile Smart Cities. MIMS = Minimum Interoperability MaaS Systems.
3 years ago I helped create GTFS-RT in Belgium. Automatic generation of data for all operators. They already did it in Belgium (MMTIS European Directive, because Netex required, but also use GTFS-RT). Subsidized by government. In OSLO, also developed a NeTEx/CD profile, Netex being a requirement for the MMTIS directive. We defined a semantic ontology (a trip, booking…) for all the parties in the market.
I also work on the e-Hubs project (with MPact).
Also participate in a working group for a standard between NL/VL (crossborder issue in Belgium). Ferdinand was supposed to be Head of Benelux Living Lab, with some cities in Belgium, to look at crossborder MaaS use cases, to implement MaaS pilots. Using TOMP. In Flanders, we established a common mobility dataspace, setting up an infrastructure. Data as a Service. Standards-based data service comparable to TOMP. Activities done in Flanders in the last few years, along with Gaia-X, is one of the way of combining all the data to reuse it. Establish global EU data space as a key data store
Worked on Flanders on an idea of Mobility Account with Utilisateur:Gabriel Plassat. It’s part of the solution for an integrated MaaS. Personal data is lacking in the industry for the user-centric dimension, leads to the fragmentation we’re seeing. So roadmap = align ESA and W3C and Netex-Static evolutions. e.g. SNCF work on legacy systems in rail. ITxPT have developed their own NeTEx Tarif. But not in sync with the other standards projects being done.
One of the problems today is integrating not just MSPs, but also financial support to develop a level playing field. ITS Belgium is going to set up an innovation cluster, with a budget to help your architecture become compliant with the required standards.
Mobility Central: a MaaS player by the Department of Transport in Flanders. 200m€ next year. Complete TOD, rural mobility, connecting to train, bus, tram… Demand-responsive transport and shared mobility through the country. Required in Flemish region for all MSPs in the production implementation to be OSLO and TOMP compliant. Flanders is among the only countries that have ticket APIs from the 4 PTOs.
How do the MSP that are not compliant yet react ?
The largest players like blueBike already have a ticket API and RT availability Some are open and some are defensive. Lots of the players consider everyone should use their own system and consider themselves as a center for MaaS.
How do you deal with it ?
- Regulatory basis : minimum data to be shared legally in Finland
- Government subsidies for innovation.
- Number of requierement still need to happen to move in forward to a MaaS level 4
- DG Move is doing MDMS to look at MaaS level 3 and 4. requierement to evolving to interoperable ticketing
Today biggest problem is that MaaS misses digital transformation.
Do you have examples of demand-based projects ?
Google and Facebook, in mobility not happened yet.
What are implementations of MIMS ?
There are projects in the Fywair Published a white paper with MIMS to be implemented
What is common Mobility Datasaoece ?
- Initiative by Industry 4.0 Germany / France (car industry, with Daimler &co)
- European Data strategy: all Data shared in mobility should be shared in European context in
- European Mobility Data Space. Big initiative.
== At project level, how can these big frameworks translate ? When we work with projects in France , people are focused on their basic project needs.
Usually it depends on specific projects. Big difference between innovation research & standards actually used, like GTFS. Lots of delay between findings of European level and implementations. What we try to do is to already implement in real production environments. It’s up to the ones who implement it to build generic services for reuse. Lots of silos, limited smart city applications available for users. It’s not just real users of standards, but at process level, have to evolve from big scope projects funded by governments, onto a continuous digital improvement process, to change previous century IT into agile processes. Improve speed of innovation. I built a ticketing system for Flanders in 6 months, rather than a lengthy public tender.
What kind of data / interdaces do they develop ?
PDS: Personal Data Store My Mobility Account Personal Data as a way to build interoperability between MaaS. Nowadays is not enough user-centric NeTEx tarifs: PTAs like SNCF in France work from legacy systems. At MaaS Alliance, some people like ITxPT have developed their own NeTEx Tarifs (level 3 implementation). Need for better sync.
NAP should evolve to RT broker to quickly implement any service. Not offering service to reusers.
Prise de note sur le PAD (cocher si Oui) ? Non
Document Central (CR) :
Evénement lié :
Organisations impliquées :
Animateur Atelier :
Défi lié à l'Atelier :
Commun(s) impliqué(s) :
Projet en cours à associer :
Communauté(s) d'intérêt impliquée(s) :
Personnes clés à solliciter :
Actions décidées par les participants :
Espace d'échange FORUM :
Espace d'échange CHAT :
Prochaine Etape : n/a
Autres informations :