Appendix_C_-_BACnet_DDC_Specification.pdf

Page 1 of 56 Version Date: 21 May 2013

DISA Enterprise Services Directorate (ESD) Facilities Engineering Team (ES521)

MINIMUM TECHNICAL SPECIFICATIONS

FOR

BACnet DIRECT DIGITAL CONTROL SYSTEMS (DDC) FOR HVAC

1. GENERAL

All designers shall utilize this specification in conjunction with Division 25 (Integrated Automation) of CSI 360-95- 3 to create a specification for DDC installers. The designer shall read and understand the concept of operations for DISA building automation systems located in Division 25. The designer shall coordinate with all design disciplines.

When the project contract or statement of work requires that the DDC system be connected to an existing Iconics Genesis 32 system, the references in this document to Iconics Genesis 64 shall be substituted with Iconics Genesis 32.

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.

DEFENSE INFORMATION SYSTEMS AGENCY (DISA)

CSI 360-95-3 Enterprise Services Directorate Facilities Standards

Note: Where a Section or Division is referenced in this specification, the reference is to the current version of CSI 360-95-3.

UNITED FACILITIES GUIDE SPECIFICATION (UFGS)

23 09 23.13.20 (Aug 2009) BACnet Direct Digital Control Systems for HVAC

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 (2010; INT 1 2011; Addenda AD & AE 2011) 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.18 (2001; R 2012) Cast Copper Alloy Solder Joint Pressure Fittings

ASME B16.22 (2001; R 2010) Standard for Wrought Copper and Copper Alloy Solder Joint Pressure

Fittings

ASME B16.26 (2011) Standard for Cast Copper Alloy Fittings for Flared Copper Tubes

ASME B16.34 (2009; Supp 2010) Valves - Flanged, Threaded and Welding End

Page 2 of 56 Version Date: 21 May 2013

ASME B16.5 (2009) Pipe Flanges and Flanged Fittings: NPS 1/2 through NPS 24 Metric/Inch Standard

ASME B31.1 (2010) Power Piping

ASME B40.100 (2005; R 2010) Pressure Gauges and Gauge Attachments

ASME BPVC SET (2010) Boiler and Pressure Vessels Code

ASTM INTERNATIONAL (ASTM)

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

Fittings

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

ASTM B32 (2008) Standard Specification for Solder Metal

ASTM B75 (2011) Standard Specification for Seamless Copper Tube

ASTM B88 (2009) Standard Specification for Seamless Copper Water Tube

ASTM B88M (2005; R 2011) Standard Specification for Seamless Copper Water Tube (Metric)

ASTM D1238 (2010) Melt Flow Rates of Thermoplastics by Extrusion Plastometer

ASTM D1693 (2008) Standard Test Method for Environmental Stress-Cracking of Ethylene Plastics

ASTM D635 (2010) Standard Test Method for Rate of Burning and/or Extent and Time of Burning of

Self-Supporting Plastics in a Horizontal Position

ASTM D638 (2010) Standard Test Method for Tensile Properties of Plastics

ASTM D792 (2008) Density and Specific Gravity (Relative Density) of Plastics by Displacement

CONSUMER ELECTRONICS ASSOCIATION (CEA)

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

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE C57.13 (2008) Standard Requirements for Instrument Transformers

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

Power Circuits

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

Less) AC Power Circuits

IEEE C62.45 (2002; R 2008) Recommended Practice on Surge Testing for Equipment Connected to

Low-Voltage (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

Page 3 of 56 Version Date: 21 May 2013

Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

NEMA/ANSI C12.10 (2011) Physical Aspects of Watthour Meters - Safety Standards

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2011; TIA 11-1; Errata 2011; TIA 11-2; TIA 11-3; TIA 11-4) National Electrical Code

NFPA 72 (2010; TIA 10-4) National Fire Alarm and Signaling Code

NFPA 90A (2012) 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 (2006; Reprint Feb 2011) Surge Protective Devices

UL 506 (2008; Reprint Mar 2010) Specialty Transformers

UL 508A (2001; Reprint Feb 2010) Industrial Control Panels

UL 916 (2007; Reprint Jun 2010) Standard for Energy Management Equipment

1.2 DEFINITIONS

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.

ARCNET. ATA 878.1 - Attached Resource Computer Network. ARCNET is a deterministic LAN technology;

meaning it is possible to determine the maximum delay before a device is able to transmit a message.

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.

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

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.

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.

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

