APPENDIX_A__FSH-UMCS_BACnet_specification_23_09_23_00_10.pdf

PDF 335 KB Posted

Attached to
General Repairs to Building 2263
Solicitation number
W9126G18B0030
Issued by

About this file

The purpose of this amendment is to include Appendix A and Appendix B into the solicitation as indicated in the Invitation for Bid SF1442 and to correct the name of amendment W9126G18B0030U00001 to W9126G18B003000001.

View the file

Other files

Show all 20

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Fort Sam Houston – UMCS BACnet Spec

Section 23 09 23 00 10 Page 1 of 57

Section 23 09 23

Heating, Ventilating and Air Conditioning (HVAC) Control System

For

Fort Sam Houston (FSH) BACnet Direct Digital Controls (DDC)

1. Part 1 – General

Table of Contents

Part 1 – General

1.1 Related Documents

1.2 Definitions

1.3 BMS System Description

1.4 Quality Assurance

1.5 References

1.6 Work By Others

1.7 Submittals

1.8 Record Documentation

1.9 Warranty

Part 2 – Products

2.1 General Description

2.2 BMS Architecture

2.3 User Interface

2.4 Network Automation Engine

2.5 Network Control Engine

2.6 DDC System Controllers

2.7 Field Devices

2.8 System Tools

2.9 Input Devices

2.10 Output Devices

2.11 Miscellaneous Devices

Part 3 – Execution

3.1 BMS Specific Requirements

3.2 Installation Practices

3.3 Training

3.4 Commissioning Requirements

1.1 Related Documents

A. All work of this Division shall be coordinated and provided by the single Building Management System (BMS) Contractor.

B. The work of this Division shall be scheduled, coordinated, and interfaced with the associated work of other trades.

Reference the Division 23 Sections for details.

Section 23 09 23 00 10 Page 2 of 57

C. The work of this Division shall be as required by the

Specifications, Point Schedules and Drawings.

D. If the BMS Contractor believes there are conflicts or missing information in the project documents, the Contractor shall promptly request clarification and instruction from the design team.

1.2 Definitions

A. Analog: A continuously variable system or value not having discrete levels. Typically exists within a defined range of limiting values.

B. Binary: A two-state system where an “ON” condition is represented by one discrete signal level and an “OFF” condition is represented by a second discrete signal level.

C. Building Management System (BMS): A total integrated system of fully operational and functional elements, including equipment, software, programming, and associated materials.

The BMS shall be provided by this Division BMS Contractor and shall be interfaced to the associated work of other related trades.

D. BMS Contractor: The single Contractor to provide the work of this Division. This Contractor shall be the primary manufacturer, installer, commissioner and ongoing service provider for the BMS work.

E. Control Sequence: A BMS pre-programmed arrangement of software algorithms, logical computation, target values and limits as required to attain the defined operational control objectives.

F. Direct Digital Control: The digital algorithms and pre-defined arrangements included in the BMS software to provide direct closed-loop control for the designated equipment and controlled variables. Inclusive of Proportional, Derivative and Integral control algorithms together with target values, limits, logical functions, arithmetic functions, constant values, timing considerations and the like.

G. BMS Network: The total digital on-line real-time interconnected configuration of BMS digital processing units, workstations, panels, sub-panels, controllers, devices and associated elements individually known as network nodes. May exist as one or more fully interfaced and integrated sub-networks, LAN, WAN or the like.

H. Node: A digitally programmable entity existing on the BMS network.

I. BMS Integration: The complete functional and operational interconnection and interfacing of all BMS work elements and

Section 23 09 23 00 10 Page 3 of 57 nodes in compliance with all applicable codes, standards and ordinances so as to provide a single coherent BMS as required by this Division.

J. Provide: The term “Provide” and its derivatives when used in this Division shall mean to furnish, install in place, connect, calibrate, test, commission, warrant, document and supply the associated required services ready for operation.

K. Furnish: The term “Furnish” and its derivatives when used in this Division shall mean supply at the BMS Contractor’s cost to the designated third party trade contractor for installation. BMS Contractor shall connect furnished items to the BMS, calibrate, test, commission, warrant and document.

L. Wiring: The term “Wiring” and its derivatives when used in this Division shall mean provide the BMS wiring and terminations.

M. Install: The term “Install” and its derivatives when used in this Division shall mean receive at the jobsite and mount.

N. Protocol: The term “protocol” and its derivatives when used in this Division shall mean a defined set of rules and standards governing the on-line exchange of data between BMS network nodes.

O. Software: The term “software” and its derivatives when used in this Division shall mean all of programmed digital processor software, preprogrammed firmware and project specific digital process programming and database entries and definitions as generally understood in the BMS industry for real-time, on-line, integrated BMS configurations.

P. The use of words in the singular in these Division documents shall not be considered as limiting when other indications in these documents denote that more than one such item is being referenced.

Q. Headings, paragraph numbers, titles, shading, bolding, underscores, clouds and other symbolic interpretation aids included in the Division documents are for general information only and are to assist in the reading and interpretation of these Documents.

R. The following abbreviations and acronyms may be used in describing the work of this Division:

ADC - Analog to Digital Converter

AI - Analog Input

AN - Application Node

Section 23 09 23 00 10 Page 4 of 57

ANSI - American National Standards

Institute

AO - Analog Output

ASCII - American Standard Code for

Information Interchange

ASHRAE American Society of Heating, Refrigeration and Air Conditioning

Engineers

AWG - American Wire Gauge

CPU - Central Processing Unit

CRT - Cathode Ray Tube

DAC - Digital to Analog Converter

DDC - Direct Digital Control

DI - Digital Input

DO - Digital Output

