Attachment 09-230923 Direct Digital Control System for HVAC.pdf

Wilmington VA Medical Center EHRM Infrastructure Upgrades

Project No. 460-22-700 June 30, 2025

Version 03-01-23

Direct-Digital Control System For HVAC 23 09 23 - 1

SECTION 23 09 23

DIRECT-DIGITAL CONTROL SYSTEM FOR HVAC

PART 1 - GENERAL

1.1 DESCRIPTION

General Contractor shall provide direct-digital control system(s) as indicated on the project documents, point list, interoperability tables, drawings and as described in these specifications. Include a complete and working direct-digital control system. Include all engineering, programming, configuration/setup hardware and software, controls and installation materials, installation labor, commissioning and startup, training, final project documentation and warranty.

1. The direct-digital control system(s) shall consist of high-speed, peer-to-peer network of DDC controllers, a control system server, all configuration and setup software and hardware devices, and an Engineering Control Center. Provide a remote user using a standard HTML 5 web browser to access the control system graphics and change adjustable setpoints with the proper password.

2. All new building controllers shall be native BACnet. All new BACnet workstations, controllers, devices and components shall be listed by BACnet Testing Laboratories.

All new BACnet workstations, controllers, devices and components shall be accessible using a HTML5 Web browser interface. Browsers shall not require the use of an extension or add on software in order to access aforementioned workstations, controllers, devices, and components.

a. If used, gateways shall be BTL listed.

b. If used, gateways shall provide all object properties and read/write services shown on VA-approved interoperability schedules.

3. The work administered by this Section of the technical specifications shall include all labor, materials, special tools, equipment, enclosures, power supplies, software, software licenses, Project specific software configurations and database entries, interfaces, wiring, tubing, installation, labeling, engineering, calibration, documentation, submittals, testing, verification, training services, permits and licenses, transportation, shipping, handling, administration, supervision, 23 09 23 - 2 management, insurance, Warranty, specified services and any other items required for a complete and fully functional Controls System.

4. The control systems shall be designed such that each mechanical system shall operate under stand-alone mode. The A/E shall designate what each “mechanical systems” is composed of. The contractor administered by this Section of the technical specifications shall provide controllers for each mechanical system. In the event of a network communication failure, or the loss of any other controller, the control system shall continue to operate independently. Failure of the ECC shall have no effect on the field controllers, including those involved with global strategies.

Some products are furnished but not installed by the contractor administered by this

Section of the technical specifications. The contractor administered by this Section of the technical specifications shall formally coordinate in writing and receive from other contractors formal acknowledgements in writing prior to submission the installation of the products.

Some products are installed but not furnished by the contractor administered by this

Section of the technical specifications. The contractor administered by this Section of the technical specifications shall formally coordinate in writing and receive from other contractors formal acknowledgements in writing prior to submission the procurement of the products. These products include but are not limited to the following:

1. Factory-furnished accessory thermostats and sensors furnished with unitary equipment.

Some products are not provided by, but are nevertheless integrated with the work executed by, the contractor administered by this Section of the technical specifications. These products include but are not limited to the following:

1. Fire alarm systems. If zoned fire alarm is required by the project-specific requirements, this interface shall require multiple relays, which are provided and installed by the fire alarm system contractor, to be monitored.

2. Unitary HVAC equipment controls. These include:

a. Discharge temperature control.

b. Setpoint reset.

c. Time of day indexing.

d. Status alarm.

23 09 23 - 3

3. The following systems have limited control (as individually noted below) from the

ECC:

a. Constant temperature rooms: temperature out of acceptable range and status alarms.

Responsibility Table:

Work/Item/System Furnish Install Low Voltage Wiring

Line Power

Control system low voltage and communication wiring

23 09 23 23 09 23 23 09 23 N/A

LAN conduits and raceway 23 09 23 23 09 23 N/A N/A

Current Switches 23 09 23 23 09 23 23 09 23 N/A

Control Relays 23 09 23 23 09 23 23 09 23 N/A

Computer Room A/C Unit field-mounted controls

23 23 26 26

Control system interface with CRU A/C controls

23 09 23 23 09 23 23 09 23 26

CRU A/C unit controls interface with control system

23 23 09 23 23 09 23 26

This facility’s existing direct-digital control (DDC) system is manufactured by Johnson

Controls International - Metasys Building Automation, and it has an existing ECC. The contractor administered by this Section of the technical specifications shall observe the capabilities, communication network, services, spare capacity of the existing control system and its ECC prior to beginning work. The contractor administered by this section to complete installation and programming of new Johnson Controls International - Metasys Building

Automation controls to match the existing installed system to ensure and maintain proper operation of existing BAS system.

1. The combined system shall operate and function as one complete system including one database of control point objects and global control logic capabilities. Facility operators shall have complete operations and control capability over all systems, new and existing including; monitoring, trending, graphing, scheduling, alarm

23 09 23 - 4 management, global point sharing, global strategy deployment, graphical operations interface and custom reporting as specified.

1.2 RELATED WORK

Section 23 31 00, HVAC Ducts and Casings.

Section 23 81 00, Decentralized Unitary HVAC Equipment.

Section 23 81 23, Computer-Room Air-Conditioners.

Section 26 05 11, Requirements for Electrical Installations.

Section 26 05 21, Low-Voltage Electrical Power Conductors and Cables (600 Volts and

Below).

Section 26 05 26, Grounding and Bonding for Electrical Systems.

Section 26 05 33, Raceway and Boxes for Electrical Systems.

Section 26 22 21, Specialty Transformers.

Section 26 27 26, Wiring Devices.

Section 26 29 11, Motor Starters.

Section 27 15 00, Communications Horizontal Cabling.

Section 28 31 00, Fire Detection and Alarm.

1.3 DEFINITION

Algorithm: A logical procedure for solving a recurrent mathematical problem; A prescribed set of well-defined rules or processes for the solution of a problem in a finite number of steps.

Analog: A continuously varying signal value (e.g., temperature, current, velocity etc.

BACnet: A Data Communication Protocol for Building Automation and Control Networks

-as defined by ANSI/ASHRAE Standard 135. This communications protocol allows diverse building automation devices to communicate data and services over a network.

BACnet/IP: Annex J of Standard 135. It defines and allows for using a reserved UDP socket to transmit BACnet messages over IP networks. A BACnet/IP network is a collection of one or more IP sub-networks that share the same BACnet network number.

BACnet Internetwork: Two or more BACnet networks connected with routers. The two networks may use different LAN technologies.

BACnet Network: One or more BACnet segments that have the same network address and are interconnected by bridges at the physical and data link layers.

23 09 23 - 5

BACnet Segment: One or more physical segments of BACnet devices on a BACnet network, connected at the physical layer by repeaters.

BACnet Broadcast Management Device (BBMD): A communications device which broadcasts BACnet messages to all BACnet/IP devices and other BBMDs connected to the same BACnet/IP network.

BACnet Interoperability Building Blocks (BIBBs): BACnet Interoperability Building Blocks

(BIBBs) are collections of one or more BACnet services. These are prescribed in terms of an

"A" and a "B" device. Both of these devices are nodes on a BACnet internetwork.

BACnet Testing Laboratories (BTL). The organization responsible for testing products for compliance with the BACnet standard, operated under the direction of BACnet International.

Baud: It is a signal change in a communication link. One signal change can represent one or more bits of information depending on type of transmission scheme. Simple peripheral communication is normally one bit per Baud. (e.g., Baud rate = 78,000 Baud/sec is 78,000 bits/sec, if one signal change = 1 bit).

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

BMP or bmp: Suffix, computerized image file, used after the period in a DOS-based computer file to show that the file is an image stored as a series of pixels.

Bus Topology: A network topology that physically interconnects workstations and network devices in parallel on a network segment.

Control Unit (CU): Generic term for any controlling unit, stand-alone, microprocessor based, digital controller residing on secondary LAN or Primary LAN, used for local controls or global controls

Deadband: A temperature range over which no heating or cooling is supplied, i.e., 22-25 degrees C (72-78 degrees F), as opposed to a single point change over or overlap).

Device: a control system component that contains a BACnet Device Object and uses

BACnet to communicate with other devices.

Device Object: 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.

23 09 23 - 6

Device Profile: A specific group of services describing BACnet capabilities of a device, as defined in ASHRAE Standard 135, Annex L. Standard device profiles include BACnet

Operator Workstations (B-OWS), 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). Each device used in new construction is required to have a PICS statement listing which service and BIBBs are supported by the device.

Diagnostic Program: A software test program, which is used to detect and report system or peripheral malfunctions and failures. Generally, this system is performed at the initial startup of the system.

Direct Digital Control (DDC): Microprocessor based control including Analog/Digital conversion and program logic. A control loop or subsystem in which digital and analog information is received and processed by a microprocessor, and digital control signals are generated based on control algorithms and transmitted to field devices in order to achieve a set of predefined conditions.

Distributed Control System: A system in which the processing of system data is decentralized and control decisions can and are made at the subsystem level. System operational programs and information are provided to the remote subsystems and status is reported back to the Engineering Control Center. Upon the loss of communication with the

Engineering Control center, the subsystems shall be capable of operating in a stand-alone mode using the last best available data.

Download: The electronic transfer of programs and data files from a central computer or operation workstation with secondary memory devices to remote computers in a network

(distributed) system.

DXF: An AutoCAD 2-D graphics file format. Many CAD systems import and export the

DXF format for graphics interchange.

Electrical Control: A control circuit that operates on line or low voltage and uses a mechanical means, such as a temperature sensitive bimetal or bellows, to perform control functions, such as actuating a switch or positioning a potentiometer.

23 09 23 - 7

Electronic Control: A control circuit that operates on low voltage and uses a solid-state components to amplify input signals and perform control functions, such as operating a relay or providing an output signal to position an actuator.

Engineering Control Center (ECC): The centralized control point for the intelligent control network. The ECC comprises of personal computer and connected devices to form a single workstation.

