Web conference notes, 2026.04.09 (MDS Working Group)

• 00:09:29 Bern Grush: Bern Grush, Pudocity Inc. Robotaxi Orchestration

• 00:09:37 Michael Schnuerle (OMF): Meeting agenda https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.04.09-(MDS-Working-Group)

• 00:11:41 Vignesh Ram - Serve Robotics: Vignesh Ram, Head of Policy at Serve Robotics. We’re on the screen 🙂

• 00:11:57 Andrew Glass Hastings (OMF): Reacted to "Vignesh Ram, Head of..." with 👋

• 00:12:09 Pierre Bouffort (Blue Systems): Hey all, nice to see everyone, apologies for being slightly late.

• 00:12:31 Amanda Harshbarger (Verra Mobility): Hi all! Amanda Harshbarger, Director of Product Management at Verra Mobility. Excited to have just joined OMF this week! We help cities, universities, and commercial fleets operate complex mobility programs at real-world scale across tolling, connected vehicle, parking, and automated enforcement of road-safety cameras and curbside management.

• 00:12:47 Michael Schnuerle (OMF): Calendar https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2026.04.09-(MDS-Working-Group)

• 00:13:22 Oskar Jahr (Municipality of Bergen): A, D

• 00:13:24 Vignesh Ram - Serve Robotics: D & E

• 00:13:35 Aylene McCallum (OMF): Hi everyone! My name is Aylene McCallum - Director of Partnerships & Development - and A + B + C + D +E

• 00:13:37 Lindsey de Boo, DFHV: Lindsey de Boo, policy analyst at DFHV and I am here because someone suggested I attend!

• 00:13:50 Halina Do-Linh (LADOT): Hi All - Halina Do-Linh, Data Analyst at LADOT. A, D, and E 🙂

• 00:13:55 Aylene McCallum (OMF): Welcome LIndsey!

• 00:13:57 Bern Grush: D,E

• 00:13:57 Kelsey Taeckens: Kelsey Taeckens, NYC DOT. A!

• 00:14:01 Lindsey de Boo, DFHV: Reacted to "Welcome LIndsey!" with ❤️

• 00:14:04 Sean Bouffiou, King County, WA: D and E

• 00:14:04 arti gupta: Arti Gupta, Transportation Mobility Solutions - A

• 00:14:30 remi kuti: Hi everyone, I’m Remi Kuti, founder of UrbanShield.

• We’re focused on building infrastructure for safety and compliance in shared micromobility — integrating helmet-based intelligence with vehicle and city-level data.

• Our work is centred on making safety measurable and auditable at scale, rather than relying on policy or rider behaviour alone.

• Looking forward to contributing to the MDS discussion.

• 00:14:46 David Von Stroh, Parametrix: David Von Stroh, Mobility and Data Technologies lead for Parametrix - I've been more involved in the CDS side of OMF and love to learn what's going on on the MDS side

• 00:15:05 Aylene McCallum (OMF): Reacted to "David Von Stroh, Mob..." with 👍🏻

• 00:15:17 Aylene McCallum (OMF): Reacted to "Hi everyone, I’m Rem..." with 👋🏻

• 00:15:21 Aylene McCallum (OMF): Reacted to "Arti Gupta, Transpor..." with 👋🏻

• 00:15:26 Aylene McCallum (OMF): Reacted to "Kelsey Taeckens, NYC..." with 👋🏻

• 00:18:41 Bern Grush: reporting to our municipal clients

• 00:19:05 Oskar Jahr (Municipality of Bergen): A stable infrastructure to build data pipelines to and from our operators and to the public

• 00:19:06 Andrew Glass Hastings (OMF): Reacted to "Hi everyone, I’m Rem..." with 👍

• 00:19:16 Andrew Glass Hastings (OMF): Reacted to "A stable infrastruct..." with 👍

• 00:19:20 Vignesh Ram - Serve Robotics: MDS enables us to share data with cities without triggering public disclosure laws that could reveal proprietary information, and do so consistently across markets and vis a vis our peers

• 00:19:21 Emily Lindsey, DRCOG: We have used it for both carshare and shared micromobility in the Denver region but its been critical for managing shared mobility programs and sharing info with the public!

• 00:19:31 Andrew Glass Hastings (OMF): Reacted to "MDS enables us to sh..." with 👍

• 00:19:34 David Von Stroh, Parametrix: Reacted to "MDS enables us to sh..." with 👍

• 00:19:41 Andrew Glass Hastings (OMF): Reacted to "We have used it for ..." with 💯

• 00:19:47 David Von Stroh, Parametrix: Reacted to "We have used it for ..." with 👍

• 00:19:59 David Von Stroh, Parametrix: Reacted to "Kelsey Taeckens, NYC..." with 👍

• 00:20:05 David Von Stroh, Parametrix: Reacted to "Hi All - Halina Do-L..." with 👍

• 00:21:32 Andrew Glass Hastings (OMF): We have a very exciting in-person OMF Academy workshop during NACTO Designing Cities Conference in Minneapolis. May 12 9:00-12:00

• Great opportunity to dive into digital infrastructure, MDS, CDS with a focus on use cases in your cities. Please join! If you won’t be at NACTO please share the invite with your colleagues!

• https://www.eventbrite.com/e/omf-academy-workshop-at-designing-cities-2026-tickets-1986342870998?aff=oddtdtcreator

• 00:23:38 Aylene McCallum (OMF): Reacted to "MDS enables us to sh..." with 👍

• 00:23:51 Andrew Glass Hastings (OMF): Nothing about MDS is boring! 😎

• 00:25:13 Aylene McCallum (OMF): Sound Transit out of Seattle recently joined the OMF to begin to explore how to use MDS for their transit services!

• 00:26:15 David Von Stroh, Parametrix: Reacted to "Sound Transit out of..." with 👏

• 00:28:19 Vignesh Ram - Serve Robotics: This is REALLY cool

• 00:29:52 Michael Schnuerle (OMF): https://github.com/openmobilityfoundation/mobility-data-specification/blob/dev/data-types.md#incidents

• 00:30:42 Raphael Dumas: Collision incidents are part of our data reporting requirement from ride-hailing companies (but not in MDS format)

• 00:30:42 remi kuti: i would like to see this for my city

• 00:30:54 Oskar Jahr (Municipality of Bergen): Sounds very interesting for Bergen, we've raised the question on how to actually get this data before and we've not had any great abilities to make it happen.

• 00:31:54 Matt McBride: I would love to see this for my city (NYC)

• 00:32:17 Michael Schnuerle (OMF): Reacted to "I would love to see ..." with 🌟

• 00:32:22 Michael Schnuerle (OMF): Reacted to "Sounds very interest..." with 🌟

• 00:32:26 Michael Schnuerle (OMF): Reacted to "i would like to see ..." with 🌟

• 00:32:30 Michael Schnuerle (OMF): Reacted to "Collision incidents ..." with 🌟

• 00:32:40 Michael Schnuerle (OMF): Reacted to "I would love to see ..." with 🎉

• 00:33:42 Halina Do-Linh (LADOT): LADOT/City of LA is interested in this, too

• 00:34:03 Aylene McCallum (OMF): Thank you for sharing those thoughts Pierre!

• 00:34:44 remi kuti: remi kuti Urbanshield is interested in this data london

• 00:37:38 michelle lee: can you share the link of user case?

• 00:39:00 Bern Grush: What about other mobile urban robots on sidewalk?: Security, maintenance (sweep, brine, plow, etc.)

• 00:41:41 Michael Schnuerle (OMF): Delivery https://github.com/openmobilityfoundation/mobility-data-specification/blob/dev/modes/delivery-robots.md#trip-type

• 00:45:48 arti gupta: Do we know if there is a plan to code bus only lanes?

• 00:50:15 Vignesh Ram - Serve Robotics: Love the push function here

• 00:51:09 Michael Schnuerle (OMF): Reacted to "Love the push functi..." with 🎉

• 00:52:34 remi kuti: That’s fantastic 👌

• 00:52:46 Lars Ove Kvalbein: This is really interesting for us in Bergen - in several cases, but we want to specifically test real time adjustments of slow speed zones, based on cameras detecting high pedestrian traffic.

• 00:52:47 Aylene McCallum (OMF): I really like how this reinforces the collaborative nature of MDS!

• 00:52:59 Michael Schnuerle (OMF): Reacted to "This is really inter..." with 🇪🇺

• 00:53:05 Michael Schnuerle (OMF): Reacted to "I really like how th..." with mds

• 00:53:07 Bern Grush: Reacted to "I really like how th..." with 👍

• 00:53:58 Aylene McCallum (OMF): Blue Systems, Seattle and the OMF will be discussing this in more detail at Curbivore next week

• 00:54:00 Michael Schnuerle (OMF): Policy Post https://github.com/openmobilityfoundation/mobility-data-specification/blob/dev/policy/README.md#policies---create

• 00:54:45 Aylene McCallum (OMF): I'll be at Curbivore (in Los Angeles) representing the OMF (and hosting our Open Mobility Mixers on Wednesday evening) - Please say hello if you or your colleagues will be there as well!

• 00:58:15 Michael Schnuerle (OMF): External Reference https://github.com/openmobilityfoundation/mobility-data-specification/blob/dev/data-types.md#external-reference

• 00:58:17 Amanda Harshbarger (Verra Mobility): I look forward to seeing you at Curbivore Aylene! I will be at both UCLA Lake Arrowhead Symposium and Curbivore next week and look forward to connecting with anyone there

• 00:58:29 Andrew Glass Hastings (OMF): Reacted to "I look forward to se..." with 👍

• 00:58:30 Aylene McCallum (OMF): Reacted to "I look forward to se..." with ❤️

