Web conference notes, 2026.03.26 (MDS Working Group)

MDS Working Group

• Monthly on a Thursday open to the public

Important

Note new date and time!

March 26 at 14:00 UK GMT, 15:00 Paris CET, 16:00 EET, 10am EST

• Zoom Registration and Join Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4
  • One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)
• Signup to the Mailing List for emails and calendar invites

Agenda

Europe’s March MDS Mobility Month

We will be reviewing the features and changes coming in MDS 2.1, and are looking for attendance and feedback from a European audience. We would like to ensure it meets the needs of cities and countries in the region.

Read our blog post about March MDS Month in Europe.

Caution

The time is shifted to accommodate our friends in Europe: 14:00 GMT / 15:00 CET

Agenda

1. Intro and announcements (10 min)
2. Review of MDS 2.1 features and changes (20 mins)
   • Modes Overhaul
   • Incidents and Crashes
   • Delivery
   • Transit fixed route
   • For-hire Autonomous Vehicles
   • Real-time Policy
   • Enforcement and Violations
3. Feedback and questions from attendees (25 mins)

To prepare, see our MDS 2.1 Release Plan and browse the updates here in our development branch.

Action Items and Decisions

1. Watch the recording, browse the draft spec then send feedback or questions about the release via email or on GitHub
2. Join the OMF to get more involved and participate in our OMF Academy courses

Minutes

• 63 Attendees
• OMF Slides
• Recording - Passcode: 3L?M44BS

Notes

...

Chat

Click to view meeting chat

• 00:05:31 Andrew Glass Hastings (OMF): Replying to "If you can while we ..."

• Next to your name click the 3 dots and select rename. If you add your city or org it helps everyone on the call know who is here. Thanks!

• 00:06:24 sondre Vasseng: Hi Andrew! Likewise

• 00:06:28 Kevin Tobias: Kevin Tobias PennDOT

• 00:06:39 Matthew Clark (Steer and CoMoUK): Replying to "If you can while we ..."

• Hi all. I'm Matthew Clark from Steer and Chair of CoMoUK. Based in London, UK, working globally on shared mobility + for cities and private sector.

• 00:06:57 Oskar Jahr (Bergen Municipality): Oskar Jahr, part of the group from Bergen Municipality, Department for Urban Environment Development and Services

• 00:06:57 Andrew Glass Hastings (OMF): Reacted to "Hi all. I'm Matthew ..." with 👋

• 00:07:05 Andrew Glass Hastings (OMF): Reacted to "Oskar Jahr, part of ..." with 👋

• 00:07:15 Otto van Boggelen: Otto vanBoggelen, CROW DashboardDeelmobiliteit.nl

• 00:07:19 Eleonora Ghetti (GRUBER Logistics): Hello, I'm Eleonora Ghetti from Gruber Logistics

• 00:07:30 Aylene McCallum (OMF): Hello everyone! I'm Aylene McCallum - Director of Partnerships & Development at the OMF. I'm based in Denver, Colorado.

• 00:08:02 Lars Ove and Jon Agnar, City of Bergen: Lars Ove Kvalbein and Jon Agnar Leirvik from the Agency for urban environment, City of Bergen, Norway.

• 00:08:29 Inga Traub (nextbike GmbH): Hello, I am Inga, a Software Developer at nextbike. I am based in Leipzig, Germany.

• 00:08:52 sondre Vasseng: Sondre Vasseng from agency for urban environment, City of Oslo in Norway

• 00:09:11 Sven Bråten (Nivel): Sven Bråten from Nivel, Norway

• 00:09:14 Aylene McCallum (OMF): Big welcome to Nivel - a brand new member to the OMF!

• 00:09:26 Evan Costagliola [Cityfi]: Hi! I’m Evan Costagliola with Cityfi based in Utrecht, NL.

• 00:09:45 Andrew Glass Hastings (OMF): Reacted to "Otto vanBoggelen, CR..." with 👋

• 00:09:47 Kristian Sims - City of Columbus, OH: Hello! Kristian Sims from the City of Columbus, OH

• 00:09:49 Andrew Glass Hastings (OMF): Reacted to "Hello, I'm Eleonora ..." with 👋

• 00:09:59 Andrew Glass Hastings (OMF): Reacted to "Hello, I am Inga, a ..." with 👋

• 00:10:12 Andrew Glass Hastings (OMF): Reacted to "Hello! Kristian Sims..." with 👋

• 00:10:52 Nivel | Harald, Antonia, Maroof: Nivel is happy to be in this great company of mobility friends, from Harald Sævareid + Antonia & Maroof.

• 00:11:17 Andrew Glass Hastings (OMF): Reacted to "Nivel is happy to be..." with 👏

• 00:11:21 Andrew Glass Hastings (OMF): Reacted to "Hi! I’m Evan Costagl..." with 👋

• 00:11:26 Andrew Glass Hastings (OMF): Reacted to "Sven Bråten from Niv..." with 👋

• 00:11:29 Andrew Glass Hastings (OMF): Reacted to "Sondre Vasseng from ..." with 👋

• 00:11:39 Andrew Glass Hastings (OMF): Reacted to "Lars Ove Kvalbein an..." with 👋

• 00:11:47 Andrew Glass Hastings (OMF): Reacted to "Kevin Tobias PennD..." with 👋

• 00:11:55 Pietro - Populus: Hello! Pietro from Populus, first time for me in this group, great to be here.

• 00:12:01 Andrew Glass Hastings (OMF): Reacted to "Hello! Pietro from P..." with 👋

• 00:12:02 Oskar Jahr (Bergen Municipality): A, D

• 00:12:04 Aylene McCallum (OMF): https://calendar.google.com/calendar/u/0/embed?src=openmobilityfoundation.org_g6gsaccjvijnmlhigfpj01ngp0@group.calendar.google.com&ctz=America/Los_Angeles

• 00:12:08 Otto van Boggelen: b

• 00:12:10 Kristine Bull Sletholt, City of Stockholm: A, B

• 00:12:11 Inga Traub (nextbike GmbH): A, D

• 00:12:14 Tommaso Bonino, SRM Bologna: A, B and D

• 00:12:15 Robbie Vinogradov (City of Amsterdam): B

• 00:12:15 Anna Ward (Blue Systems): D! Anna Ward with Blue Systems, based in NYC

• 00:12:18 Lars Ove and Jon Agnar, City of Bergen: D and E!

• 00:12:22 Elias Arnestrand - K2 Sweden: E

• 00:12:24 Joy Pasquet - Amazon: B & D

• 00:12:25 Christopher Shelley | City of Philadelphia: D+E

• 00:12:25 Evan Costagliola [Cityfi]: C & E 🙂

• 00:12:31 Kristian Sims - City of Columbus, OH: A and E

• 00:12:32 Matthew Clark (Steer and CoMoUK): B

• 00:12:35 Aylene McCallum (OMF): Reacted to "B" with 😃

• 00:12:39 Aylene McCallum (OMF): Reacted to "C & E 🙂" with 😃

• 00:12:42 Matt McBride (NYC DOT): Hello! Matt McBride, data scientist working for NYC dept of transportation. A,D, and E.

• 00:12:42 Anna Ward (Blue Systems): &E 🙂

• 00:12:43 Lea Decker, New Mobility Solutions, Hamburg: Lea Decker New Mobility Solutions HAmburg; Strategic development in autonomous Mobility services, A

• 00:12:43 Pietro - Populus: D

• 00:12:44 Eleonora Ghetti (GRUBER Logistics): A, B

• 00:12:45 Gonzalo Martinez Santos (Arcadis - CurbIQ): D & E!

• 00:12:46 Alia Verloes (Blue Systems): D + E!

• 00:12:47 Michael Schwartz, INRIX: D and E

• 00:12:48 Karen Vancluysen: E

• 00:12:50 Marco Surace: Marco Surace rome Mobility Agency

• 00:12:51 Kevin Tobias: Kevin Tobias PennDOT A fellow committee member from an ITS subcomittee suggested I attend.

• 00:13:02 Nivel | Harald, Antonia, Maroof: A, B, C, D, E

• 00:13:06 Aylene McCallum (OMF): Reacted to "A, B, C, D, E" with ❤️‍🔥

• 00:13:14 Nils Fearnley TØI - Institute of Transport Economics, Norway: B

• 00:13:17 Anna Ward (Blue Systems): Reacted to "D + E!" with ❤️

• 00:13:23 gemma schepers: gemma schepers city of amsterdam

• 00:13:24 Inga Traub (nextbike GmbH): Reacted to "A, B, C, D, E" with 😀

• 00:13:28 Michael Schnuerle (OMF): Reacted to "gemma schepers city ..." with 🌟

• 00:13:37 Michael Schnuerle (OMF): Reacted to "E" with 🎉

• 00:13:42 Michael Schnuerle (OMF): Reacted to "D and E" with 🎉

• 00:13:55 Michael Schnuerle (OMF): Reacted to "&E 🙂" with 👍

• 00:13:57 Nils Fearnley TØI - Institute of Transport Economics, Norway: Hi, I am Nils Fearnley from Institute of Transport Economics, Norway (TØI), invited by another attendant due to my interest in OMF and MDS for trip analysis. MDS 2.1 capabilities are particular interesting.

• 00:14:02 Karen Vancluysen: Karen Vancluysen POLIS

• 00:14:10 Michael Schnuerle (OMF): Reacted to "E" with 🇪🇺

• 00:14:22 Michael Schnuerle (OMF): Reacted to "D and E!" with 🇪🇺

• 00:14:24 Aylene McCallum (OMF): We love our community - thank you for showing up and contributing to making MDS relevant and effective tool for cities and industry

• 00:14:37 Michael Schnuerle (OMF): Reacted to "Nivel is happy to be..." with 🇪🇺

• 00:14:38 Aylene McCallum (OMF): Reacted to "Hi, I am Nils Fearnl..." with ❤️

• 00:14:39 Lars Ove and Jon Agnar, City of Bergen: Reacted to "gemma schepers cit..." with 👏

• 00:15:34 Michael Schnuerle (OMF): Reacted to "Karen Vancluysen POL..." with 🇪🇺

• 00:17:02 Andrew Glass Hastings (OMF): Reacted to "Hi, I am Nils Fearnl..." with 👋

• 00:17:20 Gonzalo Martinez Santos (Arcadis - CurbIQ): Hi all - I'm Gonzalo Martinez Santos, from CurbIQ (Arcadis), based in London. Great to see familiar names and faces :)

• 00:17:21 Michael Schnuerle (OMF): Reacted to "gemma schepers city ..." with 🇪🇺

• 00:17:23 Michael Schnuerle (OMF): Reacted to "gemma schepers city ..." with 👏

• 00:17:37 Andrew Glass Hastings (OMF): Reacted to "Hi all - I'm Gonzalo..." with 👋

• 00:20:25 Kirubel Hailu: Reacted to "Hi, I am Nils Fearnl…" with 👋

• 00:20:41 Lars Ove and Jon Agnar, City of Bergen: Reacted to "Hi all - I'm Gonza..." with 👋

• 00:21:26 Andrew Glass Hastings (OMF): Don’t hesitate to ask questions along the way in the chat!

• 00:21:46 Karen Vancluysen: Cities in the room which are not yet a POLIS member, do get in touch :-)

• 00:22:16 Andrew Glass Hastings (OMF): The level of familiarity with MDS is diverse so no worries if you are just getting to know the standard! You are in good company!

