Amendment 0009 - 23 09 23.13 - BACNET DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC.pdf

2ND RADIO BATTALION COMPLEX PHASE II 19P1458

MCB CAMP LEJEUNE, NC ePROJECTS W.O. NO.: 1397586

SECTION 23 09 23.13

BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC 09/22

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.

AIR MOVEMENT AND CONTROL ASSOCIATION INTERNATIONAL (AMCA)

AMCA 500-D (2012) Laboratory Methods of Testing Dampers for Rating

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2012; Addenda AR 2013; Errata 1 2013; INT 1-9 2013; Errata 2 2013; INT 10-12 2014;

Errata 3-4 2014; Addenda AI-AY 2014; INT 13-17 2015; Errata 5 2015) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE 135.1 (Errata 1 2015; INT 1 2013; Addenda O 2014) Method of Test for Conformance to BACnet

ASME INTERNATIONAL (ASME)

ASME B16.5 (2013) Pipe Flanges and Flanged Fittings:

NPS 1/2 Through NPS 24 Metric/Inch Standard

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

ASTM INTERNATIONAL (ASTM)

ASTM A126 (2004; R 2014) Standard Specification for Gray Iron Castings for Valves, Flanges, and Pipe Fittings

ASTM B117 (2011) Standard Practice for Operating Salt Spray (Fog) Apparatus

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-D (2014) Control Network Protocol Specification

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

SECTION 23 09 23.13 22 Page 1

Less) AC Power Circuits

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

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

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

ISO 8802-3 (2000) Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD)Access Method and Physical Layer Specifications

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2014; AMD 1 2013; Errata 1 2013; AMD 2 2013; Errata 2 2013; AMD 3 2014; Errata 3-4 2014; AMD 4-6 2014) National Electrical Code

NFPA 72 (2013) National Fire Alarm and Signaling Code

NFPA 90A (2015) Standard for the Installation of Air Conditioning and Ventilating Systems

SHEET METAL AND AIR CONDITIONING CONTRACTORS' NATIONAL ASSOCIATION

(SMACNA)

SMACNA 1966 (2005) HVAC Duct Construction Standards Metal and Flexible, 3rd Edition

UNDERWRITERS LABORATORIES (UL)

UL 1449 (2014;Reprint Mar 2015) Surge Protective Devices

UL 506 (2008; Reprint Oct 2013) Specialty Transformers

UL 508A (2013; Reprint Jan 2014) Industrial Control Panels

UL 916 (2007; Reprint Aug 2014) Standard for Energy Management Equipment

SECTION 23 09 23.13 22 Page 2

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

NOT USED

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.

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

SECTION 23 09 23.13 22 Page 3 operation, including: network connections, workstation management, technical support, control parameters, and daily operation. The BAS Owner for this project is Camp Lejeune Public Works .

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.

1.2.16 Device

Any control system component, usually a digital controller, that contains a BACnet Device Object and uses BACnet 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 visible properties of that device. Every Device Object requires a unique Object Identifier number on the BACnet 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

SECTION 23 09 23.13 22 Page 4 functions. In most cases, synonymous with a BACnet device described in this specification. See also "Device".

1.2.19.1 Terminal Device Controllers

Terminal device controllers typically are controllers with less control features, may have integrated actuators, and may be mounted directly on equipment (with enclosures).

1.2.19.2 Field Controllers

Field controllers typically have a greater capability for input/output and customization, do not have integral actuators, are mounted in an enclosure not on the equipment and are used for equipment such as VAV air handlers.

1.2.19.3 Plant Controllers

Plant controllers are typically used to control various equipment in mechanical rooms such as pumps, heat exchangers, and chillers.

1.2.19.4 Supervisory Building Controller (SBC)

The Supervisory Building Controller is used to coordinate all equipment in a building, input scheduling, and is used as a connection point for transferring configuration files to the other controllers. The SBC shall communicate with other controllers and equipment through a BACnet MS/TP bus. Depending on approvals and capabilities, the SBC may be used as a point of connection between the Camp Lejeune EMCS network (IP) and the building level control network (BACnet MS/TP).

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 Energy Management & Control System (EMCS)

