Microgrid Controller Test Plan

Microgrid Controller Test Plan
Grid Interactive Microgrid Controller for Resilient Communities

3002008885
Microgrid Controller Test Plan
Grid Interactive Microgrid Controller for Resilient Communities
3002008885
Technical Update, December 2016
EPRI Project Manager

R. Handa
ELECTRIC POWER RESEARCH INSTITUTE

3420 Hillview Avenue, Palo Alto, California 94304-1338  PO Box 10412, Palo Alto, California 94303-0813  USA
800.313.3774  650.855.2121  askepri@epri.com  www.epri.com
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS DOCUMENT WAS PREPARED BY THE ORGANIZATION(S) NAMED BELOW AS AN ACCOUNT OF
WORK SPONSORED OR COSPONSORED BY THE ELECTRIC POWER RESEARCH INSTITUTE, INC. (EPRI).
NEITHER EPRI, ANY MEMBER OF EPRI, ANY COSPONSOR, THE ORGANIZATION(S) BELOW, NOR ANY
PERSON ACTING ON BEHALF OF ANY OF THEM:
(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED, (I) WITH
RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM
DISCLOSED IN THIS DOCUMENT, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, OR (II) THAT SUCH USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED
RIGHTS, INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS
SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR
(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER (INCLUDING
ANY CONSEQUENTIAL DAMAGES, EVEN IF EPRI OR ANY EPRI REPRESENTATIVE HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES) RESULTING FROM YOUR SELECTION OR USE OF THIS
DOCUMENT OR ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN
THIS DOCUMENT.
REFERENCE HEREIN TO ANY SPECIFIC COMMERCIAL PRODUCT, PROCESS, OR SERVICE BY ITS
TRADE NAME, TRADEMARK, MANUFACTURER, OR OTHERWISE, DOES NOT NECESSARILY
CONSTITUTE OR IMPLY ITS ENDORSEMENT, RECOMMENDATION, OR FAVORING BY EPRI.
THE FOLLOWING ORGANIZATIONS, UNDER CONTRACT TO EPRI, PREPARED THIS REPORT:
Electric Power Research Institute (EPRI)
National Renewable Energy Laboratory (NREL)
Spirae
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 askepri@epri.com.
Electric Power Research Institute, EPRI, and TOGETHERSHAPING THE FUTURE OF
ELECTRICITY are registered service marks of the Electric Power Research Institute, Inc.
Copyright © 2016 Electric Power Research Institute, Inc. All rights reserved.
ACKNOWLEDGMENTS
The following organizations, under contract to the Electric Power Research Institute (EPRI),
prepared this report:
Electric Power Research Institute
3420 Hillview Avenue
Palo Alto, California 94304-1338
Principal Investigators
A. Huque
A. Maitra
D. Weng
National Renewable Energy Laboratory (NREL)
15013 Denver W. Pkwy
Golden, CO 80401
B. Miller
K. Prabakar
A. Pratt
Spirae
243 N. College Ave.
Fort Collins, CO 80524
S. Addington
M. Chhabra
T. Leichtman
O. Pacific
D. Schramm
J. Zinn
This report was prepared by EPRI, Spirae, and NREL and describes research sponsored by U.S.
Department of Energy, Office of Electricity Delivery and Energy Reliability, under Subcontract
DOE DE-OE000729.
EPRI would like to acknowledge the sponsorship and guidance provided by D. Ton of the U.S.
Department of Energy (DOE) Office of Electricity Delivery and Energy Reliability; C. Painter
and B. Ollis for their guidance and direction throughout the development of the test plan; and
J. Reilly for his valuable suggestions.
This publication is a corporate document that should be cited in the literature in the following
manner:
Microgrid Controller Test Plan: Grid Interactive Microgrid Controller for Resilient
Communities. EPRI, Palo Alto, CA: 2016. 3002008885.
iii
ABSTRACT
A microgrid is a small-scale electric power grid that can promote electric power network
resiliency by the ability to operate in conjunction with a local main electric grid or to disconnect
from the traditional grid and operate independently.
The Electric Power Research Institute (EPRI) team utilized a use-case approach to identify the
standard functions and requirements for a community-level microgrid system and controller. The
project’s performance targets were proposed by the U.S. Department of Energy (DOE). The
EPRI team completed the development of use cases and functional requirements and conducted
an initial gap analysis of Spirae’s Wave microgrid controller.
A microgrid testing and evaluation process was proposed in a three-step process. The first step
was validation of the controller at the vendor’s laboratory. The second step was to test the
controller’s performance at a national laboratory using hardware-in-the-loop (HIL) testing as
well as power-hardware-in-the-loop (PHIL) testing. The third step is to test the microgrid
controller’s performance in real-world conditions at a testing site. This report outlines a
comprehensive test plan that will be used during these testing and performance evaluation steps.
The proposed microgrid controller testing and evaluation will advance the state-of-the art in
microgrid capabilities and commercialization. The primary outcome is expected to be a standard
operational model that can be deployed at multiple communities, each with unique resources and
resiliency requirements.
Keywords
Hardware-in-the-loop testing
Microgrid controller performance
Microgrid controller testing
Microgrid controller use cases
v
CONTENTS
ABSTRACT ............................................................................................................................... V
1 INTRODUCTION ..................................................................................................................1-1
Objective ............................................................................................................................1-1
Approach............................................................................................................................1-2
Target Community Characterization, Status, and Selection ................................................1-4
Buffalo Niagara Medical Campus (BNMC) and Surrounding Fruitbelt Areas .................1-4
University of Mississippi Medical Center (UMMC).........................................................1-5
Concept Grid ................................................................................................................1-6
Report Organization ...........................................................................................................1-6
2 DOE REQUIREMENTS, MICROGRID CONTROLLER ARCHITECTURE, FUNCTIONS,
AND PERFORMANCE TARGETS ..........................................................................................2-1
DOE Performance Targets and Objectives .........................................................................2-1
DOE Functionality Requirements .......................................................................................2-2
Layered Microgrid Architecture ...........................................................................................2-7
Device Level Control – Layer 1 .....................................................................................2-8
Network Level Control – Layer 2...................................................................................2-8
Supervisory Level Control – Layer 3 .............................................................................2-8
Grid Interaction and Analytics – Layer 4 .......................................................................2-8
Standard Microgrid Functions for Integration ....................................................................2-10
Spirae Wave Architecture .................................................................................................2-12
Wave™ Software Architecture ....................................................................................2-12
Wave™ Processes .....................................................................................................2-12
Test Methods, Scenarios, and Laboratory Capabilities .....................................................2-15
Test Scenarios ...........................................................................................................2-17
3 MICROGRID CONTROLLER FUNCTIONALITY TESTING IN THE LABORATORY
SETUP .....................................................................................................................................3-1
Use Cases and Sequences of Operation ............................................................................3-1
Purpose and Scope: .....................................................................................................3-1
Use Case A: Operating the Microgrid While Connected to the Utility ..................................3-5
A.1 Test Case – DER Available (Renewables Only), No Control ..................................3-5
A.2 Test Case – DER Available and System Importing Power ......................................3-6
A.3 Test Case – DER Available and System Exporting Power .....................................3-8
A.4 Test Case – DER Available, and the System Is at Net-Zero Power Flow Across
the PCC........................................................................................................................3-9
Use Case B: Separating the Microgrid from the Utility ......................................................3-12
B.1 Test Case – Planned Disconnection.....................................................................3-12
B.2 Test Case – Unplanned Disconnection ................................................................3-16
Use Case C: Operating the Microgrid While Separated from the Utility ............................3-19
C.1 Test Case – Islanded Operation ................................................................................3-19
vii
Use Case D: Connecting the Microgrid to the Utility .........................................................3-23
D.1 Test Case – Resynchronization Operation ...........................................................3-24
Use Case E: Reduction in Outage Time ...........................................................................3-26
E.1 Test Case – Response to Outage ........................................................................3-26
4 HARDWARE IN LOOP (HIL) TESTING OF MICROGRID SYSTEMS ...................................4-1
HIL Test Configuration .......................................................................................................4-2
Operating the Microgrid While Connected to the Utility .......................................................4-4
Purpose ........................................................................................................................4-4
Procedure .....................................................................................................................4-4
Test Case A1: Normal Grid-Connected Operation with No Dispatch (Baseline) ............4-4
Test Case A2: Normal Grid-Connected Operation with Dispatch ..................................4-5
Separating the Microgrid from the Utility .............................................................................4-6
Purpose ........................................................................................................................4-6
Procedure .....................................................................................................................4-6
Test Case B1: Planned Separation ...............................................................................4-7
Test Case B2: Unplanned Separation Due to an External Fault....................................4-7
Test Case B3: Unplanned Separation Due to Loss of Utility .........................................4-7
Operating the Microgrid while Separated from the Utility ....................................................4-8
Purpose ........................................................................................................................4-8
Procedure .....................................................................................................................4-9
Test Case C1: Normal Islanded Operation ...................................................................4-9
Test Case C2: Internal Short During Islanded Operation ..............................................4-9
Connecting the Microgrid to the Utility ..............................................................................4-11
Scope .........................................................................................................................4-11
Procedure ...................................................................................................................4-11
Test Case D1: Reconnection ......................................................................................4-11
5 MICROGRID CONTROLLER FIELD TESTING AT EDF CONCEPT GRID ..........................5-1
Initial Concept Grid Test Plan Description: .........................................................................5-7
Preliminary Tests, Equipment and System Validation .........................................................5-8
Protection Plan .............................................................................................................5-8
Equipment and System Validation ................................................................................5-8
Use Case 1: Set Points for Active and Reactive Power Flows at the Point of Coupling
When Connected to the Grid ..............................................................................................5-8
Test Cases to Be Completed: .......................................................................................5-9
TC 1.2: Series of Set Points for the Coupling Point (Variable Load and PV
Generation) ................................................................................................................5-10
TC 1.3: Peak Shaving with the Start of a Critical Load ................................................5-17
Use Case 2: Scheduled Islanding (disconnection)............................................................5-18
TC 2.1: Normal Situation ............................................................................................5-18
TC 2.2: Microgrid in Overproduction ...........................................................................5-21
TC 2.3: Microgrid in Overconsumption........................................................................5-23
viii
Use Case 3: Maintain Islanding for a Given Duration .......................................................5-26
Tests Description ........................................................................................................5-26
Validation Criteria and Performance Indicators ...........................................................5-28
Use Case 4: Reconnection to the Main Grid .....................................................................5-28
Use Case 5: Black Start ...................................................................................................5-29
Measurements Needed ....................................................................................................5-30
Key Performance Indicators .............................................................................................5-31
6 CONCLUSION ......................................................................................................................6-1
ix
LIST OF FIGURES
Figure 1-1 A standardized microgrid control platform to enable microgrid communities ...........1-1
Figure 2-1 Disconnection requirements – voltage and frequency disturbance ..........................2-3
Figure 2-2 Layered microgrid architecture from DERS to grid interaction .................................2-7
Figure 2-3 Architectural variations of different microgrid controller capabilities .......................2-10
Figure 2-4 DER to microgrid controller functionality................................................................2-12
Figure 2-5 Wave™ processes ................................................................................................2-13
Figure 2-6 Spirae Wave microgrid controller architecture .......................................................2-14
Figure 2-7 Gap analysis – mapping Wave functionality with project needs .............................2-15
Figure 3-1 Integrid one line diagram.........................................................................................3-2
Figure 4-1 HIL test setup functional diagram, where “PV” indicates photovoltaic solar
generation, “G” indicates a synchronous generator – either diesel or natural gas; and
“CHP” indicates a combined heat and power generation ....................................................4-2
Figure 5-1 Key components of the Concept Grid ......................................................................5-3
Figure 5-2 Low voltage simplified schematic of a Concept Grid part ........................................5-4
Figure 5-3 Low voltage simplified schematic of Concept Grid covering potential microgrid
boundary for field trial .........................................................................................................5-5
xi
LIST OF TABLES
Table 1-1 Example of a table with caption ................................................................................1-4
Table 1-1 Microgrid controller and system testing approach .....................................................1-4
Table 2-1 DOE project objectives and performance targets .....................................................2-2
Table 2-2 Microgrid reconnection requirements .......................................................................2-4
Table 2-3 Layer 0 actor definitions ...........................................................................................2-8
Table 2-8 Standard microgrid functions for integration ...........................................................2-11
Table 2-9 Testing criteria .......................................................................................................2-18
Table 3-1 Mapping of use cases to functional requirements .....................................................3-1
Table 3-2 Integrid assets ..........................................................................................................3-3
Table 4-1 Mapping of scenarios to functional requirements......................................................4-1
Table 5-1 List of available equipment and location ...................................................................5-6
xiii
1
INTRODUCTION
Objective
The overall objective of this project is to develop and test the flexibility of Spirae’s Wave
microgrid controller so that it can be easily adapted to different end-user community applications
and to a range of electric grid characteristics. The proposed microgrid controller will advance the
state-of-the art in microgrid capabilities and commercialization. The primary outcome will be a
standard operational model that can be deployed at multiple communities, each with unique
resources and resiliency requirements.
A blueprint will be developed to enable utilities, working with end users, to more easily
implement microgrids where mutual community and system benefits are apparent. The EPRI
team’s approach includes a novel implementation architecture, broad configurability and well-
defined standard functions to enhance an existing, commercially available controller. Using
standard functions will enable grid operators to leverage distribution assets with similar functions
to support both islanded and grid-connected operation, enhancing the economic viability of
distributed energy resource (DER)-based microgrids.
Figure 1-1
A standardized microgrid control platform to enable microgrid communities
1-1
All the participating utilities are committed to exploring microgrids as a potential path to
promote electric power network resiliency in the communities they serve. The utilities
participating in this project are interested not only in the design, implementation, and validation
of individual microgrids, but also in the capabilities that would allow them to operate a network
(or fleet) of microgrids. This ability to standardize the roll-out and coordination of the operation
of multiple microgrids is a key feature of the proposed project.
Through rigorous, phased testing and evaluation at two of the premier grid simulation
laboratories in the US and testing in the field at one of the three target communities, the project
team hopes to quantifiably demonstrate that the microgrid controller and approach are ready for
adoption by a variety of communities and sites.
Approach
As part of an earlier effort, the EPRI team utilized a usecase approach to identify the standard
functions and requirements for community-level microgrid system and controller. The
performance targets that were proposed by Department of Energy (DOE), were utilized. The
EPRI team has completed developing usecases and functional requirements, and conducted an
initial gap analysis of Spirae’s Wave microgrid controller. The purpose of this document is to
outline a comprehensive test plan that will be utilized during testing and performance evaluation
stages.
Completeness of the microgrid system design in defining the problem and solution approach, and
how the system design, once implemented, will adequately solve the problem
In order to ensure that Spirae’s Wave microgrid controller meets all of the desired objectives, a
three-tiered, iterative testing and evaluation process will be utilized. The purpose of sequential
testing at InteGrid Lab and NREL’s Energy Systems Integration Facility (ESIF) is to provide a
rigorous method for testing and implementing real-time embedded systems. The initial testing at
Spirae assures that Spirae’s Wave Microgrid controller meets all the technical and reliability
related requirements in grid-tied and islanded mode. Next the microgrid system functionality is
evaluated via hardware-in-the-loop testing at NREL. One microgrid community configurations
will be tested to ensure the controller’s ability to meet DOE microgrid functions and
performance targets. Lastly, field testing will validate all controller capabilities in one real world
environment.
Appropriateness and completeness of the preliminary test plan including performance objectives
Through the software and system level hardware performance evaluation of the microgrid
controller at Spirae and NREL’s laboratories, a significant amount of risk in the final field testing
phase will be eliminated. The value of hardware in the loop simulation techniques is that they
provide a platform for evaluation of any portion of a closed-loop control system, whether it is
based in hardware, software, or both. This type of testing allows the controller to be directly
interfaced to a real hardware system (DER asset) and a real-time software platform
simultaneously. This arrangement then allows for the evaluation of the newly-developed
microgrid controller in the same conditions that it would see if connected to the actual microgrid
community Electric Power System (EPS), but without having to take the risk of “live” power
testing of an unknown system.
1-2
Adequacy of the test plan in providing appropriate baseline conditions that facilitate ready
identification, measurement of progress, and comparison of expected and actual results
The baseline condition will be established using a two-fold approach: 1) through usecase and
requirement development 2) Best practice system engineering and distribution operations
procedures. One of the scenarios will be devoted to providing appropriate baseline conditions
against which to compare the microgrid design, and it will involve achieving the same targets
with legacy approaches (no microgrid controller), that typically involve emergency fossil-fueled
based generators that solely provide value during an outage.
Validity of the test approach and methodology to validate implementation of the microgrid
functions and meeting the performance objectives and targets.
The purpose of sequential testing at InteGrid Lab and NREL’s ESIF is to provide a rigorous
method for testing and implementing real-time embedded systems. This testing approach will
ensure that initial control functionality verification and standard configuration at InteGrid are
able to meet microgrid functions via hardware-in-the-loop testing for three communities at
NREL. Three microgrid community configurations will be tested to ensure the controller’s
ability to meet DOE microgrid functions and performance targets.
The three steps include
 Laboratory Testing (Step 1) Microgrid control functionality verification and standard

