23 09 23.01.pdf

FY24 POL Complex 22029 Great Falls Air National Guard, MT W912DW24R0013

SECTION TABLE OF CONTENTS

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

SECTION 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

02/ 19, CHG 1: 02/ 20

PART 1 GENERAL

1.1 SUMMARY

1.1.1 System Requirements

1.1.2 Verification of Specification Requirements

1.2 REFERENCES

1.3 DEFINITIONS

1.4 SUBMITTALS

PART 2 PRODUCTS

2.1 NETWORK HARDWARE

2.1.1 CEA-709.1-D Routers

2.1.2 CEA-709.1-D Repeaters

2.1.3 CEA-709.1-D Gateways

2.1.4 Ethernet Switch

2.2 CONTROL NETWORK WIRING

2.3 DIRECT DIGITAL CONTROL (DDC) HARDWARE

2.3.1 Hardware Input-Output (I/O) Functions

2.3.1.1 Analog Inputs

2.3.1.2 Analog Outputs

2.3.1.3 Binary Inputs

2.3.1.4 Binary Outputs

2.3.1.4.1 Relay Contact Closures

2.3.1.4.2 Triac Outputs

2.3.1.5 Pulse Accumulator

2.3.2 Local Display Panel (LDP)

2.3.3 Application Specific Controller (ASC)

2.3.4 General Purpose Programmable Controller (GPPC)

2.3.5 Application Generic Controller (AGC)

PART 3 EXECUTION

3.1 CONTROL SYSTEM INSTALLATION

3.1.1 Building Control Network (BCN)

3.1.1.1 Building Control Network (BCN) Installation

3.1.1.2 Non-IP Building Control Network (BCN) Channel

3.1.1.3 Building Control Network (BCN) IP Network

3.1.2 DDC Hardware

3.1.2.1 Hand-Off-Auto (H-O-A) Switches

3.1.2.2 Overrides for GPPCs and AGCs

3.1.2.3 Overrides for ASCs

3.1.3 Scheduling, Alarming, Trending and Overrides

3.1.3.1 Scheduling

3.1.3.1.1 Schedule Groupings

3.1.3.1.2 Occupancy Mode Mapping to SNVT Values

SECTION 23 09 23.01 Page 1

REVISED 95% DESIGN

3.1.3.2 Alarming

3.1.3.3 Trending

3.1.3.4 Overrides

3.1.4 Gateways

3.1.5 Network Interface Jack

-- End of Section Table of Contents --

SECTION 23 09 23.01 Page 2

SECTION 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

02/ 19, CHG 1: 02/ 20

PART 1 GENERAL

1.1 SUMMARY

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 specified and shown and in accordance with Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

1.1.1 System Requirements

Provide a system meeting the requirements of both Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC and this Section and with the following characteristics:

a.

b.

c. Install and configure control hardware to provide all input and output Standard Network Variables (SNVTs) as indicated and as needed to meet the requirements of this specification.

d. All DDC hardware installed under this specification must communicate via CEA-709.1-D . Install the control system such that a SNVT output from any node on the network can be bound to any other node in the same domain.

1.1.2 Verification of Specification Requirements

Review all specifications related to the control system installation and advise the Contracting Officer of any discrepancies before performing any work. If Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC or any other Section referenced in this specification is not included in the project specifications advise the Contracting Officer and either obtain the missing Section or obtain Contracting Officer approval before performing any work.

1.2 REFERENCES

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

SECTION 23 09 23.01 Page 3

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 802.3 (2022) Ethernet

LONMARK INTERNATIONAL (LonMark)

LonMark Interoperability Guide (2005) LonMark Application-Layer Interoperability Guide and LonMark Layer 1-6 Interoperability Guide; Version 3.4

LonMark SCPT List (2014) LonMark SCPT Master List; Version 15

LonMark SNVT List (2014) LonMark SNVT Master List; Version 15

LonMark XIF Guide (2001) LonMark External Interface File Reference Guide; Revision 4.402

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC Part 15 Radio Frequency Devices (47 CFR 15)

