Edge Virtual Power Plants
An Edge Virtual Power Plant (eVPP) is a Grid DERMS object that represents an aggregation of Edge DERMS devices and their managed downstream load. This eVPP is distinct from the transmission-operator type of Virtual Power Plant that aggregates Grid DERMS devices.
An eVPP can use Map scope or Control Zone scope. A Map eVPP is anchored to a supported electrical branch. Nested containment allows an upstream Map eVPP to include a child load pocket; Exclusive containment prevents that inclusion. A Control Zone eVPP has no map anchor or map symbol. With no child eVPPs, it manages all eligible feeder zones beneath its selected control zone. With direct child eVPPs, it manages only the selected descendant zone scopes.
A Control Zone hierarchy supports one parent/child level. Child scopes in the same hierarchy cannot overlap or contain one another. Separate parent eVPPs can use the same control zone with different or overlapping child selections. Allocation Topology, either Nominal or As-switched, determines eligible loads within each solved source.
Creating and Managing Edge Virtual Power Plants
To create a Map eVPP, select a supported electrical branch on the Flex Operations Map and choose Create edgeVPP... from the selection-action menu. Enter a name and optional description, then specify Enabled, Approval, Containment, Allocation Topology, and Schedule Source.
To create a Control Zone eVPP, open the Virtual Power Plants (eVPP) tool and choose Create edgeVPP. Enter a name and optional description, set Enabled, Allocation Topology, and Schedule Source, and select the parent Control Zone. Optionally select non-overlapping descendant zones under Managed Child Zones. Leave this selection empty to manage all feeder zones beneath the parent zone. For File or REST schedules, supply an External ID. Use Add Schedule to enter Manual intervals on the parent when the parent will own the schedule; otherwise leave its schedule empty so schedules can be maintained on its children. Select Save to create the root and any selected child eVPPs.
The scope, selected control zone, parent relationship, map anchor where applicable, External ID, and Schedule Source cannot be changed after creation.
Use the Virtual Power Plants (eVPP) tool to create and review eVPPs and select Edit, Details, Schedule, Approve, Show on Map, Delete, or Refresh. Expand a parent row to display its children. Scope distinguishes Map from Control Zone, and Anchor / Control Zone identifies the map anchor or selected control zone. Schedules, Earliest Start, Latest End, Scheduled Energy Impact (MWh), and Scheduled Reactive Energy Impact (MVArh) summarize the eVPP's own schedule, or its children's schedules when the parent has no schedule.
Details opens the Grid DER Details Overview tab and Schedule opens its Schedule tab. Approve is available for Pending roots; children display Inherited approval and follow the parent's enabled state and approval. Show on Map is available only for Map eVPPs. Deleting a parent also deletes its child definitions and schedules.
For information about the Overview and Schedule tabs, see Understanding the Grid DER Details View under Using the Grid DERMS Dashboard in Flex Operations in this chapter.
Populating eVPP Schedules
Schedule Source determines how the complete schedule is populated:
• Manual: Maintain one or more intervals in Flex with Add Schedule and Delete Schedule.
• File: Supply an authoritative CSV or JSON schedule snapshot through the DERMS Adapter. The eVPP must be pre-provisioned with File as its Schedule Source and an External ID. See the Oracle Utilities Network Management System Adapters Guide for formats and processing details.
• REST: Supply an authoritative schedule snapshot through the Grid DERMS VPP schedule-ingest REST service. The eVPP must be pre-provisioned with REST as its Schedule Source and an External ID.
File and REST schedules are read-only in Flex Operations. A changed external snapshot replaces the eVPP's complete schedule and changes its approval state to Pending; an unchanged replay preserves its approval state.
For a Control Zone hierarchy, schedules belong either to the parent or to its children, never both. A parent with its own schedule allocates that schedule across its managed scope; a parent with child-owned schedules shows their combined schedule and impact. To change schedule ownership, first remove the existing schedules from the current owner or owners. Manual intervals can be maintained with Add Schedule and Delete Schedule; File and REST intervals remain read-only in Flex Operations.
Approve the parent to approve the hierarchy. Children cannot be approved independently. Changes to a child definition or schedule return the parent to Pending and require approval of the updated hierarchy. An unchanged external schedule replay preserves approval.
Each schedule interval has a start time, end time, MW reduction, optional MVAr reduction, and optional informational price in dollars per MW. Intervals are active from the start time up to, but not including, the end time. Duplicate and overlapping intervals are retained and add together. Positive reduction values reduce managed load; negative values increase managed load. A reduction is allocated proportionally across available active-phase load and is limited so final load does not become negative.
 
Using eVPPs in Analysis
Enabled Pending and Approved eVPPs participate in explicit study analyses. Only Approved eVPPs participate in true real-time, automatic hourly and daily Feeder Load Management forecasts, and the real-time emulator. The Edge DERMS nominal-kVA forecast remains an unadjusted baseline because Edge DERMS applies its planned reduction separately.
A Control Zone schedule specifies one MW/MVAr reduction for its managed scope. When that scope spans independently solved sources, each source receives a proportional share based on the complete nominal feeder load in the zone; the full reduction is not repeated for every feeder or source. Within each source, Allocation Topology still determines eligible loads: Nominal uses nominal connectivity and As-switched uses current switched connectivity. Selecting As-switched does not change the nominal basis used to divide the schedule among sources. Positive reduction is limited so final managed load cannot become negative.