configuration at Spirae’s InteGrid Lab
 Laboratory Testing (Step 2) Laboratory testing of microgrid system and controller within
hardware-in-the-loop (CHIL) testing for the Buffalo Niagara Medical Center (BNMC,
including surrounding Fruitbelt area) at NREL’s Energy Systems Integration Facility (ESIF).
 Field Testing (Step 3) at one Target Community
Adequacy of proposed test facilities and capabilities in carrying out all the proposed testing
Spirae’s InteGrid Lab is tied to a distribution system interconnection (2000 kVA tied to
13.2 kV utility feed) which allows the lab to interconnect with the local utility, Fort Collins
Utilities, and to grid parallel and import or export power to the grid. The flexible interconnect
enables the testing of power management strategies including import/export control, intentional
islanding and resynchronization. Generation assets include conventional natural gas
reciprocating generator sets and wind turbine and photovoltaic simulators. A load bank is
available which can be programmed with profiles generated from field data to replicate trends on
1-8 feeder lines allowing for control systems and equipment to be tested in a wide range of load
conditions. NREL's ESIF facility contains a unique collection of laboratories specifically
focused on overcoming challenges related to the interconnection of distributed energy systems
and integration of renewable energy technologies into the electricity grid. More than a dozen
laboratories are divided into four research areas (electricity, thermal, fuel and data analysis and
visualization), and are connected through multiple electrical, thermal, and fuel busses that enable
easy interconnection for testing systems spanning across multiple laboratories. The laboratory
has several real-time simulation platforms such as Opal-RT/RT-Lab, which is fully integrated
with MATLAB/Simulink, and RTDS/RSCAD. The real-time simulators as well as laboratory
and office space will be available for the testing tasks performed in this project. NREL can
1-3
integrate a 3rd party provided “black-box” microgrid controller, and integrate it into a microgrid
model (grid, distributed generation and loads) to characterize the controller. This can be done in
a real-time simulation environment using real-time simulators and control prototyping systems
such as RSCAD and OPAL-RT.
As part of this testing, NREL will leverage existing device models (conventional generators,
inverter based technologies, etc.) to emulate distributed generation and loads at different scales
of simulation (transient, dynamic, etc.) that can be used to develop control strategies. The results
from HIL testing is inherently dependent on the fidelity of the models used for the distribution
system and hardware, and also on the bandwidth (latency issues) of the connection between the
hardware and the real-time simulator.
Table 1-1
Microgrid controller and system testing approach
Testing Stage Location Rationale

Step 1 (Lab Testing): Verify Spirae’s InteGrid Lab, CO Microgrid controller proof-of-concept testing
Microgrid Controller’s will be conducted at Spirae’s Integrid
Technical/Functional Requirements laboratory. A combination of real and
simulated generation and load assets will be
used (both conventional and renewable) for
testing purposes.
Step 2 (Lab Testing): Verify NREL’s ESIF Lab, CO Laboratory scale proof-of-concept controller
Microgrid Controller in a potential and power hardware-in-the-loop (CHIL/PHIL)
Microgrid Systems through evaluation performed at NREL’s Energy
Controller and Power Hardware-In- Systems Integration Facility (ESIF) will
the-Loop (CHIL/PHIL) testing consist of a Real Time Digital Simulator
(RTDS), the microgrid controller, a battery
inverter and the interfaces between the RTDS
and the microgrid controller and the battery
inverter.
Step 3 (Field Testing): Verify Target Community A specific test plan will be developed and
Microgrid Controller performance in executed for the selected community to verify
one Microgrid System the microgrid controller’s technical/functional
requirements and Microgrid system benefits
Target Community Characterization, Status, and Selection

 Feasibility studies will be performed for the following two sites: Buffalo Niagara Medical
Campus (BNMC) (community medical corridor includes CHP, as well as the surrounding
Fruitbelt area)Entergy (community medical setup include CHP)
It should be noted that only the BNMC site configuration will be tested at NREL.
Buffalo Niagara Medical Campus (BNMC) and Surrounding Fruitbelt Areas
The BNMC is a consortium of the region's premier health care, life sciences research, and
medical education institutions, all located on 120 acres in downtown Buffalo, New York. Urban
areas such as the BNMC in Buffalo New York offer an interesting mix of customers and end-use
equipment—industrial, institutional, medical, educational, commercial, and residential including
residential and commercial customers in surrounding northern Buffalo communities of
1-4
Allentown and Fruitbelt in the event of major utility outages or natural disasters. The BNMC
offers a unique case with both scale and high tech critical loads. It includes possibility of four
23kV circuits tied together by multiple customer-side 5kV spot networks and can provide an
interesting contrast to a single radial feeder community case. The primary target of the microgrid
opportunities are envisioned in the BNMC utilizing resources of the primary tenants. The largest
tenants at the site have a significant amount of natural gas turbines at their facility. The Kaleida
Health (KH) facility has six megawatts of natural gas turbines that can supply significantly more
energy production capability than the loads of the facility. Furthermore, the nearby Roswell Park
Cancer Institute has 13 separate diesel generators that could be potentially used in a micro-grid
application.
Availability and Test Readiness Situation: EPRI has two ongoing projects with National Grid
and BNMC. As part of an 2014-2016 NYSERDA PON 2715 “Smart Grid, Microgrid and
Resiliency Assessments on an Urban Business Campus,” National Grid and BNMC is working
with EPRI to perform an engineering study to investigate how micro-grids and renewable energy
resources can improve reliability while maintaining power quality and increasing overall power
system sustainability. One of the outcomes of this study will be to identify for the utility and the
various customers both the costs of achieving a viable and effective microgrid in this urban
setting as well as the quantifiable benefits. Such envisioned benefits include an increase in the
quality of power supplied, enhanced reliability, and promotion of sustainability while achieving
increased energy efficiency and integration of renewable energy sources. As part of the NYPrize
effort, in 2015, BNMC, National Grid, and EPRI was awarded another NYSERDA contract to
conduct a feasibility study that was completed in March 2016. This project was part of the DOE
project as well as part of the NYPrize. If the project is selected for design analysis, that work will
only begin from August 2016. Based on this timeline, it appears unlikely that BNMC site will be
ready by Q4 2016 for the EPRI team to conduct the field trials with Spirae’s Wave microgrid
controller.
University of Mississippi Medical Center (UMMC)
The University of Mississippi Medical Center (UMMC) is the only Level 1 trauma hospital in
the state of Mississippi. The hospital is the states only academic health science center, and
employs 500 doctors and 10,000 full-time and part-time employees. It offers a wide range of
medical services, including a 722 bed diagnostic and treatment center. UMMC is a complex
consisting of multiple building sitting on a 100 acre site. As with all hospitals, in the unlikely
event that the electrical grid goes down, the site’s emergency diesel generators will start and
provide power to a select amount of critical loads. This includes life support equipment,
emergency lights, etc., but does not include any thermal loads. The site has multiple plant
chillers that all stop when the grid goes down. Although the patient’s immediate needs are
serviced by the emergency diesel generators, the buildings will quickly heat up, especially on a
hot summer day. When the buildings become too hot for patient care, the hospital must be
evacuated, which is a daunting task with a limited set of acceptable alternatives. The objective of
the project is to provide options that maintain not only the critical life support functionality, but
also thermal loads of the site in the event of a prolonged grid outage. The hospital must remain
open at all times and continue to perform its critical mission without interruption.
1-5
Availability and Test Readiness Situation: Based on discussions with Entergy, there are no plans
for actual implementations at this site. Therefore, the team will not be able to do field testing at
this site as per Step 3.
Concept Grid
EDF has created Concept Grid, a unique experimental platform designed to anticipate and
support the development of electrical systems. Concept Grid is a real distribution network
designed to support and anticipate the development of electrical systems towards smarter grids.
Located in southern Paris on EDF Lab Les Renardières, Concept Grid makes it possible to safely
conduct complex testing campaigns that would be impossible to perform on a real network, with
real customers. Concept Grid is a physical test facility fed by the French network (63/20 kV
transformer) and by distributed energy resources such as PV, wind power, generators or
batteries. It features MV and LV equipment working with physical and simulated loads and upon
which we could create accurate perturbations. Concept Grid allows multiple configurations
which open-up a wide range of experiments. These studies deal with resilience of electrical grids,
load shedding services, as well as integration of renewable energies or storage. Concept Grid
therefore enables the testing of electrical equipment but also service offers.
Availability and Test Readiness Situation: In terms of DER availability and site readiness, this
site will be ready for testing by June 2016. The EPRI team have already initiated several
discussions with EDF personnel. The microgrid boundary, equipment that will be needed, and
initial assessment has been completed. The EPRI team is planning an initial site visit at the
Concept grid in June/July 2016 to test connectivity and communication. . It appears that the
projected timeline is realistic and will allow the EPRI team to conduct the field trials with
Spirae’s Wave microgrid controller by Q3 2016.
Report Organization
This document includes six sections
 Chapter 1: Introduction, Approach and Objectives
 Chapter 2: Architecture, Functions, performance targets and goals
 Chapter 3: Test procedure at Spirae’s InteGrid Lab
 Chapter 4: Test procedure at NREL’s ESIF Lab
 Chapter 5: Test procedure at EDF Concept Grid
1-6
2
DOE REQUIREMENTS, MICROGRID CONTROLLER
ARCHITECTURE, FUNCTIONS, AND PERFORMANCE
TARGETS
The purpose of this chapter is to map the proposed microgrid controller architecture with DERs,
identify functions during grid tied as well as islanded mode, and capture the DOE performance
targets and objectives that will be utilized during testing. Subsequent sections capture Spirae’s
Wave controller architecture and maps its functional capabilities.
DOE Performance Targets and Objectives

Table 2-1 outlines the DOE project objectives and performance targets. Through rigorous,
phased testing and evaluation at two of the premier grid simulation laboratories in the US and
testing in the field, the project team hopes to quantifiably demonstrate that the microgrid
controller and approach are ready for adoption by a variety of communities and sites. The three-
tiered test plan to validate controls and approaches will include:
 Demonstrate technical feasibility and economic performance of the microgrid system design
 Verify the successful implementation/performance of the specified functionalities of control
(IC1:IC6)
 Validate the proposed controller will enable target community to achieve DOE program
targets
 Validate that the proposed solution satisfies resiliency, emissions, and system efficiency
objectives, and will achieve DOE targets
 Verify controller performance configured based on common function definitions and
standard communication protocols
 Verify the capabilities of local controls versus hosted solution
 Comply with IEEE 1547 interconnections standards
 Comply with IEEE 2030.7 standards
 Technology is broadly applicable and adaptable for microgrid applications in a cost effective
manner
 Design is replicable and fosters continued, wide-spread adoption of commercial-scale
systems
2-1
Table 2-1
DOE project objectives and performance targets
Microgrid System – Performance Targets &  Reducing outage time of critical loads by
Business Drivers >98% at a cost comparable to non-
integrated baseline solutions (such as an
UPS with backup generator)
 Reducing emissions by >20%
 Improving system energy efficiencies by
>20%
Microgrid Controller – Basic Technical & IC1: Disconnection
Functional Requirements
IC2: Resynchronization and Reconnection
IC3: Steady-State Frequency Range, Voltage
Range, and Power Quality
IC4: Protection
IC5: Dispatch
IC6: Enhanced Resilience
DOE Functionality Requirements

The proposed controller will need to be configured and tested to ensure it meets the DOE’s
requirements IC1-IC6 for microgrid controllers.
Requirement C1: Island Operation – Disconnection: Electric Power System (EPS) Point of
Common Coupling (PCC) voltage/frequency controlled according to the procedure in
IEEE Standard 1547.1
The proposed microgrid controller will manage resources to support planned and unplanned
islanded operation. The maximum islanding time in Figure 2-1 and can be interpreted as the
maximum time between the start of the voltage or frequency range and microgrid islanding from
the area EPS.
Planned intentional islanding involves controlling the energy flow at the point of common
coupling (PCC) to near zero and separating from the grid. During planned intentional islanding a
microgrid disconnects from the area electric power system (EPS) in a planned manner when the
EPS is grid-connected and in a normal operating mode. 1 The transition to Island mode is based on
a reasonable warning period, and can either be:
a) Command Planned Islanding: Utility or operating entity requests the microgrid transition to
an island mode at a specific time in the future with sufficient time for planning
1
Microgrid Functional Use Case #F-3, Grid Connected to Islanding Transition - Intentional. ORNL: 2014.
ORNL_UC_F-3.doc
2-2
b) Scheduled Planned Islanding: A scheduled tariff transition or operating agreement dictates
that the microgrid transition to an island mode at a specific time.
Unplanned/Unscheduled intentional islanding will also need to be supported by the microgrid
controller. This could consist of two scenarios.
Outage-Driven Unplanned Islanding: A confirmed grid outage is detected by the recloser or
switch at the PCC to open and start the unplanned/unscheduled islanding transition.
Command Driven Unplanned Islanding: A triggering event is detected by the monitoring
platform to initiate the island recloser or switch at the PCC to open and start the unscheduled
islanding transition. Alternatively the utility operation center receives the triggering event(s) and
works with the Grid Operator to use DMS/SCADA to open the recloser.
Figure 2-1
Disconnection requirements – voltage and frequency disturbance
Requirement C2: Resynchronization and Reconnection

Prior to reconnection of the microgrid system to an area EPS, monitoring should first indicate that
the islanded microgrid is properly synchronized with the EPS. After an area EPS disturbance and
subsequent microgrid islanding, reconnection shall not be initiated until the area EPS voltage is
within Range B of the American National Standards Institute/National Electrical Manufacturers
Association (ANSI/NEMA) Standard C84.1-2006, Table 1,2 the phase angle difference is within
the limits defined by IEEE 1547™,3 and the frequency range is between 59.3 Hz to 60.5 Hz.4
The interconnection device may delay reconnection for up to five minutes after the area EPS
steady-state voltage and frequency are restored to the ranges identified above. If an unscheduled
2
ANSI C84.1 – 2006: Electric power systems and equipment – voltage ratings (60 Hz).
3
Ibid., Ref. 8.
4
Ibid., Ref. 8.
2-3
event triggered the disconnection from the area EPS, reconnection should be delayed until it is
verified that the area EPS is stable. If multiple islands exist, a strategy may be adopted to
intentionally stagger the return of the islands. The microgrid must ensure that reconnection occurs
when the frequency difference, voltage magnitude difference, and voltage phase angle difference
between the area EPS and microgrid on either side of the microgrid switch are within the limits
defined by IEEE 1547™.5 For a microgrid with a rating between 1.5 and 10 megavolt-amperes
(MVA), the reconnection requirements are shown in Table 2-2.
The microgrid controller will need to interface with phasor measurement units (PMUs) or power
meters with phase angle and ∆f (Hz) capabilities. The automatic synchronizing & reconnecting
algorithms, which have been refined over the last 10 years in the field for networks between
208VAC and 150KV, take account of circuit breaker or circuit reconnection device closing times
and the system’s current configuration to calculate the estimated zero crossing allowing for
microgrid reconnection as tested in the field within ±2°of the phase angle. Synchronization &
reconnection can be achieved during adverse system conditions; the controller automatically
adjusts to accommodate voltage differences and frequency differences with a configurable
settings between 0% up to 20% in magnitude in voltage difference, and phase angle settings from
0 up to 10°, in a phase lock loop or slip frequency settings between 0.00 and 0.25 f Hz
Table 2-2
Microgrid reconnection requirements
a) Microgrid
Frequency difference Voltage difference Phase angle difference
rating
(∆f, Hz) (∆V, %) (∆Ɵ, °)
(MVA)
1.5-10 0.1 3 10
Requirement C3: Steady-State Frequency Range, Voltage Range, and Power Quality
Depending on the nature of an area EPS, the ability of a grid-connected microgrid to affect the
power quality inside the microgrid may have to be evaluated separately. Power quality
requirements could very well drive when to island. An islanded microgrid in steady state
operation must:
1. Maintain the frequency in the range 59.3 Hz < f < 60.5 Hz — a range consistent with the
frequency range for an area EPS and suitable for most loads — barring customer-specific
requirements that may override this range.
2. Maintain the voltage according to ANSI 84.1-2006 standards — specifically, the required
voltage range for microgrid islanded steady-state operation is 0.95 pu<V< 1.05 pu at the
PCC.
3. Maintain the power quality at the PCC in compliance with customer-specific requirements.
Frequency Control: Wave has built-in frequency control algorithms to support and maintain
stable system frequency at various locations or islanding scenarios. The controller continuously
monitors the health of the system frequency and available assets with frequency control
capabilities to automatically dispatch for primary frequency control (referred to as frequency
master). Wave controls the output of all non-frequency master assets in a frequency support
mode that allows the frequency master asset(s) to operate in a configurable optimal operating
range. The frequency control algorithm can also transfer frequency master responsibilities to
5
Ibid., Ref. 8.
2-4
different assets at the request of the operator (e.g. to take the frequency master asset down for
maintenance), or automatically if more capable frequency master asset becomes available. Wave
also has built-in under frequency and over frequency algorithms to manage emergency situations.
Voltage Control: Wave’s grid connected voltage control methodology utilizes reactive power
capabilities of assets in conjunction with traditional on-load tap-changer operation for advanced
control of system voltage. Multiple nominal voltage levels can be configured and independently
controlled. Voltage control areas are created automatically, based on nominal voltage levels and
real-time awareness. System operators have complete control over voltage control setpoints and
preferred operating range. The controller can transfer voltage master responsibilities to different
assets during runtime by operator request or automatically if a larger more capable voltage master
asset is available.
Requirement C4: Protection