• 00:58:39 Andrew Glass Hastings (OMF): Replying to "I look forward to se..."

• See you in the mountains!

• 00:59:18 Amanda Harshbarger (Verra Mobility): Reacted to "See you in the mou..." with 😄

• 00:59:25 Michael Schnuerle (OMF): Reacted to "I look forward to se..." with 👍

• 01:00:08 Andrew Glass Hastings (OMF): The OMF Events Calendar is stuffed with great programming over the next couple of months. Check it out and joins online or in-person!

• https://calendar.google.com/calendar/embed?src=openmobilityfoundation.org_g6gsaccjvijnmlhigfpj01ngp0%40group.calendar.google.com&ctz=America%2FLos_Angeles

• 01:00:54 Andrew Glass Hastings (OMF): Don’t be shy! No wrong answers on this. Definitely not a test 😎

• 01:01:22 michelle lee: can you share the link of user case, please?

• 01:01:48 Lars Ove Kvalbein: The external references featrure needs a lot of exploring, also combined with CDS 1.1!

• 01:02:11 Kenya Wheeler: Reacted to "The external references featrure needs a lot of exploring, also combined with CDS 1.1!" with 👍

• 01:02:41 Halina Do-Linh (LADOT): Reacted to "The external referen..." with 👍

• 01:02:43 Oskar Jahr (Municipality of Bergen): Reacted to "The external referen..." with 👍

• 01:03:05 Michael Schnuerle (OMF): https://www.openmobilityfoundation.org/whats-possible-with-mds/

• 01:03:26 Aylene McCallum (OMF): Reacted to "The external referen..." with 👍

• 01:03:33 Aylene McCallum (OMF): Reacted to "The external referen..." with 👍

• 01:03:49 Michael Schnuerle (OMF): Use case database https://airtable.com/app0XurVVjbou23uI/shrPf4QvORkjZmHIs/tblzFfU6fxQm5Sdhm

• 01:03:59 michelle lee: yes. thanks

• 01:04:37 Pierre Bouffort (Blue Systems): Have to run!

• Thanks a lot for this session, speak to you all soon

• 01:04:54 Oskar Jahr (Municipality of Bergen): This looks to be a great release, good job everyone involved!

• 01:05:01 Halina Do-Linh (LADOT): Thank you!

• 01:05:01 Bern Grush: 👍

• 01:05:02 Lindsey de Boo, DFHV: Thank you! :)

• 01:05:03 Amanda Harshbarger (Verra Mobility): Thank you Michael! And thank you everyeone!

WEBVTT

1 00:00:06.260 --> 00:00:07.570 Michael Schnuerle (OMF): Hello, everyone.

2 00:00:07.770 --> 00:00:15.509 Michael Schnuerle (OMF): Welcome to the MDS Working Group Meeting. My name is Michael Schnurla, I'm the Director of Open Source Operations at the Open Mobility Foundation.

3 00:00:16.000 --> 00:00:23.120 Michael Schnuerle (OMF): Today, we are going to be talking about the MBS 2.1 release, and reviewing it in some detail.

4 00:00:23.260 --> 00:00:27.539 Michael Schnuerle (OMF): We've reviewed it a few times before in different states, today.

5 00:00:28.050 --> 00:00:35.140 Michael Schnuerle (OMF): We will spend a little more time going into detail and answering any specific questions you have about certain features.

6 00:00:35.470 --> 00:00:39.799 Michael Schnuerle (OMF): And… let's get into it. So, a little bit of housekeeping.

7 00:00:40.190 --> 00:00:47.959 Michael Schnuerle (OMF): Go ahead and add your organization name after your personal name in the participant list, so we know who you're representing.

8 00:00:48.660 --> 00:00:56.860 Michael Schnuerle (OMF): mute yourself for now, but feel free to introduce yourself in the chat right now. You could say who you are, who you're with, why you're here, things like that.

9 00:00:58.210 --> 00:01:15.960 Michael Schnuerle (OMF): Use the chat to leave questions as we go, and then I will pause at certain times for Q&A, so you can raise your hand, or I'll also browse the chat at that point to check for questions. So either way, that's how you can get your questions answered.

10 00:01:16.670 --> 00:01:20.980 Michael Schnuerle (OMF): This meeting is being recorded, and we'll publish it with notes afterwards.

11 00:01:23.120 --> 00:01:33.520 Michael Schnuerle (OMF): So, today we'll have a little bit of announcements, and then review of MDS 2.1, specifically also a quick overview of MDS in general.

12 00:01:34.030 --> 00:01:40.590 Michael Schnuerle (OMF): Before we get into the changes, and then feedback and questions at the end, but also along the way.

13 00:01:40.720 --> 00:01:46.249 Michael Schnuerle (OMF): From you all. So, if you have questions as we go, please let us know.

14 00:01:46.350 --> 00:02:01.349 Michael Schnuerle (OMF): This is really the last meeting before… I'll put the agenda in the chat, as you can see here. This is the last public meeting before the release process begins, through the OMF approval process, so…

15 00:02:04.150 --> 00:02:18.070 Michael Schnuerle (OMF): Here is the agenda, and there are a few key links in here that you can follow along with, like the release plan, the development branch, where you can look at what's new, a recording from last month you can watch later.

16 00:02:22.910 --> 00:02:37.269 Michael Schnuerle (OMF): So, a little bit of OMF intro. The OMF is a global nonprofit created in 2019, city-founded and city-led, and we help companies and cities get to yes for different types of mobility in cities and countries.

17 00:02:37.400 --> 00:02:57.029 Michael Schnuerle (OMF): And we want to work together, and that's what we do. We build everything in the open, lots of public participation from individuals, companies, cities, operators, curb users, vendors, etc. And that has created a nice ecosystem around the use of MDS and CDS, all built through OMF's open model.

18 00:02:57.590 --> 00:03:03.330 Michael Schnuerle (OMF): Free and open source tools and public meetings based on our nonprofit bylaws.

19 00:03:05.290 --> 00:03:15.330 Michael Schnuerle (OMF): Mobility data specification is a two-way data standard, a blueprint for how to share information between public agencies and private companies.

20 00:03:15.500 --> 00:03:22.209 Michael Schnuerle (OMF): We are led by members, OMF members, that have volunteered their time to be on our steering committee.

21 00:03:22.340 --> 00:03:25.700 Michael Schnuerle (OMF): And there's public and private sector members on our steering committee.

22 00:03:25.890 --> 00:03:41.919 Michael Schnuerle (OMF): This, I think, MDS committee will be up for re-election soon, so if you're an OMF member, look for an email to see if… to see if you want to nominate yourself or someone from your teams to be part of the steering committee, which sets the agendas for these meetings.

23 00:03:44.300 --> 00:03:55.959 Michael Schnuerle (OMF): We have a lot of commercial members. Here is our current list. Some of them are new, if you're a new commercial member, or even an existing commercial member.

24 00:03:56.120 --> 00:03:59.719 Michael Schnuerle (OMF): Please introduce yourself in the chat to everybody.

25 00:03:59.830 --> 00:04:06.510 Michael Schnuerle (OMF): maybe mention why you joined the OMF, but we'd love to support you and our commercial members.

26 00:04:08.270 --> 00:04:09.250 Michael Schnuerle (OMF): Thank you.

27 00:04:09.830 --> 00:04:15.870 Michael Schnuerle (OMF): MDS is a global standard. Here's a map of… oh, hi.

28 00:04:16.390 --> 00:04:19.910 Michael Schnuerle (OMF): Hi, Biggie, welcome, sir, welcome to the OMF.

29 00:04:20.029 --> 00:04:39.060 Michael Schnuerle (OMF): Mbs is a global standard. You can see where MDS is known to be used right now. We have… there are over 200 commercial mobility service providers, like Serv Robotics, that use MDS around the world, and they operate in over 1,200 cities.

30 00:04:39.150 --> 00:04:49.300 Michael Schnuerle (OMF): representing at least 2 billion trips taken that we know of. You can see an example here, and last month's meeting was focused on Europe and

31 00:04:49.660 --> 00:04:52.459 Michael Schnuerle (OMF): Adoption in Europe is actually higher per…

32 00:04:52.560 --> 00:04:59.620 Michael Schnuerle (OMF): you know, number… count of cities than in the United States, so we were happy to see that and focus on Europe last month.

33 00:05:03.210 --> 00:05:08.840 Michael Schnuerle (OMF): We also have an OMF calendar where meetings like this are posted, you can subscribe to it,

34 00:05:09.130 --> 00:05:15.029 Michael Schnuerle (OMF): or view it, I will put the calendar, the main calendar browsable link in the chat.

35 00:05:15.330 --> 00:05:21.230 Michael Schnuerle (OMF): And then these other… this other information is available in the slides, or through the calendar itself.

36 00:05:22.530 --> 00:05:24.410 Michael Schnuerle (OMF): So, a little bit of…

37 00:05:25.380 --> 00:05:34.250 Michael Schnuerle (OMF): time for you to speak up, introduce yourself in the chat if you haven't already, and then also, why did you end up here today? Why are you in this meeting?

38 00:05:34.510 --> 00:05:50.149 Michael Schnuerle (OMF): you could just put the letters A, B, C, D, or E, so you're curious about the release, someone suggested you to attend, maybe your boss asked you. It's your job to understand and implement MDS, or you want to understand what the OMF is doing and what's coming, so…

39 00:05:50.410 --> 00:05:54.819 Michael Schnuerle (OMF): Feel free to start leaving comments around this in the chat.

40 00:06:03.030 --> 00:06:05.779 Michael Schnuerle (OMF): We have people whose job it is to understand.

