An energy aggregation program brings together resources that may have different owners, installers, equipment and operating priorities. The challenge is making them manageable as a fleet without losing the context of each individual site.
aDERMS is Serious Controls’ Aggregator DERMS offering. It organizes partner resources, sites and devices within a shared aggregation environment. This guide explains the preparation behind that operating model and the questions to resolve before scaling it.
What does an energy aggregator do?
An aggregator brings multiple distributed resources together for a defined operating program. That can involve solar, batteries, flexible building loads or charging equipment. The Department of Energy’s VPP overview describes the broader concept of coordinating distributed resources as an aggregation.
Aggregation is more than adding the ratings on equipment labels. The useful fleet is the set of resources that are available, authorized and able to respond at the required time.
Start with the partner-to-device hierarchy
Use a consistent structure before adding large numbers of assets:
- Partner: the installer, vendor or organization responsible for a group of resources.
- Site: the physical location, customer requirements and service contacts.
- Device: the equipment identity, connection and supported measurements or controls.
- Operating group: the resources assigned to a specific objective or program.
Keep ownership separate from operating groups. A site might remain associated with the same installer while its participation changes. Stable identifiers make those changes easier to track without losing history.
Five questions to answer during onboarding
1. Who has authorized participation?
Record the responsible organization, the approved scope of control and the process for changing participation. Agree on how a customer can request an override and who handles the request. A working device connection is not a substitute for authorization.
2. Which measurements are trustworthy?
Check units, timestamps and the meaning of each reading. Confirm whether a power value describes the entire site, a battery or one circuit. A consistent sign convention matters: importing and exporting must mean the same thing across the fleet.
3. What can each resource actually do?
Document supported instructions and site limits. Include the battery reserve that must remain available, charging deadlines and equipment operating windows. Avoid treating nameplate capacity as an unconditional commitment.
4. What happens when connectivity fails?
Define when data becomes stale, how unavailable resources leave a plan, and which local behavior continues. Test the recovery process as well as the failure. Operators need to know whether a reconnected device has resumed its expected state.
5. How will you confirm delivery?
Keep the instruction, acknowledgment and measured response distinct. An accepted request shows that a system received an instruction; it does not prove the physical result. Decide which measurements and time windows will support review.
An illustrative fleet-readiness check
Suppose a pilot contains twelve sites. Two have lost communications and three have opted out of the current operating window. A dashboard showing “twelve enrolled sites” is accurate but insufficient for planning.
The operator should be able to distinguish enrollment from current eligibility, then review the constraints on the remaining sites. This is a planning example, not a Serious Controls deployment result or a commitment of available capacity.
How does FERC Order 2222 fit in?
FERC Order 2222 addresses barriers to DER aggregation participation in the wholesale markets operated by regional transmission organizations and independent system operators. FERC’s explainer also describes the aggregator’s role as the direct market participant. It does not mean every resource can participate in every market immediately. Review the applicable market rules, implementation status and local requirements for your project. Read the FERC explainer.
Software selection, program enrollment and commercial eligibility are separate decisions. Resolve all three before promising a customer a participation outcome.
Choose a pilot that tests the difficult cases
Include more than the easiest devices. A useful pilot covers representative equipment, an offline resource, an override and a recovery after interruption. Assign an owner to each exception and agree on the evidence needed to accept the integration.
aDERMS focuses on organizing partner resources and fleet visibility within the Serious Controls Federated DERMS architecture. For the wider architecture, read what DERMS does. When you are ready to scope a pilot, bring your site and equipment list to our team.