A grid-connected microgrid must be capable of meeting the following protection requirements:
1. An “external” fault (a fault on the area EPS side of the microgrid switch): The microgrid
switch must open and interrupt the flow of fault current from the microgrid to the utility grid
within 0.16 seconds of the fault occurrence.
2. The microgrid must prevent unintentional islands by opening the microgrid switch consistent
with the requirement of IEEE 1547.2.
3. An “internal” fault (a fault on the microgrid side of the microgrid switch): Internal faults will
potentially draw large fault currents from the utility, through the microgrid switch, and to the
fault. The microgrid must clear internal faults.
An islanded microgrid is only subject to internal faults, and, thus, must clear internal faults.
Microgrid protection schemes vary greatly depending upon the asset mix of induction,
synchronous and inverter-based generation. Each type of generation supplies unique amounts of
fault current and have different dynamic characteristics. Without mitigation, this creates
protection coordination issues within a microgrid. Using modern utility grade protection devices
is paramount to ensure safety of personnel and equipment. The proposed controller uses Multiple
Group Protection setting schemes and understanding of the current state of the electrical network
to coordinate devices. By interfacing with a power system model, the microgrid controller can
determine the available fault current and select the appropriate protection settings.
Requirement C5: Dispatch

Dispatch for microgrid survivability includes, but is not limited to:
1. While grid-connected, ensuring sufficient resources (e.g. generation and/or energy storage)
are operating and available to support the microgrid’s seamless transition to island mode.
2. While islanded, managing energy resources consistent with ensuring service to the microgrid
critical loads for the duration of the islanded state.
Dispatch for economic operation may include, but is not limited to:
1. Optimization of the microgrid’s energy consumption and generation against electric and
natural gas tariffs.
2. Provision of services to the grid (area EPS), such as:
a) Energy,
b) Volt/VAR support,
2-5
c) Frequency regulation,
d) Spinning reserve,
e) Black start support, and
f) Demand response.
Dispatch for environmental performance includes reducing or limiting CO 2 emissions.
The Wave Microgrid Control automatically dispatches assets to meet the current operational
criterion including maintaining local survival, supporting economic operations, minimizing
environmental impacts and all combinations thereof. When grid connected the controller
manages the local resources to ensure high power quality and readiness to island in case of
emergency. Economic and environmental objectives issued by internal or external parties are
evaluated and supported by dispatching additional assets (or modifying current asset set points) if
capacity is available. While islanded, the controller’s primary objective is to maintain critical
loads and will automatically dispatch or shed generation and load assets as necessary. During
extended island operations, the objectives may be modified to maximize survivability or to
provide black start support. The allocation of assets is determined by taking an account of each
asset’s availability, capabilities (e.g., capacity and dynamic responsiveness) and operational
constraints and matching these factors to the current list of objectives. Some common factors
include active and reactive power capacity, response time, minimum and maximum operating
times, calendar constraints, etc. The Wave environment manages a database of the asset
parameters that can be easily updated via a user-interface to accommodate schedule changes or
operational changes. The dispatch of assets may be configured to be automatic or to require
operator acknowledgment.
Requirement C6: Enhanced Resiliency

Due to its ability to continue operating when electricity delivered from a utility is disrupted, a
microgrid is considered by the DOE and communities as a strategic asset to support the planning
and implementation of resilient energy communities. The microgrid controller must be capable of
managing microgrid resources to meet the community-defined resilience objectives during
disruptive events, and providing sufficient information to distribution system operators to enable
the communication of accurate information on operating conditions of the microgrid to
communities, especially those responsible for critical loads.
Wave accepts identified system critical loads and continuously develops a plan to ensure that
critical loads are met in case of grid disruption or intentional islanding events. In some instances,
“n-1” reliability may be sufficient where the unplanned loss of a single generating asset will not
adversely affect operation. Other systems may require higher levels of redundancy (e.g., n-2).
Reliability considerations will be determined in project planning and will involve community-
specified levels of redundancy and identification of critical loads. Generation and spinning
reserve algorithms manage DER according to system priorities. Spinning reserve can be
conventional generation, storage, or flexible loads. While islanded, the controller’s primary
objective is to maintain critical loads and it will dispatch accordingly. During extended islanding,
the objectives may be modified to maximize survivability or to provide black start support. The
user interface (UI) provides interface to all microgrid elements, and can interface with other
databases and SCADA systems to ensure resiliency requirements are met.
2-6
Layered Microgrid Architecture
The “general purpose” layered microgrid architecture from DERs to grid interaction is shown in
Figure 2-2.
Figure 2-2
Layered microgrid architecture from DERS to grid interaction
(Source: EPRI, LBNL, Microgrid Labs, Spirae)
The proposed microgrid controller architecture is based upon a multi-layered strategy for
managing and controlling the distributed resources and loads that may be part of local
microgrids. The specific layers identified here include device level control, network level
control, supervisory control, and grid interactions/analytics, which are further discussed below.
 Layer 0 captures the DER types and load types and pertains to energy generation (resources)
and storage as well as load requirements.
 Layer 1 (device level control) includes the individual device level control.
 Layer 2 (network level control) is the control layer which manages DER, including
scheduling and dispatching and their network connectivity and where operational commands
are sent out.
 Layer 3 (supervisory control) consists of supervisory control where energy management
activities are performed.
 Layer 4 (grid interactions/analytics) provides the grid connectivity to DMS, SCADA, and
market.
2-7
Device Level Control – Layer 1
Device level control entails interacting with the local DER itself to perform certain functions
including: device switching (physical isolation, on/off, fault clearing), device protection (fault
sensing, fault controls, re-synchronization), inverters/variable frequency drives (VFDs) (power
conversion, power control, voltage and frequency control), primary frequency control (inverter
droops, governor droops), and other controls (master voltage and frequency, island detection,
resynchronization). Device level control receives and transmits signals through the network
control layer.
Network Level Control – Layer 2
Network level control ties together all of the multiple device level controls that are distributed
and allows for data exchange, sequencing and coordination of all of the individual devices. It
includes both logic and a human machine interface.
Supervisory Level Control – Layer 3
The Supervisory Level control layer is the control and coordination layer for DERs to microgrid
controller/DERMS.
Grid Interaction and Analytics – Layer 4
The Grid Interaction and Analytic layer includes advanced algorithms performing the
optimization for interactions and communication between DERs and the microgrid
controller/DERMS. The actors listed below are based on the architecture from Figure 2-2.
Table 2-3
Layer 0 actor definitions
Layer 0: Generation/Storage/Load
PV, Wind, Microturbine Energy generation sources
Mid-Large Scale Rotating Machine Energy generation source
Batteries and Energy Storage Batteries and energy storage device that is capable of storing
Supercapacitor exponentially more energy than electrolytic capacitors and
delivering and accepting charge much faster than batteries.
Generally used when rapid charge and discharge cycles are required.
Critical Load Loads within the microgrid having the highest priority of service.
These loads will be served at the expense of all other loads in the
microgrid and at the expense of any other service the microgrid
could provide. The priority of loads within the critical loads is not
distinguished.6 Examples include hospitals, emergency lighting,
other emergency services, and entities deemed necessary.
Non-Critical Load Loads within the microgrid having the lowest priority of service.
These loads may be left unserved in favor of Critical Loads. The
priority of loads within the critical loads is not distinguished.7
6
Microgrid Functional Use Case #F-1, Frequency Control. ORNL: 2014. ORNL_UC_F-1.doc.
7
Ibid.
2-8
Table 2-4
Layer 1: Device level controls

Breakers, Contactors, and Electric switches used to control, protect, and isolate electric
Switches/Automated Switchgear circuits; switches that can break an electrical circuit without human
intervention and divert the current from one line to another.
Inverters Electronic device that converts DC to AC electrical power.
Static Switch Provides an automatic transfer of load from the preferred to a
backup or alternate energy source.
Load Controller Mechanism to monitor and control power usage and conducts load
shedding during peak energy demands periods.
Rotary Distributed Generation Control Control scheme specific to a distributed generation unit that is based
on some form of rotating machine.
Protection Devices Devices used for protection of electrical power systems from faults.
Table 2-5
Layer 2: Network/Group/Building level controls

Sensors Mechanism used to detect energy status information
PLCs (Programmable Logic Controllers) Device that interfaces objects in the physical world to a distributed
and RTUs (Remote Terminal Units) control system.
Network SCADA Communications system for the SCADA data
High-Speed Load Shedding Interrupting energy supply to accommodate demands that exceeds
available energy resources.
Building Management System/Building A traditional integrated facility-wide building management control
Automation System system for monitoring and control of temperature and HVAC set
points, operation of facility equipment (boilers, chillers, pumps, hot
water, chilled water, cooling towers, economizers, etc.)
Table 2-6
Layer 3: Supervisory/Management Level Controls

Supervisory Controller/Energy Manager Responsible for overall optimization and dispatch operation of
energy resources.
Table 2-7
Layer 4: Analytics/DMS Interface/Grid Interaction

Grid Interaction/Analytics Analysis of information gathered from energy usage and
requirements.
Figure 2-3 captures the architecture variations that different microgrid controller vendors can
have at different microgrid system deployments in terms of controls, operations, capabilities and
connectivities.
2-9
Figure 2-3
Architectural variations of different microgrid controller capabilities
Standard Microgrid Functions for Integration

The “basic” microgrid functions during grid tied and islanded mode are included in Table 2-8.
Figure 2-4 maps each of the functionalities to the different layers within the overall microgrid
architecture.
2-10
Table 2-8
Standard microgrid functions for integration
Grid-Tied Functions Islanded Functions

Grid Services Microgrid Services
 Connect/Disconnect (non-islanding)  Disconnection
 Utility SCADA and DMS coordination - Intentional, planned (scheduled, command)
 Connectivity and interface with power flow models, - Intentional, unplanned (unscheduled)
utility DMS and DERMS - Unintentional, unplanned
 Market interface for capacity, energy, and ancillary  Resynchronization
services - Voltage and frequency control
 Grid Configurations/Operations
 Isochronous/Droop Operations
 Protection
 Black start
 DER anti-islanding (within microgrids)
 Market interface for capacity, energy, and ancillary
services
Local Services (Optimization) Local Services (Optimization)
 Load and weather forecasting  Load and weather forecasting
 Energy management and dispatch  Energy management and dispatch
- Max generation level control - Max generation level control
- Power quality (PQ), outage, fault detection - Load and generation following
- Voltage regulation - PQ and reliability
 Volt-VAR management and PF control - Voltage regulation
 Power (Volt/Watt or Freq/Watt)  Volt-VAR management and PF control
curtailment/control  Power (Volt/Watt or Freq/Watt)
 Power smoothing curtailment/control
- DG, storage, load management  Power smoothing
- Voltage and frequency ride-through - DG, storage, load management
Operator Services Operator Services
 State/Status monitoring  State/Status monitoring
 Communication with DSO/ISO/RTO  Communication with DSO/ISO/RTO
 User interface and data management  User interface and data management
 Billing  Billing
 Event logging  Event logging
2-11
Figure 2-4
DER to microgrid controller functionality
(Source: EPRI, LBNL, Microgrid Labs, Spirae)
Spirae Wave Architecture

Wave™ Software Architecture
Wave™ is a highly distributed system, spanning multiple processes and multiple computers.
Relatively small, non-complex deployments may reside on a single computer. Large, complex
deployments may be spread across a distributed network of computers. The computers hosting
Wave™ may reside all within a single facility or be distributed geographically throughout the
world.
Wave™ Processes
The primary processes in Wave™ are the Wave™ Client, three types of Wave™ manager
processes, and the Wave™ Manager Service. The manager processes include a single
Distribution Network Manager (DNM), one or more Control Area Manager (CAM), and one or
more Energy Resource Manager (ERM). These processes communicate over the Wave™
Communication Bus (WCB). Figure 2-5 shows one of each process type, except for the Wave™
Manager Service.
2-12
Figure 2-5
Wave™ processes
The Wave™ Client is the extensible graphical user interface (GUI) used for configuration and
operation of Wave™. Configuration begins with the initial importation of asset topology
information from an external power system model. Next, specific manufacturer model
information is associated with each asset, along with any installation-specific customizations.
The final asset related configuration sets up I/O needed for controlling individual assets.
Requests made by the Wave™ operator are sent from the Wave™ Client to the DNM. The DNM
can process requests from the Wave™ Client directly, or forwards those requests to the correct
CAM or ERM that will ultimately process the request. The DNM mainly comprises functionality
from layer 4 in Figure 2-4.
CAM(s) host one or more Control Groups and their associated capabilities. A control croup is a
defined set of assets. An example of a control group would be a battery system, a load, and a
utility breaker that allows the battery system and load to interconnect to the utility. An example
of a capability for such a control group would be import and export control across the utility
breaker. The CAM mainly comprises functionality from layers 2 and 3 in Figure 2-4.
ERM(s) host one or more assets, their associated capabilities, and associated communication
libraries. An example of an asset would be a battery system. Example capabilities for such a
battery system would be sending set-points, activating modes, and sending online/offline
commands. The communications libraries are hosted inside a Simple Asset Manager (SAM), and
are used to establish the physical connection between Wave™ and the asset. Communication
from the SAM to the asset can be achieved via various protocols including, but not limited to,
Modbus, DNP3, Web Service, analog signals, digital signals, or OPC. The ERM mainly
comprises functionality from layer 2, and the ability to activate and monitor performance of
functionality from layer 1 in Figure 2-4.
Lastly, the Wave™ Manager Service is a Windows™ service that communicates with other
Wave™ processes (DNM, CAM, and ERM) via the Wave™ Communication Bus. The Wave™
Manager Service controls the execution of the DNM, CAM, and ERM.
2-13
Figure 2-6
Spirae Wave microgrid controller architecture
Wave is a DERMS software developed by Spirae LLC covering the functional domains of
monitoring and control (MC), microgrid (MG), advanced energy storage (AES), and Demand
Response (DR). For a given network of DERs that are configured to provide power within
defined electrical boundaries, a Wave™ DERMS solution can be deployed for monitoring and
control purposes. Such a network has its own set of resources, including energy sources, loads,
storage, and controls. Remote networks (those without access to a main grid) typically contain
diesel or gas generators, renewable energy sources such as wind turbines and photovoltaics, and
energy storage to further improve efficiency. The Wave™ MC application provides DER level
controls for each individual DER, without any coordination with other DERs in the network. The
Microgrid application provides the system level controls for efficient and stable operation of a
microgrid with optimal utilization of renewables to minimize the overall cost of energy. The
AES application will enable the operator to dispatch energy storage assets to meet one or more
power system objectives. Examples include smoothing active power profiles from renewable
generation assets (e.g., solar photovoltaic systems), re-shaping the net power profile of a
microgrid (e.g., peak load reduction), or supporting ancillary services (e.g., frequency
regulation). The DR application will allow the execution of optimized load shedding strategies,
and can be dispatched by the Wave™ operator, or a utility DMS/OMS system.
2-14
Figure 2-7
Gap analysis – mapping Wave functionality with project needs
Test Methods, Scenarios, and Laboratory Capabilities

Step 1 Spirae’s InteGrid Lab Testing: The test procedure is provided in Chapter 3. The
microgrid software control algorithms will be tested and verified in the InteGrid Lab with the
MXB hardware and the remote-hosting functionality. The InteGrid lab assets will be employed
to perform testing scenarios with hardware in the loop, the hosted Wave solution and the MXB
bundled architecture. The lab assets include Dynamic Wind Turbine Simulation, Dynamic Photo
Voltaic Simulation, Conventional Natural Gas Reciprocating Generator Sets, Transmission
Connection and Substation Emulation, and a Utility Load Simulator. The system response to
disconnection from the utility and resynchronizing, frequency and voltage variations and power
quality will be measured and recorded. The Frequency regulation, volt-VAR control, etc. from
the system model will be compared to actual test results. Control adjustments will be made to
maximize the effectiveness of the control loops.
Step 2 NREL’s ESIF Testing: The test procedure is provided in Chapter 4. The physical
experimental setup for the laboratory scale proof-of-concept HIL evaluation performed at
NREL’s Energy Systems Integration Facility (ESIF) consist of a Real Time Simulator (RTS), the
microgrid controller, a battery inverter and the interfaces between the RTS and the microgrid
controller and the battery inverter, and an external oscilloscope with voltage and current probes.
A software model of the community power system, including a simulated electric power system,
along with the distribution lines, DER, loads, system protection devices, etc. that make up the
microgrid, will be executed in real-time on the RTS. The RTS will also output signals to and
receive inputs from the microgrid controller and the battery inverter in real-time, providing for a
2-15
closed-loop simulation of the microgrid controller with the community microgrid power system.
Closed-loop simulations will be performed across a range of scenarios in order to fully evaluate
the technical feasibility and functional performance of the microgrid controller. The test methods
that will be used during the testing at NREL for each of the functional requirements of Section
I.C.1 through I.C.5 are listed below:
 I.C.1 Disconnection: Electric Power System (EPS) Point of Common Coupling (PCC)