Page 4 of 56 Version Date: 21 May 2013

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

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

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 all DISA Enterprise Services Directorate projects is DISA Facilities Engineering ES521 and the local facility manager.

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.

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

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.

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.

Broadcast. A message sent to all devices on a network segment.

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

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.

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.

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

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.

Distributed Network Architecture. A network architecture in which multiple devices are located on the network, each having their own control logic and communicating with other devices in a peer-to-peer fashion. A failure of one of these devices or controllers shall not cause other devices on the network to fail. In the event of a network failure the controllers will continue to perform the programmed sequences of operation until network communication is restored.

Page 5 of 56 Version Date: 21 May 2013

DDC System. A network of digital controllers, communication architecture, and user interfaces. A DDC system with equipment monitoring, lighting controls systems, and life safety system monitoring used for facilities. A DDC system may include programming, sensors, actuators, switches, relays, factory controls, operator workstations, and various other devices, components, and attributes.

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

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.

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.

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.

Hub. A common connection point for devices on a network.

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.

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

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

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.

Local-Area Network (LAN). A communication network that spans a limited geographic area and uses the same basic communication technology throughout.

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

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

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

Native BACnet Device. A “native” BACnet device is a device that has been tested by the BACnet Testing Laboratories (BTL) and confirmed to adequately support ASHRAE standard 135. Please reference the BTL website for detailed device listings.

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

Page 6 of 56 Version Date: 21 May 2013

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.

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

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

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.

Peer-to-Peer. Peer-to-peer refers to devices on a common network or backbone that can initiate and respond to communication directly with another device without the need of a master or server device.

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.

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

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.

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

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

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

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

Stand-Alone Control. No networked DDC control, communication, or monitoring capabilities. Typically this consists of either simple/basic control sequences or simply hardwired interlocks between safeties on equipment.

Devices may or may not be located near controlled equipment.

1.3 SUBCONTRACTOR SPECIAL REQUIREMENTS

Not Used

1.4 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC DESCRIPTION

a. Approved Controller and Software Manufacturers.

Delta Controls V3.40 or latest hardware requirements.

Approved Sensor and Hardware Manufacturers are listed in the Sensor and Hardware section.

b. [Remove existing and] [provide new BACnet] [and] [modify existing] [and merge with existing non-BACnet] [and merge with existing BACnet] DDC systems including associated equipment and accessories. All new devices must communicate using ASHRAE 135 BACnet communications without the use of gateways, unless gateways are requested or approved by the Government. When gateways are allowed, they must support ASHRAE 135, including all object properties and read-write services shown on designer provided and Government approved interoperability schedules. Manufacturer's products, including design, materials, Page 7 of 56 Version Date: 21 May 2013 fabrication, assembly, inspection, and testing shall be in accordance with ASHRAE 135, ASME B31.1, and NFPA 70, except where indicated otherwise.

NOTE: The next paragraphs provide more specific information when merging or adding to an existing Delta Controls BACnet system.

c. When installing a new system, the installed system and components shall include the latest Delta

Firmware.

d. When modifying an existing Delta Controls DDC System, the upgrade shall include an upgrade of the existing system (all components) to the latest Delta Controls firmware and software versions.

e. When modifying a Delta Controls DDC System, the upgrade or expansion shall include replacement of any operator workstation that is older than 2 years old at the time of the project end date or does not comply with the workstation requirements outlined in this specification for the upgraded software required in section 1.4 d.

f. Provide a new workstation for all new installations when an existing workstation does not exist.

1.4.1 Design Requirements

All new work stations, controllers, devices, and components shall be listed by BACnet Testing laboratories (BTL), and shall communicate exclusively using the ASHRAE Standard 135 BACnet communications protocol without the use of gateways, unless otherwise allowed by this Section of the technical specifications, specifically shown on the design drawings.

When installing a new system or expanding an existing system, the new components of the system shall be of the most recent Delta Hardware Build, and shall communicate seamlessly with previous versions of Delta Controls Hardware. The contractor shall include in his pricing the cost to “flash” the existing previous Delta hardware versions with the latest firmware and software to match that of the latest hardware being installed.

The designer shall utilize this specification to develop a complete BAS design that incorporates the projects DDC requirements and necessary interfaces, graphics, and communication with the Iconics Genesis 64 system outlined in Division 25.

