ASHE_17-1019_Tec_Spec_Rev_2.pdf

U.S. AIR FORCE

31ST FIGHTER WING

31ST CES/CENM

AVIANO AIR BASE, ITALY

Technical Specifications

Project :

ASHE 17-1019

REPAIR HVAC CONTROLS, MULTI

Location: Area F Aviano Air Base, Aviano, Italy

Date:

Rev:

09 March 2018

Page | 1 of 60 ASHE 17-1019 REV 2 09 March 2018

INDEX

SCOPE OF PROJECT 2

TECHNICAL SPECIFICATION 3

SUBMITTAL OF MATERIALS 49

CONSTRUCTION AREA SCREENING 49

PROJECT SIGN 50

JOB SITE MOBILIZATION 50

SAFETY 50

HAZMAT/HAZWASTE HOUSEKEEPING 50

PRESERVATION OF EXISTING CONDITIONS 51

WORK SITE CONDITIONS 51

AIRFIELD SAFETY TRAINING 52

PARKING 52

ACCESS ROUTES 52

TRUCKING AND ROADS 52

NOISE CONTROL 53

CONSTRUCTION SITE RESTORATION 53

PROCEDURES AND WORK PHASES 53

SALVAGEABLE MATERIALS 53

CONSTRUCTION DRAWINGS 53

REVISED MASTER SPECIFICATIONS 53

ADDITIONAL NORMS AND STANDARDS 54

PART I – DEMOLITIONS, REMOVALS AND EXCAVATIONS 56

IA - ARCHITECTURAL WORKS 56

IB - STRUCTURAL WORKS 56

IC – CIVIL WORKS 56

ID - MECHANICAL WORKS 56

IE - ELECTRICAL WORKS 56

PART II – ARCHITECTURAL, STRUCTURAL AND CIVIL WORK 56

IIA - ARCHITECTURAL WORKS 56

IIB - STRUCTURAL WORKS 56

IIC - CIVIL WORK 56

PART III – MECHANICAL WORK 56

PART IV – ELECTRICAL WORK 59

Page | 2 of 60 ASHE 17-1019 REV 2 09 March 2018

SCOPE OF PROJECT AND APPLICABLE CONDITIONS

SCOPE OF PROJECT

Design and Build Project scope is to repair HVAC Systems in three (3) facilities at Aviano AB identified by the following building numbers:

1403, 1442, 1483

Existing HVAC control systems electronic devices are currently broken or not properly working.

This project shall replace the HVAC monitoring and control systems of all the facilities listed above. The driving criteria to develop new systems is to have control systems as much as possible open source to the customer and energy efficient. It is also scope of this project, balancing and testing the HVAC system of the facilities involved.

Additionally, existing lightning protection system, grounding systems and SPD devices shall be evaluated and tested, deficiencies identified and corrected to protect HVAC electronic equipment. Project design shall require a first knowledge of existing HVAC and electrical systems of each facility and therefore existing as built drawings are an integral part of this document.

A –NEW WORKS.

PART I DEMOLITION, EXCAVATION AND REMOVALS

Part Ia – Architectural Works Not Applicable

Part Ib – Structural Works Not Applicable

Part Ic – Civil Works

Part Id – Mechanical Works

Part Ie – Electrical Works

PART II ARCHITECTURAL, STRUCTURAL AND CIVIL WORKS

Part IIa – Architectural Works

Part IIb – Structural Works

Page | 3 of 60 ASHE 17-1019 REV 2 09 March 2018

Part IIc – Civil Works

PART III MECHANICAL WORKS

Part IIIa – HVAC System

• Replace HVAC control systems;

• Test and balance HVAC system,

• Generate as-built, declaration of conformity, test report and other documents;

PART IIIb - PLUMBING SYSTEM

PART IV ELECTRICAL WORKS

• Upgrade electrical system;

• Install variable frequency driver on HVAC AHU motors

• Supply and installation of SPD system and devices; existing lightning protection system and grounding systems will be tested in accordance with applicable norms;

• generate electrical as-built, declaration of conformity, test report and other documents;

TECHNICAL SPECIFICATION

Master specifications :

The following Sections of the Master Specifications for construction projects of the Air Base in Aviano (PN), Italy, dated November 2005 and applicable modifications, shall be applicable to the present project, together with the List of Work Items to be performed:

SECTION SECTION TITLE

01100 GENERAL CONDITIONS

15050 BASIC MECHANICAL MATERIALS AND METHODS

15080 INSULATION FOR MECHANICAL EQUIPMENT

15720 AIR HANDLING AND DISTRIBITION EQUIPMENT

01101 PROJECT SIGN

15950 HVAC TESTING/ADJUSTING/BALANCING

Page | 4 of 60 ASHE 17-1019 REV 2 09 March 2018

UFGS Specifications :

USACE / NAVFAC / AFCEC / NASA UFGS-23 09 23.13 20 (November 2015) Preparing Activity: NAVFAC Superseding UFGS-23 09 23.13 20 (August 2009)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated October 2016

SECTION TABLE OF CONTENTS

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

SECTION 23 09 23.13 20

BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC 11/15

PART 1 GENERAL

1.1 REFERENCES

1.2 DEFINITIONS

1.2.1 ANSI/ASHRAE Standard 135

1.2.2 ARCNET

1.2.3 BACnet

1.2.4 BACnet Building Controller (B-BC)

1.2.5 BACnet/IP

1.2.6 BACnet Internetwork

1.2.7 BACnet Network

1.2.8 BACnet Segment

1.2.9 BBMD

1.2.10 BAS

1.2.11 BAS Owner

1.2.12 BIBBs

1.2.13 BI

1.2.14 BI/BTL

1.2.15 Bridge

1.2.16 Broadcast

1.2.17 Device

1.2.18 Device Object

1.2.19 Device Profile

1.2.20 Digital Controller

1.2.21 Direct Digital Control (DDC)

1.2.22 DDC System

1.2.23 Ethernet

1.2.24 Firmware

1.2.25 Middleware

1.2.26 Half Router

1.2.27 Hub

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

1.2.29 Input/Output (I/O)

1.2.30 I/O Expansion Unit

1.2.31 IP subnet

1.2.32 Local-Area Network (LAN)

1.2.33 LonTalk

Page | 5 of 60 ASHE 17-1019 REV 2 09 March 2018

1.2.34 MAC Address

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

1.2.36 Native BACnet Device

1.2.37 Network

1.2.38 Network Number

1.2.39 Object

1.2.40 Object Identifier

1.2.41 Object Properties

1.2.42 Peer-to-Peer

1.2.43 Performance Verification Test (PVT)

1.2.44 PID

1.2.45 PICS

1.2.46 Points

1.2.47 PTP

1.2.48 Repeater

1.2.49 Router/Protocol Gateway

1.2.50 Stand-Alone Control

1.3 SUBCONTRACTOR SPECIAL REQUIREMENTS

1.4 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC DESCRIPTION

1.4.1 Design Requirements

1.4.1.1 Control System Drawings Title Sheet

1.4.1.2 List of I/O Points

1.4.1.3 Control System Components List

1.4.1.4 Control System Schematics

1.4.1.5 HVAC Equipment Electrical Ladder Diagrams

1.4.1.6 Component Wiring Diagrams

1.4.1.7 Terminal Strip Diagrams

1.4.1.8 BACnet Communication Architecture Schematic

1.5 SUBMITTALS

1.6 QUALITY ASSURANCE

1.6.1 Standard Products

1.6.2 Delivery, Storage, and Handling

1.6.3 Operating Environment

1.6.4 Finish of New Equipment

1.6.5 Verification of Dimensions

1.6.6 Contractor's Qualifications

1.6.7 Modification of References

1.6.8 Project Sequence

PART 2 PRODUCTS

2.1 DDC SYSTEM

2.1.1 BACnet Building Controller (B-BC)

2.1.2 Direct Digital Controllers

2.1.2.1 I/O Point Limitation

2.1.2.2 Environmental Limits

2.1.2.3 Stand-Alone Controllers

2.1.2.4 Internal Clock

2.1.2.5 Memory

2.1.2.6 Immunity to Power Fluctuations

2.1.2.7 Transformer

2.1.2.8 Wiring Terminations

2.1.2.9 Input and Output Interface

Page | 6 of 60 ASHE 17-1019 REV 2 09 March 2018

2.1.2.10 Digital Controller BACnet Internetwork

2.1.2.11 Communications Ports

2.1.2.12 BACnet Gateways

2.1.2.13 Digital Controller Cabinet

2.1.2.14 Main Power Switch and Receptacle

2.1.3 DDC Software

2.1.3.1 Programming

2.1.3.2 Parameter Modification

2.1.3.3 Short Cycling Prevention

2.1.3.4 Equipment Status Delay

2.1.3.5 Run Time Accumulation

2.1.3.6 Timed Local Override

2.1.3.7 Time Synchronization

2.1.3.8 Scheduling

2.1.3.9 Object Property Override

2.1.3.10 Alarms and Events

2.1.3.11 Trending

2.1.3.12 Device Diagnostics

2.1.3.13 Device Management

2.1.3.14 Power Loss

2.1.4 BACnet Operator Workstation

2.1.4.1 BACnet Operator Workstation Hardware

2.1.5 Notebook Computer

2.1.6 Notebook Computer Software

2.1.6.1 Password Protection

2.1.6.2 Notebook Computer DDC

Software

2.1.6.3 Web-Based User Interface (UI) and Graphics

2.1.7 BACnet Discovery Tool

2.2 SENSORS AND INPUT HARDWARE

2.2.1 Field-Installed Temperature Sensors

2.2.1.1 Thermistors

2.2.1.2 Resistance Temperature Detectors (RTDs)

2.2.1.3 Temperature Sensor Details

2.2.2 Transmitters

2.2.2.1 Relative Humidity Transmitters

2.2.2.2 Pressure Transmitters

2.2.3 Current Transducers

2.2.4 Pneumatic to Electric Transducers

2.2.5 Air Quality Sensors

2.2.5.1 CO2 Sensors

2.2.5.2 Air Quality Sensors

2.2.6 Input Switches

2.2.6.1 Timed Local Overrides

2.2.7 Freeze Protection Thermostats

2.2.8 Air Flow Measurement Stations

2.2.9 Energy Metering

2.2.9.1 Steam Meters

2.2.9.2 Gas Meters

2.2.9.3 Water Meters

2.3 OUTPUT HARDWARE

Page | 7 of 60 ASHE 17-1019 REV 2 09 March 2018

2.3.1 Control Dampers

2.3.2 Control Valves

2.3.2.1 Valve Assembly

2.3.2.2 Butterfly Valves

2.3.2.3 Two-Way Valves

2.3.2.4 Three-Way Valves

2.3.2.5 Valves for Chilled Water, Condenser Water, and Glycol Fluid Service

2.3.2.6 Valves for Hot Water Service

2.3.2.7 Valves for High Temperature Hot Water Service

2.3.2.8 Pressure independent control/balancing valve

2.3.3 Actuators

2.3.3.1 Electric Actuators

2.3.3.2 Pneumatic Actuators

2.3.4 Output Signal Conversion

2.3.4.1 Electronic-to-Pneumatic Transducers

2.3.5 Output Switches

2.3.5.1 Control Relays

2.4 ELECTRICAL POWER AND DISTRIBUTION

2.4.1 Transformers

2.4.2 Surge and Transient Protection

2.4.2.1 Power Line Surge Protection

2.4.2.2 Telephone and Communication Line Surge Protection

2.4.2.3 Controller Input/Output Protection

2.4.3 Wiring

2.4.3.1 Power Wiring

2.4.3.2 Analog Signal Wiring

2.5 FIRE PROTECTION DEVICES

2.5.1 Duct Smoke Detectors

2.6 INDICATORS

2.6.1 Thermometers

2.6.2 Pressure Gauges for Piping Systems

2.6.3 Pressure Gauges for Pneumatic Controls

2.7 PNEUMATIC POWER SUPPLY AND TUBING

2.8 VARIABLE FREQUENCY (MOTOR) DRIVES

2.8.1 VFD Quality Assurance

2.8.2 VFD Service Support

2.8.3 VFD Features

2.8.4 Programmable Parameters

2.8.5 Protective Features

2.8.6 Minimum Operating Conditions

2.8.7 Additional Features

PART 3 EXECUTION

3.1 INSTALLATION

3.1.1 BACnet Naming and Addressing

3.1.2 Minimum BACnet Object Requirements

3.1.3 Minimum BACnet Service Requirements

3.1.4 Local Area Networks

3.1.5 BACnet Routers and Protocol Gateways

3.1.6 Wiring Criteria

3.1.7 Accessibility

Page | 8 of 60 ASHE 17-1019 REV 2 09 March 2018

3.1.8 Digital Controllers

3.1.9 Hand-Off-Auto Switches

3.1.10 Temperature Sensors

3.1.10.1 Room Temperature Sensors

3.1.10.2 Duct Temperature Sensors

3.1.10.3 Immersion Temperature Sensors

3.1.10.4 Outside Air Temperature Sensors

3.1.11 Energy Meters

3.1.12 Damper Actuators

3.1.13 Thermometers and Gages

3.1.14 Pressure Sensors

3.1.15 Pneumatic Tubing

3.1.16 Component Identification Labeling

3.1.17 Network and Telephone Communication Lines

3.2 TEST AND BALANCE SUPPORT

3.3 CONTROLS SYSTEM OPERATORS MANUALS

3.3.1 Storage Cabinets

3.4 PERFORMANCE VERIFICATION TESTING (PVT)

3.4.1 General

3.4.2 Performance Verification Testing Plan

3.4.3 PVT Sample Size

3.4.4 Pre-Performance Verification Testing Checklist

3.4.5 Conducting Performance Verification Testing

3.4.6 Controller Capability and Labeling

3.4.7 Workstation and Software Operation

3.4.8 BACnet Communications and Interoperability Areas

3.4.9 Execution of Sequence of Operation

3.4.10 Control Loop Stability and Accuracy

3.4.11 Performance Verification Testing Report

3.5 TRAINING REQUIREMENTS

3.5.1 Training Documentation

3.5.2 Phase I Training - Fundamentals

3.5.3 Phase II Training – Operation

PART 4 WARRANTY

4.1 Warranty Tags

4.2 Warranty Management Plan

-- End of Section Table of Contents -- USACE / NAVFAC / AFCEC / NASA UFGS-23 09 23.13 20 (November 2015) Preparing Activity: NAVFAC Superseding UFGS-23 09 23.13 20 (August 2009)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated October 2016

SECTION 23 09 23.13 20

BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC 11/15

PART 1 GENERAL

1.1 REFERENCES

Page | 9 of 60 ASHE 17-1019 REV 2 09 March 2018

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.

ASHRAE 135 (2016; INT 1 2016) BACnet—A Data Communication Protocol for Building Automation and Control Networks ASHRAE 135.1 (2014; ADD O) Method of Test for Conformance to BACnet

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

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

1.2.3 BACnet

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

1.2.4 BACnet Building Controller (B-BC)

ASHRAE 135 building controller that is the main interface for the building control system.

1.2.5 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.6 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.7 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.8 BACnet Segment

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

1.2.9 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.10 BAS

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

Page | 10 of 60 ASHE 17-1019 REV 2 09 March 2018

1.2.11 BAS Owner

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

1.2.12 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.13 BI

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

1.2.14 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.15 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.16 Broadcast

A message sent to all devices on a network segment.

1.2.17 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.18 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.19 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.20 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.2.21 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.22 DDC System

Page | 11 of 60 ASHE 17-1019 REV 2 09 March 2018

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

Communication hardware and software connecting two or more different protocols, similar to human language translators. The Middleware translates one protocol into equivalent concepts for the other protocol.

In BACnet applications, a middleware has BACnet on one side and non-BACnet protocols on the other side.

1.2.26 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.27 Hub

A common connection point for devices on a network.

1.2.28 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.29 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.30 I/O Expansion Unit

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

1.2.31 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.32 Local-Area Network (LAN)

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

1.2.33 LonTalk

CEA-709.1-D. A communication protocol developed by Echelon Corp. LonTalk is an optional physical and data link layer for BACnet.

1.2.34 MAC Address

Media Access Control address. The physical node address that identifies a

Page | 12 of 60 ASHE 17-1019 REV 2 09 March 2018 device on a Local Area Network.

1.2.35 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.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.2.37 Network

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

1.2.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.2.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.2.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.2.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.

1.2.42 Peer-to-Peer

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

1.2.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. Typically the PVT is performed by the Contractor in the presence of the Government.

1.2.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.2.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.2.46 Points

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

1.2.47 PTP

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

Page | 13 of 60 ASHE 17-1019 REV 2 09 March 2018

1.2.48 Repeater

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

1.2.49 Router/Protocol Gateway

