Web conference notes, 2026.09.24 (MDS Working Group)

• 00:12:23 Rachel Castignoli AUSTIN: Reacted to "MDS 2.1 overview deck https://docs.google.com/presentation/d/1qfRmbuszdXSX6C0jLdbpT73EJ7c-V-dE--ZXp2w9rr0/edit?usp=sharing" with 👍

• 00:12:30 Andrew Glass Hastings: Hello everyone! Andrew Glass Hastings the OMF ED! Glad you are on the call!

• 00:12:37 Rachel Castignoli AUSTIN: Reacted to "Hello everyone! Andrew Glass Hastings the OMF ED! Glad you are on the call!" with 👍

• 00:12:41 Said Abou Kharroub: Reacted to "Hello everyone! An..." with 👍

• 00:12:46 Robert White: Robert White - Nashville DOT

• 00:12:52 Vignesh Ram (Serve Robotics): Vignesh Ram with Serve Robotics! We build and deploy sidewalk delivery robots. Excited to meet anyone I haven’t met already 🙂

• 00:13:00 Ramses Madou |San Jose: Hi All, Ramses Madou here, Chair of the OMF board and from City of San Jose

• 00:13:05 Sophie Jantz: Sophie Jantz - DoorDash

• 00:13:05 Tomas Carranza: Tom Carranza with LADOT (& OMF Board Member)

• 00:13:07 Lisa Hood: Hey there. :)

• Lisa Hood City of San Jose

• 00:13:08 Rachel Castignoli AUSTIN: Reacted to "Robert White - Nashville DOT" with 👍

• 00:13:16 Fernando Navarrete: Fernando Navarrete, LADOT

• 00:13:18 Viktoriya Wise: Viktoriya Wise, SFMTA and OMF Board Member

• 00:13:18 Mary Nicol, Chicago DOT: Mary Nicol, Chicago DOT and OMF Board member

• 00:13:29 Zahra Entezami: I'm Zahra - City of Toronto, Transportations , D&A

• 00:13:31 Ricky Cervantes (Seattle DOT): Good morning everyone! Ricky Cervantes with Seattle DOT.

• 00:13:32 Hannah Morrison, PBOT: Hannah Morrison, Portland Bureau of Transportation

• 00:13:43 Sebastian Silva (LADOT): Sebastian Silva from LADOT

• 00:13:48 Miguel acosta, CA DMV: Miguel Acosta, California DMV

• 00:13:50 Chava Kronenberg: Chava Kronenberg, San Francisco Municipal Transportation Agency

• 00:13:50 tim Adams - HAAS Alert: Tim Adams - HAAS Alert

• 00:13:52 Rachel Castignoli AUSTIN: Rachel Castignoli - Austin, TX

• 00:13:52 Josh Lynch - PBOT: Josh Lynch, Portland Bureau of Transportation

• 00:13:53 Ajjit (Revoution BTS): Ajjit Narayanan from Revolution BTS, a docked bikeshare operator!

• 00:13:59 Josh David (Lyft): Josh David with Lyft

• 00:14:00 Cormac McKay: Hi Cormac McKay Aeravai CCAM-RITES Project Director here https://ec.europa.eu/eusurvey/runner/da22418f-897e-86fe-91e2-3808b99a6420

• 00:14:03 Michael Schwartz (INRIX): Michael Schwartz with INRIX

• 00:14:05 Emily Warren (CalSTA): Emily Warren, California State Transportation Agency

• 00:14:07 Andrew Glass Hastings: Reacted to "Robert White - Nashville DOT" with 👍

• 00:14:08 Rachel Castignoli AUSTIN: Reacted to "Michael Schwartz with INRIX" with 👍

• 00:14:11 Christopher Shelley | City of Philadelphia: Chris Shelley, Smart Cities team at City of Philadelphia

• 00:14:19 Lars Ove Kvalbein, City of Bergen, Norway: Lars Ove Kvalbein from the City of Bergen, Norway

• 00:14:20 Jeff Kaplan: Jeff Kaplan, joining from the City of Boston

• 00:14:21 Andrew Glass Hastings: Reacted to "Vignesh Ram with Serve Robotics! We build and deploy sidewalk delivery robots. Excited to meet anyone I haven’t met already 🙂" with ✋

• 00:14:28 Justin Wiley (UC Berkeley): Justin Wiley, UC Berkeley, Institute of Transportation Studies

• 00:14:38 Andrew Glass Hastings: Reacted to "Viktoriya Wise, SFMTA and OMF Board Member" with ✋

• 00:14:41 Andrew Glass Hastings: Reacted to "Mary Nicol, Chicago DOT and OMF Board member" with ✋

• 00:14:42 Bern Grush, Urban Robotics Foundation: Bern Grush, URF, drafted the ISO 25614 standard for robotaxi pickup/drop-off, draft completed, to be published in 2027.

• 00:14:45 Stephen Miller (Transit app): Stephen Miller from the Transit app 👋

• 00:14:57 Dan Hubert: Hello I’m Dan Hubert CEO of AppyWay. A digital kerbside company that offers large scale digital twins for curb restrictions and road way rules. We manage and publish over 45,000kms of curb data.

• 00:15:11 Andrew Glass Hastings: Reacted to "Emily Warren, California State Transportation Agency" with ✋

• 00:15:15 Andrew Glass Hastings: Reacted to "Lars Ove Kvalbein from the City of Bergen, Norway" with ✋

• 00:15:25 Andrew Glass Hastings: Reacted to "Hello I’m Dan Hubert CEO of AppyWay. A digital kerbside company that offers large scale digital twins for curb restrictions and road way rules. We manage and publish over 45,000kms of curb data." with ✋

• 00:15:37 Grant Sivesind (Daro): Grant Sivesind from Daro Technologies

• 00:16:04 Rachel Castignoli AUSTIN: Reacted to "Grant Sivesind from Daro Technologies" with 👍

• 00:16:43 Halina Do-Linh (LADOT): Hi! Halina from LADOT 🙂

• 00:18:07 Remi Kuti: Hi, I’m Remi Kuti, founder of UrbanShield in London. I’m here to learn more about MDS and how we can contribute.

• 00:18:13 Nate Gargiulo: Nathan Gargiulo - California DMV

• 00:18:27 Marcin Wójcik (Nivel): Hey, Marcin from Nivel here - engineering team.

• 00:18:39 Raphael Dumas: Raphael from Toronto Transportation Services

• 00:18:54 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:19:06 Krishna Singh: krishna from city of Boston

• 00:20:12 Anders Waage Nilsen (Bergen, Norway): Anders from the city of Bergen, (also OMF board member).

• 00:21:37 Cormac McKay CCAM-RITES: Are City/State Authorities & Transport agencies taking enough responsibility in having a responsible integration in to our Transport EcoSystem? Why are operators getting all the blame for their failure to make the necessary Investments and preparations? https://lnkd.in/p/dNFAytJ8

• 00:21:54 Sven Bråten (Nivel): Sven from Nivel, Norway.

• 00:22:02 Cormac McKay CCAM-RITES: Reacted to Are City/State Autho... with "❤️"

• 00:22:07 Cormac McKay CCAM-RITES: Reacted to Are City/State Autho... with "👍"

• 00:24:32 Andrew Glass Hastings: Reacted to "Anders from the city of Bergen, (also OMF board member)." with ✋

• 00:24:41 Marcin Wójcik (Nivel): Reacted to "Sven from Nivel, ..." with 👏

• 00:25:00 Rachel Castignoli AUSTIN: Reacted to "Hannah Morrison, Portland Bureau of Transportation" with 👍

• 00:25:43 Ramses Madou |San Jose: Michael can you share the deck you just did as well?

• 00:25:48 Matthew Clark: Matthew Clark from Steer, UK Consultant on all new mobility technologies. Great to be here, hello all!

• 00:25:54 Alia Verloes (Blue Systems): Reacted to "Matthew Clark from..." with ❤️

• 00:25:56 Emily Warren (CalSTA): Digital Conflict Area Awareness Management Program - Transportation | seattle.gov

• 00:26:05 Rachel Castignoli AUSTIN: Reacted to "Digital Conflict Area Awareness Management Program - Transportation | seattle.gov" with 👍

• 00:26:10 Ramses Madou |San Jose: Reacted to "Digital Conflict Area Awareness Management Program - Transportation | seattle.gov" with 👍

• 00:26:13 Marcin Wójcik (Nivel): Reacted to "Digital Conflict A..." with 👍

• 00:26:14 Cormac McKay CCAM-RITES: Reacted to Matthew Clark from S... with "❤️"

• 00:26:33 Cormac McKay CCAM-RITES: Reacted to Bern Grush, URF, dra... with "❤️"

• 00:26:37 Michael Schnuerle (OMF): The deck is available on our agenda page now, and in the meeting notes and recap email: https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.09.24-(MDS-Working-Group)#minutes Waymo’s upcoming slides will be added after the meeting.

• 00:27:01 Ramses Madou |San Jose: thank you!

• 00:27:19 Michael Schnuerle (OMF): Reacted to "Are City/State Authorities & Transport agencies taking enough responsibility in having a responsible integration in to our Transport EcoSystem? Why are operators getting all the blame for their failure to make the necessary Investments and preparations? https://lnkd.in/p/dNFAytJ8" with 👀

• 00:27:39 Michael Schnuerle (OMF): Reacted to "Hi! Halina from LADOT 🙂" with 👋

• 00:27:48 Michael Schnuerle (OMF): Reacted to "Stephen Miller from the Transit app 👋" with 👋

• 00:28:05 Michael Schnuerle (OMF): Reacted to "Emily Warren, California State Transportation Agency" with ✋

• 00:28:28 Andrew Glass Hastings: @Cormac McKay CCAM-RITES would you mind reposting the link to that LinkedIn post you just shared? I had to switch devices and lost the previous chats.

• 00:28:37 Alia Verloes (Blue Systems): Reacted to "Digital Conflict A..." with 👍

• 00:28:39 Michael Schnuerle (OMF): Reacted to "thank you!" with 👍

• 00:29:44 Said Abou Kharroub: Replying to "@Cormac McKay CCAM..."

• https://www.linkedin.com/feed/update/urn:li:activity:7500330478890225664/?dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287500334473364914176%2Curn%3Ali%3Aactivity%3A7500330478890225664%29

• 00:29:58 Michael Schnuerle (OMF): Reacted to "https://www.linkedin.com/feed/update/urn:li:activity:7500330478890225664/?dashCommentUrn=urn%3Ali%3Afsd_comment%3A👍87500334473364914176👍Curn%3Ali%3Aactivity%3A7500330478890225664👍9" with 👍

• 00:30:02 Cormac McKay CCAM-RITES: Replying to "@Cormac McKay CCAM-R..."

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

• 00:32:03 Stephen Miller (Transit app): Is the 911 dispatch info shared through the Policy API from SDOT also getting shared with King County Metro so it can adjust bus service as well?

• 00:32:04 Nivel | Harald Sævareid: Reacted to "Anders from the city..." with 👍

• 00:32:13 Rachel Castignoli AUSTIN: Y'all keep saying "sharing" - is data also being shared from AV companies to cities?

• 00:32:32 Michael Schnuerle (OMF): The MDS Policy is shared publicly for anyone to ingest and use. So yes, transit agencies, other companies, etc.

• 00:32:43 Stephen Miller (Transit app): Reacted to "The MDS Policy is shared publicly for anyone to ingest and use." with ❤️

• 00:32:46 Rachel Castignoli AUSTIN: Reacted to "The MDS Policy is shared publicly for anyone to ingest and use." with ❤️

• 00:32:55 Alia Verloes (Blue Systems): Reacted to "The MDS Policy is ..." with ❤️

• 00:33:23 Christopher Shelley | City of Philadelphia: Reacted to "Y'all keep saying "sharing" - is data also being shared from AV companies to cities?" with ❤️

• 00:33:27 Cormac McKay CCAM-RITES: Reacted to The MDS Policy is sh... with "❤️"

• 00:33:45 Cormac McKay CCAM-RITES: Reacted to Y'all keep saying "s... with "👍"

• 00:33:50 Michael Schnuerle (OMF): Replying to "Y'all keep saying "s..."

• We can talk about this during the Q&A thanks!

• 00:33:56 Nivel | Harald Sævareid: Hei! Harald from Nivel, Norway-based governance layer platform.

• 00:34:03 Cormac McKay CCAM-RITES: Reacted to We can talk about th... with "👍"

• 00:34:08 Rachel Castignoli AUSTIN: Reacted to "We can talk about this during the Q&A thanks!" with 👍

• 00:34:16 Christy Hirsch, Umojo: Excellent work, Pierre, Blue Systems Team, Seattle and LADOT!

• 00:34:31 Rachel Castignoli AUSTIN: Replying to "Y'all keep saying "sharing" - is data also being shared from AV companies to cities?"

• Thanks Michael! Seems like a great opportunity for cities and AV companies to work together.

• 00:34:37 Alia Verloes (Blue Systems): Reacted to "Excellent work, Pi..." with ❤️

• 00:34:50 Pierre Bouffort (Blue Systems): Reacted to "Excellent work, Pierre, Blue Systems Team, Seattle and LADOT!" with ❤️

• 00:35:06 Cormac McKay CCAM-RITES: Reacted to Are City/State Autho... with "👀"

• 00:36:40 Andrew Glass Hastings: Reacted to "Thanks Michael! Seems like a great opportunity for cities and AV companies to work together." with 💯

• 00:37:02 Andrew Glass Hastings: Reacted to "Is the 911 dispatch info shared through the Policy API from SDOT also getting shared with King County Metro so it can adjust bus service as well?" with 👍

• 00:37:20 Andrew Glass Hastings: Think Google, Waze, Apple Maps as well!

• 00:37:31 Michael Schnuerle (OMF): Reacted to "Think Google, Waze, Apple Maps as well!" with 👍

• 00:42:22 Andrew Glass Hastings: These actions are helpful. “Curb freeze” is an important condition.

• 00:42:34 Rachel Castignoli AUSTIN: Reacted to "These actions are helpful. “Curb freeze” is an important condition." with 👍

• 00:42:55 Rachel Castignoli AUSTIN: Replying to "These actions are helpful. “Curb freeze” is an important condition."

• absolutely! very useful!

• 00:43:07 Bern Grush, Urban Robotics Foundation: Reacted to "absolutely! very useful!" with 👍

• 00:43:29 Christy Hirsch, Umojo: Reacted to "Think Google, Waze, Apple Maps as well!" with 👍

• 00:45:37 Pierre Bouffort (Blue Systems): Replying to "Is the 911 dispatch info shared through the Policy API from SDOT also getting shared with King County Metro so it can adjust bus service as well?"

• No, the 911 dispatch info is shared in a custom format fom SFD/SDOT right now. The Policy API standard format doesn't allow for exchanges of dispatches, thus the translation job to MDS Policy.

• 00:47:40 Andrew Glass Hastings: Replying to "Is the 911 dispatch ..."

• But to clarify a bit - as Michael mentioned, transit agencies like King County Metro can use the Policy API in their ops and routing decisions. So transit can benefit from the emergency notifications and geofences through the Policy API as well.

• 00:48:06 Victoria Kovacs (City of Redmond, WA): If cities use MDS would Waymo still use Gemini to ingest the data, or can it more directly ingest from MDS?

• 00:48:16 Pierre Bouffort (Blue Systems): Reacted to "But to clarify a bit - as Michael mentioned, transit agencies like King County Metro can use the Policy API in their ops and routing decisions. So transit can benefit from the emergency notifications and geofences through the Policy API as well." with 👍

