Exhibit 5 - Specifications

Section 23 09 23 Instrumentation and Control for HVAC

ODOT BLDG A MS Control System Specifications

Contents

23 09 23 Direct-Digital Control System for HVAC

PART 1: GENERAL

1.0 Section Includes

1.1 Products Furnished but Not Installed under This Section

1.2 Products Installed but Not Furnished under This Section

1.3 Products Not Furnished or Installed under but Integrated with the Work of This Section

1.4 Related Sections

1.5 Description

1.6 Approved Control system Manufacturers

1.7 Quality Assurance

1.8 Codes and Standards

1.9 System Performance

1.10 Submittals

1.11 Warranty

1.12 Ownership of Proprietary Material

1.13 Definitions

ODOT BLDG A Controls

MS

DIRECT DIGITAL CONTROL SYSTEM

Section: 23 09 23 Date: 07/13/2026

23 09 23-10

1.1 Products Furnished but Not Installed under This Section

A. Section 23 09 13.23 - Sensors and Transmitters

1. Airflow stations

2. Flow meters

3. Hydronic temp sensor wells and sockets B. Section 23 09 13.33 - Control Valves

1. Control valves C. Section 23 70 00 - Central HVAC Equipment

1. AHU, heating, and ventilating unit controls

1.2 Products Installed but Not Furnished under This Section

A. None

1.3 Products Not Furnished or Installed under but Integrated with the Work of This Section A. Section - General

1. Coordination Meeting B. Section 26 29 00 - Low-Voltage Controllers

1. Variable frequency drives C. Section 23 36 00 - Air Terminal Units

1. VAV boxes D. Section 23 52 00 - Heating Boilers

1. Boiler controls E. Section 23 60 00 - Central Cooling Equipment

1. Chiller controls F. Section 23 70 00 - Central HVAC Equipment

1. Packaged AHU or evaporative cooler controls G. Section 23 80 00 - Decentralized HVAC Equipment

1. Unit ventilators, unit heaters, fan coils, etc.

1.4 Related Sections

A. The General Conditions of the Contract, Supplementary Conditions, and General Requirements are part of this specification and shall be used in conjunction with this section as part of the contract documents.

B. The following sections constitute related work:

1. Section 23 05 00 - Common Work Results for HVAC

2. Section 23 20 00 - HVAC Piping and Pumps

3. Section 23 30 00 - HVAC Air Distribution

4. Section 23 40 00 - HVAC Air Cleaning Devices

5. Section 23 50 00 - Central Heating Equipment

6. Section 23 60 00 - Central Cooling Equipment

7. Section 23 70 00 - Central HVAC Equipment

8. Section 23 80 00 - Decentralized HVAC Equipment

1.5 Description

A. General: The control system shall consist of a high-speed, peer-to-peer network of DDC controllers, a control system server, and a web-based operator interface.

B. System software shall be based on a server/thin client architecture, designed around the open standards of web technology. The control system server shall be accessed using a Web browser over the control system network, the owner's local area network, and (at the owner's discretion) over the Internet. The intent of the thin-client architecture is to provide operators complete access to the control system via a Web browser. No special software other than a web browser shall be required to access graphics, point displays, and trends, configure trends, configure points and controllers, or to download programming into the controllers.

C. System shall use the BACnet protocol for communication to the operator workstation or web server and for communication between control modules. I/O points, schedules, setpoints, trends and alarms specified in 23 09 93 – “Sequence of Operations for HVAC Controls” shall be BACnet objects.

1.6 Approved Control system Manufacturers

A. Use control system hardware and software that meet the requirements of this specification.

1.7 Quality Assurance

A. Installer and Manufacturer Qualifications

1. Installer shall have an established working relationship with Control System Manufacturer.

2. Installer shall have successfully completed Control System Manufacturer’s control system training. Upon request, Installer shall present record of completed training including course outlines.

1.8 Codes and Standards

A. Work, materials, and equipment shall comply with the most restrictive of local, state, and federal authorities' codes and ordinances or these plans and specifications. As a minimum, the installation shall comply with the current editions in effect 30 days prior to the receipt of bids of the following codes:

1. National Electric Code (NEC)

2. International Building Code (IBC)

3. International Mechanical Code (IMC)

4. ANSI/ASHRAE Standard 135, BACnet - A Data Communication Protocol for Building Automation and Control Systems

1.9 System Performance

A. Performance Standards. System shall conform to the following minimum standards over network connections. Systems shall be tested using manufacturer’s recommended hardware and software for operator workstation (server and browser for web-based systems).

1. Graphic Display. A graphic with 20 dynamic points shall display with current data within 10 sec.

