23_09_23_13_20_Spec_Amended.pdf

REPLACE HVAC BLDG 129 FTFA 03-1231

SECTION 23 09 23.13 20

BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC 08/09

PART 1 GENERAL

1.1 REFERENCES

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

AIR MOVEMENT AND CONTROL ASSOCIATION INTERNATIONAL (AMCA)

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

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (Errata 1 2013; INT 1-9 2013; Errata 2 2013; INT 10-12 2014; Errata 3-4 2014;

Addenda AI-AY 2014; Addenda O 2014) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ARCNET TRADE ASSOCIATION (ATA)

ATA 878.1 (1999) Local Area Network: Token Bus

ASME INTERNATIONAL (ASME)

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

NPS 1/2 Through NPS 24 Metric/Inch Standard

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

ASME B40.100 (2013) Pressure Gauges and Gauge Attachments

ASTM INTERNATIONAL (ASTM)

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

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

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-C (2010) Control Network Protocol Specification

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE C62.41.1 (2002; R 2008) Guide on the Surges

SECTION 23 09 23.13 20 Page 1

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 (1000v and less)AC Power Circuits

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

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

NFPA 72 (2013) National Fire Alarm and Signaling Code

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

SHEET METAL AND AIR CONDITIONING CONTRACTORS' NATIONAL ASSOCIATION

(SMACNA)

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

UNDERWRITERS LABORATORIES (UL)

UL 1449 (2014) Surge Protective Devices

UL 506 (2008; Reprint Oct 2013) Specialty Transformers

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

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

SECTION 23 09 23.13 20 Page 2

1.2 DEFINITIONS

1.2.1 ANSI/ASHRAE Standard 135

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

1.2.2 ARCNET

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

1.2.3 BACnet

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

1.2.4 BACnet/IP

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

1.2.5 BACnet Internetwork

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

1.2.6 BACnet Network

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

1.2.7 BACnet Segment

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

1.2.8 BBMD

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

1.2.9 BAS

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

SECTION 23 09 23.13 20 Page 3

1.2.10 BAS Owner

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

1.2.11 BIBBs

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

1.2.12 BI

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

1.2.13 BI/BTL

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

1.2.14 Bridge

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

1.2.15 Broadcast

A message sent to all devices on a network segment.

1.2.16 Device

Any control system component, usually a digital controller, that contains a BACnet Device Object and uses BACnet to communicate with other devices.

See also "Digital Controller".

1.2.17 Device Object

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

This number is often referred to as the device instance.

1.2.18 Device Profile

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

SECTION 23 09 23.13 20 Page 4

1.2.19 Digital Controller

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

1.2.20 Direct Digital Control (DDC)

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

1.2.21 DDC System

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

1.2.22 Ethernet

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

1.2.23 Firmware

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

1.2.24 Gateway

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

1.2.25 Half Router

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

1.2.26 Hub

A common connection point for devices on a network.

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

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

SECTION 23 09 23.13 20 Page 5

1.2.28 Input/Output (I/O)

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

1.2.29 I/O Expansion Unit

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

1.2.30 IP subnet

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

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

1.2.31 Local-Area Network (LAN)

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

1.2.32 LonTalk

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

1.2.33 MAC Address

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

1.2.34 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.35 Native BACnet Device

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

1.2.36 Network

Communication technology for data communications. BACnet approved network type is MS/TP.

1.2.37 Network Number

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

SECTION 23 09 23.13 20 Page 6

1.2.38 Object

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

1.2.39 Object Identifier

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

1.2.40 Object Properties

Attributes of an object. Examples include present value and high limit properties of an analog input object. Properties are defined in ASHRAE 135;

some are optional and some are required. Objects are controlled by reading from and writing to object properties.

1.2.41 Peer-to-Peer

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

1.2.42 Performance Verification Test (PVT)

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

1.2.43 PID

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

1.2.44 PICS

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

1.2.45 Points

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

1.2.46 PTP

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

1.2.47 Repeater

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

