Web conference notes, 2026.10.22 (MDS Working Group)

• 00:06:38 Andrew Glass Hastings (OMF): If this is your first time at a WG meeting welcome! Feel free to introduce yourself in the chat and say hello!

• 00:07:19 Andrew Glass Hastings (OMF): If you haven’t already please change your name in Zoom to add your city, org, company so we know who is on the call. Big help!

• 00:07:22 Nivel | Harald Sævareid: Thanks! Harald from Nivel - digital governance platform for cities - based in Norway

• 00:07:38 Andrew Glass Hastings (OMF): Reacted to "Thanks! Harald from Nivel - digital governance platform for cities - based in Norway" with 👋

• 00:07:43 Rachel Castignoli AUSTIN, TX: Reacted to "Thanks! Harald from Nivel - digital governance platform for cities - based in Norway" with 👋

• 00:07:46 Nivel | Harald Sævareid: Reacted to "Thanks! Harald from ..." with 👋

• 00:07:50 Karen Grove - Seattle Fire: Hello All, Karen Grove with Seattle Fire Department.

• 00:08:05 Allison Moore-Farrell, City of Boulder: Hello! Allison Moore-Farrell, City of Boulder (new member city!)

• 00:08:06 Aylene McCallum (OMF): Reacted to "Hello! Allison Moore-Farrell, City of Boulder (new member city!)" with 👋🏻

• 00:08:13 Aylene McCallum (OMF): Reacted to "Hello All, Karen Grove with Seattle Fire Department." with 👋🏻

• 00:08:18 Emily Lindsey, DRCOG: Reacted to "Hello! Allison Moore-Farrell, City of Boulder (new member city!)" with ❤️

• 00:08:18 Benjamin Listman (NYCDOT): Ben Listman, NYCDOT

• 00:08:21 Aylene McCallum (OMF): Yay Boulder!

• 00:08:24 Joshua Cregger: Joshua Cregger, U.S. DOT Volpe Center

• 00:08:31 Rachel Castignoli AUSTIN, TX: Rachel Castignoli, Austin, TX - I run the AV program

• 00:08:33 Vladimir Gallegos (LADOT-Commercial Rideshare & Mobiliy)): Good morning, Vladimir Gallegos from LADOT (CRM)

• 00:08:46 Cormac McKay: Hi Cormac McKay From Dublin Ireland 🇮🇪

• Project Director on Aeravai CCAM-RITES Project

• 00:09:11 Aylene McCallum (OMF): I see a few attendees at today's meeting that could probably contribute to the discussion!

• 00:09:12 Zahra Entezami (City of Toronto): Hi all! Zahra Entezami, City of Toronto, Transportation Services

• 00:09:19 Emily Lindsey, DRCOG: Reacted to "Yay Boulder!" with 🎉

• 00:09:21 Daniel Bernstein (LA Metro): Daniel Bernstein, LA Metro Office of Strategic Innovation

• 00:09:35 Andrew Glass Hastings (OMF): Reacted to "Ben Listman, NYCDOT" with 👋

• 00:09:42 Andrew Glass Hastings (OMF): Reacted to "Joshua Cregger, U.S. DOT Volpe Center" with 👋

• 00:09:45 Andrew Glass Hastings (OMF): Reacted to "Rachel Castignoli, Austin, TX" with 👋

• 00:09:49 Andrew Glass Hastings (OMF): Reacted to "Good morning, Vladimir Gallegos from LADOT (CRM)" with 👋

• 00:09:56 Bern Grush, Urban Robotics Foundation: Bern Grush, Urban Robotics Foundation

• 00:10:02 Andrew Glass Hastings (OMF): Reacted to "Hi Cormac McKay From Dublin Ireland 🇮🇪

• Project Director on Aeravai CCAM-RITES Project " with 👋

• 00:10:03 Nate Deshmukh Towery, USDOT Volpe Center: Hi all - Nate Deshmukh Towery w. the USDOT Volpe Center in Cambridge, MA.

• 00:10:12 Andrew Glass Hastings (OMF): Reacted to "Hi all! Zahra Entezami, City of Toronto, Transportation Services" with 👋

• 00:10:13 Steven Philpott Sr Nelcielo Mobility - Chicago: G'day. Regional Air Mobility - Midwest Aero Network.

• 00:10:25 Andrew Glass Hastings (OMF): Replying to "Daniel Bernstein, LA..."

• Welcome Daniel!

• 00:10:30 ARTI Gupta: Arti Gupta - Transportation Mobility Solutions

• 00:10:30 Andrew Glass Hastings (OMF): Reacted to "Bern Grush, Urban Robotics Foundation" with 👋

• 00:10:31 Cormac McKay: Reacted to "Bern Grush, Urban Robotics Foundation" with 👋

• 00:10:34 Andrew Glass Hastings (OMF): Reacted to "Hi all - Nate Deshmukh Towery w. the USDOT Volpe Center in Cambridge, MA." with 👋

• 00:10:41 Andrew Glass Hastings (OMF): Reacted to "G'day. Regional Air Mobility - Midwest Aero Network." with 👋

• 00:10:43 Cormac McKay: Reacted to "Hi Cormac McKay From Dublin Ireland 🇮🇪

• Project Director on Aeravai CCAM-RITES Project " with 👋

• 00:10:43 Dan Flynn: Dan Flynn, USDOT Volpe Center

• 00:10:47 Andrew Glass Hastings (OMF): Reacted to "Dan Flynn, USDOT Volpe Center" with 👋

• 00:10:49 Andrew Glass Hastings (OMF): Reacted to "Arti Gupta - Transportation Mobility Solutions" with 👋

• 00:11:35 Kuilin Zhang: Kuilin Zhang, Michigan Technological University

• 00:11:41 Allison Moore-Farrell, City of Boulder: Reacted to "Yay Boulder!" with ❤️

• 00:13:16 Tim Adams - HAAS Alert: Hi All! Tim Adams from HAAS Alert. Connecting drivers with roadway hazards, making the road a safer place for everyone!

• 00:14:01 Andrew Glass Hastings (OMF): Reacted to "Hi All! Tim Adams from HAAS Alert. Connecting drivers with roadway hazards, making the road a safer place for everyone!" with 👋

• 00:14:04 Andrew Glass Hastings (OMF): Reacted to "Kuilin Zhang, Michigan Technological University" with 👋

• 00:14:05 Michael Schnuerle (OMF): Agenda and slides for today. Recording and notes later: https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.10.22-(MDS-Working-Group)

• 00:14:45 Michael Schnuerle (OMF): Calendar https://calendar.google.com/calendar/u/0/embed?src=openmobilityfoundation.org_g6gsaccjvijnmlhigfpj01ngp0@group.calendar.google.com&ctz=America/Los_Angeles

• 00:15:42 Aylene McCallum (OMF): CoMotion LA link: https://www.comotionglobal.com/los-angeles26

• 00:16:09 Vladimir Gallegos (LADOT-Commercial Rideshare & Mobiliy)): Reacted to "I see a few attend..." with 🎉

• 00:16:13 Aylene McCallum (OMF): OMF Commercial Members receive two complimentary tickets to CoMotion LA - if you need directions on how to use those tickets, please reach out to me directly.

• 00:16:23 Aylene McCallum (OMF): aylene@openmobilityfoundation.org

• 00:17:46 Michael Schnuerle (OMF): Last meeting https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.09.24-(MDS-Working-Group)

• 00:18:20 Michael Schnuerle (OMF): MDS blog post https://www.openmobilityfoundation.org/mds-emergencies/

• 00:20:09 Ellen Partridge: Does your data take into account state privacy laws?

• 00:20:53 Aylene McCallum (OMF): Reacted to "Does your data take into account state privacy laws?" with 💡

• 00:21:07 Andrew Glass Hastings (OMF): MDS includes no personally identifiable fields - nothing about the person

• 00:22:08 Andrew Glass Hastings (OMF): And just a reminder the data shared via MDS does not flow to or through the OMF. It flows directly between the operators and city/agency or via the city’s contracted software vendor

• 00:24:25 remi kuti: Hi everyone, I’m Remi Kuti, founder of UrbanShield. We’re developing an MDS 2.1-based platform for councils, integrating micromobility incident data and vehicle telemetry for safety monitoring.

• 00:24:25 Salvador Gutierrez: Reacted to "MDS includes no personally identifiable fields - nothing about the person" with 👍

• 00:27:47 Michael Schnuerle (OMF): Replying to "Does your data take ..."

• Here are resources for privacy in MDS, on the home page of our specification: https://github.com/openmobilityfoundation/mobility-data-specification#data-privacy

• 00:30:13 Michael Schnuerle (OMF): Reacted to "Hi everyone, I’m Remi Kuti, founder of UrbanShield. We’re developing an MDS 2.1-based platform for councils, integrating micromobility incident data and vehicle telemetry for safety monitoring." with 👋

• 00:30:19 Michael Schnuerle (OMF): Reacted to "And just a reminder the data shared via MDS does not flow to or through the OMF. It flows directly between the operators and city/agency or via the city’s contracted software vendor" with ✅

• 00:30:33 Ellen Partridge: Replying to "Does your data take into account state privacy laws?"

• 👍

• 00:33:39 Cormac McKay Aeravai CCAM-RITES: As you know what happens in California has wide reaching global ramifications and negativity in the media is giving transport planners and politicians cause for pause, Even with the new SB1246 AV bill it is still not clear who should be held accountable for a responsible integration and AV deployment, Are Local State/City Authorities and Transport Agencies taking responsibility for effective communications, digital infrastructure V2X and curbside service PuDo provisions? If fees/taxes are collected from operators why is this not being spent on providing these public services?

• 00:33:49 Cormac McKay Aeravai CCAM-RITES: Replying to "As you know what hap..."

• https://lnkd.in/p/dNFAytJ8

• 00:36:46 Rachel Castignoli AUSTIN, TX: Do y'all get VMT broken down by city/county?

• 00:38:58 Ellen Partridge: Does your ability to request information exceed that of NHTSA?

• 00:39:08 ARTI Gupta: for Michael at DMV - very informative session, very nicely done. I am curious as to what is your openion on Tesla selling their FSD software to their customers, it supposedly requires customers to pay attention, many don't understand the need and do not pay attention. Do you also get safety data from Tesla when FSD mode is being used by their customers.

• 00:41:47 Michael Schnuerle (OMF): FYI from OMF: MDS can support all the data in the Expanded Data Reporting (with an id used to link to the external crash reports). It comes in JSON format, versus CSV. The Operational Restrictions could also be sent from the DMV to AVs via MDS Policy. And of course emergency geofencing requirements via MDS, just like Seattle is doing via 911 calls.

• 00:41:54 Allison Moore-Farrell, City of Boulder: Replying to "Do y'all get VMT broken down by city/county?"

• We'd be very interested in this too!

• 00:42:09 Michael Schnuerle (OMF): Thank you for the questions, we will ask Miguel after his presentation.

• 00:43:37 Cormac McKay Aeravai CCAM-RITES: Reacted to "As you know what happens in California has wide reaching global ramifications and negativity in the media is giving transport planners and politicians cause for pause, Even with the new SB1246 AV bill it is still not clear who should be held accountable for a responsible integration and AV deployment, Are Local State/City Authorities and Transport Agencies taking responsibility for effective communications, digital infrastructure V2X and curbside service PuDo provisions? If fees/taxes are collected from operators why is this not being spent on providing these public services?" with 👍

• 00:44:06 Andrew Glass Hastings (OMF): Thanks @Miguel acosta, CA DMV

• 00:44:28 Chris Shelley | City of Philadelphia: Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?

• 00:45:08 Rachel Castignoli AUSTIN, TX: Replying to "Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?"

• we've had this convo a lot in Austin - what do we want AV companies to do when we ask people to "shelter in place"

• 00:45:29 Chris Shelley | City of Philadelphia: Reacted to "we've had this convo a lot in Austin - what do we want AV companies to do when we ask people to "shelter in place"" with ❤️

• 00:45:32 Rachel Castignoli AUSTIN, TX: Replying to "Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?"

• At the last meeting Waymo talked about the 5 commands it can intake and one was a "stay put"

• 00:45:55 Chris Shelley | City of Philadelphia: Replying to "Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?"

• What are the other four?

• 00:45:56 Bern Grush, Urban Robotics Foundation: Reacted to "At the last meeting Waymo talked about the 5 commands it can intake and one was a "stay put"" with 👍

• 00:46:17 Henry Silverman (Waymo): As the product manager at Waymo who was formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports

• 00:46:23 Bern Grush, Urban Robotics Foundation: Reacted to "What are the other four?" with 👍

• 00:47:48 Rachel Castignoli AUSTIN, TX: Replying to "Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?"

• "stop driving immediately"; "stay out"; limit vehicles; curb freeze; drain out

• 00:48:48 Andrew Glass Hastings (OMF): Replying to "Interesting, fleets ..."

• @Chris Shelley | City of Philadelphia I liked the “curb freeze” command - in instances that PUDOs should not happen in an area

• 00:48:49 Chris Shelley | City of Philadelphia: Cities in Pennsylvania got preempted from regulating AVs by the state...so there's that.

• 00:49:07 Rachel Castignoli AUSTIN, TX: Replying to "Cities in Pennsylvania got preempted from regulating AVs by the state...so there's that."

• yeah, that is how it is in Texas as well

• 00:49:26 Karen Grove - Seattle Fire: There is proposed legislation in WA that would do the same (preempting locals)

• 00:50:07 Andrew Glass Hastings (OMF): @Rachel Castignoli AUSTIN, TX we need to make sure the “stay put” is a part of MDS Policy commands

• 00:50:22 Rachel Castignoli AUSTIN, TX: Reacted to "@Chris Shelley | City of Philadelphia I liked the “curb freeze” command - in instances that PUDOs should not happen in an area" with 👍

• 00:51:00 Cormac McKay Aeravai CCAM-RITES: Have you a PuDO plan?

• 00:51:01 Bern Grush, Urban Robotics Foundation: Replying to "Interesting, fleets ..."

• @Rachel Castignoli AUSTIN, TX is there a link to the definitions for these 5?

• 00:51:58 Chris Shelley | City of Philadelphia: Reacted to "@Chris Shelley | City of Philadelphia I liked the “curb freeze” command - in instances that PUDOs should not happen in an area" with 👍

• 00:52:35 Henry Silverman (Waymo): Reacted to "At the last meeting Waymo talked about the 5 commands it can intake and one was a "stay put"" with 👍

• 00:52:39 Andrew Glass Hastings (OMF): @Rachel Castignoli AUSTIN, TX makes an excellent point! MDS policy is the future of traffic management overall - not just for AVs - but a big benefit to all travelers using Google Maps or connected fleets for examples

• 00:52:47 Rachel Castignoli AUSTIN, TX: Reacted to "@Rachel Castignoli AUSTIN, TX makes an excellent point! MDS policy is the future of traffic management overall - not just for AVs - but a big benefit to all travelers using Google Maps or connected fleets for examples" with 👍

• 00:52:50 Henry Silverman (Waymo): Reacted to ""stop driving immediately"; "stay out"; limit vehicles; curb freeze; drain out" with 👌

• 00:52:52 Gian-Luca Tellenbach: Are faded street signs something that AVs can identify and communicate to cities via MDS? Are there dedicated fields?

• 00:53:04 Chris Shelley | City of Philadelphia: Reacted to "Are faded street signs something that AVs can identify and communicate to cities via MDS? Are there dedicated fields?" with ❤️

• 00:53:45 Michael Schnuerle (OMF): Reacted to "As the product manager at Waymo who was formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports" with omf

• 00:53:48 Michael Schnuerle (OMF): Reacted to "As the product manager at Waymo who was formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports" with 👍

• 00:53:54 Michael Schnuerle (OMF): Reacted to "As the product manager at Waymo who was formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports" with mds

• 00:54:11 Aylene McCallum (OMF): I also think it is important to point out that his specific use of MDS was designed to address specific concerns brought up by cities with for-hire A/V rollouts in their cities, but the beauty of it (as Andrew noted above) is that there is applicability across many many use cases.

• 00:54:18 Henry Silverman (Waymo): Replying to "Interesting, fleets can be directed to leave/avoid but is there a framework under which fleets can be asked to "stay put"?"

• Stay put will mean different things to different AV companies. We have multiple versions of it at Waymo. For example, you almost never want cars to strand in lane. And even if you ask them to pullover…what kind of pullover? Pullover? Park?

• 00:54:33 Rachel Castignoli AUSTIN, TX: Reacted to "Stay put will mean different things to different AV companies. We have multiple versions of it at Waymo. For example, you almost never want cars to strand in lane. And even if you ask them to pullover…what kind of pullover? Pullover? Park?" with 👍

• 00:54:37 Andrew Glass Hastings (OMF): For those of you who may have missed last month’s call with Waymo presenting here is the link to the recording and slide deck…

• Last meeting https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.09.24-(MDS-Working-Group)

• 00:54:38 Cormac McKay Aeravai CCAM-RITES: Reacted to "As the product manager at Waymo who was formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports" with 👍

• 00:55:25 Jerad Weiner: Reacted to "For those of you who may have missed last month’s call with Waymo presenting here is the link to the recording and slide deck…

• Last meeting https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.09.24-(MDS-Working-Group)" with 👍

• 00:55:26 Andrew Glass Hastings (OMF): Replying to "Interesting, fleets ..."

• @Henry Silverman (Waymo) very true -super important definitions here.

• 00:55:43 Jerad Weiner: Reacted to "At the last meeting Waymo talked about the 5 commands it can intake and one was a "stay put"" with 👍

• 00:55:50 Salvador Gutierrez | LADOT: Reacted to "I also think it is important to point out that his specific use of MDS was designed to address specific concerns brought up by cities with for-hire A/V rollouts in their cities, but the beauty of it (as Andrew noted above) is that there is applicability across many many use cases." with 👍

• 00:56:45 Cormac McKay Aeravai CCAM-RITES: Reacted to "Are faded street signs something that AVs can identify and communicate to cities via MDS? Are there dedicated fields?" with ❤️

