Skip to content

Web conference notes, 2026.07.09 (MDS Working Group)

Jump to bottom
Michael Schnuerle edited this page Jul 10, 2026 · 6 revisions

MDS Working Group

MDS 2.1 Modes Banner

Agenda

📅 NEW DATE - JULY 9‼️ (moved from July 2)

MDS 2.1 Launch

MDS 2.1 is approved by the MDS steering committee, and OMF Tech Council and Board. We will discuss new features and share launch materials.

Agenda

  1. Intro and announcements (5 min)
  2. New MDS Steering Committee (5 mins)
  3. MDS 2.1 Launch (45 mins)

MDS 2.1 Release Plan with details and links.

Action Items and Decisions

  1. Start using MDS 2.1 and write it into your RFPs, contracts, and permits (see guidance)
  2. Let the OMF know if you use and are interested in updating our OpenAPI schema for MDS 2.1

Minutes

Notes

See meeting slides, chat log, and recording for full details.

Chat

Click to view meeting chat

Transcript

Click to view full meeting transcript

1 00:00:00.360 --> 00:00:01.040 Michael Schnuerle (OMF): Okay.

2 00:00:05.060 --> 00:00:15.279 Michael Schnuerle (OMF): Alright, welcome everybody to this month's MDS Working Group meeting. Today we're going to be talking about MDS 2.1 and the official launch

3 00:00:15.520 --> 00:00:18.830 Michael Schnuerle (OMF): of 2.1 after a lot of work.

4 00:00:21.250 --> 00:00:30.249 Michael Schnuerle (OMF): A little bit of housekeeping. If you haven't already set your organization name after your name in the participant list, you can go over to your name and

5 00:00:30.390 --> 00:00:37.380 Michael Schnuerle (OMF): Click the three dots and, rename yourself to add your organization so you know who you're representing.

6 00:00:37.720 --> 00:00:42.540 Michael Schnuerle (OMF): mute yourself. But right now feel free to introduce yourself in the chat.

7 00:00:42.700 --> 00:00:49.079 Michael Schnuerle (OMF): So who you are, where you're from, who you're representing, why you're here, things like that. We'd love to hear from you.

8 00:00:49.440 --> 00:01:03.619 Michael Schnuerle (OMF): Use the chat, you can leave questions there as we go, and I'll check it periodically, or use the raise hand feature. A lot of these features of MDS 2.1 we've reviewed in prior meetings, so…

9 00:01:03.840 --> 00:01:16.039 Michael Schnuerle (OMF): If you do want to ask a question about it, because I'll be going slightly faster today on that part, use the raise hand feature. We'll make sure to answer your questions.

10 00:01:16.310 --> 00:01:24.199 Michael Schnuerle (OMF): And that part will be a little bit more informal. This meeting is being recorded and will be published with notes.

11 00:01:25.510 --> 00:01:31.219 Michael Schnuerle (OMF): So we'll do a little intro, talk to the steering committee, and then mostly talk about the MDS 2.1 launch.

12 00:01:35.140 --> 00:01:51.729 Michael Schnuerle (OMF): So the Open Mobility Foundation is a global nonprofit founded in 2019 to support cities and industry, helping each of them get to yes together, city founded and city led. And we want to solve problems and identify solutions together.

13 00:01:51.870 --> 00:01:54.090 Michael Schnuerle (OMF): Build everything in the open.

14 00:01:54.210 --> 00:02:06.639 Michael Schnuerle (OMF): Everything we do is built publicly on GitHub with public mailing lists and meetings like this one. Had a lot of participation, and we built MDS and CDS this way.

15 00:02:08.160 --> 00:02:22.200 Michael Schnuerle (OMF): MDS is a standard that enables right-of-way regulation, digital policy, geofencing, and two-way communication between companies and public agencies. You can see our steering committee members on the right, and I'll talk a little bit more about that.

16 00:02:22.390 --> 00:02:23.410 Michael Schnuerle (OMF): In a bit.

17 00:02:24.210 --> 00:02:37.749 Michael Schnuerle (OMF): We are a member organization, so lots of public sector members, and here are some of our private sector members. These are our currently five premier members, so we want to thank them.

18 00:02:37.860 --> 00:02:47.200 Michael Schnuerle (OMF): and our associate members at the moment. Aileen, would you like to say anything about our private sector members.

19 00:02:47.720 --> 00:02:59.930 Aylene McCallum (OMF): Yeah, I will, give some shout-outs to a few of our more recently joined members. I try to keep track of who I've, announced, and we've had a bunch of new members lately, so…

20 00:02:59.930 --> 00:03:17.220 Aylene McCallum (OMF): Wanted to give a shout out to Daro, who, they're recently new members. They are the logo just to the right of Auto Lane. Laz is a new member as well. They recently joined, I think it was last month, I'm not sure if I announced them the last time.

21 00:03:17.220 --> 00:03:24.069 Aylene McCallum (OMF): We were meeting, and then I will do a special call-out to Revolution.

22 00:03:24.070 --> 00:03:31.209 Aylene McCallum (OMF): Which is, Bicycle Transit Systems. They just changed their name. So, oh, good, Grant, I'm glad you're here.

23 00:03:31.210 --> 00:03:37.319 Aylene McCallum (OMF): to see that. So, just really excited to continue to support our members.

24 00:03:37.320 --> 00:03:56.119 Aylene McCallum (OMF): You know, we'll give you shoutouts if you have a name change and you join the OMF, any big, really fun announcements, happy to, prop you up a little bit. But overall, thank you to all of our Premier and Associate members for helping to support the work that we do. We can't host these meetings and do the work we do to

25 00:03:56.120 --> 00:04:07.300 Aylene McCallum (OMF): for example, release MDS 2.1 without you, and, and then also put on programs like the OMF Academy and the OMF Summit. So, we'll see you around. Thank you.

26 00:04:08.700 --> 00:04:10.509 Michael Schnuerle (OMF): Thank you all. Thanks, Elaine.

27 00:04:11.730 --> 00:04:23.789 Michael Schnuerle (OMF): As said, MDS is a global standard. We know of over 200 commercial mobility service providers that operate in cities around the world that send MDS to cities.

28 00:04:23.790 --> 00:04:34.830 Michael Schnuerle (OMF): They operate in over 1,200 cities in dozens of countries, maybe, I think, over 75 countries, representing billions of trips taken.

29 00:04:35.670 --> 00:04:44.350 Michael Schnuerle (OMF): We do have an OMF calendar, if you would like to follow along with everything we do, conferences, meetings, webinars, things like that.

30 00:04:44.780 --> 00:04:46.450 Michael Schnuerle (OMF): Put that in the chat.

31 00:04:50.420 --> 00:05:04.839 Michael Schnuerle (OMF): And I'd like to, talk now a little bit about our steering committee. So, in order to set the agendas for these meetings and approve the releases, we have a steering committee as part of our governance body, bodies at the OMF.

32 00:05:04.990 --> 00:05:22.909 Michael Schnuerle (OMF): The steering committee for the last year has been these folks. This is who was elected a year ago, and they've been great. We meet monthly. We talk about all sorts of things and also set the agendas here. They helped approve the MDS 2.1 release.

33 00:05:23.020 --> 00:05:24.760 Michael Schnuerle (OMF): And,

34 00:05:25.040 --> 00:05:37.119 Michael Schnuerle (OMF): they've been… they've been great, so I just want to give them a shout out, so thank you all. And their one-year term is up, and we've been… we had a nomination process, and we have a list of candidates for the next year.

35 00:05:37.310 --> 00:05:52.899 Michael Schnuerle (OMF): You can see them here. Many people are returning from last year, and these candidates are up for a vote from OMF membership. So if you are an OMF member, check your email. Yesterday, there was a ballot that was sent out.

36 00:05:52.900 --> 00:06:02.250 Michael Schnuerle (OMF): where you can vote on these folks. So just real quick, if you're part of these candidates, feel free to say hi in the chat.

