Should MDS Policy include fees or should fees be separate?

[jean-populus]

Is your feature request related to a problem? Please describe.

Currently MDS Policy contains rates as a beta feature. This supports policies such as trip fees, vehicle fees, and parking fees.

In addition to these operating fees cities also have punitive fees that are applied when policies are violated - for example, a vehicle is parked in a no parking zone. Punitive fees often require evaluation criteria beyond what is currently supported in MDS Policy.

Should MDS Policy be extended to include all fees, including punitive fees? Or would it be better to have evaluation criteria and fees in a separate endpoint?

Describe the solution you'd like

TBD

Is this a breaking change

• I'm not sure

Impacted Spec

• policy

Describe alternatives you've considered

n/a

Additional context

n/a

[schnuerle]

Based on the meeting yesterday, calculating or evaluating fees automatically using MDS may need to wait for a future release. Broadcasting what the fees/incentives are in the Policy API makes sense, but using MDS data to calculate it in a standard or automated way may not align to how cities and providers come to agree on this now, with some chance for review and fixing data errors.