voltage/frequency controlled according to modified version of procedure in IEEE Std 1547.1
 I.C.2 Resynchronization and Reconnection: Vary PCC voltage and frequency (while the
other is at nominal) and ensuring that the process of resynchronization and reconnection is
not started. The delay time will be tested by measuring the delay before reconnection
initiation once nominal conditions are present. Repeat resynchronization and reconnection
process for varying load and generation scenarios and, in each case, confirm that
reconnection occurs appropriately.
 I.C.3 Steady-State Frequency Range, Voltage Range, and Power Quality: Monitor PCC
frequency and voltage and current waveforms (to derive key PQ metrics such as THD, TDD,
etc.) while varying load and generation according to time series profiles of different
microgrid operation scenarios (e.g., lightly loaded, heavily loaded, max. PV penetration, etc.)
 I.C.4 Protection: Simulate external faults in several combinations of varying impedance
(location) and type (e.g., single-line-to-ground, double-line-to-ground, etc.). Simulate
formations of different external unintentional islands of varying configuration. Simulate
internal faults in several combinations of varying impedance (location) and type (e.g., single-
line-to-ground, double-line-to-ground, etc.)
 I.C.5 Dispatch: Vary load and generation according to time series profiles of different
microgrid operation scenarios (e.g., lightly loaded, heavily loaded, max. PV penetration,
etc.). Scenarios will be based on real-world operational data from the community to the
extent possible. Each scenario will be run for the base case (no microgrid controller
coordination) and microgrid controller case and these two cases compared to understand the
economic operation and environmental performance differences.
Step 3: On Site Testing: The test procedure is provided in Chapter 5 for the selected community
(EDF Concept Grid) to verify the functionality of the microgrid system with the installed assets
against the operational scenarios.
Justification that the methods are adequate in scope, time resolution, and measurement
resolution to accurately assess the performance of the microgrid controller against the
functional requirements and the microgrid system design objectives
Step 1 Spirae’s InteGrid Lab Testing: The software test configuration and InteGrid Lab’s
physical assets are utilized to perform the demonstration scenarios to assess the performance of
the Microgrid controller. The InteGrid Lab instrumentation will be configured to collect data to
validate the Microgrid operation against these demonstration scenarios. Measurement and
recording instrumentation will include power quality meters with sampling at 64 samples per
cycle, and SCADA sampling at 1 sample per cycle. Instrumentation data files are stored for
further analysis. The time and measurement resolution will be defined in a detailed site specific
test plan developed to the capture of the pertinent data to validate the Microgrid performance
against the functional requirements.
2-16
Step 2:NREL’s ESIF Testing: NREL’s HIL test platform can execute the model of the
microgrid community power system with time steps in microseconds, view system behavior in
real-time and save the data into the RTS hard drive for post-processing. This HIL test platform
will be used to evaluate the functional requirements of Section I.C.1 through I.C.5. Operational
and performance data will be collected during the HIL-based validation testing phase using
software metering points inside of the software microgrid system model. A physical oscilloscope
will be present at the microgrid controller board for any diagnostic need. Data will be
accumulated and stored from the real-time simulation as a time series, collected for the duration
of the test, stored in a structured file (e.g., comma-separated values file) and organized by being
named with the test ID and a test run number for easy retrieval and analysis later. A summary of
each test with key metrics (e.g., power quality indices, trip times, system efficiencies, etc.) will
be provided.
Test Scenarios
Based on the usecase efforts, the project team developed a list of specific test scenarios that will
be tested at Spirae and NREL. The test scenarios were developed so that the microgrid controller
performance can be verified for all the 6 technical requirements C1 through C6. Table 2-9
summarizes the parameters that will be measured for the testing of the microgrid controller
functional requirements. During the running of the test scenarios in the lab power metering data
will be collected at the PCC to validate the microgrid control against the functional requirements.
Metering data may also be obtained from the various DER assets in operations under various
power production and load profiles to provide insight into how fluctuations of the DER assets
affect the stability of the power at the PCC and validate that the microgrid controls mitigate these
fluctuations. The type of measured data collected include voltage, current, power, energy,
frequency, demand, individual and total harmonics, current & voltage unbalance, flicker, and
symmetrical components. Regarding the sampling rate frequency, the voltage/current transients
will be captured at 1,000 Hz+ as indicated in the table. The 60 Hz refers to the rate at which we
will read the RMS values from the RTDSs, which will calculate the RMS values over one cycle.
2-17
Table 2-9
Testing criteria
Measured Sampling Functional Purpose / Metrics

Parameter Frequency Requirement
Location: PCC
RMS Voltage 60 Hz C.1, C.2, C.4, Base set of parameters to understand the steady-state
C.5, C.6 operating conditions of the microgrid’s connection to the
Voltage phase angle
area EPS and determine the corresponding performance of
Voltage frequency the microgrid controller. Used for quick review of test to
ensure approximate expected performance was achieved.
RMS Current
Current phase angle
Voltage waveform 1000+ Hz Used for detailed review of system performance and for
calculation of key metrics such as THD, exact durations of
Current waveform
connection/disconnection, etc.
Location: Microgrid side of Microgrid Switch
RMS Voltage 60 Hz C.2 , C.3, C.4, Base set of parameters to understand the steady-state
C.5, C.6 operating conditions of the microgrid when islanded. Used
Voltage phase angle for quick review of test to ensure approximate expected
Voltage frequency performance was achieved.
RMS Current
Current phase angle
Voltage waveform 1000+ Hz Used for detailed review of system performance and for
calculation of key metrics such as THD, exact durations of
Current waveform
connection/disconnection, etc.
Location: Critical Loads and at other Sensitive Loads with Specific Customer-Defined Power
Quality Requirements
Voltage waveform 1000+ Hz C.3, C.4, C.5, Used for detailed review of system performance and for
C.6 calculation of key power quality metrics such as THD,
Current waveform
TDD, etc.
Location: Fault Location
Voltage waveform C.4 Used for detailed review of fault condition and
confirmation that fault occurred as programmed.
Current waveform
2-18
Perceived Risk Impact Mitigation Strategy
Availability of NREL’s Energy Low Laboratory scale proof-of-concept controller-hardware-in-the-loop
System Integration Facility (CHIL) evaluation planned at NREL’s ESIF will engage a Real
(ESIF) – ESIF is heavily used as Time Simulator (RTS), the microgrid controller, a battery inverter
user facility by commercial and the interfaces between these equipment. A software model of
vendors and government funded the community power system, including a simulated electric power
project teams system, along with the distribution lines, distributed energy
resources, loads, system protection devices, etc. that make up the
microgrid, will be executed in real-time on the RTS. Requirement
of MW-scale grid and PV simulators, which are in high demand, is
minimal for this project.
Readiness of the target Low EDF Concept is available for the field trial
community to deploy the
proposed controller to build a
fully functional microgrid
Availability of Spirae’s Wave Medium The project team has already evaluated the Wave controller as part
Controller of the functional testing. A detailed gap analysis has also been
performed. All the microgrid states and the DOE identified
functionalities have been successfully demonstrated at the Spirae
Lab in Dec 2015
Wave Controller’s capability to Medium Communication failures are of two categories. First, if one or more
handle Communication failures assets lose communication with Wave, and second if one or more
during operation of the Wave hardware or software components lose communication
with each other. In either case, the customer can prescribe how they
would want the assets and Wave to respond. In general, Wave will
always inform the operator of a communication failure with
appropriate alarms and status messages.
Any time new field equipment is introduced, additional time is
required to understand and develop monitoring/control interfaces
for that equipment.
Standard Protocol Low Wave has been designed to adopt to different industry standard
Implementation and risk in communication protocols. Testing of Wave controller’s
connecting to field assets monitoring/control interfaces against real equipment, a test harness,
and simulated equipment can help lower the possible risks, and
lower the set-up time for each test scenario
Field performance of the High Through the provision of software and system level hardware
proposed microgrid controller at performance evaluation of the microgrid controller at Spirae
the target community InteGrid laboratory and NREL’s ESIF, a significant amount of
potential risk in the final field testing phase has been minimized.
2-19
3
MICROGRID CONTROLLER FUNCTIONALITY TESTING
IN THE LABORATORY SETUP
Use Cases and Sequences of Operation
Purpose and Scope:
This document provides test plans for Spirae’s Integrid laboratory. The test plans will be used to
evaluate the compliance of Spirae’s microgrid controller with the microgrid controller
technical/functional requirements (C.1 – C.6) outlined in the U.S. Department of Energy’s
Funding Opportunity Announcement (FOA) DE-FOA-0000997-Amendment 0002 (FOA 997).
Specific use cases or system scenarios are outlined in the test plans will demonstrate the Spirae
microgrid controller’s conformance with the DOE functional requirements. Table 3-1 below
shows the mapping of use cases to functional requirements.
Table 3-1
Mapping of use cases to functional requirements
C1 C2 C3 C4 C5
Disconnection Resynchronization Steady-State Protection Dispatch
and Reconnection Frequency
Range, Voltage
Range, and
Power Quality
Use Operating the X
Case A Microgrid
While
Connected to
the Utility
Use Separating the X X
Case B Microgrid
from the
Utility
Use Operating the X X X
Case C Microgrid
while
Separated
from the
Utility
Use Connecting X
Case D the Microgrid
to the Utility
Use Microgrid X X
Case E Response to
Unplanned
Disconnection
3-1
Figure 3-1
Integrid one line diagram
3-2
Table 3-2 provides a list of load and generation assets at Integrid which will be used during
testing. Corresponding meters for each of the assets is also listed. The Integrid point of common
coupling (PCC) meter will be used to acquire three phase voltage, three phase current, frequency,
and voltage phase angle data, while the individual asset meters will be used to acquire three
phase voltage and three phase current data. The data will then be analyzed and compared to the
specifications described in Chapter 2.
Table 3-2
Integrid assets
Integrid Asset Capacity

Integrid Point of Common Coupling (PCC) n/a
Wind Turbine Simulator (WTS) -100 kVar, 100 kW
Synchronous Generator (Natural Gas) - GEN2 90 kVa, 80 kW, 0.88 PF
Synchronous Generator (Natural Gas) - GEN3 90 kVa, 80 kW, 0.88 PF
Synchronous Condenser (SC) 125 kVar, -10 kW
Load Bank #1 400 kVa, 400 kW, 0.8 PF
Load Bank #2 106 kW
PV Simulator (PV) 27kW, 1.0 PF
For certain test scenarios, the WTS, PV, and load bank #2 will be given profiles to follow, unless
it is explicitly stated that those assets are programmed to follow a fixed set point or remain
offline. For the test scenarios where profiles are being used, the profiles are set to update every
1 second, and will be given upper and lower limits depending on the test scenario. The difference
between the current profile value, and the next profile value, will be randomized with an upper
limit of 5.
Data logging at Integrid is conducted using two sets of power quality meters. One set of meters
consists of Bitronics M571 meters, while the other set contains DTS-300 meters. The Bitronics
meters are used to access RMS and waveform data, while the STS-300 meters are used for RMS
data. Spirae’s microgrid controller uses data from the Bitronics M571 meters for monitoring
Integrid assets. Integrid also has a SCADA system (independent of the microgrid controller) that
accesses the DTS-300 meters to monitor Integrid assets.
Bitronics M571 capture points are as follows:
RMS points (1 sample per cycle):
 Watts – Phase A
 Watts – Phase B
 Watts – Phase C
 Watts - Total
 Vars – Phase A
 Vars – Phase B
3-3
 Vars – Phase C
 Vars - Total
 Voltage – Phase A
 Voltage – Phase B
 Voltage – Phase C
 Voltage - Neutral
 Current – Phase A
 Current – Phase B
 Current – Phase C
 Frequency
 Zero Sequence Voltage
 Positive Sequence Voltage
 Negative Sequence Voltage
 Zero Sequence Current
 Positive Sequence Current
 Negative Sequence Current
 THD in Voltage – Phase A (n=2...63)
 THD in Voltage – Phase B (n=2...63)
 THD in Voltage – Phase C (n=2...63)
 TDD in Current – Phase A (n=2...63)
 TDD in Current – Phase B (n=2...63)
 TDD in Current – Phase C (n=2...63)
Waveform capture points (64 samples per cycle):
DTS-300 capture points are as follows:
RMS capture points (2 samples per second):
 Watts – Phase B
 Watts – Phase C
 Watts - Total
 Vars – Phase A
 Vars – Phase B
3-4
 Vars – Phase C
 Vars - Total
 Voltage – Phase A
 Voltage - Neutral
 Frequency
Use Case A: Operating the Microgrid While Connected to the Utility

