Amend_01_-_6861567.pdf

Repair Power Monitoring System at FRC East 6861567

SECTION 25 10 10

DIRECT DIGITAL CONTROL SYSTEMS FOR POWER MONITORING SYSTEM

06/12

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by the basic designation only.

AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)

ANSI/ATA 878.1 (1999) ARCNET - Local Area Network: Token Ring

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2008; Addenda J,L,Q,R,S,V 2009; Errata 1 & 2 2009:INT 1 & 2 2009) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASME INTERNATIONAL (ASME)

ASME B31.1 (2014; INT 1-47) Power Piping

ASTM INTERNATIONAL (ASTM)

ASTM B 117 (2009) Standing Practice for Operating Salt Spray (Fog) Apparatus

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 802.11 (2016; AI 2017; AJ 2018; AK 2018; AQ 2018)

Information Technology-Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks-Specific Requirements Part 11:

Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications

IEEE C62.41.1 (2002; R 2008) IEEE Guide on the Surges Environment in Low-Voltage (1000 V and Less) AC Power Circuits

IEEE C62.41.2 (2002) IEEE Recommended Practice on Characterization of Surges in Low-Voltage (1000 V and Less) AC Power Circuits

IEEE C62.45 (2002; R 2008) Surge Testing for Equipment Connected to Low-Voltage (1000v and less)AC Power Circuits

8/16/2019 SECTION 25 10 10 Page 1

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

ISO/IEC 8802 (2000) Telecommunications and Information Exchange Between Systems

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2017; ERTA 1-2 2017; TIA 17-1; TIA 17-2;

TIA 17-3; TIA 17-4; TIA 17-5; TIA 17-6;

TIA 17-7; TIA 17-8; TIA 17-9; TIA 17-10;

TIA 17-11; TIA 17-12; TIA 17-13; TIA

17-14; TIA 17-15; TIA 17-16; TIA 17-17 )

National Electrical Code

UNDERWRITERS LABORATORIES (UL)

UL 1449 (2006; Rev thru Sep 2009) Surge Protective Devices

UL 506 (2008; Reprint Oct 2013) Specialty Transformers

1.2 DEFINITIONS

1.2.1 ANSI/ASHRAE Standard 135

ANSI/ASHRAE Standard 135: BACnet - A Data Communication Protocol for Building Automation and Control Networks, referred to as "BACnet". ASHRAE developed BACnet to provide a method for diverse building automation devices to communicate and share data over a network.

1.2.2 ARCNET

ANSI/ATA 878.1 - Attached Resource Computer Network. ARCNET is a deterministic LAN technology; meaning it's possible to determine the maximum delay before a device is able to transmit a message.

1.2.3 BACnet

Building Automation and Control Network; the common name for the communication standard ASHRAE 135. The standard defines methods and protocol for cooperating building automation devices to communicate over a variety of LAN technologies.

1.2.4 BACnet/IP

An extension of BACnet, Annex J, defines this mechanism using a reserved UDP socket to transmit BACnet messages over IP networks. A BACnet/IP network is a collection of one or more IP subnetworks that share the same BACnet network number. See also "BACnet Broadcast Management Device".

1.2.5 BACnet Internetwork

Two or more BACnet networks, possibly using different LAN technologies, connected with routers. In a BACnet internetwork, there exists only one message path between devices.

8/16/2019 SECTION 25 10 10 Page 2

1.2.6 BACnet Network

One or more BACnet segments that have the same network address and are interconnected by bridges at the physical and data link layers.

1.2.7 BACnet Segment

One or more physical segments of BACnet devices on a BACnet network, connected at the physical layer by repeaters.

1.2.8 BBMD

BACnet Broadcast Management Device (BBMD). A communications device, typically combined with a BACnet router. A BBMD forwards BACnet broadcast messages to BACnet/IP devices and other BBMDs connected to the same BACnet/IP network. Every IP subnetwork that is part of a BACnet/IP network must have only one BBMD. See also "BACnet/IP".

1.2.9 BAS

Building Automation Systems, including DDC (Direct Digital Controls) used for facility automation and energy management.

1.2.10 BAS Owner

The regional or local user responsible for managing all aspects of the BAS operation, including: network connections, workstation management, submittal review, technical support, control parameters, and daily operation. The BAS Owner for this project is Cherry Point.

1.2.11 BIBBs

BACnet Interoperability Building Blocks. A collection of BACnet services used to describe supported tasks. BIBBs are often described in terms of "A" (client) and "B" (server) devices. The “A” device uses data provided by the "B" device, or requests an action from the “B” device.

1.2.12 BI

BACnet International, formerly two organizations: the BACnet Manufacturers Association (BMA) and the BACnet Interest Group - North America (BIG-NA).

1.2.13 BI/BTL

BACnet International/BACnet Testing Laboratories (Formerly BMA/BTL). The organization responsible for testing products for compliance with the BACnet standard, operated under the direction of BACnet International.

1.2.14 Bridge

Network hardware that connects two or more network (or BACnet internetwork) segments at the physical and data link layers. A bridge may also filter messages.

1.2.15 Broadcast

A message sent to all devices on a network segment.

8/16/2019 SECTION 25 10 10 Page 3

1.2.16 Device

Any control system component, usually a digital controller, that contains a BACnet or N2 Device Object and uses BACnet/N2 to communicate with other devices. See also "Digital Controller".

1.2.17 Device Object

Every BACnet device requires one Device Object, whose properties represent the network vi/N2sible properties of that device. Every Device Object requires a unique Object Identifier number on the BACnet/N2 internetwork.

This number is often referred to as the device instance.

1.2.18 Device Profile

A collection of BIBBs determining minimum BACnet capabilities of a device, defined in ASHRAE Standard 135-2004, Annex L. Standard device profiles include BACnet Operator Workstations (B-OWS), BACnet Building Controllers (B-BC), BACnet Advanced Application Controllers (B-AAC), BACnet Application Specific Controllers (B-ASC), BACnet Smart Actuator (B-SA), and BACnet Smart Sensor (B-SS). Each device used in new construction is required to have a PICS statement listing BIBBs supported.

1.2.19 Digital Controller

An electronic controller, usually with internal programming logic and digital and analog input/output capability, which performs control functions. In most cases, synonymous with a BACnet or N2 device described in this specification. See also "Device".

1.2.20 Direct Digital Control (DDC)

Digital controllers performing control logic. Usually the controller directly senses physical values, makes control decisions with internal programs, and outputs control signals to directly operate switches, valves, dampers, and motor controllers.

1.2.21 DDC System

A network of digital controllers, communication architecture, and user interfaces. A DDC system may include programming, sensors, actuators, switches, relays, factory controls, operator workstations, and various other devices, components, and attributes.

1.2.22 Ethernet

A family of local-area-network technologies providing high-speed networking features over various media.

1.2.23 Firmware

Software programmed into read only memory (ROM), flash memory, electrically erasable programmable read only memory (EEPROM), or erasable programmable read only memory (EPROM) chips.

1.2.24 Gateway

Communication hardware connecting two or more different protocols, similar to human language translators. The Gateway translates one protocol into

8/16/2019 SECTION 25 10 10 Page 4 equivalent concepts for the other protocol. In BACnet applications, a gateway has BACnet on one side and non-BACnet (usually proprietary) protocols on the other side. Gateways are also used to translate Modbus to BACNet MS/TP and N2 protocols for this Power Monitoring System.

1.2.25 Half Router

A device that participates as one partner in a BACnet point-to-point (PTP) connection. Two half-routers in an active PTP connection combine to form a single router.

1.2.26 Hub

A common connection point for devices on a network.

1.2.27 Internet Protocol (IP, TCP/IP, UDP/IP)

A communication method, the most common use is the World Wide Web. At the lowest level, it is based on Internet Protocol (IP), a method for conveying and routing packets of information over various LAN media. Two common protocols using IP are User Datagram Protocol (UDP) and Transmission Control Protocol (TCP). UDP conveys information to well-known "sockets" without confirmation of receipt. TCP establishes "sessions", which have end-to-end confirmation and guaranteed sequence of delivery.

1.2.28 Input/Output (I/O)

Physical inputs and outputs to and from a device, although the term sometimes describes software, or "virtual" I/O. See also "Points".

1.2.29 I/O Expansion Unit

An I/O expansion unit provides additional point capacity to a digital controller.

1.2.30 IP subnet

Internet protocol (IP) identifies individual devices with a 32-bit number divided into four groups from 0 to 255. Devices are often grouped and share some portion of this number. For example, one device has IP address

209.185.47.68 and another device has IP address 209.185.47.82. These two devices share Class C subnet 209.185.47.00

1.2.31 Local-Area Network (LAN)

A communication network that spans a limited geographic area and uses the same basic communication technology throughout.

1.2.32 LonTalk

ANSI/EIA 709. A communication protocol developed by Echelon Corp. LonTalk is an optional physical and data link layer for BACnet.

1.2.33 MAC Address

Media Access Control address. The physical node address that identifies a device on a Local Area Network.

8/16/2019 SECTION 25 10 10 Page 5

1.2.34 Master-Slave/Token-Passing (MS/TP)

ISO/IEC 8802 (Part 3). One of the LAN options for BACnet. MSTP uses twisted-pair wiring for relatively low speed and low cost communication (up to 4,000 ft at 76.8K bps).

1.2.35 Native BACnet Device

A device that uses BACnet as its primary, if not only, method of communication with other BACnet devices without intermediary gateways. A system that uses native BACnet devices at all levels is a native BACnet system.

1.2.36 Network

Communication technology for data communications. BACnet approved network types are BACnet over Internet Protocol (IP), Point to Point (PTP) Ethernet, ARCNET, MS/TP, and LonTalk®.

1.2.37 Network Number

A site-specific number assigned to each network segment to identify for routing. This network number must be unique throughout the BACnet and N2 internetwork.

1.2.38 Object

The concept of organizing BACnet information into standard components with various associated properties. Examples include analog input objects and binary output objects.

1.2.39 Object Identifier

An object property used to identify the object, including object type and instance. Object Identifiers must be unique within a device.

1.2.40 Object Properties

Attributes of an object. Examples include present value and high limit properties of an analog input object. Properties are defined in ASHRAE 135; some are optional and some are required. Objects are controlled by reading from and writing to object properties.

1.2.41 Peer-to-Peer

Peer-to-peer refers to devices where any device can initiate and respond to communication with other devices.

1.2.42 Performance Verification Test (PVT)

The procedure for determining if the installed BAS meets design criteria prior to final acceptance. The PVT is performed after installation and testing of power monitoring systems. Typically the PVT is performed by the Contractor in the presence of the Government.

1.2.43 PID

Proportional, integral, and derivative control; three parameters used to control modulating equipment to maintain a setpoint.

8/16/2019 SECTION 25 10 10 Page 6

1.2.44 PICS

