UC5

Volt-VAr optimization with increasing RES generation

1. Description of the Use Case

1.1. Name of the Use Case

IDArea /Domain(s)/Zone(s)Name of the Use Case
1Distribution DER / Field, Station, Operation,UC5

1.2. Version Management

Version No.DateName of author(s)ChangesApproval status
0.92020-11-25T00:00:00Nikolaos Livanos, Vaggelis Alifragkis, Georgios Stravopodis,NoneNone

1.3. Scope and Objectives of Use Case

ScopeThe scope of the proposed Use Case is to implement Volt-VAr optimization approaches in the context of the eBalance+ project, by means of intelligent management units and optimization algorithms in the application field (i.e. Distribution Substations, RES, etc.).
Objective(s)a. To demonstrate the impact of Volt/VAr optimization on voltage stability
b. To demonstrate the impact of Volt/VAr optimization on technical power losses
c. To demonstrate the impact of Volt/VAr optimization on RES curtailment
d. To demonstrate the performance of Volt/VAr optimization both with a centralized and a distributed implementation with respect to possible failures in both approaches.
Related business case(s)None

1.4. Narrative of Use Case

Short description

The proposed Use Case refers to Volt-VAr optimization in a Power Distribution Grid incorporating DER (mainly RES), aiming to apply and demonstrate concepts and technologies of the eBalance+ project. The Use Case shall evaluate a specific distribution grid topology (TBD) in three different setups: 1. Laboratory Numerical Simulation, 2. Laboratory Simulation with Hardware-in-the-Loop (of eBalance+ management units), 3. Actual performance in project’s demo site(s). Regarding setup 3 (demo site) certain modifications in the distribution grid topology are anticipated, mainly due to the limitations of access to grid assets, as well as the limitations to intervene in the present control schemes. Two core scenarios will be presented: 1. Centralized, 2. Distributed. In the Centralized Scenario the Volt-VAr control is arbitrated and executed in the (A)DMS system (assumed to exist). The information is exchanged via the eBalance+ middleware and the MVGMU, LVGMU and DERMU devices (management units) are mainly used for communication interfacing and as remote terminal points (RTUs). In the Distributed scenario, the Volt-Var control is performed in the MVGMU device as an alternate scenario in case of central systems failures. As in the Centralized scenario, the LVGMU and DERMU are used for communication interfacing, again following eBalance+ middleware information routes.

Complete description

The present Use Case aims on the following: • Increased RES penetration in power distribution grids causes congestion and effective Volt-VAr optimization can intelligently manage RES to alleviate the problem. • An information/communication middleware (ebalance+) adopted by intelligent management units installed in the Operation, Station, and Field domains (following SGAM notation) can increase overall system resilience by means of automatic re-configuration and continuity of Volt-VAr service. • Intelligent management units in the Station and Field domains (e.g. MVGMU) are able to provide optimized Volt-VAr service. • Distributed intelligence could support Volt-VAr optimization approaches • Simulate respective Volt-Var optimization approaches • Apply Hardware-in-the-loop of the eBalance+ intelligent devices in the above simulations • Apply selected Volt-VAr optimization scenarios in the eBalance+ pilot installations • Measure and analyze performance in the demo sites

