23 09 00.pdf

1005 Michael Rd Offce Renovation 210019

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

02/ 25 MCBCL

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) system, except for the Front End, suitable for the control of the heating, ventilating and air conditioning (HVAC) and other building-level systems as indicated and shown and in accordance with Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS, and other referenced Sections.

1.1.1 BACnet Direct Digital Control Systems for HVAC Description:

a. Remove existing and merge new BACnet DDC with existing BACnet DDC system(s) including associated equipment and accessories. Existing DDC system is manufactured by Distech .

b. All new devices are accessible using a Web browser interface and communicate using ASHRAE 135 BACnet communications without the use of gateways, unless gateways are shown on the design drawings and specifically requested by the Government. Where gateways are allowed, they must support ASHRAE 135, including all object properties and read-write services shown on Government approved interoperability schedules. Manufacturer's products, including design, materials, fabrication, assembly, inspection, and testing shall be in accordance with ASHRAE 135, ASME B31.1 , and NFPA 70 , except where indicated otherwise.

1.1.2 System Requirements

Provide systems meeting the requirements this Section and other Sections referenced by this Section, and which have the following characteristics:

a. The system implements the control sequences of operation shown in the Contract Drawings using DDC hardware to control mechanical and electrical equipment.

b. The system meet the requirements of this specification as a stand-alone system and does not require connection to any other system.

c. Control sequences reside in DDC hardware in the building. The building control network is not dependent upon connection to a Utility Monitoring and Control System (UMCS) Front End or to any other system for performance of control sequences. To the greatest extent practical, the hardware performs control sequences without reliance on the building network.

d. The hardware is installed such that individual control equipment can be replaced by similar control equipment from other equipment manufacturers with no loss of system functionality.

e. All necessary documentation, configuration information, programming tools, programs, drivers, and other software are licensed to and

SECTION 23 09 00 Page 1 otherwise remain with the Government such that the Government or their agents are able to perform repair, replacement, upgrades, and expansions of the system without subsequent or future dependence on the Contractor, Vendor or Manufacturer.

f. Sufficient documentation and data, including rights to documentation and data, are provided such that the Government or their agents can execute work to perform repair, replacement, upgrades, and expansions of the system without subsequent or future dependence on the Contractor, Vendor or Manufacturer.

g. Hardware is installed and configured such that the Government or their agents are able to perform repair, replacement, and upgrades of individual hardware without further interaction with the Contractor, Vendor or Manufacturer.

1.1.3 Verification of Dimensions

After becoming familiar with all details of the work, verify all dimensions in the field, and advise the Contracting Officer of any discrepancy before performing any work.

1.1.4 Drawings

The Government will not indicate all offsets, fittings, and accessories that may be required on the drawings. Carefully investigate the mechanical, electrical, and finish conditions that could affect the work to be performed, arrange such work accordingly, and provide all work necessary to meet such conditions.

1.2 RELATED SECTIONS

Related work specified elsewhere:

a. Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

b. Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

c. Section 25 05 11 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

1.3 REFERENCES

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

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2020; Interpretation 1-8 2021; Errata 1-2 2021; Addenda CD 2021; Addenda BY-CE 2022;

Interpretation 9-10 2022) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE 135.1 (2023) Method of Test for Conformance to BACnet

SECTION 23 09 00 Page 2

AMERICAN SOCIETY OF MECHANICAL ENGINEERS (ASME)

ASME B31.1 (2022) Power Piping

ASTM INTERNATIONAL (ASTM)

ASTM B117 (2019) 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 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 (1000 V and Less) AC Power Circuits

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2023) National Electrical Code

UNDERWRITERS LABORATORIES (UL)

UL 506 (2017; Reprint Jan 2022) UL Standard for Safety Specialty Transformers

UL 508A (2018; Reprint Jul 2022) UL Standard for Safety Industrial Control Panels

UL 1449 (2021) UL Standard for Safety Surge Protective Devices

1.4 DEFINITIONS

The following list of definitions includes terms used in Sections referenced by this Section and are included here for completeness.The definitions contained in this Section may disagree with how terms are defined or used in other documents, including documents referenced by this Section. The definitions included here are the authoritative definitions for this Section and all Sections referenced by this Section.

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

SECTION 23 09 00 Page 3

1.4.2 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.4.3 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.4.4 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.4.5 BACnet Segment

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

1.4.6 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.4.7 BAS

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

1.4.8 BAS Owner

The regional or local user responsible for managing all aspects of the BAS operation, including: network connections, workstation management, technical support, control parameters, and daily operation. The BAS Owner for this project is Camp Lejeune FRCS Cyber Operation Group. Point of contact:

Public Works Division/FRCS Cyber Ops 1110 Ash Street MCB Camp Lejeune, NC 28547

(910) 450-6891

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

SECTION 23 09 00 Page 4

1.4.10 BI

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

1.4.11 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.4.12 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.4.13 Broadcast

A message sent to all devices on a network segment.

1.4.14 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.4.15 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.4.16 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.4.17 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 device described in this specification. See also "Device".

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

SECTION 23 09 00 Page 5

1.4.17.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.4.17.3 Plant Controllers

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

1.4.17.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.4.18 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.4.19 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.4.20 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 Niagara FX N4 supervisor (JCI FX web supervisor).

1.4.21 Ethernet

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

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

SECTION 23 09 00 Page 6

1.4.23 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.4.24 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 the BAS Owner.

1.4.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.4.26 Hub

A common connection point for devices on a network.

1.4.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.4.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.4.29 I/O Expansion Unit

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

1.4.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.4.31 ISSM

Information Systems Security Manager

SECTION 23 09 00 Page 7

1.4.32 Local-Area Network (LAN)

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

1.4.33 LonTalk

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

1.4.34 MAC Address

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

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

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.4.36 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.4.37 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.4.38 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.4.39 Object

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

1.4.40 Object Identifier

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

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

SECTION 23 09 00 Page 8

1.4.42 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.4.43 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. The PVT is performed by the Contractor.

1.4.44 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.4.45 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.4.46 Points

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

1.4.47 PTP

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

1.4.48 Repeater

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

1.4.49 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.4.50 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 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

SECTION 23 09 00 Page 9 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.4.51 Supervisory Building Controller

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

1.4.52 TAB

Testing, adjusting, and balancing (of HVAC systems).

1.5 ADMINISTRATIVE REQUIREMENTS

1.5.1 FRCS Required Training

It is the contractor's sole responsibility to ensure any contractor personnel or subcontractor who will be performing any work pertaining to any new or existing SBC:

a. Attend mandatory FRCS provided training at the frequency prescribed by

FRCS.

b. Maintain valid credentials throughout the duration of the project.

FRCS training is typically conducted every two weeks at a location designated by FRCS. Contact the BAS Owner to schedule training and to obtain login credentials. The contractor shall bear the sole responsibility for any delays or mobilizations that may occur should the contractor or subcontractor fail to fulfil the qualifications required to maintain valid credentials. FRCS will not provide unscheduled training under any circumstances. Temporary credentials will not be provided.

1.5.2 DDC Pre-Installation Meeting

Prior to starting the installation, meet with the Contracting Officer's Technical Representative (COTR) and the BAS owner to develop a mutual understanding relative to the details of the DDC system requirements.

Requirements to be discussed include, but not limited to, required submittals, work schedule, field quality control, BAS Supervisory controller configuration requirements, and project DDC Specification requirements. Ensure that a representative from the controls contractor and the controls contractor's installation team or subcontractor is present. Contractor shall provide minimum fifteen days notice to COTR when scheduling pre-installation meeting.

1.5.3 Pre-PVT Meeting

A Pre-PVT meeting to review the Pre-PVT Checklist is required to coordinate all aspects of the PVT and shall include the Contractor's QA representative, the Contractor's PVT administrator, the Contracting Officer's representative, and the BAS Owner.

1.5.4 Overhead Inspection by BAS Owner

Prior to closing in any ceiling that contains any DDC component above it, meet with the COTR and the BAS Owner for a site inspection. Mutiple

SECTION 23 09 00 Page 10 overhead inspections may be required based on construction schedule.

Provide minimum 14 days notice to COTR when scheduling each overhead inspection.

1.5.5 Final Inspection by BAS Owner

After receiving approval of the Controls System Operators Manual, meet with the COTR and the BAS Owner for a final site inspection. Provide minimum 14 days notice to COTR when scheduling the final inspection.

1.5.6 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. DDC Pre-Installation Meeting.

d. Submit and receive approval for PVT Plan.

e. Pre-PVT Meeting.

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

g. Overhead Inspection by BAS Owner.

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

AND BALANCE SUPPORT.

i. Perform final tuning of all PID loops after TAB field acceptance testing is complete.

j. Perform the PVT.

k. Submit and receive approval for the PVT Report.

l. Submit and receive approval for As-Built Control Drawings.

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

n. Final inspection by BAS Owner.

o. Submit and receive approval for Trends.

p. PVT Report Field Acceptance Test.

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

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

SECTION 23 09 00 Page 11

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

t. Conduct the Phase II Training.

u. Submit and receive approval of Closeout Submittals.

1.6 SUBMITTALS

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-02 Shop Drawings

Control System Drawings Title Sheet ; G

List Of I/O Points ; G

Control System Components List ; G

Control System Schematics ; G

Hvac Equipment Control Ladder Diagrams ; G

Sequence Of Operations ; G

Component Wiring Diagrams ; G

Terminal Strip Diagrams ; G

Bacnet Communication Architecture Schematic (Network Riser) ; G

Control Panel Layout ; G

SD-06 Test Reports

Existing Conditions Report ; G

Control Contractor's Performance Verification Testing Plan ; G

Equipment Supplier's Performance Verification Testing Plan ; G

Performance Verification Testing Report ; G

Trends ; G

Bus Waveform Report ; G

SD-07 Certificates

Contractor's Qualifications ; G

Contractor's Training Certifications ; G

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

SECTION 23 09 00 Page 12

FACILITY ELECTRONIC OPERATION AND MAINTENANCE SUPPORT INFORMATION

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

Controls System Operators Manuals ; G, Data Package 4

SD-11 Closeout Submittals

Training Documentation ; G

Warranty Information ; G

1.7 QUALITY ASSURANCE

1.7.1 Standard Products

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

1.7.2 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.7.3 Verification of Dimensions

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

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

1.7.5 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.7.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 Contractor's Training Certifications required by the manufacturer for the tasks they are performing. Tasks include any activity required to

SECTION 23 09 00 Page 13 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.8 DELIVERY, STORAGE, AND HANDLING

Store and protect products from the weather, humidity, and temperature variations, dirt and dust, and other contaminants, within the storage condition limits published by the equipment manufacturer, and as approved by the Contracting Officer. Replace damaged or defective items.

PART 2 PRODUCTS

Provide products meeting the requirements of Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS for BACnet, other referenced Sections, and this Section.

2.1 DDC SYSTEM

a. Provide a networked DDC system for stand-alone control in compliance with the latest revision of the ASHRAE 135. 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 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.2 GENERAL PRODUCT REQUIREMENTS

Units of the same type of equipment must be products of a single manufacturer. Each major component of equipment must have the manufacturer's name and address, and the model and serial number in a conspicuous place. Materials and equipment must be standard products of a manufacturer regularly engaged in the manufacturing of these and similar products. The standard products must have been in a satisfactory commercial or industrial use for two years prior to use on this project.

The two year use must include applications of equipment and materials under similar circumstances and of similar size. DDC Hardware not meeting the two-year field service requirement is acceptable provided it has been successfully used by the Contractor in a minimum of two previous projects. The equipment items must be supported by a service organization. Items of the same type and purpose must be identical, including equipment, assemblies, parts and components.

2.3 OPERATION ENVIRONMENT

Provide continuous protection of components from the following conditions:

SECTION 23 09 00 Page 14

a. Pressure: Pressure conditions normally encountered in the installed location.

b. Vibration: Vibration conditions normally encountered in the installed location.

c. Temperature:

(1) Products installed indoors: Ambient temperatures in the range of 32 to 112 degrees F and temperature conditions outside this range normally encountered at the installed location.

(2) Products installed outdoors or in unconditioned indoor spaces:

Ambient temperatures in the range of -35 to +151 degrees F and temperature conditions outside this range normally encountered at the installed location.

d. Humidity: 10 to 95 percent relative humidity, noncondensing and humidity conditions outside this range normally encountered at the installed location.

2.4 WIRELESS CAPABILITY

Wireless networking is not authorized for this project as a default. Do not use any wireless communication unless approved by the ISSM which is done on a case-by-case basis. Any device with wireless communication capability is considered to be using wireless communication, regardless of whether or not the device is actively communicating wirelessly, except when wireless communication has been physically permanently disabled (such as through the removal of the wireless transceiver).

Wireless connections must follow all DoD, USN, and USMC requirements and be approved by the PWD ISSM.

2.4.1 Wireless IP Communications

Do not install wireless IP networks, including:

a. Wireless access points

b. Ad-hoc wireless networks

c. WiFi Direct communication

2.4.2 Non-IP Wireless Communication

Non-IP Wireless networking is not authorized for this project.

2.5 ELECTRICAL POWER AND CONTROL WIRING

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

SECTION 23 09 00 Page 15

2.5.2 Surge and Transient Protection

Provide each control cabinet with surge and transient power protection.

Surge protection is not required for small terminal unit controllers such as VAV controllers. Surge and transient protection shall consist of the following devices, installed externally to the controllers.

2.5.2.1 Power-Line Surge Protection

Provide surge suppressors on the incoming power at each direct digital controller or grouped terminal controllers and shall be installed externally to the device or devices being protected. 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 .

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

2.5.2.2 Communication Line Surge Protection

Provide surge and transient protection for all DDC controllers and all DDC network related devices connected to phone lines, network communication lines, lines from exterior equipment, and lines from other buildings including mechanical buildings in accordance with the following:

a. The device shall provide continuous, non-interrupting protection.

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

SECTION 23 09 00 Page 16

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

d. Include the location of the surge and transient protection devices on the control drawing network riser.

e. The device shall be located in an enclosure.

f. Surge and transient protection devices must be located at the point where the communication line exists the building and at the exterior equipment location.

2.5.3 Wiring

Provide complete electrical wiring for the DDC System, including wiring to transformer primaries. Run all control wiring in rigid or flexible conduit, metallic tubing, or covered metal raceways, unless noted otherwise. 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. Follow cable manufacturer's recommendations or requirements based on the cable usage, such as outdoors and/or underground.

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

b. Wiring for 120 V circuits shall be insulated copper 12 AWG minimum and rated for 600 VAC service.

2.5.3.2 Analog Signal Wiring and Binary Wiring

Provide in accordance with control manufacturer's recommendations and the following: Field-installed analog signal wiring shall be 18 AWG single or multiple twisted pair. Each cable shall be 100 percent shielded and have a drain wire. Each wire shall have insulation rated for 300 VAC service.

Cables shall have an overall aluminum-polyester or tinned-copper cable-shield tape. All binary input and output wiring shall be 18 AWG.

2.5.3.3 MS/TP Communication Bus

a. Provide system manufacturer's recommended or preferred cabling.

b. Follow cable manufacturer's recommendations or requirements based on the cable usage, such as outdoors and/or underground.

c. Splices in communication cable are not allowed. Segments of communication cable between field devices shall be solid lengths with no splices.

2.5.3.4 Conduit

Except for flexible conduit, all conduit for controls less than 100 volts

SECTION 23 09 00 Page 17 shall be colored blue. All conduit to be blue must be pre-tinted by the manufacturer. Painting or wrapping of conduit is not permitted. Junction box cover plates, cable/wire trough covers, etc., for controls shall be blue. Fittings and boxes do not need to be blue. The requirement for blue colored conduit may be waived for designated exposed areas at the discretion of BAS Owner and Public Works Department.

PART 3 EXECUTION

3.1 DESIGN REQUIREMENTS

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

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

3.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, 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.

3.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 number for remote devices.

b. Flow diagram for each piece of HVAC equipment.

SECTION 23 09 00 Page 18

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.

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

3.1.6 Sequence of Operations

Provide HVAC control system sequence of operation and control logic diagrams in the same format as the Contract Drawings. Within these drawings, refer to devices by their unique identifiers. Submit sequences of operation and control logic diagrams for each HVAC system

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

3.1.8 Terminal Strip Diagrams

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

3.1.9 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 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. Show connection to existing networks and include the existing network in the riser diagram. Include all external network capabilities. 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).

3.1.10 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

SECTION 23 09 00 Page 19 including controllers, terminal strips, transformers, wireway, etc.

3.2 DEMOLITION

Remove and/or demolish all existing controls, cabling, conductors, conduit, controllers, power circuits and cabinets that are no longer needed after new work is installed. Contractor shall inform government prior to start of demolition and shall give the government the option to salvage any existing equipment. Contractor shall remove all unused existing conduit and shall not reuse any existing conduit. Any existing systems to remain, must remain functional and operate properly after all demolition is complete.

3.3 EXISTING CONDITIONS

3.3.1 Existing Conditions Survey

Perform a field survey, including testing and inspection of the equipment to be controlled and submit an Existing Conditions Report documenting the current status and its impact on the Contractor's ability to meet this specification. For those items considered nonfunctional, document the deficiency in the report including explanation of the deficiencies and estimated costs to correct the deficiencies. As part of the report, define the scheduled need date for connection to existing equipment. Make written requests and obtain Government approval prior to disconnecting any controls and obtaining equipment downtime.

3.3.2 Existing Equipment Downtime

Make written requests and obtain Government approval prior to disconnecting any controls and obtaining equipment downtime.

3.3.3 Existing Control System Devices

Inspect, calibrate, and adjust as necessary to place in proper working order all existing devices which are to be reused.

3.4 INSTALLATION

Fully install and test the control system in accordance Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS for BACnet or Niagara BACnet systems, and this Section.

Perform the installation under the supervision of competent technicians regularly employed in the installation of DDC systems. All material and equipment shall be installed in accordance with the manufacturer's recommendations for the intended purpose and NFPA 70 . Maintain a copy of the manufacture's recommendations on the Contruction Site. Use the more stringent methods when manufacturer's recommendations, and plans & specification requirements differ. Use the "Preferred" method when alternative methods are given. The word "should" will be considered to mean "shall". Bring any conflicts between manufacturer's recommendations and plans and specification requirements to the Government's attention.

All equipment shall be installed level and plumb.

3.4.1 Wiring Criteria

a. Run circuits operating at more than 100 volts in rigid or flexible

SECTION 23 09 00 Page 20 conduit, metallic tubing, covered metal raceways, or armored cable.

b. Run all control wiring in blue rigid or flexible conduit, blue metallic tubing, or covered metal raceways, unless noted otherwise.

All control wiring located inside mechanical rooms shall be in conduit or metallic tubing. All conduit and junction box covers, cable/wire trough covers, etc., shall be blue in color.

c. Do not run binary control circuit wiring in the same conduit as power wiring over 100 volts. Where analog signal wiring requires conduit, do not run in the same conduit with AC power circuits or control circuits operating at more than 100 volts.

d. Provide circuit and wiring protection required by NFPA 70 .

e. Minimum conduit size is 3/4-inch. Maximum conduit fill is 40% or the cable manufacturer's recommended amount, whichever is less. Provide insulated throat at all conduit terminations to protect wiring from burrs. Support conduit by pipe straps, wall brackets, threaded rod conduit hangers, or ceiling trapeze. Plastic cable ties are not acceptable. Fasten by wood screws to wood; by toggle bolts on hollow masonry units; by concrete inserts or expansion bolts on concrete or brick; and by machine screws, welded threaded studs, or spring-tension clamps on steel work. Threaded C-clamps may be used on rigid steel conduit only. Do not weld conduits or pipe straps to steel structures.

Do not exceed one-fourth proof test load for load applied to fasteners. Provide vibration resistant and shock-resistant fasteners attached to concrete ceiling. The use of masonry screws to support conduit is not permitted.

f. Do not bury aluminum-sheathed cable or aluminum conduit in concrete.

g. Input/output identification: Permanently label each field-installed wire, cable, and pneumatic tube at each end with descriptive text using a commercial wire marking system, minimum 9 point font. Labels shall fully encircle the wire, cable, or tube. The single line text shall run parallel to the wire, cable, or tube and shall be repeated so as to be viewable without twirling or twisting the wire. Locate the markers within 2 inches of each termination. Label shall include type of network and destination of cable (ex. BACnet/AHU-1). Match the names and I/O number to the project's point list. Similarly label all power wiring serving control devices, including the word "power" and panel board and circuit number, or transformer location in the label.

Number each pneumatic tube every six feet. Label all terminal blocks with alpha/numeric labels. All wiring and the methods shall be in accordance with UL 508A .

h. Permanently display controller wiring diagram for each controller on the inside of the control cabinet door. Diagram shall be neatly lettered and taped or adhered with sticky back label.

i. Conduit identification: All conduits shall be labeled within 36 inches from terminations, boxes, bends or wall penetrations. Labels shall be 3/8 inches bold black lettering on white background and indicate what system the conduit contains. Apply labels every 10 feet of line of sight or a distance agreed upon by Camp Lejeune Public Works Department. Provide label for each side of a wall pentration by the conduit. The agreed upon distance shall be for a single building or project only. Label shall be visible and legible, while standing on

SECTION 23 09 00 Page 21 the floor, from up to three sides with a minimum dimension of 1.9 inches x 4 inches. Conduit that includes power circuits shall be labeled with source panel and circuit, and destination cabinet or equipment. When MSTP is installed within conduit, label conduit with trunk number and to and from device (ie. MSTP-01 From VAV 1-1 to VAV 1-2).

Provide a label at each control panel on the 120 VAC conduit. The label shall contain the source panel and circuit identifier.

Label Example: SF-C, SF-S, SF-O (3 cables, Supply Fan Command, Supply Fan Status, Supply Fan Output).

Label Example: ZN-T/ZN-H/ZN-Q (1 cable, Zone Temperature, Zone Humidity, Zone Quality).

j. Each terminal device shall have its own terminal conduit run. Device boxes or devices or panels shall not be used as "pass thru" for wiring.

k. Conduit to equipment and devices shall be run tight to walls, and ceilings. Avoid conduit on the floor, i.e. conduit shall not block access to or past equipment. Flex conduit is to be used only when EMT or rigid conduit is not able to satisfy the application such as a transition to a sensor or equipment. Flex conduit shall be limited to a maximum length of 3 ft.

l. For controller power, provide new 120 VAC circuits, with ground if not defined on the electrical drawings. Provide each circuit with a dedicated breaker, and run wiring in its own conduit, separate from any control wiring. Connect the controller's ground wire to the electrical panel ground; conduit grounds are not acceptable. Include a label on the 120 VAC circuit conduit at each control panel. The label is to include the source panel and circuit identification. The label size shall be a minimum of 1.9 inches by 4 inches, 3/8 inch black lettering on white background.

m. Supervisory Building Controllers (SBC) shall be powered from a dedicated transformer for the SBC only. Each control cabinet shall have a dedicated 24 volt transformer. The 120 VAC power branch circuit shall be dedicated to the DDC control system. Factory provided transformers in equipment must be used as a source of power only for the control devices intended by the equipment manufacturer.

n. Surge…