A BACnet router is a component that joins together two or more networks using different LAN technologies and protocols. Examples include joining a BACnet RS485 field bus (serial network) to an IP or Ethernet network..

In the above case the protocol gateway encapsulates BACnet data from the field bus within UDP headers for transport over IP

1.2.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. 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.3 SUBCONTRACTOR SPECIAL REQUIREMENTS.

Not applicable.

1.4 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC DESCRIPTION

a. Remove existing and provide new DDC systems including associated equipment and accessories.

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 UNI standadards.

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.

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. Typical schedules for multiple identical equipment are allowed unless otherwise requested in design or contract

Page | 14 of 60 ASHE 17-1019 REV 2 09 March 2018 criteria.

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, and physical location (e.g. Building 4, room 112 overhead). 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

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

1.4.1.5 HVAC Equipment Electrical Ladder Diagrams

Provide HVAC equipment electrical ladder diagrams. Indicate required electrical interlocks.

SECTION 23 09 23.13 20

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

Provide a schematic showing the project's entire BACnet communication network, 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. If applicable, show connection to existing networks.

1.5 SUBMITTALS

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

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only.

Page | 15 of 60 ASHE 17-1019 REV 2 09 March 2018

SD-02 Shop Drawings Include the following in the project's control system drawing set:

Control System Drawings Title Sheet; G List of I/O Points; G Control System Components List; G Control System Schematics; G HVAC Equipment Electrical Ladder Diagrams; G Component Wiring Diagrams; G Terminal Strip Diagrams; G BACnet Communication Architecture Schematic; G SD-03 Product Data Direct Digital Controllers; G Include BACnet PICS for each controller/device type, including smart sensors (B-SS) and smart actuators (B-SA).

BACnet Gateways; G Include BACnet and workstation display information;

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

BACnet Discovery Tool; G BACnet Operator Notebook Computer Software; G BACnet Operator Notebook Computer; G Include BACnet PICS for Operator Operator Notebook software.

Sensors and Input Hardware; G Output Hardware; G Surge and Transient Protection; G Indicators; G Variable Frequency (Motor) Drives; G SD-05 Design Data Performance Verification Testing Plan; G Pre-Performance Verification Testing Checklist; G SD-06 Test Reports Performance Verification Testing Report; G SD-07 Certificates Contractor's Qualifications; Not Applicable SD-09 Manufacturer's Field Reports Pre-PVT Checklist; G SD-10 Operation and Maintenance Data Comply with requirements for data packages in Section 01 78 23 OPERATION AND MAINTENANCE DATA, except as supplemented and modified in this specification.

BACnet Direct Digital Control Systems, Data Package 4; G Controls System Operators Manuals, Data Package 4; G VFD Service Manuals, Data Package 4; G SD-11 Closeout Submittals Training Documentation; G

1.6 QUALITY ASSURANCE

1.6.1 Standard Products

Provide material and equipment that are standard manufacturer's products

Page | 16 of 60 ASHE 17-1019 REV 2 09 March 2018 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 3.175 mm

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.

1.6.7 Modification of References

Not applicable

1.6.8 Project Sequence

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

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

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

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

AND BALANCE SUPPORT.

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

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

PERFORMANCE VERIFICATION TESTING.

f. Perform the Performance Verification Testing.

g. Submit and receive approval on the PVT Report.

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

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

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

k. Conduct the Phase II Training.

Page | 17 of 60 ASHE 17-1019 REV 2 09 March 2018

l. Submit and receive approval of Closeout Submittals.

PART 2 PRODUCTS

2.1 DDC SYSTEM

NOTE: Consider below whether to require integral, or factory-provided ("Native") BACnet controllers for HVAC and plant equipment. If so, coordinate this requirement with other sections and specifications for plant equipment. This allows eliminating redundant sensor/actuator requirements and provides access to many control and status parameters using BACnet with a single LAN connection to the equipment. Possible disadvantages include higher cost, disqualifying otherwise qualified vendors, and more detailed integration criteria.

NOTE: A current list of BTL certified devices are published at: http:/www.bacnetassociation.org/btl/.

Coordinate with this list to determine what devices must be BTL certified (last sentence in 2.1.a).

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

b. Provide an operator workstation and new server with complete interface software capable of programming, configuring, and monitoring the digital controllers, including graphic creation, scheduling, alarming, and trending. The server and workstation are located at the same facility as the the HVAC system.

