Web conference notes, 2022.08.04 (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:
18 Attendees
Main Topics
Agency Provider Unification Proposal
- See Agency and Provider Proposal for comments from agencies
- Review ‘option 5’ which is to align as much as possible between Agency and Provider
- See linked doc but here is the idea:
| Function | Provider 1.x | Agency 1.x | Provider 2.0 | Agency 2.0 | Notes |
|---|---|---|---|---|---|
| Devices | GET /vehicles | POST, GET, or PUT /vehicles | GET or POST /devices | POST or PUT /devices | Agency: add bulk option; Provider: Vehicle make/model/etc. info, last event, or both; single or bulk |
| Events | GET /status_changes | POST /vehicles/{device_id}/event | GET /events | POST /events | Provider: rename, drop device details. Note status_changes is removed in favor of events; Agency: rename, add bulk POST |
| Trips | GET /trips | n/a | GET /trips | POST /trips | Provider: drop device details, make route_info optional via telemetry |
| Telemetry | n/a | POST /telemetry | GET /telemetry | POST /telemetry | Add nullable trip_id to each telemetry point |
| Stops | GET /stops | POST /stops | GET /stops | POST /stops | Unchanged |
| Reports | GET /reports | n/a | GET /reports | n/a? | Should we add a POST to Agency? |
Based on working meeting with eps from SFMTA, OMF, Blue Systems, E&A, and Populus developed the proposal draft based on a public Working Group call for participants.
WGSC Meeting Organizers
- Host: Sebastian Berthaud, Blue Systems (Steve Brining = stand-in host
- Facilitator: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle, OMF
- Note taker: TBD
- Review unification document and leave comments and suggested edits
- Ask more providers to respond to this
- Review Passenger Services document and leave thoughts, then add content to the PR
- Review Justin’s work from Populus for sample JSON policy use case
Recap
- Started with idea of aligning Agency and Provider more
- Came up with options, iterated across public working meetings and document
- Had a working meeting last Friday with proposal details worked out
Marie presenting
Devices
- Vehicles has Agency registry, and Provider has list of vehicles
- Call it /devices (Also could be /vehicles but devices is canonical)
- Pull device info out of trips and put in /devices and /events
Events
- Merge status_changes into events
- Since modes will have more details about devices, good to pull that out of some endpoints and reduce redundancy
- Agency could bulk post multiple events at once, get response of issues. Could still do one at a time if wanted.
Trips
- Trips, adding to Agency, to capture metadata around trips to include metadata
- Route info would be optional, in trips, but could go in route?
- Should route even be in trips now?
- Is telemetry as accurate as routes after trip end
- If you have telemetry delays, do you wait and make the trip end data in there
- Maybe more guardrails on edge case to make sure they are handled consistently
- Pushing trips out pushes bookkeeping complexity to consumer, but maybe providers are already handling this
- Josh at Lyft will look at look at getting more engaged and review, especially a PR, in the coming weeks.
- Lyft said they would have benefited from this alignment if it was ready now.
Telemetry
- Telemetry in provider is good in other modes, like deadheading in taxis, or out of trip movement of scooters as discussed previously
- Increasing richness of telemetry data, and make it available outside of trips is good
- Alex: look at telemetry around revenue trips, or deadheading, etc.
- Does it make sense to associate a state with telemetry
- E&A internally associates states with geography and time
- Adding the trip_id to telemetry helps
- Need to think through option of adding a most recent event to telemetry?
- Outside of on a trip, SFMTA taxi telemetry, 2 status fields for driver and vehicle status, on or off shift with driver (eg, hired, available, off duty). Good to see telemetry for driver on a shift, between paid trips.
- Use cases: has a drive been driving too long without a mandated break, time for shift and time between shifts, per day, etc.
- Ensure to add trip_id to telemetry
- For journeys you could add a journey_id to telemetry, to reduce load from response
- Could have redundant data in telemetry with overlapping trips?
- Could have trip_id array in telemetry?
Stops
- Stops is not changed, added later, already symmetrical
Reports
- Reports. Could easily be added to Agency, keep push vs pull aligned here. Makes sense to add this to Agency now for when reports are ready, they can be pushed