• 00:57:40 Tony (HDR Michigan) Geara: How closley do you coordinate and align with these companies ? What mechanism do you use? Eg: monthly or quarterly meetings, ir just though reporting, etc. Do you have direct communication ? Any insight into how to do it well for other cities. ?

• 01:01:14 Chris Shelley | City of Philadelphia: Would be great to have a feedback loop of "city lets AVs know something is happening" followed by "AVs have mechanism by which they let city know that there is in fact something happening or something was erroneously reported/user error, etc."

• 01:01:39 Michael Schnuerle (OMF): Replying to "Would be great to ha..."

• MDS can do all this!

• 01:03:23 Rachel Castignoli AUSTIN, TX: We just started a local gov sub-committee at the Texas AV task force.

• 01:03:26 Cormac McKay Aeravai CCAM-RITES: Could we get this positive conversations and collaborations highlighted in the media?

• 01:04:01 Aylene McCallum (OMF): Replying to "Could we get this positive conversations and collaborations highlighted in the media?"

• The OMF just hired a new Comms & Engagement Manager who will be starting in November. This is something we can task the new manager with (pitching stories)

• 01:04:12 Cormac McKay Aeravai CCAM-RITES: Reacted to "The OMF just hired a new Comms & Engagement Manager who will be starting in November. This is something we can task the new manager with (pitching stories)" with 👋

• 01:04:13 Andrew Glass Hastings (OMF): Replying to "Could we get this po..."

• You know the media doesn’t like to cover positive stories 😉

• 01:04:21 Chris Shelley | City of Philadelphia: Reacted to "You know the media doesn’t like to cover positive stories 😉" with 🤣

• 01:04:23 Jerad Weiner: Reacted to "You know the media doesn’t like to cover positive stories 😉" with 🤣

• 01:04:24 Cormac McKay Aeravai CCAM-RITES: Reacted to "You know the media doesn’t like to cover positive stories 😉" with 😞

• 01:04:24 Andrew Glass Hastings (OMF): Replying to "Could we get this po..."

• But we can certainly continue to try!!

• 01:04:27 Henry Silverman (Waymo): Reacted to "You know the media doesn’t like to cover positive stories 😉" with 💯

• 01:04:33 Henry Silverman (Waymo): Reacted to "But we can certainly continue to try!!" with ❤️

• 01:04:35 Aylene McCallum (OMF): Replying to "Could we get this positive conversations and collaborations highlighted in the media?"

• We have a friend of the OMF at NPR

• 01:04:36 Jerad Weiner: Reacted to "But we can certainly continue to try!!" with ❤️

• 01:04:38 Jerad Weiner: Reacted to "The OMF just hired a new Comms & Engagement Manager who will be starting in November. This is something we can task the new manager with (pitching stories)" with 👋

• 01:04:40 Henry Silverman (Waymo): Reacted to "We have a friend of the OMF at NPR" with ❤️

• 01:04:44 Salvador Gutierrez | LADOT: Reacted to "The OMF just hired a new Comms & Engagement Manager who will be starting in November. This is something we can task the new manager with (pitching stories)" with 👏

• 01:04:45 Cormac McKay Aeravai CCAM-RITES: Reacted to "We have a friend of the OMF at NPR" with ❤️

• 01:04:45 Andrew Glass Hastings (OMF): Reacted to "We just started a local gov sub-committee at the Texas AV task force." with 👍

• 01:04:52 Andrew Glass Hastings (OMF): Reacted to "We have a friend of the OMF at NPR" with 💪

• 01:04:57 Cormac McKay Aeravai CCAM-RITES: Reacted to "Could we get this positive conversations and collaborations highlighted in the media?" with ❤️

• 01:05:02 Rachel Castignoli AUSTIN, TX: Replying to "Could we get this positive conversations and collaborations highlighted in the media?"

• @Cormac McKay Aeravai CCAM-RITES https://www.kvue.com/article/news/local/waymo-pilot-program-helping-austin-leaders-detect-potholes/269-73d473b7-fe5f-4923-bd39-0dc252db11fb

• 01:05:16 Tony (HDR Michigan) Geara: Reacted to Could we get this po... with "❤️"

• 01:05:21 Tony (HDR Michigan) Geara: Reacted to We just started a lo... with "❤️"

• 01:05:22 Andrew Glass Hastings (OMF): Thanks again @Miguel acosta, CA DMV for presenting! And everyone for joining and presenting!

• 01:05:23 Vladimir Gallegos (LADOT-Commercial Rideshare & Mobiliy)): Thank you, Miguel, for presenting!

• 01:05:26 Tony (HDR Michigan) Geara: Reacted to Would be great to ha... with "❤️"

• 01:05:32 Nate Deshmukh Towery, USDOT Volpe Center: thank you!

WEBVTT

00:00:05.000 --> 00:00:11.000 Hello, welcome everybody. Thanks for joining today's OMF MDS Working Group Meeting

00:00:11.000 --> 00:00:19.000 Happy to have you here. Today we'll be talking about what I'm sharing on my screen, which is evolving AV policy

00:00:19.000 --> 00:00:26.000 In states and cities and a presentation from the California DMV

00:00:26.000 --> 00:00:41.000 So, some housekeeping before we get started in the participant list, make sure you add your organization name, your company, your city after your name by editing your name and adding that so we know who you're representing

00:00:41.000 --> 00:00:49.000 That's really helpful for conversations, for transcribing the meeting, and to know who you're representing

00:00:49.000 --> 00:00:55.000 Mute yourself if you aren't already, but feel free to

00:00:55.000 --> 00:01:11.000 introduce yourself in the chat now. Harold just introduced himself. Thank you, Harold. About you know who you are, who you represent, why you're here, things like that. Feel free to share links to relevant information if you'd like

00:01:11.000 --> 00:01:27.000 Use the chat to leave questions as we go. This meeting will have some Q&A and discussion time, so you can put things in the chat and then we can come back to you and you can talk about them, or you can just hold them for the discussion. Use the raise hand feature if you really want to speak

00:01:27.000 --> 00:01:35.000 This meeting is being recorded and will be published with notes to the MDS working group mailing list.

00:01:35.000 --> 00:01:48.000 So today we'll do a little announcements and I'll give some background on MDS real-time policy and autonomous vehicles in the realm of our realm. And then the California DMV is going to do a presentation

00:01:48.000 --> 00:02:01.000 about past present and future state of AV policy, and we'll have some Q&A there. We were going to have some examples from cities, but

00:02:01.000 --> 00:02:17.000 One city backed out the last minute because of an emergency. Another city is actually has their whole team talking about AAV policy right now. At the same time as this meeting in another context, so they couldn't join

00:02:17.000 --> 00:02:37.000 And Lilla City is also working on something at the same time. So, nonetheless, if you are a city or another state, or another jurisdiction, or even a company, and later want to share your… what you're working on, or your perspectives, keep that in mind, and we can talk about that during the discussion time.

00:02:37.000 --> 00:02:50.000 So we'd love to hear from you. California DMV is the main presenter, but we want to have a bigger conversation about MDS real-time digital policy

00:02:50.000 --> 00:02:58.000 And AAV policy as well from different levels.

00:02:58.000 --> 00:03:18.000 So I'm Michael Schnirla. I work for the OMF. I'm the director of open source operations, open Mobility Foundation. You probably know a lot of this, but was created in 2019. City founded and city-led, and we help cities and companies work together to get to yes, and we provide forums like this one for cities and technology companies to work together

00:03:18.000 --> 00:03:22.000 to solve problems and identify solutions.

00:03:22.000 --> 00:03:39.000 Everything we build is in the open. We use GitHub as a public way to track everything we do. We record these meetings, have at least two public meetings a month. Lots of participation from people and agencies, operators, curb users, tech companies, etc.

00:03:39.000 --> 00:03:52.000 And this has created a nice ecosystem of local government curb users, operators in the space, technology and service providers, all using MDS and CDS

00:03:52.000 --> 00:03:56.000 To work together to improve the public realm

00:03:56.000 --> 00:04:17.000 The mobility data specification, it's a data standard. It enables right-of-way regulation, digital policy, geofencing, and two-way digital communication between mobility companies and public agencies worldwide. On the right there is our steering committee, their OMF member organizations, and these are people who volunteer their time to

00:04:17.000 --> 00:04:24.000 Be on the steering committee and set the agendas, like the, the one agenda we have today.

00:04:24.000 --> 00:04:38.000 Many of them are on this call, so I just want to shout them out in general and say thank you for being on the steering committee. And if you are on the steering committee, feel free to introduce yourself to everyone else. Thank you very much.

00:04:38.000 --> 00:04:53.000 MDS is global. We know of over 200 commercial mobility service providers that send MDS to cities or receive it from cities, and these companies operate in over 1,200 cities across the world

00:04:53.000 --> 00:04:58.000 But billions of trips taken

00:04:58.000 --> 00:05:20.000 MDS 2.1 was released recently. We might talk about, I'll just mention on this slide what's relevant, but basically MDS supports a lot of different types of mobility modes, options, and services in different jurisdictions. We started with micromobility, but for a few years now, we've already