EEPROM - Electronically Erasable

Programmable Read Only

Memory

EMI - Electromagnetic Interference

FAS - Fire Alarm Detection and

Annunciation System

GUI - Graphical User Interface

HOA - Hand-Off-Auto

ID - Identification

IEEE - Institute of Electrical and

Electronics Engineers

I/O - Input/Output

LAN - Local Area Network

LCD - Liquid Crystal Display

LED - Light Emitting Diode

MCC - Motor Control Center

NC - Normally Closed

NIC - Not In Contract

NO - Normally Open

OWS - Operator Workstation

OAT - Outdoor Air Temperature

PC - Personal Computer

RAM - Random Access Memory

RF - Radio Frequency

RFI - Radio Frequency Interference

RH - Relative Humidity

ROM - Read Only Memory

RTD - Resistance Temperature Device

SPDT - Single Pole Double Throw

SPST - Single Pole Single Throw

XVGA - Extended Video Graphics Adapter

TBA - To Be Advised

Section 23 09 23 00 10 Page 5 of 57

TCP/IP - Transmission Control

Protocol/Internet

Protocol

TTD - Thermistor Temperature Device

UPS - Uninterruptible Power Supply

VAC - Volts, Alternating Current

VAV - Variable Air Volume

VDC - Volts, Direct Current

WAN - Wide Area Network

1.3 BMS Description

A. The Building Management System (BMS) shall be a complete system designed for use at the existing Fort Sam Houston JCI

Metasys ADX Server Front End. This functionality shall extend into the equipment rooms. Devices residing on the

BMS network located in equipment rooms and similar shall be fully compatible devices that mount and communicate directly on the UMCS Post Wide Area Network. Contractor shall be responsible for coordination with Fort Sam Houston’s UMCS staff to ensure that the BMS will be displayed in a

Graphical Format at the existing Metasys ADX Server

Workstation without disruption to any of the other activities taking place on Fort Sam Houston’s UMCS Network.

B. The BMS shall include DDC Controllers for each major piece of equipment such as Air Handling Units, Chilled and Hot Water

Systems and other HVAC terminal/unitary equipment.

C. All DDC points shall not require the purchase of any special software from the BMS manufacturer for use as a building operations terminal. The primary point of interface shall be the HMI Display Terminal in each building at the post-wide

UMCS.

D. The work of the single BMS Contractor shall be as defined individually and collectively in all Sections of this

Division specification together with the associated Point

Sheets and Drawings and the associated interfacing work as referenced in the related documents.

E. The BMS work shall consist of the provision of all labor, materials, tools, equipment, software, software licenses, software configurations and database entries, interfaces, wiring, tubing, installation, labeling, engineering, calibration, documentation, samples, submittals, testing, commissioning, training services, permits and licenses, transportation, shipping, handling, administration, supervision, management, insurance, temporary protection, cleaning, cutting and patching, warranties, services, and items, even though these may not be specifically mentioned

Section 23 09 23 00 10 Page 6 of 57 in these Division documents which are required for the complete, fully functional and commissioned BMS.

F. Provide a complete, neat and workmanlike installation. Use only manufacturer employees who are skilled, experienced, trained, and familiar with the specific equipment, software, standards and configurations to be provided for this

Project.

G. Manage and coordinate the BMS work in a timely manner in consideration of the Project schedules. Coordinate with the associated work of other trades so as to not impede or delay the work of associated trades.

H. The BMS as provided shall incorporate, at minimum, the following integrated features, functions and services:

1. Operator information, alarm management and control functions.

2. Enterprise-level information and control access.

3. Information management including monitoring, transmission, archiving, retrieval, and reporting functions.

4. Diagnostic monitoring and reporting of BMS functions.

5. Offsite monitoring and management access.

6. Energy management

7. Standard applications for terminal HVAC systems.

8. Indoor Air Quality monitoring and control

1.4 Quality Assurance

A. General

1. The Building Management System Contractor shall be the primary manufacturer-owned branch office that is regularly engaged in the engineering, programming, installation and service of total integrated Building Management Systems.

2. The BMS Contractor shall have a branch facility within a 100-mile radius of the job site supplying complete maintenance and support services on a 24 hour, 7-day-a-week basis.

3. As evidence and assurance of the contractor’s ability to support the Owner's system with service and parts, the contractor must have been in the

BMS business for at least the last ten (10) years and have successfully completed total projects of at least 10 times the value of this contract in each of the preceding five years.

Section 23 09 23 00 10 Page 7 of 57

4. The Building Management System architecture shall consist of the products of a manufacturer regularly engaged in the production of Building

Management Systems, and shall be the manufacturer’s latest standard of design at the time of bid.

B. Workplace Safety And Hazardous Materials

1. Provide a safety program in compliance with the

Contract Documents.

2. The BMS Contractor shall have a corporately certified comprehensive Safety Certification

Manual and a designated Safety Supervisor for the

Project.

3. The Contractor and its employees and sub-trades shall comply with federal, state and local safety regulations.

4. The Contractor shall ensure that all subcontractors and employees have written safety programs in place that covers their scope of work, and that their employees receive the training required by the OSHA have jurisdiction for at least each topic listed in the Safety

Certification Manual.

5. Hazards created by the Contractor or its subcontractors shall be eliminated before any further work proceeds.

6. Hazards observed but not created by the Contractor or its subcontractors shall be reported to either the General Contractor or the Owner within the same day. The Contractor shall be required to avoid the hazard area until the hazard has been eliminated.

7. The Contractor shall sign and date a safety certification form prior to any work being performed, stating that the Contractors’ company is in full compliance with the Project safety requirements.

Section 23 09 23 00 10 Page 8 of 57