The EMCS at Camp Lejeune 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 adjustment and device status of all supervisory building controllers for maintenance personnel. The EMCS receives real time electrical utility pricing data and automatically manages to Camp Lejeune's energy target. The existing EMCS consists of two servers, 1) Johnson Controls Incorporated (JCI) Metasys Extended Architecture (ADX server), and 2) Niagara FX N4 supervisor (JCI FX web supervisor). Both of the systems communicate over the MCEN and either may be used to fulfill the requirements of this specification.

SECTION 23 09 23.13 22 Page 5

1.2.23 Ethernet

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

1.2.24 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.25 Gateway

Communication hardware and software connecting two or more different protocols, similar to human language translators. The Gateway translates one protocol into equivalent concepts for the other protocol. In BACnet applications, a Gateway has BACnet on one side and non-BACnet protocols on the other side.

1.2.26 Global ID

An identification number assigned to each Supervisory Building Controller. The Global ID includes assigned MSTP Trunk Instance Numbers and a range of BACnet Instance Numbers to be used for the Field Controllers. The Global ID is assigned by Public Works.

1.2.27 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.28 Hub

A common connection point for devices on a network.

1.2.29 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.30 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.31 I/O Expansion Unit

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

SECTION 23 09 23.13 22 Page 6

1.2.32 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.33 Local-Area Network (LAN)

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

1.2.34 LonTalk

CEA-709.1-D . A communication protocol developed by Echelon Corp. LonTalk is not permitted .

1.2.35 MAC Address

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

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

ISO 8802-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.37 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.38 Network

Communication technology for data communications. BACnet approved network types are BACnet over Internet Protocol (IP), Point to Point (PTP) Ethernet, MS/TP, and LonTalk®. In general, networks within the building, all controllers and equipment will be BACnet MS/TP, unless noted otherwise.

1.2.39 Network Number

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

1.2.40 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.41 Object Identifier

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

SECTION 23 09 23.13 22 Page 7

1.2.42 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.43 Peer-to-Peer

Peer-to-peer refers to devices where any device can initiate and respond to communication with other devices. Peer-to-Peer configurations must be reviewed and approved by Camp Lejeune Public Works Department.

1.2.44 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, testing, and balancing of mechanical systems. Typically the PVT is performed by the Contractor in the presence of the Government.

1.2.45 PID

Proportional, integral, and derivative control; three parameters used to control modulating equipment to maintain a setpoint. Derivative control is often not required for HVAC systems (leaving "PI" control).

1.2.46 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.47 Points

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

1.2.48 PTP

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

1.2.49 Repeater

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

1.2.50 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. If a router is connected directly to the MCEN, it must be listed on the approved DIACAP equipment list and must be Marine Corps DADMS listed and approved.

1.2.51 Stand-Alone Control

Refers to devices performing equipment-specific and small system control without communication to other devices or computers for physical I/O, SECTION 23 09 23.13 22 Page 8 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 or communications will not cause other network devices to fail. Internal time clocks and onboard scheduling are required to allow for stand-alone control if not connected to a Supervisory Building Controller . 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. Provide stand-alone control routines to provide for energy saving sequences such as free cooling. Provide stand-alone control routines that operate without connection to the BACnet/IP and MS/TP networks during a loss of communication.

1.2.52 Supervisory Building Controller

Supervisory Controller that is the main interface for the building control system.

1.3 SUBCONTRACTOR SPECIAL REQUIREMENTS

Perform all work in this section in accordance with the paragraph 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 HVAC DESCRIPTION

1.4.1 Design Requirements

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. The Title Block of each drawing must include the Drawing revision, i.e. Submittal, Revision 1, Revision 2, As-Built, etc., including the date.

1.4.1.2 List of I/O Points