• 00:23:48 Kirubel Hailu: Reacted to "Hello! Kristian Sims…" with 👌

• 00:23:52 Kirubel Hailu: Reacted to "Nivel is happy to be…" with 👌

• 00:24:01 Kirubel Hailu: Reacted to "Sven Bråten from Niv…" with 👌

• 00:24:09 Kirubel Hailu: Reacted to "Sondre Vasseng from …" with 👌

• 00:24:17 Kirubel Hailu: Reacted to "Lars Ove Kvalbein an…" with 👌

• 00:27:19 Nivel | Harald, Antonia, Maroof: Reacted to "Cities in the room w..." with ❤️‍🔥

• 00:27:27 Aylene McCallum (OMF): If your city is not an OMF member yet, please consider joining! Joining is as simple as signing and returning a membership application and dues are not required for public sector members.

• https://www.openmobilityfoundation.org/participate/

• 00:27:52 Nivel | Harald, Antonia, Maroof: Reacted to "Lea Decker New Mobil..." with 👏

• 00:29:48 Aylene McCallum (OMF): Opportunity

• 00:29:56 Matthew Clark (Steer and CoMoUK): Transparency between operators and cities

• 00:29:59 Andrew Glass Hastings (OMF): management

• 00:30:09 Pierre Bouffort (Blue Systems): Transparency and collaboration

• 00:30:15 Inga Traub (nextbike GmbH): reducing complexity

• 00:30:15 Nivel | Harald, Antonia, Maroof: It is the standardized enabler.

• 00:30:16 Pietro - Populus: comparability

• 00:30:21 Elias Arnestrand - K2 Sweden: Data driven management

• 00:30:23 Oskar Jahr (Bergen Municipality): Oversight

• 00:30:25 Otto van Boggelen: standard

• 00:30:28 Andrew Glass Hastings (OMF): Open source

• 00:30:30 gemma schepers: uniformity,

• 00:30:31 Lars Ove and Jon Agnar, City of Bergen: Control, collaboration, rich data...

• 00:30:32 Matt McBride (NYC DOT): will require data from rideshare companies and use MDS's standards to communicate what we want from them.

• 00:30:40 sondre Vasseng: Reacted to "gemma schepers cit..." with 👏

• 00:30:43 Tommaso Bonino, SRM Bologna: A standard. We have built our "reporting scheme", but having one available and shared sounds interesting. Very interesting.

• 00:30:43 Matthew Clark (Steer and CoMoUK): Reacted to "Hope to ask for data..." with 👏

• 00:30:46 Andrew Glass Hastings (OMF): Reacted to "Hope to ask for data..." with ❤️

• 00:30:46 Aylene McCallum (OMF): Reacted to "Control, collaborati..." with 👍🏻

• 00:30:47 Lars Ove and Jon Agnar, City of Bergen: Interoperatbility

• 00:30:47 Eleonora Ghetti (GRUBER Logistics): Easier communication

• 00:30:53 Aylene McCallum (OMF): Reacted to "A standard. We have ..." with 👍🏻

• 00:30:56 Aylene McCallum (OMF): Reacted to "Easier communication" with 👍🏻

• 00:30:59 Aylene McCallum (OMF): Reacted to "Interoperatbility" with 👍🏻

• 00:31:00 Andrew Glass Hastings (OMF): Replying to "will require data fr..."

• Let us know how we can help Matt!

• 00:31:05 Aylene McCallum (OMF): Reacted to "uniformity," with 👍🏻

• 00:31:06 Robbie Vinogradov (City of Amsterdam): Transparency

• 00:31:09 Aylene McCallum (OMF): Reacted to "Data driven manageme..." with 👍🏻

• 00:31:18 Aylene McCallum (OMF): Reacted to "Transparency" with 👍🏻

• 00:31:33 Matt McBride (NYC DOT): Replying to "will require data fr..."

• I would really love some help of how to communicate these standards through agency rulemaking or legislation.

• 00:31:47 Andrew Glass Hastings (OMF): Reacted to "I would really love ..." with 💯

• 00:31:47 Pietro - Populus: Reacted to "Transparency" with 👍🏻

• 00:31:54 Andrew Glass Hastings (OMF): Replying to "will require data fr..."

• We have good examples of language to use

• 00:32:02 Aylene McCallum (OMF): Reminder - membership is easy for public agencies - feel free to reach out if you are interested!

• 00:32:12 Nivel | Harald, Antonia, Maroof: Reacted to "A standard. We have ..." with ❤️‍🔥

• 00:32:27 Andrew Glass Hastings (OMF): Replying to "will require data fr..."

• Send me or Michael a note at andtew@openmobilityfoundation.org or Michael@openmobilityfoundation.org

• 00:33:00 Matt McBride (NYC DOT): Replying to "will require data fr..."

• https://legistar.council.nyc.gov/LegislationDetail.aspx?ID=7861511&GUID=05BA3489-38FD-436D-9B55-B35A46A6CD96&Options=ID%7CText%7C&Search=78

• The legislation in question atm. We hope to specify standards in the rulemaking process

• 00:33:31 Matt McBride (NYC DOT): Replying to "will require data fr..."

• Sounds good! I will reach out.

• 00:34:13 Matt McBride (NYC DOT): Reacted to "Send me or Michael a..." with ❤️

• 00:34:41 Kirubel Hailu: Reacted to "Oskar Jahr, part of …" with 👌

• 00:38:40 Matt McBride (NYC DOT): Any specifics on delivery using micromobility?

• 00:39:26 Andrew Glass Hastings (OMF): Replying to "Any specifics on del..."

• Yes. MDS 2.1 includes the type of vehicle making the delivery

• 00:39:33 Matt McBride (NYC DOT): Reacted to "Yes. MDS 2.1 include..." with ❤️

• 00:40:24 Nivel | Harald, Antonia, Maroof: @Michael Schnuerle (OMF), could you talk more about 2.1 is non-breaking, as many operators have not upgraded to 2.0 yet?

• 00:41:13 Aylene McCallum (OMF): The OMF is very focused on helping cities and operators upgrade to MDS 2.0 (and beyond!)

• 00:41:48 Nivel | Harald, Antonia, Maroof: Let’s go directly from 1.0/1.2 to 2.1!

• 00:42:06 Andrew Glass Hastings (OMF): Reacted to "Let’s go directly fr..." with 💯

• 00:42:23 Andrew Glass Hastings (OMF): Replying to "The OMF is very focu..."

• Will be focused on upgrading to latest version for sure!

• 00:44:08 Aylene McCallum (OMF): Clarification: OMF membership is organizational meaning that if your agency / company is a member, all individual employees are also considered members

• 00:46:37 Joy Pasquet - Amazon: Re: policy, is MDS compatible with EU standards like DATEX II?

• 00:48:44 Andrew Glass Hastings (OMF): Hi Joy! Good question. Short answer is yes. There is a level of interoperability. Our understanding of DATEX II is there is very little overlap, but this is an area that needs a little more attention.

• 00:49:24 Joy Pasquet - Amazon: Replying to "Re: policy, is MDS c..."

• Got it, thanks Andrew!

• 00:49:33 Andrew Glass Hastings (OMF): Replying to "Re: policy, is MDS c..."

• Aha - a better answer from Michael now!

• 00:50:02 Joy Pasquet - Amazon: Reacted to "Aha - a better answe..." with 👍

• 00:51:05 Matthew Clark (Steer and CoMoUK): ability to record AV violations

• 00:52:57 Inga Traub (nextbike GmbH): I really like the possibility to capture incidents, specifically vandalism is a great new possibility. Thank you for your work!

• 00:53:05 Elias Arnestrand - K2 Sweden: Great overview of 2.1!

• 00:53:28 Evan Costagliola [Cityfi]: Reacted to "I really like the po..." with ➕

• 00:53:40 Nivel | Harald, Antonia, Maroof: Reacted to "I really like the po..." with 👏

• 00:54:19 Alex Pazuchanics (Vianova): can you talk more about the 2.1 nexus between curb/CDS and MDS?

• 00:54:23 Aylene McCallum (OMF): Reacted to "I really like the po..." with 👏

• 00:54:40 Alex Pazuchanics (Vianova): are we on a path toward the standards eventually merging or having a more structured relationship between them?

• 00:54:56 Lars Ove and Jon Agnar, City of Bergen: I have heard about 2.1 before, but this was even more impressive and opens up a lot of exciting possibilities!

• 00:55:10 Aylene McCallum (OMF): Reacted to "are we on a path tow..." with 💡

• 00:55:15 Andrew Glass Hastings (OMF): Reacted to "I have heard about 2..." with 👏

• 00:55:24 Aylene McCallum (OMF): Reacted to "I have heard about 2..." with 👏

• 00:55:29 Nivel | Harald, Antonia, Maroof: Reacted to "I have heard about 2..." with 💞

• 00:56:19 Matt McBride (NYC DOT): If we request data from a company and want them to follow MDS standards, what infrastructure do we need as an agency for them to be able to do that?

• atm I understand MDS to simply be a request for said companies to ensure they have specific fields with specific data types. But does this tool do more than that?

• 00:56:38 Alex Pazuchanics (Vianova): Replying to "Re: policy, is MDS..."

• We've done a mapping of the schemas (alongside CDS too)- I can share what we've started

• 00:57:18 Andrew Glass Hastings (OMF): Replying to "Re: policy, is MDS c..."

• @Alex Pazuchanics (Vianova) please do! That would be great

• 00:57:21 Joy Pasquet - Amazon: Reacted to "We've done a mapping..." with 👍

• 00:57:40 Michael Schnuerle (OMF): Permit language and upgrades in MDS https://github.com/openmobilityfoundation/governance/blob/main/technical/OMF-MDS-Policy-Language-Guidance.md

• 01:00:28 Aylene McCallum (OMF): Replying to "If we request data f..."

• Yes, essentially - MDS standardizes the way information is shared between two parties. The idea is that THEN - once the data is standardized - there is greater opportunity to DO something with the data... analyze, pilot, govern, etc.

• 01:00:57 Andrew Glass Hastings (OMF): Matt if an agency requires the use of MDS the data you receive from the operator will be in MDS. The agency needs an ability to receive, analyze and display the data which is often done by a city vendor like Blue Systems, INRIX, Populus, Nivel, etc. Does that answer your question?

• 01:01:13 Thibault Castagne (Vianova): We did also look at this at Vianova for FCD data, there is actually a formal definition with the highway authority in the US, but also in the EU, in terms of deceleration equivalent to harsh braking or crashes - there are already standards that at least car manufacturers and AV companies are using

• 01:01:20 Matthew Clark (Steer and CoMoUK): Replying to "If we request data f..."

• Very interesting, thanks for the invite to join.

• 01:02:24 Aylene McCallum (OMF): Replying to "If we request data f..."

• Agencies can required (contractually) that information be accepted and shared in the MDS format. In fact, including that requirement across mobility vendor contracts unlocks more opportunity to better utilize the information being generated by the mobility companies, as well as helping the agency more efficiently disseminate policies (ie; basic traffic/parking regulation) encouraging a more efficient use of the right of way

• 01:02:30 Pierre Bouffort (Blue Systems): We have some experience integrating data from food delivery companies through workarounds but these companies have not yet shared to us through MDS

• 01:03:07 Nivel | Harald, Antonia, Maroof: Reacted to "Matt if an agency re..." with 👍