8. The Contractor’s safety program shall include written policy and arrangements for the handling, storage and management of all hazardous materials to be used in the work in compliance with the requirements of the AHJ at the Project site.

9. The Contractor’s employees and subcontractor’s staff shall have received training as applicable in the use of hazardous materials and shall govern their actions accordingly.

1.5 References

A. All work shall conform to the following Codes and Standards, as applicable:

1. National Fire Protection Association (NFPA)

Standards.

2. National Electric Code (NEC) and applicable local

Electric Code.

3. Underwriters Laboratories (UL) listing and labels.

4. UL 864 UUKL Smoke Control

5. UL 268 Smoke Detectors.

6. UL 916 Energy Management

7. NFPA 70 - National Electrical Code.

8. NFPA 90A - Standard For The Installation Of Air

Conditioning And Ventilating Systems.

9. NFPA 92A and 92B Smoke Purge/Control Equipment.

10. Factory Mutual (FM).

11. American National Standards Institute (ANSI).

12. National Electric Manufacturer’s Association

(NEMA).

13. American Society of Mechanical Engineers (ASME).

14. American Society of Heating, Refrigerating and Air Conditioning Engineers (ASHRAE).

15. Air Movement and Control Association (AMCA).

16. Institute of Electrical and Electronic Engineers

(IEEE).

17. American Standard Code for Information Interchange

(ASCII).

18. Electronics Industries Association (EIA).

19. Occupational Safety and Health Administration

(OSHA).

Section 23 09 23 00 10 Page 9 of 57

20. American Society for Testing and Materials (ASTM).

21. Federal Communications Commission (FCC) including Part 15, Radio Frequency Devices.

22. Americans Disability Act (ADA)

23 ANSI/ASHRAE Standard 195-2004 (BACnet)

B. In the case of conflicts or discrepancies, the more stringent regulation shall apply.

C. All work shall meet the approval of the US Army Corps of

Engineers at the project site.

1.6 Submittals

A. Shop Drawings, Product Data, and Samples

1. The BMS contractor shall submit a list of all shop drawings with submittals dates within 30 days of contract award.

2. Submittals shall be in defined packages. Each package shall be complete and shall only reference itself and previously submitted packages. The packages shall be as approved by the Architect and

Engineer for Contract compliance.

3. Allow 15 working days for the review of each package by the Architect and Engineer in the scheduling of the total BMS work.

4. Equipment and systems requiring approval of local authorities must comply with such regulations and be approved. Filing shall be at the expense of the BMS Contractor where filing is necessary.

Provide a copy of all related correspondence and permits to the Owner.

5. Prepare an index of all submittals and shop drawings for the installation. Index shall include a shop drawing identification number, Contract Documents reference and item description.

6. The BMS Contractor shall correct any errors or omissions noted in the first review.

7. At a minimum, submit the following:

a. BMS network architecture diagrams including all nodes and interconnections.

b. Systems schematics, sequences and flow diagrams.

c. Points schedule for each point in the BMS, including: Point Type, Object Name, Expanded

ID, Display Units, Controller type, and

Address.

Section 23 09 23 00 10 Page 10 of 57

d. Samples of Graphic Display screen types and associated menus.

e. Detailed Bill of Material list for each system or application, identifying quantities, part numbers, descriptions, and optional features.

f. Control Damper Schedule including a separate line for each damper provided under this section and a column for each of the damper attributes, including: Code Number, Fail

Position, Damper Type, Damper Operator, Duct

Size, Damper Size, Mounting, and Actuator Type.

g. Control Valve Schedules including a separate line for each valve provided under this section and a column for each of the valve attributes:

Code Number, Configuration, Fail Position, Pipe

Size, Valve Size, Body Configuration, Close off

Pressure, Capacity, Valve CV, Design Pressure, and Actuator Type.

h. Room Schedule including a separate line for each VAV box and/or terminal unit indicating location and address

i. Details of all BMS interfaces and connections to the work of other trades.

j. Product data sheets or marked catalog pages including part number, photo and description for all products including software.

1.8 Record Documentation

A. Operation and Maintenance Manuals

1. Three (3) copies of the Operation and Maintenance

Manuals shall be provided to the Owner's

Representative upon completion of the project.

The entire Operation and Maintenance Manual shall include the following for the BMS provided:

a. Table of contents.

b. As-built system record drawings shall represent the as-built condition of the system and incorporate all information supplied with the approved submittal.

c. Manufacturers product data sheets or catalog pages for all products including software.

d. System Operator’s manuals.

e. Archive copy of all site-specific databases and sequences.

f. BMS network diagrams.

Section 23 09 23 00 10 Page 11 of 57

g. Interfaces to all third-party products and work by other trades.

1.9 Warranty

A. Standard Material and Labor Warranty:

1. Provide a one-year labor and material warranty on the BMS.

2. If within twelve (12) months from the date of acceptance of product, upon written notice from the owner, it is found to be defective in operation, workmanship or materials, it shall be replaced, repaired or adjusted at the option of the BMS Contractor at the cost of the BMS

Contractor.

3. Maintain an adequate supply of materials within

100 miles of the Project site such that replacement of key parts and labor support, including programming. Warranty work shall be done during BMS Contractor’s normal business hours.

2. Part 2 – Products

2.1 General Description

A. The Building Management System (BMS) shall use an open architecture and fully support a multi-vendor environment.

To accomplish this effectively, the BMS shall support open communication protocol standards and integrate a wide variety of third-party devices and applications. The system shall be designed for use on the Internet, or intranets using off the shelf, industry standard technology compatible with other owner provided networks.

B. The Building Management System shall consist of the following:

1. Standalone Network Automation Engine(s)

