BESS Duty-Cycle Assumptions: An Owner’s Audit for Vietnam Factories

Executive answer: a factory battery proposal is not defined by “1 MW / 2 MWh” alone. The owner must define the duty cycle: what service the battery performs, when it charges and discharges, the power and energy profile at an agreed meter, the usable state-of-charge window, efficiency and auxiliary loads, reserve requirements, temperature and availability conditions, and how degradation changes the obligation through the contract term.

This guide is written for an FDI factory team comparing BESS proposals in Vietnam. It does not quote a price, select a chemistry, promise savings, or declare compliance. All numerical examples are hypothetical engineering checks. Project design must use the selected manufacturer’s limits, warranty, fire strategy, interconnection requirements and the regulations and standards applicable at the design date.

1. Begin with the business service

Peak shaving, solar shifting, backup and power-quality support are different services. They may compete for the same state of charge and inverter capacity. A proposal should translate the business objective into an operating obligation before it selects equipment.

One battery can technically provide more than one service, but the contract must define priority. If a noon solar-charge target fills the battery, it may have no upward charging headroom for a grid-support command. If peak shaving empties it before an outage, it may not meet a backup promise.

2. Write the duty cycle as a time series

A usable duty-cycle file contains timestamp, requested active power, requested reactive power where relevant, operating mode, minimum and maximum state of charge, expected ambient or equipment temperature range, reserve state, and permitted recovery time. State the sign convention: for example, positive power means discharge to the factory bus and negative power means charging from the bus.

Use a time step that can represent the service. Fifteen-minute data may support a first tariff-demand study but can hide short ramps and transient constraints. A commissioning test may need seconds or sub-second records depending on the agreed function. Keep the commercial settlement interval and the control-system sampling interval distinct.

IEC TS 62933-2-2:2022 defines testing methods and duty cycles for evaluating EES performance in different applications. It is a useful framework for requiring a reproducible test profile, but the project still has to define its own service, boundary and acceptance values.

3. Fix the measurement boundary

Power and energy can be stated at the battery DC terminals, PCS AC terminals, transformer secondary, point of common coupling or factory utility meter. Those values are not interchangeable. Transformer losses, HVAC, pumps, controls, fire systems and standby consumption may sit between them.

• The power and energy meter used for guarantees and settlement.
• Whether auxiliary consumption is inside or outside delivered energy.
• Whether charging and discharging efficiencies include the transformer.
• Time synchronization, data quality, missing-data rules and meter class.
• Who owns raw data, derived KPIs and remote-control access.

The factory electrical metering-boundary guide explains why the same physical plant can show different performance when teams use different boundaries.

4. Separate rated, usable and deliverable energy

Nameplate energy is not automatically deliverable energy. The usable value depends on the permitted state-of-charge window, present capacity, temperature, discharge rate, efficiency, reserve and protection limits.

• Rated energy: 2.0 MWh.
• Permitted SOC window: 10% to 90%, or 80%.
• Usable stored-energy window: 2.0 × 0.80 = 1.60 MWh.
• Assumed discharge-path efficiency to the contractual AC meter: 96%.
• Maximum theoretical AC delivery: 1.60 × 0.96 = 1.536 MWh.

This arithmetic is not a product claim. It shows that a requirement to deliver 0.75 MW for two hours, or 1.50 MWh, leaves only 36 kWh of theoretical margin. Control reserve, temperature derating, capacity fade, measurement tolerance and auxiliary consumption could remove that margin. The proposal should not present the 2.0 MWh nameplate as a two-hour 1 MW guarantee without defining these conditions.

5. Check power and energy together

A 1 MW PCS can meet a one-megawatt power request only within its voltage, current, temperature and reactive-power limits. It does not prove that the battery can sustain that output for the requested duration. Conversely, a large energy block may be unable to follow a fast command if the PCS, transformer or battery current limit is smaller.

Require a power-versus-duration envelope at beginning of life and at the contractual end-of-life condition. Show continuous and short-duration ratings separately. If reactive power is required, state whether active-power capability is reduced at the requested apparent power:

S² = P² + Q²

For illustration, a 1.0 MVA PCS delivering 0.80 MVAr can supply at most sqrt(1.0² − 0.8²) = 0.60 MW if apparent power is the governing constraint. Actual capability curves and thermal conditions must come from the selected equipment.

6. Reconcile round-trip efficiency

Round-trip efficiency is meaningful only with an agreed test cycle, power level, SOC window, temperature, auxiliaries and meter boundary. A single percentage cannot be applied blindly to every dispatch profile.