37 00:06:02.400 --> 00:06:13.310 Michael Schnuerle (OMF): But otherwise, since it may be hard to read, I'm just going to read off the organizations that are represented. So from the public sector, we've got LADOT, Seattle SDOT,

38 00:06:13.440 --> 00:06:15.979 Michael Schnuerle (OMF): SFMTA in San Francisco.

39 00:06:16.550 --> 00:06:19.550 Michael Schnuerle (OMF): City of Boston, City of Alexandria.

40 00:06:19.740 --> 00:06:29.909 Michael Schnuerle (OMF): New York City Department of Transportation, and the Portland Bureau of Transportation. So, great public sector, both geographic and size representation there.

41 00:06:30.160 --> 00:06:37.180 Michael Schnuerle (OMF): And then from the private sector, we've got Blue Systems, Waymo, Mojo.

42 00:06:37.440 --> 00:06:40.579 Michael Schnuerle (OMF): Last parking. Serve robotics.

43 00:06:40.800 --> 00:06:41.870 Michael Schnuerle (OMF): And Ricks.

44 00:06:42.340 --> 00:06:58.899 Michael Schnuerle (OMF): Revolution, formerly Bicycle Transit Systems, and Dara Technologies. So, welcome. All of them are OMF members and nominated themselves to volunteer on the steering committee, so we'll let you know next meeting what the results of the voting were.

45 00:06:59.540 --> 00:07:01.679 Michael Schnuerle (OMF): Thanks to all of you for volunteering.

46 00:07:04.160 --> 00:07:19.940 Michael Schnuerle (OMF): All right, so let's jump into MDS. The first part of this, I'm going to give just a quick MDS overview. Many of you have probably heard this before. There's slightly different information, but pretty much what you might be expecting, but for those of you who are new.

47 00:07:20.250 --> 00:07:37.610 Michael Schnuerle (OMF): Mds supports the management of lots of different vehicles, movements, programs across different public agencies, cities, counties, countries, states. And, you can see them… a representation of those listed here. We'll get into some more of that later.

48 00:07:38.580 --> 00:07:50.870 Michael Schnuerle (OMF): Data from these vehicles can come to cities, so cities can write into data sharing requirements or operating permits, to get information about vehicles' location and status.

49 00:07:50.960 --> 00:08:04.570 Michael Schnuerle (OMF): Vehicle information, like the properties, attributes of the vehicles, accessibility, trip details, distance, duration, fares, even incidents that may have happened along the way, trip breadcrumbs.

50 00:08:04.940 --> 00:08:10.700 Michael Schnuerle (OMF): and stop details, things like that. There's actually a lot more, but that's a high-level overview.

51 00:08:11.890 --> 00:08:20.399 Michael Schnuerle (OMF): And then cities can also provide information to people operating vehicles in the public realm. So instead of

52 00:08:20.470 --> 00:08:37.070 Michael Schnuerle (OMF): maybe communicating this via PDFs and emails and phone calls, this can all be shared digitally in real time using MDS in a computer-readable format. So all of the data sharing requirements can be communicated with this, and then any sort of geofencing.

53 00:08:37.070 --> 00:08:43.830 Michael Schnuerle (OMF): Emergency operations or event rules can also be communicated with MDS, and that helps

54 00:08:43.940 --> 00:08:48.439 Michael Schnuerle (OMF): The operations of everything in the public right-of-way go smoothly.

55 00:08:50.480 --> 00:09:02.370 Michael Schnuerle (OMF): MDS is made up of lots of different APIs and endpoints, as we call them. You can see a little bit of it here. There's some data from operators and some data from cities.

56 00:09:03.840 --> 00:09:15.119 Michael Schnuerle (OMF): We have a lot of use cases for MDS, over 60 documented, probably a lot more, well, definitely a lot more. And this has been updated for 2.1, which I'll mention later.

57 00:09:17.050 --> 00:09:30.459 Michael Schnuerle (OMF): We have a lot of privacy resources, whether you're operating in the United States, Europe, or elsewhere. We have privacy guide for cities, principles, the state of practice, and guidance for using MDS under GDPR.

58 00:09:32.470 --> 00:09:49.210 Michael Schnuerle (OMF): And just to show how this connects to CDS or other data specification, they work together to manage the public space. Both provide digital policy, data sharing, and metrics, and they could be used independently or together.

59 00:09:49.620 --> 00:09:58.540 Michael Schnuerle (OMF): MBS is all about vehicle locations, the status of those vehicles, incidents that happens, and trips taken across a whole jurisdiction.

60 00:09:59.060 --> 00:10:03.919 Michael Schnuerle (OMF): CVS is about specific pieces of infrastructure, like curbs.

61 00:10:04.020 --> 00:10:16.790 Michael Schnuerle (OMF): objects at those curbs, and then tracking the activity and interactions with those locations with vehicles via MDS, and then track that activity in CDS.

62 00:10:16.940 --> 00:10:19.349 Michael Schnuerle (OMF): So that's how they overlap at the moment.

63 00:10:23.200 --> 00:10:32.700 Michael Schnuerle (OMF): All right, so now I'm going to get into a little slight background on 2.1 and then the features. So as I go through this, I've done a lot of this before.

64 00:10:32.820 --> 00:10:39.560 Michael Schnuerle (OMF): Since we've had our preview meeting about this a month ago, and then even the month before that, we've talked about it.

65 00:10:39.700 --> 00:10:47.929 Michael Schnuerle (OMF): Not a lot has changed through our approval process. So a lot of this is going to be the same content. But so I'm going to go through it.

66 00:10:48.240 --> 00:10:56.589 Michael Schnuerle (OMF): Not too quickly, but at a good pace. But if at any point you feel like I'm glossing over something or you have a question.

67 00:10:56.610 --> 00:11:09.640 Michael Schnuerle (OMF): just use the raised hand button to get my attention, and then I'll call on you, and you can ask your question. Or you can leave it in the chat at the end of the presentation. I'll take a look, and I can answer those questions, too.

68 00:11:11.920 --> 00:11:26.240 Michael Schnuerle (OMF): So, MDS release duration at the bottom, these bars represent different historic releases of MDS. You can see each one is taking, longer, a number of days to

69 00:11:26.670 --> 00:11:35.969 Michael Schnuerle (OMF): both propose, talk about, draft a solution, update for, and then approve. So 2.1 has taken the longest.

70 00:11:36.200 --> 00:11:45.759 Michael Schnuerle (OMF): This is partially because MDS has been around for a while now, and there's added complexity whenever you add something new.

71 00:11:45.800 --> 00:11:58.290 Michael Schnuerle (OMF): But also, we have intentionally slowed the releases down. It used to be that cities were moving a little too fast with the releases, and the private sector wanted things to be a little more stable.

72 00:11:58.350 --> 00:12:07.519 Michael Schnuerle (OMF): So we intentionally have slowed things down. That doesn't mean we couldn't do a minor release quicker in the future, but that's the pace we've had recently.

73 00:12:08.060 --> 00:12:18.420 Michael Schnuerle (OMF): And that gives people time to understand what's coming, to build to it before it's even released, and make sure they understand what's in it.

74 00:12:18.520 --> 00:12:22.170 Michael Schnuerle (OMF): Before the release comes out to the public and is approved.

75 00:12:24.420 --> 00:12:39.960 Michael Schnuerle (OMF): We had a 2.1 release plan web page with a lot of things. We were tracking timelines and issues and features. The release is now officially approved through all of our OMF approval processes. That includes the steering committee.

76 00:12:39.960 --> 00:12:52.839 Michael Schnuerle (OMF): The Technology Council, the OMF City-Led Board, and all these, this is now still there online, but sort of archived because there won't be any more updates to it.

77 00:12:52.970 --> 00:12:58.960 Michael Schnuerle (OMF): We'll think about a future release after this, but for now, we're happy that 2.1 is out the door.

