Skip to content

Web Conference 2026.02.24 Curb

Jump to bottom
Michael Schnuerle edited this page Mar 6, 2026 · 8 revisions

CDS Working Group

Agenda

Implementation Pain Points with the WGSC

The steering committee members and participants will talk about pain points in the implementation journey from curb data creation to CDS API endpoint pipeline.

  • Welcome (5 mins)
  • Announcements (5 mins)
  • Implementation: Pain Points Panel (45 mins)

Organizers

  • Hosts: Michael Schnuerle, OMF
  • Note Taker: Michael Schnuerle, OMF
  • Facilitator: Michael Schnuerle, OMF
  • Outreach: Michael Schnuerle, OMF

Action Items and Decisions

  • Review recording and notes and open a CDS Issue with things you'd like to see updated or improved.

Minutes

Notes

Key Comments

Omaha

  • What data and infrastructure do cities 'own' internally?
  • Who to partner with for CDS Events and Metrics once Curbs are done?
  • Change management - commitment to to payment providers, and occupancy info to the public

San Jose

  • Worried about vendor dependency.
  • Wish vendors could output as CDS to expedite integrations.
  • Systems integrations and ETL are hard and costly.

Montreal

  • Gathering and maintining data is an issue.
  • They have custom attributes in a lot of places (can leverage new CDS feature for this)
  • Would like to see off street parking, both garage and surface, better supported in CDS *

AppyWay

  • Working on hard task of physical documentation of city policies into digital maps and CDS

Curb IQ

  • Would like to see more info on highlighting the benefits of using CDS.
  • Make it clear why everyone in the ecosystem should use CDS
  • Getting started with CDS is hard. You have to inventory and code the curb. Effort for city with vendors.
    • City needs digital infrastructure setup for this to serve CDS.
    • Very different than MDS, where you don't need anything to get started.
    • If there was a ROW spec, it would be more like CDS with very large up front city costs.
  • CDS started with loading zones, ad now has moved to all curb elements and uses more clearly.
  • Could really focus on how to do one important thing: paid parking

Policy/Zone changes

  • Right now CDS works like MDS Policy, where a change to a policy or zone requires a new zone
    • How do you handle temp events/closures (you attach a high priority policy, then remove it later, or set time frame)
    • Maybe a change could be an audit trail system that tracks changes to policies, so you don't need a new ID each time?

See the full meeting transcript below, and recording, for more nuanced and detailed discussion of these topics.

Chat

Click to view meeting chat

  • 00:04:43 Andrew Glass Hastings (OMF): As a reminder hover your mouse over your picture/name and click the three dots, then rename.

  • 00:05:44 Michael Schnuerle (OMF): Agenda for today https://github.com/openmobilityfoundation/curb-data-specification/wiki/Web-Conference-2026.02.24-Curb

  • 00:06:27 MARIETTA GELFORT: Marietta Gelfort, Arlington County Transportation, Engineering and Operations; First meeting for me

  • 00:06:47 Lisa Hood- San Jose DOT: Reacted to "Marietta Gelfort, Ar..." with 👋

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

  • 00:13:46 Leo Burnett (OMF): Reacted to "Marietta Gelfort, Ar..." with 👋

  • 00:14:15 Leo Burnett (OMF): Replying to "Marietta Gelfort, Ar..."

  • Welcome Marietta! Glad to have you here.

  • 00:14:18 Andrew Glass Hastings (OMF): Don’t hesitate to put any questions or comments in the chat

  • 00:16:36 Max Holperin (Walker Consultants): I often see issues with converting legacy data (missing or incorrect fields)

  • 00:16:43 Andrew Kay: Reacted to "I often see issues w..." with 👍

  • 00:16:54 Sarah Gallagher | Seattle DOT: Reacted to "I often see issues w..." with 💯

  • 00:18:41 Andrew Glass Hastings (OMF): OMF Academy - our professional development and capacity building training program for OMF members. Initial course happening next week March 4 with a repeat on March 19. More details below…

  • Limited to OMF members only.  Please email membership@openmobilityfoundation.org for information about membership or to receive links to register for this event.

  • Digital Infrastructure 101: The Invisible Infrastructure Behind Urban Mobility is an OMF Academy introductory session designed for any public- and private-sector mobility professional, as well as elected officials and their teams, who want to better understand how digital systems, policy goals, and governance intersect.

  • In this introductory session we'll review the history of Digital Infrastructure and why it is critical for modern mobility management.

  • 00:19:22 Duncan Balmbra: understanding historical text based traffic/ curb legislation and transforming them automatically into digital map based assets.

  • 00:20:40 Andrew Glass Hastings (OMF): This is such a good CDS use case!

  • 00:22:32 Max Holperin (Walker Consultants): Reacted to "This is such a good ..." with 👍

  • 00:24:11 Graham Rossmore (LADOT): I agree with that, also very siloed here at LADOT/City of LA, seems to be a larger municipal structure issue and how best to implement citywide

  • 00:24:55 Andrew Glass Hastings (OMF): Reacted to "I agree with that, a..." with 💯

  • 00:27:00 Kenya Wheeler, SFMTA (He/Him): Reacted to "Marietta Gelfort, Ar..." with 👋

  • 00:27:05 Kenya Wheeler, SFMTA (He/Him): Reacted to "I often see issues w..." with 💯

  • 00:27:33 Kenya Wheeler, SFMTA (He/Him): Reacted to "I agree with that, a..." with 💯

  • 00:28:53 Jerad Weiner (San Francisco Public Works): Reacted to "I agree with that, a..." with 💯

  • 00:32:01 Kenya Wheeler, SFMTA (He/Him): Similar issues with change management as well in San Francisco, We've had some success in building champions inside our agency and outside of our silo [thanks for joining @Jerad Weiner (San Francisco Public Works)], but implementing process changes to expand usage of CDS more broadly is a challenge.

  • 00:34:12 Graham Rossmore (LADOT): Reacted to "Similar issues with ..." with 👍

  • 00:35:23 Michael Schnuerle (OMF): Custom Attributes just added in CDS 1.1 in Curbs, Areas, Spaces, Objects, or Events https://github.com/openmobilityfoundation/curb-data-specification/blob/main/data-types.md#custom-attributes

  • 00:37:18 Shayda Rager: For custom attributes can’t you create a different table that can then be joined to the CDS table via unique id?

  • 00:37:32 Elias Khoury - San Jose DOT: there would be value in having off-street facilities to an extent in CDS especially when you are doing occupancy analysis for on-street and the potential for finding correlations between on-street and off-street. it also helps analyze pricing options

  • 00:37:55 Hannah Adeponu: Reacted to "there would be value..." with 👍

  • 00:37:57 Graham Rossmore (LADOT): Reacted to "there would be value..." with 👍

  • 00:38:50 Michael Schnuerle (OMF): Replying to "For custom attribute..."

  • Yes you can do that, in what we call External References, if custom attributes don’t work. https://github.com/openmobilityfoundation/curb-data-specification/blob/main/data-types.md#external-reference

  • 00:38:58 Michael Schnuerle (OMF): Reacted to "there would be value..." with 👍

  • 00:40:56 Shayda Rager: Reacted to "Yes you can do that,…" with 👍

  • 00:41:02 Andrew Glass Hastings (OMF): Liquid sunshine as we say in Seattle 🌧️

  • 00:41:17 Graham Rossmore (LADOT): Reacted to "Liquid sunshine as w..." with 😂

  • 00:41:23 Shayda Rager: Reacted to "Liquid sunshine as w…" with 😂

  • 00:41:27 Lisa Hood- San Jose DOT: Reacted to "Liquid sunshine as w..." with 😂

  • 00:41:27 Alex Demisch (SFMTA): Reacted to "Liquid sunshine as w..." with 😂

  • 00:41:29 Shayda Rager: Reacted to "Similar issues with …" with 👍

  • 00:43:35 Kenya Wheeler, SFMTA (He/Him): Reacted to "Liquid sunshine as w..." with 😂

  • 00:44:52 Andrew Glass Hastings (OMF): Very true @Jacob Malleau (CurbIQ)

  • 00:47:39 Andrew Glass Hastings (OMF): We are finding there is massive value for CDS internally to cities for asset management integration as well as parking and curb data integration leading to addressing the removal of silos. But cities need to be willing to do this work to get the real value of CDS. We are working hard through the Curb Collaborative and OMF Academy to make this value and implementation process clearer and easier

  • 00:48:13 Kenya Wheeler, SFMTA (He/Him): Reacted to "We are finding there..." with 👍🏾

  • 00:48:58 Graham Rossmore (LADOT): go paid parking!

  • 00:49:41 Michael Schwartz, INRIX: For MDS, there was also an urgent pain point for shared micromobility. Scooters were literally falling from the sky and cities couldn’t get their arms around their programs without data sharing.

  • Curb management has existed for a long time using various analog and digital methods. There hasn’t been a triggering event with the same level of urgency.

  • 00:49:49 Michael Schnuerle (OMF): Reacted to "For MDS, there was a..." with 👍

  • 00:49:55 Leo Burnett (OMF): Reacted to "For MDS, there was a..." with 💯

  • 00:49:55 Graham Rossmore (LADOT): Reacted to "For MDS, there was a..." with 👍

  • 00:50:11 Kenya Wheeler, SFMTA (He/Him): Reacted to "For MDS, there was a..." with 💯

  • 00:50:16 Andrew Kay: Reacted to "For MDS, there was a..." with 💯

  • 00:52:21 Michael Schnuerle (OMF): Reacted to "go paid parking!" with 👀

  • 00:52:35 Michael Schnuerle (OMF): Reacted to "For MDS, there was a..." with 💯

  • 00:52:42 Emily Lindsey, DRCOG: Reacted to "For MDS, there was a..." with 💯

  • 00:53:52 Jacob Malleau (CurbIQ): Reacted to "For MDS, there was a..." with 💯

  • 00:57:34 Jacob Malleau (CurbIQ): You can use priorities to have a policy temporarily override the paid parking policy

  • 00:58:00 Elias Khoury - San Jose DOT: Reacted to "You can use prioriti..." with 👍

  • 00:58:41 Graham Rossmore (LADOT): need to hop off, thanks everyone!

  • 00:58:52 Corey Bell: gotta run. thanks, everyone.

  • 01:00:21 MARIETTA GELFORT, Arlington County: thanks everyone

  • 01:00:56 Duncan Balmbra: many thanks all.

  • 01:01:20 Kenya Wheeler, SFMTA (He/Him): Thanks everyone!

