W912QR24R0021_CF_Specs_Vol2a-0002.pdf

Solicitation For Maintenance/Renovation Army Reserves (MRAR) Building 505, Fort Snelling, Minneapolis, MN

P2: 510375 Design-Build

Specifications Vol. 2a (ATT S&T - 01 78 23)

18 March 2024

W912QR24R0021

Phase 1

17 June 2024

W912QR24R0021-0002

Certified Final

ARIMS: 200A Disposition: Maintain for 15yrs after construction.

W912QR24R0021_CF_Specs_Vol2a-0002

P2# 510375 - Repair Bldg. 505, USAR Center Ft Snelling, Minneapolis, MN

February 2020 version Table of Contents ToC - 1 of 3

CERTIFIED FINAL DESIGN SUBMITTAL

DESIGN/BUILD RFP FOR

Repair Bldg. 505, USAR Center

Fort Snelling, Minneapolis, MN

Table of Contents

SPECIFICATION VOLUME 1 of 3

Division 00 – Procurement and Contracting Requirements

00 10 00 Solicitation – [Offer and Award DF 1442], Price Breakout Schedule 00 21 00 Instructions 00 22 00 Supplementary Instructions

0011x Procedures for Submittal and Evaluation of Offers for Phase One

0011x Procedures for Submittal and Evaluation of Offers for Phase Two

0045 00 Representations and Certifications 00 70 00 Conditions of the Contract 00 73 00 Supplementary Conditions 00 80 00.00 06 Special Provisions Construction Project Signage Submittal Register

Division 01 – General Requirements Specifications

01 02 00.00 48 Statement of Work Table of Contents Part 1 Design Objectives, Functional and Area Requirements Part 2 Design Criteria and Coordination with Local Authorities Part 3 Site Civil Design Part 4 Site Electrical Design Part 5 Landscape Architecture Design Part 6 Architectural and Interior Design Part 7 Structural Design Part 8 Thermal Design Part 9 Plumbing Design Part 10 Electrical Design Part 11 HVAC Design Part 12 Energy Conservation and Sustainable Design Part 13 Fire Protection Design

Part 14 Commissioning and Building Envelope Sealing Performance Requirements

Part 15 Telecommunications Design

February 2020 version Table of Contents ToC - 2 of 3

CERTIFIED FINAL DESIGN SUBMITTAL

Attachment A Preliminary Subsurface Characterization Report Attachment B1 Fire Flow Data (Sloan Boulevard) Attachment B2 Fire Flow Data (Minnehaha Ave) Attachment C Site Photographs

Attachment D Room-by-Room Supplemental Requirements

Attachment E Airport Layout Plan

Attachment F1 Alta Survey Drawings 2005

Attachment F2 City of Minneapolis Utility Maps 2004

Attachment G Existing Building 505 Drawings

Attachment H 2020 Roof As-Built Drawings and Specifications

SPECIFICATION VOLUME 2 of 3

01 02 00.00 48 Attachments to the Statement of Work (continued)

Attachment I Review of Building Enclosure Fort Snelling Building

Attachment J Existing Building 506 Floor Plans

Attachment K1 Hazardous Building Materials and Radon Survey Report

Attachment K2 Asbestos and Lead Paint Inspection Summary

Attachment K3 Additional Radon Test Results Room113B

Attachment L 88th Readiness Division Interior Signage

Attachment M Federal Aviation Administration (FAA) 7460 Report

Attachment N Arms Vault Weapons Rack List (Redacted)

Attachment O UFGS Specification Section 02 41 00 ‘Demolition and

Deconstruction’ (to be edited by the DOR)

February 2020 version Table of Contents ToC - 3 of 3

CERTIFIED FINAL DESIGN SUBMITTAL

Attachment P UFGS Specification Section 02 82 00 ‘Asbestos

Remediation’ (to be edited by the DOR)

Attachment Q UFGS Specification Section 02 83 13.00 06 ‘Lead in

Attachment R UFGS Specification Section 09 67 23.13 ‘Standard Resinous

Flooring’

Attachment S Army Reserve Enterprise Building Control System (EBCS) Design Guide (October 2021)

Attachment T Existing Building 505-506 Connector Link Floor Plans

01 03 00.00 48 Design Submission Requirements After Award 01 04 00.00 48 The Design/Build Process 01 32 01.00 06 Project Schedule 01 33 00 Submittal Procedures 01 33 29.00 06 Sustainability Reporting

Attachment A - LEED Credit Guidance 01 35 26.00 06 Government Safety Requirements

01 42 00 Sources for Reference Publications 01 45 00.15 10 Resident Management System Contractor Mode (RMS CM) 01 45 04.10 06 Contractor Quality Control 01 45 35 Special Inspections 01 46 00.00 06 Total Building Commissioning (Contractor CxA) 01 50 00 Temporary Construction Facilities and Controls 01 57 19.00 Temporary Environmental Controls

01 74 19 Construction Waste Management and Disposal 01 78 23 Operation and Maintenance Data

SPECIFICATION VOLUME 3 of 3

Divisions 03-41 D/B RFP Outline Technical Specifications

See separate Table of Contents with Outline Technical Specifications.

P2 #510375 – Repair Bldg. 505, USAR Center Fort Snelling, Minneapolis, MN

Attachment ‘S’ 01 02 00.00 48

Section 01 02 00.00 48

ATTACHMENT S

ARMY RESERVE ENTERPRISE BUILDING CONTROL SYSTEM (EBCS) DESIGN

GUIDE

(OCTOBER 2021)