78 00:13:01.270 --> 00:13:20.309 Michael Schnuerle (OMF): This is an important slide. This is a release acknowledgment. So this is a list of every organization that either created a pull request on GitHub, which is a very specific recommended change to the specification, or created an issue to talk about some change that eventually was

79 00:13:20.310 --> 00:13:26.580 Michael Schnuerle (OMF): made into the spec. And so, you can see, this pretty good list of public and private sector

80 00:13:26.580 --> 00:13:27.750 Michael Schnuerle (OMF): Entities.

81 00:13:27.750 --> 00:13:34.069 Michael Schnuerle (OMF): Highlighted in the middle are our commercial OMF members that, either

82 00:13:34.190 --> 00:13:43.929 Michael Schnuerle (OMF): created a pull request or an issue. So I just want to thank Blue Systems, Indrix, and Populous for being really on top of things and

83 00:13:44.110 --> 00:13:50.970 Michael Schnuerle (OMF): helping out and helping the development in a very targeted way for MDS 2.1.

84 00:13:51.320 --> 00:14:05.460 Michael Schnuerle (OMF): Our steering committee, of course, helped with this as well. And lots of other organizations that are not on this list participated in calls like this on GitHub with comments or on different calls. So we appreciate your time too.

85 00:14:05.570 --> 00:14:25.069 Michael Schnuerle (OMF): And overall, there are 240 incremental changes made over the course of this release. So that's 240 commits, as they're called on GitHub. And that's a pretty good number for a release, whether it's even a major or minor release.

86 00:14:27.460 --> 00:14:34.030 Michael Schnuerle (OMF): So let's get into new features. There's a lot of new features, even though this is a non-breaking

87 00:14:34.090 --> 00:14:53.669 Michael Schnuerle (OMF): 2.1 release of MDS, we were still able to add a lot of new optional things. And there's high level items and then some more details. So high level, we overhauled modes and added a lot more clarity to what modes are supported and added some new support there.

88 00:14:54.170 --> 00:14:58.140 Michael Schnuerle (OMF): We had support for incidents and crashes being tracked in MDS.

89 00:14:58.570 --> 00:15:11.029 Michael Schnuerle (OMF): Delivery mode, full support of different types of delivery instead of just sidewalk robots. Transit fixed route support for buses and different types of shuttles.

90 00:15:11.580 --> 00:15:19.550 Michael Schnuerle (OMF): for hire autonomous vehicles. It was already supported, but we made sure that it was clear in the spec that this is something MDS can handle.

91 00:15:20.110 --> 00:15:22.149 Michael Schnuerle (OMF): real-time digital policy.

92 00:15:22.410 --> 00:15:30.390 Michael Schnuerle (OMF): enforcement of violations. And we'll get into each of these with a slide later, but that's the high-level overview of top-level features.

93 00:15:31.950 --> 00:15:35.460 Michael Schnuerle (OMF): And then there are a bunch of additional features in 2.1.

94 00:15:35.560 --> 00:16:00.109 Michael Schnuerle (OMF): We added the ability to link to external references to connect information in MDS to other specs and docs. We did this with CDS in its last release. MDS 2.1 also has custom attributes, which we also did in CDS, which allows you to temporarily add custom fields that may not be in MDS yet, but may support maybe needed or

95 00:16:00.110 --> 00:16:03.690 Michael Schnuerle (OMF): Needed to support your program in a specific jurisdiction.

96 00:16:04.080 --> 00:16:06.470 Michael Schnuerle (OMF): You can read more about that in the spec.

97 00:16:06.690 --> 00:16:19.699 Michael Schnuerle (OMF): We moved a bunch of features that have been flagged as a beta feature out of beta, because they either are stable, or have been used, or haven't needed any changes for a while.

98 00:16:19.850 --> 00:16:33.829 Michael Schnuerle (OMF): In provider and agency, which is data coming from operators, we added lifecycle operations information to vehicles. We clarified what start, stop, cancel, and end events are.

99 00:16:33.870 --> 00:16:45.580 Michael Schnuerle (OMF): We clarified the relationship between vehicles and vehicle status endpoints, and then we were able to add support for multiple vehicle requests at once.

100 00:16:46.820 --> 00:17:03.520 Michael Schnuerle (OMF): And then under digital policy, which is information coming from cities, we clarified that policy can require authorization in certain cases or for certain modes and programs. We added a geography filter to policy requirements.

101 00:17:03.520 --> 00:17:18.000 Michael Schnuerle (OMF): So you can clarify those when you define your data sharing requirements. And then added a rule unit of distance traveled, which is part of a way you can specify different policies coming from your agency.

102 00:17:20.099 --> 00:17:25.540 Michael Schnuerle (OMF): Alright, so… Let's dig into each of the top-level features. There's about 7 of them.

103 00:17:25.930 --> 00:17:40.209 Michael Schnuerle (OMF): And again, if you have questions about these as I go through them, use the raise hand feature. So this is a view of how we were diagramming MDS 2.0, which added modes, as we called them. You can see the four modes there on the right.

104 00:17:40.440 --> 00:17:58.220 Michael Schnuerle (OMF): And this still is a two-way communication expanded for micromobility. And we had these defined for 2.0. In 2.1, we've expanded the types of vehicles and services and clarified some of the names of these modes.

105 00:17:58.580 --> 00:18:18.170 Michael Schnuerle (OMF): And so you can see, as I showed earlier, this breakdown of different types of vehicles, services, programs that are now supported under MDS 2.1. We'll get into some of the new ones in future slides, but you can get a good sense of those here.

106 00:18:22.400 --> 00:18:25.329 Michael Schnuerle (OMF): Another feature we added were incidents.

107 00:18:25.460 --> 00:18:44.390 Michael Schnuerle (OMF): and crashes. We started with the conversation about how to track crashes, which actually came from a long time ago. 2021 was… there was a proposal from VIANOVA to add this, and it wasn't really possible at the time with micromobility technology, but now with all the different types of modes, this is certainly possible.

108 00:18:44.540 --> 00:18:50.959 Michael Schnuerle (OMF): And we were able to add not just crashes, but all different types of incidents as required by

109 00:18:50.970 --> 00:19:06.939 Michael Schnuerle (OMF): some entities, some jurisdictions needed to track other things by law, so we added a few of those. You can see a list on the left, everything from unplanned stops to information that could be tracked from autonomous vehicles.

110 00:19:07.130 --> 00:19:14.530 Michael Schnuerle (OMF): Tipovers, obstructions in the road, vandalism, theft, near misses, which are actually being used.

111 00:19:14.680 --> 00:19:29.839 Michael Schnuerle (OMF): In Amsterdam, we'll talk about that briefly, and collisions or crashes. And each of these gets information about, short-term information, like the location, date, key time severity, was there a medical response, and accelerometer data.

112 00:19:30.050 --> 00:19:35.389 Michael Schnuerle (OMF): And then more detailed information can be added in the future by a report ID.

113 00:19:35.610 --> 00:19:45.980 Michael Schnuerle (OMF): And this is all connected to the MDS telemetry endpoint, which already tracks this information for vehicles, and it sort of associates this now with the incident.

114 00:19:48.030 --> 00:19:52.730 Michael Schnuerle (OMF): And then I want to thank Pierre from Blue Systems for coming up with this slide.

115 00:19:52.810 --> 00:20:01.570 Michael Schnuerle (OMF): This is just another view into that. So before MDS 2.1, data for incidents and crashes would be reported by

116 00:20:01.610 --> 00:20:20.669 Michael Schnuerle (OMF): Emails, phone would be delayed a lot. Lots of different sources, different formats, different timing. Difficult to understand and make sense of all those. With MDS 2.1, the reporting of incidents and crashes are standardized now. This includes the things I said, GPS location.

117 00:20:20.670 --> 00:20:29.650 Michael Schnuerle (OMF): timestamps, incident type, link to external reports, and all with the capability to do it in real time if available. And this