Transcript

Click to view full meeting transcript

1 00:00:30.020 --> 00:00:33.090 Michael Schnuerle (OMF): Alright, we're gonna kick off the meeting. Hello, everybody.

2 00:00:33.240 --> 00:00:38.669 Michael Schnuerle (OMF): Thanks for joining today's OMF Curb Working Group public meeting.

3 00:00:39.700 --> 00:00:44.399 Michael Schnuerle (OMF): Today, we're going to talk about implementation pain points, and this is around

4 00:00:44.940 --> 00:00:51.470 Michael Schnuerle (OMF): digital curb management in general, but also CVS, our data specification in particular.

5 00:00:52.830 --> 00:00:54.369 Michael Schnuerle (OMF): Little bit of housekeeping.

6 00:00:54.850 --> 00:01:11.030 Michael Schnuerle (OMF): Set your name and organization in the participant list. My name is Michael Schnurle, I work for the Open Mobility Foundation, and I am the steward of the data specifications and the groups that manage them that are members and non-members.

7 00:01:11.590 --> 00:01:20.029 Michael Schnuerle (OMF): Mute yourself for now. If you'd like to, go ahead and introduce yourself in the chat, whether you've attended these meetings before or not.

8 00:01:21.000 --> 00:01:35.650 Michael Schnuerle (OMF): If you want to speak up during this meeting, you could use the chat, use the raise hand feature. There's a… going to be a part of the meeting today where we have an open discussion, so you can also just turn on your camera and or your mic and speak up that way.

9 00:01:35.950 --> 00:01:42.450 Michael Schnuerle (OMF): This meeting is being recorded, and we… the recording will be published with notes to our mailing list.

10 00:01:46.350 --> 00:01:53.289 Michael Schnuerle (OMF): Do a little bit of a welcome and announcements, and then we'll get into the implementation part, discussion of today's meeting.

11 00:01:53.450 --> 00:01:59.899 Michael Schnuerle (OMF): Here is the agenda for today in the chat, if you'd like to take a look at that. And that's where the notes will go.

12 00:02:01.930 --> 00:02:13.400 Michael Schnuerle (OMF): A little bit about the curve data specification, which is the focus of the meetings in general. So, this is a data specification that we have, that we steward at the OMF.

13 00:02:13.510 --> 00:02:21.539 Michael Schnuerle (OMF): That provides a structured way to catalog and track how cities… city streets, curbs, and street assets are used. And…

14 00:02:21.780 --> 00:02:27.249 Michael Schnuerle (OMF): CDS 1.1 is released, and it is starting to be adopted right now.

15 00:02:30.460 --> 00:02:46.880 Michael Schnuerle (OMF): Basically, CDS allows you to code the curb, create a digital model of the curb with the curbs API, track events and activity, loading and unloading of goods and passengers at those curb locations, and then

16 00:02:47.040 --> 00:02:51.430 Michael Schnuerle (OMF): Roll that into metrics to improve your digital policies.

17 00:02:53.140 --> 00:03:12.759 Michael Schnuerle (OMF): It's been built in the open through public and private sector collaboration. At least 300 individuals and 130 public agencies, curb user companies, and tech companies have been involved, and this has created a competitive marketing ecosystem for curb management and

18 00:03:13.230 --> 00:03:15.940 Michael Schnuerle (OMF): Digitizing the curb and managing the curb.

19 00:03:17.290 --> 00:03:20.670 Michael Schnuerle (OMF): There's a lot of different people using CDS here, some of them

20 00:03:20.930 --> 00:03:32.070 Michael Schnuerle (OMF): On this slide, and if you have… if you're using CDS somewhere, you can email me or put a link in the chat, and we'll make sure to add you to our list of people using CDS.

21 00:03:33.740 --> 00:03:37.470 Michael Schnuerle (OMF): For CDS 1.1, there's a ton of resources available.

22 00:03:37.580 --> 00:03:43.460 Michael Schnuerle (OMF): These are some of them, everything from websites to slide decks, one-pagers.

23 00:03:44.410 --> 00:03:48.399 Michael Schnuerle (OMF): Different policy language, contract language guidance.

24 00:03:48.580 --> 00:03:54.829 Michael Schnuerle (OMF): And recordings of meetings and kickoffs and things like that. So, lots of resources there.

25 00:03:55.100 --> 00:03:59.650 Michael Schnuerle (OMF): And you'll find this in the slides when we put them on the agenda page.

26 00:04:01.260 --> 00:04:02.940 Michael Schnuerle (OMF): Alright, quick announcements.

27 00:04:03.480 --> 00:04:12.409 Michael Schnuerle (OMF): We want to thank our commercial members for being part of the Open Mobility Foundation. We have a premier level and an associate level. These are our current members.

28 00:04:12.730 --> 00:04:25.299 Michael Schnuerle (OMF): Thank you all for participating, and many of these members are also on our steering committee for this working group, or the MDS working group, so we appreciate your time and volunteering to be on the steering committees.

29 00:04:27.400 --> 00:04:38.030 Michael Schnuerle (OMF): We also have an OMF calendar where we catalog our public events and even OMF member events, and so if you want to,

30 00:04:38.550 --> 00:04:43.130 Michael Schnuerle (OMF): Follow along. You can subscribe to this calendar, or look at it visually in your

31 00:04:43.580 --> 00:04:46.350 Michael Schnuerle (OMF): In your web browser, here's a link.

32 00:04:47.110 --> 00:04:50.470 Michael Schnuerle (OMF): That's about… hold on, let me click this.

33 00:04:52.070 --> 00:04:53.999 Michael Schnuerle (OMF): There's a link to the calendar.

34 00:04:59.000 --> 00:04:59.960 Michael Schnuerle (OMF): There we go.

35 00:05:02.070 --> 00:05:07.979 Michael Schnuerle (OMF): And, this is where we keep everything up to date, so follow along and you'll know what's happening with the OMF.

36 00:05:11.220 --> 00:05:15.720 Michael Schnuerle (OMF): Alright, let's get into the topic of today, implementation pain points.

37 00:05:17.500 --> 00:05:34.110 Michael Schnuerle (OMF): So, at our last meeting last month, we focused on sharing companies and cities share their CDS data workflows, and how they handle change management along the curb, so when a sign or policy changes, how does that flow through

38 00:05:34.360 --> 00:05:41.180 Michael Schnuerle (OMF): Some sort of combination of internal systems, departments, vendors…

39 00:05:41.240 --> 00:05:44.850 Michael Schnuerle (OMF): And then eventually, either go to CDS,

40 00:05:44.900 --> 00:06:03.679 Michael Schnuerle (OMF): as an API, to web maps, to, out to the curb itself, the physical curb. And so, we had a lot of different sharing. This is just some of the, some of the sharing that happened at last month's meeting. There's a recording and slides as well, so you can look at that, but I think the…

41 00:06:04.100 --> 00:06:10.370 Michael Schnuerle (OMF): One takeaway is every city and every company is sort of implementing it

42 00:06:10.620 --> 00:06:19.300 Michael Schnuerle (OMF): In their own way a little bit, based on the restrictions they have, and those can be certain software platforms they're currently using.

43 00:06:19.450 --> 00:06:21.790 Michael Schnuerle (OMF): Or funding that they have.

44 00:06:22.420 --> 00:06:26.019 Michael Schnuerle (OMF): Or expertise, where they're comfortable.

45 00:06:26.140 --> 00:06:32.470 Michael Schnuerle (OMF): Doing something, or maybe what they're historically used to doing, and working within those constraints.

46 00:06:32.960 --> 00:06:49.649 Michael Schnuerle (OMF): And so the… the end result might be something consistent and shareable, like a CDS Curbs API, which is one of the values of having a data standard, is because it doesn't matter what your internal systems are like, you can get to this point where you share a CDS

47 00:06:50.550 --> 00:07:02.210 Michael Schnuerle (OMF): Definition of your digital curbs and track events and activity there in a standard way, but the internal systems behind all of that are varied and complex.

48 00:07:04.670 --> 00:07:12.629 Michael Schnuerle (OMF): So today, we'll be having a bit of a panel discussion, but also welcome anyone who is attending to be part of the conversation.

49 00:07:12.840 --> 00:07:15.050 Michael Schnuerle (OMF): And we want to think about

50 00:07:15.170 --> 00:07:23.150 Michael Schnuerle (OMF): What are the pain points that you have, that you have already discovered, or maybe that are even preventing you from starting?

51 00:07:23.440 --> 00:07:32.419 Michael Schnuerle (OMF): To implement a digital curb management solution or system that maybe involves the curb data specification?

52 00:07:33.180 --> 00:07:40.380 Michael Schnuerle (OMF): And so those pain points can come and fall at many different places along this digitization journey.

53 00:07:41.160 --> 00:07:47.609 Michael Schnuerle (OMF): So, just… To get you thinking about some of this, there's some questions here, so…

54 00:07:48.180 --> 00:07:54.849 Michael Schnuerle (OMF): Where are those pain points on that digitizing and data creation process for your curb?

55 00:07:55.290 --> 00:08:02.690 Michael Schnuerle (OMF): Are there internal change management processes that are a bit of a roadblock or a pain point?

56 00:08:02.960 --> 00:08:06.939 Michael Schnuerle (OMF): What about your technical pipelines to move data between

57 00:08:07.090 --> 00:08:10.020 Michael Schnuerle (OMF): Systems to extract it and transform it

58 00:08:10.260 --> 00:08:14.439 Michael Schnuerle (OMF): to get it from one system to another, or into CDS.