41 00:06:06.350 --> 00:06:08.279 Michael Schnuerle (OMF): Curious about the new release.

42 00:06:08.930 --> 00:06:11.750 Michael Schnuerle (OMF): All of the above. That's Aileen.

43 00:06:11.890 --> 00:06:12.820 Michael Schnuerle (OMF): Hello?

44 00:06:16.650 --> 00:06:19.960 Michael Schnuerle (OMF): someone suggested you attend, that's great. So it's,

45 00:06:20.130 --> 00:06:26.450 Michael Schnuerle (OMF): I can tell from the attendee list, it's a mix of people who have attended in the past, and some new people, so…

46 00:06:27.680 --> 00:06:29.269 Michael Schnuerle (OMF): Thanks, keep sharing.

47 00:06:29.450 --> 00:06:31.380 Michael Schnuerle (OMF): Curious about the release?

48 00:06:33.740 --> 00:06:34.929 Michael Schnuerle (OMF): It's your job.

49 00:06:35.860 --> 00:06:36.650 Michael Schnuerle (OMF): Alright.

50 00:06:37.310 --> 00:06:38.130 Michael Schnuerle (OMF): Thank you.

51 00:06:38.330 --> 00:06:40.260 Michael Schnuerle (OMF): So I'll give… you can keep leaving.

52 00:06:40.720 --> 00:06:56.580 Michael Schnuerle (OMF): your comments. I'm going to give a quick overview of MDS, and then jump into 2.1. So, MDS in general is a two-way data standard, as I mentioned, that serves all these types of modes you see here, these services, these modes, these vehicle types, and this is

53 00:06:56.610 --> 00:07:01.000 Michael Schnuerle (OMF): what we're really focusing on for 2.1 is the scope of MDS.

54 00:07:03.550 --> 00:07:07.519 Michael Schnuerle (OMF): Mbs allows you to,

55 00:07:08.270 --> 00:07:12.750 Michael Schnuerle (OMF): As, as a, as a public sector,

56 00:07:13.180 --> 00:07:17.089 Michael Schnuerle (OMF): Like, the city, or county, MPO, or country.

57 00:07:17.350 --> 00:07:22.850 Michael Schnuerle (OMF): You can request to get information about vehicles and vehicle movements.

58 00:07:23.130 --> 00:07:31.540 Michael Schnuerle (OMF): From operators, and you could see information like the vehicle location and status, vehicle…

59 00:07:32.130 --> 00:07:46.310 Michael Schnuerle (OMF): what happened either historically or in real time, trip details, information about the trips, trip breadcrumbs, and stop details, and this is just a quick overview of some of the data. As many of you know, there's a lot of other optional

60 00:07:46.570 --> 00:07:49.329 Michael Schnuerle (OMF): Fields and information you can receive.

61 00:07:49.440 --> 00:08:04.899 Michael Schnuerle (OMF): But also, it's useful for public entities publishing and digitizing their permit and data sharing requirements and operating rules. This is all possible in MVS as well, so when you have your PDF of

62 00:08:05.330 --> 00:08:22.630 Michael Schnuerle (OMF): data sharing rules, or certain policies, or information you want to share, you can digitize that, and when you have geofencing, or emergency, or event information, or vehicle caps, and things like that, you can also digitize that in MBS, all of that is possible.

63 00:08:22.630 --> 00:08:28.460 Michael Schnuerle (OMF): And that's part of the two-way data sharing. MDS is made up of two different…

64 00:08:28.860 --> 00:08:40.709 Michael Schnuerle (OMF): APIs and groups of endpoints, provider and agency, which are sets of endpoints coming from operators, and then four different ones coming from cities to the operators.

65 00:08:42.539 --> 00:08:47.679 Michael Schnuerle (OMF): We have a lot of use cases defined for MDS over 60 in our use case database.

66 00:08:47.810 --> 00:08:57.220 Michael Schnuerle (OMF): And we're trying to increase these all the time. These will probably get a refresh after we launch 2.1, because there'll be some new use cases and some new modes.

67 00:08:59.150 --> 00:09:12.219 Michael Schnuerle (OMF): Privacy is important. We intend and try to only track vehicle information, not rider information. And so, this is part of our, you know, privacy guide for cities.

68 00:09:12.770 --> 00:09:21.089 Michael Schnuerle (OMF): privacy principles, a mobility data set of practice of what other cities are doing, and then guidance in Europe for a GDPR.

69 00:09:23.040 --> 00:09:35.419 Michael Schnuerle (OMF): And MDS and CDS, our other data standard, work together to manage the public space. They both communicate digital policy, they both have data sharing, they both have metrics. They can be used independently or cooperatively.

70 00:09:35.450 --> 00:09:43.200 Michael Schnuerle (OMF): And MDS really understands the location, status, incidents, and trips of vehicles, and where they are.

71 00:09:43.300 --> 00:09:50.830 Michael Schnuerle (OMF): And CDS defines the infrastructure and the interaction between physical infrastructure and those vehicles and activities.

72 00:09:54.370 --> 00:10:09.889 Michael Schnuerle (OMF): If you want to learn more and you're an OMF member, you can attend our OMF Academy sessions. We've had two already. Digital Infrastructure 101, the CDS 101s start soon. This month, there's going to be two sessions that are the same at different dates and times.

73 00:10:10.150 --> 00:10:12.339 Michael Schnuerle (OMF): And then MDS in May.

74 00:10:12.610 --> 00:10:19.030 Michael Schnuerle (OMF): And you can learn about who's using MDS, what it is, where does it fit into your ecosystem?

75 00:10:19.250 --> 00:10:23.670 Michael Schnuerle (OMF): Why would you want to use MDS or CDS, and how you can

76 00:10:23.780 --> 00:10:29.620 Michael Schnuerle (OMF): use MDS and CDS, so if you remember, you're probably getting emails about this, but…

77 00:10:29.800 --> 00:10:33.779 Michael Schnuerle (OMF): We welcome your participation in the OMF Academy courses.

78 00:10:34.800 --> 00:10:38.740 Michael Schnuerle (OMF): So, another question for you in the chat.

79 00:10:39.870 --> 00:10:45.570 Michael Schnuerle (OMF): What does MDS enable for you? So if you're already using MDS, or you're familiar with it.

80 00:10:46.060 --> 00:10:48.490 Michael Schnuerle (OMF): At a high level or a specific level.

81 00:10:49.170 --> 00:10:55.100 Michael Schnuerle (OMF): how does MDS benefit you? How are you using it? What does it allow you to do?

82 00:11:10.480 --> 00:11:12.620 Michael Schnuerle (OMF): I'm catching up on the comments as well.

83 00:11:18.570 --> 00:11:23.090 Michael Schnuerle (OMF): Allows you to report to your city and municipal clients, that's great.

84 00:11:29.840 --> 00:11:32.180 Michael Schnuerle (OMF): Alright, continue to leave comments about

85 00:11:32.590 --> 00:11:35.699 Michael Schnuerle (OMF): What does MDS enable for you?

86 00:11:36.780 --> 00:11:38.750 Michael Schnuerle (OMF): Sustainable infrastructure.

87 00:11:41.650 --> 00:11:43.930 Michael Schnuerle (OMF): For the operators and for the public.

88 00:11:45.720 --> 00:11:46.580 Michael Schnuerle (OMF): Thank you.

89 00:11:48.230 --> 00:11:52.419 Michael Schnuerle (OMF): Alright, so as you're leaving those comments, I'm going to talk about MBS 2.1,

90 00:11:53.380 --> 00:11:58.260 Michael Schnuerle (OMF): And get into the details, and then you can start asking questions of new features.

91 00:11:58.870 --> 00:12:13.649 Michael Schnuerle (OMF): So, a note about the duration of our MDS releases. When MDS was younger, we had more frequent releases, and I think around the sort of 1.0, 1.1 timeframe.

92 00:12:13.730 --> 00:12:23.590 Michael Schnuerle (OMF): operators and vendors were saying, oh, you're sort of moving too fast. The commercial sector can't keep up with the cities.

93 00:12:23.650 --> 00:12:36.539 Michael Schnuerle (OMF): and their needs for MDS. And so, based on the feedback from the industry, we intentionally slowed our releases, made them more intentional, added more review and feedback time.

94 00:12:36.710 --> 00:12:41.400 Michael Schnuerle (OMF): And so you can see, starting with around 1.2 to 2.0, things…

95 00:12:41.680 --> 00:12:57.879 Michael Schnuerle (OMF): have, expanded. Some of these are overlapping, so for instance, we might have been working on 2.1 while we're working on finishing 2.0. But you can see for 2.1, we're at about two and a half years of work in public meetings, and there's a whole list

96 00:12:57.970 --> 00:13:05.710 Michael Schnuerle (OMF): As part of our release plan of every meeting and every recording, and everything you can see on GitHub as well.

97 00:13:07.160 --> 00:13:14.349 Michael Schnuerle (OMF): It's a lot of work, so we're very excited that 2.1 is coming to fruition and reaching the finish line. We have a release plan.

98 00:13:14.730 --> 00:13:20.439 Michael Schnuerle (OMF): These are the 7 things that are high level, what's going to be new in 2.1.

99 00:13:20.600 --> 00:13:35.930 Michael Schnuerle (OMF): We have a timeline, and the release plan page is here, and you can see very specifically links to all the GitHub issues and changes, and also a timeline of what happened when.

100 00:13:36.400 --> 00:13:41.900 Michael Schnuerle (OMF): For… as we go through the development, and now the approval process is about to start.

