200131_Specifications_Rev. 01.pdf

ISSUED FOR CONSTRUCTION

SPECIFICATIONS

Repair Chilled Water System, B2280 – Dust off

Architect-Engineering Services for 100% Design

Project Number: WWYK200131 Work Order: 22956

Revision 01

Tinker Air Force Base, Oklahoma June 2, 2026

Prepared By:

HDR Engineering, Inc.

9311 San Pedro Ave, Suite 1100 San Antonio, TX 78216

This page intentionally left blank.

REPAIR CHILLED WATER SYSTEM, B2280 � Revision 1 WWYK200131

06/01/2026

REPAIR CHILLED WATER SYSTEM, B2280 � Revision 1 WWYK200131

REPAIR CHILLED WATER SYSTEM, B2280 WWYK200131

ISSUED FOR CONSTRUCTION - Revision 1

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

08/24, CHG 1: 08/25

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) system, suitable for the control of the heating, ventilating and air conditioning (HVAC) and other building-level systems as indicated and shown and in accordance with Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS, and other referenced Sections.

The newly installed control systems shall be programmed into the existing facility control system. Expand the existing control system to accommodate new control system requirements. The existing facility currently utilizes Honeywell Comfort Point Open CPO-PC-6A controllers. All new and replacement building-level controllers shall provide native, seamless connection and full functional operability into the existing Honeywell base front end. To minimize lifecycle maintenance, training, and cybersecurity risks, expanding upon the existing hardware architecture is strongly preferred. The Controls Contractor shall verify the exact base front end with the Contracting Officer's Representative (COR) before starting any work. Before the start of construction, the Controls Contractor shall meet with the Base Energy Monitoring and Control System (EMCS) Supervisor to discuss the recovery of existing working controls that are removed from the building.

All installed control systems shall be connected to the existing base-wide Civil Engineering Community of Interest Network (CE COIN). The control systems shall be programmed into the base-wide Honeywell Enterprise Building Integrator (EBI). The Contractor shall contact and coordinate connections with the Civil Engineering Information System Security Manager (CE ISSM) for the Control System (CS). If a system other than the existing facility standard is proposed, the Contractor shall bear full responsibility for all costs, engineering, and cybersecurity compliance required to achieve seamless integration without the use of third-party protocol translators or gateways.

Whenever possible and where indicated on plans, reuse existing Direct Digital Control (DDC) panels and field devices. Modify DDC panels to match the new control requirements. New field devices shall comply with the requirements of this section and Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC [Heating, Ventilation, and Air Conditioning]. New graphics shall be provided for all new components as indicated in the control drawings. Existing graphics shall be updated to remove any demolished or modified equipment.

1.1.1 Proprietary Systems

1.1.1.1 Proprietary Systems Exempted From Open Protocol Requirements

The following systems are specifically exempted from the open protocol requirements of Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS:

SECTION 23 09 00 Page 1

SGARDENO

Polygon

a. A simple split (DX) system consisting of a single indoor unit and a single outdoor unit from the same manufacturer.

b. Systems in Table I (previously approved by the designer in accordance with UFC 3-410-02 ).

TABLE I: Systems Approved to Use Proprietary Communications

System Type (Multi-Split/VRF or Chiller/Boiler Plant)

Proprietary Multi-Split Engineering Tool Software Required (for Multi-Split/VRF only)

c. A system (not already shown Table I) of multiple boilers or multiple chillers communicating with a proprietary network for which an approved request has been obtained and for which: all units are from the same manufacturer, they are all co-located in the same room, the network connecting them is fully contained in that room, and the units are operating using a common "plant" sequence of operation which stages the units in a manner that requires operational parameters be shared between them and which cannot be accomplished with a single lead-lag command from a third-party controller.

1.1.1.2 Implementation of Proprietary Systems

For proprietary systems exempted from open protocol requirements, a proprietary network and DDC hardware communicating via a proprietary protocol are permitted. For these systems a building control network meeting the requirements of Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS must also be provided, along with a gateway or interface to connect the proprietary system to the open building control network.

The proprietary system gateway or interface must provide the required functionality as shown on the points schedule. Scheduling, alarming, trending, overrides, network inputs, network outputs and other protocol related requirements must be met on the open protocol control system as specified in Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS.

1.1.1.3 Proprietary Multi-Split Engineering Tool Software

For each permitted proprietary systems in Table 1 shown as requiring Proprietary Multi-Split Engineering Tool Software, provide the software needed to replace a unit and configure the replacement. Submit hard copies of the software user manuals with the software submittal.

Submit Proprietary Multi-Split Engineering Tool Software on CD-ROM as a Technical Data Package. Submit 1 hard copy of the software user manual for each piece of software.