UNDERWRITERS LABORATORIES (UL)

UL 916 (2015; Reprint Oct 2021) UL Standard for Safety Energy Management Equipment

1.3 DEFINITIONS

For definitions related to this section, see Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

1.4 SUBMITTALS

Submittals related to this Section are specified in Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

PART 2 PRODUCTS

All products used to meet this specification must meet the specified requirements, but not all products specified here will be required by every project. Provide products which meet the requirements of both Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC and this Section.

2.1 NETWORK HARDWARE

2.1.1 CEA-709.1-D Routers

CEA-709.1-D Routers must meet the requirements of CEA-709.1-D and must provide connection between two or more CEA-709.3 TP/FT-10 channels, or between one or more CEA-709.3 TP/FT-10 channels and a LonMark Interoperability Guide TP/XF-1250 channel.

SECTION 23 09 23.01 Page 4

2.1.2 CEA-709.1-D Repeaters

CEA-709.1-D Repeaters must be CEA-709.1-D Routers configured as repeaters.

Physical layer repeaters are prohibited.

2.1.3 CEA-709.1-D Gateways

In addition to the requirements for DDC Hardware, CEA-709.1-D gateways must

a. Allow bi-directional mapping of data between the non- CEA-709.1-D protocol and SNVTs

b. Incorporate a network connection to a TP/FT-10 network in accordance with CEA-709.3 and a separate connection appropriate for the a non- CEA-709.1-D network

Although Gateways must meet DDC Hardware requirements they are not DDC Hardware and must not be used when DDC Hardware is required.

2.1.4 Ethernet Switch

Ethernet Switches must autoconfigure between 10,100 and 1000 megabits per second (MBPS).

2.2 CONTROL NETWORK WIRING

a. Provide TP/FT-10 control wiring in accordance with CEA-709.3 .

b. Provide TP/XF-1250 control wiring in accordance with the LonMark Interoperability Guide .

c. For the Building Control Network IP Network provide media that is CAT-5e Ethernet media at a minimum and meets all requirements of

IEEE 802.3 .

2.3 DIRECT DIGITAL CONTROL (DDC) HARDWARE

All DDC Hardware must meet the following general requirements:

a. must incorporate a "service pin" which, when pressed will cause the DDC Hardware to broadcast its 48-bit NodeID and its ProgramID over the network. The service pin must be distinguishable and accessible.

b. It must incorporate a light to indicate the device is receiving power.

c. incorporate a TP/FT-10 transceiver in accordance with CEA-709.3 and connections for TP/FT-10 control network wiring.

d. It must communicate on the network using only the CEA-709.1-D protocol .

e. It must be capable of having network communications configured via.

f. It must be locally powered; link powered devices are not acceptable.

g. LonMark external interface files (XIF files), as defined in the LonMark XIF Guide , must be submitted for each type of DDC Hardware .

SECTION 23 09 23.01 Page 5

h. Application programs and configuration settings must be stored in a manner such that a loss of power does not result in a loss of the application program or configuration settings:

(1) Loss of power must never result in the loss of application programs, regardless of the length of time power is lost.

(2) Loss of power for less than 2,500 hours must not result in the loss of configured settings.

i. It must have all functionality specified and required to support the application (Sequence of Operation or portion thereof) in which it is used, including but not limited to:

(1) It must provide input and output SNVTs as specified, as indicated on the Points Schedule, and as otherwise required to support the sequence and application in which it is used. All SNVTs must have meaningful names identifying the value represented by the SNVT .

Unless a standard network variable type of an appropriate engineering type is not available, all network variables must be of a standard network variable type with engineering units appropriate to the value the variable represents.

(2) All settings and parameters used by the application in which the DDC hardware is used must be configurable via one of the following: standard configuration properties (SCPTs) as defined in the LonMark SCPT List , user-defined configuration properties (UCPTs), network configuration inputs ( ncis) of a SNVT type as defined in the LonMark SNVT List , network configuration inputs ( nci

s) of a user defined network variable type, or hardware settings on the controller itself.

