Suppose a battery energy storage system is asked to discharge at 50 kW, but the actual output settles at 35 kW. Nothing is necessarily wrong. The difference may simply mean that 50 kW is what the site wants, while 35 kW is what the battery and power-conversion equipment can support at that moment. This gap is a useful way to understand PCS, BMS, and EMS as parts of the same operating process.Three roles, different kinds of authority
The EMS usually sits closest to the site’s operating objective. It may decide that the battery should discharge because load has increased, solar output has fallen, or another operating instruction calls for stored energy to be used. The immediate result may be simple: charge, discharge, or hold at a particular power level. Siemens Energy describes the EMS as the layer that manages overall BESS operation and dispatch, while the PCS performs power conversion and the BMS monitors and controls battery conditions. (siemens-energy.com)
The battery has its own operating condition. Cell voltages, temperatures and other measurements, together with estimated states such as SOC, affect how much charge or discharge it can support. Infineon lists SOC/SOH estimation alongside monitoring, balancing, fault detection and communication among core BMS functions for battery energy storage. (infineon.com) In managed systems, the BMS can communicate battery status along with limits on charge voltage, charge current and discharge current. Victron, for example, documents batteries that send these limits dynamically to the system controller as cell voltage, SOC or temperature changes. (victronenergy.com)
A battery limit therefore serves a different purpose from an EMS request. Suppose the EMS asks for 50 kW of discharge, while the current battery-side limits mean that only about 35 kW is available. The 35 kW figure sets the battery-side boundary under those conditions. If the site only needs 20 kW, there is no reason to discharge at 35 kW simply because the battery can. If the site wants 50 kW, the requested operating point has to be reduced to something the system can actually support.
Imagine the same control screen shows a 50 kW request, a 35 kW allowable value and a measured output of 34.7 kW. All three are expressed in kilowatts, yet they describe different things: intention, boundary and result. The unit alone is not enough. The label and source matter because a setpoint, a limit and an actual measurement can legitimately differ without indicating a malfunction.
The same system can carry several limits at once. Victron documents one arrangement in which a BMS-provided charge-current limit is compared with a user-configured maximum and the lower value is applied, while device-level limits can remain active. Which controller reconciles these constraints varies by architecture, so a universal hierarchy is misleading. A request describes the intended operation; a limit defines the boundary within which that operation can occur. The feasible operating point is where those two meet. (victronenergy.com)
The PCS turns a feasible request into power
Once an operating request fits within the active limits, the PCS turns that decision into electrical power flow. The battery operates on the DC side, while the site or grid is typically on the AC side; the PCS controls the conversion between them. Siemens Energy describes the PCS as the power-conversion element of the BESS, distinct from the EMS that manages dispatch and the BMS that manages battery conditions. (siemens-energy.com)
A simple diagram may suggest a clean sequence in which the EMS issues an order, the BMS approves it and the PCS carries it out. Real systems are usually more distributed. NXP’s high-voltage BESS reference design, for example, gives the battery-management unit responsibility for interlock monitoring and contactor control as well as communication with an EMS. If battery protection requires isolation, that response can occur within the battery-protection layer rather than waiting for a site-level optimization decision. (nxp.com)
The PCS also operates within its own electrical limits and AC-side conditions. Final power flow is shaped by the operating request together with battery, converter and system constraints. Calling any one controller the system’s “brain” hides how authority is actually distributed. The EMS determines what the site would like the battery to do. The BMS provides battery-side status, limits and protection. The PCS converts an allowable operating point into controlled electrical power.
The 50 kW example becomes more useful if conditions change while the system is running. A request that was feasible a minute ago may become infeasible after battery temperature rises or another battery-side limit tightens. In Victron’s documented setup, Multis and Quattros shut down in island mode when the maximum discharge current reaches zero. NXP’s BESS battery-management unit also includes contactor control, showing how battery-side protection can move from a communicated operating limit to physical isolation when required. (victronenergy.com) (nxp.com)
A changing limit simply means the feasible operating point has moved. Battery-side status and limits can be communicated to higher-level control through interfaces such as CAN FD, RS485 and Ethernet; NXP includes all three on its BESS battery-management unit for communication with an EMS. Higher-level control can then respond to the new battery boundary while the PCS continues to operate within the constraints that remain active. The control process is therefore continuous: conditions are observed, limits are updated, operating requests are adjusted where necessary, and actual operation becomes part of the information used for the next decision. (nxp.com)
Seen this way, a 3S diagram becomes a map of how an operating intention turns into executable power flow. The EMS represents what the site wants to do, the BMS provides the battery-side information and boundaries that shape what is possible, and the PCS performs the conversion that makes the resulting operating point real. When a system asks for 50 kW and delivers 35 kW, the useful question is what constraint made 35 kW the feasible operating point. That question reveals more about the system than the controller names alone.
