Begin your smart grid journey by demystifying DERMS

You’re the one who’ll turn a strategic interest in DERMS into a program with a scope, a budget and a timeline leadership will hold you to. The questions now are foundational: what a DERMS initiative involves, which teams need to be at the table, and what you can deliver in the near term from existing business cases.

Frame the effort realistically before you’re asked to commit to dates, so you can plan a modular, phased rollout rather than an all-at-once build.

Technical depth

• Inventory the DERs on your system and who owns them: smart thermostats, batteries, EV chargers, C&I load and solar, held by customers, aggregators or the utility.
• Tie each near-term business case to a program: peak reduction, capacity deferral, wholesale demand response or voltage support.
• List the systems a DERMS exchanges data with: the CIS for customers and enrollment, the MDM for meter data, the ADMS and GIS for the network. Decide which day one needs and which can follow.
• Phase it: one program on the platform first, then each new program on the same record, rather than a new tool per program.

Every new system deserves a fair question from the people who run the grid in real time: does this make the job easier, or just add another screen to watch?

A DERMS is designed to aggregate and dispatch distributed resources so they behave as something you can manage, rather than thousands of unpredictable endpoints acting on their own. The intent is more visibility and control, not more noise.

Technical depth

• Aggregation: thousands of endpoints grouped by program, feeder or substation, so they dispatch as one resource.
• Telemetry: device status, availability and response before, during and after an event.
• The network view: DER locations on the GIS topology, beside the ADMS data operators already use.
• Field communication: devices that speak IEEE 2030.5, DNP3 or Modbus answer through one platform.

Your team is figuring out whether distributed resources can become a revenue stream: can aggregated DERs participate in wholesale markets, and what does a virtual power plant bid into, and where?

Before you can model any of that, you need a clear picture of how a DERMS turns thousands of small, scattered resources into a single dispatchable, market-eligible asset.

Technical depth

• The chain from resource to revenue: enrollment, availability forecast, offer, dispatch, measurement against a baseline, settlement.
• What a market asks of an aggregation: registration, size, telemetry and proof of performance, set by each ISO or RTO.
• Where value comes from: capacity, energy and, where the rules allow, ancillary services.

Distributed energy resources are growing on your system whether or not you have a plan for them. A DERMS is how a utility turns that growth from a reliability liability into managed, even monetizable, assets.

The case is strategic: where DERMS fits in grid modernization, what problem it solves, and why timing matters with rising DER penetration and near-term load growth.

Technical depth

• Load is rising with data centers, industrial manufacturing and electrification; flexible DER capacity is the fastest resource to put to work.
• Peak reduction from resources already on the system can defer capacity and wires investment.
• Modularity limits risk: start with one program and grow on the same platform. OATI built the first DERMS in 2009; more than 250 utilities run their DERMS on OATI.