BESS Warranty Exclusions: An Industrial Buyer’s Contract Review for Vietnam

A battery energy storage system can carry several warranties at once: cell or module product coverage, retained-energy or capacity guarantees, power-conversion coverage, availability commitments, workmanship obligations and software support. Their headlines may look compatible while their exclusions leave the factory with the dominant operating risk. An industrial buyer should therefore review a BESS warranty as a controlled engineering interface, not as a marketing percentage.

This guide is written for FDI factory owners and EPC procurement teams in Vietnam. It does not interpret a specific supplier warranty, provide legal advice or prescribe a fire-safety solution. All numeric examples are hypothetical. The applicable OEM manuals, approved design, licensed standards, Vietnamese regulations and authority requirements must be checked for the actual project before award.

1. Define exactly what is warranted

Start by separating the asset layers. A “battery warranty” may apply only to cells or modules, while the usable plant also depends on racks, battery-management systems, HVAC, fire detection and suppression interfaces, DC cabling, power-conversion systems, transformers, switchgear, controls, metering and the energy-management system. Ask the bidder to map every warranted function to an equipment tag, responsible entity, warranty period, trigger and remedy.

The owner should not accept one undifferentiated statement such as “ten-year system warranty.” Require a warranty matrix with at least these rows:

• defects in materials and workmanship for each equipment package;
• retained energy or capacity at a named measurement boundary;
• charge and discharge power over an agreed duration and state-of-charge range;
• round-trip efficiency and treatment of auxiliaries;
• system availability, excluded hours and response time;
• software, cybersecurity, communications and remote-support availability;
• spares, replacement compatibility and support after a product revision;
• installation and integration workmanship; and
• remedies, labor, transport, recommissioning and repeated-failure treatment.

The industrial BESS owner-requirements brief can be used to keep these warranty rows aligned with the original procurement scope.

2. Match the warranty envelope to the real duty cycle

Warranty validity often depends on temperature, state-of-charge window, charge/discharge rate, depth of discharge, annual energy throughput, number of equivalent full cycles, idle time and permitted operating modes. These variables must come from the same factory use cases used for sizing. A warranty for daily peak shaving may not cover a system that is also asked to provide power-quality support, backup duty or frequent dispatch by an external optimiser.

Build a duty-cycle register that states, for each service:

• dispatch trigger and responsible controller;
• maximum charge and discharge power;
• energy duration and minimum reserve;
• expected annual operating hours and equivalent full cycles;
• state-of-charge limits and recovery rule;
• ambient and equipment-room temperature assumptions;
• simultaneous services and priority when commands conflict; and
• data retained to prove compliant operation.

For a detailed input method, see the BESS duty-cycle assumptions audit.

3. Check calendar, cycle and throughput limits together

A warranty may expire at the earliest of a calendar date, cycle count or cumulative throughput. Compare all three limits against the owner’s dispatch forecast. Do not treat “ten years” as the guaranteed life when another limit is expected to arrive earlier.

Hypothetical check: a 10 MWh system is forecast to complete 500 equivalent full cycles per year. A warranty ends at the earlier of ten years or 4,000 equivalent full cycles. The throughput limit is reached after:

4,000 cycles ÷ 500 cycles/year = 8.0 years.

If the owner expects 5,000 cycles over ten years, the proposed warranty envelope is short by 1,000 cycles. The solution may be a different operating plan, a larger energy capacity, an extended warranty or a revised commercial risk allocation. It is not valid to ignore the cycle cap and continue presenting the offer as ten-year coverage.

Also define how partial cycles are counted. The contract should state the equivalent-full-cycle method, energy boundary, sampling interval, treatment of auxiliary consumption and source of truth. A supplier-only cloud dashboard is not sufficient if the owner cannot export the raw data and reproduce the count.

4. Put retained-energy guarantees on one AC boundary

Module nameplate capacity is not the same as net AC energy available to the factory. A retained-energy guarantee should identify the test meter, state-of-charge endpoints, power level, rest periods, temperature conditions, auxiliary loads, transformer losses, data filtering and allowable uncertainty. If the guarantee is at DC rack terminals but the business case uses net AC energy, the owner carries the gap.

Hypothetical example: the initial acceptance test verifies 10.00 MWh of net AC-deliverable energy at the agreed meter. A year-ten retention floor is 80% under the specified test conditions. The year-ten contractual floor is:

10.00 MWh × 0.80 = 8.00 MWh net AC.

If a supplier instead applies 80% to an 11.0 MWh DC nameplate, the result is 8.8 MWh DC and cannot be compared with the 8.0 MWh net-AC floor without a documented loss bridge. The contract should prevent the measurement boundary from changing after award.

The end-of-warranty net AC energy test guide explains the acceptance evidence in more detail.

5. Turn operating exclusions into measurable limits

Exclusions are not automatically unreasonable. Batteries and power electronics need defined operating envelopes. The risk appears when an exclusion is vague, controlled only by the supplier, or inconsistent with the approved site design. Convert every exclusion into a measurable limit and assign responsibility.

Link these limits to alarms and owner-visible reports. If a limit is breached, the system should record start time, duration, affected equipment and cause. The warranty should distinguish an owner-caused breach from an OEM design, control or service failure.

6. Do not let site conditions become an unlimited escape clause

Factory sites can present heat, humidity, dust, corrosive atmosphere, flooding, vibration, pests, roof or yard constraints and difficult emergency access. The bidder sees these conditions during tender and must identify the design response. A general exclusion for “harsh environment” should not override an accepted site survey and approved equipment specification.

Require a site-condition schedule with design values, survey evidence and margins. Where corrosion class, enclosure protection, cooling redundancy or flood level matters, connect the assumption to the selected equipment and maintenance plan. If the supplier needs an environmental condition that the facility cannot reliably maintain, resolve that conflict before purchase.

For fire safety, the Ministry of Construction’s consolidated instrument 92/2026/VBHN-TT-BXD, dated 28 September 2026, consolidates the circular issuing QCVN 06:2022/BXD as amended. That building regulation does not by itself constitute a complete BESS fire strategy. The project team must confirm applicability, classification, authority requirements, separation, detection, suppression or control interfaces, drainage, ventilation, emergency access and operational response for the actual installation. A warranty exclusion must not be mistaken for regulatory acceptance.

7. Separate safety compliance from performance warranty

IEC 62619:2022 addresses safety requirements and tests for industrial secondary lithium cells and batteries, including stationary applications. IEC 62933-5-1:2024 addresses hazard identification, risk assessment and risk mitigation for grid-integrated electrical energy storage systems. IEC 62933-5-2:2025 adds electrochemical-system safety requirements over the BESS life cycle. IEC 62933-5-4:2026 provides selected lithium-ion BESS safety test methods based on the second edition of IEC 62933-5-2.

These references help define safety evidence; they do not create a project performance guarantee or replace the approved Vietnamese design. Likewise, IEC 62933-2-1:2017 provides general EES unit parameters and testing methods, while IEC TS 62933-2-2:2022 addresses application and performance tests and duty cycles. The owner must state which edition and clauses are contractually adopted and obtain the licensed documents.

A compliance certificate for a cell or module does not prove that the complete installed system satisfies its site interfaces. Trace serial numbers, certificates, drawings, firmware, protection settings and test records through the equipment hierarchy. The material traceability guide provides a practical records structure.

8. Control data, software and remote access

A performance warranty is difficult to enforce when the supplier controls the only dataset. Require owner access to time-synchronised raw data for meters, PCS, BMS, EMS, HVAC and alarms at a defined resolution and retention period. Document units, scaling, quality flags, clock source and missing-data treatment. The owner should be able to export evidence without an active supplier subscription.

Software and firmware are also warranty interfaces. Define approved versions, security support period, vulnerability notification, change authority, regression tests and recovery backups. An OEM-directed update should not erase event logs or restart the degradation baseline. An owner-requested control change should be assessed against the warranty before implementation, with the result recorded rather than assumed.

Remote access needs named roles, multi-factor authentication where supported, logging, approval windows and emergency revocation. The warranty should explain what support remains available if the owner suspends remote access during a cybersecurity incident.

9. Make maintenance exclusions proportionate

List maintenance activities with interval, responsible party, required competence, evidence and cure period. Separate safety-critical missed work from administrative defects. A late report upload should not automatically void coverage for unrelated equipment, while failure to maintain cooling or protective functions may have a direct technical consequence.