• 01:03:22 Pietro Peyron (Populus): Thanks for the informative meeting!

• 01:04:03 Michael Schnuerle (OMF): MDS 2.1 https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev

• 01:04:13 sondre Vasseng: Replying to "Permit language an..."

• We should also be on this list :D

• 01:04:39 Alia Verloes (Blue Systems): Reacted to "We have some exper..." with ❤️

• 01:04:47 Alia Verloes (Blue Systems): Thank you all!

Transcript

Click to view full meeting transcript

1 00:00:12.060 --> 00:00:25.940 Michael Schnuerle (OMF): Good afternoon, everyone. Welcome to our monthly MDS working group meeting. Today, we're going to focus on European engagement around MDS and a review of 2.1 for the European audience, so…

2 00:00:26.020 --> 00:00:33.060 Michael Schnuerle (OMF): I thank you all for attending. My name is Michael Schnurle. I'm the Director of Open Source Operations for the OMF.

3 00:00:33.380 --> 00:00:39.910 Michael Schnuerle (OMF): And we have a packed agenda for today, lots of information to cover, so we'll go ahead and get started.

4 00:00:42.440 --> 00:01:01.870 Michael Schnuerle (OMF): If you could, a little bit of housekeeping. Set your name and your organization after your name in the participant list, so we know who you're representing, and that really helps with note-taking later as well. Mute yourself for now, but feel free to introduce yourself in the chat, who you are, where you're from, why you're here.

5 00:01:02.620 --> 00:01:20.180 Michael Schnuerle (OMF): And then, for this meeting, as we go along, use the chat to leave questions as we go, and then we will have, I'm hoping for about 20 minutes of Q&A towards the end, and that's when you can raise your hand and share verbal questions, and we can have a discussion.

6 00:01:21.050 --> 00:01:27.140 Michael Schnuerle (OMF): This meeting is being recorded and will be published with notes to the MDS mailing list.

7 00:01:29.490 --> 00:01:49.220 Michael Schnuerle (OMF): We'll do some quick announcements, and then the first half of the meeting will be me basically reviewing what is MDS for some of you who may not be as familiar with it as others, but the bulk of the meeting will be reviewing the 2.1 features that are coming to get your opinion and feedback

8 00:01:49.250 --> 00:02:01.390 Michael Schnuerle (OMF): on anything that you see that might be applicable or not applicable to you and your audience and your residents. And then, at the end, feedback and questions from you all in the audience.

9 00:02:03.360 --> 00:02:10.539 Michael Schnuerle (OMF): So, first, a little bit of an introduction about the OMF. We're a global nonprofit created in 2019.

10 00:02:10.910 --> 00:02:14.680 Michael Schnuerle (OMF): And we were created to support cities and industry collectively.

11 00:02:14.860 --> 00:02:33.989 Michael Schnuerle (OMF): on digital transformation of the transportation arena. It's city-founded and city-led, supported by the private sector, and we want to help cities and companies work together to get to yes, and we provide this forum, like meetings here, to solve problems and identify solutions together.

12 00:02:34.170 --> 00:02:53.130 Michael Schnuerle (OMF): Everything we do is built in the open. It's open source, free-to-use data specifications and resources, a lot of participation around the world from individuals and different companies and agencies, and this helps build an ecosystem of a market for solutions for everybody.

13 00:02:53.640 --> 00:03:01.900 Michael Schnuerle (OMF): And everything is done publicly in the open, online, on GitHub, using open source tools and public meetings like this one.

14 00:03:02.780 --> 00:03:13.269 Michael Schnuerle (OMF): So today we're focusing on the mobility data specification. This is a digital data standard that enables right-of-way or public space regulation.

15 00:03:13.640 --> 00:03:23.519 Michael Schnuerle (OMF): And includes things like digital policy, geofencing, and two-way communication and data sharing between mobility companies and public agencies worldwide.

16 00:03:23.670 --> 00:03:33.940 Michael Schnuerle (OMF): On the right, we have an annual voting process with our members to elect steering committee members. You can see who our current steering committee members are there.

17 00:03:34.350 --> 00:03:37.690 Michael Schnuerle (OMF): And today we'll talk about 2.1 in a little more detail.

18 00:03:39.190 --> 00:03:50.799 Michael Schnuerle (OMF): We have over 80 members. This is a sampling of some of the public sector members, and I highlighted a few of the European ones with circles, so you can sort of see

19 00:03:50.930 --> 00:03:58.310 Michael Schnuerle (OMF): a sampling of that. There are more in both, around the world and in Europe than what you see here, and they're on our website.

20 00:03:59.940 --> 00:04:08.820 Michael Schnuerle (OMF): And then we also have commercial members, Premier and Associates, so we'd really like to thank all of you for being commercial members.

21 00:04:09.030 --> 00:04:13.729 Michael Schnuerle (OMF): A number of these members are new as of this month.

22 00:04:15.720 --> 00:04:21.620 Michael Schnuerle (OMF): I'm gonna let… if anyone… Aileen or Andrew, if you want to just call out the new members real fast?

23 00:04:22.040 --> 00:04:22.600 Michael Schnuerle (OMF): Yeah.

24 00:04:22.600 --> 00:04:40.880 Aylene McCallum (OMF): Yeah, I wanted to… I'll call out, Novell. You know, Harold from Novell is fun and really helped promote the working group meeting today, so thank you to Novell for your investment and partnership. We're so excited to have you officially join and support our work.

25 00:04:40.880 --> 00:04:54.539 Aylene McCallum (OMF): Another member, new member that just joined is Zoox. On my screen, it's cut out a little bit at the bottom. I don't know if it is for you two, but, Zoox is an autonomous vehicle company.

26 00:04:54.540 --> 00:05:09.120 Aylene McCallum (OMF): Similar to Waymo, and so they just joined the OMF as well. So thank you to those two, call-outs, and then thank you to all of our members. We appreciate all the support and investment that you, you make.

27 00:05:10.530 --> 00:05:13.440 Michael Schnuerle (OMF): Thank you, Aileen. Is it cut off for anyone else at the bottom?

28 00:05:15.970 --> 00:05:22.480 Andrew Glass Hastings (OMF): It was just cut off because of the zoom bar. The actual screen is not cut off. It shows fine, Michael.

29 00:05:22.860 --> 00:05:23.350 Michael Schnuerle (OMF): Okay.

30 00:05:23.350 --> 00:05:25.420 Aylene McCallum (OMF): Or error on my end, sorry.

31 00:05:25.420 --> 00:05:27.490 Michael Schnuerle (OMF): No, no, that's okay, thanks for…

32 00:05:27.490 --> 00:05:29.509 Andrew Glass Hastings (OMF): The zoom menu, yeah, pops up.

33 00:05:31.110 --> 00:05:46.340 Michael Schnuerle (OMF): All right, we'll continue on. Thank you to our public and private sector members. And because of all of our members and the use of MDS, MDS is a global data standard. You can see a world map here and zoom in on Europe of where

34 00:05:46.340 --> 00:05:51.620 Michael Schnuerle (OMF): MDS is used, the different circle sizes represent OMF members.

35 00:05:51.620 --> 00:06:00.109 Michael Schnuerle (OMF): confirmed to OMF use, and then the smaller dots are actually suspected MDS use, because it's open source. We can't always tell where it is, but we have

36 00:06:00.430 --> 00:06:02.470 Michael Schnuerle (OMF): Pretty good authority that,

37 00:06:02.750 --> 00:06:14.149 Michael Schnuerle (OMF): MBS is used by 200 commercial mobility service providers around the world, and these companies operate in over 1,200 cities and dozens of countries around the world.

38 00:06:14.370 --> 00:06:19.740 Michael Schnuerle (OMF): And we know of at least 2 billion trips taken and tracked with MDS.

39 00:06:21.660 --> 00:06:39.530 Michael Schnuerle (OMF): We also have an OMF calendar, if someone could… from staff could share the link to the calendar, this tracks all of our… all of our public-facing events and conferences and things like that, but also a little bit of our internal member events as well, so you can see when they're happening.

40 00:06:41.440 --> 00:06:53.510 Michael Schnuerle (OMF): And now, as we get through that introduction, please take a moment, introduce yourself in the chat. I see a lot of people doing that already, but I'd like to know, how did you end up here today? You can just…

41 00:06:53.680 --> 00:07:01.030 Michael Schnuerle (OMF): put these letters ABCDE in there. Are you curious about MDS? Someone suggested you were here.

42 00:07:01.210 --> 00:07:14.209 Michael Schnuerle (OMF): someone required you to be here, maybe, or it's your job to understand this, and… or you just want to support the OMF, and feel free to leave other options if you… if there are any that you don't see here.

43 00:07:21.720 --> 00:07:30.760 Michael Schnuerle (OMF): And we know that everyone comes to MDS from different starting points, so we're really curious how everyone arrived here, and

44 00:07:30.980 --> 00:07:36.019 Michael Schnuerle (OMF): Where you're headed with it, which is what we'll get into in the next part of the meeting.

45 00:07:38.650 --> 00:07:45.639 Michael Schnuerle (OMF): Alright, I'm gonna move on. I could see a lot of great responses in the chat. A, B, C, D, and E, all over.

46 00:07:48.950 --> 00:07:51.339 Michael Schnuerle (OMF): A lot of D's, which is… is good.

47 00:07:52.110 --> 00:07:57.380 Andrew Glass Hastings (OMF): One or two, one or two comments there about my boss signing me up, which is, you know, hey, you know, that works too.

48 00:07:57.380 --> 00:07:57.910 Michael Schnuerle (OMF): Yeah.

49 00:07:58.400 --> 00:08:04.179 Michael Schnuerle (OMF): Great. And welcome, Andrew. Do you want to give a little bit of overview for the… for this audience?

50 00:08:04.490 --> 00:08:12.170 Andrew Glass Hastings (OMF): Yeah, of course, Michael, thanks. And welcome, everyone. Thanks for joining us on this MDS Working Group for Europe.

51 00:08:12.240 --> 00:08:30.790 Andrew Glass Hastings (OMF): I want to thank you all, first of all, for being here, and just mention, you know, a little bit what Michael said is, you know, MDS is a global standard. It's used by cities, mobility operators, technology companies around the world, as you saw from that map.

52 00:08:30.880 --> 00:08:49.520 Andrew Glass Hastings (OMF): But it's used not because it's required, or there's some higher authority requiring its use, it's used because it works. Because there was a recognized problem or challenge or opportunity. Cities and their technology partners used MDS to address it.

53 00:08:49.830 --> 00:09:00.270 Andrew Glass Hastings (OMF): But the standard is really only as good as the community that contributes to it and that stewards it, and that's really what this working group is all about.

54 00:09:00.350 --> 00:09:19.069 Andrew Glass Hastings (OMF): an effort to really keep MDS up to date with the evolving needs of cities and their technology partners. As mobility continues to rapidly change, we want to make sure that MDS stays relevant and stays a tool that you use because it works.

55 00:09:19.070 --> 00:09:25.589 Andrew Glass Hastings (OMF): And that's what these working groups are all about. So, thank you for taking the time and being here. This is…

56 00:09:25.770 --> 00:09:36.249 Andrew Glass Hastings (OMF): what we hope the first of a series of working groups that are focused on the European community, really intentionally trying to bring