• 00:48:33 Aylene McCallum: Replying to "If cities use MDS would Waymo still use Gemini to ingest the data, or can it more directly ingest from MDS?"

• Great questions to help clarify a common misunderstanding

• 00:48:35 Cormac McKay CCAM-RITES: Replying to "Is the 911 dispatch ..."

• FOI from SFFD states they don't share live gps Tracking data

• 00:48:40 Michael Schnuerle (OMF): Gemini can still be used on ingested MDS Policy feeds, to take actions, combine with other info, and or understand the data. MDS Policy give you a jump start and consistent/clear data starting point.

• 00:49:13 Michael Schnuerle (OMF): Yes, these 4 things are supported now in MDS Policy

• 00:49:34 Emily Warren (CalSTA): Reacted to "Yes, these 4 things are supported now in MDS Policy" with 👍

• 00:49:45 Rachel Castignoli AUSTIN: I do not know that any of us know the incident duration of an emergency situation? That's why our expectation is 1 hour.

• 00:50:24 Emily Warren (CalSTA): The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency response official

• 00:50:39 Michael Schnuerle (OMF): Replying to "I do not know that a..."

• One thing to note with MDS Policy and the Seattle example, the details, duration, severity, etc get updated over time as new info is available.

• 00:50:59 Michael Schnuerle (OMF): Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency response official may extend the duration for the avoidance area.

• (5) Upon receipt of an emergency geofencing message from an emergency response official, an autonomous vehicle manufacturer shall acknowledge receipt of the message to the requesting official within two minutes.”

• And:

• “(2) In the event of a fleetwide emergency or system failure that may create a traffic hazard or impeded emergency response, an autonomous vehicle manufacturer shall immediately notify affected local jurisdictions, including emergency dispatch, of the location and status of the portion of their impacted fleet and deploy local incident technicians, where appropriate, whenever affected vehicles cannot be remotely recovered.”" with ✅

• 00:51:01 Andrew Glass Hastings: Replying to "I do not know that a..."

• So true - which is a benefit of the MDS translation of the CAD (Computer Aided Dispatch) which notifies in real-time as event changes in severity, size, location and when it ends!

• 00:51:24 Alia Verloes (Blue Systems): Reacted to "One thing to note ..." with 👍

• 00:51:31 Rachel Castignoli AUSTIN: Replying to "I do not know that any of us know the incident duration of an emergency situation? That's why our expectation is 1 hour."

• I'll have to look into our CAD but I don't believe we have a "close" time on emergencies. We think if an event is more than an hour we will at least have traffic control set up in that time.

• 00:51:39 Christy Hirsch, Umojo: Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency respon

• 00:51:44 Bern Grush, Urban Robotics Foundation: Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency response official may extend the duration for the avoidance area.

• (5) Upon receipt of an emergency geofencing message from an emergency response official, an autonomous vehicle manufacturer shall acknowledge receipt of the message to the requesting official within two minutes.”

• And:

• “(2) In the event of a fleetwide emergency or system failure that may create a traffic hazard or impeded emergency response, an autonomous vehicle manufacturer shall immediately notify affected local jurisdictions, including emergency dispatch, of the location and status of the portion of their impacted fleet and deploy local incident technicians, where appropriate, whenever affected vehicles cannot be remotely recovered.”" with 👍

• 00:51:50 Michael Schwartz (INRIX): These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc.

• 00:51:52 Vignesh Ram (Serve Robotics): Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency response official may extend the duration for the avoidance area.

• (5) Upon receipt of an emergency geofencing message from an emergency response official, an autonomous vehicle manufacturer shall acknowledge receipt of the message to the requesting official within two minutes.”

• And:

• “(2) In the event of a fleetwide emergency or system failure that may create a traffic hazard or impeded emergency response, an autonomous vehicle manufacturer shall immediately notify affected local jurisdictions, including emergency dispatch, of the location and status of the portion of their impacted fleet and deploy local incident technicians, where appropriate, whenever affected vehicles cannot be remotely recovered.”" with ✅

• 00:51:53 Vignesh Ram (Serve Robotics): Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency response official may extend the duration for the avoidance area.

• (5) Upon receipt of an emergency geofencing message from an emergency response official, an autonomous vehicle manufacturer shall acknowledge receipt of the message to the requesting official within two minutes.”

• And:

• “(2) In the event of a fleetwide emergency or system failure that may create a traffic hazard or impeded emergency response, an autonomous vehicle manufacturer shall immediately notify affected local jurisdictions, including emergency dispatch, of the location and status of the portion of their impacted fleet and deploy local incident technicians, where appropriate, whenever affected vehicles cannot be remotely recovered.”" with 👍

• 00:51:54 Rachel Castignoli AUSTIN: Replying to "I do not know that any of us know the incident duration of an emergency situation? That's why our expectation is 1 hour."

• But maybe that is something we can add in our CAD

• 00:51:54 Cormac McKay CCAM-RITES: Replying to "The California legis..."

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

• 00:52:12 Rachel Castignoli AUSTIN: Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency respon

• 00:52:31 Christopher Shelley | City of Philadelphia: Reacted to "Y'all keep saying "sharing" - is data also being shared from AV companies to cities?" with 👀

• 00:52:34 Andrew Glass Hastings: Replying to "I do not know that a..."

• Worth double-checking. In most systems we have found he “all clear” closeout notice is communicated by the first responders on the scene as they are leaving, and this is updated in the CAD.

• 00:52:38 Rachel Castignoli AUSTIN: Replying to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency respo

• 00:52:41 Pierre Bouffort (Blue Systems): Reacted to "One thing to note with MDS Policy and the Seattle example, the details, duration, severity, etc get updated over time as new info is available." with 👍

• 00:53:15 Emily Warren (CalSTA): Reacted to "California is really the leader on AVs and emergency response! Thanks for your work Emily." with ❤️

• 00:53:25 Michael Schnuerle (OMF): Replying to "These are all polygo..."

• Good point Michael I was thinking of how to work this into the discussion. CDS Curbs API publishes real time info, availability, access rules, policies, etc about curb zones, parking spaces, etc. It works like MDS Policy, but specific to curbs and parking.

• 00:53:26 Aylene McCallum: Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency respon

• 00:53:27 Rachel Castignoli AUSTIN: Reacted to "Worth double-checking. In most systems we have found he “all clear” closeout notice is communicated by the first responders on the scene as they are leaving, and this is updated in the CAD." with 👍

• 00:53:34 Aylene McCallum: Reacted to "California is really the leader on AVs and emergency response! Thanks for your work Emily." with ❤️

• 00:53:50 Michael Schwartz (INRIX): Yes and also thinking about Right of Way Data Specification beyond that.

• 00:53:51 Chava Kronenberg: Replying to "I do not know that a..."

• Our FD shared that there is just varying levels of the same emergency, so an all clear may be 10 hours after it’s likely fine for vehicles to return to roadways. Probably a place we need to work with our first responders more.

• 00:54:03 Victoria Kovacs (City of Redmond, WA): Reacted to "The California legislature recently passed SB 1246, which is pending signature and contains the following relevant requirements for commercial AV fleets:

• Bill Text - SB-1246 Autonomous vehicles.

• “(d) (1) An emergency response official may issue an emergency geofencing message to a manufacturer.

• (2) Within two minutes of receiving an emergency geofencing message, a manufacturer shall issue direction to its fleet to leave or avoid the area identified.

• (3) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

• (4) An emergency geofencing message shall include the initial duration for the defined avoidance area based on a reasonable assessment of the emergency. Where necessary, an emergency respon

• 00:54:04 Rachel Castignoli AUSTIN: Reacted to "Our FD shared that there is just varying levels of the same emergency, so an all clear may be 10 hours after it’s likely fine for vehicles to return to roadways. Probably a place we need to work with our first responders more." with 👍

• 00:54:13 Oskar Jahr: Replying to "These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc."

• I thought you were complimenting yourself for a second there, @Michael Schnuerle (OMF) 😅

• 00:54:23 Michael Schwartz (INRIX): Reacted to "I thought you were complimenting yourself for a second there, @Michael Schnuerle (OMF) 😅" with 🤣

• 00:54:24 Aylene McCallum: Reacted to "These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc." with 💡

• 00:54:29 Josh Schacht - Stantec: Reacted to "These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc." with 💡

• 00:54:30 Suresh L: Is my understanding correct - Waymo would have their own systems to keep the policy and pothole information (or) does it depend on others to keep that information. And, if there are multiple systems/operators, who ensures to keep them synced. ?

• 00:54:37 Rachel Castignoli AUSTIN: Replying to "I do not know that any of us know the incident duration of an emergency situation? That's why our expectation is 1 hour."

• Yeah, I think it could be short - just to give first responders time to set up a temp traffic control

• 00:54:43 Josh Schacht - Stantec: Reacted to "I thought you were complimenting yourself for a second there, @Michael Schnuerle (OMF) 😅" with 🤣

• 00:55:36 Fernando Navarrete: As far as Geofencing, and the “over geofencing “ is Waymo communicating with cities where they plan to stand up depots?

• 00:55:39 Henry Silverman(Waymo): Reacted to "One thing to note ..." with 👍

• 00:56:19 Henry Silverman(Waymo): Reacted to "Our FD shared that..." with 👍

• 00:56:52 Christopher Shelley | City of Philadelphia: Reacted to "These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc." with 👀

• 00:57:54 Christopher Shelley | City of Philadelphia: Reacted to "Yes and also thinking about Right of Way Data Specification beyond that." with 🧠

• 00:58:09 Blaine Ebert - Seattle DOT: Does MDS currently support any type of real time integration with Google Maps/Waze?

• 00:58:12 Andrew Glass Hastings: Quick call out to the several OMF Board Members on the call today. The Board provides the leadership and support to make this work possible.

• Viktoriya Wise, SFMTA

• Ramses Madou, San Jose - Board Chair

• Mary Nicol, Chicago

• Anders Waage Nilsen, Bergen, Norway

• Tomas Carranza, LADOT

• We also have other OMF Board Member cities represented:

• Seattle

• Portland

• Minneapolis

• Huge thanks all!

• 00:58:22 Raphael Dumas: Reacted to "Quick call out to the several OMF Board Members on the call today. The Board provides the leadership and support to make this work possible.

• Viktoriya Wise, SFMTA

• Ramses Madou, San Jose - Board Chair

• Mary Nicol, Chicago

• Anders Waage Nilsen, Bergen, Norway

• Tomas Carranza, LADOT

• We also have other OMF Board Member cities represented:

• Seattle

• Portland

• Minneapolis

• Huge thanks all!" with 👏

• 00:58:29 Rachel Castignoli AUSTIN: Reacted to "Quick call out to the several OMF Board Members on the call today. The Board provides the leadership and support to make this work possible.

• Viktoriya Wise, SFMTA

• Ramses Madou, San Jose - Board Chair

• Mary Nicol, Chicago

• Anders Waage Nilsen, Bergen, Norway

• Tomas Carranza, LADOT

• We also have other OMF Board Member cities represented:

• Seattle

• Portland

• Minneapolis

• Huge thanks all!" with 👍

• 00:58:36 Andrew Glass Hastings: Replying to "Does MDS currently s..."

• Yes. Google can ingest the Policy API

• 00:58:44 Jarvis Murray (LADOT): Reacted to "Quick call out to th..." with 👏🏾

• 00:58:44 Blaine Ebert - Seattle DOT: Reacted to "Yes. Google can in..." with 👍

• 00:59:12 Michael Schnuerle (OMF): Replying to "Does MDS currently s..."

• It supports that yes. Somewhere between 70-100 cities are publishing public MDS Policy feeds globally. Google, Waze, Apple can ingest these… but we are not sure if they are yet.

• 00:59:51 Henry Silverman(Waymo): Replying to "These are all poly..."

• Yes specifics about lanes are also very helpful and something we can absolutely ingest. In fact, the more granular the better. If there is a 2-lane road, and only the rightmost lane or curb needs to be avoided, that would be fantastic information for Waymo and other AV companies to have

• 01:00:08 Michael Schnuerle (OMF): Reacted to "I thought you were complimenting yourself for a second there, @Michael Schnuerle (OMF) 😅" with 🤣

• 01:00:13 Michael Schnuerle (OMF): Reacted to "Yes and also thinking about Right of Way Data Specification beyond that." with 🧠

• 01:01:21 Michael Schnuerle (OMF): OMF MDS Policy Collaborative!

• 01:02:40 Blaine Ebert - Seattle DOT: Reacted to "It supports that y..." with 👍

• 01:02:48 Andrew Glass Hastings: A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested.

• 01:03:10 Andrew Glass Hastings: Reacted to "Yes specifics about lanes are also very helpful and something we can absolutely ingest. In fact, the more granular the better. If there is a 2-lane road, and only the rightmost lane or curb needs to be avoided, that would be fantastic information for Waymo and other AV companies to have" with 👍

• 01:03:15 Rachel Castignoli AUSTIN: Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 👍

• 01:03:33 Raphael Dumas: Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 🤔

• 01:03:41 David Von Stroh (Parametrix): Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 👍

• 01:03:42 Victoria Kovacs (City of Redmond, WA): Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 👍

• 01:03:48 Said Abou Kharroub: Reacted to "A lot of exciting ..." with 👍

• 01:03:53 Tom Carranza, LADOT: Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 👍

• 01:04:12 Aylene McCallum: Reacted to "Yes and also thinking about Right of Way Data Specification beyond that." with 🧠

• 01:04:17 Aylene McCallum: Reacted to "I thought you were complimenting yourself for a second there, @Michael Schnuerle (OMF) 😅" with 🤣

• 01:04:36 Aylene McCallum: Replying to "These are all polygon geometries. Do you see any value in having policies tied to specific geoassets? For example, in CDS specific curb zones could be called out. Alternatively, with a broader street digitization, specific travel lanes could be communicated as closed, reversed, etc."

• Stay tuned! We have something cookin' about this!

• 01:04:46 Zackary Campden | LADOT: Reacted to "A lot of exciting wo..." with 👍

• 01:04:47 Aylene McCallum: Reacted to "OMF MDS Policy Collaborative!" with ❤️

• 01:04:53 Aylene McCallum: Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 👍

• 01:05:04 Chava Kronenberg: Nothing from me! Thanks Muyi!

• 01:05:25 Fernando Navarrete: Reacted to "Y'all keep saying "sharing" - is data also being shared from AV companies to cities?" with 👀

• 01:05:32 Ramses Madou |San Jose: This has been fantastic Thank you so much.

• 01:05:48 Christopher Shelley | City of Philadelphia: Reacted to "A lot of exciting work on MDS and CDS into next year - we will be exploring the convergence of these standards and the possible creation of a Right of Way Data Specification (RWDS) that would digitize the rules and regs from building face to building face, covering both the underlying regs and the management of the vehicles on the sidewalk, road, bike lanes, etc. Much more to come on this so please stay connected if you’re interested." with 🥳

• 01:06:06 Aylene McCallum: If you enjoyed this conversation, you'll love the panel discussion we will be hosting at CoMotion LA as part of the OMF Summit track

• 01:06:09 Dan Hubert: Does SF have a digital twin of their curb that is kept up to date?

• 01:06:12 Tom Carranza, LADOT: Agreed, thanks for the great presentations & for the amazing work.

• 01:06:59 Muyi Zhou (SFMTA): Yes we will release our digital curb data later this year.