59 00:08:14.860 --> 00:08:29.419 Michael Schnuerle (OMF): What about the CDS actual data structure? So we have made decisions about how CDS is architected. Does everything you need fit into that structure, or is there something missing that's preventing you from adopting it?

60 00:08:30.100 --> 00:08:31.699 Michael Schnuerle (OMF): And then…

61 00:08:32.600 --> 00:08:48.009 Michael Schnuerle (OMF): for whatever you're doing in the curb, does that translate well into the CDS curbs? Does it track well with events, and are the metrics valuable to you? So that gets into, is the structure of CDS valuable, or are there any pain points there as well?

62 00:08:51.280 --> 00:08:56.780 Michael Schnuerle (OMF): And… Today, the focus, the people that will probably

63 00:08:56.940 --> 00:09:00.509 Michael Schnuerle (OMF): Participate a little more than everyone else, will be our…

64 00:09:00.550 --> 00:09:13.880 Michael Schnuerle (OMF): curb working groups, steering committee members. So we have… all of our working groups have OMF members from the public and private sector that have volunteered to help guide these meetings and guide the discussions and the development of the data.

65 00:09:13.880 --> 00:09:21.409 Michael Schnuerle (OMF): specifications. So, you can see here our current members and who they represent in both the public and private sector.

66 00:09:21.690 --> 00:09:25.169 Michael Schnuerle (OMF): And they set the agendas for these meetings.

67 00:09:25.350 --> 00:09:36.620 Michael Schnuerle (OMF): So many of them will be speaking up today and sharing, just like they did last month with their implementation details. And so our panel of steering committee members will lead this discussion today.

68 00:09:36.970 --> 00:09:39.379 Michael Schnuerle (OMF): But we welcome everyone to participate.

69 00:09:39.670 --> 00:09:42.860 Michael Schnuerle (OMF): On camera, audibly, or in the chat.

70 00:09:46.940 --> 00:09:51.080 Michael Schnuerle (OMF): Alright, so I have a series of questions, and…

71 00:09:51.220 --> 00:10:01.389 Michael Schnuerle (OMF): we'll just go through them and leave space for people to talk about it, especially our steering committee can kick off the discussions. But…

72 00:10:01.740 --> 00:10:05.310 Michael Schnuerle (OMF): We could… we can branch off from these questions if needed.

73 00:10:05.850 --> 00:10:11.230 Michael Schnuerle (OMF): But the goal is to have a discussion enough, and this is being recorded, to…

74 00:10:11.600 --> 00:10:18.330 Michael Schnuerle (OMF): understand what's happening, where people's pain points are, so that we at the OMF, and the steering committee as well.

75 00:10:18.820 --> 00:10:29.970 Michael Schnuerle (OMF): can take action to help you eliminate those pain points. So, if it is, some sort of issue with the curb data specification, we can work to improve that.

76 00:10:30.250 --> 00:10:34.649 Michael Schnuerle (OMF): If it's an issue with… Getting buy-in, or…

77 00:10:34.770 --> 00:10:48.779 Michael Schnuerle (OMF): implementing it, we may be able to help with our OMF Academy that we have, to help drive understanding and adoption of CVS across different departments and different levels of your organization.

78 00:10:48.980 --> 00:11:04.640 Michael Schnuerle (OMF): If it's about interoperability or moving between systems, we may be able to help engage with some of those companies that run those systems to help make that easier for you. So the goal is to share out your pain points so that we can take action.

79 00:11:08.950 --> 00:11:14.470 Michael Schnuerle (OMF): Alright, so this is a… A general, high-level general question for now.

80 00:11:14.610 --> 00:11:15.909 Michael Schnuerle (OMF): But in general.

81 00:11:16.030 --> 00:11:27.710 Michael Schnuerle (OMF): When you think about the CDS, what is standing in your way of implementing it? Whether it means implementing it at all, or implementing a piece of it, or implementing it fully.

82 00:11:28.310 --> 00:11:34.620 Michael Schnuerle (OMF): Share your thoughts on what your pain points are for CVS implementation.

83 00:11:39.390 --> 00:11:46.309 Michael Schnuerle (OMF): And I'll leave it open right now for anyone to respond, and I'm looking at the steering committee specifically to kick us off.

84 00:11:50.980 --> 00:11:52.160 Michael Schnuerle (OMF): Yeah, how not.

85 00:11:53.490 --> 00:11:57.240 Hannah Adeponu: Hey everybody, Hannah DeWanu from Omaha, Nebraska.

86 00:11:58.030 --> 00:12:03.830 Hannah Adeponu: I think, for us, we're committed to implementing CDS, and we've…

87 00:12:04.310 --> 00:12:20.430 Hannah Adeponu: We've been a big part of this… this steering committee and this working group, historically, and so I… just getting… getting into all of the information that's out there, in the… in the standard, I think, is one thing that…

88 00:12:20.430 --> 00:12:27.689 Hannah Adeponu: Our team, with turnover, is really digging into and ensuring that we really understand what's in there.

89 00:12:27.690 --> 00:12:39.189 Hannah Adeponu: But also, like, deciding from a municipality standpoint, what is it that we feel is appropriate for us to own?

90 00:12:39.220 --> 00:12:53.139 Hannah Adeponu: And I… I will opine on that, that I think that as far as, like, the Curbs API is concerned, we should own that, and we should see how, best to implement that within our municipal structure.

91 00:12:53.540 --> 00:13:06.840 Hannah Adeponu: But I think as far as, like, really having a system that completely embraces the APIs that you have within this standard.

92 00:13:07.160 --> 00:13:17.510 Hannah Adeponu: We then need to, after implementing what we feel is something that we should do internally, decide who to best partner with.

93 00:13:17.800 --> 00:13:25.330 Hannah Adeponu: And implementing those other, APIs, so that we have the metrics and the events.

94 00:13:26.070 --> 00:13:35.229 Hannah Adeponu: And that we're consistently using everything that the standard has to offer in order to really benefit from it.

95 00:13:36.050 --> 00:13:43.279 Hannah Adeponu: There's other ones, but maybe I'll leave it at that and let other people put their two cents in as well.

96 00:13:43.950 --> 00:14:00.599 Michael Schnuerle (OMF): Yeah, I'll respond to that, but welcome other people to jump off that, too. I think knowing what you're doing in Omaha, you've done a lot of the coding the curb digitization and internal management of that. Inside the city of Omaha, you have a good

97 00:14:00.900 --> 00:14:05.479 Michael Schnuerle (OMF): infrastructure and a pipeline for that, which is… I think…

98 00:14:05.480 --> 00:14:22.389 Michael Schnuerle (OMF): somewhat unusual. Most cities are not able to do that on their own, and so you've been able to, and now… but now you're thinking, how do we expand that, and what parts of the rest of CDS can you do internally, and what do you need to partner with, a vendor?

99 00:14:22.470 --> 00:14:25.460 Michael Schnuerle (OMF): So…

100 00:14:26.020 --> 00:14:41.630 Michael Schnuerle (OMF): maybe a quick question, maybe a dumb question for me, but, you know, we have this ecosystem of vendors who are helping cities do this. Are you thinking about what's next for you? Is it an RFP process, or do you have to do more research before you decide

101 00:14:42.340 --> 00:14:44.630 Michael Schnuerle (OMF): Who, your partner could be.

102 00:14:45.220 --> 00:14:54.250 Hannah Adeponu: Well, I think… I think low-hanging fruit for us, Michael, is that we want to make sure that all of the data that we have

103 00:14:54.450 --> 00:15:08.850 Hannah Adeponu: Because it's always changing, right? As far as policy rules and regulations are concerned, these things can change on a daily basis. And so we want to make sure for Omaha that we have something in place

104 00:15:09.160 --> 00:15:16.580 Hannah Adeponu: To communicate our rules and regulations to our payment providers, to our

105 00:15:16.790 --> 00:15:22.909 Hannah Adeponu: parks providers to our… well, maybe not parks providers, but our… our…

106 00:15:23.530 --> 00:15:35.799 Hannah Adeponu: folks in our… in our system that are providing, the ways for people to interact with our system. And… and we want it to be comprehensive in that

107 00:15:36.190 --> 00:15:42.730 Hannah Adeponu: We're able to then communicate out to the public what occupancy looks like.

108 00:15:42.760 --> 00:15:48.299 Hannah Adeponu: Right? But we can't do that if we don't have… so, like, we have a…

109 00:15:48.320 --> 00:16:05.099 Hannah Adeponu: huge meter hooding program here in Omaha, and a lot of construction that happens. So we have a system that we want to integrate into the database that we've created so that we say, okay, today these meters are not available.

110 00:16:05.810 --> 00:16:14.359 Hannah Adeponu: That will take them out of the inventory so that we can then communicate to the public, this is what our street looks like today.

111 00:16:14.620 --> 00:16:27.159 Hannah Adeponu: And obviously, like, that needs to be something that's efficient for us to be able to do. We don't want to have to go in manually every day and do that, so we're trying to figure out how do we

112 00:16:27.340 --> 00:16:47.449 Hannah Adeponu: build the system in a way that we're constantly updating our database, what our rules and regulations are, and then from there, that's when we would push it out to vendors that we already partner with today, and potentially new vendors in the future. But right now, we'll start with

113 00:16:47.550 --> 00:16:50.559 Hannah Adeponu: The folks we have in the system today, and then expand it out.

114 00:16:53.020 --> 00:17:02.179 Michael Schnuerle (OMF): Yeah, that's great. So, your sort of internal process and change management, workflows are something that you're trying to get a handle on, and I feel like

115 00:17:02.420 --> 00:17:06.950 Michael Schnuerle (OMF): That is something that came up a lot last… last month's meeting, and…

116 00:17:07.480 --> 00:17:16.569 Michael Schnuerle (OMF): it's one of the hardest things, and something that, if you're trying to implement CDS, it sort of forces you to have that set up

117 00:17:16.720 --> 00:17:19.300 Michael Schnuerle (OMF): Either along the way, or first.