1.2.48 Router

A BACnet router is a component that joins together two or more networks

SECTION 23 09 23.13 20 Page 7 using different LAN technologies. Examples include joining a BACnet Ethernet LAN to a BACnet MS/TP LAN.

1.2.49 Stand-Alone Control

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

1.3 SUBCONTRACTOR SPECIAL REQUIREMENTS

All contract requirements of this section shall be accomplished directly by a first tier subcontractor. No work required shall be accomplished by a second tier subcontractor.

1.4 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC DESCRIPTION

a. Remove existing and provide new BACnet DDC systems including associated equipment and accessories as indicated on the mechanical controls drawings with the following exception: Niagara AX Framework shall be no later than Revision 3.6.47.9. 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.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 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, SECTION 23 09 23.13 20 Page 8 manufacturer, and manufacturer part number. 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.

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 addressing used for LANs, LAN devices including routers and bridges, gateways, controllers, workstations, and field interface devices.

1.5 SUBMITTALS

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

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

SECTION 23 09 23.13 20 Page 9 submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following according to 01 33 00 SUBMITTAL PROCEDURES:

SD-02 Shop Drawings

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

Control system drawings title sheet; 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 Protocol Analyzer; G

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

DDC Software; G

BACnet Operator Workstation; G

BACnet Operator Workstation DDC Software; G

Include BACnet PICS for Operator Workstation software.

Notebook Computer; G

Sensors and Input Hardware; G

Output Hardware; G

SECTION 23 09 23.13 20 Page 10

Surge and transient protection; G

Indicators; G

Duct smoke detectors; 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; G

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 00 CLOSEOUT SUBMITTALS, 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 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

SECTION 23 09 23.13 20 Page 11 within the manufacturer's limits.

1.6.4 Finish of New Equipment

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

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

1.6.5 Verification of Dimensions

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

1.6.6 Contractor's Qualifications

Submit documentation certifying the controls Contractor performing the work has completed at least three DDC systems installations of a similar design to this project, and programmed similar sequences of operation for at least two years.

1.6.7 Modification of References

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

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

1.6.8 Project Sequence

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

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

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

SECTION 23 09 23.13 20 Page 12 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.

l. Submit and receive approval of Closeout Submittals.

PART 2 PRODUCTS

2.1 DDC SYSTEM

a. Provide an operator workstation with complete interface software capable of programming, configuring, and monitoring the digital controllers.

Interface the new DDC system with Eglin AFB EMCS. Coordinate with Base Comm.

2.1.1 Direct Digital Controllers

Direct digital controllers shall be UL 916 rated.

2.1.1.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.1.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.1.3 Stand-Alone Control

Provide stand-alone digital controllers.

2.1.1.4 Internal Clock

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

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

SECTION 23 09 23.13 20 Page 13

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

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

2.1.1.7 Transformer

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

2.1.1.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.1.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 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.1.10 Digital Controller BACnet Internetwork

Provide a BACnet internetwork with control products, communication media, SECTION 23 09 23.13 20 Page 14 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.1.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. Telecommunications Interface Port: Provide one telecommunication port per building, permitting remote communication via point-to-point (PTP) protocol over telephone lines.

2.1.1.12 Modems

Provide modems where required for communication between the BACnet Operator Workstation (B-OWS) and the DDC system.

2.1.1.13 BACnet Gateways

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

Typical BACnet controlled plant equipment includes, but is not limited to, boilers, chillers, and variable frequency motor drives.

Provide gateways to connect BACnet to legacy systems, existing non-BACnet devices, and existing non-BACnet DDC controlled plant equipment, only when specifically requested and approved by the Government, and shown on the Government approved BACnet Communication Architecture Schematic. Provide with each gateway an interoperability schedule, showing each point or event on the legacy side that the BACnet "client" will read, and each parameter that the BACnet network will write to. Describe this interoperability in terms of BACnet services, or Interoperability Building Blocks (BIBBS), defined in ASHRAE 135 Annex K. Provide two-year minimum warranty for each gateway, including parts and labor.