1.1.2 System Requirements

Provide systems meeting the requirements this Section and other Sections

SECTION 23 09 00 Page 2 referenced by this Section, and which have the following characteristics:

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

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

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

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

e. All necessary documentation, configuration information, programming tools, programs, drivers, and other software are licensed to and otherwise remain with the Government such that the Government or their agents are able to perform repair, replacement, upgrades, and expansions of the system without subsequent or future dependence on the Contractor, Vendor or Manufacturer.

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

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

h. All Niagara Framework components have an unrestricted interoperability license with a Niagara Information and Conformance Statement (NICS)which allows open access as defined by Niagara NICS with a value of "ALL" for "Station Compatibility In", "Station Compatibility Out", "Tool Compatibility In" and "Tool Compatibility Out". Note that this will result in the following entries in the license file:

accept.station.in="*" accept.station.out="*" accept.wb.in="*" accept.wb.out="*"

1.1.3 End to End Accuracy

Select products, install and configure the system such that the maximum error of a measured value as read from the DDC Hardware over the network is less than the maximum allowable error specified for the sensor or instrumentation.

SECTION 23 09 00 Page 3

1.1.4 Verification of Dimensions

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

1.1.5 Drawings

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

1.2 RELATED SECTIONS

Related work specified elsewhere:

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

BUILDING CONTROL SYSTEMS.

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

Section 01 91 00.15 BUILDING COMMISSIONING

1.3 REFERENCES

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

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2024; INT 1-3 2025; Errata 1 2025; INT 4-6 2025; Addenda CU 2025) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE FUN IP (2021; CORR 2023) Fundamentals Handbook, I-P Edition

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE C62.41 (1991; R 1995) Recommended Practice on Surge Voltages in Low-Voltage AC Power Circuits

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

NEMA 250 (2020) Enclosures for Electrical Equipment (1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2023; ERTA 1 2024; TIA 24-1; TIA 25-2)

National Electrical Code

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

SECTION 23 09 00 Page 4

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2021) NiagaraAX User's Guide

Niagara NICS (2022) Niagara Information and Conformance Statement

U.S. DEPARTMENT OF DEFENSE (DOD)

UFC 3-410-02 (2018; with Change 2, 2021) Direct Digital Control for HVAC and Other Building Control Systems

UL SOLUTIONS (UL)

UL 5085-3 (2006; Reprint Jan 2022) UL Standard for Safety Low Voltage Transformers - Part 3:

Class 2 and Class 3 Transformers

1.4 DEFINITIONS

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

Definitions including "(BACnet)" after the term are definitions derived from ASHRAE 135.

1.4.1 Alarm Generation

Alarm Generation is the monitoring of a value, comparison of the value to alarm conditions and the creation of an alarm when the conditions set for the alarm are met. Note that this does NOT include delivery of the alarm to the final destination (such as a user interface).

1.4.2 Building Automation and Control Network (BACnet) (BACnet)

The term BACnet is used in two ways. First meaning the BACnet Protocol Standard - the communication requirements as defined by ASHRAE 135 including all annexes and addenda. The second to refer to the overall technology related to the ASHRAE 135 protocol.

1.4.3 BACnet Advanced Application Controller (B-AAC) (BACnet)

A hardware device BTL Listed as a B-AAC, which is required to support BACnet Interoperability Building Blocks (BIBBs) for scheduling and alarming, but is not required to support as many BIBBs as a B-BC.

1.4.4 BACnet Application Specific Controller (B-ASC) (BACnet)

A hardware device BTL Listed as a B-ASC, with fewer BIBB requirements than a B-AAC. It is intended for use in a specific application.

SECTION 23 09 00 Page 5

1.4.5 BACnet Building Controller (B-BC) (BACnet)

A hardware device BTL Listed as a B-BC. A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks including control and monitoring via direct digital control (DDC) of specific systems and data storage for trend information, time schedules, and alarm data. Like the other BTL Listed controller types (B-AAC, B-ASC etc.) a B-BC device is required to support the server ("B") side of the ReadProperty and WriteProperty services, but unlike the other controller types it is also required to support the client ("A") side of these services. Communication between controllers requires that one of them support the client side and the other support the server side, so a B-BC is often used when communication between controllers is needed.

1.4.6 BACnet Broadcast Management Device (BBMD) (BACnet)

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. Each IP subnet that is part of a BACnet/IP network must have at least one BBMD. Note there are additional restrictions when multiple BBMDs share an IP subnet.

1.4.7 BACnet/IP (BACnet)

