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).
VPP - Market DER groups can also use DERMS Automatic Generation Control (DAGC) in real time. When a DAGC-enabled group receives a valid Target MW SCADA change that meets the configured deadband, Grid DERMS runs unit commitment for the current interval and automatically dispatches the resulting DER real-power setpoints through a DAGC Dispatch switching sheet. Each successfully solved, processed target appends a timestamped dispatch block to the same sheet for that market analysis. See Working with VPP - Market Group Details in this chapter. The current DAGC workflow dispatches real-power setpoints from Target MW changes; Target MVAR, Target Voltage, and Target Frequency associations do not trigger automatic dispatch.
Working with VPP - Market Group Details
DERMS Automatic Generation Control (DAGC) uses an external Target MW SCADA measurement to update the real-power dispatch of a VPP - Market DER group. This workflow is available in Flex Operations Group Details. It is separate from the Edge DERMS strategy and event workflow.
Enabling Automatic DER Control
The group must be a VPP - Market group with an active analog Target MW SCADA point association configured for DAGC. Access requires the DERMS license and Access DERMS DAGC permission. Changing the setting also requires Allow DERMS Update DER Group permission. Ask your administrator to configure the SCADA measurement mapping and applicable market-analysis and unit-commitment data.
1. Open Group Details for the VPP - Market group and select Real Time Market.
2. Review SCADA Points. If necessary, use Add SCADA Point to associate the group's configured analog Target MW measurement. Use Refresh to reload the associations. Adding or removing associations requires the applicable DER-group update permissions.
3. Select DAGC Enabled and select Save. The setting cannot be enabled until an eligible Target MW association exists. Save is available when the setting has changed and you have update permission.
4. To disable DAGC, clear DAGC Enabled and select Save. Removing the last eligible Target MW association also disables DAGC; restoring an association requires enabling and saving DAGC again.
When an enabled group receives a valid Target MW change that passes the configured deadband, Grid DERMS runs unit commitment for the current interval. Accepted results are dispatched automatically through a system-generated DAGC Dispatch switching sheet. Further accepted targets in the same market-analysis window append dispatch blocks to that sheet. Target MVAR, Target Voltage, and Target Frequency associations do not initiate automatic dispatch in the current implementation.
Monitoring Setpoints and Dispatch
Use DAGC Setpoint vs Dispatch on Real Time Market to compare the following series in MW:
• Market Award: the market-awarded target profile.
• Initial UC Dispatch: the initial unit-commitment dispatch profile.
• Target MW SCADA: the external real-power target measurements.
• Latest UC Dispatch: the latest unit-commitment dispatch profile.
Set Plot Horizon Start and Plot Horizon End to display the required time window. Available series depend on the retained market, unit-commitment, and SCADA data. The dispatch profiles represent unit-commitment results; use switching-step status to check control execution rather than treating the graph as proof that equipment reached the requested output.
Reviewing Automatic Dispatch
DAGC Dispatch sheets are system-managed and view-only in Web Switching and Flex Operations. Operators cannot create these sheets or edit their steps. Review the latest dispatch block and its step states when monitoring the current dispatch. Rejected identifies rejected submissions or unexecuted sibling operations rejected after a DAGC operation fails. Schedule Expired identifies operations whose scheduling deadline expired. A later valid dispatch can recover an eligible Error sheet; historical failed, rejected, and expired operations are retained and are not replayed.
Linking SCADA Points to a VPP - Market DER Group
Use SCADA Points in Flex Operations Group Details to associate existing analog or digital measurements with a Grid DERMS VPP - Market group. Measurements may belong to any NMS device, including a pseudo device that is not a member of the group. Linking a point creates an association; it does not add the owning device to the group's DER members or create a new measurement.
Open Group Details for the VPP - Market group and select Real Time Market. Add and remove actions require Access Grid DERMS DER Group and Allow DERMS Update DER Group permissions.
The SCADA Points table shows Point, Device Name, Measurement, and Value. Point is the current one-based display order. Remaining rows keep their relative order and are numbered consecutively after removal. Associations persist when Group Details is closed and reopened. Values use configured SCADA formatting when available, including digital state text; numeric zero values are displayed. Scroll within the table to view additional rows.
Adding a SCADA Point
1. Select Add SCADA Point to open Link Group to SCADA Points.
2. Enter at least three characters in SCADA Point Search.
3. Set Search Field to All Fields, Point Name, Device Name, or Measurement.
4. Set Match to Wildcard After (starts with), Wildcard Before (ends with), Wildcard Before and After (contains), or Exact Match. Matching is case-insensitive.
5. Set Measurement Type to All, Analog, or Digital, then select Search.
6. Review the SCADA Point, Device Name, Measurement, and Type columns. Only active configured measurements are available, and points already linked to this group are excluded. The list displays at most 100 results. If more results are available, refine the search.
7. Select one result and select Add. The association is saved immediately and appears at the end of SCADA Points. Repeat to add another point.
A VPP - Market group permits only one analog association per configured market-signal category, such as Target MW, Target MVAR, Target Voltage, or Target Frequency. To replace a point in an occupied category, remove the existing association before adding the replacement. Associating other target categories does not by itself enable automatic dispatch.
Refreshing and Removing SCADA Points
• Select Refresh in SCADA Points to reload the saved associations and current values.
• To remove a link, select its row, choose Remove SCADA Point from the Actions or context menu, and confirm. Removal is saved immediately and removes only the association, not the underlying SCADA measurement.
• Removing the last eligible Target MW association disables DAGC for the group. After adding an eligible replacement, select DAGC Enabled and Save to enable it again. Linking a measurement alone does not enable DAGC.
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 has a higher priority.
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.
 
