25_00_00_Integrated_Automation.pdf

Pennsylvania Air National Guard, 193d RSG Project No. LKLW959716

CONSOLIDATE VEHICLE MAINTENANCE FUNCTION 5/1/2015

INTEGRATED AUTOMATION 25 00 00 - 1

SECTION 25 00 00

INTEGRATED AUTOMATION

PART 1 GENERAL

1.01 SUMMARY

A. This Section contains the specification for a Building Automation System (BAS) including supporting equipment. Building Automation System (BAS) is to be a fully functional Web-based native BACnet. This system must comply with the following Specifications and BAS sequence of operation with I/O points schedule. A non-BACnet/Web-based system will not be acceptable.

B. Related Sections:

1. Section 22 11 13 – Domestic Water Piping

2. Section 25 90 00 - Sequence of Operation

3. Section 26 05 03 – Equipment Wiring Connections

4. Section 26 24 13 – Switchboards

5. Section 26 24 19 – Panel Boards

1.02 SCOPE OF WORK

A. The direct digital control system is to be Automated Logic. Substitutions are not acceptable.

B. The lighting control system shall be an integral part of the BAS.

C. Lighting control panels shall reside on the BAS network.

D. Provide lighting control panels and low voltage switches.

E. Integrate output from the power meters, water meter, and natural gas meter into the BAS.

1. Coordinate output requirements of the meters with the BAS

a. Refer to Section 26 24 13 and 26 24 19.

F. Contractor's Responsibilities: Furnish and install all necessary software and hardware, wiring, and computing equipment in compliance with this Specification. Any variances from this specification or related documentation shall be submitted in writing at the time of Bid.

G. All power wiring and conduit for the BAS system controllers and supporting equipment such as motor operated dampers, control panels, relay panels, and sensors are to be provided and installed under Division 21, 22, and 23.

1. Refer to Electrical Drawings for the locations of panel boards and spare circuits for control system power.

INTEGRATED AUTOMATION 25 00 00 - 2

H. System Requirements:

1. Standard Material/Products: All material and equipment used shall be standard components, regularly manufactured and available, and not custom designed especially for this Project.

2. Modular Design: The system architecture shall be fully modular permitting expansion of application software, system peripherals, and field hardware.

3. NATIVE BACNET: The system must be native BACnet.

I. Equipment and System Software:

1. System Hardware:

a. Provide the Following:

1) PC’s, Laptops, PDA’s, server(s), routers, modems and control modules as specified.

2) All sensing devices, relays, switches, indicating devices, and transducers required to perform the functions as listed in the control sequences.

3) All monitoring and control wiring and air tubing.

2. System Software: The Controls Contractor shall provide all software identified in Part 2, BAS SERVER AND WEB BROWSER GUI, of this Specification, including the BAS Server, fully configured database, graphics, reports, alarm/events. The Graphical User Interface (GUI) shall be completely Web based as specified herein.

J. Input/Output Point Summary Schedule: The system as specified shall monitor, control, and calculate all of the points and perform all the functions as needed to accomplish Sequence of Operation; Refer to Section 25 90 00.

K. Codes and Regulations:

1. Standards Authority: All electrical equipment and material, and its installation, shall conform to the current requirements of the following authorities:

a. Occupational Safety and Health Act (OSHA).

b. National Electric Code (NEC).

c. National Fire Code.

d. International Mechanical Code.

e. International Building Code.

f. International Plumbing Code.

2. Product Applicable Standards: All distributed, standalone and unitary controllers supplied shall be in compliance with the following listings and standards:

a. UL916 for Open Energy Management (for U.S. and Canada).

b. FCC Part 15, Sub-Part B, Class A.

c. CE Electro Magnetic Compatibility.

3. Manufacturer’s Quality System: The control system manufacturer shall be ISO9001 listed for design and manufacture of environmental control systems for precise control and comfort, indoor air quality, HVAC plant operation, energy savings and preventative maintenance. ISO Certification

INTEGRATED AUTOMATION 25 00 00 - 3

shall be by a registrar that is accredited by an internationally recognized organization such as RAB. Copy of ISO9001 certificate shall be submitted with Bid.

4. Conflict of Codes: Where two or more codes conflict, the most restrictive shall apply. Nothing in this Specification or related documentation shall be construed to permit work not conforming to applicable codes.

L. Provide software updated to the central base control system.

1.03 QUALITY ASSURANCE

A. General:

1. The Building Automation System herein specified shall be fully integrated and installed as a complete package by the Building Automation System Contractor. The System shall include all wiring, installation supervision, calibration, adjustments, commissioning, and checkout necessary for a complete and fully operational system.

2. The Building Automation System Contractor shall be regularly engage in the engineering, programming, installation, and service of building automation system of similar size and complexity.

3. The BAS Contractor shall have a local branch facility within a 50-mile radius of this job site. Emergency service shall be available on a 24 hour, 7 day a week basis.

4. The BAS Contractor shall be responsible for all work fitting into place in a satisfactory and neat workmanlike manner acceptable to the Contracting Officer.

5. The BAS Contractor will coordinate with other Trade Contractors regarding the location and size of pipes, equipment, fixtures, conduit, ducts, openings, switches, outlets, etc., in order to eliminate any delays in the progress of the job.