118 00:17:19.480 --> 00:17:38.670 Michael Schnuerle (OMF): So you need that process to be set up, that pipeline, understanding and workflow and buy-in across every… all those different pieces you mentioned, like the payment providers, and internally and all that, before you… because that is… all of that is a dependency to…

119 00:17:38.940 --> 00:17:51.800 Michael Schnuerle (OMF): create a, you know, a valid CDS public API endpoint that people can use to determine rules, policies, and occupancy like you're hoping to do.

120 00:17:53.880 --> 00:17:55.500 Michael Schnuerle (OMF): Yeah, I would agree with that.

121 00:17:56.770 --> 00:18:03.460 Michael Schnuerle (OMF): Alright, would anyone else like to keep talking about that, or something else related to CDS implementation? That's a big one.

122 00:18:15.470 --> 00:18:16.650 Michael Schnuerle (OMF): Yeah, life's…

123 00:18:23.550 --> 00:18:34.529 Elias Khoury - San Jose DOT: Yeah, good morning, everyone. I just want to add a couple things, and that's, not very technical, but it, helped

124 00:18:35.070 --> 00:18:46.030 Elias Khoury - San Jose DOT: everyone understand the challenges. As a department, and as a unit, actually, I can't even speak, like, as a city, because we work solo.

125 00:18:46.300 --> 00:18:49.480 Elias Khoury - San Jose DOT: in this… on this project.

126 00:18:49.650 --> 00:19:01.710 Elias Khoury - San Jose DOT: And, and we rely on vendors to provide the CDS specs. What we have found, that there are some specs that, outside the scope.

127 00:19:02.490 --> 00:19:19.720 Elias Khoury - San Jose DOT: of current CDS standards, and that the vendor has to work, do a workaround, right, in order to digitize everything that we have asked them to digitize. So I think one thing that would be helpful is if we can

128 00:19:19.790 --> 00:19:27.639 Elias Khoury - San Jose DOT: Expedite as a, as a group here, like, expedite the changes that, or,

129 00:19:28.070 --> 00:19:33.530 Elias Khoury - San Jose DOT: new features with CDS so that it can catch up with our needs.

130 00:19:33.680 --> 00:19:36.610 Elias Khoury - San Jose DOT: The other thing is…

131 00:19:36.920 --> 00:19:52.340 Elias Khoury - San Jose DOT: we face is an internal problem. As I mentioned earlier, we work solo on this project, and it's difficult to integrate with other systems within the department and within the city.

132 00:19:52.720 --> 00:20:06.240 Elias Khoury - San Jose DOT: And that is a real challenge, because the… whatever is used as an infrastructure may be not compatible with CDS,

133 00:20:06.410 --> 00:20:13.320 Elias Khoury - San Jose DOT: And, For every, change that happens on the curb.

134 00:20:13.630 --> 00:20:20.899 Elias Khoury - San Jose DOT: We need to reflect it on our platform, and then we have somehow to reflect it on the other platforms.

135 00:20:21.250 --> 00:20:29.299 Elias Khoury - San Jose DOT: That the city or department is using. And I think these are the two, pain points for us.

136 00:20:32.270 --> 00:20:35.660 Michael Schnuerle (OMF): Yeah, so, to your first one,

137 00:20:37.720 --> 00:20:47.459 Michael Schnuerle (OMF): Can you talk a little… can you just maybe share an example of an outside standard that is creating a sort of conflict, and then…

138 00:20:47.670 --> 00:20:51.300 Michael Schnuerle (OMF): When you talk about expediting

139 00:20:51.440 --> 00:21:03.190 Michael Schnuerle (OMF): CDS updates, are you talking about, like, a vendor finds something, and then they need it to be added to CDS, and what's the timeline for that through the approval process with the spec?

140 00:21:04.080 --> 00:21:22.480 Elias Khoury - San Jose DOT: That is accurate on the second point. The first point, I think… I wish Rick is here, he can explain it better than me, on the challenges that they faced while they were… but there are certain things, like, not maybe contemplated in CDS,

141 00:21:22.510 --> 00:21:34.540 Elias Khoury - San Jose DOT: And, for many reasons, like, it's probably something unique to the city of San Jose, right? And there could be another thing unique to Boston or SFMTA.

142 00:21:34.800 --> 00:21:44.760 Elias Khoury - San Jose DOT: And so the vendor, and I think all vendors on… in the working group, do other efforts in order to

143 00:21:44.910 --> 00:21:57.869 Elias Khoury - San Jose DOT: deliver the… the… the service we ask for, but not necessarily all of it fits in… in CDS. And if someone else has this… this,

144 00:21:57.960 --> 00:22:05.309 Elias Khoury - San Jose DOT: Experience they can share, but that's my understanding from talking with,

145 00:22:05.620 --> 00:22:12.449 Elias Khoury - San Jose DOT: you know, emojo, that there are certain things they have to do outside CDS.

146 00:22:13.270 --> 00:22:33.040 Christy Hirsch, Umojo: Yeah, and thanks, Elias. Rick was, unfortunately, couldn't be here today. He's on a plane, but he, Michael, said he was going to get a lot of updates to you, in the next day or two. But yeah, change management is something that the dev team's squarely focused on, but Elias covered it really well. Thanks.

147 00:22:33.550 --> 00:22:34.220 Michael Schnuerle (OMF): Yeah.

148 00:22:34.870 --> 00:22:48.159 Michael Schnuerle (OMF): Thanks. Yeah, there's another part, and if you have other people on your team that want to chime in later, another question that's more specific about, like, what specifically in CDS is potentially holding you back in the spec, so we can talk more about that.

149 00:22:48.630 --> 00:22:57.450 Michael Schnuerle (OMF): But yeah, the system integrations internally is a challenge, and I see Graham from LADOT also mentions that in the chat.

150 00:22:57.780 --> 00:23:03.719 Michael Schnuerle (OMF): I think that's… Part of what we saw last meeting is that internal

151 00:23:03.960 --> 00:23:12.240 Michael Schnuerle (OMF): integration, what is… and that integration involves, a lot of times, something that I would probably call ETL.

152 00:23:12.380 --> 00:23:30.320 Michael Schnuerle (OMF): extract transform load processes, so how do you get data from one system to another? And many times, you need a custom piece of software or a system just to move data between systems. You need another system on top of everything. And some cities.

153 00:23:30.320 --> 00:23:44.229 Michael Schnuerle (OMF): do that, and have that ability with their infrastructure. I think, I could name a few, but, but some maybe don't, or it's a challenge, and that's where you need a vendor, or you need to develop that, so that… that can be tough.

154 00:23:44.850 --> 00:23:49.869 Michael Schnuerle (OMF): I'm gonna go to the chat for a second.

155 00:23:50.090 --> 00:23:52.090 Michael Schnuerle (OMF): There's a comment from Duncan.

156 00:23:52.780 --> 00:23:56.470 Michael Schnuerle (OMF): About understanding historical texts based on…

157 00:23:56.940 --> 00:24:04.440 Michael Schnuerle (OMF): Curb… curb legislation and transferring them automatically into digital map-based assets.

158 00:24:04.560 --> 00:24:07.180 Michael Schnuerle (OMF): Duncan, do you want to elaborate on that?

159 00:24:07.390 --> 00:24:09.150 Michael Schnuerle (OMF): Now, a little bit more.

160 00:24:11.460 --> 00:24:13.320 Michael Schnuerle (OMF): Or you could do it in the chat, too.

161 00:24:17.680 --> 00:24:20.109 Michael Schnuerle (OMF): But otherwise, yeah, that's…

162 00:24:21.150 --> 00:24:24.929 Michael Schnuerle (OMF): there's that… I guess there's that other side of it which you're getting at, which is…

163 00:24:25.260 --> 00:24:34.069 Michael Schnuerle (OMF): that same internal process, and how do you get it into map form, so ArcGIS or other digital maps? And that's a similar problem

164 00:24:36.140 --> 00:24:43.129 Michael Schnuerle (OMF): or a challenge that you… and pipeline you would go through, just like you get it to CDS from your systems, you… getting it to a map is also…

165 00:24:43.530 --> 00:24:56.879 Michael Schnuerle (OMF): Similar because there's workflows, there's change management, and there's a loss of some sort of information along the way, because the map can't show everything that's happening, only geospatial-type components.

166 00:24:57.140 --> 00:25:01.479 Michael Schnuerle (OMF): Of the data, so… Mapping is another output.

167 00:25:03.570 --> 00:25:07.930 Michael Schnuerle (OMF): Alright, well, I'll keep it open for other people to comment over the VA.

168 00:25:11.380 --> 00:25:16.180 Olivier Audet-AMD Montreal: Yes, audier from Montreal.

169 00:25:17.670 --> 00:25:28.470 Olivier Audet-AMD Montreal: Some general aspect, same as many people's on our sites, it's to gather the data, so live, live data from the street first.

170 00:25:29.450 --> 00:25:32.749 Olivier Audet-AMD Montreal: More than that, it's more complicated to maintain it.

171 00:25:32.950 --> 00:25:37.799 Olivier Audet-AMD Montreal: So, having a nice process to maintain it, so…

172 00:25:37.930 --> 00:25:48.710 Olivier Audet-AMD Montreal: We're working on that, so having an enterprise system to… an internet surgeon to, like, gather the data, update it, and generate CDS or other,

173 00:25:49.020 --> 00:25:59.369 Olivier Audet-AMD Montreal: outputs with these data. So that's the general things, so I think we'll talk about this many, many public or private entities have that problem.

174 00:26:00.350 --> 00:26:02.579 Olivier Audet-AMD Montreal: More technical point.

175 00:26:02.870 --> 00:26:07.279 Olivier Audet-AMD Montreal: Just skinning out at the oven, I have a report I get today from my,

176 00:26:07.650 --> 00:26:13.350 Olivier Audet-AMD Montreal: We did a pilot test with our data convert to CDS.

177 00:26:13.720 --> 00:26:24.990 Olivier Audet-AMD Montreal: And some things came out, and we'll discuss more on that, but sometimes, custom attributes. Maybe have a space to have custom attributes about everywhere.

