Begin with well-defined installations
A collection of homes is only useful as a portfolio when you know what each installation can contribute. Identify connected batteries, PV, chargers and controllable thermal loads, then document available power and operating boundaries. Treat every home as a complete installation with its own connection and customer needs. This keeps the portfolio discussion grounded in usable flexibility rather than simply the number of devices on a map.
Agree how the portfolio reaches the market
SmartgridX supports several connection routes and market strategies. Your project might work with an aggregator, supplier or another authorised market party. Select services that fit the assets and country, and agree commercial responsibilities before activation. Establish eligibility for the chosen market through the agreed technical and commercial onboarding process. Explain to customers which service they are joining, what is controlled and which commitments are part of the agreement.
Preserve the local boundaries
Portfolio commands must remain within equipment protections and agreed site limits. Define setpoints, battery boundaries, signal timeouts and fallback behaviour before external dispatch begins. Use feedback measurements to check requested versus actual behaviour. For installers, that makes the local configuration part of the portfolio's foundation: accurate meter data, supported interfaces and a known response when communication changes. Monitor individual installations as well as the aggregate so an exception can be traced back to its source.
Preparing a group of residential installations
An installer wants to connect a group of homes with batteries and PV to an agreed aggregator service. Start by checking each home's supported devices, grid limits and customer agreement. Eniris and the market partner can then define the connection and control scope. Test a small representative group, including fallback behaviour, before expanding. The remaining homes are added against the same documented requirements.
Before you activate
- List assets, firmware, available power and customer constraints.
- Agree the market partner, service and contractual roles.
- Confirm connection route, setpoints and fallback.
- Validate feedback and representative sites before expansion.
Technical documentation
Ready to configure this feature? Find the precise settings, supported connections and installation instructions in our documentation.