j. It must meet FCC Part 15 requirements and have UL 916 or equivalent safety listing.

k. In addition to these general requirements and the DDC Hardware Input-Output (I/O) Function requirements, all DDC Hardware must also meet the requirements of a Local Display Panel (LDP), Application Specific Controller (ASC), General Purpose Programmable Controller (GPPC), or an Application Generic Controller (AGC). All pieces of DDC Hardware must have their DDC Hardware Type identified as part of the Manufacturer's Product Data submittal as specified in Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. Except for Local Display Panels provided as part of another controller, where a single device meets the requirements of multiple types, select a single type for that specific device based on it's use. Where a Local Display Panel is provided as part of another device, indicate both the controller type and local display panel. One model of DDC hardware may be submitted as different DDC Hardware types when used in multiple applications.

l. The user interface on all DDC Hardware with a user interface which allows for modification of a value must be password protected.

m. Clocks in DDC Hardware incorporating a Clock must continue to function for 120 hours upon loss of power to the DDC Hardware.

SECTION 23 09 23.01 Page 6

2.3.1 Hardware Input-Output (I/O) Functions

DDC Hardware incorporating hardware input-output (I/O) functions must meet the following requirements:

2.3.1.1 Analog Inputs

DDC Hardware analog inputs (AIs) must perform analog to digital (A-to-D) conversion with a minimum resolution of 8 bits plus sign or better as needed to meet the accuracy requirements specified in Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. Signal conditioning including transient rejection must be provided for each analog input. Analog inputs must be capable of being individually calibrated for zero and span.

Calibration via software scaling performed as part of point configuration is acceptable. The AI must incorporate common mode noise rejection of at least 50 dB from 0 to 100 Hz for differential inputs, and normal mode noise rejection of at least 20 dB at 60 Hz from a source impedance of 10,000 ohms.

2.3.1.2 Analog Outputs

DDC Hardware analog outputs (AOs) must perform digital to analog (D-to-A) conversion with a minimum resolution of 8 bits plus sign, and output a signal with a range of 4-20 mAdc or 0-10 Vdc. Analog outputs must be capable of being individually calibrated for zero and span. Calibration via software scaling performed as part of point configuration is acceptable. DDC Hardware with Hand-Off-Auto (H-O-A) switches for analog outputs must provide for overriding the output through the range of 0 percent to 100 percent

2.3.1.3 Binary Inputs

DDC Hardware binary inputs (BIs) must accept contact closures and must ignore transients of less than 5 milli-second duration. Protection against a transient of 50 Vac must be provided.

2.3.1.4 Binary Outputs

DDC Hardware binary outputs (BOs) must provide relay contact closures or triac outputs for momentary and maintained operation of output devices.

DDC Hardware with H-O-A switches for binary outputs must provide for overriding the output open or closed.

2.3.1.4.1 Relay Contact Closures

Closures must have a minimum duration of 0.1 second. Relays must provide at least 180V of isolation. Electromagnetic interference suppression must be provided on all output lines to limit transients to 50 Vac. Minimum contact rating must be 0.5 amperes at 24 Vac.

2.3.1.4.2 Triac Outputs

Triac outputs must provide at least 180 V of isolation. Minimum contact rating must be 0.5 amperes at 24 Vac.

2.3.1.5 Pulse Accumulator

DDC Hardware pulse accumulators must have the same characteristics as the BI. In addition, a buffer must be provided to totalize pulses. The pulse

SECTION 23 09 23.01 Page 7 accumulator must accept rates of at least 20 pulses per second. The totalized value must be resettable via a configurable parameter.

2.3.2 Local Display Panel (LDP)

The Local Display Panels (LDPs) must be DDC Hardware with a display and navigation buttons or a touch screen display, and must provide display and adjustment of network variables as indicated on the Points Schedule and as specified. LDPs must be provided as stand-alone DDC Hardware or as an integral part of another piece of DDC Hardware. LDPs must come factory installed with all applications necessary for the device to function as an