The following minimum capabilities are required:

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

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

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

d. Gateways shall meet the requirements of Data Sharing Read Property (DS-RP-B), Data Sharing Write Property (DS-WP-B), Device Management Dynamic Device Binding-B (DM-DDB-B), and Device Management

SECTION 23 09 23.13 20 Page 15

Communication Control (DM-DCC-B) BIBBs, in accordance with ASHRAE 135.

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

2.1.1.14 Digital Controller Cabinet

Provide each digital controller in a factory fabricated cabinet enclosure.

Cabinets located indoors shall protect against dust and have a minimum NEMA 1 rating, except where indicated otherwise. Cabinets located outdoors or in damp environments shall protect against all outdoor conditions and have a minimum NEMA 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.1.15 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.2 DDC Software

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

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

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

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

Use descriptive comments frequently to describe the programming.

d. If providing a computer with device programming tools as part of the project, provide a means for detecting program errors and testing software strategies with a simulation tool. Simulation may be inherent within the programming software suite, or provided by physical

SECTION 23 09 23.13 20 Page 16 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.2.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.2.3 Short Cycling Prevention

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

2.1.2.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.2.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.2.6 Timed Local Override

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

2.1.2.7 Time Synchronization

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

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

SECTION 23 09 23.13 20 Page 17 the BACnet internetwork, alarms/events shall report to the computer, printer, e-mail or cell phone, as defined by an authorized operator.

Otherwise alarms/events shall be stored within a device on the BACnet network until connected to a user interface device and retrieved. Provide alarms/events in agreement with the point schedule, sequence of operation, and the BAS Owner. At a minimum, provide programming to initiate alarms/events any time a piece of equipment fails to operate, a control point is outside normal range or condition shown on schedules, communication to a device is lost, a device has failed, or a controller has lost its memory.

2.1.2.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 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.2.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.2.13 Power Loss

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

2.1.3 BACnet Operator Workstation

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.

2.1.3.1 BACnet Operator Workstation Hardware

Configure according to system manufacturer's specifications and conforming to BACnet Operator Workstation (B-OWS) device standards found in ASHRAE 135, Annex L. Install to permit complete monitoring and troubleshooting of the DDC system.

At a minimum the workstation hardware shall include: a desktop personal computer with Microsoft Windows XP or VISTA Professional operating system or equal, processor and RAM exceeding capability and speed required by operating system and application software, hard drive capacity exceeding software and yearly archive requirements, 16X internal DVD+/-R/RW/CD-RW

SECTION 23 09 23.13 20 Page 18 drive with archive creator software, 4 USB 2.0 ports, 10/100 network interface card, 19-inch LCD monitor, internal V.92 modem, sound card with speakers, 101 character keyboard, optical mouse, USB Hub with four USB 2.0 ports and connecting cable, laser printer with USB port and cable, 3 matching color and black ink cartridges, 120-volt 800 VA uninterruptible power supply with automatic voltage regulation and 4 minimum battery back-up outlets and 2 surge protected outlets. Provide all original licenses, installation media, documentation, and recovery CDs capable of restoring the original configuration. Provide a manufacturer's 3-year next business day on-site warranty with the Government listed as the warranty owner.

2.1.3.2 Password Protection

Provide at least five levels of password protection for operator interfaces. The lowest level only allow viewing graphics. The second level allows viewing graphics and changing space temperature setpoints.

The third level allows the previous level's capability, plus changing operating schedules. The fourth level allows access to all functions except passwords. The highest level provides all administrator rights and allows full access to all programming, including setting new passwords and access levels. Provide the BAS Owner with the highest level password access. Provide automatic log out if no keyboard or mouse activity is detected after a user-defined time delay.

2.1.3.3 BACnet Operator Workstation DDC Software

Provide the workstation software with the manufacturer's installation CDs and licenses. Configure the software according to the DDC system manufacturer's specifications and in agreement with BACnet Operator Workstation (B-OWS) device standards found in ASHRAE 135, Annex L.

