Demand response event
Under grid stress eligible consumers are selected, the offer sent by channel, participation measured and settlement computed.
Demand response event is an agent scenario in the Energy & Utilities sector running on the api, app, whatsapp, batch channels. Trigger: Load-reduction call from the market operator or SCADA. The Demand Response Supervisor coordinates 3 specialist agents (Selection Agent, Offer Agent, Settlement Agent) across 4 systems (SCADA / DMS, Meter Data Management, Billing / Settlement, WhatsApp Business API); of 9 steps, 1 write to systems and 2 are checks or approvals. Outcome: Participants selected and informed for the target MW; realised reduction measured, settlement computed. Approval rule: Event > 10 MW → grid operator approval; settlement with an audit trail.
Demand response event
- Call: 12 MW reduction 17:00–19:00, region: Aegean industrial feeders
- Flexibility portfolio pulled: 214 sites, contracted potential 31 MW
- 63 sites selected by forecast and past participation; expected reduction 14.8 MW
- Event > 10 MW → grid operator approved the participant list
- WhatsApp and app notification to 63 sites: hours, target kW, tariff
- 57 accepts, 4 declines, 2 no reply in 20 minutes; committed 13.6 MW
- Post-event 15-minute interval data pulled; baseline computed
- Realised reduction 12.9 MW; 51 sites met commitment, 6 partial
- Payments computed and posted to settlement; event report attached to the SCADA record
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Load-reduction call from the market operator or SCADA
Participants selected and informed for the target MW; realised reduction measured, settlement computed
Agents
Demand Response Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Selection Agent
Selects consumers by flexibility potential
get_flex_portfolioforecast_reductionrank_participantsOffer Agent
Sends the offer by channel and collects responses
send_whatsappsend_pushcollect_responsesSettlement Agent
Measures reduction from meter data and computes payment
get_interval_datacompute_baselinecompute_settlementpost_settlementSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Demand Response Supervisor | Call: 12 MW reduction 17:00–19:00, region: Aegean industrial feeders | SCADA / DMS | 200 | — |
| 02 | tool | Selection Agent | Flexibility portfolio pulled: 214 sites, contracted potential 31 MW | Meter Data Management | 480 | — |
| 03 | reason | Selection Agent | 63 sites selected by forecast and past participation; expected reduction 14.8 MW | — | 820 | 1,100 |
| 04 | approval | Demand Response Supervisor | Event > 10 MW → grid operator approved the participant list | — | 2,400 | — |
| 05 | notify | Offer Agent | WhatsApp and app notification to 63 sites: hours, target kW, tariff | WhatsApp Business API | 300 | — |
| 06 | tool | Offer Agent | 57 accepts, 4 declines, 2 no reply in 20 minutes; committed 13.6 MW | WhatsApp Business API | 420 | — |
| 07 | tool | Settlement Agent | Post-event 15-minute interval data pulled; baseline computed | Meter Data Management | 520 | — |
| 08 | verify | Settlement Agent | Realised reduction 12.9 MW; 51 sites met commitment, 6 partial | — | 560 | 480 |
| 09 | write | Settlement Agent | Payments computed and posted to settlement; event report attached to the SCADA record | Billing / Settlement | 480 | — |
Utility customer assistant: bill, outage, consumption and instalments in one dialogue
The customer calls or writes; the high bill is explained, outage ETA given, meter data shown, an instalment plan set up.
Outage report handling
Reports are clustered by feeder, one OSS ticket is raised and everyone affected hears before the crew leaves.
Meter reading dispute
Customer sends a meter photo; the index is read by vision, the estimated bill fixed, big credits approved.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis