BESS & Microgrids · 45–60 min
BESS and Microgrids: A Practical Guide to Power, Energy and Control
A rigorous, plain-language study of how storage behaves as a controlled power system, from power and energy fundamentals to safety, degradation, dispatch, resilience, economics and acceptance evidence.
A traceable educational edition.
This record separates publication authority from project approval. It identifies what was researched, what remains limited and when the source base must be reviewed again.
What this paper examines.
This paper treats battery storage as a controlled power system. It separates power from energy, traces BMS, PCS and EMS authority, explains usable capacity and degradation, examines dispatch conflicts, safety layers, microgrid transitions, economics and acceptance evidence, and identifies the Philippine questions that must be resolved before commercial commitment.
- Stationary electrochemical BESS and microgrid planning
- Power, energy, controls, safety, resilience and economics
- Project evidence gates from discovery through handover
- Does not provide final sizing, protection, fire, structural or interconnection design
- Chemistry, product configuration, location and operating mode materially change the hazard and approval path
- Draft regulatory material is identified as draft and must not be treated as final
Use the same language at every decision gate.
- BESS
- Battery Energy Storage System
- BMS
- Battery Management System
- EMS
- Energy Management System
- PCS
- Power Conversion System
- POI
- Point of Interconnection
- SOC
- State of Charge
- SOH
- State of Health
- STS
- Static Transfer Switch
What changed and when.
Initial public web edition
Research, technical-writing and editorial-control upgrade
What you should be able to explain after reading.
- Distinguish kW, kWh, state of charge and usable energy
- Trace the battery, BMS, PCS, EMS, protection and site interfaces
- Match operating use cases to data, dispatch and acceptance criteria
- Identify the engineering, safety and commercial evidence required before sizing
Follow the complete operating chain.
At 3:00 p.m., site demand begins to climb. Should the battery discharge now?
A battery can respond in milliseconds, but a responsible decision begins much earlier with the use case, load profile, reserve policy, electrical design and operating authority.
Imagine a facility with a 600 kW demand target, rooftop solar, a critical operations building and a Battery Energy Storage System. At 3:00 p.m., load rises toward the target while solar output begins to fall. The EMS can discharge the battery to reduce imported power. Three hours later, the grid fails.
If the battery used too much energy for peak shaving, the resilience reserve may be insufficient. If the PCS cannot establish voltage and frequency, the battery cannot form an island. If protection, grounding and switching were not designed for that mode, opening the grid breaker does not create a safe microgrid. The same battery capacity can therefore produce very different outcomes depending on control priorities and system architecture.
BESS and microgrids as controlled power systems
This edition separates power from energy, connects the battery to PCS and EMS behavior, and examines safety, degradation, interconnection, resilience, economics and acceptance evidence.
The required service determines the battery system
A BESS is not sized responsibly from a monthly bill or a desired container count. First define the service: demand reduction, energy shifting, renewable firming, backup, frequency response, capacity support, power-quality assistance or microgrid operation. Each service has a different response time, power, energy, reserve, availability and dispatch requirement. The US DOE Energy Storage Handbook organizes storage around technologies, engineered systems and applications for exactly this reason [1].
Start by writing the operating statement in plain language. “Hold grid import below 600 kW during the utility demand interval” is testable. “Provide two hours of critical-load support after loss of grid” is testable once the critical-load profile and transition requirement are defined. “Install a 1 MWh battery” is not a use case. It is an equipment quantity without an operating promise.
A project may pursue several value streams, but they can compete. Energy reserved for an outage cannot simultaneously be committed to daily arbitrage. High cycling for one service can accelerate degradation and reduce future energy available to another. Dispatch priority and commercial priority must therefore be written together.
BESS operating architecture
Use-case requirements are not interchangeable
Power, energy, duration and usable state of charge answer different questions
Power, expressed in kW or MW, describes the instantaneous rate of charge or discharge. Energy, expressed in kWh or MWh, describes how much can be delivered over time. A 1 MW / 2 MWh system has a nominal two-hour duration at rated power before accounting for usable SOC window, auxiliary consumption, conversion loss, temperature, degradation and operating reserve.
Nameplate energy is not the same as energy delivered at the point of interconnection. The model should distinguish DC battery capacity, usable DC window, PCS efficiency, transformer and cable loss, HVAC and controls, minimum reserve and end-of-life guarantee. NREL notes that power and energy together define BESS size and that oversizing can strand capital [2].
State of charge is an estimate inside an operating window
State of charge, or SOC, expresses the estimated remaining charge relative to a defined usable reference. It is not a direct fuel-gauge measurement. The BMS estimates SOC from electrical and temperature behavior using its supported methods. Accuracy can vary with operating history, calibration and cell condition.
Operators also distinguish state of health, which describes how present capability compares with an agreed beginning-of-life reference. A system at 90 percent SOC late in life does not necessarily contain the same usable energy it held at 90 percent when new. Warranty and dispatch models should therefore state whether limits and guarantees apply at cell, rack, DC bus, PCS output or point of interconnection.
SOC, reserve and degradation define different boundaries
From nameplate energy to useful delivered energy
Required nominal energy
delivered load energy ÷ (usable SOC fraction × discharge-path efficiency × end-of-life capacity fraction)
This frames the calculation only. A qualified design must include load sequence, power limits, reserve, auxiliaries, temperature and warranty rules.Why 500 kW for two hours is not simply a 1,000 kWh purchase
A facility wants 500 kW delivered for two hours. Assume, only for illustration, an 80 percent usable SOC window, 92 percent discharge-path efficiency and 80 percent end-of-life capacity.
- Required delivered energy: 500 kW × 2 h = 1,000 kWh.
- Combined usable factor: 0.80 × 0.92 × 0.80 = 0.5888.
- Indicative beginning-of-life nameplate: 1,000 ÷ 0.5888 = 1,698 kWh.
- Add verified auxiliary and reserve requirements, then check whether 500 kW remains available across SOC, temperature and warranty limits.
Battery cells do not operate the AC system by themselves
Cells form modules, modules form racks and racks form DC subsystems monitored by a battery-management system. The BMS supervises voltage, current, temperature, SOC estimates and protective limits. The PCS converts between DC and AC and controls active and reactive power within its capability. The EMS or microgrid controller translates site objectives into permitted setpoints while coordinating forecasts, meters, generators and operating constraints.
These controls operate at different speeds and authority levels. Cell voltage or temperature protection cannot wait for an economic optimizer. The BMS should constrain permitted charge and discharge. The PCS should respect those limits while controlling AC behavior. The EMS may choose the desired dispatch only inside the permitted envelope. Independent protection should isolate faults under the approved design even if a supervisory communication link is unavailable.
Protection, switchgear, transformer, grounding, metering, communications, HVAC, fire detection, enclosure and auxiliary power are not accessories. They determine whether the system can connect, survive faults, maintain temperature, stop safely and be operated after handover.
Control hierarchy and decision ownership
Key interfaces to control
A schedule is only valid inside operating constraints
Peak shaving requires a demand forecast and enough power and energy to hold the site below a target through the peak interval. Arbitrage requires tariff spread large enough to cover efficiency loss, degradation, operating cost and financing. Renewable firming needs a forecast, ramp objective and curtailment logic. Resilience needs an explicit reserve policy and critical-load model.
The shape of the peak matters. A 1 MW spike lasting five minutes can require high power but relatively little energy. A 400 kW exceedance lasting three hours needs less instantaneous power but much more energy. Monthly bills normally reveal the peak charge and total energy, not the interval shape needed to distinguish these cases.
The EMS should define priority when services conflict, recovery after communication failure, SOC targets, generator coordination, import and export limits, maintenance states and manual authority. Cybersecurity matters because the controller can influence substantial real power.
Illustrative peak-shaving dispatch
Competing value streams need dispatch priority
Safety is an engineered lifecycle, not a certificate list
Electrochemical hazards depend on chemistry, cell condition, enclosure, propagation behavior, ventilation, detection, suppression strategy, separation, emergency access and operating response. The US DOE Energy Storage Handbook addresses performance testing, electrochemical safety, physical security, cybersecurity, procurement and commissioning as distinct engineering topics [1].
A thermal event can progress through abnormal cell behavior, heating, venting and propagation depending on chemistry, design and failure conditions. Detection must be connected to an approved response. An alarm that reaches an unattended dashboard has not created emergency readiness. Site personnel and responders need clear isolation boundaries, hazards, access information and authority.
The project must identify applicable current codes and authority requirements, then translate them into site design, product evidence, hazard analysis, emergency procedures, training, inspection and maintenance. A foreign listing or report can be relevant evidence but does not, by itself, establish Philippine approval.
Layered safety model
Prevent
Cell quality, limits and thermal management
Detect
Gas, smoke, heat and electrical monitoring
Contain
Propagation and enclosure strategy
Isolate
Protection, shutdown and electrical separation
Respond
Emergency plan, access and trained personnel
Backup capability requires a supported electrical operating mode
A grid-connected BESS does not automatically form an island. Microgrid operation requires a defined boundary, isolation method, grid-forming source or compatible control strategy, protection changes, grounding treatment, load shedding, generator and renewable coordination, black-start sequence where required, resynchronization and utility approval.
Grid-following operation generally synchronizes to an existing voltage and frequency reference. Grid-forming operation can establish or regulate that reference within a supported design. These phrases do not prove black-start capability, seamless transfer or compatibility with every generator and inverter. The exact PCS mode, controller sequence, protection and tested configuration determine what can be claimed.
Critical-load resilience must use an interval or scenario profile, not merely the building peak. Motor starting, step load, inrush, harmonics, minimum generator loading and communications availability can determine whether the island remains stable.
Grid-connected to islanded operating sequence
Model each value stream once and carry performance through time
Economics should separate demand reduction, energy shifting, avoided outage cost, renewable utilization and other services. A benefit must have a baseline, dispatch rule, tariff or valuation basis, adoption timing and responsible owner. Avoid double counting energy that serves two commitments in the same interval.
Round-trip efficiency is also conditional. It depends on power level, temperature, auxiliaries, SOC range and where energy is measured. A headline PCS efficiency does not equal site-level round-trip efficiency. The economic model should use the warranted or tested boundary relevant to billing and include HVAC, controls and standby energy.
One stored megawatt-hour does not return one delivered megawatt-hour
Capacity and efficiency change with age, cycles, calendar time, temperature and operating window. The model should state beginning and end-of-life performance, augmentation, replacements, availability, downtime, auxiliary energy, warranty throughput and residual value.
Testing whether a demand-saving claim is technically available
A project assumes 600 kW of monthly demand reduction. Interval data shows the relevant peak lasts 2.6 hours, while another resilience commitment reserves 30 percent SOC.
- Calculate energy needed above the demand target from interval data, not 600 kW × the billing period.
- Apply PCS limit, SOC reserve, efficiency, auxiliary load and end-of-life capacity.
- Verify recharge opportunity before the next potential peak.
- Model missed forecasts and downtime instead of assuming perfect dispatch.
- Value only demand reduction that the operating strategy can reliably deliver.
Freeze the use case, evidence and approval path before commitment
The Philippine DOE issued an ESS policy framework under DC2019-08-0012, and current project treatment depends on application, ownership, connection and applicable market or utility requirements [3]. Confirm the current DOE, ERC, NGCP or distribution-utility pathway, system-impact requirements, environmental and local permits, fire and electrical approvals, and the authority having jurisdiction for the exact project.
Procurement should define the guaranteed power and energy at an agreed condition and measurement point, usable SOC window, efficiency method, auxiliary treatment, availability, degradation curve, throughput or cycle conditions, augmentation, warranty exclusions and acceptance tests. A warranty stating only years and cycles may not explain how operating temperature, depth of discharge, C-rate and annual throughput affect coverage.
Before sizing
Obtain interval load, tariff, outage, critical-load, renewable and site data.
Before selection
Confirm use case, ratings, duration, chemistry, warranty and operating envelope.
Before production
Freeze SLD, protection, controls, interfaces, safety design and tests.
Before energization
Complete studies, permits, commissioning, emergency plan and training.
Before acceptance
Demonstrate capacity, power, efficiency, controls, protection and use case.
Before final handover
Deliver as-builts, settings, credentials, spares, warranty and lifecycle plan.
Project evidence gates
Primary sources engaged in this edition
- US DOE Energy Storage HandbookSandia National Laboratories. Technologies, engineered systems, safety, commissioning and applications.
- Preparing Distribution Utilities for Utility-Scale Storage and Electric VehiclesNREL. BESS power, energy, sizing and peak-shaving context.
- Philippine DOE Energy Sector Accomplishment ReportOfficial context for DC2019-08-0012 and ESS applications.
- BESS Procurement ChecklistUS DOE FEMP. Procurement planning reference.
All diagrams and illustrative calculations are original Metro Power educational material. Concept examples are not final engineering or a performance guarantee.
Storage starts with an operating objective
Peak reduction, energy shifting, renewable integration, backup, resilience and grid services create different charge and discharge patterns. A system optimized for a short high-power event may not support a long outage. A resilience reserve can reduce energy available for daily savings.
The first project document should state the priority use case, secondary use cases, dispatch authority, critical constraints and success measures. Without that hierarchy, the design can double-count value or create conflicting expectations.
- Name the operating problem
- Define when the battery must charge, wait and discharge
- State which value stream has priority during conflict
Power and energy answer different questions
A 500 kW system can deliver or absorb energy at a rate up to its controlled operating limit. A 1,000 kWh usable energy window can theoretically support 500 kW for about two hours before considering efficiency, operating reserves and changing conditions. Nameplate energy is not automatically available for every cycle.
State of charge, depth of discharge, temperature, cell limits, degradation reserve and warranty conditions influence the usable operating window. The design should distinguish gross, nominal and usable energy and state the assumptions behind each.
- Calculate power from the target demand or load
- Calculate energy from duration and dispatch profile
- Apply efficiency, reserve and lifecycle assumptions transparently
A BESS is an integrated electrical system
Battery modules and racks are monitored by a battery-management system. The power-conversion system exchanges DC battery energy with the AC system. An energy-management or microgrid controller schedules operation against site conditions and use-case priorities. Transformers, switchgear, protection, metering, auxiliary power, HVAC, fire systems and communications complete the installation.
Every interface needs ratings, control logic, fault behavior, alarms and ownership. The single-line diagram, control narrative and cause-and-effect logic should agree before commissioning.
- Map the AC and DC power paths
- Define normal, degraded and emergency states
- Control settings and software revisions
Credible sizing needs interval evidence
Interval load data reveals peaks, duration, variability and the relationship between demand and operating schedules. Tariffs identify energy and demand cost structures. Outage history and critical-load data support resilience analysis. Solar and generator profiles affect charging opportunities and microgrid behavior.
Data quality must be checked for missing periods, abnormal operations and representativeness. A preliminary model should show assumptions and sensitivity rather than hide uncertainty behind one savings figure.
- Collect interval load and tariff data
- Identify critical and noncritical loads
- Confirm transformer, generator, solar and site constraints
Safety is designed through the lifecycle
The project must consider cell behavior, thermal management, detection, separation, emergency response, access, ventilation where applicable, protection, isolation and manufacturer requirements. Applicable codes, permits and authority requirements must be confirmed for the actual Philippine site.
Operations need alarms, escalation, inspection, maintenance, training and incident procedures. Emergency responders and facility personnel should understand the installation boundaries and shutdown approach before energization.
The financial case follows the dispatch case
A commercial model should include equipment, integration, civil and electrical works, interconnection, commissioning, software, maintenance, insurance, financing, auxiliary consumption, efficiency, degradation and replacement assumptions. Revenue or savings should follow a dispatch model consistent with the warranty.
Sensitivity testing should show what happens when tariffs, load, operating availability, degradation or financing changes. A project can be technically feasible and commercially weak, or financially attractive under assumptions the site cannot operationally maintain.
Commission the use case, not only the equipment
Testing should verify protection, controls, communications, charge and discharge response, power and energy performance, alarms, transitions and recovery. Microgrid or islanding functions require coordinated testing with generation, loads and interconnection requirements.
Handover includes as-built drawings, settings, software records, operating limits, training, maintenance, spares, warranty conditions and support escalation. The owner needs enough information to operate safely after the project team leaves.
Questions to take into a real project discussion.
- What outcome has first dispatch priority?
- What interval data supports the selected power and energy ratings?
- Which reserve, efficiency and degradation assumptions define usable energy?
- How will the system behave during grid loss, faults and communication failure?
- What test proves the commercial use case at acceptance?
Authoritative references used to develop this paper.
This is an original Metro Power synthesis. International references do not replace Philippine laws, project specifications or approvals.
01Technology, system engineering, safety, procurement and commissioning.
Utility planning and implementation context.
Foundational grid-storage concepts and project questions.
Second-edition evidence review: usable energy, hazard boundaries and operating authority
A storage decision is complete only when the energy model, electrical behavior, safety case, interconnection path and commercial obligation use the same configuration and operating assumptions.
Define the measurement boundary
DC cell energy, DC rack energy, PCS AC output and point-of-interconnection delivery are not interchangeable. Efficiency, auxiliaries and guarantees must use an identified boundary.
Reserve energy only once
Daily peak shaving, arbitrage, resilience and grid services can compete for the same state of charge. EMS priority and commercial commitment must reconcile.
Treat safety as continuing evidence
Product reports, site design, installation, commissioning, emergency planning, training, maintenance and change control form one lifecycle safety case.
Sizing a resilience obligation through the delivered-energy boundary
A critical load needs 420 kW for 2.5 hours. Illustrative assumptions are 85 percent usable SOC, 91 percent discharge-path efficiency, 82 percent end-of-life capacity and 35 kW of continuing BESS auxiliaries.
- Load energy is 420 kW × 2.5 h = 1,050 kWh.
- Auxiliary energy is 35 kW × 2.5 h = 87.5 kWh.
- Total delivered requirement is 1,137.5 kWh before additional reserve.
- Combined usable factor is 0.85 × 0.91 × 0.82 = approximately 0.634.
- Illustrative beginning-of-life nameplate is 1,137.5 ÷ 0.634 = approximately 1,794 kWh, before project-specific reserve and power checks.
- Verify that PCS power, starting current, temperature, SOC limits and island controls support the full load sequence.
What to challenge before commitment.
Peak shape and required dispatch energy remain unknown
Evidence: Validated interval load profileBackup mode cannot establish a stable electrical reference
Evidence: Exact mode declaration and integrated transition testDelivered duration is overstated
Evidence: Measured or warranted auxiliary profileCommercial commitment follows an unverified approval path
Evidence: Current ERC, DOE, NGCP, DU and local-authority confirmations- ERC has published draft ESS rules and interconnection standards under ERC Case No. 2024-006 RM
- ERC issued 2026 microgrid-service-provider operating-authority materials
- Whether the draft ESS rules have been finalized or superseded
- Project classification and applicable COC, ATO, interconnection, market and local requirements
- Fire, building, electrical, environmental and emergency-response acceptance for the exact site
Educational publication only. This paper does not certify equipment, establish project compliance, replace professional engineering or guarantee performance, savings, approval or commercial outcome. Confirm the controlling TOR, current regulations, site data, selected configuration and responsible authority before procurement, installation or operation.