Where the supplier provides long-term service, define response and restoration metrics separately. Availability calculations should distinguish planned maintenance, supplier-caused outage, owner-requested shutdown, grid outage, force majeure and waiting for imported parts. Cap excluded planned hours and prevent double exclusion of the same event.

Use the factory electrical maintenance tender guide to connect access, permits, spares and evidence to the BESS service scope.

10. Specify a claim process that can actually work

A warranty without a usable claim process is weak risk transfer. State the notice channel, minimum evidence, acknowledgement time, diagnostic period, site-access rules, interim safety action and final remedy deadline. Preserve the owner’s right to make the system safe during an emergency.

Define who pays for:

• diagnostic labour and independent tests;
• removal, packaging, dangerous-goods transport and customs interfaces;
• replacement equipment, compatible firmware and engineering changes;
• installation, recommissioning and capacity/performance retest;
• temporary loss of service and agreed commercial remedies; and
• disposal or return of failed equipment and associated records.

Check whether the remedy is repair, replacement, augmentation, prorated credit or supplier election. A credit based on depreciated module value may not restore the factory’s contracted energy or power. Define repeated-failure and systemic-defect triggers, including the owner’s right to an engineering review when similar failures affect multiple racks.

11. Build the warranty schedule into FAT, SAT and operations

The warranty baseline should be created during delivery, not reconstructed after a failure. The ITP should identify hold and witness points for equipment traceability, firmware and settings, insulation and protection tests, communications, HVAC, alarms, emergency interfaces, capacity/performance tests and data export. FAT evidence must be linked to the equipment actually shipped; SAT must verify the installed interfaces.

At handover, collect the approved design basis, single-line diagrams, cause-and-effect matrix, equipment register, certificates, test reports, baseline capacity results, parameter backups, spares list, maintenance plan, training records and warranty contact matrix. Record unresolved punch items and state whether they affect the warranty start date.

Schedule periodic warranty health reviews before claim windows expire. Compare actual throughput, temperature exposure, availability, alarms, firmware status and retained energy with the contractual envelope. This is an evidence-control task, not a forecast of failure.

12. Owner bid-return checklist

1. Return a layer-by-layer warranty matrix for cells, modules, racks, BMS, PCS, HVAC, EMS, transformer and integration.
2. State the earliest-of calendar, cycles and throughput expiry rule.
3. Define capacity, power, efficiency and availability at named meter boundaries.
4. List every environmental, operating, maintenance, software and data exclusion.
5. Provide calculation methods for equivalent cycles, throughput and excluded hours.
6. Map each limit to owner-visible sensors, alarms and retained raw data.
7. Identify all Vietnamese regulatory and authority assumptions requiring confirmation.
8. Return FAT, SAT and periodic-test procedures with acceptance tolerances.
9. State claim notice, response, cure, retest and repeated-failure procedures.
10. Price labor, logistics, augmentation, replacement and extended coverage separately.

FAQ

Is a ten-year BESS warranty necessarily ten years of usable coverage?

No. Coverage may end earlier when a cycle or throughput cap is reached, and retained-energy coverage may apply only within specified operating conditions. Compare all limits with the forecast duty cycle.

Should the owner accept a DC capacity guarantee?

Only if the commercial model and acceptance boundary are also DC. For a factory using net AC energy, require a documented bridge or a net AC guarantee that includes the relevant auxiliaries and conversion losses.

Can one temperature excursion void the warranty?

The contract should define sensor location, threshold, duration, cause and affected equipment. It should also distinguish an owner-caused site breach from a cooling, control or design failure under supplier responsibility.

Does IEC compliance prove the complete BESS is suitable for the site?

No. Standards support specified safety and performance evidence, but the installed system still requires project-specific integration, Vietnamese regulatory checks, authority acceptance and verified site interfaces.

Request an owner-side BESS warranty review

QuangAnhcons can structure a BESS warranty matrix, duty-cycle register, AC test boundary, exclusions schedule, FAT/SAT evidence plan and claim workflow for an industrial procurement. Share the technical offer, intended dispatch profile, site conditions and warranty draft through an approved confidential channel; do not publish customer names, prices or security credentials.

Discuss a Vietnam industrial BESS warranty review