1.4.1.1 Control System Drawings

Drawings shall incorporate CSI 360-95-3 Record Drawing Configuration Management (CM) 01 78 39. Provide a control system drawing set. Include in the drawing set:

Provide complete control system drawings. All submitted drawings shall comply with the requirements of Section 01 78 39 and the Record Drawing Configuration Management (CM) Specification. The control system drawing set shall consist of the following:

Sheet Number Sheet Title M600 Title Sheet, Legend, Sheet Index

M601-M609 Network Architecture M610-M619 Floor Plans (BAS Components, Network Routing) M620-M629 DDC Points List, DDC Control Programs M630-M634 Chilled Water Systems M635-M639 Condenser Water Systems M640-M644 Hot Water Systems M645-M669 Air Distribution Systems (AHU, VAV, CRAH, CRAC et cetera) M670-M699 Monitoring of Electrical Systems, Points List, Programs MD600 – MD650 BAS System Demo/Removal

Page 8 of 56 Version Date: 21 May 2013

Project floor plan drawings shall annotate all DDC equipment locations and network wiring. Include locations of all workstations.

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 tag (read only, read write) 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 NOT permitted.

1.4.1.3 Control System Bill of Materials

Provide a complete list of control system components installed on this project. Include for each controller and device: Control system schematic name, control system schematic designation, device description, manufacturer, and manufacturer part number. 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. 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

Page 9 of 56 Version Date: 21 May 2013

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.

If applicable, show connection to existing networks.

1.4.1.9 Floor Plans

Not Used

1.4.1.10 Transformer Calculations

Provide calculations that demonstrate how each transformer being used in the DDC system was sized. The calculations shall show all load power requirements.

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.

1.5.1 Shop Drawings

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

• Control system drawings title sheet

• Floor Plan (BAS Equipment and BAS Network Routing)

• List of I/O Points

• Control System Components List

• Control System Schematics

• HVAC Equipment Sequence of Operations

• HVAC Equipment Electrical Ladder Diagrams

• Component Wiring Diagrams

• Terminal Strip Diagrams

• BACnet Communication Architecture Schematic

• Electrical Power Sources

• Wire numbers on all wires and terminations

1.5.2 Product Data

• Direct Digital Controllers

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

(B-SA)

• BACnet Gateways;

• Include BACnet and workstation display information; bi-directional communication ability; compliance with 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)

• DDC Software;

• BACnet Operator Workstation

• BACnet Operator Workstation DDC Software

• Include BACnet PICS for Operator Workstation software

• Sensors and Input Hardware

• Output Hardware

Page 10 of 56 Version Date: 21 May 2013

• Surge and transient protection

• Indicators

• Valves (per valve schedule)

1.5.3 Design Data

• Transformer Sizing Calculations

• Pre-PVT Checklist

• Commissioning Plan

1.5.4 Test Reports

• Pre-PVT Report

1.5.5 Certificates

• Contractor's Qualifications: Include in the documentation the name and location of each project, reference/contact information for each project, approximate size of the controls scope of work (in dollars), project duration. Include resumes of the contractor’s project team.

1.5.6 Manufacturer's Field Reports

• Pre-PVT Checklist

1.5.7 Operation and Maintenance Data

• Comply with requirements for O&M manuals as outlined in section 3.3 of this specification and CSI 360- 95-3 section 01 77 53.

1.5.8 Closeout Submittals

Training Manuals: The contractor shall provide a course outline and training manuals for all training classes at least six weeks prior to the first class. DISA may modify any or all of the training course outline and training materials to meet the needs of the Facility. Review and approval by DISA shall be completed at least three weeks prior to the first class.

1.6 QUALITY ASSURANCE

Designers shall utilize this section in conjunction with Sections 01 43 00 and 01 91 00 to develop a project-specific quality assurance specification.

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

Page 11 of 56 Version Date: 21 May 2013

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 that includes the name and location of each project, reference/contact information for DISA and contracting, approximate size of the controls scope of work (in dollars), project duration. Include resumes of the contractor’s project team, including phone numbers for all personnel who will be working onsite.

Contractor performing the work shall have 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 Pre-Performance Verification Testing Plan and the Commissioning Plan specified under section 3.4.4 and in Section 01 91 00.

f. Submit and receive approval on the Training Documentation specified under the paragraph

"INSTRUCTION TO GOVERNMENT PERSONNEL. Submit at least 30 days before training.

