{"id":5065,"date":"2026-08-27T17:55:40","date_gmt":"2026-08-27T09:55:40","guid":{"rendered":"https:\/\/www.solidess.com\/?p=5065"},"modified":"2026-08-27T17:55:40","modified_gmt":"2026-08-27T09:55:40","slug":"logique-de-priorite-bess-ems","status":"publish","type":"post","link":"https:\/\/www.solidess.com\/fr\/bess-ems-priority-logic\/","title":{"rendered":"Logique de priorit\u00e9 du syst\u00e8me BESS EMS : r\u00e9serve, lissage des pics ou recharge photovolta\u00efque ?"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Most BESS failures are obvious: a breaker opens, an alarm appears or the PCS stops. An EMS priority failure is quieter. The battery keeps running. Peak shaving can still spend energy reserved for an outage. PV charging can still fight a demand limit. Post-event recharge can still create a second peak at the PCC.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The result depends less on how many modes sit on the HMI than on which mode is allowed to act first. MegSolid ESSA0100B-0215 combines a 100 kW PCS, 215.04 kWh nominal battery energy and integrated EMS in one outdoor C&I platform. Those functions help only after the project writes one hierarchy for safety, grid obligations, reserve, commercial dispatch and recovery.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Logique\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Why several useful BESS functions can produce the wrong result<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Take a factory that wants three outcomes from one battery: keep energy for a controlled shutdown, cut the afternoon demand peak, and absorb surplus PV before an evening shift.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

At midday, PV charging is useful. When factory demand rises, charging should drop before peak-shaving discharge starts. If the grid fails later, the protected reserve should still be there. After the event, recharge should restore readiness without pushing grid import above the demand target.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Each command is reasonable on its own. The conflict appears when they compete for the same PCS power and battery energy. Independent mode switches do not resolve that. The EMS needs one control order that confines each commercial objective to the envelope left by higher-priority requirements.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The five-level EMS hierarchy that keeps the objectives aligned<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
Priority<\/th>Control authority<\/th>Effect on lower-priority modes<\/th><\/tr><\/thead>
1<\/td>BMS, PCS, temperature, alarm and emergency limits<\/td>Unsafe or unavailable commands are blocked<\/td><\/tr>
2<\/td>Breaker state, anti-islanding and contractual PCC limits<\/td>Dispatch stays inside the permitted electrical state<\/td><\/tr>
3<\/td>Protected-load reserve<\/td>Commercial discharge stops at the approved reserve floor<\/td><\/tr>
4<\/td>Peak shaving, tariff dispatch and PV self-consumption<\/td>Only the remaining power and SOC band are used<\/td><\/tr>
5<\/td>Controlled recharge<\/td>Recovery uses available charge headroom and PCC margin<\/td><\/tr><\/tbody><\/table><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

This order separates control authority from commercial preference. The owner can still rank demand reduction, tariff shifting or PV capture inside Priority 4. None of those objectives can override BMS limits, an export constraint or protected energy.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

OpenEMS documents separate controllers for minimum battery level, peak shaving and PV self-consumption, then uses a scheduler for execution order. One higher-priority controller narrows the setpoints available to the next. See the OpenEMS Edge architecture<\/a> et scheduler and controller concepts<\/a>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Where measurements, permissions and commands originate: Architecture de communication entre le BMS et l'EMS<\/a><\/strong>. The priority hierarchy then decides which valid request gets the available battery power.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tGet a Project-Specific EMS Priority Matrix<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"MegSolid\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Backup reserve starts with protected-load energy<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

A fixed 20%, 30% or 40% SOC floor has no engineering meaning without a protected-load profile. The same SOC percentage can support very different durations as load, temperature, auxiliary demand, battery condition and the usable SOC window change.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Reserve starts with the AC energy required by the selected circuits. Safe-stop loads, restart loads and auxiliary consumption belong in the same calculation when they form part of the resilience objective.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Protected energy fraction = required protected-load AC energy \u00f7 warranted usable AC energy<\/strong><\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The result is an energy allocation. It becomes an EMS setpoint only after applying that model\u2019s SOC definition, operating window, measurement accuracy and state-of-health boundary.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Why nominal battery energy is not guaranteed AC delivery: Proc\u00e9dure d'essai de capacit\u00e9 des syst\u00e8mes de stockage d'\u00e9nergie par batterie (BESS) \u00e0 usage commercial<\/a><\/strong>. DOD, throughput and end-of-life: C&I BESS warranty boundary<\/a><\/strong>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Dynamic reserve avoids wasting the commercial working band<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

A permanent high reserve protects resilience and can leave too little energy for daily savings. A permanent low reserve releases more commercial capacity and can leave production exposed in a known risk period.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

A dynamic reserve changes with a defined event: a utility outage notice, a high-value production shift, severe weather, a weak-grid period or planned generator maintenance. Each change needs an activation time, expiry condition, recovery target and audit record. Forecasts can move the schedule. They must not override BMS, PCS or PCC constraints.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

NREL\u2019s Microgrids for Energy Resilience<\/a> separates grid-connected economic operation from resilience operation. The EMS control narrative should keep that same split. A daily tariff schedule should not decide whether backup energy survives.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Peak shaving succeeds or fails at the PCC meter<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Peak shaving is a feedback-control problem measured at the contractual PCC, where grid import and demand compliance are judged.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Using positive values for grid import and BESS discharge, an initial feed-forward request is:<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Requested BESS discharge power = max(0, net site demand before BESS \u2212 PCC import target)<\/strong><\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Measured PCC power then closes the loop. The EMS must account for meter latency, ramp rate, deadband, load variation and the active demand-measurement window. The final command stays inside available PCS power, BMS discharge permission, temperature limits and the protected SOC floor.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

When reserve is the active limitation, the HMI should show that reason. A generic \u201cSystem normal\u201d state hides the difference between healthy equipment and an unmet PCC target.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Zero export uses the same PCC measurement and a different obligation. Export envelope first, commercial peak target second: Sp\u00e9cification de contr\u00f4le \u00ab z\u00e9ro exportation \u00bb BESS<\/a><\/strong>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

PV charging and grid recharge need different envelopes<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

PV charging uses generation that would otherwise be exported or curtailed. Grid recharge uses available import capacity to restore SOC. One unrestricted \u201ccharge\u201d mode hides two different effects at the PCC.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The instantaneous PV charging command should contain only power quantities:<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Permitted battery charging power = min(PV-surplus power, PCS charge-power limit, BMS charge-power limit, PCC charge allowance, SOC-dependent charge-power limit)<\/strong><\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

SOC headroom is an energy quantity. It sets how long the charging command can continue. Convert it over a defined control horizon before it enters a kW limit.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Grid recharge follows the remaining import margin:<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Allowed grid-recharge power = max(0, PCC import ceiling \u2212 site import before BESS charging)<\/strong><\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

This limit stops reserve recovery from recreating the peak the battery just cut. A scheduled low-load window or available PV can restore SOC with less import stress. BMS charge permission, PCS limits and active alarms still set the final command. Commercial context for that recovery: C&I peak-shaving ROI page<\/a><\/strong>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

What the EMS should do when operating modes collide<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
Simultaneous condition<\/th>Winning control<\/th>Observable result<\/th><\/tr><\/thead>
Peak shaving reaches the reserve floor<\/td>Protected-load reserve<\/td>Commercial discharge stops and the limitation is logged<\/td><\/tr>
Grid recharge reaches the import ceiling<\/td>PCC import limit<\/td>Recharge is reduced to the remaining margin<\/td><\/tr>
Battery becomes full while export is restricted<\/td>Approved PV or load-control fallback<\/td>The alternative actuator responds<\/td><\/tr>
Zero-export and peak shaving request different setpoints<\/td>PCC export constraint<\/td>The commercial request is clipped<\/td><\/tr>
Grid status or PCC data becomes invalid<\/td>Electrical-state or fail-safe logic<\/td>Grid-connected dispatch exits or enters the approved fallback<\/td><\/tr><\/tbody><\/table><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Generator operation adds another constraint. Reverse-power protection and minimum generator loading sit above commercial battery dispatch. Generator envelope and control boundary: BESS and diesel-generator control page<\/a><\/strong>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Stale data also needs a defined response. Holding the last valid setpoint can be unsafe because load or breaker state may have changed. A timeout, alarm, local fallback and controlled recovery sequence make the failure visible and testable.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Why the ESSA0100B-0215 platform fits this control problem<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Cabinet architecture with battery, PCS, isolation transformer and EMS in one boundary: MegSolid ESSA outdoor C&I platform<\/a><\/strong>. Priority control crosses every one of those interfaces.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Integrated EMS reduces control handoffs<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

ESSA publishes access to grid, PV, storage, load and generator information. One EMS can evaluate those sources in a single operating cycle. Project-specific meter mapping and actuator logic remain necessary. The control foundation is already part of the platform.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Rated power and nominal energy serve different decisions<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

ESSA0100B-0215 is rated at 100 kW AC with 215.04 kWh nominal battery energy. The 100 kW rating is the cabinet\u2019s dispatch power class. The 215.04 kWh figure is the starting energy value for reserve and duration analysis. Keep those roles separate. A nominal two-hour ratio is not a backup guarantee.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Built-in electrical and outdoor integration simplify the equipment boundary<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

The published platform includes a built-in isolation transformer, IP54 enclosure and intelligent air cooling. That gives a defined outdoor cabinet and electrical interface for C&I sites. External switchgear, ATS design, PCC metering, PV controls and generator protection stay in project engineering. They are not implied by an \u201call-in-one\u201d label.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Standard communications support commissioning evidence<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

RS485 and TCP\/IP let the cabinet exchange measurements, limits, commands and alarms with project meters and SCADA. Their value is the trend from EMS target to BESS response to PCC result.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Wider power, duration and site-interface decision: Page de s\u00e9lection ESSA0100B-0215<\/a><\/strong>. Other classes: MegSolid C&I energy-storage portfolio<\/a><\/strong>.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Commissioning should prove priority during overlapping modes<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Separate tests prove that backup, peak shaving and PV charging can run. Controlled overlap tests prove which function receives priority.<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

A complete FAT and SAT sequence should include:<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t