Ethernet: A trademark for a system for exchanging messages between computers on a local area network using coaxial, fiber optic, or twisted-pair cables.

Firmware: Firmware is software programmed into read only memory (ROM) chips.

Software may not be changed without physically altering the chip.

Gateway: Communication hardware connecting two or more different protocols. It translates one protocol into equivalent concepts for the other protocol. In BACnet applications, a gateway has BACnet on one side and non-BACnet (usually proprietary) protocols on the other side.

GIF: Abbreviation of Graphic interchange format.

Graphic Program (GP): Program used to produce images of air handler systems, fans, chillers, pumps, and building spaces. These images can be animated and/or color-coded to indicate operation of the equipment.

Graphic Sequence of Operation: It is a graphical representation of the sequence of operation, showing all inputs and output logical blocks.

I/O Unit: The section of a digital control system through which information is received and transmitted. I/O refers to analog input (AI, digital input (DI), analog output (AO) and digital output (DO). Analog signals are continuous and represent temperature, pressure, flow rate etc., whereas digital signals convert electronic signals to digital pulses (values), represent motor status, filter status, on-off equipment etc.

I/P: a method for conveying and routing packets of information over LAN paths. User

Datagram Protocol (UDP) conveys information to “sockets” without confirmation of receipt.

Transmission Control Protocol (TCP) establishes "sessions", which have end-to-end confirmation and guaranteed sequence of delivery.

JPEG: A standardized image compression mechanism stands for Joint Photographic

Experts Group, the original name of the committee that wrote the standard.

23 09 23 - 8

Local Area Network (LAN): A communication bus that interconnects operator workstation and digital controllers for peer-to-peer communications, sharing resources and exchanging information.

Network Repeater: A device that receives data packet from one network and rebroadcasts to another network. No routing information is added to the protocol.

MS/TP: Master-slave/token-passing (ISO/IEC 8802, Part 3). It uses twisted-pair wiring for relatively low speed and low cost communication.

Native BACnet Device: A device that uses BACnet as its primary method of communication with other BACnet devices without intermediary gateways. A system that uses native BACnet devices at all levels is a native BACnet system.

Network Number: A site-specific number assigned to each network segment to identify for routing. This network number must be unique throughout the BACnet internetwork.

Object: The concept of organizing BACnet information into standard components with various associated properties. Examples include analog input objects and binary output objects.

Object Identifier: An object property used to identify the object, including object type and instance. Object Identifiers must be unique within a device.

Object Properties: Attributes of an object. Examples include present value and high limit properties of an analog input object. Properties are defined in ASHRAE 135; some are optional and some are required. Objects are controlled by reading from and writing to object properties.

Operating system (OS): Software, which controls the execution of computer application programs.

PCX: File type for an image file. When photographs are scanned onto a personal computer they can be saved as PCX files and viewed or changed by a special application program as Photo Shop.

Peripheral: Different components that make the control system function as one unit.

Peripherals include monitor, printer, and I/O unit.

Peer-to-Peer: A networking architecture that treats all network stations as equal partners- any device can initiate and respond to communication with other devices.

PICS: Protocol Implementation Conformance Statement, describing the BACnet capabilities of a device. All BACnet devices have published PICS.

23 09 23 - 9

PID: Proportional, integral, and derivative control, used to control modulating equipment to maintain a setpoint.

Repeater: A network component that connects two or more physical segments at the physical layer.

Router: a component that joins together two or more networks using different LAN technologies. Examples include joining a BACnet Ethernet LAN to a BACnet MS/TP LAN.

Sensors: devices measuring state points or flows, which are then transmitted back to the

DDC system.

Thermostats : devices measuring temperatures, which are used in control of standalone or unitary systems and equipment not attached to the DDC system.

1.4 QUALITY ASSURANCE

Criteria:

1. Single Source Responsibility of subcontractor: Either the DDC Contractor or the

System Integrator shall obtain hardware and software supplied under this Section and delegate the responsibility to a single source controls installation subcontractor.

The Integration subcontractor shall be responsible for the complete design, installation, integration, and commissioning of the system. The controls subcontractor shall be in the business of design, installation and service of such building automation control systems similar in size and complexity.

2. Equipment and Materials: Equipment and materials shall be cataloged products of manufacturers regularly engaged in production and installation of HVAC control systems. Products shall be manufacturer’s latest standard design and have been tested and proven in actual use.

3. The controls subcontractor shall provide a list of no less than five similar projects which have building control systems as specified in this Section. These projects must be on-line and functional such that the Department of Veterans Affairs (VA) representative could observe the control systems in full operation.

4. The controls subcontractor shall have an in-place facility within 100 miles with technical staff, spare parts inventory for the next five (5) years, and necessary test and diagnostic equipment to support the control systems.

23 09 23 - 10

5. The controls subcontractor shall have minimum of three years of experience in design and installation of building automation systems similar in performance to those specified in this Section. Provide evidence of experience by submitting resumes of the project manager, the local branch manager, project engineer, the application engineering staff, and the electronic technicians who would be involved with the supervision, the engineering, and the installation of the control systems.

Training and experience of these personnel shall not be less than three years.

Failure to disclose this information will be a ground for disqualification of the supplier.

6. Provide a competent and experienced Project Manager employed by the Controls

Contractor. The Project Manager shall be supported as necessary by other

Contractor employees in order to provide professional engineering, technical and management service for the work. The Project Manager shall attend scheduled

Project Meetings as required and shall be empowered to make technical, scheduling and related decisions on behalf of the Controls Contractor.

Codes and Standards:

1. All work shall conform to the applicable Codes and Standards.

2. Electronic equipment shall conform to the requirements of FCC Regulation, Part 15, Governing Radio Frequency Electromagnetic Interference, and be so labeled.

1.5 PERFORMANCE

The system shall conform to the following:

1. Graphic Display: The system shall display up to four (4) graphics on a single screen with a minimum of twenty (20) dynamic points per graphic. All current data shall be displayed within ten (10) seconds of the request.

2. Graphic Refresh: The system shall update all dynamic points with current data within eight (8) seconds. Data refresh shall be automatic, without operator intervention.

3. Object Command: The maximum time between the command of a binary object by the operator and the reaction by the device shall be two(2) seconds. Analog objects shall start to adjust within two (2) seconds.

4. Object Scan: All changes of state and change of analog values shall be transmitted over the high-speed network such that any data used or displayed at a controller or work-station will be current, within the prior six (6) seconds.

23 09 23 - 11

5. Alarm Response Time: The maximum time from when an object goes into alarm to when it is annunciated at the workstation shall not exceed (10) seconds.

6. Program Execution Frequency: Custom and standard applications shall be capable of running as often as once every (5) seconds. The Contractor shall be responsible for selecting execution times consistent with the mechanical process under control.

7. Multiple Alarm Annunciations: All workstations on the network shall receive alarms within five (5) seconds of each other.

8. Performance: Programmable Controllers shall be able to execute DDC PID control loops at a selectable frequency from at least once every one (1) second. The controller shall scan and update the process value and output generated by this calculation at this same frequency.

9. Reporting Accuracy: Listed below are minimum acceptable reporting end-to-end accuracies for all values reported by the specified system:

Measured Variable Reported Accuracy

Space temperature ±0.5 degrees C (±1 degrees F)

Relative humidity ±2 percent RH

10. Control stability and accuracy: Control sequences shall maintain measured variable at setpoint within the following tolerances:

Controlled Variable Control Accuracy Range of Medium

Space Temperature ±1.0ºC (±2.0 degrees F)

Humidity ±5 percent RH MRI, SPS, PHARMACY

11. Extent of direct digital control: control design shall allow for at least the points indicated on the points lists on the drawings.

1.6 WARRANTY

Labor and materials for control systems shall be warranted for a period as specified under Warranty in FAR clause 52.246-21.

Control system failures during the warranty period shall be adjusted, repaired, or replaced at no cost or reduction in service to the owner. The system includes all computer equipment, transmission equipment, and all sensors and control devices.

The on-line support service shall allow the Controls supplier to dial out over telephone lines to or connect via (through password-limited access) VPN through the internet to monitor

23 09 23 - 12 and control the facility’s building automation system. This remote connection to the facility shall be within two (2) hours of the time that the problem is reported. This coverage shall include normal business hours, after business hours, weekend and holidays. If the problem cannot be resolved with on-line support services, the Controls supplier shall dispatch the qualified personnel to the job site to resolve the problem within 8 hours after the problem is reported.

Controls subcontractor shall be responsible for temporary operations and maintenance of the control systems during the construction period until final commissioning, training of facility operators and acceptance of the project by VA.

1.7 SUBMITTALS

Submit shop drawings in accordance with Section 01 33 23, SHOP DRAWINGS, PRODUCT DATA, AND SAMPLES.

Information and material submitted under this section shall be marked “SUBMITTED

UNDER SECTION 23 09 23, DIRECT-DIGITAL CONTROL SYSTEM FOR HVAC”, with applicable paragraph identification.

Manufacturer’s Literature and Data Including:

1. A wiring diagram for each type of input device and output device including DDC controllers, modems, repeaters, etc. Diagram shall show how the device is wired and powered, showing typical connections at the digital controllers and each power supply, as well as the device itself. Show for all field connected devices, including but not limited to, control relays, motor starters, electric or electronic actuators, and temperature pressure, flow and humidity sensors and transmitters.

2. A diagram of each terminal strip, including digital controller terminal strips, terminal strip location, termination numbers and the associated point names.

3. Control dampers and control valves schedule, including the size and pressure drop.

4. Control air-supply components, and computations for sizing compressors, receivers and main air-piping, if pneumatic controls are furnished.

5. Catalog cut sheets of all equipment used. This includes, but is not limited to software

(by manufacturer and by third parties), DDC controllers, panels, peripherals, airflow measuring stations and associated components, and auxiliary control devices such as sensors, actuators, and control dampers. When manufacturer’s cut sheets apply to a product series rather than a specific product, the data specifically applicable to

23 09 23 - 13 the project shall be highlighted. Each submitted piece of literature and drawings should clearly reference the specification and/or drawings that it supposed to represent.

6. Sequence of operations for each system and the associated control diagrams.

Equipment and control labels shall correspond to those shown on the drawings.

7. Color prints of proposed graphics with a list of points for display.

8. Furnish a BACnet Protocol Implementation Conformance Statement (PICS) for each

BACnet-compliant device.

9. Schematic wiring diagrams for all control, communication and power wiring. Provide a schematic drawing of the central system installation. Label all cables and ports with computer manufacturers’ model numbers and functions. Show all interface wiring to the control system.

10. An instrumentation list for each controlled system. Each element of the controlled system shall be listed in table format. The table shall show element name, type of device, manufacturer, model number, and product data sheet number.

11. Riser diagrams of wiring between central control unit (CCU) and all control panels.

12. Plan drawings showing routing of LAN and locations of control panels, controllers, routers, gateways, ECC, and larger controlled devices.

13. Construction details for all installed conduit, cabling, raceway, cabinets, and similar.

Construction details of all penetrations and their protection.

14. Quantities of submitted items may be reviewed but it is the responsibility of the contractor administered by this Section of the technical specifications to provide sufficient quantities for a complete and working system.

Product Certificates: Compliance with Article, QUALITY ASSURANCE.

Validation Test Plan: Along with manufacturer’s literature, product certificates, wiring and functional diagrams, and sequence of operations, submit for review and approval a Validation

Test Plan which is specific to the work of this project and which references the specific controls component nomenclatures found in the control contractor’s wiring and functional diagrams and the specific sequences of controls for this project and which describes how the contractor will implement the controls system validation and demonstration as specified in paragraph 3.2

SYSTEM VALIDATION AND DEMONSTRATION found in this section.

23 09 23 - 14

Licenses: Provide licenses for all software residing on and used by the Controls

Systems, ECC, and portable OWS and transfer these licenses to the Owner prior to completion.

As Built Control Drawings:

1. Furnish three (3) copies of as-built drawings for each control system. The documents shall be submitted for approval prior to final completion.

2. Furnish one (1) set of applicable control system prints for each mechanical system for wall mounting. The documents shall be submitted for approval prior to final completion.

3. Furnish one (1) CD-ROM in CAD DWG and/or .DXF format for the drawings noted in subparagraphs above.

Operation and Maintenance (O/M) Manuals):

