R0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

W912DW-16-B-0003 FY14 Aviation Unit Complex Battalion Headquarters (BNHQ) PN 78196, JBLM, WA

See Continuation Pages

1. CONTRACT ID CODE PAGE OF PAGES

1 2

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 09-Mar-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912DW-16-B-0003

X 9B. DATED (SEE ITEM 11)

16-Feb-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

09-Mar-2016

CODE

USA ENGINEER DISTRICT, SEATTLE

ATTN: CECT-NWS

4735 EAST MARGINAL WAY SOUTH, BLDG. 1202

SEATTLE WA 98134-2388

W912DW 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912DW-16-B-0003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

A. This amendment (R0003) provides for revisions to the following Sections:

1. Section 02 41 00 for DEMOLITION

2. Section 02 84 16 for HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING

PCBs AND MERCURY

3. Section 23 09 23.00 11 for DIRECT DIGITAL CONTROL (DDC) SYSTEMS

4. Section 23 52 00 for HEATING BOILERS

5. REGISTER

B. Bidders shall note that the above revised sections, as enclosed, replace the previous versions in their entirety.

C. Specifications changes are generally identified, for convenience, either by strikeout for deletions, and double underlining of text for additions or a single dark line in the margin. All portions of the revised sections shall apply whether or not changes have been indicated.

D. The closing time and date of the solicitation remain the same at 11:00:00 AM, local time (Pacific Time), 18 March 2016.

E. NOTICE TO BIDDERS: BIDDERS must acknowledge receipt of this amendment by number and date on bid.

Encl:

1. Revised Section 02 41 00 for DEMOLITION

2. Revised Section 02 84 16 for HANDLING OF LIGHTING BALLASTS AND LAMPS

CONTAINING PCBs AND MERCURY

3. Revised Section 23 09 23.00 11 for DIRECT DIGITAL CONTROL (DDC) SYSTEMS

4. Revised Section 23 52 00 for HEATING BOILERS

5. Revised REGISTER

SUMMARY OF CHANGES

(End of Summary of Changes)

FY14 ACS Phase 2C, BNHQ - PN 78196 13023 Joint Base Lewis-McChord W912DW-16-B-0003

SECTION 02 41 00

DEMOLITION

PART 1

THIS SECTION NOT USED

PART 2

PART 3

-- End of Section --

SECTION 02 41 00 Page 1 R0003

SECTION 02 84 16

HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING PCBs AND MERCURY 04/06

PART 1

THIS SECTION NOT USED

PART 2

PART 3

-- End of Section --

SECTION 02 84 16 Page 1 R0003

SECTION TABLE OF CONTENTS

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

SECTION 23 09 23.00 11

DIRECT DIGITAL CONTROL (DDC) SYSTEMS

08/03

PART 1 GENERAL

1.1 REFERENCES

1.2 DEFINITIONS

1.2.1 Digital Controller

1.2.1.1 Interoperable Digital Controller (IDC)

1.2.1.2 Interoperable BACnet Controller (IBC)

1.2.2 Direct Digital Control (DDC)

1.2.3 DDC System

1.2.4 Distributed Control

1.2.5 Dynamic Control

1.2.6 Firmware

1.2.7 Graphic User Interface Software (GUI)

1.2.8 Hand-Held Terminal

1.2.9 Input/Output (I/O) Points

1.2.10 I/O Expansion Unit

1.2.11 JACE (Java Application Control Engine) Network Area Controller

(NAC)

1.2.12 EEDRS (Enterprise Energy Data Recorcing System) JACE

1.2.13 Local Area Network (LAN)

1.2.14 LonMark

1.2.15 LonMark International

1.2.16 LonWorks

1.2.17 Microprocessor

1.2.18 Optimum Start

1.2.19 Peer-to-Peer

1.2.20 Performance Verification Test

1.2.21 PID

1.2.22 Resolution

1.2.23 Stand-Alone Control

1.2.24 Terminal Control Unit (TCU)

1.3 TEMPERATURE CONTROL AND FACILITY MANAGEMENT AND CONTROL SYSTEM

1.4 DDC SYSTEM DESCRIPTION

1.4.1 Design Requirements

1.4.1.1 Control System Schematic

1.4.1.2 Electrical Equipment Ladder Diagrams

1.4.1.3 Component Wiring Diagrams

1.4.1.4 Terminal Strip Diagrams

1.4.1.5 Communication Network Architecture and Block Diagram

1.4.2 Symbols, Definitions and Abbreviations

1.4.3 System Units and Accuracy

1.5 SUBMITTALS

1.6 Operating environment

1.7 QUALITY ASSURANCE

1.7.1 Standard Products

1.7.2 Nameplates and Tags

SECTION 23 09 23.00 11 Page 1 R0003

1.7.3 Verification of Dimensions

1.7.4 Drawings

1.7.5 Contractors Qualifications

1.7.6 Training Course Documentation

1.7.7 Service Organizations

1.7.8 Contractor Certification

1.7.9 Modification of References

PART 2 PRODUCTS

2.1 DDC SYSTEM

2.1.1 Interoperable Direct Digital Controllers

2.1.1.1 Distributed Control

2.1.1.2 I/O Point Limitation

2.1.1.3 Environmental Operating Limits

2.1.1.4 Stand-Alone Control

2.1.1.5 Internal Clock

2.1.1.6 Memory

2.1.1.7 Inputs

2.1.1.8 Outputs

2.1.1.9 PID Control

