-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Policy API] clarify how to meet min for vehicle distribution policies #619
Comments
This is super reminiscent of what we went through with Rates, where we defined Rate Recurrences to accomplish things like a per vehicle fee that gets assessed once a day. During this process, we went through an exercise to take different Policy rules and express them in English to try to find a general form of how you'd "read a rule". What we came up with is: set the Here are some examples:
So, for this use case, maybe what we are looking for can be accomplished just by allowing recurrences to use for other rule types. For example, the fleet must reach at least 200 once a day: |
Notes from the working group meeting discussions.
@jean-populus and @Karcass what do you think of @quicklywilliam's examples to accomplish this by allowing recurrences for other rule types? William is what you shared here the work you mentioned on the call that Ride Report has done on this? |
I like idea of |
@schnuerle Yes, that is the work I mentioned! @jean-populus I think that's right, two options but with the ability to specify the time period. And maybe we could have There must be 200 vehicles minimum (always): There must be 200 vehicles minimum once each day: Ideally we'd align with the terms used here with those in rate recurrences, which has Weird side note |
Also, do we have any use cases for this besides |
Example distribution policy from Baltimore: How this works in real life is that they check to see if the vehicle count reaches 3 at any time between 5am - 9am. Operators comply by looking at the number of vehicles they already have in that area then dropping off more vehicles to reach 3. Operators don't always drop-off 3 vehicles because equity zones are not necessarily high utilization areas so they want to minimize the number of vehicles they have in those zones while still being in compliance. So unfortunately we can't just count vehicle drop-offs. Example distribution policy from Chicago: Example from DDOT: |
Posting an update from presentation MDS Policy Extensions 15 July 2021
|
Can't recall why I reopened this after Jean closed it. Closing again! |
Is your feature request related to a problem? Please describe.
Many cities have a policy for how many vehicles must be distributed in specific geographies at the beginning of the day. This is generally described as the minimum number of vehicles that operator must deploy. To comply with these policies these policies there must be at least that many vehicles at some point during the specified time. This is not usually the way we think of min/max where the min is the floor and the max is the ceiling. In this case the min is a target that the vehicle count needs to hit but doesn't need to be maintained at that level.
Currently there is no way to describe how these distribution vehicle counts have a different compliance measure then regional vehicle mins/caps.
Describe the solution you'd like
Is this a breaking change
Impacted Spec
policy
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: