MaaS in Vlaanderen

360°
 infrastructure
TIME TABLE …table of
content…

Hard-hearing
Journey

BELLOT
MaaS
Customer’s Experience
EXPLORER
Customer’s CONCENTRIC service Nettex

ARTIFICIAL INTELLIGENCE
Service INTERMODAL ROUTE PLANNER
interuptions INTERUPTION
SMP

(BIG) DATA
API
TICKETIN MOBILIT

Settlement
BGTS
RITUALSIST G
Law, mobility
Y
budget NEURAL
NETWORK
GTFS-RT

SMART MOBILITY PLANNER

TSP
PAYMENT
elderly BLOCKCHAIN
AI-assisted

INTERFACE LESS-MOBILE
BLINDness weather

TMaaS REAL TIME Customers

Journey, eco system providers TSP/PTO

Steppy

Smart
Mobility MaaS
Planner
operator

Lime

Scotty
taxi
Uber
Journey
 Customer Centric privacy management
TSP/P
TO
Customer_ID1 Klant_ID1

1 MaaS 2 Klant_ID1

operator Klant_ID1

Logging initiating Klant_ID1

activities
Klant_ID1 Klant_ID1

Klant_ID1

billing

Klant_ID1

settlement
3
payment

The MaaS User manages and controls the access to personal

NMBS MIVB DE LIJN
data (ID, travel preferences and ‘history’, payment data, and
other). TSP will only have access to Customer’s data:
BLUE i) When granted by Customer, and ii) having serviced the
CAMBIO MOBIT BIKE Customer
Journey
TSP#X TSP#Y TSP#Z
Note: “Settlement” : blockchain (private, consortium)
MaaS - 360° - Customer’s centric services
• Basic functionalities
• Onboarding : profile, payment preferences (card-on-file, third-party payment scheme), [“know your Customer”]
• Route planner (incl. requirements of less, or disabled people) : taking into account season pass, profile settings,…
• Ticketing : single, multi ticket, season pass, bundle(-s)
sto m er ’s
• Payment : cash, vouchers, credit, debit cards, Direct Carrier Billing, invoice Cu
• Journey x p e rience
: location guiding to –next- stop, TSP, alternative, re-routing, E
• {data, big data lake}
• For less- mobile , disabled persons
• Customised transport
• Deaf, hard-of-hearing, blind persons, elderly persons
• Help-desk assistance, enhanced – personalised – assistance
• Special features
• Indoor (building, public areas) gps’-function
• Occupation rates of TSP (public transport), impact on your journey
c ed
• AI-assisted operations enhancement (neural network) Enhan r ’s
• Prediction of your next journey stage u sto me
C
• Swift intervention in case of abnormalities, or service interruption x p e rience
E
• Management
• MaaS
• Billing, settlement
• Integration van TSP’s
• TMaas, management of supply & demand of Customers and transport provider/service
 TSP capacity management
demand- side
supply-demand

MaaS Big_Data Customer's concentric

profile
behaviour
Next slide

weather

predictive (neural network)