The workstation software shall permit complete monitoring, modification, and troubleshooting interface with the DDC system. The operator interface with the software shall be menu-driven with appropriate displays and menu commands to manipulate the DDC system's objects, point data, operating schedules, control routines, system configuration, trends, alarms, messages, graphics, and reports. Trends shall be capable of graphic display in real time, with variables plotted as functions of time. Each alarmed point shall be capable of displaying its alarm history, showing when it went into alarm, if and when it was acknowledged, and when it went out of alarm. The modification of DDC system parameters and object properties shall be accomplished with "fill in the blank" and/or "point and drag" methods. Modifications shall download to the appropriate controllers at the operator's request.

2.1.3.4 Graphics Software

Provide web-based system graphics viewable on browsers compatible with MS Internet Explorer 6.X or greater using an industry-standard file format such as HTML, BMP, JPEG, or GIF.

Graphic displays shall have full-screen resolution when viewed on the workstation and notebook computers. Dynamic data on graphics pages shall refresh within 10 seconds using an Internet connection, or 30 seconds using a dial-up modem connection. Graphics viewing shall not require additional "plug-in" software like Java, Shockwave and Flash applications unless the software is readily available for free over the Internet, and certified for use with Navy Marine Corps Internet (NMCI) personal computers.

SECTION 23 09 23.13 20 Page 19

The graphics shall show the present value and object name for each of the project's I/O points on at least one graphic page. Arrange point values and names on the graphic displays in their appropriate physical locations with respect to the floor plan or equipment graphic displayed. Graphics shall allow the operator to monitor current status, view zone and equipment summaries, use point-and-click navigation between graphic pages, and edit setpoints and parameters directly from the screens. Items in alarm shall be displayed using a different color or other obvious visual indicator.

Provide graphics with the following:

a. Graphic Types: Provide at least one graphic display for each piece of HVAC equipment, building floor, and controlled zone. Indicate dynamic point values, operating statuses, alarm conditions, and control setpoints on each display. Provide summary pages where appropriate.

(1) Building Elevation: For buildings more than one story, provide an elevation view of the building with links to each of the building's floor plans. Simulate the building's architecture and include the building number and floor numbers. If possible, use an actual photograph of the building.

(2) Building Floor Plans: Provide a floor plan graphic for each of the building's floors with dynamic display of space temperature and other important data. If used, indicate and provide links to sub-plan areas. If possible, use the project's electronic drawing files for the graphic backgrounds. Provide clear names for important areas, such as "Main Conference Room." Include room names and numbers where applicable. Include features such as stairwells, elevators, and main entrances. Where applicable, include the mechanical room, HVAC equipment, and control component locations, with corresponding links to the equipment graphics.

(3) Sub-plan Areas: Where a building's floor plan is too large to adequately display on the screen, sub-divide the plan into distinct areas, and provide a separate graphic display for each area. Provide same level of detail requested in building floor plan section above.

(4) HVAC Equipment: Provide a graphic display for each piece of HVAC equipment, such as a fan coil unit, VAV terminal, or air handling unit. Equipment shall be represented by a two or three-dimensional drawing. Where multiple pieces of equipment combine to form a system, such as a central chiller plant or central heating plant, provide one graphic to depict the entire plant. Indicate the equipment, piping, ductwork, dampers, and control valves in the installed location. Include labels for equipment, piping, ductwork, dampers, and control valves. Show the direction of air and water flow. Include dynamic display of applicable object data with clear names in appropriate locations.

(5) Sequence of Operation: Provide a graphic screen displaying the written out full sequence of operation for each piece of HVAC equipment. Provide a link to the sequence of operation displays on their respective equipment graphics. Include dynamic real-time data within the text for setpoints and variables.

b. Graphic Title: Provide a prominent, descriptive title on each graphic page.

SECTION 23 09 23.13 20 Page 20

c. Dynamic Update: When the workstation is on-line, all graphic I/O object values shall update with change-of-value services, or by operator selected discrete intervals.