2. Graphic Refresh. A graphic with 20 dynamic points shall update with current data within 8 sec.and shall automatically refresh every 15 sec.

3. Configuration and Tuning Screens. Screens used for configuring, calibrating, or tuning points, PID loops, and similar control logic shall automatically refresh within 6 sec.

4. Object Command. Devices shall react to command of a binary object within 2 sec. Devices shall begin reacting to command of an analog object within 2 sec.

5. Alarm Response Time. An object that goes into alarm shall be annunciated at the workstation within 45 sec.

6. Program Execution Frequency. Custom and standard applications shall be capable of running as often as once every 5 sec. Select execution times consistent with the mechanical process under control.

7. Performance. Programmable controllers shall be able to completely execute DDC PID control loops at a frequency adjustable down to once per sec. Select execution times consistent with the mechanical process under control.

8. Multiple Alarm Annunciation. Each workstation on the network shall receive alarms within 5 sec of other workstations.

9. Reporting Accuracy. System shall report values with minimum end-to-end accuracy listed in Table 1.

10. Control Stability and Accuracy. Control loops shall maintain measured variable at setpoint within tolerances listed in Table 2.

Table-1 Reporting Accuracy

Note 1: Accuracy applies to 10%–100% of scale Note 2: For both absolute and differential pressure Note 3: Not including utility-supplied meters

Table 2 Control Stability and Accuracy

±3 Pa (±0.01 in. w.g.)

0–1.5 kPa (0–6 in. w.g.)

-25 to 25 Pa (-0.1 to 0.1 in. w.g.)

±250 Pa (±1.0 in. w.g.)

MPa (1–150 psi) 0–12.5 kPa (0–50 in. w.g.) differential

1.10 Submittals

A. Product Data and Shop Drawings: Meet requirements of Section 01 30 00 on Shop Drawings, Product Data, and Samples. In addition, the contractor shall provide shop drawings or other submittals on hardware, software, and equipment to be installed or provided. No work may begin on any segment of this project until submittals have been approved for conformity with design intent. Provide drawings as AutoCAD 2006 (or newer) compatible files on magnetic or optical disk (file format: .DWG, .DXF, .VSD, or comparable) and three 11” x 17” prints of each drawing. When manufacturer’s cutsheets apply to a product series rather than a specific product, the data specifically applicable to the project shall be highlighted or clearly indicated by other means. Each submitted piece of literature and drawing shall clearly reference the specification and/or drawing that the submittal is to cover. General catalogs shall not be accepted as cutsheets to fulfill submittal requirements. Select and show submittal quantities appropriate to scope of work. Submittal approval does not relieve Contractor of responsibility to supply sufficient quantities to complete work.

Submittals shall be provided within 12 weeks of contract award. Submittals shall include:

1. DDC System Hardware

a. A complete bill of materials to be used indicating quantity, manufacturer, model number, and relevant technical data of equipment to be used.

b. Manufacturer’s description and technical data such as performance curves, product specifications, and installation and maintenance instructions for items listed below and for relevant items not listed below:

i. Direct digital controllers (controller panels)

ii. Transducers and transmitters

iii. Sensors (including accuracy data)

iv. Actuators

v. Valves

vi. Relays and switches

vii. Control panels

viii. Power supplies

ix. Batteries

x. Operator interface equipment

xi. Wiring

c. Wiring diagrams and layouts for each control panel. Show termination numbers.

d. Schematic diagrams for all field sensors and controllers. Provide floor plans of all sensor locations and control hardware. Riser diagrams showing control network layout, communication protocol, and wire types.

2. Central System Hardware and Software

a. A complete bill of material of equipment used indicating quantity, manufacturer, model number, and relevant technical.

b. Manufacturer’s description and technical data such as product specifications and installation and maintenance instructions for items listed below and for relevant items furnished under this contract not listed below:

i. Central Processing Unit (CPU) or web server

ii. Monitors

iii. Keyboards

iv. Power supplies

v. Battery backups

vi. Interface equipment between CPU or server and control panels

vii. Operating System software

viii. Operator interface software

ix. Color graphic software

x. Third-party software

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

d. Network riser diagrams of wiring between central control unit and control panels.

3. Controlled Systems

a. Riser diagrams showing control network layout, communication protocol, and wire types.

b. A schematic diagram of each controlled system. The schematics shall have all control points labeled with point names shown or listed. The schematics shall graphically show the location of all control elements in the system.

c. A schematic wiring diagram of each controlled system. Label control elements and terminals. Where a control element is also shown on control system schematic, use the same name.

d. An instrumentation list (Bill of Materials) for each controlled system. List each control system element in a table. Show element name, type of device, manufacturer, model number, and product data sheet number.

e. A mounting, wiring, and routing plan-view drawing. The design shall take into account HVAC, electrical, and other systems’ design and elevation requirements. The drawing shall show the specific location of all concrete pads and bases and any special wall bracing for panels to accommodate this work.

f. A complete description of the operation of the control system, including sequences of operation. The description shall include and reference a schematic diagram of the controlled system.

g. A point list for each control system. List I/O points and software points specified in Section 23 09 93. Indicate alarmed and trended points.

4. Quantities of items submitted shall be reviewed but are the responsibility of the Contractor.

5. Description of process, report formats, and checklists to be used in Section 23 09 23 Article 3.17 (Control System Demonstration and Acceptance).

6. BACnet Protocol Implementation Conformance Statement (PICS) for each submitted type of controller and operator interface.

B. Schedules

1. Within one month of contract award, provide a schedule of the work indicating the following:

a. Intended sequence of work items

b. Start date of each work item

c. Duration of each work item

d. Planned delivery dates for ordered material and equipment and expected lead times

e. Milestones indicating possible restraints on work by other trades or situations

2. Monthly written status reports indicating work completed and revisions to expected delivery dates. Include updated schedule of work.

C. Project Record Documents. Upon completion of installation, submit three copies of record (as-built) documents of the documents shall be submitted for approval prior to final completion and shall include:

1. Project Record Drawings. As-built versions of submittal shop drawings provided as AutoCAD 2006 (or newer) compatible files on magnetic or optical media (file format: .DWG, .DXF, .VSD, or comparable) and as 11" x 17" prints.

2. Testing and Commissioning Reports and Checklists. Completed versions of reports, checklists, and trend logs used to meet requirements of Section 23 09 23 Article 3.17 (Control System Demonstration and Acceptance).

3. Operation and Maintenance (O&M) Manual.

4. As-built versions of submittal product data.

5. Names, addresses, and telephone numbers of installing contractors and service representatives for equipment and control systems.

6. Operator’s manual with procedures for operating control systems: logging on and off, handling alarms, producing point reports, trending data, overriding computer control, and changing setpoints and variables.

7. Programming manual or set of manuals with description of programming language and syntax, of statements for algorithms and calculations used, of point database creation and modification, of program creation and modification, and of editor use.

8. Engineering, installation, and maintenance manual or set of manuals that explains how to design and install new points, panels, and other hardware; how to perform preventive maintenance and calibration; how to debug hardware problems; and how to repair or replace hardware.

9. Documentation of programs created using custom programming language including setpoints, tuning parameters, and object database. Electronic copies of programs shall meet this requirement if control logic, setpoints, tuning parameters, and objects can be viewed using furnished programming tools.

10. Graphic files, programs, and database on magnetic or optical media.

11. List of recommended spare parts with part numbers and suppliers.

12. Complete original-issue documentation, installation, and maintenance information for furnished third-party hardware including computer equipment and sensors.

13. Complete original-issue copies of furnished software, including operating systems, custom programming language, operator workstation or web server software, and graphics software.

14. Licenses, guarantees, and warranty documents for equipment and systems.

15. Recommended preventive maintenance procedures for system components, including schedule of tasks such as inspection, cleaning, and calibration; time between tasks; and task descriptions.

D. Training Materials: Provide course outline and materials for each class at least six weeks before first class. Training shall be furnished via instructor-led sessions, computer-based training, or web-based training. Engineer will modify course outlines and materials if necessary to meet Owner’s needs. Engineer will review and approve course outlines and materials at least three weeks before first class.

1.11 Warranty

A. Warrant work as follows:

1. Warrant labor and materials for specified control system free from defects for a period of 12 months after final acceptance. Control system failures during warranty period shall be adjusted, repaired, or replaced at no additional cost or reduction in service to Owner. Respond during normal business hours within 24 hours of Owner’s warranty service request.

2. Work shall have a single warranty date, even if Owner receives beneficial use due to early system start-up. If specified work is split into multiple contracts or a multi-phase contract, each contract or phase shall have a separate warranty start date and period.

3. If the engineer determines that equipment and systems operate satisfactorily at the end of final start-up, testing, and commissioning phase, the engineer will certify in writing that control system operation has been tested and accepted in accordance with the terms of this specification. Date of acceptance shall begin warranty period.

4. Provide updates to operator workstation or web server software, project-specific software, graphic software, database software, and firmware that resolve the contractor-identified software deficiencies at no charge during warranty period. If available, Owner can purchase in-warranty service agreement to receive upgrades for functional enhancements associated with above-mentioned items. Do not install updates or upgrades without Owner’s written authorization.

5. Exception: Contractor shall not be required to warrant reused devices except those that have been rebuilt or repaired. Installation labor and materials shall be warranted. Demonstrate operable condition of reused devices at time of Engineer’s acceptance.

