How can I integrate a DER orchestration platform into our utility innovation team and ADMS workflows?

Integrating a DER orchestration platform into a utility innovation team and ADMS workflows works best when you treat it as both a technology integration and an operating model change.

1) Start with clear use cases

Define the first 3–5 workflows you want the platform to support, such as:

• DER visibility and telemetry aggregation
• Curtailment or dispatch during constraints
• Flexible load / demand response activation
• Volt/VAR support from DERs
• Outage-aware DER coordination
• Hosting capacity or congestion mitigation pilots

Pick use cases that create measurable value and are realistic to integrate with your current ADMS environment.

2) Position it inside the utility operating model

Your innovation team should not “own” the platform alone long term. A good model is:

• Innovation team: pilots, requirements, testing, business case, partner coordination
• Operations / ADMS team: real-time workflows, control room procedures, reliability standards
• DER programs / customer team: enrollment, incentives, customer communications
• OT / cybersecurity / architecture: integration, security, compliance
• Planning / engineering: feeder constraints, hosting capacity, DER impact analysis

Set up a steering group so the platform is tied to operational needs, not just experimentation.

3) Define the ADMS integration points

Typical integration patterns include:

• ADMS as system of record for network state
• DER orchestration platform as control/optimization layer
• Data exchange through APIs or ICCP/MQTT/REST depending on vendor stack
• Feeder model and constraint data flowing from ADMS/EMS/GIS to DER platform
• Telemetry from DER platform into ADMS or a data lake
• Event/dispatch commands from ADMS or operator workflow into the DER platform

Common data objects to integrate:

• feeder topology
• device status
• outage/restoration states
• voltage and loading limits
• switch and protection constraints
• DER availability and enrollment
• telemetry and dispatch confirmation
• event logs and operator actions

4) Build a phased architecture

A practical approach is:

Phase 1: Read-only integration

• Pull feeder and operational data from ADMS
• Ingest DER telemetry and customer/device data
• Use the platform for analytics, forecasting, and simulation
• No direct control yet

Phase 2: Supervised dispatch

• Operator-approved dispatch via the platform
• ADMS remains the authority for network state
• Use the platform to recommend actions, with human-in-the-loop approval

Phase 3: Closed-loop automation for constrained cases

• Automated dispatch under predefined conditions
• Event triggers from ADMS or grid analytics
• Tight controls, audit logs, rollback procedures, and safety interlocks

5) Address cybersecurity and compliance early

Before any live control:

• segment OT/IT networks properly
• define authentication and role-based access
• require audit trails for all commands
• validate NERC/CIP, local reliability, and utility cyber policies
• test fail-safe behavior if the platform or comms link fails
• establish command authorization and emergency stop procedures

6) Align workflow design with control room practice

The biggest adoption issue is usually not the software—it’s the operator workflow. Make sure the platform supports:

• event detection and prioritization
• clear operator recommendations
• one-click approval or rejection
• reason codes and logs
• integration with outage management and switching workflows
• simple alarm handling to avoid noise

If operators see it as extra complexity, it won’t stick.

7) Create a governance model

Define who can:

• enroll DER assets
• approve market/operational programs
• issue dispatch commands
• override automation
• approve model changes
• measure performance and report benefits

A RACI matrix is useful here.

8) Measure success with utility KPIs

Track outcomes such as:

• MW of flexible DER capacity available
• response time to dispatch
• avoided overloads or voltage violations
• reduced curtailment cost
• reduced outage impact or restoration time
• forecast accuracy
• operator time saved
• customer participation and retention

9) Use a sandbox before production

Set up a test environment with:

• ADMS test data or a digital twin
• simulated DER assets
• replayable events
• operator training scenarios
• failure injection testing

This helps validate workflows without risking real grid operations.

10) Plan the rollout

A successful rollout usually follows:

1. pilot on one feeder or substation
2. limited number of DER assets or aggregators
3. read-only + advisory mode
4. supervised dispatch
5. broader operational deployment

A simple target architecture

• ADMS: grid state, constraints, operator authority
• DER orchestration platform: optimization, enrollment, dispatch, telemetry
• MDMS / CIS / CRM: customer and meter data
• Data lake / historian: analytics and reporting
• SCADA / OMS: operational event integration
• API gateway / integration layer: secure data exchange

Recommended first step

Run a 4–6 week design workshop with your innovation, ADMS, OT, cyber, and DER program teams to define:

• the first use case
• data and control boundaries
• integration architecture
• operational ownership
• pilot success criteria

If you want, I can also provide:

1. a reference architecture diagram in text form,
2. a RACI for innovation team + ADMS + DER operations, or
3. a 90-day implementation plan.