Edge-native control
Control logic that runs on-site (at the edge) rather than in the cloud - required for fast market participation and for maintaining backup readiness without cloud dependency.
Edge-native control means the control logic - the software that decides when the battery charges, discharges, and participates in markets - runs on-site, on hardware installed next to the battery. Cloud services may be used for monitoring, reporting, and long-term optimisation, but the real-time dispatch decisions are made locally.
This matters for two reasons:
Latency. Fast ancillary services products (FCAS Contingency, Reserve services) require response within 6 seconds - some products under 1 second. A cloud round-trip is 200-800ms in the best case; if the network is degraded, dispatch windows are missed and revenue is lost.
Resilience. A battery whose control depends on cloud connectivity is a battery whose backup guarantee depends on cloud connectivity. That's not acceptable for critical-infrastructure sites. Edge-native control ensures the battery can protect the site even if internet is down.
Amplicity's dispatch layer is fully edge-native: real-time decisions run on-site, with cloud used only for monitoring and long-term learning.