101 00:13:47.800 --> 00:14:01.599 Michael Schnuerle (OMF): And then, a little bit about our structure. So we have public-facing events like this for MDS, CDS working groups, and other discussions, webinars, and things like that. Internally, for OMF members, we have steering committees.

102 00:14:01.930 --> 00:14:14.260 Michael Schnuerle (OMF): For both MDS and CDS, and then leadership roles of volunteer OMF members, strategy committee, tech council, privacy committee, advisory committee, and then our city-led

103 00:14:14.520 --> 00:14:20.450 Michael Schnuerle (OMF): Board of Directors, so that the release approval process will go through this… parts of this structure.

104 00:14:21.000 --> 00:14:34.419 Michael Schnuerle (OMF): Right now, we are in the working group and steering committee area. Then, after today's meeting, the steering committee will vote to approve the release to move on to our technology council, which is mostly commercial members.

105 00:14:34.430 --> 00:14:41.960 Michael Schnuerle (OMF): For review, and then they will, when ready, approve it and recommend it to the board. Then the board will review it.

106 00:14:42.010 --> 00:14:45.670 Michael Schnuerle (OMF): And then take a vote, and have at least 2 weeks to review it.

107 00:14:46.300 --> 00:14:52.949 Michael Schnuerle (OMF): Usually more. And then that's when the release as a final deliverable and becomes the latest version.

108 00:14:56.560 --> 00:15:00.500 Michael Schnuerle (OMF): Alright, so here's a high-level list of new features. These are…

109 00:15:00.870 --> 00:15:07.599 Michael Schnuerle (OMF): top… it's actually top 7 here. There's a duplicate here with the two twos, but

110 00:15:07.760 --> 00:15:16.329 Michael Schnuerle (OMF): top 7 new features, and I'm going to get into each of these and show you how… what it looks like in the specs. But there's a…

111 00:15:16.470 --> 00:15:33.709 Michael Schnuerle (OMF): More information, more types of modes are supported, incidents and crashes are supported, all kinds of delivery instead of just robot delivery on the sidewalk. Transit, fixed route support, four-hire autonomous vehicles, robo-taxis is more clearly supported.

112 00:15:34.030 --> 00:15:40.549 Michael Schnuerle (OMF): And better real-time digital policy, and the ability to understand enforcement and violations.

113 00:15:43.020 --> 00:15:50.480 Michael Schnuerle (OMF): There are a lot of other features that are part of MDS 2.1, and you can see this on our release plan page or on GitHub.

114 00:15:50.740 --> 00:16:02.309 Michael Schnuerle (OMF): If you are following along and want to ask questions about this during this meeting, feel free to, but I'm not going to really go into a lot of detail reviewing these additional features. Some of them are…

115 00:16:03.210 --> 00:16:13.609 Michael Schnuerle (OMF): Really kind of boring, or minor points, but they're all been… they've all been requested by our community, and are part of the release.

116 00:16:17.260 --> 00:16:31.720 Michael Schnuerle (OMF): So, MDS 2.0, we created modes for 2.0 with micromobility, passenger, fleet, and delivery modes, and this was sort of the way we visualized that, you know, the…

117 00:16:31.990 --> 00:16:34.139 Michael Schnuerle (OMF): Public sector in the green.

118 00:16:34.290 --> 00:16:47.790 Michael Schnuerle (OMF): is managing the public space and understanding where the vehicles and the commercial companies are operating in yellow, and MBS allows this two-way communication between this and the different modes.

119 00:16:48.450 --> 00:16:58.889 Michael Schnuerle (OMF): With 2.1, We are expanding, in some ways, the modes, so delivery, for instance, is greater in scope.

120 00:16:58.990 --> 00:17:15.449 Michael Schnuerle (OMF): But we're also just clarifying what it means to be part of micromobility, or part of a passenger mode, or part of a fleet vehicle. And so, to that end, we have a more detailed diagram with the different listings, not only of

121 00:17:15.450 --> 00:17:32.659 Michael Schnuerle (OMF): pictures of some of the vehicles that you might be familiar with at a glance, but also a list of the different types of modes or services or programs that could be supported by MDS under each of these categories.

122 00:17:32.820 --> 00:17:35.820 Michael Schnuerle (OMF): So you can see the scope for 2.1.

123 00:17:35.920 --> 00:17:39.149 Michael Schnuerle (OMF): Is more clearly defined and expanded as well.

124 00:17:43.400 --> 00:17:45.620 Michael Schnuerle (OMF): Alright, so let's get into our first

125 00:17:46.330 --> 00:17:50.920 Michael Schnuerle (OMF): feature that I want to talk about, and it's one of our bigger ones.

126 00:17:51.110 --> 00:17:59.850 Michael Schnuerle (OMF): So, in 2.1, there will be a… there is a new endpoint, a new API endpoint, to capture all types of incidents.

127 00:17:59.990 --> 00:18:07.360 Michael Schnuerle (OMF): And incidents are… Anything that you see here, there's actually a few more, but everything from

128 00:18:08.250 --> 00:18:15.460 Michael Schnuerle (OMF): And you can imagine these applying to some types of modes or vehicles, but not others. None of them… nothing here is required.

129 00:18:15.520 --> 00:18:27.910 Michael Schnuerle (OMF): It's if it's possible, and if it's required, and if you can… if the operator can provide it, then there is a path to define that in MDS. So, for instance, with autonomous vehicles, or maybe…

130 00:18:27.930 --> 00:18:35.689 Michael Schnuerle (OMF): robots on the sidewalk. You might have things like unplanned stops, remote takeovers, ADS.

131 00:18:35.760 --> 00:18:42.559 Michael Schnuerle (OMF): automatic driving system disengagements or engagements. Maybe you can understand harsh braking and acceleration.

132 00:18:42.870 --> 00:19:01.940 Michael Schnuerle (OMF): Tip-overs for things like scooters or sidewalk robots. Vandalism events, you might be aware of. Theft, breakages, things like that. Near misses as well. Many new vehicle types can understand new misses, including even bikes.

133 00:19:02.420 --> 00:19:21.929 Michael Schnuerle (OMF): And collisions. So when there's an incident of any kind, like a collision or a crash, and each of these gets basic information about that incident in the short term, so where it happened, the date, time, the severity of it, was there a medical response, what's the accelerometer data?

134 00:19:22.070 --> 00:19:23.220 Michael Schnuerle (OMF): And then…

135 00:19:23.250 --> 00:19:42.959 Michael Schnuerle (OMF): It also has the ability to add and connect to information as it becomes available through a report ID, so maybe there was a police report made. You can attach that ID to MDS, and then use that ID to connect the information that MDS provides to the maybe different or more detailed information in the report.

136 00:19:43.200 --> 00:20:00.880 Michael Schnuerle (OMF): And all of this is connected… incidents are connected to MDS telemetry points, so these are sort of GPS points, which includes, by default, time and location of vehicles, and includes it whether they're on a trip or not. So, if it's parked somewhere, or if it's…

137 00:20:01.240 --> 00:20:16.140 Michael Schnuerle (OMF): moving, or it's been reserved, it doesn't matter. As long as it's collecting telemetry, you can attach an incident to it. And it also applies for all modes. So, I'm going to click this link, but before I do, I just wanted to show an example.

138 00:20:16.470 --> 00:20:23.229 Michael Schnuerle (OMF): It's a great example from our last meeting from Amsterdam. They have a… company called Cowboy.

139 00:20:23.390 --> 00:20:39.710 Michael Schnuerle (OMF): And Cowboy is providing Amsterdam near misses and crash information across the whole city for their bikes, their e-bikes. And you can see here they're taking that data and turning it into maps and dashboards, and this… they have

140 00:20:40.080 --> 00:20:45.969 Michael Schnuerle (OMF): dozens of dashboards of different types of this data. This is just a screenshot of one of them.

141 00:20:46.320 --> 00:20:57.040 Michael Schnuerle (OMF): But they're really using it to, when they hit certain thresholds of near misses or crashes, to improve intersections. And, it really shows the value of

142 00:20:57.170 --> 00:21:03.059 Michael Schnuerle (OMF): Understanding this from the perspective of a city where they can make real changes.

143 00:21:03.200 --> 00:21:13.769 Michael Schnuerle (OMF): and get it in MDS. Currently, they're not getting it in MDS because it didn't exist when they started this program, but they will be switching to MDS to get that information.

144 00:21:16.510 --> 00:21:25.579 Michael Schnuerle (OMF): And I'll ask anyone who's on the call who is interested in getting or sending crash data to speak up,

145 00:21:25.790 --> 00:21:34.250 Michael Schnuerle (OMF): this… This actually came… this came… I'll show you the… the link for the… Information of incidents, but…

146 00:21:34.280 --> 00:21:39.239 Michael Schnuerle (OMF): This conversation started in 2021, I think, when

147 00:21:39.260 --> 00:21:52.820 Michael Schnuerle (OMF): Via Nova, a European company, wanted to get and provide and receive information from… about crashes from micromobility and bike share operators, but at the time, it wasn't really possible to do that.

148 00:21:52.820 --> 00:22:05.500 Michael Schnuerle (OMF): And now we have a number of cities who are asking for this. DC, for instance, is a big one that led this effort where they are requiring this information for all their different types of managed modes.

149 00:22:05.560 --> 00:22:09.729 Michael Schnuerle (OMF): Including autonomous vehicles. And so…

150 00:22:09.890 --> 00:22:21.789 Michael Schnuerle (OMF): them and other cities wanted this, and so we… we worked over the course of a few months to come up with the spec and what you see here. So every incident, this is what you're seeing here. I'll go ahead and put this in the chat.

151 00:22:22.470 --> 00:22:28.940 Michael Schnuerle (OMF): But if you're interested in this, we'd love for you just to say, yes, I'd love to see this for my city. You can put that in the chat.

