Configuration (Administration Users)
To adjust the setpoint limit parameters, the following SRS rules should be changed using Configuration Assistant.
Rule: Optimization High Setpoint Limit
• Rule_value_2: The maximum setpoint that can be issued at a device for normal optimization plans.
Rule: Optimization Low Setpoint Limit
• Rule_value_2: The minimum setpoint that can be issued at a device for normal optimization plans.
Rule: Optimization High Setpoint Limit FLISR
• Rule_value_2: The maximum setpoint that can be issued at a device for FLISR optimization plans.
Rule: Optimization Low Setpoint Limit FLISR
• Rule_value_2: The minimum setpoint that can be issued at a device for FLISR optimization plans.
Rule: Unganged Regulator Maximum Voltage Difference
• Rule_value_2: The maximum voltage difference between any of the phases present on the un-ganged voltage regulator.
Rule: Demote VVO Plans with Setpoint Limit
• Rule_value_1: If set to “Yes” then optimization plans with a setpoint limit violation will be demoted to manual execution if the area is configured for automatic execution.
Tracking Number of Operations on Capacitors and Penalizing Them
To limit the over utilization of capacitors and mechanical wear on capacitors, the number of close operations on SCADA capacitors are tracked on a device by device basis. If the count of the operations on a capacitor (in a configurable time period) exceeds a threshold configured for the class of the device, then Volt/VAr optimization will penalize the capacitor in its real time plans. First the optimization will try to come up with a feasible plan by excluding the capacitor. If there are still violations, then it will attempt to use the excluded capacitor to relieve more violations.
Configuration (Administration Users)
To enable this, the following SRS rules need to be configured using Configuration Assistant.
Rule: Capacitor Operations Count Penalty Threshold
• Rule_value_1: Class name of the capacitors
• Rule_value_2: Threshold count of close operations to penalize a capacitor
Rule: Capacitor Operations History Period
• Rule_value_2: Number of days to consider back in time to count the close operations. By default, it is one day (last calendar day).
Rule: Use Rolling Period Capacitor Operations Count to Penalize
• Rule_value_1: yes or no. By default, it is no (use the count of operations in the last calendar day). If it is set to yes, then the operations in the last 24 hours are used to determine the count and penalize the capacitors.
Rule: Capacitor Operations Penalty Weight
• rule_value_integer_1: Enable: 0 - No, 1 - Yes. Default: 0.
• rule_value_2: Weight.
Note: Currently weight is not in use. Optimization penalizes a capacitors whose operations exceed a threshold by excluding it, if rule_value_integer_1 is set to 1. If there are still violations in the plan, it checks if the capacitor can help relieve them. If it helps, then it will come up with a plan that includes the capacitor.