EMS requirements
What an energy management system has to provide so Furo can operate a battery with it — learned from the first integrations.
Furo does not build its own EMS. The optimization runs in the cloud, the control on site stays with the EMS or power plant controller that runs the asset anyway. For this to work together, the EMS has to provide a few things. Every point on this page has already delayed a commissioning by weeks. Hand the list to the manufacturer before you order an EMS — and have every point shown to you at the interface, not just promised.
Control via limits
Furo sends a set of targets every 15 minutes. The storage is controlled via limits, not via a fixed operating mode:
- maximum charge power and maximum discharge power of the storage (kW)
- maximum grid import and maximum grid export at the grid connection point (kW), separately — not one symmetric value for both directions
- optionally a setpoint for the storage
Within these limits the EMS keeps controlling locally, normally self-consumption. Three of the four limits are enough; what is missing, Furo covers through the others.
Measurements back
The EMS delivers at least every 15 minutes, better more often:
- grid import and export at the grid connection point, from one measurement at the handover point
- PV generation
- power of the storage — measured, not computed from the difference of other values
- state of charge (SOC)
- feedback on which mode and which limits are currently active
All power values as the average over the interval, not as an instantaneous value at the end of the interval. The demand charge is billed on the average; an instantaneous value produces a wrong peak and thus a wrong optimization. Timestamps with timezone.
One interface per product, not per asset
A parameter — for example the upper limit of charge power — has the same name, the same unit, the same sign and the same meaning on every asset. Regardless of which storage, inverter or power plant controller sits behind it. Only then is the integration built once and used on all projects.
Names and signs are documented and stay stable. If the manufacturer changes them, they announce it, version the interface and keep the old names running for a transition period. Otherwise a renaming "for internal harmonization" or a second project with flipped signs means: rebuild and retest the integration.
Limits always apply — locally and in real time
Grid connection capacity, export limit, SOC limits and temperature derating are kept by the EMS, within seconds. Furo plans in quarter hours and cannot take this over. A limit overrides any target from Furo.
At the export limit, first discharge the storage less, then curtail the PV — not only the PV. A storage that runs over the export limit on a setpoint because the limit only acts on the PV is a defect of the interface. Fast local functions such as active power limitation, zero feed-in or self-consumption control stay on site.
Defined behaviour without a schedule
If the schedule runs out, a value is missing or the connection drops, the EMS falls back to its safe default mode: self-consumption or peak shaving. Not: charge the storage at full power. Not: freeze the last value.
This includes:
- a switch between external control by Furo and local control, with read-back of the active state
- a watchdog: after an agreed time without a valid target the EMS goes to default mode; who writes it is defined
- an agreed cadence at which the EMS adopts new values — every minute, not only at the next quarter hour. If it only adopts pushes at the slot start, a heartbeat runs into nothing and control falls back after minutes
Everything via the interface, nothing only in the dashboard
The reserve SOC for peak shaving, the import limit, the operating mode: whatever Furo has to change during operation is settable via the interface. A setting that exists only in the manufacturer's UI is of no use to Furo.
The EMS's own optimization or forecast can be switched off, otherwise two controllers work against each other.
Test environment before the first project
Before the first customer project Furo tests the interface: on a test device the manufacturer unlocks remotely, on a simulation, or on a device in the Furo office. A run takes a few days, because the serious errors do not show in the first hour: a storage oscillating between charging and discharging every few seconds, or an export protection with a swapped sign.
The interface already exists and is documented at that point. "Being built, three weeks" has turned into a quarter of a year without result more than once — without a finished interface there is no schedule for commissioning.
Outages are visible
The controller reports when it last transmitted. A device that delivers frozen values for hours or drops out briefly every day looks healthy locally and still delivers nothing to Furo. These gaps have to be visible on both sides.
Summary for the manufacturer
| Topic | Requirement |
|---|---|
| Control | limits for charge, discharge, grid import, grid export (separate); optional setpoint |
| Measurements | grid import and export at the connection point, PV, storage power measured, SOC; interval averages; echo of active limits |
| Interface | one product, one set of names, units, signs; stable and versioned |
| Limits | locally in real time, override targets; at the export limit storage first, then PV |
| Without schedule | safe default mode, switch with read-back, watchdog, adoption every minute |
| Settings | everything operationally relevant via the interface; own optimization switchable off |
| Test | test device or simulation, several days, before the first project |
| Operation | timestamp of the last transmission, outages visible |