Web conference notes, 2024.06.06 (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 Digital Policy and Emergency Response for Robotaxis/AVs

1. Intro and announcements (5 min)
2. MDS 2.1 Release Plan (5 min) - Michael Schnuerle, OMF
   1. Robotaxis, emergency response, real-time policy, crashes, air taxis
3. MDS Policy Overview (10 min) - Michael Schnuerle, OMF
4. Seattle Robotaxi Emergency Response Automation (15 min) - Armand Shahbazian, Electric and Automated Mobility Policy Advisor, SDOT
5. Discussion with Participants (20 mins)

WGSC Meeting Organizers

• Host: Michael Schnuerle, OMF
• Facilitator: Michael Schnuerle, OMF
• Preparation: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF
• Note taker: Gene Laynes, Chicago

Action Items and Decisions

1. ...

Minutes

• 71 Attendees
• OMF Slides
• Recording - Password W9W?T*1e

Notes

Agenda

1. Intro and Announcements

2. MDS 2.1 release plan

3. MDS policy overview

4. Seattle robotaxi - Emergency Response Automation

5. Discussion

Notes:

Definition: AV: Automated Vehicles

Introduction

• Michael Schnuerle

  • Intro to OMF / MDS

• Em Burnett

  • Smart curb collaborative - Final chance to apply for funding

• Andrew Hastings

  • OMF Summit this fall - November 12

    - Expanded full day event
    
    - Planned to coincide with the CoMotionLA conference
    

  • New OMF members

    - beam
    
    - appyway
    
    - cruise
    
    - TRANZITO SMART MOBILITY
    

MDS 2.1 Release Plan (Michael Schnuerle)

• Clearer support for Autonomous Vehicles in passenger services mode (i.e. robotaxis)

• Full support or real time policy for emergency response is / will be more explicitly supported

• Considering data standards for crash reporting

MDS Policy overview

• Shift from physical infrastructure to digital infrastructure

• MDS enables two way communication between public / private entities and actors.

• MDS Use cases includes things like fees and incentives, emergency guidance, event areas, no-ride zones / geofencing, policy and environmental goals.

• OMF publishes sample policy language, how to guides, and RFP scoring language, contract renewal, etc.

• Github - where everything happens outside of meetings (asynchronous content)

  • Place to post comments and engage

  • Many purposes: issues, policy, clearinghouse of decision making.

  • https://github.com/openmobilityfoundation/mobility-data-specification#get-involved

• MDS Policy for passenger services

• Question: How do you specify geographies for the data exchange?

  • Answer: it really depends on the specific connectors and

Seattle Department of Transportation

• Armand Shabazian - Electric and automated mobility policy advisor at SDOT

• Data for autonomous transportation awareness (DATA)

• General Stats: 27% of Seattle is public space, 60% of Seattle's emissions come from vehicles.

• Pillars of AV policy: Safety, Sustainability, Equity, Collaboration

• Washington State Senate Bill 5594 addresses AVs is currently stalled, however...

• State lawmakers allocated 500k for advancing WA AV services

• SDOT is using this to demonstrate geofencing and other AV digital services

• Timeline (2017-2024)

  • Starts with Mobility playbook in 2017

  • Includes collaboration with several private companies including Nvidia

  • Ends with 20 year plan for AVs and DATA program

• Looking at San Francisco's experience (50 written reports of AV interference)

  • (see diagram) Complex flow of information and response when there is an incident with AVs that includes calls to AV

  • AVs are more challenging for engagement with first responders

• Seattle's approach to avoiding AV interference is data driven and they are looking at digital tools to streamline operations.

  • Ingest real time data (911, crashes, etc.)

  • Translate to MDS

  • Create geofencing for "no go zones" for rerouting

  • monitor feed use for effectiveness

  • Share: create guide for other cities

• Data flow

  • SaaS platform: (911 / Work zones / Traffic operations / events / traveler information API)

  • SaaS platform feeds into Policy Feed

  • Policy Feed feeds into Geofencing development

  • Geofencing feeds into downstream communication

• Demonstration example of data flow (see slides)

• Partners include State, OMF, University of Washington, and (TBD) private SaaS company.

• Contact:

• [email protected]

• https://www.seattle.gov/transportation/projects-and-programs/programs/new-mobility-program

• Question: how do you evaluate the results?

  • Looking at the impact on staff time, and for better processes (currently involves manual entry)

• How will you coordinate the feeds from a staffing perspective?

  • Still developing, but we're getting good quotes from external services, we plan to depend on existing state APIs.