g. Deliver the final Controls System Operators Manuals.

Page 12 of 56 Version Date: 21 May 2013

h. Conduct the Training.

i. Submit and receive approval of Closeout Submittals.

1.7 SECURITY REQUIREMENTS

1.7.1 Designer Security Requirements

The designer of the DDC system shall maintain a security clearance in compliance with the contract documents for the contract that the work is being performed under.

1.7.2 DDC Operator, Installer and Repairer Security Requirements

All installer, operators and repairers of a DDC system shall posses and maintain a valid Secret security clearance. All operators and programmers of DDC systems shall additionally posses an IT-II access.

2. PRODUCTS

2.1 DDC SYSTEM

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 and central plant equipment. All devices provided shall be certified in the BACnet Testing Laboratories (BTL) Product Listing.

Provide an operator workstation with complete interface software capable of programming, configuring, and monitoring the digital controllers. Interface the new DDC system with the [a new/existing] Iconics Genesis 64 system. Create graphics, trends, schedules, alarming on the workstations as outlined in Division 25.

2.1.1 Direct Digital Controllers

Direct digital controllers shall be UL 916 listed.

2.1.1.1 I/O Point Limitation

Each critical system or equipment shall have its own dedicated controller with I/O modules to meet redundancy requirements as specified in other parts of this specification. Multiple and different systems and equipment shall not be combined on a single controller. Provide a minimum of 4 spare input and 4 outputs per 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 Peer-to-peer communication in distributed network architecture

The control systems shall be designed such that each mechanical system shall operate under stand alone. The contractor administered by this Section of the technical specifications shall provide controllers for each mechanical system. In the event of a network communication failure, or the loss of any field controller, the control system shall continue to operate independently. Failure of the operator work station (s) (OWS) shall have no effect on the field controllers, including those involved with global strategies.

2.1.1.4 Internal Clock

Page 13 of 56 Version Date: 21 May 2013

Provide internal clocks for all BACnet Building Controllers (B-BC) and BACnet Advanced Application Controllers (B-AAC). Automatically synchronize system clocks daily.

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. 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.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, keyed three-position (on-off-auto) override switches and status lights. 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. Analog outputs shall have a toggle switch and method to adjust the analog signal, or provide a maintained open-closed position for on-off control. For HVAC equipment and plant controllers, provide for manual overrides, keyed three-position (on-off-auto) override switches, analog modulation method and status lights,

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

Page 14 of 56 Version Date: 21 May 2013

2.1.10 Digital Controller BACnet Internetwork

Provide a BACnet internetwork with control products, communication media, connectors, repeaters, hubs, and routers. Provide intermediate gateways, only when approved by the Government to connect existing non- BACnet devices to the BACnet internetwork. Controller and operator interface communication shall conform to ASHRAE 135, BACnet. Where appropriate use the building's existing Building Automation System (BAS) network. Do not connect to any DISA network unless provided approval in writing by the ES521 project engineer. If a controller becomes non-responsive, the remaining controllers shall continue operating and not be affected by the failed controller.

2.1.11 Communications Ports

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

2.1.12 Modems

Modems not allowed for installation.

2.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 approved by the Government. 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 a 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 Communication Control (DM-DCC-B) BIBBs, in accordance with ASHRAE 135.

e. All unused ports and terminations on a Gateway shall be turned off/diabled via the gateways software, firmware, or configuration tool.

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

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

Page 15 of 56 Version Date: 21 May 2013 in damp environments such as chiller rooms, basements, crawlspaces, attics 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 for each panel to the Facility Manager.

Controller cabinet enclosures shall be UL508A listed. All fabricated control panels shall comply and be certified UL508A. Each panel assembly shall be fabricated and bench tested prior to being shipped to the site for field installation. Each panel shall be provided with its own UL508A listing, identifiable by a UL label affixed to the backplane. Panel enclosure test results shall be logged, attached to a digital photograph of each panel, and included in the O&M package provided to the owner a project closeout.

Each cabinet that contains manual equipment operation as defined by this specification provide a phenolic label on the cabinet that describes the steps/actions required to manually operate the equipment.

2.1.1.15 Network Switches

Provide industrial grade managed network switch with the appropriate port quantities and the following options:

MFG: Sixnet – SLX Series Only