The Volt-VAr Use Case is based on the following methodology:

  1. Define a configurable power distribution grid topology a. Based on detailed analysis the topology may incorporate assets, such as: HV/MV Substation, Substation Capacitor Bank, Substation Transformer with On-Load TAP changer, MV RES, MV/LV Transformer with Voltage Regulator, MV Line Capacitors, LV RES, MV Loads, LV Loads, etc. b. The topology shall define the connections between the assets and perhaps possible reconfigurations (e.g. power switches, etc.) c. The RES generation shall be configurable (e.g. define three RES penetration scenarios: 50%, 100%, 200%). d. Part of the overall topology will be similar to the demo installation topologies
  2. Define various congestion situations
  3. Define specific optimization objective functions: Voltage Range, Power Loss Reduction, Minimum RES Curtailment
  4. Define specific KPIs to support evaluation, comparisons and reporting: Voltage Violations (Frequency, Duration, Number, Excess), Power Losses, RES Energy, (optional KPIs depending on available control of assets: number of capacitor transitions, number of OLTC transitions, etc.)
  5. Implement two scenarios: a. Centralized Volt-VAr: the solver is executed in the (A)DMS at the DSO’s Operation Center b. Distributed Volt-VAr: the solver is executed in the intelligent device in the Primary Distribution Substation (e.g. MVGMU)
  6. Evaluate and compare the two scenarios
  7. Evaluate and compare the grid’s performance before and after the application of optimization
  8. The Use Case shall be implemented according to the following phases: a. Phase 1: Analysis, definitions and laboratory numerical simulations b. Phase 2: Laboratory simulations with Hardware-in-the-loop (e.g. MVGMU, LVGMU, DERMU in the simulation loop) c. Phase 3: Demo sites operations

1.5. Key Performance Indicatiors (KPI)

IDNameDescriptionReference to mentioned use case objectives
KPI.01Reduction of voltage violationsBased on the application of the Voltage Range objective function, this KPI measures the Frequency, Count and Duration of Voltage Violations per busVoltage Range,

1.6. Use case conditions

Assumptions
UC5
Prerequisites

1.7. Further information to the use case for classification/mapping

Relation to other use cases
Level of depth
Prioritisation
Mandatory
Generic, regional or national relation
Generic
Nature of the use cases
Technical
Further keywords for classification
Advanced Distribution Management System, optimisation, simulation, RES, substation

1.8. General remarks

General remarks

2. Diagrams of Use Case

Sequence Diagram - Scenario 1 part 1/2 Sequence Diagram - Scenario 1 part 2/2 Sequence Diagram - Scenario 2 SGAM - Component Layer - Scenario 1 SGAM - Component Layer - Scenario 2 SGAM - Function Layer - Scenario 1 SGAM - Function Layer - Scenario 2 SGAM - Communication Layer - Scenario 1 SGAM - Communication Layer - Scenario 2 SGAM - Information Layer - Scenario 1 SGAM - Information Layer - Scenario 2 SGAM - Buisness Layer

3. Technical Details

3.1. Actors

Actor NameActor TypeActor DescriptionFurther information specific to this Use Case
DSO / UtilityRoleResponsible for operating, ensuring the maintenance of and, if necessary, developing the distribution system in a given area
Service ProviderRoleIndustrial partner involved in the ebalance+ project providing providing management units and algorithms
DER OwnerRoleThe owner of DER installation (see below) or the appointed representative that allows flexibility management
DER installation(s)System(s)Small generation plant(s) (mainly of renewable energy) owned by a legal person
MVGMU, LVGMU, DERMUSystem(s)All devices placed on MV/LV network for monitoring or gathering information on grid’s situation or electrical parameters values. It also includes the IS associated
SCADA, (A)DMSSystemsAll the hardware and software associated, used at power command to control and monitor the network
DMS.VVCSystemThe software that performs the algorithms and produces the desired results. Operates at the DMS level
MVGMU.VVCSystemThe software that performs the algorithms and produces the desired results. Operates at the MVGMU level

3.2. References

No.References TypeReferenceStatusImpact on Use CaseOrganistaor / OrganisationLink

4. Step by Step Analysis of Use Case

4.1. Overview of Scenarios

No.Scenario NameScenario DescriptionPrimary ActorTriggering EventPre-ConditionPost-Condition
PS1Centralized Volt/Var Optimization with RES VariabilityThe optimization logic is performed on the Distribution Management System level by collecting readings from the complete underlying grid. In turn control actions computed by the algorithm are distributed to the complete grid. The Primary scenario is separated in the following cases: 1. Nominal scenario, where the grid experiences no failures 2. DMS failure 3. MVGMU failure 4. LVGMU failure 5. DERMU failureCentralized Volt/Var Optimization with RES Variability
AS1Distributed Volt/Var Optimization with RES VariabilityThe optimization logic is performed on the Medium Voltage Grid level by collecting readings from the complete underlying grid. In turn control actions computed by the algorithm are distributed to the complete gridDistributed Volt/Var Optimization with RES Variability

