Configuring the Grid DERMS Objectives
Overview
The DERMS_OBJECTIVES SRS rule allows system administrators and project teams to configure multiple DERMS Optimizer objectives within Grid DERMS. Each objective defined in this rule establishes the parameters for a specific type of DERMS analysis, including its scheduling, execution window, interval granularity, and policy for pre-existing network violations. By customizing these settings, utilities can fine-tune Grid DERMS to match operational priorities such as Network Capacity Allocation (NCA), Economic Dispatch, and Peak Shaving.
Rule Definition
The DERMS_OBJECTIVES rule is structured as a collection of parameter sets, with each set representing a unique DERMS Optimizer objective. Each set contains the following parameters:
Parameter Details
 
Parameter
Description
Example Value(s)
rule_value_1
Objective Name: Human-friendly identifier for the objective.
"NCA Main Feeders"
rule_value_2
Objective Type: Selects the application's behavior.
0 = Disabled, 1 = NCA, 2 = Economic Dispatch, 3 = Peak Shaving
rule_value_integer_1
Analysis Schedule Hour: Hour in server time zone when analysis should be triggered.
18 (runs analysis at 18:00, or 6 PM)
rule_value_integer_2
Analysis Start Hour: Hour in server time zone that defines the start time of the analysis window.
1 (analysis window starts at 01:00, or 1 AM)
rule_value_integer_3
Number of Analysis Intervals: Number of intervals the analysis will span.
24 (24 intervals for a 24-hour analysis horizon)
rule_value_integer_4
Minutes Between Intervals: Interval granularity in minutes.
60 (intervals are each 60 minutes apart)
rule_value_integer_5
Pre-existing Violations Handling: Policy for how to treat existing network violations during analysis.
0 = Do not ignore, 1 = Ignore, but do not worsen, 2 = Ignore, even if worsened
 
Pre-existing Violations Handling (rule_value_integer_5)
0: Do not ignore pre-violations
The analysis considers any pre-existing network violations as hard constraints-the system will not permit the solution to worsen or overlook these violations.
1: Ignore pre-violations (do not worsen)
The analysis will continue even if violations exist; however, the optimizer ensures that the device's loading is not increased beyond its current state, preventing existing violations from worsening.
2: Ignore pre-violations (allow worsening)
The analysis can proceed even if the solution results in higher loading, meaning violations are permitted to worsen if necessary to meet the objective.
How to Use
Define Each Objective:
Create a parameter set for each required objective (for example, NCA Consider Pre-Existing Conditions, Economic Dispatch Ignore Pre-Existing Conditions (do not worsen)).
Set Schedule:
Configure the analysis schedule hour and start hour according to operational needs and time zone.
Set Analysis Window:
Define the horizon and granularity by specifying the number of intervals and the minutes between each.
Configure Violation Handling:
Choose how pre-existing violations should be treated for each objective.
Enable/Disable Objectives:
Setting rule_value_2 to 0 disables the objective; any other value enables the corresponding objective type.