Army Reserve Enterprise Building Control System (EBCS)

Design Guide

Updated Revision: October 2021

Table of Contents List of Acronyms

Revision History

1.0 Introduction

1.1. EBCS System Architecture

2.0 Technical Design Guide

2.1 Hardware

2.2 Steps for Integration

2.2.1 Installing JACE

2.2.2 JACE Setup and Configuration

2.2.3 JACE Programming

2.2.4 Graphical User Interface (GUI)

2.2.5 Final Steps

Attachment A. Unified Facilities Guide Specifications

Attachment B. Integration Ready Definition

Attachment C. Site Readiness Assessment

Attachment D. DHCP Reservation

Attachment E. JACE Enclosure Layout

Attachment F. User Profiles

Attachment G. Point Naming Convention

Attachment H. MDMS Standard Meter Data Format

Attachment I. EBCS User Interface Examples

Attachment J. QA/QC Checklist

List of Acronyms ARNET: Army Reserve Network.

BCS: Building Control System

DHCP: Dynamic Host Configuration Protocol

EBCS: Enterprise Building Control System

FAC: Facility

FOXS: Secured communications protocol developed as part of the Tridium Niagara framework

GUI: Graphical User Interface

HTTPS: Hypertext Transfer Protocol Secure

HVAC: Heating, Ventilation, and Air Conditioning

IC: Integration Controller

IP: Internet Protocol

JACE: Java Application Control Engine

JAR: Niagara software operations modules

MAC: Media Access Control

NAC: Network Area Controller

NEMA: National Electrical Manufactures Association

POC: Point of Contact

QA/QC: Quality Assurance / Quality Check

QNX: Operation system

RD: Readiness Division

SRA: Site Readiness Assessment

TCP: Transmission Control Protocol

TLS: Transport Layer Security

UFGS: Unified Facilities Guide Specifications

UL: Underwriters Laboratories

WIFI: Wireless network

Revision History

Version Description Date

January

Initial Version JAN

October

Design Guide: Specs updated to (1) include point naming convention for meters;

(2) requiring the integrator to send trend data to the SQL server

Attachment C: Updated per FY21 SRAs

Attachment H: New attachment (MDMS Standard Meter Data Format)

Attachment J: (1) Removed “Logic/Sequencing” from Graphics section; (2)

Updated “Logic/Sequencing” verbiage on Line 65; (3) Added “JACE Model and

Niagara Version” to Line 72

OCT

1.0 Introduction

The Enterprise Building Control System (EBCS) Technical Design Guide provides the technical details for both EBCS equipment and hardware; and the system configuration. This guide follows and is supplemental to the standards of UFGS 23.09.00 and UFGS 25.10.10 found in Attachment A.

1.1. EBCS System Architecture

The EBCS architecture relies on the Tridium Niagara 4 Framework to provide seamless integration of common and accepted hardware at the building level to communicate with a central server at the

“enterprise” level. The Java Application Control Engine (JACE) is the device that provides a firewall to allow local building controls from various vendors to connect to and communicate across the ARNET

(see Figure 1).

Figure 1. EBCS Simplified Architecture

The NAC/JACE example in Figure 1 shows building equipment (e.g., chillers, air-handlers, etc.) connected to a proprietary vender’s device called a Network Area Controller (NAC). The NAC cannot be connected to the ARNET directly. Therefore, an Integration Controller (IC) JACE serves as a gateway to make the data and control function of the local BCS/NAC available across the network. Sometimes the NAC is also a JACE but dedicated to building-level functions only, thus resulting in a JACE/JACE configuration. Lastly, the JACE/Server configuration uses a single JACE as both the NAC and IC, although users should be careful that these functions do not over-whelm the capabilities of the JACE. This configuration will be determined by the RD with support from the integration contractor.

2.0 Technical Design Guide

This guidance provides a framework for systems that are NAC/JACE, JACE/JACE, and JACE/Server configurations. Integration configuration shall be determined by each Readiness Division (RD). The determination of these configurations relies not only on technical capabilities, but also contractual parameters. Hardware and system responsibilities must be taken into consideration while evaluating the integration configurations.

A BCS is considered “Integration Ready” when the system does not require any additional work before establishing a connection and integrating to the EBCS server. Review Attachment B to determine when the system is integration ready. The primary integration steps are: determining the integration configuration and verifying the JACE, establishing communications between the JACE and the EBCS server, and establishing links to all the points in the existing system.

2.1 Hardware

The IC JACE must meet the following specifications regardless of the integration configuration.

• VYKON JACE 8000 series with an open license. License version must be 4.7 or newer with the

Wi-Fi disabled.

• 5 year SMA maintenance plan

• License should include the workbench tools to be installed on the JACE.

• A dedicated UL-listed, Class 2, 24Vac power supply with a manufacture approved surge protection. The JACE must be powered by a dedicated breaker or off the circuit providing power to the local BCS NAC (if existing).

• Mounted in a NEMA Type III enclosure with associated wiring, fusing, and mounting blocks.

2.2 Steps for Integration

a) Prior to integration, a Site Readiness Assessment (SRA) must be performed by the contractor on all facilities appropriate for integration at that site. The RD POC will provide guidance to the contractor on which facilities require a SRA. The SRA can be found in Attachment C.

2.2.1 Installing JACE

a) The JACE MAC address, serial number, QNX code, and additional information must be entered in the “Request for DHCP Reservation Form” in Attachment D and submitted to the RD POC and

ARIMD EBCS Sustainability Manager for DHCP reservation.