178 00:26:25.130 --> 00:26:30.819 Olivier Audet-AMD Montreal: Because, it would help us to, like, keep up in the standard, and maybe…

179 00:26:30.980 --> 00:26:37.900 Olivier Audet-AMD Montreal: Proposed evolution that, the version you're using, make sure you have, like, custom attributes.

180 00:26:38.130 --> 00:26:40.519 Olivier Audet-AMD Montreal: So is that something I can put on GitHub?

181 00:26:41.740 --> 00:26:44.860 Olivier Audet-AMD Montreal: Other stuff.

182 00:26:46.340 --> 00:26:55.629 Olivier Audet-AMD Montreal: To maintain or report error from the field, or maintain stuff, Montreal, we have many…

183 00:26:56.380 --> 00:27:01.220 Olivier Audet-AMD Montreal: Geospatial and timely, overlap regulation.

184 00:27:01.940 --> 00:27:06.880 Olivier Audet-AMD Montreal: So, be forced to have just one geometry.

185 00:27:07.240 --> 00:27:09.769 Olivier Audet-AMD Montreal: And not putting, like, many together.

186 00:27:09.880 --> 00:27:14.819 Olivier Audet-AMD Montreal: Could be a problem for us, because we won't be able to…

187 00:27:15.790 --> 00:27:22.699 Olivier Audet-AMD Montreal: manage and see which panels are problematic on the field sometimes. So, it's a maintenance…

188 00:27:22.940 --> 00:27:25.330 Olivier Audet-AMD Montreal: Things, maybe, so that's detailed.

189 00:27:25.640 --> 00:27:27.870 Olivier Audet-AMD Montreal: I'm in my destined for now that

190 00:27:28.400 --> 00:27:33.909 Olivier Audet-AMD Montreal: We're supposed to have, like, just maybe one line string, or one geometry per recital street.

191 00:27:34.020 --> 00:27:40.319 Olivier Audet-AMD Montreal: So maybe having more things, more flexibility on that maybe can be some things that'll help us.

192 00:27:40.780 --> 00:27:50.080 Olivier Audet-AMD Montreal: And the other one, that's, our thinking is I have, thinking of, other type of parking, let's say, off-street parking.

193 00:27:50.290 --> 00:27:54.419 Olivier Audet-AMD Montreal: So we have off-street parking, we need to manage it. I know there's other options.

194 00:27:55.120 --> 00:27:57.980 Olivier Audet-AMD Montreal: Maybe I have more guideline to…

195 00:27:58.310 --> 00:28:01.309 Olivier Audet-AMD Montreal: To manage or integrate with CDS.

196 00:28:01.530 --> 00:28:11.670 Olivier Audet-AMD Montreal: So that's the thing. I just looked 10 minutes before that meeting in the report I received this morning, but I'll dig more and have more information for everyone.

197 00:28:13.510 --> 00:28:16.780 Michael Schnuerle (OMF): Yeah, thank you for sharing. That's… that's interesting. The,

198 00:28:17.340 --> 00:28:20.719 Michael Schnuerle (OMF): For off-street parking, so CDS supports

199 00:28:20.830 --> 00:28:26.599 Michael Schnuerle (OMF): In a way, you can use CVS, and I think Omaha does this for surface parking off-street.

200 00:28:26.880 --> 00:28:30.390 Michael Schnuerle (OMF): But it really doesn't support parking garages very well.

201 00:28:30.560 --> 00:28:33.709 Michael Schnuerle (OMF): Do you have a need for both of those, or something.

202 00:28:33.710 --> 00:28:39.710 Olivier Audet-AMD Montreal: Maybe both, but more… on our side, we're more, service parking that we manage.

203 00:28:39.950 --> 00:28:42.099 Michael Schnuerle (OMF): The order, like, in…

204 00:28:42.100 --> 00:28:45.990 Olivier Audet-AMD Montreal: Building, parking, or, basement parking is more a partner.

205 00:28:46.250 --> 00:28:52.069 Olivier Audet-AMD Montreal: So, that's more an issue, but it might be interesting to have something too, but…

206 00:28:52.300 --> 00:29:00.320 Olivier Audet-AMD Montreal: what we manage, it's, service parking, yeah. We have, like, zones that are our permits, specialized permits for that.

207 00:29:02.060 --> 00:29:02.400 Michael Schnuerle (OMF): Yeah.

208 00:29:02.400 --> 00:29:05.020 Olivier Audet-AMD Montreal: So, if that's in CDS, just…

209 00:29:05.380 --> 00:29:13.889 Olivier Audet-AMD Montreal: if we, like, talk that, or are having a paper not to say how to work with, let's say, a PDS or other, another,

210 00:29:14.940 --> 00:29:17.140 Olivier Audet-AMD Montreal: As they endure to manage that.

211 00:29:17.780 --> 00:29:20.170 Michael Schnuerle (OMF): Yeah, Hannah's got her hand up, maybe…

212 00:29:20.330 --> 00:29:22.960 Michael Schnuerle (OMF): Are you gonna talk about Omaha in this?

213 00:29:23.120 --> 00:29:25.609 Hannah Adeponu: Yeah, yeah, so I… I guess…

214 00:29:25.800 --> 00:29:33.959 Hannah Adeponu: My mind has always been to partner what we do with CVS and also use APBS.

215 00:29:34.110 --> 00:29:37.750 Hannah Adeponu: For the structured environment.

216 00:29:37.990 --> 00:29:53.059 Hannah Adeponu: Now, I can see where they overlap and… and would be beneficial to have, kind of, an understanding of how they would maybe mesh well together, but from a… from a standpoint of our use of CDS, I, like, we have some…

217 00:29:53.250 --> 00:30:02.180 Hannah Adeponu: Enforcement procedures that are very similar for, for our service lot parking.

218 00:30:02.180 --> 00:30:13.540 Hannah Adeponu: So I guess you could consider CDS as part of that, but I would… I would steer towards APDS and being the solution that Omaha will…

219 00:30:13.660 --> 00:30:17.880 Hannah Adeponu: likely have an enduring implementation of, or the opposite requirement.

220 00:30:19.910 --> 00:30:33.469 Michael Schnuerle (OMF): Yeah, I remember, when you first… when Omaha first released, and maybe it's still there, I haven't looked recently, your Curbs API publicly, there was some definition of the off-street parking in CDS.

221 00:30:33.560 --> 00:30:42.920 Michael Schnuerle (OMF): That way, in addition to on-street parking. But yeah, APDS sort of has that larger scope, with less detail at the curb.

222 00:30:43.180 --> 00:30:51.150 Michael Schnuerle (OMF): And so it handles things like payment interactions and, higher level.

223 00:30:51.650 --> 00:31:02.940 Michael Schnuerle (OMF): things, and does… I think it does handle, parking garages in a way that CDS does not. But I think we haven't, we have had discussions about

224 00:31:03.220 --> 00:31:08.519 Michael Schnuerle (OMF): making it clear that CDS supports surface parking and how to do it.

225 00:31:08.900 --> 00:31:10.219 Michael Schnuerle (OMF): And then…

226 00:31:10.350 --> 00:31:20.100 Michael Schnuerle (OMF): if we wanted to, we could look at parking garages in that same sort of scope of CDS, to be supported as well.

227 00:31:22.390 --> 00:31:32.499 Michael Schnuerle (OMF): Something else that, Olivia, you managed… you mentioned was, custom attributes. So we do, in CPS 1.1, I just want to point out we have

228 00:31:32.500 --> 00:31:45.200 Michael Schnuerle (OMF): some custom attributes in some areas of CDS. I put a link in the chat. So, if you have, yeah, certain fields, you can add it to these sorts of pieces of CDS. Are you thinking of something beyond that?

229 00:31:45.930 --> 00:31:55.400 Olivier Audet-AMD Montreal: I don't… Recall which field exactly meant in some places or entities that do not have custom attributes.

230 00:31:55.520 --> 00:32:01.739 Olivier Audet-AMD Montreal: For sure, we use the one, like, in Zones and stuff like that, but I think there's some places that's missing, maybe.

231 00:32:02.440 --> 00:32:07.940 Olivier Audet-AMD Montreal: That's what I recall after, like I said, is that, like, 10 minutes, my report, so…

232 00:32:08.720 --> 00:32:18.589 Olivier Audet-AMD Montreal: Let's say maybe in policy, or not really in, or object, if there's, like, custom, yeah, I see now already looking like right now.

233 00:32:19.060 --> 00:32:21.570 Olivier Audet-AMD Montreal: I don't think do we have for policy?

234 00:32:22.580 --> 00:32:23.930 Olivier Audet-AMD Montreal: That's an example.

235 00:32:24.250 --> 00:32:24.989 Michael Schnuerle (OMF): Okay, yeah.

236 00:32:24.990 --> 00:32:37.059 Olivier Audet-AMD Montreal: So, so that's flexibility, I think it's easy to put, just like custom, and you put it in there, you can promote, and after discuss, how it can be implemented or added to the standard afterwards.

237 00:32:37.540 --> 00:32:45.239 Michael Schnuerle (OMF): Yeah, that's great. Yeah, if it needs to be added to the policy, that would be pretty straightforward, but that's good to know that that is a potential pain point for you.

238 00:32:47.410 --> 00:32:51.720 Olivier Audet-AMD Montreal: And maybe, I don't know if it's really explained well also how to…

239 00:32:52.220 --> 00:32:55.120 Michael Schnuerle (OMF): Manage and define these custom attributes?

240 00:32:55.420 --> 00:33:01.979 Olivier Audet-AMD Montreal: So, I think I have a proposition, but maybe I'll, I'll have to… I bring up this to,

241 00:33:02.530 --> 00:33:06.449 Olivier Audet-AMD Montreal: The current meetings, you have, they can evaluate by everyone, too.

242 00:33:07.640 --> 00:33:15.629 Michael Schnuerle (OMF): Yeah, yeah, I think we've… I feel like we had a good solution where you're required to provide a data dictionary, for instance, to make it clear what they all mean.