LDP.

The adjustment of values using display and navigation buttons must be password protected.

2.3.3 Application Specific Controller (ASC)

Application Specific Controllers (ASCs) have a fixed factory-installed application program (i.e. ProgramID) with configurable settings and do not have the ability to be programmed for custom applications. ASCs must meet the following requirements in addition to the General DDC Hardware and DDC Hardware Input-Output (I/O) Function requirements:

a. ASCs must be LonMark Certified.

b.

c. ASCs may include an integral or tethered Local Display Panel

2.3.4 General Purpose Programmable Controller (GPPC)

A General Purpose Programmable Controller (GPPC) must be programmed for the application. GPPCs must meet the following requirements in addition to the general DDC Hardware requirements and Hardware Input-Output (I/O) Functions:

a. The programmed GPPC must conform to the LonMark Interoperability Guide .

b. All programming software required to program the GPPC must be delivered to and licensed to the project site in accordance with Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. Submit the most recent version of the Programming software for each type (manufacturer and model) of General Purpose Programmable Controller

(GPPC).

c. Submit copies of the installed GPPC application programs (all software that is not common to every controller of the same manufacturer and model) as source code compatible with the supplied programming software in accordance with Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. The submitted GPPC application program must be the complete application necessary for the GPPC to function as installed and be sufficient to allow replacement of the installed controller with a GPPC of the same type.

d. GPPCs may be include an integral or tethered Local Display Panel

SECTION 23 09 23.01 Page 8

2.3.5 Application Generic Controller (AGC)

An Application Generic Controller (AGC) has a fixed application program which includes the ability to be programmed for custom applications. AGCs must meet the following requirements in addition to the general DDC Hardware requirements and Hardware Input-Output (I/O) Functions:

a. The programmed AGC must conform to the LonMark Interoperability Guide .

b. The AGC must have a fixed ProgramID and fixed XIF file.

c. Unless otherwise approved, the ACG must be fully configurable and programmable for the application using one or more, all of which must be submitted as specified for each type of AGC (manufacturer and model).

d. Submit copies of the installed AGC application programs as source code compatible with the supplied used for programming the device in accordance with Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. The submitted AGC application program must be the complete application program necessary for the AGC to function as installed and be sufficient to allow replacement of the installed controller with an AGC of the same type.

e. AGCs may be include an integral or tethered Local Display Panel

PART 3 EXECUTION

3.1 CONTROL SYSTEM INSTALLATION

3.1.1 Building Control Network (BCN)

Provide a Building Control Network (BCN) connecting all DDC hardware as specified. The Building Control Network (BCN) must consist of an IP Network, one or more, and one or more Non-IP Building Control Network Channels:

3.1.1.1 Building Control Network (BCN) Installation

Provide building control networks meeting the following requirements:

a. Provide a Building Control Network IP Network, Non-IP Building Control Network Channels and to a create a single building control network connecting all DDC Hardware.

b. In addition to the connection to the, each Non-IP Building Control Network (BCN) Channel directly connected to a must be directly connected to either DDC Hardware or to CEA-709.1-D Routers, but not to both. A channel containing only CEA-709.1-D Routers is a backbone channel and a channel containing DDC Hardware is a non-backbone channel.

c. When only a single is required, the IP network consists of only the.

When multiple are required, provide an IP Network connecting all.

d. Connect all DDC Hardware to a non-backbone BCN Channel.

e. Install components such that there is no more than than one CEA-709.1-D Router between any DDC Hardware and a

SECTION 23 09 23.01 Page 9

f. Install the network such that the peak expected bandwidth usage for each and every channel is less than 70 percent, including device-to-device traffic and traffic to the Utility Monitoring and Control System (UMCS) as indicated on the Points Schedule.

