23 09 23 - CONTROLS FOR HVAC REV 1.pdf

FAA | AJW-2E11A

EWR, ATCT, HVAC SPLIT-SYSTEM INSTALLATION

APRIL 2026

CONTROLS FOR HVAC 23 09 23 - 1

REV 1

SECTION 23 09 23 - CONTROLS FOR HVAC

PART 1 - GENERAL

1.1 RELATED DOCUMENTS

A. Drawings and general provisions of the Contract, including General and Supplementary Conditions and Division 1 Specification Sections, apply to this section.

1.2 RELATED SECTIONS

A. This section includes the Building Management System (BMS) control equipment for HVAC (Heating, Ventilation and Air Conditioning) systems and components, including but not limited to Servers, Network Controllers, Field Bus Controllers, Sensors, End Devices and communication networks required for a complete and functional control system.

B. Depending on the scope of the project, the complete specification may have numerous sections that interface to this section, including several from Divisions 23 and 26.

C. The scope of work for this project is to provide integration of the ductless split system in the the existing BMS system including all necessary components to meet the requirements of the sequence of operations. As part of the integration adjustments to the operation of AHU-3 and related VAV boxes will be required to optimize the system operation including changes to the reset schedule as necessary to assure temperature control withing the ranges specified for all areas of the base building served by AHU 3.

1.3 DEFINITION OF TERMS AND ABBREVIATIONS

A. Architecture for BMS Systems:

1. Bus Topology: A term used to describe the sequential connection of devices on a LON segment. The communication cable runs from device to device with no tees or stubs from the main communication cable to a device. Also referred to as daisy chain wiring.

2. Channel: A LON network consisting of one segment with no LON routers or repeaters or multiple segments connected by repeaters.

3. Field Bus: Field bus is a generic term referring to control networks that connect multiple control devices that share a common protocol and common electrical communication characteristics. A field bus does not use TCP/IP for data transfer. Two very common examples are the FT-10A LON field bus and the RS485 Shielded Twisted Pair field bus.

4. Free Topology: A data wiring topology supported by LON that allows for loops, tees, y-connections, etc. When this topology is used, only one terminator of a specific design is required and allowable cable lengths are significantly reduced.

5. LAN (Local Area Network): A LAN is an organizations IP network serving a local area where data transfer between multiple components on the LAN does not involve transport over public physical IP networks.

6. LON to LON Router: A physical device used to connect two channels. These devices filter message traffic based on subnet numbers.

CONTROLS FOR HVAC 23 09 23 - 2

7. Repeater: A physical device used to connect two segments. A repeater does not filter any message traffic. A repeater does isolate physical problems such as short circuits to a single segment and is typically required to allow the use of additional devices or additional cable length.

8. Terminator: An electronic component that consists of a resistive and capacitive circuit specifically designed to enhance the quality of communications on a segment. With bus topology, a termination device is required at both ends of the segment. With free topology, only one termination device is required at any point on the network.

9. WAN (Wide Area Network): This is also referred to as the Enterprise Network. The WAN is an organizations IP network that is made up of a collection of Local Area Networks (LAN) belonging to the organization. Dataflow between LANs may utilize public physical networks but the dataflow is private and secure.

a. BMS Control Components: The detailed technical specifications for the following components are included in Section 2.

1) ASC (Application Specific Controller): A subset of application specific devices (ASD). An ASC has physical inputs, physical outputs and control logic. It does not fit in the category of sensor or end device. Example: Xenta 102AX VAV controller.

2) ASD (Application Specific Device): A sensor, controller, or end device that is pre-programmed by the vendor. It may have physical inputs and physical outputs. The control logic, while not programmable, may be configurable through the use of configuration parameters. The application may require input network variables and may send output network variables. Example:

Xenta 422A IO Device when commissioned in a stand-alone mode

3) DCU (Distributed Control Unit): A proprietary name for a programmable process controller in the INET product line.

4) ES (Enterprise Server): A computer hosted server that coagulates the databases from multiple Network Server Controllers. Example:

SmartStruxure Enterprise Server

5) NSC (Network Server Controller): An IP level controller and router. It connects to the IP level of the system architecture to multiple field busses that use LonTalk, BACNet MSTP and ModBus RTU. It may also support a field bus that uses a proprietary protocol such as the Schneider Electric INET protocol. Example: SmartStruxure Automation Server

6) PEM (Packaged Equipment Module): An application specific controller that is native to a HVAC equipment item. Within the HVAC industry these controllers will typically fall into one of three categories; LON, BACnet or Modbus. Example: A VFD with an integral LON communications card

7) PCU (Process Control Unit): A proprietary name for a programmable process controller in the INET product line.

8) PPC (Programmable Process Controller): A controller with provisions for all of the physical inputs and physical outputs associated with a single mechanical component such as a terminal unit, air-handling unit and chiller.

The control logic for the sequence of control is created using an application programming editor that is compatible with the controller. A programmable process controller may or may not have data management features such as time schedules, trend data storage and alarm message generation capabilities.

These features may be provided by another device using network

CONTROLS FOR HVAC 23 09 23 - 3

communication to and from the PPC. Example: Xenta 302 Programmable Controller

9) SLC (Supervisory Logic Controller): A device that does not use physical inputs or physical outputs. It collects data over the network from other devices, applies logic to the data, generates instructions for use by other devices and sends the instructions to the appropriate device. Example: Xenta 401B Programmable Controller

10) Add other device descriptions as necessary.

b. BMS Tools and Software

1) Application Programming Tool: A software tool used to create control logic for use in a Network Server Controller, a Programmable Process Controller or a Supervisory Logic Controller. Application Programming Tools are vendor unique and may require a separate operating license.

2) Graphical Programming: A concept where mathematical and logical algorithms are represented by graphical objects. Control logic is laid out by placing objects on a palate and connecting the output of one object to the input of the next object.

3) Graphics Editor: A software tool use to create dynamic graphical displays.

A Graphics Editor is vendor unique and may require a separate operating license.

4) Line Programming: Application programming that uses line by line code that is similar to FORTRAN, Basic or C+ programming. Master programs and subroutines are created to meet a sequence of control.

5) Web Server: Software that is installed on an Enterprise Server and/or Network Server Controllers to enable access by an operator using an industry standard web browser such as Internet Explorer or Google Chrome.

6) Workstation Presentation Software: Vendor unique software that allows an operator to access an Enterprise Server and/or a Network Server Controller for operation or engineering purposes.

c. Communication

1) Bandwidth Utilization: The average utilization of the network in percent measured over a specified period of time as measured by a protocol analyzer.

2) Data Propagation Parameters: To ensure appropriate data transfer from device to device without excessive bandwidth utilization, sending devices will utilize a combination of communication parameters.

a) Maximum Send Time: An adjustable parameter that defines the maximum time period between multiple transmissions of the same data element. This parameter ensures periodic data transfer even if the data has not changed its state or value.

b) Minimum Send Time: An adjustable parameter that defines a mandatory time period during which the device must wait prior to sending the same data element a second time. This parameter ensures that data is not sent too often resulting in excessive bandwidth utilization.

c) Send on Delta: An adjustable parameter that defines a requirement to send an element of data as a result of the data changing by an amount

CONTROLS FOR HVAC 23 09 23 - 4

that exceeds this parameter’s value. For binary data, a change of state is the default. Minimum send time and maximum send time parameters have priority over send on delta. Between the minimum send time and the maximum send time, the send on delta will govern the sending of data.

d) The maximum send time parameter is mandatory.

e) Either the minimum send time parameter or the send on delta parameter must be used. Both may be used. When minimum send time is not used, the system performs as if the minimum send time is zero seconds.

d. Control Applications

1) Algorithm Execution Sample Rate: How often a mathematical algorithm in a controller generates a new or updated value.

2) Analog Calibration Offsets: For all analog input measured variables, there is a requirement to adjust the value measured by the hardware based analog input point to match the value reported by a certified test instrument.

3) Dead Zone: With respect the performance of a PID algorithm, the dead zone is the range of an input variable to the PID above and below the set point for which the output of the PID algorithm shall not be changed. Once the input variable gets within the dead zone, it is fruitless to attempt changes to get the input variable any closer to the set point. Assigning a dead zone to a PID loop improves stability and reduces wear and tear on the actuator.

4) Dynamic Data: Data that is calculated within control logic and is viewable by the system operator.

5) Floating Control: Floating control is a control loop algorithm used for fast responding airside and waterside pressure and flow control loops. Key parameters are the set point, the neutral zone, the bump rate and the algorithm sample rate.

6) Forced by Operator: Sometimes referred to as Manual Control. When a software object is “Forced by Operator”, the value or state of the object is assigned by the operator and a value or state that flows to the object from another object or by physical measurement is blocked.

7) PID: Proportional-Integral-Derivative control. Key parameters are the set point, the gain, the interval time constant, the derivative time constant and the dead zone. Integral gain is defined as the gain divided by the interval time constant. Derivative gain is defined as the gain multiplied by the derivative time constant.

8) Points: Software objects associated with physical inputs and physical outputs (sensors and end devices). Input points receive their value or state from a sensor. Output points receive their value or state from the control logic.

9) User Adjustable Parameters: Parameters within the control logic that have a fixed but adjustable value or state. The value or state is set by the system operator. The parameters are initially programmed with a default value.

e. Equipment

1) AHU-3 (Air Handling Unit)

2) AC-3 (Air Conditioning System Outdoor Unit)

3) AC-3A (Air Conditioning System Indoor Unit)

4) AC-3B (Air Conditioning System Indoor Unit)

CONTROLS FOR HVAC 23 09 23 - 5

5) AC-3C (Air Conditioning System Indoor Unit)

6) TU (Terminal Unit)

7) VAV (Variable Air Volume)

f. Facilities

1) FAA facilities are typically operational 24/7. As such, some work in existing facilities may require off normal work hours.

g. Qualified System

1) The DDC Control System shall be the SmartStruxure System as manufactured by Schneider Electric.

a) Field Bus Controllers for new work shall be from the Xenta LON family of field bus controllers.

b) The b3 BACnet, MNL Lon and MNB BACnet field bus controllers under SmartStruxure shall not be used for new work.

2) HVAC components with integral PEMs that utilize one of the following protocols may be part of the proposed solution.

a) BACnet MSTP

b) BACnet IP

h. Pre-Approved Bidders: Only pre-approved installers are eligible to perform work on Terminal FAA projects. The following companies are known to be pre-approved installers for this project.

1) Future Controls, Inc., 5719 Zip Drive, Suite 1, Fort Meyers, Florida 33905, 800-330-1303, Attn: Thomas Hansen, Jr.

2) C-Tech, 116 Portland Road, Whitehouse, Tennessee 37188, 615-672-8210, Attn: Jim Brown.

i. Qualifications:

1) All work described in this document shall be installed, wired, circuit tested and calibrated by factory certified technicians qualified for this work and in the regular employment of the approved manufacturer’s local field office.

2) The approved manufacturer’s local field office shall have a minimum of 3 years of installation experience with the manufacturer and shall provide documentation in the bid and submittal package to verify this requirement has been met.

3) Supervision, hardware and software engineering, calibration, tuning and functional testing of the system shall be by the employees of the approved manufacturer’s local field office and shall not be subcontracted.

4) The BMS contractor shall have factory certified technicians and engineers, spare parts inventory and all necessary test and diagnostic equipment for the installed system.

5) The BMS contractor shall have 24 hour per, 7 days per week emergency service available.

1.4 SCOPE OF WORK

CONTROLS FOR HVAC 23 09 23 - 6

A. The contractor shall furnish, install and commission an addition to the recent newly installed building automation system including all necessary hardware, networks, wiring, custom applications and operating software required to perform the control sequences of operation as called for in this specification and on the contract drawings. Systems to be controlled shall include but not be limited to:

1. Air Handling Unit -3 (AHU3)

2. AC-3 (Air Conditioning System Outdoor Unit)

3. AC-3A (Air Conditioning System Indoor Unit)

4. AC-3B (Air Conditioning System Indoor Unit)

5. AC-3C (Air Conditioning System Indoor Unit)

6. Variable Air Volume Terminal Units with and without fans and reheat

B. This modification to the building automation system shall, as a minimum, include the following items. The technical specifications for each of these items are included in Part 2 of this document.

1. All necessary Field Bus Controllers at the field bus level of the system architecture.

2. All necessary WAN/LAN controllers that use the BACnet IP or ModBus TCP protocols.

3. All necessary sensors, transducers, relays, valves, valve operators, dampers, damper operators, control panels and other accessory equipment.

4. All necessary network wiring and electrical interlocking wiring to meet the intent of the specification and provide a complete and operable system.

a. All wires shall be labeled at both ends to facility wire tracing

5. All control components shall be labeled so that the component can be easily associated with the design drawings/submittals.

6. All network wiring and hardware required to integrate existing Schneider Electric INET systems as required by the contract drawings.

7. Power wiring to BMS components and except as otherwise specified. Power wiring shall be provided under Division 26 (Electrical).

8. All custom applications in the Enterprise Server, Network Server Controllers, Programmable Process Controllers and Supervisory Logic Controllers.

9. Fully configured applications in all application specific devices.

10. All modifications to Schneider Electric INET applications required to enable the combined systems to meet the complete sequences of operation.

11. All trend logs required by this specification and the contract drawings.

12. All alarms with alarm routing required by this specification and the contract drawings.

13. All operator graphic pages required by this specification and the contract drawings.

C. Work Associated With Other Contractors

1. The BMS Contractor shall cooperate with other contractors performing work on this project necessary to achieve a complete and neat installation. To that end, each contractor shall consult the drawings and specifications for all trades to determine the nature and extend of others’ work

2. The BMS Contractor shall furnish all control valves, sensor wells, flow meters and other similar equipment for installation by the Mechanical Contractor.

3. The BMS Contractor shall provide field supervision to the designated contractor for the installation of the following.

a. Automatic control dampers

b. Blank-off plates for dampers that are smaller than duct size

CONTROLS FOR HVAC 23 09 23 - 7

c. Sheet metal baffles plates to eliminate stratification

D. Calibration: Calibration of all analog sensors under normal operating conditions. Off season calibration may be required for this task. Example: Calibrating a chilled water temperature sensor must be accomplished when the chilled water system is in operation. Submission requirement for calibration plans and reports are described in the Submittal section of this document.

E. Loop Tuning: Tuning of all P, PI and PID control loops under normal operating conditions. Off season tuning may be required for this task. Example: A mixed air damper control loop is not in operation when the outside air temperature is 90 deg F. A mixed air damper control loop is typically in modulation mode when the outside air temperature is less than 60 deg F. Submission requirement for loop tuning plans and reports are described in the Submittal section of this document.

F. System Start-Up and Start-Up Testing.

1. The BMS contractor shall set in operating condition all major equipment and systems, such as the chilled water, electric heating and all air handling systems, working in a support role to the Mechanical Contractor. The Owner’s representatives shall have the opportunity to be present.

2. Start-Up Testing is the process of verifying the system is physically complete and properly installed in accordance with the approved installation submittals.

a. It does not include calibration of analog sensors as the systems may not be in a state to support calibration efforts.

b. It does not include loop tuning as the systems may not be in a state to support loop tuning.

c. It does not include functional testing.

3. Start-Up Testing may be accomplished on a per component basis.

a. Each Network Server controller with its embedded physical IO may be the subject of one Start-Up Test.

b. Each Field Bus Controller with its connected physical IO may be the subject of one Start-Up Test.

c. Each network can be tested as part of a Start-Up Test.

4. Start-Up Testing may be accomplished on a per control panel basis where a control panel contains multiple components.

5. Start-Up Testing tasks shall include as a minimum the following.

a. Verification of component inventory compared to the submittals

b. Measurement of voltage sources; line voltage, low voltage AC and DC

c. Verification that the power consumption of all devices connected to a single power source does not exceed the power capacity of the power source

d. Verification that devices that required half wave power are not powered from the same source as devices that require full wave power

e. For each controller, verification of correct controller:

CONTROLS FOR HVAC 23 09 23 - 8

1) Power wiring (voltage, VA, full wave versus half wave)

2) Grounding

3) Communication wiring

f. Verification that each IO device is landed per the submittals and:

1) Analog sensors are properly scaled and a value is reported

2) Binary sensors have the correct normal position and the state is correctly reported

3) Analog outputs have the correct normal position and move full stroke when so commanded

4) Binary outputs have the correct normal state and respond appropriately to energize/de-energize commands.

g. For each communication network, verification of:

1) Bus topology

2) Polarity is consistently maintained device to device on RS485 networks

3) Shielded wire is used where required

4) Wire characteristics match the type required (LON, RS485)

5) The AWG of the cable does not change within a single segment and it is per the submittals

6) Single point grounding of shields and continuity of the shield over each segment of the network (when shielded wire is used)

7) The installation of the correct terminal devices at the both ends of each segment (FT-10A Networks)

8) Terminal resisters are installed at the end of each segment for RS485 networks

9) Biasing power sources and resistors are properly installed per the design.

10) The installed unit load of RS485 devices does not exceed the calculated maximum.

h. For all wiring verify that:

1) All wires are labeled such that both ends of each wire can be easily identified

2) Connection integrity and quality is good (no loose strands and no loose connections)

3) All cabling shall be installed “uncut” in a single continuous run from starting point to ending point without splices when practical. (Note: at a minimum, conductors within the same room, same system, and common origin shall be considered practical).

6. Submission requirement for start-up testing plans and reports are described in the Submittal section of this document.

G. Functional Testing

1. When the system is fully installed and operational, the BMS contractor shall execute functional tests of the system in the presence of representatives of the owner.

2. The functional tests shall be written by the BMS contractor and shall be designed to verify all aspects of the sequence of operation. Off season functional testing may be required for some tasks.

CONTROLS FOR HVAC 23 09 23 - 9

3. Submission requirement for functional testing plans and reports are described in the Submittal section of this document.

4. Support for HVAC and Balancing Contractors: Provide software tools, services and manpower as necessary so that the HVAC and Balancing Contractors are equipped to accomplish their functional testing and balancing tasks. The HVAC and Balancing Contractors will not be familiar with the BMS operator interface. The BMS Contractor may provide tools and training for these contractors to make them self sufficient or provide a trained operator to support their efforts.

H. Support for Commissioning: For Commissioning effort, the BMS Contractor shall provide software tools, services and manpower as follows so that the agent is equipped to perform commissioning tasks.

1. HVAC systems primarily consist of:

a. Energy Delivery Systems such as air handling units or piping systems.

b. Terminal Units such as Fan Coil Units, VAV Terminals, Unit Heaters, etc.

c. Third Party End Devices such as VFDs

2. The BMS Contractor shall provide an engineering technician that was significantly involved with the installation of the BMS System and is fully trained to operate the installed system. This technician shall:

a. Using Contract Documents and Facility Architectural Plans, brief the Commission Agent on the location of BMS components within the facility.

b. Furnish custom tools and cables that are unique to the BMS and not generally available in the commercial market.

c. Execute operator tasks as instructed by the commissioning agent.

d. Make minor engineering changes to the system such as adding trend logs, changing parameter values, overriding automatic control, etc.

e. Extract performance data from the BMS system for the Commissioning Agent.

3. The BMS Contractor personnel shall not be tasked to assist in the physical tasks associated with verifying system performance such as accessing system components, taking measurements, observing the physical status of end devices, etc. The primary task for the supporting technician is to operate the BMS system.

4. The BMS Contractor shall provide support to the Commissioning Agent in accordance with the following manpower budget:

a. 4 Man-hours for each third party device

b. 16 Man-hours for operator interaction tasks.

c. Man-hours not expended for one system shall be available for other systems.

d. The BMS Contractor is responsible for providing manpower to support CX, T&B and FAA turnover demonstrations.

5. When repeat testing is required by the Commissioning Agent as a result of the system not meeting the contract requirements during the first test, BMS Contractor support shall be provided at no additional cost to the Owner.

I. Operator Interaction Testing

1. When the system is fully installed and operational, the BMS contractor shall execute operator interaction tests of the system in the presence of representatives of the owner.

This can be combined in the training specified in the next section.

CONTROLS FOR HVAC 23 09 23 - 10

2. These tests shall be written by the BMS contractor and shall be designed to verify all aspects of operator interaction with the system. Additional requirements will be found in the System Acceptance and Testing section of this document.

3. Test elements shall include but not be limited to:

a. Graphics navigation

b. Alarm viewing, acknowledging, inhibited and routing

c. Viewing trend log lists and trend charts

d. Time schedule editing

e. Application/configuration parameter adjustment

f. Viewing data in the system tree

g. Manual control of all objects that are equipped for this function

h. Viewing reports

i. Viewing application programs in the ES, NSCs, PPCs and SLCs (Engineering

Workstation Only)

j. Using the Search Function

4. Unless otherwise noted, verify that the above tasks can be accomplished from the Engineering Workstation and Web-Based Operator Workstations.

5. Submission requirement for operator interaction testing plans and reports are described in the Submittal section of this document.

J. Training

1. On-site training shall be focused on the tasks that are described in the Operator Interaction Testing Plan.

a. Training will be customized to reflect operation of the delivered system.

b. Training shall be provided for up to 10 of the Owner’s personnel.

c. As part of the training, each student shall have the opportunity to perform each of the tasks in the testing plan.

K. Submittals: The contractor is required to submit technical information to the owner hear after referred to as “Submittals” at three different phases of the project:

1. Pre-Construction

2. During Construction

3. Post-Construction.

L. The requirements for each submittal are described later in this document.

M. Quantity Review: The BMS contractor shall review the entire specification and all contract drawings to determine the systems to be controlled, the operation sequences and the quantities and types of dampers, valves, operators, sensors, transducers, end devices required for a complete operational control system and to be provided by the BMS contractor.

1.5 WORK BY OTHERS

A. The Electrical Contractor shall provide:

1. All power wiring to motors, heat trace and junction boxes for power to BMS panels

CONTROLS FOR HVAC 23 09 23 - 11

2. Wiring between the smoke detectors and the building fire alarm system

3. Auxiliary contact (pulse type) on electric meters for central monitoring of kWH and KW by the BMS

4. The scaling parameters for the auxiliary contact on the electric meters to enable engineering of the electrical monitoring by the BMS contractor.

1.6 CODES, LAWS AND GOVERNING BODIES

A. All work performed under this section of the specification will comply with all governing codes, laws and governing bodies.

B. If the drawings and/or specifications are in conflict with governing codes, the Contractor, with guidance from the Owner, shall submit a proposal with appropriate modifications to the project to meet code requirements. If this specification and/or drawings exceed governing code requirements, the specification and drawings will govern.

C. The Contractor shall obtain and pay for all necessary construction permits and licenses.

1.7 CODE COMPLIANCE

A. BMS components and ancillary equipment shall be UL-916 listed and labeled as such.

B. All equipment and piping used in conditioned air streams, spaces or return air plenums shall comply with NFPS 90A Flam/Smoke/Fuel contribution ratings of 25/50/0 respectively and all applicable building codes or requirements.

C. All wiring shall conform to the National Electric Code.

D. Computing devices and low power communication equipment shall comply with FCC rules, Part 15 regarding Class A radiation in commercial environments.

1.8 SYSTEM DESCRIPTION

A. Network Server Controllers: The BMS contractor shall provide, install and commission one (1) or more Network Server Controllers as necessary to meet the control requirements defined in this document and the requirements of the manufacturer’s architectural guidelines.

1. These controllers will communicate with the following devices via the WAN/LAN with the capability to communicate at 100 bits per second.

a. The Enterprise Server

b. Other Network Server Controllers

c. Operator Workstation

d. Engineering Workstation

e. Web-based operation workstations

2. These controllers shall communicate with their embedded input and output devices via a dedicated bus.

3. These controllers shall communicate with LON field bus controllers via a dedicated 76.8 kilobit per second FT-10A LON field bus network.

CONTROLS FOR HVAC 23 09 23 - 12

4. These controllers shall communicate with up to 3 distinct RS485 networks. Use of the RS485 networks shall be selected from the following:

a. ModBus RTU devices via a dedicated RS485 shielded twisted pair field bus network.

b. BACnet MSTP devices via a dedicated RS485 shielded twisted pair field bus network.

c. INET DCUs and PCUs via a dedicated RS485 shielded twisted pair field bus network.

d. When using RS485 devices under a Network Server Controller, the loading of the Network Server Controller must conform to vendor recommendations on the simultaneous use of the multiple RS485 networks and number of devices per network. In most cases, one of the three options will dominate with very limited loading on the other two RS485 networks.

5. The Network Server Controllers shall support the use of:

a. Modbus TCP

b. BACnet over IP using UDP

6. The Network Server Controllers shall support the use of the following for communication at the WAN/LAN layer of the system architecture using web services:

a. HTTP: Hyper Text Transfer Protocol

b. SOAP: Simple Object Access Protocol

c. XML: eXtensible Markup Language

7. Network Server Controllers shall NOT communicate with the Enterprise Server or any workstation using RS232 or ARCNET.

B. Networks: The networks that allow for connection of the components that make up the BMS system shall exist in two layers; the Ethernet/IP layer (WAN/LAN) and the field bus layer. The devices that transition from the WAN/LAN layer to the field bus layer are Network Server Controllers.

1. WAN/LAN

a. Enterprise Ethernet (IEEE 802.3), WAN: This network shall utilize CSMA/CD, ARP and UDP operating at 10 or 100 Mbps.

b. Local Area TCP/IP Network, LAN: This network shall be either a 10 or 100 Mbps Ethernet network supporting BACnet Over IP, Modbus TCP, Java, XML, HTTP, SOAP and COBRA IIOP for maximum flexibility for integration of building data with enterprise information systems and providing support for multiple Network Server Controllers, an Enterprise Server, and multiple workstations (engineering or web-based).

2. Field Bus Layer: Field Bus Networks shall be RS485 Twisted Shielded Pair.

a. RS485 Shielded Twisted Pair networks to support devices with RS485 transceivers shall connect to a Network Server Controller.

CONTROLS FOR HVAC 23 09 23 - 13

C. Environmental Control Equipment

1. The BMS system shall use electronic sensors and electronic/electric actuation of valves, dampers and two position electric circuits on central station HVAC equipment, HVAC terminal equipment, variable frequency drives, low voltage lighting control, electrical circuit breakers and power monitoring.

2. The BMS is intended to seamlessly connect devices throughout the building regardless of system type.

D. WAN/LAN Reliability

1. A Network Server Controller and all field bus controllers that are subordinate to the NSC represent a defined subset of the overall BMS.

2. Each NSC system shall be designed for the maximum possible stand alone operation when the NSC can no longer communicate with other NSC or ES systems on the WAN/LAN.

3. When a specific piece of measured data (Example: Outside Air Temperature) is critical to the performance of two NSC systems, each NSC system shall have its own electronic sensor (to measure the Outside Air Temperature).

4. When schedules and set points originate in the ES, each NSC system shall hold the last data received from the ES until communication with the ES is re-established or the NSC system shall revert to local applications until communication with the ES is re-established.

E. Custom Tools and Cables

1. One set of all custom tools and cables that are acquired from the BMS manufacturer and used during installation, configuration and engineering of the system.

F. Graphics

1. The type, quantity and technical requirements for graphic pages are described in Part 2 of this document.

2. Graphic pages that relate to systems and components that are controlled by a Network Server Controller (or devices on a field bus managed by the Network Server Controller), shall be located in the Network Server Controller.

3. Graphic pages that relate to systems and components that are controlled by multiple Network Server Controllers shall be located in the Enterprise Server.

G. Trend Log Data

1. Trend log data for values in a field bus controller.

a. If trend log data is collected in a field bus controller, the trend log data must be periodically uploaded to larger capacity trend logs in the Network Server Controller.

b. If trend log data is not collected in a field bus controller, the data to be trended shall be mirrored in the Network Server Controller and the mirrored data shall be logged in the Network Server Controller. The mirroring process shall use send on delta, minimum send time and maximum send time parameters to avoid excessive bandwidth utilization on the field bus.

2. Data that originates in the Network Server Controller shall be trended in the Network Server Controller.

CONTROLS FOR HVAC 23 09 23 - 14

3. Trend log data in the Network Server Controller shall be periodically uploaded to long term data storage in the Enterprise Server when applicable/provided.

4. All trends shall be local to the Smart Struxure Software and shall be set to the following:

15 minute snapshot / 14 day storage.

1.9 SUBMITTALS

A. Shop Drawings and Product Data.

1. Shop drawings shall be 11 inch by 17 inch, landscape, bound on the left edge. Organize the packages by building.

2. All text based documents and product data sheets shall be 8 ½ inch by 11 inch format bound on the left edge. To the maximum extent possible Adobe Acrobat shall be used to produce the documents in an X.pdf format.

3. Software files shall be submitted on fully labeled CDs that shall include a table of contents file in “filename.pdf” format that provides a description of all of the files on the CD.

B. Submittals Prior To Construction.

1. Shop Drawings

a. System Architecture Alteration Diagram.

1) This is a riser diagram of the WAN/LAN layer, all NSCs and all connected field busses. It shall show all BMS components to be installed on the WAN/LAN and all of the field busses.

2) The physical relationship of one component to another component shall reflect the proposed installation. Example: If AHU1 controller is the closest controller to NSC on the field bus, then this device shall be shown as the first device on the riser diagram just below the NSC. This requirement does not apply to the existing control system.

b. Wiring Design Diagram for individual NSCs and Field Bus Controllers: The wiring diagram for each component shall identify all I/O, power and communication wiring, and the locations on the terminal blocks to which wires are landed. Example:

Fan Status sensor is wired from terminals 5/6 on the controller to terminals 17 and 18 on the terminal strip.

c. Installation Design Detail for each I/O device.

1) Include a drawing of the wiring details for each sensor and/or end device.

2) For devices with multiple quantities a standard detail may be submitted.

d. A System Flow Design Diagram for each controlled system.

1) A two dimensional cross sectional diagram showing key components such as fans, coils, dampers, valves, pump, etc.

2) Identify the locations and names of all sensors and end devices that are associated with the control system. Label the panel name and terminal numbers where the connections are landed.

3) A legend shall be provided for all symbols used.

2. Data

CONTROLS FOR HVAC 23 09 23 - 15

a. BMS manufacturer’s architectural guidelines that define the systems architecture, the number of devices supported at each level of the architecture and any other software or hardware limitations for an efficient system.

b. BMS Hardware Technical Data.

1) A complete bill of materials of equipment to be used indicating quantity, manufacturer and model number.

2) Manufacturer’s description and technical data for each unique device to include performance curves, product specification sheets and installation instructions. When a manufacturer’s data sheet refers to a series of devices rather than a specific model, the data specifically applicable to the project shall be highlighted or clearly indicated by other means.

3) An Instrumentation List for each system. The list shall be in a table format and Include name, type of device, manufacturer, model number and product data sheet number.

c. Sequence of Control: A sequence of control for each system being controlled.

1) A list of all physical inputs and outputs associated with each sequence.

2) Identify those points that shall be subject to manual control from an operator workstation.

3) A list of all alarms, a description of the alarm and a description of the alarm criteria.

4) A list of all variables for which historical trending will be applied, the sample rates and any criteria used to start and stop the historical trending.

3. Submit electronic copies of submittal data and shop drawings to the Owner for review and approval prior to ordering or fabrication of the equipment.

4. The Owner will annotate required corrections and return to the BMS Contractor. The BMS Contractor will then re-submit with corrected data or additional data. This procedure shall be repeated until all corrections are made to the satisfaction of the Owner and the submittals are fully approved.

C. Submittals During Construction

1. Training Manuals for on-site BMS Contractor conducted training.

a. Six weeks in advance of the training, submit the following:

1) List of training objectives.

2) Outline of the course with time allocations per topic.

3) Methodology to be followed to ensure each student has a complete hands-on training experience.

4) Methodology to be followed to ensure each student masters the training objectives.

b. Submit the following within 3 weeks of training completion:

1) List of attendees.

2) Performance scores on the assessment devices.

CONTROLS FOR HVAC 23 09 23 - 16

c. Training sessions shall accommodate up to ten (10) participants for a minimum of 3 hours.

2. Startup Testing Plan: Submit a start up testing plan for each unique system.

a. The purpose of a startup test is to demonstrate the “completeness” of the physical tasks associated with installation and the physical performance of the components.

See the Scope of Work Section in this document for a task list.

b. For each task on the startup test checklist, the plan shall require the technician to enter his or her initials and the date the test was completed along with any recorded data such as voltages, offsets or tuning parameters. Any deviations from the submitted installation plan shall also be recorded.

c. Submit at least four weeks prior to any scheduled start-up tests.

3. Startup Testing Report: Startup testing reports shall be submitted on a per system basis.

They shall be the documented results of the executed startup testing plans.

4. Performance Verification Testing Plan: Submit a verification plan for each system. For each end device that is controlled, the plan shall define a series of step by step cause and effect tests to verify each aspect of the sequence of control.

5. Performance Verification Testing Report: Performance Verification Testing Reports shall be submitted on a per system basis. Performance Verification Testing reports shall be the documented results of the executed performance verification testing plans with initials and dates.

6. Operator Interaction Testing Plan: Submit a verification plan for the Engineering Workstation and the Web-based Workstation. List each operator task to be accomplished as part of the test. See the Scope of Work Section of this document for a list of tasks.

7. Operator Interaction Testing Report: Operator Interaction Testing reports shall be submitted for both types of workstations. The successful execution of each operator task with initials and date accomplished shall be documented in the report.

8. Calibration Report: A calibration report shall be submitted on a device by device basis listing the analog sensors that were calibrated and the final calibration offsets for each sensor.

D. Submittals After Construction

1. As-built system architecture drawing.

2. As-Built layout drawing for each control panel.

3. As-built wiring diagram for each control panel.

4. As-built wiring diagram for individual components.

5. As-built system flow diagram for each controlled system.

6. As-built Instrumentation list for each controlled system.

7. As-built sequence of control.

8. Operation and Maintenance Manuals: Operations and Maintenance Manuals shall consist of two parts. Both parts shall be provided electronically on each workstation with links to the information from the home page. Diagrams shall be on 11” by 17” files. If color has been used to differentiate information, the copies shall also be in color.

a. Part II: Information common to the systems in a single building.

1) As-built system architecture diagram for components within the building annotated with specific location information.

CONTROLS FOR HVAC 23 09 23 - 17

2) As-built drawing for each control panel.

3) As-built wiring design diagram for each control panel.

4) As-built wiring design diagram for all components.

5) As-built details for each I/O device.

6) As-built system flow diagram for each system.

7) As-built sequence of control for each system.

8) Product data sheet for each component.

b. Submit one electronic copy.

1.10 OWNERSHIP

A. The BMS Contractor may use temporary licenses during the installation and commission of the system, but permanent licenses without expiration dates shall be installed on the system prior to completion. These license files shall be provided to the owner as part of the post construction submittals and they shall become the property of the owner.

B. The Owner shall sign a copy of the manufacturer’s standard software and firmware licensing agreement as a condition of this contract.

1. The license agreement shall grant use of all software programs, firmware files, application library files, graphical symbol library, files created by the contractor during engineering and installation and product documentation to the owner.

2. The Owner shall agree to the terms of the license agreement that protect the manufacturer’s right to non-disclosure of Trade Secrets contained within all files provided to the owner.

3. The licensing agreement shall not preclude the use of the software and firmware by individuals under contract to the Owner for commissioning, servicing or altering the system in the future.

4. The Owner shall agree that use of the software and firmware by individuals under contract to the owner shall be restricted to use on the Owner’s computers and only for the purpose of commissioning, servicing, or altering the installed system.

C. All software programs and tools, firmware files, application library files, graphics libraries and product documentation used on this project shall be provided to the Owner in a format that the Owner could install them on a computer or download them to a control component. This shall include but not be limited to:.

1. All software programs and tools as listed

2. Firmware files for all control components if the components allow for firmware updates

3. Xif files and NXE files for each type of Application Specific device

4. Application files created during project engineering and installation

5. Graphic files created during project engineering and installation

6. Graphic symbol and graphic component library files

7. Data sheets, installation manuals, engineering manuals and operator manuals for all components in the system

8. Application files, graphic files and other files created during engineering of the project that are intrinsic to the system database and can be easily extracted from the database do not have to be separately provided to the owner.

1.11 WARRANTY AND MAINTENANCE

CONTROLS FOR HVAC 23 09 23 - 18

A. All components, system software and parts furnished and installed by the BMS Contractor shall be guaranteed against defects in materials and workmanship for 1 year after substantial completion.

B. Labor to repair, reprogram or replace these components shall be furnished by the BMS contractor at no charge during normal working hours during the warranty period.

C. Materials furnished by not installed by the BMS contractor shall be covered to the extent of the product only. Installation labor shall be the responsibility of the trade contractor than originally installed the product.

D. All corrective software, firmware and application modifications made during warranty periods shall be updated on all owner documentation and owner digital files from previous submittals.

The intent of this specification is that the BMS contractor will work with the Owner to ensure that what was submitted during post construction submittals is updated to reflect the changes made.

PART 2 - PRODUCTS

2.1 PRE-APPROVED MANUFACTURERS

A. Electric Components: Schneider Electric Field Devices

B. Electronic Components: Schneider Electric Field Devices

C. Direct Digital Control Systems: Schneider Electric

2.2 SYSTEM ARCHITECTURE

A. General

1. The system architecture shall consist of two layers; the WAN/LAN layer and a Field Bus layer. Network Server Controllers are the devices that transition the field bus layer to the WAN/LAN layer. The field bus layer consists of two unique types: FT-10A LON and RS-485 for Modbus RTU, BACnet MSTP and INET.

2. WAN/LAN Connected Devices: The following components shall connect to the

WAN/LAN.

a. Network Server Controllers

b. Enterprise Server Computer

c. Engineering Workstation Computer

d. Operator Workstations (Web-Based)

e. ModBus TCP Controllers

f. BACnet IP Controller

3. Fault Tolerance:

a. The failure of one component within the system architecture shall not cause the entire system to fail. All system users shall be notified by the alarm management system when a component fails.

CONTROLS FOR HVAC 23 09 23 - 19

b. Failure of the Enterprise Server shall not prevent operator connection to any of the Network Server Controllers.

c. Failure of a Network Server Controller shall not negatively affect the Enterprise Server or the other Network Server Controller. The Enterprise Server may no longer present the database from the failed NSC and its subordinate field bus controllers.

4. RS-485 Field Bus:

a. The cable shall be shielded twisted pair between AWG 20 and AWG 24. The same AWG shall be used for the entire field bus. The cable shall be rated for RS-485 installations by the supplying vendor.

1) Cable Impedance shall be 120 Ohms

2) Cable Capacitance Wire to Shield shall be less than 25 picofarads per foot

3) Cable Capacitance Wire to Wire shall be less than 13 picofarads per foot

b. Device to device, polarity shall be maintained with the same wire always connected to the Data + terminal on each device and the second wire always connected to the Data – terminal on each device.

c. The initial RS-485 field bus shall start at the Network Server Controller.

d. Bus Topology shall be used. No tees or stubs are allowed no matter how short.

e. An RS-485 repeater may be used to extend the overall length of the RS-485 field bus. When a repeater is used, this creates a multi-segment field bus.

f. RS-485 segments shall not be longer than 4,000 feet.

g. The shield shall be continuous over an entire segment. Shield tie terminals on controllers may only be used if they are not connected to earth ground within the controller. If ungrounded tie terminal are not available a wire nut shall be used to keep the shield continuous.

h. The shield shall be connected to earth ground at the NSC. The shield for the initial segment shall not touch earth ground at any other location along the segment. Care shall be taken to ensure no accidental earth ground connections are made within control cabinets.

i. If a RS-485 repeater is used to create a second segment, the shield for the second segment shall be connected to earth ground on the downstream side of the repeater.

j. 120 ohm termination resisters shall be installed at both ends of each segment. The resister shall be connected between the Data + and Data – terminals. Care shall be taken to ensure that the resister leads do not touch earth ground or the shield.

k. The outer cable sheathing shall be color coded as follows:

1) Mod-bus = Purple

2) BacNet = Gray

3) INET = Blue

4) INET sublan = Orange

5. Controller…