Also known as a Point Schedule, provide for each input and output point physically connected to a digital controller: point name, point description, point type (Analog Output (AO), Analog Input (AI), Binary Output (BO), Binary Input (BI)), point sensor range, point actuator range, point address, BACnet object, associated BIBBS (where applicable), and point connection terminal number and cable type (18/2, 18/3, etc) . Typical schedules for multiple identical equipment are allowed unless otherwise requested in design or contract criteria. All points shall adhere to the Camp Lejeune Standard naming conventions.

1.4.1.3 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, model, part number, firmware version, serial number, SECTION 23 09 23.13 22 Page 9 physical location (e.g. Building 4, room 112 overhead) , and power requirements (i.e. AC/DC voltage and power draw) . For sensors, include point name, sensor range, and operating limits. For valves, include body style, Cv, design flow rate, pressure drop, valve characteristic (linear or equal percentage), and pipe connection size. For actuators, include point name, spring or non-spring return, modulating or two-position action, normal (power fail) position, nominal control signal operating range (0-10 volts DC or 4-20 milliamps), and operating limits.

1.4.1.4 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 ,specify room # for remote devices.

b. Flow diagram for each piece of HVAC equipment

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

d. Setpoints, with differential or proportional band values

e. Written sequence of operation for the HVAC equipment

f. Valve and Damper Schedules, with normal (power fail) position

g. Control cabinet general layout, include all devices, point count, cable type (18/2, 18/3, etc), 24VAC VA power requirement for all devices including those powered from the cabinet.

1.4.1.5 HVAC Equipment Control Ladder Diagrams

Provide HVAC equipment control ladder diagrams. Indicate required electrical interlocks. Ladder diagram schematics shall include 120 VAC and low voltage devices in each panel. Ladder diagram schematics shall also include all field devices (sensors, relays, actuators, etc.) and any connection point to controlled equipment or devices.

1.4.1.6 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 at the digital controller and power supply. Show for all field connected devices such as control relays, motor starters, actuators, sensors, and transmitters.

1.4.1.7 Terminal Strip Diagrams

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

1.4.1.8 BACnet Communication Architecture Schematic (Network Riser)

Provide a schematic showing the project's entire BACnet communication network complete with wire sizes , including Internet Protocol (IP), Media

SECTION 23 09 23.13 22 Page 10

Access Control (MAC), BACnet network, Device ID, field bus address, BBMDs, any devices using BACnet FDR, and Firmware version / Operating System, LAN devices including routers and bridges, gateways, controllers, workstations, and field interface devices. If applicable, show connection to existing networks and include the existing network in the riser diagram. Include surge protection device at all locations on the riser when the field controller communication trunk is leaving or entering a building and at all external equipment (such as chillers) .

1.4.1.9 Control Panel Layout

Provide a detailed panel layout for each control panel, relay panel, etc.

The layout shall include all components to be installed in the panel including controllers, terminal strips, transformers, wireway, etc.

1.5 SUBMITTALS

Submit detailed and annotated manufacturer's data, drawings, and specification sheets for each item listed, that clearly show compliance with the project specifications.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-02 Shop Drawings

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

Control System Drawings Title Sheet

List of I/O Points

Control System Components List

Control System Schematics

HVAC Equipment Control Ladder Diagrams

Component Wiring Diagrams

Terminal Strip Diagrams

BACnet Communication Architecture Schematic

Sequence of Operations

Control Panel Layout

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).

BACnet Gateways

Include BACnet and workstation display information;

bi-directional communication ability; compliance with

SECTION 23 09 23.13 22 Page 11 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).

Notebook Computer Software

BACnet Operator Workstation

Include BACnet PICS for Operator Workstation software.

Notebook Computer

Sensors and Input Hardware

Output Hardware

Surge and Transient Protection

Indicators

Duct smoke detectors

Variable Frequency (Motor) Drives

SD-05 Design Data

Performance Verification Testing Plan

SD-06 Test Reports

Performance Verification Testing Report

Bus Waveform Report

SD-07 Certificates

Contractor's Qualifications

Contractor's Training Certifications

SD-10 Operation and Maintenance Data

Comply with requirements for data packages in Section 01 78 23 OPERATION AND MAINTENANCE DATA and in Section 01 78 24.00 20

FACILITY ELECTRONIC OPERATION AND MAINTENANCE SUPPORT INFORMATION

(eOMSI) , except as supplemented and modified in this specification.

BACnet Direct Digital Control Systems , Data Package 4

Controls System Operators Manuals , Data Package 4

VFD Service Manuals , Data Package 4

SD-11 Closeout Submittals

Training Documentation

Warranty Information

SECTION 23 09 23.13 22 Page 12

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.

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 B117, 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 the installation, programming, checkout, commissioning and training shall, at a minimum, have obtained all certifications required by the manufacturer for the tasks they are performing. Tasks include any activity required to execute and complete the contracted work. Certifications for each person shall be submitted prior to the beginning of the contracted work. Certifications shall be made available at any time upon the request from Camp Lejeune.

1.6.7 Modification of References

The advisory provisions in ASME B31.1 , NFPA 70 and the manufacturer's recommendations 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.

SECTION 23 09 23.13 22 Page 13

1.6.8 Project Sequence

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

a. Preparatory meeting for controls work.

b. Submit and receive approval on the Shop Drawings, Product Data, and Certificates specified under the paragraph SUBMITTALS>

c. Submit and receive approval for Performance Verification Testing (PVT) Plan.

d. DDC Pre-Installation Meeting - Contractor shall provide minimum fifteen days notice to COTR when scheduling pre-installation meeting.

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

f . Overhead Inspection.

g. Provide support to TAB personnel as specified under the paragraph TEST

AND BALANCE SUPPORT.

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

i . Perform the Performance Verification Testing.

j . Submit and receive approval on the PVT Report. Submit As-Built Control Drawings

k. PVT Report Acceptance test for Season 1.

l . Submit and receive approval on the Training Documentation specified under the paragraph INSTRUCTION TO GOVERNMENT PERSONNEL and VFD Service Support. Submit at least 30 days before training.

m. Deliver the final Controls System Operators Manuals and VFD Service Manuals.

n. Conduct the Phase I Training and VFD on-site/hands-on training.

o. Conduct the Phase II Training.

p. Submit and receive approval of Closeout Submittals.

q. PVT Report Acceptance Test for Season 2.

PART 2 PRODUCTS

2.1 DDC SYSTEM

a. Provide a networked DDC system for stand-alone control in compliance with the latest revision of the ASHRAE 135 BACnet standard. Include all programming, objects, and services required to meet the sequence of control. Provide BACnet MS/TP communications between the DDC system and native BACnet devices furnished with HVAC equipment and plant equipment including boilers, chillers, and variable frequency

SECTION 23 09 23.13 22 Page 14 drives. Devices provided shall be certified in the BACnet Testing Laboratories (BTL) Product Listing and in accordance with ASHRAE 135.1 Method of Test for Conformance to BACnet. Controls provided integral to equipment shall be part of the DDC system and shall fully comply with this specification. Coordinate integration of integral controls into the system as a whole. BACnet over IP is not permitted within the DDC system.

b. Assist the Government in interfacing the new DDC system with the site's existing server and operator workstation and software . Create graphics , scheduling, alarming, and trending.

2.1.1 Supervisory Building Controller ( SBC)

ASHRAE 135 building controller that is the main interface for the building control system. Provide either a Johnson Controls Incorporated NAE, NCE, SNE or SNC; OR a JACE based on the Niagara N4 platform. The JACE (JAVA Application Control Engine) shall be minimally based on a Tridium 8000 with expanded memory and embedded "Niagara Workbench or Workplace" software.

Any device implementing the Niagara Framework is a Niagara Framework Supervisory Gateway and must meet these requirements. In addition to the general requirements for all DDC Hardware, Niagara Framework Supervisory Gateway Hardware must:

a. Be direct digital control hardware.