118 00:20:30.100 --> 00:20:38.380 Michael Schnuerle (OMF): Basically, all the safety type information is now standardized and centralized through MDS 2.1.

119 00:20:40.450 --> 00:20:52.709 Michael Schnuerle (OMF): And this is an example from Amsterdam. So they have a private e-bike company called Cowboy, and Cowboy was tracking near misses and accidents, crashes.

120 00:20:52.710 --> 00:21:09.479 Michael Schnuerle (OMF): with their bikes, with their customers, and they offered to share this with Amsterdam. You can see how Amsterdam took all that data and made sense of it, and actually use it to make road design changes. They are under a process right now, which the OMF is involved with, to

121 00:21:09.480 --> 00:21:15.769 Michael Schnuerle (OMF): convert this bespoke data format from coming from Cowboy into MDS 2.1.

122 00:21:15.800 --> 00:21:24.729 Michael Schnuerle (OMF): So that it would be in that standard for Cowboy and any other future operators that can send this information to Amsterdam.

123 00:21:25.160 --> 00:21:29.860 Michael Schnuerle (OMF): So this is a great example and we appreciate their work.

124 00:21:30.390 --> 00:21:31.470 Michael Schnuerle (OMF): on this.

125 00:21:33.390 --> 00:21:50.600 Michael Schnuerle (OMF): Another new feature is the delivery mode, so it used to be delivery robots only, because we sort of started there with 2.0, there was a little more contained and easier to define, and now with 2.1, we have all types of delivery, goods, foods, packages, freight.

126 00:21:51.040 --> 00:22:04.980 Michael Schnuerle (OMF): Delivery, I can refer to either employees or contractors. It can be autonomous, it can be remotely operated. App deliveries cover different types of packages, freight goods, food delivery.

127 00:22:05.290 --> 00:22:19.619 Michael Schnuerle (OMF): private hire vehicles, even postal service type vehicles, medicine delivery, other delivery services. So it's very robust. This came out of Boston initially, but other cities are going to be using it as well.

128 00:22:19.760 --> 00:22:36.799 Michael Schnuerle (OMF): there could be one or multiple orders on different trips at the same time, connected by an identifier we have called the journey identifier, and then MDS tracks trip states of the orders separately from the vehicle state, so you can get a lot of information about

129 00:22:36.800 --> 00:22:42.719 Michael Schnuerle (OMF): Delivery, again, everything here is optional, it's based on the mode, it's based on

130 00:22:42.720 --> 00:22:48.139 Michael Schnuerle (OMF): agreements with the public agency, but there's a lot of optional fields available.

131 00:22:48.450 --> 00:22:57.339 Michael Schnuerle (OMF): Here's an example of a… relatively complex chip type that could happen and can be tracked with MDS delivery.

132 00:22:57.970 --> 00:23:06.790 Michael Schnuerle (OMF): So you can track things from the bright green is the actual trip that was taken for an individual.

133 00:23:07.380 --> 00:23:21.379 Michael Schnuerle (OMF): a start and end point of one location to another. Within that, you can see an example here of different orders. So maybe one trip had three orders, but they were delivered at different times. Maybe it's in a high-rise or something like that.

134 00:23:21.520 --> 00:23:30.909 Michael Schnuerle (OMF): Those trips can be… Connected via journeys, so if you had multiple trips that you're taking from maybe one.

135 00:23:30.950 --> 00:23:34.700 Michael Schnuerle (OMF): Restaurant area of town to a commercial area.

136 00:23:34.700 --> 00:23:52.139 Michael Schnuerle (OMF): You can define those trips and maybe you're bouncing between places. That could be all one journey until you loop back to the starting point. Those can be strung together by routes if you'd like to. And then those routes can be rolled up to shifts if needed. So shift of a worker, a driver.

137 00:23:52.150 --> 00:23:54.540 Michael Schnuerle (OMF): To determine the total

138 00:23:54.610 --> 00:24:07.529 Michael Schnuerle (OMF): shift for that either autonomous or in-person driver or operator of the vehicle. So you just can get a sense of some of the complexity possible here and what you can track.

139 00:24:12.020 --> 00:24:25.310 Michael Schnuerle (OMF): Another new feature is transit fixed routes. This came from SFMTA for commuter shuttle operators, but MDS now can support different types of fixed route buses, shuttles, fleets.

140 00:24:25.390 --> 00:24:44.010 Michael Schnuerle (OMF): And it connects over to GTFS trips for stops and schedules also to determine, you know, GTFS trips defines what is the expected route and expected timing of all the different fixed route operations of a vehicle.

141 00:24:44.780 --> 00:24:53.879 Michael Schnuerle (OMF): This, in MDS, allows you to determine what was the actual timing, were there any missed stops, detours, how long was the vehicle at a stop?

142 00:24:54.200 --> 00:24:59.339 Michael Schnuerle (OMF): And that is useful for municipalities like SFMTA.

143 00:24:59.800 --> 00:25:13.430 Michael Schnuerle (OMF): This connects also to… so there's a way to connect it to GTFS routes and stop data feeds. It's under the passenger mode, and then information comes by MDS trips, events, and telemetry as needed.

144 00:25:18.100 --> 00:25:24.370 Michael Schnuerle (OMF): Another… Feature we have is this clarification of for-hire autonomous vehicles.

145 00:25:24.620 --> 00:25:38.650 Michael Schnuerle (OMF): We now explicitly mention that better in the spec. We can track these different types of incidents that I mentioned before, like mapping of trip types, testing trip types, unplanned stops, remote takeovers, crashes, near misses, etc.

146 00:25:39.120 --> 00:25:53.509 Michael Schnuerle (OMF): And then also with the connection to MDS real-time policy, which has been approved, it's also helpful for situational awareness and as an option in emergencies. And we'll talk about that in the next feature.

147 00:25:56.250 --> 00:26:10.950 Michael Schnuerle (OMF): So another thing we did, MDS policy was already real-time, but it was a little bit cumbersome, so we added some options to support real-time digital policy, which means a city, an agency, can publish information out and push it

148 00:26:10.950 --> 00:26:19.340 Michael Schnuerle (OMF): Two operators in real time, but as fast as a one second communication of anything that's happening specifically for.

149 00:26:19.340 --> 00:26:27.829 Michael Schnuerle (OMF): maybe emergency response or special events. So we've added a push endpoint instead of a pull endpoint. I'll talk about that in a sec.

150 00:26:28.280 --> 00:26:47.250 Michael Schnuerle (OMF): Filters, so you can filter down if you are going to use the pull endpoint to only get the information you need and only see if there has been an update. Agencies can also manage their public feeds with an API key if they'd like. And then we just clarify that policies need to be unique to prevent duplication.

151 00:26:47.340 --> 00:26:51.830 Michael Schnuerle (OMF): And then we've provided some examples of this as well in the spec.

152 00:26:52.630 --> 00:27:00.729 Michael Schnuerle (OMF): So before MDS 2.1, again, this is thanks to Pierre from Blue Systems for this slide.

153 00:27:00.810 --> 00:27:13.190 Michael Schnuerle (OMF): It used to be a GET method only, so it's like the city has a book that has all the rules in it, and you as an operator would have to look at that book whenever you wanted to see has this book changed or not.

154 00:27:13.190 --> 00:27:22.500 Michael Schnuerle (OMF): And, it was up to you to check it. You didn't know if it was changed, so you have to keep checking it. And that was, kind of a problem for near real time.

155 00:27:22.630 --> 00:27:33.180 Michael Schnuerle (OMF): Versus real time. But now with MBS 2.1, you can get it via that same way, you can check the book, or you can get pushed with the notification

156 00:27:33.480 --> 00:27:50.000 Michael Schnuerle (OMF): New additions to the book basically can be pushed directly to you as they happen, but the book is still there and able for you to look at. This allows for actual real-time MDS policy communication in an easier, more standard, industry-standard kind of way.

