SNL EPRI Data Guide SAND V2
SNL EPRI Data Guide SAND V2
SAND2021-8492
Printed
Prepared by
Sandia National Laboratories
Albuquerque, New Mexico
87185 and Livermore,
California 94550
Electrical Energy Storage Data
Submission Guidelines, Version 2
3002022119
SAND2021-8492
NOTICE: This report was prepared as an account of work sponsored by an agency of the United States
Government. Neither the United States Government, nor any agency thereof, nor any of their
employees, nor any of their contractors, subcontractors, or their employees, make any warranty,
express or implied, or assume any legal liability or responsibility for the accuracy, completeness, or
usefulness of any information, apparatus, product, or process disclosed, or represent that its use would
not infringe privately owned rights. Reference herein to any specific commercial product, process, or
service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply
its endorsement, recommendation, or favoring by the United States Government, any agency thereof, or
any of their contractors or subcontractors. The views and opinions expressed herein do not necessarily
state or reflect those of the United States Government, any agency thereof, or any of their contractors.
Printed in the United States of America. This report has been reproduced directly from the best available
copy.
This is an EPRI Technical Update report. A Technical Update report is intended as an informal report of
continuing research, a meeting, or a topical study. It is not a final EPRI technical report.
NOTE
For further information about EPRI, call the EPRI Customer Assistance Center at 800.313.3774 or
e-mail [email protected].
Electric Power Research Institute, EPRI, and TOGETHER…SHAPING THE FUTURE OF ELECTRICITY
are registered service marks of the Electric Power Research Institute, Inc.
Copyright © 2021 Electric Power Research Institute, Inc. All rights reserved
ACKNOWLEDGMENTS
Contributors from Sandia National Laboratories (SNL) were supported by the U.S. Department
of Energy, Office of Electricity, Energy Storage Program under the direction of Dr. Imre Gyuk.
Pacific Northwest National Laboratory (PNNL), the Electric Power Research Institute’s (EPRI)
Energy Storage Integration Council (ESIC) participants, and Xanthus Consulting provided
technical guidance, insight, and review during the development of this report. Sandia National
Laboratories (SNL) and EPRI would like to acknowledge specifically the following personnel:
EPRI ESIC Task Force
Pacific Northwest National Laboratory
Vilayanur Viswanathan
Charlie Vartanian
Alasdair Crawford
Phil George
Matt Paiss
Sandia National Laboratories
Waylon Clark
Xanthus Consulting
Frances Cleveland
This report describes research cosponsored by EPRI and SNL.
SNL and EPRI collaborated with PNNL in producing some of the material in the report. SNL
and EPRI acknowledge that portions of the report might have been previously published by the
Government and are now believed to be in the public domain.
This publication is a corporate document that should be cited in the literature in the following
manner:
Electrical Energy Storage Data Submission Guidelines, Version 2. Electric Power Research
Institute (EPRI) and Sandia National Laboratories (SNL): 2021. 3002022119.
iii
ABSTRACT
Energy storage technologies are positioned to play a substantial role in power delivery systems.
They have the potential to serve as an effective new resource to maintain reliability and allow for
increased penetration of renewable energy. However, because of their relative infancy, there is a
lack of knowledge about how these resources truly operate over time. A data analysis can help
ascertain the operational and performance characteristics of these emerging technologies.
Rigorous testing and a data analysis are important for all stakeholders to ensure a safe, reliable
system that performs predictably on a macro level. Standardizing testing and analysis approaches
to verify the performance of energy storage devices, equipment, and systems when integrating
them into the grid will improve the understanding and benefit of energy storage over time from
technical and economic vantage points.
Demonstrating the life-cycle value and capabilities of energy storage systems begins with the
data that the provider supplies for the analysis. After a review of energy storage data received
from several providers, some of these data have clearly shown to be inconsistent and incomplete,
raising the question of their efficacy for a robust analysis. This report reviews and proposes
general guidelines, such as sampling rates and data points, that providers must supply for a
robust data analysis to take place. Consistent guidelines are the basis of a proper protocol and
ensuing standards to (1) reduce the time that it takes for data to reach those who are providing
the analysis; (2) allow them to better understand the energy storage installations; and (3) enable
them to provide a high-quality analysis of the installations. The report is intended to serve as a
starting point for what data points should be provided when monitoring. Readers are encouraged
to use the guidance in the report to develop specifications for new systems, as well as enhance
current efforts to ensure optimal storage performance. As battery technologies continue to
advance and the industry expands, the report will be updated to remain current.
Keywords
Energy storage data
Storage controls
Storage performance
v
ACRONYMS
vii
O&M operations and maintenance
PCC point of common coupling
PCS power conditioning system
PF power factor
PNNL Pacific Northwest National Laboratory
Psi pounds per square inch
Pst Perceptibility
RPM revolutions per minute
SCADA supervisory control and data acquisition
SNL Sandia National Laboratories
SOC state of charge
SOH state of health
THD total harmonic distortion
V voltage
viii
CONTENTS
ABSTRACT ..................................................................................................................................V
ACRONYMS ...............................................................................................................................VII
1 OVERVIEW............................................................................................................................. 1-1
ix
6.5.3 Flywheel .............................................................................................................. 6-8
6.5.4 Compressed Air .................................................................................................. 6-8
6.5.5 Pumped Hydro .................................................................................................... 6-9
6.6 Sample Points List—General Energy Storage Three-Phase System .......................... 6-9
x
LIST OF FIGURES
xi
LIST OF TABLES
xiii
1
OVERVIEW
As energy storage technologies promulgate, the need to accurately understand their reliability
and performance has become paramount. Indications of storage performance are directly tied to
performance warranties and grid reliability expectations. As storage becomes more prevalent, the
grid will become more dependent on storage reliability to ensure overall grid reliability. When
reviewing data from fielded energy storage systems (ESS), it quickly becomes clear that, despite
the perceived best efforts and intentions from the provider, the data provided are not always
sufficient or accurate enough to perform a robust reliability and performance analysis. Complete
and accurate data are necessary to truly evaluate the ESS. The four main problems addressed by
this report are (1) required data points, (2) sampling rates of the data, (3) importing data into a
structured database that allows a complete analysis, and (4) managing data to ensure alarms and
other pertinent data are acted upon appropriately by assigned personnel. Additionally, a new
topic of power quality issues stemming from the DC side of systems is introduced.
If the provider of the information can supply data consistent with the following proposed
guidelines, a robust analysis can be performed without the need to petition the provider for
additional data. There also needs to be recognition that too much data may be inefficient and
overwhelm acquisition, data transport, and subsequent analysis systems. Therefore, the points
and sampling rates are described in a posture to optimize the amount of data needed.
This guideline will serve to define needed parameters. Many attributes of data collection will
ultimately need to be addressed. These include:
• With valid amounts of data in place, it becomes possible to further understand system
operation and allow an in-depth analysis on an independent basis of vendor performance
claims. Numerous research efforts are underway to develop these independent techniques.
• It is also necessary, when prescribing data for reliability and performance assessment, to be
cognizant of data that can be used for safety monitoring and allow export of relevant data to
relevant parties.
• With cybersecurity, data collection must follow security best practices in collecting,
accessing, and transmitting information.
• The data acquisition and the attendant optimal data set therefore need to be classified
according to need, as follows:
– Safety
– Warranty and performance
– Maintenance
– R&D
1-1
Overview
• While standards can ultimately describe the data needed for a robust analysis of performance,
the scope of implementing the needed sensors and systems needs to be detailed and assigned
as the storage vendor, site owner, and system operator responsibilities.
• A typical storage system can employ numerous computer platforms that, in themselves, can
process data and minimize the need to transport data upstream to a historian. Definition is
needed on these downstream platforms and who supplies them and how they are operated.
1-2
2
INTEROPERABILITY, STANDARDS, AND GUIDELINES
The framework under which storage data are acquired, stored, and analyzed is an important
consideration. Successfully performing a data analysis requires communication between
numerous devices and other actors, such as system operators and analysts. Many of these
devices communicate in different protocols. Storage components can use CANbus to internally
communicate and SunSpec Modbus to communicate between modules or devices. Utility
supervisory control and data acquisition systems typically operate using the IEEE 1815 (DNP3)
protocol in the United States or IEEE 2030.5 in California, and International Electrotechnical
Commission (IEC) 61850 internationally. In many cases in the United States, the DNP3 protocol
uses the MESA specification, which maps the IEC 61850-7-420 distributed energy resources
(DER) object model to DNP3 data points, as defined in the DNP3 Application Note (AN2018).
Standards that govern how ESS communicate are currently evolving to enable more complete
interoperability. This standardization is based on the IEC 61850-7-420 data object standard that
governs how data are defined, named, and structured. Some protocol standards then map these
data objects directly (for example, IEC 61850-8-1, IEC 61850-8-2, and MESA), whereas others
have a looser mapping (for example, IEEE 2030.5 and SunSpec Modbus).
This report aims to provide information on these existing and still-developing standards efforts
in order to push a uniform stance on storage data and performance analysis, such as the MESA
effort, which is currently being updated to reflect a better understanding of the communication
requirements as utility-scale storage systems and combined photovoltaic (PV) plus storage
systems are being implemented. Examples of standards under development that can be informed
from the report include IEEE 1547.9 (Interconnection of ES-DER Guide) [1], P2686 (BMS
Recommended Practice) [2], P2688 (ESMS Recommended Practice) [3], and the forthcoming
ANSI C12.32-2021 standard, which is addressing DC metering.
Recent guidance from the North American Electric Reliability Corporation (NERC) is also
touching on data availability and lack of uniformity [4]. A recent report, Energy Storage:
Impacts of Electrochemical Utility-Scale Battery Energy Storage Systems on the Bulk Power
System, highlighted the lack of uniformity seen in storage data.
Key findings and recommendations from the NERC report included [4]:
• Data on battery storage tends to be non-uniform and lacking in consistency across reporting
entities necessitating a need for better reporting mechanisms for BESS data.
• As regulators provide more incentives for the viability of battery storage to provide capacity
and energy, system planners must adequately plan the system for a projected large increase
in BESS, understanding the impact of size, location, and operating characteristics on
maintaining the reliable operation of the grid.
2-1
Interoperability, Standards, and Guidelines
• Entities that compile battery data information must enhance both their data collection
methods as well as their reporting methods. As energy storage systems become more
prolific, accurate and timely data will be essential for both system planners and operators.
The Institute of Electrical and Electronics Engineers (IEEE) should update the IEEE
Standards to reflect any implications of battery storage systems. The GADS Working Group
should ensure that battery storage is accurately reflected in their data capturing protocols.
The current report is therefore structured to provide guidance on energy storage resources,
a subset of the DER classification. It will serve to inform further work on the MESA updated
specifications, IEEE 1815 and 2686 and various other standards, guides and recommended
practices, in part, as well as emerging market rules, guidance documents, and standard
specification updates produced by the Electric Power Research Institute (EPRI) Energy
Storage Integration Council (ESIC) and the Department of Energy.
2-2
3
DATA RESPONSIBILITY AND RELEVANCE
In framing the specific attributes of acquiring and analyzing data, it is important to create a
structure that assigns responsibility for the different project phases and elements placed. This
structure should be thoroughly developed early in the project to allow all stakeholders to
understand roles, assignments, and system requirements in both the design and operational phases.
The following sample high-level responsibility matrix can serve as a template for this purpose.
Table 3-1
Data Responsibility Matrix
Project Equipment
Integrator Operator Maintenance Analyst
Deliverable Vendor
Data System
X X X X X
Design
Installation X X X
Commissioning X X X X X
Operation X X X X
Analysis X X X
As is evident in even a high-level approach, all parties need to be intricately involved in the
design process as well as the commissioning effort. When the system is operable, the maintenance
activities need to be well coordinated with data acquisition and subsequent analysis. Indeed, the
analysis effort may, in itself, inform operational and maintenance activities [5].
The data and associated metrics of performance can also be classified in terms of relevance
to specific project activities throughout the project life cycle in relation to business metrics.
Figure 3-1 classifies metrics derived from sensors and related calculations to a continuum of
business metrics.
3-1
Data Responsibility and Relevance
Figure 3-1
Business Relevance of Storage Performance Metrics
3-2
4
OVERALL SYSTEM REQUIREMENTS
Before the data can be supplied, a system must be in place for effective data transfer. Figure 4-1
shows the overall high-level control architecture used for a larger system with an associated
architecture for data collection.
Figure 4-1
Data and Control Architectures
More detailed architectures are presented in Appendix A (Figure A-1) that point out the inherent
complexity and numerous systems that are typically involved in storage operation.
In most cases, a sophisticated off-site data historian system is preferred due to the tools that can
be used for a deep analysis. An on-site historian can be used to compile data for transport via
alternative means or on an as-needed basis. The system can be broken down into the following
elements to allow an understanding of requirements:
• Battery (battery management system [BMS]) in the storage unit. This includes all
necessary points associated with the storage device(s), Power Conditioning System (PCS),
metrology, and all installed power meters. Specific data points collected for the storage
unit(s) are discussed in Section 6.
• Master station site controller (DNP3 or IEC 61850-based outstation). The data collection
device must also have a backup connection to the primary with a speed of at least 10 Mbps,
less than 200 ms of latency, and less than 5% packet loss.
4-1
Overall System Requirements
• Data transport. Primary link for the data collection to and from devices via high-speed
wired or wireless connection with a speed of at least 10 Mbps for wired and 5 Mbps for
wireless with less than 1% packet loss. Standard connections of this type include fiber optic,
Category 6 or 5e ethernet, RS232, and/or cellular. It should be noted that higher upload
speeds may be difficult to attain in certain cell coverage areas. Strategies for lower cellular
transmission rates need to be researched further.
• Off-site historian. Data collection software, such as the historian, database, and operating
system, must be the latest version and kept up to date throughout the project to ensure that
data and cybersecurity policies are met. Data collection devices must have an onboard
memory of at least 60 days with the same resolution of that being collected. Note that there
may be more than one historian where an on-site historian can collect and analyze data and
report out, lessening the burden on data transport. This could be coupled with an off-site
historian that is connected to numerous systems.
• Off-site control systems. These are the utility or market participant control systems that
ingest external or grid signals and instruct downstream control systems. This could include
grid operations controls adapted to accommodate storage as a grid resource.
4-2
5
SAMPLING RATES OF DATA
For the system being monitored, there are typically three different kinds of sample rates. The
first is the data acquisition system sample rate: the rate at which the system samples a specific
data point. The second rate is the reporting sampling rate: the rate at which the logged data are
to be transmitted to the analyst. The last sample rate is the rate at which the system collects data
during a triggered event. Triggered events are identified using a set of boundaries for a given
data point which, if violated, cause the system to collect the data at their highest resolution. The
required resolution for particular triggered events will be addressed, in part, in later sections on
alarm management and DC power quality.
The data acquisition sample rate can typically range from 1 second to 1 hour, and it is important
to consider the optimal need, balancing the quantity of data needed against the bandwidth and
data storage available. Many power-based values or basic voltages and currents are best obtained
on a 1-second basis to understand subcomponent (battery cell) degradation and power
characteristics. Energy-based values, such as kilowatt-hour(s) and measured temperatures, do not
necessarily need to be collected at intervals smaller than 15 minutes. High resolution is typically
performed in subcycle or greater than 180 Hz to capture waveform data, which can be stored and
assessed locally.
5-1
6
GENERAL SYSTEM DATA POINTS
The following sections describe the data points that should be collected to ensure in-depth
performance assessments for the entire ESS and specific technologies. See Section 7 for more
discussion on the implications of collecting limited versus in-depth amounts of data. These data
points need to be collected to evaluate the performance, safety, and longevity of the ESS. All
data points need to be synchronously timestamped for accurate modeling and analysis.
6.1 Electrical AC
The AC data points are important as they inform the engineer/analyst of the amount of power
coming in and out of the entire ESS. With these data points, they can find important system
statistics that indicate what the system is putting back into the grid as well as overall round trip
efficiencies (RTEs) and capacity fade. Auxiliary load data are also collected to understand the
parasitic loads associated with various technologies. Below are the listed data points.
Note: It is important to designate charge versus discharge values for storage where the standard
nomenclature is positive for discharging, negative for charging [1] [6].
6.1.1 Considerations
When designing the data acquisition system and the surrounding infrastructure, which will be used
to collect and transmit the AC data, the following items should be considered:
• Ownership of meters and responsibility for programming, reporting, and maintaining data.
• Ability to capture events based on exceeding meter/parameter thresholds and how to
transport, store, and analyze. Some meters are capable of recording events on a subcycle
basis, and the quantity of data captured may be large. It may be best to store these events
separately from the historian.
• Ability to host large data sets on site. If event recording is enabled, means to store the data
(potentially in the recording device data buffer) need to be addressed. These files are
typically not suited to communication protocols and are too large for data transport, unless
fiber connections are in place.
6-1
General System Data Points
6-2
General System Data Points
In addition to the previous data points, the listed points below should also be provided for their
relation to AC as indicators of power quality:
• Flicker (Pst)
• System frequency (Hz)
• Total harmonic distortion (THD) (dBm)
6.2 Electrical DC
DC data points are collected at the DC side of the PCS. These data points allow insight into
the performance of the energy storage technology behind the PCS, including items such as
degradation and RTE. Without access to DC measurements, an accurate assessment of battery
performance is not possible. There are ESS such as pumped hydro that may not have an
electrical DC data point to collect and may ignore collecting the data points described in the
following sections.
6.2.1 Considerations
When collecting DC data, the following items should be considered during the data acquisition
design phase and collection:
• Number of points needed for cells in a module to accurately get average as well as maximum
and minimum values, including temperatures. Number of points should accurately provide a
representation of behavior of all cells for which data are not being collected. For large
installations in which multiple ESS are being operated, sampling methods such as simple
random, stratified random, or cluster sampling can be used. The sample set should be
representative of all ESS in operation.
• Accuracy of sensors (see Section 8) and overarching BMS calculations.
• Processing that the BMS does, to potentially compile points, versus systems upstream, such
as a site controller or historian-based analytic engine.
• Increasing interest in DC power quality. Recent focus has been placed on the potential for
DC components, especially DC/DC converters, to introduce power quality issues, even on
the AC side. Section 10 below further discusses DC power quality.
6-3
General System Data Points
Figure 6-1
Flowchart for Battery Data Points
6-4
General System Data Points
6.3 Conditional
Environmental and energy market points are useful because they allow the engineer to see the
conditions the system is operating in and how these conditions affect the system. Financial
market conditions like electricity price/cost are also included in this set because they help with
the economic analysis of the system and its feasibility.
6.3.1 Considerations
The following are items that need to be considered when collecting conditional data:
• Setpoints may be required to allow further understanding relating to data analytics.
These would be classified as Analog Outputs according to the DNP AN 2018 document.
• Temperature alerts are needed for safety concerns. Prioritization of alarms is available at
three levels, and a thorough analysis needs to be given to thresholds and associated priority
of alarms.
• Humidity measurements are also important in indicating the performance of environmental
control systems. Both internal to system and ambient (outside) measurements are needed to
ascertain internal conditions. Lack of proper control of internal humidity can lead to
condensation of water vapor on surfaces that could lead to potential safety issues.
6-5
General System Data Points
• Operating mode. ESS have many modes of operations, which need to be collected to
determine proper functionality and performance. This can include operating modes such as
startup, standby, and load following.
6.4.1 Considerations
Points listed in Section 6.4.2 are equally as important for the analysis of the system as they let
the operators know when and where there is a problem. Stakeholders can see how the associated
data are affected by the problem and/or whether the data should be omitted. Some of the points
in this section can be accessed through an analog or digital signal, whereas others are accessed
through logs such as maintenance logs, highlighted in Section 6.4.3. The following is a list of
considerations when determining other signals to collect for analysis:
• Prioritizing which alarms to send through for direct action and which alarms to send for
condition monitoring. Alarm data may need to be filtered to limit the number of data points.
See the alarm management discussion below (Section 9).
• There needs to be an indication to alarm recipients if the system has lost connectivity.
• Delivery of maintenance or other logs, either electronically or via hard copy, to the analysts
needs to be discussed and determined.
6-6
General System Data Points
6-7
General System Data Points
6.5.3 Flywheel
A flywheel is an ESS that consists of a spinning mass attached to a shaft that converts
mechanical energy into electrical energy. Specific data to be collected for this technology are
as follows:
• Speed of flywheel (RPM)
• Vacuum pressure (psi)
• System temperatures (°C)
• Vibration sensor (m/s2)
6-8
General System Data Points
6-9
General System Data Points
Table 6-1
System Data Points
1 = Closed
Relay Status Binary ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
0 = Open
6-10
General System Data Points
1 = Closed
Breaker Status Binary ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
0 = Open
6-11
General System Data Points
Value, max,
Outside Temperature ºC ≥1 Sample/Minute ≥1 Sample/Minute ≥1 Sample/15 minutes
min, avg
Value, max,
Outside Dew Point ºC ≥1 Sample/Minute ≥1 Sample/Minute ≥1 Sample/15 minutes
min, avg
Value, max,
Internal Enclose Humidity % ≥1 Sample/Minute ≥1 Sample/Minute ≥1 Sample/15 minutes
min, avg
Value, max,
Precipitation mm ≥1 Sample/Minute ≥1 Sample/Minute ≥1 Sample/15 minutes
min, avg
(mph,
Wind Speed and Value, max,
cardinal ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
Direction min, avg
direction)
Electricity Sample rate associated Sample rate associated Sample rate associated
$/kWh Value
Price/Cost with price data with price data with price data
(kW,
Value, max,
Power Request kVAR, ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
kVA)
Integer value
related to
Operating Mode Integer ≥1 Sample/5 Minute ≥1 Sample/5 Minute ≥1 Sample/15 minutes
operating
mode
6-12
General System Data Points
Tablature
Maintenance Logs Per manufacturer Monthly Monthly
report
Communication 1 = Online
Integer ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
Conductivity Disruptions 0 = Offline
6-13
General System Data Points
Table 6-2
Technology-Specific Data Points
Cell-Based Battery
Value, max,
Cell Resistance Ohms ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Flow Battery
Value, max,
Cell Temperature ºC ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Anolyte Flow(s) L/min ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Anolyte Tank Level(s) L ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
6-14
General System Data Points
Value, max,
Catholyte Flow(s) L/min ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Flywheel
Value, max,
Speed of Flywheel rpm ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Vacuum Pressure psi ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Vibration Sensor m/s2 ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
6-15
General System Data Points
Compressed Air
Value, max,
Inlet Air Pressure psi ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Outlet Air Pressure psi ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Speed of Turbine rpm ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
System Temperature(s) ºC ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
System Fuel Value, max,
(MMBtu/kWh) ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
Consumption min, avg
Value, max,
System Emission Data ppm ≥1 Sample/15 Minutes ≥1 Sample/15 minutes ≥1 Sample/hour
min, avg
Pumped Hydro
Value, max,
Reservoir Height m ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
6-16
General System Data Points
Value, max,
Water Pump Speed rpm ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
System Temperature(s) ºC ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Value, max,
Turbine Inlet Pressure psi ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
min, avg
Turbine Outlet Value, max,
psi ≥1 Sample/Second ≥1 Sample/Second ≥1 Sample/15 minutes
Pressure min, avg
6-17
General System Data Points
Q(VAR) x x x x x x x x
Vrms (V) x x x x x x x x
Irms (A) x x x x x x x x
Relay x x x x x x x x
Status
Breaker x x x x x x x x
Faults/Alarms x x x x x x x x
Flicker (Pst) x x x
Quality
Power
Frequency (Hz) x x x
THD (dBm) x x x x
Outside Temperature (Degrees Celsius) x x x x x x x x
Outside Dew Point (Degrees Celsius) x x x x x x x x
Conditional
x x x x x x x x
Operating Mode
Figure 6-2
Data Points Mapped to Storage Functions
A list of the DER autonomous functions that a storage system can provide is shown in Table A-1
of Appendix A. As storage system assume numerous duties it is increasingly important to
uniformly label the duties being enabled and or executed to ensure correct understanding of
which control mode was enabled and pursued, especially if numerous modes of operation are
being pursued. It displays these functions mapped to overarching and regional standards.
6-18
7
DATA QUALITY AND TRANSMISSION
7.1 Overview
After the data are measured and logged, they shall be sent to the analyst by the provider in 24 hours
or less. If the data from a time period are aggregated into a single file, like daily data, the provider
should have 24 hours from the last sample to make the data available for the analyst.
When the data are transmitted, they should be sent in a timestamped row-column format where
one of the columns documents each row’s unique timestamp with all other columns relaying
measurements and status values for the corresponding timestamp.
It may be necessary to create multiple files for logging data within a given interval. Each file
may logically represent a subsystem within the larger storage system (for example, data from
controllers, meteorological stations, containers, racks, modules, cells). The files should abide
by an intuitive naming scheme. For instance, each file name should contain the date, a short
descriptor for what subsystem it represents, and, if there are numerous files produced in a day,
a number designating which file it is for that day. An example for a group of files under this
naming scheme might look like the following:
• Bank1_20190111_1.csv
• Bank1_20190111_2.csv
• Bank1_20190111_3.csv
A “data details” document should accompany the first data set (and any subsequent changes to
the reported data) and should provide the following information to support the interpretation,
storage, and analysis of the data. This includes:
• A short description of the data in each column
• Corresponding units
• All possible values with a description of what the values represent, if the data point is an
enumerated type
If a software/firmware update will in any way affect the way data are logged by the system, the
vendor must alert the operator of the expected changes. If new data points will be added to the
log files, the columns should be appended to the end of the file. A new “data details” document
should also be provided by the vendor for added visibility into the changes.
To ensure privacy and protection of proprietary information, a possible non-disclosure agreement
can be signed between the analyst and the provider of data. This, combined with the read-only
access for the analyst, will ensure that data will not be shared with anyone else, and the provider
can remain confident that the information will remain private.
7-1
Data Quality and Transmission
If the provider, upon review, finds that the data quality is compromised due to any planned or
unplanned outages, the provider should request or initiate repair of the system within 24 hours to
ensure the smallest downtime. In addition, the provider should tag the data loss interval in a log
provided to the engineer. To combat data loss due to network issues or outages, the vendor shall
implement on site data storage from where compiled data can be pulled later once connection
is reestablished.
The system also needs to account for daylight savings time in cases where revenue meters
automatically adjust. Data should be timestamped using methods such as Universal Time
Coordinated or similar.
7-2
Data Quality and Transmission
Figure 7-1
Sparse and Robust Data Sets Versus Temporal Resolution
A relatively sparse data system may only report AC-level power and a handful of battery-specific
details like SOC and operating mode every minute, while a robust system may report data at the
point of interconnection, at all major DC junctions, and for all cells each second. These data can
include both direct measurements (for example, power, temperatures, voltages, currents, SOC,
state of health), control information (for example, setpoints), and statuses (for example, errors,
warnings, setpoints), which extend the realm of possibilities for robust data systems. Unless
specified on the project inception, the owner and operators may not have access to the data
needed for an independent performance assessment.
7-3
8
SENSOR AND COMPUTATIONAL ACCURACY
Inaccurate sensors lead to poor quality data and hence inaccurate analysis and misleading
representation and calculated metrics of system condition. Inaccuracies can also be introduced
through calculation routines where significant digits are truncated, or the equations used are
inaccurate in themselves. Lack of clarity on proprietary algorithms can further obfuscate a firm
understanding of storage performance.
8-1
Sensor and Computational Accuracy
• The operational SOC and operational capacity calculations, along with their parameters,
should be made available to the device owner through the procurement process. This
calculation should specify whether it uses values reported by a device management system
whose algorithms are proprietary or unknown.
8.1.1.1 New Standard: ANSI C12.32-2021, Electricity Meters for the Measurement of
DC Energy
This new standard is due to be published in 2021 and is poised to establish performance criteria
for revenue grade DC watt-hour meters and demand meters. It is also slated to target, similar to
ANSI AC meter standards, various accuracy and current classes and other similar attributes. This
new standard should be integral in understanding DC power and energy measurements.
8.1.1.2 U.S.-Based
• ANSI C12.1-2014 – National Standard for Electric Meters – Code for Electricity Metering
which covers the testing and installation of the meter [11] [3].
• ANSI C12.20-2015 – American National Standard for Electric Meters for Electricity Meters
– 0.1, 0.2, and 0.5 Accuracy Classes. This revision introduced a new 0.1 accuracy class.
Previous versions had a 0.5 accuracy (error rate <0.2%) and 0.2 accuracy (error rate <0.1%).
The new 0.1 accuracy class dictates an error rate of <0.05% [12, 13].
8.1.1.3 International
Similar to the ANSI Class structure, the IEC standards applicable to meter accuracy include:
(1) IEC 62053-21 Class 1 and (2) IEC 62053-22 Class 0.5, 0.2, and 0.1 (ed. 2) [14, 15].
8-2
Sensor and Computational Accuracy
There are a variety of humidity sensors available with a wide range of accuracy. It is important to
understand not only the needed accuracy, but also any drift that may be experienced over time. In
containerized systems, understanding humidity may be important with respect to the prevention
of condensation on surfaces that are cooler than the dew point of the surrounding air. This should
be a key consideration in humid environments with regard to O&M practices and when open
doors can introduce humid air.
Figure 8-1
A 50-MWh/Year Cumulative Energy Error for ANSI 0.1, 0.2, and 0.5 Class Meters
The relative expanse of the error experienced in Figure 8-1 would be expected to broaden
significantly with the use of less-than-revenue-grade metering.
8-3
9
ALARM MANAGEMENT
9-1
Alarm Management
Depending on the ESS site, several site employees may have access (physically, or at least
visually) to a site. They may identify or be able to initiate alarms and also may act as first
responders. Their education and training regarding ESS guidelines can support safe and
continuous operations. The general public may also have access to a site and present the same
opportunities (and risks) as site employees. Robust and clear signage can help communicate
alarm acknowledgment and response to this group.
The fire service is trained in general emergency response, though may be unaware of ESS-
specific issues, and may be volunteers. Specific training should be conducted with respect to
response to ESS incidents, and the training should be periodically repeated to address any
turnover or staff changes.
An alarm management team can be helpful to periodically review alarms for validity and
importance. The team can include participants from each of the above roles and develop
guidance for alarm communications and responses.
9-2
Alarm Management
9-4
Alarm Management
Table 9-1
Alarm Management Matrix
Possible Possible
Responder Response
Manual Remote
General Public
Site Employee
Manual Local
Fire Service
Automated
Operator
Vendor
SME
Action Design Consideration Benefit Concern/Hazard When to Use
9-5
Alarm Management
9-6
Alarm Management
9-7
Alarm Management
9.7 Prioritization
Prioritization of alarms requires a thorough assessment through the alarm management
framework and may be further refined using the MESA architecture. This carries three levels of
priority, and embedded sensors or indicators can be mapped as an option to these priority points.
Relying on sensors alone may not be sufficient to detect hazardous situations. It is important to
note the difference between monitoring discrete sensors versus monitoring trends that may be
computationally derived. These trends can potentially indicate situations that can be ameliorated
before a hazard situation arises. This would include off-normal temperature and voltage and
current fluctuations, as well as higher-than-normal cell balancing.
9-8
10
DC POWER QUALITY
Traditionally, solar or ESS have been composed of a solar array or battery coupled directly to an
inverter. While AC power quality concerns did and do occur with these arrangements, DC power
quality concerns have not typically been considered in such systems due to PV modules or
batteries presenting a relatively constant impedance to the inverter.
However, improved efficiency, lower interconnection costs, and regulatory considerations have
driven some integrators toward DC-coupled topologies where more than one source is coupled
to a single inverter, generally using one or more DC:DC converters. Increasing utilization of DC
coupling for some flow-based storage or hybrid ESS, such as solar plus storage, is creating greater
complexity. DC coupling is also becoming prevalent in electric vehicles (EVs) and other industries.
Solar or storage inverters are power converters that have not historically been designed to
interface with active sources such as DC:DC converters. Typically, inverters have been
connected to passive components such as PV modules on one side and a transformer with known
impedance on the other. But where converters are coupled and regulated, they become constant
power loads and may present negative impedance characteristics that can destabilize control
functions and lead to resonance. As a result, negative impedance instability or other resonances
can occur where converters are connected. Interactions between converters can occur in multi-
converter renewables architectures and industrial motor drives but perhaps are best known in
the EV space.
Undesirable resonances in multi-converter DC systems are, at their core, stability issues. In some
cases, these issues may lead to instability, in which case the magnitude of oscillation increases
until hardware or firmware limits are exceeded. This can result in equipment damage and/or
nuisance tripping. Perhaps more problematically, resonant behaviors may lead to a marginally
stable state in which oscillation persists at a constant magnitude. If the magnitude of the
resonance never reaches the trip threshold of protective devices, these issues may remain
permanently undetected. High-frequency oscillations reduce system efficiency and decrease
component reliability. Additionally, these resonances can propagate to or from the AC side
connection of a system, negatively impacting grid power quality. Such issues may remain
undetected in commercial systems if inverter tripping does not occur, but may yield lower
than expected efficiency, reduced component life, and undesirable grid power quality.
The underlying phenomena responsible for stability issues in multi-converter DC systems
are well-known in the specific power quality arena, and a variety of effective strategies for
mitigating their influence are available in the literature. Impedance-based stability criteria are
a well-established family of methods for predicting, describing, and mitigating undesirable
interactions between converters.
10-1
DC Power Quality
Despite the maturity in this area of DC system stability theory, addressing emergent stability
issues in the field remains challenging. Accurate knowledge of converter and system
impedances, obtained either from model-based expressions or empirical measurements, is
required to apply impedance-based stability criteria. These criteria are most easily employed
when, for example, a multi-converter system is being designed from the ground up with full
knowledge of constituent converter topologies, control structures, and gain parameters. In
practice, this depth of information is not always available. This is particularly true in the
emerging area of DC coupled systems for grid-tied storage and distributed resources, where
complex multi-converter structures are assembled from general purpose power conversion
devices by a system integrator. When problematic interactions appear during integration, their
root cause is often obscured by a “black box” representation of the converters, complicating the
diagnosis of the issue.
New tools, both in terms of instrumentation and computational methods, are needed to support
the detection, identification, and resolution of DC power quality issues in the field. Because
resonant behaviors commonly involve high frequency modes of oscillation, detecting and
understanding these issues require very granular data capture, large amounts of data storage
capability, and powerful analytic tools.
Oscilloscopes are typically used to troubleshoot and understand issues with electronics and
power systems. The high sampling rate offered by oscilloscopes (and some high-end meters)
enables viewing of very granular data. However, this sampling rate produces data at a much
higher rate than can be transferred by Modbus or other traditional meter data transmission
protocols.
Additionally, traditional data logging solutions simply collect and transmit time-averaged data
back to an enterprise location where post-processing may take place using database and other
tools. Oscilloscopes often conduct data storage and processing within the oscilloscope tool itself
but are not typically designed for permanent installation and long-term data capture or export to
traditional field data logging systems. Due to the high data bandwidth resulting from high
sampling rates of numerous channels, it may be advisable to process this data output on site and
transmit only desired segments and post-processing data.
To address emerging DC power quality measurement needs in a cost-efficient and effective
manner, EPRI is investigating an array of new components that can be permanently field-placed
and allow for ongoing analysis as compared to relatively expensive and temporary placement of
traditional oscilloscopes. These components include novel, very compact meters designed for
advanced and high-resolution power quality measurement with an open-source web interface that
can provide substantial post-processing.
Additionally, fast Fourier transformation (FFT) on-site analysis can save transmitted data
bandwidth. This technique can help analyze ripple on DC circuits or harmonics on AC circuits
at the site without burdening outgoing communication channels. FFT functionality is currently
available from inexpensive hardware, and open-source software already exists. Another
application of FFT is the capture and analysis of current steps that permit impedance calculations
for cell degradation evaluation. With on-site processing, only limited indicators need to be
exported to remote operators who can then trigger on-site manual downloads of detailed data.
These low-cost approaches to detection and on-site processing are being investigated for ease
of incorporation into distributed resource control panels, accuracy, and cost-efficiency.
10-2
DC Power Quality
An alternative approach is to integrate system identification and adaptive control capabilities into
power converter firmware. All modern utility-scale power converters perform high-speed local
voltage and current sensing as part of a feedback path for closed-loop control systems. These
measurements provide all the information necessary to accomplish permanent on-site power
quality monitoring without requiring any additional hardware. Additionally, this approach would
empower the converter to adjust its control parameters on-line in response to developing power
quality issues. This could be as simple as changing controller gains to manipulate closed-loop
output impedance or engaging an active damping control scheme to suppress current and voltage
oscillations. However, if the vendor does not allow access to these data, independent
measurement and analysis may be necessary.
10-3
11
CONCLUSION
While this proposed procedure for providing data does not guarantee a perfect analysis, it serves
as a starting point to enable quality data analysis of ESS. Ultimately, if the data are collected in a
consistent manner across a large number of storage systems, accurate evaluation and comparison
will be possible and allow for even more efficient integration of energy storage technologies.
Robust data, provided via these guidelines, can benefit all stakeholders and facilitate meaningful
analysis and independent verification of storage performance. This analysis capability can lead to
impactful conclusions that help improve the performance of ESS as well as improve O&M
practices. As noted throughout this guideline, there are numerous areas that need more research.
Numerous activities will help inform subsequent versions, including sessions under the auspices
of EPRI’s ESIC and IEEE Energy Storage and Stationary Battery (IEEE ESSB) Committee.
These forums are open to all, and information on participation can be found at www.epri.com/esic
or www.ieee.org.
11-1
12
REFERENCES
12-1
References
12-2
A
DER FUNCTIONS
A.1 Table
A list of the most common DER operational functions is shown in Table A-1. The table also
indicates where the operational functions are described in the EPRI Common Functions report
and the current edition of IEC 61850-7-420. In addition, it indicates which operational functions
are mandatory in different jurisdictions.
Table A-1
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
3
References
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
4
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
5
References
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
6
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
7
References
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
8
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
9
References
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
Non-Functional Capabilities
34. Collect and Provide Collect and provide detailed LN MMXU
Historical measurement and performance plus PV,
Information data which may be valuable to Wind, CHP,
record in an operational historian Fuel Cell,
Battery
detailed
LNs
35. Establish Different In addition to the default ramp Relevant ramp Per
Ramp Rates for rate, the DER may support rates or ramp function
Different Purposes multiple ramp rates that reflect times are
different conditions. This included in each
function was defined in operational
California’s Rule 21 Phase 1 function
requirements.
10
Table A-1 (continued)
DER Operational Functions from the Second Edition of IEC 61850-7-420 (Pending Release)
11
References
Hierarchical DER System Five-Level Architecture, Mapped to the Smart Grid Architecture Model (SGAM)
Level 5: Market Interactions
Transmission Energy Distribution Energy Market Flexibility Retail Energy Market
Market Information and
Communications Market
7 9 8 8
Technology (ICT)
Level 4: DSO: Distribution Utility
Level 4: ISO/RTO/TSO Distribution
Operational Analysis and Control Level 3: Third Parties:
Balancing Authority Management
for Grid Management DER Managers and
System (DMS) Plant-Level
Aggregators, or CSO
Balancing Geographic Outage Contractual Microgrid DERMS
Information Agreements with DER Demand Response (DR)
Authority for
System (GIS)
Management
Systems, Facilities, and/or Market System Enterprise
Frequency System (OMS) Facility: Overall
Management and Aggregators DER and Load
Energy
Aggregator DER & Load
Management
11 Management System
Transmission Utility WAN/LAN (FDEMS)
(ADMS), Aggregator
Energy DERMS, or Charging 5
Management 6 Energy Services
Transmission Station Management
System (EMS) DER Management DER Interface (ESI)
Bus Load System (CSMS)
System (Utility Communications 3
Model (TBLM) Capabilities
SCADA DERMS) Customer Energy Operation
SCADA DERMS Management
(CEM)
2
2 4
System Integrity 4a
Level 2: Facilities with DERs 10
Protection
Scheme and/or IBRs 1
Facilities Site WAN/LAN
Station
Building/Area #1 DER Building/Area #2 DER Resource Management (RM) Facilities
1 Energy Management Energy Management Charging Station Load
Systems Systems Management System (CSMS) Management
16
Distribution Level 1: Autonomous
Substation cyber-physical DER Energy Storage PV Wind Fossil Fuel Charging Station Load
Field
systems Controller Controller Controller Controller Controller (CSC) & Controllers
EVSEs
Integrated 12 15
12 12 12 14
Protection 13
Scheme Local EPS Battery/Thermal Wind Diesel GenSet Facilities
PV Panels Electric Vehicles
Protection Storage Turbine or Gas Turbine Site Loads
Utility Grid
Process
Area EPS ECP ECP ECP ECP ECP ECP
Meter at
PCC Local EPS
Figure A-1
Detailed Data and Control Architectures
12
Figure A-2 is an overview of the MESA “de facto” standard, built on IEC 61850, DNP3, and
SunSpec Modbus. There are hundreds of data points in the MESA-DER and SunSpec Modbus
device models.
SCADA or DERMS
MESA-DER
IEC 61850-7-420 Mapped to DNP3
MESA-DER
IEC 61850-7-420 Mapped to DNP3
MESA-DEVICE
SunSpec Energy Storage Model
SunSpec Inverter 700 Series SunSpec Storage 800 Series SunSpec Meter 200 Series
Figure A-2
MESA Standard
13
References
14
This page left blank
15
A-1