57 00:09:36.250 --> 00:09:50.130 Andrew Glass Hastings (OMF): European cities and companies and organizations together around the ongoing stewardship of MDS. Because we need to make sure that this standard, if it's going to continue to be global, works.

58 00:09:50.130 --> 00:10:02.300 Andrew Glass Hastings (OMF): for cities in all parts of the world. I fundamentally believe, in my experience working for cities and working with cities in different parts of the world, that cities have far more in common than not.

59 00:10:02.300 --> 00:10:10.270 Andrew Glass Hastings (OMF): You know, despite what's happening at our national or supernational politics, you know, cities are where the work gets done.

60 00:10:10.380 --> 00:10:24.260 Andrew Glass Hastings (OMF): And the work that you all do has direct impact on your communities, on the populations in those communities, and that, you know, whether cities in North America, Europe, or beyond are facing many of the same challenges.

61 00:10:24.410 --> 00:10:28.829 Andrew Glass Hastings (OMF): Whether it's from, you know, the challenges of climate.

62 00:10:28.830 --> 00:10:52.899 Andrew Glass Hastings (OMF): or equity, or the pressures of, you know, just ongoing urbanization. Innovation has opportunities, but also challenges with it, and that's why we want to make sure that MDS stays up-to-date and relevant through that. So I look forward to continuing to work with all of you as we move forward and advance MDS. We're going to hear about a lot of great

63 00:10:52.900 --> 00:10:58.260 Andrew Glass Hastings (OMF): upcoming changes to MDS as a part of the 2.1 exploration today.

64 00:10:58.260 --> 00:11:12.319 Andrew Glass Hastings (OMF): And huge thanks to, you know, many of our partners here on the call. Also, big thanks to Polis for being a really strong partner for the Open Mobility Foundation in Europe specifically.

65 00:11:12.320 --> 00:11:19.690 Andrew Glass Hastings (OMF): And, look forward to future, conversations, related to the MDS Working Group for Europe. Alright, Michael, thanks.

66 00:11:20.100 --> 00:11:34.019 Michael Schnuerle (OMF): Thank you, Andrew, and thanks for mentioning Polis. We have Karen here from Polis, and Karen, if you'd like to talk a little bit about Polis and how it overlaps with the work we do here at OMF.

67 00:11:35.250 --> 00:11:47.840 Karen Vancluysen: Yes, thank you, Michael. Hi, Andrew. Hi, Arlene. And hi, everyone. Nice to be here, and happy to see this workshop happening for the European audience. So, I'm Karen Van Klauser, the Secretary General of Polis.

68 00:11:47.840 --> 00:12:12.820 Karen Vancluysen: the European Network of Cities and Regions working together on sustainable mobility and innovation, and very happy to see, as well, many of our member cities in the room as well. And of course, the Open Mobility Foundation itself is also an associate member of the Polis Network, so we have been working together for quite a while in the meantime. And that's also because we believe in each other, let's say, so I put E also as…

69 00:12:12.820 --> 00:12:36.770 Karen Vancluysen: love the OMF, and I want to support them in the poll. Why is that? Because, of course, we've seen shared micromobility come to our city streets here in Europe as well a couple of years ago, and we saw that we needed proper tools to regulate these new services in a way that we can capitalize on their opportunities, but also mitigate possible negative externalities.

70 00:12:36.770 --> 00:13:01.719 Karen Vancluysen: And they generate a lot of data, and that brings a lot of potential as well. But also, we saw that there is a digital divide between the public and the private sector, and the lack of skills still on the side of the public sector in terms of making good use of that data. And that's where MDS also comes in, and is really, really helpful for cities to use that data to inform policy, to enforce policy, also to

71 00:13:01.720 --> 00:13:21.029 Karen Vancluysen: policies, and to have this good exchange between the public and the private sector in a way that is a win-win for both sides. There were some efforts at some point to come up with a European alternative for MDS, which is a U.S. data specification by Origin.

72 00:13:21.030 --> 00:13:43.879 Karen Vancluysen: But very soon, it also became clear that there was no point in reinventing the wheel, even more so, because in the meantime, also, MDS is fully GDPR compliant. So, we're all in favor, also, of joining forces and capitalizing on each other's strength, and as Andrew was saying, European and American cities have a lot of challenges in common, so it only

73 00:13:43.880 --> 00:13:49.539 Karen Vancluysen: It's a good thing to work together and make each other stronger.

74 00:13:49.590 --> 00:14:03.240 Karen Vancluysen: urban space is a very scarce and very valuable resource, and MDS is a very good tool to manage that urban space in a more effective way. And while, with shared micromobility, we have been maybe

75 00:14:03.240 --> 00:14:15.939 Karen Vancluysen: reactive rather than proactive, but we're trying to catch up. I think it's very important for the next innovations that are coming to our city streets to really be more proactive, and MDS can really help with that, because the next

76 00:14:15.940 --> 00:14:38.489 Karen Vancluysen: big thing coming our way, and it has already happened in the US, is automation and AVs. So how are we going, again, to regulate in a way that we embrace opportunities, but also really, really make sure that we mitigate negative side effects? And what is happening in the US can be very informative that way, and I'm very happy to see that MDS is also moving

77 00:14:38.490 --> 00:14:40.330 Karen Vancluysen: In… in that direction.

78 00:14:40.330 --> 00:14:54.200 Karen Vancluysen: So, we also have a tutorial series that is currently running within POLIS with the support of the OMF, to help our members understand the potential of data specifications, such as MDS, but also CDS, the curb data specification.

79 00:14:54.200 --> 00:15:06.769 Karen Vancluysen: to help build the skills and to really fully embrace the potential of these data specifications. So I wish you all a successful workshop, and I look forward to continuing the cooperation.

80 00:15:06.770 --> 00:15:07.170 Karen Vancluysen: Thanks.

81 00:15:08.500 --> 00:15:19.790 Michael Schnuerle (OMF): Thank you so much, Karen, and thank you for your partnership over the years. We love participating in your tutorial series, and I think it's been really valuable for everybody.

82 00:15:19.880 --> 00:15:36.019 Michael Schnuerle (OMF): There's a lot of other things we've been doing in Europe. This first six things here are things we've done just in the month of March with Europe and MDS. The Pulse tutorial series is one of them, but also our team was in Amsterdam for intertraffic, and…

83 00:15:36.020 --> 00:15:53.970 Michael Schnuerle (OMF): We were part of a EIT Urban Mobility Workshop there, and we had a mixer in Amsterdam, and we had a deep dive with the City of Amsterdam for crash and incident data, which I'll mention later. And then, of course, this meeting. And this isn't the first time we've been involved in Europe. Here's a few events that

84 00:15:54.080 --> 00:15:56.899 Michael Schnuerle (OMF): We're more recent, but we definitely have

85 00:15:57.110 --> 00:16:00.860 Michael Schnuerle (OMF): Connected with Europe dozens of times over the years in person.

86 00:16:02.950 --> 00:16:15.739 Michael Schnuerle (OMF): Alright, so I'm going to do a little bit of an MDS overview. I'm going to go relatively quickly through this, assuming that most of you understand what MDS is, basically.

87 00:16:15.860 --> 00:16:19.429 Michael Schnuerle (OMF): There's a lot of resources online if you want to try to catch up later.

88 00:16:19.850 --> 00:16:22.180 Michael Schnuerle (OMF): And I'll also point out that

89 00:16:22.410 --> 00:16:30.970 Michael Schnuerle (OMF): Just thinking about how this section's gonna go in the next section, I anticipate we might go over time, and so as we get to the Q&A later.

90 00:16:31.370 --> 00:16:40.819 Michael Schnuerle (OMF): I will stay here, and anyone else who wants to stay beyond the hour can stay and continue asking questions until they're resolved, so we'll make sure we get to those.

91 00:16:42.150 --> 00:16:53.109 Michael Schnuerle (OMF): So, MDS is a two-way data standard between the private and the public sector, and it supports all the types of modes and vehicles and services that you see here.

92 00:16:53.170 --> 00:17:06.200 Michael Schnuerle (OMF): along the categories of micro-mobility, passenger, fleet, and delivery. And we'll dig a little bit into some of these later. But it's very robust, although it started here with scooters and bike share.

93 00:17:06.270 --> 00:17:14.439 Michael Schnuerle (OMF): It really covers a broad range of shared and owned mobility services across the public space.

94 00:17:16.380 --> 00:17:17.970 Michael Schnuerle (OMF): So, data…

95 00:17:18.310 --> 00:17:34.280 Michael Schnuerle (OMF): from MDS can be provided to cities. That's part of that two-way communication. Cities can write data sharing requirements into their permits for services in the public realm, and this includes information, and all of this is… can be made optional as you need it for your program, but

96 00:17:34.280 --> 00:17:50.780 Michael Schnuerle (OMF): Vehicle location and status, vehicle information, the details of certain trips, including breadcrumbs, if you'd like that, and then details about stops. And this is just a quick overview of what's possible. There's a lot of data when you dig into it beyond this.

97 00:17:51.580 --> 00:18:06.139 Michael Schnuerle (OMF): An example of this, CRove, Crow, as I say, in the Netherlands, has a nationwide shared micromobility dashboard using MDS data.

98 00:18:06.140 --> 00:18:15.400 Michael Schnuerle (OMF): And so they work with about two dozen cities across the nation to collectively aggregate all the MDS data that comes in.

99 00:18:15.440 --> 00:18:32.970 Michael Schnuerle (OMF): from bikes and scooters, and aggregates it into this nationally funded dashboard for all the cities to use. And they also, interestingly, have a public-facing data quality dashboard from each of the operators, so…

100 00:18:32.970 --> 00:18:40.439 Michael Schnuerle (OMF): If you're curious, for instance, how your operator might perform in your city with… as far as compliance and,

101 00:18:40.630 --> 00:18:47.560 Michael Schnuerle (OMF): update times and correct use of the data standards, like MDS. Also, GBFS is on here.

102 00:18:48.060 --> 00:19:02.440 Michael Schnuerle (OMF): You can look at the rankings for these different companies, and I think this is a really great feature that, they… and also, Villanova is another company that has a public-facing dashboard like this in Europe, which is great.

103 00:19:03.180 --> 00:19:20.059 Michael Schnuerle (OMF): The other side of MDS is digital policy and operating rules and geofencing. So, MDS allows you to take what might have been in a PDF or a document about all your rules of data sharing and geofencing.

104 00:19:20.130 --> 00:19:33.219 Michael Schnuerle (OMF): And then I turn that into a digital version that's easily machine-readable, but also very clearly defined, so it's… it's not so up in the air what you mean when you talk about these things in your permit.

105 00:19:33.260 --> 00:19:44.019 Michael Schnuerle (OMF): And everyone's on the same page. And also for… instead of, say, sending an email to a company about, oh, we're gonna have this event, or there's an emergency, or don't go here.

106 00:19:44.020 --> 00:19:54.790 Michael Schnuerle (OMF): you can also turn all of that into MDS and publish that as well. So that's the other side of the two-way data sharing, so that cities can inform operators what's happening on the ground.

107 00:19:56.020 --> 00:20:11.070 Michael Schnuerle (OMF): And a little bit of a technical view, but this is how we name different things within MDS in version 2.0. We have data coming from operators through our provider and agency endpoints, which is just really push or pull how the data gets moved.

108 00:20:11.070 --> 00:20:19.109 Michael Schnuerle (OMF): And then a lot of data from cities to the operators around digital policy, geography, aggregated metrics, and then jurisdiction definitions.