If the owner needs 1.50 MWh discharged at the contractual AC meter and the agreed AC-to-AC round-trip efficiency for that cycle is hypothetically 88%, the charging energy required is 1.50 / 0.88 = 1.705 MWh. The loss is approximately 0.205 MWh. If HVAC and standby loads are outside the stated efficiency, add them explicitly. At low power, fixed auxiliary consumption may materially reduce effective efficiency.

7. Count throughput and equivalent full cycles

Calendar age and energy throughput both affect long-term performance. A daily cycle is ambiguous when the battery performs partial charges, regulation or multiple services. Define equivalent full cycles at the warranty boundary.

For example, 1.20 MWh of AC discharge on each of 300 operating days gives 1.20 × 300 = 360 MWh. Using a 2.0 MWh reference energy, that is 360 / 2.0 = 180 discharge-equivalent full cycles per year. A vendor warranty may define throughput, cycle counting and reference energy differently. The owner must use the contractual definition rather than this illustrative denominator.

Request a yearly table showing charge energy, discharge energy, equivalent cycles, average SOC, dwell time near SOC limits, temperature distribution and reserve events. Compare it with the warranty’s operating envelope.

8. Model degradation at the obligation

Capacity retention, power capability and efficiency can change over time. State whether the vendor will oversize initially, augment later, replace modules, or reduce the guaranteed duty. Define who bears augmentation engineering, outage, logistics, disposal and commissioning cost.

Suppose a factory needs 1.50 MWh AC at end of term, the usable SOC window is 80%, discharge efficiency is 96%, and warranted capacity retention is hypothetically 70%:

E_BOL = 1.50 / (0.80 × 0.96 × 0.70) = 2.79 MWh

This is only a screening calculation. Real design must use the degradation model for the actual chemistry, dispatch, temperature, calendar time and maintenance strategy. Do not multiply a generic annual percentage without checking whether the vendor model is linear, nonlinear, throughput-limited or linked to operating conditions.

9. Define state-of-charge reserves

A dispatch plan should include hard safety limits, normal operating limits and commercial reserve bands. These are different. A backup reserve may be protected from peak shaving except during an authorized emergency. Grid support may require both charging and discharging headroom.

The percentages are examples, not recommended settings. OEM limits and the approved operating philosophy govern.

10. Capture factory load uncertainty

A duty cycle based on one month of load data may fail when production schedules, holidays, new lines or seasonal HVAC demand change. Use a representative interval dataset and label shutdowns, missing data and abnormal events. Keep historical load, approved future load and contingency scenarios separate.

For peak shaving, define how the controller predicts end-of-interval demand and avoids oscillating around the threshold. For solar shifting, align PV and load data on the same time base. For backup, build an essential-load sequence rather than applying one diversity factor to the transformer rating.

The rooftop-solar feasibility data guide describes load and site evidence needed before coupling PV and storage assumptions.

11. Resolve service conflicts

Create a service-priority matrix with trigger, minimum reserve, maximum duration, recovery target and override authority. A practical hierarchy might place life safety and equipment protection first, authorized backup second, grid or industrial-park obligations third, and economic dispatch last. The actual order is project-specific.

• A peak event occurs before the backup reserve deadline.
• Solar surplus arrives when the battery is near maximum SOC.
• A demand-response call overlaps maintenance.
• Reactive-power support reduces active-power capability.
• A utility outage occurs during charging.
• Communications fail while an external optimizer is issuing commands.

Define the safe fallback state and local-control authority. Remote optimization must never bypass OEM protection or approved site interlocks.

12. Treat temperature and auxiliaries as inputs

Container HVAC, battery thermal management, transformer fans, pumps, controls, networking, lighting and safety systems consume energy. Consumption can vary with ambient temperature and power. Record whether quoted net output and efficiency include these loads.

Request environmental limits for operation, storage and maintenance, plus derating curves where applicable. State sensor locations and what happens when temperature data are unavailable. Do not infer a Vietnam-wide ambient profile; use project weather and equipment-location evidence.

13. Specify availability correctly

Availability can be time-based, energy-based, service-based or component-based. The denominator, exclusions and data substitution rules matter. A BESS may be available at reduced power yet unable to meet the full duty.

• Required power and energy constituting full availability.
• Partial-availability calculation.
• Planned maintenance windows and approval.
• Utility outage, owner outage and communications exclusions.
• Response, repair and spare-parts obligations.
• How failed or missing data are treated.

IEC 62933-3-1:2025 addresses planning and performance assessment for grid-connected EES, including functions, capabilities, monitoring and assessment. Use its scope to structure evidence; it does not set a project-specific availability promise.

14. Build acceptance around the duty

IEC TS 62933-2-3:2025 covers performance assessment testing during site operation after commissioning. The project procedure should still name instruments, calibration, stabilization, tolerances, invalid-test rules and retest responsibility.

15. Define safety before optimizing dispatch