2.1.1.10 Digital Controller Networking Capabilities

2.1.1.11 Communications Ports

2.1.1.12 Digital Controller Cabinet

2.1.1.13 Main Power Switch

2.1.2 Terminal Control Units (TCUs)

2.1.3 DDC Software

2.1.3.1 Sequence of Control

2.1.3.2 Parameter Modification

2.1.3.3 Differential

2.1.3.4 Motor and Flow Status Delay

2.1.3.5 Run time Accumulation

2.1.3.6 Timed Local Override

2.1.3.7 Time Programs

2.1.3.8 Scheduling

2.1.3.9 Point Override

2.1.3.10 Alarming

2.1.3.11 Messages

2.1.3.12 Trending

2.1.3.13 Status Display

2.1.3.14 Diagnostics

2.1.3.15 Power Loss

2.1.3.16 Program Transfer

2.1.3.17 Password Protection

2.1.4 Workstation

2.1.4.1 Hardware

2.1.4.2 Software

2.1.4.3 Graphic-Based Software

2.1.5 Maintenance Personnel Interface Tools

2.1.5.1 Notebook Computer

2.2 SENSORS AND INPUT HARDWARE

2.2.1 Field Installed Temperature Sensors

2.2.1.1 Thermistors

2.2.1.2 Resistance Temperature Detectors (RTDs)

2.2.1.3 Temperature Sensor Details

2.2.2 Transmitters

2.2.2.1 Spans and Ranges

2.2.3 Relative Humidity Transmitters

2.2.4 Pressure Transmitters

SECTION 23 09 23.00 11 Page 2 R0003

2.2.5 Current Transducers

2.2.6 Air Quality Sensors

2.2.6.1 Carbon Dioxide (CO2) Sensor

2.2.7 Input Switches

2.2.7.1 Timed Local Override

2.2.7.2 Insertion Freeze Protection Switch

2.2.7.3 Electronic Airflow Measurement Stations and Transmitters

2.2.8 Energy Metering

2.2.8.1 Meters

2.3 OUTPUT HARDWARE

2.3.1 Control Dampers

2.3.2 Control Valves

2.3.2.1 Valve Assembly

2.3.2.2 Butterfly Valve Assembly

2.3.2.3 Two-Way Valves

2.3.2.4 Three-Way Valves

2.3.2.5 Duct Coil and Terminal Unit Coil Valves

2.3.2.6 Valves for Hot Water Service

2.3.3 Actuators

2.3.3.1 Electric Actuators

2.3.4 Output Switches

2.3.4.1 Control Relays

2.4 ELECTRICAL POWER AND DISTRIBUTION

2.4.1 Transformers

2.4.2 Surge Protection

2.4.2.1 Power Line Surge Protection

2.4.2.2 Telephone and Communication Line Surge Protection

2.4.2.3 Controller Input/Output Protection

2.4.3 Wiring

2.4.3.1 AC Control Wiring

2.4.3.2 Analog Signal Wiring

2.5 FIRE PROTECTION DEVICES

2.5.1 Smoke Detectors

2.6 INDICATORS

2.6.1 Thermometers

2.6.2 Pressure Gages

2.7 VARIABLE FREQUENCY 3-PHASE MOTOR DRIVES

PART 3 EXECUTION

3.1 INSTALLATION

3.1.1 Wiring Criteria

3.1.2 Digital Controllers

3.1.3 Temperature Sensors

3.1.3.1 Room Temperature Sensors

3.1.3.2 Duct Temperature Sensors

3.1.3.3 Immersion Temperature Sensors

3.1.3.4 Outside Air Temperature Sensors

3.1.4 Damper Actuators

3.1.5 Thermometers

3.1.6 Differential Pressure Sensors

3.1.7 Control Drawings

3.2 HVAC SYSTEMS SEQUENCES OF OPERATION

3.3 TEST AND BALANCE SUPPORT

3.4 FIELD QUALITY CONTROL TESTS

3.4.1 General

3.4.2 Test Reporting for Field Testing and Performance Verification

Tests

3.4.3 Contractor's Field Tests

SECTION 23 09 23.00 11 Page 3 R0003

3.4.3.1 System Inspection

3.4.3.2 Calibration Accuracy and Operation of Inputs Test

3.4.3.3 Actuator Range Adjustment Test

3.4.3.4 Digital Controller Startup and Memory Test

3.4.3.5 Surge Protection Test

3.4.3.6 Application Software Operation Test

3.4.4 Performance Verification Tests

3.5 TRAINING

3.5.1 DDC Training Phase I

3.5.2 DDC Training Phase II

-- End of Section Table of Contents --

SECTION 23 09 23.00 11 Page 4 R0003

SECTION 23 09 23.00 11

DIRECT DIGITAL CONTROL (DDC) SYSTEMS

08/03

PART 1 GENERAL

1.1 REFERENCES

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

AIR MOVEMENT AND CONTROL ASSOCIATION INTERNATIONAL(AMCA)

AMCA 500-D (2007) Laboratory Methods of Testing Dampers for Rating

AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)

ANSI/EIA 709.1B (2002) Control Network Protocol Specification

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2008; Addenda Q 2009) BACnet

ASHRAE FUN IP (2009; Errata 2010) Fundamentals Handbook, I-P Edition

ASME INTERNATIONAL (ASME)

ASME B16.5 (2009) Pipe Flanges and Flanged Fittings:

NPS 1/2 Through NPS 24 Metric/Inch Standard

ASME B31.1 (2010) Power Piping

ASTM INTERNATIONAL (ASTM)

ASTM A 126 (2004; R 2009) Standard Specification for Gray Iron Castings for Valves, Flanges, and Pipe Fittings

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE Std 100 (2000) The Authoritative Dictionary of IEEE Standards Terms

IEEE C62.41 (1991; R 1995) Recommended Practice for Surge Voltages in Low-Voltage AC Power Circuits

IEEE C62.45 (2002) Surge Testing for Equipment Connected to Low-Voltage (1000 V and Less) AC Power Circuits

SECTION 23 09 23.00 11 Page 5 R0003

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2011; AMD 1-4; Errata 1-2) National Electrical Code

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

SHEET METAL AND AIR CONDITIONING CONTRACTORS' NATIONAL ASSOCIATION

(SMACNA)

SMACNA 1780 (2002) HVAC Systems - Testing, Adjusting and Balancing, 3rd Edition

SMACNA 1966 (2005) HVAC Duct Construction Standards Metal and Flexible, 3rd Edition

UNDERWRITERS LABORATORIES (UL)

UL 506 (2008; Reprint Mar 2010) Specialty Transformers

UL 916 (2007) Energy Management Equipment

UL 1449 (2009) Surge Protective Devices, 3rd edition

1.2 DEFINITIONS

1.2.1 Digital Controller

1.2.1.1 Interoperable Digital Controller (IDC)

A control module which is microprocessor based Interoperable LonMark (TM) or LonWorks. HVAC control is accomplished using LonMark (TM) based devices where the application has a LonMark (TM) profile defined and performs stand-alone operations.

1.2.1.2 Interoperable BACnet Controller (IBC)

A control module which is microprocessor based Interoperable BACnet Controller in accordance with ASHRAE 135. IBC's must be provided with product interoperability compliance statement documents that demonstrate the compliance level to ASHRAE 135.

1.2.2 Direct Digital Control (DDC)

Digital controls, as defined in this specification, performing control logic. The controller directly senses building environment and makes control decisions based on user defined, controller resident programs. The controller outputs control signals that directly operate valves, dampers, and motor controllers. No conventional control devices, such as thermostats, and logic units are present within or interface with a direct digital control loop. Actuators are electric.

1.2.3 DDC System

A system made up of one or more interoperable digital controllers which

SECTION 23 09 23.00 11 Page 6 R0003 communicate on a network.

1.2.4 Distributed Control

The intent of distributed control is to install the controllers near their respective controlled equipment. The control system consists of stand-alone controllers, with the total number of input and output points limited to 48 or less per controller. Failure of any single controller will not cause the loss of more then 48 control points.

1.2.5 Dynamic Control

A process that optimizes energy efficiency of HVAC systems (air handling units, converters, chillers, and boilers) by increasing and decreasing setpoints or starting and stopping equipment in response to heating and cooling needs of the facility. A requirement of dynamic control is knowing the heating/cooling demand status of the process. Therefore dynamic control requires controllers connected in a communications network and receiving feedback, necessary variable point data and/or actual status input to accomplish closed loop control.

1.2.6 Firmware

Firmware is software programmed into read only memory (ROM) and erasable programmable read only memory (EPROM) chips. Software may not be changed without physically altering the chip.

1.2.7 Graphic User Interface Software (GUI)

Graphic user interface software shall run on Microsoft Windows XP service Pack 2, or later. The GUI employs browser like functionality that includes a tree view (similar to Windows Explorer) for quick viewing of, and access to, the hierarchical structure of the database. Pull down menus and toolbars employ buttons, commands and navigation that permit the operator to perform tasks with a minimum knowledge of the HVAC Control System and basic computing skills. These include, but are not limited to, forward/backward buttons, home button, and a context sensitive locator line (similar to a URL line), that displays the location and the selected object definition.

1.2.8 Hand-Held Terminal

A hand-held terminal is a manufacturer specific device connected directly to a communications port on a controller, through which the controller is accessed and, in some cases, programmed. This style of interface is not an acceptable installation at JBLM.

1.2.9 Input/Output (I/O) Points

I/O points refer to analog inputs (AI), digital inputs (DI), analog outputs (AO), and digital outputs (DO) in a digital controller. Another term for digital inputs and outputs is binary inputs and outputs. Inputs are from analog sensors (temperature, pressure, humidity, flow) and digital sensors (motor status, flow switches, switch position, and pulse output devices).

Outputs operate modulating and on/off control devices.

1.2.10 I/O Expansion Unit

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

SECTION 23 09 23.00 11 Page 7 R0003 controller and communicates with the stand-alone digital controller on a LAN. An I/O unit is not stand-alone because the control program does not reside in the I/O unit. An I/O expander which connects directly to a stand alone controller through a multi-line microprocessor bus is restricted to reside within 3 feet of the stand alone controller and is considered part of the stand alone controller. The total point count of the I/O and all connected expansion units shall not exceed the 48 point limit.

1.2.11 JACE (Java Application Control Engine) Network Area Controller (NAC)

The JACE network area controller (NAC) provides the interface between a higher level LAN or WAN and the interoperable digital controllers, providing global supervisory control functions. NAC's provide multiple user access at varying levels through password protection.

1.2.12 EEDRS (Enterprise Energy Data Recorcing System) JACE

The EEDRS JACE provides the interface between a higher level LAN or WAN and the metering devices, providing data to the JBLM EEDRS system.

1.2.13 Local Area Network (LAN)

a. A communications bus that interconnects digital controllers for peer-to-peer (see "peer-to-peer" below) communications.

Different levels of LANs are possible within a single DDC system.

In this case, a digital controller on a higher level LAN acts as a network controller to the controllers on the lower level LAN. The network controller, then, has at least two LAN communications ports. One port supports peer-to-peer communications with other digital controllers on the higher level LAN. The other port supports communications with the digital controllers on the lower level LAN.

b. LANs permit sharing global information. This allows building and site wide control strategies such as peak demand limiting, dynamic control strategies, coordinated response to alarm conditions, and remote monitoring and programming of digital controllers.

c. The controllers peer-to-peer communications bus is commonly referred to as "the field bus".

d. The "LAN" typically refers to the communications bus using the Ethernet protocols (Category 6) within a building.

1.2.14 LonMark

See LonMark International. Also, a certification issued by LonMark International to ANSI/EIA 709.1B devices.

1.2.15 LonMark International

Standards committee consisting of numerous independent product developers and systems integrators dedicated to determining and maintaining the interoperability guidelines for the LonWorks industry. Maintains guidelines for the interoperability of ANSI/EIA 709.1B devices and issues the LonMark Certification for ANSI/EIA 709.1B devices.

SECTION 23 09 23.00 11 Page 8 R0003

1.2.16 LonWorks

The overall communications technology, developed by Echelon Corporation, for control systems. The term is often used to refer to the technology in general, and may include reference to any/all of the: protocol, network management, and interoperability guidelines where the technology is based on the ANSI/EIA 709.1B protocol and employs interoperable devices along with the capability to openly manage these devices (via multiple vendors) using a network configuration (or service) tool.

1.2.17 Microprocessor

A microprocessor refers to the central processing unit (CPU) that contains all registers and logic circuitry that allow digital controllers to function.

1.2.18 Optimum Start

Optimum start is a method of starting HVAC equipment prior to scheduled occupancy in order to have the building at setpoint when occupied. Optimum start is based on the zone temperatures, zone setpoints, and outdoor temperature.

1.2.19 Peer-to-Peer

Peer-to-peer refers to controllers connected on a communications LAN typically referred to as the "field bus" that act independently, as equals, and communicate with each other to pass information.

1.2.20 Performance Verification Test

The performance verification test (PVT) is the formal commissioning of the DDC system performed after successful contractor field testing and prior to the second phase of DDC training. It is used as a means for final acceptance of the control system and provides a means to verify the system functions are performing in accordance with the manufacturers written instructions, sequence of operation and control drawings.

1.2.21 PID

PID refers to proportional, integral, and derivative control; the three types of action that are used in controlling modulating equipment.

1.2.22 Resolution

Refers to the number of possible states an input value or output value can take and is a function of the digital controller I/O circuitry; the A/D converter for input and the D/A converter for output. Ten bit resolution has 1024 possible states.

1.2.23 Stand-Alone Control

Refers to the digital controller performing required climate control, and energy management functions without connection to another digital controller or computer. Requirements for stand-alone control are a time clock, a microprocessor, resident control programs, PID control, and I/O.

All stand-alone controllers have a communication port and firmware for direct connection and interrogation with a laptop computer. This interrogation includes parameter changes and program downloads.

SECTION 23 09 23.00 11 Page 9 R0003

1.2.24 Terminal Control Unit (TCU)

An off-the-shelf, stand-alone digital controller equipped for communication on a lower level LAN. TCUs may deviate from stand-alone only in receiving energy management and time information from a stand alone digital controller. A TCU is commonly application specific and is used for distributed control of specific HVAC subsystems. A TCU communicates with other digital controllers. Typically, a TCU communicates on a lower level LAN. Examples where TCUs are used include small air handling units (AHUs), variable air volume (VAV) boxes, fan coil units, and heat pumps. TCUs shall be LonMark/LonWorks or BACnet-based. All TCUs shall be remotely programmable via the JBLM WAN (Wide Area Network).

1.3 TEMPERATURE CONTROL AND FACILITY MANAGEMENT AND CONTROL SYSTEM

The building's Temperature Control System (TCS) shall be capable of being extended to the existing JBLM Niagara Framework Utilities Management and Control System (UMCS), and comprised of a network of interoperable, stand-alone digital controllers communicating via LonMark/LonTalk and/or BACnet communication protocols to a JACE Network Area Controller (NAC).

The JACE Controller shall be connected to the UMCS through the Network Enterprise Center (NEC) switch. NEC switch is not within the Scope of the contract. Cat-6 wiring to the NEC switch shall be provided by contractor.

Access to the system, either locally in each building, or remotely from a central site or sites as specified by JBLM Public Works, shall be accomplished through standard Web browsers and/or local area network (LAN), and/or wide area network (WAN).

The TCS shall be comprised of a network of interoperable, stand-alone digital controllers communicating to a host computer within one facility within the project using graphical user interface software. The UMCS shall communicate to third party systems such as chillers, boilers, air handling systems, energy management systems, access control systems, fire-life safety systems and other building management related devices with open, interoperable communication capabilities.

Provide a TCS including associated equipment and accessories as specified.

Manufacturer's products, including design, materials, fabrication, assembly, erection, examination, inspection, and testing shall be in accordance with ASME B31.1 and NFPA 70, except as modified herein or indicated otherwise. Routers and /or gateways between the JACE NAC or workstation computer to the JBLM Wide Area Network (WAN)/ Local Area Network (LAN) shall not be utilized due to security restrictions.

The TCS systems shall maintain stable temperature control and all other conditions as indicated. The end-to-end accuracy of the system, including temperature sensor error, wiring error, A/D conversion, and display, shall be 1 degree F or less.

1.4 DDC SYSTEM DESCRIPTION

1.4.1 Design Requirements

1.4.1.1 Control System Schematic

Provide control system schematic that includes the following:

SECTION 23 09 23.00 11 Page 10 R0003

a. Location of each input and output device

b. Flow diagram of each HVAC component, for instance flow through coils, fans, dampers

c. Name or symbol for each component such as V-1, DM-2, and T-1 for a valve, damper motor, and temperature sensor, respectively

d. Setpoints

e. Sensor range

f. Actuator range

g. Valve and damper schedules and normal position

h. Switch points on input switches

i. Written sequence of operation for each schematic

j. Schedule identifying each sensor and controlled device with the following information:

(1) LAN and Software point name with send and receive address if applicable

(2) Point type (AO, AI, DO, DI)

(3) Point range

(4) Digital controller number for each point

1.4.1.2 Electrical Equipment Ladder Diagrams

Submit diagrams showing electrical equipment interlocks, including voltages and currents.

1.4.1.3 Component Wiring Diagrams

Submit a wiring diagram for each type of input device and each type of output device. Diagram shall show how the device is wired and powered;

showing typical connections at the digital controller and each power supply, as well as at 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, proof, and humidity sensors and transmitters.

1.4.1.4 Terminal Strip Diagrams

Submit a diagram of each terminal strip, including digital controller base terminal strips (digital controllers shall not be directly wired for ease of removal and replacement), terminal strip location, termination numbers and the associated point names.

1.4.1.5 Communication Network Architecture and Block Diagram

Submit a schematic showing communication networks used for all DDC system controllers, workstations, and field interface devices. Schematic shall show hierarchical topology. The supplied system must incorporate the

SECTION 23 09 23.00 11 Page 11 R0003 ability to access all data using Java enabled browsers without requiring proprietary operator interface and configuration programs. An Open DataBase Connectivity (ODBC) or Structured Query Language (SQL) compliant server database is required for all system database parameter storage.

This data shall reside on a supplier-installed server/computer using a Web Supervisor for all database access. Systems requiring proprietary database and user interface programs shall not be acceptable. All controllers shall be fully programmable and/or configurable from a remote workstation via the WAN using a Niagara Workbench application and/or a Web Supervisor.

Configurable controls are only acceptable in application specific topology i.e. VAV controllers part of a distributed control network connected to a higher level controller such as a Air Handling Unit controller.

1.4.2 Symbols, Definitions and Abbreviations

Symbols, definitions, and engineering unit abbreviations used in information displays, submittals and reports shall be as shown in the contract drawings. Symbols, definitions and abbreviations not in the contract drawings shall conform at a minimum to IEEE Std 100 and the ASHRAE FUN IP, unless indicated otherwise.

1.4.3 System Units and Accuracy

System print-outs and calculations shall be performed in English (inch-pound) units. Graphical User Interface (GUI) system displays shall be in English (inch-pound) units. Parameter modifications made through the GUI shall be displayed and accomplished in English units. Calculations shall have accuracy equal to or exceeding sensor accuracy. Displays and printouts shall have precision and resolution equal to or exceeding sensor accuracy.

1.5 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only or as otherwise designated. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government.

Submit manufacturers' specification sheets for each type of equipment to show compliance with the project specification. For each type of equipment highlight each compliance item and reference each item to the relevant specification paragraph number. Submit sufficient manufacturers' information to allow verification of compliance by the reviewing authority. Equipment and software for which specification compliance data shall be submitted (in accordance with Section 01 33 00 SUBMITTAL PROCEDURES) includes but is not limited to the following:

SD-01 Preconstruction Submittals

List of Drawings; G

List of Symbols, Definitions and Abbreviations Used on Drawings; G

List of Input/Output (I/O) Points; G

SD-02 Shop Drawings

Drawings shall be on A1 34 by 22 inch sheets in the form and

SECTION 23 09 23.00 11 Page 12 R0003 arrangement shown. The drawings shall use the same abbreviations, symbols, nomenclature and identifiers shown. Each control system element on a drawing shall have a unique identifier as shown. The HVAC Control System Drawings shall be delivered together as a complete submittal. Deviations must be approved by the Contracting Officer. Drawings shall be submitted along with Submittal SD-01, Preconstruction Submittals.

a. HVAC Control System Drawings shall include the following:

Sheet One: Drawing Index, HVAC Control System Legend.

Sheet Two: Valve Schedule, Damper Schedule.

Sheet Three: (Not used).

Sheet Four: Control System Schematic and Equipment Schedule.

Sheet Five: Sequence of Operation and Data Terminal Strip Diagrams.

Sheet Six: Control Loop Wiring Diagrams and Ladder Diagrams

Sheet Seven: Motor Starter and Relay Wiring Diagram.

Sheet Eight: Communication Network Architecture and Block Diagram; G.

Sheet Nine: DDC Panel Installation and Block Diagram.

(Repeat Sheets Four through Seven for each AHU System.)

b. The HVAC Control System Drawing Index shall show the name and number of the building and military site. The Drawing Index shall list HVAC Control System Drawings, including the drawing number, sheet number, drawing title, and computer filename when used. The HVAC Control System Legend shall show generic symbols and the name of devices shown on the HVAC Control System Drawings.

c. The valve schedule shall include each valve's unique identifier, size, flow coefficient Cv, pressure drop at specified flow rate, spring range, positive positioner range, actuator size, close-off pressure data, dimensions, and access and clearance requirements data. Valve schedules may be submitted in advance but shall be included in the complete submittal.

d. The damper schedule shall contain each damper's and each actuator's identifier, nominal and actual sizes, orientation of axis and frame, direction of blade rotation, spring ranges, operation rate, positive positioner ranges, locations of actuators and damper end switches, arrangement of sections in multi-section dampers, and methods of connecting dampers, actuators, and linkages. The Damper Schedule shall include the maximum leakage rate at the operating static-pressure differential. The Damper Schedule shall contain actuator selection data supported by calculations of the torque required to move and seal the dampers, access and clearance requirements. Damper schedules may be submitted in advance but shall be included in the complete submittal.

SECTION 23 09 23.00 11 Page 13 R0003

e. The HVAC control system schematics shall show all control and mechanical devices associated with the HVAC system. A system schematic drawing shall be submitted for each HVAC system.

f. The HVAC control system equipment Schedule shall be developed. All devices shall have unique identifiers and shall be referenced in the equipment schedule. Information to be included in the equipment schedule shall be the control loop, device unique identifier, device function, setpoint, input range, and additional important parameters (i.e., output range). An equipment schedule shall be submitted for each HVAC system.

g. The HVAC control system sequence of operation shall reflect the language and format of this specification, and shall refer to the devices by their unique identifiers as shown on the contract drawings. No operational deviations from specified sequences will be permitted without prior written approval of the Contracting Officer. Sequences of operation shall be submitted for each HVAC control system including each type of terminal unit control system.

h. The HVAC control system wiring diagrams shall be functional wiring diagrams which show the interconnection of conductors and cables to HVAC control panel terminal blocks and to the identified terminals of devices, starters and package equipment. The wiring diagrams shall show necessary jumpers and ground connections. The wiring diagrams shall show the labels of all conductors. Sources of power required for HVAC control systems and for packaged equipment control systems shall be identified back to the panel board circuit breaker number, HVAC system control panel, magnetic starter, or packaged equipment control circuit. Each power supply and transformer not integral to a controller, starter, or packaged equipment shall be shown. The connected volt-ampere load and the power supply volt-ampere rating shall be shown. Wiring diagrams shall be submitted for each HVAC control system.

SD-03 Product Data

DDC hardware; G

Workstation software; G

a. Programming software

b. General purpose programmable controller operating programs

c. External interface files

d. Database

Input device; G

Output device; G

Surge and Transient Protection; G

Notebook computer; G

SD-05 Design Data

SECTION 23 09 23.00 11 Page 14 R0003

Network Bandwidth Usage Calculations; G

In lieu of calculations, provide a network bandwidth test generated from software such as Loytec Protocol Analyzer.

SD-06 Test Reports

Performance Verification Tests

Field Tests; G

Preconstruction QC Checklist

Postconstruction QC Checklist

Training

Three copies of an outline for the HVAC control system training course with a proposed time schedule. Approval of the planned training schedule shall be obtained from the Government at least 60 days prior to the start of the training. Ten copies of HVAC control system training course material 30 days prior to the scheduled start of the training course. The training course material shall include the operation manual, maintenance and repair manual, and paper copies of overheads used in the course.

SD-07 Certificates

Contractors' Qualifications; G

Training; G

SD-11 Closeout Submittals

Posted operating instructions:

Provide administrative and closeout submittals:

Training Course Documentation; G

Service organizations; G

Contractor certification; G

Closeout QC Checklist;

1.6 Operating environment

Protect components from humidity and temperature variations, dust, and other contaminants, within limits published by the manufacturer.

1.7 QUALITY ASSURANCE

1.7.1 Standard Products

a. Material and equipment shall be standard products of manufacturer regularly engaged in the manufacturing of such product, using similar materials, design and workmanship. The standard products

SECTION 23 09 23.00 11 Page 15 R0003 shall have been in commercial or industrial use for 2 years prior to bid opening. The 2-year use shall include applications of similarly sized equipment and materials used under similar circumstances and sold on the commercial market through advertisements, manufacturers' catalogs, or brochures.

b. Products are supported by a local service organization.

1.7.2 Nameplates and Tags

a. Nameplates and tags bearing device unique identifiers shall be engraved or stamped. Permanently attach nameplates to HVAC control panel doors and back plates.

b. For each field mounted piece of equipment attach a plastic or metal tag with equipment name and point identifier.

1.7.3 Verification of Dimensions

Verify all dimensions in the field, and shall advise the Contracting Officer of any discrepancy before performing work.

1.7.4 Drawings

Because of the small scale of the drawings, it is not possible to indicate all offsets, fittings, and accessories that may be required. Carefully investigate the mechanical, electrical, and finish conditions that could affect the work, and shall furnish all work necessary to meet such conditions.

1.7.5 Contractors Qualifications

The Contractor or subcontractor(s) performing the work shall have completed at least five DDC systems installations of a similar design and complexity and have successfully completed at least five Tridium integrations using both LonMark controllers and BACnet systems with the use of Niagara Workbench programming software running on the Niagara platform.

1.7.6 Training Course Documentation

Training course documentation shall include a manual for each trainee plus two additional copies and two copies of audiovisual training aids (DVD format). Documentation shall include an agenda, defined objectives for each lesson and detailed description of the subject matter of each lesson.

1.7.7 Service Organizations

Qualified service organization list shall include the names and telephone numbers of organizations qualified to service the HVAC control systems.

1.7.8 Contractor Certification

Provide certification that installation of the control system is complete and meets the technical requirements of this section.

1.7.9 Modification of References

The advisory provision in ASME B31.1 and NFPA 70 are mandatory. Substitute the word "shall" for "should" wherever it appears and interpret all

SECTION 23 09 23.00 11 Page 16 R0003 references to the "authority having jurisdiction" and "owner" to mean the Contracting Officer.

PART 2 PRODUCTS

2.1 DDC SYSTEM

a. Provide a DDC system as a distributed control system. The system shall have stand-alone Interoperable LonMark (TM) or LonWorks, or BACnet digital controllers, a communications Network , and a separate workstation computer with Web Supervisor workstation software, licensed to the Government as "GSA" in the license orgId (organization identification) property file. The installing controls contractor will be included in the orgId for system access during construction and warranty period. LonMark/LonWorks controllers and, or BACnet controllers shall be connected to a Tridium JACE Network Area Controller (provided by controls contractor) to be node licensed to the existing JBLM UMCS Master Web Supervisor.

b. Provide an operator programmable system to perform closed-loop, modulating control of building equipment. Connect all digital controllers through the communication network to share common data and report to workstation computers. Provide Web Supervisor software on the DDC workstation capable of programming and monitoring the digital controllers. The control system shall be capable of downloading programs between the workstation and digital controllers.

c. Provide the quantity of digital controllers as required to perform the sequences of operation, or where shown, or as indicated on the drawings to perform required climate control, energy management, and alarm functions. The quantity of controllers shall be no less than that required to perform the sequences of operation within the parameters indicated in these specifications and contract drawings. All material used shall be currently in production.

2.1.1 Interoperable Direct Digital Controllers

DDC hardware shall be UL 916 rated. Interoperable controllers (IDC's) shall be LonMark (TM) or LonWorks bearing the applicable LonMark (TM) interoperability logo and shall be compatible with the Niagara Framework (a Tridium partner). Where LonMark (TM) devices are not available, devices based on LonWorks are acceptable providing that the controllers are programmable or configurable through the JACE controller. Interoperable BACnet Controllers (IBC's) shall be in accordance with ASHRAE 135 and shall be compatible with the Niagara Framework (a Tridium partner). IBC's must be provided with product interoperability compliance statement documents that demonstrate the compliance level to ASHRAE 135.

2.1.1.1 Distributed Control

Apply digital controllers in a distributed control manner.

2.1.1.2 I/O Point Limitation

Total number of I/O hardware points, including those communicated over a LAN, used by a single stand-alone digital controller, including I/O expansion units shall not exceed 48.

SECTION 23 09 23.00 11 Page 17 R0003

2.1.1.3 Environmental Operating Limits

Provide digital controllers that operate in environmental conditions between 32 and 120 degrees F.

2.1.1.4 Stand-Alone Control

Provide stand-alone digital controllers.

2.1.1.5 Internal Clock

Provide a clock with each stand-alone controller. Each controller shall have its clock backed up by a battery or capacitor with sufficient capacity to maintain clock operation for a minimum of 72 hours during power outage.

2.1.1.6 Memory

a. Provide sufficient memory for each controller to support required control, communication, trends, alarms, and messages

b. Memory Protection: Programs residing in memory shall be protected either by using EEPROM, flash memory, or by an uninterruptible power source (battery or uninterruptible power supply (UPS)). The backup power source shall have sufficient capacity to maintain volatile memory during an AC power failure. Where the uninterruptible power source is rechargeable (a rechargeable battery), provide sufficient back-up capacity for a minimum of seventy-two hours. The rechargeable power source shall be constantly charged while the controller is operating under normal line power. Where a non-rechargeable power source is used, provide sufficient capacity for a minimum of two years accumulated power failure. Batteries shall be replaceable without soldering.

2.1.1.7 Inputs

Provide input function integral to the direct digital controller. Provide input type(s) as required by the DDC design. For each type of input used on high-level controllers, provide at least one similar spare input point per controller.

a. Analog Inputs: Allowable input types are 100 ohm (or higher) platinum RTDs, thermistors, 4 to 20 mA, and 0-10 VDC. Thermistor and direct RTD inputs must have appropriate conversion curves stored in controller software or firmware. Analog to digital (A/D) conversion shall have 10-bit minimum resolution.

b. Digital Inputs: Digital inputs shall sense open/close, on/off, or other two state indications.

2.1.1.8 Outputs

Provide output function integral to the direct digital controller. Provide output type(s) as required by the DDC design. For each type of output used on high-level controllers, provide at least one similar spare output point per controller.

a. Analog Outputs: Provide controllers with a minimum output resolution of 10 bits. Output shall be 4 to 20 mA or 0 to 10

SECTION 23 09 23.00 11 Page 18 R0003

VDC.

b. Digital Outputs: Provide contact closure with contacts rated at a minimum of 1 ampere at 24 volts.

2.1.1.9 PID Control

Provide controllers with proportional integral, and derivative control capability. Terminal controllers are not required to have the derivative component.

2.1.1.10 Digital Controller Networking Capabilities