Protocol Implementation Conformance Statement (PICS), describing the BACnet capabilities of a device. See BACnet, Annex A for the standard format and content of a PICS statement.

1.2.45 Points

Physical and virtual inputs and outputs. See also "Input/Output".

1.2.46 PTP

Point-to-Point protocol connects individual BACnet devices or networks using serial connections like modem-to-modem links.

1.2.47 Repeater

A network component that connects two or more physical segments at the physical layer.

1.2.48 Router

A BACnet router is a component that joins together two or more networks using different LAN technologies. Examples include joining a BACnet Ethernet LAN to a BACnet MS/TP LAN.

1.2.49 Stand-Alone Control

Refers to devices performing equipment-specific and small system control without communication to other devices or computers for physical I/O, excluding outside air and other common shared conditions. Devices are located near controlled equipment, with physical input and output points limited to 64 or less per device, except for complex individual equipment or systems. Failure of any single device will not cause other network devices to fail. BACnet "Smart" actuators (B-SA profile) and sensors (B-SS profile) communicating on a network with a parent device are exempt from stand-alone requirements.

1.3 SUBCONTRACTOR SPECIAL REQUIREMENTS

Perform all work in this section in accordance with the paragraph entitled "Subcontractor Special Requirements" in Section 01 30 00 ADMINISTRATIVE REQUIREMENTS. The paragraph specifies that all contract requirements of this section shall be accomplished directly by a first tier subcontractor.

No work required shall be accomplished by a second tier subcontractor.

1.4 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR POWER MONITORING DESCRIPTION FRC-E is served by an existing FRC-E wide Johnson Controls, Inc.

Metasys EMCS which communicates over the RDT&E communications network to multiple supervisory building controllers (SBC). The existing EMCS central server is located in Building 137. This project shall upgrade the existing Power Monitoring System (PMS) to be fully integrated into the EMCS. This shall require the addition of power meters, SBC's, and Modbus RTU to BACnet/N2 gateways. The meters shall communicate via Modbus RTU protocol, to be translated to BACNet MS/TP or N2, and shall be connected to EMCS communications network though the use of existing or new SBCs.

8/16/2019 SECTION 25 10 10 Page 7

Provide a BACnet compliant DDC system including associated equipment and accessories. Manufacturer's products, including design materials, fabrication, assembly, erection, examination, inspections, and testing shall be in accordance with ASME B31.1 and NFPA 70, except as modified herein or indicated otherwise.

The new DDC system shall interface and communicate with the existing Energy Management and Control System (EMCS) central server at MCAS Cherry Point, Building 137 utilizing the existing EMCS Ethernet network.

1.4.1 Design Requirements

Cherry Point's record documents of the FRC-E Power Monitoring System consist of Johnson Controls, Inc. (JCI) as-built drawings from the Project Name: "Cherry Point EMCS Controls Retrofit/Power Monitoring" (known as:

"Phase 1"), circa 2000, and JCI as-built drawings from the Project Name:

"Phase 2 Energy Monitoring, Cherry Point, NADEP," circa 2002. These two sets of documents are no longer current in many respects. This contract requires the contractor to provide a comprehensive set of schematics, risers, diagrams, system component lists, etc. for complete and accurate as-built documentation of the entire FRC-E Power Monitoring System.

1.4.1.1 Control System Drawings Title Sheet

Provide a title sheet for the control system drawing set. Include the project title, project location, contract number, the controls contractor preparing the drawings, an index of the control drawings in the set, and a legend of the symbols and abbreviations used throughout the control system drawings.

1.4.1.2 Control System Components List

Provide a complete list of control system components installed on this project. Include for each controller and device: control system schematic name, control system schematic designation, device description, manufacturer, and manufacturer part number.

1.4.1.3 Control System Schematics

Provide control system schematics. Typical schematics for multiple identical equipment are allowed unless otherwise requested in design or contract criteria. Include the following:

a. Location of each input and output device

b. Name or symbol for each control system component, such as V-1 for a valve

c. Setpoints, with differential or proportional band values

1.4.1.4 Electrical Ladder Diagrams

Provide equipment electrical ladder diagrams. Indicate required electrical interlocks.

1.4.1.5 Component Wiring Diagrams

Provide a wiring diagram for each type of input device and output device.

Indicate how each device is wired and powered; showing typical connections

8/16/2019 SECTION 25 10 10 Page 8 at the digital controller and power supply. Show for all field connected devices.

1.4.1.6 Terminal Strip Diagrams

Provide a diagram of each terminal strip. Indicate the terminal strip location, termination numbers, and associated point names.

1.4.1.7 Communication Architecture Schematic

Provide a schematic showing the project's entire communication network, including addressing used for LANs, LAN devices including media converters, switches, routers and bridges, gateways, controllers, workstations, and field interface devices. If applicable, show connection to existing networks. Show bus routing and component locations on a separate floor plan.

1.5 SUBMITTALS

Submit the following according to 01 33 00 SUBMITTAL PROCEDURES:

Prior to making submittals to the Government, Conduct Software Design Review and Presentation.

SD-02 Shop Drawings

Include the following in the project's control system drawing set:

Control system drawings title sheet

Control System Components List

Control system schematics

Electrical Ladder diagrams

Component wiring diagrams

Terminal strip diagrams

Communication architecture schematic

SD-03 Product Data

Direct Digital Controllers

Include BACnet PICS for each controller/device type, including smart sensors (B-SS) and smart actuators (B-SA).