00:05:20.000 --> 00:05:35.000 been supporting things like taxis, robotaxis, autonomous vehicles, car share, robots on the sidewalk, and then with 2.1, we've added and expanded that even more to things like buses

00:05:35.000 --> 00:05:45.000 Fixed route services, more support for AV, Robotaxis, or for hire taxis, robotaxis, like we're going to talk about today.

00:05:45.000 --> 00:06:01.000 Different sanitation and city fleets also, and then all types of delivery, not just sidewalk robots, but app delivery, packages, freight goods, food. A lot of our cities are using MDS to, wanted to use MDS

00:06:01.000 --> 00:06:06.000 To do this, and so it was added, and now some of them are

00:06:06.000 --> 00:06:19.000 We have a lot of resources. You can find this on our blog and our website and on the MDS repository page on GitHub. But lots of information to get you up to speed on what MDS is, what it does

00:06:19.000 --> 00:06:22.000 And how it works.

00:06:22.000 --> 00:06:30.000 And we have another data standard, CDS. It works together with MDS, so MDS is… which we'll talk about today a little bit

00:06:30.000 --> 00:06:49.000 It's about understanding vehicle locations, the status of those vehicles, incidents, trips, geofencing, things like that. And CDS is about defining physical infrastructure locations around your city, objects that that infrastructure, and tracking activity in and out and around that infrastructure.

00:06:49.000 --> 00:06:54.000 They could be used together or independently.

00:06:54.000 --> 00:07:02.000 We'd like to thank our commercial members who participate with the OMF, Premier members. You can see them listed here

00:07:02.000 --> 00:07:08.000 I'll ask Aileen if she wants to say anything about our Premier or Associate members

00:07:08.000 --> 00:07:23.000 that we want to thank them for their support. Blue Systems, CurbIQ, NREX, Passport, and Emojo invest significant energy and financial resources to the OMF, so we very much appreciate their investment. You can

00:07:23.000 --> 00:07:39.000 Turn it to the next page. These are our associate members. You can see we have members big and small all over the world. Thank you to all of you that are joining today. I will also tease that we've got a couple new members

00:07:39.000 --> 00:07:49.000 That should be showing up on these slides next month, and we're excited to share them with you when everything gets finalized.

00:07:49.000 --> 00:07:51.000 Stay tuned

00:07:51.000 --> 00:07:53.000 Great. Thank you.

00:07:53.000 --> 00:08:11.000 We're excited, to have all these great companies support the work of the cities and the OMF. We have an OMF calendar, so if you want to know what we're doing, our conferences, meetings like this one, member meetings, things like that, you could see it and subscribe to it. I'll put

00:08:11.000 --> 00:08:19.000 I'll copy the link and put it in the chat. But it's really useful for keeping up with us.

00:08:19.000 --> 00:08:32.000 And then where will the OMF be through 2026? A lot of September and October is behind us, but coming up in November, we will be have staff members at Tomorrow Mobility in Barcelona

00:08:32.000 --> 00:08:47.000 The big OMF summit at Co-Motion in Los Angeles is coming up, and then Polis in Europe in Brussels in December. If any staff members want to share links or say anything about these events

00:08:47.000 --> 00:08:48.000 Please do.

00:08:48.000 --> 00:09:08.000 Yeah, Michael, real quick, I'll mention tomorrow mobility for those of you, especially of the European audience who will be in Barcelona, we are hosting a workshop on Thursday, the 5th of that week, focusing on the work we've been doing in partnership with the city of Amsterdam and the Dutch National Ministry

00:09:08.000 --> 00:09:24.000 Around defining MDS as a crash data standard for bicycles and light electric vehicles. This is an exciting opportunity to partner with additional cities, bring more stakeholders into the conversation

00:09:24.000 --> 00:09:41.000 With the goal of being able to use MDS as a crash data standard across Europe and beyond. So it's kind of building from the work we've been doing focused around the Netherlands and Amsterdam, taking it to a larger audience and actually being able to show a proof of concept, real data

00:09:41.000 --> 00:10:00.000 Coming from micromobility services related to crash and incidences. So stay tuned for more on that. Join us at the workshop in Barcelona if you will be there. If you don't have the details yet, feel free to message anyone on the OMF team and we'll help get you connected.

00:10:00.000 --> 00:10:10.000 Thanks, Andrew. And yes, crash data can be sent through MDS. I know that might be part of the discussion today. Many cities get

00:10:10.000 --> 00:10:29.000 crash reports or a monthly reports. Some cities are getting it in near real time when it's available, or with a short few-day turnaround. DC helped us add this because DC has multiple modes that are sending or will be sending crash data

00:10:29.000 --> 00:10:35.000 through MDS to them. So, it's relevant for today as well

00:10:35.000 --> 00:10:41.000 So I'm going to talk just a little bit about MDS policy and AVs

00:10:41.000 --> 00:10:58.000 And give some background and some resources for you if you want to follow up later. So, we've talked about this a lot over the years, but even more recently, our last working group meeting was with Waymo Blue Systems in three cities, talking about

00:10:58.000 --> 00:11:06.000 Emergency, real-time data standards and notifications using MDS. So this is a

00:11:06.000 --> 00:11:22.000 This is the last month's meeting. We had a lot of people attend over 100, but you can see the recording and the slides here. So I'm going to put this in the chat and you can look at this later because it's relevant to today's conversation

00:11:22.000 --> 00:11:40.000 And then we also have a great blog post that summarizes some of what we talked about last month at a high level about how information about emergencies can get from first responders to autonomous vehicles and really all road users in near real time

00:11:40.000 --> 00:11:54.000 with the new solution and using MDS 2.1. So I'll put that in the in the chat as well.

00:11:54.000 --> 00:12:03.000 And you can see some great examples here. There's a video, there's also a recording of this from our working group.

00:12:03.000 --> 00:12:08.000 So lots of this has been talked about on some levels at prior meetings.

00:12:08.000 --> 00:12:27.000 And the kinds that I want to share the kinds of data that MDS can provide to cities from operators like autonomous vehicles. Many cities obviously get this for different types of other modes, but cities can write data sharing requirements into operating permits for

00:12:27.000 --> 00:12:37.000 mobility services and get information about the vehicle location, the status of the vehicle, either real time or historically

00:12:37.000 --> 00:12:48.000 vehicle information, like propulsion types, is it electric hybrid attributes of the vehicle, fuel capacity, accessibility attributes, which might be relevant to today's conversation.

00:12:48.000 --> 00:12:58.000 Trip details, so, like, the kinds of trip taken, the distance duration, any fares, costs, fees, the different kind of payload, like if you're talking about a delivery

00:12:58.000 --> 00:13:14.000 And then what Andrew was talking about, incidents, and they're all different types of incidents that can be sent over, crashes are one of them, but a lot of these other incidents, cities are asking for from different types of mobility services.

00:13:14.000 --> 00:13:31.000 Automatic driving, disengagement, near-miss information, which is actually also coming through in Amsterdam and the Netherlands through MDS. That's a big part of their work, is not only understanding when a crash happened, but getting data and MDS about near misses to improve infrastructure.

00:13:31.000 --> 00:13:39.000 Obstructions, violations, theft, vandalism, harsh braking or acceleration, that's all part of incidents and can be sent

00:13:39.000 --> 00:13:48.000 chip breadcrumbs, after rides are complete, those could be sent. And then stop details at pre-designated places

00:13:48.000 --> 00:14:05.000 I'll answer the question real quick in the chat. Yes, it does take into account state privacy laws and in Europe, GDPR, which is a big data privacy framework. All of this is dependent on the jurisdiction, city, county, MPO, state, or even country

00:14:05.000 --> 00:14:21.000 And what they're allowed to collect, what they have use cases for, how they store the data, and we have a lot of resources about this on our website at privacyguideforcities, understanding of the fields in MDS that could be sensitive, GDPR

00:14:21.000 --> 00:14:28.000 guide and legal framework. So a lot of that's on our website.

00:14:28.000 --> 00:14:32.000 And then the other side of MDS since it's two-way.

00:14:32.000 --> 00:14:43.000 Cities can also digitize the data sharing requirements and the use cases that they need and what they don't need for privacy

00:14:43.000 --> 00:14:59.000 through MDS so that can actually be digit digitally described to make it really clear what you do want and what you don't want, and then also information about policies, geofencing, emergencies and events that also can be communicated

00:14:59.000 --> 00:15:15.000 in MDS and all of this falls under the part of MDS we call policy. MDS policy, that's the graphic, the icon up here. So it includes digital policy fields, information, and geofencing.

00:15:15.000 --> 00:15:23.000 And so with 2.1, we enhanced how policy worked. It's been there from the beginning, but before 2.1,

00:15:23.000 --> 00:15:38.000 MDS policy was what we call a get method. So the way MDS worked is the operators would have to check in with the city to see, is there something new? And it's like looking at a book. So every time they'd have to like look through the book

00:15:38.000 --> 00:15:53.000 digital book and say, oh, is it in here? Is something different? Okay, know that I don't have to do anything. Yes, there's a new chapter, I have to go do something. And so it made it hard to get near real time, because you'd have to check all the time

00:15:53.000 --> 00:16:10.000 With 2.1 MDS policy is both a get method where you get the information from the city, or a push method where the city pushes it directly to the operators, kind of like a notification on your phone. So the the company is just listening, and when there's

