Attachment H -23 09 00.pdf

B-3280 Repair HVAC and Electrical Systems MCB Quantico, VA

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

02/19

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) 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, and Section 23 09 23.02, BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS and other referenced Sections.

1.1.1 System Requirements

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

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

b. The building DDC system must be seamlessly compatible with the existing Base Energy Management Control System (EMCS) Network. The Base EMCS Network consists of building HVAC control devices connected via LAN to a central, Siemens's Apogee application Database. the Siemens's Apogee Database is a, government-owned, government-operated network. The existing Base EMCS Network must be coordinated through G6 and public works. All network and computer/peripheral equipment must meet the current cyber-security Authority to Operate (ATO) requirements. BLDG DDC shall be connected to existing Base-wide EMCS system after ATO authorization.

c. After the contract award, the Contractor's submittal must include a thorough explanation of how a successful, seamless interface between the new and existing DDC systems will be accomplished. As part of construction, provide:

1. Advanced proof (including an existing case study) that the system blends seamlessly with the servers, network and Siemen's application Database. This must be submitted for Government approval.

2. Thorough testing and advanced commissioning that must include vendor supported technicians from both systems (the building DDC and Siemen's Apogee Database if these are not from the same vendor as the MCB EMCS) once the integration is complete, to achieve a fully functional local and remotely controlled systems. A thorough testing of all integrational functionalities must be performed.

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

SECTION 23 09 00 Page 1 REV 8/2020 practical, the hardware performs control sequences without reliance on the building network.

e. 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. As such the system shall be open and shall be capable of supporting numerous manufacturer "off-the shelf devices".

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

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

h. Hardware is installed and configured such that the Government or their agents are able to perform repair, replacement, and upgrades of individual hardware without further interaction with the Contractor, Vendor or Manufacturer. 1.1.2 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.

1.1.3 Verification of Dimensions

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

1.1.4 Drawings

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

1.2 RELATED SECTIONS

Related work specified elsewhere:

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

BUILDING CONTROL SYSTEMS.

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

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

d. Section 01 91 00.15 10 TOTAL BUILDING COMMISSIONING

SECTION 23 09 00 Page 2

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 (2016) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE FUN IP (2017) Fundamentals Handbook, I-P Edition

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-D (2014) Control Network Protocol Specification

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 (2018) Enclosures for Electrical Equipment (1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2017; ERTA 1-2 2017; TIA 17-1; TIA 17-2;

TIA 17-3; TIA 17-4; TIA 17-5; TIA 17-6;

TIA 17-7; TIA 17-8; TIA 17-9; TIA 17-10;

TIA 17-11; TIA 17-12; TIA 17-13; TIA

17-14; TIA 17-15; TIA 17-16; TIA 17-17 )

National Electrical Code

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

UNDERWRITERS LABORATORIES (UL)

UL 5085-3 (2006; Reprint Nov 20121) 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.

SECTION 23 09 00 Page 3

After each term the protocol related to that term is included in parenthesis.

1.4.1 Alarm Generation (All protocols)

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.

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.

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.

SECTION 23 09 00 Page 4

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)

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)

SECTION 23 09 00 Page 5

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

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.

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 (All protocols)

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 (BACnet)

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) (All protocols)

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

SECTION 23 09 00 Page 6

1.4.20 Building Point of Connection (BPOC) (All protocols)

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 (All protocols)

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 (All protocols)

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.

In a 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

Note this is more stringent than the ASHRAE 135 definition.

1.4.24 Control Logic Diagram (All protocols)

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

SECTION 23 09 00 Page 7

1.4.28 Digital Controller (All protocols)

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) (All protocols)

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) (All protocols)

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 which it is used.

1.4.31 Gateway (All protocols)

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.

1.4.32 IEEE 802.3 Ethernet (All protocols)

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.33 Internet Protocol (IP, TCP/IP, UDP/IP) (All protocols)

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.34 Input/Output (I/O) (All protocols)

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

SECTION 23 09 00 Page 8

1.4.35 I/O Expansion Unit (All protocols)

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

1.4.36 IP subnet (All protocols)

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.37 NOT USED.