1. Submit in accordance with Article, INSTRUCTIONS, in Specification Section 01 00

00, GENERAL REQUIREMENTS.

2. Include the following documentation:

a. General description and specifications for all components, including logging on/off, alarm handling, producing trend reports, overriding computer control, and changing set points and other variables.

b. Detailed illustrations of all the control systems specified for ease of maintenance and repair/replacement procedures, and complete calibration procedures.

c. One copy of the final version of all software provided including operating systems, programming language, operator workstation software, and graphics software.

d. Complete troubleshooting procedures and guidelines for all systems.

e. Complete operating instructions for all systems.

f. Recommended preventive maintenance procedures for all system components including a schedule of tasks for inspection, cleaning and calibration. Provide a list of recommended spare parts needed to minimize downtime.

g. Training Manuals: Submit the course outline and training material to the Owner for approval three (3) weeks prior to the training to VA facility personnel. These persons will be responsible for maintaining and the operation of the control

23 09 23 - 15 systems, including programming. The Owner reserves the right to modify any or all of the course outline and training material.

h. Licenses, guaranty, and other pertaining documents for all equipment and systems.

Submit Performance Report to COR prior to final inspection.

1.8 INSTRUCTIONS

Instructions to VA operations personnel: Perform in accordance with Article, INSTRUCTIONS, in Specification Section 01 00 00, GENERAL REQUIREMENTS, and as noted below. Contractor shall also video tape instruction sessions noted below.