An extension of BACnet, Annex J, defines the use of a reserved UDP socket to transmit BACnet messages over IP networks. A BACnet/IP network is a collection of one or more IP subnets that share the same BACnet network number. See also paragraph BACNET BROADCAST MANAGEMENT DEVICE.

1.4.8 BACnet Internetwork (BACnet)

Two or more BACnet networks, connected with BACnet routers. In a BACnet Internetwork, there exists only one message path between devices.

1.4.9 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

A BIBB is a collection of one or more ASHRAE 135 Services intended to define a higher level of interoperability. BIBBs are combined to build the BACnet functional requirements for a device in a specification. Some BIBBs define additional requirements (beyond requiring support for specific services) in order to achieve a level of interoperability. For example, the BIBB DS-V-A (Data Sharing-View-A), which would typically be used by a front-end, not only requires the client to support the ReadProperty Service, but also provides a list of data types (Object / Properties) which the client must be able to interpret and display for the user.

In the BIBB shorthand notation, -A is the client side and -B is the server side.

The following is a list of some BIBBs used by this or referenced Sections:

DS-COV-A Data Sharing-Change of Value (A side)

DS-COV-B Data Sharing-Change of Value (B side)

SECTION 23 09 00 Page 6

The following is a list of some BIBBs used by this or referenced Sections:

NM-RC-B Network Management-Router Configuration (B side)

DS-RP-A Data Sharing-Read Property (A side)

DS-RP-B Data Sharing-Read Property (B side)

DS-RPM-A Data Sharing-Read Property Multiple (A Side)

DS-RPM-B Data Sharing-Read Property Multiple (B Side)

DS-WP-A Data Sharing-Write Property (A Side)

DM-TS-B Device Management-Time Synchronization (B Side)

DM-UTC-B Device Management-UTC Time Synchronization (B Side)

DS-WP-B Data Sharing-Write Property (B side)

SCHED-E-B Scheduling-External (B side)

DM-OCD-B Device Management-Object Creation and Deletion (B side)

AE-N-I-B Alarm and Event-Notification Internal (B Side)

AE-N-E-B Alarm and Event-Notification External (B Side)

T-VMT-I-B Trending-Viewing and Modifying Trends Internal (B Side)

T-VMT-E-B Trending-Viewing and Modifying Trends External (B Side)

1.4.10 BACnet Network (BACnet)

In BACnet, a portion of the control Internetwork consisting of one or more segments connected by repeaters. Networks are separated by routers.

1.4.11 BACnet Operator Display (B-OD) (BACnet)

A basic operator interface with limited capabilities relative to a B-OWS.

It is not intended to perform direct digital control. A B-OD profile could be used for LCD devices, displays affixed to BACnet devices, handheld terminals or other very simple user interfaces.

1.4.12 BACnet Segment (BACnet)

One or more physical segments interconnected by repeaters ( ASHRAE 135).

1.4.13 BACnet Smart Actuator (B-SA) (BACnet)

A simple actuator device with limited resources intended for specific applications.

1.4.14 BACnet Smart Sensor (B-SS) (BACnet)

A simple sensing device with limited resources.

SECTION 23 09 00 Page 7

1.4.15 BACnet Testing Laboratories (BTL) (BACnet)

Established by BACnet International to support compliance testing and interoperability testing activities and consists of BTL Manager and the BTL Working Group (BTL-WG). BTL also publishes Implementation Guidelines.

1.4.16 BACnet Testing Laboratories (BTL) Listed (BACnet)

A device that has been listed by BACnet Testing Laboratory. Devices may be certified to a specific device profile, in which case the listing indicates that the device supports the required capabilities for that profile, or may be listed as "other".

1.4.17 Binary

A two-state system where an "ON" condition is represented by a high signal level and an "OFF" condition is represented by a low signal level.

'Digital' is sometimes used interchangeably with 'binary'.

1.4.18 Broadcast

Unlike most messages, which are intended for a specific recipient device, a broadcast message is intended for all devices on the network.

1.4.19 Building Control Network (BCN)

The network connecting all DDC Hardware within a building (or specific group of buildings).

1.4.20 Building Point of Connection (BPOC)

A FPOC for a Building Control System. (This term is being phased out of use in preference for FPOC but is still used in some specifications and criteria. When it was used, it typically referred to a piece of control hardware. The current FPOC definition typically refers instead to IT hardware.)

1.4.21 Commandable

See Overridable.

1.4.22 Commandable Objects (BACnet)

Commandable Objects have a Commandable Property, Priority_Array, and Relinquish_Default Property as defined in ASHRAE 135, Clause 19.2, Command Prioritization.

1.4.23 Configurable

A property, setting, or value is configurable if it can be changed via hardware settings on the device, via the use of engineering software or over the control network from the front end, and is retained through (after) loss of power.