The focus of this use case is the availability of local distributed energy resources (DER) and
curtailable loads to offset electrical demand from the utility in return for financial compensation
and energy security. The compliance of the Wave™ Controller with respect to
Technical/Functional requirement C.5 (as outlined in FOA 997) will be evaluated.
Four test cases are addressed under this use case:
1. DER available (renewables only), no control.
2. DER available, and the system is importing power from the utility.
3. DER available, and the system is exporting power to the utility.
4. DER available, and the system is at net-zero power flow across the PCC.
To further demonstrate Spirae’s Wave™, large renewables variations will be introduced while
connected to the utility grid. Wave™ will maintain a PCC I/E set-point during those
disturbances. Additional variations will include operating the utility interconnection with certain
assets unavailable.
A.1 Test Case – DER Available (Renewables Only), No Control
This test case simply determines a baseline of the system with no Wave™ influence.
Initial Conditions (unless specified otherwise):
1. Main tie CB-SG3B-1 (PCC breaker) closed.
2. Wave™ offline.
3. Load bank #2 profile {25-106} kW.
4. WTS profile {10-100} kW.
5. PV profile {0-23} kW.
3-5
A.1.1 DER Available (Renewables Only), No Control
Test steps:
1. Determine the baseline parameters while running the InteGrid ab under these conditions.
A.2 Test Case – DER Available and System Importing Power
This test case will demonstrate Wave™ import power functionality while connected to the
utility.
2. Wave™ set to import (kW/kVAr) set points at the PCC.
A.2.1 DER Available and System Importing Power
A.2.1a Baseline:
1. DER set points provided by Wave™.
2. Verify proper import (kW/kVAr) control.
A.2.2 DER Available and System Importing Power: Renewable Variations
This test case will demonstrate Wave™ import power functionality while connected to the utility
with disturbances in the renewable resources.
A.2.2a Loss of Wind:
Initial Conditions:
4. WTS turned off, and breaker opened.
Test steps:
3-6
A.2.2b Loss of PV:
Initial Conditions:
5. PV turned off, and breaker opened.
Test steps:
A.2.2c Loss of Wind and PV:
Initial Conditions:
Test steps:
A.2.3 DER Available and System Importing Power: Generator Variations
This test case will demonstrate Wave™ import power functionality while connected to the utility
with disturbances in the generator resources.
6. GEN2 turned off, and breaker opened.
A.2.3a Loss of One Generator:
3-7
A.3 Test Case – DER Available and System Exporting Power
This test case will demonstrate Wave™ export power functionality while connected to the utility.
2. Wave™ set to export (kW/kVAr) set points at the PCC.
4. Wind Turbine Simulator (WTS) profile {10-100} kW.
5. Photovoltaic Simulator (PV) profile {0-23} kW.
A.3.1 DER Available and System Exporting Power
A.3.1a Baseline:
2. Verify proper export (kW/kVAr) control.
A.3.2 DER Available and System Exporting Power: Renewable Variations
This test case will demonstrate Wave™ export power functionality while connected to the utility
with disturbances in the renewable resources.
Initial Conditions:
Test steps:
A.3.2b Loss of PV:
Initial Conditions:
3-8
Test steps:
Initial Conditions:
Test steps:
A.3.3 DER Available and System Exporting Power: Generator Variations
This test case will demonstrate Wave™ export power functionality while connected to the utility
with disturbances in the generator resources.
A.4 Test Case – DER Available, and the System Is at Net-Zero Power Flow Across
the PCC
This test case will demonstrate net-zero power flow functionality while connected to the utility.
2. Wave™ set to maintain zero import/export (kW/kVAr) at the PCC.
3-9
A.4.1 DER Available, and the System Is at Net-Zero Power Flow Across the PCC
A.4.1a Baseline:
2. Verify near net-zero power flow across PCC.
A.4.2 DER Available, and the System Is at Net-Zero Power Flow Across the PCC:
Renewable Variations
This test case will demonstrate Wave™ net zero power flow functionality while connected to the
utility with disturbances in the renewable resources.
Initial Conditions:
Test steps:
A.4.2b Loss of PV:
Initial Conditions:
Test steps:
Initial Conditions:
3-10
Test steps:
A.4.3 DER Available, and the System Is at Net-Zero Power Flow Across the PCC:
Generator Variations
This test case will demonstrate Wave™ net zero power functionality while connected to the
utility with disturbances in the generator resources.
A.4.4 DER Available, and the System Is at Net-Zero Power Flow Across the PCC: Loss
of Communications
This test case will demonstrate Wave™ net zero power functionality while connected to the
utility with loss of communications between Wave™ and Integrid assets.
A.4.4a Loss of Communications:
1. Disconnect Wave™ hardware from the Ethernet network, thus disabling communications
between Wave™ and Integrid assets.
2. Log the response of each asset, and the system as a whole.
3-11
Use Case B: Separating the Microgrid from the Utility
The focus of this case is clean separation of the microgrid or cluster from the utility, which can
occur for two reasons:
1. The system operator requests to separate the microgrid from the utility.
2. An unplanned event occurs where utility power is lost (including frequency or voltage
deviations) and the microgrid is separated from the utility.
The compliance of the Wave™ Controller with respect to Technical/Functional requirements C.1
and C.4 (as outlined in FOA 997) will be evaluated.
For the C.4 requirement regarding Protection, there will be two approaches for introducing a
fault in the system. Since the local utility power supply cannot be adjusted to non-conformance
levels, our approach will be to disconnect the power transformer (PT) circuit of the PCC
protective relay that will cause it to trip the PCC breaker. The system would then respond to the
utility separation in a controlled manner. Also, to further demonstrate Spirae’s Wave™, power
flow at the PCC would be set to some non-zero import/export value during the test sequences.
Another variation to the test sequences will be to initiate a demand response or dispatch signal
from an external source. Additional variations will include starting the disconnect sequences
with certain assets unavailable.
B.1 Test Case – Planned Disconnection
The system operator requests to separate the microgrid from the utility.
B.1.1 Planned Disconnection Using Spirae Wave™ Interface
This test case will demonstrate Wave™ utility separation functionality during a planned
disconnection. The disconnection will be initiated via the controller operator interface.
B.1.1a Baseline:
2. Operator commands island operation via Wave™
3. Main tie CB-SG3B-1 (PCC breaker) opens.
4. DER set points and modes provided by Wave™.
5. Verify that the microgrid runs for several minutes.
3-12
B.1.1b High Renewable Penetration:
Initial Conditions:
Test steps:
B.1.1c High Load:
Initial Conditions:
Test steps:
B.1.2 Planned Disconnection Using Spirae Wave™ Interface: Renewable Variations
disconnection with renewable variations. The disconnection will be initiated via the controller
operator interface.
3-13
B.1.2a Loss of Wind (Curtailment):
Initial Conditions:
Test steps:
B.1.2b Loss of PV:
Initial Conditions:
5. PV stopped, and breaker opened.
Test steps:
B.1.2c Loss of Wind and PV:
Initial Conditions:
4. WTS stopped, and breaker opened.
5. PV stopped, and breaker opened.
3-14
Test steps:
B.1.3 Planned Disconnection Using Spirae Wave™ Interface: Generator Variations
disconnection with generator variations. The disconnection will be initiated via the controller
operator interface.
B.1.3a Loss of One Generator:
Initial Conditions:
Test steps:
B.1.4 Planned Disconnection Using an External Source
disconnection. The disconnection will be initiated via an external laptop or workstation sending
a dispatch signal to Wave™.
3-15
B.1.4a Planned Disconnection Using an External Source
Test steps:
1. Operator commands island operation via an external source such as a separate
workstation or laptop.
2. Operator commands net-zero power flow at the PCC via Wave™.
3. Verify proper net-zero (kW/kVAr) control.
B.2 Test Case – Unplanned Disconnection
An unplanned event occurs where utility power is lost (including frequency or voltage
deviations) and the microgrid is separated from the utility.
2. Wave™ set to non-zero import or export (kW/kVAr) set points at the PCC.
B.2.1 Unplanned Disconnection Via Manual Breaker Trip
This test case will demonstrate Wave™ utility separation functionality during an unplanned
disconnection. The disconnection will be executed by manually tripping the main tie PCC
breaker.
B.2.1a Baseline:
1. Operator opens PCC breaker at utility switch gear.
B.2.2 Unplanned Disconnection Via Manual Breaker Trip: Renewable Variations
disconnection, with renewable variations. The disconnection will be executed by manually
tripping the main tie PCC breaker.
3-16
B.2.2a Loss of Wind:
Initial Conditions:
Test steps:
B.2.2b Loss of PV:
Initial Conditions:
Test steps:
B.2.2c Loss of Wind and PV:
Initial Conditions:
3-17
Test steps:
B.2.3 Unplanned Disconnection Via Manual Breaker Trip: Generator Variations
disconnection, with generator variations. The disconnection will be executed by manually
tripping the main tie PCC breaker.
B.2.3a Loss of One Generator:
Test steps:
B.2.4 Unplanned Disconnection Via Protective Relay Trip
disconnection. The disconnection will be executed by injecting abnormal voltage and/or
frequency signals at the PCC, and allowing the protective relay to trip the PCC breaker.
3-18
B.2.4a Unplanned Disconnection Via Protective Relay Trip
Test steps:
1. Simulate abnormal voltage and/or frequency signals at the PCC.
2. Main tie CB-SG3B-1 (PCC breaker) opens due to protective relay trip.
B.2.5 Unplanned Disconnection Via Wave™
disconnection. The disconnection will be executed by injecting abnormal voltage and/or
frequency signals at the PCC, and allowing Wave™ to trip the PCC breaker.
B.2.5a Unplanned Disconnection Via Wave™
Test steps:
1. Simulate abnormal voltage and/or frequency signals at the PCC.
2. Main tie CB-SG3B-1 (PCC breaker) opened by Wave™ after sensing abnormal
frequency and/or voltage on the grid side of the PCC.
Use Case C: Operating the Microgrid While Separated from the Utility
The focus of this use case is stable and reliable operation of DERs to support local loads while
separated from the utility.
The compliance of the Wave™ Controller with respect to Technical/Functional requirements
C.3, C.4 and C.5 (as outlined in FOA 997) will be evaluated.
C.1 Test Case – Islanded Operation
This test case will demonstrate Wave™ functionality while separated from the utility.
1. Main tie CB-SG3B-1 (PCC breaker) opened.
2. Wave™ set to maintain island mode.
3-19
C.1.1a Baseline
2. Verify that the microgrid runs for several minutes and is reliable based on the C.3
requirements outlined in FOA 997.
C.1.1b Large Load Step
This test case will demonstrate Wave™ functionality while separated from the utility (Islanded
Operation) with a large load step introduced to the system.
Initial Conditions:
3. Load bank #2 set to manual control mode.
Test steps:
1. Set load bank #2 to 70kW.
3. Introduce a large load step that is equal to 20% of total available generation at that time,
or if the new total calculated load exceeds the capacity of load bank #2, set the load bank
to 106kW.
C.1.2 Island Operation: Renewable Variations
Operation) with variations in renewable resource availability.
C.1.2a Loss of Wind:
Initial Conditions:
3-20
Test steps:
C.1.2b Loss of PV:
Initial Conditions:
Test steps:
C.1.2c Loss of Wind and PV:
Initial Conditions:
Test steps:
C.1.3 Island Operation: Generator Variations
This test case will demonstrate Wave™ functionality while separated from the utility with
variations in generator availability, with one generator in swing mode, and the other in baseload
mode.
3-21
C.1.3a Loss of Swing Generator
1. Identify the swing generator, and turn it off via its local controls.
3. Verify that the microgrid runs for several minutes and is reliable based on requirements
provided in DOE C3.
4. Turn the offline generator back on via its local controls.
C.1.3b Loss of Baseload Generator
1. Identify the baseload generator, and turn it off via its local controls.
3. Verify that the microgrid runs for several minutes and is reliable based on requirements
provided in DOE C3.
4. Turn the offline generator back on via its local controls.
C.1.4 Island Operation: Internal Short
Operation) with an internal power system short circuit.
3. Load bank #2 set to 50 kW.
3-22
C.1.4a Internal Short
Test steps:
1. Inject a short circuit in the microgrid system. This will be accomplished by increasing the
load on load bank #2, thus drawing a large amount of current to replicate short circuit
conditions. The overcurrent relay on load bank #2 is rated for 150A, and is not
configurable. The load bank can only draw 127A. It is only possible to increase the load,
in step fashion, to replicate a short circuit condition, even though the load bank itself will
not trip off during the test. The load will be stepped from 50kW to 100kW (60A to
120A).
C.1.5 Island Operation: Loss of Communications
This test case will demonstrate Wave™ functionality while separated from the utility with loss of
communications between Wave™ and Integrid assets.
C.1.5a Loss of Communications
Test steps:
1. Disconnect Wave™ hardware from the Ethernet network, thus disabling communications
between Wave™ and Integrid assets.
2. Log the response of each asset, and the microgrid system as a whole.
Use Case D: Connecting the Microgrid to the Utility

The focus of this use case is demonstrate synchronization and reconnection of the microgrid to
the utility grid. For this, the microgrid must be running in a stable fashion, and factors which
resulted in separation should have been resolved.
The compliance of the Wave™ Controller with respect to Technical/Functional requirements C.2
and C.4 (as outlined in FOA 997) will be evaluated.
3-23
D.1 Test Case – Resynchronization Operation
The system operator requests to synchronize the microgrid to the utility.
1. Main tie CB-SG3B-1 (PCC breaker) initially open.
D.1.1 Resynchronization Operation
This test case will demonstrate Wave™ utility synchronization functionality. Resynchronization
will be initiated via the controller operator interface.
D.1.1a Baseline:
1. Operator commands resynchronization operation via Wave™.
2. After synchronization of voltage magnitude and frequency slip, Main tie CB-SG3B-1
(PCC breaker) closes.
3. Verify that the resynchronization occurs in compliance with requirements provided in C2.
D.1.2 Resynchronization Operation: Renewable Variations
This test case will demonstrate Wave™ utility synchronization functionality with renewable
variations. Resynchronization will be initiated via the controller operator interface.
D.1.2a Loss of Wind (Curtailment):
Initial Conditions:
Test steps:
3. Verify that the resynchronization occurs in compliance with requirements provided in C2.
3-24
D.1.2b Loss of PV:
Initial Conditions:
Test steps:
3. Verify that the resynchronization occurs in compliance with requirements for C.2
outlined in FOA 997.
D.1.2c Loss of Wind and PV:
Initial Conditions:
Test steps:
D.1.3 Resynchronization Operation: Generator Variations
This test case will demonstrate Wave™ utility synchronization functionality with generator
variations. Resynchronization will be initiated via the controller operator interface.
3-25
D.1.3a Loss of Baseload Generator:
Initial Conditions:
6. Baseload generator turned off, and breaker opened.
Test steps:
Use Case E: Reduction in Outage Time

The focus of this case is to demonstrate the use of Spirae’s Wave™ to reduce the average outage
time of the microgrid. The local utility’s publically reported System Average Interruption
Duration Index (SAIDI) will be used as the baseline metric for outage time.
The only assets at Integrid that can be used in isochronous and voltage master modes (and are
therefore required to maintain the microgrid) are GEN2 and GEN3. Both generators receive
natural gas from a utility supplied line that does not have any reported outage or interruption
metrics associated with it.
New outage times for the microgrid will be calculated for the following scenarios.
1. Once the utility experiences an electrical outage, the time required for Wave™ to ensure
that all pre-outage load has been restored will be the new outage time metric for the
microgrid.
2. Once the utility experiences an electrical outage, the time required for Wave™ to ensure
that all pre-outage critical load has been restored will be the new outage time metric for
the microgrid. Critical load will be pre-assigned for this scenario.
E.1 Test Case – Response to Outage
1. Main tie CB-SG3B-1 (PCC breaker) initially closed.
3-26
3. Load bank #2 set to 100kW.
E.1.1 Microgrid Response to an Unplanned Disconnection
disconnection and monitor the time to recover power to the microgrid loads. The disconnection
will be executed by manually tripping the main tie PCC breaker. Total pre-outage load is set to
100kW, of which 40kW is considered to be critical.
E.1.1a Unplanned Disconnection While Maintaining Non-Zero Import/Export at PCC
Test steps:
5. Load can be shed in case the microgrid voltage and/or frequency are/is observed to
violate known stability bounds.
6. In case load had to be shed, log restoration time for critical load and total load.
E.1.1b Unplanned Disconnection When Only Renewables Were Initially Online
Initial Conditions:
1. Main tie CB-SG3B-1 (PCC breaker) initially closed.
2. Wave™ set to monitor microgrid.
3. Load bank #2 set to 100kW.
6. GEN2, GEN3, and SC are turned off, and breaker opened.
Test steps:
5. Log restoration time for critical load and total load.
3-27
4
HARDWARE IN LOOP (HIL) TESTING OF MICROGRID
SYSTEMS
This chapter describes the plan for Hardware-in-the-Loop (HIL) testing of the Spirae Wave
microgrid controller for the selected microgrid target community, Buffalo Niagara Medical
Campus (BNMC) and surrounding Fruitbelt areas at NREL. It describes the HIL test
configuration to be constructed, the functionality to be tested, and an outline of the test
procedure.
The purpose of HIL testing is the validation of the Spirae Wave controller’s ability to meet the
following functional requirements (outlined in FOA 997) at the selected target community:
C1 (Disconnection), C2 (Resynchronization and Reconnection), C3 (Steady-State Frequency
Range, Voltage Range, and Power Quality), C4 (Protection), and C5 (Dispatch). In order to
validate functional requirements C1-C5, the Wave controller will be tested for the target
community under four major scenarios:
 Operating the Microgrid While Connected to the Utility
 Separating the Microgrid from the Utility
 Operating the Microgrid while Separated from the Utility
 Connecting the Microgrid to the Utility