2.1.1 BACnet Building Controller (B-BC)

ASHRAE 135 building controller that is the main interface for the building control system. New equipment finishing shall be factory provided.

2.1.2 Direct Digital Controllers

Direct digital controllers shall be CE marked.

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

2.1.2.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.2.3 Stand-Alone Controllers

Provide stand-alone direct digital controllers with internal time clocks.

Page | 18 of 60 ASHE 17-1019 REV 2 09 March 2018

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.2.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 (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.2.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.2.6 Immunity to Power Fluctuations

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

2.1.2.7 Transformer

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

2.1.2.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.2.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 have a toggle switch and monitor on and off contacts from a "dry" remote device without external power, and external 5-24 VDC voltage inputs.

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

Page | 19 of 60 ASHE 17-1019 REV 2 09 March 2018 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 have a toggle switch and send a pulsed 24 VDC low-voltage signal for modulation control, or provide a maintained open-closed position for on-off control. For HVAC equipment and plant controllers, provide for manual overrides, either with three-position (on-off-auto) override switches and status lights, or with an adjacent operator display and interface. 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.2.10 Digital Controller BACnet Internetwork

Provide a BACnet internetwork with control products, communication media, connectors, repeaters, hubs, and routers. 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.2.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.

b. BACnet routers supporting ARCnet shall also be capable of supporting

MS/TP.

2.1.2.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 Use gateway interoperability schedules shown on design drawings or other project documents, 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. Middleware 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.

b. Middleware shall be able to write to all writeable object properties

Page | 20 of 60 ASHE 17-1019 REV 2 09 March 2018 listed in the interoperability schedule on the non-BACnet network from the BACnet network and vice versa where applicable.

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

d. Middleware 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. Middleware 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.2.13 Digital Controller Cabinet

Provide each digital controller in a factory fabricated cabinet enclosure.

Cabinet shall be locked and alarmed. The alarm shall include both a local audible alarm and a networked alarm (e.g. switch connected to controller DI). Networked alarm events shall be recorded remotely for a period not less than one year.

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

2.1.2.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 receptacle.

2.1.3 DDC Software

2.1.3.1 Programming

Provide programming to execute the sequence of operation indicated.

Provide all programming and tools to configure and program all controllers. Provide programming routines in simple, easy-to-follow logic with detailed text comments describing what the logic does and how it corresponds to the project's written sequence of operation. All logic programming and control functions shall be closed loop, command and feedback for fault detection and alarming when status != command.

Programming shall be Graphic-based and 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

Page | 21 of 60 ASHE 17-1019 REV 2 09 March 2018 each function block.

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

c. Provide 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.3.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.3.3 Short Cycling Prevention

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

2.1.3.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.3.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.3.6 Timed Local Override

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

2.1.3.7 Time Synchronization

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

2.1.3.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.3.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.3.10 Alarms and Events

Alarms and events shall be capable of having programmed time delays and high-low limits. When a computer workstation or web server is connected to the BACnet internetwork, alarms/events shall report to the computer, . Otherwise alarms/events shall be stored within a device on the BACnet network until connected to a user interface device and

Page | 22 of 60 ASHE 17-1019 REV 2 09 March 2018 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.3.11 Trending

Provide BACnet trend services capable of trending all object present values set points, and other parameters indicated for trending on project schedules. Trends may be associated into groups, and a trend report may be set up for each group. Trends are stored within a device on the BACnet network, with operator selectable trend intervals from 10 seconds up to 60 minutes. 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 operator workstation 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.

2.1.3.12 Device Diagnostics

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

2.1.3.13 Device Management

System shall be capable of managing devices remotely to include updating/loading firmware, restarting, and network configuration. These capabilities shall be restricted to authorized roles. The system shall support, either natively or with provided add-on software, remote read/write and management of BBMD tables.

2.1.3.14 Power Loss

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

2.1.4 BACnet Operator Workstation (Notebook Computer)

The workstation shall be capable of accessing all DDC system devices and communicate using the BACnet protocol. The workstation shall be capable of displaying, modifying, creating, archiving, and deleting (as applicable):

all points, objects, object properties, programming, alarms, trends, messages, schedules, and reports. For software, see the paragraph BACnet Operator Workstation Software.

2.1.4.1…