b) Integration contractor shall work with the RD POC to determine the ideal location of the JACE.

c) The contractor shall connect the JACE to the local BCS NAC (if existing) and provide all Cat 6E cabling to the ARNET switch.

d) Any onsite BCS computers inside the building used for control or monitoring need to be connected on the Port 2 side of the JACE and remain operational.

e) Label JACE with station name and Port 1 and Port 2 MAC address

f) Review Attachment E for a JACE enclosure layout for further technical installation guidance.

2.2.2 JACE Setup and Configuration

a) A Cat 6E cable must be plugged into Comm 1 of the JACE from the ARNET switch.

b) Only the following runtime profiles shall be enabled.

i. RUNTIME: Module JARs having core runtime Java classes only, no user interface.

ii. UX: Module JARs having lightweight HTML5+JavaScript+CSS user interface only.

iii. WB: Module JARs having Workbench or Workbench Applet user interface classes.

c) The contractor will use a standardized station name and hostname that will be provided by the

RD POC. Station name and hostname will adhere to the following format.

i. HVAC Controls Station Name: FACID_FACNUM_C01

ii. MDMS Station Name: FACID_FACNUM_M01

d) A station template will be provided by the RD POC that must be used by the contractor.

e) All communications between Niagara devices and the EBCS server will be secured with SSL, using the following points.

Interface Protocol Specified Port

Internet Browser HTTPS 443

Niagara Station FOXS 4911

Niagara Station TLSv1 5011

f) When configuring the JACE in the TCP/IP configuration screen, Comm 1 will be set for DHCPv4 enabled. DHCPv6 will be disabled. Configure Hostname to match station name.

i. HVAC Controls Hostname: FACID-FACNUM-C01

ii. MDMS Hostname: FACID-FACNUM-M01

g) When configuring the Jace in the TCP/IP config screen, Comm 2 on the JACE will be configured with a standardized static IP address and subnet mask to allow for a local laptop to be connected for future onsite work.

h) The contractor will refer to the document titled “User Profiles” (Attachment F) for configuration of user name and password combinations and system passphrases.

2.2.3 JACE Programming

a) The contractor will use a standardized point naming convention in the JACE for all data points as listed in “Point Naming Convention” in Attachment G for HVAC and auxiliary equipment.

b) The contractor will use a standardized point naming convention for meter points in accordance with the MDMS Variable from Table 1 in Attachment H.

c) The contractor will add alarm extensions to the data points as designated in the “Point Naming

Convention”. Alarm messages will be added to each alarm as outlined below.

i. Out of Range (Analog Points). The message will display the current value of the point and either the high or low threshold.

ii. Command Failure (Boolean Point). The message will display the current command of the point and the current status.

iii. Change of Value (Boolean or Enumerated Points). The message will display the current value of the point.

iv. Change of Status (Niagara Components). The message will display the current value of the component.

d) The contractor will add trend extensions to the data points as designated in the “Point Naming

Convention Guide”. The data types that will be used for the trend extension are outlined below.

i. Interval Trends. This trend type will be assigned to analog points that are fast changing in nature. The trend extension will be configured to record a data point every 5-15 minutes.

ii. Change-of-Value Trends. This trend type will be assigned to either analog or Boolean points that are not fast changing in nature. The trend extension will automatically be configured to record a data point whenever there is a change of value in the point.

e) The trend extension configuration will be set to allow for a minimum three-day rolling window of data, but not to exceed 1800 records per JACE.

f) Trend extensions must be added to the Rdbms Network to be exported to the EBCS SQL Server.

i. Trend extensions must be added to the Rdbms Network station in accordance to the associated Army Reserve Division and controller type. For example, BCS trend extensions for a building in the 63rd DIV will be added to the “63RD_EBCS” station.

ii. A New Folder must be created for the new trend extensions in the Rdbms Network station for data organization purposes.

iii. Trend extensions added to any of the “_MDMS” Rdbms Network stations must be configured to export hourly for all seven days of the week starting at 12:00 A.M. EST.

iv. Trend extensions added to any of the “_EBCS” Rdbms Network stations must be configured to export as follows:

i. 63RD: Daily at 1:20 A.M. EST for all seven days of the week

ii. 81RD: Daily at 2:20 A.M. EST for all seven days of the week

iii. 88RD: Daily at 4:20 A.M. EST for all seven days of the week

iv. 99RD: Daily at 3:20 A.M. EST for all seven days of the week

2.2.4 Graphical User Interface (GUI)

a) A station template will be provided by the RD POC that contains the GUI package that must be used by the contractor.

b) The GUI package will provide template graphics for system and equipment level screens, layout, and functionality. Attachment I provides examples of the graphics.

c) The contractor will edit the equipment level screens to be representative of the equipment configuration and piping/ducting layout.

d) Floorplans will be provided by the RD POC will be added to the floorplan graphics by the contractor.

i. The contractor will implement a floorplan color presentation to match each zone as served by the HVAC system. The floorplans in the template station can be used as an example.

ii. The contractor will implement a zone temperature deviation calculation for each zone and integrate the deviation into the floorplans. The deviation scale will be setup as followed. The floorplans in the template station can be used as an example.

Green: when zone is +/- 2°F of setpoint

Yellow: when zone is above setpoint by 2-4°F

Orange: when zone is above setpoint by 4-6°F

Red: when zone is above setpoint by more than 6°F

Light blue: when zone is below setpoint by 2-4°F

Blue: when zone is below setpoint by 4-6°F

Dark blue: when zone is below setpoint by more than 6°F

