open-loadflow GLSK balance adjustment plugin

[jeandemanged]

Describe the current behavior

Current way to perform custom balances adjustments with existing powsybl features is via the existing powsybl-entsoe balance-adjustment module, working externally to any load flow implementation.

Describe the expected behavior

powsybl-open-loadflow plans to provide a plugin mecanism allowing to describe externally how balancing should be done (powsybl/powsybl-open-loadflow#979).
For Entso-e users this will be leveraged to use GLSKs in all possible forms (GSKs, LSKs, mix of GSKs and LSKs, proportional and merit order, ...).
This issue proposes to create an OLF plugin where slack imbalance distribution and/or area interchange control error would use GLSKs in replacement of the existing OLF balance modes (as defined in the powsybl-loadflow-api).

Describe the motivation

Typical use cases:

• Being able to import GLSKs from various sources (e.g. Entsoe XML, Entsoe CIM/NC/CSA profiles, CSV files, ...)
• Area Interchange Control (AIC Area Interchange Control as OuterLoop powsybl-open-loadflow#978) using GLSKs in Load Flow and Security Analysis
  • In Load-Flow: AIC uses GLSKs to adjust area net position to target values
  • In Security Analysis, it is basically the same as load-flow:
    • In N-1: when simulating a generator loss, we might want to check violations after aFRR/mFRR (secondary control) actions, i.e. after area net positions are restored to market values (aFRR/mFRR acts mostly within 1-2 minutes, 5 max), instead of checking violations immediately after the trip on a network state having the generation loss imbalance distributed over all areas of the network.
    • (potentially/why not/to triage) In N-1 with OperatorStrategy: Countertrading & Redispatching remedial actions using GLSKs

Extra Information

No response