Modbus RTU to BACnet and Modbus RTU to N2 Gateways

Include BACnet/N2 and workstation display information;

bi-directional communication ability; compliance with interoperability schedule; expansion capacity; handling of alarms, events, scheduling and trend data; and single device capability (not depending on multiple devices for exchanging information from either side of the gateway).

BACnet Protocol Analyzer

8/16/2019 SECTION 25 10 10 Page 9

Include capability to store and report data traffic on BACnet networks, measure bandwidth usage, filter information, and identify BACnet devices.

DDC Software

Sensors and Input Hardware

SD-05 Design Data

Performance Verification Testing Plan

Pre-Performance Verification Testing Checklist

SD-06 Test Reports

Performance Verification Testing Report

SD-07 Certificates

Contractor's Qualifications

SD-09 Manufacturer's Field Reports

Pre-PVT Checklist

SD-10 Operation and Maintenance Data

Comply with requirements for data packages in Section 01 78 23 OPERATION AND MAINTENANCE DATA, except as supplemented and modified in this specification.

BACnet Direct Digital Control Systems, Data Package 4

SD-11 Closeout Submittals

Training documentation

1.6 QUALITY ASSURANCE

1.6.1 Standard Products

Provide material and equipment that are standard manufacturer's products currently in production and supported by a local service organization.

1.6.2 Delivery, Storage, and Handling

Handle, store, and protect equipment and materials to prevent damage before and during installation according to manufacturer's recommendations, and as approved by the Contracting Officer. Replace damaged or defective items.

1.6.3 Operating Environment

Protect components from humidity and temperature variation, dust, and contaminants. If components are stored before installation, keep them within the manufacturer's limits.

8/16/2019 SECTION 25 10 10 Page 10

1.6.4 Finish of New Equipment

New equipment finishing shall be factory provided. Manufacturer's standard factory finishing shall be proven to withstand 125 hours in a salt-spray fog test. Equipment located outdoors shall be proven to withstand 500 hours in a salt-spray fog test.

Salt-spray fog test shall be according to ASTM B 117, with acceptance criteria as follows: immediately after completion of the test, the finish shall show no signs of degradation or loss of adhesion beyond 0.125 inch on either side of the scratch mark.

1.6.5 Verification of Dimensions

The contractor shall verify all dimensions in the field, and advise the Contracting Officer of any discrepancy before performing work.

1.6.6 Contractor's Qualifications

Submit documentation certifying the controls Contractor performing the work has completed at least three DDC systems installations of a similar design to this project, and programmed similar sequences of operation for at least two years. Personnel performing work on the EMCS server must have training and experience working with Johnson Controls Incorporation (JCI) Metasys Extended Architecture (MESA) software and be approved for access by the EMCS system administrator.

1.6.7 Modification of References

The advisory provisions in ASME B31.1 and NFPA 70 are mandatory.

Substitute "shall" for "should" wherever it appears and interpret all references to the "authority having jurisdiction" and "owner" to mean the Contracting Officer.

1.6.8 Project Sequence

The control system work for this project shall proceed in the following order:

a. Submit and receive approval on the Shop Drawings, Product Data, and Certificates specified under the paragraph entitled "SUBMITTALS."

Prior to submission of the Software Product Data submittal, perform Software Presentation.

b. Perform the control system installation work, including all field check-outs and tuning.

c. Submit and receive approval of the Controls System Operators Manual specified under the paragraph "CONTROLS SYSTEM OPERATORS MANUALS."

d. Submit and receive approval of the Performance Verification Testing Plan and the Pre-PVT Checklist specified under the paragraph

"PERFORMANCE VERIFICATION TESTING."

e. Perform the Performance Verification Testing.

f. Submit and receive approval on the PVT Report.

g. Submit and receive approval on the Training Documentation specified

8/16/2019 SECTION 25 10 10 Page 11 under the paragraph "INSTRUCTION TO GOVERNMENT PERSONNEL". Submit at least 30 days before training.

h. Deliver the final Controls System Operators Manuals.

i. Conduct the Phase I Training.

j. Conduct the Phase II Training.

k. Submit and receive approval of Closeout Submittals.

PART 2 PRODUCTS

2.1 DDC SYSTEM

a. Provide new DDC systems including associated equipment, accessories and communication media. Manufacturer's products, including design materials, fabrication, assembly, erection, examination, inspections, and testing shall be in accordance with ASME B31.1 and NFPA 70, except as modified herein or indicated otherwise. The new DDC system shall interface and communicate with the existing Energy Management and Control System (EMCS) at MCAS Cherry Point, Building 137. The new DDC system shall use Cherry Point's Point Naming Nomenclature and Graphical Standards attached at the end of this section. The new DDC system via the supervisory building controller shall be capable of upload/download from the central server at Building 137. All DDC points whether physical or pseudo, shall be exposed as BACnet objects and accessible by the Metasys server in Building 137 for purposes of monitoring status, controlling operation, or modifying values.

b. The Energy Management and Control System (EMCS) at MCAS Cherry Point is an enterprise system that actively receives energy and building condition information from multiple sources and provides load shedding, electric metering, alarming, trending, scheduling, set point adjusting, device communications status of all Supervisory Building Controller (SBC) and TCU for maintenance personnel. The existing EMCS system is Johnson Controls and incorporates the Metasys System that communicates over the Ethernet communications network to the supervisory building controllers. The existing EMCS central server is located at Building 137.

