Draft Details

1.General

This Standard provides an Electrical Energy Storage System (EESS) testing protocol for quality assurance and reliability programs. It is intended to be used by code officials, financial institutions and insurers, first responders, developers, independent engineers, manufacturers and other relevant stakeholders in the Energy Storage System industry. It provides best practices for an EESS testing protocol of a representative energy storage system for quality and reliability assurance programs.

2.Intended use

This Standard is intended to be a stand-alone document that does not interact with other safety or performance standards as it is intended to focus on reliability and quality assurance for long-term durability. Market practices as they currently exist might require independent quality assurance and reliability testing and due diligence for energy storage systems.

3.Inclusions

The individual test legs in the protocol of this Standard have been designed to reproduce incidences and failures of a representative energy storage system that has been seen in the field or potentially could be seen in the field. Data generated from testing will reflect the behavior, reliability, and durability of the system and its components during natural or accidental occurrences of conflagration, inundation, convulsion or other related incidences, as well as reflect the harsh environmental conditions during operation. This data is intended to be used as part of an assessment for bankability and insurability of energy storage systems.

4.Exclusions

This Standard does not apply to the following:

a) evaluating or rating the Individual components used in the construction of an EESS; Note: Individual components are evaluated using their own standards.

b) installation requirements except those for installation manuals and c) installation documents provided with the EESS; and

c) uninterruptible power system that

i) fall under the scope of UL 1778; or

ii) use lead-acid or nickel-cadmium batteries.

5.Terminology

In this Standard, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy to comply with the standard; “should” is used to express a recommendation or that which is advised but not required; “may” is used to express an option or that which is permissible within the limits of the standard.

Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.

Notes to tables and figures are considered part of the table or figure and may be written as requirements.

Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.