Example Aggregator Example Gridcsip-aus-v1.2-teachingVirtual clock · 2026-10-13 00:00:00 UTC Side-by-side needs a screen at least 1440px wide. Single View remains fully available.
DISCOVER THE INTERACTIONS
Follow the links.
Understand the protocol.
Act as an Aggregator Client and explore a fictional Utility Server, one request at a time. Compare readable resources with the XML and HTTP exchange behind them.
How to read an operation and response
One operation, one responseIllustrative discovery example, not your current practice1. Operation / request
Aggregator → Utility Server
GET https://utility.example/edev?s=1&l=1Read one page of the discovered EndDeviceList. No request body.
↓
2. Response
Status & HTTP headers200 OK
Content-Type: application/sep+xml
XML body / resource attributesEndDeviceList · all=6 · results=1
Included itemDemo Site 01 · /edev/1
Links within that itemDERListLink → /edev/1/der
FunctionSetAssignmentsListLink → /edev/1/fsa
Expanding an included item reads the same response. Following its returned link sends a new GET. A link is an address, not the linked resource’s contents or permission to write.
01Connect & discover
See a conceptual TLS exchange, then send a separate GET to DeviceCapability.
02Follow returned resources
Discover EndDevices, connection points, DERs and both assignment groupings.
03Inspect every exchange
Human View, illustrative XML and HTTP Details share one response snapshot.
Fictional data. Real learning.https://utility.example is simulated, never a real network destination. Do not enter real operational information. This independent demonstrator is not a certified implementation or compliance tool.