Column
Required
Comments
DEV_CLS
Y
The device class of the DER
DEVICE_IDX
Y
The device index of the DER
AVAIL_PRICE
Y
The availability price in $/MW for the generator to be available and ready at the corresponding date and time range
UTIL_PRICE
Y
The price in $/MW that power can produced at for the corresponding date and time range
KW_FORECAST
Y
The forecast kW for the DER unit for the date and time range
KVAR_FORECAST
Y
The forecast kVAr for the DER unit for the date and time range
MIN_KW
N
The minimum output that generator can produce for the date and time range
START_DATE
Y
The start time for the bid range
END_DATE
Y
The end time for the bid range
 
 
 
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:
 
DMS Status Column
Description
DERMS Solution Generated
DERMS has found a solution.
DERMS Solution Generated with Violations
DERMS has generated a solution, but it contains violations; manual intervention is required if in automatic mode.
DERMS Plan Executing
In automatic mode, DERMS has generated a plan and is automatically executing it. In manual mode a user has reviewed the plan and has initiated plan
DERMS Plan Executed
In automatic mode, DERMS has generated a plan and has automatically executed it. In manual mode a user has reviewed the plan, initiated plan execution from Switching Management, and the plan is now executed.
DERMS Plan Execution Failed
In automatic mode, DERMS has generated a plan and automatic execution has failed. In manual mode a user has reviewed the plan, initiated plan execution from Switching Management, but the plan has failed execution.
DERMS Tags Found
During the DERMS analysis, tags were found in the area being analyzed. The specific tags can be viewed in the Optimization Messages table within the DERMS Optimization Report.
DERMS Aborted
DERMS processing or execution has been aborted by a user.
DERMS Executed with Violations
In automatic mode, DERMS has automatically executed a plan with violations.
DERMS Finding Pre-Violations
DERMS is in the process of analyzing the network for pre-existing violations. These are violations that are present before any analysis takes place, depending on the objective configuration we may ignore these.
DERMS Solution in Progress
DERMS is in the process of analyzing the network to come up with steps for the configured objective.
DERMS Solution Generated with Suspect SCADA
DERMS has generated a solution, but it was conducted in an area with SCADA measurements that are "Suspect"; manual
intervention is required if in automatic mode.
DERMS Event Canceled due to Network Changes
DERMS event has been cancelled due to network changes (e.g., topology, significant voltage change or load change). A new event will be created to replace the old event that was cancelled.
DERMS Event Canceled due to Forecast Expiration
The DERMS event has been canceled due to its schedule expiring. For example, if we have a DERMS event that covers 12/12/25 from 12:00AM to 12/13/25 12:00AM and we now reach 12/13/25 12:00 its now time to cancel the event as its no longer relevant and will likely have been replaced by a plan for the next 24 hours.
DERMS Event Canceled due to Update
The DERMS event has been canceled since a newer version has been created to replace it.
DERMS Plan Execution Scheduled
DERMS is setup for Automatic execution, or a user has manual initiated execution of the switching plan. The event is now in queue to start automatic execution. For example, a plan may cover 12am – 12am the following day but the plan may not have steps until the middle the 24-hour period. Until the execution reaches the first steps it will sit in the scheduled state. As soon as the first steps are executed it will transition to an “Executing” state.
DERMS No Steps Found
During the DERMS analysis no steps for were found.
DERMS No Control Found
During the DERMS analysis no controllable DER devices were available for the selected DERMS objective.
DERMS Event Manually Canceled
The DERMS event was manually canceled by an operator.
 
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.
• A submitted Grid DERMS Event created in Flex Operations with Run Daily? selected.
Note: When one or more Flex Operations UI-based scheduled Grid DERMS Events exist, NMS uses those scheduled events instead of the SRS-based Grid DERMS schedule.
• 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.