Attachment _2 DDC Specs.pdf

SECTION 23 09 23 Page 1

SECTION 23 09 23

DIRECT DIGITAL CONTROL FOR HVAC AND OTHER LOCAL BUILDING

SYSTEMS 05/19

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 within the text by the basic designation only.

AIR MOVEMENT AND CONTROL ASSOCIATION INTERNATIONAL (AMCA)

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

ASME INTERNATIONAL (ASME)

ASME B16.5 (2003) Standard for Pipe Flanges and Flanged Fittings: NPS 1/2 through NPS 24

ASME B31.1 (2007; Addenda 2008) Power Piping

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE FUN IP (2005) Fundamentals Handbook, I-P Edition

ASHRAE 135 (2004; Int 1 thru 5 2004; Addenda A 2004;

Errata 2005; Int 6 thru 15 2005; Int 16 thru

18 2006; Addenda C 2006; Addenda D 2006; Errata to Addenda D 2006; Int 19 thru 22

2007; Addenda F 2007; Addenda E 2007; Errata 2007, Errata 2008, Errata 2008; Int 23 thru 28 2008; Addenda M 2008) BACnet

ASHRAE Gdln3 (2007) Exterior Enclosure Technical Requirements for the Commissioning Process

ASTM INTERNATIONAL (ASTM)

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

CONSUMER ELECTRONICS ASSOCIATION (CEA)

SECTION 23 09 23 Page 2

CEA-709.1B (2002) Control Network Protocol Specification

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

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

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 90A (2008) Standard for the Installation of Air

Conditioning and Ventilating Systems

NFPA 70 (2007; AMD 1 2008) National Electrical Code - 2008 Edition

SHEET METAL AND AIR-CONDITIONING CONTRACTORS' NATIONAL ASSOCIATION

(SMACNA)

SMACNA 1966 (2005) HVAC Duct Construction Standards Metal and Flexible

SMACNA HVACTAB (2002, 3rd Ed) HVAC Systems - Testing, Adjusting and Balancing

UNDERWRITERS LABORATORIES (UL)

UL 268A (2008) Smoke Detectors for Duct Application

UL 506 (2000; Rev thru May 2006) Standard for Specialty Transformers

UL 916 (2007) Energy Management Equipment

UL 1449 (2006) Surge Protective Devices

1.2 DEFINITIONS

1.2.1 Digital Controller

1.2.1.1 Interoperable Digital Controller (IDC)

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

1.2.1.2 Interoperable BACnet Controller (IBC)

SECTION 23 09 23 Page 3

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 the 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 receiver controllers, thermostats, and logic units are present within or interface with a direct digital control loop. Actuators are electric and the controller output is converted to the appropriate type of signal.

1.2.3 DDC System

A system made up of one or more interoperable digital controllers which 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 two 48 or less per controller. Failure of any single controller will not cause the loss of more than 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 set points 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 a computer that is compatible with the latest version of the Army Gold Master (AGM) (Verify latest version with EMSC Administrator). The GUI employs browser like