152 00:22:29.130 --> 00:22:37.519 Michael Schnuerle (OMF): And think about questions as I go through this, but each incident gets an ID, a type of incident, and I gave a list of most of those in the slide.

153 00:22:37.770 --> 00:22:43.179 Michael Schnuerle (OMF): The time of the incident that it actually happened, that it first occurred.

154 00:22:43.450 --> 00:23:02.799 Michael Schnuerle (OMF): But there's also discovery times, the time that the operator understood that it was an incident, and then when it first became available in this endpoint, and the last it was updated, in case there are updates to any of the fields. It gets a description, a severity description as well, we're not

155 00:23:02.810 --> 00:23:07.359 Michael Schnuerle (OMF): enumerating these… this thing. We're just saying, okay, you can describe it in some way.

156 00:23:07.760 --> 00:23:14.629 Michael Schnuerle (OMF): A yes or no for if there was medical dispatch or medical transport, this report ID I mentioned.

157 00:23:14.920 --> 00:23:21.670 Michael Schnuerle (OMF): The type of report, you know, was it a 311 thing, or something from the police, or a customer report?

158 00:23:22.060 --> 00:23:34.110 Michael Schnuerle (OMF): So you know how to look that ID up in an external system. Was there any enforcement action attached to this? And we'll talk about enforcement soon in another slide.

159 00:23:34.360 --> 00:23:42.620 Michael Schnuerle (OMF): You can link to external… more external information about this, either in a spec or a web page or another system.

160 00:23:42.920 --> 00:24:00.100 Michael Schnuerle (OMF): Contact info, if you want to provide it. Maybe there's something that is outside the realm of normal contact info. And then a flag for, is this preliminary or not? So maybe you get this information, you flag it as preliminary until you have more details, and then you say, okay, now it's not preliminary.

161 00:24:02.410 --> 00:24:09.770 Michael Schnuerle (OMF): Alright, and we see some… I see some comments from people, if you want to add your city.

162 00:24:09.910 --> 00:24:19.850 Michael Schnuerle (OMF): name, or your company name after your name, that would be great, so we know who you're representing. But I see a few people there. And, we got a hand up for, Pierre.

163 00:24:21.080 --> 00:24:23.059 Pierre Bouffort (Blue Systems): Yeah, hi. Hi, Michael.

164 00:24:23.130 --> 00:24:32.000 Pierre Bouffort (Blue Systems): So, really excited about this incident feature. One quick, remark or thing that I want to say about this.

165 00:24:32.010 --> 00:24:49.310 Pierre Bouffort (Blue Systems): is really in terms of the optics that cities will take when looking at implementing those features with the different mobility operators that they have, roaming their streets. I think it's really important to understand that

166 00:24:49.340 --> 00:25:00.449 Pierre Bouffort (Blue Systems): You want to frame the conversation around sharing incident data as a really, like, collaborative thing, and not make it feel like this is in any way, shape, or form enforcement-related.

167 00:25:00.450 --> 00:25:14.030 Pierre Bouffort (Blue Systems): I think in many ways, if you want to make the most of that data set, that's just, you know, a personal take, but that I'm sharing here, is that those devices, those vehicles that are out there on the streets, you know.

168 00:25:14.030 --> 00:25:20.560 Pierre Bouffort (Blue Systems): If they start reporting incidents, what they really are telling you is,

169 00:25:20.620 --> 00:25:36.509 Pierre Bouffort (Blue Systems): They're bringing you information about safety issues that are already happening on your streets, and that are not necessarily tied to the devices being there, but more so, think of the devices as, like, a new sensor that you now have access to, if they're willing to share the data with you.

170 00:25:36.530 --> 00:25:53.760 Pierre Bouffort (Blue Systems): Rather than thinking, you know, examples of bots or scooters, you know, if you're thinking… if you're approaching this conversation as, like, oh, every time there is a crash happening with a scooter, I want to know about it, because then I want to be able to hold you liable for it, or hold you accountable for it.

171 00:25:53.760 --> 00:26:06.390 Pierre Bouffort (Blue Systems): I personally think you're approaching this conversation wrong, because then, you know, the sharing of this incident data is really, you know, is really… I personally see it as, like, a way to

172 00:26:06.710 --> 00:26:20.719 Pierre Bouffort (Blue Systems): bridge a lot of, like, safety gaps that you might have on your streets today. So, just want to share a thought here on how this conversation should be approached in my perspective from the city's standpoint.

173 00:26:21.900 --> 00:26:38.989 Michael Schnuerle (OMF): Thanks, Pierre, and Blue Systems has a great perspective on this, having worked with a lot of different cities and operators, so I appreciate your thoughts there, and I agree that this could definitely… I mean, I think if you look at how

174 00:26:39.340 --> 00:26:50.509 Michael Schnuerle (OMF): Amsterdam's using it. They are not penalizing Cowboy in any way. They are just using it to approve it for everybody, and it is a new source of information that

175 00:26:50.710 --> 00:27:08.990 Michael Schnuerle (OMF): Otherwise, they wouldn't have. In fact, something Amsterdam did is they compared the data they're getting with Cowboy from all of their police reports and resident reports of near misses or crashes, and they found that the Cowboy data, which is just one company.

176 00:27:09.070 --> 00:27:14.659 Michael Schnuerle (OMF): the count of those, and I think it's actually… it might be in this chart a little bit.

177 00:27:14.670 --> 00:27:32.040 Michael Schnuerle (OMF): But, it's actually about the same as everything else reported combined, and so by just getting information from one company, they're able to get a lot more information and new information they wouldn't get otherwise from just police reports.

178 00:27:37.910 --> 00:27:47.070 Michael Schnuerle (OMF): All right, thank you. If you have other questions, I don't see any more in the chat or raised hands, feel free to continue asking about incidents, and we can loop back if we need to.

179 00:27:49.390 --> 00:28:04.989 Michael Schnuerle (OMF): I'll move on to the second high-level feature, which is delivery. So, prior to 2.1, we focused on delivery robots, and part of the reason was that… for that was the complexity of the multiple types of delivery

180 00:28:05.510 --> 00:28:11.349 Michael Schnuerle (OMF): services and things available that, at the time for MDS 2.0,

181 00:28:11.680 --> 00:28:30.399 Michael Schnuerle (OMF): was a little too much to tackle, because, like, delivery robots were enough. We… when you start thinking about app delivery drivers, or freight, or goods, or food, or trucks, or bicycles, and micro hubs, it starts to get really complicated, and so we waited

182 00:28:30.630 --> 00:28:36.130 Michael Schnuerle (OMF): to really support 2.0 more, and it's come…

183 00:28:36.250 --> 00:28:50.579 Michael Schnuerle (OMF): out of the needs of cities to support it in this version. So we have a number of cities, and again, if you are interested in delivery information in MDS, or you were part of these conversations, please leave something in the chat for people to see. I know LA

184 00:28:50.580 --> 00:29:05.549 Michael Schnuerle (OMF): was really interested and part of this. Boston initiated this in many ways, but there are a lot of different cities that wanted this information. So now, we've expanded the scope, the wording, the fields, the options.

185 00:29:05.550 --> 00:29:19.219 Michael Schnuerle (OMF): For delivery of all types, and so it could be all types of goods, food, packages, freight deliveries, from… and it could be from companies that use employees or contractors, they could be autonomous or remotely operated.

186 00:29:19.220 --> 00:29:30.030 Michael Schnuerle (OMF): Or have a human driver in there. It could be app delivery, includes packages, freight goods, food, private hire vehicles that maybe are doing some sort of delivery.

187 00:29:30.180 --> 00:29:39.399 Michael Schnuerle (OMF): even could support your postal service vehicles, or medicine, medical delivery, and other delivery services. So, very broad.

188 00:29:40.380 --> 00:29:41.470 Michael Schnuerle (OMF): And…

189 00:29:41.820 --> 00:29:54.659 Michael Schnuerle (OMF): For all of those types of delivery, there is details, again, all optional fields on this, but there can be one or more orders, so if you need order information, and

190 00:29:54.870 --> 00:30:03.359 Michael Schnuerle (OMF): So, both Boston… I think Boston, for sure, and LA a little, needed some bit of order information.

191 00:30:03.620 --> 00:30:05.919 Michael Schnuerle (OMF): And I'll show you what that is.

192 00:30:06.050 --> 00:30:15.049 Michael Schnuerle (OMF): And they could be overlapping orders on the same trip, or different trips, and there's ways to connect those trips through a journey.

193 00:30:15.530 --> 00:30:30.409 Michael Schnuerle (OMF): And these… the trips and the orders are tracked separately from the state of the vehicle, and I'll show you a picture of this. So this is one of our more complex examples in the spec for doing a delivery trip.

194 00:30:30.940 --> 00:30:32.370 Michael Schnuerle (OMF): So we have…

195 00:30:32.820 --> 00:30:41.969 Michael Schnuerle (OMF): This third area here is a journey. You can see journeys can connect multiple trips in bright green, so…

196 00:30:42.000 --> 00:30:52.589 Michael Schnuerle (OMF): For instance, there are 3 delivery trips in one journey, actually four, including a return trip to a restaurant, and maybe in this one delivery trip, you're tracking

197 00:30:52.590 --> 00:31:06.739 Michael Schnuerle (OMF): three different orders that happened, and there's another journey later, another one later. There's also this ability to wrap journeys up into routes, so maybe for larger delivery systems, like a FedEx or a UPS route.

198 00:31:06.740 --> 00:31:23.950 Michael Schnuerle (OMF): You can do that, and then even a driver shift identifier, if that is important to you, and it is, in some cases, for labor laws, where you just want to know number of hours that, some driver has worked on their shift, and

199 00:31:23.950 --> 00:31:35.729 Michael Schnuerle (OMF): connecting it to maybe some journeys and trips. So, this is a bit of an example showing, oh, sorry, showing what's possible.

200 00:31:36.300 --> 00:31:41.429 Michael Schnuerle (OMF): I'm going to click over to the spec now and show you this. So…

201 00:31:41.850 --> 00:31:46.429 Michael Schnuerle (OMF): For… here's the example I just showed.

202 00:31:46.630 --> 00:32:06.620 Michael Schnuerle (OMF): of a more complex delivery example. There are simpler ones as well, with just… this is one with four overlapping trips in the same journey. Or maybe you only want to know there were two trips taken, you just want to know about trips, that's also possible as well. And you don't need to tie it together or get information about orders.

203 00:32:07.080 --> 00:32:15.339 Michael Schnuerle (OMF): So every trip has, a type, so a delivery type, a return, advertising, mapping, roaming, testing.

204 00:32:15.630 --> 00:32:22.880 Michael Schnuerle (OMF): And then there are lots of different optional trip attributes, like the type of driver, some…

205 00:32:23.050 --> 00:32:32.649 Michael Schnuerle (OMF): you create… you uniquely created UUID of the driver, so the primary driver, this, again, is not,

206 00:32:33.290 --> 00:32:36.700 Michael Schnuerle (OMF): Identifying a driver directly.

207 00:32:37.030 --> 00:32:50.669 Michael Schnuerle (OMF): But it could be used to connect it to an autonomous system or remote operations. What permit is this operating under? Does it have a payload? What's the count of parcels for this particular trip that are in the vehicle?

208 00:32:51.130 --> 00:33:10.949 Michael Schnuerle (OMF): What's the range? And then for every order, maybe you only want to track some one order per trip, you can still use these fields, but also orders have things like, when was it requested, when was it accepted, when was it picked up, when was it delivered, what address did it end up, originating from?

209 00:33:11.540 --> 00:33:18.470 Michael Schnuerle (OMF): what was the type of origin? So, ghost kitchens are, for instance, an example, and…

210 00:33:18.660 --> 00:33:32.869 Michael Schnuerle (OMF): Los Angeles that they wanted to track. Drop-off location, what kind of payload, so a categorization of the payload that could affect fees or, identification being required, like for medicine, or…

211 00:33:33.200 --> 00:33:38.259 Michael Schnuerle (OMF): alcohol, again, a parcel count for that trip.

212 00:33:38.460 --> 00:33:41.919 Michael Schnuerle (OMF): And then the type of destination it was going to.

213 00:33:42.950 --> 00:33:43.750 Michael Schnuerle (OMF): So…

214 00:33:44.330 --> 00:33:56.520 Michael Schnuerle (OMF): Yeah, there's a little bit of information about fares, and then information about the vehicles themselves as well. Really, all of this is optional, but some cities require this… some of this information.

215 00:33:57.430 --> 00:34:07.829 Michael Schnuerle (OMF): some accessibility, and then we get into the final… the vehicle information. So, I'll pause there. Again, I'll put this in the chat.

216 00:34:08.250 --> 00:34:17.900 Michael Schnuerle (OMF): So you can… look at delivery, and then I'll look at the… questions here,

217 00:34:20.830 --> 00:34:27.859 Michael Schnuerle (OMF): What about other mobile urban robots on sidewalks? Security, maintenance, sweep, brine, plow,

218 00:34:29.190 --> 00:34:41.370 Michael Schnuerle (OMF): That would not be delivery, so that would be more in the fleet vehicles, section, and that's where you can have plows and other things. So, I will show…

219 00:34:41.800 --> 00:34:45.790 Michael Schnuerle (OMF): I'll just pop over to the fleet mode real fast so you can see that.

220 00:34:48.510 --> 00:35:07.290 Michael Schnuerle (OMF): So you can see these types of vehicles, including street sweepers, snowplows, utility services, city fleets, garbage recycling, etc, inspection, permitting vehicles, maintenance vehicles, etc. So that's where you would track those things, as opposed to delivery.

221 00:35:10.190 --> 00:35:13.759 Michael Schnuerle (OMF): Alright, any other questions about the delivery mode?

222 00:35:18.760 --> 00:35:25.029 Michael Schnuerle (OMF): Or thoughts. Again, share if you're interested in using this at your organization.

223 00:35:39.630 --> 00:35:42.510 Michael Schnuerle (OMF): All right We'll continue on.

224 00:35:42.670 --> 00:35:45.869 Michael Schnuerle (OMF): There'll be time, I hope, for Q&A at the end as well.

225 00:35:46.870 --> 00:35:59.390 Michael Schnuerle (OMF): So, I'll say I'm going to stay a little bit later after the time, if there are questions, so I can stay and answer specific questions and get it on the recording if you have them at the end, over time.

226 00:35:59.390 --> 00:36:10.110 Michael Schnuerle (OMF): feature transit fixed routes, so we are, sort of ex… sort of had this support before, but more explicitly have it now, and this was out of a need of San Francisco SFMTA.

227 00:36:10.260 --> 00:36:15.479 Michael Schnuerle (OMF): Support for buses, shuttles, fixed route, fleets, and we…

228 00:36:15.560 --> 00:36:33.229 Michael Schnuerle (OMF): there's a way to connect this information in MDS, which is actually what happened to… what was supposed to happen in GTFS trips, stops and schedules, to determine things like the timing of the buses and what happened at the stops and missed stops and detours and things like that.

229 00:36:33.620 --> 00:36:48.569 Michael Schnuerle (OMF): This was, again, requested from SFMTA for commuter shuttle operations, connects it to GTFS, supports these under the passenger services mode, and provides this information via trips, telemetry, events, etc.

230 00:36:48.680 --> 00:37:01.710 Michael Schnuerle (OMF): And so, under trips now, there are some new fields, and we thought at first we had to add a lot of new fields to support this, but it ends up we really only had to add maybe two fields. One was a trip ID,

231 00:37:02.260 --> 00:37:06.199 Michael Schnuerle (OMF): And then the URL for the GTFS link.

232 00:37:06.320 --> 00:37:19.120 Michael Schnuerle (OMF): And then by using that, you can connect all the information that's in GTFS to everything that actually happened in operations in MDS, through this field, these two links. So…

233 00:37:19.300 --> 00:37:27.500 Michael Schnuerle (OMF): That's how we support it. If you look also up at the… The modes for…

234 00:37:28.870 --> 00:37:45.899 Michael Schnuerle (OMF): passenger modes. You can see that we've enumerated other things. Our buses, TNCs were already supported, private hire vehicles, shuttles, paratransit, on-demand vehicles, limousines, microtransit.

235 00:37:45.910 --> 00:37:49.570 Michael Schnuerle (OMF): Some of these are already supported, some are more clearly defined.

236 00:37:49.680 --> 00:38:02.150 Michael Schnuerle (OMF): And you also get information about these sorts of passenger trips and trip types, and information about them all the way from what you might expect from a taxi service to

237 00:38:02.420 --> 00:38:03.879 Michael Schnuerle (OMF): A bus service.

238 00:38:07.140 --> 00:38:14.839 Michael Schnuerle (OMF): Alright, any questions or thoughts, or if you are intending to use this, or want to use this for your city, leave something in the chat, or…

239 00:38:15.590 --> 00:38:17.370 Michael Schnuerle (OMF): Pandora, you can raise your hand.

240 00:38:22.770 --> 00:38:30.080 Michael Schnuerle (OMF): Question in the chat, do we know if there's a plan to code bus-only lanes? So… you in…

241 00:38:31.190 --> 00:38:41.250 Michael Schnuerle (OMF): In CDS, you can do this in some ways right now. So CDS, if you remember from the slide, defines a lot of the physical infrastructure.

242 00:38:41.260 --> 00:38:54.239 Michael Schnuerle (OMF): So you can define the location and rules around access of lanes or around curbs, and sometimes beyond curbs in whole areas, and you can say this is a bus-only lane.

243 00:38:54.680 --> 00:39:14.600 Michael Schnuerle (OMF): right now, MDS and CDS don't fully support the definitions of every type of lane or intersection or connections of sidewalks and bike lanes and bus lanes to other car lanes and things like that, but it is something we are exploring in the future, so if you have a need for this, we'd love to hear from you. Send us an email.

244 00:39:19.620 --> 00:39:36.520 Michael Schnuerle (OMF): All right, another thing that we clarified was MBS already supported all kinds of passenger services, including robotaxis, but we made it clear in the spec and the documentation that, this is definitely supported, four-hire AVs are supported.

245 00:39:36.850 --> 00:39:42.869 Michael Schnuerle (OMF): And with the tracking of special incidents that are really…

246 00:39:43.000 --> 00:39:53.780 Michael Schnuerle (OMF): tied more directly to autonomous vehicles, like unplanned stops, or remote takeovers, or the ability to understand crashes. That's also more clearly defined.

247 00:39:54.140 --> 00:39:57.819 Michael Schnuerle (OMF): And, as I'll get into in the next feature.

248 00:39:58.160 --> 00:40:06.070 Michael Schnuerle (OMF): there is a way in MDS to better communicate real-time digital policy for situational awareness for autonomous vehicles as well.

249 00:40:06.700 --> 00:40:10.140 Michael Schnuerle (OMF): So just to show you this in the spec.

250 00:40:10.740 --> 00:40:21.349 Michael Schnuerle (OMF): Just clarified it with a lot of different call-outs for different types of for-hire AVs and robo-taxis and other services.