1. First Phase: Formal instructions to the VA facilities personnel for a total of 16 hours, given in multiple training sessions (each no longer than four hours in length), conducted sometime between the completed installation and prior to the performance test period of the control system, at a time mutually agreeable to the

Contractor and the VA.

2. Second Phase: This phase of training shall comprise of on the job training during startup, checkout period, and performance test period. VA facilities personnel will work with the Contractor’s installation and test personnel on a daily basis during startup and checkout period. During the performance test period, controls subcontractor will provide 16 hours of instructions, given in multiple training sessions (each no longer than four hours in length), to the VA facilities personnel.

3. The O/M Manuals shall contain approved submittals as outlined in Article 1.7, SUBMITTALS. The Controls subcontractor will review the manual contents with VA facilities personnel during second phase of training.

4. Training shall be given by direct employees of THE CONTROLS system subcontractor.

1.9 PROJECT CONDITIONS (ENVIRONMENTAL CONDITIONS OF OPERATION)

The ECC and peripheral devices and system support equipment shall be designed to operate in ambient condition of 20 to 35 degrees C (65 to 90 degrees F) at a relative humidity of

20 to 80 percent non-condensing.

The Controllers used outdoors shall be mounted in NEMA 4 waterproof enclosures, and shall be rated for operation at –40 to 65 degrees C (-40 to 150 degrees F).

