Frequently asked
Answers in plain English, not marketing copy.
What is ECC?
Energy Cloud Control (ECC) is an industrial IoT platform that connects Modbus TCP devices at energy infrastructure sites — battery storage, inverters, protection relays, circuit breakers — to a multi-tenant cloud dashboard. It is operated by EC Control s.r.o., a Czech company founded in 2025, and is in production at the SPL Energo site in Poustka.
Who is ECC for?
ECC is built for operators of sub-5 MW battery energy storage and photovoltaic sites in Central and Eastern Europe. Typical customers are independent power producers, energy cooperatives, and integrators that own or run distributed generation assets but do not want to build their own SCADA stack. It is not a replacement for utility-scale DERMS platforms such as AutoGrid, Stem, or Fluence IQ.
What hardware do I need to install ECC at my site?
A small edge gateway capable of running Docker on Linux (x86_64 or ARM64). Customers typically deploy on an Azure IoT Edge–certified industrial gateway such as the Advantech ICO-300, but any Docker-capable Linux host with a route to the Modbus network works. ECC does not sell hardware — you procure the gateway, we provide the container image.
How does ECC differ from building this myself?
Building an equivalent stack in-house typically costs €60–120k in engineering time and 6–12 months before first production use, plus ongoing maintenance of the cloud ingest pipeline, the multi-tenant access layer, the audit chain, and the device-twin update mechanism. ECC ships with all of that in place from day one for €5–10k per site per year.
How does ECC differ from Stem, AutoGrid, or Fluence IQ?
Those platforms target utility-scale assets (10+ MW) with utility-scale pricing. ECC targets the sub-5 MW segment where their fixed-cost base does not allow them to operate competitively. ECC is also Modbus-native and self-serve, where they typically require integration projects.
Is ECC secure enough for critical energy infrastructure?
ECC uses TLS-encrypted AMQP for all edge-to-cloud traffic, JWT authentication with HttpOnly cookies, account lockout after 5 failed logins, a SHA-256 hash-chain audit log on every mutation, and tenant-isolated multi-customer data access verified by automated tests. The platform is designed to meet the NIS2 directive’s logging and incident-response obligations. A security disclosure path is published at /.well-known/security.txt.
Where is my data stored?
Telemetry and configuration are stored in Azure Cosmos DB in the West Europe region (Netherlands). Each customer’s data is isolated by a tenant filter applied to every query at the API layer. Per-customer infrastructure (dedicated IoT Hub, dedicated Cosmos DB database) is available for customers with strict data-residency requirements.
Can ECC write commands to my devices?
Yes — Modbus function code 6 writes are supported, with per-operation RBAC, double-confirmation in the UI, rate limiting, and full audit logging. Write commands are server-validated against the device’s register map and rejected if the register is not whitelisted as writable. Common operations include power setpoints, start/stop, and circuit breaker control.
What happens if the internet connection at the site goes down?
The edge module keeps polling the local Modbus devices and buffers telemetry to a local SQLite database (72-hour retention by default). When connectivity returns the buffer is flushed automatically. Alarm detection runs locally and is queued for delivery as soon as the connection is restored.
What does ECC cost?
Pricing is not published on the website. Every engagement begins with a thirty-minute walkthrough against the live Poustka deployment, after which we send a tailored quote based on site capacity, device count, and which service tier (monitoring, predictive, dispatch) fits the asset. Book a walkthrough at https://eccontrol.org/demo.
How long does it take to onboard a new site?
Typically 1–3 weeks end-to-end. Week 1: edge gateway installation and Modbus connectivity verification. Week 2: register map authoring and configuration push via Azure IoT Hub Device Twin. Week 3: dashboard customisation, alarm threshold tuning, and user training. Existing supported device types (Sinexcel PCS, CATL BMS, ABB REF615, ABB Emax 2) can be brought online inside a single day.
Is ECC open source?
No — ECC is proprietary software developed by EC Control s.r.o. Customers can self-host the dashboard if required and the device-twin configuration format is documented and inspectable. The source code is hosted on a private Gitea instance with mirror access available to enterprise customers under NDA.
What languages does the platform support?
The dashboard and marketing site are available in English and Czech. Other CEE languages (Polish, Slovak, German) are on the roadmap pending customer demand.
How do I get started?
Email [email protected] with a one-paragraph description of your site (number of devices, types, location). We respond within one business day and typically book a 30-minute remote walkthrough of the dashboard, then a paid pilot of €1k/month for three months (fully credited toward the first annual subscription if you convert).