00:16:10.000 --> 00:16:27.000 New change, or something new, the city will push it. And so then the book is still available. You can still check on the operating rules at any time, and the emergencies. But now you can be notified when there is something new and get just that bit of information that's new

00:16:27.000 --> 00:16:43.000 And this allows for actual real-time, easier MDS policy communication and confirmation of receipt of this information. That's something that's part of this California conversation that MDS can… through MDS you can confirm that an operator received

00:16:43.000 --> 00:16:48.000 your emergency notification

00:16:48.000 --> 00:17:04.000 And then just to describe a little bit, this is before we get into the California presentation, I think this is most relevant to this. But MDS policy. These are the types of things that can be digitally pushed from

00:17:04.000 --> 00:17:22.000 public agency to an operator, either in real time, future events, past events, per mode, per operator. There's a lot of different ways to slice it, so you can say, okay, for autonomous vehicles, here's information that's relevant for scooters, here's information that's relevant

00:17:22.000 --> 00:17:45.000 And so you can define and send things like the… out the whole operating area of where these vehicles should be operating, caps citywide or localized exclusion zones, allowances for caps with other operators, speed limit restrictions, idle time limitations, parking areas, or curb data specific

00:17:45.000 --> 00:18:01.000 zones, tryptase subsidies, and then maybe for today's conversation, real-time emergency notifications get sent through MDS or maybe, like, events that are happening, you can send policies around that.

00:18:01.000 --> 00:18:15.000 All right, so maybe I'll… before I kick it over to California DMV, a few minutes ahead here. Does anyone have questions about MDS the scope of it? We had a privacy question. Are there other questions before we

00:18:15.000 --> 00:18:25.000 talk about it from a state example.

00:18:25.000 --> 00:18:40.000 All right, if you think of something, feel free to leave it in the chat, or unless… and and then we will make sure that we answer that. I'll make sure to monitor the chat, and I'll go back and look and see if there are prior questions.

00:18:40.000 --> 00:18:53.000 All right, so now we have, thankfully with us the California DMV, Miguel Acosta is here to present on the past, present and future policies for AVs in California

00:18:53.000 --> 00:19:09.000 So Miguel, welcome, and thank you for presenting today, and feel free to share your slides and introduce yourself, and you can spend as much time as you want, maybe 20 min if you'd like.

00:19:09.000 --> 00:19:26.000 Well, hey, thanks, Mike. Thanks, Andrew and the OMF team. Appreciate the opportunity to be here and share with the group about what we're doing here in California on the regulations that we have set in place here in April, our fourth set of regulations

00:19:26.000 --> 00:19:32.000 And they're the most comprehensive set of rules for autonomous vehicles in the nation.

00:19:32.000 --> 00:19:40.000 And this is really a body of work that has resulted from many years and received a lot of stakeholder input

00:19:40.000 --> 00:20:10.000 And today I'm just going to give a overview. There's a lot to cover, but I'd like to give an overview of kind of where we were, and then what the new rules cover.

00:20:25.000 --> 00:20:41.000 Okay, as I mentioned, just want to give a brief overview of our regulatory framework here in California. And I think one of the ways where I want to start is really the federal government's role versus the state's role in regulating autonomous vehicles here in the United States. So the federal government's role

00:20:41.000 --> 00:20:55.000 Through the National Highway Traffic Safety Administration for NHTSA, they're responsible for ensuring the safety of vehicles. They do this for overseeing the equipment of vehicles, and they promulgate Federal Motor Vehicle Safety Standards

00:20:55.000 --> 00:21:12.000 Here in the States, like in California, we're responsible for ensuring the safe operation of those vehicles, and we do so through licensing and permitting, registration, insurance requirements, and we do that through the California Vehicle Code

00:21:12.000 --> 00:21:27.000 And of course, many of you have seen this before, but I think it's really important to start here and talk about what is an autonomous vehicle and what is not, and we've actually codified this in California Vehicle Code 38750 as to what exactly is an autonomous vehicle

00:21:27.000 --> 00:21:46.000 An autonomous vehicle essentially is one that is capable of performing all of the driving tasks without any expectation of the human driver. So we use the Society of Automotive Engineers. We have here the taxonomy, levels 3 through 5. Of course, 5 is aspirational at this point

00:21:46.000 --> 00:22:07.000 But the light of demarcation for an autonomous vehicle or an automated driving system is level three. Of course, many automakers have advanced driver assistance systems. Those are as capable as they are and whether an OEM wants to put a plus on the

00:22:07.000 --> 00:22:19.000 Those are ADAS and those are not autonomous systems. They are the human driver is responsible for the driving task at levels two and below.

00:22:19.000 --> 00:22:27.000 So when we're talking about autonomous vehicles, we're referring to levels three and levels four

00:22:27.000 --> 00:22:42.000 And as I mentioned, we've had rules here in California for over a decade and starting back in 2012, the California legislature authorized the DMV to start regulating autonomous vehicles

00:22:42.000 --> 00:22:58.000 And in 2014, we issued our first set of regulations governing AV testing, and those were really focused with building safety driver requirements. So in 2014, we set rules associated with testing with safety driver on public roads

00:22:58.000 --> 00:23:15.000 And in 2018, we issued the next set of regulations, which allowed for testing without a safety driver and what we call here in California, commercial deployment. Now, deployment, the difference between deployment and testing here in California

00:23:15.000 --> 00:23:31.000 is whether a manufacturer is able to receive compensation for either providing Robotaxi services or providing delivery services, or even selling an autonomous vehicle to members of the public. We actually have one manufacturer that does that

00:23:31.000 --> 00:23:41.000 Today, in California, members of the public can actually purchase an autonomous vehicle with an automated driving system feature.

00:23:41.000 --> 00:23:57.000 And then in 2019, we issued another set of regulations allowing light duty vehicles to do commercial delivery services. And again, here, what we're going to talk about today is effective April of this year, we issued the next set of regulations

00:23:57.000 --> 00:24:09.000 Which again are really comprehensive and build upon California's long history of regulating AVs

00:24:09.000 --> 00:24:26.000 And just a quick overview of our program here in California. We have 26 companies that are authorized to test with a safety drug. We have 3 levels of permits here in California. Testing with a safety driver, testing without a safety driver, and then, as I mentioned, commercial deployment. Many of the companies, most of the companies, are in the first

00:24:26.000 --> 00:24:43.000 leg, so to speak, of the testing permits. There's 26 manufacturers, 6 companies are authorized to test on California public roads without the presence of a safety driver, and three have authorization to deploy

00:24:43.000 --> 00:24:59.000 Or to provide commercial services, as I mentioned, those 3 companies are Waymo, many of you guys know Waymo is a robotaxi company. They're operating in San Francisco, in the peninsula here in California, Los Angeles area, San Diego

00:24:59.000 --> 00:25:18.000 They have a comprehensive ODD in California, covering large parts of California. The second company is a company called Neuro, operating out of Mountain View. And the third company is Mercedes-Benz. Mercedes-Benz was the company I was referring to that sells

00:25:18.000 --> 00:25:24.000 on an automated driving feature to members of the public.

00:25:24.000 --> 00:25:39.000 Okay, so let's get into the new regulations that we have here in California. I think this is the kind of the big topic that is the use case that we're adding here to our regulations, and that is heavy duty autonomous trucks. Since 2014

00:25:39.000 --> 00:25:54.000 California has prohibited vehicles with that weigh over 10,001 gross vehicular weight rating from testing or deploying automated driving systems on California roads. We wanted to start with light duty vehicles, and we wanted the companies to focus on

00:25:54.000 --> 00:26:11.000 The testing of those smaller vehicles on public roads, but what we've seen in other jurisdictions, such as Texas and Arizona and some of the other Sun Belt states, that this use case has emerged. And so this year, we have

00:26:11.000 --> 00:26:27.000 folded those vehicles into our program. Some of the highlights here for testing and deployment, these trucks, number one, they have to provide us with a safety case before they can actually apply for a permit. They're only authorized to

00:26:27.000 --> 00:26:45.000 operate on roads that are approved for freight corridors, and they're limited to accessing roads that are 25 miles per hour, unless those roads are between major freight facilities. And again, all commercial vehicle rules apply to these trucks

00:26:45.000 --> 00:27:03.000 They can't carry hazardous materials or oversized loads. They're not allowed to carry bulk or tanks, and they're not allowed to provide passenger service in these larger types of vehicles.

00:27:03.000 --> 00:27:18.000 And as I mentioned, we have three permits here in the state of California. We have safety driver, driverless and deployment. One of the new things that's in our regulations is a required progression. Now we require manufacturers to actually move through these stages of

00:27:18.000 --> 00:27:34.000 permits before they can actually move to deployment. As, again, they start with safety driver testing, and they move to driverless testing, and then finally on to deployment. And one of the things we've put in the regulations is an evidence-based progression

00:27:34.000 --> 00:27:49.000 The companies have to provide us with mileage, operational data, and safety performance along with their safety case before they can actually move into these and progress throughout these permits. So if they start with a safety driver