6. The BAS Contractor will conduct a system wide point to point checkout and verification of the BAS systems operation with a management designated Facilities Management employee to confirm and validate operation of all BAS systems. Twenty four hours of consolidated verification time must be provided by the BAS Contractor and any additional time will be billed on a Time and Material Basis.

B. Experience Record:

1. The BAS Contractor shall have a minimum of 5 years experience with the complete, turn-key installation of building automation systems of similar size and technical complexity. The BAS Contractor shall provide site visits for the Contracting Officer for a minimum of two comparable projects which have building automation systems with the features as specified for this Project. These projects must be on-line and functional.

2. The BAS Contractor shall employ specialists in the field of Building Automation Systems including: Programming, Engineering, Field

INTEGRATED AUTOMATION 25 00 00 - 4

Supervision and Installation. Specialists shall have a minimum of 5 years of experience with Building Automation Systems.

C. Products:

1. The Building Automation System architecture shall consist of the products of a manufacturer regularly engaged in the production of Building Automation Control Systems and shall be the manufacturer’s latest standard of design. Controllers and DDC system components shall be current production products.

2. All other equipment shall be the products of the BAS manufacturers or approved manufacturer regularly engaged in production of specialized building automation system materials or equipment.

D. Electrical Wiring:

1. All Wiring to Comply with the Following:

a. Conduit for the BAS is to be colored green.

b. All electrical wiring located inside any mechanical/electrical room will be installed in Intermediate Metal Conduit.

c. All wiring located on roof or exposed to outdoor elements shall be installed in Rigid Galvanized Steel conduit

d. Refer to section 26 05 03.

2. All DDC Controllers shall be UL listed.

1.04 SUBMITTALS, DOCUMENTATION, ACCEPTANCE, AND TRAINING

A. Submittals:

1. Shop Drawings: A minimum of ten copies of Shop Drawings shall be submitted and shall consist of a complete list of equipment, materials, manufacturer's technical literature, cut-sheets, and installation instructions.

Drawings shall contain proposed layout, complete wiring, routing, schematic diagrams, tag number of devices, software descriptions, written sequences of operations, calculations, installation details, and any other details required to demonstrate that the system will function properly.

2. Graphical Programming Documentation: Provide a printout all Graphical Programs, identifying the specific HVAC or mechanical/electrical subsystem being controlled.

3. Drawing Approval: Shop Drawings shall be approved before any equipment is installed. Controls contractor shall allow a minimum of 14 business days for drawing approval.

B. As Built Drawings: All Drawings shall be reviewed after the final system checkout and updated or corrected to provide 'as-built' drawings to show exact installation. All Shop Drawings will be acknowledged in writing by the Contracting Officer before installation is started and again after the final checkout of the system. The system will not be considered complete until the as-built Drawings have received their final approval.

INTEGRATED AUTOMATION 25 00 00 - 5

C. Documentation:

1. Operating and Maintenance (O&M) manuals for the system shall be made available electronically using Acrobat 4.X (PDF) format and include the following categories: Workstation User's Manual, Project Engineering Handbook, Software Documentation.

2. BAS User's Manual shall Contain as a Minimum:

a. System overview.

b. Networking concepts.

c. Launching a web browser from a networked PC/PDA and login.

d. Graphical User Interface (GUI) screen menus and their definitions.

e. Creating, modifying or deleting schedules.

f. Uploading and downloading software to the field hardware.

g. Creating historical trends, collecting trend data and generating trend graphs.

h. Enabling and assigning alarms and messages to reporting actions/groups.

i. Report generation and ‘third party software.

j. Backing up software and data files.

3. Project Engineering Manual shall Contain as a Minimum:

a. System architecture overview.

b. Hardware cut-sheets and product descriptions.

c. Deliver four sets of as-built Drawings. All Drawings shall be reviewed after the final system checkout and updated to provide as-built Drawings. The system will not be considered complete until the as-built Drawings have received their final approval.

d. Installation, mounting and connection details for all field hardware and accessories.

e. Commissioning, setup and backup procedures for all control modules/accessories, BAS server software, and database.

f. Listing of basic terminology, alarms/messages, error messages and frequently used commands or shortcuts.

D. Acceptance Test:

1. Acceptance Testing: Upon completion of the installation, startup the system and perform all necessary calibration, testing, and debugging operations. Perform the acceptance test in the presence of the Contracting Officer

2. Notice of Completion: When the system performance is deemed satisfactory, the system parts will be accepted for beneficial use and placed under warranty. At this time, the Contracting Officer shall issue a “notice of completion” and the warranty period shall start.

E. System Training:

1. System Use Instructions: Controls Contractor shall provide full Computer

Based Training (CBT) in addition to 8 hours of training of designated personnel in the operation, maintenance, and programming of the system.

INTEGRATED AUTOMATION 25 00 00 - 6

F. Guarantee:

1. Material: The Control System shall be free from defects in material, workmanship and programming under normal use and service. If within 24 months from the date of substantial completion any of the equipment herein described is defective in operation, workmanship or materials, it will be replaced, repaired or adjusted at the option of the BAS Contractor free of charge.

2. Installation: The Control System shall be free from defects in installation workmanship for a period of 24 months from final acceptance. The BAS Contractor shall, free of charge, correct any defects in workmanship within 48 hours for any systems that are critical and within 1 week (5 working days) of notification in writing or verbally by the Contracting Officer.

PART 2 PRODUCTS

2.01 BAS SYSTEM ACCEPTABLE MANUFACTURERS

A. Automated Logic

B. Alerton

C. Delta

2.02 BAS SYSTEM OVERVIEW

A. The BAS contractor shall provide system software based on a server/thin client architecture, designed around the open standards of web technology.

B. The BAS server shall communicate using ASHRAE’s BACnet/IP protocol, and in addition, offer concurrent support over the same data-link of the following protocols: MODBUS and SNMP.

C. The intent of the thin-client architecture is to provide the operator(s) complete access to the BAS system via a web browser. The thin-client web browser Graphical User Interface (GUI) shall be browser and operating system agnostic, meaning it will support Microsoft Internet Explorer browser (6.0 or later versions), and Windows as well as non-Window operating systems. No special software, (active-x components or fat java clients) shall be required to be installed on the PC’s/Laptop used to access the BAS via a web browser.

D. The existing server software supports at least the following server platforms (Windows, Sun Solaris, and Linux). The BAS server software shall be developed and tested by the manufacturer of the system standalone controllers and network controllers/routers. Third party manufactured and developed BAS software is not acceptable. The web browser GUI shall provide a completely interactive user interface and must offer the following features as a minimum:

1. Trending.

INTEGRATED AUTOMATION 25 00 00 - 7

2. Scheduling.

3. Downloading Memory to field devices.

4. Real time ’live’ Graphic Programs.

5. Tree Navigation.

6. Parameter change of properties.

7. Set point Adjustments.

8. Alarm/Event information.

9. Configuration of operators.

10. Execution of global commands.

E. Software Components: All software components of the BAS system software shall be installed and completed in accordance with the Specification. BAS system components shall include:

1. Server Software, Database, and Web Browser Graphical User Interface.

2. System Configuration Utilities for future modifications to the system.

3. Graphical Programming.

4. Direct digital control software.

5. Application Software.

F. BAS Server Database: The BAS server software shall utilize a Java Data Base Connectivity (JDBC) compatible database such as: MS Access, MS SQL 7.0, Oracle 8i or IBM DB2. BAS systems written to Proprietary databases are NOT acceptable.

G. Communication Protocol(s): The native protocol for the BAS server software shall be BACnet as defined by ASHRAE standard SPC135.

H. Cross Platform Capability: The BAS system software (client and server) shall be operating system and hardware agnostic, being able to run on Windows 98, Windows 2000, Windows NT, Sun Microsystems Solaris, and Red Hat Linux.

I. Thin Client – Web Browser Based:

1. Web Browser’s for PC’s: Only a browser (Internet Explorer 6.0 or higher) will be required as the GUI, and a valid connection to the server network.

No installation of any custom software shall be required on the operator’s GUI workstation/client. Connection shall be over an intranet or the Internet.

2. Secure Sockets Layer: Communication between the Web Browser GUI and BAS server shall offer encryption using 128-bit encryption technology within Secure Sockets Layer (SSL) as a minimum level of security.

Communication protocol shall be Hyper-Text Transfer Protocol (HTTP).

2.03 WEB BROWSER GRAPHICAL USER INTERFACE

A. Web Browser Navigation: The Thin Client web browser GUI shall provide a comprehensive user interface. Using a collection of web pages, it shall be constructed to “feel” like a single application, and provide a complete and

INTEGRATED AUTOMATION 25 00 00 - 8

intuitive mouse/menu driven operator interface. It shall be possible to navigate through the system using a web browser.

B. Login: On launching the web browser and selecting the appropriate domain name or IP address, the operator shall be presented with a login page that will require a login name and password. Navigation in the system shall be dependent on the operator’s role privileges, and geographic area of responsibility (see below).

C. Color Graphics: The Web Browser GUI shall make extensive use of color in the graphic pane to communicate information related to set points and comfort. Animated gif’s, active set point graphic controls and valid web content (like local weather forecast) shall be used to enhance usability:

1. Display Size: The GUI workstation software shall graphically display in

1024 by 768 pixels 24 bit True Color.

2. General Graphic: General area maps shall show locations of controlled buildings in relation to local landmarks.

3. Color Floor Plans: Floor plan graphics shall show heating and cooling zones throughout the buildings in a range of colors, which provide a visual display of temperature relative to their respective set points (see section below). The colors shall be updated dynamically as a zone's actual comfort condition changes. Locations of space sensors shall also be shown for each zone. The intent of the specification is to enable the operator to readily assess ‘problems’ at a glance.

4. Mechanical Components: Mechanical system graphics shall show the type of mechanical system components serving any zone through the use of a pictorial representation of components. Selected I/O points being controlled or monitored for each piece of equipment shall be displayed with the appropriate engineering units. Animation shall be used for rotation or moving mechanical components to enhance usability.

5. Minimum System Color Graphics: Color graphics shall be selected and displayed via a web browser for the following:

a. Each piece of equipment monitored or controlled including each terminal unit.

b. Each building.

c. Each floor and zone controlled.

D. Zone Set Point Adjustments: Color floor plans displayed via a web browser shall utilize a contiguous band of colors, each corresponding to actual zone temperatures relative to the desired heating and cooling set points. The ideal temperature shall be shown as a green color band. Temperatures slightly warmer than ideal shall be shown in yellow, and even warmer temperature band shall be shown in orange. Temperatures slightly cooler than ideal shall be light blue, and even cooler temperatures shall be shown as dark blue. All alarm colors shall be in red.

