Control and data

VPP optimisation must stay within the technical boundaries of each asset, site, and grid connection. Define the control contract before market activation so that every command has an unambiguous meaning and a safe fallback.

Supported control patterns

Depending on the connected equipment and project setup, SmartgridX VPP can support:

• real-time import and export limits communicated over MQTT;
• control against quarter-hourly average set-points where enabled;
• automatic control modes that react to incoming grid signals;
• pre-configured fallback states when communication is interrupted; and
• handling of exceptional import or export limit signals.

Define the command interface

Document the following for every controllable device or group:

• the device or group identifier;
• the agreed power and set-point convention, including sign and unit;
• command frequency and required response time;
• minimum and maximum allowed values;
• state-of-charge boundaries for batteries;
• timeout detection and the fallback behaviour after signal loss; and
• the party responsible for issuing, validating, and stopping commands.

Feedback and historical data

The control loop should expose enough data to confirm whether a command was accepted and executed. Agree on:

• required real-time measurements and their update frequency;
• historical measurements and retention requirements;
• units, timestamps, and time zone conventions;
• command acknowledgement and actual-versus-requested power;
• availability and communication-health signals; and
• KPIs required per battery, site, and portfolio.

Safety hierarchy

Local protection settings, device limits, and grid-connection constraints remain leading. A VPP command must never override equipment protection or an agreed site limit.