243 00:33:15.960 --> 00:33:35.810 Michael Schnuerle (OMF): And then it's discouraged to use them if otherwise it can fit in other parts of CDS, and then if you are using a lot of them, then those things that are used frequently could become an official field in CDS in a future version. So we do have some guardrails on it, but yeah, look at it and see if it… if it… if it matches all of your needs.

244 00:33:39.650 --> 00:33:43.559 Michael Schnuerle (OMF): I'm gonna look at Kenya's comment here in the chat.

245 00:33:43.930 --> 00:33:52.620 Michael Schnuerle (OMF): Change Management in San Francisco, Success Building Champions inside our agency, outside of our silo.

246 00:33:52.850 --> 00:33:58.919 Michael Schnuerle (OMF): But implementing process changes to expand the use of CDS more broadly is a challenge, yeah.

247 00:33:59.940 --> 00:34:00.860 Michael Schnuerle (OMF): I agree.

248 00:34:05.980 --> 00:34:08.969 Kenya Wheeler, SFMTA (He/Him): Michael, if I could just expand on that just really briefly.

249 00:34:08.969 --> 00:34:09.649 Michael Schnuerle (OMF): Yeah, go ahead.

250 00:34:09.650 --> 00:34:10.199 Kenya Wheeler, SFMTA (He/Him): Nope.

251 00:34:10.440 --> 00:34:20.629 Kenya Wheeler, SFMTA (He/Him): you know, I think a part of that… Expanding the… Window of, of change management.

252 00:34:21.810 --> 00:34:25.419 Kenya Wheeler, SFMTA (He/Him): Involves, bringing in other…

253 00:34:25.659 --> 00:34:41.100 Kenya Wheeler, SFMTA (He/Him): disciplines, to the conversation about CDS, which you… I've already started doing, like, some of the work that was done, like, in the last couple years, doing presentations to, like, ITS and, you know, our presentations at TRB and NACTO, but I think the more we can…

254 00:34:41.210 --> 00:34:48.099 Kenya Wheeler, SFMTA (He/Him): sort of make the case for… the benefits that CDS offers.

255 00:34:48.760 --> 00:34:52.780 Kenya Wheeler, SFMTA (He/Him): not just for parking current management, but for Allied

256 00:34:53.100 --> 00:35:00.689 Kenya Wheeler, SFMTA (He/Him): You see as Mihanna talked about the, Need to identify temporary meter

257 00:35:01.430 --> 00:35:17.770 Kenya Wheeler, SFMTA (He/Him): deactivations, it's something that we… we deal with, I think most cities deal with at some… to some extent, but that, you know, that can impact, utility construction, merchant operations, so there's really lots of linkages beyond just the, sort of.

258 00:35:18.130 --> 00:35:26.200 Kenya Wheeler, SFMTA (He/Him): Transportation, infrastructure, enterprise, to, like, economic development, to, you know, Communications to the general public.

259 00:35:26.370 --> 00:35:34.100 Kenya Wheeler, SFMTA (He/Him): And so, to the extent that we can also, like, I think… more broadly, You know, advertise, like.

260 00:35:34.330 --> 00:35:47.540 Kenya Wheeler, SFMTA (He/Him): these features, I think that can… especially to policymakers, that can make an argument for why cities can and should invest, resources into bringing CDS to more than just the parking management world.

261 00:35:51.780 --> 00:35:59.290 Michael Schnuerle (OMF): Thanks, Kenya. I'll also point out, related to the discussion about, custom attributes.

262 00:35:59.500 --> 00:36:05.060 Michael Schnuerle (OMF): Shada Rager in the chat mentions

263 00:36:05.230 --> 00:36:10.939 Michael Schnuerle (OMF): something… something else that we already have, which is external references, so if you have an ID,

264 00:36:11.450 --> 00:36:20.649 Michael Schnuerle (OMF): that can link to an external table of information to CVS, then that is also possible with unique ID, so thank you for that.

265 00:36:21.000 --> 00:36:22.149 Michael Schnuerle (OMF): that comment.

266 00:36:22.390 --> 00:36:30.849 Michael Schnuerle (OMF): And then, I think, Duncan is back. Duncan, would you like to speak about your comments about historical orders?

267 00:36:33.980 --> 00:36:40.179 Duncan Balmbra: Yeah, hi there, Duncan Bombra from, Appuay, based here in…

268 00:36:40.810 --> 00:36:51.060 Duncan Balmbra: sunny London today. Yeah, so I'm working with lots of municipalities and cities here, and

269 00:36:51.720 --> 00:36:55.899 Duncan Balmbra: We come across a lot of… the legislation is…

270 00:36:56.040 --> 00:36:59.650 Duncan Balmbra: Very much, in very much historic legislation, it's text-based.

271 00:36:59.720 --> 00:37:16.360 Duncan Balmbra: which is sitting in a filing cabinet, you know, and Michael, to your point earlier on about how loading bays or restrictions of certain bays, that's all documented, but then it's been able to, pull that.

272 00:37:16.460 --> 00:37:22.590 Duncan Balmbra: text automatically into a map-based

273 00:37:23.180 --> 00:37:30.830 Duncan Balmbra: capability, because everyone loves visual stuff. Reading a document that says, you know.

274 00:37:31.080 --> 00:37:38.160 Duncan Balmbra: here in the UK, I'll use an example, double yellow lines, 100 yards from junction A,

275 00:37:38.660 --> 00:37:42.860 Duncan Balmbra: to Junction B, it, you know, it's quite dry, whereas actually.

276 00:37:43.120 --> 00:37:55.600 Duncan Balmbra: viewing the map, and having that legislation converted, and being able to present it easily, on that map layer, I think that's a challenge, but it's that automation

277 00:37:55.870 --> 00:37:58.669 Duncan Balmbra: And that's the key, because to have someone

278 00:37:58.870 --> 00:38:12.859 Duncan Balmbra: literally pull up a document and go, oh, okay, yeah, I've got to draw a line from that vector, you know, to that point, that… and then put the attributes to it, like, you can park there between 9 and 10, but you can't park

279 00:38:13.560 --> 00:38:24.370 Duncan Balmbra: Yeah, it's… that's quite a long-winded way of doing it, so that onboarding process. I'm just sort of talking about the pain points, that I've come across.

280 00:38:24.950 --> 00:38:29.280 Michael Schnuerle (OMF): Yeah, no, that's sort of… especially if you're going from a paper system.

281 00:38:29.750 --> 00:38:41.919 Michael Schnuerle (OMF): To a digital system, that's a lot of time, effort, and either machine learning happening, where you're trying to digitize that with some sort of system, or with a bunch of humans.

282 00:38:42.160 --> 00:38:52.369 Michael Schnuerle (OMF): working hard to turn it into something valuable that can then be communicated as a map or as a CDS API or something. So that is a problem.

283 00:38:52.540 --> 00:38:57.999 Michael Schnuerle (OMF): Is that… are you working in multiple cities in the UK on that problem? Yes. Yeah.

284 00:38:59.070 --> 00:39:01.860 Duncan Balmbra: Yeah, it's not just the UK, I think,

285 00:39:02.040 --> 00:39:10.019 Duncan Balmbra: throughout a lot of Europe, the legislation, curbside legislation, is It has traditionally been tax-based.

286 00:39:10.420 --> 00:39:15.180 Duncan Balmbra: And is stored in a filing cabinet, you know.

287 00:39:15.510 --> 00:39:16.170 Michael Schnuerle (OMF): Yeah.

288 00:39:16.490 --> 00:39:27.269 Duncan Balmbra: So it's been able to convert that quickly, and the quicker you can do that, and the quicker you can validate it, the quicker these cities can start utilizing that data in the digital

289 00:39:27.450 --> 00:39:28.560 Duncan Balmbra: arena.

290 00:39:29.940 --> 00:39:37.110 Michael Schnuerle (OMF): Yeah, I think that's a challenge for a lot of cities. Maybe not filing cabinet level, but even if it's digital in some form, it's… you have to…

291 00:39:37.330 --> 00:39:47.790 Michael Schnuerle (OMF): check the quality and make sure it's consistent and, and then valuable in the end. Jacob, you've had your hand up for a while. You wanna share your…

292 00:39:47.950 --> 00:39:48.960 Michael Schnuerle (OMF): Painpoint.

293 00:39:49.950 --> 00:39:55.279 Jacob Malleau (CurbIQ): Yeah, thanks, Michael. And also, well, I guess kind of a pain point.

294 00:39:55.700 --> 00:39:58.599 Jacob Malleau (CurbIQ): Or more speaking on behalf of some of our clients.

295 00:39:59.310 --> 00:40:01.189 Jacob Malleau (CurbIQ): I mean, first thing I want to say is, I think.

296 00:40:02.470 --> 00:40:07.850 Jacob Malleau (CurbIQ): highlighting the benefits, which Kenya mentioned, and Duncan mentioned some of the benefits there, I think would be…

297 00:40:08.230 --> 00:40:13.920 Jacob Malleau (CurbIQ): like, a clear list of why using CVS is helpful would be important. I have a feeling that

298 00:40:15.370 --> 00:40:22.499 Jacob Malleau (CurbIQ): it almost… The benefits maybe appear to be more for…

299 00:40:23.690 --> 00:40:41.140 Jacob Malleau (CurbIQ): less so for the city and more for all the vendors that deal with the data that the city has, which should also directly benefit the city as well, if it's easy to share data and get it out there, but I think there appears to be, like, this level of effort that has to happen on the city front first, which is maybe…

300 00:40:41.840 --> 00:40:48.500 Jacob Malleau (CurbIQ): You know, speaking on behalf of some cities, maybe, like, making them wary of trying to adopt this.

301 00:40:48.730 --> 00:40:56.030 Jacob Malleau (CurbIQ): I guess I'm also curious… just because you've gone through the same process with MDS, was it the…

302 00:40:56.710 --> 00:40:59.519 Jacob Malleau (CurbIQ): to, like, scale up the usage of MDS, was it…

303 00:41:00.700 --> 00:41:05.750 Jacob Malleau (CurbIQ): Was it the benefits that got the cities on board? Was it the vendors basically forcing

