Using Grid DERMS in Real-Time Mode
Grid DERMS can be operated in real-time mode to provide immediate, constraint-aware optimization and dispatch of distributed energy resources (DERs) based on the current state of the network. In this mode, all actions taken, and recommendations provided can applied to the real-time model, and changes are reflected across active operator views and user interfaces. This functionality will run in the background and generate recommendations based on the configured time horizon and start time for each objective that is enabled (for example, NCA, Economic Dispatch, and so on).
Setting the Mode and Objective
The Feeder's DERMS Mode can be set to one following modes of operation using Configuration Assistant Feeder Management Tab (see
Using the Schematica Options Tab for details).
• Disabled: DERMS analysis does not run for the specified feeder.
• Manual: Places DERMS in manual mode, where solutions are automatically generated but must be manually executed by the operator via a switching sheet generated from the DERMS Optimization Report.
• Automatic: Places DERMS in automatic mode, which automatically generates and executes switching sheets.
When setting the mode in configuration assistant a second dialog will appear after the mode has been set which will ask the user to also set the associated DERMS objective. This list will be based on the project configured objectives that have been configured for DERMS (for example, NCA Consider Pre-Existing Violations, Peak Shaving Consider Pre-Existing Violations, and so on).
DERMS Objective Ranking
Overview
In scenarios where feeders or areas connected for DERMS have different objectives, the system uses SRS rule rankings to determine which objective should take precedence. Only the objective with the highest priority (lowest integer rank) is chosen and a single DERMS optimization event is created for all the tied feeders or areas. This approach guarantees that the DERMS analysis and resulting actions are fully aligned across the networked areas.
Rule Definition
The DERMS_OBJECTIVE_RANK SRS rule configures a ranked order of the configured DERMS objectives. This ranking is used when two areas are tied together electrically that may be configured for different objectives. The rank will determine which objective will be run in this scenario. Please note that a lower rank is considered better.
Parameter Details
• rule_value_1: Specifies the name of the DERMS objective. (for example, Network Capacity Allocation, Economic Dispatch, and so on)
• rule_value_2: Specifies the rank that will be applied to the DERMS objective. Note: The lower the number the higher the preference.
1. In Configuration Assistant, ensure OPTIMIZATION_OBJECTIVE_RANK SRS rules exist for each applicable optimization objective.
2. Assign and verify integer ranks for each DERMS objective (lower integer = higher priority).
DERMS Bids for Network Capacity Allocation
The DERMS_BIDS table within NMS will need to be populated by a project defined process or adapter. This table is used to store the proposed output and pricing information for each DER unit participating in the NCA analysis. The table will hold information on an hour by hour basis to represent the output levels the generator plans to operate at and the pricing information the power can be produced at for that same hour. This data will be used as inputs into the analysis to determine if all proposed generation will create congestion issues on the network. The pricing information will be used to determine which generator to curtail first.
Understanding DERMS Events in the Work Agenda
The Work Agenda DMS Status column provides information about DERMS events and results of the calculations. When row or cell coloring is enabled in the Web Workspace (see
Understanding the Table Settings Menu for more information), the DMS Status information is color coded. Possible DERMS status results:
DERMS Event Creation and Management
DERMS processing can be triggered via different operations within the NMS that will lead to event creation. The DERMS Triggers:
• A scheduled timer that runs once a day at a configurable time period; see section Configuring the Grid DERMS Objectives for more information.
• Upon a topology change within the network mode that impacts an area configured for DERMS.
• Upon a change to a DERs configuration within the DERMS Management dialog box.
Typical Life Cycle of a DERMS Event
1. Event Creation / Initiation
When the Grid DERMS optimizer runs an analysis for an enabled objective (such as Network Capacity Allocation, Economic Dispatch, or Peak Shaving), it generates a DERMS event if a solution and action plan is found. This event is automatically added to the Work Agenda for operator visibility. The event captures key contextual information such as the analysis objective, solution start and end time, targeted feeders or zones, and summary of computed control actions or recommended dispatch changes. Please note that when the timer runs to create an event for the next DERMS cycle it will leave any events that are for the current cycle alone as they are the current active events that are being executed, Note: this assumes the DERMS solve is not for a network change that was unexpected. Depending on the time of the day it’s possible to have two events for a DERMS optimization area 1) For the Active Event that is being executed and 2) For the scheduled event that is in queue for the next DERMS cycle.
2. Event Details and Reporting
Each DERMS event includes linked solution data and a detailed DERMS Optimization report. Operators can open the event from the Work Agenda to review the associated solution, including feeder-level impacts, DER dispatch recommendations, pre- and post-solution constraint summaries, and any relevant warnings or violations. This provides a transparent view for validation and decision support.
3. Switching Sheet Generation and Execution
The DERMS solution will include control actions for DER devices, an associated switching sheet is generated and linked to the event. Depending on system and feeder configuration, execution can be manual (operator-initiated) or automatic (executed by the system). The status of plan execution (executing, executed, failed, or aborted) is tracked and shown in the Work Agenda and related dialogs. The various statuses at the beginning of this section describe the possible event statuses.
4. Event Monitoring and Status Updates
As the DERMS event progresses—whether it is awaiting execution, being executed, successfully executed, encounters violations, or fails—the status is updated in real time in the Work Agenda. Statuses include "Solution Generated," "Plan Executing," "Plan Executed," "Execution Failed," and others, allowing users to track the end-to-end event lifecycle.
5. Post-Execution Auditing and Cleanup
After execution, actual outcomes may be collected and compared to estimated values if real-time SCADA telemetry is available. The event record—along with all actions and final statuses—is persisted for reporting and audit purposes. The system periodically cleans up expired or superseded events and solutions from the Work Agenda to ensure only current, actionable information is presented.
6. Handling Topology Updates or New Analyses
If the network changes (such as model edits, outages--unsolicited device operations, or user changes--solicited device operations) occur after an event has been generated, the DERMS system may automatically close out or replace the previous event and associated switching sheet with an updated event and plan. This is dependent on SRS rule DERMS_RESOLVE_ON_TOPOLOGY change which specifies whether DERMS will close out and replace a plan with a new one upon a change to the network.