Uploaded bySami Pippuri
MaaS for MyData2016
The document discusses the challenges of urban mobility due to increasing urbanization, leading to traffic congestion and inefficient transport solutions. It introduces 'Whim', a unified mobility service that simplifies travel through a single app, enhancing user experience and promoting car-free living. The document also emphasizes the need for collaboration on common definitions to foster a consumer-empowered mobility ecosystem.
More Related Content
MaaS for MyData2016
- 1. Building the Future ofMobility
- 2. The key challengesof 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
- 3. Mobility as aService is 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
- 4. 4 We want to: •Give you back 90 minutes to your day • Make sure you have full freedom of mobility • Take away the pain of ‘how do I get there’ • Make sure you’re not a polluter • Under a simple pricing scheme Introducing Whim: the first mobility operator service
- 5. Winner takes all Public transportation Takes itall Roaming ecosystem Three ways for markets to evolve Winner Takes it all is a lucrative proposition for incumbents PT takes it all is always restricted geographically and in choice Roaming Ecosystem empowers the consumer with choice Which option do you prefer to see as the future?
- 6. Whim is builtfor - and with – ecosystem APIs Routing Traffic Operator Traffic Operator Traffic Operator Transport Operator Weather Payment Identity Rule Engine Customer Portal Whim backend APIGW Whim Apps OTP, GTFS MaaS-API JWT BPMN EMV OWM Data
- 7. Common interchange definitionshelp drive MaaS business forward, by enabling consumer choice Routing Traffic Operator Traffic Operator Traffic Operator Transport Operator Weather Payment Identity Rule Engine Customer Portal Whim backend APIGW Whim Apps APIs –Booking, Ticketing, Roaming Commercial Agreements Ticketing Definitions Trust Model Mobility Data Interchange Other Provider
- 8. Current State ofPlay http://www.maas-api.org - Open Definitions for transport booking APIs - Reference implementation - System state diagrams - Documentation - TODO: LOTS! - Goal: have a set of definitions and policies to bring forward for approval in e.g. MaaS Alliance, other bodies - Goal: build a lean business-focused enabler that empowers consumers with choice of operator - Non-Goal: thickest spec possible, that is also difficult to implement in vendor-neutral fashion Call to Action Help the MaaS movement by working with the community on common definitions that increase supply to consumers Let’s connect and discuss!
- 9.