2. Field Equipment Controller(s)

3. Input/Output Module(s)

4. Local Display Device(s)

5. Portable Operator's Terminal(s)

6. Distributed User Interface(s)

7. Network processing, data storage and communications equipment

7. Other components required for a complete and working BMS

Section 23 09 23 00 10 Page 12 of 57

C. The system shall be modular in nature, and shall permit expansion of both capacity and functionality through the addition of sensors, actuators, controllers and operator devices, while re-using existing controls equipment.

D. System architectural design shall eliminate dependence upon any single device for alarm reporting and control execution.

1. The failure of any single component or network connection shall not interrupt the execution of control strategies at other operational devices.

2. The System shall maintain all settings and overrides through a system reboot.

E. System architectural design shall eliminate dependence upon any single device for alarm reporting and control execution.

2.2 BMS Architecture

A. Automation Network

1. The automation network shall be based on an industry standard of Ethernet TCP/IP. LAN controller cards shall be standard “off the shelf” products available through normal PC vendor channels.

2. All BMS devices on the automation network shall be capable of operating at a communication speed of

100 Mbps, with full peer-to-peer network communication.

3. Network Automation Engines (NAE) shall reside on the automation network.

4. The automation network will be compatible with other enterprise-wide networks. Where indicated, the automation network shall be connected to the enterprise network and share resources with it by way of standard networking devices and practices.

B. Control Network

1. Network Automation Engines (NAE) shall provide supervisory control over the control network and shall support the following communication protocols:

a. BACnet Standard MS/TP Bus Protocol ASHRAE SSPC-

135, Clause 9

The NAE shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

The NAE shall be tested and certified as a

BACnet Building Controller (B-BC).

Section 23 09 23 00 10 Page 13 of 57

b. The Johnson Controls N2 Field Bus.

2. Control networks shall provide either “Peer-to-

Peer,” Master-Slave, or Supervised Token Passing communications, and shall operate at a minimum communication speed of 9600 baud.

3. DDC Controllers shall reside on the control network.

4. Control network communication protocol shall be

BACnet Standard MS/TP Bus Protocol ASHRAE SSPC-

135.

C. Integration

1. BACnet Protocol Integration - BACnet

a. The neutral protocol used between systems will be BACnet over Ethernet and comply with the

ASHRAE BACnet standard 135-2003.

b. A complete Protocol Implementation Conformance

Statement (PICS) shall be provided for all

BACnet system devices.

c. The ability to command, share point object data, change of state (COS) data and schedules between the host and BACnet systems shall be provided.

2.3 User Interface

A. Human Machine Interface (HMI)

1. Where indicated on plans the BMS Contractor shall provide and install an HMI Display Terminal for command entry, information management, network alarm management, and database management

Rncluding scheduling, history collection and alarming, shall be resident in the BMS Network

Automation Engines to facilitate greater fault tolerance and reliability.

2. Dedicated User Interface Architecture – The architecture of the HMI shall be implemented to conform to industry standards, so that it can accommodate applications provided by the BMS

Contractor and by other third party applications suppliers.

a. Required network operating system for exchange of data and network functions such as printing of reports, trends and specific system summaries

2.4 Network Automation Engines (NAE)

Section 23 09 23 00 10 Page 14 of 57

A. Network Automation Engine (NAE 5510)

1. The Network Automation Engine (NAE) shall be a fully user-programmable, supervisory controller.

The NAE shall monitor the network of distributed application-specific controllers, provide global strategy and direction, and communicate on a peer-to-peer basis with other Network Automation

Engines.

2. Automation network – The NAE shall reside on the automation network and shall support a subnet of system controllers.

3. User Interface – Each NAE shall have the ability to deliver a web based User Interface. All computers connected physically or virtually to the automation network shall have access to the web based UI.

a. The web based UI software shall be imbedded in the NAE. Systems that require a local copy of the system database on the user’s personal computer are not acceptable.

b. The NAE shall support up a minimum of four (4) concurrent users.

c. The web based user shall have the capability to access all system data through one NAE.

d. Remote users connected to the network through an Internet Service Provider (ISP) or telephone dial up shall also have total system access through one NAE.

e. Systems that require the user to address more than one NAE to access all system information are not acceptable.

f. The NAE shall have the capability of generating web based UI graphics. The graphics capability shall be imbedded in the NAE.

g. Systems that support UI Graphics from a central database or require the graphics to reside on the user’s personal computer are not acceptable.

h. The web based UI shall support the following functions using a standard version of Microsoft

Internet Explorer:

Configuration

Commissioning

Data Archiving

Monitoring

Section 23 09 23 00 10 Page 15 of 57

Commanding

System Diagnostics

i. Systems that require workstation software or modified web browsers are not acceptable.

j. The NAE shall allow temporary use of portable devices without interrupting the normal operation of permanently connected modems.

4. Processor – The NAE shall be microprocessor-based with a minimum word size of 32 bits. The NAE shall be a multi-tasking, multi-user, and real-time digital control processor. Standard operating systems shall be employed. NAE size and capability shall be sufficient to fully meet the requirements of this Specification.

5. Memory – Each NAE shall have sufficient memory to support its own operating system, databases, and control programs, and to provide supervisory control for all control level devices.

6. Hardware Real Time Clock – The NAE shall include an integrated, hardware-based, real-time clock.

7. The NAE shall include troubleshooting LED indicators to identify the following conditions:

a. Power - On/Off

b. Ethernet Traffic – Ethernet Traffic/No Ethernet

Traffic

c. Ethernet Connection Speed – 10 Mbps/100 Mbps

d. FC Bus A – Normal Communications/No Field

Communications

e. FC Bus B – Normal Communications/No Field