a. In a non-Niagara Framework BACnet system, a property, setting, or value is configurable if it can be changed via one or more of:

(1) via BACnet services (including proprietary BACnet services)

(2) via hardware settings on the device

SECTION 23 09 00 Page 8

b. In a Niagara Framework BACnet system, a property, setting, or value is configurable if it can be changed via one or more of:

(1) via BACnet services (including proprietary BACnet services)

(2) via hardware settings on the device

(3) via the Niagara Framework

Note this is more stringent than the ASHRAE 135 definition.

1.4.24 Control Logic Diagram

A graphical representation of control logic for multiple processes that make up a system.

1.4.25 Device (BACnet)

A Digital Controller that contains a BACnet Device Object and uses BACnet to communicate with other devices.

1.4.26 Device Object (BACnet)

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 or device ID.

1.4.27 Device Profile (BACnet)

A collection of BIBBs determining minimum BACnet capabilities of a device, defined in ASHRAE 135. Standard device profiles include BACnet Advanced Workstations (B-AWS), 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).

1.4.28 Digital Controller

An electronic controller, usually with internal programming logic and digital and analog input/output capability, which performs control functions.

1.4.29 Direct Digital Control (DDC)

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

1.4.30 Field Point of Connection (FPOC)

The FPOC is the point of connection between the UMCS IP Network and the field control network (either an IP network, a non-IP network, or a combination of both). The hardware at this location which provides the connection is generally an IT device such as a switch, IP router, or firewall.

In general, the term "FPOC Location" means the place where this connection occurs, and "FPOC Hardware" means the device that provides the connection. Sometimes the term "FPOC" is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in

SECTION 23 09 00 Page 9 which it is used.

1.4.31 Fox Protocol (Niagara Framework)

The protocol used for communication between components in the Niagara Framework . By default, Fox uses TCP port 1911.

1.4.32 Gateway

A device that translates from one protocol application data format to another. Devices that change only the transport mechanism of the protocol

- "translating" from TP/FT-10 to Ethernet/IP or from BACnet MS/TP to BACnet over IP for example - are not gateways as the underlying data format does not change. Gateways are also called Communications Bridges or Protocol Translators. Some devices contain bith gateway and control functions; these devices are considered both gateways and digital controllers and must meet the requirements for both.

A Niagara Framework Supervisory Gateway is one type of Gateway.

1.4.33 IEEE 802.3 Ethernet

A family of local-area-network technologies providing high-speed networking features over various media, typically Cat 5, 5e or Cat 6 twisted pair copper or fiber optic cable.

1.4.34 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 connections, also known as "sessions", which have end-to-end confirmation and guaranteed sequence of delivery.

1.4.35 Input/Output (I/O)

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

1.4.36 I/O Expansion Unit

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

1.4.37 IP subnet

A group of devices which share a defined range IP addresses. Devices on a common IP subnet can share data (including broadcasts) directly without the need for the traffic to traverse an IP router.

1.4.38 JACE (Niagara Framework)

Java Application Control Engine. See paragraph NIAGARA FRAMEWORK

SUPERVISORY GATEWAY

SECTION 23 09 00 Page 10

1.4.39 Local-Area Network (LAN)

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

1.4.40 Local Display Panels (LDPs)

A DDC Hardware with a display and navigation buttons, and must provide display and adjustment of points as shown on the Points Schedule and as indicated.

1.4.41 MAC Address

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

1.4.42 Multidrop Serial Bus/Token-Passing (MS/TP) (BACnet)

Data link protocol as defined by the BACnet standard. Multiple speeds (data rates) are permitted by the BACnet MS/TP standard.

1.4.43 Monitoring and Control (M&C) Software

The UMCS 'front end' software which performs supervisory functions such as alarm handling, scheduling and data logging and provides a user interface for monitoring the system and configuring these functions.

1.4.44 Network Number (BACnet)

A site-specific number assigned to each network. This network number must be unique throughout the BACnet Internetwork.

1.4.45 Niagara Framework (Niagara Framework)

A set of hardware and software specifications for building and utility control owned by Tridium Inc. and licensed to multiple vendors. The Framework consists of front end (M&C) software, web based clients, field level control hardware, and engineering tools. While the Niagara Framework is not adopted by a recognized standards body and does not use an open licensing model, it is sufficiently well-supported by multiple HVAC vendors to be considered a de-facto Open Standard.

1.4.46 Niagara Framework Supervisory Gateway (Niagara Framework)

DDC Hardware component of the Niagara Framework. A typical Niagara architecture has Niagara specific supervisory gateways at the IP level and other (non-Niagara specific) controllers on field networks (TP/FT-10, MS/TP, etc.) beneath the Niagara supervisory gateways. The Niagara specific controllers function as a gateway between the Niagara framework protocol (Fox) and the field network beneath. These supervisory gateways may also be used as general purpose controllers and also have the capability to provide a web-based user interface.

Note that different vendors refer to this component by different names.

The most common name is "JACE"; other names include (but are not limited to)"EC-BOS", "FX-40", "TMN", "SLX" and "UNC".

SECTION 23 09 00 Page 11

1.4.47 Object (BACnet)

An ASHRAE 135 Object. The concept of organizing BACnet information into standard components with various associated Properties. Examples include Analog Input objects and Binary Output objects.

1.4.48 Object Identifier (BACnet)

A grouping of two Object properties: Object Type (e.g. Analog Value, Schedule, etc.) and Object Instance (in this case, a number). Object Identifiers must be unique within a device.

1.4.49 Object Instance (BACnet)

See paragraph OBJECT IDENTIFIER

1.4.50 Object Properties (BACnet)

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.4.51 Operator Configurable

Operator configurable values are values that can be changed from a single common front end user interface across multiple vendor systems.

For Niagara Framework Systems, a property, setting, or value is Operator Configurable when it is configurable from a Niagara Framework Front End.

For non Niagara-based BACnet systems, a property, setting, or value in a device is Operator Configurable when it is Configurable and is either:

a. a Writable Property of a Standard BACnet Object; or

b. a Property of a Standard BACnet Object that is Writable when

Out_Of_Service is TRUE and Out_Of_Service is Writable.

1.4.52 Overridable (Point)

A point is Overridable if it can be Overriden (See Override).

1.4.53 Override

Changing the value of a point outside of the normal sequence of operation where the change has priority over the sequence and where there is a mechanism for releasing the change such that the point returns to the normal value. Overrides persist until released or overridden at the same or higher priority but are not required to persist through a loss of power.

Overrides are often used by operators to change values, and generally originate at a user interface (workstation or local display panel).

1.4.54 Packaged Equipment

Packaged equipment is a single piece of equipment provided by a manufacturer in a substantially complete and operable condition, where the controls (DDC Hardware) are factory installed, and the equipment is sold and shipped from the manufacturer as a single entity. Disassembly and

SECTION 23 09 00 Page 12 reassembly of a large piece of equipment for shipping does not prevent it from being packaged equipment. Package units may require field installation of remote sensors. Packaged equipment is also called a "packaged unit".

Note industry may use the term "Packaged System" to mean a collection of equipment that is designed to work together where each piece of equipment is packaged equipment and there is a network that connects the equipment together. A "packaged system" of this type is NOT packaged equipment; it is a collection of packaged equipment, and each piece of equipment must individually meet specification requirements.

1.4.55 Packaged Unit

See packaged equipment.

1.4.56 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.4.57 Physical Segment (BACnet)