behaviour of the Customer
incidents
Customer’s (traffic, mass events,
Experience MaaS Operations road incidents, fall
-out of
management
 • profile
individual • Behaviour
• Specific requirements
• profile
family • Composition, behaviour
• Specific requirements
Customer's concentric • profile
profile
behaviour groupe(-s) • Composition, behaviour
• Specific requirements

• Profile
‘business-travel’ • Specific requirements

Profile: age, own car or /and bike, weather-influenced travel behaviour, preference transport modi, regular festival, sport events,…
Specific requirement: handicap, less-mobility, blind, hard of hearing, wheel chair, buggy (children),…
OV
other
MaaS car

other
b
i
k
e
MaaS in Vlaanderen
Technology assisted
…..
• Block(-chain), python coded
• Certificate (signing)
• Timestamp
• Hashing
• Trans actioning
• Real time data (alle TSP en OV, indien beschikbaar)
• Weersimpact op transport in brede vorm (fiets, te voet, publiek transport, alternatieve
middelen (shared services), auto,…) [ 13-16% modal shift, afhankelijk van ‘severity’]
• Impact door ‘events’ en ‘incidents’(welke oorzaak dan ook)
• Artificial intelligence & neural network voor optimalisatie van de ultieme Customer’s
Experience!
• Inclusief de bijzondere behoeften van ‘minder-validen’, die eveneens van een ‘ultieme
Customer’s Experience’ kunnen genieten.
 Success keys for MaaS
• qualitative and widespread 4G coverage, preferably 5G (roll out in preparation)
• widespread smartphone usage;
• cashless payment processors;
• contactless interchange of data;
• data (preferably real time data);
• legislation (i.e. mobility budget);
• need to change mobility of the Users (roadworks, eg. Antwerp );
• separate driving lanes for both tram, and buses;
• {popping-up idea to limit, or restrict the use of widespread ‘fuel cards’, attached to
the ‘salary cars’}
will need to form the base of any comprehensive MaaS system, alongside the ability of passengers to interchange seamlessly between
transport nodes, with this vision requiring the collaboration of diverse stakeholders, which may need support of Authorities to establish.
Note:
seamlessly interchange: Leuven initiates clusters of mobility ‘centrals’ on selected areas across the town. On these ‘centrals’, a variety of
mobility services are centralised (coming together);
Infrastructure, and technology assistance
• MaaS will be successful if several conditions are met. Most of these conditions are without any doubt in the hands of Governments, Federal, or local.
• Buses are as fast as the surrounding traffic.
• Separate bus lanes are imperative. Also buses and trams must be enabled with features to influence the traffic lights when nearing a cross

• Government is taking some interesting initiatives to enable the shift:

• mobility budget. [potentially, Blue Ocean’s progressing to Red Ocean]
• Questioning ‘fuel card’ available for some Employees (part of salary car package)

• If / when Passengers will be confronted with the real transport cost for the society, they will be more tended to other mobility modes, than only
usage of a ‘individual car’-solution.
• Stepping on a public transport vehicle (bus, and tram), induces transactions.
• This can be i) ticket, ii) ticket type selection, and iii) ticket payment (selection of payment method). This causes time delays for the ‘next
‘passengers, and later departure of the public transport vehicle, causing delays in the line.
• Facilitating this process, would enable a faster throughput of people and transport vehicles.
• [there are several cases where payment is done ‘on the vehicle’, when seated, with i.e. QR enabling apps]

• Correct and accurate passengers ‘counting’, generates data for the Operator to manage additional vehicles on the line (loaded tram, or bus, on rush
hours, or rather unexpected moments in time). [ akas: occupation rate]
• Information sharing could facilitate the Operator to offer more transport vehicles, at a certain moment of time (i.e. Event organisation indicates end
of an event (with many people), so the Operator foresees additional vehicles)
 TSP capacity management
demand- side
supply-demand

MaaS Big_Data Customer's centric

profile
behaviour

weather

predictive (neural network) behaviour of the Customer

incidents
Customer's Experience (traffic, mass events,
MaaS Operations road incidents, fall
-out of
management
 Kohonen

In concept verwerkt, of beschouwd:

 In concept verwerkt, of beschouwd :
https://www.mckinsey.com/featured-insights/artificial-intelligence/notes-from-the-ai-frontier-applications-and-value-of-deep-learning?cid=other-eml-ttn-mip-mck&hlkid=4ae869ea19e04091b1e3e02de73db47e&hctky=9583324&hdpid=3b57a116-183f-412e-a787-
f8e957290e64#part1
 time

Blockchain approach
geo

TSA
Start End
journey journey

Ticket; code;
QR M-ticket; mobib#
mobib#
mobib #

Smart_contract_ID#
User_ID#
Smartphone_ID#;emei
journey Name_user
User_ID# Mobit: Recorded data: Surname_user
Bus: (birthdate)
Train: Timestamp_in;timestamp_out
Blue bike: TSP_ID#
Mobib_ID#;m-ticket_#; validity_identificatory;
Traject_coordinates_in;traject_coordinates_out
Payment_amount_1
Consent&privacy NFC(+Bluetooth) is
Policy, signing policy recommended
-> encryption, hashing
MaaS
CRM
Settlement layer VPN,SSL, PKI, server certificate, CA, RA, policy

Other TSP_x Other TSP_y

Mobit De Lijn NMBS-SNCB Blue Bike
 Blockchain approach