Notes

4.2. Steps – Scenarios

Scenario Name:
Centralized Volt/Var Optimization with RES Variability
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
1.1Periodic Execution /No Failures – Set InputsNoneDMS sets all the required input to VVCGET
1.2Periodic Execution – OptimizationNoneVVC performs optimization algorithm on given inputs (Optimum Power flow)EXECUTE
1.3Periodic Execution – Get OutputsNoneVVC sends control signals based on resultsCHANGE[VVC.008] The VVC function shall calculate the following:
  1. Capacitor Bank New Status (on/off per capacitor)
  2. TAP Position (number)
  3. Line Capacitor Status (on/off flag)
  4. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 1.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 2.1 | DMS Failure Set Inputs | None | DMS.VVC tries to collect inputs but communication has failed. (Please see AS1) | GET | | | | | | 3.1 | MVGMU Failure Set Input | None | DMS.VVC tries to collect all inputs but MVGMU fails to provide | GET | | | | | | 3.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from MVGMU | EXECUTE | | | | | | 3.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  5. Capacitor Bank New Status (on/off per capacitor)
  6. TAP Position (number)
  7. Line Capacitor Status (on/off flag)
  8. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 3.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 4.1 | LVGMU Failure Set Input | None | DMS.VVC tries to collect all inputs but LVGMU fails to provide | GET | | | | | | 4.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from LVGMU | EXECUTE | | | | | | 4.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  9. Capacitor Bank New Status (on/off per capacitor)
  10. TAP Position (number)
  11. Line Capacitor Status (on/off flag)
  12. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 4.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 5.1 | DERMU Failure Set Input | None | DMS.VVC tries to collect all inputs but DERMU fails to provide | GET | | | | | | 5.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from DERMU | CHANGE | | | | | | 5.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  13. Capacitor Bank New Status (on/off per capacitor)
  14. TAP Position (number)
  15. Line Capacitor Status (on/off flag)
  16. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 5.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. |
Scenario Name:
Distributed Volt/Var Optimization with RES Variability
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
0ConfigurationNoneMVGMU Configures VVC according to VVC.CONFCREATE[VVC.001] The execution period shall be expressed in seconds

[VVC.002] The topology provided to the VVC function shall include the following:

  1. Line Specification (length, conductance)
  2. Load Specification
  3. Generator Specification (rated power)
  4. RES Generator Specification (rater power, inverter specification)
  5. Transformer Specification (voltage step, losses)
  6. Capacitor specification (capacitance)
  7. TAP Specification (voltage Step) | | 1.1 | Periodic Execution /No Failures – Set Inputs | None | MVGMU sets all the required input to VVC | GET | | | | | | 1.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) | EXECUTE | | | | | | 1.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  8. Capacitor Bank New Status (on/off per capacitor)
  9. TAP Position (number)
  10. Line Capacitor Status (on/off flag)
  11. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 1.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 2.1 | DMS Failure Set Inputs | None | MVGMU.VVC tries to collect inputs but DMS has failed | GET | | | | | | 2.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from MVGMU | EXECUTE | | | | | | 2.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  12. Capacitor Bank New Status (on/off per capacitor)
  13. TAP Position (number)
  14. Line Capacitor Status (on/off flag)
  15. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 2.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 3.1 | MVGMU Failure Set Input | None | MVGMU.VVC tries to collect all inputs but MVGMU fails to provide | GET | | | | | | 4.1 | LVGMU Failure Set Input | None | MVGMU.VVC tries to collect all inputs but LVGMU fails to provide | GET | | | | | | 4.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from LVGMU | EXECUTE | | | | | | 4.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  16. Capacitor Bank New Status (on/off per capacitor)
  17. TAP Position (number)
  18. Line Capacitor Status (on/off flag)
  19. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 4.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | 5.1 | DERMU Failure Set Input | None | MVGMU.VVC tries to collect all inputs but DERMU fails to provide | GET | | | | | | 5.2 | Periodic Execution – Optimization | None | VVC performs optimization algorithm on given inputs (Optimum Power flow) without input from DERMU | CHANGE | | | | | | 5.3 | Periodic Execution – Get Outputs | None | VVC sends control signals based on results | CHANGE | | | | [VVC.008] The VVC function shall calculate the following:
  20. Capacitor Bank New Status (on/off per capacitor)
  21. TAP Position (number)
  22. Line Capacitor Status (on/off flag)
  23. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | 5.4 | Reporting | None | VVC computes and reports KPI compliance (continued process across multiple runs) | REPORT | | | | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. |

