Web conference notes, 2021.01.28 (Joint Working Group)
Joint Working Group - Provider Services
NOTE NEW TIME TWO HOURS SOONER
- Every other week call at 9am PT / 12pm ET / 6pm CET
NOTE NEW ZOOM MEETING ID/LINK/PHONE! (as of Jan 1, 2021)
Meeting ID: 841 7098 9462 - Passcode 612987
https://us02web.zoom.us/j/84170989462?pwd=WTRlY25wOVhNeS8wQk1iM2QzYkQvUT09
One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)
Dial by phone: +1 929 436 2866 (US) (Find your local number)
Add your own name, link, and organization during call
- Steve Brining, BlueSystems
- Michael Schnuerle, OMF
- William Henderson, Ride Report
- Alex Demisch, SFMTA
- Seth Herr
- 28 attendees
Goal setting for next release. Meeting 1 - Meeting 2 - Meeting 3
We aren't sure yet if it will have breaking changes or not, if it will be a major or minor release, or clarity on what changes the community is requesting.
Main Topics
- New 'mode' field in provider for how vehicle types are being used. #614
- Delivery Robots - How to split this out into 2 issues (slight movement of vehicles in the ROW in an automated or remote way VS delivery robots) and what tweaks Blue Systems/San Jose has made to MDS to support this on the ground #521
- Requirements API, see Draft document, #608
- Discussion of any unresolved issues that are a priority
- Note there is a new Milestone of "Next Release" to track items that are possible for the next release, but not yet assigned to a release number.
- Bylaws change for release approval timeline
Notes and or transcript of the call with presentation, document, GitHub links and calls to action.
- Should this be high level, in general information, like vehicle type?
- Autonomous scooter vehicles are combination of all these?
- Are these service types?
- Need to look at the combination of type, mode, operation (human hands on, remote camera, AV)
- How are agencies considering this?
- Could end up with multiple state machines
- Policy should govern the available use cases
- After drop off bot may not be available and might need to move to waiting zone, new state or new transition to unavailable
- Need to put in provider, possible in agency
- Drop off, end of trip, and/or linking points along the way
- Track period between trips - like lifecycle of ride hail trips
- See https://ww2.arb.ca.gov/sites/default/files/2020-04/April_1_CMS_workshop_slides.pdf Slide 8
- Develop something for other vehicles, map state machine to that in use in LA
- LA has remote operated robots
- Map to existing State Machine first instead of making changes now in MDS - prove it out
- Scenario where you may want to know the number of packages on board change as deliveries happen - but cities might not care about this
- Dwell time on sidewalk. Why it’s pausing, where it’s going.
- PDD - personal delivery device
- We could add extra states to Policy for testing by city in a fork, then add useful ones back into MDS
- Fork MDS and then bring back changes later
- OMF can offer a forum for discussing all the current work happening from all parties
- Drop in discussion, affinity group, gathering docs in one place, get contact info, temporary working group could be made
- La, San Jose, blue systems, e&A, tortoise - get people together in public area, gather docs and choices
- Taxis? GDEs? May be possible now, but keep robots separate from TNCs/taxis as the latter is a much more mature space
- Which areas/APIs is GPS required, or where you could specify geographies?
- How does aggregation fit into this, GDEs?
- Could add telemetry information requirements to metadata
- Is this for discovery, eg. a root level api?
- What can be added to existing APIs like Policy/Jurisdiction? Timezone, contact info could be in Jurisdiction
- What makes it a new API?
- Healthy for this to be public for transparency and accountability, able to see what agencies are requiring and using
- Need to add versioning/date changed. And guidance with policy. Need to talk to providers just like Policy now.
- Notification period could be a parameter in metadata section.
