Connection architecture

SmartgridX VPP can combine assets that use different connection routes. Select the route per site based on the existing infrastructure, the required response, and whether local control is needed.

Connection routes

A portfolio can use more than one route. For example, one group of sites can use local SmartgridOne controllers while another group connects through a manufacturer's platform or a third-party EMS.

How to choose

Consider the following for every asset or site:

• whether a compatible controller or EMS is already installed;
• whether commands must continue locally during a cloud interruption;
• which protocols or APIs are available;
• the required command frequency and response time;
• network ownership, firewall restrictions, and security requirements; and
• who remains responsible for the local controls and equipment limits.

Connection details to collect

• Connection route: SmartgridOne, customer EMS, VPP API, or manufacturer platform
• Controller serial number when SmartgridOne is already installed
• Interface or protocol: for example Modbus TCP/RTU, SunSpec, API, or MQTT
• Network setup: internet route, firewall restrictions, and responsible network contact
• MQTT setup: availability of ports 1883 or 8883, plus the required TLS and authentication method
• Technical documentation: device protocol or register documentation for custom integrations

When a device needs a custom integration, submit the specifications through the Eniris integration request form.