1.4.38 Local-Area Network (LAN) (All protocols)

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

1.4.39 Local Display Panels (LDPs) (All protocols)

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.40 MAC Address (All protocols)

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

1.4.41 Master-Slave/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.42 Monitoring and Control (M&C) Software (All protocols)

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.43 Network Number (BACnet)

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

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

SECTION 23 09 00 Page 9

1.4.46 Object Instance (BACnet)

See paragraph OBJECT IDENTIFIER

1.4.47 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.48 Operator Configurable (All protocols)

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

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.49 Override (All protocols)

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.50 Packaged Equipment (All protocols)

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 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.51 Packaged Unit (All protocols)

See packaged equipment.

SECTION 23 09 00 Page 10

1.4.52 Performance Verification Test (PVT) (All protocols)

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

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

1.4.54 Polling (All protocols)

A device periodically requesting data from another device.

1.4.55 Points (All protocols)

Physical and virtual inputs and outputs. See also paragraph INPUT/OUTPUT (I/O).

1.4.56 Proportional, Integral, and Derivative (PID) Control Loop (All protocols)

Three parameters used to control modulating equipment to maintain a setpoint. Derivative control is often not required for HVAC systems (leaving "PI" control).

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

1.4.58 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.59 Repeater (All protocols)

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

1.4.60 Router (All protocols)

A device that connects two CEA-709.1-D channels (in a LonWorks system) or two ASHRAE 135 networks and controls traffic between the two by retransmitting signals received from one side onto the other based on the signal destination. Routers are used to subdivide a BACnet internetwork and to limit network traffic.

SECTION 23 09 00 Page 11

1.4.61 Segment (All protocols)

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.62 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.63 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.64 Standard BACnet Services (BACnet)

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

1.4.65 UMCS (All protocols)

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 connecting multiple building or facility control networks to the Monitoring and Control Software.

1.4.66 UMCS Network (All protocols)

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

1.4.67 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 I: 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 I does not specify overall project milestone and

SECTION 23 09 00 Page 12 completion dates.

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 I the abbreviation AAO is used for 'after approval of' and 'ACO' is used for 'after completion of'.

TABLE I. PROJECT SEQUENCING

(FOR NAVY PROJECTS WITH AN ACCEPTANCE ENGINEER)

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

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

7 S Post-Construction QC Checklist ACO #6

8 S Programming Software Configuration Software

Niagara Framework Engineering Tool Niagara Framework Wizards

XIF Files

LNS Plug-Ins

ACO #6

9 S Draft As-Built Drawings ACO #6

SECTION 23 09 00 Page 13

TABLE I. PROJECT SEQUENCING

(FOR NAVY PROJECTS WITH AN ACCEPTANCE ENGINEER)

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

10 S,E PVT Testing Activities As indicated in PART 3 of this Section.

11 S PVT Report As indicated in PART 3 of this Section.

12 S Controller Application Programs Controller Configuration SettingsNS">

Final LNS Database

AAO #11

13 S Final As-Built Drawings AAO #11

14 S O&M Instructions AAO #13

15 S Training Documentation 14 days before scheduled start of #16

16 E Training AAO #14 and #15

17 S Closeout QC Checklist ACO #16

1.6 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING.

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

SECTION 23 09 00 Page 14

Controller Application Programs; G

Configuration Software; G

Controller Configuration Settings; G

Manufacturer's Product Data; G

SD-05 Design Data

Boiler Or Chiller Plant Gateway Request

SD-06 Test Reports

Existing Conditions Report

Start-Up Testing Report;

PVT Report; G

Pre-Construction Quality Control (QC) Checklist; G

Post-Construction Quality Control (QC) Checklist; G

Control Contractor’s Performance Verification Testing Plan; G

Equipment Supplier’s Performance Verification Testing Plan; G

Endurance Testing Results; G

Performance Verification Test 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.

SECTION 23 09 00 Page 15

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 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 3 hard copies of the software user manual for each piece of software.

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 3 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.9 QUALITY CONTROL CHECKLISTS

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

SECTION 23 09 00 Page 16

Government.