d. Graphic Linking: Provide forward and backward linking between floor plans, sub-plans, and equipment.

e. Graphic Editing: Provide installed software to create, modify, and delete the DDC graphics. Include the ability to store graphic symbols in a symbol directory and import these symbols into the graphics.

f. Dynamic Point Editing: Provide full editing capability for deleting, adding, and modifying dynamic points on the graphics.

2.1.4 Notebook Computer

Provide a notebook computer, complete with the project's installed DDC software, applications database, and graphics to fully troubleshoot and program the project's devices. Notebook computers for web-based systems do not require this installed software if they have the ability to connect locally in real time, view all graphics, and fully troubleshoot, modify, and program all project devices. Provide the notebook computer with ballistic nylon carrying case with shoulder strap with all necessary cables and interface hardware needed for setup and communication with the controllers and control system components.

At a minimum the notebook computer shall include: a Microsoft XP Professional operating system, processor with capability and speed required by application software, 40 giga-byte hard drive, 512 mega-byte RAM, 2 USB

2.0 ports, 10/100 network interface card, internal V.92 modem, 15-inch display, keyboard, 3-hour battery with charger, 52X internal CD-RW drive with CD creator software. Provide all original licenses, installation media, documentation, and recovery CDs capable of restoring the original configuration. Provide the manufacturer's 3-year next business day on-site warranty with the Government listed as the warranty owner.

2.1.5 BACnet Protocol Analyzer

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

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

b. Measure bandwidth usage.

c. Filtering options with ability to ignore select traffic.

2.2 SENSORS AND INPUT HARDWARE

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

2.2.1 Field-Installed Temperature Sensors

Where feasible, provide the same sensor type throughout the project. Avoid using transmitters unless absolutely necessary.

SECTION 23 09 23.13 20 Page 21

2.2.1.1 Thermistors

Precision thermistors may be used in applications below 200 degrees F.

Sensor accuracy over the application range shall be 0.36 degree F or less between 32 to 150 degrees F. Stability error of the thermistor over five years shall not exceed 0.25 degrees F cumulative. A/D conversion resolution error shall be kept to 0.1 degrees F. Total error for a thermistor circuit shall not exceed 0.5 degrees F.

2.2.1.2 Resistance Temperature Detectors (RTDs)

Provide RTD sensors with platinum elements compatible with the digital controllers. Encapsulate sensors in epoxy, series 300 stainless steel, anodized aluminum, or copper. Temperature sensor accuracy shall be 0.1 percent (1 ohm) of expected ohms (1000 ohms) at 32 degrees F. Temperature sensor stability error over five years shall not exceed 0.25 degrees F cumulative. Direct connection of RTDs to digital controllers without transmitters is preferred. When RTDs are connected directly, lead resistance error shall be less than 0.25 degrees F. The total error for a RTD circuit shall not exceed 0.5 degrees F.

2.2.1.3 Temperature Sensor Details

a. Room Type: Provide the sensing element components within a decorative protective cover suitable for surrounding decor.

b. Duct Probe Type: Ensure the probe is long enough to properly sense the air stream temperature.

c. Duct Averaging Type: Continuous averaging sensors shall be one foot in length for each 4 square feet of duct cross-sectional area, and a minimum length of 6 feet.

d. Pipe Immersion Type: Provide minimum three-inch immersion. Provide each sensor with a corresponding pipe-mounted sensor well, unless indicated otherwise. Sensor wells shall be stainless steel when used in steel piping, and brass when used in copper piping. Provide the sensor well with a heat-sensitive transfer agent between the sensor and the well interior.

e. Outside Air Type: Provide the sensing element on the building's north side with a protective weather shade that positions the sensor approximately 3 inches off the wall surface, does not inhibit free air flow across the sensing element, and protects the sensor from snow, ice, and rain.

2.2.2 Transmitters

Provide transmitters with 4 to 20 mA or 0 to 10 VDC linear output scaled to the sensed input.