E. Hierarchical Schedules:

INTEGRATED AUTOMATION 25 00 00 - 9

1. BACnet Schedules: Schedules shall comply with the BACnet standard, (Schedule Object, Calendar Object, Weekly Schedule property and Exception Schedule property) and shall allow events to be scheduled based on:

a. Types of schedule shall be Normal, Holiday, or Override.

b. A specific date.

c. A range of dates.

d. Any combination of Month of Year (1 to 12, any), Week of Month (1 to

5, last, any), Day of Week (M to Sun, Any).

e. Wildcard (example, allow combinations like second Tuesday of every month).

F. Events (and Alarms):

1. Event Categories: The operator shall be able to create, edit or delete vent categories such as HVAC, Maintenance, Fire, or Generator. An icon shall be associated with each Event category, enabling the operator o easily sort through multiple events displayed using a built-in filter.

2. BACnet Event Templates: BACnet Event template shall define different types of alarms and their associated properties. As a minimum, properties shall include a reference name, verbose description, severity f event, acknowledgement requirements, high/low limit and out of range information.

3. Event Time/Date Stamp: All events shall be generated at the DDC control module level and comprise the Time/Date Stamp using the standalone control module time and date.

4. Event Configuration: Operators shall be able to define the type of events generated per BACnet object. A ‘network’ view of the BAS shall expose all BACnet objects and their respective event configuration. Configuration shall include assignment of event, alarm, type of acknowledgement and notification for return to normal or fault status.

5. Event Reporting Actions: Event Reporting Actions specified shall be automatically launched (under certain conditions) after an event is received by the BAS server software. Operators shall be able to fully define these Reporting Actions using the web browser GUI. Reporting

G. Actions shall be as follows:

1. Print: Alarm/Event information shall be printed to the BAS server’s PC or a networked printer.

2. Email: Email shall be sent via any POP3-compatible e-mail server (most

Internet Service Providers use POP3). Email messages may be copied to several email accounts.

3. Email reporting action shall also be used to support alphanumeric paging services, where email servers support pagers.

4. File Write: The ASCII File write reporting action shall enable the operator to append operator defined alarm information to any alarm through a text file. The alarm information that is written to the file shall be completely definable by the operator. The operator may enter text or attach other data

INTEGRATED AUTOMATION 25 00 00 - 10

point information (such as AHU discharge temperature and fan condition upon a high room temperature alarm).

5. Write Property: The write property reporting action updates a property value in a hardware module.

6. SNMP: The Simple Network Management Protocol (SNMP) reporting action sends an SNMP trap to a network in response to receiving an event.

7. Run External Program: The Run External Program reporting action launches specified program in response to an event.

H. Event Simulator: The web browser GUI user shall provide an Event Simulator to test assigned Reporting Actions. The operator shall have the option of using current time or scheduling a specific time to generate the Event. Utilizing the Navigation Tree and drop-down menus in the Graphic Pane, the operator shall be able to select the Event Type, Status, Notification, Priority, Message, and whether acknowledgement is required.

I. Trends: Trends shall conform to the BACnet Trend Log Object specification.

The system shall be able to trend and display graphically all analog, digital or calculated points simultaneously. A trend log’s properties shall be editable using the web browser GUI. Sample intervals shall be as small as second.

J. Security Access: Systems that require Security access from the web browser GUI to BAS server are to require a Login Name and Password. Access to different areas of the BAS system shall be defined in terms of Roles, Privileges, and geographic area of responsibility as specified:

1. Roles: Roles shall reflect the actual roles of different types of operators.

Each role shall comprise a set of ‘easily understood English language’ privileges. Roles shall be defined in terms of View, Edit, and Function Privileges. Systems that use cryptic Boolean numbers to define system access are not acceptable.

2. Geographic Assignment of Roles: Roles shall be geographically assigned using a similar expandable/collapsible navigation tree. For example, it shall be possible to assign two HVAC Technicians with similar competencies (and the same operator defined HVAC Role) to different areas of the system.

2.04 GRAPHICAL PROGRAMMING

A. The system software shall include a Graphic Programming Language (GPL) for all DDC control algorithms resident in standalone control modules. Any system that does not use a drag and drop method of graphical icon programming as described herein is NOT acceptable.

B. GPL Capabilities: The following is a minimum definition of the capabilities of the Graphic Programming software:

INTEGRATED AUTOMATION 25 00 00 - 11

1. Function Block (FB): Shall be a collection of points, microblocks and wires which have been connected together for the specific purpose of controlling a piece of HVAC equipment or a single mechanical system.

2. Logical I/O: Input/Output points shall interface with the control modules in order to read various signals and/or values or to transmit signal or values to controlled devices.

3. BACnet Points: Shall be points that comply with the BACnet structure as defined in the BIBB’s Addendum B1/B2, and the BACnet standard.

4. Microblocks: Shall be software devices that are represented graphically and may be connected together to perform a specified sequence. A library of microblocks shall be submitted with the control contractors bid.

5. Wires: Shall be Graphical elements used to form logical connections between microblocks and between logical I/O. Different wires types shall be used depending on whether the signal they conduct is analog or digital.