157 00:27:53.010 --> 00:28:06.590 Michael Schnuerle (OMF): And a great example and driver of this is Blue Systems' work in Seattle with SDOT. What SDOT has done is they have a, like many cities, a 911 dispatch system.

158 00:28:06.740 --> 00:28:08.680 Michael Schnuerle (OMF): And those, you know.

159 00:28:08.960 --> 00:28:21.489 Michael Schnuerle (OMF): what's happening is those 911 database calls, as they come in, are being converted automatically into MDS real-time digital policy in a machine-readable format.

160 00:28:21.670 --> 00:28:32.029 Michael Schnuerle (OMF): And then published out and pushed out to autonomous vehicle operators, but actually anyone who's using the right-of-way and wants to have this information.

161 00:28:32.190 --> 00:28:37.480 Michael Schnuerle (OMF): can get this information. And so things like an example here is

162 00:28:37.480 --> 00:28:53.309 Michael Schnuerle (OMF): There's a fire that happened with a certain severity level and a certain response, then that can create automatically a no-go zone for autonomous vehicles with a certain radius, maybe a quarter mile, and that could be refined over time as new information comes in.

163 00:28:53.800 --> 00:29:01.900 Michael Schnuerle (OMF): And then, another example is a medical response. Maybe it's less severe, maybe there's only one vehicle responding, so that could be, like, a slow zone.

164 00:29:01.900 --> 00:29:16.330 Michael Schnuerle (OMF): of a certain speed limit with a tighter radius around it, just to give people a heads up before the vehicles get there, and for routing purposes. So this system, importantly, it's built on MDS 2.1, but also

165 00:29:16.510 --> 00:29:20.490 Michael Schnuerle (OMF): It's replicable in other cities, and it's not limited to just AVs.

166 00:29:21.780 --> 00:29:25.110 Michael Schnuerle (OMF): It's a great example and driver of this new feature.

167 00:29:27.000 --> 00:29:31.279 Michael Schnuerle (OMF): We also added enforcement information, which we pulled from CDS, so if

168 00:29:31.640 --> 00:29:42.000 Michael Schnuerle (OMF): An operator is able to, or required to in some cases, notify an agency when they have done something accidentally.

169 00:29:42.000 --> 00:29:57.080 Michael Schnuerle (OMF): or even on purpose, illegally, they can send that information along with the location and time information, and then that can be updated as more information becomes available, like the type of violation or a citation ID,

170 00:29:57.130 --> 00:29:58.400 Michael Schnuerle (OMF): Things like that.

171 00:29:59.910 --> 00:30:03.510 Michael Schnuerle (OMF): And then, external references, which I mentioned, this is a way to link

172 00:30:03.630 --> 00:30:20.399 Michael Schnuerle (OMF): MDS data fields to any other external data fields or data sources. So you can see a list of them there. It can link MDS fields to CDS or GTFS or Waze or Tides or anything else, EV charging information.

173 00:30:20.660 --> 00:30:35.540 Michael Schnuerle (OMF): So it can link to actually any API, standard or non-standard, open or not open. It can also link to web pages, documents, reports that may provide context. It can be used in MDS with events, trips, and incidents.

174 00:30:35.610 --> 00:30:50.879 Michael Schnuerle (OMF): And we did this in CDS 1.1, and you can see some examples there of MDS events linking to connected work zone, road closures, or a trip in MDS ending at a CDS curb zone, or with event tracking.

175 00:30:50.990 --> 00:30:54.800 Michael Schnuerle (OMF): or an incident that happened in MDS connected to a police report.

176 00:30:57.760 --> 00:31:09.730 Michael Schnuerle (OMF): All right, so now that's the end of the high-level feature overview. I do see a few comments in the chat, but think about your other questions, and I'll jump over to the chat.

177 00:31:11.090 --> 00:31:16.979 Michael Schnuerle (OMF): I'll point out that Armand from SDOT has shared a link to the 911 Alerting Project.

178 00:31:17.280 --> 00:31:19.340 Michael Schnuerle (OMF): So thanks for that, Armand.

179 00:31:20.270 --> 00:31:21.080 Michael Schnuerle (OMF): Yeah.

180 00:31:21.450 --> 00:31:34.630 Michael Schnuerle (OMF): Rafael says, does the pushing functionality require operators to submit endpoints to agencies, or is this a feature? Yeah, so the way that it works is the city

181 00:31:35.000 --> 00:31:38.859 Michael Schnuerle (OMF): or the public agency would either do it themselves or have a vendor, and

182 00:31:38.910 --> 00:31:55.689 Michael Schnuerle (OMF): push out via HTTP a chunk of information, and it needs to know where to go, where does it need to send that information, so then the operator sends up the receiving point of that notification. And so it's a bit of a…

183 00:31:55.860 --> 00:32:05.739 Michael Schnuerle (OMF): both parties are coordinating, but once you set it up, then it just happens automatically. So, I mean, you can… analogy is, like.

184 00:32:05.910 --> 00:32:20.969 Michael Schnuerle (OMF): an email. So if a city were to… let's say a city were sending an automated email to a company now, they need to know what that email address is before they can send the email. So similarly here, they need to know where to send this information. But otherwise, it's analogous to that.

185 00:32:21.440 --> 00:32:22.310 Michael Schnuerle (OMF): Is that…

186 00:32:22.460 --> 00:32:24.699 Michael Schnuerle (OMF): If that is unclear, let me know.

187 00:32:27.380 --> 00:32:31.250 Michael Schnuerle (OMF): And then David asks,

188 00:32:31.590 --> 00:32:33.399 Michael Schnuerle (OMF): Does the spec have a way to keep?

189 00:32:33.760 --> 00:32:46.460 Michael Schnuerle (OMF): real-time count of the number of AVs within a zone and cap the vehicles until entering. For example, you don't want to jam up a situation, an area with lots of different vehicles.

190 00:32:47.640 --> 00:32:53.320 Michael Schnuerle (OMF): Yeah, so Arvan says, yes, I mean, basically the answer is yes, this is possible.

191 00:32:53.570 --> 00:33:06.840 Michael Schnuerle (OMF): Especially if it's one operator, you can certainly limit with MDMS policy the number of vehicles allowed in an area for each operator, as long as you have that authority.

192 00:33:07.040 --> 00:33:13.610 Michael Schnuerle (OMF): Regulatory authority like Armand mentions there for multiple operators.

193 00:33:13.950 --> 00:33:14.730 Michael Schnuerle (OMF): And.

194 00:33:15.010 --> 00:33:21.189 Michael Schnuerle (OMF): The city, obviously, if they get that information, they will know how many AVs are in there.

195 00:33:21.460 --> 00:33:26.020 Michael Schnuerle (OMF): MDS does have a feature to publish the count.

196 00:33:26.150 --> 00:33:27.090 Michael Schnuerle (OMF): of…

197 00:33:27.330 --> 00:33:48.550 Michael Schnuerle (OMF): certain types of vehicles in certain areas and set the rule for a maximum amount of those. So the city can gather all that from all of the operators and publish it out, that count. And then the operator can check that to say, look, are we over the count now? Maybe there's only 10 in this area. It says there's 10. That means I really know that I shouldn't go in there now.

198 00:33:48.550 --> 00:33:51.020 Michael Schnuerle (OMF): Even though I only have 3 vehicles in there.

199 00:33:51.090 --> 00:34:05.319 Michael Schnuerle (OMF): So that's possible. I will say that the way that that's done now is a little bit clunky, and there's a open issue, or will be an open issue, to think about how to do that in a more orchestrated way in a future MDS version. But it's…

200 00:34:05.590 --> 00:34:10.310 Michael Schnuerle (OMF): possible now, but I think could be optimized a little bit better.

201 00:34:14.260 --> 00:34:19.059 Michael Schnuerle (OMF): you know, you can imagine that scenario for sidewalk robots. I think that's where that's come up a lot

202 00:34:21.790 --> 00:34:27.589 Michael Schnuerle (OMF): All right. Any other questions about features in MDS 2.1?