1.12 Ownership of Proprietary Material

A. Project-specific software and documentation shall become Owner's property. This includes, but is not limited to:

1. Graphics

2. Record drawings

3. Database

4. Application programming code

5. Documentation

1.13 Definitions

PART 2: PRODUCTS

2.0 Section Includes

2.1 Materials

2.2 Communication

2.3 Operator Interface

2.4 Controller Software

2.5 Controllers

2.6 Input and Output Interfaces

2.7 Power Supplies and Line Filtering

2.8 Auxiliary Control Devices

2.9 Wiring and Raceways

2.10 Fiber Optic Cable System

2.11 Compressed Air Supply - Pneumatic

2.1 Materials

A. Use new products the manufacturer is currently manufacturing and selling for use in new installations. Do not use this installation as a product test site unless explicitly approved in writing by Owner. Spare parts shall be available for at least five years after completion of this contract.

2.2 Communication

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

B. Install new wiring and network devices as required to provide a complete and workable control network.

C. Each controller shall have a communication port for temporary connection to a laptop computer or other operator interface. Connection shall support memory downloads and other commissioning and troubleshooting operations.

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

1. An operator interface connected to a controller shall allow the operator to interface with each internetwork controller as if directly connected. Controller information such as data, status, and control algorithms shall be viewable and editable from each internetwork controller.

2. Inputs, outputs, and control variables used to integrate control strategies across multiple controllers shall be readable by each controller on the internetwork. Program and test all cross-controller links required to execute control strategies specified in Section 23 09

93. An authorized operator shall be able to edit cross-controller links by typing a standard object address or by using a point-and-click interface.

E. Workstations, Building Control Panels, and Controllers with real-time clocks shall use the BACnet Time Synchronization service. System shall automatically synchronize system clocks daily from an operator-designated device via the internetwork. The system shall automatically adjust for daylight saving and standard time as applicable.

F. System shall be expandable to at least twice the required input and output objects with additional controllers, associated devices, and wiring.

2.3 Operator Interface

A. The Operator Workstation or server shall conform to the BACnet Operator Workstation (B-OWS) or BACnet Advanced Workstation (B-AWS) device profile as specified in ASHRAE/ANSI 135 BACnet Annex L.

B. Operator Interface. Web server shall reside on high-speed network with building controllers. Each standard browser connected to server shall be able to access all system information.

C. Communication. Web server or workstation and controllers shall communicate using BACnet protocol. Web server or workstation and control network backbone shall communicate using ISO 8802-3 (Ethernet) Data Link/Physical layer protocol and BACnet/IP addressing as specified in ANSI/ASHRAE 135, BACnet Annex J.

D. Hardware. Each workstation or web server shall consist of the following:

1. Computer. Industry-standard hardware shall meet or exceed DDC system manufacturer’s recommended specifications and shall meet response times specified elsewhere in this document. The following hardware requirements also apply:

a. The hard disk shall have sufficient memory to store:

i. All required operator workstation software.

ii. A DDC database at least twice the size of the delivered system database.

iii. One year of trend data based on the points specified to be trended at their specified trend intervals.

b. Provide additional hardware (communication ports, video drivers, network interface cards, cabling, etc.) to facilitate all control functions and software requirements specified for the DDC system.

c. Minimum hardware configuration shall include the following:

i. Dual or Quad Core Processor

ii. 6 GB RAM

iii. 500 GB hard disk providing data at 3.0 Gb/sec

iv. 16x DVD-RW drive

v. Serial, parallel, and network communication ports and cables as required for proper DDC system operation E. System Software.

1. Operating System. Web server or workstation shall have an industry-standard professional-grade operating system. Operating system shall meet or exceed the DDC System manufacturers minimum requirements for their software. Typically acceptable systems include Microsoft Windows7,Microsoft Vista, Microsoft Windows XP Pro, Windows Server 2003 or 2008, Red Hat Enterprise Linux, or Ubuntu Desktop 10.04.

2. System Graphics. The operator interface software shall be graphically based and shall include at least one graphic per piece of equipment or occupied zone, graphics for each chilled water and hot water system, and graphics that summarize conditions on each floor of each building included in this contract. Indicate thermal comfort on floor plan summary graphics using dynamic colors to represent zone temperature relative to zone setpoint.

a. Functionality. Graphics shall allow operator to monitor system status, to view a summary of the most important data for each controlled zone or piece of equipment, to use point-and-click navigation between zones or equipment, and to edit setpoints and other specified parameters.

b. Animation. Graphics shall be able to animate by displaying different image files for changed object status.

c. Alarm Indication. Indicate areas or equipment in an alarm condition using color or other visual indicator.