1.9.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.9.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.9.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 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 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 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 all BACnet hardware: for each manufacturer, model and version (revision) of DDC Hardware provide the Protocol Implementation Conformance Statement (PICS) in accordance with Section23 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

SECTION 23 09 00 Page 17 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

For products incorporating any wireless capability (including but not limited to radio frequency (RF), infrared and optical), provide products for which wireless capability can be permanently disabled at the device.

Optical and infrared capabilities may be disabled via a permanently affixed opaque cover plate.

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:

2.5.1 Outdoors

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

2.5.2 Mechanical and Electrical Rooms

For enclosures located in mechanical or electrical rooms, provide enclosures meeting NEMA 250 Type 4 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.

SECTION 23 09 00 Page 18

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.

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.

SECTION 23 09 00 Page 19

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 for BACnet systems, and this Section.

3.2.1 Dielectric Isolation

Provide dielectric isolation where dissimilar metals are used for connection and support. Install control system in a matter that provides clearance for control system maintenance by maintaining access space required to calibrate, remove, repair, or replace control system devices.

Install control system such that it does not interfere with the clearance requirements for mechanical and electrical system maintenance.

3.2.2 Penetrations in Building Exterior

Make all penetrations through and mounting holes in the building exterior watertight.

3.2.3 Device Mounting Criteria

Install devices in accordance with the manufacturer's recommendations and as indicated and shown. Provide a weathershield for all devices installed outdoors. Provide clearance for control system maintenance by maintaining access space required to calibrate, remove, repair, or replace control system devices. Provide clearance for mechanical and electrical system maintenance; do not not interfere with the clearance requirements for mechanical and electrical system maintenance.

3.2.4 Labels and Tags

Key all labels and tags to the unique identifiers shown on the As-Built drawings. For labels exterior to protective enclosures provide engraved plastic labels mechanically attached to the enclosure or DDC Hardware.

Labels inside protective enclosures may be attached using adhesive, but must not be hand written. For tags, provide plastic or metal tags mechanically attached directly to each device or attached by a metal chain or wire.

a. Label all Enclosures and DDC Hardware.

b. Tag Airflow measurement arrays (AFMA) with flow rate range for signal output range, duct size, and pitot tube AFMA flow coefficient.

SECTION 23 09 00 Page 20

c. Tag duct static pressure taps at the location of the pressure tap

3.2.5 Surge Protection

3.2.5.1 Power-Line Surge Protection

Protect equipment connected to AC circuits to withstand power-line surges in accordance with IEEE C62.41 . Do not use fuses for surge protection.

3.2.5.2 Surge Protection for Transmitter and Control Wiring

Protect DDC hardware against or provided DDC hardware capable of withstanding surges induced on control and transmitter wiring installed outdoors and as shown. Protect equipment against the following two waveforms:

a. A waveform with a 10-microsecond rise time, a 1000-microsecond decay time and a peak current of 60 amps.

b. A waveform with an 8-microsecond rise time, a 20-microsecond decay time and a peak current of 500 amperes.

3.2.6 Basic Cybersecurity Requirements

3.2.6.1 Passwords

For all devices with a password, change the password from the default password. Do not use the same password for more than one device.

Coordinate selection of passwords with Contracting Officer. Provide a Password Summary Report documenting the password for each device and describing the procedure to change the password for each device. DDC workstations are to require CAC authentication to gain access.

Provide two hardcopies of the Password Summary Report, each copy in its own sealed envelope.

3.2.6.2 Wireless Capability

Unless otherwise indicated, disable wireless capability (including but not limited to radio frequency (RF), infrared and optical) for all devices with wireless capability. Optical and infrared capabilities may be disabled via a permanently affixed opaque cover plate. Password protecting a wireless connections does not meet this requirement; the wireless capability must be disabled.

3.2.6.3 IP Network Physical Security

Install all IP Network media in conduit. Install all IP devices including but not limited to IP-enabled DDC hardware and IP Network Hardware in lockable enclosures.

3.3 DRAWINGS AND CALCULATIONS

Provide drawings in the form and arrangement indicated and shown. Use the same abbreviations, symbols, nomenclature and identifiers shown. Assign a unique identifier as shown to each control system element on a drawing.