00:27:49.000 --> 00:28:03.000 They have to provide this level of data and mileage to the department in their application before they can progress to removing the safety driver from the vehicle and before they can actually progress to deployment

00:28:03.000 --> 00:28:14.000 For light duty vehicles, the minimum miles that they have to test in an intended operational design domain is 50,000 miles for the heavy duty companies, it's 500,000.

00:28:14.000 --> 00:28:31.000 I'll couch this by saying that the heavy-duty vehicles, many of them are operating long-haul trucking in other states, such as, again, as I mentioned, Arizona and Texas, and so in our rules, we are allowing up to 400,000 of those miles to come from other jurisdictions

00:28:31.000 --> 00:28:40.000 But at least 100,000 miles must be conducted here in the state of California

00:28:40.000 --> 00:29:00.000 Another big item for our regulations is enhanced data reporting. Previously in our regulations, we focused on just crash reporting and collecting disengagements. And what we noticed is that while crash reporting is important, it's really a lagging indicator of safety

00:29:00.000 --> 00:29:20.000 And so what we wanted to provide for our oversight is more leading indicators of safety. And so, in addition to collisions, we're actually aligning now with NHTSA's SGO framework. We actually get all the full reports, not the redacted, but the unredacted reports that are sent to

00:29:20.000 --> 00:29:26.000 to the USDOT, we now receive those in the same timeframe as the USDOT

00:29:26.000 --> 00:29:40.000 But also we get leading indicators of safety that may provide us with information on perhaps near misses or indications of safety that we need to investigate.

00:29:40.000 --> 00:29:42.000 And those are

00:29:42.000 --> 00:29:57.000 System failures. So we see here on the screen dynamic driving task performance relevant system failures. This is where there's an issue with the software or hardware that prevents the automated driving system from performing the driving task

00:29:57.000 --> 00:30:12.000 We get vehicle miles traveled. We collect braking events. These are situations where there is a hard braking event of over 0.5 G's occurring on the public roads and also vehicle immobilizations

00:30:12.000 --> 00:30:27.000 So under a testing permit, the companies have to provide this information to the department on a monthly basis. So we get near real-time information on these leading indicators. And when a company moves into deployment

00:30:27.000 --> 00:30:31.000 They have to provide this information to us quarterly

00:30:31.000 --> 00:30:42.000 Okay, so we have, again, much greater visibility into the safety and performance of these automated driving systems as they're operating on California public roads.

00:30:42.000 --> 00:31:02.000 And in addition to the data, we have expanded our enforcement tools. And I can't stress this enough that, of course, here in the United States, we operate under a self-certification model. Our colleagues in Europe have the type approval, but we're here in the United States, we have a self-certification model

00:31:02.000 --> 00:31:19.000 And it's very important under a self-certification model to have strong post-permitting controls. And so here in California, we have expanded our abilities, our enforcement tools, which gives us greater authority to monitor risk and to impose operational controls and to step in

00:31:19.000 --> 00:31:36.000 If we need to, to enforce compliance. And part of those tools include, you know, again, identifying these risks, as I mentioned, with the data. We have the ability to provide… to send information requests to the manufacturers.

00:31:36.000 --> 00:31:42.000 And something that's new here in our regulations is the ability to

00:31:42.000 --> 00:31:56.000 to provide operational controls in the form of restrictions. So our previous enforcement mechanism was either a suspension or revocation where we would cease all operations with the manufacturer

00:31:56.000 --> 00:32:13.000 And what has changed here in these new regulations is we can be much more precise and we can restrict either the fleet size, the ODD, the hours of operation, perhaps the weather, the speed. And again, this gives us a much more

00:32:13.000 --> 00:32:20.000 precise tool to use when we are looking at specific infants that are occurring on public roads.

00:32:20.000 --> 00:32:38.000 Something else that's new here in the state of California that was recently effective July 1st of 2026 this year, our AV moving violations. Prior to July 1st, 2026, peace officers could not issue a traffic citation to an autonomous vehicle

00:32:38.000 --> 00:32:59.000 that was operating without a safety driver. Why is that? Well, here in California, we do not issue a driver license to artificial intelligence. We don't issue… we issue driver licenses to human drivers. And so, prior to this law being 38752 of the vehicle code

00:32:59.000 --> 00:33:18.000 There was no mechanism to provide a citation to an autonomous vehicle. So 38752 vehicle code now allows for a peace officer to issue what is a notice of noncompliance to the manufacturer of the technology as well as to the department

00:33:18.000 --> 00:33:35.000 And why are we issuing it to the manufacturer? Well, when we were determining how best to structure this program, who or what entity is most responsible for improving or correcting the driving behavior of the automated driving system

00:33:35.000 --> 00:33:37.000 It's the manufacturer

00:33:37.000 --> 00:33:55.000 And so again, law enforcement now can conduct a traffic stop and issue these notices directly to the manufacturer and directly to the department. We receive these notices. We have received eight so far since July 1st for

00:33:55.000 --> 00:34:06.000 Various incidents, we review those incidents, and then determine whether or not any enforcement action is needed.

00:34:06.000 --> 00:34:23.000 Again, another topic that's very important here in California, because we are seeing many of these robotaxis and also Level 4 driverless vehicles, is remote operations. This is something that I think all jurisdictions, not only in the United States, but all of our colleagues across

00:34:23.000 --> 00:34:53.000 that are regulating this space across the globe is a very important topic, and that is how do we create requirements associated with remote operators? And there's really two remote operator roles that we have provided rules for here in California, and that's one is the remote driver, and one is the remote assistant

00:35:05.000 --> 00:35:06.000 And I think it's really important to understand the distinction between both of these roles. And here in California, we have actually created requirements associated with both of these roles because they are distinct.

00:35:06.000 --> 00:35:09.000 So for a remote driver, these are individuals that actually have the ability to drive the vehicle to perform the driving task of the vehicle from a remote location, from an office or from somewhere else.

00:35:09.000 --> 00:35:15.000 A remote assistant is one that is able to provide guidance and support, but they're not performing the dynamic driving task.

00:35:15.000 --> 00:35:31.000 So we have specific requirements associated with both of those roles to ensure that number one, we are understanding incidents that occur on the roads and ensure that manufacturers are supporting these ADS as they operate.

00:35:31.000 --> 00:35:48.000 And I think most important to our discussion today is emergency geofencing requirements. Again, this is codified in Vehicle Code 38751 here in California. And again, we have also folded this into our regulations

00:35:48.000 --> 00:36:03.000 And this is regarding emergency geofence messages. Emergency response officials in our cities here throughout California can now issue an emergency geofencing message to manufacturers

00:36:03.000 --> 00:36:19.000 And once a manufacturer receives that, they have 2 minutes to direct their fleet to leave or and avoid a particular area. Now, I will say that these are for emergency situations, and emergencies we define here in California

00:36:19.000 --> 00:36:33.000 Are sudden or unexpected occurrences that require immediate action to prevent loss or damage of life, health, property, or essential public services. So these are for emergency-type situations.

00:36:33.000 --> 00:36:49.000 And there are specific officials that can actually perform this, and those are emergency dispatch, first responders, or peace officers. And so I think this is a really key to our discussion here with the OMF. We're really excited that there's

00:36:49.000 --> 00:37:05.000 a project that is going on between the OMF and some of our jurisdictions here in California. I will say also, we are in close discussions, not only with those just those jurisdictions, but also with the manufacturers

00:37:05.000 --> 00:37:21.000 To see how these new regulations are going to be implemented, especially with the OMF solution that we will be discussing later today. So again, I know I covered a lot of information here. Again, these are very comprehensive rules

00:37:21.000 --> 00:37:28.000 Happy to take any questions and continue the discussion today.

00:37:28.000 --> 00:37:33.000 I'm a brilliant presentation. Thank you so much for that.

00:37:33.000 --> 00:37:43.000 Lots of great details. I appreciate it. There are some questions in the chat. You can take a glance and then we'll call them out individually.

00:37:43.000 --> 00:37:54.000 I'll take moderator prerogative and just point out, like you sort of did at the end there. But MDS as it stands now

00:37:54.000 --> 00:38:01.000 can support a lot of the different things you talked about, like the expanded data reporting even

00:38:01.000 --> 00:38:08.000 All of that can come in MDS and you're currently using a CSV format, MDS would be JSON

00:38:08.000 --> 00:38:18.000 And then the operational restrictions could also be sent in a digital way, similar to the geofencing requirements, like you talked about

00:38:18.000 --> 00:38:23.000 So I guess I could… I guess I'll ask

00:38:23.000 --> 00:38:35.000 beyond the geofencing requirements, is there any discussions about potentially using MDS as a standard way to do that? So other states or cities could maybe do the same thing?

00:38:35.000 --> 00:38:52.000 I think that's a great question. I think that our rules right now are not prescriptive. The California Vehicle Code talks about a common communication mechanism to do so. I think we're here discussing right now, this is a avenue that

00:38:52.000 --> 00:39:10.000 That it appears that there's jurisdictions here on the call that are using this already, and I think this is a tool that can be used, Michael, as you mentioned, to support what we're talking about. But at this point, we haven't prescribed a particular mechanism