Duty-cycle optimization must remain inside the approved safety design. The HSE and emergency package should cover hazard analysis, access control, isolation and lockout/tagout, stored-energy verification, thermal-event detection, ventilation where applicable, fire and gas strategy, emergency shutdown, first-responder interface, drainage or containment where relevant, signage, training and post-event recovery.

IEC 62933-5-1:2024 provides general safety criteria for EES systems. IEC 62933-5-2:2025 adds system-level safety requirements for electrochemical systems. These references do not replace local regulatory approval, manufacturer instructions, site-specific fire engineering or competent-authority review.

Only trained and authorized personnel should inspect, isolate, test or maintain the system. A commercial duty-cycle requirement is never permission to exceed OEM limits or defeat protective controls.

16. Request a priceable BOQ

• Battery enclosures or racks, BMS, PCS and energy-management controls.
• MV/LV transformer, switchgear, protection, metering and communications.
• HVAC or thermal management and auxiliary distribution.
• Fire detection/protection and emergency interfaces.
• Civil works, foundations, drainage, barriers, access and lifting provisions.
• SCADA, historian, cybersecurity responsibilities and data retention.
• Factory tests, shipping, installation, SAT, performance testing and training.
• Spare parts, tools, software licences and service subscriptions.
• Warranty, augmentation, replacement and end-of-life boundaries.

The industrial BESS procurement brief provides a wider RFQ structure. This article focuses on making the proposed operating duty auditable.

17. Compare normalized assumptions

Do not rank bids by VND/kWh of nameplate energy unless scope, boundary, duty, warranty and end-of-term obligation are equivalent. Record exclusions in a deviation register. The electrical EPC tender-boundary guide helps separate owner, EPC and vendor responsibilities.

18. Maintain an operating evidence pack

The handover dossier should include approved settings, control priority, meter map, data dictionary, alarm matrix, OEM limits, warranty calculation, baseline tests, as-builts, software versions, cybersecurity ownership, maintenance plan, spare parts, training and emergency contacts. Each dispatch-algorithm change should be versioned and risk-reviewed.

Use a consistent-boundary monthly reconciliation: Charge energy − losses − net discharge energy = change in stored energy. Account for the SOC difference between the start and end of the period. Investigate drift rather than forcing the balance to zero.

19. Questions for the RFQ

1. Provide the exact one-year duty-cycle file used for sizing and warranty review.
2. State guaranteed power and energy boundary, SOC window and environmental conditions.
3. Show beginning-of-life and end-of-term power-duration envelopes.
4. Define throughput, cycle counting, capacity retention and augmentation responsibility.
5. State efficiency test conditions and auxiliary-load treatment.
6. Provide service-priority and safe-fallback logic.
7. List meter, historian, time-sync and raw-data access requirements.
8. Provide FAT, SAT and operational performance-test procedures.
9. Describe safety, emergency response, isolation and maintenance interfaces.
10. Submit a deviation register against the owner’s normalized duty.

Frequently asked questions

Is a 1 MW / 2 MWh BESS always a two-hour system?

No. Deliverable duration depends on the meter boundary, usable SOC window, efficiency, auxiliaries, temperature, degradation, reserve and power limits.

How many cycles per day should the owner assume?

Do not choose a generic number. Derive throughput from the time-series service and compare it with the vendor’s contractual definition.

Can one BESS provide backup and peak shaving?

Potentially, if the architecture and controls support both. The contract must reserve sufficient energy and power and define priority.

Should efficiency be measured at the battery or utility meter?

Use the boundary matching the decision and contract. State each required boundary and reconcile transformer and auxiliary losses.

Does an IEC reference prove the project is safe or compliant?

No. Project conformity requires applicable design, equipment evidence, installation, testing, regulatory approvals and competent review.

Owner decision checklist

• Freeze the service hierarchy and one-year duty-cycle file.
• Fix the meter boundary, sign convention and auxiliary-load treatment.
• Reconcile power, usable energy, duration and end-of-term capacity.
• Check throughput, SOC dwell, temperature and warranty limits.
• Normalize bid assumptions and exclusions.
• Link the duty cycle to controls, HSE, ITP, FAT, SAT and operating tests.
• Keep raw data and formulas auditable.

QuangAnhcons can help an FDI owner structure the load-data request, duty-cycle register, electrical interface, BOQ boundary, bid normalization, ITP and commissioning evidence for a factory BESS evaluation in Vietnam. Start with interval load data, tariff and demand rules, outage requirements, PV profile where relevant, the preliminary SLD, operating priorities and the proposed vendor warranty. Final safety, regulatory, investment and contract decisions remain with the owner’s authorized specialists and project representatives.

No quick estimate yet. You can still submit a project quotation request.