JSW Energy's Pune site already had a battery: a legacy EMS and a first 5 MWh container. JSW then added a second 5 MWh container from a different maker. Each container came with its own BMS speaking its own protocol, and both had to sit behind the same 2.5 MVA PCS.
Ingro replaced the EMS, hardware and software. The new Ingro EMS reads both BMS protocols, works out the plant's state of charge weighted by each container's energy, and commands the single PCS as one 2.5 MW / 10 MWh plant. Either container can be taken out of service or brought back while the plant keeps running, and a container with a critical fault is isolated automatically. The legacy EMS stays on site as a backup.
A brownfield sitea legacy EMS and a first 5 MWh container were already installed and running
The second 5 MWh container came from a different maker, with a BMS speaking a different protocol
Both containers share one 2.5 MVA PCS, so they have to be controlled as one plant, not two
Maintenance on one container must not stop the whole plant
A fault in one container must be contained before it affects the other
What Ingro put in place, step by step.
Ingro replaced the legacy EMS with its own controller panel and software; the legacy EMS stays only as a backup
both containers' BMS are read through one common layer, so the controller sees one battery
the plant's SoC is calculated across the containers in service, weighted by each one's energy, with power limits combined
either container can be taken out for maintenance or brought back while the plant runs; the PCS ramps down before a DC contactor opens
a critical BMS fault takes that container out of service and opens its DC contactors, and the plant can restart on the healthy container
the EMS charges from spare grid headroom and discharges to hold the site's grid import at its cap
More of our energy storage and optimisation work.
Tell us about your site and we will show how the approach used on Two Containers, One Plant would apply to it.