251 00:40:21.650 --> 00:40:23.810 Michael Schnuerle (OMF): Clarifying the journey types.

252 00:40:23.950 --> 00:40:36.069 Michael Schnuerle (OMF): the types of trips, more trip attributes, and fairer attributes. Vehicle properties, inspection date, I think, is something new we added.

253 00:40:36.260 --> 00:40:41.420 Michael Schnuerle (OMF): And then, of course, all the incidents are connected to that as well.

254 00:40:42.530 --> 00:40:47.429 Michael Schnuerle (OMF): So, any questions about for-hire AV support in MVS 2.1?

255 00:40:52.570 --> 00:41:03.140 Michael Schnuerle (OMF): And again, some of this came from DC, who is going to be, asking for a lot of this, and some of it came from Seattle, and so…

256 00:41:03.370 --> 00:41:10.139 Michael Schnuerle (OMF): We're gonna talk about this feature next. This was a… there's a lot of changes to our digital policy part of MDS.

257 00:41:10.370 --> 00:41:18.289 Michael Schnuerle (OMF): that came out of a need of a project in Seattle, but then also became apparent that it was a need in other places as well.

258 00:41:18.400 --> 00:41:27.020 Michael Schnuerle (OMF): So, it used to be that the policy API endpoint was a push, a pull-only endpoint, where

259 00:41:27.120 --> 00:41:41.739 Michael Schnuerle (OMF): the… you as an operator would have to keep checking it to see if there was an update, and you sort of had to get the whole data feed back, and then compare it to what you already knew to figure out, oh, is there… is there an emergency here? Is there a change to the… the geofencing?

260 00:41:41.850 --> 00:41:50.060 Michael Schnuerle (OMF): But what we've done is added a number of new features to MDS 2.1 for policy that allows you to check it more lightweight.

261 00:41:50.140 --> 00:41:55.140 Michael Schnuerle (OMF): More frequently, and… or to have it pushed to you.

262 00:41:55.140 --> 00:42:11.829 Michael Schnuerle (OMF): from the city to the operator as it happens, and so this allows as fast as a one-second communication of policy changes and geofencing situations, especially for emergency response or unplanned events. So we have a new push endpoint, so instead of

263 00:42:12.990 --> 00:42:27.219 Michael Schnuerle (OMF): just only grabbing things and trying to understand them. You can get pushed new information as it happens. There's a way to filter the pull endpoints now as well, so if you do want to continue to pull, you can just

264 00:42:27.220 --> 00:42:33.939 Michael Schnuerle (OMF): Pass in the last updated date, so last time you checked, and only return things that are new since it was last updated.

265 00:42:34.010 --> 00:42:44.779 Michael Schnuerle (OMF): Or you can, and or you can pass in only show me active things, not past policies. And then some language to say that with this complexity.

266 00:42:45.030 --> 00:42:59.630 Michael Schnuerle (OMF): public agencies can manage these feeds with an API key if they want. We also wanted to avoid policy duplication, so there's a bit of a rule in there to prevent hundreds of duplicate policies being returned.

267 00:42:59.850 --> 00:43:02.519 Michael Schnuerle (OMF): And then some more examples as well.

268 00:43:03.690 --> 00:43:06.450 Michael Schnuerle (OMF): Yes, Pierre, please.

269 00:43:07.680 --> 00:43:26.839 Pierre Bouffort (Blue Systems): Yeah, just wanted to chime in again on this, because, so Blue Systems, we've been very much involved in the development of this new feature. I mean, that's… I segue into this. We… we were the ones to work with Seattle, on this system, and, and, in the work to push

270 00:43:26.840 --> 00:43:36.230 Pierre Bouffort (Blue Systems): 911 dispatches, translate them into MDS policies, and then push, to a operational system. This is really where this idea, stemmed from.

271 00:43:36.230 --> 00:43:51.110 Pierre Bouffort (Blue Systems): Without reiterating on this, because I know we've presented this system multiple times, I'm happy to, you know, answer any questions around this, but what I wanted to say here is that, as much as, like, this endpoint, the push policy endpoint, is, like.

272 00:43:51.350 --> 00:44:03.599 Pierre Bouffort (Blue Systems): a push policy endpoint. I also want to emphasize that it's also the first push endpoint for the city, for communication that goes from the city to the operators, right, in MDS.

273 00:44:03.600 --> 00:44:20.020 Pierre Bouffort (Blue Systems): So far, we have push endpoints for the operators to push data to the city. We have no push endpoints for the city to push data to the operators, right? And so, kind of, like, nudging my, you know, our friends from, you know.

274 00:44:21.360 --> 00:44:37.270 Pierre Bouffort (Blue Systems): mobility operators, delivery operators, but basically from the private sector, to have this in mind, that yes, it's started and stemmed with this policy API, but what we're really saying is that we now have a way for cities to push data over to you.

275 00:44:37.270 --> 00:44:49.670 Pierre Bouffort (Blue Systems): And so, this is something that probably will get your brain running, you know, on many different ideas that you might have, but this is where, you know, I think we as a private sector also have a lot to say in terms of

276 00:44:49.990 --> 00:44:57.610 Pierre Bouffort (Blue Systems): we want to make our operations, you know, we want to make the operations better, whatever mode you're operating. This is a great

277 00:44:57.610 --> 00:45:10.169 Pierre Bouffort (Blue Systems): you know, strong foundation to base a reflection off of, because now cities will be able to push information to you, so whatever you think is relevant is also, I think, is a great time for you as an operator to ask something from your cities

278 00:45:10.170 --> 00:45:20.469 Pierre Bouffort (Blue Systems): In terms of data sharing, right? If you're… if… I'm fairly confident, from our experience working with cities where, you know, if you were to say.

279 00:45:20.470 --> 00:45:38.469 Pierre Bouffort (Blue Systems): you know what, we as a bot operator, as a Navy operator, as a scooter operator, would be great if you could push to us, and we would make our operations a lot safer if you were able to push to us where, you know, roadblocks are happening, police roadblocks, or construction zones, or whatnot. I mean, you probably have a lot more ideas than I do right now, but…

280 00:45:38.470 --> 00:45:48.779 Pierre Bouffort (Blue Systems): this is the base we can build on to achieve that. So, yeah, just wanted to mention that I see this as much more than just pushing policies. It's really pushing information.

281 00:45:48.780 --> 00:45:50.370 Pierre Bouffort (Blue Systems): Per se, from UC.

282 00:45:51.320 --> 00:46:10.320 Michael Schnuerle (OMF): Yes. Thank you for all your work on this, Pierre, and for Blue Systems, and Seattle DOT as well, for working on this. I think it's been a great project, and definitely replicable in other cities. That's the intention. And it is, you know, the name of the API endpoint is MDS Policy.

283 00:46:10.320 --> 00:46:17.699 Michael Schnuerle (OMF): But it is not just policy, it's really information, and so this information, communications of information.

284 00:46:17.790 --> 00:46:22.199 Michael Schnuerle (OMF): is what is the real great feature here.

285 00:46:22.590 --> 00:46:27.169 Michael Schnuerle (OMF): This is… this gets… starts to get a little more technical, but I will put in the chat here.

286 00:46:27.360 --> 00:46:31.129 Michael Schnuerle (OMF): The policy post endpoint.

287 00:46:32.000 --> 00:46:42.780 Michael Schnuerle (OMF): link, and then you can look at the policy objects and just see the information that's, gonna be part of it, or is already part of it, actually. But the,

288 00:46:43.230 --> 00:46:50.259 Michael Schnuerle (OMF): on the same page as the get information for policy and how you can pass in the last updated

289 00:46:50.470 --> 00:46:58.710 Michael Schnuerle (OMF): Date, or, active-only, flags, which limit the amount of data that comes through.

290 00:47:02.210 --> 00:47:16.349 Michael Schnuerle (OMF): All right, and then enforcement of violations. The next two features and the last ones I'm going to talk about really come from the curb data specification work, and we duplicated them in MDS because of the need for something either identical or similar.

291 00:47:16.370 --> 00:47:23.949 Michael Schnuerle (OMF): And so, enforcement of violations information can be sent in MDS as well, as it already can in CDS now.

292 00:47:23.990 --> 00:47:39.240 Michael Schnuerle (OMF): And so, for enforcement, you can connect these to incidents, or they can be independent. You can describe information about citation, the cost, action taken, warning… was it a warning? What violations? Or,

293 00:47:39.240 --> 00:47:51.959 Michael Schnuerle (OMF): what things were violated, and actually provide in another object the violations list. Again, optional, but can be tied to incidents or enforcement actions, and you can describe the violation code name and cost, and

294 00:47:52.000 --> 00:47:54.490 Michael Schnuerle (OMF): Just to show you what these objects look like.

295 00:47:55.780 --> 00:48:14.130 Michael Schnuerle (OMF): this is really all the things I just mentioned, but listed in code version, and then for the violations, you can get an array of violations attached to an enforcement object, and for each violation, you can say that what code, what was the name of that, and was there any cost associated? So…

296 00:48:14.370 --> 00:48:24.780 Michael Schnuerle (OMF): Again, this is information coming from the operators to the cities, and this could be something they detect or maybe are asked to share.

297 00:48:24.900 --> 00:48:29.610 Michael Schnuerle (OMF): In CVS, many times this is detected through…

298 00:48:29.740 --> 00:48:38.410 Michael Schnuerle (OMF): cameras or other sensors in MDS, this would come from the operators. So we'll see. There was some need for this, and we'll see how this gets used in practice.

299 00:48:40.720 --> 00:48:45.209 Michael Schnuerle (OMF): And the last thing I want to mention, again, coming from CVS, is this ability to link