geo time
Both will be the same
‘device’
Sign-on MaaS   Route planning   delivering service   payment   CRM
[Smart_Contract] [Smart_Contract]
User ID# (certificate) User ID# (certificate) User ID# (certificate) User ID# (certificate)
(smarphone ID#) (smarphone ID#) (smarphone ID#) (smarphone ID#)
name User name User name User Name,voornaam User Collect ‘big
voornaam User voornaam User voornaam User (birthdate) data’ :
(birthdate) (birthdate) (birthdate) timestamp management
(time_indication, login/access) (time_indicatie, login/access) timestamp (tsp_ID) steer
Consent&privacy (tsp_ID) (tsp_ID) ticket ID# Pro-active &
Consent&privacy ticket ID# Validity identificator predictive
Customer
Travel/stage coordinates Travel/stage coordinates behaviour
Consent&privacy payment_amount_1 marketing
Consent&privacy settlement
Tariff policy, policy
Hashing & signing
hash algorithme hash algorithme hash algorithme hash algorithme
################# ################# ################# #################
TSP_ID_1 TSP_ID_1 TSP_ID_1
     MaaS DB – back office    
hash algorithme hash algorithme hash algorithme hash algorithme
################# ################# ################# #################
TSP_ID_1 TSP_ID_1 TSP_ID_1
       (GATEWAY)-TSP      
"+key "+key "+key "+key
hash algorithme hash algorithme hash algorithme hash algorithme
################# ################# ################# #################
TSP_ID_1 TSP_ID_1 TSP_ID_1
 User ID# (certificate)
(smarphone ID#)
Name,voornaam User
(birthdate)
timestamp
(tsp_ID)
hash ticket ID#
Validity identificator
traject coördinaten

payment_amount_1
CA42750ABCBE20F46DB22C690D4B89CC52BCC88AA4C72C56DE7950E399BC9C6E
Consent&privacy
Certificate Tariff policy, policy

signature

timestamp
 MaaS
Wat is belangrijk
 stop
_5

4 min +2min
6 min
stop
_17
6 min 6 stop
time table _16
+1 min min
+1 min
3 min
stop
stop
_15 stop
_14
_6
2
1 min 5 min min
stop
home (start point) 8 _7
min

at
walk to hour
impact of RT walk to platform
starting stop tabel
line TSP (elapsed arrival at platform (total assessment
time (elapsed (elapsed
time) station (elapsed travel
time) time)
(S time) time) time)
line blue 11:00 0:01 0:10 0:03 0:14 0:03 0:17 late
line green 11:00 0:08 0:05 0:00 0:13 0:02 0:15 timely
 tsp_
tsp_ 2**
2*

tsp_
2

1
TSP_

time
 exact (bus) stop location
example : Mechelen railroad station

P_10

NMBS- station (entry) NMBS- station (exit_1)

7 overarching categories in users’ satisfaction survey:
1. onboard experience:
1. Cleanliness,
2. comfort,
3. seating capacity,
4. onboard information,
5. crowding,
6. quality of vehicles,
7. safety,
8. Illumination,
9. temperature and
10. accessibility (physical).
2. customer service:
1. Driver and personnel’s attitudes,
2. personnel skills and
3. complaint dealing
3. service delivery:
1. Reliability,
2. on-time performance/ punctuality,
3. frequency,
4. travel time,
5. access time,
6. network coverage,
7. number of transfers,
8. service provision hours,
9. convenience,
10. stop location,
11. station parking and
12. waiting time
7 overarching categories in users’ satisfaction survey (2)
1. waiting conditions:
1. Waiting conditions,
2. information at stops and
3. safety at stops
2. Costs:
1. Value,
2. types of tickets and
3. passes and
4. ticket selling network
3. quality of transfers:
1. transfer time and
2. ease of transfer
4. Image
1. image and
2. environmentally friendly
Journey, eco system providers

TSP/PTO Customer Centric privacy management

Steppy NMBS 2
Klant_ID1 Klant_ID1

Klant_ID1
MIVB initiating
1 Klant_ID1

Klant_ID1
DE LIJN
billing
Logging MaaS Klant_ID1 Klant_ID1
activities
operator Klant_ID1
CAMBIO
payment

Klant_ID1
Lime MOBIT

BLUE
BIKE De MaaS User beheert zelf de access tot zijn/haar/het
Scotty persoonsgebonden gegevens (id, reisgedrag, betaalgegevens,
…)
taxi
Uber
Journey