Table 4-1 shows the mapping of the test scenarios to functional requirements
Table 4-1
Mapping of scenarios to functional requirements
Scenario description C1 C2 C3 C4 C5
Disconnection Resynchronization Steady-State Protection Dispatch
and Reconnection Frequency
Range, Voltage
Range, and
Power Quality
Operating the Microgrid X
While Connected to the
Utility
Separating the Microgrid X X
from the Utility
Operating the Microgrid X X X
while Separated from the
Utility
Connecting the X
Microgrid to the Utility
4-1
HIL Test Configuration
HIL testing of the Spirae Wave microgrid controller will be performed at the Energy Systems
Integration Facility (ESIF) at NREL. A reduced-order model of the Buffalo Niagara Medical
Campus (BNMC) will be simulated within the RTDS real-time simulator, as shown in
Figure 4-1. This model provides a good approximation of the actual community and models the
operation of the microgrid in enough detail to allow for evaluation of the microgrid controller.
Instead of four parallel distribution lines and parallel substation transformers, a single line and
transformer equivalent is used as a substitution. Also, the load at each member institution
(Medical School, Roswell, Kaleida, and Cleveland) and at the Fruitbelt neighborhood is
aggregated as a single load equivalent to the total load profile. Generation is also aggregated, but
the different types of generation are preserved. For example, the total diesel generation at a
campus is aggregated into a single equivalent diesel plant, but other types of generation (such as
natural gas, PV, etc.) are kept distinct. Since the aggregated loads and generators are
controllable and variable, the actual operation of the system is a good approximation of the real
system.
Figure 4-1
HIL test setup functional diagram, where “PV” indicates photovoltaic solar generation, “G”
indicates a synchronous generator – either diesel or natural gas; and “CHP” indicates a combined
heat and power generation
4-2
A Wave Commander microgrid control system (provided by Spirae) will run all of the Wave
control software necessary to control the BNMC microgrid. The Wave controller device will be
coupled with the Real-Time Digital Simulator (RTDS) that runs the reduced-order model of
BNMC’s electricity distribution system. The RTDS will solve the model of the feeder (for a
configuration based on control commands from the Wave controller) in real-time and generate
measurement signals as if it were the actual facility electricity distribution system. These
measurement signals will be received by the Wave control system, which will act on them and
produce control commands for the facility’s controllable devices, thus closing the control loop in
real-time as if it were connected to the real facility.
The battery energy storage system (BESS) at the Medical School will be represented in hardware
by a grid-following 480V/540 kW 3-phase battery inverter. The bus where the BESS connects
will be reflected in hardware as a 480V 3-phase bus. A grid simulator – a controllable,
bidirectional AC source - will be used to create the interface between the hardware AC bus and
virtual parts of the model. The RTDS will control the grid simulator to follow the (scaled)
voltage on the modeled bus. The current output of the AC source will be measured and reflected
in the RTDS model as a (scaled) current source. The voltage and current scaling between the
RTDS model and the hardware AC bus will be selected to allow the inverter power hardware
connected to the AC bus at ESIF to scale-appropriately represent the inverter power hardware to
be connected at the target community site. A controllable, bidirectional DC supply will be
controlled to act as a battery.
This controller and power hardware-in-the-loop (CHIL/PHIL) test setup8 allows realistic testing
of the ability of the Wave controller to control and regulate the facility electricity distribution
system under conditions that would be difficult or expensive to create in the actual system.
The results will depend on the communication delay between the RTDS and the Wave controller,
which can be very small in a HIL test setup. We will include a delay in the communications path
that is typical of a field installation, since this delay could cause instabilities, especially during
islanded operation, but we will not characterize the impact of the delay on the results as part of
this testing.
A control algorithm will be developed for the microgrid switch (circuit breaker) at the PCC to
disconnect and resynchronize the microgrid. The control algorithm will monitor the three phase
voltage waveforms on both the sides of the microgrid switch and will operate based on the
following: RMS voltage, frequency, and phase angle.
Both internal and external faults will be modeled to evaluate the microgrid controller response to
fault conditions. It will be assumed that the faults will be cleared by the protection scheme
employed by the distribution system owner, and a simple time based fault clearing will be
employed in the simulation.
8
The project team proposes that CHIL testing in support of Phase 1 and CHIL/PHIL testing in support of Phase 2 be
conducted simultaneously due to time constraints.
4-3
Operating the Microgrid While Connected to the Utility
Purpose
The purpose is to validate the ability of the Wave controller to dispatch the DERs, while grid-
connected, in order to achieve the following objectives: 1) survivability, 2) economic operation
and 3) satisfactory environmental performance, as specified by functional requirement C5:
Dispatch Outlined in FOA 997.
Procedure
The test setup as shown in Figure 4-1 will be used and the RTDS will run the reduced order
model in real-time for the specific community under test. A specified load and generation profile,
for non-dispatchable generation, will be applied (accelerated as necessary) that is representative
of real-world conditions for the community. The load and non-dispatchable generation profiles
will be selected such that, at times, the generation exceeds the load, and at other times, the load
exceeds the generation, if both conditions are feasible for the target community.
For the baseline, the Wave controller will be disabled. For other test cases, the Wave controller
will provide dispatch. The simulated RMS voltage, voltage phase angle, voltage frequency, RMS
current, current phase angle, active and reactive power will be recorded at a rate of 60Hz at the
utility PCC and on the microgrid side of the microgrid switch. The simulated voltage and current
waveforms will be recorded at a rate of 1000+ Hz at the utility PCC and on the microgrid side of
the microgrid. The simulated active and reactive power for all loads and distributed energy
resources (DERs) within the microgrid, in addition to the state of charge of any batteries and the
fuel level of any generators within the microgrid, will be recorded at a rate of 60Hz under both
control conditions. In this scenario, the Microgrid Switch (see Figure 4-1) is closed, and the
target community microgrid is connected to the external utility, which effectively controls both
voltage and frequency on the microgrid.
Two test cases will be tested.
Test Case A1: Normal Grid-Connected Operation with No Dispatch (Baseline)
In this test case, no dispatch will be run and all dispatchable generation will be off.
Initial Conditions:
1. Microgrid switch (CBK_PCC) closed, CBK_NL closed, CBK_EL open.
2. Set assets in Wave™ to offline.
3. Selected load profiles programmed (accelerated, e.g., 24 minutes equivalent to 24 hours.)
4. Selected non-dispatchable generation profiles programmed (accelerated)
Test Scenario:
5. Determine the baseline metrics
4-4
Test Case A2: Normal Grid-Connected Operation with Dispatch
In this test case, the microgrid controller will be set to provide dispatch.
Initial Conditions:
1. Microgrid switch switch (CBK_PCC) closed, CBK_NL closed, CBK_EL open.
2. Activate import/export control and provide selected active and reactive power setpoints.
Test Scenario:
5. Set Wave™ to dispatch according to community-specific objective function
6. Determine the metrics for Wave providing dispatch
Requirements
The load and non-dispatchable generation profiles used for the tests shall be feasible for the
target community.
The test report shall record the definition of the metrics and the calculated metrics.
Criteria
Metrics related to the objectives of survivability, economic operation and satisfactory
environmental performance for each resulting test will be calculated, and the Wave controller
performance calculated by comparison of these metrics between the baseline and other tests. The
microgrid controller shall be considered capable of providing dispatch that meet the specified
objectives if the metrics calculated for the test case with dispatch shows improvement over the
baseline metrics.
The survivability metric will reflect whether sufficient resources (e.g., generation and/or energy
storage) are operating and available to support the microgrid’s seamless transition to island mode
for the duration of the test case and will be calculated as follows:
𝑃𝑙𝑜𝑎𝑑𝑠,𝑛
𝑆𝑛 =
𝑃𝑎𝑣𝑎𝑖𝑙,𝑛
where Ploads,n is the total active power of all loads during time step n and Pavail,n is the total power
available from all dispatchable generation during time step n. The survivability metric should be
less than one at all time steps.
The economic operation metric will reflect the energy cost of operating the microgrid for the
duration of the test case, based on electric and natural gas tariffs and diesel fuel costs, as
applicable.
4-5
The cost of operating the microgrid over the duration of the scenario simulated, C, will be
calculated as follows:
𝐶 = ∑ Pgrid,n ∙ τ ∙ 𝑐𝑔𝑟𝑖𝑑,𝑛 + ∑ {∑ PDER,k,n ∙ τ ∙ 𝑐DER,k,n } + 𝑐𝐷 ∙ max(Pgrid,n )

N 𝑘 N
where Pgrid is the power supplied by the grid, cgrid is the cost of grid power, PDER,k is the power
supplied by the kth DER resource within the microgrid, cDER,k is the cost of supplying power from
the kth DER resource within the microgrid and cD is the demand charge associated with grid
power. Note that cDER,k will be based on natural gas tariffs and/or diesel fuel costs, as applicable.
The environmental performance metric will reflect the estimated CO2 emissions, based on a fuel
mix for grid power that is reflective of the service territory of the BNMC community, for the
duration of the test case.
The estimated CO2 emissions associated with operating the microgrid over the duration of the
scenario simulated, ϑ, will be calculated as follows:
𝜗 = ∑ Pgrid,n ∙ τ ∙ 𝜉𝑒 + ∑ {∑ PDER,k,n ∙ τ ∙ 𝜉g }
N 𝑘 N
where ξe is the electricity emissions factor for the grid and ξg is the diesel or natural gas
emissions factor, as applicable. Note that ξg is zero for PV and BESS.
Separating the Microgrid from the Utility

Purpose
The purpose is to validate the ability of the Wave controller to successfully separate the target
community microgrid from the external utility, either as a part of a planned operation or in
response to an external fault or loss of utility, and that it meets the specifications of functional
requirements C1 (Disconnection) and C4 (Protection).
Procedure
The test setup as shown in Figure 4-1, will be used and the RTDS will run the reduced order
model in real-time for the specific community under test (BNMC). A specified load and
generation profile will be applied (accelerated as necessary) that is representative of real-world
conditions for the community. The load and generation profiles will be selected such that, at
times, the generation exceeds the load, and at other times, the load exceeds the generation, if
both conditions are feasible for the target community. The separation will be tested at a time that
the load exceeds the generation, and at a time that the generation exceeds the load (i.e., the
microgrid may be importing or exporting power at the time of separation).
The simulated RMS voltage, voltage phase angle, voltage frequency, RMS current, current phase
angle, active and reactive power will be recorded at a rate of 60Hz at the utility PCC and on the
microgrid side of the microgrid switch. The simulated voltage and current waveforms will be
recorded at a rate of 1000+ Hz at the utility PCC and on the microgrid side of the microgrid
switch. In this scenario, the Microgrid Switch is initially closed, and the target community
microgrid is connected to the external utility. Based on these measurements, the ability of the
4-6
Wave controller to meet the specifications in functional requirement C1 during separation will be
assessed. In addition, the ability of the Wave controller to appropriately respond to an external
fault by separating from the utility will be assessed (functional requirement C4).
Three test cases will be performed:
Test Case B1: Planned Separation
In this test case, the external utility remains within normal operational conditions, and the
microgrid separation is part of a planned operation.
Initial Conditions:
1. Microgrid switch (CBK_PCC) closed, CBK_EL open and CBK_NL closed.
2. Selected load profiles programmed (accelerated)
4. Wave™ island and import/export controls enabled.
Test Scenario:
5. Request Wave™ to island, verify that Wave brings power flow across PCC to zero and
opens the microgrid switch.
6. Verify that Wave™ sets which assets are the isochronous master and voltage master.
7. Use Wave™ to shed Station 34 load, turn off Station 34 generation and open CBK_NL
and close CBK_EL. Then add Station 34 assets to Microgrid control group and restore
station 34 loads.
8. Verify that the microgrid runs for several minutes to verify stable operation.
Test Case B2: Unplanned Separation Due to an External Fault
In this case, the microgrid must perform an emergency separation from the utility in response to
an external fault.
Initial Conditions:
4. Wave™ island and import/export controls enabled
Test Scenario:
5. Apply an external fault in the simulation
6. Verify that the microgrid switch opens within islanding criteria
7. Verify that Wave™ sets which assets are the isochronous master and voltage master
8. Verify that the microgrid runs for several minutes to verify stable operation
Test Case B3: Unplanned Separation Due to Loss of Utility
In this case, the microgrid must perform an emergency separation from the utility in response to
an unplanned utility outage and the formation of an unintended island.
4-7
Initial Conditions:
2. Selected load profiles programmed (accelerated, e.g., 24 minutes equivalent to 24 hours)
4. Wave™ island and import/export controls enabled
Test Scenario:
5. Simulate an unintentional islanding condition
6. Verify that the microgrid switch opens within islanding criteria
8. Verify that the microgrid runs for several minutes to verify stable operation
Requirements
 The model of the microgrid switch in the RTDS will include a time delay typical of the time
taken by the mechanical circuit breaker to open.
 The models of the DERs in the microgrid will include trip settings.
 The load and generation profiles used for the tests shall be feasible for the target community.
 The test report shall record the time between the start of the voltage or frequency range
excursion and microgrid islanding from the area utility.
Criteria
For functional requirement C1 (Disconnection), the microgrid controller shall be considered
capable of separating the target community from the utility if the maximum islanding time
criteria provided in the modified version of IEEE Standard 1547.1 (superseding Table 1 and
Table 2 of DE-FOA-0000997), are met.
For functional requirement C4 (Protection), the microgrid controller shall be considered capable
of providing adequate protection if;
1. for an “external” fault, the microgrid controller opens the microgrid switch and interrupts
the flow of fault current from the microgrid to the utility grid within 0.16 seconds of the
fault occurrence; and if,
2. for a loss of utility, the microgrid controller opens the microgrid switch and disconnects
the microgrid from the utility grid when an unintentional island is formed beyond the
boundaries of the microgrid consistent with the requirement of IEEE 1547.2.
Operating the Microgrid while Separated from the Utility

Purpose
The purpose is to validate the ability of the Wave controller to successfully operate the target
community microgrid within normal operating conditions while separated from the external
utility (microgrid switch is open). It will validate that voltage and frequency are maintained
within specified ranges under typical load and generation profiles (functional requirement C3).
The HIL simulation may use average models for inverters and as such the simulation results will
4-8
not be able to verify other power quality conditions. It will also validate that the controller
responds appropriately to internal faults (functional requirement C4), and appropriately
dispatches generation and controllable load to meet the survivability objective during islanded
operation (functional requirement C5).
Procedure
recorded at a rate of 1000+ Hz at the utility PCC and on the microgrid side of the microgrid. The
simulated active and reactive power for all loads and distributed energy resources within the
microgrid, in addition to the state of charge of any batteries within the microgrid, will be
recorded at a rate of 60 Hz. The test setup as shown in
Figure 4-1 will be used and the RTDS will run the reduced order model in real-time for the
specific community under test. A load and non-dispatchable generation profile will be applied
(accelerated as necessary) that are representative of real-world conditions for the community.
The load and generation profiles will be selected such that, at times, the non-dispatchable
generation exceeds the load, and at other times, the load exceeds the non-dispatchable
generation, if both conditions are feasible for the target community.
Two test cases will be performed:
Test Case C1: Normal Islanded Operation
In this test case, the microgrid is in islanded mode (separated from the external utility). Both a
baseline case, with no dispatch, and a case with dispatch activated will be simulated.
Initial Conditions:
5. Request Wave™ to island, verify that Wave opens the microgrid switch
Test Scenario:
6. Verify that the microgrid meets the requirements provided in C.3 while running the
selected load and generation profiles
7. Determine the islanded survivability metric
Test Case C2: Internal Short During Islanded Operation
In this test case, an internal short occurs during islanded operation.
4-9
Initial Conditions:
5. Request Wave™ to island, verify that Wave opens the microgrid switch.
Test Scenario:
6. Verify that the microgrid meets the requirements provided in C.3 while running the
selected load and generation profiles
7. Apply an internal fault and verify that the microgrid clears the fault and meets the
requirements provided in C.3 after clearing the fault, and record any change in load
served
Requirements
The RTDS model of the community must include sheddable load components if load shedding is
available in the target community.
The load and non-dispatchable generation profiles used for the tests shall be feasible for the
target community.
The test report shall record the voltage and frequency at the PCC with the utility, on the
microgrid side of the microgrid switch, during the simulation.
The test report shall record the critical and non-critical load served during the simulation and the
calculated islanded survivability metric. The survivability metric will reflect whether the
controller is managing energy resources consistent with ensuring service to the microgrid critical
loads for the duration of the islanded state and will be calculated as follows:
∑𝑁 𝑃𝑙𝑜𝑎𝑑𝑠,𝑐𝑟𝑖𝑡,𝑑𝑖𝑠𝑝𝑎𝑡𝑐ℎ,𝑛 ∙ 𝜏
𝑆=
∑𝑁 𝑃𝑙𝑜𝑎𝑑𝑠,𝑐𝑟𝑖𝑡,𝑏𝑎𝑠𝑒𝑙𝑖𝑛𝑒,𝑛 ∙ 𝜏
where τ is the time step of the time series inputs used in the simulation, N is the total number of
time steps in the time series inputs and Ploads,crit are the active power of the critical loads. The
metric therefore determines the ratio of the total energy delivered over the duration of the
scenario.
Criteria
For functional requirement C3 (Steady-State), the microgrid controller must meet the voltage and
frequency criteria provided in DE-FOA-0000997, i.e., it must:
1. Maintain the frequency in the range 59.3 Hz < f < 60.5 Hz – barring customer-specific
requirements that may override this range.
2. Maintain the voltage in the range 0.95 pu<V< 1.05 pu, according to ANSI 84.1-2006
standards.
4-10
For functional requirement C4 (Protection), the microgrid controller shall be considered capable
of providing adequate protection if, for an “internal” fault, the microgrid controller is able to
clear the fault and minimize loss of load.
For functional requirement C5 (Dispatch), the islanded survivability metric will reflect whether
the microgrid controller manages the energy resources consistent with ensuring service to the
microgrid critical loads for the duration of the islanded state. The survivability metric should
equal one for successful operation.
Connecting the Microgrid to the Utility

Scope
The purpose is to validate the ability of the Wave controller to reconnect the (islanded) microgrid
to the utility following a restoration of utility service. It must resynchronize the microgrid to the
external utility and maintain conditions in the range specified during reconnection (functional
requirement C2) and restore the microgrid to normal grid-connected operation following
reconnection (functional requirement C3).
Procedure
recorded at a rate of 1000+ Hz at the utility PCC and on the microgrid side of the microgrid
switch. The test setup as shown in
Figure 4-1 will be used and the RTDS will run the reduced order model in real-time for the
specific community under test. A load and non-dispatchable generation profile will be applied
(accelerated as necessary) that are representative of real-world conditions for the community.
The load and generation profiles will be selected such that, at times, the non-dispatchable
generation exceeds the load, and at other times, the load exceeds the non-dispatchable
generation, if both conditions are feasible for the target community.
Three test cases will be performed:
Test Case D1: Reconnection
In this test case, the microgrid is initially operating in islanded mode. This test will be performed
for the case where load exceeds the installed microgrid generation capacity. Following
reconnection, the microgrid may be exporting power to or importing power from the utility.
Initial Conditions:
1. Microgrid switch closed
2. Selected load profiles programmed
3. Selected non-dispatchable generation profiles programmed
4. Wave™ set to zero PCC export (kW/kVAr) set point
5. Wave™ set to “Activate Island” controls
4-11
Test Scenario:
6. Simulate the microgrid switch opening
8. Verify that the microgrid runs for several minutes
9. Request Wave™ to send synchronize signal
10. Verify that the microgrid switch closes and that stable operation is achieved
Requirements
The model of the microgrid switch in the RTDS will include a time delay typical of the time
taken by the mechanical circuit breaker to close.
The models of the DERs in the microgrid will include trip settings.
The load and generation profiles used for the tests shall be feasible for the target community.
The test report shall record the frequency difference, voltage magnitude difference, and voltage
phase angle difference between the area utility and microgrid at the time that reconnection
occurs.
Criteria
For functional requirement C2 (Resynchronization and Reconnection), the microgrid controller
shall be considered capable of reconnecting the target community to the utility if it meets the
criteria provided in Table 3 of DE-FOA-0000997.
4-12
5
MICROGRID CONTROLLER FIELD TESTING AT EDF
CONCEPT GRID
EDF R&D has created Concept Grid on its "Les Renardières" site in the south of Paris. The
Concept Grid distribution network includes 3 km of medium voltage network (20 kV) supplying
7 km of low voltage network. Additional electrical hardware – such as RLC banks (resistors
inductors capacitors), an amplifier and a simulator – allow the characteristics of larger size
distribution networks to be reproduced in a controlled environment. To make Concept Grid even
more representative of real distribution networks, EDF has reproduced a residential
neighborhood with 5 houses of 20m2 each fitted with smart meters, remote controlled household
appliances, reversible heat pumps, micro-wind turbines, photovoltaic panels, terminals for
charging electric vehicles, storage systems. This residential neighborhood of sample homes
brings together new technologies such as renewable energies, storage and electric mobility. The
communication functions are provided by different technologies such as power line carriers
(PLC), radio and two separated fiber optics telecommunication networks.
A part of this network provides control i.e. the management and the supervision of Concept Grid
from the control station with:
 The feedback of information;
 The flow of commands;
 The automation of the protective device coordination.