300 00:48:45.210 --> 00:49:00.780 Michael Schnuerle (OMF): really many parts of MDS to any other external data standards or data sources. So, I'll start with the examples down here. So, for instance, maybe in MDS events, there's an event ID,

301 00:49:01.040 --> 00:49:03.499 Michael Schnuerle (OMF): And you want to connect it to your…

302 00:49:03.800 --> 00:49:08.980 Michael Schnuerle (OMF): connected Work Zone API data feed for their own event.

303 00:49:08.980 --> 00:49:10.450 Michael Schnuerle (OMF): closure feature.

304 00:49:10.450 --> 00:49:28.990 Michael Schnuerle (OMF): then you can actually attach… you can send that information of… there's… here's the link to the connected work zone data feed, here's the event ID that connects to the ID over here, and so you get this sense of other information from other sources. So maybe your trip ends at a CES curb zone, you can connect the event

305 00:49:28.990 --> 00:49:47.910 Michael Schnuerle (OMF): ID at the CDS… in the CDS side to the trip end and MDS, or maybe your incident has an ID and it goes to a police report, that's… and you want to provide a URL to that, and some other information. And it can link to… so it can go to any

306 00:49:48.220 --> 00:49:55.860 Michael Schnuerle (OMF): External API, we have a list of some options here, GBFS, GTFS, Waze, TOMP,

307 00:49:56.100 --> 00:50:07.910 Michael Schnuerle (OMF): Nevi, Daytech, some of these are European. But it could also just link to web pages, so maybe this trip, there's some reason you would want to connect that trip to a web page for maybe,

308 00:50:07.910 --> 00:50:21.869 Michael Schnuerle (OMF): an event closure, or something that happened for… on a specific trip for a specific reason. It can go to web pages, documents, reports, that provide more context. And so this external reference is available in MDS Events.

309 00:50:22.080 --> 00:50:32.960 Michael Schnuerle (OMF): trips or incidents in both provider and agency, and it was already added to the recently launched CDS1.1 in the same way.

310 00:50:33.400 --> 00:50:36.049 Michael Schnuerle (OMF): So, just wanted to point this out.

311 00:50:36.650 --> 00:50:43.430 Michael Schnuerle (OMF): This external reference option was a way to, make these connections.

312 00:50:45.480 --> 00:50:52.440 Michael Schnuerle (OMF): To other specs in a way that was, pretty complete and And, relevant.

313 00:50:56.550 --> 00:51:04.689 Michael Schnuerle (OMF): Alright, so now, quick engagement question as you think about other questions you have about the MDS 2.1 release, so…

314 00:51:05.080 --> 00:51:19.400 Michael Schnuerle (OMF): This is Q&A time. I'll stay late if there's more questions that need to be answered. In the meantime, what MDS 2.1 feature are you most excited about using when it launches?

315 00:51:22.100 --> 00:51:27.360 Michael Schnuerle (OMF): And feel free to also… ask general questions, and then I have,

316 00:51:27.690 --> 00:51:31.829 Michael Schnuerle (OMF): Some prompts that might get you thinking about certain questions as well.

317 00:51:33.060 --> 00:51:34.230 Michael Schnuerle (OMF): Yes, Aileen.

318 00:51:36.570 --> 00:51:42.410 Aylene McCallum (OMF): I wanted to also ask that question in a little bit different way, but maybe also share

319 00:51:42.810 --> 00:51:43.700 Aylene McCallum (OMF): you know.

320 00:51:43.880 --> 00:51:54.809 Aylene McCallum (OMF): what are you… what features are you excited about using, but, like, maybe what might you need to do internally to be able to use them? Like, we're… I… I want to…

321 00:51:54.810 --> 00:52:06.290 Aylene McCallum (OMF): Acknowledge that, you know, maybe there's something you have to change internally in your system to be able to use them, but please, still, we want to know, like, what you're excited about using, and then, you know, what are some of the steps you might have to take?

322 00:52:06.360 --> 00:52:10.810 Aylene McCallum (OMF): You don't have to reveal any secrets, but just generally good.

323 00:52:16.170 --> 00:52:21.449 Michael Schnuerle (OMF): And as you're thinking about that, here are some prompts, so if you're not sure what sort of questions

324 00:52:21.890 --> 00:52:25.750 Michael Schnuerle (OMF): you, have. These might get you thinking.

325 00:52:26.530 --> 00:52:31.430 Michael Schnuerle (OMF): About, in general, MDS questions and answers, what do you need to know?

326 00:52:31.610 --> 00:52:34.220 Michael Schnuerle (OMF): Which is part of Aileen's comment.

327 00:52:34.720 --> 00:52:40.290 Michael Schnuerle (OMF): Maybe you have a scenario, you're not sure if MDS applies to it. You can ask about that.

328 00:52:40.650 --> 00:52:48.029 Michael Schnuerle (OMF): And then… More of general thoughts, what features resonate with you, and what will you use from 2.1?

329 00:53:20.920 --> 00:53:24.419 Michael Schnuerle (OMF): And maybe there are no questions about MBS? Maybe…

330 00:53:24.900 --> 00:53:26.519 Michael Schnuerle (OMF): We'll give you all a little more time.

331 00:53:30.630 --> 00:53:36.470 Michael Schnuerle (OMF): I kind of… I thought maybe some of this might be new for some of you, so I figured there would be some questions, so…

332 00:53:37.170 --> 00:53:40.640 Michael Schnuerle (OMF): If there aren't, that's okay, but… Feel free to ask.

333 00:53:46.540 --> 00:54:02.210 Aylene McCallum (OMF): I'll also add, while we're waiting for people, if anyone's kind of still thinking about a question, that we will be talking about these features in a little more detail, at our MDS 101 session, and

334 00:54:02.210 --> 00:54:13.430 Aylene McCallum (OMF): at the in-person workshop at NACTO, where we're going to be basically combining our three introductory OMF Academy courses,

335 00:54:13.460 --> 00:54:25.370 Aylene McCallum (OMF): Digital Infrastructure 101, CDS 101, MDS 101. We will be talking about this a little bit in person, and then obviously at the virtual session. So,

336 00:54:25.570 --> 00:54:44.489 Aylene McCallum (OMF): happy to get your feedback if you're, you know, want us to explore a particular issue in a little bit more detail. We love to make sure that these sessions respond to your needs and your interests, so feel free to send us an email or a little note saying, hey, I hope you cover

337 00:54:44.630 --> 00:54:54.260 Aylene McCallum (OMF): Blah, blah, blah. And then, you know, sign up to attend these sessions, because we'll go into them in more detail, go into the details in more detail.

338 00:55:00.930 --> 00:55:08.880 Michael Schnuerle (OMF): And I see… I do see, Lars saying the external references, needs exploring, and yes, it can be combined with CDS, which is…

339 00:55:08.900 --> 00:55:21.109 Michael Schnuerle (OMF): Really, the start of that was that connection, making a more direct connection between parts of CVS and MDS. There's also a request for, I think, the use case list for MDS,

340 00:55:21.130 --> 00:55:24.279 Michael Schnuerle (OMF): I'm gonna do a Google search here, let's see if this works.

341 00:55:24.810 --> 00:55:25.600 Michael Schnuerle (OMF): Use.

342 00:55:26.120 --> 00:55:27.470 Michael Schnuerle (OMF): Cases.

343 00:55:29.670 --> 00:55:33.069 Michael Schnuerle (OMF): There it is. Okay, so we have a blog post about it.

344 00:55:34.620 --> 00:55:38.509 Michael Schnuerle (OMF): That's the blog post, and then in the blog post, you can…

345 00:55:38.790 --> 00:55:52.839 Michael Schnuerle (OMF): get a summary, but also go to this… I'll put this link in here… the gallery view of all the defined MDS use cases, and just to point out, it's filterable, so you could say, like, where the use case involves

346 00:55:53.000 --> 00:55:54.180 Michael Schnuerle (OMF): Yeah, maybe.

347 00:55:54.640 --> 00:55:57.300 Michael Schnuerle (OMF): Speed… there's 3…

348 00:55:57.730 --> 00:56:10.470 Michael Schnuerle (OMF): Related to that, and each one you can click and sort of see which APIs are relevant to that use case, and which parts or fields, even, are needed if you want to have that use case in which modes as well.

349 00:56:10.570 --> 00:56:19.230 Michael Schnuerle (OMF): So… That's that. Here is the… use case database.

350 00:56:20.610 --> 00:56:22.590 Michael Schnuerle (OMF): And I hope that answers your question.

351 00:56:28.370 --> 00:56:31.379 Michael Schnuerle (OMF): Alright, any other, questions or thoughts?

352 00:56:32.180 --> 00:56:33.779 Michael Schnuerle (OMF): Yes, thanks, great.

353 00:56:41.210 --> 00:56:46.100 Michael Schnuerle (OMF): Alright, just to point out that our next meeting, we may 7th,

354 00:56:47.590 --> 00:56:53.280 Michael Schnuerle (OMF): We don't have the topic set for that yet. The steering committee will help define that. It may be…

355 00:56:54.730 --> 00:57:13.689 Michael Schnuerle (OMF): I don't know, we'll see what that is. Because the release is going to go through the approval process, we're not sure what that would be. Maybe it'll be presentations from people or some other background information, or maybe something about the release that the Tech Council or the board has… requires some feedback or changes.

356 00:57:14.530 --> 00:57:25.189 Michael Schnuerle (OMF): But thanks a lot for attending. Look us up on… online, and feel free to email us or email me questions you have about MDS 2.1, and we'll be sure to answer it.

357 00:57:35.550 --> 00:57:37.380 Michael Schnuerle (OMF): Thanks, have a great day.