e) Contractor shall install all building graphics on the JACE. If the JACE was login into at the building the graphics from the building down to the equipment should look the same as the server level graphics.

2.2.5 Final Steps

a) The contractor will work with the RD POC to test and verify the access and basic functionality of the new JACE is satisfactory while accessing the system remotely.

b) The contractor will provide the following to verify quality workmanship.

i. Use hole-knockout protectors, properly aligned holes, and do not leave any jagged edges.

ii. Submit photos of before and after JACE installation including close up images of the cable connections at the JACE and at the local BCS (if existing), cable pathways, and all enclosure penetrations.

iii. Completed QA/QC checklist found in Attachment J.

iv. Red-lines of building layouts and equipment manuals/documentation in Microsoft Office format.

Attachment A. Unified Facilities Guide Specifications The EBCS framework and all underlaying BCS must be in accordance to the Unified Facilities Guide Specification (UFGS) from the Department of Defense. Below are the links for the full versions of the applicable specification. Amended examples are in Attachment A.

UFGS 23 09 00: Instrumentation and Control for HVAC http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-23-09-00

UFGS 25 10 10: Utility Monitoring and Control System (UMCS) Front End and Integration http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-25-10-10

Attachment B. Integration Ready Definition Attachment B provides the definition of systems that are considered “Integration Ready”. A BCS is considered

Integration Ready if it meets all the critical criteria without needing additional work.

Attachment C. Site Readiness Assessment Attachment C is the SRA workbook that must be completed before any system is integrated to the EBCS. The primary functions of the SRA are to:

• Gather details about the current BCS (vendor, software, IP, etc)

• Perform functional testing on the BCS in relation to the integrated mechanical equipment

• Determine if the BCS is Integration Ready

• Complete an onsite checklist on BCS, HVAC, networking, and metering details

• Draft preliminary list of expected costs

Attachment D. DHCP Reservation Attachment D is the form that can be used for submitting DHCP and IP reservations and assist RD’s with technical documentation. The form includes the following fields:

• FAC ID and Building

• Panel Name

• Tridium Jace Model

• MAC Address Port 1 & 2

• Serial Number

• QNX Code

• Station Passphrase

• Host ID#

• Platform Username & Password

• Station Admin Username &Password

• DHCP Reservation

• Port 1 & 2 DHCP IP Address

• Port 1 & 2 DHCP Subnet Mask

Attachment E. JACE Enclosure Layout Attachment E provides schematics for potential parts list and JACE wiring diagrams.

Attachment F. User Profiles Attachment F is the user profile sheet detailing the specifications for credentials, roles, and accessibility for each user.

These will be defined by each RD and will be specific to the needs of each RD.

Attachment G. Point Naming Convention Attachment G provides the naming conventions for control points. Additionally, this table indicates which points should be trending (storing data histories) and which should be generating alarms on faults.

Attachment H. MDMS Standard Meter Data Format Attachment H is the MDMS Standard Meter Data Format to provide the guidance for which MDMS metering data points must be named when they are integrated to EBCS.

Attachment I. EBCS User Interface Examples Attachment I provides examples of the user interface. Exact images are subject to change, so the images are to provide a general understanding. An RD-provided station template will be used that contains the required graphics package.

Attachment J. QA/QC Checklist Attachment J is the QA/QC checklist to be completed after EBCS integration is complete.

THIS IS A DRAFT DOCUMENT EDITED BY PNNL TO

1) EXCLUDE ANY SPECS IN REGARDS TO LON/LONWORKS

2) ADD SPECS RELATED TO THE EBCS

DOCUMENT IS CURRENTLY FOR REFERENCE ONLY AND SHALL NOT BE USED FOR

SOLICITATION OR PROJECT DEVELOPMENT.

USACE / NAVFAC / AFCEC / NASA UFGS 23 09 00 (February 2019)

Preparing Activity: USACE Superseding

UFGS-23 09 00 (November 2015)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated July 2019

SECTION TABLE OF CONTENTS

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

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

02/19

PART 1 GENERAL

1.1 SUMMARY

1.1.1 System Requirements

1.1.2 End to End Accuracy

1.1.3 Verification of Dimensions

1.1.4 Drawings

1.2 RELATED SECTIONS

1.3 REFERENCES

1.4 DEFINITIONS

1.4.1 Alarm Generation (All protocols)

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

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

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

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

1.4.8 BACnet Broadcast Management Device (BBMD) (BACnet)

1.4.9 BACnet/IP (BACnet)

1.4.10 BACnet Internetwork (BACnet)

1.4.11 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

1.4.12 BACnet Network (BACnet)

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

1.4.14 BACnet Segment (BACnet)

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

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

1.4.17 BACnet Testing Laboratories (BTL) (BACnet)

1.4.18 BACnet Testing Laboratories (BTL) Listed (BACnet)

1.4.19 Binary (All protocols)

1.4.21 Broadcast (BACnet)

1.4.22 Building Control Network (BCN) (All protocols)

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

1.4.25 Commandable (All protocols)

1.4.26 Commandable Objects (BACnet)

1.4.27 Configurable (All protocols)

1.4.29 Control Logic Diagram (All protocols)

1.4.30 Device (BACnet)

1.4.31 Device Object (BACnet)

1.4.32 Device Profile (BACnet)

1.4.33 Digital Controller (All protocols)

1.4.34 Direct Digital Control (DDC) (All protocols)

1.4.38 Field Point of Connection (FPOC) (All protocols)

1.4.39 Fox Protocol (Niagara Framework)

1.4.41 Gateway (All protocols)

1.4.43 IEEE 802.3 Ethernet (All protocols)

1.4.44 Internet Protocol (IP, TCP/IP, UDP/IP) (All protocols)

1.4.45 Input/Output (I/O) (All protocols)

1.4.46 I/O Expansion Unit (All protocols)

1.4.47 IP subnet (All protocols)

1.4.48 JACE (Niagara Framework)

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

1.4.50 Local Display Panels (LDPs) (All protocols)

1.4.58 MAC Address (All protocols)

1.4.59 Master-Slave/Token-Passing (MS/TP) (BACnet)

1.4.60 Monitoring and Control (M&C) Software (All protocols)

1.4.61 Network Number (BACnet)

1.4.64 Niagara Framework (Niagara Framework)

1.4.65 Niagara Framework Supervisory Gateway (Niagara Framework)

1.4.69 Object (BACnet)

1.4.70 Object Identifier (BACnet)

1.4.71 Object Instance (BACnet)

1.4.72 Object Properties (BACnet)

1.4.73 Operator Configurable (All protocols)

1.4.74 Override (All protocols)

1.4.75 Packaged Equipment (All protocols)

1.4.76 Packaged Unit (All protocols)

1.4.77 Performance Verification Test (PVT) (All protocols)

1.4.78 Physical Segment (BACnet)

1.4.79 Polling (All protocols)

1.4.80 Points (All protocols)

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

1.4.83 Proprietary (BACnet)

1.4.84 Protocol Implementation Conformance Statement (PICS) (BACnet)

1.4.85 Repeater (All protocols)

1.4.86 Router (All protocols)

1.4.87 Segment (All protocols)

1.4.89 Standard BACnet Objects (BACnet)

1.4.90 Standard BACnet Properties (BACnet)

1.4.91 Standard BACnet Services (BACnet)

1.4.99 UMCS (All protocols)

1.4.100 UMCS Network (All protocols)

1.4.101 Writable Property (BACnet)

1.5 PROJECT SEQUENCING

1.6 SUBMITTALS

1.7 DATA PACKAGE AND SUBMITTAL REQUIREMENTS

1.8 SOFTWARE FOR DDC HARDWARE AND GATEWAYS

1.8.1 Programming Software

1.8.2 Controller Application Programs

1.8.3 Configuration Software

1.8.4 Controller Configuration Settings

1.8.5 Programming Software

1.8.6 Controller Application Programs

1.8.9 Niagara Framework Supervisory Gateway Backups

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

1.8.11 Certificate of Networthiness Documentation

1.9 BOILER OR CHILLER PLANT GATEWAY REQUEST

1.10 QUALITY CONTROL CHECKLISTS

1.10.1 Pre-Construction Quality Control (QC) Checklist

1.10.2 Post-Construction Quality Control (QC) Checklist

1.10.3 Closeout Quality Control (QC) Checklist

PART 2 PRODUCTS

2.1 GENERAL PRODUCT REQUIREMENTS

2.2 PRODUCT DATA

2.2.1 XIF Files

2.3 OPERATION ENVIRONMENT

2.4 WIRELESS CAPABILITY

2.5 ENCLOSURES

2.5.1 Outdoors

2.5.2 Mechanical and Electrical Rooms

2.5.3 Other Locations

2.6 WIRE AND CABLE

2.6.1 Terminal Blocks

2.6.2 Control Wiring for Binary Signals

2.6.3 Control Wiring for Analog Signals

2.6.4 Power Wiring for Control Devices

2.6.5 Transformers

PART 3 EXECUTION

3.1 EXISTING CONDITIONS

3.1.1 Existing Conditions Survey

3.1.2 Existing Equipment Downtime

3.1.3 Existing Control System Devices

3.2 INSTALLATION

3.2.1 Dielectric Isolation

3.2.2 Penetrations in Building Exterior

3.2.3 Device Mounting Criteria

3.2.4 Labels and Tags

3.2.5 Surge Protection

3.2.5.1 Power-Line Surge Protection

3.2.5.2 Surge Protection for Transmitter and Control Wiring

3.2.6 Basic Cybersecurity Requirements

3.2.6.1 Passwords

3.2.6.2 Wireless Capability

3.2.6.3 IP Network Physical Security

3.3 DRAWINGS AND CALCULATIONS

3.3.1 Sample Drawings

3.3.2 Drawing Index and Legend

3.3.3 Thermostat and Occupancy Sensor Schedule

3.3.4 Valve Schedule

3.3.5 Damper Schedule

3.3.6 Project Summary Equipment Schedule

3.3.7 Equipment Schedule

3.3.8 Occupancy Schedule

3.3.9 DDC Hardware Schedule

3.3.9.1 DDC Hardware Identifier

3.3.9.2 HVAC System

3.3.9.3.1 Network Address

3.3.9.3.2 Unique Node ID

3.3.9.4 BACnet Device Information

3.3.9.4.1 Device Object Identifier

3.3.9.4.2 Network Number

3.3.9.4.3 MAC Address

3.3.9.4.4 BTL Listing

3.3.9.4.5 Proprietary Services Information

3.3.9.4.6 Alarming Information

3.3.9.4.7 Scheduling Information

3.3.9.4.8 Trending Information

3.3.9.5 Niagara Station ID

3.3.10 Points Schedule

3.3.10.1 Point Name

3.3.10.2 Description

3.3.10.3 DDC Hardware Identifier

3.3.10.4 Settings

3.3.10.5 Range

3.3.10.6 Input or Output (I/O) Type

3.3.10.7 Object and Property Information

3.3.10.8 Primary Point Information: SNVT Name

3.3.10.9 Primary Point Information: SNVT Type

3.3.10.10 Niagara Station ID

3.3.10.11 Network Data Exchange Information (Gets Data From, Sends Data To)

3.3.10.12 Override Information (Object Type and Instance Number)

3.3.10.13 Override Information (SNVT Name and Type)

3.3.10.14 Trend Object Information

3.3.10.15 Alarm Information

3.3.10.16 Configuration Information

3.3.11 Riser Diagram

3.3.12 Control System Schematics

3.3.13 Sequences of Operation[ Including Control Logic Diagrams]

3.3.14 Controller, Motor Starter and Relay Wiring Diagram

3.4 CONTROLLER TUNING

3.5 START-UP

3.5.1 Start-Up Test

3.5.1.1 Systems Check

3.5.1.1.1 Step 1 - System Inspection

3.5.1.1.2 Step 2 - Calibration Accuracy Check

3.5.1.1.3 Step 3 - Actuator Range Check

3.5.1.2 Weather Dependent Test

3.5.2 Start-Up Testing Report

3.5.3 Draft LNS Database

3.6 PERFORMANCE VERIFICATION TEST (PVT)

3.6.1 PVT Procedures

3.6.1.1 Sensor Accuracy Checks

3.6.1.2 Temporary Trending Hardware

3.6.1.3 Endurance Test

3.6.1.4 PVT Equipment List

3.6.2 PVT Execution

3.6.3 PVT Report

3.6.4 Final LNS Database

3.7 PERFORMANCE VERIFICATION TESTING

3.7.1 General

3.7.2 Performance Verification Testing and Commissioning

3.7.3 Performance Verification Testing of Equipment with Packaged Controls

3.7.3.1 Controls Contractor Responsibilities

3.7.3.2 Equipment Supplier Responsibilities

3.7.4 Sequencing of Performance Verification Testing Activities

3.7.4.1 PVT Testing for Multi-Phase Construction

3.7.5 Control Contractor's Performance Verification Testing Plan

3.7.6 Performance Verification Testing Sample Size

3.7.6.1 Selection of Systems to Test

3.7.7 Conducting Performance Verification Testing

3.7.8 Endurance Testing

3.7.8.1 General

3.7.8.2 Hardware

3.7.8.3 Endurance Testing Results Format

3.7.8.4 Endurance Testing Start, Duration, and Frequency

3.7.8.4.1 Points Trended at One Minute Intervals

3.7.8.4.2 Points Trended at 15 Minute Intervals

3.7.8.5 Trended Control Points

3.7.8.5.1 Air-Cooled Chiller Chilled Water System.

3.7.8.5.2 HVAC Heating Hot Water System with Boiler.

3.7.8.5.3 HVAC Heating Hot Water System with Steam-to-Hot Water Heat Exchanger.

3.7.8.5.4 Air Handling Unit with Relief Air Fan

3.7.8.5.5 Dedicated Outside Air System (DOAS)

3.7.8.5.6 Series Fan-Powered Supply Air Terminal Units

3.7.8.6 Endurance Testing Sample Size

3.7.8.6.1 Selection of Systems to Test

3.7.9 Performance Verification Test Report

3.8 FINAL LNS DATABASE

3.9 OPERATION AND MAINTENANCE (O&M) INSTRUCTIONS

3.10 MAINTENANCE AND SERVICE

3.10.1 Description of Work

3.10.2 Personnel

3.10.3 Scheduled Inspections

3.10.4 Scheduled Work

3.10.5 Emergency Service

3.10.6 Operation

3.10.7 Records and Logs

3.10.8 Work Requests

3.10.9 System Modifications

3.11 TRAINING

3.11.1 Training Documentation

3.11.2 Training Course Content

3.11.3 Training Documentation Submittal Requirements

ATTACHMENTS:

QC Checklist for BACnet Systems QC Checklist for Niagara Framework Based BACnet Systems

QC CHECKLIST FOR NIAGARA FRAMEWORK BASED LONWORKS SYSTEMS

QC CHECKLIST FOR BACNET SYSTEMS

QC CHECKLIST FOR NIAGARA FRAMEWORK BASED BACNET SYSTEMS

-- End of Section Table of Contents -- SECTION 23 09 00 Page 6

USACE / NAVFAC / AFCEC / NASA UFGS 23 09 00 (February 2019)

Preparing Activity: USACE Superseding

UFGS-23 09 00 (November 2015)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated July 2019

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

02/19

NOTE: This guide specification covers the requirements for HVAC control systems, including tailoring options for LNS-Based LonWorks, Niagara

Framework-Based LonWorks, BACnet and Niagara

Framework-Based BACnet systems.

Adhere to UFC 1-300-02 Unified Facilities Guide Specifications (UFGS) Format Standard when editing this guide specification or preparing new project specification sections. Edit this guide specification for project specific requirements by adding, deleting, or revising text. For bracketed items, choose applicable item(s) or insert appropriate information.

Remove information and requirements not required in respective project, whether or not brackets are present.

Comments, suggestions and recommended changes for this guide specification are welcome and should be as a Criteria Change Request (CCR). CCRs for this specification can be submitted through the Whole

Building Design Guide page for this section:

http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-

NOTE: The use of this UFGS, and the design of control systems, must be in accordance with UFC

3-410-02, DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS. This specification MUST be used in conjunction with UFGS 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS or UFGS 23 09 23.02 BACNET

DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS as well as UFGS 23 09 13

INSTRUMENTATION AND CONTROL DEVICES FOR HVAC and

UFGS 23 09 93 SEQUENCES OF OPERATION FOR HVAC

CONTROL in order to specify a complete and

SECTION 23 09 00 Page 7 functional system.

Except as otherwise indicated, edit this guide specification for project specific requirements ONLY by selecting appropriate tailoring options, choosing applicable items(s), or inserting appropriate information in bracketed items. Do not make edits outside of bracketed items except as noted without prior approval as indicated in UFC 3-410-02 DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING SYSTEMS.

When used with UFGS 23 09 23.01 LONWORKS DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS, this specification covers installation of local (building-level) controls using LonWorks-based

DDC using either LNS or the Niagara Framework.

When used with UFGS 23 09 23.02 BACNET DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS, this specification covers installation of local (building-level) controls using BACnet-based

DDC, and may include the Niagara Framework.

This specification is primarily intended for building level control systems which are to be integrated into a Utility Monitoring and Control

System (UMCS) as specified in Section 25 10 10

UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT

END AND INTEGRATION (where Section 25 10 10 has also used the matching protocol tailoring option).

For projects that require the building system to provide UMCS functionality (without connection to a

UMCS), include the necessary requirements from

Section 25 10 10 UTILITY MONITORING AND CONTROL

SYSTEM (UMCS) FRONT END AND INTEGRATION in the project specifications.

Template drawings in electronic format for use with this section are available online at the Whole

Building Design Guide page for this section:

http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-

NOTE: This specification makes use of SpecsIntact

Tailoring Options. This note describes these options and how to use them.

"TAILORING OPTION NOTES" Tailoring Option

Each time tailoring options are used there is an accompanying designer note describing the text that is tailored. As this Section makes heavy use of tailoring options there are many of these notes and they can distract from designer notes describing other decisions. The designer notes describing tailoring options are all in a "TAILORING OPTION

NOTES" tailoring option which can be hidden (in

SpecsIntact select View-Tailoring Options and then

SECTION 23 09 00 Page 8 deselect "TAILORING OPTION NOTES") once this section is tailored and the tailoring option notes are no longer needed.

Protocol Tailoring Options

This specification includes tailoring options for selection of protocol, and whether the Niagara

Framework is required. There are four tailoring options, of which EXACTLY ONE must be used (the remaining three must be DESELECTED when managing tailoring options):

1) BACNET: A (non-Niagara Framework) BACnet system: When this tailoring option is included this Section will reference

Section 23 09 23.02 BACNET DIRECT DIGITAL

CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS. Use UFGS 23 09 23.02 with the "NOT Niagara Framework" tailoring option selected (DESELECT the "Niagara

Framework" tailoring option in

UFGS 23 09 23.02).

2) LNS: A LonWorks system using LNS. When this tailoring option is included this

Section will reference Section 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND

OTHER BUILDING CONTROL SYSTEMS.

Use UFGS 23 09 23.01 with the "LNS" tailoring option selected (and DESELECT the

"Niagara Framework" tailoring option in

UFGS 23 09 23.01).

3) NIAGARA BACNET: A Niagara Framework system using BACnet controllers. When this tailoring option is included this

Section will reference Section 23 09 23.02

BACNET DIRECT DIGITAL CONTROL FOR HVAC AND

OTHER BUILDING CONTROL SYSTEMS.

Use UFGS 23 09 23.02 with the "Niagara

Framework" tailoring option selected (DESELECT the "NOT Niagara Framework" tailoring option in UFGS 23 09 23.02).

4) NIAGARA LONWORKS: A Niagara Framework system using LonWorks controllers. When this tailoring option is included this

Section will reference Section 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND

OTHER BUILDING CONTROL SYSTEMS.

Use UFGS 23 09 23.01 with the "Niagara

Framework" tailoring option selected (DESELECT the "LNS" tailoring option in

UFGS 23 09 23.01).

You have currently included the following options:

NIAGARA BACNET

NIAGARA LONWORKS

BACNET

SECTION 23 09 00 Page 9

LNS

If you don't see any text between dashes above, you have DESELECTED all protocol tailoring option and this specification is not valid. SELECT ONE of the tailoring options.

If you see more than one line of text between the dashes above you have left multiple tailoring options related to protocol selected. DESELECT one or more tailoring options until a SINGLE protocol tailoring option is selected.

Service Tailoring Option

This specification also includes tailoring options for the Service (Air Force, Army, Navy) the specification is used for. There is a "NAVY

ACCEPTANCE ENGINEER" tailoring option that is used on Navy projects which have an Acceptance Engineer.

There is a "Service Generic" tailoring option that can also be used when none of the other services tailoring options apply. Only ONE of the five tailoring options related to the services should be used. You have currently included the following options:

AIR FORCE

ARMY

NAVY

NAVY WITH ACCEPTANCE ENGINEER

SERVICE GENERIC

If more than one item appears between the dashes above you have included more than one services tailoring option and need to DESELECT all but one of them. If there is no text between the dashes above you have not included any services tailoring options. Select ONE of the services tailoring options for inclusion.

PART 1 GENERAL

1.1 SUMMARY

NOTE: If sequences of operation are provided in

Section 23 09 93 SEQUENCES OF OPERATION FOR HVAC

CONTROL, keep the bracketed text referring to that section. If Section 23 09 93 is not provided remove the bracketed text.

NOTE: This subpart uses tailoring options:

1) Text referring to UFGS 23 09 23.01 will be included if the LNS or NIAGARA LONWORKS tailoring

SECTION 23 09 00 Page 10 options are selected.

2) Text referring to UFGS 23 09 23.02 will be included if the BACNET or NIAGARA BACNET tailoring options are selected.

Provide a complete Direct Digital Control (DDC) system, except for the Front End which is specified in Section 25 10 10 UTILITY MONITORING AND CONTROL (UMCS) FRONT END AND INTEGRATION, 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 93 SEQUENCES OF OPERATION FOR HVAC CONTROL,] Section 23 09 23.02

BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

for BACnet or Niagara BACnet 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:

NOTE: Select where sequences of operation are specified. UFGS 23 09 93 SEQUENCES OF OPERATION FOR

HVAC CONTROL contains template sequences of operation.

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.

NOTE: The requirement ", unless otherwise pre-approved by the Contracting Officer" in the following paragraph is required only for Air Force projects and is in AIR FORCE tailoring tags.

(Deselect the AIR FORCE tailoring option if not specifying an Air Force owned 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.

SECTION 23 09 00 Page 11

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.

NOTE: The following list paragraph is included only when the NIAGARA BACNET or NIAGARA LONWORKS tailoring options are selected.

h. All Niagara Framework components have an unrestricted interoperability license with a Niagara Compatibility Statement (NiCS) following the Tridium Open NiCS Specification and have 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.2 End to End Accuracy

NOTE: This paragraph is referenced (by subpart title) elsewhere in the specification. If this paragraph is edited, removed, renamed, etc. make sure to verify that all references to it are updated as needed.

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

NOTE: Select whether Section 01 91 00.15 10 TOTAL

BUILDING COMMISSIONING is used for commissioning or provide appropriate reference to the Commissioning specification.

NOTE: This subpart used tailoring options:

1) Text referring to UFGS 23 09 23.01 is included only when the LNS or NIAGARA LONWORKS tailoring option is selected.

2) Text referring to UFGS 23 09 23.02 is included only when the BACNET or NIAGARA BACNET tailoring option is selected.

Related work specified elsewhere:

a. Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS for BACnet systems with or without Niagara Framework.

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

c. Section 23 09 93 SEQUENCES OF OPERATIONS FOR HVAC CONTROLS

d. Section 25 08 10 UTILITY MONITORING AND CONTROL SYSTEMS TESTING

e. Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEMS (UMCS) FRONT

END AND INTEGRATION

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

g. [Section 01 91 00.15 10 TOTAL BUILDING COMMISSIONING][_____]

1.3 REFERENCES

NOTE: This paragraph is used to list the publications cited in the text of the guide specification. The publications are referred to in the text by basic designation only and listed in this paragraph by organization, designation, date, and title.

Use the Reference Wizard's Check Reference feature when you add a Reference Identifier (RID) outside of

SECTION 23 09 00 Page 13 the Section's Reference Article to automatically place the reference in the Reference Article. Also use the Reference Wizard's Check Reference feature to update the issue dates.

References not used in the text will automatically be deleted from this section of the project specification when you choose to reconcile references in the publish print process.

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 ASHRAE FUN SI (2017) Fundamentals Handbook, SI Edition

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-D (2014) Control Network Protocol Specification CEA-709.3 (1999; R 2015) Free-Topology Twisted-Pair Channel 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 SECTION 23 09 00 Page 14

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide or newest User Guide from Niagara Tridium Open NiCS (2005) Understanding the NiagaraAX or newest Guide from Niagara Compatibility Statement (NiCS)

UNDERWRITERS LABORATORIES (UL)

UL 5085-3 (2006; Reprint Nov 20121) Low Voltage Transformers - Part 3: Class 2 and Class 3 Transformers

1.4 DEFINITIONS

NOTE: Other sections (UFGS 23 09 23.01 LONWORKS

DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS, UFGS 23 09 23.02 BACNET DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS, UFGS 23 09 13 INSTRUMENTATION AND CONTROL

DEVICES FOR HVAC, UFGS 23 09 93 SEQUENCES OF

OPERATION FOR HVAC CONTROL) reference this section for relevant 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.

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

NOTE: The following subparts use tailoring options to include or exclude terms based on the which tailoring options are selected. Each individual term does not have a designer note associated with it as this makes the list of definitions very difficult to read. The parenthesis after the subpart title will also indicate when the term is in tailoring option tags:

1) Subparts including "(LonWorks)" in the title are included when the LNS or NIAGARA LONWORKS tailoring options are selected.

2) Subparts including "(BACnet)" in the title are included when the BACNET or NIAGARA BACNET tailoring options are selected.

3) Subparts including "(Niagara Framework)" in the title are included when the NIAGARA BACNET or

NIAGARA LONWORKS tailoring options are selected.

4) Subparts including "(All protocols)" are not in

SECTION 23 09 00 Page 15 any tailoring options and are always included.

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 (such as a user interface) - see paragraph ALARM ROUTING in Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS)

FRONT END AND INTEGRATION.

1.4.1a Alarm extensions will be added to the data points as designated in the “Point Naming Convention”. Alarm messages will be added to each alarm as outlined

i. Out of Range (Analog Points). The message will display the current value of the point and either the high or low threshold.

ii. Command Failure (Boolean Point). The massage will display the current command of the point and the current status.

iii. Change of Value (Boolean or Enumerated Points). The message will display the current value of the points.

iv. Change of Status (Niagara Components). The message will display the current value of the component.

1.4.4 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.5 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.6 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.7 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.