SECTION 23 09 23 Page 4 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 on Joint Base Lewis McChord (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 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 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.

SECTION 23 09 23 Page 5

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

c. The controller’s peer-to-per 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.12 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.13 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. The JACE shall not be used to control major HVAC equipment or systems.

1.2.14 LonMark

See LonMark International. Also, a certification issued by LonMark International to CEA-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 CEA-709.1B devices and issues the LonMark Certification for CEA-709.1B devices.

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 CEA-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 Output Signal Conversion

SECTION 23 09 23 Page 6

Output signal conversion refers to changing one kind of control output into a proportionally related signal appropriate for direct actuation of the controlled device. An example is converting a 4 to 20 mA or 0 to 10 VDC signal to a proportional 20 to 103 kPa (3 to 15 psig) signal to operate a pneumatic actuator.

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 set point when occupied.

Optimum start is based on the zone temperatures, zone set points, 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 IAW (in accordance with) the manufacturers written instructions, sequence of operation and control drawings. See Commissioning Appendix A as a reference.

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.

SECTION 23 09 23 Page 7

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

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 (FCUs), and heat pumps. TCUs shall be LonMark/Lonworks or BACnet based. All TCUs shall be remotely configurable via the JBLM Enviro VLAN 4003.

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 JBLM Niagara Framework Utilities Management and Control System (UMCS), and comprised of a network of interoperable, standalone digital controllers communicating via LonMark/LonTalk and/or BACnet to a JACE Controller (Network NAC). The JACE Controller to be connected to the UMCS/DDC Controller through the NEC switch. NEC switch is not within the Scope of the contract. Cat-6 wiring to switch to be provided by Contractor. Access to the system shall be accomplished through the JBLM Enviro VLAN 4003.

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, 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 Enviro VLAN 4003 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

SECTION 23 09 23 Page 8 temperature sensor error, wiring error, A/D conversion, and display, shall be 0.5 degree C or less.

1.4 DESIGN REQUIREMENTS

1.4.1 Control System Schematic

Provide control system schematic that includes the following:

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 by component name such as V-1, DM-2, and T-1 for a valve, damper motor, and temperature sensor, respectively

d. Set points

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 control system 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.2 Electrical Equipment Ladder Diagrams

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

1.4.3 Component Wiring Diagrams

SECTION 23 09 23 Page 9

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.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.5 Communication Architecture Schematic

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 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 Enviro VLAN 4003 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 an Air Handling Unit controller.

1.4.6 Symbols, Definition 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.

1.4.7 System Units and Accuracy

System print-outs and calculations shall be performed in English (inch pound) units. Graphic User Interface (GUI) system displays shall be in English (inch-pound). 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

SECTION 23 09 23 Page 10

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Drawings; G

List of abbreviations, symbols, nomenclature and identifiers used on the Drawings; G

List of I/O Points; G

List of Equipment Components; G

AC Power Table; G

SD-02 Shop Drawings

Shop Drawings; G

SD-03 Product Data DDC hardware; G

DDC capabilities

Variable Frequency 3 Phase Motor Drives; G

Workstation software

Programming software General purpose programmable controller operating programs

External interface files

Database

Input devices

Output devices

Surge and transient protection

Smoke detectors

SD-05 Design Data

SECTION 23 09 23 Page 11

Network Bandwidth Usage Calculations; In lieu of calculations provide a network bandwidth test to the communications contractor and COE generated from software such as Loytec Protocol Analyzer.

SD-06 Test Reports

Field tests

Preconstruction QC Checklist

Post construction QC Checklist

Commissioning Report

Performance verification test

Training

An electronic (.pdf) version 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, five copies of the 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

Training

SD-10 Operation and Maintenance (O&M) Data

Controls and HVAC System Operators

Manual

DDC Manufacturer's Hardware and Software Manuals

SD-11 Closeout Submittals

Provide administrative and closeout submittals:

Training course documentation

Service organizations

Contractor certification

Closeout QC Checklist

SECTION 23 09 23 Page 12

DDC Training DVD

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 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

The Contractor shall 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. The Contractor shall 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

SECTION 23 09 23 Page 13 programming software running on the Niagara platform. Contractor shall be a Certified and/or Authorized Tridium Controls Integrator.

C

1.7.6 Training Course Documentation

Training course documentation shall include a manual for each trainee plus one electronic (.pdf) version and 2 additional hard copies of manuals or audiovisual training aids. 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 that shall include the names and telephone numbers of organizations qualified to service the HVAC control systems.

1.7.8 Contractor Certification

Provide certification that the 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 references to the "authority having jurisdiction" and "owner" to mean the Contracting Officer.

1.7.10 Performance Verification Test

An electronic (.pdf) version of the HVAC Control System Performance Verification Test Procedures, in booklet form and indexed, 60 days before the Contractor's scheduled test dates. The performance verification test procedures shall refer to the devices by their unique identifiers as shown, shall explain, step-by-step, the actions and expected results that will demonstrate that the HVAC control system performs in accordance with the sequences of operation, the requirements of paragraph "Field Quality Control Tests" and other contract documents. An HVAC control system performance verification test equipment list shall be included that lists the equipment to be used during performance verification testing. The list shall include manufacturer name, model number, equipment function, the date of the latest calibration, and the results of the latest calibration.

1.7.11 Commissioning Report

Submit one electronic (.pdf) version and 2 hard copies of the HVAC control system commissioning procedures, in booklet form and indexed, 60 days prior

SECTION 23 09 23 Page 14 to the scheduled start of commissioning. Commissioning procedures shall be provided for each HVAC control system, and for each type of terminal unit control system. The Commissioning procedures shall reflect the format and language of this specification, and refer to devices by their unique identifiers as provided by the Contractor, or if applicable, as shown. The Commissioning procedures shall be specific for each HVAC system, and shall give detailed step-by-step procedures for commissioning of the system per paragraph "Field Quality Control Tests." Contractor shall provide at least 2 weeks advance notice to the Contracting Office in order for the Government representative to be present at commissioning.

a. The Commissioning procedures shall include detailed, product specific set-up procedures, configuration procedures, adjustment procedures, Lon network testing to include simulated failures proving controllers operate as stand-alone and calibration procedures for each device. Where the detailed product specific commissioning procedures are included in manufacturer supplied manuals, reference may be made in the HVAC control system commissioning procedures to the manuals.

b. An HVAC control system commissioning procedures equipment list shall be included that lists the equipment to be used to accomplish commissioning. The list shall include manufacturer name, model number, equipment function, the date of the latest calibration, and the results of the latest calibration.

1.7.12 DDC Manufacturer's Hardware and Software Manuals

Provide one electronic (.pdf) version and 2 hard copies of the following manuals.

a. Installation and Technical Manuals for all digital controller hardware.

b. Installation and Technical Manuals for workstation.

c. Operator Manuals for all digital controllers.

d. Operator Manuals for all workstation software.

e. Programming Manuals for all digital controllers.

f. Provide one electronic (.pdf) version and 2 hard copies of programming Manuals for workstation software.

1.7.13 Controls and HVAC System Operators Manual

Submit one electronic (.pdf) version and 2 hard copies of the Control and

SECTION 23 09 23 Page 15

HVAC Systems Operators Manual. Provide in hard copies in a 3 ring binder with a minimum of the following 7 sections. Use tabs to divide each section.

a. Description of HVAC Systems: Provide a description of the HVAC system components and control system. Include sequence of operation and a complete List of I/O Points.

b. Controls Drawings: Provide drawings as specified in submittal paragraph.

c. Control Program Listings: Provide listing of all control programs, including terminal equipment controller setup pages if used.

d. Current Operating Parameters: Provide printouts of input and output setup information, (database setups). This section provides information such as point addresses, slopes and offsets for all points, database of points, etc.

e. Design Information: Provide tab, but leave this section blank.

f. Control Equipment Technical Data Sheets: Provide technical data sheets for all controller hardware and accessories.

g. Backup of Control Program: Provide backup copies of the control program and ACAD control drawings on CD-ROM.

PART 2 PRODUCTS

2.1 DDC SYSTEM

a. Provide a DDC system as a distributed control system. The system shall have stand-alone Interoperable LonMarkTM 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 owner section. The installing controls contractor should be included in the owner section 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/Server.

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

SECTION 23 09 23 Page 16 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 LonMarkTM or LonWorks bearing the applicable LonMarkTM interoperability logo and shall be compatible with the Niagara Framework (a Tridium partner). Where LonMarkTM 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. IBC's must be provided with product interoperability compliance statement documents that demonstrate the compliance level to the 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.

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.

SECTION 23 09 23 Page 17

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 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

SECTION 23 09 23 Page 18

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 JBLM Enviro VLAN 4003 network. Upper level controllers shall also be capable of communicating over JBLM Enviro VLAN 4003 network between buildings. The JACE Controller is to 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.

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 network. Controllers shall have controller to controller communication ports to both peer controller (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:

Down loading 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

SECTION 23 09 23 Page 19

Each indoor digital controller cabinet shall protect the controller from dust and shall be rated NEMA 1, unless specified otherwise. Each outdoor digital controller cabinet shall protect the controller from all outside conditions and shall be rated NEMA 4. Cabinets for high level controllers shall be hinged door, lockable, and have offset removable metal back plate.

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. 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.

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

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. Provide any access keys which restrict programming language software functions or the ability to compile or prepare programming for download to controllers while editing parameters offline. Provide final copy of each program used in the

SECTION 23 09 23 Page 20 system in both compiled and editable formats. Where specially programmed factory configured smart controllers are used in the system, provide the minimum factory programming tools and specialized controller programs ready for download to replacement controllers. At minimum, controllers must be capable of performing programming functions outlined in the following "Parameter Modification" section. The units for graphic display, parameter modification and maintenance interface shall be English, even if the project is a metric design.

2.1.3.2 Parameter Modification

Provide software capable of modifying all control parameters. Parameter modification shall be accomplished for all controllers (high level and low level application specific) through the main workstation computer and with laptop computer or keypad terminal directly at each controller. The supplied computer software shall employ object-oriented technology (OOT) for representation of all data and control devices within the system.

Modifications shall be accomplished without having to make changes directly in line-by-line programming. Block programming languages shall provide for modification of these database parameters in fill-in-the-blank screens.

Parameters of like type, including those in different high level and low level controllers, may be grouped together for a single, global change.

For example, an operator may group all second floor space temperature set points into a group and raise the set point by two degrees with a single command. The following parameters shall be modifiable in this way:

a. Set points (English Units)

b. Dead band limits and spans

c. Reset schedules

d. Switch over points

e. PID gains and time between control output changes

f. Time

g. Timed local override time

h. Occupancy schedules

i. Holidays

j. Alarm points, alarm limits, and alarm messages

k. Point definition database

l. Point enable, disable, and override

m. Trend points, trend intervals, trend reports

SECTION 23 09 23 Page 21

n. Analog input default values

o. Passwords

p. Communications parameters including network and telephone communications setups

q. User thermostat/sensor set point limitations

2.1.3.3 Differential

Where set point is in response to some analog input such as temperature, pressure, or humidity, include a set point differential for the control loop to prevent short cycling of control devices.

2.1.3.4 Motor and Flow Status Delay

Provide an adjustable delay between when a motor is commanded on or off and when the control program looks to the motor or flow status input for confirmation of successful command execution.

2.1.3.5 Runtime Accumulation

Provide resettable run time accumulation for each controlled digital output.

2.1.3.6 Timed Local Override

Provide user definable adjustable run time for each push of a momentary contact timed local override. Pushes shall be cumulative with each push designating the same length of time. Provide a user definable limit on the number of contact closures summed, such as 6, before the contact closures are ignored. Timed local overrides are disabled during occupancy periods.

2.1.3.7 Time Programs

Provide programs to automatically adjust for leap years and make daylight savings time and standard time adjustments.

2.1.3.8 Scheduling

a. Individual controlled equipment shall be schedulable with schedule based on time of day, day of week, and day of year. Equipment may be associated into groups. Each group may be associated with a different schedule. Changing the schedule of a group shall change the schedule of all equipment in the group. Groups may be modified, created and deleted by the operator.

b. Provide capability that will allow current schedules to be viewed and modified in a seven-day week format. When control program does not automatically compute holidays, provide capability to enter holiday schedules one full year at a time.

SECTION 23 09 23 Page 22

2.1.3.9 Point Override

I/O and virtual points shall accept software overrides to any possible value.

2.1.3.10 Alarming

I/O points and software points shall be configured to alarm. Alarms may be enabled and disabled for every point and shall be initiated as shown on the Point Schedule. Alarm limits shall be adjustable on analog points.

Controllers connected to an external communications device such as a printer, terminal, or computer, shall download alarm and alarm message when alarm occurs. Alarms will be stored and automatically downloaded to a Supervisor/Server. See Appendix B for Alarm Matrix. The following conditions shall generate alarms:

a. Motor is commanded on or off but the motor status input indicates no change

b. Temperature, humidity, or pressure strays outside selectable limits

c. An analog input takes a value indicating sensor failure

d. A module is not communicating on the LAN

e. A power outage occurs

f. Do not alarm a “return to normal state”

2.1.3.11 Messages

Messages shall be operator defined and assigned to alarm or status conditions. Messages shall be displayed on the workstation or printer when these conditions occur.

2.1.3.12 Trending

DDC system shall have the capability to trend all I/O and virtual points.

Trend logs shall be initialed for the points identified in the Point Schedule. Points may be associated into groups. A trend report may be set up for each group. The period between logging consecutive trend values shall range from one minute to 60 minutes at a minimum. The minimum number of consecutive trend values stored at one time shall be 30 per variable.

When trend memory is full, the most recent data shall overwrite the oldest data. Trend data shall be capable of being uploaded to computer. Trend data shall be available on a real time basis; trend data shall appear numerically and graphically on a connected computer's screen as the data is processed from the DDC system. Trend reports shall be capable of uploading to computer for storage.

2.1.3.13 Status Display

SECTION 23 09 23 Page 23

Current status of I/O and virtual points shall be displayed on command.

Points shall be associated into functional groups, such as all the I/O and virtual points associated with control of a single air handling unit, and displayed as a group, so the status of a single mechanical system can be readily checked. A group shall be selectable from a menu of groups having meaningful names; such as AHU-4, Second Floor, Chiller System, and other such names.

2.1.3.14 Diagnostics

Each controller shall perform self-diagnostic routines and provide messages to an operator when errors are detected. The DDC system shall be capable of recognizing a non-responsive module on a LAN. The remaining, responsive modules on a LAN shall not operate in a degraded mode.

2.1.3.15 Power Loss

During a power outage, each controller shall assume a disabled status and outputs shall go to a user definable state. Upon restoration of power, DDC system shall perform an orderly restart, with sequencing of outputs without a need for human interaction.

2.1.3.16 Program Transfer

Provide software for download of control programs and database from a computer to controllers and upload of same to computer from controllers.

Every digital controller in the DDC system shall be capable of being downloaded and uploaded to through a single controller on the highest level LAN. At project completion a Station Backup shall be copied to a Supervisor/Server at 2012.

2.1.3.17 Password Protection

Provide at least three levels of password protection to the DDC system permitting different levels of access to the system. The lowest level allows monitoring only. The highest level allows full control of all functions, including setting new passwords.

2.1.4 Workstation

a. If specified in contract the contractor is to provide a central workstation computer installed with Web Supervisor Niagara Workbench software to provide an interface for monitoring, troubleshooting, and making adjustments to the program or operating parameters of all DDC controllers, including TCUs. The workstation shall also be capable of programming all controllers, including TCUs.

b. DDC system shall operate continuously without connection to the workstation. Information at the workstation is not required for day-to-day operations of the direct digital controllers.

SECTION 23 09 23 Page 24

c. Per Executive Order 13423, desktop computers, notebook computers, and PC monitors shall be registered under the Electronic Product Environmental Assessment Tool (EPEAT) (IEEE 1680 standard for personal computer products) at a minimum Bronze level, but preferably at Silver or above (http://www.epeat.net/). These items shall also meet applicable FEMP recommended standby power requirements (http://www1.eere.energy.gov/femp/procurement/eep_standby_power.htm l).

2.1.5 Hardware

The DDC system manufacturer shall assure compatibility of all workstation computer equipment and peripherals. The workstation shall be configured to operate according to the DDC system manufacturer's specifications.

Workstation hardware shall be configured to allow operation of software, uploading and downloading of programs, and creation of graphics. At a minimum the workstation hardware shall consist of:

a. If requested in the contract; computer shall be compatible with the latest version of the Army Gold Master (AGM), (verify the latest version with the UMCS/DDC Administrator),

b. Computer install DVD’s shall also be provided with desktop.

c. A 24 inch Flat Panel monitor with 1920 x 1080 minimum resolution,

d. A 101 character keyboard.

e. Optical Mouse: Three button with scroll wheel USB mouse.

f. 120-volt terminal strip UL 1449 6-outlet with surge protection.

g. Security Workstation Cabinet features: Locking upper compartment with Plexiglas window provided viewable access to most 20 inch monitors; Locking pull-out drawer facilitates ergonomic operation of keyboard, mouse, and convenient storage of small supplies;

Keyboard and supplies can be accessed even while top and bottom compartments are locked; Full size locking bottom doors in front and rear for complete access to equipment and cables; Lower compartment features one fixed bottom and one adjustable shelf for desktop or tower style PCs, printer, paper or supplies; Louvers in rear provide equipment ventilation; Heavy duty all welded steel top and bottom sections bolt together for easy assembly; Top Level Compartment (internal): 20¾" W x 21¾" D x 19¼" H; Lower Level Compartment (internal): 20¾" W x 21¼ D x 23½" H; Overall Dimensions: 21" W x 22½" D x 59½" H

SECTION 23 09 23 Page 25

2.1.6 Software

Workstation software shall be Web Supervisor with the appropriate Niagara Workbench (Latest version of Tridium Niagara, verify version with the UMCS/DDC Administrator) services and configured to operate according to the DDC system manufacturer's specifications. Software shall be resident in the workstation computer and permit monitoring, programming and troubleshooting of the DDC system. Workstation software permits modification of controller parameters and control for all controllers, both high level and low level application specific. Operations shall be menu selected. Menu selections shall be made with a mouse.

a. Menu System: Menu system shall allow an operator to select a particular function or access a particular screen through successive menu penetration.

b. Controller Parameter Modification: The workstation software shall be an interface for performance specified in paragraph entitled "Parameter Modification" and available through direct connection of a computer to a digital controller. Parameter modification shall require only that an operator "fill in the blank" for a parameter on a screen requesting the information in plain language. Parameter modifications shall download to the appropriate controllers at operator request.

c. Program…