• 01:07:10 Dan Hubert: Reacted to "Yes we will release our digital curb data later this year." with 👍

• 01:07:12 zipporah maina: Reacted to Yes we will release ... with "👍"

• 01:07:16 Michael Schnuerle (OMF): Replying to "Does SF have a digit..."

• @Muyi Zhou (SFMTA) can answer this, but Yes! They are about to publish a public CDS Curbs data feed, and have new internal systems to keep it all up to date.

• 01:07:26 Andrew Glass Hastings: Check out our latest blog post on this topic covering much of what was discussed today… https://www.openmobilityfoundation.org/mds-emergencies/

• 01:08:23 Aylene McCallum: Cormac, I'll also add that one of the biggest challenges for cities is lack of financial resources to build out these systems and internal technical expertise.

• 01:08:41 RUPAL BAPAT (Chicago): Reacted to "Cormac, I'll also add that one of the biggest challenges for cities is lack of financial resources to build out these systems and internal technical expertise." with 👍

• 01:09:33 Aylene McCallum: The OMF is trying to pull the public and private sectors together to help cities implement these types of systems as well as offering technical assistance programs like the OMF Academy and our Collaborative programs

• 01:10:01 Alia Verloes (Blue Systems): Reacted to "Check out our late..." with ❤️

• 01:10:01 Vignesh Ram (Serve Robotics): +1 to Andrew’s point

• 01:10:09 Vignesh Ram (Serve Robotics): NTD, thank you all!

• 01:10:12 Rick Neubauer: Is waymo using any data standard for the lane data that is needed? or self scanned?

• 01:10:22 Christopher Shelley | City of Philadelphia: Replying to "Cormac, I'll also add that one of the biggest challenges for cities is lack of financial resources to build out these systems and internal technical expertise."

• Plus our internal technical expertise always leaves to go work for the private sector lol

• 01:10:26 Aylene McCallum: OMF Commercial Members (like Blue Systems, Waymo and Passport on the curb side!) help launch these programs.

• 01:10:30 Blaine Ebert - Seattle DOT: City action/funding follow public perception/demand and does not lead it. Until vehicles hit the ground and problems arise the public and thus policy makers do not prioritize investments.

• 01:10:34 Alia Verloes (Blue Systems): Reacted to "OMF Commercials (l..." with ❤️

• 01:10:50 Michael Schnuerle (OMF): Also many cities are not willing to take on the cost until devices are on the ground. For example, we worked on getting ahead of air taxis and drones a few years ago with MDS, but those haven’t really hit cities yet, so they haven’t started building systems for that.

• 01:10:51 Aylene McCallum: So thank you to our 20+ OMF Commercial Members!

• 01:10:57 Rachel Castignoli AUSTIN: AV companies always tell us they don't need any help :)

• 01:11:16 Michael Schnuerle (OMF): Reacted to "City action/funding follow public perception/demand and does not lead it. Until vehicles hit the ground and problems arise the public and thus policy makers do not prioritize investments." with ✅

• 01:11:16 Rachel Castignoli AUSTIN: @Gian-Luca Tellenbach (Vianova) waymo shares pothole data with us

• 01:11:19 Rachel Castignoli AUSTIN: and we fill them

• 01:11:35 Michael Schnuerle (OMF): Reacted to "@Gian-Luca Tellenbach (Vianova) waymo shares pothole data with us" with 👀

• 01:11:51 Andrew Glass Hastings: Reacted to "and we fill them" with 👏

• 01:11:59 Christopher Shelley | City of Philadelphia: Reacted to "Is waymo using any data standard for the lane data that is needed? or self scanned?" with ❤️

• 01:12:22 Christopher Shelley | City of Philadelphia: Reacted to "Yes we will release our digital curb data later this year." with ❤️

• 01:12:23 Aylene McCallum: Reacted to "Also many cities are not willing to take on the cost until devices are on the ground. For example, we worked on getting ahead of air taxis and drones a few years ago with MDS, but those haven’t really hit cities yet, so they haven’t started building systems for that." with 💡

• 01:12:44 Henry Silverman(Waymo): Reacted to "and we fill them" with 👏

• 01:12:56 Aylene McCallum: Reacted to "Plus our internal technical expertise always leaves to go work for the private sector lol" with 💡

• 01:13:05 Aylene McCallum: Reacted to "and we fill them" with 👏

• 01:13:11 Emily Warren (CalSTA): Reacted to "and we fill them" with 👏

• 01:13:17 Emily Warren (CalSTA): Reacted to "@Gian-Luca Tellenbach (Vianova) waymo shares pothole data with us" with 👍

• 01:14:00 Bern Grush, Urban Robotics Foundation: Reacted to "and we fill them" with 👏

• 01:15:25 Jarvis Murray (LADOT): Reacted to "and we fill them" with 👏🏾

• 01:15:53 Rachel Castignoli AUSTIN: Henry if there is a way waymo wants to intake construction zones please share with us.

• 01:16:28 Emily Warren (CalSTA): Caltrans Commercial Wholesale Web Portal Caltrans provides real-time lane closure data; they have a process for having staff in the field log work zones in and out when they are closed/opened and sharing that data on a 5-minute update cycle

• 01:16:49 Emily Warren (CalSTA): They're working to put it in WzDx format

• 01:16:54 Christopher Shelley | City of Philadelphia: If we even get into lane-level data, enforcement and compliance are a major issue. We have permits for one lane and contractors do the construction in a different lane...

• 01:17:23 Michael Schnuerle (OMF): Reacted to "If we even get into lane-level data, enforcement and compliance are a major issue. We have permits for one lane and contractors do the construction in a different lane..." with 😆

• 01:17:50 Michael Schnuerle (OMF): Reacted to "Caltrans Commercial Wholesale Web Portal Caltrans provides real-time lane closure data; they have a process for having staff in the field log work zones in and out when they are closed/opened and sharing that data on a 5-minute update cycle" with 👀

• 01:18:07 Rachel Castignoli AUSTIN: Really the issue is weather and how construction schedules work - typically we monitor our signal cameras to see what's happening with big construction closures

• 01:18:14 Henry Silverman(Waymo): Reacted to "If we even get int..." with 😆

• 01:18:53 Cormac McKay CCAM-RITES: Reacted to Cormac, I'll also ad... with "❤️"

• 01:18:55 Chava Kronenberg: I think it would be great if any of these all-knowing, all-seeing robot machines could help tell us when there is active construction!

• 01:19:00 Rachel Castignoli AUSTIN: Reacted to "Caltrans Commercial Wholesale Web Portal Caltrans provides real-time lane closure data; they have a process for having staff in the field log work zones in and out when they are closed/opened and sharing that data on a 5-minute update cycle" with 👍

• 01:19:07 Rachel Castignoli AUSTIN: Reacted to "I think it would be great if any of these all-knowing, all-seeing robot machines could help tell us when there is active construction!" with 👍

• 01:19:42 RUPAL BAPAT (Chicago): Reacted to "City action/funding follow public perception/demand and does not lead it. Until vehicles hit the ground and problems arise the public and thus policy makers do not prioritize investments." with 👍

• 01:19:51 Chava Kronenberg: Fixing the way our contractors have done work for 100 years seems like a Sisyphian task

• 01:19:57 Cormac McKay CCAM-RITES: Replying to "Cormac, I'll also ad..."

• It's one of the reasons we're providing funding for digital infrastructure as part of a deployment in Horizon Europe CCAM eligible locations

• 01:20:10 Blaine Ebert - Seattle DOT: Reacted to "Fixing the way our..." with 😂

• 01:20:12 Aylene McCallum: Reacted to "It's one of the reasons we're providing funding for digital infrastructure as part of a deployment in Horizon Europe CCAM eligible locations " with ❤️

• 01:20:41 Aylene McCallum: Replying to "Cormac, I'll also add that one of the biggest challenges for cities is lack of financial resources to build out these systems and internal technical expertise."

• Cormac - can you share any additional details or a website about this?

• 01:21:22 Cormac McKay CCAM-RITES: Replying to "Cormac, I'll also ad..."

• https://ec.europa.eu/eusurvey/runner/da22418f-897e-86fe-91e2-3808b99a6420

• 01:21:30 Aylene McCallum: Replying to "Cormac, I'll also add that one of the biggest challenges for cities is lack of financial resources to build out these systems and internal technical expertise."

• Thank you!

• 01:21:47 Cormac McKay CCAM-RITES: Replying to "Cormac, I'll also ad..."

• Feel free to reach out on LinkedIn

• 01:21:54 Aylene McCallum: Reacted to "Feel free to reach out on LinkedIn " with 👍🏻

• 01:22:28 Gian-Luca Tellenbach (Vianova): Reacted to "@Gian-Luca Tellenbach (Vianova) waymo shares pothole data with us" with 👍

• 01:22:31 Aylene McCallum: Thank you Henry! And thank you Waymo!

• 01:23:07 Rachel Castignoli AUSTIN: What happens in California helps all the cities in the US!

• 01:23:16 Aylene McCallum: The OMF loves bringing the public and private sectors together :)

• 01:23:31 Aylene McCallum: Thank you Vlad!

• 01:23:53 Emily Warren (CalSTA): Reacted to "What happens in California helps all the cities in the US!" with ❤️

• 01:23:59 Aylene McCallum: Reacted to "What happens in California helps all the cities in the US!" with ❤️

• 01:24:03 Emily Warren (CalSTA): Thank you!

WEBVTT

1 00:00:03.630 --> 00:00:10.560 Michael Schnuerle (OMF): Alright, hello everyone, my name is Michael Schnerle. I'm the Director of Open Source Operations for the Open Mobility Foundation.

2 00:00:10.870 --> 00:00:19.220 Michael Schnuerle (OMF): This is our monthly public working group meeting for the MDS Working Group, and today we're going to be talking about

3 00:00:19.460 --> 00:00:25.720 Michael Schnuerle (OMF): real-time data standards, and specifically how Waymo's using them in their operations.

4 00:00:26.570 --> 00:00:41.709 Michael Schnuerle (OMF): Go ahead and set your name and your organization in the participant list, so go over there, and at the top of the list is your name, hit the three dots, add your organization afterwards, so we know who you're representing, whether it's a city or a company.

5 00:00:41.810 --> 00:00:47.259 Michael Schnuerle (OMF): Or an operator, that really helps with note-taking later, and to know who you're representing.

6 00:00:47.340 --> 00:01:01.079 Michael Schnuerle (OMF): Mute yourself for now, but feel free to introduce yourself in the chat, so whether it's your first time, or you've been coming every month, just… you can say your name, who you are, why you're here, you can provide a link if you want.

7 00:01:01.080 --> 00:01:19.860 Michael Schnuerle (OMF): anything to let people get to know you. Use the chat to leave questions as we go today. If you have something really urgent to say, you can use the raise hand feature, but we do… we are planning to have a good chunk of time at the end for a Q&A, a live Q&A, and

8 00:01:19.990 --> 00:01:34.080 Michael Schnuerle (OMF): open… open questions. So, this meeting is being recorded and will be published with notes to the same working group page, where the agenda was. And if you're on the mailing list, you'll get that information.

9 00:01:34.830 --> 00:01:40.689 Michael Schnuerle (OMF): So today, I want to do some announcements, and then give a quick overview of

10 00:01:40.860 --> 00:01:45.349 Michael Schnuerle (OMF): how MDS can be used for real-time digital policy.

11 00:01:45.770 --> 00:01:56.610 Michael Schnuerle (OMF): We're gonna have one example of how Seattle is using it for their, emergency response and autonomous vehicles.

12 00:01:56.750 --> 00:02:10.949 Michael Schnuerle (OMF): So that'll be a quick thing, a topic of what we're doing now. And then, Waymo will have the majority of the time to talk about how they are planning or using real-time planning to use their

13 00:02:10.949 --> 00:02:18.939 Michael Schnuerle (OMF): are currently using real-time data standards, and then a little bit about some future use cases that are coming up, and open Q&A at the end.

14 00:02:20.870 --> 00:02:31.320 Michael Schnuerle (OMF): Alright, so a little bit about the Open Mobility Foundation, maybe for those of you who are new, we're a global nonprofit created in 2019 to support cities and industry collectively.

15 00:02:31.490 --> 00:02:40.680 Michael Schnuerle (OMF): City-led and founded, but with support from the private sector. We help cities and companies get to yes together and work together to solve solutions.

16 00:02:40.930 --> 00:03:02.479 Michael Schnuerle (OMF): Everything we do is built in the open, free to use, open source. We put everything on GitHub. A lot of public participation over the years from at least 1,400 individuals in 500 different cities and companies, and that has created a nice competitive market and solutions and ecosystem.

17 00:03:02.480 --> 00:03:09.099 Michael Schnuerle (OMF): For everyone you see here, the local government, curb users, operators in the street, tech and service vendors.

18 00:03:10.830 --> 00:03:33.810 Michael Schnuerle (OMF): Mobility data specification is a data standard that enables right-of-way, public space, management and regulation, digital policy, geofencing, two-way digital communication, and the steering committee you see on the right is made up of current OMF members who are working to do things like set the agendas for these meetings and approve releases.

19 00:03:33.810 --> 00:03:44.980 Michael Schnuerle (OMF): after it comes out of these public meetings and from GitHub. So, thanks to our volunteers here who are on the steering committee, and I'll point out, relevant today, Henry Silverman from Waymo.

20 00:03:44.980 --> 00:03:47.259 Michael Schnuerle (OMF): It's on there, so thank you for that.

21 00:03:48.070 --> 00:04:00.810 Michael Schnuerle (OMF): MDS is global. We know of over 200 commercial mobility service providers that send MDS data to cities, and some percentage of those receive it from cities as well, which is what we're talking about today.

22 00:04:00.810 --> 00:04:15.470 Michael Schnuerle (OMF): These companies operate in over 1,200 cities in dozens of countries around the world, and at least a couple billion trips taken have been sent in MDS. You can see North America is lit up here with where MDS is being used, but

23 00:04:15.470 --> 00:04:17.570 Michael Schnuerle (OMF): actually more use in Europe.

24 00:04:17.680 --> 00:04:21.080 Michael Schnuerle (OMF): If you count total number of jurisdictions.

25 00:04:22.820 --> 00:04:40.219 Michael Schnuerle (OMF): MDS 2.1 was just released. This expanded our modes and scope of what MDS could be used for, so it started with micromobility, but now it can support all different types of passenger services, taxis, AV, ridehail, which we'll be talking about today.

26 00:04:40.220 --> 00:04:42.910 Michael Schnuerle (OMF): Buses, TNCs, etc.

27 00:04:42.920 --> 00:04:55.590 Michael Schnuerle (OMF): Also, fleet vehicles, or car share, city fleets, things like that. And then delivery of all types, whether that's sidewalk robots, app delivery, package delivery, freight, goods, food, etc.

28 00:04:55.650 --> 00:05:09.610 Michael Schnuerle (OMF): All of that is supported in MDS, and I'll talk about MDS a little bit when we get into that part. For 2.1, we have a ton of resources that are available for everyone to get familiar with it. These are all

29 00:05:09.680 --> 00:05:16.620 Michael Schnuerle (OMF): On our blog post about this, and then also online in multiple places, so, lots of…

30 00:05:16.800 --> 00:05:41.310 Michael Schnuerle (OMF): Lots of possibilities for you to understand how to use MDS 2.0. And then, real quick, we also have another data standard, CDS, which is a curb data specification. It works in conjunction with MDS, so MDS manages vehicle locations, status, incidents, and trips, and CDS manages physical infrastructure, objects there, and activity tracking of those vehicles