203 00:34:29.020 --> 00:34:33.589 Michael Schnuerle (OMF): Is there anything you want more information on? Maybe a link to?

204 00:34:33.810 --> 00:34:36.199 Michael Schnuerle (OMF): or… And…

205 00:34:36.679 --> 00:34:43.269 Michael Schnuerle (OMF): something I didn't cover that you know is in 2.1 that you want more information on, or would like to talk about.

206 00:34:51.659 --> 00:34:56.379 Michael Schnuerle (OMF): I'll also… I'm about to say this, but I'll put it in the chat now.

207 00:34:56.520 --> 00:34:58.820 Michael Schnuerle (OMF): Mbs 2.1 is live.

208 00:34:59.360 --> 00:35:05.039 Michael Schnuerle (OMF): So, if you go to the main homepage for the spec now, I'll put it in the chat.

209 00:35:05.480 --> 00:35:14.990 Michael Schnuerle (OMF): what you're seeing there on the main homepage, the main branch, is the latest 2.1 release. So you can see that there, and that helps you

210 00:35:15.150 --> 00:35:16.970 Michael Schnuerle (OMF): Browse it, kind of, if you'd

211 00:35:23.280 --> 00:35:35.660 Michael Schnuerle (OMF): All right. I'm going to continue on with the sort of resources available and some other things. But think about questions you have or as I get into this, even other resources you'd like to see.

212 00:35:39.620 --> 00:35:43.780 Michael Schnuerle (OMF): So here's the list of resources, the types of things we do with each release.

213 00:35:43.950 --> 00:35:55.259 Michael Schnuerle (OMF): the four at the top with the check marks are done, the four at the bottom are in progress. So, our GitHub repository has been updated with the latest release, I just put that in the chat.

214 00:35:55.550 --> 00:36:05.620 Michael Schnuerle (OMF): are also our wiki, so information about on our MDS wiki, I'll put this in there as well, for which releases are supported.

215 00:36:05.890 --> 00:36:10.310 Michael Schnuerle (OMF): Which ones are deprecated?

216 00:36:11.150 --> 00:36:14.599 Michael Schnuerle (OMF): That's all listed now as well. Maybe I'll bring that up.

217 00:36:15.180 --> 00:36:16.669 Michael Schnuerle (OMF): To show you…

218 00:36:20.530 --> 00:36:37.659 Michael Schnuerle (OMF): So you can see the current release is 2.1, and there's information about it. Future releases we haven't, set up yet. You can see a list of past releases and the dates they were approved. Basically now every prior release is deprecated.

219 00:36:37.740 --> 00:36:44.640 Michael Schnuerle (OMF): Except for 2.1s, because when they become more than 2 years old, Then,

220 00:36:44.860 --> 00:36:54.510 Michael Schnuerle (OMF): They are no longer supported, which means they won't be getting patches. We don't recommend their use. We recommend upgrading to the latest release at that point, which is 2.1.

221 00:36:58.170 --> 00:37:03.830 Michael Schnuerle (OMF): Our website has been updated, too, so I'll go there now.

222 00:37:06.520 --> 00:37:11.360 Michael Schnuerle (OMF): So, the About MDS page… We have…

223 00:37:11.920 --> 00:37:19.449 Michael Schnuerle (OMF): information, slightly updated text here, and graphics about, what MDS is and how it works.

224 00:37:19.650 --> 00:37:32.839 Michael Schnuerle (OMF): And then when we get to the more technical parts, the code releases, it shows the current release, nothing yet upcoming, and you can link over to GitHub and the MDS repository.

225 00:37:37.190 --> 00:37:51.410 Michael Schnuerle (OMF): Use cases, we have a use case database. I won't bring that up now, but we've made modifications to that to make sure it's supported 2.1 with the new modes, new mode names, things like that, a few new use cases.

226 00:37:52.490 --> 00:38:08.090 Michael Schnuerle (OMF): Policy language, we've updated the policy language just to reflect 2.1, and guidance for cities, cities that wish to write MDS into their operating policy permits, tenders, or RFPs. We have sample language for that, and that has been updated as well.

227 00:38:08.800 --> 00:38:14.360 Michael Schnuerle (OMF): We are working on a blog post right now for MBS 2.1 that should be ready soon.

228 00:38:14.760 --> 00:38:21.720 Michael Schnuerle (OMF): We'll also have a slide deck, so if someone wanted to do… be a trimmed-down version of what I showed here today.

229 00:38:22.000 --> 00:38:28.889 Michael Schnuerle (OMF): For MDS 2.1 overview, we'll have that with links to different resources in those slides.

230 00:38:30.300 --> 00:38:41.309 Michael Schnuerle (OMF): Armand, I see your hand. Let me finish the last two here, because they're short. Media release, we'll work on this, and have a media release for media and social media.

231 00:38:41.480 --> 00:38:50.200 Michael Schnuerle (OMF): And OpenAPI, this is a schema, so if you're developing MBS 2.1, we have what's called an OpenAPI schema for 2.0.

232 00:38:50.520 --> 00:39:01.929 Michael Schnuerle (OMF): And we would like to develop this and update this to 2.1. What we're looking for here, if you do use the OpenAPI, we'd love to have some volunteers to help with that.

233 00:39:02.070 --> 00:39:10.139 Michael Schnuerle (OMF): In CVS, CVS was just updated, we had a company called Passport lead that effort with a few other companies and cities to update it.

234 00:39:10.320 --> 00:39:27.509 Michael Schnuerle (OMF): for CDS 1.1. We'd love to see the same volunteer effort for MDS 2.1. That also helps us know that it's being used, and we're not spending resources on it without… in time, without knowing that people are actually using it and finding it valuable in their development work.

235 00:39:28.880 --> 00:39:29.939 Michael Schnuerle (OMF): Armand.

236 00:39:32.090 --> 00:39:45.030 Armand Shahbazian: Great presentation. Also would love the virtual background. That's a good one. My question is, for the policy language, is it generic, or is there policy language for each use case?

237 00:39:46.210 --> 00:39:48.770 Armand Shahbazian: requirement of… Easy.

238 00:39:49.590 --> 00:39:51.889 Armand Shahbazian: That, sort of, like, one size fits all.

239 00:39:52.910 --> 00:39:58.419 Michael Schnuerle (OMF): Yeah, it's a good question. It's a little bit one size fits all. I'll show it to you.

240 00:39:59.060 --> 00:40:04.060 Michael Schnuerle (OMF): You know, I'll just go through it and show you, so…

241 00:40:04.320 --> 00:40:24.880 Michael Schnuerle (OMF): We have a little bit of purpose. Things that are like customizable, we've designated with a highlight. So for an RFP, we have some examples of things you could write into your RFP requirements and some sample selection criteria and deliverables.

242 00:40:25.100 --> 00:40:30.860 Michael Schnuerle (OMF): So these are definitely generic for all modes and all types of services, I think.

243 00:40:32.670 --> 00:40:48.059 Michael Schnuerle (OMF): you know, all of this, I think, to your point, is we could create custom versions of this for different services, and honestly, when you do go to implement it for micromobility, this might look a little bit different, especially based on that scale and type and

244 00:40:48.310 --> 00:40:52.459 Michael Schnuerle (OMF): Scope of your program, some of these things may or may not be applicable.

245 00:40:52.640 --> 00:40:58.440 Michael Schnuerle (OMF): You also have data sharing, policy guidance for how to write it into a data sharing agreement.

246 00:40:58.830 --> 00:41:05.909 Michael Schnuerle (OMF): Or a permit. Recommendations for how to share that information digitally.

247 00:41:06.190 --> 00:41:08.880 Michael Schnuerle (OMF): Wording for contract renewal…

248 00:41:09.030 --> 00:41:16.180 Michael Schnuerle (OMF): When you have an annual renewal, you may then specify MDS as part of that renewal. Some service level agreement language.

249 00:41:16.300 --> 00:41:21.139 Michael Schnuerle (OMF): And this is where it might be useful, is we do have a showcase of