23 09 23 - 16

All electronic equipment shall operate properly with power fluctuations of plus 10 percent to minus 15 percent of nominal supply voltage.

Sensors and controlling devices shall be designed to operate in the environment, which they are sensing or controlling.

1.10 APPLICABLE PUBLICATIONS

The publications listed below form a part of this specification to the extent referenced.

The publications are referenced in the text by the basic designation only. Where conflicts occur these specifications and the VHA standards will govern.

American Society of Heating, Refrigerating, and Air-Conditioning Engineers (ASHRAE):

135-2020 .............................. BACnet A Data Communication Protocol for Building

Automation and Control Networks

147-2019 .............................. Reducing the Release of Halogenated Refrigerants from

Refrigerating and Air-Conditioning Equipment and Systems

Federal Communication Commission (FCC):

Rules and Regulations Title 47 Chapter 1-2014 Part 15: Radio Frequency Devices

Institute of Electrical and Electronic Engineers (IEEE):

802.3-2018 ........................... Standard for Ethernet

National Fire Protection Association (NFPA):

70-2020 ................................ National Electric Code

PART 2 - PRODUCTS

2.1 MATERIALS

Use new products that the manufacturer is currently manufacturing and that have been installed in a minimum of 25 installations. Spare parts shall be available for at least five years after completion of this contract.

2.2 CONTROLS SYSTEM ARCHITECTURE

General

1. The Controls Systems shall consist of multiple Nodes and associated equipment connected by industry standard digital and communication network arrangements.

2. The ECC, building controllers and principal communications network equipment shall be standard products of recognized major manufacturers available through normal

23 09 23 - 17

PC and computer vendor channels – not "Clones" assembled by a third-party subcontractor.

3. The networks shall, at minimum, comprise, as necessary, the following:

a. A fixed ECC and a portable operator’s terminal.

b. Network computer processing, data storage and BACnet-compliant communication equipment including Servers and digital data processors.

c. BACnet-compliant routers, bridges, switches, hubs, modems, gateways, interfaces and similar communication equipment.

d. Active processing BACnet-compliant building controllers connected to other

BACnet-compliant controllers together with their power supplies and associated equipment.

e. Addressable elements, sensors, transducers and end devices.

f. Third-party equipment interfaces and gateways as described and required by the

Contract Documents.

g. Other components required for a complete and working Control Systems as specified.

The Specifications for the individual elements and component subsystems shall be minimum requirements and shall be augmented as necessary by the Contractor to achieve both compliance with all applicable codes, standards, and to meet all requirements of the Contract

Documents.

Network Architecture

1. The Controls communication network shall utilize BACnet communications protocol operating over a standard Ethernet LAN and operate at a minimum speed of 100

Mb/sec.

2. The networks shall utilize only copper and optical fiber communication media as appropriate and shall comply with applicable codes, ordinances and regulations.

3. All necessary telephone lines, ISDN lines and internet Service Provider services and connections will be provided by the VA.

Third Party Interfaces:

1. The contractor administered by this Section of the technical specifications shall include necessary hardware, equipment, software and programming to allow data

23 09 23 - 18 communications between the controls systems and building systems supplied by other trades.

2. Other manufacturers and contractors supplying other associated systems and equipment shall provide their necessary hardware, software and startup at their cost and shall cooperate fully with the contractor administered by this Section of the technical specifications in a timely manner and at their cost to ensure complete functional integration.

Servers:

1. Provide data storage server(s) to archive historical data including trends, alarm and event histories and transaction logs.

2. Equip these server(s) with the same software tool set that is located in the BACnet building controllers for system configuration and custom logic definition and color graphic configuration.

3. Access to all information on the data storage server(s) shall be through the same browser functionality used to access individual nodes. When logged onto a server the operator will be able to also interact with any other controller on the control system as required for the functional operation of the controls systems. The contractor administered by this Section of the technical specifications shall provide all necessary digital processor programmable data storage server(s).

4. These server(s) shall be utilized for controls systems application configuration, for archiving, reporting and trending of data, for operator transaction archiving and reporting, for network information management, for alarm annunciation, for operator interface tasks, for controls application management and similar.

2.3 COMMUNICATION

Control products, communication media, connectors, repeaters, hubs, and routers shall comprise a BACnet internetwork. Controller and operator interface communication shall conform to ANSI/ASHRAE Standard 135, BACnet.

1. The Data link / physical layer protocol between the ECC and all B-BC’s (for communication) acceptable to the VA throughout its facilities is Ethernet (ISO 8802-

3) and BACnet/IP.

23 09 23 - 19

2. The MS/TP data link / physical layer protocol is prohibited to the VA in any new

BACnet network or sub-network in its healthcare or lab facilities.

Each controller shall have a communication port for connection to an operator interface.

Project drawings indicate remote buildings or sites to be connected by a nominal 56,000 baud modem over voice-grade telephone lines. In each remote location a modem and field device connection shall allow communication with each controller on the internetwork as specified in Paragraph D.

Internetwork operator interface and value passing shall be transparent to internetwork architecture.