d. Format. Graphics shall be saved in an industry-standard format such as BMP, JPEG, PNG, or GIF. Web-based system graphics shall be viewable on browsers compatible with World Wide Web Consortium browser standards. Web graphic format shall require no plug-in (such as HTML and JavaScript) or shall only require widely available no-cost plug-ins (such as Active-X and Adobe Flash).

3. Custom Graphics. Custom graphic files shall be created with the use of a graphics generation package furnished with the system. The graphics generation package shall be a graphically based system that uses the mouse to create and modify graphics that are saved in the same formats as are used for system graphics.

4. Graphics Library. Furnish a complete library of standard HVAC equipment graphics such as chillers, boilers, air handlers, terminals, fan coils, and unit ventilators. This library also shall include standard symbols for other equipment including fans, pumps, coils, valves, piping, dampers, and ductwork. The library shall be furnished in a file format compatible with the graphics generation package program.

F. System Applications. System shall provide the following functionality to authorized operators as an integral part of the operator interface or as stand-alone software programs. If furnished as part of the interface, the tool shall be available from each workstation or web browser interface. If furnished as a stand-alone program, software shall be installable on standard IBM-compatible PCs with no limit on the number of copies that can be installed under the system license.

1. Automatic System Database Configuration. Each workstation or web server shall store on its hard disk a copy of the current system database, including controller firmware and software. Stored database shall be automatically updated with each system configuration or controller firmware or software change.

2. Manual Controller Memory Download. Operators shall be able to download memory from the system database to each controller.

3. System Configuration. The workstation software shall provide a method of configuring the system. This shall allow for future system changes or additions by users under proper password protection. Operators shall be able to configure the system.

4. On-Line Help. Provide a context-sensitive, on-line help system to assist the operator in operating and editing the system. On-line help shall be available for all applications and shall provide the relevant data for that particular screen. Additional help information shall be available through the use of hypertext.

5. Security. Each operator shall be required to log on to the system with user name and password in order to view, edit, add, or delete data.

a. Operator Access. The user name and password combination shall define accessible viewing, editing, adding, and deleting privileges for that operator. Users with system administrator rights shall be able to create new users and edit the privileges of all existing users.

b. Automatic Log Out. Automatically log out each operator if no keyboard or mouse activity is detected. This auto logoff time shall be user adjustable.

c. Encrypted Security Data. Store system security data including operator passwords in an encrypted format. System shall not display operator passwords.

6. System Diagnostics. The system shall automatically monitor the operation of all building management panels and controllers. The failure of any device shall be annunciated to the operator.

7. Alarm Processing. System input and status objects shall be configurable to alarm on departing from and on returning to normal state. Operator shall be able to enable or disable each alarm and to configure alarm limits, alarm limit differentials, alarm states, and alarm reactions for each system object. Configure and enable alarm points as specified in Section 23 09 93 (Sequences of Operation). Alarms shall be BACnet alarm objects and shall use BACnet alarm services.

8. Alarm Messages. Alarm messages shall use the English language descriptor for the object in alarm in such a way that the operator will be able to recognize the source, location, and nature of the alarm without relying on acronyms.

9. Alarm Reactions. Operator shall be able to configure (by object) what, if any actions are to be taken during an alarm. As a minimum, the workstation or web server shall be able to log, print, start programs, display messages, send e-mail, send page, and audibly annunciate.

10. Alarm and Event log. Operators shall be able to view all system alarms and changes of state from any location in the system. Events shall be listed chronologically. An operator with the proper security level may acknowledge and delete alarms, and archive closed alarms to the workstation or web server hard disk.

11. Trend Logs. The operator shall be able to configure trend sample or change of value (COV) interval, start time, and stop time for each system data object and shall be able to retrieve data for use in spreadsheets and standard database programs. Controller shall sample and store trend data and shall be able to archive data to the hard disk. Configure trends as specified in Section 23 09 93 (Sequences of Operation). Trends shall be BACnet trend objects.

12. Object and Property Status and Control. Provide a method for the operator to view, and edit if applicable, the status of any object or property in the system. The status shall be available by menu, on graphics, or through custom programs.

13. Reports and Logs. Operator shall be able to select, to modify, to create, and to print reports and logs. Operator shall be able to store report data in a format accessible by standard spreadsheet and word processing programs.

14. Standard Reports. Furnish the following standard system reports:

a. Objects. System objects and current values filtered by object type, by status (in alarm, locked, normal), by equipment, by geographic location, or by combination of filter criteria.

b. Alarm Summary. Current alarms and closed alarms. System shall retain closed alarms for an adjustable period.

c. Logs. System shall log the following to a database or text file and shall retain data for an adjustable period:

i. Alarm History.

ii. Trend Data. Operator shall be able to select trends to be logged.

iii. Operator Activity. At a minimum, system shall log operator log in and log out, control parameter changes, schedule changes, and alarm acknowledgment and deletion. System shall date and time stamp logged activity.

15. Energy Reports. System shall include an easily configured energy reporting tool that provides the capabilities described in this section.

a. The energy reporting tool shall be accessible through the same user interface (Web browser or operator workstation software) as is used to manage the BAS.

b. The energy reporting tool shall be preconfigured by the Contractor to gather and store energy demand and consumption data from each energy source that provides metered data to the BAS. Meter data shall be stored at 5 minute intervals unless otherwise specified in the Sequence of Operation provided in section 23 09 93. This data shall be maintained in an industry standard SQL database for a period of not less than five years.

c. The energy reporting tool shall allow the operator to select an energy source and a time period of interest (day, week, month, year, or date range) and shall provide options to view the data in a table, line graph, bar graph, or pie chart. The tool shall also allow the operator to select two or more data sources and display a comparison of the energy used over this period in any of the listed graph formats, or to total the energy used by the selected sources and display that data in the supported formats.

d. The energy reporting tool shall allow the operator to select and energy source and two time periods of interest (day, week, month, year, or date range) and display a graph that compares the energy use over the two time periods in any of the graph formats listed in the previous paragraph. The tool shall also allow the operator to select multiple energy sources and display a graph that compares the total energy used by these sources over the two time periods.

e. The energy reporting tool shall allow the operator to easily generate the previously described graphs "on the fly," and shall provide an option to store the report format so the operator can select that format to regenerate the graph at a future date. The tool shall also allow the user to schedule these reports to run on a recurring basis using relative time periods, such as automatically generating a consumption report on the first Monday of each month showing consumption over the previous month. Automatically generated reports shall be archived on the server in a common industry format such as Adobe PDF or

Microsoft Excel with copies e-mailed to a user editable list of recipients.

f. The energy reporting tool shall be capable of collecting and displaying data from the following types of meters:

i. Electricity

ii. Gas

iii. Oil

iv. Steam

v. Chilled Water

vi. Potable Water

vii. Heating and cooling degree days. (May be calculated from sensor data rather than metered.)

g. The user shall have the option of using Kw (Kwh) or Btu/hr (Btu) as the units for demand and consumption reports. Multiples of these units (MWH, kBtu, etc.) shall be used as appropriate. All selected sources shall be automatically converted to the selected units. The user shall similarly have the option of entering facility area and occupancy hours and creating reports that are normalized on an area basis, an annual use basis, or an occupied hour basis.

h. The user shall have the option of entering benchmark data for an individual facility or a group of facilities.

i. The user shall have the option of displaying any or all of the following data on any chart, line, or bar graph generated by the energy reporting tool:

i. Low/High/Average value of the metered value being displayed.

ii. Heating and/or Cooling Degree Days for the time period(s) being displayed.

iii. The Environmental Index for the facilities and time periods being displayed.

16. Environmental Index. System shall monitor all occupied zones and compile an index that provides a numerical indication of the environmental comfort within the zone. As a minimum, this indication shall be based upon the deviation of the zone temperature from the heating or cooling setpoint. If humidity is being measured within the zone then the environmental index shall be adjusted to reflect a lower comfort level for high or low humidity levels. Similarly, if carbon dioxide levels are being measured as an indication of ventilation effectiveness then the environmental index shall be adjusted to indicate degraded comfort at high carbon dioxide levels. Other adjustments may be made to the environmental index based upon additional measurements. The system shall maintain a trend of the environmental index for each zone in the trend log. The system shall also compute an average comfort index for every building included in this contract and maintain trendlogs of these building environmental indices. Similarly, the system shall compute the percentage of occupied time that comfortable conditions were maintained within the zones. Through the UI the user shall be able to add a weighting factor to adjust the contribution of each zone to the average index based upon the floor area of the zone, importance of the zone, or other static criteria.

17. Custom Reports. Operator shall be able to create custom reports that retrieve data, including archived trend data, from the system, that analyze data using common algebraic calculations, and that present results in tabular or graphical format. Reports shall be launched from the operator interface.

G. Workstation Application Editors. Each PC or browser workstation shall support editing of all system applications. The applications shall be downloaded and executed at one or more of the controller panels.

1. Controller. Provide a full-screen editor for each type of application that shall allow the operator to view and change the configuration, name, control parameters, and set points for all controllers.

2. Scheduling. An editor for the scheduling application shall be provided at each workstation. Provide a method of selecting the desired schedule and schedule type. Exception schedules and holidays shall be shown clearly on the calendar. The start and stop times for each object shall be adjustable from this interface.