304 00:41:06.960 --> 00:41:22.070 Jacob Malleau (CurbIQ): or, like, vendors sending over data in MDS that, like, forced the cities to adopt MDS on their own fronts? Was it the cities pushing for it? Was it legislation? Like, where did you see… like, how did you see the success of MDS happening? And if there's any lessons learned? Yeah.

305 00:41:22.270 --> 00:41:27.820 Michael Schnuerle (OMF): Yeah, that's a good question. There… and you're right about that effort of the city up front. I think…

306 00:41:27.980 --> 00:41:34.400 Michael Schnuerle (OMF): I think with MDS, one big difference with MDS versus CDS is with MDS, you can implement

307 00:41:34.600 --> 00:41:41.159 Michael Schnuerle (OMF): Your feeds and, information about the equivalent of events or activity.

308 00:41:41.280 --> 00:41:45.199 Michael Schnuerle (OMF): Without having to first digitize any of your infrastructure.

309 00:41:45.480 --> 00:41:59.109 Michael Schnuerle (OMF): So a city could say, okay, for this bike share program, for this scooter share program, for now taxis, or Uber, or for-hire AVs, the cities don't really have to define the roadways or

310 00:41:59.270 --> 00:42:13.249 Michael Schnuerle (OMF): things like that, if they don't want to. It's sort of optional in MDS. And so you can just write into a contract, we are asking for data about operations for these use cases.

311 00:42:13.600 --> 00:42:16.750 Michael Schnuerle (OMF): through M… by using MDS, and so then…

312 00:42:16.870 --> 00:42:21.989 Michael Schnuerle (OMF): More of the effort, I'd say, is on the private companies that are operating.

313 00:42:22.290 --> 00:42:28.059 Michael Schnuerle (OMF): And less is on the city. And so the cities were really pushing for MDS initially.

314 00:42:28.180 --> 00:42:35.730 Michael Schnuerle (OMF): When a lot of these new modes were getting started, like bike share and scooters.

315 00:42:36.320 --> 00:42:41.430 Michael Schnuerle (OMF): And so the cities were the driver there, and I think partially because

316 00:42:42.070 --> 00:42:49.230 Michael Schnuerle (OMF): It gave them something easy to point to, to say, instead of enumerating 20 different fields in a

317 00:42:49.230 --> 00:43:02.879 Michael Schnuerle (OMF): paragraphs of descriptions of what information they needed from the operators who they… who were implementing a program. They could just say, we just want MDS, like, very short, simple, it's through an organization like

318 00:43:02.880 --> 00:43:16.580 Michael Schnuerle (OMF): the OMF, that's a non-profit that's open, and so it's very easy to point to and get that information. The… I think the operators initially were a little bit concerned with the implementation load on their end.

319 00:43:16.880 --> 00:43:21.930 Michael Schnuerle (OMF): But as they scaled and started to go to 10,

320 00:43:22.070 --> 00:43:30.950 Michael Schnuerle (OMF): 20, 50 different cities, they realized that the data standard is actually really valuable, because then they only have to build this extract

321 00:43:30.950 --> 00:43:45.149 Michael Schnuerle (OMF): in this one format once for every city, versus every city asking for something custom or bespoke with data sharing, and so it became adopted more and more as those organizations scaled.

322 00:43:45.610 --> 00:43:53.759 Michael Schnuerle (OMF): And so, lessons learned, it's a good question. I think the CDS does have that upfront

323 00:43:54.610 --> 00:43:59.460 Michael Schnuerle (OMF): challenge, in a way, from cities to have to digitize something or another.

324 00:44:00.110 --> 00:44:02.810 Michael Schnuerle (OMF): It is lightweight, as you know, so you could…

325 00:44:02.990 --> 00:44:09.649 Michael Schnuerle (OMF): Pretty quickly define where your curb zones are that you want to have some special thing in, and then

326 00:44:10.040 --> 00:44:13.169 Michael Schnuerle (OMF): Define those rules and publish that.

327 00:44:13.650 --> 00:44:19.580 Michael Schnuerle (OMF): But to do your whole city consistently and integrate it into a change management system, I think that's where it gets…

328 00:44:19.740 --> 00:44:20.980 Michael Schnuerle (OMF): Complicated.

329 00:44:21.480 --> 00:44:22.460 Jacob Malleau (CurbIQ): Yeah, and…

330 00:44:23.490 --> 00:44:28.800 Jacob Malleau (CurbIQ): kind of like your point about with MDS, you didn't have to digitize everything to start. I wonder…

331 00:44:29.210 --> 00:44:31.509 Jacob Malleau (CurbIQ): And kind of spitballing here a bit is, like.

332 00:44:31.600 --> 00:44:51.590 Jacob Malleau (CurbIQ): when you look at CDS, it really… it maybe is a bit overwhelming. Like, you go and there's, like, a bunch of different endpoints, like, where do I start? What do I want to digitize? I know initially when CDS first came about, a big motivation of it was focusing on the loading zone side of things, and now it's expanded to all elements of the curb.

333 00:44:51.930 --> 00:44:57.240 Jacob Malleau (CurbIQ): But I wonder if, like, focusing on a specific use case again.

334 00:44:57.350 --> 00:45:12.390 Jacob Malleau (CurbIQ): One I'm thinking of offhand is paid parking. So, something I know a lot of cities have to do with, especially if they have multiple vendors, is they maintain where all their paid parking locations are, and they have to send out the updated rates and rules to

335 00:45:12.390 --> 00:45:25.790 Jacob Malleau (CurbIQ): to vendors as they change. And that happens in a wide range of ways. Some just send, like, CSV files with what all the IDs and rules are, and it can be quite manual. Like, showing a clear use case of…

336 00:45:25.790 --> 00:45:28.590 Jacob Malleau (CurbIQ): If you use CDS, and you just…

337 00:45:29.070 --> 00:45:42.439 Jacob Malleau (CurbIQ): Create all your paid parking spaces as curb zones, which is, like, one of the more straightforward conversions. You have all your paid parking rules in CDS, which is also those ones… there's only so many paid parking rules in a city.

338 00:45:42.850 --> 00:45:43.940 Jacob Malleau (CurbIQ): and then…

339 00:45:44.220 --> 00:46:00.349 Jacob Malleau (CurbIQ): here's how you share those out with vendors, so that if you make a change to your paid parking, or you remove meters or add meters, like, here's the clear way of how to do that, like, almost a user guide for that specific use case. I don't know if that'd be valuable to cities, to start, like, with something more…

340 00:46:00.350 --> 00:46:04.699 Jacob Malleau (CurbIQ): concrete and smaller? Yeah. I think it would.

341 00:46:04.730 --> 00:46:20.419 Michael Schnuerle (OMF): That's actually something that we're starting to do with MDS, so it's a broad… you can do a lot with both specs, and to have a specific use case of a specific need, and to describe how to do that one thing with the data standard, I think is valuable. So.

342 00:46:20.840 --> 00:46:30.730 Michael Schnuerle (OMF): And that's why we sort of started with loading zones, was because that was a very specific sort of niche way to frame the whole development of CDS.

343 00:46:30.730 --> 00:46:42.749 Michael Schnuerle (OMF): And now it's larger, and so maybe we need some other use cases to be clearly defined, like paid parking could be one that we can work on and have guidance on for, like, what do you really need? What pieces of…

344 00:46:42.960 --> 00:46:46.330 Michael Schnuerle (OMF): CDS, do you need to do, paid parking?

345 00:46:46.650 --> 00:46:51.690 Michael Schnuerle (OMF): Management. Alright, I'm gonna show… Yeah, Jacob, go ahead.

346 00:46:51.690 --> 00:46:52.220 Jacob Malleau (CurbIQ): so…

347 00:46:52.350 --> 00:47:03.270 Jacob Malleau (CurbIQ): Final thought on that, like, just to speak to, like, the change management process that a lot of people brought up, I think it is a very valuable, use case of CDS, but it is probably one of the hardest to, like.

348 00:47:03.270 --> 00:47:03.660 Michael Schnuerle (OMF): Yeah.

349 00:47:03.660 --> 00:47:07.830 Jacob Malleau (CurbIQ): Revamp your internal change management process, so… I don't know if…

350 00:47:08.410 --> 00:47:15.629 Jacob Malleau (CurbIQ): In theory, in an ideal world, that would be a good starting point, but because it's a big undertaking, maybe some of these smaller initiatives

351 00:47:15.770 --> 00:47:20.509 Jacob Malleau (CurbIQ): could show the value of CDS, which would then make that internal change management easier.

352 00:47:21.190 --> 00:47:31.170 Michael Schnuerle (OMF): Yeah, in some ways, that internal change management is outside of what the scope of CDS is, or even the… what the OMF is able to

353 00:47:31.440 --> 00:47:45.789 Michael Schnuerle (OMF): influence, although we are going to try with the Academy, LMF Academy, and some other things Andrew mentioned here. The Curb Collaborative helps with that as well, I think. But yeah, starting with some of these more straightforward,

354 00:47:45.840 --> 00:47:58.850 Michael Schnuerle (OMF): more external-facing use cases might be good. So, I'm going to show the… Andrew, I'll let you talk a sec. I'm going to show the rest of these questions, just so you all can start thinking about it from even a broader perspective.

355 00:47:59.120 --> 00:48:08.529 Michael Schnuerle (OMF): While someone talks, so just thinking about other issues you might have, are there pain points with the spec itself? And we mentioned a few of those already. Andrew, did you have a follow-up?

356 00:48:08.930 --> 00:48:32.099 Andrew Glass Hastings (OMF): Yeah, just real quick, Michael, thanks. And Jacob, really good points, and I think the, kind of, at the meta level around CDS and some of the key differences with MDS is the longer, the slow burn, if you will. Like, CDS is premised on the notion that the digital management of infrastructure, the digital management of public space is the way cities are going to do their work in the future.