109 00:20:21.480 --> 00:20:35.740 Michael Schnuerle (OMF): An example of this two-way sharing comes from Navelle, which is, this is… they operate in Bergen, but many other places as well. And, you can see in this picture, they have a software tool as a vendor for

110 00:20:35.740 --> 00:20:52.970 Michael Schnuerle (OMF): cities, and using MDS to push policies out to a digital version of the right-of-way, and then getting vehicle data back, from… through MDS back to their platform for these different cities. And they work in micromobility, car sharing, logistics, carpooling, and autonomy as well.

111 00:20:57.750 --> 00:21:09.800 Michael Schnuerle (OMF): We do have a database of use cases, so if you're unsure how to use MDS, we have a use case database that you can pull from for over… with over 60 documented use cases for MDS.

112 00:21:09.800 --> 00:21:19.250 Michael Schnuerle (OMF): And it also specifies a little bit about what parts of MDS would be beneficial if you want to meet that use case for your need for the public benefit.

113 00:21:20.630 --> 00:21:31.709 Michael Schnuerle (OMF): And then a little bit about privacy. So, we have a defined data flow that… in this picture shows sort of what's in a vehicle or a commercial app.

114 00:21:31.780 --> 00:21:41.930 Michael Schnuerle (OMF): And then what the company gets from that app, so you can see they get a lot of information about riders and vehicle data, trip data, financial data, transactions. But really.

115 00:21:42.050 --> 00:21:54.099 Michael Schnuerle (OMF): a subset of that comes through the company to the city through MDS, and it's really just vehicle and trip data. We intentionally don't have transactional data or rider data.

116 00:21:54.190 --> 00:22:08.730 Michael Schnuerle (OMF): And then the city can use that and maybe publish some aggregated reports to the public. But this is… this is sort of the data flow, and it's a bit of a funnel down from what the companies have to what the cities are able to see.

117 00:22:08.830 --> 00:22:12.020 Michael Schnuerle (OMF): We have a lot of different,

118 00:22:12.470 --> 00:22:21.500 Michael Schnuerle (OMF): resources on… on privacy, but also specifically GDPR. We have very detailed guidance on this.

119 00:22:21.580 --> 00:22:34.659 Michael Schnuerle (OMF): It's a… we had a review by a lawyer in Europe, and this is something like 70 pages of detailed guidance, if you want to get into it in that detail, but it answers common questions about

120 00:22:34.900 --> 00:22:50.730 Michael Schnuerle (OMF): how to process MDS data, what do you need to do with riders, how do MDS… how do you handle erasure requests, but like Karen said for COLUS, yes, MDS is fully allowed to be used under GDPR, and I think the key there, as long as you have the use cases for it.

121 00:22:52.270 --> 00:23:09.260 Michael Schnuerle (OMF): And we have a bunch of other privacy resources as well, a city guidance guide, under GDPR, but general privacy guide as well, and different principles for mobility data sharing and a state of practice from our privacy and Transparency Committee.

122 00:23:09.710 --> 00:23:23.129 Michael Schnuerle (OMF): And then the last thing I want to point out in this intro of MDS is we have also another data standard called CDS, the curb data specification, and just to communicate here what the difference is, the overlap.

123 00:23:23.160 --> 00:23:42.709 Michael Schnuerle (OMF): So MDS is really about understanding vehicle locations, their status, incidents that happen with those vehicles, and the trips taken. And so that's the movement around your entire public space. CDS is more about the physical definition of infrastructure, the location of different objects in the right… in the public space in the right-of-way.

124 00:23:42.770 --> 00:23:58.590 Michael Schnuerle (OMF): and activity tracking in relationship to those physical curb zones, objects, and other areas that are defined. And so you can think of CDSs, defining the public space, and MDS as monitoring vehicle movements in there.

125 00:24:00.090 --> 00:24:05.979 Michael Schnuerle (OMF): But they both have digital policy, data sharing, and metrics, and they can be used independently or cooperatively.

126 00:24:07.570 --> 00:24:26.800 Michael Schnuerle (OMF): So if you want to learn more about this, if you're an OMF member, we do have an OMF Academy for OMF members. We had two already on Digital Infrastructure 101, but upcoming, we have CDS 101 and MDS 101 sessions. You'll learn a lot about the who, what, where, why, and how.

127 00:24:26.950 --> 00:24:34.849 Michael Schnuerle (OMF): of MDS and CDS, so if you're interested, reach out to us, and Aileen can help get you registered for those.

128 00:24:36.840 --> 00:24:46.379 Michael Schnuerle (OMF): And so, another quick engagement in the chat, if you… if you're using MDS, or if you're thinking about it, what does MDS mean to you? You could just put a word or two.

129 00:24:46.660 --> 00:24:53.300 Michael Schnuerle (OMF): How… how do you think about MDS in your… with your company, with your city, with your agency?

130 00:25:06.230 --> 00:25:09.949 Michael Schnuerle (OMF): All right, and as you're… please continue to write those responses.

131 00:25:10.850 --> 00:25:17.520 Michael Schnuerle (OMF): And now, I'm going to get into MBS 2.1, so I'll give a little bit of background and then talk about the specific features.

132 00:25:18.760 --> 00:25:37.729 Michael Schnuerle (OMF): So this is a chart of MDS releases over time, and this… these bars represent how long we took to develop and publish and approve the releases. So, we are here at 2.1, and it's been over a thousand days of working on this, so we've been working on this for about two to three years.

133 00:25:37.820 --> 00:25:57.290 Michael Schnuerle (OMF): And, it's our longest release, and the releases are… seem to be getting longer, and part of that is intentional. We wanted to only do releases when there was a need for it and a demand from the public and private sectors. And so, that is why you see this sort of thoughtful consideration of each release and time spent on it.

134 00:25:59.350 --> 00:26:15.290 Michael Schnuerle (OMF): We have a release plan for 2.1, and this has been public since we started working on it. It's a timeline of everything. You can see seven high-level features here, which we will get into in detail. But we are now in the sort of March time period.

135 00:26:15.350 --> 00:26:26.210 Michael Schnuerle (OMF): of European focus and feedback, but after this, we will start the approval process for approving it in our… using our bylaws. We have a structure of

136 00:26:26.460 --> 00:26:37.339 Michael Schnuerle (OMF): of the OMF, we are here down at the MDS Working Group. We also have the Curb Working Group and different events that are public-facing, and then everything above here is for members.

137 00:26:37.360 --> 00:26:56.840 Michael Schnuerle (OMF): We have a steering committee, which I mentioned for MDS, but also for CVS. We have member networks, and then these different committees made up of members that roll up to the board, strategy, technology, privacy, and advisory committees, and then the board. And so, for approving a release, we start with the working group and the working group steering committee.

138 00:26:56.840 --> 00:27:03.359 Michael Schnuerle (OMF): to make what we call a release candidate for the release, which then gets recommended to our technology council, which is mostly

139 00:27:03.420 --> 00:27:06.600 Michael Schnuerle (OMF): Private sector companies, majority private sector.

140 00:27:06.760 --> 00:27:14.380 Michael Schnuerle (OMF): And then, once they approve it, it will go to our board of directors for final review and approval.

141 00:27:14.920 --> 00:27:17.549 Michael Schnuerle (OMF): And then it officially becomes the latest version.

142 00:27:18.660 --> 00:27:36.859 Michael Schnuerle (OMF): So, in 2.1, we have a number of new features. We have a mode… overhaul of modes, and I want to get into each of these with their own slides. We have incidents and crashes, a way to capture unplanned stops, remote takeovers, crashes, theft, vandalism, near misses, harsh braking or acceleration.

143 00:27:37.040 --> 00:27:53.099 Michael Schnuerle (OMF): We have delivery, which is all types of delivery of goods, foods, packages, and freight. Some transit updates, some for-hire autonomous vehicle features, and more clearly defining

144 00:27:53.100 --> 00:28:00.659 Michael Schnuerle (OMF): how MDS could be used for those, real-time digital policy, even better than it was before, and enforcement and violations.

145 00:28:00.660 --> 00:28:05.669 Michael Schnuerle (OMF): And then a lot of other additional features that you can get into when you look online.

146 00:28:05.760 --> 00:28:10.090 Michael Schnuerle (OMF): And our GitHub page, and our release notes, and our release plan.

147 00:28:10.290 --> 00:28:14.769 Michael Schnuerle (OMF): You can see some of these things here. Some of these are a little more…

148 00:28:15.100 --> 00:28:21.769 Michael Schnuerle (OMF): I guess, technical, but also just operational minor changes, but we wanted to document them.

149 00:28:23.520 --> 00:28:40.630 Michael Schnuerle (OMF): All right, so in MDS 2.0, which is sort of the visual you're seeing here, we did have these modes. We did have the sense of micromobility, and passenger services and fleet vehicles, and delivery vehicles. But they were really focused on specific types of these things, so…

150 00:28:40.630 --> 00:28:50.399 Michael Schnuerle (OMF): Delivery was really just delivery robots, and we didn't really define necessarily all the sorts of modes that could go into this two-way data sharing.

151 00:28:50.400 --> 00:28:56.819 Michael Schnuerle (OMF): So, for MBS 2.1, we've added this visual of a lot of different types of

152 00:28:56.840 --> 00:29:01.510 Michael Schnuerle (OMF): Vehicles within each of these modes, as we call them.

153 00:29:01.530 --> 00:29:15.519 Michael Schnuerle (OMF): And then, as you saw prior, more of a breakdown, a text version of what it means to be a delivery vehicle. This includes, for instance, with delivery robots, but also app delivery and packages, freight goods and food.

154 00:29:15.520 --> 00:29:21.800 Michael Schnuerle (OMF): For fleets, it could be car share, which is what it started as, but also your city fleets, or sanitation.

155 00:29:21.800 --> 00:29:34.949 Michael Schnuerle (OMF): vehicles, rentals, car rentals, things like that, street sweepers. And then passenger services wanted to make sure it was clear that it was about taxis, and maybe robo-taxis as well.

156 00:29:35.080 --> 00:29:44.679 Michael Schnuerle (OMF): Buses, TNCs like Uber and Lyft, different shuttles, paratransit, on-demand services, etc, and of course, all of micromobility.

157 00:29:47.100 --> 00:30:02.320 Michael Schnuerle (OMF): So let's get into these high-level features for 2.1. The first one we want to talk about is incidents and crashes. So, this is a new area in MDS. It's basically its own separate endpoint, as we call it, within one of the APIs.

158 00:30:02.320 --> 00:30:26.519 Michael Schnuerle (OMF): And it can capture anything related to any of the modes, related to an unplanned stop of any type. A remote takeover, if you're talking about a, let's say, a delivery robot or an autonomous vehicle. Similarly, ADS disengagements or engagements. It could also, if the vehicles have the capability, detect harsh braking and acceleration incidents.

159 00:30:26.520 --> 00:30:33.809 Michael Schnuerle (OMF): Which can be sent back to the cities. Tip-overs, like in the case of scooters, any sort of vandalism that can be recorded.

160 00:30:33.900 --> 00:30:45.400 Michael Schnuerle (OMF): And, theft, near misses as well, so maybe you can detect that, like a lot of, for hire AVs can do. And then collisions as well. And collisions is maybe…