c. If applicable, provide supervisory building controllers (SBC) for the new DDC system. Provide all necessary hardware, drivers, software, material, and equipment, which shall allow communication between the SBC and the existing EMCS system via the RDT&E Ethernet network. The SBC shall act as the interface between the existing EMCS system and the new DDC system.

d. Provide a complete fully BACnet Open Protocol compatible Direct Digital Control (DDC) system. The system shall have stand-alone digital meters that are connected to the SBC. All BACnet devices shall be BACnet Testing Laboratories (BTL) certified and listed.

The DDC system shall be capable of monitoring all electrical meters. The manufacturer's control system shall have a successful, proven, in use history of at least 2 years. The DDC control system object configuration and communication - shall be totally native

8/16/2019 SECTION 25 10 10 Page 12

BACnet Open protocol (or N2 where indicated) with no other programming language protocol, interface, or gateways utilized, except as required by the Project documents.

e. The contractor shall update the existing Johnson Controls server, ADX-1, located in Building 137 to incorporate and integrate the new DDC system. The update requirements include, but are not limited to the EMCS server database, graphics for the new DDC system and any other affected graphics.

f. The contractor shall fully test and verify all levels of control and communication of all the DDC system controllers from the existing Johnson Controls ECMS server in Building 137. The contractor shall also test and verify all levels of control and communication of the new DDC system.

2.1.1 Supervisory Building Controller

Provide either a Johnson Controls NAE or NCE, as required to support the requirements of this contract. This will serve as both the Supervisory Building Controller and the connection point between the Power Monitoring System and the EMCS.

2.1.2 Direct Digital Controllers

2.1.2.1 Environmental Limits

Controllers shall be suitable for, or placed in protective enclosures suitable for the environment (temperature, humidity, dust, and vibration) where they are located.

2.1.2.2 Internal Clock

Provide internal clocks for all BACnet Building Controllers (B-BC) and BACnet Advanced Application Controllers (B-AAC) using BACnet time synchronization services. Automatically synchronize system clocks daily from an operator-designated controller. The system shall automatically adjust for daylight saving time.

2.1.2.3 Memory

Provide sufficient memory for each controller to support the required control, communication, trends, alarms, and messages. Protect programs residing in memory with EEPROM, flash memory, or by an uninterruptible power source (battery or uninterruptible power supply). The backup power source shall have capacity to maintain the memory during a 72-hour continuous power outage. Rechargeable power sources shall be constantly charged while the controller is operating under normal line power.

Batteries shall be replaceable without soldering. Trend and alarm history collected during normal operation shall not be lost during power outages less than 72 hours long.

2.1.2.4 Immunity to Power Fluctuations

Controllers shall operate at 90 percent to 110 percent nominal voltage rating.

8/16/2019 SECTION 25 10 10 Page 13

2.1.2.5 Transformer

The controller power supply shall be fused or current limiting and rated at 125 percent power consumption.

2.1.2.6 Wiring Terminations

Use screw terminal wiring terminations for all field-installed controllers. Provide field-removable modular terminal strip or a termination card connected by a ribbon cable for all controllers other than terminal units.

2.1.2.7 Modbus RTU to BACnet and Modbus RTU to N2 Gateways

Regardless of whether the gateway devices will be integrated into the JCI system by way of BACnet MS/TP or N2, the gateway hardware device must be identical at all instances. If N2-based network segments that serve meters are to be retained, the gateway hardware devices shall be able to support either protocol by way of menu-configuration and software download and can be field-converted from one protocol to the other by way of configuration, re-programming, and re-termination. This will support a simpler transition from N2 to BACnet at Cherry Point going forward.

Provide BACnet communication ports, whenever available as a plant equipment OEM standard option, for DDC integration via a single communication cable.

Provide gateways to connect BACnet and N2 protocols to Modbus RTU to support complete communication with the Power Monitoring System. Provide with each gateway an interoperability schedule, showing each point or event on the legacy side that the BACnet/N2 "client" will read, and each parameter that the BACnet/N2 network will write to. Describe this interoperability in terms of BACnet/N2 services, or Interoperability Building Blocks (BIBBS), defined in ASHRAE 135 Annex K. Provide two-year minimum warranty for each gateway, including parts and labor.

The following minimum capabilities are required:

a. Gateways shall be able to read and view all readable object properties listed in the interoperability schedule on the non-BACnet network to the BACnet/N2 network and vice versa where applicable.

b. Gateways shall be able to write to all writeable object properties listed in the interoperability schedule on the non-BACnet network from the BACnet/N2 network and vice versa where applicable.

c. Gateways shall provide single-pass (only one protocol to BACnet/N2 without intermediary protocols) translation from the non-BACnet protocol to BACnet/N2 and vice versa.

d. Gateways shall meet the requirements of Data Sharing Read Property (DS-RP-B), Data Sharing Write Property (DS-WP-B), Device Management Dynamic Device Binding-B (DM-DDB-B), and Device Management Communication Control (DM-DCC-B) BIBBs, in accordance with ASHRAE 135.

e. Gateways shall include all hardware, software, software licenses, and configuration tools for operator-to-gateway communications. Provide backup programming and parameters on CD media and the ability to modify, download, backup, and restore gateway configuration.

8/16/2019 SECTION 25 10 10 Page 14

2.1.2.8 Supervisory Building Controller Cabinet

Provide each digital controller in a factory fabricated cabinet enclosure.