The other part of the network is dedicated to the transmission of experimental data and to the
remote control of equipment located in the houses using networked meters.
MAIN CIRCUITS to recreate an electrical network
 3 km of MV overhead and underground lines (20 kV)
 120 km of MV network simulated by resistors, inductors and capacitors km of LV circuits
 2 distribution substations (400 kVA)
 3 neutral point treatments (20 kV) (resistance, Petersen coil, active)
 1 motor-generator (50 kVA)
 1 communication network by power line carrier, radio and optical fiber (IEC 61850)
5-1
SOURCES to supply the grid with electricity
 1 power transformer 63kV/20kV (20 MVA)
 Photovoltaic panels (20 kVA)
 2 micro-wind turbines
 1 LV power amplifier (120 kVA generating)
 Battery storage systems (50 kVA)
LOADS to reproduce power consumption
 1 office building (500 kVA)
 sample houses fitted with electrical devices for domestic use (50 kVA)
 Heat pumps (up to 50 kVA)
 The charging terminals for electric vehicles (up to 100 kVA)
 1 LV power amplifier
Figure 5-1, parts a and b, provides the key elements within the Concept Grid. Figure 5-2 captures
the one-line diagram of the concept. Based on initial discussions with EDF personnel a smaller
segment of the Concept grid will be utilized for testing. This is captured in Figure 5-3. A list of
equipment that could potentially be utilized during testing is shown in Table 5-1.
5-2
a) b)
Figure 5-1
Key components of the Concept Grid
5-3
Figure 5-2
Low voltage simplified schematic of a Concept Grid part
5-4
Figure 5-3
Low voltage simplified schematic of Concept Grid covering potential microgrid boundary for field
trial
5-5
Table 5-1
List of available equipment and location
Nominal Power Connection Connected

Device Brand Reference Serial Number Communication
(kVA) 3ph/1ph at
Fronius IGplus 150V-3 12 3 phases 26035725 house 3 local command only
STP 15000TL-10 15 3 phases 2110445311 house 2 Modbus TCP IP

PV Inverter
SMA
Modbus TCP / IP
Sunny island SI6.0H-11 4 1 phase 1261002632 house 3
(in progress)
SRK50ZJ-S SRC50ZJ-S 1,6 1 phase 242506261RE house 3
Heat Pump Mitsubishi SRK25ZJ-S SRC25ZJ-S 0,8 1 phase 145409534RE house 2

MSC-GE-35VB MUH-GE-35VB 1 1 phase 1010713 house 1
MSZ-GE-42VA MUZ-GE42VA 1,4 1 phase 2005899 house 1
Resistive load 0 -1kW-600 kW
kVA A14-1488 3 phases B600-1M – June 14 mobile Modbus TCP / IP
1 3ph
Resistive load Residential
/ / 600kW 3 phases / Controllable locally
2 neighborhood
Bosch KGN36AW32/01 0,24 1 phase 212020269093000330 house 3
Fridge
Bosch Avantixx 7 WTW86381FF 1 1 phase 462080273572001580 house 3 Loads can be
controlled by
Avantixx 8 WAQ24482FF 2,3 1 phase 433050275838001692 house 3 contactors.
Washing Bosch
machine PSL all houses +
PQube Classic 6 units 3 phases
- 1 mobile
LV
Measurement Atlantic 2 1 phase Modbus TCP/ IP
unit RSGNEP10 - all houses
4 units of 2 kW
S&P TLS-401 1 phase - mobile
each
Loads can be
Radiator Thermor SFMG TRO 1,75 1 phase 1228 19 house 3 controlled by
contactors.
SUNSYS PCS² 33TR or Substation
Socomec 50kVA 3 phase _
SUNSYS PCS² IM 66TR "T"
Energy Puissance substation
_ 120kVA 3 phase _ Modbus TCP/ IP
Storage + "E"
The amplifier is not
directly controlled
Amplifier
by the microgrid
controller.
5-6
Initial Concept Grid Test Plan Description:
This is the description of generic test plan that could be utilized during field trial, including the
description of use cases and functions to be tested, the description of test procedures for each use
case, and the description of validation criteria for each test.
This test plan aims at evaluating the ability of a microgrid controller to perform basic microgrid
use cases. For each Use Case (UC), several scenarios are proposed, i.e. different ways to run the
UC, in order to test different functions of the microgrid controller. The proposed Test Cases
examples are thus concrete examples of how these scenarios can be applied at the Concept Grid
test field.
The Microcontroller will be evaluated in the following uses cases:
 Use Case 1: Set points for active and reactive power flows at the point of coupling when
connected to the grid,
 Use Case 2: Scheduled islanding,
 Use Case 3: Maintain islanding for a given duration.
 Use Case 4: Reconnection to the main grid,
 Use Case 5: Black Start,
Furthermore, Key Performance Indicators (KPI) are proposed, that can be applied to several of
the UC. Although some of these KPI evaluate more the performance of microgrid and/or the
storage system, rather than of the microgrid controller specifically, these indicators are still
pertinent to compare different controlling strategies.
In microgrid configuration, the Concept Grid resources will be used in the following way.
 The battery storage system will be used as voltage and frequency master in islanding mode.
In grid connected mode, the charging and discharging of the battery is controlled by the
microgrid controller.
 The LV circuit breaker located downstream the transformer “T” is considered as the coupling
point with the overlay grid. Transitions from grid connected to islanding mode, and reverse
will be managed by the microcontroller by sending an order to the storage system. Then the
storage system will control the opening and closing circuit breaker.
 The PV inverters will be used as current sources
 The LV amplifier can be used either as a load or as a current source, depending on the Test
Case needs. It can also amplify the current (load/source) of a controllable device in order to
have equivalent impact of multiple controllable device.
 The other loads can be divided between fatal consumption and controllable loads. The
microgrid controller should be able to power on and off the controllable loads.
 The Socomec islanding controller is in charge of the real time battery inverter operation
(maintaining voltage and frequency stability). The Spirae EMS should be able to
communicate with the islanding controller and other RES inverters and loads, in order
optimize the overall microgrid operation (make sure that islanding target duration can be
reached, preventive load shedding…)
5-7
Preliminary Tests, Equipment and System Validation
The purpose of the preliminary tests described here is to validate the security of the system, the
proper functioning of the different equipment and of the interfaces between the equipment.
Protection Plan
The Concept Grid platform has done several microgrid tests using the proposed network
configuration and equipment (such as storage system, PV generation and loads). Moreover,
several short-circuit test has been performed. Therefore, the protection plan has been studied and
tested:
 The short circuit power of the sources;
 The short circuit power flows in the lines, in different grid configurations;
During the test period, only the Concept Grid team is allowed on the platform and only they and
the manufacturer are allowed in the control room. x
Before the test starts some security points have to be treated:
 Most power sources are equipped with anti-islanding protections, which should be
deactivated or set in a way that they don’t prevent the islanding of the microgrid;
 The power sources and storage systems should not disconnect at an untimely moment when
they face voltage or frequency fluctuations (which can be important when the microgrid is
islanded); it is therefore important to define the acceptable voltage and frequency fluctuations
(see the § Normative references for validation criteria and performance indicators).
Equipment and System Validation
The proper functioning of the different equipment will be validated independently. This concerns
especially:
 For generators and storage systems that have different settings possible (Isochronous mode,
Droop mode, etc.), validation of the different modes and the transitions between them;
 For controllable equipment (loads, generators and storage systems), verification that the
communication system planned for the microgrid is able to control the equipment through the
telecommunication network;
Use Case 1: Set Points for Active and Reactive Power Flows at the Point of
Coupling When Connected to the Grid
When connected to the grid, the microgrid should behave as a controllable entity. Therefore, it
should be able to control the active and reactive power flows at its point of coupling with the
main grid, and stabilize them at a given set point (which can be given either by the main grid
operator or by internal optimization processes).
5-8
During these tests, the target is to measure different performance indicators:
 Success of failure of the request,
 Time response for each configuration,
 Priority management,
 Power flow deviation (PD),
 State of charge/ duration expectations.
Test Cases to Be Completed:
TC 1.1: Series of Set Points for the Coupling Point (constant load and PV generation)
This test case has the objective to evaluate the microgrid controller capability in terms of power
flow management at the point of coupling for different set points requests.
The load and the generation will be constant during the test period.
Different network configurations will be implemented in order to cover several situations as
follow:
 The system storage has the capability to compensate a consumption or generation power flow
at the point of coupling in order to fulfill the request.
 The system storage has not the capability to compensate a consumption or generation power
flow at the point of coupling in order to fulfill the request.
 The system storage has (or has not) the capability to compensate an unbalanced consumption
or generation power flow at the point of coupling in order to fulfill the request.
Three network configurations will be implemented as follows.
Case 1 * Case 2 * Case 3 *

Active and reactive power
P Q P Q P Q
in (kW or kVar)
Phase Three phases 1 2 3 1 2 3
Resistive Load 1 30 6 20 20 20
Stockage 50 -20
Stockage 4 4
PV SMA -12 -12 -4 -4 -4
PV Fronius -8 -8 -3 -3 -3
Amplifier 20
-15 20 10 8 6
(inductive)
House 1 3 3
House 2 3 3
House 3 3 3 3
Theoretical power flow at the
19 20 -40 20 20 13 13 10 8 6
PCC (by phase or total)
5-9
For each case, the following steps describe the scheduled islanding procedure:
1. At time t0 - 1min, the microgrid controller receives P = 0 kW and Q = 0 kVAr set points,
to start at t0 for a 30min duration.
2. At time t0 + 1min, the microgrid controller receives new set points, P = -35 kW and
Q = -20 kVAr (exporting to main grid), to start at t0 + 2min, for the same total duration.
3. At time t0 + 5min, the microgrid controller receives new set points, P = 0 kW and
Q = 0 kVAr, to start immediately for the same total duration.
4. At time t0 + 10min, the microgrid controller receives new set points, P = +35 kW and
Q = +20 kVAr (importing from the grid), to start immediately for the same total
duration.
5. At time t0 + 15min, end of the TC.
* Cases description
System Storage Case 1 Case 2 Case 3

P=0kW The excess Consumption on the microgrid is inferior to the
Q=0kVAr storage capacity
The excess Consumption on the The excess Consumption on The excess
P=-35kW
microgrid is superior to the the microgridis inferior to the consumption on
Q=20kVAr the microgrid is
Power Flow storage capacity storage capacity
inferior to the
Set point The excess Production on the The excess Consumption on
P=0kW storage capacity
microgrid is inferior to the the the microgrid is superior to and unbalanced
Q=0kVAr
storage capacity the storage capacity phase
P=+35kW Excess Production < Capacity Excess Production > capacity
Q=20kVAr SS SS
TC 1.2: Series of Set Points for the Coupling Point (Variable Load and PV
Generation)
flow management at the point of coupling for different set points requests.
The load and the generation will be variable during the test period. The target is to study the
behavior and the reaction of the microgrid controller with variations load and generation.
Three scenarios will be performed in order to cover several situations as follow:
 Case 1 : high level and variable load with constant level of PV generation,
 Case 2 : high level of variable PV generation and low constant consumption,
 Case 3: variable load and PV generation.
The load and source profile proposed for the tests are “real” consumptions from low voltage
feeders and real PV generation curves measured on the French distribution network.
5-10
Case 1: Variable Load
The network configuration for this case is as follows:
Case 1
Active power in (kW) P
Phase Three phases
Resistive Load 1 30
PV SMA -10
PV Fronius -5
Amplifier Refer to the load profile below
House 1 3
House 2 3
House 3 3
Load Profile:
The amplifier will simulate the following load profile.
5-11
Power Flow:
The theoretical power flow at the point of coupling with this network configuration is shown
below.
Test Description:
The microgrid controller receives P = 0 kW and Q = 0 kVAr set points, to start at t0 for a 10min
duration.
Case 2: Variable PV Generation (Profile n°1)
Case 2
Phase Three phases
Resistive Load 1 20
PV SMA Refer to the generation profile below
PV Fronius Refer to the generation profile below
Amplifier Refer to the generation profile below
House 1 3
House 2 3
House 3 3
5-12
PV Generation:
The PV generation curve will be injected on the network via the following sources:
 PV inverter SMA,
 PV inverter Fronius,
 Amplifier.
The amplifier will measure the injected current by the PV inverter in order to inject the same
generation profile with a power five times more important than the Fronius PV.
Power Flow:
The theoretical power flow at the point of coupling with this network configurations is shown
below.
5-13
Test Description:
duration.
Case 3: Variable Load and PV Generation (profile n°1)
Case 1
Phase Three phases
Resistive Load 1 10
PV SMA -6
PV Fronius -4
Amplifier Refer to the variation power below
House 1 3
House 2 3
House 3 3
Load and generation profile

The amplifier will simulate the following power variation (load and generation).
5-14
Power Flow:
below.
Test Description:
duration.
Case 4: Variable and Load PV Generation (profile n°2)
Case 1
Phase Three phases
Resistive Load 1 10
PV SMA -6
PV Fronius -4
Amplifier Refer to the variation power below
House 1 3
House 2 3
House 3 3
5-15
Load and Generation Profile:
The amplifier will simulate the following power variation (load and generation).
Power Flow:
below.
5-16
Test Description:
duration.
TC 1.3: Peak Shaving with the Start of a Critical Load
flow management at the point of coupling taking into account critical and no critical load.
The load and the generation will be constant during the test period.
The initial network configuration is as follows:
Case 1
Active and reactive power in (kW) P
Phase Three phases
Resistive Load 1
Customer 1 (critical) : 5kW
Customer 2 (non critical load) : 10kW 50
Customer 3 (non critical load) : 15kW
Customer 4 (non critical load) : 20kW
Resistive load 2 (critical load) 0
Stockage 50 20
Stockage 4 /
PV SMA (non critical) -12
PV Fronius (critical) -8
Amplifier /
House load 1 (phase 1) 3
Theoretical power flow at the PCC 59
For the network configuration shown above, the following steps describe the procedure:
1. At time t0, the microgrid controller receives a peak shaving request: the power flows
importations from the grid should not exceed P0 = +15 kW, to be maintained for the next
30 min. Every critical and controllable loads are on.
2. At time t0 + 5min, the “resistive load 2” is switched on as a 30 kW, considered as a
critical load. The size of this load should be sized so that, in order to maintain the peak
shaving, the microgrid controller has to switch off the controllable loads at some
moment.
3. Restart the test case with a set point at P0 = +5 kW.
5-17
Validation criteria and performance indicators
 Success / failure to fulfill the request (i.e. active and reactive power flows at the coupling
point stay in the acceptance range – to be defined accordingly with the microgrid controller
specifications – for the given duration).
 Response time to fulfill the request (i.e. active and reactive power flows at the coupling
point stay in the acceptance range – to be defined accordingly with the microgrid controller
specifications – for the given duration).
 Priority Management chosen to fulfill the request.
 KPI # 1 : Power flow deviation (PD)
- Impact of load forecasting errors (nRMSE Cons) on PD% and PDMax
- Impact of generation forecasting errors (nRMSE Prod) on PD% and PDMax
Use Case 2: Scheduled Islanding (disconnection)