6. Labels: Labels shall be similar to wires in that they are used to form logical connections between two points. Labels shall form a connection by reference instead of a visual connection, i.e. two points labeled 'A' on a Drawing are logically connected even though there is no wire between them.

7. Parameter: A parameter shall be a value that may be tied to the input of a microblock.

8. Properties: Dialog boxes shall appear after a microblock has been inserted which has editable parameters associated with it. Default parameter dialog boxes shall contain various editable and noneditable fields and shall contain 'push buttons’ for the purpose of selecting default parameter settings.

9. Icon: An icon shall be graphic representation of a software program. Each graphic microblock has an icon associated with it that graphically describes it function.

10. Menu-Bar Icon: Shall be an icon that is displayed on the menu bar on the GPL screen, which represents its associated graphic microblock.

11. Live Graphical Programs: The Graphic Programming software must support a ‘live’ mode, where all input/output data, calculated data, and set points shall be displayed in a ‘live’ real-time mode.

12. For each piece of HVAC equipment, the entire graphic program shall be displayed through the Web Browser GUI. The operator must have the ability to scroll through the entire ‘live’ graphic program as necessary.

Piecemeal graphic programs that only show one part of HVAC equipment program at any one time are NOT acceptable. For example, when viewing an AHU live graphic program, the operator shall see the entire AHU graphic program, not just the Heating Coil control.

2.05 NETWORK ROUTERS AND BRIDGES

A. The controller network shall use BACnet as its native communication protocol.

Network bridges and routers must be of a modular design to ensure reliability and system performance.

INTEGRATED AUTOMATION 25 00 00 - 12

B. BACnet Router: The central system shall use the building Local Area Network (LAN) for communication. The communication between the central server and the controllers shall be BACnet/IP. A router shall be provided, as required, to bridge BACnet/IP and the data link used between the controllers (BACnet ARCNET and BACnet MS/TP). Proprietary networks and proprietary protocols are not acceptable.

1. BACnet BIBBS: BACnet Routers must use BACnet as the native communication protocol.

2. Firmware Updates: The BACnet Router utilize FLASH memory to flow firmware updates to be performed remotely.

2.06 STANDALONE CONTROLLERS

A. General Purpose Multiple Application Controllers:

1. BACnet BIBBS: General Purpose Multiple Application controllers must use

BACnet as the native communication protocol between controllers.

2. Communication Speed: Controllers shall communicate at a minimum of

156 Kbps using ARCNET implemented over EIA-485 using an unshielded twisted pair at the Data Link Layer.

3. General Specification: Each General Purpose Multiple Application controller must be capable of standalone direct digital operation utilizing its own 32 bit processor, nonvolatile flash memory, input/output, 12 bit A to D conversion, hardware clock/calendar and voltage transient and lightning protection devices. A separate coprocessor shall be used for communications to the controller network. All nonvolatile flash memory shall have a battery backup of at least 5 years. Firmware revisions to the module shall be made from the BAS server or remotely over the Intranet or Internet. Controllers that require component changes to implement firmware revisions are not acceptable.

4. Point Expansion: The General Purpose Multiple Application Controllers shall be expandable to the specified I/O point requirements. Each controller shall accommodate multiple I/O Expander Modules via a designated expansion I/O bus port. These expander modules shall expand the total point capacity of each controller up to 192 points where specified.

The controller, in conjunction with the expansion modules, shall act as one standalone controller.

5. Point Programming: All point data, algorithms and application software within a controller shall be custom programmable from the operator workstation.

6. Program Execution: Each General Purpose Multiple Application Controller shall execute application programs, calculations, and commands via a 32-bit microcomputer resident in the controller. All operating parameters for application programs residing in each controller shall be stored in read/writable nonvolatile flash memory within the controller and will be able to upload/download to/from the BAS Server.

INTEGRATED AUTOMATION 25 00 00 - 13

7. Self-Test Diagnostics: Each controller shall include self-test diagnostics, enabling the controller to report malfunctions to the router and BAS Server.

8. PID Loops: Each General Purpose Multiple Application Controller shall contain both software and firmware to perform full DDC Proportional, Integral, Derivative (PID) control loops and programs.

9. Input-Output Processing: Digital Outputs shall be relays, 24 Volts ac or dc maximum, 3 amp maximum current. Each configured as normally open or normally closed using jumpers and either dry contact or bussed. Each output shall have a manual Hand-Off-Auto switch to allow for override and an LED to indicate the operating mode of the output. Triac outputs are unacceptable.

a. Universal Inputs shall be Thermistor (BAPI Curve II) 10K Ohm at 77 degrees F (25 degrees C), 0 to 5V dc, 10K Ohm maximum source impedance, 0 to 20mA – 24V dc loop power, 250 Ohm input impedance, dry contact - 0.5mA maximum current.

b. Analog Output shall be electronic, voltage mode 0 to 10V dc or current mode 4 to 20mA.

B. General Purpose Single Application Controllers:

1. BACnet BIBBS: The General Purpose Single Application Controllers must use BACnet as the native communication protocol between controllers.

2. Communication Speed: Controllers shall communicate at a minimum of

156 Kbps using ARCNET implemented over EIA-485 using an unshielded twisted pair at the Data Link Layer.