Cabinets located indoors shall protect against dust and have a minimum NEMA 1 rating, except where indicated otherwise. Cabinets located outdoors or in damp environments shall protect against all outdoor conditions and have a minimum NEMA 4X rating. Outdoor control panels and controllers must be able to withstand extreme ambient conditions, without malfunction or failure, whether or not the controlled equipment is running. If necessary, provide a thermostatically controlled panel heater in freezing locations, and an internal ventilating fan in locations exposed to direct sunlight.

Cabinets shall have a hinged lockable door and an offset removable metal back plate. Provide like-keyed locks for all hinged panels provided and a set of two keys at each panel, with one key inserted in the lock.

2.1.2.9 Main Power Switch and Receptacle

Provide each control cabinet with a main external power on/off switch located inside the cabinet. Also provide each cabinet with a separate 120 VAC duplex receptacle.

2.1.3 DDC System Integration and Monitoring

a. Two laptop workstations and associated printers shall be provided as specified.

b. All interface to the DDC system shall be provided through the existing EMCS server at Building 137. The workstation via the EMCS server at Building 137 shall be capable of monitoring, troubleshooting, and making adjustments to the program or operating parameters of all DDC controllers, including TCU's. The workstation shall also be capable of remotely programming of all controllers, including TCU's. The contractor shall provide a temporary workstation for system interface and start-up until the connection to the EMCS server at Building 137 is completed, tested, and verified.

c. DDC system shall routinely operate continuously without connection to the workstation. Information at the workstation is not required for day to day operations of the direct digital controllers.

2.1.3.1 Software

The EMCS server (ADX-1) uses Johnson Controls Incorporation (JCI) Metasys Extended Architecture (MESA) software. Modify and update the existing EMCS server at Building 137 as necessary for proper interface with the new DDC system. The MESA software shall be configured to operate according to the DDC system manufacturer's specifications. Software shall be installed in the supervisory building controller (SBC) that permits monitoring and troubleshooting of the DDC system using the ADX-1 server. The ADX-1 in conjunction with the SBC software shall permit modification of controller parameters and control for all controllers, both high level and low level application specific. Operations shall be menu selected. Menu selections shall be made with a mouse.

a. Menu System: Menu system shall allow an operator to select a particular function or access a particular screen through successive menu penetration or icon selection.

8/16/2019 SECTION 25 10 10 Page 15

b. Controller Parameter Modification: The ADX-1 software shall be an interface for performance specified in paragraph entitled "Parameter Modification" and available through a workstation logged into the ADX-1 server. Parameter modification shall require only that an operator "fill in the blank" for a parameter on a screen requesting the information in plain language.

Parameter modifications shall download to the appropriate controllers at the operator request.

2.1.3.2 Graphic-Based Software

Update the existing graphics located on the ADX-1 server in Building 137 to incorporate and integrate the new DDC system. Create new graphics as required for the new DDC controllers. Graphic-based software shall provide graphical location of the building on the map, the building floor plan, the building electrical systems, and the DDC system. The current value and point name of every I/O point shall be shown on at least one graphic and in its appropriate physical location relative to building and electrical systems.

a. Graphic shall closely follow the style of the control drawings in representing electrical systems, sensors, controlled devices and point names.

b. Graphic Title: Graphics shall have an identifying title visible when the graphic is viewed.

c. Dynamic Update: When the ADX-1 server is on-line with the control system, point data shall update dynamically on the graphic images.

d. Graphic Penetration: Provide graphic penetration using buttons to select graphics with more detail or to select different equipment.

e. Graphic Types: Graphic-based software shall have graphics of the building exterior, building section, floor plans, and electrical systems. At a minimum, provide the following graphics:

(1) Building Exterior Graphic: Show exterior architecture, major landmarks, and building number.

(2) Building Section Graphic: Show floors in section graphic with appropriate floor name on each floor.

(3) Floor Plan Graphics: Provide a single graphic for each floor, unless the graphic will contain more information than can reasonably be shown on a single graphic. Show each controlled variable in the zone. Provide visual warning for each point in alarm. Show existing and new bus routings on floor plan as physically installed in the building.

2.1.4 DDC Software

2.1.4.1 Programming

The existing FRC-E Basewide EMCS Metasys® software shall be upgraded to integrate new meter points and graphics into the existing system including storage of meter data to history files. New graphics screens for PMS meters and screens for analysis of historical meter data/trends shall be

8/16/2019 SECTION 25 10 10 Page 16 provided. The PMS shall have an interface that allows multiple points to be selected from points lists for user selected time periods. Report and graph formats shall be flexible and allow user configuration of scales, ranges, colors, line types, legends, labels, etc. Reports shall allow summary statistics to be calculated for selected points and allow output to spreadsheet programs. A separate dedicated screen shall be provided that provides a snapshot of the the overall health of all meters. A "green" indicator shall indicate the meter is functioning and reporting properly, otherwise the indicator shall be "red." Provide the ability to alert the BAS Owner and up to 10 other designated individuals via text message and email should any meter enter into "red" status. Printing capability shall also be included. Database maintenance functions such as data backup to archive and retrieval from archive shall be included. This application shall be accessible from any EMCS workstation (existing and new workstations provided under this contract). If the Metasys® software does not have this capability, then a separate application can be used that accesses the historical data. Provide programming to execute the power monitoring system inputs indicated. Provide all programming and tools to configure and program all controllers. Provide programming routines in simple, easy-to-follow logic with detailed text comments describing what the logic does and how it corresponds to the project's written sequence of operation.

a. Graphic-based programming shall use a library of function blocks made from pre-programmed code designed for BAS control. Function blocks shall be assembled with interconnecting lines, depicting the control sequence in a flowchart. If providing a computer with device programming tools as part of the project, graphic programs shall be viewable in real time showing present values and logical results from each function block.