1. An operator interface connected to a controller shall allow the operator to interface with each internetwork controller as if directly connected. Controller information such as data, status, reports, system software, and custom programs shall be viewable and editable from each internet controller.

2. Inputs, outputs, and control variables used to integrate control strategies across multiple controllers shall be readable by each controller on the internetwork. Program and test all cross-controller links required to execute specified control system operation. An authorized operator shall be able to edit cross-controller links by typing a standard object address.

System shall be expandable to at least twice the required input and output objects with additional controllers, associated devices, and wiring. Expansion shall not require operator interface hardware additions or software revisions.

ECCs and Controllers with real-time clocks shall use the BACnet Time Synchronization service. The system shall automatically synchronize system clocks daily from an operator-designated device via the internetwork. The system shall automatically adjust for daylight savings and standard time as applicable.

2.4 BACnet PROTOCOL ANALYZER

For ease of troubleshooting and maintenance, provide a BACnet protocol analyzer.

Provide its associated fittings, cables and appurtenances, for connection to the communications network. The BACnet protocol analyzer shall be able to, at a minimum: capture and store to a file all data traffic on all network levels; measure bandwidth usage; filter out (ignore) selected traffic.

23 09 23 - 20

2.5 NETWORK AND DEVICE NAMING CONVENTION

Network Numbers

1. BACnet network numbers shall be based on a "facility code, network" concept. The

"facility code" is the VAMC’s or VA campus’ assigned numeric value assigned to a specific facility or building. The "network" typically corresponds to a "floor" or other logical configuration within the building. BACnet allows 65535 network numbers per

BACnet internet work.

2. The network numbers are thus formed as follows: "Net #" = "FFFNN" where:

a. FFF = Facility code (see below)

b. NN = 00-99 This allows up to 100 networks per facility or building

Device Instances

1. BACnet allows 4194305 unique device instances per BACnet internet work. Using

Agency's unique device instances are formed as follows: "Dev #" = "FFFNNDD" where

a. FFF and N are as above and

b. DD = 00-99, this allows up to 100 devices per network.

2. Note Special cases, where the network architecture of limiting device numbering to

DD causes excessive subnet works. The device number can be expanded to DDD and the network number N can become a single digit. In NO case shall the network number N and the device number D exceed 4 digits.

3. Facility code assignments:

4. 000-400 Building/facility number

5. Note that some facilities have a facility code with an alphabetic suffix to denote wings, related structures, etc. The suffix will be ignored. Network numbers for facility codes greater than 400 will be assigned in the range 000-399.

Device Names

1. Name the control devices based on facility name, location within a facility, the system or systems that the device monitors and/or controls, or the area served. The intent of the device naming is to be easily recognized. Names can be up to 254 characters in length, without embedded spaces. Provide the shortest descriptive, but unambiguous, name. For example, in building #123 prefix the number with a “B”

23 09 23 - 21 followed by the building number, if there is only one chilled water pump "CHWP-1", a valid name would be "B123.CHWP. 1.STARTSTOP". If there are two pumps designated "CHWP-1", one in a basement mechanical room (Room 0001) and one in a penthouse mechanical room (Room PH01), the names could be

"B123.R0001.CHWP.1. STARTSTOP" or "B123.RPH01.CHWP.1.STARTSTOP". In the case of unitary controllers, for example a VAV box controller, a name might be

"B123.R101.VAV". These names should be used for the value of the "Object_Name" property of the BACnet Device objects of the controllers involved so that the BACnet name and the EMCS name are the same.

2.6 BACnet DEVICES

All BACnet Devices – controllers, gateways, routers, actuators, Operator Displays, and sensors shall conform to BACnet Device Profiles and shall be BACnet Testing Laboratories

(BTL) -Listed as conforming to those Device Profiles. Protocol Implementation Conformance

Statements (PICSs), describing the BACnet capabilities of the Devices shall be published and available for the Devices through links in the BTL website.

1. BACnet Building Controllers, shall conform to the BACnet B-BC Device Profile, and shall be BTL-Listed as conforming to the B-BC Device Profile. The Device’s PICS shall be submitted.

2. BACnet Advanced Application Controllers shall conform to the BACnet B-AAC

Device Profile and shall be BTL-Listed as conforming to the B-AAC Device Profile.

The Device’s PICS shall be submitted.

3. BACnet Application Specific Controllers shall conform to the BACnet B-ASC Device

Profile and shall be BTL-Listed as conforming to the B-ASC Device Profile. The

Device’s PICS shall be submitted.

4. BACnet Smart Actuators shall conform to the BACnet B-SA Device Profile and shall be BTL-Listed as conforming to the B-SA Device Profile. The Device’s PICS shall be submitted.

5. BACnet Smart Sensors shall conform to the BACnet B-SS Device Profile and shall be BTL-Listed as conforming to the B-SS Device Profile. The Device’s PICS shall be submitted.

23 09 23 - 22

6. BACnet routers and gateways shall conform to the BACnet B-OTH Device Profile, and shall be BTL-Listed as conforming to the B-OTH Device Profile. The Device’s

