DRAFT_ATTACHMENT_6.pdf

DRAFT

USACE / NAVFAC / AFCEC / NASA UFGS 23 09 00 (November 2015)

Change 2 - 08/18

Preparing Activity: USACE Superseding UFGS-23 09 23 (May 2011) UFGS-23 09 23.13 20 (August 2009)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated July 2018

SECTION TABLE OF CONTENTS

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

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

11/15

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

1.4.2 Application Generic Controller (AGC)

1.4.3 Application Specific Controller (ASC)

1.4.4 Building Automation and Control Network (BACnet)

1.4.5 BACnet Advanced Application Controller (B-AAC)

1.4.6 BACnet Application Specific Controller (B-ASC)

1.4.7 BACnet Building Controller (B-BC)

1.4.8 BACnet Broadcast Management Device (BBMD)

1.4.9 BACnet/IP

1.4.10 BACnet Internetwork

1.4.11 BACnet Interoperability Building Blocks (BIBBs)

1.4.12 BACnet Network

1.4.13 BACnet Operator Display (B-OD)

1.4.14 BACnet Segment

1.4.15 BACnet Smart Actuator (B-SA)

1.4.16 BACnet Smart Sensor (B-SS)

1.4.17 BACnet Testing Laboratories (BTL)

1.4.18 BACnet Testing Laboratories (BTL) Listed

1.4.19 Binary

1.4.20 Binding

1.4.21 Broadcast

1.4.22 Building Control Network (BCN)

1.4.23 Building Point of Connection (BPOC)

1.4.24 Channel

SECTION 23 09 00 Page 1

1.4.25 Commandable

1.4.26 Commandable Objects

1.4.27 Configurable

1.4.28 Configuration Property

1.4.29 Control Logic Diagram

1.4.30 Device

1.4.31 Device Object

1.4.32 Device Profile

1.4.33 Digital Controller

1.4.34 Direct Digital Control (DDC)

1.4.35 Domain

1.4.36 Explicit Messaging

1.4.37 External Interface File (XIF)

1.4.38 Field Point of Connection (FPOC)

1.4.39 Fox Protocol

1.4.40 Functional Profile

1.4.41 Gateway

1.4.42 General Purpose Programmable Controller (GPPC)

1.4.43 IEEE 802.3 Ethernet

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

1.4.45 Input/Output (I/O)

1.4.46 I/O Expansion Unit

1.4.47 IP subnet

1.4.48 JACE (Niagara Framework)

1.4.49 Local-Area Network (LAN)

1.4.50 Local Display Panels (LDPs)

1.4.51 LonMark

1.4.52 LonMark International

1.4.53 LonMark Interoperability Association

1.4.54 LonMark Object

1.4.55 LonWorks

1.4.56 LonWorks Network Services (LNS)

1.4.57 LonWorks Network Services (LNS) Plug-in

1.4.58 MAC Address

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

1.4.60 Monitoring and Control (M&C) Software

1.4.61 Network Number

1.4.62 Network Variable

1.4.63 Network Configuration Tool

1.4.64 Niagara Framework (Niagara Framework)

1.4.65 Niagara Framework Supervisory Gateway (Niagara Framework)

1.4.66 Node

1.4.67 Node Address

1.4.68 Node ID

1.4.69 Object

1.4.70 Object Identifier

1.4.71 Object Instance

1.4.72 Object Properties

1.4.73 Operator Configurable

1.4.74 Override

1.4.75 Packaged Equipment

1.4.76 Packaged Unit

1.4.77 Performance Verification Test (PVT)

1.4.78 Physical Segment

1.4.79 Polling

1.4.80 Points

1.4.81 Program ID

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

1.4.83 Proprietary

SECTION 23 09 00 Page 2

1.4.84 Protocol Implementation Conformance Statement (PICS)

1.4.85 Repeater

1.4.86 Router

1.4.87 Segment

1.4.88 Service Pin

1.4.89 Standard BACnet Objects

1.4.90 Standard BACnet Properties

1.4.91 Standard BACnet Services

1.4.92 Standard Configuration Property Type (SCPT)

1.4.93 Standard Network Variable Type (SNVT)

1.4.94 Subnet

1.4.95 TP/FT-10

1.4.96 TP/XF-1250

1.4.97 User-defined Configuration Property Type (UCPT)

1.4.98 User-defined Network Variable Type (UNVT)

1.4.99 UMCS

1.4.100 UMCS Network

1.4.101 Writeable Property

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.7 LNS Plug-Ins

1.8.8 Niagara Framework Wizards

1.8.9 Niagara Framework Supervisory Gateway Backups

1.8.10 Niagara Framework Engineering Tool

1.8.11 Certificate of Networthiness Documentation

1.9 QUALITY CONTROL CHECKLISTS

1.9.1 Pre-Construction Quality Control (QC) Checklist

1.9.2 Post-Construction Quality Control (QC) Checklist

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

SECTION 23 09 00 Page 3

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 Network Address

3.3.9.4 Unique Node ID

3.3.9.5 Device Object Identifier

3.3.9.6 Network Number

3.3.9.7 MAC Address

3.3.9.8 BTL Listing

3.3.9.9 Proprietary Services Information

3.3.9.10 Alarming Information

3.3.9.11 Scheduling Information

3.3.9.12 Trending Information

3.3.9.13 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]

SECTION 23 09 00 Page 4

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 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 Inervals

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

SECTION 23 09 00 Page 5

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 LNS-Based LonWorks Systems

QC Checklist for Niagara Framework Based LonWorks Systems

QC Checklist for Niagara Framework Based BACnet Systems

QC Checklist for BACnet Systems

QC CHECKLIST FOR LNS-BASED LONWORKS 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 (November 2015) Change 2 - 08/18 Preparing Activity: USACE Superseding UFGS-23 09 23 (May 2011) UFGS-23 09 23.13 20 (August 2009)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated July 2018

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

11/15

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

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 functional system.

SECTION 23 09 00 Page 7

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 in online at:

http://www.wbdg.org/FFC/NAVGRAPH/graphtoc.pdf

NOTE: This specification makes use of SpecsIntact Tailoring Options. This note describes these options and how to use them.

"Printview Tailoring Tags" When printed to PDF there is no easy way to differentiate between different tailoring options.

For this reason temporary "tags" have been added to the text to indicate which tailoring options applies to which text. These "tags" take the form of an opening tag and a closing tag in curly braces ("{ and }") brackets. For example, the following text would be shown to be in Army tailoring option tags:

{ARMY}Text for specific tailoring{/ARMY}

These temporary tags are in turn in the "PRINTVIEW TAILORING TAGS" tailoring option. When managing

SECTION 23 09 00 Page 8 tailoring options for this specification DESELECT the "PRINTVIEW TAILORING TAGS" tailoring option to remove these temporary tags.

WARNING - YOU HAVE NOT DESELECTED THE "PRINTVIEW

TAILORING TAGS" TAILORING OPTION. YOU MUST DESELECT

THIS TAILORING OPTION.

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:

SECTION 23 09 00 Page 9

{NIAGARA BACNET}Niagara BACnet {/NIAGARA BACNET} {NIAGARA LONWORKS}Niagara LonWorks {/NIAGARA LONWORKS} {BACNET}BACnet {/BACNET}

{LNS} LNS{/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 Egnineer.

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} AIR FORCE{/AIR FORCE}

{ARMY}ARMY{/ARMY}

{NAVY} NAVY{/NAVY}

{NAVY WITH ACCEPTANCE ENGINEER}NAVY WITH ACCEPTANCE

ENGINEER{/NAVY WITH ACCEPTANCE ENGINEER}

{SERVICE GENERIC} SERVICE GENERIC{/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.

Provide a complete Direct Digital Control (DDC) system, except for the

SECTION 23 09 00 Page 10

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,] {LNS or NIAGARA LONWORKS} Section 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

{/LNS or NIAGARA LONWORKS} {BACNET or NIAGARA BACNET} Section 23 09 23.02

BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

{/BACNET or NIAGARA BACNET} 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 tailoring option in the following list paragraph contains requirments specific to Air Force managed projects. Deselect the AIR FORCE tailoring option if will not be administered by the Air Force.

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

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

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

f. Sufficient documentation and data, including rights to documentation and data, are provided such that the Government or their agents can execute work to perform repair, replacement, upgrades, and expansions

SECTION 23 09 00 Page 11 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 tailoring options in this list paragraph contain requirements for either a Niagara BACnet or a Niagara LonWorks application. Deselect the NIAGARA BACNET and NIAGARA LONWORKS tailoring options if this list paragraph should not be included in the project.

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

SECTION 23 09 00 Page 12

NOTE: Select whether Section 01 91 00.15 TOTAL BUILDING COMMISSIONING is used for commissioning or provide appropriate reference to the Commissioning specification.

Related work specified elsewhere:

a. {LNS or NIAGARA LONWORKS} Section 23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS{\LNS or NIAGARA LONWORKS}{BACNET or NIAGARA BACNET} Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS{\BACNET or

NIAGARA BACNET} DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

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

SECTION 23 09 00 Page 13

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 2004) 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 (2014) 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) National Electrical Code

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

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide

Tridium Open NiCS (2005) Understanding the NiagaraAX 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

SECTION 23 09 00 Page 14

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.

1.4.1 Alarm Generation

Alarm Generation is the monitoring of a value, comparison of the value to alarm conditions and the creation of an alarm when the conditions set for the alarm are met. Note that this does NOT include delivery of the alarm to the final destination (such as a user interface) - see paragraph ALARM ROUTING in Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS)

FRONT END AND INTEGRATION.

{NIAGARA LONWORKS}For Niagara Framework LonWorks Systems, Alarm Generation is the creation of alarm events using the Niagara Framework Alarm Service

{/NIAGARA LONWORKS}

{BACNET or NIAGARA BACNET} In BACnet, Alarm Generation is the creation of alarm events {NIAGARA BACNET}using the Niagara Framework Alarm Service, or {/NIAGARA BACNET} using Event Reporting as defined in ASHRAE 135 in one of three ways:

a. Intrinsic Alarm Generation using Intrinsic Reporting

b. Local Algorithmic Alarm Generation using Algorithmic Reporting where the referenced property is in the same device as the Event Enrollment Object

c. Remote Algorithmic Alarm Generation using Algorithmic Alarming where the referenced property is in a different device than the Event Enrollment Object. {/BACNET or NIAGARA BACNET}

1.4.2 Application Generic Controller (AGC)

NOTE: The tailoring options in this subpart contain requirements for either a Niagara LonWorks or LNS application. Deselect the NIAGARA LONWORKS and LNS tailoring options if this subpart should not be included in the project.

A device that is furnished with a (limited) pre-established application that also has the capability of being programmed. Further, the ProgramID and XIF file of the device are fixed. The programming capability of an AGC may be less flexible than that of a General Purpose Programmable Controller

(GPPC).

1.4.3 Application Specific Controller (ASC)

SECTION 23 09 00 Page 15 requirements for either a Niagara LonWorks or LNS application. Deselect the NIAGARA LONWORKS and LNS tailoring options if this subpart should not be included in the project.

A device that is furnished with a pre-established built in application that is configurable but not re-programmable. An ASC has a fixed factory-installed application program (i.e Program ID) with configurable settings.

1.4.4 Building Automation and Control Network (BACnet)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet

SECTION 23 09 00 Page 16 tailoring options if this subpart should not be included in the project.

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.8 BACnet Broadcast Management Device (BBMD)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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.9 BACnet/IP

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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

1.4.10 BACnet Internetwork

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

Two or more BACnet networks, connected with BACnet routers. In a BACnet

SECTION 23 09 00 Page 17 internetwork, there exists only one message path between devices.

1.4.11 BACnet Interoperability Building Blocks (BIBBs)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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)

SECTION 23 09 00 Page 18

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

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

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

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

1.4.12 BACnet Network

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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

1.4.13 BACnet Operator Display (B-OD)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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.14 BACnet Segment

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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

1.4.15 BACnet Smart Actuator (B-SA)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

SECTION 23 09 00 Page 19

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

1.4.16 BACnet Smart Sensor (B-SS)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

A simple sensing device with limited resources.

1.4.17 BACnet Testing Laboratories (BTL)

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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.18 BACnet Testing Laboratories (BTL) Listed

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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.19 Binary

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

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

1.4.20 Binding

requirements for either a LNS or Niagara LonWorks application. Deselect the LNS and NIAGARA LONWORKS

SECTION 23 09 00 Page 20 included in the project.

The act of establishing communications between CEA-709.1-D devices by associating the output of a device to the input of another so that information is automatically (and regularly) sent.

1.4.21 Broadcast

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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

1.4.22 Building Control Network (BCN)

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

1.4.23 Building Point of Connection (BPOC)

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

1.4.24 Channel

requirements for either a LNS or Niagara LonWorks application. Deselect the LNS and NIAGARA LONWORKS tailoring options if this subpart should not be included in the project.

A portion of the control network consisting of one or more segments connected by repeaters. Channels are separated by routers. The device quantity limitation is dependent on the topology/media and device type.

For example, a TP/FT-10 network with locally powered devices is limited to 128 devices per channel.

1.4.25 Commandable

See Overridable.

1.4.26 Commandable Objects

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet

SECTION 23 09 00 Page 21 included in the project.

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

1.4.27 Configurable

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

{BACNET or NIAGARA BACNET}

In a {NIAGARA BACNET}Niagara Framework {/NIAGARA BACNET} 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 {NIAGARA BACNET}

3) via the Niagara Framework {/NIAGARA BACNET} .

Note this is more stringent than the ASHRAE 135 definition.

{/BACNET or NIAGARA BACNET}

1.4.28 Configuration Property

requirements for either a LNS or Niagara LonWorks application. Deselect the LNS and NIAGARA LONWORKS tailoring options if this subpart should not be included in the project.

Controller parameter used by the application which is usually set during installation/testing and seldom changed. For example, the P and I settings of a P-I control loop. Also see paragraph STANDARD CONFIGURATION PROPERTY

TYPE (SCPT).

1.4.29 Control Logic Diagram

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

1.4.30 Device

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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

SECTION 23 09 00 Page 22

1.4.31 Device Object

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

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.32 Device Profile

NOTE: The tailoring options in this subpart contain requirements for either a BACnet or Niagara BACnet application. Deselect the BACNET and NIAGARA BACnet tailoring options if this subpart should not be included in the project.

A collection of BIBBs determining minimum BACnet capabilities of a device, defined in ASHRAE 135. Standard device profiles include BACnet Advanced Workstations (B-AWS), BACnet Building Controllers (B-BC), BACnet Advanced Application Controllers (B-AAC), BACnet Application Specific Controllers (B-ASC), BACnet Smart Actuator (B-SA), and BACnet Smart Sensor (B-SS).

1.4.33 Digital Controller

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

1.4.34 Direct Digital Control (DDC)

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

{LNS or NIAGARA LONWORKS} 1.4.35 Domain

NOTE: start here

A grouping of up to 32,385 nodes that can communicate directly with each other. (Devices in different domains cannot communicate directly with each other.) See also Node Address. {/LNS or NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.36 Explicit Messaging

A non-standard and often vendor (application) specific method of communication between devices where each message contains a message code that identifies the type of message and the devices use these codes to

SECTION 23 09 00 Page 23 determine the action to take when the message is received. {/LNS or

NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.37 External Interface File (XIF)

A file which documents a device's external interface, specifically the number and types of LonMark objects, the number, types, directions, and connection attributes of network variables, and the number of message tags.

{/LNS or NIAGARA LONWORKS}

1.4.38 Field Point of Connection (FPOC)

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

In general, the term "FPOC Location" means the place where this connection occurs, and "FPOC Hardware" means the device that provides the connection.

Sometimes the term "FPOC" is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in which it is used.

{NIAGARA BACNET or NIAGARA LONWORKS}1.4.39 Fox Protocol

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

NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.40 Functional Profile

A standard description, defined by LonMark, of one or more LonMark Objects used to classify and certify devices. {/LNS or NIAGARA LONWORKS}

1.4.41 Gateway

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

- "translating" from TP/FT-10 to Ethernet/IP or from BACnet MS/TP to BACnet over IP for example - are not gateways as the underlying data format does not change. Gateways are also called Communications Bridges or Protocol Translators.

{NIAGARA BACNET or NIAGARA LONWORKS} A Niagara Framework Supervisory Gateway is one type of Gateway. {/NIAGARA BACNET or NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.42 General Purpose Programmable Controller

(GPPC)

Unlike an ASC or AGC, a GPPC is not furnished with a fixed application program and does not have a fixed ProgramID or XIF file. A GPPC can be (re-)programmed, usually using vendor-supplied software. When a change to the program affects the external interface (and the XIF file) the ProgramID will change. {/LNS or NIAGARA LONWORKS}

1.4.43 IEEE 802.3 Ethernet

A family of local-area-network technologies providing high-speed networking

SECTION 23 09 00 Page 24 features over various media, typically Cat 5, 5e or Cat 6 twisted pair copper or fiber optic cable.

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

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

1.4.45 Input/Output (I/O)

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

1.4.46 I/O Expansion Unit

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

1.4.47 IP subnet

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

{NIAGARA BACNET or NIAGARA LONWORKS}1.4.48 JACE (Niagara Framework)

Java Application Control Engine. See paragraph NIAGARA FRAMEWORK SUPERVISORY GATEWAY {/NIAGARA BACNET or NIAGARA LONWORKS}

1.4.49 Local-Area Network (LAN)

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

1.4.50 Local Display Panels (LDPs)

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

{LNS or NIAGARA LONWORKS} 1.4.51 LonMark

See paragraph LONMARK INTERNATIONAL. Also, a certification issued by LonMark International to CEA-709.1-D devices. {/LNS or NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.52 LonMark International

Standards committee consisting of numerous independent product developers, system integrators and end users dedicated to determining and maintaining the interoperability guidelines for LonWorks. Maintains guidelines for the interoperability of CEA-709.1-D devices and issues the LonMark Certification for CEA-709.1-D devices. {/LNS or NIAGARA LONWORKS}

SECTION 23 09 00 Page 25

{LNS or NIAGARA LONWORKS} 1.4.53 LonMark Interoperability Association

See paragraph LONMARK INTERNATIONAL. {/LNS or NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.54 LonMark Object

A collection of network variables, configuration properties, and associated behavior defined by LonMark International and described by a Functional Profile. It defines how information is exchanged between devices on a network (inputs from and outputs to the network). {/LNS or NIAGARA

LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.55 LonWorks

The term used to refer to the overall technology related to the CEA-709.1-D protocol (sometimes called "LonTalk"), including the protocol itself, network management, interoperability guidelines and products. {/LNS or

NIAGARA LONWORKS}

{LNS or NIAGARA LONWORKS} 1.4.56 LonWorks Network Services (LNS)

A network management and database standard for CEA-709.1-D devices. {/LNS or NIAGARA LONWORKS}

{LNS} 1.4.57 LonWorks Network Services (LNS) Plug-in

Software which runs in an LNS compatible software tool, typically a network configuration tool. Device configuration plug-ins provide a user friendly method to edit a device's configuration properties. {/LNS}

1.4.58 MAC Address

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

{BACNET or NIAGARA BACNET} 1.4.59 Master-Slave/Token-Passing (MS/TP)

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

NIAGARA BACNET}

1.4.60 Monitoring and Control (M&C) Software

The UMCS 'front end' software which performs supervisory functions such as alarm handling, scheduling and data logging and provides a user…