Mobility Provider Kickoff Meeting 12132018 1 Introductions VisionObjectives Delivery Approach Open Source Operating System Schedule Mobility Provider Integration Why be Involved ID: 780311
Download The PPT/PDF document "Multimodal Trip Planning Application" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Multimodal Trip Planning ApplicationMobility Provider Kickoff Meeting12/13/2018
1
Slide2Introductions
Vision/Objectives
Delivery ApproachOpen SourceOperating SystemScheduleMobility Provider IntegrationWhy be Involved?DataPrioritizationStaying Connected
TODAY’S AGENDA
2
Slide3MMTPA VISION
The future of transit is multimodal and on-demand
A shift away from personally-owned vehicles
A solution that uses both public and private entitiesIntegration with the Smart Columbus Operating SystemOne-stop shop to plan, book, and payAs the regional public transit provider, COTA is the ultimate owner
3
Slide4CITY OF COLUMBUS OBJECTIVES
Facilitate improved access to multimodal trip planning information
Increase usage of available transportation servicesImprove ease of multimodal trip planningProvide travelers with more convenient access to transportation service optionsIncrease access to jobs and servicesIncrease customer satisfaction
4
Slide5COTA OBJECTIVES
Reduce cash-for-fare payment on buses
Reduce onboard fare processing time Use centralized server/account-based processing Provide customers a “guaranteed lowest fare” system Retrieve accurate and timely ridership and revenue data Support open architecture and new technologies
5
Slide6PROJECT COMMUNICATIONS
6
Communication Type
Frequency
Format
Participants/ Distribution
Deliverable
Owner
Scrum Meetings
Bi-Weekly
In Person/WebEx
Development Team
Status and Metric Presentation
Lead App Dev
Demonstrations
Bi-Weekly
In Person/WebEx
City, COTA, Project Team, and Stakeholders
Summary of Live demo
Project Manager
Release Meetings
Milestone Dates
In Person/WebEx
City, COTA, Project Team and Stakeholders
Release completion report and New release kickoff
Project Manager
Overview Demonstrations
Monthly
In Person/Web Ex
City, COTA, Project Team and Stakeholders
Summary of Live demo with OS
Project Manager
Slide7DELIVERY APPROACH
7
A foundation of open, free, and proven technologies. A platform that is consistent with the Smart Columbus Operating System project.A distributed ledger (“blockchain”) offers redundancy, transparency, shared governance, and long-term viability.
The assurance that user data is not available to anyone unless volunteered to release.
All user-facing apps use the same codebase, but can run on different devices (Android, iOS, kiosk, PC).
Slide8OPERATING SYSTEM
8
Slide9SCHEDULE
9
Slide10SCHEDULE
10
Slide11SCHEDULE
11
SPRINT 1: ROUTE PLANNING WEB APP – 12/11/2018SPRINT 2: RECORD TRIPS TO BLOCKCHAIN – 12/25/2018
SPRINT 3: USER INTERFACE – 1/14/2019SPRINT 4: NATIVE MOBILE APPS – 1/28/2019
SPRINT 5: COTA + 1 MOBILITY PROVIDER – 2/11/2019
SPRINT 6: DATA COLLECTION – 2/25/2019
SPRINT 7: FEATURES FROZEN – 2/28/2019
Agile approach allows for user feedback and comments throughout the process.
Slide12DELIVERY APPROACH
12
Slide13DELIVERY APPROACH
13
Slide14WHY SHOULD YOU BE INVOLVED?
Subsidies for traveler (Employer Pretax and National Transit Database (NTD) funding)
Increase in shared rides and linked trips to other modes
Understand travel patterns in the regionAllows mobility providers to identify gaps in transportation servicesOS team will continuously analyze and update
Allows government agencies to:
Make policy decisions to meet the public’s travel needs
Understand shifts in transportation modes
Plan and invest in infrastructure improvements to meet the public’s travel needs
Access to funded Paratransit and NEMT trips
Connection to growing COTA ridership
Access to more riders (unbanked, low tech, mode shift from SOV)
Pay once across multiple modes
Promotion/marketing plan for MMTPA
Incentives and rewards will be used to promote use and services
14
Slide15Encourage the use of
accessible vehicles
to make sure a reasonable number of accessible vehicles is maintained.Maximize the riders per vehicle
while still maintaining an acceptable added travel time (X) or deviation time for the travelers. Encourage the use of transit as a leg of the trip if reasonable service is available from the origin to the destination.Incorporate the traveler’s preference profile for tradeoffs between cost, trip time, walking distance and mode preferences.
Verify
driver & vehicle qualifications
to meet NTD requirements (Opt-in program with drivers)
BUSINESS RULES
15
Slide16GTFS/GTFS-Real-time
Site: https://github.com/google/transit/tree/master/gtfs-realtime Service Providers: TransitGBFS (station)
Site: https://github.com/NABSA/gbfs/blob/master/gbfs.md Service Providers: Car Share/Docked Bike ShareModified GBFS (free_bike) Site: https://github.com/NABSA/gbfs/blob/master/gbfs.md Service Providers: Dockless Bike Share/
Dockless
Scoter Share
Modified TNC API
Site: See Modified TNC API
Service Providers:
Ridesourcing
(TNC)/Taxi/OnDemand paratransit/NEMT
Van Pool/Car Pool
Site: Waze Carpool API
Service Providers: Car pool, van pool, ride matching, etc.
Future APIs
Parking
Site: Alliance for Parking Data Standards (APDS)
https://www.allianceforparkingdatastandards.org/resources
&
ParkMobile
/
ParkColumbus
App
Service Providers:
Onstreeet
Parking (IPS/Conduent), Garages, Lots
MMTPA DATA NEEDS FROM MOBILTIY PROVIDERS
16
Slide17Provider_Locations
allows check if the provider should be included in the selection process for a trip from/to a transit stop. In general, a 15 minute (configurable parameter) arrival time will be used to show available vehicles.
Service Provider, Mode Type, Driver ID (if applicable),
Vehicle ID, Lat, Long, timestampTNC PROVIDERS DATA
17
Provider_Log
table needs to be maintained in the OS to allow tracking of the activated trips for payment to the Ride Share Providers. It will contain:
trip unique key,
Timestamp (initiation, driver acceptance, arrival at origin, arrival at destination),
ETAs (initiation, driver acceptance, arrival at origin, arrival at destination),
origin,
destination,
provider ID,
driver ID,
driver rating
whether it was an accessible request,
was car seat requested,
customer ID,
transit
tripID
,
status (Completed, Cancelled by driver, Cancelled by Customer, Open)
Slide18Before pickup request
Provides qualified drivers in area to service trip
Confirmation requestInitiates trip request to selected driverAllows drive response timeLogs trip to OS and payment to CPS
Vehicle update requestUpdates vehicle location every 30 seconds from initiation to completion for traveler display and notificationsCustomer rating requestProvides customer feedback and rating for driver and vehicle
TNC PROVIDERS API
18
Slide19Use business account to Provider API
All trip recorded to
SmartColumbus business account when requested on APIProvide periodic reconciliation of services - Monthly, weekly, dailyService Provider Web Portal
Dashboard for service provider monitoringReports available for all transactions and tripsAnalytics showing predicted travel patterns and needs for all modesOptional Access to CPS for your usersCan allow your app to provide payment on other modes of travelPayPal like landing pagesShared Traveler accounts in back officePayment broker API checks funds availability
TNC PAYMENT AND SUPPORT
19
Slide20Landing Pages
CPS Login page (can save on phone, but not to OS)
Proof of payment page (QR Code, NFC, BLE, Bar Code, Activation Code)Traveler account pages Add payment methodsAdd PII
Traveler parametersPayment BrokerData: request source, traveler account ID, service providerID, transaction amount, timestamp IVRData: If telephone activation requested at HUBS or Web Portal then send: tripIDService providerIDtravelerID
IVR Telephone #
CPS DATA NEEDS FROM MMTPA
20
Slide21MOBILITY PROVIDER INTEGRATION
21
Criteria
Point Value
Required for MMTPA
Require deep integration
N/A
Participate in Common Payment System
N/A
Primary Criteria (85 total points)
ADA accessible fleet
25
Provides service to underserved areas
15
Ability to transport multiple passengers
15
Licensed to operate in Columbus
10
Policies to support transit connections (FM/LM)
10
Able to provide car seats
10
Secondary Criteria (15 total points)
Flexibility with Incentives/Rewards program
5
Service available at a Smart Mobility Hub
5
Zero/low emissions fleet availability
5
Total
100
Slide22NEXT STEPS
22
Provide input on transportation capabilities by 12/21/18
Support in developing agreements
Participate in Demonstrations
Bi-Weekly
Monthly (aligns with OS demonstrations)
Participate in Release Meetings
Milestone Dates
Slide23Contact: Andy Wolpert
adwolpert@Columbus.gov
614-230-1798QUESTIONS?23