31 00:05:41.340 --> 00:05:49.009 Michael Schnuerle (OMF): At those locations or at those objects, and they could be used independently or cooperatively.

32 00:05:51.270 --> 00:06:00.110 Michael Schnuerle (OMF): I'd like to thank our premier public… our private sector members. We have a lot of public sector members. It's free if you're a public sector member to join.

33 00:06:00.280 --> 00:06:13.989 Michael Schnuerle (OMF): For the private sector, they pay to join, which we appreciate and keeps everything going, everything that we do going. Thanks to our Premier members, you can see them here, and thanks to our associate… associate members, which you can see here.

34 00:06:14.060 --> 00:06:23.760 Michael Schnuerle (OMF): Thanks for all of your support of the OMF, and I'll call out Waymo again, because they're presenting today, but they've been a long-time supporter of the OMF.

35 00:06:25.700 --> 00:06:37.600 Michael Schnuerle (OMF): Upcoming OMF Academy sessions, if you are an OMF member, you have access to our OMF Academy for you and your staff and any colleagues that work in your city or your company.

36 00:06:37.660 --> 00:06:54.780 Michael Schnuerle (OMF): We just had one in August for CDS 101, we'll have it again in October, MDS 101 is also coming up, and then Digital Infrastructure 101. So, you should have gotten some emails about that, but if you haven't, let us know, and we can make sure you have access to how to sign up for those courses.

37 00:06:56.220 --> 00:07:13.709 Michael Schnuerle (OMF): We have an OMF calendar, which is everything we're doing, whether it's meetings like this one, or board meetings for members, or different webinars, or physical conferences that we're at. You can subscribe to this Google Calendar.

38 00:07:13.710 --> 00:07:18.100 Michael Schnuerle (OMF): Or, look at it visually. I'll put it in the chat right now.

39 00:07:20.150 --> 00:07:21.450 Michael Schnuerle (OMF): There you go.

40 00:07:21.650 --> 00:07:26.229 Michael Schnuerle (OMF): It's a good way to keep up. And then where will the OMF be through 2026?

41 00:07:26.330 --> 00:07:43.330 Michael Schnuerle (OMF): Well, we had two events in September, including a relevant USDOT automated vehicle peer exchange in San Francisco, Mobility Mixer in Denver, and then we've got a member meeting coming up, and OMF Academy sessions, but also we'll be working with the City of Amsterdam.

42 00:07:43.330 --> 00:08:01.920 Michael Schnuerle (OMF): to understand how they can put their crash data from operators into the MDS APIs, be at Tomorrow Mobility in Barcelona, our OMF Summit with Comotian in Los Angeles, and then Polis, which is, like, the European NACDO in Brussels in December.

43 00:08:03.610 --> 00:08:16.700 Michael Schnuerle (OMF): All right, so that's… that's a lot of announcements, but I wanted to make sure everyone was up to speed, and a lot of these resources are on our website. So, I'm going to give a pretty quick overview of MDS real-time policy.

44 00:08:16.920 --> 00:08:24.909 Michael Schnuerle (OMF): If you want more information about this, reach out to us or to me, and we can give you some one-on-one information.

45 00:08:25.060 --> 00:08:39.829 Michael Schnuerle (OMF): This won't be a deep dive, or at least, let's say it won't be a high level. It'll be pretty quick and pretty to the point, so if you're not familiar with it, you might be a little bit lost, but if you are at least a little bit familiar, hopefully you get a refresher.

46 00:08:41.110 --> 00:08:50.629 Michael Schnuerle (OMF): So, MDS can provide data to cities. These… we have these sets of APIs called provider and agency, which just means, whether it's a

47 00:08:50.720 --> 00:08:57.410 Michael Schnuerle (OMF): Pushing data, from the operators to the cities, or the city is pulling

48 00:08:57.480 --> 00:08:59.969 Michael Schnuerle (OMF): Data from them, one or the other.

49 00:08:59.990 --> 00:09:17.579 Michael Schnuerle (OMF): But it's things like vehicle location and status, before or after a reservation is made, real-time and historic. Vehicle information, like propulsion types, different vehicle attributes, accessibility, fuel types and capacity. Trip details, so…

50 00:09:17.580 --> 00:09:21.239 Michael Schnuerle (OMF): Trip, distance, duration, fares cost, maybe the payload.

51 00:09:21.260 --> 00:09:33.770 Michael Schnuerle (OMF): A lot of these are optional fields. Incidents, this is new for 2.1. Things like crashes, ADS disengagements, near misses, obstructions, violations, theft, vandalism, or harsh braking.

52 00:09:33.830 --> 00:09:38.070 Michael Schnuerle (OMF): All of those are, possible to…

53 00:09:38.850 --> 00:09:49.759 Michael Schnuerle (OMF): to get from the operators, and then trip breadcrumbs, and after the trips are complete, and stop details. So, a lot of different information can come from the operators.

54 00:09:50.580 --> 00:10:03.219 Michael Schnuerle (OMF): But also, relevant to today, much data can come from the cities, or whatever jurisdiction it is, to the operators operating in the cities. So, there's two sources of that information. One is

55 00:10:03.320 --> 00:10:10.579 Michael Schnuerle (OMF): permit policies and data sharing rules, so maybe an operator has to abide by some permit, or

56 00:10:10.990 --> 00:10:21.389 Michael Schnuerle (OMF): contract, those… those can actually be digitized, the data sharing requirements, and be put into MDS, so it's really clear what data you are asking for and

57 00:10:21.490 --> 00:10:25.060 Michael Schnuerle (OMF): What you really need for the program, and what you don't need.

58 00:10:25.290 --> 00:10:40.469 Michael Schnuerle (OMF): So it's not just a fuzzy paragraph. And then, for today, you can also digitize any sort of geofencing, emergency information, event rules, or information.

59 00:10:40.470 --> 00:10:53.129 Michael Schnuerle (OMF): via MDS digital policy. And so, one thing that happened with 2.1 is before 2.1, we did have real-time digital policy publishing from cities. It was a…

60 00:10:53.130 --> 00:11:10.309 Michael Schnuerle (OMF): GET API where the operators had to check on the city's feeds and see when it got updated and do it on a regular basis. Sort of like a book that they could look and see what the rules were. The main limitation is that the near real time was, like, dependent on how frequently they could check it.

61 00:11:10.400 --> 00:11:11.939 Michael Schnuerle (OMF): But with 2.1,

62 00:11:12.200 --> 00:11:26.780 Michael Schnuerle (OMF): MDS is both a get and a push, which means it's more like a notification on your phone, so the operator gets a notification that something has changed, they get the notification of what has been changed, but they could still go check that book to see everything.

63 00:11:26.780 --> 00:11:40.630 Michael Schnuerle (OMF): available at all times. And this push notification system is really what allows for actual real-time MDS policy communication, down to the second if the systems can allow it. So.

64 00:11:40.720 --> 00:11:44.329 Michael Schnuerle (OMF): Some of that we'll talk about today.

65 00:11:44.380 --> 00:12:01.080 Michael Schnuerle (OMF): And just to give you a sense of what is possible with MDS policy, basically it's a way for an agency to communicate rules, incentives, notices, events, either real or historic or in the future, so upcoming things as well, and it could be communicated

66 00:12:01.330 --> 00:12:16.230 Michael Schnuerle (OMF): per mode, so maybe there's some restrictions or information about, bikes and scooters for some area of your city for some event. Like, maybe they're allowed, or maybe they're preferred parking areas for those modes.

67 00:12:16.230 --> 00:12:21.360 Michael Schnuerle (OMF): Or specific operators, and then maybe for autonomous vehicles or car share.

68 00:12:21.360 --> 00:12:44.440 Michael Schnuerle (OMF): There's different rules, and those can be specified. Everything from operating area to vehicle caps, exclusion zones, speed limits, idle time restrictions, parking, preferred or designated areas, trip fees and subsidies, real-time emergency notifications, which we'll talk about today, and large event policy rules. All of that's possible in MDS policy.

69 00:12:46.970 --> 00:12:56.809 Michael Schnuerle (OMF): Alright, so let's get into, an example before we kick it over to Waymo, and this is an example from Seattle, and,

70 00:12:56.970 --> 00:13:11.890 Michael Schnuerle (OMF): Let me see if… Pierre from Blue Systems. So, Blue Systems helped work on this with Seattle, and they provided some slides. Pierre, would you like to present on these? Maybe, like, a minute per slide, or would you like me to present on them?

71 00:13:12.190 --> 00:13:17.689 Pierre Bouffort (Blue Systems): Oh, I'm happy to go, Michael. Do you have the slides? Perfect. Awesome.

72 00:13:18.990 --> 00:13:21.870 Pierre Bouffort (Blue Systems): Great, great synchronicity here.

73 00:13:21.960 --> 00:13:32.479 Pierre Bouffort (Blue Systems): Alright, so, hi everyone, so my name is Pierre Bouffort, I'm head of product at Blue Systems. I have been working in this

74 00:13:32.480 --> 00:13:50.509 Pierre Bouffort (Blue Systems): industry and with the OMF for the past, 5 plus years, closing in on 6 now. And yeah, so we at Blue Systems have been, you know, working with Seattle on the project we fondly call, DCAMP, for digital communication, digital…

75 00:13:51.330 --> 00:13:58.580 Pierre Bouffort (Blue Systems): Damn, I should have went over this, gone over this again before, digital,

76 00:13:58.580 --> 00:13:59.730 Michael Schnuerle (OMF): No light on the color.

77 00:13:59.730 --> 00:14:06.259 Pierre Bouffort (Blue Systems): And then it's… it's digital, and then it's awareness, project. Well, essentially…

78 00:14:06.260 --> 00:14:06.770 Michael Schnuerle (OMF): the mall.

79 00:14:06.770 --> 00:14:07.390 Pierre Bouffort (Blue Systems): Yeah.

80 00:14:07.390 --> 00:14:08.590 Michael Schnuerle (OMF): project, yeah.

81 00:14:08.590 --> 00:14:09.990 Pierre Bouffort (Blue Systems): Yeah, exactly.

82 00:14:09.990 --> 00:14:33.250 Pierre Bouffort (Blue Systems): And so basically what this does is, as Michael very clearly explained, the possibility to share, data in real time through Policy API to robotaxi operators and create a pilot for this in the City of Seattle. So, the goal there was really to leverage, the possibilities of MDS, right, to create

83 00:14:33.330 --> 00:14:39.580 Pierre Bouffort (Blue Systems): A collaborative, data-sharing environment, so really, like, paving the way to,

84 00:14:39.580 --> 00:15:01.660 Pierre Bouffort (Blue Systems): leaner, real-time communication of emergencies and events, and anything that is relevant to the operations of those robotaxis from the city to these robotaxi operators in real time and as clearly as can be, and really using the standards that are already existing, like MDS and CDS, to

85 00:15:01.660 --> 00:15:23.239 Pierre Bouffort (Blue Systems): pave the way, essentially, for a more complete data integration in the future, should, you know, cities, operators, legislation, governments, whatever, decide to go in this direction. We are using and leveraging standards to achieve that at a much lower operational cost for everybody in the future.

86 00:15:23.250 --> 00:15:28.240 Pierre Bouffort (Blue Systems): Should that happen. So, basically, we have two examples of that.

87 00:15:28.360 --> 00:15:44.439 Pierre Bouffort (Blue Systems): Sorry. Two examples of that. So, the first one is the one we did with LADOT and Waymo. And so, in LADOT… with LADOT in Los Angeles, essentially what we did was use MDS Policy API to send geofences

88 00:15:44.440 --> 00:15:51.819 Pierre Bouffort (Blue Systems): to AV fleets, in this case, Waymo. So basically, what that looked like is for the LADOT folks

89 00:15:51.820 --> 00:16:04.099 Pierre Bouffort (Blue Systems): They would log on to, Blue Systems' platform, which they already had access to, and whenever there was any kind of, event, you know, like, say.

90 00:16:04.100 --> 00:16:28.859 Pierre Bouffort (Blue Systems): FIFA World Cup event, watch party, but also, you know, Pride March, Farmers Market, anything of the sort, right? Where, Ciclavia events in LA. We were able to create the geofences in the platform, and then have them sent, to the Waymo systems and backend.

91 00:16:28.860 --> 00:16:43.949 Pierre Bouffort (Blue Systems): without any, need for, like, a human putting together some kind of PDF document saying, okay, do not go north of 46th Street and south of blah blah blah, and, you know, and removing that kind of tedious, work. And then.

92 00:16:44.170 --> 00:16:57.390 Pierre Bouffort (Blue Systems): the next project here is the 911 dispatch integration. So once we had that building block of being able to send MDS policies to robotaxi operators, then the next step was to

93 00:16:57.390 --> 00:17:05.690 Pierre Bouffort (Blue Systems): not only have the possibility to manually input events as a source of geofences, so for, like I said.

94 00:17:05.690 --> 00:17:30.129 Pierre Bouffort (Blue Systems): you know, FIFA watch parties, and farmers market, but to have, on top of that, the possibility to have automated integration of real-time data sources, and in this case, 911 dispatches was the decision with Seattle. And so, basically what this means, and I think this is going to be on the next slide here, Michael.

95 00:17:30.630 --> 00:17:46.350 Pierre Bouffort (Blue Systems): That we're touching this, yes, exactly. So, what this means is, the system was able to, integrate with, first responders, emergency dispatch system, so we would know where, you know, appeared.

96 00:17:46.350 --> 00:17:56.869 Pierre Bouffort (Blue Systems): First responders are being dispatched. We know where they're going, we know what type of emergency they're going to respond to, we know the type of apparatus that is being dispatched.

97 00:17:56.870 --> 00:18:10.789 Pierre Bouffort (Blue Systems): We know the severity, we know the number of vehicles that are going, so we have a bunch of information about that dispatch. And we get that in real time, thanks to the collaboration with, Seattle Fire Department, the SFD.

98 00:18:10.790 --> 00:18:27.419 Pierre Bouffort (Blue Systems): So from there, this feeds into our system, and it has a small translation engine, if you will, that is configurable entirely by the city agency. So, in this case, again, the DOT, so Seattle DOT and Seattle Fire Department working together on this.

99 00:18:27.420 --> 00:18:51.520 Pierre Bouffort (Blue Systems): to configure it and say, okay, if it's a massive fire hazard that has 5, you know, vehicles dispatched, high severity, maybe we say we don't wanna… we wanna let the, robotaxi operators that maybe they shouldn't get too close to this in a radius of, say, 100 meters, a quarter mile, 2 meters, whatever, you know, this is configurable entirely based on the geography of your city.

100 00:18:51.520 --> 00:19:02.100 Pierre Bouffort (Blue Systems): So that, you can let the operators know that you are… you have an indication out there for them through that policy API that you recommend not going closer

101 00:19:02.100 --> 00:19:08.050 Pierre Bouffort (Blue Systems): Then… or entering this geofenced area of a few streets of a given radius, or whatnot.

102 00:19:08.050 --> 00:19:26.980 Pierre Bouffort (Blue Systems): But also, the system is configurable in a way that allows you to say, well, if it's only a cat stuck in the tree, I mean, I know, you know, this is not a realistic scenario, but you get the gist of it. If it's a cat stuck in the tree, maybe let's not bother them too much, right? And then the entire spectrum between those two possibilities is

103 00:19:26.980 --> 00:19:28.659 Pierre Bouffort (Blue Systems): is, is…

