grd-sgr · SmartGridready test bench

EMS target

Only drive an installation you own or are authorised to test.

I understand: these commands drive the real installation.

Automatic mode (GRD event generator)

The simulator sends a sequence of SGCP commands on its own.

Scenario

Step (s) Loop

Quick GRD commands

Custom command

Command

Data point Mode

Connect to the EMS to get started.

The EMS under test

Load the EMS's EID, its SmartGridready product description. Its configuration values become the form below. Credentials stay with this tool and never come back to the browser: a secret field left blank keeps the value given before.

EID of the EMS

Evidence API — optional; needed for E4 and the console's journal

Base URL Header name Header value

Reference meter — optional; F1 and F4 judge the effect against it

No independent meter: use the EMS's own Metering point (the report will say the reference is not independent) EID of the meter

Point giving the grid power in kW, positive for import

Compliance tests

The tool acts as the grid operator's flexibility manager and drives the EMS through its own EID. Each run produces an audit report: scope, method, every verdict with its clause and evidence, and what the run cannot prove.

What to run S — Declarations. The EID against the SmartGridready schema and profile library. P — Protocol, read-only. Connection, typed reads, FlexMgmt schemas. E — Traceability. Every command found in the EMS's evidence journal (needs the evidence API and writes).

Writes to the installation Protocol writes (P3, P4, P6, P7). Valid, invalid and unauthenticated commands, then the state found is restored. Functional tests (F1, F4). Each mode is held and its effect judged against the reference meter.

Hold per mode, seconds Declared reaction time, seconds

I understand: these tests command the real installation, and each ends by writing the released state.

Runs of this session

Dynamic tariffs (T1–T6)

The tool serves the VSE dynamic-tariff API, v1 and v2, scenario after scenario, while the EMS polls it; then it judges what the EMS asked and what it journalled. The EMS must reach this machine: start grd-sgr ui --expose if it runs elsewhere.

Scenarios

Seconds per scenario

Grid operator console

Talk to the EMS as a grid operator would: through its EID, with the official CommHandler. Read its data points, send a mode or a restriction, and watch the EMS journal what it did.

every 5 s

Data points

Profile	Point	Value	Unit

Send a command

I understand: a write commands the real installation.

Commands sent

Evidence journal

#	Time (EMS)	Kind	Subject	Result