Web conference notes, 2022.08.18 (MDS Working Group)
MDS Working Group
- Every other Thursday at 9am PT, 12pm ET, 5/6pm CET
Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4
One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom
Note: Attendees register upon entry into the Zoom meeting. An attendee count will be posted here after the meeting:
19 Attendees
Main Topics
- Modes Month kickoff
- MDS 2.0 Goals
- Modes Architecture Task Force
- Modes Month
- How Modes Work in MDS 2.0
- Delivery Robots use cases and data
- Slide Presentation
-
Meeting Recording - Password:
G&zt=c1X
Part of Modes Month.
WGSC Meeting Organizers
- Host: Steve Brining, Blue Systems
- Facilitator: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle, OMF
- Note taker: Marie Maxham, Lacuna
Michael: OMF will be at NACTO in person in Boston, early Sept
Angela: Hosting two sessions, one on curb, one on digital infra
Michael: [presentation for Modes Month, recorded]
Marie: Are we going after delivery writ large, or just bots?
Michael: I feel like we should nail down delivery bots first to learn before getting into larger delivery scenarios, including license plates, drivers, etc.
Alex D: We will also learn about those adjacent topics in the taxi/passenger-services discussion
Angela: Given that this is still an emerging mode, what’s the lightest lift for the first release / MVP? Too many requirements might create unnecessary burden for new modes.
Vlad: I’d like to know about where the depots are, and the range of the bots, so that we can collaborate with the parking division in LADOT. Being able to measure that from MDS would be valuable.
Michael: We may or may not need additional data structures for that.
Vlad: Some level of payload info is important - medicine or food is easier to justify with locals
Camilo: Incidents (malfunction, obstacle detection, etc.) would be useful info
Michael: Operators usually don’t know what happened so this is hard to do in real time, but maybe bots are better for this task than scooters because cameras and sensors. Maybe add a new event type or types.
Camilo: Recommend identify “food from local restaurant” level-of-detail but not specific restaurant or contents
Michael: Must respect laws regarding trade secrets, and document how we are protecting business privacy
Michael: Hey Kiwibot, do you collect info about remote operators, like hours worked or permitting? Do cities ask about that info? Those are important with passenger services.
Camilo: No requests so far. Mostly they ask for location, incidents (e.g. rollovers), and trip details.
Vlad: Internal LADOT discussion: If there’s an incident, what level access can the city get to the raw data? What would be appropriate and necessary. Was the incident because of human/robot interaction, or terrain/robot interaction? This is what the citizens will ask. Can correlate with 311.
Michael: Incident reports could inform Policy. Is SJ publishing Policy objects?
Camilo: Not that I’ve seen.
Michael: [next steps from the slide deck]
Andrew: Great kickoff! Work beyond micro mobility is exciting. Thanks to Kiwibot for being on the call! We need as much participation from operators as possible. Please let us know who else you’re working with.