A microgrid should be able to island, i.e. disconnect from the main grid, and work as an
autonomous grid. This first use case is the simplest one for the disconnection phase. If
maintenance work is planned on the main grid, or other activities that would make it out of
service for a time, the microgrid can anticipate this outage and disconnect from the grid before.
As it is scheduled, this operation should be transparent for the loads in the microgrid, and the
system has time to prepare for the islanding, by adjusting the storage state of charge or other
flexibilities.
TC 2.1: Normal Situation
The objective of this test case is to observe the microcontroller capabilities in terms of storage
Soc, power flow on the microgrid.
In this test case, the storage system can handle the islanding without any modifications (charging
or discharging the storage, shedding…).
The following steps describe the scheduled islanding procedure:
1. The initial network configuration is shown in the table below. Before the step 2, the state
of charge is approximately at 50%.
2. The microgrid controller receives a request for islanding, at least one hour ahead. The
request contains :
- the time t0 to begin the islanding,
- the duration of the islanding : d0=1h,
- the load forecast illustrated in the Figure below,
- the generation forecast illustrated in the Figures below.
3. The microgrid controller evaluates the possibility to realize the requested islanding,
taking into account the generation and load forecast.
4. The microgrid controller reports the possibility. If it is possible, an operator gives an
agreement to pursue.
5-18
5. The microgrid controller prepares the system (state of the battery charge, controllable
loads and generators) in order to make it ready for the islanding.
6. At t0 – x min (to be determined), the active and reactive power flows at the point of
coupling are set at 0 via the microgrid controller.
7. At t0, the microgrid controller gives an order to the storage system for starting the
scheduled islanding.
8. The microgrid controller reports the islanding start.
9. For 5 min, the islanding is maintained, by managing the generators, the storage systems
and the loads to keep the frequency and the voltage in a given range.
10. At t0 + 5 min, the islanding is stopped by powering off the microgrid.
Case 1
Active and reactive power in (kW) P Q
Resistive load 1 15
Stockage 50kW
-20
Soc 50%
Stockage (4kW)
PV SMA -12
PV Fronius -8
Amplifier 20
House load 1 3
House load 2 3
House load 3 3
Theoretical power flow at the PCC -16 20
5-19
5-20
TC 2.2: Microgrid in Overproduction
The objective of this test case is to observe the microcontroller capabilities during the
preparation period before the islanding.
In this test case, the storage system have to evaluate the load and generation forecast and prepare
the microgrid for the islanding (charging or discharging the storage, shedding…).
1. The initial network configuration is shown in the table below. Before the step 2, the
initial state of charge is approximately at 95%.
request contains :
- the duration d0=1h of the islanding
- the generation forecast illustrated in the figures below.
3. follow the test case “2.1” procedures.
5-21
Case 2
Active and reactive power in (kW or kVar) P Q
Phase Three phases
Resistive load 1 :
Customer 1 : 15
Customer 2 :
Stockage 50 20
Stockage 4
PV SMA -12
PV Fronius -8
Amplifier -40 20
House 1 3
House 2 3
House 3 3
Theoretical power flow at the PCC -16 20
5-22
TC 2.3: Microgrid in Overconsumption
The objective of this test case is to observe the microcontroller capabilities during the
preparation period before the islanding.
In this test case, th storage system do not have the capability to powered the microgrid due to the
overconsumption. The microgrid controller have to determine the possible solutions taking into
account the generation and load forecast and in order to respect the islanding duration.
1. The initial network configuration is shown in the table below. Before the step 2, the
initial state of charge is approximately at 20%.
request contains :
- the duration d0=1h of the islanding
- the load forecase illustrated in the Figure below,
- the generation forecast illustrated in the figures below.
5-23
Case 3
Active and reactive power in (kW or kVar) P Q
Phase Three phases
Resistive load 1 30
Stockage 50 -20
Stockage 4
PV SMA -12
PV Fronius -8
Amplifier 30 20
House 1 3
House 2 3
House 3 3
Theoretical power flow at the PCC 29 20
5-24
Validation criteria and performance indicators
 Success / failure to start and anticipate the scheduled islanding (the microcontroller have to
analyse the load and generation forecast, define the necessary Soc for the request in order to
modify the Soc of the storage system.
 KPI # 1 : Power flow deviation (PD) before islanding,
 State of charge: evaluate the evolution of the Soc during the time before the islanding.
5-25
Use Case 3: Maintain Islanding for a Given Duration
Whatever was the way the islanding started (scheduled, automatically or black start), the
microgrid should be able to maintain the islanding for as long as possible, ideally until the power
on the main grid is back to normal, so that it can reconnect.
Tests Description
This use case will be carry out at the end of the test case in chapter: “5.4 Use Case 2: Scheduled
islanding”.
The test case “TC 2.1: Normal situation” will be performed in two situations:
 Case 1: the scheduled islanding will be tested with accurate load and generation forecast.
 Case 2: the scheduled islanding will be tested with an error of the load and generation
forecast. The real generation curves are shown below. The amplifier will simulate the
following load profile in figure below.
The following steps describe the test procedure:
 The microgrid is islanded (Use Case 2: scheduled islanding).
 The microgrid controller receives a request for an islanding duration (Use Case 2: scheduled
islanding).
 The microgrid controller evaluates for how long it can maintain the islanding, based on
generation and load forecast. It reports the result (Use Case 2: scheduled islanding),
 The microgrid controller manages the loads, storage systems and generators in order to reach
the requested islanding duration.
 The management strategy of the loads, storage systems and generators is updates as often as
possible (depending on the microgrid controller specifications), based on real-time
monitoring and forecasts results.
 If at a given time, maintaining the islanding is not possible anymore, the microgrid is
powered off.
 If the requested islanding time is reached, the microgrid reconnects to the main grid (Use
Case 4).
5-26
5-27
Validation Criteria and Performance Indicators
 Success / failure to reach the requested islanding duration.
 KPI #2: Islanding duration
- Impact of load forecasting errors (nRMSE Cons)
- Impact of generation forecasting errors (nRMSE Prod)
The goal of this indicators is to evaluate the impact of a generation and load forecasting error on
the microgrid regulation strategy.
Use Case 4: Reconnection to the Main Grid

After islanding, when the power on the main grid is back to normal, the microgrid should
reconnect to it, without disturbances to its loads.
This use case will be carry out at the end of “use case 2” and “use case 3”.
Tests Description
The initial network configurations are the same as the use case 2 and 3.
The following steps describe the reconnection procedure:
 The main grid is islanded.
 The microgrid controller checks if the voltage and frequency on the main grid are stable.
 The microgrid controller reports the possibility to reconnect. If possible, an operator gives an
agreement to pursue.
5-28
 The microgrid controller gives an order to the storage in order to synchronize the voltage at
the point of coupling with the grid’s voltage.
 The microgrid physically reconnects, and the necessary transitions of generator modes are
made so that the main grid becomes the voltage source.
 The microgrid controller reports the success of reconnection.
 Success / failure of the microcontroller to command the storage system for the reconnection
to the main grid continued by reconnection confirmation.
Use Case 5: Black Start

If the main grid fails and the microgrid is not able to automatically start the islanding, the power
will be interrupted for the loads inside. If the microgrid is able to black start, i.e. power up its
loads using its generation and storage units, before the main grid is re-powered, it can decrease
significantly the outage time for the loads. To realize this black start, the microgrid controller
must have an auxiliary back-up power source, to keep it powered on during the outage.
Tests Description
The following steps describe the black start procedure for each test case.
1. The initial network configurations is shown in table below. The first test starts with the
“Case 1”. For all the test cases, the storage SoC has to be approximately at 50%.
2. The main grid is cut off, and the microgrid is powered off.
3. The microgrid controller evaluates the possibility to realize a black start, and the possible
duration of the islanding, taking into account the current system configuration.
4. The microgrid controller reports the possibility to black start.
5. The microgrid physically disconnects from the main grid.
6. The microgrid controller prepares the system (controllable switches and loads, generators
modes) in order to make it ready for the black start.
7. The black start begins by powering up the grid with the main generator.
8. The loads and the other generators are progressively repowered.
9. The microgrid controller reports the islanding start.
10. For 5 min, the islanding is maintained, by managing the generators, the storage systems
and the loads to keep the frequency and the voltage in a given range.
11. At t0 + 5 min, the islanding is stopped by powering off the microgrid.
12. Restart the test with each case.
5-29
Case 1 Case 2 Case 3 Case 4
Active and reactive power in (kW or kVar) P Q P Q P Q P Q
Resistive load 1 30 6 6 15
Stockage 50 -20 20 /
Stockage 4
PV SMA -12 -12 -12 -12
PV Fronius -8 -8 -8 -8
Amplifier 20 -15 20 -60 60
House 1 3 3 3 3
House 2 3 3 3 3
House 3 3 3 3 3
Theoretical power flow at the PCC 19 20 -40 20 -45 20 64
Comments Excess Excess Excess Excess
Consumption Production < Production > Consumption
< Capacity SS Capacity SS Capacity SS > Capacity SS

 Success / failure to evaluate the microgrid islanding capability and deliver a go/no-go to
launch the black start.
 The microcontroller should be able to estimate the islanding duration.
Measurements Needed
To measure the validation criteria and performance indicators, the system should be equipped
with the following monitoring units:
 At the point of coupling, measurement of voltage and current (3s values, complete wave form
during variations, bidirectional)
 At several points of the microgrid (connection points of loads, generators and storage
systems), measurement of voltage and frequency (3s values, complete wave form during
variations, spectral values for voltage).
 At each house of the microgrid, measurement of voltage and frequency (RMS values
recorded every 3 seconds, complete wave form during variations, spectral values for voltage)
5-30
Key Performance Indicators
This paragraph describes several Key Performance Indicators (KPI), which are used in the tests
presented in this document, but can also be used to evaluate the performance of any microgrid.
KPI #1: power flow deviation
 Error margin: size of the interval around the set points (P 0, Q0) in which the measured
power flows actually stay. Two indicators can be calculated :
- The power flow deviation PD (and QD) is calculated in % by :
 P  P 
2
t 0
PD%  t
 100%
P0
- The maximum power flow deviation PDMax (and QDMax) is calculated in % by:
 Pt  P0 
PD Max  max    100%

 P0 
t
KPI #2: Islanding duration

The goal of this KPI is to evaluate how long the system is able to run disconnected from the grid,
and thus assess the ability of the system to provide power in case of grid outage.
Calculation methodology
 The islanding duration is the difference between the effective islanding start time and the
effective islanding end time.
 The effective islanding start time is the first time when the microgrid is physically
disconnected from the main grid, and at least one load inside the microgrid is powered by at
least one energy source inside the microgrid.
 The effective islanding end time is the first time when the microgrid is physically
reconnected to the main grid, or all loads inside the microgrid are powered off.
Necessary data
 Position of the switch at the point of coupling and time measurements at movements of the
switch.
 Indicators of the power state of the loads.
Other indicators
This paragraph describes others Indicators, which are used in the tests presented in this
document, but can also be used to evaluate the performance of any microgrid on the field.
5-31
I #1: Accuracy of generation forecasting
The goal of this indicator is to evaluate the accuracy of the generation forecasting procedure, in
order to assess the capacity of the system to establish a good strategy for energy management.
The generation forecasting can be done on different time scales. Here, we consider the generic
case of a forecast made at a time tf of the consumption between t 1 and t2 (t1 > tf).
For the tests at Concept Grid, this indicator will be imposed, as it cannot be evaluated
impartially.
 Pforecast,t ,the total generation of all the generators (not including storage) inside the microgrid
at regular time steps t between t1 and t2 , is forecasted at t f.
 The real generation Pmeasured,t is measured at regular time steps t between t 1 and t2.
 The normalized root-mean-square error of the forecast is calculated as:
 P  Pmeasured,t 
2
nRMSE Pr od  100
t forecast,t
P t
2
measured,t
 nRMSEProd is calculated for each generation forecast realized by the system.

Necessary data
 Measurements of the total production of all the generators inside the microgrid at regular
time steps t.
 Forecasted production powers.
I #2: Accuracy of load forecasting
The goal of this KPI is to evaluate the accuracy of the load forecasting procedure, in order to
assess the capacity of the system to establish a good strategy for energy management. The load
forecasting can be done on different time scales. Here, we consider the generic case of a forecast
made at a time t f of the consumption between t 1 and t2 (t1 > tf).
One should note that this KPI cannot be evaluated impartially in a test procedure where the loads
are operated using a predefined demand profile.
5-32
 Pforecast,t ,the total consumption of all the loads (not including storage) inside the microgrid at
regular time steps t between t 1 and t2, is forecasted at t f.
 The real consumption Pmeasured,t is measured at regular time steps t between t 1 and t2.
 The normalized root-mean-square error of the forecast is calculated as:
 P  Pmeasured,t 
2
nRMSECons  100
t forecast,t
P t
2
measured,t
 nRMSECons is calculated for each load forecast realized by the system.

Necessary data
 Measurements of the total consumption of all the loads inside the microgrid at regular time
steps t.
 Forecasted consumptions.
5-33
6
CONCLUSION
A detailed test plan is outlined in this report. A three tiered microgrid testing and evaluation
process has been proposed. Laboratory testing will be coordinated between the Energy Systems
Integration Facility (ESIF) at NREL and the InteGrid Test and Development Lab at Spirae.
Testing between the two labs will be coordinated with the ESIF testing conducted with a site
model configured with the specific site assets using a controller hardware-in-the-loop (CHIL)
platform while the InteGrid Lab testing will use the physical assets of the lab operated as a
remote hosted solution. An initial plan for the on-site field testing has been provided to verify the
microgrid performance as expected in community’s application. Additional refinements will be
made as we learn more specific information.
6-1
Export Control Restrictions The Electric Power Research Institute, Inc.
Access to and use of EPRI Intellectual Property is granted (EPRI, www.epri.com) conducts research and
with the specific understanding and requirement that development relating to the generation, delivery
responsibility for ensuring full compliance with all applicable and use of electricity for the benefit of the public.
U.S. and foreign export laws and regulations is being
An independent, nonprofit organization, EPRI
undertaken by you and your company. This includes an
brings together its scientists and engineers as well
obligation to ensure that any individual receiving access
hereunder who is not a U.S. citizen or permanent U.S. as experts from academia and industry to help
resident is permitted access under applicable U.S. and address challenges in electricity, including
foreign export laws and regulations. In the event you are reliability, efficiency, affordability, health, safety and
uncertain whether you or your company may lawfully obtain the environment. EPRI members represent 90% of
access to this EPRI Intellectual Property, you acknowledge
the electric utility revenue in the United States with
that it is your obligation to consult with your company’s legal
international participation in 35 countries. EPRI’s
counsel to determine whether this access is lawful. Although
EPRI may make available on a case-by-case basis an principal offices and laboratories are located in
informal assessment of the applicable U.S. export Palo Alto, Calif.; Charlotte, N.C.; Knoxville, Tenn.;
classification for specific EPRI Intellectual Property, you and and Lenox, Mass.
your company acknowledge that this assessment is solely
for informational purposes and not for reliance purposes. Together…Shaping the Future of Electricity
You and your company acknowledge that it is still the
obligation of you and your company to make your own
assessment of the applicable U.S. export classification and
ensure compliance accordingly. You and your company
understand and acknowledge your obligations to make a
prompt report to EPRI and the appropriate authorities
regarding any access to or use of EPRI Intellectual Property
hereunder that may be in violation of applicable U.S. or
foreign export laws or regulations.
© 2016 Electric Power Research Institute (EPRI), Inc. All rights reserved.
Electric Power Research Institute, EPRI, and TOGETHERSHAPING THE
FUTURE OF ELECTRICITY are registered service marks of the Electric
Power Research Institute, Inc.
3002008885
Electric Power Research Institute

3420 Hillview Avenue, Palo Alto, California 94304-1338 • PO Box 10412, Palo Alto, California 94303-0813 • USA
800.313.3774 • 650.855.2121 • askepri@epri.com • www.epri.com

Microgrid Controller Test Plan

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microgrid Controller Test Plan

Uploaded by

Copyright:

Available Formats

Microgrid Controller Test Plan

Grid Interactive Microgrid Controller for Resilient Communities

EPRI Project Manager

ELECTRIC POWER RESEARCH INSTITUTE

 Laboratory Testing (Step 1) Microgrid control functionality verification and standard

Testing Stage Location Rationale

Target Community Characterization, Status, and Selection

DOE Performance Targets and Objectives

DOE Functionality Requirements

Requirement C2: Resynchronization and Reconnection

Requirement C4: Protection

Requirement C5: Dispatch

Requirement C6: Enhanced Resiliency

Layer 1: Device level controls

Layer 2: Network/Group/Building level controls

Layer 3: Supervisory/Management Level Controls

Layer 4: Analytics/DMS Interface/Grid Interaction

Standard Microgrid Functions for Integration

Grid-Tied Functions Islanded Functions

Spirae Wave Architecture

Test Methods, Scenarios, and Laboratory Capabilities

Measured Sampling Functional Purpose / Metrics

Integrid Asset Capacity

Use Case A: Operating the Microgrid While Connected to the Utility

Use Case D: Connecting the Microgrid to the Utility

Use Case E: Reduction in Outage Time

𝐶 = ∑ Pgrid,n ∙ τ ∙ 𝑐𝑔𝑟𝑖𝑑,𝑛 + ∑ {∑ PDER,k,n ∙ τ ∙ 𝑐DER,k,n } + 𝑐𝐷 ∙ max(Pgrid,n )

Separating the Microgrid from the Utility

Operating the Microgrid while Separated from the Utility

Connecting the Microgrid to the Utility

Nominal Power Connection Connected

STP 15000TL-10 15 3 phases 2110445311 house 2 Modbus TCP IP

Heat Pump Mitsubishi SRK25ZJ-S SRC25ZJ-S 0,8 1 phase 145409534RE house 2

Case 1 * Case 2 * Case 3 *

System Storage Case 1 Case 2 Case 3

Load and generation profile

Use Case 2: Scheduled Islanding (disconnection)

Use Case 4: Reconnection to the Main Grid

Use Case 5: Black Start

Validation Criteria and Performance Indicators

KPI #2: Islanding duration

 nRMSEProd is calculated for each generation forecast realized by the system.

 nRMSECons is calculated for each load forecast realized by the system.

Electric Power Research Institute

You might also like