b. Have an unrestricted interoperability license and its Niagara Compatibility Statement (NiCS) must follow the Tridium Open NiCS Specification.

c. Manage communications between a field control network and the Niagara

Framework Monitoring and Control Software, and between itself and other Niagara Framework Supervisory Gateways. Niagara Framework Supervisory Gateway Hardware must use Fox protocol for communication with other Niagara Framework Components, regardless of the manufacturer of the other components.

d. Be fully programmable using the Niagara Framework Engineering Tool and must support the following:

(1) Time synchronization, Calendar, and Scheduling using Niagara Scheduling Objects

(2) Alarm generation and routing using the Niagara Alarm Service

(3) Trending using the Niagara History Service and Niagara Trend Log Objects

(4) Integration of field control networks using the Niagara Framework Engineering Tool

(5) Configuration of integrated field control system using the Niagara Framework Engineering Tool when supported by the field control system

e. Meet the following minimum hardware requirements:

SECTION 23 09 23.13 22 Page 15

(1) Two 10/100/1000 Mbps Ethernet Port(s)

(2) One or more MS/TP ports.

(3) Central Processing Unit of 1000 Mhz or higher.

(4) Embedded operating system.

f. Provide access to field control network data and supervisory functions via web interface and support a minimum of 16 simultaneous users.

Note: implementation of this capability may not be required on all projects.

g. Submit a backup of each Niagara Framework Supervisory Gateway. The backup must be sufficient to restore a Niagara Framework Supervisory Gateway to the final as-built condition such that a new Niagara Framework Supervisory Gateway loaded with the backup is indistinguishable in functionality from the original.

2.1.1.1 Niagara Framework Engineering Tool

The Niagara Framework Engineering Tool must be Niagara Workbench or an equivalent Niagara Framework engineering tool software and must:

a. Have an unrestricted interoperability license and its Niagara Compatibility Statement (NiCS) must follow the Tridium Open NiCS Specification.

b. Be capable of performing network configuration for Niagara Framework Supervisory Gateways and Niagara Framework Monitoring and Control Software.

c. Be capable of programming and configuring of Niagara Framework Supervisory Gateways and Niagara Framework Monitoring and Control Software.

d. Be capable of discovery of Niagara Framework Supervisory Gateways and all points mapped into each Niagara Framework Supervisory Gateway and making these points accessible to Niagara Framework Monitoring and Control Software.

2.1.1.2 Supervisory Controller MCEN Network Homerun

See UFGS 27 10 00 and CLGS 27 10 00 for requirements

2.1.2 EMCS Interface

The Energy Management & Control System (EMCS) at Camp Lejeune is comprised of two separate systems. Both of the systems communicate over the basewide Marine Corps Enterprise Network (MCEN). One uses the Johnson Controls Network Automation Engine (NAE), Network Control Engine (NCE), Supervisory Network Engine (SNE) or Supervisory Network Control Engine (SNC) to the ADX server. The second system uses a Niagara FX N4 web supervisor with a JACE in the building communicating using Fox protocol.

Because of IT security and permissions, only these systems and equipment are permitted as part of the EMCS.

SECTION 23 09 23.13 22 Page 16

2.1.2.1 Supervisory Building Controller

Provide either a Johnson Controls NAE, NCE, SNE, SNC or a JACE. This will serve as both the Supervisory Building Controller and the connection point between the buildings DDC and the EMCS. Provide a five year service license on all Supervisory Controllers. Provide a reserve of 10% of additional points and additional devices on the Supervisory Controller license at the final project acceptance.

The contractor shall assign Camp Lejeune Public Works Department as the owner and manager of all licenses including 3rd party drivers.

2.1.2.2 Palo Alto Firewall

For any building provided with a new Supervisory controller, contractor shall also provide a Palo Alto Firewall Model PAN-PA-220R. Contractor shall also provide a five year government support option for the Palo Alto firewall complete with all licenses.

2.1.3 Direct Digital Controllers

Direct digital controllers shall be UL 916 rated.