357 00:48:32.100 --> 00:48:56.200 Andrew Glass Hastings (OMF): But that transition is not going to happen overnight. And some cities are going to get there faster, some cities are going to get there slower, and so we need to support this transition over the next several years. And that's exactly what we're seeing. And so the pace of change that we're seeing right now is exactly what I would expect to see, because we're asking public agencies to do things very differently than they've done them for decades, and that change is hard and takes time.

358 00:48:56.200 --> 00:49:20.800 Andrew Glass Hastings (OMF): And so, CDS is going to be a slow burn, but it is a perfect example of a tool that is necessary to enable that transition from, essentially, an analog management of infrastructure to a digital management of infrastructure. And that's what we're here to support through programs like the Academy, or the Curb Collaborative, or frankly, just continuing to work with you, Jacob, and the steering committee, to make sure CDS can

359 00:49:20.800 --> 00:49:28.059 Andrew Glass Hastings (OMF): Can be supportive, be approachable, and help that ongoing implementation process.

360 00:49:30.040 --> 00:49:48.289 Michael Schnuerle (OMF): Yes, that's good, good, big picture, Andrew, good picture of what's happening in the ecosystem and sort of the point of the OMF. Also just point people to the chat here for Michael Schwartz from the Exist comment on what MDS is also valid, and I think, accurate, too.

361 00:49:48.420 --> 00:49:56.780 Michael Schnuerle (OMF): So I thought I saw a hand. Do other people have any more of these implementation pain points they'd like to talk about?

362 00:50:10.930 --> 00:50:15.180 Michael Schnuerle (OMF): Maybe I didn't see… I thought I saw a hand raised, but I didn't see who it was.

363 00:50:17.250 --> 00:50:21.829 Michael Schnuerle (OMF): Is there… does anyone have off the top of their head a specific

364 00:50:22.250 --> 00:50:38.709 Michael Schnuerle (OMF): besides, some things we mentioned with surface parking, or parking garages, or external references, or custom attributes, is there anything about this, part of CDS? How do you define zones, or rules, policies, or change those in

365 00:50:38.710 --> 00:50:43.659 Michael Schnuerle (OMF): CDS, or that sort of CDS data schema structure that people would like to

366 00:50:44.100 --> 00:50:46.090 Michael Schnuerle (OMF): Point out as some sort of pain point.

367 00:50:52.630 --> 00:50:55.429 Michael Schnuerle (OMF): This one is, you know, sort of our…

368 00:50:55.540 --> 00:51:06.859 Michael Schnuerle (OMF): in a way, our bread and butter, like, this is where, if there is a problem with these things, that's something we can certainly work on in these working groups and address in the next version of CVS.

369 00:51:08.210 --> 00:51:12.370 Michael Schnuerle (OMF): And I do think that… Yumojo.

370 00:51:12.680 --> 00:51:19.730 Michael Schnuerle (OMF): And San Jose had some things they're going to bring forward around some of this, like how rules and policies are connected.

371 00:51:21.870 --> 00:51:23.140 Michael Schnuerle (OMF): Hannah.

372 00:51:23.970 --> 00:51:39.210 Hannah Adeponu: So, I might just not be totally understanding everything yet, but we were talking internally here in Omaha about the, like, when you implement a new policy, you retire the old policy.

373 00:51:39.480 --> 00:51:42.799 Hannah Adeponu: And for us, I guess I would say that

374 00:51:43.970 --> 00:51:57.040 Hannah Adeponu: is there the potential that we would have, like, an underlying policy for rates, right? So, in Omaha, we have, like, a progressive rate structure on-street, where we have

375 00:51:57.090 --> 00:52:05.789 Hannah Adeponu: 2-plus zones, three-plus zones, and economy zones. But from time to time, as I was talking about earlier, we'll have meter hooding, so

376 00:52:05.790 --> 00:52:17.940 Hannah Adeponu: There would be a policy for a time-limited point in time from today through the end of the week, where the rule and regulation in that particular zone

377 00:52:17.940 --> 00:52:21.670 Hannah Adeponu: For particular spaces may be no parking.

378 00:52:22.130 --> 00:52:30.999 Hannah Adeponu: But then we would want to revert back to that, underlying rate policy once those hoods were taken off.

379 00:52:31.300 --> 00:52:37.040 Hannah Adeponu: I guess I would expect that that's how the spec is working Today.

380 00:52:37.120 --> 00:52:55.729 Hannah Adeponu: And if not, we could certainly architect something to… to reapply that underlying policy with a new number after we take the hoods off, but I was just wanting to know, like, did you have… did… was that contemplated in the original conversations, or is that something…

381 00:52:55.730 --> 00:52:58.530 Hannah Adeponu: That I'm just not getting completely yet.

382 00:52:58.860 --> 00:53:12.849 Michael Schnuerle (OMF): I think that's a great question. What I'll do is I'll follow up and look at the specs and see how that is… should be implemented now. I don't know off the top of my head, maybe someone else on the call does, but if I had to guess off the top of my head, I think…

383 00:53:14.040 --> 00:53:27.160 Michael Schnuerle (OMF): if you… I think that might be a gap in CDS, where if you want to temporarily change what's happening and then go back to what it was, I do feel like the spec now says you would need to make a new policy for the bagging.

384 00:53:27.430 --> 00:53:32.379 Michael Schnuerle (OMF): Give it a new number, attach it to the zone, and then when you go back.

385 00:53:33.300 --> 00:53:48.709 Michael Schnuerle (OMF): you could probably use that same policy, actually, because that other policy didn't change. You just took it away from the zone, and you could put it back on there, but you need to do that. But if that policy ever changes later, like, let's say, citywide, you go from

386 00:53:48.890 --> 00:54:01.230 Michael Schnuerle (OMF): you know, one of your things is no parking from 8 to 5, or something like that, and you change it to 8 to 6, then you've made a change, and you need a new policy and a new ID, and you have to change that everywhere.

387 00:54:01.570 --> 00:54:06.720 Michael Schnuerle (OMF): So, anyway, I guess… just thinking out loud, I feel like you could swap that

388 00:54:07.050 --> 00:54:16.430 Michael Schnuerle (OMF): curb ID policy… attached policy to a new one temporarily, and then switch it back, but I could be wrong about that, so I'll research that and figure it out.

389 00:54:17.530 --> 00:54:18.130 Hannah Adeponu: Okay.

390 00:54:18.130 --> 00:54:24.120 Michael Schnuerle (OMF): Oh, and Jacob from KirbyQ also says you can leverage the CDS priority field.

391 00:54:24.680 --> 00:54:29.309 Michael Schnuerle (OMF): to have a policy temporarily override the paid parking policy. That's true.

392 00:54:30.090 --> 00:54:31.030 Michael Schnuerle (OMF): That could be awaited.

393 00:54:31.030 --> 00:54:44.079 Hannah Adeponu: So we wouldn't have to remove that policy from the zone at all. We would just prioritize the hooding one, and then once that one is over, it would be archived, and the paid parking would be

394 00:54:44.280 --> 00:54:47.919 Hannah Adeponu: reimplemented. Essentially, take this priority. Okay.

395 00:54:48.250 --> 00:54:58.810 Jacob Malleau (CurbIQ): Which, maybe that's one… another good example of a simple use case of, like, here's how you show that… where all your meters are to the commission, and the policies you would use to do that.

396 00:55:01.130 --> 00:55:17.860 Michael Schnuerle (OMF): Yeah, but I will say, maybe in general, this bullet here, changing zones and policies, is a discussion point. The way it's implemented in CDS is very similar to how it is in MDS, so we did it the same way, where if you make a structural change to a policy, you need to make a new policy.

397 00:55:17.910 --> 00:55:19.210 Michael Schnuerle (OMF): Because…

398 00:55:19.210 --> 00:55:42.279 Michael Schnuerle (OMF): neither spec really has, like, an audit trail of what happened with changes, and so rather than confuse someone who's looking at, you know, all the policies in your city, and then you've just changed the time on them, this gives them, like, a really obvious way to know, oh, something has changed, I need to look at it, versus trying to make a change, and they're not aware of it because it's the same policy ID, so…

399 00:55:42.280 --> 00:55:43.710 Michael Schnuerle (OMF): But, having said that.

400 00:55:43.980 --> 00:55:53.859 Michael Schnuerle (OMF): That could be an update to CDS where we don't do it that way. Maybe there is more of, like, an audit trail of this time this field was changed, and so go ahead and check it, or something like that.

401 00:55:57.670 --> 00:56:17.289 Michael Schnuerle (OMF): All right, so, that brings us to the end of the meeting. I have a lot of notes, and I will look at the recording as well to take more notes. Speaking of implementation, consider using CDS 1.1 in your work. We've got a bunch of resources. Some of the things, even, that were brought up today about

402 00:56:17.660 --> 00:56:37.989 Michael Schnuerle (OMF): benefits of CDS, or maybe how to get started. We do have a getting started guide, which can address some of those things, and that's linked to in the slides. I'll make sure to put it in the notes. And our next meeting is going to be, we think, March 17th now, instead of March 24th, because of a

403 00:56:38.590 --> 00:56:39.680 Michael Schnuerle (OMF): conflict.

404 00:56:39.930 --> 00:56:56.270 Michael Schnuerle (OMF): In Europe, so we might move that, so just keep an eye out for an email about the new time, new date, for the CDS meeting next month, but otherwise, we will see you there. Thanks for attending today, thanks for the discussion.

405 00:56:56.700 --> 00:57:14.700 Michael Schnuerle (OMF): And if you have other things that were not brought up today that you thought about, please email me or get in touch with us through our website, and we can make sure to… I can point you in the right direction, and we can make sure to capture those so that we can take action on them in the future.

406 00:57:16.280 --> 00:57:17.960 Michael Schnuerle (OMF): All right. Thanks, everyone.

407 00:57:19.210 --> 00:57:21.170 Michael Schnuerle (OMF): Thanks to our steering committee as well.

408 00:57:22.590 --> 00:57:23.740 Michael Schnuerle (OMF): See you all later.

CDS logo

CDS Links

1.1.0 Release

1.0.0 Release

Clone this wiki locally