Communications

f. Peer Communication – Data Traffic between NAE

Devices

g. Run – NAE Running/NAE in Startup/NAE Shutting

Down/Software Not Running

h. Bat Fault – Battery Defective, Data Protection

Battery Not Installed

i. 24 VAC – 24 VAC Present/Loss Of 24VAC

j. Fault – General Fault

k. Modem RX – NAE Modem Receiving Data

l. Modem TX – NAE Modem Transmitting Data

8. Communications Ports – The NAE shall provide the following ports for operation of operator

Input/Output (I/O) devices, such as industry-standard computers, modems, and portable operator’s terminals.

Section 23 09 23 00 10 Page 16 of 57

a. Two (2) USB port

b. Two (2) URS-232 serial data communication port

c. Two (2) RS-485 port

d. One (1) Ethernet port

9. Diagnostics – The NAE shall continuously perform self-diagnostics, communication diagnosis, and diagnosis of all panel components. The Network

Automation Engine shall provide both local and remote annunciation of any detected component failures, low battery conditions, or repeated failures to establish communication.

10. Power Failure – In the event of the loss of normal power, The NAE shall continue to operate for a user adjustable period of up to 10 minutes after which there shall be an orderly shutdown of all programs to prevent the loss of database or operating system software.

a. During a loss of normal power, the control sequences shall go to the normal system shutdown conditions. All critical configuration data shall be saved into Flash memory.

b. Upon restoration of normal power and after a minimum off-time delay, the controller shall automatically resume full operation without manual intervention through a normal soft-start sequence.

11. Certification – The NAE shall be listed by Underwriters Laboratories (UL).

12. Controller network – The NAE shall support the following communication protocols on the controller network:

a. The NAE shall support BACnet Standard MS/TP Bus

Protocol ASHRAE SSPC-135, Clause 9 on the controller network.

The NAE shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

The NAE shall be tested and certified as a

BACnet Building Controller (B-BC).

A BACnet Protocol Implementation

Conformance Statement shall be provided for the NAE.

The Conformance Statements shall be submitted 10 days prior to bidding.

Section 23 09 23 00 10 Page 17 of 57

The NAE shall support a minimum of 100 control devices.

b. The NAE shall support the Johnson Controls N2

Field Bus.

The NAE shall support a minimum of 100 N2 control devices.

The Bus shall conform to Electronic

Industry Alliance (EIA) Standard RS-485.

The Bus shall employ a master/slave protocol where the NAE is the master.

The Bus shall employ a four (4) level priority system for polling frequency.

The Bus shall be optically isolated from the NAE.

The Bus shall support the Metasys

Integrator System.

2.5 Network Control Engine (NCE 2510)

1. The Network Control Engine (NCE) shall be a fully user-programmable, supervisory controller. The

NCE shall monitor the network of distributed application-specific controllers, provide global strategy and direction, and communicate on a peer-to-peer basis with other Network Automation

Engines. NCEs may be used for AHU and Central

Plant Room Applications.

2. The Network Control Engine (NCE) shall be a fully user-programmable, digital controller that includes a minimum of 33 I/O points.

3. Automation Network – The NCE shall reside on the automation network and shall support a subnet of

32 Field controllers.

4. User Interface – Each NCE shall have the ability to deliver a web based User Interface (UI) as previously described. All computers connected physically or virtually to the automation network shall have access to the web based UI.

a. The web based UI software shall be imbedded in the NCE. Systems that require a local copy of the system database on the user’s personal computer are not acceptable.

b. The NCE shall support a minimum of two (2) concurrent users.

Section 23 09 23 00 10 Page 18 of 57

c. The NCE shall have the capability of generating web based UI graphics. The graphics capability shall be imbedded in the NCE.

d. Systems that support UI Graphics from a central database or require the graphics to reside on the user’s personal computer are not acceptable.

e. The web based UI shall support the following functions using a standard version of Microsoft

Internet Explorer:

Configuration

Commissioning

Data Archiving

Monitoring

Commanding

System Diagnostics

f. Systems that require workstation software or modified web browsers are not acceptable.

g. The NCE shall allow temporary use of portable devices without interrupting the normal operation of permanently connected modems.

5. The NCE shall employ a finite state control engine to eliminate unnecessary conflicts between control functions at crossover points in their operational sequences. Suppliers using non-state based DDC shall provide separate control strategy diagrams for all controlled functions in their submittals.

6. The NCE shall be factory programmed with a continuous adaptive tuning algorithm that senses changes in the physical environment and continually adjusts loop tuning parameters appropriately. Controllers that require manual tuning of loops or perform automatic tuning on command only, shall not be acceptable.

7. The NCE shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-

5VB.

8. The NCE shall support the following number and types of inputs and outputs:

a. Ten Universal Inputs - shall be configured to monitor any of the following:

Analog Input, Voltage Mode

Analog Input, Current Mode

Analog Input, Resistive Mode

Section 23 09 23 00 10 Page 19 of 57

Binary Input, Dry Contact Maintained Mode

Binary Input, Pulse Counter Mode

b. Eight Binary Inputs - shall be configured to monitor either of the following:

Dry Contact Maintained Mode

Pulse Counter Mode

c. Four Analog Outputs - shall be configured to output either of the following

Analog Output, Voltage Mode

Analog Output, Current Mode

d. Seven Binary Outputs - shall output the following:

24 VAC Triac

e. Four Configurable Outputs - shall be configured to output either of the following:

Analog Output, Voltage Mode

Binary Output, 24 VAC Triac Mode

9. The NCE shall have the ability to monitor and control a network of sensors and actuators over a

Sensor-Actuator Bus (SA Bus).