When packaging drawings, group schedules by system. When space allows, it is permissible to include multiple schedules for the same system on a single sheet. Except for drawings covering all systems, do not put

SECTION 23 09 00 Page 21 information for different systems on the same sheet.

Submit hardcopy drawings on ISO A1 34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in PDF and in AutoCAD format. In addition, submit electronic drawings in editable Excel format for all drawings that are tabular, including but not limited to the Point Schedule and Equipment Schedule.

a. Submit DDC Contractor Design Drawings consisting of each drawing indicated with pre-construction information depicting the intended control system design and plans. Submit DDC Contractor Design Drawings as a single complete package: 3 hard copies and 3 copies on

CD-ROM.

b. Submit Draft As-Built Drawings consisting of each drawing indicated updated with as-built data for the system prior to PVT. Submit Draft As-Built Drawings as a single complete package: 3 hard copies and 3 copies on CD-ROM.

c. Submit Final As-Built Drawings consisting of each drawing indicated updated with all final as-built data. Final As-Built Drawings as a single complete package: 3 hard copies and 3 copies on CD-ROM.

3.3.1 Sample Drawings

Sample drawings in electronic format are available at the Whole Building Design Guide page for this section:

http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-23-09-00 These drawings may prove useful in demonstrating expected drawing formatting and example content and are provided for illustrative purposes only. Note that these drawings do not meet the content requirements of this Section and must be completed to meet project requirements.

3.3.2 Drawing Index and Legend

Provide an HVAC Control System Drawing Index showing the name and number of the building, military site, State or other similar designation, and Country. In the Drawing Index, list all Contractor Design Drawings, including the drawing number, sheet number, drawing title, and computer filename when used. In the Design Drawing Legend, show and describe all symbols, abbreviations and acronyms used on the Design Drawings. Provide a single Index and Legend for the entire drawing package.

3.3.3 Thermostat and Occupancy Sensor Schedule

Provide a thermostat and occupancy sensor schedule containing each thermostat's unique identifier, room identifier and control features and functions as shown. Provide a single thermostat and occupancy sensor schedule for the entire project.

3.3.4 Valve Schedule

Provide a valve schedule containing each valve's unique identifier, size, flow coefficient Kv (Cv), pressure drop at specified flow rate, spring range, positive positioner range, actuator size, close-off pressure to torque data, dimensions, and access and clearance requirements data. In the valve schedule include actuator selection data supported by calculations of the force required to move and seal the valve, access and clearance requirements. Provide a single valve schedule for the entire

SECTION 23 09 00 Page 22 project. Exterior tags not within lockable enclosure shall be stainless steel or brass for longevity.

3.3.5 Damper Schedule

Provide a damper schedule containing each damper's unique identifier, type (opposed or parallel blade), nominal and actual sizes, orientation of axis and frame, direction of blade rotation, actuator size and spring ranges, operation rate, positive positioner range, location of actuators and damper end switches, arrangement of sections in multi-section dampers, and methods of connecting dampers, actuators, and linkages. Include the AMCA 511 maximum leakage rate at the operating static-pressure differential for each damper in the Damper Schedule. Provide a single damper schedule for the entire project.

3.3.6 Project Summary Equipment Schedule

Provide a project summary equipment schedule containing the manufacturer, model number, part number and descriptive name for each control device, hardware and component provided under this specification. Provide a single project equipment schedule for the entire project.

3.3.7 Equipment Schedule

Provide system equipment schedules containing the unique identifier, manufacturer, model number, part number and descriptive name for each control device, hardware and component provided under this specification.

Provide a separate equipment schedule for each HVAC system.

3.3.8 Occupancy Schedule

Provide an occupancy schedule drawing containing the same fields as the occupancy schedule Contract Drawing with Contractor updated information.

Provide a single occupancy schedule for the entire project.

3.3.9 DDC Hardware Schedule

Provide a single DDC Hardware Schedule for the entire project and including following information for each device.

3.3.9.1 DDC Hardware Identifier

The Unique DDC Hardware Identifier for the device.

3.3.9.2 HVAC System

The system "name" used to…