00:39:10.000 --> 00:39:26.000 But I think that what we're discussing today shows great promise to providing a solution that can be used by not only the cities and locals, but also the manufacturers. I think in the last meeting we had in Waymo participant

00:39:26.000 --> 00:39:42.000 mentioned creating some kind of standardized way to receive these messages, to be able to communicate. I think that that's what's really important, is you take a look at AV manufacturers that are operating in multiple local jurisdictions throughout California

00:39:42.000 --> 00:39:48.000 And I think that that is what an OMF solution can provide.

00:39:48.000 --> 00:40:05.000 Great, yeah, thank you for that answer. And thinking about it from a broader adoptability concept. And yeah, if people want to look back at last month's meeting, like Miguel just mentioned, Waymo and Henry from Waymo presented about how they

00:40:05.000 --> 00:40:24.000 are interested in having some standard way to get these emergency notifications across jurisdictions, because it helps them versus getting it by email or other methods. So, let's go to the chat and just sort of take the questions as they came in

00:40:24.000 --> 00:40:33.000 And you, Miguel, might want to read this, so I don't have to read the whole thing, but the first one's from Cormac McKay

00:40:33.000 --> 00:40:38.000 And it's basically talking about the accountability

00:40:38.000 --> 00:40:43.000 For responsible integration and AV deployment

00:40:43.000 --> 00:40:59.000 And maybe this might be a question for you as a state authority, but also city authorities. How are they taking authority and responsibility for effective communications, etc. I don't know if Cormac, you want to express that verbally or we could

00:40:59.000 --> 00:41:03.000 Let me go all try to answer that

00:41:03.000 --> 00:41:14.000 Hi, yes. Thanks. I did mention it last month at the meeting, and I do think too much responsibility has been put on the operators

00:41:14.000 --> 00:41:19.000 And because of that, there's a lot of negativity in the media

00:41:19.000 --> 00:41:34.000 And this is doing real damage to public perception when city authorities aren't really taking responsibility for that effective communication. Now, this new communications for emergencies is a small step along the way

00:41:34.000 --> 00:41:43.000 But there has to be more effective communications and responsibility taken from the city authorities.

00:41:43.000 --> 00:41:45.000 And I'll leave it at that.

00:41:45.000 --> 00:41:51.000 Okay, Miguel, do you have thoughts on that?

00:41:51.000 --> 00:42:09.000 Yeah, I mean, I'll probably, you know, leave it up to the cities here on the call, but you know, I think that the cities are actively working on this. I mean, I think you see Salvador here and also our San Francisco colleagues as well, they're actively working on these efforts right now, so I think that

00:42:09.000 --> 00:42:25.000 I mean, I don't know, Cormac, if there's a specific incident or those kinds of things, but I can share that here, at least here in California, the cities are actively working on developing these solutions.

00:42:25.000 --> 00:42:26.000 Salvador? Yeah.

00:42:26.000 --> 00:42:27.000 Thank you. Thanks.

00:42:27.000 --> 00:42:40.000 Thank you, Miguel. Yeah, just to speak, I just wanted to add, so my name is Salvador Gutierrez. I'm a supervising transportation planner with the Los Angeles Department of Transportation. So the commercial rideshare mobility team, the great and mighty team, small and mighty team, I should say

00:42:40.000 --> 00:42:55.000 You're at LADOT is that we're working, we're trying to do our best, you know? So we're working with the operators. We're having conversations with them. We are in communication with them, and we're also working with the state regulatory agencies. So the California DMV, the CPUC

00:42:55.000 --> 00:43:01.000 And currently, cities don't have any authority per the regulations to

00:43:01.000 --> 00:43:18.000 To permit and to regulate these autonomous vehicles, but we're, you know, we're using the existing regulations, and they're advancing, as you can see, as Miguel was speaking to the emergency geofencing. So we're very excited, to work with the DMV, work with the OMF

00:43:18.000 --> 00:43:28.000 Also work with other cities in California, like San Francisco, and really build upon what Seattle has piloted, working with the OMF Foundation. So

00:43:28.000 --> 00:43:44.000 We, we're doing our best and we're also learning from our friends in Austin, so we're trying to do the best of what we can, and I think some cities are at the table, and again, a lot of it is dependent on resources. So cities manage the public right of way, so autonomous vehicles is

00:43:44.000 --> 00:44:02.000 One, one mode that we manage, or that are trying to get a sense of, but we're really managing the whole transportation ecosystem. And so we're trying to, you know, do the best that we can to manage private vehicles, our regular ledot. We manage public buses. So we have. We're like the second largest

00:44:02.000 --> 00:44:10.000 municipal, bus operator in LA County. So that's like we have 52 business lands. So we're trying to

00:44:10.000 --> 00:44:23.000 We're trying to do the best we can, but we are, I think it's… we're going to figure this out together, and so it's not going to just be the operators. We're not trying to put the onus just on the operators, but we're trying to work with

00:44:23.000 --> 00:44:36.000 But DMV, our friends at the DMV, Cpuc, and other cities so that we can try to figure this out and how to Cavs operate safely on our public roads.

00:44:36.000 --> 00:44:43.000 Any other city folks want to chime in

00:44:43.000 --> 00:44:46.000 Yeah, so from Austin, I'll add like

00:44:46.000 --> 00:45:03.000 Vita X, our digital infrastructure is great, but like mostly what AVs need is really good hard infrastructure of, you know, striping signs, stuff like that. And it's hard for us to justify spending a huge amount of money on AV infrastructure when these are like

00:45:03.000 --> 00:45:11.000 In Austin, at least, the three richest companies in the world, and we have to, like, bond out building a pool, you know? Like

00:45:11.000 --> 00:45:25.000 Spending money for specifically AVs is just not going to fly with voters. So, like, we're doing everything we can. Hard infrastructure helps drivers as well, and a lot of V2X solutions is going to help drivers as well. So, like, that's what we've got to pursue. And I think MDS

00:45:25.000 --> 00:45:46.000 Because it, you know, will help our emergency services, but it will also help, you know, possibly like TNC drivers, micro mobility, things like that. Like, we need solutions that aren't just to support Waymo, Tesla, and Zoox, but to support all the users of the right of way

00:45:46.000 --> 00:45:48.000 Thank you, Rachel. Alex

00:45:48.000 --> 00:46:09.000 Yeah, basically echoing a lot of what Rachel said. I mean, like you saw my colleague Mui present on San Francisco is kind of like ideal goal to digitize a lot of the temporary, I guess, incidents and closures happening on the street. Certainly an AV benefit, I think it's motivating a lot of efforts now, but a lot of

00:46:09.000 --> 00:46:22.000 If the information is important and good enough for AVs, then I think it's also important, good enough for everyone else, kind of connected fleets and everyone else is using mapping services like Google Maps. So, MDS can provide that pathway

00:46:22.000 --> 00:46:25.000 Which is

00:46:25.000 --> 00:46:39.000 Great. Thanks for that feedback from California and Texas cities. Let's move to the next question so we can hit them all. Ellen asks, does your ability at California DMV

00:46:39.000 --> 00:46:42.000 to request information exceed that of

00:46:42.000 --> 00:46:46.000 NHTSA

00:46:46.000 --> 00:46:50.000 We have the ability to

00:46:50.000 --> 00:47:04.000 to ask for a variety of information, whether that's sensor data, that's information regarding specific incidents, we have a very comprehensive ability to ask for information.

00:47:04.000 --> 00:47:22.000 And so I say it would probably be along the lines of something similar to what the USDOT can ask for. Of course, we have different charges, right? The USDOT, ODI is looking for defect investigation. They're looking at various types of engineering type of questions

00:47:22.000 --> 00:47:37.000 And we're looking for more in terms of the incidence and relative, the safe operation of those vehicles. So, we do have a very comprehensive authority to investigate.

00:47:37.000 --> 00:47:46.000 Great. Thank you for that answer. I'm going to jump to a quick response here from Henry from Waymo

00:47:46.000 --> 00:48:01.000 It's not a question, but just I think Henry's saying, as a product manager at Waymo, who's formerly responsible for regulatory reporting across all markets, we generally would love to use APIs to submit regulatory reports. So

00:48:01.000 --> 00:48:06.000 Henry from Waymo's a favor. Henry, would you like to say anything about that?

00:48:06.000 --> 00:48:09.000 Yeah, sure.

00:48:09.000 --> 00:48:24.000 We, like, different jurisdictions, we submit regulatory reports in different ways. Oftentimes it's CSVs, sometimes it's via email. We've discussed at various points, potentially building a portal internally where different regulators can log in

00:48:24.000 --> 00:48:41.000 And extract their data, but like, you know, an API also would be beneficial for us as well. We're essentially trying to automate as much of this as possible. And so, yeah, APIs, like be it for NHTSA or different city

00:48:41.000 --> 00:48:47.000 regulators or international markets is definitely our preferred way of doing this.

00:48:47.000 --> 00:48:55.000 That's great. As a proponent of APIs, it's nice to hear you say that. And

00:48:55.000 --> 00:49:02.000 Part of alphabet, I feel like APIs are a great way to go to facilitate data communication.

00:49:02.000 --> 00:49:08.000 I've got another question here. This one might be a quick answer, Miguel, but