a. The SA Bus shall be a Master-Slave/Token-

Passing (MS/TP) Bus supporting BACnet Standard protocol SSPC-135, Clause 9.

b. The SA Bus shall support a minimum of 10 devices.

c. The SA Bus shall operate at a maximum distance of 1,200 Ft. between the NCE and the furthest connected device.

10. The NCE shall have the capability to execute complex control sequences involving direct wired

I/O points as well as input and output devices communicating over the Field Trunk or the SA Bus.

11. The NCE shall support, but not be limited to, the following applications:

a. Central Equipment including chillers and boilers

b. Lighting and electrical distribution

c. Built-up air handling units for special applications

d. Power generation and energy monitoring equipment

e. Interfaces to security and fire detection systems

Section 23 09 23 00 10 Page 20 of 57

12. The NCE shall support a Local Controller Display (DIS1710) either as an integral part of the NCE or as a remote device communicating over the SA Bus.

a. The Display shall use a BACnet Standard SSPC-

135, clause 9 Master-Slave/Token-Passing protocol.

b. The Display shall allow the user to view monitored points without logging into the system.

c. The Display shall allow the user to view and change setpoints, modes of operation, and parameters.

d. The Display shall provide password protection with user adjustable password timeout.

e. The Display shall be menu driven with separate paths for:

Input/Output

Parameter/Setpoint

Overrides

f. The Display shall use easy-to-read English text messages.

g. The Display shall allow the user to select the points to be shown and in what order.

h. The Display shall support a back lit Liquid

Crystal Display (LCD) with adjustable contrast and brightens and automatic backlight brightening during user interaction.

i. The display shall be a minimum of 4 lines and a minimum of 20 characters per line

j. The Display shall have a keypad with no more than 6 keys.

k. The Display shall be panel mountable.

13. The NCE shall be microprocessor-based with a minimum word size of 32 bits. The NAE shall be a multi-tasking, multi-user, and real-time digital control processor. Standard operating systems shall be employed. NCE size and capability shall be sufficient to fully meet the requirements of this Specification.

14. The NCE shall employ an industrial single board computer.

15. Each NCE shall have sufficient memory to support its own operating system, databases, and control programs, and to provide supervisory control for all control level devices.

Section 23 09 23 00 10 Page 21 of 57

16. The NCE shall include an integrated, hardware-based, real-time clock.

17. The NCE shall employ nonvolatile Flash memory to store all programs and data. The NCE shall employ a data protection battery to save data and power the real time clock when primary power is interrupted.

18. The NCE shall provide removable, color coded, screw terminal blocks for 24 VAC power, communication bus and I/O point field wiring.

19. The NCE shall include troubleshooting LED indicators to identify the following conditions:

a. Power

b. Fault

c. SA Bus

d. FC Bus

e. Modem TX

f. Modem RX

g. Battery Fault

h. Ethernet

i. 10 LNK

j. 100 LNK

k. Run

l. Peer Com

20. Communications Ports – The NCE shall provide the following ports for operation of operator

Input/Output (I/O) devices, such as industry-standard computers, modems, and portable operator’s terminals.

a. USB port

b. RS-232 serial data communication port

c. RS-485 port

d. RJ-45 Ethernet port

e. RJ-12 jack

21. Diagnostics – The NCE shall continuously perform self-diagnostics, communication diagnosis, and diagnosis of all panel components. The Network

Control Engine shall provide both local and remote annunciation of any detected component failures, low battery conditions, or repeated failures to establish communication.

22. Power Failure – In the event of the loss of normal power, The NCE shall continue to operate for a user adjustable period of up to 10 minutes after

Section 23 09 23 00 10 Page 22 of 57 which there shall be an orderly shutdown of all programs to prevent the loss of database or operating system software.

a. During a loss of normal power, the control sequences shall go to the normal system shutdown conditions. All critical configuration data shall be saved into Flash memory.

b. Upon restoration of normal power and after a minimum off-time delay, the controller shall automatically resume full operation without manual intervention through a normal soft-start sequence.

23. Certification – The NCE shall be listed by Underwriters Laboratories (UL).File E107041, CCN

PAZX, UL 916, Energy Management Equipment. FCC

Compliant to CFR47, Part 15, Subpart B, Class A

24. Field Controller Bus – The NCE shall support the following communication protocols on the Field

Controller Bus:

a. The NCE shall support BACnet Standard MS/TP Bus

Protocol ASHRAE SSPC-135, Clause 9 on the controller network.

The NCE shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

The NAE shall be tested and certified as a

BACnet Building Controller (B-BC).

A BACnet Protocol Implementation

Conformance Statement shall be provided for the NCE.

The Conformance Statements shall be submitted 10 days prior to bidding.

The NCE shall support a minimum of 32 control devices.

control devices.

b. The NCE shall support the N2 devices on the

Field Controller Bus (Johnson Controls N2 Bus).

The NCE shall support a minimum of 32 N2 control devices.

The Bus shall conform to Electronic

Industry Alliance (EIA) Standard RS-485.

The Bus shall employ a master/slave protocol where the NCE is the master.

The Bus shall employ a four (4) level priority system for polling frequency.

Section 23 09 23 00 10 Page 23 of 57

The Bus shall be optically isolated from the NCE.

The Bus shall support the Metasys

Integrator System.

2.6 DDC System Controllers

A. BACnet Field Equipment Controller (FEC 2610 and FEC 1610)

1. The Field Equipment Controller (FEC) shall be a fully user-programmable, digital controller that communicates via BACnet MS/TP protocol.

a. The FEC shall support BACnet Standard MS/TP Bus

Protocol ASHRAE SSPC-135, Clause 9 on the controller network.

The FEC shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