250 00:41:21.570 --> 00:41:28.390 Michael Schnuerle (OMF): public agency documents that mention MDS, and there's a lot of them here, and it's for a lot of different services and modes.

251 00:41:28.910 --> 00:41:36.319 Michael Schnuerle (OMF): So… Probably most of these are gonna be micro mobility or bike share, but I think,

252 00:41:36.530 --> 00:41:42.890 Michael Schnuerle (OMF): As we get other ones, we can add them here and flag them as maybe for other types of modes.

253 00:41:43.230 --> 00:41:52.810 Michael Schnuerle (OMF): And then lastly, we do have release guidance, so if you want to upgrade it, and you want to talk to your vendors or operators about, hey, an upgrade is coming, there's a series of

254 00:41:52.860 --> 00:42:07.429 Michael Schnuerle (OMF): just a bit of sample language and timing. So you could say, look, a release is coming soon, please prepare, take a look. The release is now in the approval phase, which means, you know, within the next month or two, it's going to be live.

255 00:42:07.430 --> 00:42:17.129 Michael Schnuerle (OMF): And now the release is ready and we recommend putting it into full production within X number of days. And so we do have that guidance as well.

256 00:42:17.460 --> 00:42:22.600 Michael Schnuerle (OMF): So, Armand, to your question, do you want to ask maybe what you're hoping to see here?

257 00:42:24.760 --> 00:42:27.549 Armand Shahbazian: No, that was really helpful. I was thinking,

258 00:42:28.400 --> 00:42:34.890 Armand Shahbazian: we… so, for example, have our own language in our micromobility permit, but for thinking about AV regs, we were…

259 00:42:35.080 --> 00:42:37.809 Armand Shahbazian: Trying to determine,

260 00:42:38.400 --> 00:42:47.829 Armand Shahbazian: like, what needs to be adjusted, and if that had already been done before, but I think if we take a first take at that, we're also happy to provide that.

261 00:42:47.980 --> 00:42:55.709 Armand Shahbazian: to put in the reference library based on the guidance language to make sure that that's aligned in in that sense.

262 00:42:56.700 --> 00:43:02.560 Michael Schnuerle (OMF): Yeah, we'd love to see that and add you as an example. Let's see if Seattle's even on here.

263 00:43:04.110 --> 00:43:08.989 Michael Schnuerle (OMF): Yeah, Seattle, it's probably for micro mobility. I won't bring it up now.

264 00:43:10.440 --> 00:43:15.369 Michael Schnuerle (OMF): But we could flag it as Seattle Microbility, Seattle AVs, etc.

265 00:43:21.790 --> 00:43:25.490 Michael Schnuerle (OMF): All right, other questions about the spec or about these resources?

266 00:43:34.850 --> 00:43:35.919 Michael Schnuerle (OMF): And if you're…

267 00:43:36.300 --> 00:43:48.850 Michael Schnuerle (OMF): on the steering committee, or you are OMF staff, and you feel like I missed something, feel free to speak up and share, or clarify anything that I had talked about, or anything you were involved with directly.

268 00:44:00.510 --> 00:44:02.139 Michael Schnuerle (OMF): As of MTA, yes.

269 00:44:02.390 --> 00:44:10.960 Shayda Rager - SFMTA: I have a question about the delivery section or modes. How do the robots get uniquely identified?

270 00:44:12.910 --> 00:44:22.489 Michael Schnuerle (OMF): Good question. So the way that the spec works, whether it's robots or any other vehicle in all of MDS, and so this applies to everything, not just delivery.

271 00:44:22.830 --> 00:44:31.249 Michael Schnuerle (OMF): is that a… basically a random, unique identifier called a UUID is generated for every vehicle.

272 00:44:31.470 --> 00:44:36.710 Michael Schnuerle (OMF): And the operators generate those for their own vehicles, so they may have an internal

273 00:44:37.310 --> 00:44:52.510 Michael Schnuerle (OMF): you know, serial number or something they use, but for MDS, they associate that serial number or identifier VIN or something like that to a UUID, and so whenever they send you information about that vehicle, they're sending over that unique identifier

274 00:44:52.580 --> 00:45:01.099 Michael Schnuerle (OMF): the same way every time. And so you as a public agency are getting information about that particular delivery robot.

275 00:45:01.310 --> 00:45:11.379 Michael Schnuerle (OMF): via its ID, you know, in that history of, sort of, where it was, and what it was doing, and maybe how it's even properties… what its properties are, and how it changed over time.

276 00:45:11.650 --> 00:45:12.980 Michael Schnuerle (OMF): That answer the question.

277 00:45:12.980 --> 00:45:16.630 Shayda Rager - SFMTA: Yeah, it does. I'm just kind of trying to figure out, like.

278 00:45:16.740 --> 00:45:21.410 Shayda Rager - SFMTA: Problem solving in the distant future, if we can ever.

279 00:45:21.610 --> 00:45:23.809 Shayda Rager - SFMTA: Curb DoorDash stuff.

280 00:45:23.940 --> 00:45:26.170 Shayda Rager - SFMTA: And I was just trying to see how it would work if…

281 00:45:26.380 --> 00:45:29.260 Shayda Rager - SFMTA: It's already in practice with the robots.

282 00:45:29.630 --> 00:45:32.170 Shayda Rager - SFMTA: Or any other… I don't know, has Jordan…

283 00:45:32.170 --> 00:45:32.820 Michael Schnuerle (OMF): Oh.

284 00:45:32.820 --> 00:45:34.329 Shayda Rager - SFMTA: Participated in this.

285 00:45:34.330 --> 00:45:57.160 Michael Schnuerle (OMF): Yes. In fact, I'll show you this. If an operator is using MDS in any way, actually go back to MDS, they register for basically what we call a provider ID. So they're a provider of the service and they register for this in the MDS repository. There's a list of them here in sort of a spreadsheet form.

286 00:45:57.710 --> 00:45:59.889 Michael Schnuerle (OMF): I'll put this in the chat.

287 00:46:00.610 --> 00:46:01.070 Shayda Rager - SFMTA: Thanks.

288 00:46:01.280 --> 00:46:13.870 Michael Schnuerle (OMF): Yeah, and so, they sort of get added over time and by mode, and you can see DoorDash is here for delivery robots, and they have… this is their UUID for their company.

289 00:46:14.090 --> 00:46:21.690 Michael Schnuerle (OMF): And that comes through in MDS, but then each vehicle gets its own identifier as well, so they are definitely

290 00:46:21.860 --> 00:46:31.610 Michael Schnuerle (OMF): using MDS to have it registered here to get an identifier for the company, and I know there are other cities that are

291 00:46:32.050 --> 00:46:33.190 Michael Schnuerle (OMF): either…

292 00:46:33.380 --> 00:46:41.989 Michael Schnuerle (OMF): They're definitely asking for, they definitely are receiving MDS data for delivery robots and, or working with DoorDash.

293 00:46:42.380 --> 00:46:49.119 Michael Schnuerle (OMF): for delivery robots and/or food and other types of delivery as well.

294 00:46:49.720 --> 00:47:06.450 Andrew Glass Hastings (OMF): So Shada, are you familiar with what Boston is doing in terms of food delivery? Actually, it's beyond food. It's gig delivery management. So their council passed an ordinance that requires.

295 00:47:06.450 --> 00:47:19.919 Andrew Glass Hastings (OMF): any entity that has over a certain number of deliveries within the city of Boston in a year to be permitted. And as a part of that permit, they require data sharing via MDS.

296 00:47:19.920 --> 00:47:42.829 Andrew Glass Hastings (OMF): And DoorDash specifically is one of the companies that fell under this permitting requirement. And Boston has worked with them so that DoorDash is now permitted and is part of that data sharing scheme through MDS. So if you want to become more familiar with what Boston has been able to do, which was pretty leading edge in this.

