Rooftop solar connection application
Application documents are read, transformer capacity and regulation checked, gaps reported the same day; the connection opinion belongs to the engineer.
Rooftop solar connection application is an agent scenario in the Energy & Utilities sector running on the web, email, api channels. Trigger: Rooftop solar connection application from the DSO portal. The Connection Supervisor coordinates 4 specialist agents (Document Agent, Grid Agent, Regulation Agent, Case Agent) across 4 systems (Connection Portal, GIS / Network Model, Regulation Vector Store (EPDK), E-mail); of 9 steps, 1 write to systems and 2 are checks or approvals. Outcome: Technical pre-assessment and gap list ready; connection opinion published with engineer approval. Approval rule: The connection opinion is always signed by a network planning engineer.
Rooftop solar connection application
- Application B-2026-31877: 48 kWp rooftop solar, commercial customer, 6 documents uploaded
- Documents read: single-line diagram valid, deed matches, building permit missing a page
- Transformer TR-2291: 400 kVA, peak load 71%, connected generation 96 kWp
- Hosting capacity sufficient: with 48 kWp total generation is 36% of transformer rating
- Regulation: same metering point as consumption, within contracted power limit → eligible
- Opinion draft: positive, conditional on protection settings and meter change; 1 missing document
- Connection opinion → network planning engineer reviewed and signed
- Application set to “conditionally positive”, opinion document attached
- Opinion and missing-document list e-mailed to the applicant; 15-day completion window
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Rooftop solar connection application from the DSO portal
Technical pre-assessment and gap list ready; connection opinion published with engineer approval
Agents
Connection Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Document Agent
Reads the single-line diagram, deed and permit
extract_documentclassify_documentcheck_completenessGrid Agent
Evaluates transformer and feeder capacity
get_transformer_loadget_connected_generationassess_hosting_capacityRegulation Agent
Checks against unlicensed-generation regulation
search_regulationcheck_eligibilitydraft_opinionCase Agent
Updates the application and informs the applicant
update_applicationsend_emailSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Connection Supervisor | Application B-2026-31877: 48 kWp rooftop solar, commercial customer, 6 documents uploaded | Connection Portal | 200 | — |
| 02 | reason | Document Agent | Documents read: single-line diagram valid, deed matches, building permit missing a page | — | 980 | 1,300 |
| 03 | tool | Grid Agent | Transformer TR-2291: 400 kVA, peak load 71%, connected generation 96 kWp | GIS / Network Model | 460 | — |
| 04 | reason | Grid Agent | Hosting capacity sufficient: with 48 kWp total generation is 36% of transformer rating | — | 700 | 760 |
| 05 | retrieve | Regulation Agent | Regulation: same metering point as consumption, within contracted power limit → eligible | Regulation Vector Store (EPDK) | 480 | 520 |
| 06 | verify | Regulation Agent | Opinion draft: positive, conditional on protection settings and meter change; 1 missing document | — | 620 | 640 |
| 07 | approval | Connection Supervisor | Connection opinion → network planning engineer reviewed and signed | — | 3,000 | — |
| 08 | write | Case Agent | Application set to “conditionally positive”, opinion document attached | Connection Portal | 440 | — |
| 09 | notify | Case Agent | Opinion and missing-document list e-mailed to the applicant; 15-day completion window | 240 | — |
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