The intent of this specification is to provide a peer-to-peer networked, stand-alone, distributed control system with the capability to integrate both the ASHRAE 135 BACnet and LonWorks technology communication protocols in one open, interoperable system. The upper level digital controllers shall be Tridium JACE controllers capable of networking with the existing Public Works network of JACE controllers at JBLM. Upper level controllers shall also be capable of communicating over JBLM Ethernet WAN and V-LAN network between buildings. The JACE Controller shall be connected to the UMCS through the NEC switch. NEC switch is not within the Scope of the contract. Cat-6 wiring to switch to be provided by contractor.

a. LonMark (TM) IDC Networking Capabilities

Run the LonWorks network trunk to the nearest JACE Network Area Controller (NAC). Coordinate locations of the NAC to ensure that maximum network wiring distances, as specified by the LonWorks wiring guidelines, are not exceeded. A maximum of 126 devices may occupy any one LonWorks trunk and must be installed using the appropriate trunk termination device. All LonWorks and LonMark devices must be supplied using FTT-10A LonWorks communications transceivers. The IDCs shall communicate with the NAC at a baud rate of not less than 78.8K baud. The IDC shall provide LED indication of communication and controller performance to the technician, without cover removal.

b. IBC Networking Capabilities:

The system supplier must provide a PICS document showing the installed systems compliance level to the ASHRAE 135, to the Division 17 contractor. Minimum compliance is Level 3.

Physical connection of BACnet devices shall be via Ethernet.

The IBC Sensor shall connect directly to the IBC and shall not utilize any of the I/O points of the controller. The IBC Sensor shall provide a two-wire connection to the controller that is polarity and wire type insensitive. The IBC Sensor shall provide a communications jack for connection to the BACnet communication trunk to which the IBC controller is connected. The IBC Sensor, the connected controller, and all other devices on the BACnet bus shall be accessible by the portable operators terminal (POT).

2.1.1.11 Communications Ports

a. Controller-to-Controller LAN Communications Ports: Controllers in the building DDC system shall be connected in a communications

SECTION 23 09 23.00 11 Page 19 R0003 network. Controllers shall have controller to controller communication ports to both peer controllers (upper level controllers) and terminal controllers (lower level controllers).

Network may consist of more than one level of local area network and one level may have multiple drops. Communications network shall permit sharing information between controllers, allowing execution of dynamic control strategies, and coordinated response to alarm conditions. Minimum baud rate for the lowest level LAN shall be 9600 Baud. Minimum baud rate for the highest level LAN shall be 9600 Baud. Minimum baud rate for a DDC system consisting of a single LAN shall be 9600 Baud.

b. On-Site Interface Ports: Provide a RS-232, RS-485, or RJ-11 communications port for each digital controller that allows direct connection of a computer or laptop and through which the controller may be fully accessed. Controller access shall not be limited to access through another controller. On-site interface communication ports shall be in addition to the communications port(s) supporting controller to controller communications.

Communication rate shall be 9600 Baud minimum. Every controller on the highest level LAN shall have a communications port supporting direct connection of a computer; a hand held terminal port is not sufficient. The following operations shall be available: downloading and uploading control programs, modifying programs and program data base, and retrieving or accepting trend reports, status reports, messages, and alarms.

2.1.1.12 Digital Controller Cabinet

Each indoor digital controller cabinet shall protect the controller from damage and shall be rated NEMA 1. Cabinets for controllers, including maintenance controllers located in the Mechanical Room, shall have hinged door, be lockable, of welded construction, be sized for at least a 16-inch monitor, include an internal fan and removable filter, and have a removable metal back plate. Slide-out keyboard drawer shall also be lockable. All doors shall be keyed alike. Cabinet shall be bolted by the contractor to a floor mounted pad where indicated, and be suitably braced for seismic loads.

2.1.1.13 Main Power Switch

Each controller on the highest level LAN or each control cabinet shall have a main external power switch for isolation of the controller from AC power. The switch shall be located in the DDC cabinet and shall be labeled.

2.1.2 Terminal Control Units (TCUs)

a. The same company as the digital controllers shall manufacture TCUs.

b. TCUs shall automatically start-up on return of power after a failure, and previous operating parameters shall exist or shall be automatically downloaded from a digital controller on a higher level LAN.

c. TCUs do not require an internal clock if they get time information from a higher level digital controller.

SECTION 23 09 23.00 11 Page 20 R0003

2.1.3 DDC Software

The Contracting Officer's representative shall sign a copy of the manufacturer's standard software and firmware licensing agreement as a condition of this contract. Such license shall grant use of all programs and application software to JBLM as defined by the manufacturer's license agreement, but shall protect manufacturer's rights to disclosure of trade secrets contained within such software. The supplied computer software shall employ object-oriented technology (OOT) for representation of all data and control devices within the system. In addition, adherence to industry standards including ASHRAE 135, BACnet and LonMark to assure interoperability between all system components is required. For each LonWorks device that does not have LonMark certification, the device supplier must provide an XIF file for the device. For each BACnet device, the device supplier must provide a PICS document showing the installed device's compliance level. Minimum compliance is Level 6; with the ability to support data read and write functionality. All integration and programming shall be via the Niagara Framework network engineering software tools, Niagara Workbench.

2.1.3.1 Sequence of Control

Provide, in the digital controllers, software to execute the sequence of control. Provide one registered copy of all software used to program control sequences in direct digital controllers, LAN controllers and field configurable smart controllers on the stationary workstation.