PICS shall be submitted.

2.7 CONTROLLERS

General. Provide an adequate number of BTL listed B-BC building controllers, BTL listed

B-AAC, BTL listed B-ASC, BTL listed B-SA, and BTL listed B-SS’s to achieve the performance specified in the Part 1 Article on “System Performance.” Each of these controllers shall meet the following requirements.

1. Communication.

a. Each B-BC controller shall reside on a BACnet network using the ISO 8802-3

(Ethernet) Data Link/Physical layer protocol for its communications.

b. Each B-BC controller shall provide a service communication port using BACnet

Data Link/Physical layer protocol for connection to a portable operator’s terminal.

If this port is not available built into the controller, contractor is to install a 4 port unmanaged switch inside the B-BC control cabinet.

2. Keypad. A local keypad and display shall be provided for each controller. The keypad shall be provided for interrogating and editing data. Provide a system security password to prevent unauthorized use of the keypad and display.

3. Serviceability. Provide diagnostic LEDs for power, communication, and processor. All wiring connections shall be made to field-removable, modular terminal strips or to a termination card connected by a ribbon cable.

4. Memory. The controller shall maintain all BIOS and programming information in the event of a power loss for at least 72 hours.

5. The controller shall be able to operate at 90 percent to 110 percent of nominal voltage rating and shall perform an orderly shutdown less than 80 percent nominal voltage. Controller operation shall be protected against electrical noise of 5 to 120 Hz and from keyed radios up to 5 watt at 1 meter (3 feet).

6. Transformer. Power supply for the ASC must be rated at a minimum of 125 percent of B-ASC power consumption and shall be of the fused or current limiting type.

23 09 23 - 23

Provide BTL-Listed B-ASC application specific controllers for each piece of equipment for which they are constructed. Application specific controllers shall communicate with other

BACnet devices on the internetwork using the BACnet Read (Execute) Property service.

1. Each B-ASC shall be capable of stand-alone operation and shall continue to provide control functions without being connected to the network.

2. Each B-ASC will contain sufficient I/O capacity to control the target system.

3. Communication.

a. Each controller shall reside on a BACnet network using the ISO 8802-3

(Ethernet) Data Link/Physical layer protocol for its communications. Each building controller also shall perform BACnet routing if connected to a network of custom application and application specific controllers.

b. Each controller shall have a BACnet Data Link/Physical layer compatible connection for a laptop computer or a portable operator’s tool. This connection shall be extended to a space temperature sensor port where shown.

4. Serviceability. Provide diagnostic LEDs for power, communication, and processor. All wiring connections shall be made to field-removable, modular terminal strips or to a termination card connected by a ribbon cable.

5. Memory. The application specific controller shall use nonvolatile memory and maintain all BIOS and programming information in the event of a power loss.

6. Immunity to power and noise. Controllers shall be able to operate at 90 percent to

110 percent of nominal voltage rating and shall perform an orderly shutdown below

80 percent. Operation shall be protected against electrical noise of 5-120 Hz and from keyed radios up to 5 watts at 1 meter (3 feet).

Direct Digital Controller Software

1. The software programs specified in this section shall be commercially available, concurrent, multi-tasking operating system and support the use of software application that operates under Microsoft Windows.

2. All points shall be identified by up to 30-character point name and 16-character point descriptor. The same names shall be used at the ECC.

3. All control functions shall execute within the stand-alone control units. All new controllers installed will also include all software and/or hardware required to

23 09 23 - 24 program, commission, or alter the sequence of operation of said controller(s).

Controllers requiring software or hardware that is not commercially available will not be allowed. Installation of software and/or hardware for controller configuration will be the responsibility of the DDC contractor. COR will direct to install said hardware and/or software on either the B-AWS or portable operator terminal. The VA shall be able to customize control strategies and sequences of operations defining the appropriate control loop algorithms and choosing the optimum loop parameters without requiring the services of a DDC contractor.

4. All controllers shall be capable of being programmed to utilize stored default values for assured fail-safe operation of critical processes. Default values shall be invoked upon sensor failure or, if the primary value is normally provided by the central or another CU, or by loss of bus communication. Individual application software packages shall be structured to assume a fail-safe condition upon loss of input sensors. Loss of an input sensor shall result in output of a sensor-failed message at the ECC. Each ACU and RCU shall have capability for local readouts of all functions.

The UCUs shall be read remotely.

5. All DDC control loops shall be able to utilize any of the following control modes:

a. Two position (on-off, slow-fast) control.

b. Proportional control.

c. Proportional plus integral (PI) control.

d. Proportional plus integral plus derivative (PID) control. All PID programs shall automatically invoke integral wind up prevention routines whenever the controlled unit is off, under manual control of an automation system or time-initiated program.

e. Automatic tuning of control loops.

6. System Security: Operator access shall be secured using individual password and operator’s name. Passwords shall restrict the operator to the level of object, applications, and system functions assigned to him. A minimum of three (3)or a maximum of six (6) levels of security for operator access shall be provided.

7. Application Software: The controllers shall provide the…