Web conference notes, 2021.02.04 (Joint Working Group)

Web Conference, 2021.02.04

Joint Working Group - City Services

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

Conference Call Info

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)

Attendees

Add your own name, link, and organization during call

• Henri Bourdeau, BlueSystems
• Michael Schnuerle, OMF
• Steve Brining, BlueSystems
• Mark Maxham, E&A
• Neil Goldader, E&A
• Matt Davis, Populus
• Alex Demisch, SFMTA
• Jean Kao, Populus
• 28 attendees

Agenda

Main Topic : Policy

1. Intro/Importance of Policy (Michael)
2. Support vehicle distribution by % #618
3. Clarify how to meet min for vehicle distribution policies #619
4. Support utilization policies #620
5. Better support for fee 'schedules' #621
6. Other open policy issues

Minutes

Notes and or transcript of the call with presentation, document, GitHub links and calls to action.

Policy API

• Used in a few cities we know of, can support about half of what cities have in their policy docs, would like for it to support more.

618 Distribution Policy

• Percentage of vehicles in zones
• Max per zone
• You have to know the number
• Percent of Cap - on backend
• Tied to deployment numbers. Mean, max
• Meg Baltimore uses % metric - measure in morning 6-9am, up to 35% then redistribute in afternoon before rush hour
• How to define a metric so it’s readable in policy
• Unclear based on permit language
• Maybe make agencies pick a time
• Pick a time window, any time in there if the provider meets it
• Maybe a string field - metric description
• Info is there for public, but maybe a free form text field to
• Tied to direct measurements and metrics.
• Metrics - definition/description/formula in there

619 minimum distribution policies

• William - Could use rates, but question of each time, or for a whole day/hour, etc
• Rate recurrence that could apply to more of the rule types. How often is the rule evaluated?
• Evaluation is checking for compliance
• Once the min is hit, then you know it’s good for that interval
• Jack Reilly Vianova - Max filter over 10 hour enforcement - 5% between 8-12. Look at the previous 4 hours.
• Look back over a period and find the max, compare to the min, historic look to see if it’s met
• Metrics has min over a time period. Must cross the min once. Metrics could be used.
• What’s the sentence in English for how you define a policy in MDS - Ride Report can share their work on this

620 Utilization

• Investigate using metrics API - what are the simplest things to be measured vs complex
• Things could be added to policy which would be simple, eg percents.
• Don’t want to replicate Metrics in policy
• Metrics based policy - anything that can be there can be referenced in Metrics from Policy
• Metrics has API for digital movement, and then there is Methodology that came from SAE.
• In order of complexity: Could 1) add things into policy 2) add well established metrics 3) dynamic metrics calculations
• Jean could share things pulled from all cities

621 Fee schedules

• Pricing for different times of day or how long parked
• It can be expressed with spec, but lots of new rules
• Policy not designed for human readability but 30 rules in Policy vs a table is complex
• Looks messy if you put it in Policy now
• Populus works with car share and others, and they use fee tables.
• GBFS has some complexity https://docs.google.com/document/d/1gJYR2u-rfZI0-HxHkhiXz5nkh7vR1JF2Ux4NwiCI4Gg/edit though it’s not necessarily easy to implement or human readable