104 00:19:28.660 --> 00:19:53.570 Pierre Bouffort (Blue Systems): is configurable on the platform, so that if it's a cat stuck in the tree, you don't bother your operators with that. If it's a massive fire hazard, you tell them to stay away. And if it's, you know, like a medic response that is… doesn't look too severe, but it's only, you know, in one street where you know it's a critical area of your city, you might want to just tell them, hey, slow down, go into a safer driving mode, whatever this may mean for the

105 00:19:53.570 --> 00:19:58.819 Pierre Bouffort (Blue Systems): Robotaxi operators to just be sure that there is no problem happening on those streets.

106 00:19:59.090 --> 00:20:10.530 Pierre Bouffort (Blue Systems): And all of that, thanks to the policy API, then gets, you know, published out to the AV operational systems for them to integrate.

107 00:20:11.090 --> 00:20:32.680 Pierre Bouffort (Blue Systems): And yeah, just maybe a couple thoughts on that previous slide before we go, and I think we can skip this one, because I kind of explained the whole thing already. The thing that's important to mention here is that this system that we've built, through the DCAM project with Seattle is entirely replicable and extensible. So what this means, practically speaking, is that

108 00:20:32.680 --> 00:20:42.609 Pierre Bouffort (Blue Systems): thanks to the fact that we leveraged MDS as the data standard to do this, it is a much lower cost project to implement in a new city.

109 00:20:42.610 --> 00:20:51.010 Pierre Bouffort (Blue Systems): For, you know, both the operators and for the cities, because we have the experience of doing this through MDS,

110 00:20:51.010 --> 00:21:00.830 Pierre Bouffort (Blue Systems): with Seattle and with LA. I mean, not in real time with LA, but you heard my previous example with LA, so that we can basically say.

111 00:21:00.830 --> 00:21:08.719 Pierre Bouffort (Blue Systems): you can replicate this at a lower cost, A, and B, MDS, as Michael was mentioning, is also

112 00:21:08.720 --> 00:21:25.039 Pierre Bouffort (Blue Systems): you know, open to a lot more modes, right? Right now, we're talking about robo-taxis, and I'll hand it over shortly to our friends at Waymo. Obviously, robotaxis are, like, top of mind in, you know, the recent, in the past few months.

113 00:21:25.040 --> 00:21:34.409 Pierre Bouffort (Blue Systems): But if you think ahead and want to have some kind of vision on the long run for your city, you can definitely think about how you can use this system for many, many more modes.

114 00:21:34.410 --> 00:21:59.389 Pierre Bouffort (Blue Systems): and how it can interconnect both with more data sources. So, like, 911 dispatch is one of them, but you could think weather events, you could think construction zone permits, you could think traffic information, you could think, you know, all kinds of sources of data could be translated and then published out to more and more modes. So, again, we just started with robo-taxis, but you could do that with your micromobility, with your TNC, with your delivery environment, potentially.

115 00:21:59.390 --> 00:22:01.279 Pierre Bouffort (Blue Systems): Even on the long run, look at, like.

116 00:22:01.280 --> 00:22:08.049 Pierre Bouffort (Blue Systems): driver routing apps, you know? So, it's really a first base.

117 00:22:08.250 --> 00:22:15.389 Pierre Bouffort (Blue Systems): That you can then build upon regarding the, like… you can build upon,

118 00:22:15.500 --> 00:22:28.370 Pierre Bouffort (Blue Systems): for the needs of your… the specific needs of your city. But we… we… yeah, I guess we'll talk more about this in Q&A. I think the next slide is not necessarily that relevant for today. I'll keep it at that. I'm happy to…

119 00:22:28.370 --> 00:22:39.979 Pierre Bouffort (Blue Systems): turn over to maybe a demo later on, but I do want to give room enough for Waymo and the Q&A, so I'll leave it at that for now, and I'm happy to take questions over in the chat or at the Q&A session.

120 00:22:42.030 --> 00:23:00.609 Michael Schnuerle (OMF): All right, thank you, Pierre. That's great. Great work in Seattle, replicable in other cities. Other cities are looking at this. Pierre, I know you've presented on this before at a working group meeting. I'm sure there's a recording out there. Whoever, you or I could find it and put it in the chat if people want to see your demo, too.

121 00:23:00.610 --> 00:23:01.430 Pierre Bouffort (Blue Systems): Absolutely.

122 00:23:01.940 --> 00:23:15.670 Michael Schnuerle (OMF): All right, so now that… that's a lot of, what… what… how it is… how it works, what it is, and what's been going on so far, and now we'll kick it over to Henry to talk about real-time data standards, with Waymo. I'll stop sharing.

123 00:23:17.490 --> 00:23:17.990 Michael Schnuerle (OMF): There you go.

124 00:23:17.990 --> 00:23:21.979 Henry Silverman(Waymo): Let me try to take over. Give me a second…

125 00:23:24.340 --> 00:23:28.030 Henry Silverman(Waymo): Everyone see my screen? Looks like they can. Yeah.

126 00:23:28.250 --> 00:23:47.819 Henry Silverman(Waymo): Great. First off, hi everyone. I want to introduce myself. My name's Henry, I'm a product manager at Waymo, focused on event response and some of our tooling that we have, and I want to talk about standardizing municipal alerts for autonomous fleets. This isn't just for Waymo, I imagine

127 00:23:47.820 --> 00:23:57.829 Henry Silverman(Waymo): all autonomous fleets, would be interested in this sort of thing. And, essentially, what the thing I want to convey is all the things Michael has already conveyed, is

128 00:23:57.830 --> 00:24:10.810 Henry Silverman(Waymo): why autonomous vehicle operators, would prefer consistent APIs, generally structured event schemas, structured data, and real-time city integration, specifically for municipal alerts.

129 00:24:11.520 --> 00:24:17.150 Henry Silverman(Waymo): So, I don't think, everyone can see my screen, yes? Everyone's… Yes.

130 00:24:17.150 --> 00:24:18.820 Michael Schnuerle (OMF): Yeah, we can see one slide, yep.

131 00:24:19.000 --> 00:24:33.600 Henry Silverman(Waymo): Great. I don't think I need to convince this audience of this, but essentially, like, just to set the groundwork for why this is important, we want to have continuous, 24-7 metro operations at scale.

132 00:24:33.760 --> 00:24:48.979 Henry Silverman(Waymo): Waymo operates a commercial ride-hailing, across major U.S. markets, with global expansion soon. Some of you might have seen this. We are going to multiple, areas in Asia and Europe, and others, upcoming.

133 00:24:49.160 --> 00:25:03.109 Henry Silverman(Waymo): We, also want to have emergency management coordination. We already have coordination with emergency management, but, you know, generally speaking, we want our vehicles to

134 00:25:03.110 --> 00:25:14.990 Henry Silverman(Waymo): Avoid, areas that really, pose a public safety hazard if the vehicles are there, or to clear the way for emergency corridors for emergency vehicles.

135 00:25:14.990 --> 00:25:28.590 Henry Silverman(Waymo): So, these can be fires, crime scenes, hazardous areas that essentially pose a heightened risk to passengers. That being said, you can imagine there are many of these where the vehicle or anything else can drive through

136 00:25:28.610 --> 00:25:47.339 Henry Silverman(Waymo): totally okay, so making that distinction of what's just an area where something's going on, maybe on the sides of the curb where driving is still allowed, as opposed to just, no, we really want to avoid this area. I think there's nuance there, some of that is hard, but that's generally, I think, the end goal, here.

137 00:25:47.340 --> 00:25:57.969 Henry Silverman(Waymo): And then just the need for machine-to-machine feeds, you know, manual communication, as I don't think I need to explain to the folks here, can't keep pace with

138 00:25:57.970 --> 00:26:15.749 Henry Silverman(Waymo): fleet density, scale, all the different municipalities we're going to. We want this to be low latency. We want these pipelines to be very quick, you know, very structured, because we want to be responsive to routing our vehicles for the sake of public safety.

139 00:26:16.300 --> 00:26:20.090 Henry Silverman(Waymo): I think that's all pretty self-explanatory, but it's nice to ground us there.

140 00:26:21.370 --> 00:26:35.369 Henry Silverman(Waymo): And then I sort of just want to go through, because I think this is, you know, there are some municipalities that, use MDS, others that don't, and there's somewhat of a fragmented landscape of emergency alert inbound.

141 00:26:35.370 --> 00:26:52.000 Henry Silverman(Waymo): So, you know, I have some examples here, but essentially, different municipalities can provide different levels of information. It's structured in different ways if it's not using MDS. Some are, but if they aren't, this is one of the issues. So.

142 00:26:52.110 --> 00:27:00.209 Henry Silverman(Waymo): Some provide, so if we look at Phoenix, we have raw incident text, and then there's a Google Map.

143 00:27:00.280 --> 00:27:10.840 Henry Silverman(Waymo): link that's added, to this location. There's also a, raw text of, in this case, it's a house fire, right, in this location.

144 00:27:10.900 --> 00:27:24.720 Henry Silverman(Waymo): Right, other, areas might just say… might not provide as much context as to what is actually going on, right? And they will, again, provide cross streets, or addresses, or sometimes just a point of interest.

145 00:27:24.820 --> 00:27:43.789 Henry Silverman(Waymo): And other municipalities will provide a radius, right? What is the area to avoid? How big of an area ought we avoid? and place a geofence. Others don't. Others just say, like, here's a pin, and what does it mean to avoid that area? It's sometimes a bit unclear.

146 00:27:44.130 --> 00:27:59.359 Henry Silverman(Waymo): others, so some provide, you know, addresses, others go directly in latitude and longitude and say, hey, here's the latitude and longitude, we want you to avoid. And how that latitude and longitude is conveyed is also something that's not consistent.

147 00:27:59.360 --> 00:28:15.230 Henry Silverman(Waymo): And then there are different pathways to ingest this information. Sometimes we work with third-party services, sometimes we ingest it directly, sometimes there's MDS, and other times, you know, there are municipalities that might just post all of this, online.

148 00:28:15.290 --> 00:28:34.239 Henry Silverman(Waymo): Right, and tables, and so we need to accommodate those sorts of situations. And, you know, there are hybrids here, where some will align and send an email as well, but, like, in general, what I'm trying to convey is that as we expand, these are some of the challenges that, Waymo

149 00:28:34.240 --> 00:28:39.920 Henry Silverman(Waymo): And I imagine other fleet operators are dealing with is, like, how can we essentially take all of this

150 00:28:39.920 --> 00:28:44.970 Henry Silverman(Waymo): Right? And convert it into a consistent pipeline, a consistent method.

151 00:28:44.990 --> 00:28:48.379 Henry Silverman(Waymo): Of actually placing, geofence, areas.

152 00:28:48.950 --> 00:28:57.050 Henry Silverman(Waymo): And then there's also international markets that I won't even go into, but that place… that has its own challenges, as everyone can imagine.

153 00:28:57.290 --> 00:29:06.160 Henry Silverman(Waymo): My sister lives in Berlin, and there are all sorts of issues of just shipping packages to Berlin, so there are challenges abound.

154 00:29:06.270 --> 00:29:29.740 Henry Silverman(Waymo): So, from a fleet and operational response, I want to also convey some of the things that we can do, because we essentially say geofence, and this is a term that is often just used, and I want to talk about what that actually means, and what the different, responses, that Waymo, and I imagine other fleet operators.

155 00:29:29.770 --> 00:29:35.169 Henry Silverman(Waymo): might have as well. And where this is as important is, I think, what Michael is describing. It's…

156 00:29:35.170 --> 00:29:52.919 Henry Silverman(Waymo): You know, you can just share information about what's going on, but then there's also an opportunity of, and we want this action, or we believe this action is appropriate, or it's possible that some severity is conveyed, or there's a taxonomy, and based on that taxonomy, a certain set of actions can be taken.

157 00:29:52.920 --> 00:30:09.590 Henry Silverman(Waymo): And so, to that end, we can direct vehicles to do different things, right? So, in an area, you can say, hey… and this one's actually rather extreme, we don't do this very often, because it poses its own, risk, but you can say, whoa, stop driving immediately.

158 00:30:09.590 --> 00:30:28.209 Henry Silverman(Waymo): park. It's usually a better situation to actually, like, say, hey, avoid this area, try to get out soon, or as soon as possible, or soonish, but there are certain situations where driving any bit, right, would be dangerous. So you can imagine a sinkhole opened up, right? Now, obviously, Waymo has

159 00:30:28.210 --> 00:30:45.310 Henry Silverman(Waymo): You know, we build a full perception stack to try to account for many of these situations, but still, as all of you know, Waymo's a big fan of redundancy. We have a very complicated technological stack across many sensors, so redundancy is very important to us.

160 00:30:45.350 --> 00:30:49.549 Henry Silverman(Waymo): So that's one of the, things that we can do.

161 00:30:49.550 --> 00:31:01.469 Henry Silverman(Waymo): Right? Drain out, is another one that I talked about, right? Leave this area. And again, there's optionality here, right? It can be, you know, drain out immediately if someone's on a trip.

162 00:31:01.470 --> 00:31:16.269 Henry Silverman(Waymo): you know, we don't care, like, just, like, cancel, don't drop off there, right? There are others where, hey, we want you to avoid this area, you can finish what you're doing, but generally we want to keep this area clear. And you can imagine different situations, you know, require those different actions.

163 00:31:16.270 --> 00:31:29.050 Henry Silverman(Waymo): overlapped on all of these, you can say, stay out, right? Essentially, like, avoid this area, at all costs, right? And there are various… there, again, I'm not going to go into the details, there are various nuances to all of these.

164 00:31:29.060 --> 00:31:43.449 Henry Silverman(Waymo): that Wayne will work through. Curb freeze, as I think someone just mentioned, right? Through traffic can flow completely normally, but pickups and drop-offs are frozen. You know, a canonical use case would be a sidewalk protest.

165 00:31:43.460 --> 00:31:58.179 Henry Silverman(Waymo): Right? Where, you know, the streets are operating normally. Again, some police responses also happen along the sidewalks, and so how much you actually need to avoid that area, you know, I think some of this is debatable.

166 00:31:58.260 --> 00:32:11.189 Henry Silverman(Waymo): right? And so, I say this, you know, just to say, like, all the different things that can be possible, as opposed to just, like, one black blanket term and just say geofence. The last one I'll say is, you can limit vehicles, right?

167 00:32:11.220 --> 00:32:18.329 Henry Silverman(Waymo): You get… this isn't a black or white, like, either stay in or stay out, or drain out, or anything like that. You can say, like, hey.

168 00:32:18.330 --> 00:32:32.219 Henry Silverman(Waymo): Normally, we allow whatever the throughput is in this area. Here, we use the term penalties internally, but you can essentially, right, or, like, put restrictions on how many vehicles can go in at a different, in a given period of time.

169 00:32:32.220 --> 00:32:39.139 Henry Silverman(Waymo): That's also an option. So, very willing to work with cities on all of these. There's also an overall risk of over-geofencing.

170 00:32:39.190 --> 00:32:55.220 Henry Silverman(Waymo): And I say this not just, right, you know, you can say, like, oh, you know, you might not want to geofence, you know, because we're losing revenue, and yes, we want to keep our customers happy, and people do complain if an area of the city is off-limits, but also it has

171 00:32:55.220 --> 00:33:10.739 Henry Silverman(Waymo): implications for the smooth operation of the fleet through the municipality itself. You can strand vehicles by creating islands, right? If you over-geofence an area, then the vehicle has nowhere to go, so it suddenly strands in an area because there's nowhere for it to go, given