A single contiguous medium to which BACnet devices are attached ( ASHRAE 135

1.4.58 Polling

A device periodically requesting data from another device.

1.4.59 Points

Physical inputs and outputs, and virtual values read from or written to a controller over the the network. See also paragraph INPUT/OUTPUT (I/O).

1.4.60 Proportional, Integral, and Derivative (PID) Control Loop

A closed-loop control algorithm calculating control output based using the error between a process variable and setpoint. The proportional control component adjusts control output based on the current error, the integral component adjusts based on a sum of errors over time, and the derivative component adjusts based on the rate of change of the errors. Not all components are employed in all implementation of a PID loop, and when a component is not used the corresponding letter is generally dropped from the abbreviation used for that control. For example derivative control is often not required for HVAC systems, leaving "PI" control.

1.4.61 Proprietary (BACnet)

Within the context of BACnet, any extension of or addition to object types, properties, PrivateTransfer services, or enumerations specified in ASHRAE 135. Objects with Object_Type values of 128 and above are Proprietary Objects. Properties with Property_Identifier of 512 and above are proprietary Properties.

SECTION 23 09 00 Page 13

1.4.62 Protocol Implementation Conformance Statement (PICS) (BACnet)

A document, created by the manufacturer of a device, which describes which portions of the BACnet standard may be implemented by a given device.

ASHRAE 135 requires that all ASHRAE 135 devices have a PICS, and also defines a minimum set of information that must be in it. A device as installed for a specific project may not implement everything in its PICS.

1.4.63 Repeater

A device that connects two control network segments and retransmits all information received on one side onto the other.

1.4.64 Router

Generically, a Router is a device that connects two or more networks and controls traffic between them by retransmitting signals received from one network onto another based on the signal destination.

As used in this Section, a Router connects two or more ASHRAE 135 networks and controls traffic between them by retransmitting signals received from one network onto another based on the signal destination. Routers are used to subdivide a BACnet internetwork and to limit network traffic.

1.4.65 Segment

A 'single' section of a control network that contains no repeaters or routers. There is generally a limit on the number of devices on a segment, and this limit is dependent on the topology/media and device type.

1.4.66 Standard BACnet Objects (BACnet)

Objects with Object_Type values below 128 and specifically enumerated in Clause 21 of ASHRAE 135. Objects which are not proprietary. See paragraph PROPRIETARY.

1.4.67 Standard BACnet Properties (BACnet)

Properties with Property_Identifier values below 512 and specifically enumerated in Clause 21 of ASHRAE 135. Properties which are not proprietary. See Proprietary.

1.4.68 Standard BACnet Services (BACnet)

ASHRAE 135 services other than ConfirmedPrivateTransfer or UnconfirmedPrivateTransfer. See paragraph PROPRIETARY.

1.4.69 UMCS

UMCS stands for Utility Monitoring and Control System. The term refers to all components by which a project site monitors, manages, and controls real-time operation of HVAC and other building systems. These components include the UMCS "front-end" and all field building control systems connected to the front-end. The front-end consists of Monitoring and Control Software (user interface software), browser-based user interfaces and network infrastructure.

The network infrastructure (the "UMCS Network"), is an IP network

SECTION 23 09 00 Page 14 connecting multiple building or facility control networks to the Monitoring and Control Software.

1.4.70 UMCS Network

The UMCS Network connects multiple building or facility control networks to the Monitoring and Control Software.

1.4.71 Writable Property (BACnet)

A Property is Writable when it can be changed through the use of one or more of the WriteProperty services defined in ASHRAE 135, Clause 15 regardless of the value of any other Property. Note that in the ASHRAE 135 standard, some Properties may be writable when the Out of Service Property is TRUE; for purposes of this Section, Properties that are only writable when the Out of Service Property is TRUE are not considered to be Writable.

1.5 PROJECT SEQUENCING

TABLE II: PROJECT SEQUENCING lists the sequencing of submittals as specified in paragraph SUBMITTALS (denoted by an 'S' in the 'TYPE' column) and activities as specified in PART 3 EXECUTION (denoted by an 'E' in the 'TYPE' column). TABLE II does not specify overall project milestone and completion dates; these dates are specified in the contract documents.

a. Sequencing for Submittals: The sequencing specified for submittals is the deadline by which the submittal must be initially submitted to the Government. Following submission there will be a Government review period as specified in Section 01 33 00 SUBMITTAL PROCEDURES. If the submittal is not accepted by the Government, revise the submittal and resubmit it to the Government within 14 days of notification that the submittal has been rejected. Upon resubmittal there will be an additional Government review period. If the submittal is not accepted the process repeats until the submittal is accepted by the Government.

b. Sequencing for Activities: The sequencing specified for activities indicates the earliest the activity may begin.

c. Abbreviations: In TABLE II the abbreviation AAO is used for 'after approval of' and 'ACO' is used for 'after completion of'.

TABLE II. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)1 S Existing Conditions Report

2 S DDC Contractor Design Drawings

3 S Manufacturer's Product Data

4 S Pre-construction QC Checklist

5 E Install Building Control System AAO #1 thru #4

SECTION 23 09 00 Page 15

TABLE II. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)6 E Start-Up and Start-Up Testing ACO #5

7 S Post-Construction QC Checklist 14 days ACO #6

8 S Programming Software Configuration Software

Niagara Framework Engineering Tool Niagara Framework Wizards

14 days ACO #6

9 S Draft As-Built Drawings 14 days ACO #6

10 S Start-Up Testing Report 14 days ACO #6

11 S PVT Procedures 14 days before schedule start of #12 and AAO #10

12 E Execute PVT AAO #9 and #11

13 S PVT Report 14 days ACO #12

14 S Controller Application Programs Controller Configuration Settings

Niagara Framework Supervisory Gateway Backups

28 days AAO #13

15 S Final As-Built Drawings 28 days AAO #13

16 S O&M Instructions AAO #15

17 S Training Documentation AAO #10 and 14 days before scheduled start of #18

18 E Training AAO #16 and #17

SECTION 23 09 00 Page 16

TABLE II. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)19 S Closeout QC Checklist ACO #18

1.6 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-02 Shop Drawings

DDC Contractor Design Drawings ; G

Draft As-Built Drawings ; G

Final As-Built Drawings ; G

SD-03 Product Data

Programming Software ; G

Controller Application Programs ; G

Configuration Software ; G