b. Menu-based programming shall be done by entering parameters, definitions, conditions, requirements, and constraints.

c. For line-by-line and text-based programming, declare variable types (local, global, real, integer, etc.) at the beginning of the program.

Use descriptive comments frequently to describe the programming.

d. If providing a computer with device programming tools as part of the project, provide a means for detecting program errors and testing software strategies with a simulation tool. Simulation may be inherent within the programming software suite, or provided by physical controllers mounted in a NEMA 1 test enclosure. The test enclosure shall contain one dedicated controller of each type provided under this contract, complete with power supply and relevant accessories.

2.1.4.2 Parameter Modification

All writeable object properties, and all other programming parameters needed to comply with the project specification shall be adjustable for devices at any network level, including those accessible with web-browser communication, and regardless of programming methods used to create the applications.

2.1.4.3 Time Synchronization

Provide time synchronization, including adjustments for leap years, daylight saving time, and operator time adjustments.

8/16/2019 SECTION 25 10 10 Page 17

2.1.4.4 Scheduling

Provide operating schedules as indicated, with equipment assigned to groups. Changing the schedule of a group shall change the operating schedule of all equipment in the group. Groups shall be capable of operator creation, modification, and deletion. Provide capability to view and modify schedules in a seven-day week format. Provide capability to enter holiday and override schedules one full year at a time.

2.1.4.5 Object Property Override

Allow writeable object property values to accept overrides to any valid value. Where specified or required for the sequence of control, the Out_Of_Service property of Objects shall be modifiable using BACnet's write property service. When documented, exceptions to these requirement are allowed for life, machine, and process safeties.

2.1.4.6 Alarms and Events

Alarms and events shall be capable of having programmed time delays and high-low limits. When a computer workstation or web server is connected to the BACnet internetwork, alarms/events shall report to the computer, printer, e-mail, as defined by an authorized operator. Otherwise alarms/events shall be stored within a device on the BACnet network until connected to a user interface device and retrieved. Provide alarms/events in agreement with the point schedule, sequence of operation, and the BAS Owner. At a minimum, provide programming to initiate alarms/events any time a piece of equipment fails to operate, a control point is outside normal range or condition shown on schedules, communication to a device is lost, a device has failed, or a controller has lost its memory.

2.1.4.7 Trending

Provide trend services on the supervisory building controller capable of trending all object present values set points, and other parameters indicated for trending on project schedules. Trends may be associated into groups, and a trend report may be set up for each group. Trends are stored within a device on the BACnet network, with operator selectable trend intervals from 10 seconds up to 60 minutes and/or change of value set points. Server shall be capable of storing trend data for up to 12 months. The minimum number of consecutive trend values stored at one time shall be 100 per variable. When trend memory is full, it shall be selectable to stop trending or overwrite the oldest data. Upon reaching 3/4 of the device buffer limit (via Notification_Threshold property), by operator request, or by time schedule for archiving. Archived and real-time trend data shall be available for viewing numerically and graphically for at the EMCS server and connected notebook computers.

2.1.4.8 Device Diagnostics

Each controller shall have diagnostic LEDs for power, communication, and device fault condition. The DDC system shall recognize and report a non-responsive controller.

2.1.4.9 Power Loss

Upon restoration of power, the DDC system shall perform an orderly restart and restoration of control.

8/16/2019 SECTION 25 10 10 Page 18

2.1.5 BACnet Protocol Analyzer

Provide a BACnet protocol analyzer and required cables and fittings for connection to the BACnet network. The analyzer shall include the following minimum capabilities:

a. Capture and store to a file data traffic on all network levels.

b. Measure bandwidth usage.

c. Filtering options with ability to ignore select traffic.

2.1.6 Workstation Hardware (Laptop)

Provide two standard laptop computers meeting the following minimum requirements for the Computer Workstation Hardware (workstation).

2.1.6.1 Processor

2.1.6.1.1 Laptop

Quad-core processor designed for laptop applications. Processor speed must be at least 50 percent of the speed of the fastest Intel laptop processor commercially available.

2.1.6.2 Random Access Memory (RAM)

300 percent of the recommended requirements of the software to be installed on the server and no less than 8GB.

2.1.6.3 Communications Ports

2.1.6.3.1 Laptop

Two USB ports, plus a PCMCIA card slot or an additional USB port, plus an integral RS-232 serial port or an additional USB port and a USB to RS-232 serial adapter. Also include one Ethernet port.

2.1.6.4 Hard Drive and Controller

2.1.6.4.1 Laptop

250GB or larger solid state drive.

2.1.6.5 Optical Drive

DVD-RW drive

2.1.6.6 Video Output

2.1.6.6.1 Laptop

32-bit color with a minimum resolution of 1920 by 1080 at minimum refresh rates of 70 Hz and VGA or HDMI output.

8/16/2019 SECTION 25 10 10 Page 19

2.1.6.7 Network Interface

2.1.6.7.1 Laptop

Integrated 1000Base-T Ethernet with RJ45 connector and an integrated IEEE 802.11b/g/n wireless interface. The Laptop must have a physical switch for activation and deactivation of the wireless interface.

2.1.6.8 Monitor

2.1.6.8.1 Laptop

LCD Screen sized as indicated but no less than 325 mm 15.6 inch nominal with a maximum supported resolution of no less than 1600 by 900 pixels.