The FEC shall be tested and certified as a

BACnet Application Specific Controller (B-

ASC).

A BACnet Protocol Implementation

Conformance Statement shall be provided for the FEC.

The Conformance Statement shall be submitted 10 days prior to bidding.

2. The FEC shall employ a finite state control engine to eliminate unnecessary conflicts between control functions at crossover points in their operational sequences. Suppliers using non-state based DDC shall provide separate control strategy diagrams for all controlled functions in their submittals.

3. Controllers shall be factory programmed with a continuous adaptive tuning algorithm that senses changes in the physical environment and continually adjusts loop tuning parameters appropriately. Controllers that require manual tuning of loops or perform automatic tuning on command only shall not be acceptable. The FEC shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-5VB.

4. The FEC shall include a removable base to allow pre-wiring without the controller.

5. The FEC shall include troubleshooting LED indicators to identify the following conditions:

a. Power On

b. Power Off

Section 23 09 23 00 10 Page 24 of 57

c. Download or Startup in progress, not ready for normal operation

d. No Faults

e. Device Fault

f. Field Controller Bus - Normal Data Transmission

g. Field Controller Bus - No Data Transmission

h. Field Controller Bus - No Communication

i. Sensor-Actuator Bus - Normal Data Transmission

j. Sensor-Actuator Bus - No Data Transmission

k. Sensor-Actuator Bus - No Communication

6. The FEC shall accommodate the direct wiring of analog and binary I/O field points.

7. The FEC shall support the following types of inputs and outputs:

a. Universal Inputs - shall be configured to monitor any of the following:

Analog Input, Voltage Mode

Analog Input, Current Mode

Analog Input, Resistive Mode

Binary Input, Dry Contact Maintained Mode

Binary Input, Pulse Counter Mode

b. Binary Inputs - shall be configured to monitor either of the following:

Dry Contact Maintained Mode

Pulse Counter Mode

c. Analog Outputs - shall be configured to output either of the following

Analog Output, Voltage Mode

Analog Output, current Mode

d. Binary Outputs - shall output the following:

24 VAC Triac

e. Configurable Outputs - shall be capable of the following:

Analog Output, Voltage Mode

Binary Output Mode

8. The FEC shall have the ability to reside on a

Field Controller Bus (FC Bus).

a. The FC Bus shall be a Master-Slave/Token-

Passing (MS/TP) Bus supporting BACnet Standard protocol SSPC-135, Clause 9.

b. The FC Bus shall support communications between the FECs and the NAE.

Section 23 09 23 00 10 Page 25 of 57

c. The FC Bus shall also support Input/Output

Module (IOM) communications with the FEC and with the NAE.

d. The FC Bus shall support a minimum of 100 IOMs and FECs in any combination.

e. The FC Bus shall operate at a maximum distance of 15,000 Ft. between the FEC and the furthest connected device.

f.

9. The FEC shall have the ability to monitor and control a network of sensors and actuators over a

Sensor-Actuator Bus (SA Bus).

a. The SA Bus shall be a Master-Slave/Token-

Passing (MS/TP) Bus supporting BACnet Standard

Protocol SSPC-135, Clause 9.

b. The SA Bus shall support a minimum of 10 devices per trunk.

c. The SA Bus shall operate at a maximum distance of 1,200 Ft. between the FEC and the furthest connected device.

10. The FEC shall have the capability to execute complex control sequences involving direct wired

I/O points as well as input and output devices communicating over the FC Bus or the SA Bus.

11. The FEC shall support, but not be limited to, the following:

a. Chilled water/central plant automation applications including but not limited to the selection and sequencing of up to 8 chillers of different sizes (constant or variable speed capacity control), 8 primary and secondary chilled water pumps, as well as selection and sequencing of cooling towers and bypass valve.

Sequencing of the devices shall consider user-defined efficiency ratings, runtime equalization and number-of-starts/number-of -stops.

b. Heating central plant applications

c. Built-up air handling units for special applications

c. Terminal units

d. Special programs as required for systems control

Section 23 09 23 00 10 Page 26 of 57

12. The FEC shall support a Local Controller Display (DIS1710) either as an integral part of the FEC or as a remote device communicating over the SA Bus.

a. The Display shall use a BACnet Standard SSPC-

135, clause 9 Master-Slave/Token-Passing protocol.

b. The Display shall allow the user to view monitored points without logging into the system.

c. The Display shall allow the user to view and change setpoints, modes of operation, and parameters.

d. The Display shall provide password protection with user adjustable password timeout.

e. The Display shall be menu driven with separate paths for:

Input/Output

Parameter/Setpoint

Overrides

f. The Display shall use easy-to-read English text messages.

g. The Display shall allow the user to select the points to be shown and in what order.

h. The Display shall support a back lit Liquid

Crystal Display (LCD) with adjustable contrast and brightens and automatic backlight brightening during user interaction.

i. The display shall be a minimum of 4 lines and a minimum of 20 characters per line

j. The Display shall have a keypad with no more than 6 keys.

k. The Display shall be panel mountable.

2.7 Field Devices

A. Input/Output Module (IOM s)

1. The Input/Output Module (IOM) provides additional inputs and outputs for use in the FEC.

2. The IOM shall communicate with the FEC over the FC

Bus or the SA Bus.

3. The IOM shall support BACnet Standard MS/TP Bus

Protocol ASHRAE SSPC-135, Clause 9 on the controller network.

Section 23 09 23 00 10 Page 27 of 57

a. The IOM shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

b. The IOM shall be tested and certified as a

BACnet Application Specific Controller (B-ASC).

c. A BACnet Protocol Implementation Conformance

Statement shall be provided for the FEC.