3. General Specification: General Purpose Single Application controllers must be capable of stand-alone DDC operation utilizing its own 32-bit processor, nonvolatile flash memory, input/output, 8 bit A to D conversion, hardware clock/calendar and voltage transient protection devices. A separate coprocessor shall be used for communications to the controller network. All RAM memory shall have a battery backup of at least 5 years.

Firmware revisions to the module shall be made from the BAS server, or remote locations over the Internet. Controllers that require component changes to implement Firmware revisions are not be acceptable.

4. Point Programming: All point data, algorithms, and application software within the controllers shall be custom programmable from the Operator Workstation.

5. Program Execution: Each General Purpose Single Application Controller shall execute application programs, calculations, and commands via a 32-bit microcomputer resident in the controller. All operating parameters for the application program residing in each controller shall be stored in read/writable nonvolatile flash memory within the controller and will be able to upload/download to/from the Operator Workstation.

6. Self-Test Diagnostics: Each controller shall include self-test diagnostics, enabling the controller to report malfunctions to the router and BAS Server input.

INTEGRATED AUTOMATION 25 00 00 - 14

7. PID Loops: Each General Purpose Single Application Controller shall contain both software and firmware to perform full DDC PID control loops.

8. Rooftop Mounting: The General Purpose Single Application Controllers shall be capable of being mounted directly in or on rooftop AHU equipment.

9. Operating Temperature: The General Purpose Single Application Controllers shall be capable of proper operation in an ambient temperature environment of minus 20 degrees F to plus 150 degrees F (-

28.9 degrees to 65.6 degrees C).

10. Input-Output Processing:

a. Digital outputs shall be relays, 24 Volts ac or dc maximum, 3 amp maximum current. Each output shall have a manual Hand-Off- Auto switch to allow for override and an LED to indicate the operating mode of the output. Triac outputs are unacceptable.

b. Universal inputs shall be Thermistor (BAPI Curve II) 10K Ohm at 77 degrees F (25 degrees C), 0 to 5V dc - 10K Ohm maximum source impedance, 0 to 20mA - 24V dc loop power, 250 Ohm input impedance, Dry Contact - 0.5mA maximum current.

c. Analog electronic outputs shall be voltage mode 0 to 10V dc or current mode 4 to 20mA.

d. Enhanced zone sensor input shall provide one thermistor input, one local set point adjustment, one timed local override switch, and an occupancy LED indicator.

C. Unitary Controller Network

1. Unitary Controllers:

a. BACnet BIBBS: The Unitary Controllers shall use BACnet as the native communications protocol between controllers on the unitary controller network.

b. Communication Speed: The communication between unitary controllers shall be 38.4 Kbps minimum over EIA-485 using an MS/TP architecture.

c. Sensor Support: Each Unitary Controller shall be able to support various types of zone temperature sensors, such as; temperature sensor only, temperature sensor with built-in local override switch and temperature sensor with built-in set point adjustment switch.

d. Airflow Transducer: In order to provide reliable Pressure Independent VAV operation, Unitary Controllers for pressure independent VAV applications shall have a precision built-in airflow transducer for accurate air flow measurement.

e. Integral Actuator: Each Unitary Controller for VAV applications shall have an integral direct coupled electronic actuator with the following features:

1) The actuator shall provide on-off/floating point control with a minimum of 35 inch-pound of torque.

2) The assembly shall mount directly to the damper operating shaft with a universal V-Bolt clamp assembly.

INTEGRATED AUTOMATION 25 00 00 - 15

3) The actuator shall not require any limit switches, and shall be electronically protected against overload.

4) The actuator shall automatically stop when reaching the damper or actuator end position.

5) The gears shall be capable of being manually disengaged with a button on the assembly cover.

6) A visual pointer for the position of the actuator.

7) The assembly shall have an anti-rotational strap supplied with the assembly that will prevent lateral movement.

8) Five-year warranty from the manufacturer.

f. Visual Status: Each Unitary Controller and Unitary Controller Interface shall have LED indication for visual status of communication, power, and all outputs.

g. Standalone Algorithm: In the event of a loss of communication, each Unitary Controller shall control from a standalone algorithm, which maintains the assigned space temperature until communication with the Unitary Control Module Interface is restored.

h. Input/Output Processing:

1) Digital outputs shall be relays, 24 Volts ac or dc maximum, having a 3 Amp maximum current. Each relay shall be configured as normally open or normally closed, and either dry contact or bussed. Triac outputs are not acceptable.

2) Universal inputs shall be Thermistor Precon Type II, dry contacts or 0 to 5V dc with 0 to 10K Ohm input impedance.

3) Enhanced Zone Sensor Input. The input shall provide one thermistor input, one local set point adjustment, one timed local override switch, and an occupancy LED indicator.

4) Analog output electronic, voltage mode 0 to 10V dc or current mode 4 to 20mA.

2. Unitary Controller Router: A router shall be provided to bridge between the unitary controller network and the main controller network, as required.

a. BACnet BIBBS: The Unitary Controllers Routers shall use BACnet as the native communications protocol between controllers on the unitary controller network.

2.07 LIGHTING CONTROL PANELS

A. The BAS contractor shall provide lighting control panels that reside directly on the building automation system communication network.

B. Lighting control panels shall provide:

1. Capacities of 32 relays.

2. One 2 pole eclectically held lighting contactor with 30 Amp contact rating.