172 00:33:10.740 --> 00:33:21.740 Henry Silverman(Waymo): the way the map is structured, it might be in a one-way street or something like that, right? You can sever depot, access, right? We… our vehicles return to depots.

173 00:33:21.760 --> 00:33:33.799 Henry Silverman(Waymo): charge, and so given how some of these, areas are, geofences are placed, that's also an implication that can happen. And yeah, you, like, users do get frustrated as well.

174 00:33:33.800 --> 00:33:45.660 Henry Silverman(Waymo): If large portions of the city are blocked, especially if they sometimes go through these areas and they say, hey, things are normal, why can't I… I'm looking outside of my house, everything's fine, why can't

175 00:33:45.660 --> 00:34:04.419 Henry Silverman(Waymo): you know, something, pick up in this area. And so here's an example, you know, of what a geofence might look like. We have many types of geofences. This one looks like it was placed on an intersection, and so we can place any sort of geofence, we can shape it however we want. Here, it's done with a radius, but again, there's options here.

176 00:34:05.100 --> 00:34:06.120 Henry Silverman(Waymo): Cool.

177 00:34:06.860 --> 00:34:14.630 Henry Silverman(Waymo): So we do have some, interim solutions, right? We… not everything is flowing through a very neat API.

178 00:34:14.630 --> 00:34:34.370 Henry Silverman(Waymo): that we can consume, and so one of the things that we've worked on is we like to structure everything, in a consistent format, and we have used Gemini. Gemini's an LLM that, we, those of you who don't know, that we, use internally, where, we actually have, Gemini Assist.

179 00:34:34.370 --> 00:34:43.120 Henry Silverman(Waymo): us with extracting the data, if there isn't a fully consistent API. If we'd have one that everyone used, this wouldn't really be necessary, but,

180 00:34:43.120 --> 00:34:55.549 Henry Silverman(Waymo): Sort of just conveying this. So, first, we need to ensure that, whatever sources we're getting, this information from, they're secure. You can imagine allow lists, all sorts of verifications that we have. We don't want folks to spoof.

181 00:34:55.639 --> 00:35:01.339 Henry Silverman(Waymo): Right? And say, hey, block off this area or that area. So we have that, for sure.

182 00:35:01.420 --> 00:35:10.680 Henry Silverman(Waymo): We also use Gemini to assist in extracting the data, so there are things that we care about, that we want to know, that we want to log in our databases, so…

183 00:35:10.680 --> 00:35:22.010 Henry Silverman(Waymo): You can imagine that we, send the raw data through Gemini, with a given prompt, and it essentially extracts the relevant data that is needed, right? We then ask it to essentially provide

184 00:35:22.010 --> 00:35:37.299 Henry Silverman(Waymo): confidence of how well it extracted something, right? If something's not confident, we send it for… I'll talk about the human in the loop validation later. And then in doing this automated process, we can essentially very quickly place a geofence.

185 00:35:37.640 --> 00:35:53.169 Henry Silverman(Waymo): Right? It doesn't have to go through some manual process initially, where someone's like, okay, I'm trying to interpret this block of text, I'm now going to a map to try to actually place this in here, right? We can sort of create a, a pipeline.

186 00:35:53.170 --> 00:36:06.289 Henry Silverman(Waymo): And then, for, various things that we might extract, we will do a human-in-the-loop validation, right? Sort and exception handling if we get an alert where, whoa, this, you know, for some reason.

187 00:36:06.340 --> 00:36:25.680 Henry Silverman(Waymo): this lat long that's provided is in the middle of the Atlantic Ocean, or something like that, right? You can have a human and loop validation there, and they can make any necessary adjustments. So, the example we listed on the right is we have, an original alert, an example that came in, right, and

188 00:36:26.480 --> 00:36:42.809 Henry Silverman(Waymo): essentially, like, how we would extract that and place it into our database, and from this database, from this, instructions, we would actually be able to place the geofence. Please use MDSUST will use Gemini ingestion, or can it more… more directly, exactly. Like, if everything's consistent.

189 00:36:42.820 --> 00:37:01.379 Henry Silverman(Waymo): Victoria there. Yeah, essentially, like, this Gemini solution is when things are unstructured, right? If all the information is provided via an API, that wouldn't be necessary, right? Because essentially, like, we know exactly it's provided, here's the lat long, here's, for example, and I'll talk about this. Oops, sorry.

190 00:37:01.410 --> 00:37:11.499 Henry Silverman(Waymo): here's essentially the ideal schema, or the… and I think all of this is enabled in MDS, but this I'm just sort of talking about, like, what we

191 00:37:11.720 --> 00:37:30.009 Henry Silverman(Waymo): would care about, and I imagine others do as well. One is just an understanding of just what type of event are we talking about here, an understanding of severity, and there are worries where you can, like, you know, severity might not actually need to be implied in the initial alert. There can be a taxonomy that just exists.

192 00:37:30.100 --> 00:37:45.940 Henry Silverman(Waymo): Right, around these sorts of events, but essentially, you know, understanding different incident, you know, categories, right? Is this a structure fire? Is there some sort of hazmat situation? You know, is there an area where

193 00:37:45.940 --> 00:37:51.439 Henry Silverman(Waymo): you know, there's a presidential motorcade, I don't know, right? All of these, there are many types of things that can exist.

194 00:37:51.480 --> 00:38:11.329 Henry Silverman(Waymo): In an area. And then severity tiers, this sort of goes to all the different types of geofences, you know, that, we can place, right? We talk about curb freezes, for example, right? Like, hey, oh, this is a sidewalk protest, right? As opposed to a protest spilling out into the street. That's very useful context, for us to know.

195 00:38:11.450 --> 00:38:25.999 Henry Silverman(Waymo): the second one is machine-readable geometry. So, yes, one version of it is explicit latitude and longitude with a radius. That's one way of doing it, right? If you give us a latitude and longitude and a radius, we can place it.

196 00:38:26.000 --> 00:38:42.830 Henry Silverman(Waymo): you know, a polygon, a geofence, according to that. You also can just give us a polygon, right, that says, hey, here's this, you know, shape that's drawn. Please avoid this area. There's also intricacies of maps, you know, where there are lane levels

197 00:38:42.830 --> 00:38:56.340 Henry Silverman(Waymo): You can imagine some bridges or various other streets have multi-tiers of lanes, depending on which international markets you go to, this is more common, right? Essentially, like, hey, this level is blocked off, but this level is fine.

198 00:38:56.340 --> 00:39:03.750 Henry Silverman(Waymo): So that's also, very useful information for us to have, so we can more precisely place, the avoidance areas.

199 00:39:03.750 --> 00:39:16.589 Henry Silverman(Waymo): The third one is a very big one, and a challenging one, I imagine, for everyone, is just sort of having the idea of temporal life cycle and expiration, and what Michael was actually saying in terms of push is actually also helpful here as well.

200 00:39:16.590 --> 00:39:26.850 Henry Silverman(Waymo): Right? So you… a lot of these things, we get a notification, and it says, hey, there's this situation going on right now, and how long

201 00:39:26.870 --> 00:39:49.879 Henry Silverman(Waymo): that lasts, is open to interpretation, you sometimes have to infer that sort of thing, right? If there's a way of saying, oh, and this area is clear now, that's actually very helpful for us as well, and that's something that we would actively be consuming. You know, you have to create… we create… in absence of these, and this is very rarely provided, you create policies, you adjust these policies, you work with municipalities on them as well.

202 00:39:50.340 --> 00:39:56.799 Henry Silverman(Waymo): and then 4 is similar to what I was describing before, you know.

203 00:39:56.920 --> 00:40:09.620 Henry Silverman(Waymo): you know, a directive mapping as an option. So, you know, this is the idea of, you know, hey, there's an FYI version of these that can be provided. There's also, no, we want you to take this action.

204 00:40:09.710 --> 00:40:28.649 Henry Silverman(Waymo): Right? Boarding is banned, right, but you can still drive through this area, that sort of stuff. Essentially, these are the pieces of information that we would need to place the best geofence that we can place for, everyone, for public safety, for the smoothness of our operations, and for municipalities as well.

205 00:40:28.710 --> 00:40:30.730 Henry Silverman(Waymo): So, summarizing.

206 00:40:30.740 --> 00:40:47.360 Henry Silverman(Waymo): At the very end, like, I think this… something like this, if it can really be standardized and used for as many markets as possible, you know, benefits everyone. You know, for municipalities, this helps with low latency responses to emergency scenes, you know, it's standardized, consistent control.

207 00:40:47.360 --> 00:41:05.339 Henry Silverman(Waymo): over these corridors, less reliance, you know, we heard earlier today from, Pierre about, like, you know, we don't… I don't think any of this is scaled with manual communication, right, to non-scene officers. We can't have people calling and be like, hey, the corner of this… not that this happens all the time right now, but we need to reduce this at scale.

208 00:41:05.350 --> 00:41:14.820 Henry Silverman(Waymo): For everyone. For us, it's the, you know, the… the thing we're trying to avoid is having

209 00:41:15.250 --> 00:41:23.740 Henry Silverman(Waymo): 25 different ways of ingesting different types of data from different places, right? We, to the extent that we can keep

210 00:41:23.790 --> 00:41:35.869 Henry Silverman(Waymo): our product, my engineering team saying is having as few of these, inbound as possible, right? Having it as consistent as possible, making this seamless.

211 00:41:35.870 --> 00:41:45.209 Henry Silverman(Waymo): And then as we expand to new markets, we can say, hey, all of these places are using this format, if you can convert this format, that would be fantastic, right? I think it would benefit everyone.

212 00:41:45.330 --> 00:42:03.850 Henry Silverman(Waymo): And then, obviously, for communities, right? The whole point of this is for public safety, during high-stress situations, emergency scenes, right? We want first responders to operate unimpeded. You know, we want to avoid the areas that we absolutely need to avoid.

213 00:42:03.920 --> 00:42:15.249 Henry Silverman(Waymo): because public safety is actually, you know, a lot of the motivation behind Waymo, and safety of individuals as a whole, is a lot of the motivation behind Waymo as a whole.

214 00:42:15.610 --> 00:42:20.319 Henry Silverman(Waymo): With that, I'm gonna end, but, hopefully that was helpful.

215 00:42:22.570 --> 00:42:25.189 Michael Schnuerle (OMF): Yeah, very helpful,

216 00:42:26.250 --> 00:42:38.369 Michael Schnuerle (OMF): Thank you so much for that, Henry. I… I have some questions, there are some in the chat. I'd like, if you could, to go through the chat and just maybe reply to some people and answer some of them as we go here.

217 00:42:38.670 --> 00:42:55.149 Michael Schnuerle (OMF): I do want to give San Francisco and LA time just a few minutes each to show what they're about to be working on, and then we can have a more verbal Q&A, but there's a lot of activity in the chat, which is great.

218 00:42:55.150 --> 00:42:55.970 Henry Silverman(Waymo): Yeah.

219 00:42:56.090 --> 00:43:02.060 Henry Silverman(Waymo): Let me see, I was trying to respond to some of these in real time, but let me sort of go through.

220 00:43:02.370 --> 00:43:07.400 Henry Silverman(Waymo): michael, yes, these four things are supported,

221 00:43:07.590 --> 00:43:09.110 Henry Silverman(Waymo): But do you know that any instantly.

222 00:43:09.110 --> 00:43:15.579 Michael Schnuerle (OMF): Henry, if you could, maybe type your replies there. I'm gonna try to get San Francisco to present just.

223 00:43:15.580 --> 00:43:17.879 Henry Silverman(Waymo): Oh, go for it, yes, I'll just reply, I'll just reply.

224 00:43:17.880 --> 00:43:28.600 Michael Schnuerle (OMF): Yeah, and then we can follow up with the ones you'd like to verbalize at the Q&A. Cool. So, San Francisco, Muyi, are you on here? Would you like to talk about

225 00:43:29.020 --> 00:43:31.580 Michael Schnuerle (OMF): Your, your future setup.

226 00:43:32.400 --> 00:43:38.570 Muyi Zhou （SFMTA）: Yeah, sure. Thank you, Piers, and… Henry's for the presentation.

227 00:43:39.010 --> 00:43:43.170 Muyi Zhou （SFMTA）: I will go next to talk about MDS.

228 00:43:43.510 --> 00:43:49.490 Muyi Zhou （SFMTA）: use in the future. I'm trying to share my screen. Let me know if you can see my slide.

229 00:43:49.970 --> 00:43:53.439 Michael Schnuerle (OMF): I can see your slides now, yeah. And the single slide, yep.

230 00:43:53.440 --> 00:43:54.669 Muyi Zhou （SFMTA）: Let me go back.

231 00:43:55.140 --> 00:43:58.280 Muyi Zhou （SFMTA）: Under this low. Let me stop.

232 00:43:58.690 --> 00:44:09.819 Muyi Zhou （SFMTA）: Good morning, everyone. My name is Muyi Zhou. I'm a Transportation Planner with San Francisco Municipal Transportation Agency. I've been working closely with MDS and CDS in the past years.

233 00:44:10.190 --> 00:44:18.380 Muyi Zhou （SFMTA）: Today, I want to share some undergoing work of San Francisco on street closures and emergency management of the streets.

234 00:44:18.520 --> 00:44:23.699 Muyi Zhou （SFMTA）: And our vision of sharing this information with MDS Policy API in the future.

235 00:44:25.090 --> 00:44:32.700 Muyi Zhou （SFMTA）: Let's start with some background and what makes us interested in MDS policies. So first of all.

236 00:44:33.220 --> 00:44:43.849 Muyi Zhou （SFMTA）: there was a widespread use of navigation apps by the public, so digitized data of standardized form. It is desired to get this information into these apps.

237 00:44:44.070 --> 00:44:46.780 Muyi Zhou （SFMTA）: To reach a broader group of users.

238 00:44:46.980 --> 00:44:59.170 Muyi Zhou （SFMTA）: The growth of connected fleets, such as autonomous vehicles, BrightHell, and delivery services have increased the importance of digital mapping and navigation services that guide vehicles on the street.

239 00:44:59.800 --> 00:45:09.099 Muyi Zhou （SFMTA）: San Francisco is one of the biggest markets for A-B testing and deployment, while San Francisco's dense urban streets have generated great challenges for them.

240 00:45:09.350 --> 00:45:22.619 Muyi Zhou （SFMTA）: So if you have struggled to timely take direction from first responder, and thus impacted the work of traffic control and emergency responses that we see on the street, and this conflict presents

241 00:45:23.120 --> 00:45:28.720 Muyi Zhou （SFMTA）: Several safety concerns that, for example, the delay in emergency response.

242 00:45:28.840 --> 00:45:31.290 Muyi Zhou （SFMTA）: And the safety of people on the street?

243 00:45:31.610 --> 00:45:35.290 Muyi Zhou （SFMTA）: And… Potentially secondary collections.

244 00:45:35.770 --> 00:45:44.899 Muyi Zhou （SFMTA）: To manage street closure and emergency geofence, our city departments, have their own solutions and systems.

245 00:45:45.030 --> 00:45:54.649 Muyi Zhou （SFMTA）: So for the emergency… dispatch, San Francisco Department of Emergency Management has a CAD system,

246 00:45:55.710 --> 00:46:07.510 Muyi Zhou （SFMTA）: It used the CAD system to communicate emergency geofence messages via emails and test messages to AV operators, or any subscriber at the same time that dispatched emergency resources to ASTIN.

