Joint Working Group - Provider Services

• Every other week call at 9am PT / 12pm ET / 6pm CET

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

• Michael Schnuerle, OMF
• Sebastien Berthaud, Blue Systems
• Marie Maxham, E&A
• Jack Reilly, Vianova
• Steve Brining, Blue Systems
• Thibault Castagne, Vianova
• Alex Demisch, SFMTA
• 17 attendees

Main Topics

1. MDS 1.2.0 Release review and status. Slower pace, working on Delivery Robots in Member Networks, Requirements finishing up, Policy examples and review.
2. WGSC members and nominations update. 5 nominees. Board vote June 29. Review Checkpoint after that.
3. Review smaller and more direct open issues in 1.2 release
   • #643 Adding KWh consumption in /trip endpoints
   • #589 #616 Rich telemetry data
   • other issues the WG would like to focus on

WGSC Meeting Organizers

• Host: Michael Schnuerle
• Facilitator: Steve Brining
• Outreach: Michael Schnuerle
• Note taker: Alex Demisch

1. MDS 1.2.0 Release review and status.

• Timeline intentionally slower than previous releases due to member feedback. Targeting 1.2 release for the fall.
• Work on delivery robots in the member network will likely be included. If you are an OMF member please join.
• Carshare and passenger services are other member networks.
• Requirements API finishing up, maybe next week.

2. WGSC members and nominations update. 5 nominees. Board vote June 29.

• Review checkpoint scheduled for July - will include new steering committee members at that meeting.

3. #643 Adding KWh consumption in /trip endpoints

• Providing electricity consumption data can support greenhouse gas emission reduction calculations. Cost calculations may be helpful as well.
• How accurate do providers think this information would be? Without very specific guidance, each provider would likely calculate these differently.
• Electricity consumption on trips alone also not the complete picture. Spin and Superpedestrian use carbon offsets to balance out other portions of their operations.
• Scooter electricity consumption will also vary based on terrain, temperature, weight, and rider behavior.
• RideReport would use this for carshare as it would show the benefits of electric vehicles in a mixed fleet.
• Emissions calculations are complex and there is a risk of misrepresenting actual usage through adding this field. Tackling energy consumption is a much larger topic (e.g., lifecycle analysis) that would involve additional organizations. It may be best to piggyback onto other efforts to model energy consumption and greenhouse gas emission calculation efforts. Jascha will reach out to a few researchers.
• This issue will be marked as "Future" for more discussions with more stakeholders

4. #589 #616 Rich telemetry data

• Spin does not keep this information currently.
• Having more accurate GPS chips across fleets would likely reduce conflicts over geofencing violations.
• Providing accuracy data would allow cities and aggregators to display margin of error in maps/location calculations, useful around geofences.
• Including instantaneous speed from GPS would likely mislead as this is typically inaccurate.
• PR 73 is related as it addresses horizontal and vertical accuracy.
• William will file PR to propose bringing related fields in Agency over to Provider trips endpoint. Items will stay 'Required if Available.'
• Will add horizontal and vertical GPS accuracy fields to potentially be added to both Agency and Provider.

New Attendees

No new attendees.