Have monitoring limits

[alicecaron]

Describe the current behavior

Today, LoadingLimits have a permanent limit and some TemporaryLimit. The permanent limit is the one under which it is possible to remain during an infinite amount of time.
Security class checks for any violation of the permanent or temporary limit by element.
Those or action limits.

Describe the expected behavior

We can model monitoring limits, by element, that can be more restrictive than its permanent limit but do no aim at taking action in case they are crossed. They are not action limits but monitoring limits. These new kind of limits are checked by the Security class and present in the security analysis result as alerts.

Describe the motivation

Be able to monitor an element and alert but not to take action contrary to the permanent limit, temporary limits and their possibly reduced value. The monitor limit can be applied in N and/or N-K state so we need to be able to precise the context case to take into account or not these limits.

Extra Information

• new model class, or refacto to be able to model monitoring limits (use a flag to distinguish action/monitoring limits?)
• serde impacts to be able to import/export these new limits
• import/export gateways (CGMES, UCTE, PSS/E, IEEE, matpower, powerfactory...)
• API
  • security analysis results: model all the violated limits (even the monitoring limits)
  • SA results serde impact
• check for all the violated monitoring limits in the Security class to raise as alert in he result object
• open load flow impact: SA results, take into account the monitored limits as alert (do not aim at having predefined operator strategy action to trigger when the limit is crossed)

[geofjamg]

This is exactly what already existing limit reduction api is doing. Why another feature?