247 00:46:07.640 --> 00:46:17.220 Muyi Zhou （SFMTA）: The geofence messages describe emergency response zone and tell AV operators to avoid these areas, and Henry, just showed us, like, example of this.

248 00:46:17.600 --> 00:46:23.189 Muyi Zhou （SFMTA）: And we, SFMTA, permit street closures due to special event and construction.

249 00:46:23.340 --> 00:46:31.860 Muyi Zhou （SFMTA）: The agency, inside the agency, we consolidated permit data from multiple permit programs to make them on a data stack.

250 00:46:32.220 --> 00:46:45.939 Muyi Zhou （SFMTA）: called WorkZone Data Exchange, which is championed by U.S. DOT a couple years ago. We announced this data being available to our contacts of navigation service providers, AVs, BrightHell.

251 00:46:46.050 --> 00:46:53.079 Muyi Zhou （SFMTA）: and delivery companies, and now this data feed is ingested by Wastemap, Google Maps, and TomTom.

252 00:46:53.270 --> 00:46:54.960 Muyi Zhou （SFMTA）: In their map portals.

253 00:46:55.130 --> 00:47:05.570 Muyi Zhou （SFMTA）: My team also communicated geofence of pickup and drop-off zones to this company via emails when and where we start loading and unloading chaos's.

254 00:47:06.000 --> 00:47:18.440 Muyi Zhou （SFMTA）: We also hosted the MDS Geography API for micro-mobility Geofencer. We use this data feed to communicate with Scooter and Bike share company about operation restriction restriction area.

255 00:47:18.850 --> 00:47:38.660 Muyi Zhou （SFMTA）: even though it is not highly AV relevant, but our plan is to use MDS policy as a multimodal geofencing tool. Like, AV is definitely our primary consumer, but I think the scope of this approach can be broadened to amplify its benefit if we consider almost applicable.

256 00:47:39.800 --> 00:47:51.099 Muyi Zhou （SFMTA）: And Public Works managed the street closure from capital projects. I don't know what system they have, but they do have open data and a public web map that shows the construction location and time span.

257 00:47:51.590 --> 00:47:58.999 Muyi Zhou （SFMTA）: There might be other city departments that close the street, like, for example, city, the police department permits parade.

258 00:47:59.300 --> 00:48:07.909 Muyi Zhou （SFMTA）: But I think they have a paper system. But anyway, the city have different teams manage different street closure and emergency in different systems.

259 00:48:08.070 --> 00:48:18.579 Muyi Zhou （SFMTA）: But we know that these events share a commonality, right? So they can be represented by a geography, and this geography will allow or not allow a certain group of users

260 00:48:18.610 --> 00:48:29.239 Muyi Zhou （SFMTA）: This restriction should have, like, an effective time span. Our vision is to bring all of them into a centralized system.

261 00:48:29.310 --> 00:48:35.279 Muyi Zhou （SFMTA）: and get them on an industry data standard, and we decided MDS policy is a good fit.

262 00:48:36.840 --> 00:48:52.810 Muyi Zhou （SFMTA）: So this year, we applied for the Safe Street for All grant, and we said we will use MDS to communicate the data mentioned in the previous slide. We hope to have, a tech platform to consolidate data and host the MDS policy data feed.

263 00:48:52.920 --> 00:49:08.920 Muyi Zhou （SFMTA）: And we will develop necessary interface for the emergency… the Department of Emergency Management's CAD system, because the emergency closure is more dynamic and urgent, while other closures from advanced planning allow us more time to define.

264 00:49:09.120 --> 00:49:15.000 Muyi Zhou （SFMTA）: For city staff, we will build internal data visualization and coordination tools.

265 00:49:15.160 --> 00:49:21.929 Muyi Zhou （SFMTA）: We are also looking for consultant support to bring all the city agencies to the table and facilitate the conversation.

266 00:49:22.080 --> 00:49:34.849 Muyi Zhou （SFMTA）: Through this project, we could have OMF form the MDS Policy Collaborative by bringing more cities on board, just like what we did for the CTS Curb Collaborative.

267 00:49:34.960 --> 00:49:51.079 Muyi Zhou （SFMTA）: AV operators and other, like, intended audience of this data feeds need to see, a critical mass of cities providing this information in the same way to justify the investment into ingesting and, using it.

268 00:49:52.820 --> 00:50:02.640 Muyi Zhou （SFMTA）: So our grant application is not just about MDS policy. A big portion of it will be used to upgrade the city's traffic signal to a bigger size.

269 00:50:02.870 --> 00:50:05.740 Muyi Zhou （SFMTA）: So, AV can easily see them.

270 00:50:06.320 --> 00:50:14.429 Muyi Zhou （SFMTA）: But, like, we don't have commitments or funding for this to be a project yet. We will hear the grant winner by the end of this year.

271 00:50:16.650 --> 00:50:21.609 Muyi Zhou （SFMTA）: Our intended audience of MDS policies are AE,

272 00:50:22.020 --> 00:50:26.179 Muyi Zhou （SFMTA）: Of course, like, some AV operators have noted that they would be able to

273 00:50:26.290 --> 00:50:44.420 Muyi Zhou （SFMTA）: use emergency information more rapidly if they were provided in a standardized, machine-readable database, just like Henry said. The pass of the California AB177T7 require AV operator to respond to emergency geofan messages from public

274 00:50:44.420 --> 00:50:48.070 Muyi Zhou （SFMTA）: safety officials, starting in July 2026.

275 00:50:48.160 --> 00:50:54.980 Muyi Zhou （SFMTA）: Which is in effect now. So the law is that within 2 minutes of receiving an emergency geofence.

276 00:50:55.120 --> 00:50:57.829 Muyi Zhou （SFMTA）: fencing message, the manufacturer shall

277 00:50:58.300 --> 00:51:06.900 Muyi Zhou （SFMTA）: issue direction to explain, to leave or avoid the area, identify. So currently, it takes time for AV to receive

278 00:51:07.060 --> 00:51:14.749 Muyi Zhou （SFMTA）: Text message or email, understand it, determine the appropriate course of actions, and direct their fleets accordingly.

279 00:51:14.900 --> 00:51:20.050 Muyi Zhou （SFMTA）: We hope MDS policy in real time can greatly improve this workflow.

280 00:51:20.260 --> 00:51:22.729 Muyi Zhou （SFMTA）: The same benefit.

281 00:51:23.120 --> 00:51:26.170 Muyi Zhou （SFMTA）: We'll also go to Connected Fleet.

282 00:51:26.650 --> 00:51:35.630 Muyi Zhou （SFMTA）: like Uber and Lyft, about receiving emergency information in real time, and thus avoiding the area identified and triggering rerouting and trip planning.

283 00:51:35.740 --> 00:51:47.929 Muyi Zhou （SFMTA）: Same idea, navigation service provider can use this information to guide their users of all modes to take detour and avoid area and get alerts about the emergencies.

284 00:51:48.020 --> 00:51:56.540 Muyi Zhou （SFMTA）: They can make this message reach a wider group of rural users, that are not watching the city's official social media channels.

285 00:51:56.690 --> 00:51:58.570 Muyi Zhou （SFMTA）: For city staff.

286 00:51:58.910 --> 00:52:12.139 Muyi Zhou （SFMTA）: This tool will benefit, cross-department coordination of street closure for better planning, scheduling, and prioritization. The city have been looking for tools to avoid, conflict planning closure.

287 00:52:12.310 --> 00:52:23.569 Muyi Zhou （SFMTA）: These closure events usually don't get announced until they got approved, so it happens that several departments are looking at closing the same street at the same time in the planning phase.

288 00:52:23.880 --> 00:52:42.269 Muyi Zhou （SFMTA）: Other than that, the consolidated street closure and emergency data in MDS Policy API can be very helpful for city departments to get updates from another. For example, SFMTA as a transit operator can adjust our transit services accordingly with,

289 00:52:42.620 --> 00:52:46.309 Muyi Zhou （SFMTA）: Department of Emergency Management's Emergency Closures.

290 00:52:47.620 --> 00:52:50.470 Muyi Zhou （SFMTA）: Last but not least, the public.

291 00:52:50.580 --> 00:53:04.790 Muyi Zhou （SFMTA）: Safety of people on the street at the incidents, including first responder, construction worker, traffic control worker, people attending the special event, shall be protected from timely and accurate reactions of the data receiver.

292 00:53:05.510 --> 00:53:06.540 Muyi Zhou （SFMTA）: Hmm…

293 00:53:08.270 --> 00:53:17.450 Muyi Zhou （SFMTA）: Okay, this is the end. I'm on the technical side of the house. I have my colleague, Hoffa Kronenberg, with me today, if you have any policy or grant questions.

294 00:53:18.100 --> 00:53:21.589 Muyi Zhou （SFMTA）: Oh, Harvard, feel free to jump in if you have anything to add.

295 00:53:22.520 --> 00:53:24.890 Michael Schnuerle (OMF): Right. Thank you, Muyi.

296 00:53:25.200 --> 00:53:29.840 Michael Schnuerle (OMF): We, so we're a little bit over… we're going over time a little bit. I'd like…

297 00:53:29.840 --> 00:53:45.999 Michael Schnuerle (OMF): to suggest that, whoever can stay, if people can stay an extra 10 minutes over, that would be great. LADOT was going to present on something they've been doing, but I'd like to maybe, if you can stay, Vlad, after you can present, it could be on the recording.

298 00:53:46.000 --> 00:53:51.460 Michael Schnuerle (OMF): But right now, I'd like to start the… any Q&A, if people want to raise their hands, and…

299 00:53:51.540 --> 00:53:59.090 Michael Schnuerle (OMF): ask questions about anything we've talked about, or if, Henry, you want to say anything based on anything you've replied to.

300 00:54:01.500 --> 00:54:17.940 Henry Silverman(Waymo): Yeah, regarding the, whether, municipal… whether Waymo communicates, geofan, where we establish our depots, I'm not the expert on that, so I'm… I can't respond to that right now. I generally know that cities do

301 00:54:17.980 --> 00:54:27.539 Henry Silverman(Waymo): eventually know, like, where our depots are for, for various reasons, but, I can follow up on… it's just not my, it's not… it's not my area of expertise.

302 00:54:27.720 --> 00:54:46.670 Henry Silverman(Waymo): and then, yeah, I think, like, a lot of the comments just that I've read are, the ones that are… the ones that I particularly want to call out is just some of the specificity. Like, I think someone mentioned, oh, you can specify even which lanes, or is there a directional change in traffic?

303 00:54:46.670 --> 00:55:01.510 Henry Silverman(Waymo): all of the stuff is… would be fantastic, right? And so the example I laid out was, like, if it's a two-lane road, and the right lane is blocked, that's very important, but the left lane, right, is still open for through traffic. Like, all of that information would be very, very important.

304 00:55:01.860 --> 00:55:03.790 Henry Silverman(Waymo): See, there's a hand raised, I believe.

305 00:55:04.420 --> 00:55:06.690 Michael Schnuerle (OMF): Yeah, we can take the hand from Cormac.

306 00:55:07.670 --> 00:55:17.740 Cormac McKay CCAM-RITES: Hi, Cormac here from, CCAM Rights. I'm project director on the European Commission's flagship, large-scale demonstration.

307 00:55:18.100 --> 00:55:26.540 Cormac McKay CCAM-RITES: And, this has come up a lot, here in Europe, on the lack of integration, and,

308 00:55:26.580 --> 00:55:41.550 Cormac McKay CCAM-RITES: The reputational damage that has been done by the failure of authorities in the US to prepare for deployments has had global ramifications. And I'm just wondering, why has it taken authorities so long

309 00:55:41.550 --> 00:55:49.690 Cormac McKay CCAM-RITES: To come up with these solutions, since deployments are nearly 5 years into progression right now.

310 00:55:49.970 --> 00:55:54.399 Cormac McKay CCAM-RITES: And I don't think it's fair that operators are getting all the blame.

311 00:55:54.660 --> 00:55:56.519 Cormac McKay CCAM-RITES: So, just to put that out there.

312 00:55:57.160 --> 00:56:03.430 Michael Schnuerle (OMF): I'll… I'll say briefly, so I used to work in the city, too. I was chief data officer in Louisville.

313 00:56:04.680 --> 00:56:27.529 Michael Schnuerle (OMF): you know, MDS has been able to support things like this since its inception, MDS policy in some way or another for 7 years, so it's been available, and then more specifically around AVs and passenger services for 4 years now. But many cities have not specifically picked it up for autonomous vehicles or taxis. But I will say, especially in Europe, many, many cities have used MDS policy to

314 00:56:27.570 --> 00:56:44.839 Michael Schnuerle (OMF): allow operators of bikes share, scooter share, to understand what's happening in emergencies and rules of the road. That's been going on a while. So I think everything just takes a little bit of time to raise the funds, to get the buy-in.

315 00:56:44.860 --> 00:56:59.199 Michael Schnuerle (OMF): when I was in the city, it… it was really hard. I tried to, organize, for instance, a data feed like this using the Waze, CIFs, Waze for Cities feed, and we had something like 8 different

316 00:56:59.440 --> 00:57:18.979 Michael Schnuerle (OMF): possible sources of road closures, all coming from different agencies, sometimes not even city agencies, and to try to consolidate that into a single data feed was a task that honestly turned out to be impossible, and I feel like they're just now cracking it in Louisville, Kentucky, 10 years later. So, there's a lot to it.

317 00:57:19.280 --> 00:57:22.889 Michael Schnuerle (OMF): That's what I'll say, but anyone else could share what they want to say. Andrew?

318 00:57:23.880 --> 00:57:40.030 Andrew Glass Hastings: Yeah, real quick, you know, it's a really good point that you raise, although cities certainly aren't monoliths, cities across the U.S, cities across Europe, I mean, there's… there's a lot to learn as this industry continues to evolve really quickly. I think

319 00:57:40.100 --> 00:57:53.029 Andrew Glass Hastings: right or wrong, the dynamic in the states in the U.S. that have seen AVs deployed the earliest, California, Arizona, Texas, Florida, Georgia.

320 00:57:53.030 --> 00:58:03.589 Andrew Glass Hastings: have unfortunately preempted City's ability to really manage and find ways of active partnership with these operators, and that has hindered a lot of the

321 00:58:03.590 --> 00:58:09.430 Andrew Glass Hastings: Possible, kind of, management solutions to be put into place more proactively.

322 00:58:09.430 --> 00:58:33.859 Andrew Glass Hastings: At the same time, like I said, they're not monoliths, and you just heard about Seattle, who doesn't even have AVs deployed yet, and yet, in collaboration with the state, got funding to put this MDS policy, emergency response notification system in place. So, there are… there are pros and cons across the board, but certainly lots of lessons as cities in Europe begin to

323 00:58:33.860 --> 00:58:37.499 Andrew Glass Hastings: To face the… the deployment of… of robotaxis.

324 00:58:38.990 --> 00:58:46.009 Cormac McKay CCAM-RITES: Yes, there's plenty of opportunities for the actual robo-taxis to fund the infrastructure for cities.

325 00:58:48.500 --> 00:58:49.920 Cormac McKay CCAM-RITES: I'll just hat that there.

326 00:58:53.400 --> 00:58:58.179 Michael Schnuerle (OMF): Vianova, do you want to go next? I think your hand was up.

327 00:58:58.660 --> 00:59:22.160 Gian-Luca Tellenbach (Vianova): Sure. Thank you, Michael. Thank you, everyone, for the super interesting content here. My question sort of spins it around the other way a little bit, also from the European perspective, looking to build on what great work has been done in the US. Question is more around, has there been any exploration into the data coming from AVs to cities? So, leveraging AVs as the, you know.