DDC Field Controllers:

Acceptable DDC field controllers are Facility Explorer, Metasys or Distech.

2.1.3.1 I/O Point Limitation

The total number of I/O hardware points used by a single stand-alone digital controller, including I/O expansion units, shall not exceed 64, except for complex individual equipment or systems. Place I/O expansion units in the same cabinet as the digital controller. The field controller must have one spare Configurable Output and one spare Universal Input available per system upon project completion, i.e. AHU, ERU, DOAS, HW System, CHW System and other building primary systems. VAV controllers and programmable thermostats are excluded.

2.1.3.2 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.3.3 Stand-Alone Controllers

Provide stand-alone direct digital controllers with internal time clocks if not connected to a Supervisory Building Controller . Each piece of equipment shall be controlled by a single controller to provide stand-alone control in the event of any building communication failure.

All I/O points specified for a piece of equipment shall be integral to its controller and serial connected expansion modules. Provide stable and reliable stand-alone control using default values or other method for values normally read over the network.

2.1.3.4 Internal Clock

Provide internal clocks and scheduling for all Direct Digital Controllers. Provide controllers with BTL listed profiles for all BACnet Building Controllers (B-BC) and BACnet Advanced Application Controllers

SECTION 23 09 23.13 22 Page 17

(B-AAC) using BACnet time synchronization services. This includes but is not limited to VAV Controllers, Fan Coil controllers, Heat Pump controllers and any terminal controllers. BACnet Application specific controllers (B-ASC) will only be accepted for dedicated small exhaust system control such as restroom and mechanical room exhaust fans.

Automatically synchronize system clocks daily from an operator-designated controller. The system shall automatically adjust for daylight saving time.

2.1.3.5 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.3.6 Immunity to Power Fluctuations

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

2.1.3.7 Transformer

The controller power supply shall be fused or current limiting and rated at 125 percent power consumption. Each transformer must singularly serve the connected load, i.e. do not wire transfomers in parallel on the load side. Transformer shall be mounted in the upper portion of the control panel to aid in heat dissipation. The 120 volt power feed must also enter in the upper portion of the cabinet - power shall not be brought in from the bottom of the panel.

2.1.3.8 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.3.9 Input and Output Interface

Provide hard-wired input and output interface for all controllers as follows:

a. Protection: Shorting an input or output point to itself, to another point, or to ground shall cause no controller damage. Input or output point contact with sources up to 24 volts AC or DC for any duration shall cause no controller damage.

b. Binary Inputs: Binary inputs shall monitor on and off contacts from a "dry" remote device without external power, and external 5-24 VDC voltage inputs.

SECTION 23 09 23.13 22 Page 18

c. Pulse Accumulation Inputs: Pulse accumulation inputs shall conform to binary input requirements and accumulate pulses at a resolution suitable to the application.

d. Analog Inputs: Analog inputs shall monitor low-voltage (0-10 VDC), current (4-20 mA), or resistance (thermistor or RTD) signals.

e. Binary Outputs: Binary outputs shall send a pulsed 24 VDC low-voltage signal for modulation control, or provide a maintained open-closed position for on-off control. Where appropriate, provide a method to select normally open or normally closed operation.

f. Analog Outputs: Analog outputs shall send modulating 0-10 VDC or 4-20 mA signals to control output devices.

g. Tri-State Outputs: Tri-State outputs shall provide three-point floating control of terminal unit electronic actuators.

2.1.3.10 Digital Controller BACnet Internetwork

Provide intermediate gateways, only when requested by the Government and shown on the contract drawings, to connect existing non-BACnet devices to the BACnet internetwork. Controller and operator interface communication shall conform to ASHRAE 135, BACnet. If a controller becomes non-responsive, the remaining controllers shall continue operating and not be affected by the failed controller.

2.1.3.11 Communications Ports

a. Direct-Connect Interface Ports: Provide at least one extra communication port at each local BACnet network for direct connecting a notebook computer or BACnet hand-held terminal so all network BACnet objects and properties may be viewed and edited by the operator.