5. Information Exchanged

Information exchanged IDName of InformationDescription of Information ExchangedRequirement

6. Requirements (optional)

Category IdentifierNameDescriptionmRID
Req_IDReq_Name‘Volt-VAr optimization with increasing RES generation’
IdentifierNameDescriptionmRID
VVC.CONFVVC ConfigurationDescribes all the configuration options needed to be set to the VVC from the SCADA or RTU system that contains the VVC. These options only need to be set once and are:
  1. Grid Topology
  2. Execution Period | [VVC.001] The execution period shall be expressed in seconds

[VVC.002] The topology provided to the VVC function shall include the following:

  1. Line Specification (length, conductance)
  2. Load Specification
  3. Generator Specification (rated power)
  4. RES Generator Specification (rater power, inverter specification)
  5. Transformer Specification (voltage step, losses)
  6. Capacitor specification (capacitance)
  7. TAP Specification (voltage Step) | | VVC.IN | VVC Input Execution Parameters | Describes the Information needed for a Volt/Var execution loop to compute. These are provided by the SCADA or RTU system that contains the VVC and are the following:
  8. Voltage (Distribution Grid)
  9. Active Power (Distribution Grid)
  10. Reactive Power (Distribution Grid)
  11. TAP Position
  12. Capacitor Bank Status
  13. Voltage (RES)
  14. Active Power (RES)
  15. Reactive Power (RES) | [VVC.003] The VVC function shall get as input the Distribution Grid state, which is:
  16. Voltage (V)
  17. Active Power (MW)
  18. Reactive Power (MW)
  19. TAP Position (number)
  20. Capacitor Bank Status (on/off per capacitor) [VVC.004] The VVC function shall get as input the RES state, which is:
  21. Voltage (V)
  22. Active Power (MW)
  23. Reactive Power (MVar) [VVC.005] All the inputs shall be provided by the SCADA in the case of DMS deployment (scenario 1) [VVC.006] All the inputs shall be provided by the MVGMU RTU in the case of MVGMU deployment (scenario 2) [VVC.007] All the inputs shall be provided Inputs that have no value for any reason shall be denoted as “null” | | VVC.OUT | VVC Output Results | Describes the results returned from the VVC after an execution loop. All results are returned to the SCADA or RTU system that contains the VVC which is then responsible to route them to the correct components. The output variables are:
  24. Capacitor Bank New Status
  25. TAP Position
  26. Line Capacitor Status
  27. RES set-points | [VVC.008] The VVC function shall calculate the following:
  28. Capacitor Bank New Status (on/off per capacitor)
  29. TAP Position (number)
  30. Line Capacitor Status (on/off flag)
  31. RES Set-Point (desired power factor per RES source) [VVC.009] All outputs shall be provided to the SCADA in the case of DMS deployment [VVC.010] All outputs shall be provided to the MVGMU.RTU in the case of MVGMU deployment [VVC.011] Any not-set values shall be denoted by “null” | | VVC.RPT | VVC Reporting | Describes the metrics computed after operation for the evaluation target KPIs. These metrics are aggregated in a temporal and a statistical manner and are persistent across runs. The Metrics are:
  32. Voltage Violations Frequency
  33. Voltage Violations Count
  34. Voltage Violation Duration
  35. Voltage Violation Excess
  36. Power Losses
  37. RES Energy
  38. RES Curtailment percentage
  39. Number of Capacitor Switches
  40. Number of OLTC Switches | [VVC.012] The VVC shall be able to report the value of its KPIs [VVC.013] The KPIs shall be measured by the VVC function after it provides outputs. | | MGVMU.OUT | MGVMU RTU Outputs/Measurements | Describes all the values measured and retrieved from the specific RTU. These are:
  41. Capacitor Bank Measurement
  42. Tap Measurement
  43. Voltage
  44. Reactive Power
  45. Active Power | [VVC.014] The MVGMU.RTU shall provide its measurements to the SCADA (scenario 1) [VVC.015] The MVGMU shall provide its measurements to the VVC function directly (scenario 2) [VVC.016] The measurements of the MVGMU.RTU shall be:
  46. Capacitor Bank Status (on/off per capacitor)
  47. Tap Measurement (number)
  48. Voltage (V)
  49. Reactive Power (MVAr)
  50. Active Power (MW) | | MGVMU.CTRL | MGVMU RTU Control Input | Describes all the elements that the specific RTU can control. These are:
  51. TAP Position
  52. Capacitor State | [VVC.017] The MVGMU shall receive control signals from the SCADA as calculated by the VVC function (scenario 1) [VVC.018] The MVGMU shall receive control signals from the VVC function directly (scenario 2) [VVC.019] The MVGMU.RTU shall support the following control signals:
  53. TAP Position (number)
  54. Capacitor State (on/off per capacitor) | | LVGMU.OUT | LVGMU Output measurements | Describes all the values measured and retrieved from the specific RTU. These are:
  55. Line Capacitor Status
  56. Line Voltage Measurement
  57. Reactive Power
  58. Active Power | [VVC.020] The LVGMU.RTU shall provide its measurements to the SCADA (scenario 1) [VVC.021] The LVGMU shall provide its measurements to the MVGMU (scenario 2) [VVC.022] The measurements of the LVGMU.RTU shall be:
  59. Line Capacitor Status (on/off flag)
  60. Line Voltage (V)
  61. Reactive Power (MVAr)
  62. Active Power (MW) | | LVGMU.CTRL | LVGMU RTU Control Input | Describes all the elements that the specific RTU can control. These are:
  63. Line Capacitor State
  64. Voltage Regulator set-point | [VVC.023] The LVGMU shall receive control signals from the SCADA as calculated by the VVC function (scenario 1) [VVC.024] The LVGMU shall receive control signals from the MVGMU (scenario 2) [VVC.025] The LGMU.RTU shall support the following control signals:
  65. Capacitor State (on/off flag)
  66. Live Voltage Regulator Set-Point (Power Factor) | | DERMU.OUT | DERMU Output measurements | Describes all the values measured and retrieved from this unit. These are:
  67. Voltage (RES)
  68. Active Power (RES)
  69. Reactive Power (RES) | [VVC.026] The DERMU.RTU shall provide its measurements to the SCADA (scenario 1) [VVC.027] The DERMU shall provide its measurements to the MVGMU (scenario 2) [VVC.028] The measurements of the DERMU.RTU shall be:
  70. Line Voltage (V)
  71. Reactive Power (MVAr)
  72. Active Power (MW) | | DERMU.CTRL | DERMU Control Input | Describes the controllable element of this unit which is: RES Set-Points. | [VVC.029] The DERMU shall receive control signals from the SCADA as calculated by the VVC function (scenario 1) [VVC.030] The DERMU shall receive control signals from the MVGMU (scenario 2) [VVC.031] The DERMU.RTU shall support the following control signals:
  73. RES Set-Point (Power Factor per RES) |

7. Common Terms and Definitions

8. Custom Information (optional)

KeyValueRefers to Section