00:49:08.000 --> 00:49:23.000 Curious as to what basically about Tesla FSD software and customers requires customers to pay attention. Do you get safety data from Tesla when FSD mode is being used?

00:49:23.000 --> 00:49:40.000 So I think the question was regarding the FSD supervised. That is a level two ADAS. And so again, as I mentioned in the slide deck, we don't regulate. We regulate ADS or automated driving systems. So Tesla is a permit holder

00:49:40.000 --> 00:49:57.000 For AVs and as such, all permit holders have to provide us with the data that I mentioned in the slide deck. So, but in terms of the specific product that I think the person's referencing, we don't regulate ADAS

00:49:57.000 --> 00:50:01.000 Here in California

00:50:01.000 --> 00:50:05.000 Yeah, thanks. The next question is

00:50:05.000 --> 00:50:15.000 Our faded street sign something that AVs can identify and communicate to cities via MDS so this might be an OMF question more than for you

00:50:15.000 --> 00:50:18.000 Are there dedicated fields?

00:50:18.000 --> 00:50:30.000 There's not specifically for reporting faded signs, but there is through MDS 2.1 the ability to report an incident and the incident can be

00:50:30.000 --> 00:50:39.000 an issue or an obstruction, and that that information has like a name and description that could be open-ended

00:50:39.000 --> 00:50:44.000 Or you could provide, actually, custom fields through MDS so it's not

00:50:44.000 --> 00:50:57.000 explicitly in there, but there is certainly a way to send that information if, for instance, you like, let's say you have a sanitation truck with a camera on it, and it has some

00:50:57.000 --> 00:51:09.000 machine learning, you could send that via MDS back to a central location if you'd like to sort of get a sense of where there are signs that need repairs or clarifications.

00:51:09.000 --> 00:51:14.000 All right, let's see.

00:51:14.000 --> 00:51:30.000 There is a discussion here from Philadelphia with a few comments about fleets being directed to leave or avoid areas, which is something that you have in there. But is there a way to say a fleet needs to stay put and or

00:51:30.000 --> 00:51:40.000 With a follow-up question, stay at the curb for some reason. Is that… do you… do you have that particular level of detail in your geofencing and emergency?

00:51:40.000 --> 00:51:44.000 Response.

00:51:44.000 --> 00:51:47.000 Sorry, is this a question for me on the layman?

00:51:47.000 --> 00:51:50.000 I think it's a wild question, I think

00:51:50.000 --> 00:51:51.000 Isaac.

00:51:51.000 --> 00:51:57.000 Like, do you… is that… do you have that ability, I guess, for that type of emergency request

00:51:57.000 --> 00:52:13.000 That's bringing up a really interesting point. And again, that's something that, you know, again, we're learning that we're very early on here, but I think these emergency geofence messages, I think as this is the first set of regulations associated with them, but I think you're bringing up a really interesting point

00:52:13.000 --> 00:52:30.000 And that is, can we have the ability, and we've talked to the cities about this as well, to have more of a dynamic ability to send messages, like, for example, what we're just talking about here, not just to avoid, but is there an ability to send a specific message about to stay

00:52:30.000 --> 00:52:45.000 or to move off the travel lane, something a little bit more granular. And I think that that's a really good point, and something that we're actually continuing to explore as we launch these new set of regulations.

00:52:45.000 --> 00:52:50.000 Henry has his hand up and had left a comment as well. Henry

00:52:50.000 --> 00:53:06.000 Yeah, just to, this is something we're very much working on right now. And so our default for a lot of these messages right now is we call it, don't be here. It essentially tries to keep AVs out, and if they're in, tries to send them out

00:53:06.000 --> 00:53:20.000 That being said, from what we've seen, a lot of the times is that can potentially be overkill. A lot of these can just be, hey, don't do pickups or drop-offs in these areas, but it's totally safe to drive through

00:53:20.000 --> 00:53:36.000 And it definitely has, you know, user impact. People get very frustrated because they have to walk, you know, multiple blocks, right, to get, you know, or their routes are very severely impacted, especially if there are multiple of these. So, yeah, we would be very

00:53:36.000 --> 00:53:38.000 the more granular

00:53:38.000 --> 00:53:48.000 bits of information we get, the better we can respond to these sorts of events. So yeah, a lot of interest at least this AV company.

00:53:48.000 --> 00:54:00.000 That's great. Thank you, Henry. And Andrew mentioned this, but MDS, based on the conversations happening in chat, MDS supports, let's say 90% of these types of

00:54:00.000 --> 00:54:16.000 incidents that if we need to clarify it or add new types of things, rules to MDS that's we have a process for that. So if you want to use MDS and it looks like it's not supporting it, let us know and we can work through this working group

00:54:16.000 --> 00:54:22.000 I'll take… I'll do one more question, and the rest we might have to do via

00:54:22.000 --> 00:54:29.000 Chat or follow up later. The last question on here is from Tony

00:54:29.000 --> 00:54:43.000 How closely do you coordinate and align with the company's McQuell? What mechanism do you use? I think

00:54:43.000 --> 00:54:44.000 Yeah.

00:54:44.000 --> 00:54:45.000 Do you have direct communications, any insight how to do it well for other cities? So I think your presentation covers a lot of this, but maybe if you want to speak to it in summary.

00:54:45.000 --> 00:55:02.000 Absolutely. I think that that, you know, collaboration communication is essential. And I saw our colleague, there's a Waymo representative here. You know, we have direct communication with all the companies and, you know, companies that are

00:55:02.000 --> 00:55:17.000 Operating here on California public roads, some we meet on a with a monthly basis or even more frequently than that quarterly basis, but absolutely we meet very frequently. And in fact, we even visit with them

00:55:17.000 --> 00:55:33.000 Face-to-face, we do it online. So, I think that that's really important. We have that direct interface, but also we'll mention that we also have created working groups with our local and city partners as well. And I think tackling this particular

00:55:33.000 --> 00:55:49.000 challenge and I think… I don't know Michael or Andrew, if there's an opportunity to talk about this in a future meeting, but the work we're doing here in California from a state and local collaborative perspective to tackle this particular issue

00:55:49.000 --> 00:56:05.000 I think is also important. So, I think here we have very strong state regulations, of course, the authority here is at the state level, but we work very… we're working very closely with our city partners as well. You saw LADOT here

00:56:05.000 --> 00:56:21.000 There's SFMTA, and there's other cities here, San Jose. We're working with many other cities as well. So I think, and there are regular meetings going on with each one of those. So I think it's all of that together. And so, Andrew or Mike, I just want to say, maybe for a future meeting

00:56:21.000 --> 00:56:36.000 It'd be great to have a discussion about how we're collaborating. And I don't know, I'd love to hear how Texas and Arizona and the other states and cities are doing that as well, but collaboration is the key.

00:56:36.000 --> 00:56:53.000 I'll say we'll bring that back to the steering committee, which sets the agendas for these meetings and many of those cities are on the are here and on the steering committee, Los Angeles, San Francisco, San Jose. So there's a lot of them on there. So it is probably

00:56:53.000 --> 00:57:02.000 A great discussion topic for a future meeting that that city perspective. Would anyone like to share anything about that now? If you are a city

00:57:02.000 --> 00:57:05.000 And how you're collaborating

00:57:05.000 --> 00:57:08.000 With the state and with the companies

00:57:08.000 --> 00:57:11.000 Rachel has something there, but Henry?

00:57:11.000 --> 00:57:26.000 Yeah, I will say, like, we definitely… for regulatory reporting, like, we consult with regulators, we also have meetings when we submit reports before we submit reports, but also, you know, I've been in multiple meetings with, for example, SF

00:57:26.000 --> 00:57:43.000 Department of Emergency Management and other folks to think about, you know, what are we going to do for our different types of operational response? So, yeah, the… I think the best answer is yes, all of the above. The more collaboration, the better.

00:57:43.000 --> 00:57:50.000 Great, and I see Rachel's comment as well that they've started

00:57:50.000 --> 00:57:56.000 AV, Texas AV Task Force subcommittee, so I think that might be connected to this

00:57:56.000 --> 00:58:12.000 And Aileen's comment about in response to, can we get some of this positive energy out to the media and highlighted there, because I would agree, it would be nice. And she points out that UMF is just tired of communications and engagement manager, so that's something we can

00:58:12.000 --> 00:58:15.000 We can work on. But

00:58:15.000 --> 00:58:21.000 That's that. Okay, I think since we're at time, I'll go ahead and wrap up the meeting.

00:58:21.000 --> 00:58:39.000 Thank you all for the great discussion today, and feel free to email us with follow up questions. The recording will be shared. The slides that you saw will be shared and we will definitely talk about something related to this at a future meeting

00:58:39.000 --> 00:58:45.000 The next meeting is in, let me get the date right…

00:58:45.000 --> 00:59:04.000 December 17th, so look for a message about that, and we'll talk to our steering committee about the agenda. So, thanks everyone. Thank you, Miguel, for the great presentation and the details and the work that you're doing in California.

00:59:04.000 --> 00:59:13.000 Bye, everybody.

00:59:13.000 --> 00:59:19.000 Thanks, everybody.