297 00:47:42.830 --> 00:47:43.250 Shayda Rager - SFMTA: Yeah, that'.

298 00:47:43.250 --> 00:47:50.940 Andrew Glass Hastings (OMF): area of regulating gig delivery. Happy to put you in touch with the folks there. They're doing some really excellent work.

299 00:47:50.940 --> 00:47:56.000 Shayda Rager - SFMTA: Sure, yeah, let me see if Hank isn't already in touch with him on that.

300 00:47:56.140 --> 00:48:01.849 Shayda Rager - SFMTA: But it's something that's been an ongoing issue around, like, there's just a lot of.

301 00:48:02.160 --> 00:48:13.960 Shayda Rager - SFMTA: For San Francisco, there are just a lot of DoorDash providers that are using Vespas, or, like, mopeds, and are using the bike lane, and… or riding on the sidewalk, and…

302 00:48:14.080 --> 00:48:19.050 Shayda Rager - SFMTA: There's just a desire from the public to figure out how to curb that.

303 00:48:19.320 --> 00:48:26.730 Shayda Rager - SFMTA: But I feel like MDS could be one way, and it sounds like Boston was able to do something with that.

304 00:48:26.960 --> 00:48:33.190 Shayda Rager - SFMTA: And I mean, I feel like geofencing could be another way to kind of… Support.

305 00:48:33.700 --> 00:48:36.300 Shayda Rager - SFMTA: Safer locations for deliveries.

306 00:48:38.030 --> 00:48:39.260 Andrew Glass Hastings (OMF): Yeah, absolutely.

307 00:48:43.240 --> 00:48:51.530 Michael Schnuerle (OMF): Yeah, the question about… I put… I put a Boston Living presentation in there. There's also,

308 00:48:52.320 --> 00:49:03.870 Michael Schnuerle (OMF): a recording of that, so if you want to reach out to me, I can send you… I think there's actually two recordings and two slide presentations about it. You can learn about what Boston's doing, and we can put you in touch, of course.

309 00:49:04.050 --> 00:49:10.410 Michael Schnuerle (OMF): And then, sir, Viggy, you're asking about… Serve, I think you…

310 00:49:10.650 --> 00:49:14.839 Michael Schnuerle (OMF): I don't… I'm not sure, have you made a request?

311 00:49:14.950 --> 00:49:21.500 Michael Schnuerle (OMF): Let me, link to… I'll send the link to the way that you make a request.

312 00:49:21.940 --> 00:49:36.610 Michael Schnuerle (OMF): to do this. So, on the home page here, this is maybe for everyone's benefit, but if you're a provider using MDS, there's instructions here about how to get an identifier, so I'll put that here.

313 00:49:41.370 --> 00:49:46.139 Michael Schnuerle (OMF): And I don't recall off the top of my head if CERF has done that yet or not.

314 00:49:46.260 --> 00:49:51.239 Michael Schnuerle (OMF): But there's a process there. There's… you can either email me, open an issue, or open a pull request.

315 00:49:51.880 --> 00:49:54.000 Michael Schnuerle (OMF): Hope that helps feel free to send me an email.

316 00:49:58.980 --> 00:49:59.850 Michael Schnuerle (OMF): Okay.

317 00:50:00.760 --> 00:50:03.910 Michael Schnuerle (OMF): All right, let's get back to…

318 00:50:04.490 --> 00:50:20.100 Michael Schnuerle (OMF): the end here. If anyone has last-minute questions, feel free to ask them. Of course, you can get involved by participating in these meetings, sign up for the mailing list, and start using the official version 2.1 release.

319 00:50:20.150 --> 00:50:26.790 Michael Schnuerle (OMF): Get in touch with us if you have questions. The next meeting was scheduled for July 30th.

320 00:50:27.030 --> 00:50:36.699 Michael Schnuerle (OMF): We are going to cancel that one and instead jump to the August 27th meeting, so we'll send an email about that, but just a little bit of a heads up now.

321 00:50:37.950 --> 00:50:43.770 Michael Schnuerle (OMF): And otherwise… That brings us to the end of that MDS launch meeting.

322 00:50:44.310 --> 00:50:51.870 Michael Schnuerle (OMF): Thank you all for participating, and for bringing your questions, and for all the work you've done on this over the last

323 00:50:52.310 --> 00:50:55.570 Michael Schnuerle (OMF): few… two years? I'd say two to three years of work.

324 00:50:57.760 --> 00:51:22.539 Andrew Glass Hastings (OMF): Before we go, I want to first just say, Michael, thank you for leading the effort here on 2.1 and helping to facilitate the steering committee as well as the working group all in all. It's been a lot of work over the past couple of years, and this version of MDS is by far the most comprehensive to date in terms of modes and features.

325 00:51:22.540 --> 00:51:38.959 Andrew Glass Hastings (OMF): And kudos to you, the steering committee, the entire OMF community for getting to this point. Now there's a lot of opportunity, as we just talked about in terms of delivery, talked about earlier around autonomous vehicles, now to apply these new features and this spec.

326 00:51:38.960 --> 00:51:57.569 Andrew Glass Hastings (OMF): in ways beyond, you know, the core use case for MDS, which has been micromobility. Lots of new opportunity, excited to work with this community to do that. And along those lines, want to be able to dig a little bit deeper into this. Aileen, did you want to say anything about the Academy sessions this fall?

327 00:51:58.060 --> 00:52:09.940 Aylene McCallum (OMF): Yeah, we had about, we had over a hundred professionals attend our OMF Academy programming earlier this year. So we're doing another round of that and introducing a few extra new topics.

328 00:52:09.940 --> 00:52:25.710 Aylene McCallum (OMF): But these OMF Academy sessions are great for you if you need to dig in a little bit to build your base and understanding of digital infrastructure. They are great for your colleagues if you maybe have an executive or an elected official or their staff.

329 00:52:25.710 --> 00:52:32.419 Aylene McCallum (OMF): who, you could send to these sessions to help them understand how MDS works or the applications.

330 00:52:32.420 --> 00:52:47.700 Aylene McCallum (OMF): And so we just really encourage you to look for those registration details. You can see the dates are saved on our OMF calendar in the next few months, and then the information on how to register for those programs will be updated shortly.

331 00:52:47.700 --> 00:52:59.229 Aylene McCallum (OMF): And quick note, sorry, OMF Academy programming is limited to OMF members. So if you are a public sector organization and not a member of the OMF yet, please reach out to me.

332 00:52:59.230 --> 00:53:00.860 Aylene McCallum (OMF): Super easy to sign up.

333 00:53:00.860 --> 00:53:19.660 Aylene McCallum (OMF): And, our members help support the development of this OMF Academy programing, which is why we limit it to, our community. But any, commercial organizations, if you want to join and support this work and have access to this programing, we'd also love to have you. Thank you.

334 00:53:22.390 --> 00:53:24.259 Michael Schnuerle (OMF): Thank you all for those updates.

335 00:53:24.560 --> 00:53:28.619 Michael Schnuerle (OMF): And, thanks everyone for participating today. We'll send out the recording

336 00:53:28.850 --> 00:53:31.939 Michael Schnuerle (OMF): Soon, and feel free to browse the spec in the meantime.

337 00:53:32.240 --> 00:53:33.410 Michael Schnuerle (OMF): See you all next time. Bye.

338 00:53:33.940 --> 00:53:34.810 Shayda Rager - SFMTA: Thank you.

339 00:53:35.440 --> 00:53:36.010 Michael Schnuerle (OMF): Bye.

340 00:53:36.560 --> 00:53:37.300 Vladimir Gallegos (LADOT): Thank you.

omf-mds-github-footer

MDS Wiki Home

MDS Links

Working Groups

2.1.0 Release

2.0.0 Release Plan

1.2.0 Release Plan

1.1.0 Release Plan

1.0.0 Release Plan

0.4.1 Release Planning Meetings

0.4.0 Release Planning Meetings

0.3.2 and earlier Release Planning Meetings

Clone this wiki locally