161 00:30:45.450 --> 00:30:57.950 Michael Schnuerle (OMF): It's actually where we started with this back in 2021, when B&OVA first recommended this, but we didn't think that… the mobility companies actually didn't think that they had the ability to send that information.

162 00:30:57.970 --> 00:31:19.520 Michael Schnuerle (OMF): But now, many of them do, especially when we get into the autonomous realm. So, we started with collisions and then talked with cities and companies about what's possible and what we'd like to see in MDS. And for each of these things, you get information about location, date, time, severity, if there was a medical response, accelerometer data before and after the incident.

163 00:31:19.520 --> 00:31:27.410 Michael Schnuerle (OMF): And then more detailed information through a report ID that can also be sent, and then you can look in another system for details of that report.

164 00:31:27.580 --> 00:31:38.859 Michael Schnuerle (OMF): And it connects to the basic MBS telemetry points, which includes time and location of the vehicles, and whether they're on a trip, and it supports all modes.

165 00:31:38.910 --> 00:31:54.389 Michael Schnuerle (OMF): This will be the first time you guys are seeing in this meeting what it looks like in the code, but basically, you know, for incidents here, there's a definition of what all these things are, and the different fields, and timestamps, and

166 00:31:54.490 --> 00:31:59.449 Michael Schnuerle (OMF): how to define this in MDS like we do, and so this is available.

167 00:32:02.150 --> 00:32:09.449 Michael Schnuerle (OMF): So, if you have questions about this, maybe write it down, and we'll get… we'll hit it in the Q&A.

168 00:32:09.690 --> 00:32:15.679 Michael Schnuerle (OMF): But for now, this is, what we're going to talk about. I'll share an example of this. So, in the city of Amsterdam.

169 00:32:16.190 --> 00:32:29.170 Michael Schnuerle (OMF): They are receiving not only crashes, but also near-miss information and harsh braking information from Cowboy, a private bike

170 00:32:29.190 --> 00:32:42.490 Michael Schnuerle (OMF): operator, and they're getting this data and putting it into a dashboard, and using it to make infrastructure improvements, even before an actual crash happens. And so they're… they have this… this great dashboard, and

171 00:32:42.510 --> 00:32:55.799 Michael Schnuerle (OMF): great use of the information, and they intend to adopt MDS 2.1 incident and crash endpoint once it's approved. So, I just want to share this great example from Amsterdam.

172 00:32:57.660 --> 00:33:04.670 Michael Schnuerle (OMF): Alright, the next feature just to talk about is delivery. So, it used to be that we had delivery robots.

173 00:33:05.000 --> 00:33:14.600 Michael Schnuerle (OMF): was what we focused on. We didn't have, intentionally with 2.1, the idea of a human or remote driver or app deliveries and things like that.

174 00:33:14.600 --> 00:33:37.419 Michael Schnuerle (OMF): But now with, there were many cities that needed this for their regulations, and so we've added all delivery modes, which includes goods, foods, packages, and freight. And it's any kind of delivery you can imagine, basically. And there could be one or more orders that can be tracked along with this on different trips overlapping, or at the same time.

175 00:33:37.420 --> 00:33:40.470 Michael Schnuerle (OMF): Connected with an identifier we have, calling in

176 00:33:40.470 --> 00:33:45.720 Michael Schnuerle (OMF): Journey identifier, and this… you can track the state of these orders separately.

177 00:33:45.720 --> 00:33:51.100 Michael Schnuerle (OMF): from the vehicle state. So there's a lot going on here. So if you think about the realm of delivery.

178 00:33:51.100 --> 00:34:07.179 Michael Schnuerle (OMF): and information about what's happening on deliveries, you can pretty much use many of these optional fields to capture that in your city. This is just an example from the… from the spec of a complex trip example, where

179 00:34:07.310 --> 00:34:10.050 Michael Schnuerle (OMF): Maybe this is an app delivery…

180 00:34:10.130 --> 00:34:25.900 Michael Schnuerle (OMF): And there is a shift of a worker, which is right here, and maybe they've done two routes over their shift, and one of those routes has all these different journeys in it, and these journeys contain different types of trips, like a delivery trip or a return trip.

181 00:34:25.920 --> 00:34:34.000 Michael Schnuerle (OMF): or maybe a maintenance trip, those can all be defined. And within these trips, there are also overlapping orders that can be

182 00:34:34.000 --> 00:34:47.619 Michael Schnuerle (OMF): tracked as well. So you can see this is… this looks complex, but it could actually get a lot more… a lot more detailed than this if you'd like, or even less detailed. You could really just say, just tell me when there's a trip, and a little bit of information about it.

183 00:34:48.480 --> 00:34:51.879 Michael Schnuerle (OMF): And I'll just, show you how this looks in the spec.

184 00:34:53.199 --> 00:34:59.600 Michael Schnuerle (OMF): You can see a lot of different trip types that are defined, delivery, return trips, advertising, mapping, roaming, or testing.

185 00:35:00.030 --> 00:35:09.949 Michael Schnuerle (OMF): And then this is that example I showed, but there's also more simplified, different types of trip examples, and it supports all different types of modes.

186 00:35:11.660 --> 00:35:13.040 Michael Schnuerle (OMF): Within delivery

187 00:35:14.100 --> 00:35:26.709 Michael Schnuerle (OMF): All right, so think about your questions for that later, and like, as well, if you have a question, you can put it in the chat, and our staff will answer it as I'm talking, and then we can follow up with it later if we need to.

188 00:35:29.980 --> 00:35:34.900 Michael Schnuerle (OMF): Yeah, and I'll… I'll mention that… I'll… I'll…

189 00:35:35.170 --> 00:35:52.900 Michael Schnuerle (OMF): point out that I was just a question from Harold from Novell about, is this breaking? I should have mentioned that. So, 2.1 is not a breaking change. It's intentionally a minor release. We're adding things, but not changing or removing things. So if you're on 2.0,

190 00:35:52.900 --> 00:36:09.299 Michael Schnuerle (OMF): and you want to upgrade to 2.1 and not do anything different, you can pretty much just say, okay, now we're on 2.1. But if you want to use 2.1 for some of these new things I'm talking about, then yes, you could upgrade. But otherwise, 2.1 is not a breaking change.

191 00:36:12.080 --> 00:36:16.780 Michael Schnuerle (OMF): And then another, here's an example of delivery from CityFi

192 00:36:16.880 --> 00:36:23.850 Michael Schnuerle (OMF): In Europe, so they have provided a list of cities that they've worked with implementing MDS, or they know of.

193 00:36:23.860 --> 00:36:42.039 Michael Schnuerle (OMF): You can see a list of them here and what they're doing, and specifically calling out this Helsingberg Sweden example, where they had a sidewalk delivery robot pilot, but also it's interesting, it included full delivery, so these large vehicles would come to certain points in a more

194 00:36:42.240 --> 00:36:53.930 Michael Schnuerle (OMF): suburban type of area, and deliver all these packages for then the sidewalk robots to go deliver to specific houses in the area. So it's a combination of delivery.

195 00:36:53.930 --> 00:37:04.829 Michael Schnuerle (OMF): vehicle… large delivery vehicles and smaller sidewalk delivery robots, so that's happening, and we know of sidewalk robots in, probably at least a dozen cities in Europe right now.

196 00:37:04.860 --> 00:37:08.680 Michael Schnuerle (OMF): Where they're already deployed out in public space.

197 00:37:11.090 --> 00:37:23.560 Michael Schnuerle (OMF): Another… a third feature is transit fixed route information, so we already had support for on-demand transit and other… some sort of transit like that, but what we did was we explicitly

198 00:37:23.690 --> 00:37:25.689 Michael Schnuerle (OMF): Connected that to

199 00:37:25.800 --> 00:37:38.560 Michael Schnuerle (OMF): GTFS trips, so if you have a public-facing GTFS feed for a transit service of some sort, which publishes where a bus, for instance, is going to be, and what their schedule is.

200 00:37:38.590 --> 00:37:50.870 Michael Schnuerle (OMF): You can also now get information about operations from MDS to connect those… what was going to happen with GTFS, and even maybe the real-time location of those buses, but also

201 00:37:50.900 --> 00:37:54.649 Michael Schnuerle (OMF): What actually happened on that trip? What happened at each stop?

202 00:37:54.740 --> 00:38:03.780 Michael Schnuerle (OMF): How many passengers got off and on? What GTFS stop was it? Where? Did the trip have to do a detour?

203 00:38:04.020 --> 00:38:15.220 Michael Schnuerle (OMF): or, go around something, or maybe miss the stop, or is late or early. So all of that information is available in MDS, and we have some cities ready to use that as well.

204 00:38:15.380 --> 00:38:17.210 Michael Schnuerle (OMF): I'll just show that.

205 00:38:17.320 --> 00:38:22.760 Michael Schnuerle (OMF): That page, each trip, you can get a lot of different information about a trip here.

206 00:38:22.910 --> 00:38:35.670 Michael Schnuerle (OMF): And then, each mode has specific trip information, but you can see trips can be connected to a GTFS trip ID, optionally, and then the URL of that GTFS feed.

207 00:38:35.780 --> 00:38:37.209 Michael Schnuerle (OMF): If needed.

208 00:38:40.390 --> 00:38:41.240 Michael Schnuerle (OMF): Alright.

209 00:38:42.230 --> 00:38:49.110 Michael Schnuerle (OMF): Another top-line feature is we… MDS 2.1 already supported all kinds of passenger services, including

210 00:38:49.270 --> 00:38:57.670 Michael Schnuerle (OMF): robotaxis for higher AVs, but we really made this more explicit in the spec for this release, 2.1.

211 00:38:57.740 --> 00:39:11.989 Michael Schnuerle (OMF): It also adds what we talked about prior about tracking of special types of incidents for autonomous vehicles, like mapping, testing, unplanned stops, remote takeovers, crashes, near misses, acceleration, etc.

212 00:39:12.130 --> 00:39:26.990 Michael Schnuerle (OMF): And then we clarified the use that cities can broadcast MBS policy as a health situational awareness option in emergencies for autonomous vehicles, specifically in addition to all modes. And so,

213 00:39:27.500 --> 00:39:33.289 Michael Schnuerle (OMF): Just wanna… you can see here where we've done some of that clarification about what is supported.

214 00:39:33.500 --> 00:39:43.609 Michael Schnuerle (OMF): This was a little less defined before, and then more information about implementation differences, and again, all this stuff about different passenger

215 00:39:43.780 --> 00:39:45.409 Michael Schnuerle (OMF): Types of trips.

216 00:39:49.560 --> 00:39:56.409 Michael Schnuerle (OMF): Another big change is real-time policy, so MDS 2.0 and prior

217 00:39:56.480 --> 00:40:05.200 Michael Schnuerle (OMF): Had support for real-time policy, but it was a little cumbersome and could be resource-intensive, the way it was architected.

218 00:40:05.200 --> 00:40:24.120 Michael Schnuerle (OMF): So now it's been updated where, in as fast as one second, you can have a communication of a policy change published and received by any number of operators, which includes things like geofencing changes for emergency response and events. And the way we did that is we added what we call a push endpoint.

219 00:40:24.330 --> 00:40:29.409 Michael Schnuerle (OMF): Policy used to be pull, where the operator would have to check at a certain interval to see what's new.

220 00:40:29.410 --> 00:40:46.919 Michael Schnuerle (OMF): But now, the agency, the public agency, can just push it as soon as it's known. And then, if you do, you still use the pull version, there is a way to filter it down just to get an updated date to see, is this updated, so I don't have to get the whole file at once, only return active.