328 00:59:22.180 --> 00:59:41.799 Gian-Luca Tellenbach (Vianova): really high-quality eyes on the street that they are, and delivering information on, you know, where there might need to be some kind of, intervention, there might be an accident, or, even some other, you know, more data debris, information such as poorly visible street signs or potholes,

329 00:59:42.170 --> 00:59:42.930 Henry Silverman(Waymo): Yeah.

330 00:59:42.930 --> 00:59:50.919 Gian-Luca Tellenbach (Vianova): exploration that's been done on that from… I guess it applies to operators, cities, and OMF, but yeah, please, Henry.

331 00:59:51.340 --> 01:00:10.990 Henry Silverman(Waymo): Yeah, and again, I'm not the expert on all the different things that we do, but I think we published an article a few months back about, like, our pothole integration, how we communicate. For example, potholes, you know, I think it's been said that it was one of the best pothole detectors out there, just given our sensory stacks, so that's definitely one of the things that's explored. We definitely also

332 01:00:10.990 --> 01:00:32.030 Henry Silverman(Waymo): do communicate, and different municipalities have different requirements about different types of accidents that might occur. Some of these are in real time, some of them don't have to be in real time they're after the fact, but we absolutely do communicate that. I don't think we use MDS for a lot of that sort of stuff, just given

333 01:00:32.030 --> 01:00:47.139 Henry Silverman(Waymo): There are different reporting pathways that some cities, require, so similar type of thing. Hey, can you send this in an email? Can this be, you know, in this form or that form? I think it, like, both directions face their own… face their own problems, but…

334 01:00:47.150 --> 01:00:50.539 Henry Silverman(Waymo): Yes, there are various efforts like that underway.

335 01:00:50.950 --> 01:01:14.780 Gian-Luca Tellenbach (Vianova): Awesome to hear. Yeah, I mean, we found, at least we're trialing this in Paris with an operator, and we found that where the infrastructure, the data infrastructure is set, that's usually the biggest hurdle, because then cities feel like they can ask for it, and operators, you know, are easily able to share it. Is there any thoughts towards adding these as optional fields? Like, we have optional fields in MDS for scooters and

336 01:01:14.780 --> 01:01:16.589 Gian-Luca Tellenbach (Vianova): And other data points?

337 01:01:17.120 --> 01:01:23.520 Michael Schnuerle (OMF): Yeah, I'll point out that MDS, as of 2.1, does support the reporting of something like a pothole, so…

338 01:01:23.580 --> 01:01:40.379 Michael Schnuerle (OMF): in the incidents API data feed, which is also for crashes, but there is an obstruction incident type, and that obstruction can be a pothole, it could be a tree branch, it could be something blocking the road. So that is able to be recorded in MDS with

339 01:01:40.380 --> 01:01:46.319 Michael Schnuerle (OMF): things like latitude and longitude, timestamps, things like that. So, it is possible, but I think, to Henry's point.

340 01:01:46.320 --> 01:02:01.849 Michael Schnuerle (OMF): Cities may already have, like, some sort of agreement written in detail into a contract about how that data comes over, and so they might not necessarily be able to accept MDS, so cities need to update that language so that Waymo and others can send it in that format as well.

341 01:02:02.720 --> 01:02:07.090 Gian-Luca Tellenbach (Vianova): Makes sense. Incidents sounds like an awesome extension that we're waiting for.

342 01:02:07.780 --> 01:02:17.809 Michael Schnuerle (OMF): Yeah, it's really great. Actually, B&O proposed this in 2021, and now we finally got it, and we're working with Amsterdam on implementing it, maybe one of the first cities, and DC.

343 01:02:17.960 --> 01:02:20.330 Michael Schnuerle (OMF): Rachel, you had your hands up, your hands up.

344 01:02:20.890 --> 01:02:21.810 Rachel Castignoli AUSTIN: Yeah.

345 01:02:21.810 --> 01:02:41.320 Rachel Castignoli AUSTIN: Hey everyone. I will say that Waymo's potholes are about 50% correct, which is also what humans are. Humans are also very bad at reporting potholes correctly. A lot of utility, sunken utility manhole covers. So… but we're very thankful for the data, it's very helpful. I wanted to ask SFMTA, Muyi, like.

346 01:02:41.320 --> 01:02:56.299 Rachel Castignoli AUSTIN: how are you dealing with work zone data exchange? Our issue here is we give a permit for a long period, but the construction only closes the road for a few days, and we, the city, do not know what those days will be. And so…

347 01:02:56.300 --> 01:03:10.079 Rachel Castignoli AUSTIN: we're really trying to figure out, because it's something AV companies have asked us for, like, how to get those construction sites faster, and I'm wondering how MDS or Muyi, or any one of us, if someone has a solution, like, please let us know, we really want to implement

348 01:03:10.080 --> 01:03:20.420 Rachel Castignoli AUSTIN: something around construction zones, but we don't really know where… we know where they will be at some point in a 90-day period, we just don't know when in the period.

349 01:03:20.850 --> 01:03:31.760 Muyi Zhou （SFMTA）: Yeah, this is exactly, the same challenge we are having here. So when we share the data, we mark all the construction-relevant closure assembling closed.

350 01:03:31.900 --> 01:03:34.070 Muyi Zhou （SFMTA）: Which, like, wouldn't impact

351 01:03:34.590 --> 01:03:41.949 Muyi Zhou （SFMTA）: Say, the navigation service provider direct traffic there, because we're assuming the lane is… at least still some lanes are open.

352 01:03:42.160 --> 01:03:55.160 Muyi Zhou （SFMTA）: at those street, so that… I think Google Maps only take our, like, full-length closed, special event-related street closures, and just mark the whole street closed. They show the red dashed line on there.

353 01:03:55.230 --> 01:04:08.390 Muyi Zhou （SFMTA）: map interface, but for those construction-relevant ones, they still direct traffic there. But we just include it in the WZDS feed, so people know that this area might be impacted by… by construction.

354 01:04:08.800 --> 01:04:27.060 Muyi Zhou （SFMTA）: So our permits are still paper-based. We try to pass out the critical information from the PDF. Like, we would… like, if people would want to look at a specific closure, like, it will provide, like, the from time to time, which is the permitted date range, so no one knows,

355 01:04:27.570 --> 01:04:35.679 Muyi Zhou （SFMTA）: When the contractor is actually working on the sign, and now there's some vendor approaching us.

356 01:04:35.680 --> 01:04:48.220 Muyi Zhou （SFMTA）: Proposing there should be, like, a two-way communication, like, when the contractor is on-site, they should have, like, a platform to tell, like, there's… there's work going on. So, yeah, something like that, but we don't have that implemented yet.

357 01:04:48.720 --> 01:04:53.069 Muyi Zhou （SFMTA）: So basically, the idea in WZLX is just the full day range of the permit.

358 01:04:53.720 --> 01:05:14.440 Michael Schnuerle (OMF): I'll note in Louisville, we have the same problem, and the city is looking at ordinances to say, yes, you might have a permit for 30 days, but you need to notify the city, like, 3 days before construction starts, and then keep that up to date with notifications, and then notify the city when it ends, or when it's supposed to end, and then update that as well.

359 01:05:14.440 --> 01:05:17.250 Michael Schnuerle (OMF): So that's going to be a new ordinance that will help

360 01:05:17.250 --> 01:05:21.090 Michael Schnuerle (OMF): Clarify that permit process for a city, and the actual construction times.

361 01:05:21.150 --> 01:05:32.949 Michael Schnuerle (OMF): So that it can go into a feed. Henry, I think Rachel was asking if you could send construction information to them. MDS supports that in one way. Of course, Workstone Data Exchange does too.

362 01:05:34.150 --> 01:05:48.510 Henry Silverman(Waymo): Yeah, I was just gonna say, this isn't my, like, the area I'm most involved in, although I work with these folks quite a bit, just given some of my other work at Waymo, and I'm glad, like, the Caltrans example was provided, but I can guarantee you that

363 01:05:48.510 --> 01:06:12.139 Henry Silverman(Waymo): any pathway that gives the most precise and up-to-date method of, like, what is construction, even if it's something along the lines of, like, we think construction's gonna happen here during this period of time, we might actually change our policies, just even given that information, right? Where we might change our thresholds for various sorts of things, and then once you know more, getting the most real-time updates is absolutely something we're interested in.

364 01:06:12.170 --> 01:06:26.529 Henry Silverman(Waymo): I know of the Caltrans example, I don't know of the details of others, but I'm absolutely happy to follow up and Rachel, like, make those… make those connections. I know it's something that's a big area that a lot of the folks at this company are working on right now.

365 01:06:27.560 --> 01:06:32.379 Michael Schnuerle (OMF): Emily, would you… I know you put some information about California

366 01:06:32.500 --> 01:06:37.379 Michael Schnuerle (OMF): changes coming, and you had some comments here. Would you like to comment on that verbally?

367 01:06:38.420 --> 01:06:54.589 Emily Warren (CalSTA): Sure, yeah, I, I think it's mostly there, but, you know, basically, Caltrans has their own format for publishing lane closure information, and they also have that connected to operational processes in the field, where the constructions and maintenance teams

368 01:06:54.590 --> 01:06:58.930 Emily Warren (CalSTA): You know, will, as part of their protocol, digitally log

369 01:06:58.930 --> 01:07:23.139 Emily Warren (CalSTA): a lane as being open or closed when they open or close it, so that that data gets updated, in the Caltrans headquarters system, and then communicated out on a 5-minute update cycle through this web portal. But we understand that this is a non-standard format, and so it's a priority that Caltrans is actively working on to put it in

370 01:07:23.140 --> 01:07:34.120 Emily Warren (CalSTA): WZDX format, but we've had conversations with the Waymo product team about, accessing this information just to help… to help augment their situational awareness of where work zones are likely to be.

371 01:07:34.160 --> 01:07:35.630 Emily Warren (CalSTA): On California highways.

372 01:07:36.520 --> 01:07:49.109 Michael Schnuerle (OMF): And Emily, you could use MDS as well if you'd like, but I understand. Emily, would you like to mention anything about SB 1246, which seems… which overlaps with today's conversation?

373 01:07:50.330 --> 01:08:06.170 Emily Warren (CalSTA): Yeah, I think, as you saw in the chat, that our legislature has been actively discussing different policies this year, as SB 1246 was going through the legislative process, related to,

374 01:08:06.170 --> 01:08:22.410 Emily Warren (CalSTA): the need for coordination with AV companies around emergency situations. And of course, our regulations already address this in a number of ways. Like, we already require, AV companies to ingest and, respond to emergency geofencing messages.

375 01:08:22.410 --> 01:08:39.320 Emily Warren (CalSTA): from local emergency officials, but this bill would take it a step further, in a number of ways, but relevant to this conversation, it would, require AV companies to also acknowledge the receipt of those emergency geofencing messages back to the issuing

376 01:08:39.330 --> 01:08:50.419 Emily Warren (CalSTA): officials, so that there's kind of that handshake, and that the emergency officials would know that the message was received. And then there's also some provisions specific to when

377 01:08:50.580 --> 01:09:08.410 Emily Warren (CalSTA): an emergency… like, a fleet-wide emergency state, happens, which is defined in the legislation, that affects the ability of the AV fleet, to, to operate, and they're not able to remotely retrieve vehicles.

378 01:09:08.410 --> 01:09:21.369 Emily Warren (CalSTA): then the locations of the affected vehicles would need to be communicated, digitally to the local jurisdiction. And you can imagine that MDS could certainly be a mechanism that could be used for communicating that.

379 01:09:21.370 --> 01:09:28.959 Emily Warren (CalSTA): So this legislation has been passed through both houses, of our state legislature, and is pending on the governor's desk.

380 01:09:30.170 --> 01:09:43.520 Michael Schnuerle (OMF): And to make a quick note before Henry talks, MDS does support that sort of handshake and acknowledgement of receipt through the MDS 2.1 push method, so I just want to point that out.

381 01:09:43.520 --> 01:10:01.320 Henry Silverman(Waymo): Michael, you essentially pointed out the exact thing I was going to say. Like, yeah, it's essentially, like, you know, what that handshake means in receipt. Like, you know, again, this goes towards, like, the fragmented nature. If it's an email, you have to reply to the email, right? If it's something else, there are other ways of doing it.

382 01:10:01.320 --> 01:10:09.450 Henry Silverman(Waymo): I always prefer an API, but I'm a tech worker, right? Because of the reasons that Michael was saying, is essentially, like, you know, that's one way of confirming the handshake.

383 01:10:09.450 --> 01:10:25.930 Henry Silverman(Waymo): I also believe in that legislation, and Emily, I'm, like, looking through it. I believe there's also some of the things I talked about, which is, responders would provide the duration, right, of the closure, and it can be updated as well, right, if needed. And so, again, this is all the things that can happen

384 01:10:25.940 --> 01:10:40.290 Henry Silverman(Waymo): with MDS or an API, you know, if there's an update, you can publish that update, and we can adjust as needed. So, yes, I'm aware of this legislation, and also, like, MDS would be a fantastic vehicle for,

385 01:10:40.310 --> 01:10:49.749 Henry Silverman(Waymo): For some of this stuff, the more folks can adapt it. So, I unfortunately do have to drop, but I really appreciate everyone taking the time

386 01:10:49.890 --> 01:10:55.120 Henry Silverman(Waymo): it's a great group. I'm excited to work with you all. Thank you.

387 01:10:55.120 --> 01:11:02.410 Michael Schnuerle (OMF): Thank you, Henry, thanks for presenting. I think, Vlad, do you have time to present? I know we've had more than half the people staying.

388 01:11:02.410 --> 01:11:12.049 Vladimir Gallegos (LADOT): You know, I just wanted to comment. Most of what's great about all of the work that you guys are all doing is that what happens in California really helps all the cities in California.

389 01:11:12.120 --> 01:11:27.600 Vladimir Gallegos (LADOT): So that is… so with, you know, San Francisco doing their research and their depth of work is… is… we're talking, you know, we're also… we're talking to Caltrans, we're talking to… to Metro, we're talking to everybody, and OMF, thank you for just gluing that together. And, you know, California is leading this way.

390 01:11:27.600 --> 01:11:40.810 Vladimir Gallegos (LADOT): But it's our collaboration and working with companies. You know, OMF MDS stuff, you know, started City of LA, right? And, like, we've been… we've been talking about this before any autonomous vehicle was on the public right-of-way.

391 01:11:40.920 --> 01:11:51.250 Vladimir Gallegos (LADOT): You know, so this is… we've been telling this story for a long time, and… but we can't just… we can't just be the only ones. So thank you, everyone, for just joining and being part of this. That's all.

392 01:11:52.010 --> 01:11:55.760 Michael Schnuerle (OMF): Okay, great. We'll save your, presentation for a future meeting, then.

393 01:11:55.760 --> 01:11:56.540 Vladimir Gallegos (LADOT): Yeah.

394 01:11:56.540 --> 01:12:03.580 Michael Schnuerle (OMF): All right, thanks everyone for joining today. We'll end it here. There will be, this recording and…

395 01:12:03.580 --> 01:12:23.459 Michael Schnuerle (OMF): the transcript and the chat will all be published along with the slides that I get from everybody and put into one deck, by email to the mailing list, so make sure you're signed up. And, thanks for participating, thanks for everyone who presented today. We really appreciate it. It was a great discussion.