3. Switch inputs for local override and occupancy sensor control for the number of overrides and sensors indicated on the drawings.

4. Occupant flash warning to notify the occupants that the lights will be turned off, programmable from 1 to 60 minutes.

INTEGRATED AUTOMATION 25 00 00 - 16

5. Switch input timers that automatically turn lights off, programmable from 1 minute to 18 hours.

6. Nonvolatile memory shall be provided so data is not lost during power outages or brown outs.

C. Relays shall provide the following features and operation:

1. Mechanically latching

2. Switch up to 277V, 20 Amp lighting loads

3. Provide up to 300,000 operations at full load

4. Provide a built-in manual override lever:

a. Manual override lever shall indicate status of relay

b. Manual override lever shall not require power to operate

5. Individually replaceable.

6. Relay terminal shall be able to accept one #14-8AWG solid or stranded wire or two #10AWG solid or stranded wires in each hole.

D. Lighting Contactor shall provide the following features:

1. 2 pole, 30 Amp contact ratings, continuous duty, electrically held

2. Flush dead back design with arc shields and barriers to prevent pole-to-pole flashover.

E. The lighting control system shall provide the capability for digital lighting override switches:

1. The switches shall reside on a 4-wire digital device network.

a. The switch shall use two wires for communication

b. The switch shall use two wires for power

2. Each digital switch shall provide a push button switch with an embedded dual color LED to indicate the status of the lighting group controlled by the digital switch.

a. Red will indicate ON.

b. Green will indicate OFF.

3. The digital switch shall have a mechanical life of a minimum of 1,000,000 operations.

4. A digital switch shall be able to control any one of lighting groups in the lighting control panel.

5. The status of the lighting group controlled by the digital switch shall be automatically displayed on the building automation system user interface.

F. The lighting control system shall provide the capability for standard lighting override switches:

1. Provide momentary on, momentary on/off switch for override switches as indicated on the drawings.

2. Switch shall be low voltage

3. Switches shall be connected to the lighting control panel as indicated on the approved drawings.

INTEGRATED AUTOMATION 25 00 00 - 17

2.08 LOW VOLTAGE SWITCHES

A. The lighting control system shall provide the capability for digital lighting override switches:

1. The switches shall reside on a 4-wire digital device network.

a. The switch shall use two wires for communication

b. The switch shall use two wires for power

2. Each digital switch shall provide a push button switch with an embedded dual color LED to indicate the status of the lighting group controlled by the digital switch.

a. Red will indicate ON.

b. Green will indicate OFF.

3. The digital switch shall have a mechanical life of a minimum of 1,000,000 operations.

4. A digital switch shall be able to control any one of lighting groups in the lighting control panel.

5. The status of the lighting group controlled by the digital switch shall be automatically displayed on the building automation system user interface.

B. The lighting control system shall provide the capability for standard lighting override switches:

1. Provide momentary on, momentary on/off switch for override switches as indicated on the drawings.

2. Switch shall be low voltage

3. Switches shall be connected to the lighting control panel as indicated on the approved drawings.

2.09 BAS SYSTEM SOFTWARE APPLICATIONS

A. The following applications software shall be provided for the purpose of optimizing energy consumption while maintaining occupant comfort:

1. Time of Day Scheduling (TOD) The system shall be capable of the following scheduling features:

a. Schedule by Type: Scheduling by building, area, zone, groups of zones, individually controlled equipment and groups of individually controlled equipment. Each schedule shall provide beginning and ending dates and times (hours: minutes). A weekly repeating schedule, i.e. between 8:00 a.m. and 5:00 p.m., Monday through Friday shall constitute one schedule, not five.

b. Schedule in Advance: Dated schedules shall be entered up to 9 years in advance.

c. Self-Deleting: Schedules shall be self-deleting when effective dates have passed.

d. Leap Year: Leap years shall be adjusted automatically without operator intervention.

2. Optimum Start/Stop (OSS)/Optimum Enable/Disable (OED): This application provides software to start and stop equipment on a sliding

INTEGRATED AUTOMATION 25 00 00 - 18

Schedule based on the individual zone temperature and the heating/cooling capacity in degrees F/hour of the equipment serving that zone. The heating/cooling capacity value shall be operator adjustable.

Temperature compensated peak demand limiting shall remain in effect during morning startup to avoid setting a demand peak.

3. Source Temperature Optimization (STO): The system shall automatically perform source optimization for all air handling units, chillers and boilers in response to the needs of other downstream pieces of equipment, by increasing or decreasing supply temperature set points, i.e. chilled water, discharge air, etc.. In addition to optimization, the STO capability shall also provide for starting and stopping primary mechanical equipment based on zone occupancy and/or zone load conditions.

a. Set point Reset: The STO program will allow set points for various equipment in the heating/cooling chain to be reset between an operator defined maximum and a minimum set point based on the actual requirements of the building zones. The actual set point shall be calculated based on the number of heating or cooling requests which are currently being received from the equipment or zones served. Once every update period, the STO program surveys the network to see if any piece of equipment requires any additional heating or cooling from its source. As an example, a VAV air handler is the source of cold air for a number of VAV boxes.

