Web conference notes, 2024.08.29 (MDS Working Group)

Web Conference

MDS Working Group

Monthly on Thursday at 9am PT, 12pm ET, 5/6pm CET

Conference Call Info

Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4

One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom

Agenda

Meeting Agenda

MDS 2.0 for Taxis in LADOT

Intro and announcements (5 min)
MDS 2.0 for Taxis in LADOT
1. MDS for Passenger Services (5 mins) - Michael Schnuerle, OMF
2. History and Taxi Companies (10 mins) - Pierre Bouffort, Blue Systems
3. Vision and Integration (20 min) - Jarvis Murray, LADOT
4. IATR - Matthew Daus
5. SFMTA and CPUC - Julia Friedlander
6. Discussion and questions (20 min)

WGSC Meeting Organizers

Host: Pierre Bouffort, Blue Systems
Facilitator: Michael Schnuerle, OMF
Preparation: Michael Schnuerle, OMF
Outreach: Michael Schnuerle, OMF
Note taker: Craig Dittman, San Jose

Action Items and Decisions

Read LADOT's permit language for taxis - Section 300
Review OMF blog post with guidance on permitting and MDS for Passenger Services
Register and attend the OMF Summit in Los Angeles where this topic will be discussed by LADOT and Jarvis

Minutes

66 Attendees
OMF Slides
Recording - Password wK6UA6*W

Notes

Overview of MDS 2.0 for Passenger Services:

Development of MDS 2.0 took over a year, focusing on standardizing data fields already collected by cities for taxis and rideshare services.
MDS 2.0 simplifies the data collection process by providing a standardized format, reducing the need for cities to request similar data in different formats.
The release includes guidance on how to use MDS for passenger services, with recommended language for requiring the latest version of MDS for publishing digital policies and collecting vehicle information.
Operators and public agencies can use MDS to meet permit requirements and manage data collection. This can be done internally or by hiring vendors, aligned with defined use cases.

Integration of the Taxi Industry with MDS:

Collaboration with LADOT and Blue Systems focused on integrating the taxi industry with MDS 2.0.
The integration process was designed to be as seamless as possible, minimizing the effort required from taxi companies while meeting LADOT’s needs.
The main challenge was acquiring basic data, such as vehicle registration and trip details. LADOT now requires taxi companies to comply with MDS, specifically MDS 2.0.
Future plans include developing a fee structure to cover the costs associated with submitting data in near-real-time, ensuring sustainability for taxi companies.

Technical Aspects of Integration:

Initial integration efforts focused on minimizing the burden on taxi companies by leaving out certain features, such as fare rates and trip types beyond passenger trips.
Vehicle registration data was simplified, and some optional features, like accessibility and propulsion information, were not fully implemented.
These decisions allowed for a quicker integration process, though they limited some use cases. Lessons learned from this integration have informed future versions of MDS.
Data is important to understand rates and price setting, understand idling/roaming, know about accessible taxi patterns, learn hotspots to created dedicated taxi only lanes, and allows comparison of taxis and micro and bike directly. Not data for data’s sake
- VMT, empty w/ driver, sitting with fare, idling and roaming
LADOT requires real time data every 30 seconds from companies. Usually do it every 5 seconds (eg with scooters) but eased the burden for now
Airports around the world want to and require this data, and can ask for it
For taxis, LADOT is using MDS Agency to get data pushed to them, not using MDS Policy yet

Current Status and Future Directions:

The current integration provides the same level of information as more mature MDS integrations, like those for micromobility.
By using the same data visualization tools across different modes, LADOT can better compare and analyze data from various mobility programs, including taxis.
Efforts are ongoing to integrate TNCs (Uber, Lyft, Flywheel) into MDS. Initial progress includes data sharing through partnerships with companies like Curb.
There are signs that the TNC industry is becoming more open to data sharing, which could lead to further collaboration in the future.
Working to add a fee per user trip so taxi companies can recover their MDS and data setup and operation costs
Pushing for up front pricing requirements for Taxis, like what TNCs offer now
Regulatory limited by state to not allow asking for data from AVs and TNCs
Blue Systems just finished negotiating an MDS data sharing agreement with Lyft for San Jose
Want to ensure taxis can
- Maintain profitability
- Assist their growth in hotspots, loading zones, mobility hubs for olympics
- Ensure equity of service
Los Angeles has 2026 World Cup, 2027 Super Bowl, 2028 Olympics. Want options beside personal car ownership
- Waymo and 35 AV companies testing in CA
- LA has Carshare too
- Looking at Taxi only lanes. Bus only lanes coming soon. Bike lanes now on Hollywood boulevard
- 100,000+ TNC drivers, harder to manage than taxis, need data for operational management
- 10Ks of trips per day per venue, need to understand the fleets
Matt Daus from IATR commented about how if we ever want MaaS, what we are talking about today is essential
- Hoping to see Miami do this next
- International Association of Transportation Regulators is 1000% in support of MDS 2.0 and beyond
- You are all welcome to join us in Florida for the IATR conference where we will be talking about this and data
Julia Friedlander gave an update on the CPUC rulemaking on August 23 on the proposed decision from the CPUC on AV data. Link to PDF

Closing Remarks:

LADOT emphasized the importance of this work, particularly as taxis remain a significant part of the transportation ecosystem despite the rise of TNCs.
The integration with MDS will help LADOT manage transportation more effectively, with the potential for expanded use cases as more data becomes available.

LADOT Taxi Permit Language

302 Permitted Taxicab Service Companies and all vehicles operating under each Taxicab Service Company’s permit shall comply with the Mobility Data Specification (MDS.)
303 Taxicab Service Companies shall provide, through their own communications platform or through a third party, accessible Application Programing Interfaces (APIs) that meet the requirements of the Los Angeles Mobility Data Specification (MDS) as published on https://github.com/openmobilityfoundation/mobility-data-specification
304 Taxicab Service Companies shall have the ability to incorporate Special Operation Zones (SOZ), Geo-Fenced areas, and underserved service areas into the digital platform as published on the MDS.

Full permit language