221 00:40:46.920 --> 00:40:55.089 Michael Schnuerle (OMF): policies, and then some other information about how agencies can manage this with an API key, if they'd like.

222 00:40:55.210 --> 00:41:01.799 Michael Schnuerle (OMF): And some other information about making sure policies are unique, and we added some examples as well.

223 00:41:03.240 --> 00:41:04.399 Michael Schnuerle (OMF): Let's see if we…

224 00:41:04.660 --> 00:41:14.119 Michael Schnuerle (OMF): If we look at the policy, yeah. So here's a new endpoint slash policies, which is POST, and similar, that's a push method.

225 00:41:14.210 --> 00:41:25.479 Michael Schnuerle (OMF): Where, you can push updates as they happen out to the agencies. If you're technical, this will make sense to you. If not, have your tech team or your vendor take a look at this.

226 00:41:27.960 --> 00:41:47.359 Michael Schnuerle (OMF): Example from this is Blue Systems, a European vendor. They are working on, and have developed already emergency geofences for higher AV fleets, and have built it where it's replicable in more cities. And so, when real-time information

227 00:41:47.360 --> 00:42:03.299 Michael Schnuerle (OMF): comes from a dispatch system in a city that automatically gets translated into MDS and can be pushed to AV operational systems that are out in the wild, autonomous vehicles, and so that's an example of a working system that can be adopted from many other cities.

228 00:42:03.300 --> 00:42:08.060 Michael Schnuerle (OMF): They also do delivery robot management, which connects to delivery.

229 00:42:08.060 --> 00:42:21.849 Michael Schnuerle (OMF): And then multi-jurisdictional options for when you have a lot of jurisdictions overlapping, but you want to capture what's happening as a holistic whole. An example for that is London for Blue Systems.

230 00:42:24.350 --> 00:42:30.929 Michael Schnuerle (OMF): And then, second to last feature I want to talk about is enforcement and violations. So there are

231 00:42:30.940 --> 00:42:49.269 Michael Schnuerle (OMF): new struct data structures that didn't exist before for capturing this. You can capture an enforcement incident, so if there is an incident, you can attach to this enforcement action and or a violation, or this can be independent of an incident if you just want to capture it on a trip or something.

232 00:42:49.570 --> 00:43:05.039 Michael Schnuerle (OMF): Now, these can be captured and self-reported by the operators and validated, but sometimes they're… in permit rules, it is required for many operators, especially in the autonomous or robot delivery.

233 00:43:05.230 --> 00:43:23.179 Michael Schnuerle (OMF): realm to report any sort of violations they've done, or incidents that have happened, so they can self-report on this, and it includes incidents like citation ID, any actions taken, warning violations, and then details about those violations, like the code, the name, and the cost.

234 00:43:23.240 --> 00:43:40.810 Michael Schnuerle (OMF): And you can see now these data structures here, and then enforcement one, which has a lot of those things I mentioned, and then connection to multiple violations, if needed, that just provide the code name and the cost, all optional, if that information is available.

235 00:43:43.790 --> 00:43:45.339 Michael Schnuerle (OMF): Alright, and the last thing…

236 00:43:45.490 --> 00:43:59.599 Michael Schnuerle (OMF): is external references. This is a feature where you can tie specific MDS data from any part of MDS, whether it's trips, or vehicle properties, or, policy, or anything.

237 00:43:59.600 --> 00:44:07.390 Michael Schnuerle (OMF): to any other data source that's external to MDS, so it could be an API, like a data standard,

238 00:44:07.520 --> 00:44:20.359 Michael Schnuerle (OMF): like GBFS, GTFS, CDS as well, TOMP, ATEX, etc. So all of these things can be connected at the field level, so you could say, oh, we just had a trip.

239 00:44:20.500 --> 00:44:23.469 Michael Schnuerle (OMF): And it was a transit trip.

240 00:44:23.660 --> 00:44:39.720 Michael Schnuerle (OMF): And it connects to this trip ID over in GTFS, or maybe this Datex ID in the Datex standard, and here's what you can send along. It can also link directly to web pages, documents, or reports, so it doesn't have to be a data standard. So let's say…

241 00:44:39.780 --> 00:44:50.230 Michael Schnuerle (OMF): A trip happened and a permit was used in order to access an area in the city. You could pass along a link to that permit page for more information on that specific trip.

242 00:44:50.330 --> 00:45:07.600 Michael Schnuerle (OMF): And it could be used across events, trips, incidents in MDS. And, here's some examples where you can tie a road closure info to another type of data standard for road closures, or a trip to a CDS

243 00:45:07.660 --> 00:45:12.240 Michael Schnuerle (OMF): A curb zone, or maybe an incident that happened over to a police report.

244 00:45:12.420 --> 00:45:17.310 Michael Schnuerle (OMF): And it gets this information here. So, we…

245 00:45:17.430 --> 00:45:31.930 Michael Schnuerle (OMF): basically, this is identical to what's in CDS, and similarly, enforcement of violations are in CDS as well, the same way, and so we have a consistency there to cross-link things and to record enforcement violations.

246 00:45:33.050 --> 00:45:37.260 Michael Schnuerle (OMF): Alright, so I'm gonna stop there. That's the end of the 2.1 overview.

247 00:45:37.370 --> 00:45:45.239 Michael Schnuerle (OMF): And we have a quick question here with something you might have learned about the OMF or MDS specifically that you didn't already know.

248 00:45:48.740 --> 00:45:53.109 Michael Schnuerle (OMF): And then I am going to start the Q&A.

249 00:45:53.620 --> 00:45:55.470 Michael Schnuerle (OMF): And,

250 00:45:59.740 --> 00:46:02.210 Michael Schnuerle (OMF): We'll put this up here, and…

251 00:46:02.620 --> 00:46:21.799 Michael Schnuerle (OMF): share your thoughts. So I have some prompts here, some example questions, but you can ask the kinds… answer and ask the kinds of questions you'd like. Before we get into the verbal things, is there anything, staff that have been monitoring chat, is there anything that you'd like for me to address or talk about from the chat that isn't resolved yet?

252 00:46:25.610 --> 00:46:27.470 Andrew Glass Hastings (OMF): Michael, I think we're in good shape at the moment.

253 00:46:27.920 --> 00:46:29.160 Michael Schnuerle (OMF): Okay, great.

254 00:46:29.630 --> 00:46:37.860 Michael Schnuerle (OMF): All right, so, feel free to raise your hand or just, unmute and start asking questions if you have anything that you'd like to ask.

255 00:46:42.600 --> 00:46:56.329 Andrew Glass Hastings (OMF): Michael, we've got a… we do have a question from Matthew Clark in the chat, a good one related to AVs, the ability to record AV, you know, violations in MDS.

256 00:46:56.840 --> 00:47:02.580 Michael Schnuerle (OMF): Yeah, I feel like that is… that's something you're… you learned about right, Matthew.

257 00:47:02.580 --> 00:47:03.510 Andrew Glass Hastings (OMF): Right.

258 00:47:03.510 --> 00:47:05.520 Michael Schnuerle (OMF): Yes.

259 00:47:05.520 --> 00:47:06.340 Matthew Clark (Steer and CoMoUK): learning, that's not.

260 00:47:06.340 --> 00:47:12.919 Andrew Glass Hastings (OMF): Good, okay, alright, thanks. I mean, it's a good point, we're happy to cover it again, so… but that's great. Thanks, Matthew.

261 00:47:13.180 --> 00:47:16.440 Michael Schnuerle (OMF): But that resonated strongly with you, potentially, so…

262 00:47:38.590 --> 00:47:50.340 Michael Schnuerle (OMF): Well, if there are not a lot of questions, we don't have to go overtime, we can stick to the schedule, but I'm still going to give people time now to answer some… or to ask some questions, or share your thoughts.

263 00:47:59.070 --> 00:48:01.659 Pietro Peyron (Populus): Hi everyone, I'm Pietro from Populous.

264 00:48:01.760 --> 00:48:06.709 Pietro Peyron (Populus): I have a question that is not really related to the presentation of today, but is a…

265 00:48:07.060 --> 00:48:14.380 Pietro Peyron (Populus): A topic that I think is interesting for all European cities, related to MBS 2.6, probably.

266 00:48:14.630 --> 00:48:17.110 Pietro Peyron (Populus): Which is,

267 00:48:17.310 --> 00:48:26.550 Pietro Peyron (Populus): We are… we usually work with e-scooters, which share micromobility, as, like, we don't have CTD scooters or… or standing e-scooters.

268 00:48:26.970 --> 00:48:41.719 Pietro Peyron (Populus): And in MDS 2.0, you introduced a differentiation, which is creating a little bit of a trouble sometimes, because in some cities, you've got some operators that are still on MDS1, and some others on MDS2.

269 00:48:41.830 --> 00:48:47.849 Pietro Peyron (Populus): And you have seated e-sco… sorry, standing e-scooters and e-scooters as different vehicle types.

270 00:48:48.020 --> 00:48:52.859 Pietro Peyron (Populus): So, it's a very specific question for the EU market.

271 00:48:53.350 --> 00:49:01.819 Pietro Peyron (Populus): Are you planning to address this issue in the next 2.1 release? Is this something that was already on your radars?

272 00:49:01.930 --> 00:49:02.920 Pietro Peyron (Populus): Thank you.

273 00:49:04.020 --> 00:49:05.409 Michael Schnuerle (OMF): Yeah, I would,

274 00:49:05.710 --> 00:49:13.370 Michael Schnuerle (OMF): I'd like to understand more about that issue, if you'd like, so this is maybe educational for everyone as well.

275 00:49:13.520 --> 00:49:26.499 Michael Schnuerle (OMF): We work through any new feature changes or requests through this working group process, like the meetings we're in today, but they initially get captured on GitHub, and I know Populous has opened many issues here.

276 00:49:26.500 --> 00:49:44.669 Michael Schnuerle (OMF): But, you can see there's 23 open discussion areas about things we could add to MDS in the future. And then, Pietro, if you want to add a new feature request here by making a new issue, that'll help really define what you're thinking, and then we can think about how to work it in.

277 00:49:44.920 --> 00:49:48.000 Michael Schnuerle (OMF): to a future release. Does that make sense?

278 00:49:49.270 --> 00:49:50.710 Pietro Peyron (Populus): Yes, thank you.

279 00:49:52.830 --> 00:49:55.530 Michael Schnuerle (OMF): And I'll also point out… yes, go ahead.

280 00:49:56.260 --> 00:49:59.859 Pietro Peyron (Populus): Yeah, yeah, no, no, it's not really a feature, it's more like a,

281 00:50:00.630 --> 00:50:08.360 Pietro Peyron (Populus): a feature you've created on MBS2 that is not really needed yet for the EU market. I just wanted you to be aware.

282 00:50:08.690 --> 00:50:16.879 Michael Schnuerle (OMF): Yeah, you mean that people are not upgrading to 2.0? Is that the problem, or when they.

283 00:50:16.880 --> 00:50:26.140 Pietro Peyron (Populus): No, no, people are upgrading to 2.0, but in 2.0, you've got the… you don't have e-scooter as a vehicle type, but you've got seated and standing.

284 00:50:26.140 --> 00:50:26.570 Michael Schnuerle (OMF): Bye.