2.1.6.9 Keyboard and Smart Card Reader

2.1.6.9.1 Laptop

Standard laptop keyboard. Internal smart card reader compatible with a Department of Defense Common Access Card (CAC).

2.1.6.10 Mouse

2.1.6.10.1 Laptop

Integrated touch-pad plus a 2-button wired USB optical scroll mouse with a minimum resolution of 400 dots per inch.

2.1.7 Printers

Provide two network printers as indicated. Provide network printers which have a 100Base-T or faster interface with an RJ45 connection and a firmware print spooler compatible with the Operating System print spooler.

2.1.7.1 Laser Printer

Provide laser printers as indicated meeting the following minimum requirements:

Resolution 600 by 600 dots per inch

Printing Time 10 pages per minute

Data Buffer Size 16 Megabytes

Media Type Paper and transparency film

Media Size ANSI A( 8.5 by 11 inches) and other sizes as indicated

Paper Cassette 250 sheet capacity

2.2 SENSORS AND INPUT HARDWARE

Coordinate sensor types with the BAS Owner to keep them consistent with existing installations.

8/16/2019 SECTION 25 10 10 Page 20

2.2.1 Energy Metering

2.2.1.1 Electric Meters

Provide kilowatt-hour (kWh) meter(s) shown as specified in Section

26 27 14.00 20 ELECTRICITY METERING.

2.3 ELECTRICAL POWER AND DISTRIBUTION

2.3.1 Transformers

Transformers shall conform to UL 506. For control power other than terminal level equipment, provide a fuse or circuit breaker on the secondary side of each transformer.

2.3.2 Surge and Transient Protection

Provide each digital controller with surge and transient power protection.

Surge and transient protection shall consist of the following devices, installed externally to the controllers.

2.3.2.1 Power Line Surge Protection

Provide surge suppressors on the incoming power at each controller or grouped terminal controllers. Surge suppressors shall be rated in accordance with UL 1449, have a fault indicating light, and conform to the following:

a. The device shall be a transient voltage surge suppressor, hard-wire type individual equipment protector for 120 VAC/1 phase/2 wire plus ground.

b. The device shall react within 5 nanoseconds and automatically reset.

c. The voltage protection threshold, line to neutral, shall be no more than 211 volts.

d. The device shall have an independent secondary stage equal to or greater than the primary stage joule rating.

e. The primary suppression system components shall be pure silicon avalanche diodes.

f. The secondary suppression system components shall be silicon avalanche diodes or metal oxide varistors.

g. The device shall have an indication light to indicate the protection components are functioning.

h. All system functions of the transient suppression system shall be individually fused and not short circuit the AC power line at any time.

i. The device shall have an EMI/RFI noise filter with a minimum attenuation of 13 dB at 10 kHz to 300 MHz.

j. The device shall comply with IEEE C62.41.1 and IEEE C62.41.2, Class "B" requirements and be tested according to IEEE C62.45.

8/16/2019 SECTION 25 10 10 Page 21

k. The device shall be capable of operating between minus 20 degrees F and plus 122 degrees F.

2.3.2.2 Telephone and Communication Line Surge Protection

Provide surge and transient protection for DDC controllers and DDC network related devices connected to phone and network communication lines, in accordance with the following:

a. Provide surge and transient protection at each incoming and outgoing connection to and from DDC network devices, including but not limited to gateways, meters, NAE's, NCE's, etc. Each incoming and outgoing network connection must include surge protection.

b. The device shall provide continuous, non-interrupting protection, and shall automatically reset after safely eliminating transient surges.

c. The protection shall react within 5 nanoseconds using only solid-state silicon avalanche technology.

d. The device shall be installed at the distance recommended by its manufacturer.

2.3.2.3 Controller Input/Output Protection

Provide controller inputs and outputs with surge protection via optical isolation, metal oxide varistors (MOV), or silicon avalanche devices.

Fuses are not permitted for surge protection.

2.3.3 Wiring

Provide complete electrical wiring for the DDC System, including wiring to transformer primaries. Unless indicated otherwise, provide all normally visible or otherwise exposed wiring in conduit. Where conduit is required, control circuit wiring shall not run in the same conduit as power wiring over 100 volts. Circuits operating at more than 100 volts shall be in accordance with Section 26 20 00, INTERIOR DISTRIBUTION SYSTEM. Run all circuits over 100 volts in conduit, metallic tubing, covered metal raceways, or armored cable. Use plenum-rated cable for circuits under 100 volts in enclosed spaces. Examples of these spaces include HVAC plenums, within walls, above suspended ceilings, in attics, and within ductwork.

2.3.3.1 Power Wiring

The following requirements are for field-installed wiring:

a. Wiring for 24 V circuits shall be insulated copper 18 AWG minimum and rated for 300 VAC service.

PART 3 EXECUTION

3.1 INSTALLATION

Perform the installation under the supervision of competent technicians regularly employed in the installation of DDC systems.

3.1.1 BACnet/N2 Naming and Addressing

Coordinate with the BAS Owner and provide unique naming and addressing for

8/16/2019 SECTION 25 10 10 Page 22

BACnet networks and devices using the attached Point Naming Convention.

a. MAC Address

Every BACnet and N2device shall have an assigned and documented MAC Address unique to its network. For Ethernet networks, document the MAC Address assigned at its creation. For ARCNET or MS/TP, assign from 00 to 64.

b. Network Numbering

Assign unique numbers to each new network installed on the BACnet and N2internetwork. Provide ability for changing the network number;

either by device switches, network…