3. Custom Application Programming. Provide the tools to create, edit, debug, and download custom programs. System shall be fully operable while custom programs are edited, compiled, and downloaded. Programming language shall have the following features:

a. Language. Language shall be graphically based and shall use function blocks arranged in a logic diagram that clearly shows control logic flow. Function blocks shall directly provide functions listed below, and operators shall be able to create custom or compound function blocks.

b. Programming Environment. Tool shall provide a full-screen, cursor-and-mouse-driven programming environment that incorporates word processing features such as cut and paste. Operators shall be able to insert, add, modify, and delete custom programming code, and to copy blocks of code to a file library for reuse in other control programs.

c. Independent Program Modules. Operator shall be able to develop independently executing program modules that can disable, enable and exchange data with other program modules.

d. Debugging and Simulation. Operator shall be able to step through the program observing intermediate values and results. Operator shall be able to adjust input variables to simulate actual operating conditions. Operator shall be able to adjust each step’s time increment to observe operation of delays, integrators, and other time-sensitive control logic. Debugger shall provide error messages for syntax and for execution errors.

e. Conditional Statements. Operator shall be able to program conditional logic using compound Boolean (AND, OR, and NOT) and relational (EQUAL, LESS THAN, GREATER THAN, NOT EQUAL) comparisons.

f. Mathematical Functions. Language shall support floating-point addition, subtraction, multiplication, division, and square root operations, as well as absolute value calculation and programmatic selection of minimum and maximum values from a list of values.

g. Variables. Operator shall be able to use variable values in program conditional statements and mathematical functions.

i. Time Variables. Operator shall be able to use predefined variables to represent time of day, day of the week, month of the year, and date. Other predefined variables or simple control logic shall provide elapsed time in seconds, minutes, hours, and days. Operator shall be able to start, stop, and reset elapsed time variables using the program language.

ii. System Variables. Operator shall be able to use predefined variables to represent status and results of Controller Software and shall be able to enable, disable, and change setpoints of Controller Software as described in Controller Software section.

H. Portable Operator's Terminal. Provide all necessary software to configure an IBM-compatible laptop computer for use as a Portable Operator’s Terminal. Operator shall be able to connect configured Terminal to the system network or directly to each controller for programming, setting up, and troubleshooting.

2.4 Controller Software

A. Furnish the following applications for building and energy management. All software application shall reside and operate in the system controllers. Applications shall be editable through operator workstation, web browser interface, or engineering workstation.

B. System Security. See Paragraph 2.3.E.5 (Security) and Paragraph 2.3.E.14.c.iii (Operator Activity).

C. Scheduling. Provide the capability to execute control functions according to a user created or edited schedule. Each schedule shall provide the following schedule options as a minimum:

1. Weekly Schedule. Provide separate schedules for each day of the week. Each schedule shall be able to include up to 5 occupied periods (5 start-stop pairs or 10 events).

2. Exception Schedules. Provide the ability for the operator to designate any day of the year as an exception schedule. Exception schedules may be defined up to a year in advance. Once an exception schedule has executed, the system shall discard and replace the exception schedule with the standard schedule for that day of the week.

3. Holiday Schedules. Provide the capability for the operator to define up to 24 special or holiday schedules. These schedules will be repeated each year. The operator shall be able to define the length of each holiday period.

D. System Coordination. Operator shall be able to group related equipment based on function and location and to use these groups for scheduling and other applications.

E. Binary Alarms. Each binary object shall have the capability to be configured to alarm based on the operator-specified state. Provide the capability to automatically and manually disable alarming.

F. Analog Alarms. Each analog object shall have both high and low alarm limits. The operator shall be able to enable or disable these alarms.

G. Alarm Reporting. The operator shall be able to determine the action to be taken in the event of an alarm. An alarm shall be able to start programs, print, be logged in the event log, generate custom messages, and display on graphics.

H. Remote Communication. System shall automatically contact operator workstation or server on receipt of critical alarms.

I. Demand Limiting.

1. The demand-limiting program shall monitor building power consumption from a building power meter (provided by others) which generates pulse signals or a BACnet communications interface. An acceptable alternative is for the system to monitor a watt transducer or current transformer attached to the building feeder lines.

2. When power consumption exceeds adjustable levels, system shall automatically adjust setpoints, de-energize low-priority equipment, and take other programmatic actions to reduce demand as specified in Section 23 09 93 (Sequences of Operation). When demand drops below adjustable levels, system shall restore loads as specified.

J. Maintenance Management. The system shall be capable of generating maintenance alarms when equipment exceeds adjustable runtime, equipment starts, or performance limits. Configure and enable maintenance alarms as specified in 23 09 93 (Sequences of Operation).