Standard Compliance: UL508/CSA C22.2/14; EN61010-1,CE EMI Emissions FCC Part 15, ICES-003; EN6100-6-4, CE EMC Immunity IEC6100-6-2, CE Hazardous Locations UL 1604 Eye Safety (Fiber Models) IEC60825-1 IEEE 802.3 (10mBPS Ethernet – Legacy devices) IEEE 802.3u (Fast Ethernet 100Mpbs – newer devices IEEE 802.3x (Full Duplex with flow control) IEEE 802.1D/w (Rapid Spanning Tree)

Power: Redundant Power DC Spike Protection – 5000W Transient Protection - 15,000 watts

Performance: Rapid Spanning Tree

SNMP V3

SNMP notifications (traps) for report event

Environmental: Operating temperature -40 to +75 deg C Humidity (non condensing) 5 – 95% RH

Ethernet: RJ45 ports (shielded) 10/100Base TX RJ45 speed (10 or 100M) auto-negotiation

Ports 8 Ports minimum per switch

Mounting: Din Rail

Warranty: 5 Year

2.1.1.17 Main Power Switch and Receptacle

Page 16 of 56 Version Date: 21 May 2013

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

2.1.1.18 Standalone UPS

When required by this specification provide a standalone UPS with the correct input and output voltage to support the controls system being supported by the UPS. The UPS shall meet the following minimum requirements:

UPS Type – Online, Double Conversion

AC output - +- 2% of output rating

Monitoring – Dry Contacts to alert on UPS alarm and failure

NO WEB MONITORING OPTIONS ARE PERMITTED.

Battery Metering – LED type

Battery Runtime – Full load for 5 minutes

2.1.1.19 DDC Redundancy Levels

Provide redundancy to the DDC system as follows:

System Redundancy Level Air Handler and VAV (Admin Spaces) N Chiller Plants (supporting Data Centers) 2N*

Condenser Plants (supporting Data Centers) 2N* Chiller Plants (Admin Spaces) N

Condenser Plants (Admin Spaces) N Exhaust Systems (Life safety and Battery Rooms) N

* The reference to 2N is not intended to require a 2N control system to each component in the controlled system, but rather to require that the existing 2N mechanical system shall have a controls system that compliments the mechanical systems redundancy without introducing single points of failure in the mechanical system as a result of the control system design or installation.

When a DDC system is required to have a 2N redundancy level, the entire DDC system shall not have a Single Point of Failure (SPOF) as defined by Section 01 42 00. Specific attention shall be taken to ensure that single points of failure are not introduced in the programming, external power, controllers, valve control (data and power), sensors, leak detection, gateways, switches, and routers.

2.1.1.20 External Power Sources for DDC systems

DDC systems shall be installed with external power sources as follows:

System External Power Source

Standalone UPS Required

Air Handler and VAV (Admin Spaces) Essential Power No Chiller Plants (supporting Data Centers) One Essential, One

Critical* Yes, Essential Power Source Only

Condenser Plants (supporting Data Centers) One Essential, One Critical*

Yes, Essential Power Source Only

Chiller Plants (Admin Spaces) Essential Yes Condenser Plants (Admin Spaces) Essential Yes

Exhaust Systems (Life safety and Battery Rooms)

Critical No

Page 17 of 56 Version Date: 21 May 2013

* The term one is not intended to indicate providing a single source, but rather to indicate that one N system is to be powered by a particular source or power. Provide the quantity of circuits necessary to provide a reliable and operable DDC system.

Refer to Section 01 42 00 for definitions of Critical and Essential Power.

External power sources shall be sized in accordance with NFPA 70 (National Electrical Code).

2.1.1.21 Network Architecture

Utilize or install (as required by the contract or design) the network established by the requirements of CSI 360- 95-3 division 25 to interconnect all DDC controllers in a Distributed Network Architecture fashion.

Install a MS/TP subnet from the nearest DDC controller to establish communication with administrative space equipment such as VAV’s, FTU’s, and exhaust systems.

Label all network wiring so that the labels are readable without having to disconnect or manipulate the wire to make the label legible.

Wire insulation and jacket color for the network shall comply with the following table:

Equipment Connected Wire Jacket Color Ethernet Blue

MSTP, Modbus Orange

2.1.2 DDC Software

Refer to Division 25 for a list of data points.

2.1.2.1 Equipment Sequence of Operations

NOTE: Provide a complete, clear, and concise written sequence of operation for the HVAC equipment.

Include all conventional control operations, time event operations, energy management functions (night setback, reset schedules, optimum start), push button overrides, demand limiting, safeties, and emergency conditions. Put the sequence of operation on the design drawings, not in the specifications.

The following generalized sequences of operations shall be used by the BAS designer as a baseline for operation of the systems. The BAS designer shall not simply copy and paste these sequences of operations into their design, but use the sequences as a baseline for their design. The sequence of operation shall be shown on the design drawings. It is provided in the specification as an identification of minimum compliance for DISA.

a. Air Systems:

AIR HANDLERS

Occupied Mode: (Normal Day Operation – VFD/Chilled Water/VAV)

• Unit supply fan is activated when any room has exceeded their temperature set point.

• The unit supply fan shall stop when the temperature set point has been reached and all of the temperature sensors are within there deadband.

• Supply fan VFD modulates fan speed to maintain supply air static pressure setpoint

(Supply air static pressure setpoint to be determined by the balance contractor)

• The chilled water valve modulates to maintain the supply air temperature setpoint (55°F

Page 18 of 56 Version Date: 21 May 2013 adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the highest associated space temperature reading reported back through the network.

Occupied Mode: (Normal Day Operation – Constant Volume/Chilled Water)

• The unit supply fan shall stop when the temperature set point has been reached.

• Supply fan maintains a constant flow of air

• Chilled water valve modulates to maintain supply air temperature setpoint (55°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the

Occupied Mode: (Normal Day Operation – VFD/DX/VAV) the temperature sensors are within there deadband.

• Supply fan VFD modulates fan speed to maintain supply air static pressure setpoint

(Supply air static pressure setpoint to be determined by the balance contractor)

• If available, the compressor providing refrigerant flow shall modulate to maintain supply air temperature setpoint (55°F adj.)

• If refrigerant flow is constant, the outside air and return air dampers shall modulate to maintain the supply air temperature setpoint (55°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the

Occupied Mode: (Normal Day Operation – Constant Volume/DX)

• Supply fan maintains a constant flow of air

• Compressor maintains constant flow of refrigerant to maintain supply air temperature setpoint (55°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the

Occupied Mode: (Normal Day Operation – VFD/Electric Heat/VAV)

• Unit supply fan is activated when any room has fallen below their temperature set point.

the temperature sensors are within there deadband.

• Supply fan VFD modulates fan speed to maintain supply air static pressure setpoint

(Supply air static pressure setpoint to be determined by the balance contractor)

• The electric heater is activated to maintain the supply air temperature setpoint (95°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the lowest associated space temperature reading reported back through the network.

Occupied Mode: (Normal Day Operation – Constant Volume/Electric Heat)

• Supply fan maintains a constant flow of air

• The electric heater is activated to maintain the supply air temperature setpoint (95°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the

Occupied Mode: (Normal Day Operation – VFD/Hot Water/VAV)

Page 19 of 56 Version Date: 21 May 2013 the temperature sensors are within there deadband.

• Supply fan VFD modulates fan speed to maintain supply air static pressure setpoint

(Supply air static pressure setpoint to be determined by the balance contractor)

• Hot water valve modulates to maintain the supply air temperature setpoint (95°F adj.)

• Unoccupied Mode: (Night Setback Operation) - Unit supply fan starts/stops based on the

Occupied Mode: (Normal Day Operation – Constant Volume/Hot Water)

• Supply fan maintains a constant flow of air

• Hot water valve modulates to maintain the supply air temperature setpoint (95°F adj.)

Unoccupied Mode: (Night Setback Operation)

• Unit supply fan starts/stops based on the lowest associated space temperature reading reported back through the network.

General Notes:

When operation is permitted by the DDC schedule, the air handler shall:

• Maintain minimum outside air flow as required by ASHRAE 62 unless:1. ATFP signal is active. When active close outside air intakes, shut off exhaust fans in admin space; alarm when CO2 levels reach alarm thresholds.

• Monitor outside air intake Air Quality Sensors; close dampers as necessary to prevent poor internal air quality.

• Compare outside air temperature and return temperature; utilize lowest temperature as primary airflow in mixing chambers to maintain efficiencies. In high humidity climates, use enthalpy to determine free cooling activation.

• Modulate fan speed or inlet fans to maintain supply duct and building static pressure.

Upon activation of safety device (smoke detector, freeze stat, pressure switch, motor failure):

• Stop fan