> For the complete documentation index, see [llms.txt](https://renewables.docs.helinplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://renewables.docs.helinplatform.com/sgm-product-docs/guides/configuration-examples.md).
# Configuration examples
Common site layouts for SGM, with the right control mode and key considerations for each.
These examples cover the most common site layouts customers deploy with SGM. Each one describes what assets are involved, which control mode applies, and what the key considerations are.
For a full explanation of Asset Control vs Site Control, see the respective pages. For energy concepts referenced below (CBC, SDE, UCL, limited/unlimited grid), see [Energy concepts](/sgm-product-docs/concepts/energy-concepts.md).
***
## Asset Control configurations
### 1. PV + Unlimited grid (basic)
The simplest possible configuration. A single PV system on an unlimited grid connection, controlled with a direct static setpoint.
```mermaid
flowchart LR
API[Your System] -->|setpoint| SGM[SGM\nAsset Control]
SGM -->|curtailment command| PV[PV Inverter]
PV --> UCL[Unlimited\nGrid Connection]
style UCL fill:#dcfce7,stroke:#22c55e,color:#000
```
**What SGM does:** Passes the setpoint directly to the inverter, capped at the configured min/max limits. No meter feedback required.
**Use when:** You need remote curtailment on a simple site with no consumption to compensate for and no grid limit constraint.
***
### 2. PV + Unlimited grid + Grid limit (CBC, Physical, or SDE)
The same setup as above, with an active grid feed-in limit. This requires Dynamic Power Control, a grid meter is added to measure actual feed-in and the Gateway adjusts the PV setpoint continuously to stay within the limit.
```mermaid
flowchart LR
API[Your System] -->|limit setpoint| SGM[SGM\nDynamic Control]
Meter[Grid Meter] -->|actual feed-in| SGM
SGM -->|adjusted setpoint| PV[PV Inverter]
PV --> Grid[Grid\nwith feed-in limit]
style Grid fill:#fef9c3,stroke:#eab308,color:#000
style Meter fill:#f3e8ff,stroke:#a855f7,color:#000
```
**What SGM does:** Continuously adjusts PV output based on real grid meter readings to keep feed-in at or below the limit, accounting for any local consumption on site.
**Use when:** You have a CBC contract, a physical grid cap, or an SDE subsidy that limits how much you can feed into the grid.
***
### 3. PV + Unlimited grid + Grid limit + Uncontrolled local PV (MLOEA)
A more complex variant where a second PV system at the site is *not* controlled by SGM (e.g. it has its own logger and is not integrated). The Dynamic Power Control unit monitors the combined feed-in at the grid connection and compensates by adjusting only the *controlled* PV system.
{% hint style="warning" %}
**Important constraint:** The uncontrolled PV system cannot be scaled down by SGM. If it produces enough to push the site over the grid limit on its own, Asset Control cannot solve this, Site Control is required instead.
{% endhint %}
**Use when:** You have a mixed installation where part of the PV fleet is outside SGM's control, and the uncontrolled portion alone never exceeds the grid limit.
***
### 4. Multiple branches (multi-DPC)
For sites with multiple independent grid connection points (branches), each branch can have its own Dynamic Power Control unit with its own meter.
```mermaid
flowchart TB
API[Your System] --> SGM[SGM Asset Control]
SGM --> DPC1[DPC Unit 1\nPV + Meter]
SGM --> DPC2[DPC Unit 2\nPV + Meter]
DPC1 --> G1[Branch 1\ngrid connection]
DPC2 --> G2[Branch 2\ngrid connection]
style G1 fill:#fef9c3,stroke:#eab308,color:#000
style G2 fill:#fef9c3,stroke:#eab308,color:#000
```
{% hint style="warning" %}
**Important constraint:** With multiple branches, SGM can only enforce limits at the branch level, not at the total site level. If you have an SDE or CBC contract that specifies a total site cap (not per branch), you need to divide that limit across branches and set each accordingly. For site-level limit enforcement across branches, Site Control is required.
{% endhint %}
***
## Site Control configurations
### 5. PV + BESS + EV + Unlimited grid
The most common Site Control setup. Multiple controllable asset types, PV, battery, and EV chargers, all managed together within the site's global limits.
```mermaid
flowchart LR
API[Your System] -->|setpoints| SGM[SGM\nSite Control]
SGM --> PV[PV Inverters]
SGM --> BESS[Battery\nBESS]
SGM --> EV[EV Chargers]
PV & BESS & EV --> UCL[Unlimited\nGrid Connection]
Meter[Site Meter] -->|monitoring| SGM
style UCL fill:#dcfce7,stroke:#22c55e,color:#000
style Meter fill:#f3e8ff,stroke:#a855f7,color:#000
```
**What SGM does:** Enforces global site limits across all assets simultaneously. EV load balancing distributes available current across chargers. BESS can be used for self-consumption optimisation. PV is curtailed if total production approaches grid or SDE limits.
**Use when:** You need coordinated control of multiple asset types on a site with an unlimited grid connection. This is the standard configuration for most commercial and industrial sites with on-site generation, storage, and EV charging.
***
## Choosing the right configuration
| Site description | Recommended configuration |
| ------------------------------------------ | --------------------------------------------- |
| Single PV, no grid limit | Config 1, Static Asset Control |
| Single PV, with CBC / SDE / physical limit | Config 2, Dynamic Asset Control |
| Multiple PV systems, some uncontrolled | Config 3, Dynamic Asset Control with MLOEA |
| Multiple grid connection branches | Config 4, Multi-branch Asset Control |
| PV + BESS and/or EV, any grid type | Config 5, Site Control |
| Limited grid connection (any asset mix) | Site Control with BESS load-shifting strategy |
## Relevant pages
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://renewables.docs.helinplatform.com/sgm-product-docs/guides/configuration-examples.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.