K. Sequencing. Application software shall sequence chillers, boilers, and pumps as specified in Section 23 09 93 (Sequences of Operation).

L. PID Control. System shall provide direct- and reverse-acting PID (proportional-integral-derivative) algorithms. Each algorithm shall have anti-windup and selectable controlled variable, setpoint, and PID gains. Each algorithm shall calculate a time-varying analog value that can be used to position an output or to stage a series of outputs. The calculation interval, PID gains, and other tuning parameters shall be adjustable by a user with the correct security level.

M. Staggered Start. System shall stagger controlled equipment restart after power outage. Operator shall be able to adjust equipment restart order and time delay between equipment restarts.

N. Energy Calculations.

1. The system shall accumulate and convert instantaneous power (kW) or flow rates (L/s [gpm]) to energy usage data.

2. The system shall calculate a sliding-window average (rolling average). Operator shall be able to adjust window interval to 15 minutes, 30 minutes, or 60 minutes.

O. Anti-Short Cycling. All binary output objects shall be protected from short cycling by means of adjustable minimum on-time and off-time settings.

P. On and Off Control with Differential. Provide an algorithm that allows a binary output to be cycled based on a controlled variable and a setpoint. The algorithm shall be direct-acting or reverse-acting.

Q. Runtime Totalization. Provide software to totalize runtime for each binary input and output. Operator shall be able to enable runtime alarm based on exceeded adjustable runtime limit. Configure and enable runtime totalization and alarms as specified in Section 23 09 93 (Sequence of Operations).

2.5 Controllers

A. General. Provide an adequate number of Building Controllers (BC), Advanced Application Controllers (AAC), Application Specific Controllers (ASC), Smart Actuators (SA), and Smart Sensors (SS) as required to achieve performance specified in Section 23 09 23 Article 1.9 (System Performance). Every device in the system which executes control logic and directly controls HVAC equipment must conform to a standard BACnet Device profile as specified in ANSI/ASHRAE 135, BACnet Annex L. Unless otherwise specified, hardwired actuators and sensors may be used in lieu of BACnet Smart Actuators and Smart Sensors.

B. BACnet.

1. Building Controllers (BCs). Each BC shall conform to BACnet Building Controller (B-BC) device profile as specified in ANSI/ASHRAE 135, BACnet Annex L, and shall be listed as a certified B-BC in the BACnet Testing Laboratories (BTL) Product Listing.

2. Advanced Application Controllers (AACs). Each AAC shall conform to BACnet Advanced Application Controller (B-AAC) device profile as specified in ANSI/ASHRAE 135, BACnet Annex L and shall be listed as a certified B-AAC in the BACnet Testing Laboratories (BTL) Product Listing.

3. Application Specific Controllers (ASCs). Each ASC shall conform to BACnet Application Specific Controller (B-ASC) device profile as specified in ANSI/ASHRAE 135, BACnet Annex L and shall be listed as a certified B-ASC in the BACnet Testing Laboratories (BTL) Product Listing.

4. Smart Sensors (SSs). Each SS shall conform to BACnet Smart Sensor (B-SS) device profile as specified in ANSI/ASHRAE 135, BACnet Annex L and shall be listed as a certified B-SS in the BACnet Testing Laboratories (BTL) Product Listing.

5. BACnet Communication.

a. Each BC shall reside on or be connected to a BACnet network using ISO 8802-3 (Ethernet) Data Link/Physical layer protocol and BACnet/IP addressing.

b. BACnet routing shall be performed by BCs or other BACnet device routers as necessary to connect BCs to networks of AACs and ASCs.

c. Each AAC shall reside on a BACnet network using ISO 8802-3 (Ethernet) Data Link/Physical layer protocol with BACnet/IP addressing, or it shall reside on a BACnet network using the ARCNET or MS/TP Data Link/Physical layer protocol.

d. Each ASC shall reside on a BACnet network using the ARCNET or MS/TP Data Link/Physical layer protocol.

e. Each SA shall reside on a BACnet network using the ARCNET or MS/TP Data Link/Physical layer protocol.

f. Each SS shall reside on a BACnet network using ISO 8802-3 (Ethernet) Data Link/Physical layer protocol with BACnet/IP addressing, or it shall reside on a BACnet network using ARCNET or MS/TP Data Link/Physical layer protocol.

C. Communication

1. Service Port. Each controller shall provide a service communication port for connection to a Portable Operator’s Terminal. Connection shall be extended to space temperature sensor ports where shown on drawings.

2. Signal Management. BC and ASC operating systems shall manage input and output communication signals to allow distributed controllers to share real and virtual object information and to allow for…