285 00:50:26.570 --> 00:50:32.059 Pietro Peyron (Populus): But this actually only reflects a change that happened in the US, not really in the EU.

286 00:50:32.970 --> 00:50:41.500 Pietro Peyron (Populus): So, shortcut here would be to keep treating standing e-scooters as e-scooters, basically.

287 00:50:42.920 --> 00:50:50.909 Michael Schnuerle (OMF): Yeah, I feel like if you're not having any seated scooters, then you would just keep using the standing room? Is that right?

288 00:50:52.290 --> 00:51:11.179 Andrew Glass Hastings (OMF): Yeah, Pietro, we created more options to represent the fleets, the micromobility fleets that exist in different countries, but if in a particular geography the seated does not exist, then you just would not use that as the vehicle type. You just continue to use the standing as the vehicle type.

289 00:51:13.350 --> 00:51:15.260 Pietro Peyron (Populus): Yeah, this is clear. Okay.

290 00:51:15.690 --> 00:51:16.070 Michael Schnuerle (OMF): Yeah, yeah.

291 00:51:16.070 --> 00:51:17.739 Pietro Peyron (Populus): The, the… yeah.

292 00:51:19.750 --> 00:51:37.950 Michael Schnuerle (OMF): And just, while we're on this sort of tangential topic here, I just want to point out, we do have guidance for upgrades, so, you know, if you are… if people have not upgraded, we do recommend upgrading within 2 years of, of changes, and so,

293 00:51:38.190 --> 00:51:44.529 Michael Schnuerle (OMF): there's a lot of information here about that, and then how to upgrade as well, so I'll put some of this in the…

294 00:51:45.060 --> 00:51:50.069 Michael Schnuerle (OMF): In the chat. Another question I saw was.

295 00:51:50.450 --> 00:52:02.199 Michael Schnuerle (OMF): I think from VNOVA, Alex, are we on a path towards standards eventually emerging and having a relationship between them? I think we are. I think it's up to the community and the working group here.

296 00:52:02.200 --> 00:52:18.239 Michael Schnuerle (OMF): But, yes, I can imagine a state where CDS sort of defines more and more of the public space in a physical infrastructure way, and MDS sits on top of that, and maybe they get either more connected than they are already. You can already cross-connect them.

297 00:52:18.380 --> 00:52:29.400 Michael Schnuerle (OMF): In many ways, but maybe they're… become part of the same standard. I think that's at least, you know, two years out, but, it is a possibility and something we have thought about.

298 00:52:29.710 --> 00:52:32.080 Michael Schnuerle (OMF): Yes, Espin.

299 00:52:42.890 --> 00:52:44.230 Michael Schnuerle (OMF): Do you have your hand up?

300 00:52:45.750 --> 00:52:48.009 Andrew Glass Hastings (OMF): Espin, you're on mute still, if you tried to come on.

301 00:52:48.010 --> 00:52:49.900 Espen Johnsson: Joe, do you hear… do you hear me now?

302 00:52:49.900 --> 00:52:50.370 Andrew Glass Hastings (OMF): Yep, here you.

303 00:52:50.370 --> 00:52:50.740 Michael Schnuerle (OMF): You know?

304 00:52:50.740 --> 00:52:58.980 Espen Johnsson: Okay. Esperan from Institute of Transport Economic is in Oslo. Yeah, regarding the… Excuse

305 00:53:01.690 --> 00:53:06.390 Espen Johnsson: incident, information. Have any thoughts about standardizing, like.

306 00:53:06.600 --> 00:53:09.870 Espen Johnsson: There's lots of different sensors, and

307 00:53:10.080 --> 00:53:16.920 Espen Johnsson: You know, even on the same fleet with the same sensors, there's quite a lot of job to calibrate, and…

308 00:53:17.140 --> 00:53:21.750 Espen Johnsson: Kind of differentiate between an actual accident and just…

309 00:53:22.090 --> 00:53:28.339 Espen Johnsson: Like, some… somebody throwing the bike around, or the e-scooter around, or…

310 00:53:28.560 --> 00:53:34.379 Espen Johnsson: That kind of stuff. I've been working quite a bit with the accelerometer data from some scooters, and it's…

311 00:53:34.500 --> 00:53:40.629 Espen Johnsson: It's not… Obvious every time what's an accident and what's not.

312 00:53:41.060 --> 00:53:45.209 Michael Schnuerle (OMF): Yeah, it's a good question, and if you notice in spec, many times.

313 00:53:45.590 --> 00:53:57.810 Michael Schnuerle (OMF): We… we leave some of this open to interpretation, because even the definition of a… what needs to be reported as a crash can vary per city, per country.

314 00:53:57.970 --> 00:54:16.340 Michael Schnuerle (OMF): And so the details of what to… what that operator needs to send back is really up to that agreement, that permit, or the local laws between that… in that jurisdiction and the operator. And so, we leave that part up to that communication and agreement.

315 00:54:16.340 --> 00:54:23.090 Michael Schnuerle (OMF): But whatever that is decided on, so if that AV operator has… is following some law.

316 00:54:23.120 --> 00:54:29.659 Michael Schnuerle (OMF): For when there's a crash, that maybe there's contact between the vehicle and something else, and maybe that's how it's defined there.

317 00:54:29.790 --> 00:54:38.409 Michael Schnuerle (OMF): that information, whatever is needed to be reported, can be sent in MDS at that point. So, it's a little bit of a…

318 00:54:38.630 --> 00:54:44.059 Michael Schnuerle (OMF): Leave some things up to the jurisdiction, but we have a capability to record it when needed.

319 00:54:46.460 --> 00:54:48.120 Michael Schnuerle (OMF): Harold.

320 00:54:52.040 --> 00:55:05.109 Nivel | Harald, Antonia, Maroof: Yes, thank you. I've got a question about the food delivery that's also now being included. What kind of experience is there out there, actually, on…

321 00:55:05.260 --> 00:55:19.069 Nivel | Harald, Antonia, Maroof: On the data sharing, because normally, like, from all the other modes, it's, like, the vehicles that are connected to some kind of fleet management system that is sharing the data, but if these are, like, just, like, individual…

322 00:55:19.270 --> 00:55:24.500 Nivel | Harald, Antonia, Maroof: Workers? Is it, like, the… the… like…

323 00:55:24.840 --> 00:55:33.290 Nivel | Harald, Antonia, Maroof: Their mobile phone, or whatever that is, like, delivering the data, or how is this being solved, or how do you foresee it being solved?

324 00:55:33.810 --> 00:55:45.850 Michael Schnuerle (OMF): Yeah, I think that there's a lot of different ways to track… companies track delivery vehicles, and as you said, a lot of different situations where there's an employee driving an employee… a company vehicle.

325 00:55:45.860 --> 00:55:55.669 Michael Schnuerle (OMF): or a regular person doing a delivery on the side. And so, MDS supports all those ways, and the way it does it, for instance, we have

326 00:55:55.840 --> 00:56:02.800 Michael Schnuerle (OMF): An example… maybe some of the staff could fill me in here, but there's some examples already where

327 00:56:03.010 --> 00:56:21.760 Michael Schnuerle (OMF): cities, at least in the U.S, are writing this into their permits, and a scenario is, like, using DoorDash. So, DoorDash is an app that someone uses to deliver food to your home from a restaurant, or to a business from your restaurant, and there's a private vehicle driver

328 00:56:21.840 --> 00:56:31.970 Michael Schnuerle (OMF): But that company, DoorDash, has their own app that that private driver uses that says… that driver says, oh, I want to pick up… I'll go pick up this restaurant order, and I'll deliver it.

329 00:56:32.010 --> 00:56:45.590 Michael Schnuerle (OMF): And DoorDash knows that at a higher level, and knows where they are through the location of that app. So as that information about those trips and the reservations and pickup and drop-off of those trips come to the DoorDash

330 00:56:45.610 --> 00:57:02.620 Michael Schnuerle (OMF): central servers, DoorDash, the company, is sending that information back via permit, required permit, to the cities. And so the driver really has no knowledge or doesn't need to do anything extra. They're just using the app provided by DoorDash. And of course.

331 00:57:02.980 --> 00:57:12.689 Michael Schnuerle (OMF): different scenarios, like a FedEx or UPS or DHL, they… they have their own systems, and they can also report that information back through their internal systems.

332 00:57:15.470 --> 00:57:16.380 Michael Schnuerle (OMF): Thank you.

333 00:57:22.050 --> 00:57:35.040 Michael Schnuerle (OMF): Yeah, and Thibault from Villanova is a good point in the chat. There are definitions of crashes in the U.S. and the EU. I think that's true, and those can be used.

334 00:57:35.390 --> 00:57:46.049 Michael Schnuerle (OMF): I think even in some cities, though, that the cities may have the authority to ask for different ones than beyond what the federal authority might require.

335 00:57:46.230 --> 00:57:54.010 Michael Schnuerle (OMF): And so… or define, and so sometimes, again, it could be left up to the local, state, province, or city.

336 00:57:56.470 --> 00:58:03.450 Michael Schnuerle (OMF): All right, well, let me… I'm gonna pause there. I'm sure… I bet there are other questions out there that maybe didn't even get

337 00:58:03.450 --> 00:58:17.220 Michael Schnuerle (OMF): put in chat, or you didn't raise your hand, feel free to reach out to us. Get involved. You can get in touch with us through our website, or from the email that you got this invite from, or the social media post.

338 00:58:17.400 --> 00:58:25.999 Michael Schnuerle (OMF): We are… and we're happy to answer those questions offline and bring them back to the working groups. Our next meeting is April 9th.

339 00:58:26.040 --> 00:58:45.890 Michael Schnuerle (OMF): And this is our final 2.1 working group review, so it'll be similar to this, but a more general review of 2.1 and just looking for any final feedback. So you can also bring your feedback to that meeting, and you can open up a GitHub issue as well, if you'd like to get something a little more defined and concrete.

340 00:58:45.890 --> 00:58:47.629 Michael Schnuerle (OMF): So for now.

341 00:58:47.730 --> 00:58:57.790 Michael Schnuerle (OMF): go ahead and, of course, use MDS, get to know MDS, start to use the official, 2.1 release. You can actually, I will put it in the chat.

342 00:58:58.200 --> 00:59:02.040 Michael Schnuerle (OMF): We have… everything is documented in our development branch.

343 00:59:02.330 --> 00:59:09.250 Michael Schnuerle (OMF): And you can see it right now, as it's… before it gets approved. There's a link to the spec

344 00:59:09.620 --> 00:59:15.489 Michael Schnuerle (OMF): And so, feel free to look at it and speak with your teams and customers about how it can be used for other modes.

345 00:59:16.570 --> 00:59:22.310 Michael Schnuerle (OMF): And that is it, so thank you for today. Thank you, everyone, for attending.

346 00:59:22.710 --> 00:59:30.470 Michael Schnuerle (OMF): We appreciate all the great examples from the European space, and have everyone attending this meeting.

347 00:59:30.640 --> 00:59:39.520 Michael Schnuerle (OMF): We look forward to implementing 2.1 and getting it out there for you to use. So, happy to have everyone here. Thanks for everyone who participated.

348 00:59:45.280 --> 00:59:46.509 Andrew Glass Hastings (OMF): Thank you all. We'll see you next time.

349 00:59:47.350 --> 00:59:48.160 Michael Schnuerle (OMF): Yep.