Mobility as a Service and making an entirely new solution complete with a new backend and a mobile client in three months, scalably and cost effectively

1. Building the Future
of Mobility

2. About Me
Sonera
Longish Nokia Career
- Software
- Music Industry
- Developer Relations across S40, Symbian, Maemo, MeeGo, Qt,
HERE, Flash, WRT, HTML5, Windows Phone…
- 2-time Webby Award Winner
SSH, Ixonos
Non-profit initiatives & startups
MaaS Global
Sami Pippuri
CTO, MaaS Global
@pippuri
#spaceselfie
Topicalio
Whim

3. Transportation is being hit by a
DIGITAL TSUNAMI.
So what is changing?

4. The key challenges of fast evolving urbanmobility
Urbanisation Travel problems
Insufficient
solutions
More people More traffic jams
Multiple
and disconnected apps
Route based
public transportation
Emerging transport
sharing
More vehicles Less parking space
More urban travel More time spent on PT
More complex travel More delays
Car ownership not fitting with
modern lifestyle

5. Cities can’t cope with urban mobilitydemand
2,8
43,2
67,1
2010 2030 2050
Urbanisation Current
alternative
Urban mobility demand 2010-2050 (trillions pkm.p.a.;%)
Source: Appendix
URBAN MOBILTYDEMAND
EXPLODES
2,6 x
3 bn
The number of vehicles on
the road worldwide is
projected to triple, to as
many as 3billion
by 2035.
37,2%
From1995 to 2013public
transportation ridership
increased by 37,2%,exceeding
the 22,7%growth rateof
the U.Spopulation
42 h
42 hours a year are
spent in a traffic
jam (USA).
106h
106 h/year on
average spent on
urban travel.
149min
on public transport
each day.
2 x
The world’s current total
of 1,2 billion cars could
double by 2030.
10,8 bn
In 2014, people took
a record -breaking
10.8 billion
trips on public
transport.
40%
of inner-city traffic
consists of vehicles
looking for a parking
space.
38min
38 minutes
(26 %) of which is spent idly
waiting for the bus or
train to arrive.
40%
with a 40 %
dissatisfaction
rate.
Private
traffic
Public
transport
New York
+68%
+55%
Travel
problems

6. Current options
Type of transport
Government role
Challenges
Increasing costs
Traffic jams and curfews
Privatecars
Mismatch between
supply and demand
Publictransport
Limited and expensive parking
Heavyrestrictions
NO SINGLE SOLUTIONEXISTS
Heavysubsidies
Urban pollution
Huge amount of disparate
service providers
Inefficient due to single
passenger jurneys
Low usage vs cost
Cost ofownership
More time spent on public
transport than ever
Extensive planning required
Cost ofoperation
Urbanisation Current
options
Travel
problems

7. The MaaS solution
Freedom from
ownership
A singleapp
Increased
efficiency
Access to all transport
without the need to
own a car
Hassle free
One intuitive app to manage
your travel needs
User friendly
Increased utilisation
rate AND route optimisation
WITH on-demand routing
Saves money

8. … AND TAILORED TO YOUR NEED AS MONTHLY PACKAGES?
Our product - transport sold by monthlysubscription
WHAT IF ALL TRANSPORTATION WAS CONVERGED…

9. Pilot Project:
MVP TEST AREA
Copyright Maas Global Oy 9
Tampere
Helsinki
Region
Turku
Region
Tallinn
Region

10. Perhaps the more
INTERESTING BIT
So how are we making this happen?

11. System Goals
Goals
• Scalable, cloud-based
• Mobile-first customer experience
• Utilizing readymade cloud APIs
• Infrastructure-as-code
• Establish industry standard APIs where they
don’t exist yet
• Open for ecosystem partners
• Create enthusiasm in the wider ecosystem –
enable e.g. Universities and smaller developer
houses around the world
Non-Goals
• Closed architecture or
lock-ins
• Exclusive deals
• Server infrastructure
• Intermediate, all-
encompassing frameworks
• Something for everybody

12. Loosely coupled Microservice API integrations
– flexible inclusion into MaaS framework
Routing
Traffic Operator
Traffic Operator
Traffic Operator
Transport Operator
Weather
Subscription Payment
Identity
Generic Rule Engine
Customer Support
Whim backend
APIGW
Whim Apps

13. MaaS tech Mission: Build a “Transport AI”
Anticipation,
Service
Optimization
“Transport AI”
BETTER SERVICE, HIGHER UTILIZATION

14. IoT and ML Powered Decision Making
Transport AI
API bridge
Analytics Store
TSP Adapter(s)
Routing API
Booking API
Service Bus / Registry
IoT API GW

15. Transport Service Provider Adapter
Flexible Routes (GeoJSON)
Fixed Routes (GTFS2JSON)
Real-time vehicles
Journey booking / ticketing
Journey payment
Contract Data
An open source framework and adapter for
integrating providers
• No lock-in to a single MaaS Operator
• Create open API standards where they
don’t exist yet
• Enable an ecosystem of developers
• Scale integration globally
Open Source Project (first focusing on bookings):
http://maas-api.org

16. Tech Stacks
iOS MaaS CoreAndroid
Swift Java
AWS SDK
AWS IoT Cognito …
Lambda (Node.js 4.x)
Serverless
AWS Components
REST APIs
Apps Backend Integrations
BPMN-js MaaS-API SBUS

17. Serverless Project Workflow*
Serverless w/ CloudFormation
autoinstall meta
mocha
Webpack+ Babel
Base toolstack
Travis CI
Manual
Deployment
Unit & integration
testing
sls X deploy
* Current state – not ideal!

18. Why cloud-native and serverless
Virtual Hardware Cost Set-up time Personnel
BEFORE 1 firewall/LB, 2 DB
machines, 2 frontends,
3 backends…
> $1500/month for 0
users
> 1 week just to have
an environment,
accounts, OS
installations,
networking rules,
databases..
DBA
infra engineer
Networking,
Backups, Updates…
Monitoring,
Developers
MaaS 0 EUR to set up,
< $100/month to
support ~5000 users
First routing demo on
day 1, capable of
scaling to thousands
of concurrent users
1 Senior Full Stack
Javascript developer

19. Lessons learned
Bleeding edge is sharp
- Serveless 0.5
- Testing & Deployment flow & management
- Remote Teams
- Learning curve & Hiring
- Unknown failure situations & debugging

20. Conclusions
Serverless computing was the right model to go for
- Effortless scalability
- Zero maintenance
- Stateless patterns
- Isolation
- Native Cloud Components
- Productivity
… but still a bit rough around the edges.

21. @pippuri
maas.global/jobs