2.1.3.12 BACnet Gateways

Provide BACnet communication ports, whenever available as a plant equipment OEM standard option, for DDC integration via a single communication cable. Typical BACnet controlled plant equipment includes, but is not limited to, boilers, chillers, and variable frequency motor drives.

Provide gateways to connect BACnet to legacy systems, existing non-BACnet devices, and existing non-BACnet DDC controlled plant equipment, only when specifically requested and approved by the Government, and shown on the Government approved BACnet Communication Architecture Schematic. Provide with each gateway an interoperability schedule, showing each point or event on the legacy side that the BACnet "client" will read, and each parameter that the BACnet network will write to. Describe this interoperability in terms of BACnet 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 network and vice versa where applicable.

SECTION 23 09 23.13 22 Page 19

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 network and vice versa where applicable.

c. Gateways shall provide single-pass (only one protocol to BACnet without intermediary protocols) translation from the non-BACnet protocol to BACnet 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.

2.1.3.13 Digital Controller Cabinet

Provide each digital controller including gateways, in a factory fabricated locked 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 4 rating. Mechanical rooms that contain steam service or equipment including new steam boiler rooms are considered damp environments. 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, except controllers integral with terminal units, like those mounted on VAV boxes. 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. All devices must be mounted only to the cabinet backplane with adequate space allowed for serviceability and proper heat dissipation from devices. The Supervisory controller cabinet door position (closed/open) shall be monitored with a door switch and BACnet programmable relay such as the Functional Devices RIBTW2401B-BC. An "open" door status shall initiate an alarm to the EMCS Server.

2.1.3.14 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 convenience receptacle.

2.1.4 DDC Software

2.1.4.1 Programming

Provide programming to execute the sequence of operation indicated.

Provide all programming , tools , interfaces, cables, etc. to configure and program all controllers. All software shall be licensed to Marine Corps Base, Camp Lejeune Complex for unrestricted use on Camp Lejeune Complex and reproduction for use on Camp Lejeune Complex. Software keys and

SECTION 23 09 23.13 22 Page 20

"dongles" are not permitted. 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. All logic programming and control functions shall be closed loop, command and feedback for fault detection and alarming when status != command.

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 (variable types include but are not limited to the following: local, global, real, and integer) 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 Short Cycling Prevention

Provide setpoint differentials and minimum on/off times to prevent equipment short cycling.

2.1.4.4 Equipment Status Delay

Provide an adjustable delay from when equipment is commanded on or off and when the control program looks to the status input for confirmation.

2.1.4.5 Run Time Accumulation

Use the Elapsed Time Property to provide re-settable run time accumulation for each Binary Output Object connected to mechanical loads greater than 1 HP, electrical loads greater than 10 KW, or wherever else specified.

2.1.4.6 Timed Local Override

Provide an adjustable override time for each push of a timed local

SECTION 23 09 23.13 22 Page 21 override button.

2.1.4.7 Time Synchronization

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

2.1.4.8 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.9 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.10 Alarms and Events

Alarms and events shall be capable of having programmed time delays and high-low limits. When a web server is connected to the BACnet internetwork, alarms/events shall report to web server 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.11 Trending

Provide BACnet trending all object present values , set points, and other parameters indicated for trending on project schedules or at the request of Camp Lejeune or commissioning agents . 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 24 hours . The minimum number of consecutive trend values stored at one time shall be 100 per variable.

When trend memory is full, the most recent data shall overwrite the oldest data.

The BACnet system shall allow for Change-Of-Value (COV) subscription based trending at user defined thresholds.

The B-BC shall upload trends automatically 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 workstation and connected notebook computers.

SECTION 23 09 23.13 22 Page 22

Additionally, provide daily trend on geothermal well field supply and return temperatures. Allocate sufficient memory to store 24 months data.

2.1.4.12 Device Diagnostics

Each controller shall have diagnostic LEDs for power, communication, and device fault condition.