g. Where multiple pieces of DDC Hardware are used in the execution of a single sequence of operation, directly connect all DDC Hardware used to execute the sequence to the same channel and do not install other DDC Hardware to that channel.

3.1.1.2 Non-IP Building Control Network (BCN) Channel

Provide Non-IP Building Control Network (BCN) Channels meeting the following requirements:

a. For each non-backbone channel, provide a TP/FT-10 channel in doubly terminated bus topology in accordance with CEA-709.3 . For each backbone channel, provide either a TP/FT-10 channel in doubly terminated bus topology in accordance with CEA-709.3 or a TP/XF-1250 channel in accordance with the LonMark Interoperability Guide .

b. Connect no more than 2/3 the maximum number of devices permitted by CEA-709.3 to each TP/FT-10 channel. Connect no more than 2/3 the maximum number of devices permitted by LonMark Interoperability Guide to TP/XF-1250 channel.

c. Connect no more than 2/3 the maximum number of devices permitted by the manufacturer of the device transceivers to each channel. When more than one type of transceiver is used on the same channel, use the transceiver with the lowest maximum number of devices to calculate the 2/3 limit.

3.1.1.3 Building Control Network (BCN) IP Network

Install IP Network Cabling in conduit. Install Ethernet Switches in lockable enclosures. Install the Building Control Network (BCN) IP Network so that it is available at the Facility Point of Connection (FPOC) location . When the FPOC location is a room number, provide sufficient additional media to ensure that the Building Control Network (BCN) IP Network can be extended to any location in the room.

3.1.2 DDC Hardware

Install in lockable enclosures. Install other DDC Hardware which is not is suspended ceilings in enclosures.

Configure and commission all DDC Hardware on the Building Control Network .

Use Application Specific Controllers whenever an Application Specific Controller suitable for the application exists. When an Application Specific Controller suitable for the application does not exist use .

3.1.2.1 Hand-Off-Auto (H-O-A) Switches

Provide Hand-Off-Auto (H-O-A) switches as specified and as indicated on the Points Schedule. H-O-A switches must be integral to the controller hardware, an external device co-located with (in the same enclosure as) the controller, integral to the controlled equipment, or an external device co-located with (in the same enclosure as) the controlled equipment.

SECTION 23 09 23.01 Page 10

a. For H-O-A switches integral to DDC Hardware, meet the requirements specified in paragraph DIRECT DIGITAL CONTROL (DDC) HARDWARE.

b. For external H-O-A switches for binary outputs, provide switches capable of overriding the output open or closed.

c. For external H-O-A switches for analog outputs, provide switches capable of overriding through the range of 0 percent to 100 percent.

3.1.2.2 Overrides for GPPCs and AGCs

Provide the capability to override points for all General Purpose Programmable Controllers and Application Generic Controllers as specified and as indicated on the Points Schedule using one of the following methods:

a. Override SNVT of Same SNVT Type method:

(1) Use this method for all setpoint overrides and for overrides of inputs and outputs whenever practical.

(2) Provide a SNVT input to the DDC hardware containing the point to be overridden of the same SNVT type as the point to be overridden.

(3) Program and configure the DDC hardware such that:

(a) If the value of the SNVT on the override input is the Invalid Value defined for that SNVT by the LonMark SNVT List , then the point is not overridden (its value is determined from the sequence).

(b) If the value of the SNVT on the override input is not the Invalid Value defined for that SNVT by the LonMark SNVT List then set the value of the point to be overridden to the value of the SNVT on the override input.

b. HVAC Override SNVT method:

(1) Use this method for override of inputs and outputs when the "Override SNVT Shares SNVT Type" method is impractical.

(2) Provide a SNVT input to the DDC hardware containing the point to be overridden of SNVT type SNVT_hvac_overid. Show on the Points Schedule how to perform the specified override using this SNVT.

3.1.2.3 Overrides for ASCs

Whenever possible use the methods specified for General Purpose Programmable Controllers and Application Generic Controllers to perform overrides for all Application Specific Controllers. If neither the "Override SNVT of Same SNVT Type" method or "HVAC Override SNVT" method are supported by the Application Specific Controller show this on the Points Schedule and perform overrides as follows:

