RFI-02 - SPEC 26 37 13.pdf
PDF 346 KB Posted
- Solicitation number
- W912DS26BA032
About this file
This is a technical specification for a Microgrid Control System (MCS) to be installed at Joint Base McGuire-Dix-Lakehurst (JBMDL) in New Jersey as part of a power generation microgrid construction project. The MCS must monitor and control a bounded electrical system with multiple distributed energy resources (DERs) including two 500kW natural gas generators, a 400kWac solar photovoltaic array, and three 500kW/500kWh battery energy storage systems. The system is required to integrate with JBMDL's existing Niagara JACE-based SCADA system while maintaining independent operational capability in the event of communication loss.
The specification requires the contractor to deliver a comprehensive control architecture with primary, secondary, and tertiary control levels managing real-time power flow, fault detection, load shedding, and system optimization. Critical operational capabilities include black start functionality to restore power to 2.5MW critical loads within 60 seconds following outages, seamless transitions between grid-connected and island modes without closed transitions, anti-islanding protection with 10-millisecond disconnect capability, and automated load-shedding algorithms prioritizing mission-critical systems. The MCS must support multiple operational states including normal grid-tie mode, islanding, black start microgrid formation, optimized islanded operation, and reconnection sequences. Deliverables include detailed design specifications, factory and site acceptance testing procedures, performance verification testing in three phases, comprehensive operator training, operations and maintenance documentation, and as-built drawings. All hardware components must be commercial, warrantied products from single manufacturers with ISO 9001 compliance certification, and all software must be licensed to the Government in perpetuity without periodic renewal fees. The project sequencing specifies detailed submittal deadlines with Government approval required for design specifications, test procedures, HMI mockups, and all regulatory compliance documentation.
View the file
Other files
Show all 26
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Power Generation with Microgrid 164947 Joint Base McGuire-Dix-Lakehurst, New Jersey
SECTION 26 37 13
MICROGRID CONTROL SYSTEM
02/24
PART 1 GENERAL
1.1 SUMMARY
The Microgrid Control System (MCS) defined herein monitors and controls the operation of the microgrid equipment. This specification refers only to that control system and does not include specification of the connected equipment which comprises the microgrid such as Distributed Energy Resources (DERs), controlled loads, distribution or utilization circuits, low, medium, or high-voltage protective devices, or other similar components specified elsewhere. However, these other components must be provided with any necessary interface equipment to be controlled by the MCS as described in these documents. There are also existing pieces of equipment which must be modified by the Contractor to be integrated into the MCS.
JB MDL - Lakehurst has an existing SCADA system based on Niagara JACE power management and control system. The Contractor must integrate the new MCS functions (described herein) into this existing system so that the new microgrid, and all of its components, are seamless entities within the overall SCADA system. Although the new MCS is fully integrated into the existing SCADA system, it must be designed and built so that the microgrid can be fully functional with complete loss of communication between JB MDL's overall SCADA system and the equipment within the functional boundaries of the microgrid. The Contractor must pay attention to potential interface points between these systems to ensure that failure of the SCADA to communicate to the MCS does not adversely affect the safe operation of the microgrid.
1.1.1 System Requirements
Provide an electrical Microgrid Control System (MCS) as specified and indicated, and in accordance with the following characteristics:
1.1.1.1 General MCS Requirements
a. Scope of Control: The MCS controls the microgrid system. The microgrid is defined as a bounded electrical system with multiple points of interconnection with an external grid. The system includes DERs, distribution devices, dispatchable and non-dispatchable loads, controls, and communication systems.
b. Fault Management: MCS supervisory monitoring and control functions include but are not limited to automated fault detection, microgrid isolation from the external electrical grid, and internal system reconfiguration capabilities to maintain critical load supply.
c. Component Standards: Provide components and technology which are commercial, warrantied, and intended for permanent installation.
Materials and equipment must be standard unmodified products of a manufacturer regularly engaged in the manufacturing of such products.
Units of the same type of equipment must be products of a single
SECTION 26 37 13 Page 1 manufacturer. Items of the same type and purpose must be identical and supplied by the same manufacturer, unless replaced by a new version approved by the Government.
d. Island Mode Operation: Ensure the Microgrid Control system operates the microgrid in island mode, paralleling either one or more than one disparate source of generation, with at least one grid-forming DER.
e. Black Start Capability: Equip the MCS to manage the microgrid black start procedure. Initiate the startup of more than one firm-generation grid-forming DER asset(s) after an unplanned external grid outage.
f. Load Management: Incorporate functionality within the MCS to dispatch DER and direct load shedding, ensuring the islanded system generation meets the critical load within the system boundary.
g. Operational Modes: Equip the MCS with functionality to direct transitions between operational modes, including but not limited to black start in island mode, automatic transition from grid-connected to islanded mode, resynchronization and reconnection to grid-connected mode from islanded mode, and system balancing. Manage energy to optimize both real and reactive power generation and consumption for microgrid-connected load resilience,economic benefits, and utility system demand response through DER and load dispatch.
h. System Interface: The MCS must be fully integrated into JB MDL's existing utility SCADA system. The Contractor must coordinate all changes and testing of the MCS with JB MDL in order to minimize outages to the SCADA system.
i. Monitoring and Control: Equip the MCS with supervisory monitoring and control functions, including but not limited to: Point of Common Coupling (PCC) monitoring and control, frequency control, load shedding, anti-islanding, low- or high- voltage or frequency ride-through, remote breaker control and monitoring in accordance with facility SOP, synchronization, and power quality monitoring.
j. Grid Interface: Coordinate the microgrid and microgrid system controller to present to the larger grid as a single entity with multiple points of electrical interconnection and a single control and communication interface between the microgrid and external grid.
Ensure all MCS control and reporting functions appear as a single entity to all external devices. Execute functions defined herein from that single point of interconnection.
k. Human Machine Interface: System includes human-machine interface with graphical interface into the MCS. The HMI must allow for graphical navigation between systems, graphical representations of systems and interconnection, access to real-time data for systems, ability to override points in a system, and access to all supervisory monitoring and control functions.
l. Control Workstation: Provide a standard desktop computer or a laptop meeting the following minimum requirements for the Computer Workstation Hardware (workstation) in accordance with this specification.
m. Government's Existing Software Licenses: The Contractor must provide
SECTION 26 37 13 Page 2 any additional licensing requirements (e.g., additional seat or control points) as necessary for the new MCS to be added to the Government's existing SCADA software license, but the Contractor is not responsible for any renewal fees of the Government's existing software licenses. Contractor must procure any development tools or licenses in order to create and/or test the new MCS prior to deployment on the Government's system. The Government licenses must not be used by the Contractor for these functions.
n. Additional Software Licenses: For any software beyond the Government's SCADA system, provide all necessary software documentation, configuration information, configuration tools, programs, drivers, and other software. Ensure they are licensed to and remain with the Government so that the Government or their agents can repair, replace, upgrade, and expand the system without subsequent or future dependence on the Contractor. Software licenses must not require periodic fees and be valid in perpetuity.
o. Documentation: Supply sufficient documentation and data, including rights to documentation and data, enabling the Government or their agents to execute work to repair, replace, upgrade, expand, and cyber-secure the system without subsequent or future dependence on the Contractor.
1.1.1.2 Symbols, Definitions, and Abbreviations
Use symbols, definitions, and engineering unit abbreviations indicated in the contract drawings for displays, submittals and reports. For symbols, definitions and abbreviations not in the contract drawings use terms conforming at a minimum to IEEE Standards Dictionary as applicable.
1.1.1.3 System Units and Accuracy
Use metric (SI) units for displays, print-outs and calculations. Ensure calculations have an accuracy of at least three significant figures and present values on displays and printouts to at least three significant figures.
1.2 RELATED SECTIONS
a. Section 25 05 11.06 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS
ELECTRICAL SCADA - LOW IMPACT.
b. Section 26 31 00 FACILITY-SCALE SOLAR PHOTOVOLTAIC (PV) SYSTEMS.
c. Section 26 32 15 ENGINE-GENERATOR SET STATIONARY 15-2500 KW, WITH
AUXILIARIES.
d. Section 48 18 00 BATTERY ENERGY STORAGE SYSTEMS.
1.2.1 Cybersecurity Requirements
Cybersecurity requirements related to this Section are specified in Sections 25 05 11.06 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS ELECTRICAL SCADA - LOW IMPACT and 25 05 11.01 CYBERSECURITY FOR
FACILITY-RELATED CONTROL SYSTEMS EMCS DDC - LOW IMPACT.
SECTION 26 37 13 Page 3
1.2.2 Distributed Energy Resources
a. Integrate the two natural gas fueled generators provided as part of this Project into the microgrid. The generators shall be capable of operating as either the grid forming resource during black start and islanded operation or a base loaded resource in parallel to the energy storage system or the utility grid. When dispatched in parallel to the grid or energy storage system, the MCS must be able to dispatch both real and reactive power within the limits of the connected generator(s). Refer to Section 26 32 15 ENGINE-GENERATOR SET
STATIONARY 15-2500KW, WITH AUXILIARIES.
b. Ensure the microgrid control system interfaces with, providing control and communication as outlined throughout this specification for solar photovoltaic arrays provided under this contract using compatible inverter technology. Ensure inverters can control real and reactive power and comply with grid interconnection standards, including IEEE 1547 and UL 1741 . Refer to Section 26 31 00 FACILITY-SCALE SOLAR
PHOTOVOLTAIC (PV) SYSTEMS.
c. Integrate the Battery Energy Storage Systems (BESS) into the microgrid control system for purposes such as load leveling, peak shaving, and backup power. Ensure the BESS can control both charge and discharge, with real and reactive power capabilities. Refer to Section 48 18 00
BATTERY ENERGY STORAGE SYSTEMS.
1.3 REFERENCES
INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)
IEEE 1547 (2018) Interconnection and Interoperability of Distributed Energy Resources with Associated Electric Power Systems Interfaces
IEEE 1613 (2023) Environmental and Testing Requirements for Devices with Communications Functions used with Electric Power Apparatus
IEEE 2030.7 (2017) The Specification of Microgrid Controllers
IEEE 2030.8 (2008) The Testing of Microgrid Controllers
IEEE C37.90.1 (2023; ERTA) Standard for Surge Withstand Capability (SWC) Tests for Relays and Relay Systems Associated with Electric Power Apparatus
IEEE C37.90.2 (2004; R 2010) Withstand Capability of Relay Systems to Radiated Electromagnetic Interference from Transceivers
IEEE C62.41.1 (2002; R 2008) Guide on the Surges Environment in Low-Voltage (1000 V and Less) AC Power Circuits
IEEE C62.41.2 (2002) Recommended Practice on
SECTION 26 37 13 Page 4
Characterization of Surges in Low-Voltage (1000 V and Less) AC Power Circuits
IEEE Stds Dictionary (2009) IEEE Standards Dictionary: Glossary of Terms & Definitions
INTERNATIONAL ELECTROTECHNICAL COMMISSION (IEC)
IEC 60068-2-1 (2007) Environmental testing - Part 2-1:
Tests - Test A: Cold
IEC 60068-2-2 (2007) Environmental testing - Part 2-2:
Tests - Test B: Dry heat
IEC 60068-2-30 (2005; ED 3.0) Environmental Testing - Part 2-30: Tests - Test Db: Damp Heat, Cyclic (12 H + 12 H Cycle)
IEC 60068-2-78 (2012) Environmental testing - Part 2-78:
Tests - Test Cab: Damp heat, steady state
IEC 60255-1 (2022) Measuring relays and protection equipment - Part 1: Common Requirements
IEC 60255-21-1 (1988) Electrical relays - Part 21:
Vibration, shock, bump and seismic tests on measuring relays and protection equipment - Section One: Vibration tests
IEC 60255-21-2 (1988) Electrical relays - Part 21:
Vibration, shock, bump and seismic tests on measuring relays and protection equipment - Section Two: Shock and bump tests
IEC 60255-21-3 (1993; ED 1.0) Electrical Relays - Part 21: Vibration, Shock, Bump And Seismic Tests On Measuring Relays And Protection Equipment - Section 3: Seismic Tests
IEC 60255-26 (2023) Measuring relays and protection equipment - Part 26: Electromagnetic compatibility requirements
IEC 61000-4-4 (2012) Electromagnetic compatibility (EMC)
- Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test
IEC 61000-4-8 (2009) Electromagnetic compatibility (EMC)
- Part 4-8: Testing and measurement techniques - Power frequency magnetic field immunity test
IEC 61131-3 (2013) Programmable Controllers - Part 3:
Programming Languages
IEC 61850 (2021) Communication networks and systems for power utility automation
SECTION 26 37 13 Page 5
INTERNATIONAL SOCIETY OF AUTOMATION (ISA)
ISA 5.2 (1976; R1992) Binary Logic Diagrams for Process Operations
ISA 18.2 (2016) Management of Alarm Systems for the Process Industries
ISA 101.01 (2015) Human Machine Interfaces for Process Automation Systems
NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)
NEMA 250 (2020) Enclosures for Electrical Equipment (1000 Volts Maximum)
NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)
NFPA 70 (2026) National Electrical Code
NFPA 262 (2023) Standard Method of Test for Flame Travel and Smoke of Wires and Cables for Use in Air-Handling Spaces
U.S. DEPARTMENT OF DEFENSE (DOD)
MIL-STD-3071 (2023) Tactical Microgrid Communications and Control
U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)
FCC EMC (2002) FCC Electromagnetic Compliance Requirements
FCC Part 15 Radio Frequency Devices (47 CFR 15)
TELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)
ANSI/TIA-606 (2021d) Administration Standard for Telecommunications Infrastructure
TIA/EIA-568.1-D (2015) Commercial Building Telecommunications Infrastructure Standard
UNDERWRITERS LABORATORIES (UL)
UL 1741 (2021, Edition 3) UL Standard for Inverters, Converters, Controllers and Interconnection System Equipment for Use With Distributed Energy Resources
UL 60950 (2000; Reprint Oct 2007) Safety of Information Technology Equipment
SECTION 26 37 13 Page 6
1.4 ACRONYMS
Acronym Term
ARC Communication Architecture
ATS Automatic Transfer Switch
BESS Battery Energy Storage System
DER Distributed Energy Resource
DERMS DER Management System
DFD Data Flow Diagram
DMS Distribution Management System
FAT Factory Acceptance Test
HIL Hardware in the Loop
HMI Human Machine Interface
IBR Inverter-Based Resource
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
ISE Interconnection System Equipment
IT Information Technology
LAN Local Area Network
MCS Microgrid Control System
MEMS Micro-Electro-Mechanical Systems
NEC National Electric Code (NFPA 70)
NEMA National Electric Manufacturers Association
NFPA National Fire Protection Association
OT Operational Technology
PCC Point of Common Coupling
POI Point of Interface
PV Photovoltaic
RPM Revolutions Per Minute
ROI Return on Investment
SAT Site Acceptance Test
SECTION 26 37 13 Page 7
Acronym Term
SCADA Supervisory Control and Data Acquisition
SER Sequential Events Recorder
SOE Sequence of Events
SOO Sequence of Operation
SOP Standard Operating Procedure
UL Underwriters Laboratory
UPS Uninterruptible Power Supply
1.5 DEFINITIONS
1.5.1 IEEE Stds Dictionary
For terms not explicitly defined in this section, refer to the IEEE Stds Dictionary .
1.5.2 ASTM E772
For terms related to solar energy, refer to ASTM E772 for definitions and standard terminology.
1.5.3 Anti-Islanding
A safety mechanism that detects when a microgrid has been separated from the main grid and ensures that the microgrid does not continue to feed power back into the disconnected grid.
1.5.4 Automatic Transfer Switch (ATS)
A switch that automatically transfers a power supply from its primary source to a backup source when it senses a failure or outage in the primary source.
1.5.5 Base Load Power DER
A DER that provides a constant output as commanded by the MCS.
1.5.6 Black Start
The process of restoring a disabled or shut down microgrid to operation without relying on the external electric power transmission network.
SECTION 26 37 13 Page 8
1.5.7 Distributed Energy Resource Management System (DERMS)
A control system that allows for the centralized control of DERs within the microgrid, often integrated into the microgrid control system.
1.5.8 Firm Electrical Output DER
A DER capable of providing a guaranteed level of output under specified conditions.
1.5.9 Grid Following
A mode of operation where the DER adjusts its output based on grid conditions but cannot independently maintain grid voltage and frequency.
1.5.10 Grid Forming
A mode of operation where the DER can independently control voltage and frequency within a microgrid, effectively forming a grid.
1.5.11 Grid Forming DER
A DER capable of operating in a grid-forming mode, independently controlling voltage and frequency within a microgrid.
1.5.12 Human-Machine Interface (HMI)
The user interface that connects an operator to the controller in an industrial system, often a part of the microgrid control system.
1.5.13 Inverter-Based DER
A DER that uses an inverter to convert its output to alternating current (AC) for grid interconnection.
1.5.14 Islanding
Condition in which a microgrid operates independently and electrically isolated from the external grid.
1.5.15 Load Following DER
A DER that adjusts its output in real-time to match fluctuations in load demand.
1.5.16 Microgrid
A localized energy system consisting of DERs and loads capable of operating in parallel with, or independently from, the main power grid.
1.5.17 Point of Common Coupling (PCC)
The demarcation point between the owned electrical system of the microgrid and the utility distribution system.
1.5.18 Power Quality Correcting DER
A DER that provides ancillary services to improve power quality, such as voltage and frequency regulation.
SECTION 26 37 13 Page 9
1.6 ADMINISTRATIVE REQUIREMENTS
The contractor is responsible for the complete installation, testing, and commissioning of the Microgrid Control System (MCS) in accordance with the project's Division 01 Specification. The contractor must also coordinate with other trades and disciplines to ensure seamless integration of the MCS with other systems, including but not limited to DERs, UMCS, and existing utility infrastructure.
1.6.1 Pre-Installation Meeting
In accordance with UFC 1-300-02, a pre-installation meeting is required be held to discuss plans, procedures, responsibilities, and the impact on existing facilities. The meeting must include, but is not limited to, the following:
1.6.1.1 Coordination with Other Trades
Discussion of coordination requirements with other trades to ensure seamless integration of the MCS into the larger project infrastructure.
1.6.1.2 Phasing Plan
Prepare and submit a Phasing Plan that includes listing for duration and estimated start date for any and all outages of existing assets impacted by the installation of the MCS. Include outages or simulated outages related to testing as specified in Part 3.
Include in the submitted equipment phasing plan an Integration Plan for MCS with existing or planned assets, a detailed Phasing Plan outlining outages and coordination, and Risk Mitigation Strategies.
1.6.1.3 Related Project Coordination
Discussion of interface with concurrent, prior, or subsequent projects which may interface with the microgrid or microgrid control system.
1.7 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section
01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
Phasing Plan ; G, RO
SD-02 Shop Drawings
Contractor Design Drawings ; G, RO
Draft As-Built Drawings ; G, RO
Microgrid Control System HMI Graphical Mockup ; G, RO
SECTION 26 37 13 Page 10
SD-03 Product Data
Product Data Sheets ; G, RO
Computer Software Specifications ; G, RO
SD-05 Design Data
Microgrid System Architecture Diagram; G, RO
SD-06 Test Reports
Comprehensive Execution Plan ; G, RO
Site Assessment Survey ; G, RO
Factory Test Procedures ; G, RO
Factory Test Report ; G, RO
PVT Testing Procedures ; G, RO
PVT Phase I Testing Report ; G, RO
PVT Phase II Testing Report ; G, RO
PVT Phase III Testing Report ; G, RO
Startup Testing Plan ; G, RO
Startup Testing Report ; G, RO
Pre-construction QC checklist ; G, RO
Post-construction QC checklist ; G, RO
SD-07 Certificates
Regulatory Compliance Documentation ; G, RO
ISO 9001 Compliance Certificate ; G, RO
Installer Qualifications ; G, RO
SD-10 Operation and Maintenance Data
Emergency Response Plan ; G, RO
Training Documentation ; G, RO
Operation And Maintenance Instructions; G, RO
SD-11 Closeout Submittals
As-Built Documents ; G, RO
Enclosure Keys ; G, RO
SECTION 26 37 13 Page 11
Closeout QC Checklist ; G, RO
Backup Copies of All Settings Files ; G, RO
Instructions for Restoring Settings ; G, RO
1.8 DATA PACKAGE AND SUBMITTALS REQUIREMENTS
Technical data packages consisting of computer software and technical data (meaning technical data which relates to computer software) which are specifically identified in this project and which may be defined/required in other specifications must be delivered strictly in accordance with the CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered must be identified by reference to the particular specification paragraph against which it is furnished. All submittals not specified as technical data packages are considered shop drawings under the Federal Acquisition Regulation Supplement (FARS) and must contain no proprietary information and must be delivered with unrestricted rights.
1.9 PROJECT SEQUENCING
Table I outlines the sequencing of submittals as detailed in the SUBMITTALS paragraph (indicated by an 'S' in the 'TYPE' column) and activities as described in PART 3 EXECUTION (marked by an 'E' in the 'TYPE' column).
1.9.1 Sequencing for Submittals
The sequencing for submittals indicates the final date by which the submittal must be provided. After submission, the Government will review as outlined in 01 33 00 SUBMITTAL PROCEDURES. If the Government does not accept the submittal, revise the submittal and resubmit within 14 days of receiving the rejection notification. Each re-submission will undergo an additional Government review, and this process will continue until the Government accepts the submittal.
1.9.2 Sequencing for Activities
The sequencing specified for activities indicates the earliest activity may begin.
TABLE I - PROJECT SEQUENCING
ITEM TYPE DESCRIPTION SEQUENCING (START OF ACTIVITY
or DEADLINE FOR SUBMITTAL)
Commercial contracts and Pos in place
Resource plan
S Project schedule
S Monthly progress reports
Kick-off meetings
SECTION 26 37 13 Page 12
ITEM TYPE DESCRIPTION SEQUENCING (START OF ACTIVITY
or DEADLINE FOR SUBMITTAL)
Internal/External audit review meetings
1 S Detailed functional design specification
2 S Microgrid System Architecture Diagram
S Equipment layout drawings
3 S HMI Graphical Mockup
S Factory Acceptance Plan
4 S Acceptance of Factory Test Report
S Existing Conditions Report (site assessment survey)
14 days after #1
S Product Data Sheets and Certificate of Networthiness Documentation
14 days after #1
S MCS IP Network Bandwidth Usage Estimate 14 days after #1
S Pre-construction QC Checklist 30 days after #1
S Isolation, commissioning, testing, and restoration plans for system
30 days after #1
S Site readiness checklist 30 days after #1
5 Review Safety Requirements and Procedures with DPW
15 days before modifications made to SCADA
6 E Install MCS AAO #1 thru #4, ACO #5
7 E Start-Up Procedures and Start-Up Testing ICW #6 as per commissioning plan
Post-Construction QC Checklist as each phase is completed
Start-Up and Start-Up Testing Report as each phase is completed
Draft As-Built Drawings as each phase is completed
S PVT Phase I Procedures 15 days before scheduled start of PVT
8 S Preventive Maintenance Work Plan
9 S O&M Instructions
10 S Basic Training Documentation 30 days before scheduled start of training
11 E Basic Training (PVT Phase II) AAO #8, #9, and #10
S PVT Phase II Report ### days ACO #11
SECTION 26 37 13 Page 13
ITEM TYPE DESCRIPTION SEQUENCING (START OF ACTIVITY
or DEADLINE FOR SUBMITTAL)
S Final As-Built Drawings
S Advanced Training Documentation
12 E Advanced Training ACO #11
S Refresher Training Documentation 30 days before #13
13 E Refresher Training between 90 days ACO #11
S Closeout QC Checklist ACO #12
E Contract closure meeting
In TABLE I the abbreviation AAO is used for 'after approval of' and 'ACO' is used for 'after completion of', and ICW is used for 'in conjunction with'.
1.10 STANDARD MATERIALS AND PRODUCTS
Provide certification that control systems are designed and tested in accordance with DoD Instruction 8500.01, DoD Instruction 8510.01, and as required by individual Service Implementation Policy.
1.11 QUALITY ASSURANCE AND QUALITY CONTROL
Every manufacturer of the microgrid control system and its components must implement a documented quality assurance program (QAS), which includes an inspection test plan (ITP). All suppliers, including sub-suppliers, must provide QAS and ITP documentation for all deliverables. The QAS must encompass established process control documents, either as formal procedures or work instructions. Suppliers must ensure the availability of all relevant procedures and work instructions at every work location.
Supplier's adherence to their QMS and its effectiveness will be evaluated by:
a. Ongoing output quality verifications.
b. Internal and External "Hold", "Witness" "Observation" and "Review" points.
c. Inspection reports of incoming parts, modular assemblies and final product.
SECTION 26 37 13 Page 14
d. Company involvement in the 'non-conformance' process.
e. Periodic independent quality audits.
f. Performing quality inspections and tests by third parties.
1.11.1 Inspection Reports
Submit inspection reports created following the ITP procedures. Provide ITP documentation to the designated authority before site delivery.
1.11.2 Traceability and Markings
Within the Product Data Sheets submittals, report the country of origin for all materials and equipment in the submitted traceability documentation. All test reports and certificates must clearly indicate the origin of all software and the manufacturing location of relevant goods or materials. Ensure every item, component, software, and sub-component is traceable to its origin for both software development and manufacturing.
Submit this traceability documentation within the applicable Product Data Sheets submittals. Mark all goods and materials and trace their associated certifications throughout all processes, from engineering to construction. Ensure traceability of all sub-components through their markings to their origin and document this traceability.
1.11.3 Proof of Performance
Provide evidence of adherence to customer expectations, performance specifications, QAS requirements, IEEE 2030.8 standards, and other testing prerequisites within ITP, inclusive of both FAT and SAT.
1.11.4 Documented ISO 9001 Compliance
Submit documentation verifying ISO 9001 Compliance Certificate for all entities in the supply chain, including engineering design firms, commissioning teams, and manufacturing teams.
1.11.5 Qualifications
Engineering and manufacturing companies participating in this microgrid must submit Installer Qualifications including evidence of having previously completed five projects of similar size and complexity of microgrid projects.
1.11.6 Documentation
Maintain and make accessible for review by the designated authority all QAS and ITP documentation, including changes and revisions. Including but not limited to, design documents, test reports, and quality records.
1.12 REGULATORY REQUIREMENTS
Comply with all utility, local, state, and federal regulatory requirements related to this microgrid. Submit Regulatory Compliance Documentation demonstrating compliance with all utility interconnect contract stipulations. Ensure that no installation or testing done before the final SAT invalidates any warranties. Submit a table listing all regulatory
SECTION 26 37 13 Page 15 requirements and confirmations of compliance. Update this list as required and make it available for review when asked.
Equip the microgrid control system with functionality required to meet the control and communication requirements of the external grid. Secure certification from the connected external grid provider or operator during the interconnect application process.
1.13 DELIVERY, STORAGE, AND HANDLING
1.13.1 General Requirements
Deliver all equipment and materials in the manufacturer's original, unopened, undamaged containers with identification labels intact. Store all materials in a secure, clean, dry space in accordance with the manufacturer's instructions.
1.13.2 Handling
Handle all materials and equipment in a manner to prevent damage, adulteration, and soiling, and in accordance with the manufacturer's recommendations.
1.13.3 Storage
Store all materials and equipment off the ground and covered to protect them from weather, humidity, and temperature extremes.
1.14 SAFETY REQUIREMENTS
1.14.1 Grounding and Bonding
The microgrid includes variable grounding system topology to accommodate various operational states. It is designed to include multiple points of system bonding within the microgrid boundary. Within this boundary, the grounded conductors (neutrals) are unswitched.
1.14.2 Anti-Islanding Protection
Incorporate anti-islanding protection mechanisms in the microgrid control system (MCS) to safeguard both microgrid components and personnel. Ensure the MCS detects and disconnects the microgrid from the main grid during a grid outage, preventing unintentional islanding.
Equip the MCS with multiple methods to detect islanding conditions. These methods include, but are not limited to: Active Frequency Drift: Monitor the system frequency and comparing it against predefined thresholds.
Voltage Unbalance Detection: Monitor voltage levels to identify imbalances indicating an islanding condition. Rate of Change of Frequency (ROCOF): Track the rate of system frequency changes over time.
Initiate a disconnect sequence within 10 milliseconds upon detecting an islanding condition to ensure system safety and prevent equipment damage.
Do not reconnect to the main grid after an islanding event until verifying grid stability. Set a reconnection delay of at least 10 minutes.
Coordinate anti-islanding protection with other microgrid protection mechanisms, such as over/under voltage, over/under frequency, and phase imbalance protections.
SECTION 26 37 13 Page 16
1.15 PROJECT AND SITE CONDITIONS
1.15.1 Environmental Conditions
Install the MCS outdoors in a NEMA Type 3R enclosure. Ensure each system component operates effectively in its designated environment. Comply with NFPA 70 , UL 60950 , NFPA 262 , FCC EMC, and FCC Part 15 standards.
Equipment located outdoors, not provided with climate-controlled enclosure, must be capable of operating in the ambient temperature range.
Electrical equipment must conform to Section 26 20 00 INTERIOR DISTRIBUTION SYSTEM INTERIOR DISTRIBUTION SYSTEM. Equipment and wiring must be in accordance with NFPA 70 , with proper consideration given to environmental conditions such as moisture, dirt, corrosive agents, and hazardous area classification
1.15.2 Existing Conditions
1.15.2.1 External Utility Distribution System
Refer to drawings for existing utility distribution system information.
1.15.2.2 Description of Existing Electrical Interconnection Means
Building 678's distribution system connects to JB MDL - Lakehurst 34.5kV distribution system at the service switch in the mechanical yard. This is the only point of connection between Building 678 and the 34.5kV distribution system.
It is the intent of this Project that no closed transitions occur when the microgrid goes from grid to islanded operation or vice versa. No matter which connection is supplying the microgrid, upon loss of utility power within the microgrid's boundary, the microgrid's critical loads shall go dark and then be restored only after all connections to the wider distribution system have been confirmed to be open. Similarly, restoration of commercial utility power will require a complete outage of the microgrid's critical loads.
1.16 OPERATION AND MAINTENANCE (O&M) INSTRUCTIONS
Provide MCS Operation and Maintenance Instructions which include:
a. Procedures for the MCS system start-up, operation and shut-down.
b. Final As-Built Drawings.
c. Routine maintenance checklist, arranged in a columnar format: The first column listing all installed devices, the second column stating the maintenance activity or stating that no maintenance required, the third column stating the frequency of the maintenance activity, and the fourth column providing any additional comments or reference.
d. Qualified service organization list including points of contact with phone numbers.
e. Start-Up and Start-Up Testing Report.
f. Performance Verification Test (PVT Phases I, II, & III) Procedures and
SECTION 26 37 13 Page 17
Reports.
g. Procedures to restore settings / programs for all components within the MCS.
h. Procedures to update firmware in all components within the MCS.
PART 2 PRODUCTS
2.1 SYSTEM DESCRIPTION AND OPERATIONAL REQUIREMENTS
2.1.1 Microgrid System Architecture
The microgrid and associated MCS is designed as a Central-Plant Type Architecture with co-located DERs networked together and connected to the distribution system at a single point.
Submit a detailed schematic Microgrid System Architecture Diagram that displays the layout and interconnections of all MCS components, DERs, and other interfacing systems to be connected to or controlled by the MCS.
Account for the interconnection of communication networks belonging to the Government and third parties. If external grid operators require interconnection, include devices within the MCS to supply the necessary data. Two-way communication between the MCS and third-party communications systems is prohibited.
For each component and equipment indicated on the System Architecture Diagram, provide technical Product Data Sheets for all hardware components of the Microgrid Control System, including but not limited to controllers, Human-Machine Interface (HMI) devices, and communication equipment .
2.1.2 Microgrid Equipment
2.1.2.1 Microgrid Isolation Points
The microgrid's boundaries are controlled by a pad-mounted transformer and switch within the JB MDL's overall distribution system. These points are critical to the successful islanding of the critical loads within the microgrid, so the equipment at each of these isolation points must communicate on the same physical network with the MCS and directly respond to its commands. This will avoid a loss of information from the SCADA or other resource causing the microgrid to not be able to supply power during a commercial power outage within the microgrid's boundary. All data associated with grid-tied operation of the microgrid may be passed through the existing SCADA system.
2.1.2.2 Power Generating Assets
Asset Type & ID Firm Power Asset Grid-Connected Operation
Island Operation Nameplate Generation
Natural Gas Generator NG-1
Yes D/T S/F 1 500KW / 625KVA
Natural Gas Generator NG-2
Yes D/T S/F 1 500 KW / 625KVA
SECTION 26 37 13 Page 18
Asset Type & ID Firm Power Asset Grid-Connected Operation
Island Operation Nameplate Generation
Solar PV No S/P/E S 400KWac / 480Vdc
BESS-1 Yes S/P/E S/F 2 500KW/500KWh
BESS-2 Yes S/P/E S/F 2 500KW/500KWh
BESS-3 Yes S/P/E S/F 2 500KW/500KWh
POWER GENERATING ASSET TABLE LEGEND:
Grid-Connected Operation:
D - Disabled; Will not generate power while in grid-connected mode S - Supporting; Grid-following Power provided in parallel to external distribution network, only when total microgrid generation is less than microgrid connected load. No power export.
P - Power Factor Correction E - Exporting; Permitted to Export power to the external distribution network T - Test Mode; DER shall be able to operate in parallel to the grid for testing if PCC requirements are satisfied.
Island Operation:
D - Disabled; Asset will not operate in island mode F(1) - Grid-forming; optional preference indication for primary, alternate grid-forming S - Supporting; Grid-following power provided in parallel to grid-forming asset(s)
2.1.2.3 Controlled Switches, Breakers, and Devices
Asset Type & ID Asset Location Functional Requirements
Supported Condition(s)
Connected Load (W)
Breakers Microgrid Electrical Yard
O,M,D E,S
BESS-1, 2, 3 Microgrid Electrical Yard
O,M,D E 1.5MW
LEGEND:
Functional Requirements:
O - Operable Open and close via signal from MCS M - Metered data provided to microgrid control system D - Dispatchable Load; either able to increase or decrease as outlined further elsewhere
SECTION 26 37 13 Page 19
Supported Conditions E - Essential load; supported under all modes of operation S - Supported Load; served by microgrid, though may be shed based on programming D - Discretionary Load; Able to be served by microgrid. Within microgrid boundary N - Not located within the microgrid boundary
2.1.3 Functional Requirements and Design Parameters
The microgrid control system is to enable the bounded microgrid to meet the following minimum requirements. Unless stated otherwise, the MCS must fulfill these requirements. For equipment requiring control and connected to the MCS, coordinate with the connection and communication standards detailed in this specification.
2.1.3.1 Autonomy
Ensure the MCS provides essential islanding and interconnection functions, independent of external power sources and communication networks. While economic dispatch, demand forecasting, and other optimization models can utilize external networks or services, the microgrid system controller must have fallback logic to command generation that satisfies the designated critical load.
2.1.3.2 Supported Load Profile
The microgrid is designed to be capable of serving a peak critical load of
2.5 MW during both normal and peak mission activity. Incorporate multiple grid-forming DDER asset(s) in the system to sustain this load during islanded operations, as detailed in this specification. Direct each grid-forming DER asset with variable startup instructions.
2.1.3.3 Off-grid (Island) System Endurance
The microgrid system is designed to maintain off-grid endurance indefinitely without the need for commercial power restoration or DER refueling.
2.1.3.4 Energy Surety and Redundancy
Designer option - define the level of redundancy required by mission. In terms of load and redundant grid-forming or generating assets to support the critical load.
2.1.3.5 Load Shedding Requirements
An automated load shedding strategy must be implemented to maintain the integrity of both critical and non-critical loads within the microgrid boundary. The automated load shedding must occur during specified anomalies observed within the microgrid system. When islanded, load shedding must be executed under conditions such as under-frequency, under-voltage, over-voltage, DER failure, protection system activation, and system instability.
Loads are categorized into priority levels, which are defined as Level 1:
Mission-Critical Systems, Level 2: Microgrid Optional Loads and Level 3:
Non-Critical Systems. Shedding strategies must be executed in descending
SECTION 26 37 13 Page 20 order based on these levels, beginning with the least critical. Post load shedding, the MCS must automatically restore the shed loads in ascending order of priority levels, once grid stability is re-established. The restoration must be completed within 5 minutes.If sufficient generation capacity exists in island mode, either through dispatchable firm generation assets or non-dispatchable generation assets, the MCS must automatically restore shed loads based on available capacity. Level 3 loads shall not be served by the microgrid while islanded.
The MCS must employ algorithms to make shedding decisions. These algorithms must be capable of acting within 100 ms from the detection of the specified anomaly.
Provide manual override function, accessible through the Human-Machine Interface (HMI), allowing for the alteration of priority levels during emergencies.
Upon initiation and restoration of load shedding, designated personnel must be notified through HMI alerts.
2.1.3.6 Restoration and Resynchronization
The MCS must restore power to critical loads within 60 seconds following an unplanned outage. This includes the sequence of isolating all points of interconnection, starting generation assets, and restoring designated critical loads. The restoration time is to be measured from the moment of anomaly detection to the restoration of the first critical load.
Upon detecting the return of utility power at the primary side of the PCC, the system must initiate a configurable waiting period of 15 minutes.
After confirming the stability of the external grid, the MCS begins execution of an open transition, grid. Total transition duration for each load must be no less than 30s and no longer than 60s.
Provide a manual override function, available through the Human-Machine Interface (HMI) to alter restoration time settings. Notifications must be sent to designated personnel through HMI alerts when transitions are initiated and when normal operations are restored.
2.1.3.7 Power System Studies
Provide microgrid system model created using software and methods in accordance with 26 05 73 POWER SYSTEM STUDIES. Studies are intended to validate performance metrics of the provided equipment. In addition to the studies outlined by 26 05 73 POWER SYSTEM STUDIES, provide study and reports for microgrid control system in relation to voltage regulation, frequency stability, and fault response analyses.
Incorporate into the model all DERs, load profiles, and grid interaction points, such that the model is capable of simulating transient.
Submit Power System Studies including modeled analyses reports such as Short Circuit Study, Coordination Study, Arc Flash Study, and Transient Stability Study.
Upon substantial completion the microgrid system model, including all library files in their native format, unlocked and editable, must be submitted to the Government for future system analysis and upgrades.
SECTION 26 37 13 Page 21
2.1.3.8 Expandability
The Microgrid Control System (MCS) must be provided with a modular architecture to facilitate future expandability and scalability. This includes the ability to integrate additional DER, loads, and control algorithms without requiring a complete system overhaul.
Provide MCS hardware components, including controllers, sensors, and Human-Machine Interface (HMI) devices, such that the system is readily scalable by addition of supplemental components. Provide the complete MCS system to accommodate additional hardware through modular expansion units or through software updates. Software updated must be via manual installation only. All systems capable of upgrade must include a rollback feature, capable of reverting to previous software versions in case of update failures.
2.1.3.9 Real-time Data Export
The Microgrid Control System (MCS) must be capable of feeding real-time data to designated engineering analysis tools centralized within the SCADA system. The data required to be available includes, but is not limited to, system status, DER performance metrics, load profiles, and fault events. Design the MCS to support standard data exchange protocols such as OPC UA and DNP3 for seamless integration with the analysis tools.
2.1.3.10 Bi-Directional 'Blinkless' Transitions
Not required.
2.1.3.11 Island-mode Black Start Capability
The Microgrid has been designed with the capability for operator initiated and MCS automatic initiation of a black start in island-mode operation to restore power to critical and essential loads in the absence of external grid power. The MCS is to coordinate the black start process with designated DDERs capable of self-starting without external electrical supply. These DERs include battery energy storage systems and the two natural gas generators..
Provide MCS capable of employing advanced control algorithms to manage voltage and frequency during the black start process. These algorithms must be capable of stabilizing the microgrid within 30 seconds from the initiation of the black start. Voltage and frequency must be maintained within plus/minus 3 percent of nominal values during the entire black start process.
Provide a manual override function to be accessible through the Human-Machine Interface (HMI) to disable the automated black start process. This function must be password-protected and accessible only to authorized personnel.
The MCS must be tested to validate its black start capability under various load and DER conditions. Select the testing to be in accordance with this specification and IEEE 2030.8 standards.
2.1.3.12 Control System Resilience and Redundancy
Integrate resiliency and redundancy within the MCS control algorithms and components to ensure uninterrupted operation under various failure
SECTION 26 37 13 Page 22 scenarios. Notifications must be sent to designated personnel through HMI alerts upon the activation of any redundancy or failover mechanisms.
Provide the MCS with redundant controllers.
Redundant communication paths are to be established using ring topology.
In case of a communication link failure, the system is to reroute data through an alternate path.
2.1.3.13 Operational Mode Prioritization
Provide within the MCS, the ability to prioritize between efficient and resilient operational modes. The prioritization is to consider the installation location, mission requirements, and other external factors.
Prioritize operational modes based on a hierarchy that aligns with mission objectives and operational constraints. This prioritization is to be configurable and adaptable to real-time conditions.
2.1.3.14 Communication with Protection System
Provide capability within MCS to maintain real-time communication with the protection system. It must be capable of sending and receiving signals related to fault detection, isolation, and system restoration. Establish seamless and secure communication between the MCS and the protection system. This communication is to be in real-time and adhere to industry-standard protocols such as IEC 61850 , DNP3, or Modbus. The chosen protocol must support bidirectional data flow and be capable of transmitting both analog and digital signals.
Upon detection of a fault condition by the protection system, immediate notification must be sent to the MCS. Subsequently, the MCS must execute pre-configured actions such as load shedding, DER reconfiguration, or mode transition. All events detected by the protection system that result in a change of state or action by the MCS must be logged.
2.1.4 Microgrid Control System Multi-Level Architecture
This section outlines the multi-level logic architecture of the Microgrid Control System (MCS), detailing the various control levels, interface components, and external communication connections. The MCS is structured into primary, secondary, and tertiary control levels, each with distinct functionalities and responsibilities. The interaction of these logic functions with the microgrid forms the basis of the MCS state control and sequences of operation and control.
2.1.4.1 MCS Primary Control (High-Speed Communications)
2.1.4.1.1 Power Flow Management
Responsible for real-time control of power flows within the microgrid, ensuring stability and reliability.
2.1.4.1.2 Fault Detection and Isolation
Detects and isolates faults within the microgrid to prevent cascading failures.
SECTION 26 37 13 Page 23
2.1.4.1.3 Operational Safety
Ensures the safe operation of all microgrid components, including adherence to safety protocols and standards.
2.1.4.1.4 State Transition Management
Manages the transitions between different operational states of the microgrid.
2.1.4.1.5 Emergency Response
Coordinates actions during emergency situations, such as natural disasters or equipment failures.
2.1.4.2 Low-Speed Communications and Control - Secondary Control
2.1.4.2.1 Load Shedding
Manages the disconnection of non-essential loads during peak demand, during faults, or for island-mode endurance in accordance with sequences of control.
2.1.4.2.2 Economic Dispatch
Near real-time optimization through the dispatch of generation resources to meet demand at the lowest cost.
2.1.4.2.3 Reactive Control
Manages the reactive power in the system to maintain voltage levels within specified limits.
2.1.4.2.4 Load Shaping
Controls load patterns to optimize energy usage and costs.
2.1.4.2.5 Voltage Control
Maintains the voltage levels within the microgrid at optimal levels by directing dispatchable generation, reactive power capable DERs, and shedding of loads.
2.1.4.3 Low-Speed Communications and Control - Tertiary Control ( Optimization)
2.1.4.3.1 Energy Optimization
Optimizes the energy resources to reduce costs and emissions, optimize renewable energy utilization, and ensure system resilience, through optimizing storage charging/discharging schedules, demand response, and predictive optimization based on economic or weather forecasts.
2.1.4.3.2 Grid Interaction
Manages the interactions between the microgrid and the main grid.
SECTION 26 37 13 Page 24
2.1.4.3.3 Fuel Management
Optimizes fuel usage among dispatchable generation resources.
2.1.4.3.4 Curtailment Requests
Handles requests for renewable energy curtailment.
2.1.4.3.5 HMI and Visualization
Provides human-machine interface capabilities for monitoring and control.
Provides access to real-time and historical data.
2.1.4.3.6 Real-time Analytics
Performs real-time analysis of microgrid performance metrics.
2.1.4.4 MCS Physical Interface Level
2.1.4.4.1 DER Firewall
Provides cybersecurity measures to protect the MCS and interconnected systems.
2.1.4.4.2 Protocol Converter
Converts communication protocols to ensure interoperability among different devices and systems.
2.1.4.5 MCS Connection to External Communications Systems
2.1.4.5.1 SCADA
Supervisory Control and Data Acquisition system for real-time monitoring and control.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .