Introducing an operator SLA concept on top of policy

[S-eb]

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

The policy concept is well used today to define rules of operations that an agency wants to enforce. The policy specifications allows the definition of penalty that can apply when the rules are not applied.

Now most agencies SLA with operators are considering the overall operator operations not every single device, in order to give some flexibility. For instance: 80% of scooters should not have had a speed limit offense in the reporting period.

The current policy object is well design to enforce the rules, but does not allow the definition of global SLA such as the example above.

Describe the solution you'd like

A new overarching SLA concept in order to explain how a given agency will compute penalty in case a policy is not enforced. Now before pushing in this direction, the question is: should MDS cover this use case? or should it be defined at each agency level without standardization, as long as the rules pushed to the operator follow the policy specifications

Is this a breaking change

• No, not breaking

This SLA object would be a new concept on top of the existing policy ones.

Impacted Spec

For which spec is this feature being requested?

• policy

Describe alternatives you've considered

No alternative consider in the scope of MDS

[schnuerle]

I think this is a good concept with a need and would be pretty easy at least to use MDS to communicate an agency's SLA requirements. I think it would be a new field/area in the Policy Requirements endpoint, maybe per program the city is running.

A starting point could be OMF's sample SLA language about availability and response times.

Could even add SLA language around limiting the use of certain parts/options in MDS, like you see here with Event Types.

[S-eb]

Michael

I think the SLA link above is really linked to the MDS endpoints.

Here the SLA would be related to the MSP operations.

Seb