a. Provide one or more SNVT input(s) to the DDC hardware containing the point to be overridden. Document the number and type of each SNVT provided on the Points Schedule.

b. Configure the Application Specific Controller such that:

SECTION 23 09 23.01 Page 11

(1) For some specific combination or combinations of values at the SNVT override input(s) the point is not overridden, and its value is determined from the sequence as usual. Show on the Points Schedule the values required at the SNVT override input(s) to not override the point.

(2) For other specific combinations of SNVT override input(s), the value of the point to be overridden is determined from the value of the override input(s). Show on the Points Schedule the correlation between the SNVT override input(s) and the resulting value of the overridden point.

3.1.3 Scheduling, Alarming, Trending and Overrides

3.1.3.1 Scheduling

3.1.3.1.1 Schedule Groupings

Provide a separate schedule for each AHU including it's associated Terminal Units and for each stand-alone Terminal Unit (those not dependent upon AHU service).

3.1.3.1.2 Occupancy Mode Mapping to SNVT Values

Use the following mapping between SNVT_Occupancy enumerations and occupancy modes:

a. OCCUPIED mode: Enumeration value of OC_OCCUPIED

b. UNOCCUPIED mode: Enumeration value of OC_UNOCCUPIED

c. WARM-UP/COOL-DOWN (PRE-OCCUPANCY) mode: Enumeration value of OC_STANDBY

3.1.3.2 Alarming

3.1.3.3 Trending

3.1.3.4 Overrides

3.1.4 Gateways

The requirements in this paragraph do not themselves permit the installation of hardware not meeting the other requirements of this section. Except for proprietary systems specifically indicated in Section 23 09 00, all control hardware installed under this project must meet the requirements of this specification, including the control hardware providing the network interface for a package unit or split system specified under this Section or another Section. Only use gateways to connect to pre-existing control devices and to proprietary systems specifically permitted by Section 23 09 00.

Provide Gateways to connect non- CEA-709.1-D control hardware in accordance with the following:

SECTION 23 09 23.01 Page 12

a. Configure gateway to map writeable data points in the controlled equipment to Network Variable Inputs of Standard Network Variable Types as defined by the LonMark SNVT List as indicated in the Points Schedule and as specified.

b. Configure gateway to map readable data points in the controlled equipment to Network Variable Outputs of Standard Network Variable Types as defined by the LonMark SNVT List as indicated in the Points Schedule and as specified.

c. Do not use non- CEA-709.1-D control hardware for controlling built-up units or any other equipment that was not furnished with factory-installed controls.

d. Do not use non- CEA-709.1-D control hardware for system scheduling functions.

e. Each gateway must communicate with and perform protocol translation for non- CEA-709.1-D control hardware controlling one and only one package unit or a single non- CEA-709.1-D system specifically permitted by Section 23 09 00.

f. Connect one network port on the gateway to the Building Control Network and the other port to the single piece of controlled equipment or the non- CEA-709.1-D network specifically permitted by Section 23 09 00.

g. For gateways to existing package units or simple split systems, non- CEA-709.1-D network wiring connecting the gateway to the package unit or split system interface must not exceed 10 feet in length and must connect to exactly two devices: the controlled equipment or split system interface and the gateway.

3.1.5 Network Interface Jack

Provide standard network interface jacks such that each node on the control network is within 10 ft of an interface jack. For terminal unit controllers with hardwired thermostats this network interface jack may instead be located at the thermostat. Locating the interface jack near the controller is preferred. If the network interface jack is other than a 1/8 inch phone jack, provide an interface cable with a standard 1/8 inch phone jack on one end and a connector suitable for mating with installed network interface jack on the other. No more than one type of interface cable must be required to access all network interface jacks. Furnish one interface cable(s).

-- End of Section --

SECTION 23 09 23.01 Page 13