d. The Conformance Statement shall be submitted 10 days prior to bidding.

4. The IOM shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-

5VB.

5. The IOM shall have a minimum of 4 points to a maximum of 17 points.

6. The IOM shall support the following types of inputs and outputs:

a. Universal Inputs - shall be configured to monitor any of the following:

Analog Input, Voltage Mode

Analog Input, Current Mode

Analog Input, Resistive Mode

Binary Input, Dry Contact Maintained Mode

Binary Input, Pulse Counter Mode

b. Binary Inputs - shall be configured to monitor either of the following:

Dry Contact Maintained Mode

Pulse Counter Mode

c. Analog Outputs - shall be configured to output either of the following

Analog Output, Voltage Mode

Analog Output, current Mode

d. Binary Outputs - shall output the following:

24 VAC Triac

e. Configurable Outputs - shall be capable of the following:

Analog Output, Voltage Mode

Binary Output Mode

7. The IOM shall include troubleshooting LED indicators to identify the following conditions:

a. Power On

b. Power Off

c. Download or Startup in progress, not ready for normal operation

d. No Faults

Section 23 09 23 00 10 Page 28 of 57

e. Device Fault

f. Normal Data Transmission

g. No Data Transmission

h. No Communication

B. Networked Thermostat (TEC 2600 Series)

1. The networked thermostat shall be capable of controlling two- or four-pipe fan coils, cabinet unit heaters or other similar equipment.

2. The TEC shall communicate over the Field

Controller Bus using BACnet Standard MS/TP Bus

Protocol ASHRAE SSPC-135, Clause 9.

3. The TEC shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

a. The TEC shall be tested and certified as a

BACnet Application Specific Controller (B-ASC).

b. A BACnet Protocol Implementation Conformance

Statement shall be provided for the TEC.

c. The Conformance Statement shall be submitted 10 days prior to bidding.

4. The Networked Thermostat shall support remote read/write and parameter adjustment from the web based User Interfaceable through a Network

Automation Engine.

5. The Networked Thermostat shall include an intuitive User Interface providing plain text messages.

a. Two line, 8 character backlit display

b. LED indicators for Fan, Heat, and Cool status

c. Five (5) User Interface Keys

Mode

Fan

Override

Degrees C/F

Up/Down

d. The display shall continuously scroll through the following parameters:

Room Temperature

System Mode

Schedule Status –

Occupied/Unoccupied/Override

Applicable Alarms

Section 23 09 23 00 10 Page 29 of 57

6. The Networked Thermostat shall provide the flexibility to support any one of the following inputs:

a. Integral Indoor Air Temperature Sensor

b. Duct Mount Air Temperature Sensor

c. Remote Indoor Air Temperature Sensor with

Occupancy Override and LED Indicator

d. Two configurable binary inputs

7. The Networked Thermostat shall provide the flexibility to support any one of the following outputs:

a. Three Speed Fan Control

b. Two On/Off

c. Two Floating

d. Two Proportional (0 to 10V)

8. The Networked Thermostat shall provide a minimum of six (6) levels of keypad lockout.

9. The Networked Thermostat shall provide the flexibility to adjust the following parameters:

a. Adjustable Temporary Occupancy from 0 to 24 hours

b. Adjustable heating/cooling deadband from 2º F to 5º F

c. Adjustable heating/cooling cycles per hour from

4 to 8

10. Where required by application and indicated on plans or room schedules provide the Networked

Thermostat with an integral Passive Infra-Red

(PIR) occupancy sensor.

11. The Networked Thermostat shall employ nonvolatile electrically erasable programmable read-only memory (EEPROM) for all adjustable parameters.

12. .

C. VAV Modular Assembly (VMA 1615 and 1630)

1. The VAV Modular Assembly shall provide both standalone and networked direct digital control of pressure-independent, variable air volume terminal units. It shall address both single and dual duct applications.

2. The VMA shall be BACnet Testing Labs (BTL) certified and carry the BTL Label.

a. The VMA shall be tested and certified as a

BACnet Application Specific Controller (B-ASC).

Section 23 09 23 00 10 Page 30 of 57

b. A BACnet Protocol Implementation Conformance

Statement shall be provided for the VMA.

c. The Conformance Statement shall be submitted 10 days prior to bidding.

3. The VAV Modular Assembly shall communicate over the FC Bus using BACnet Standard protocol SSPC-

135, Clause 9.

4. The VAV Modular Assembly shall have internal electrical isolation for AC power, DC inputs, and

MS/TP communications. An externally mounted isolation transformer shall not be acceptable.

5. The VAV Modular Assembly shall be a configurable digital controller with integral differential pressure transducer and damper actuator. All components shall be connected and mounted as a single assembly that can be removed as one piece.

6. The VAV Modular Assembly shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-5VB.

7. The integral damper actuator shall be a fast response stepper motor capable of stroking 90 degrees in 30 seconds for quick damper positioning to speed commissioning and troubleshooting tasks.

8. The controller shall determine airflow by dynamic pressure measurement using an integral dead-ended differential pressure transducer. The transducer shall be maintenance-free and shall not require air filters.

9. Each controller shall have the ability to automatically calibrate the flow sensor to eliminate pressure transducer offset error due to ambient temperature / humidity effects.

10. The controller shall utilize a proportional plus integration (PI) algorithm for the space temperature control loops.

11. Each controller shall continuously, adaptively tune the control algorithms to improve control and controller reliability through reduced actuator duty cycle. In addition, this tuning reduces commissioning costs, and eliminates the maintenance costs of manually re-tuning loops to compensate for seasonal or other load changes.

12. The controller shall provide the ability to download and upload VMA configuration files, both locally and via the…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.