4. Demand Limiting (DL) - Temperature Compensated: The DL application shall be programmable for a minimum of six separate time of day KW demand billing rate periods. The system shall be capable of measuring electrical usage from multiple meters serving one building and each piece of equipment being controlled on the LAN shall be programmable to respond to the peak demand information from its respective meter.

a. Sliding Window: The demand control function shall utilize a sliding window method with the operator being able to establish the kilowatt threshold for a minimum of three adjustable demand levels. The sliding window interval shall be operator selectable in increments of 1 minute, up to 60 minutes. Systems that incorporate rotating shed tables will not be acceptable.

1) Set points for Defined Demand Level: The operator shall have the capability to set the individual equipment temperature set points for each operator defined demand level. Equipment shall not be shed if these reset set points are not satisfied; rather the set point shall be revised for the different established demand levels. The system shall have failed meter protection, such that when a KW pulse is not received from the utility within an operator adjustable time period, an alarm will be generated. The system software will automatically default to a predetermined fail-safe shed level.

2) Information Archiving: The system shall have the ability to archive demand and usage information for use at a later time. system

INTEGRATED AUTOMATION 25 00 00 - 19

shall permit the operator access to this information on a current day, month to date and a year to date basis.

B. Day/Night Setback (DNS): The system shall allow the space temperature to drift down (up) within a preset (adjustable) unoccupied temperature range. The heating (cooling) shall be activated upon reaching either end of the DNS range and shall remain activated until the space temperature returns to the DNS range.

1. Outside and Exhaust Air: The system shall be capable of closing all outside air and exhaust air dampers during the unoccupied period, except for 100 percent outside air units.

2. Unoccupied Space Temperature: Unoccupied space temperature shall be monitored by the DDC temperature sensors located in the individual zones being controlled or within a representative room.

3. Parameter Changes: Operator shall be able to define, modify or delete the following parameters.

a. DNS set point temperature(s).

b. Temperature band for night heating operation.

c. Period when the DNS is to be activated.

C. Timed Local Override (TLO): The system shall have TLO input points that permit the occupants to request an override of equipment that has been scheduled OFF. The system shall turn the equipment ON upon receiving a request from the local input device. Local input devices shall be push button (momentary contact), wind-up timer, or ON/OFF switches as detailed in the I/O summary.

1. Equipment On Time: If a push button is used the system operator shall be able to define the duration of equipment ON time per input pulse and the total maximum ON time permitted. The input point will cancel override time already entered. If a wind-up timer is used the equipment will stay in override mode until the timer expires. Year to date, month to date and current day override history shall be maintained for each TLO input point.

History data shall be accessible by the operator at any time and shall be capable of being automatically stored on hard disk and/or printed on a daily basis.

D. Space Temperature Control (STC): There shall be two space temperature set points, one for cooling and one for heating, separated by a dead band. Only one of the two set points shall be operative at any time. The cooling set point is operative if the actual space temperature has more recently been equal to or greater than the cooling set point. The heating set point is operative if the actual space temperature has more recently been equal to or less than the heating set point. There are two modes of operation for the set points, one for the occupied mode (example: heating = 72 degrees F or 22 degrees C, cooling = 76 degrees F or 24.4 degrees C) and one for the unoccupied mode (example: heating = 55 degrees F or 12.7 degrees C, cooling = 90 degrees F or 32 degrees C).

INTEGRATED AUTOMATION 25 00 00 - 20

1. Schedule: The occupied/unoccupied modes may be scheduled by time, date, or day of week.

2. Color Code: One of seven colors shall be generated to represent the comfort conditions in the space, and shall be displayed graphically at the operator station.

a. If the actual space temperature is in the dead band between the heating set point and the cooling set point, the color displayed shall be green for the occupied mode, representing ideal comfort conditions. If in the unoccupied mode, the color displayed shall be gray representing 'after-hours' conditions.

b. If the space temperature rises above the cooling set point, the color shall change to yellow. Upon further rise beyond the cooling set point plus an offset, the color shall change to orange. Upon further rise beyond the cooling set point plus the yellow band offset, plus the orange band offset, the color shall change to red indicating unacceptable high temperature conditions. At this point an alarm shall be generated to notify the operator.

c. When space temperature falls below the heating set point, the color shall change to light blue. Upon further temperature decrease below the heating set point minus an offset, the color shall change to dark blue. Upon further space temperature decrease below the heating set point minus the light blue band offset minus the dark blue band offset the color shall change to red indicating unacceptable low temperature conditions. At this point an alarm shall be generated to notify the operator.

3. Operator Definable: All set points and offsets shall be operator definable.

When in the occupied mode, start-up mode, or when heating or cooling during the night setback unoccupied mode, a request shall be sent over the network to other equipment in the HVAC chain, such as to an AHU fan that serves the space, to run for ventilation. The operator shall be able to disable this request function if desired.

4. Additional Cooling: When comfort conditions are warmer than ideal, indicated by the colors yellow, orange, and high temperature red, a request for additional cooling shall be sent over the network to other cooling equipment in the HVAC chain, such as a chiller. This information is to be used for optimization of equipment in the HVAC chain. The operator shall be able to disable this function if desired.

5. Additional Heating: When comfort conditions are cooler than ideal;

indicated by the colors light blue, dark blue, and low temperature red; a request for additional heating shall be sent over the network to other heating equipment in the HVAC chain, such as a boiler. This information is to be used for optimization of equipment in the HVAC chain.