Controller Configuration Settings ; G

Proprietary Multi-Split Engineering Tool Software ; G

Manufacturer's Product Data ; G

Niagara Framework Supervisory Gateway Backups ; G

Niagara Framework Engineering Tool ; G

SD-05 Design Data

Boiler Or Chiller Plant Gateway Request

SD-06 Test Reports

SECTION 23 09 00 Page 17

Existing Conditions Report

Pre-Construction Quality Control (QC) Checklist ; G

Post-Construction Quality Control (QC) Checklist ; G

Start-Up Testing Report ; G

PVT Procedures ; G

PVT Report ; G

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions ; G

Training Documentation ; G

SD-11 Closeout Submittals

Enclosure Keys ; G

Password Summary Report ; G

Closeout Quality Control (QC) Checklist ; G

1.7 DATA PACKAGE AND SUBMITTAL REQUIREMENTS

Technical data packages consisting of technical data and computer software (meaning technical data which relates to computer software) which are specifically identified in this project and which may be defined/required in other specifications must be delivered strictly in accordance with the CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered must be identified by reference to the particular specification paragraph against which it is furnished. All submittals not specified as technical data packages are considered 'shop drawings' under the Federal Acquisition Regulation Supplement (FARS) and must contain no proprietary information and be delivered with unrestricted rights.

1.8 SOFTWARE FOR DDC HARDWARE AND GATEWAYS

Provide all software related to the programming and configuration of DDC Hardware and Gateways as indicated. License all Software to the project site. The term "controller" as used in these requirements means both DDC Hardware and Gateways.

1.8.1 Configuration Software

For each type of controller, provide the configuration tool software in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. Submit hard copies of the software user manuals for each software with the software submittal.

Submit Configuration Software on CD-ROM as a Technical Data Package.

Submit 2 hard copies of the software user manual for each piece of software.

SECTION 23 09 00 Page 18

1.8.2 Controller Configuration Settings

For each controller, provide copies of the installed configuration settings as source code compatible with the configuration tool software for that controller in accordance with Section 23 09 23.02 BACNET DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

Submit Controller Configuration Settings on CD-ROM as a Technical Data Package. Include on the CD-ROM a list or table of contents clearly indicating which files are associated with each device. Submit 2 copies of the Controller Configuration Settings CD-ROM.

1.8.3 Programming Software

For each type of programmable controller, provide the programming software in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. Submit hard copies of software user manuals for each software with the software submittal.

Submit Programming Software on CD-ROM as a Technical Data Package.

Submit 2 hard copies of the software user manual for each piece of software.

1.8.4 Controller Application Programs

For each programmable controller, provide copies of the application program as source code compatible with the programming software for that controller in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL

CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

Submit Controller Application Programs on CD-ROM as a Technical Data Package. Include on the CD-ROM a list or table of contents clearly indicating which application program is associated with each device.

Submit 2 copies of the Controller Application Programs CD-ROM.

1.8.5 Niagara Framework Supervisory Gateway Backups

For each Niagara Framework Supervisory Gateway, provide a backup of all software within the Niagara Framework Supervisory Gateway, including configuration settings. This backup must be sufficient to allow the restoration of the Niagara Framework Supervisory Gateway or the replacement of the Niagara Framework Supervisory Gateway.

Submit backups for each Niagara Framework Supervisory Gateway on CD-ROM as a Technical Data Package. Mark each backup indicating clearly the source Niagara Framework Supervisory Gateway.

1.8.6 Niagara Framework Engineering Tool (for all Niagara Framework system)

Provide a Niagara Framework Engineering Tool in accordance with Section

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS. Submit software user manuals with the Niagara Framework Engineering Tool submittal.

Submit the Niagara Framework Engineering Tool on CD-ROM as a Technical Data Package. Submit 2 hard copies of the software user manual for the Niagara Framework Engineering Tool.

SECTION 23 09 00 Page 19

1.9 BOILER OR CHILLER PLANT GATEWAY REQUEST

If requesting the use of a gateway to a boiler or chiller plant as indicated in paragraph Proprietary Systems Exempted From Open Protocol Requirements, submit a Boiler or Chiller Plant Gateway Request describing the configuration of the boilers or chillers including model numbers for equipment and controllers, the sequence of operation for the units, and a justification for the need to operate the units on a shared non-BACnet network.

1.10 QUALITY CONTROL CHECKLISTS

The QC Checklist for BACnet Systems in APPENDIX A of this Section must be completed by the Contractor's Chief Quality Control (QC) Representative and submitted as indicated.

The QC Checklist for Niagara Framework Based BACnet Systems in APPENDIX A of this Section must be completed by the Contractor's Chief Quality Control (QC) Representative and submitted as indicated.

The QC Representative must verify each item indicated and initial in the space provided to indicate that the requirement has been met. The QC Representative must sign and date the Checklist prior to submission to the Government.

1.10.1 Pre-Construction Quality Control (QC) Checklist

Complete items indicated as Pre-Construction QC Checklist items in the QC Checklist. Submit four copies of the Pre-Construction QC Checklist.

1.10.2 Post-Construction Quality Control (QC) Checklist

Complete items indicated as Post-Construction QC Checklist items in the QC Checklist. Submit four copies of the Post-Construction QC Checklist.

1.10.3 Closeout Quality Control (QC) Checklist

Complete items indicated as Closeout QC Checklist items in the QC Checklist. Submit four copies of the Closeout QC Checklist.

PART 2 PRODUCTS

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

2.1 GENERAL PRODUCT REQUIREMENTS

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

The two year use must include applications of equipment and materials under similar circumstances and of similar size. DDC Hardware not meeting

SECTION 23 09 00 Page 20 the two-year field service requirement is acceptable provided it has been successfully used by the Contractor in a minimum of two previous projects. The equipment items must be supported by a service organization. Items of the same type and purpose must be identical, including equipment, assemblies, parts and components.

2.2 PRODUCT DATA

Provide manufacturer's product data sheets documenting compliance with product specifications for each product provided under Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS, or this Section. Provide product data for all products in a single indexed compendium, organized by product type.

For each manufacturer, model and version (revision) of DDC Hardware provide the Protocol Implementation Conformance Statement (PICS) in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS.

Submit Manufacturer's Product Data on CD-ROM.

2.3 OPERATION ENVIRONMENT

Unless otherwise specified, provide products rated for continuous operation under the following conditions:

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

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

c. Temperature:

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

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

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

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

2.4 WIRELESS CAPABILITY

Wireless capabilities are not permitted.

2.5 ENCLOSURES

Enclosures supplied as an integral (pre-packaged) part of another product are acceptable. Provide two Enclosure Keys for each lockable enclosure on a single ring per enclosure with a tag identifying the enclosure the keys operate. Provide enclosures meeting the following minimum requirements:

SECTION 23 09 00 Page 21

2.5.1 Outdoors

For enclosures located outdoors, provide enclosures meeting NEMA 250 Type 3 requirements.

2.5.2 Mechanical and Electrical Rooms

For enclosures located in mechanical or electrical rooms, provide enclosures meeting NEMA 250 Type 2 requirements.

2.5.3 Other Locations

For enclosures in other locations including but not limited to occupied spaces, above ceilings, and in plenum returns, provide enclosures meeting NEMA 250 Type 1 requirements.

2.6 WIRE AND CABLE

Provide wire and cable meeting the requirements of NFPA 70 and NFPA 90A in addition to the requirements of this specification and referenced specifications.

2.6.1 Terminal Blocks

For terminal blocks which are not integral to other equipment, provide terminal blocks which are insulated, modular, feed-through, clamp style with recessed captive screw-type clamping mechanism, suitable for DIN rail mounting, and which have enclosed sides or end plates and partition plates for separation.

2.6.2 Control Wiring for Binary Signals

For Control Wiring for Binary Signals, provide 18 AWG copper or thicker wire rated for 300-volt service.

2.6.3 Control Wiring for Analog Signals

For Control Wiring for Analog Signals, provide 18 AWG or thicker, copper, single- or multiple-twisted wire meeting the following requirements:

a. minimum 2 inch lay of twist

b. 100 percent shielded pairs

c. at least 300-volt insulation

d. each pair has a 20 AWG tinned-copper drain wire and individual overall pair insulation

e. cables have an overall aluminum-polyester or tinned-copper cable-shield tape, overall 20 AWG tinned-copper cable drain wire, and overall cable insulation.

2.6.4 Power Wiring for Control Devices

For 24-volt circuits, provide insulated copper 18 AWG or thicker wire rated for 300 VAC service. For 120-volt circuits, provide 14 AWG or thicker stranded copper wire rated for 600-volt service.

SECTION 23 09 00 Page 22

2.6.5 Transformers

Provide UL 5085-3 approved transformers. Select transformers sized so that the connected load is no greater than 80 percent of the transformer rated capacity.

PART 3 EXECUTION

3.1 EXISTING CONDITIONS

3.1.1 Existing Conditions Survey

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

Submit four copies of the Existing Conditions Report.

3.1.2 Existing Equipment Downtime

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

3.1.3 Existing Control System Devices

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

3.2 INSTALLATION

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

3.2.1 Dielectric Isolation

Provide…