Attachment 5. MAHG211140 - Specifications V2.pdf

ATTACHMENT D - MAHG 211140 CONTROLS PHASE II, KEESLER

SECTION 23 81 00 PAGE 1

SECTION 23 09 23

CONTROLS, INSTRUMENTATION & ENERGY MANAGEMENT

1. Part 1 – General

Table of Contents

Part 1 – General

1.1 Related Documents

1.2 Definitions

1.3 BMS System Description

1.4 Quality Assurance

1.5 References

1.6 Work By Others

1.7 Submittals

1.8 Record Documentation

1.9 Warranty

Part 2 – Products

2.1 System Architecture

2.2 Operator Workstation

2.3 Operator Interface

2.4 Application Nodes

2.5 Application Software

2.6 Field Devices

2.7 Specialty Items

Part 3 – Execution

3.1 Installation Practices

3.2 Training

3.3 Commissioning Requirements

3.4 Coordination

3.5 Sequences

3.6 Point Lists

1.1 Related Documents

A. All work of this Division shall be coordinated and provided by the single Building Management System (BMS) Contractor.

B. The work of this Division shall be scheduled, coordinated, and interfaced with the associated work of other trades. Reference the Division 15 Sections for details.

C. The work of this Division shall be as required by the Specifications, Point Schedules and Drawings.

D. If the BMS Contractor believes there are conflicts or missing information in the project documents, the Contractor shall promptly request clarification and instruction from the design team.

1.2 Definitions

A. Analog: A continuously variable system or value not having discrete levels. Typically exists within a defined range of limiting values.

Attachment 5

FA301024R0007

SECTION 23 81 00 PAGE 2

B. Binary: A two-state system where an “ON” condition is represented by one discrete signal level and an “OFF” condition is represented by a second discrete signal level.

C. Building Management System (BMS): The total integrated system of fully operational and functional elements, including equipment, software, programming, and associated materials, to be provided by this Division BMS Contractor and to be interfaced to the associated work of other related trades.

D. BMS Contractor: The single Contractor to provide the work of this Division. This Contractor shall be the primary manufacturer, installer, commissioner and ongoing service provider for the BMS work.

E. Control Sequence: An BMS pre-programmed arrangement of software algorithms, logical computation, target values and limits as required to attain the defined operational control objectives.

F. Direct Digital Control: The digital algorithms and pre-defined arrangements included in the BMS software to provide direct closed-loop control for the designated equipment and controlled variables. Inclusive of Proportional, Derivative and Integral control algorithms together with target values, limits, logical functions, arithmetic functions, constant values, timing considerations and the like.

G. BMS Network: The total digital on-line real-time interconnected configuration of BMS digital processing units, workstations, panels, sub-panels, controllers, devices and associated elements individually known as network nodes. May exist as one or more fully interfaced and integrated sub-networks, LAN, WAN or the like.

H. Node: A digitally programmable entity existing on the BMS network.

I. BMS Integration: The complete functional and operational interconnection and interfacing of all

BMS work elements and nodes in compliance with all applicable codes, standards and ordinances so as to provide a single coherent BMS as required by this Division.

J. Provide: The term “Provide” and its derivatives when used in this Division shall mean to furnish, install in place, connect, calibrate, test, commission, warrant, document and supply the associated required services ready for operation.

K. PC: IBM-compatible Personal Computer from a recognized major manufacturer L. Furnish: The term “Furnish” and its derivatives when used in this Division shall mean supply at the

BMS Contractor’s cost to the designated third party trade contractor for installation. BMS Contractor shall connect furnished items to the BMS, calibrate, test, commission, warrant and document.

M. Wiring: The term “Wiring” and its derivatives when used in this Division shall mean provide the BMS wiring and terminations.

N. Install: The term “Install” and its derivatives when used in this Division shall mean receive at the jobsite and mount.

O. Protocol: The term “protocol” and its derivatives when used in this Division shall mean a defined set of rules and standards governing the on-line exchange of data between BMS network nodes.

P. Software: The term “software” and its derivatives when used in this Division shall mean all of programmed digital processor software, preprogrammed firmware and project specific digital process programming and database entries and definitions as generally understood in the BMS industry for real-time, on-line, integrated BMS configurations.

Q. The use of words in the singular in these Division documents shall not be considered as limiting when other indications in these documents denote that more than one such item is being referenced.

SECTION 23 81 00 PAGE 3

R. Headings, paragraph numbers, titles, shading, bolding, underscores, clouds and other symbolic interpretation aids included in the Division documents are for general information only and are to assist in the reading and interpretation of these Documents.

S. The following abbreviations and acronyms may be used in describing the work of this Division:

ADC - Analog to Digital Converter AI - Analog Input AN - Application Node ANSI - American National Standards Institute AO - Analog Output ASCII - American Standard Code for Information

Interchange ASHRAE American Society of Heating, Refrigeration and Air

Conditioning Engineers AWG - American Wire Gauge CPU - Central Processing Unit CRT - Cathode Ray Tube DAC - Digital to Analog Converter DDC - Direct Digital Control DI - Digital Input DO - Digital Output EEPROM - Electronically Erasable Programmable Read Only

Memory EMI - Electromagnetic Interference FAS - Fire Alarm Detection and Annunciation System GUI - Graphical User Interface HOA - Hand-Off-Auto ID - Identification IEEE - Institute of Electrical and Electronics Engineers I/O - Input/Output LAN - Local Area Network LCD - Liquid Crystal Display LED - Light Emitting Diode MCC - Motor Control Center NC - Normally Closed NIC - Not In Contract NO - Normally Open OWS - Operator Workstation OAT - Outdoor Air Temperature PC - Personal Computer RAM - Random Access Memory RF - Radio Frequency RFI - Radio Frequency Interference RH - Relative Humidity ROM - Read Only Memory RTD - Resistance Temperature Device SPDT - Single Pole Double Throw SPST - Single Pole Single Throw XVGA - Extended Video Graphics Adapter TBA - To Be Advised TCP/IP - Transmission Control Protocol/Internet

Protocol

SECTION 23 81 00 PAGE 4

TTD - Thermistor Temperature Device UPS - Uninterruptible Power Supply VAC - Volts, Alternating Current VAV - Variable Air Volume VDC - Volts, Direct Current WAN - Wide Area Network

1.3 BMS Description

A. The Building Management System (BMS) shall be a complete system designed for use with the enterprise IT systems.. This functionality shall extend into the equipment rooms. Devices residing on the automation network located in equipment rooms and similar shall be fully IT with the existing local area network. Contractor shall be responsible for coordination with the EMCS department to ensure that the BMS will perform in the owner’s environment.

B. All points of user interface shall be on standard PCs that communicate with and will be an extension of the existing Metasys ADX OR Siemens server located in building 4705.

C. The work of the single BMS Contractor shall be as defined individually and collectively in all Sections of this Division specifications together with the associated Point Sheets and Drawings and the associated interfacing work as referenced in the related documents.

D. The BMS work shall consist of the provision of all labor, materials, tools, equipment, software, software licenses, software configurations and database entries, interfaces, wiring, tubing, installation, labeling, engineering, calibration, documentation, samples, submittals, testing, commissioning, training services, permits and licenses, transportation, shipping, handling, administration, supervision, management, insurance, temporary protection, cleaning, cutting and patching, warranties, services, and items, even though these may not be specifically mentioned in these Division documents which are required for the complete, fully functional and commissioned

BMS.

E. Provide a complete, neat and workmanlike installation. Use only manufacturer employees who are skilled, experienced, trained, and familiar with the specific equipment, software, standards and configurations to be provided for this Project.

F. Manage and coordinate the BMS work in a timely manner in consideration of the Project schedules. Coordinate with the associated work of other trades so as to not impede or delay the work of associated trades.

G. The BMS as provided shall incorporate, at minimum, the following integrated features, functions and services:

1. Operator information, alarm management and control functions.

2. Enterprise-level information and control access.

3. Information management including monitoring, transmission, archiving, retrieval, and reporting functions.

4. Diagnostic monitoring and reporting of BMS functions.

5. Offsite monitoring and management access.

6. Energy management

7. Standard applications for terminal HVAC systems.

1.4 Quality Assurance

A. General

SECTION 23 81 00 PAGE 5

1. The Building Management System Contractor shall be the primary manufacturer-owned branch office that is regularly engaged in the engineering, programming, installation and service of total integrated Building Management Systems.

2. The BMS Contractor shall be a recognized national manufacturer, installer and service provider of BMS.

3. If a franchised dealer is to be considered via addendum, the authorized building control system installer must provide a letter written by a minimum Vice President of Operations for Johnson Controls. This letter must be provided to the engineer along with the other supporting documentation at the time of request for equivalence.

4. The BMS Contractor shall have a branch facility within a 100-mile radius of the job site supplying complete maintenance and support services on a 24 hour, 7-day-a-week basis.

5. As evidence and assurance of the contractor’s ability to support the Owner's system with service and parts, the contractor must have been in the BMS business for at least the last ten (10) years and have successfully completed total projects of at least 10 times the value of this contract in each of the preceding five years.

6. The Building Management System architecture shall consist of the products of a manufacturer regularly engaged in the production of Building Management Systems, and shall be the manufacturer’s latest standard of design at the time of bid.

B. Workplace Safety And Hazardous Materials

1. Provide a safety program in compliance with the Contract Documents.

2. The BMS Contractor shall have a corporately certified comprehensive Safety Certification Manual and a designated Safety Supervisor for the Project.

3. The Contractor and its employees and subtrades comply with federal, state and local safety regulations.

4. The Contractor shall ensure that all subcontractors and employees have written safety programs in place that covers their scope of work, and that their employees receive the training required by the OSHA have jurisdiction for at least each topic listed in the Safety Certification Manual.

5. Hazards created by the Contractor or its subcontractors shall be eliminated before any further work proceeds.

6. Hazards observed but not created by the Contractor or its subcontractors shall be reported to either the General Contractor or the Owner within the same day.

The Contractor shall be required to avoid the hazard area until the hazard has been eliminated.

7. The Contractor shall sign and date a safety certification form prior to any work being performed, stating that the Contractors’ company is in full compliance with the Project safety requirements.

SECTION 23 81 00 PAGE 6

8. The Contractor’s safety program shall include written policy and arrangements for the handling, storage and management of all hazardous materials to be used in the work in compliance with the requirements of the AHJ at the Project site.

9. The Contractor’s employees and subcontractor’s staff shall have received training as applicable in the use of hazardous materials and shall govern their actions accordingly.

C. Quality Management Program

1. Designate a competent and experienced employee to provide BMS Project

Management. The designated Project Manger shall be empowered to make technical, scheduling and related decisions on behalf of the BMS Contractor. At minimum, the Project Manager shall:

a. Manage the scheduling of the work to ensure that adequate materials, labor and other resources are available as needed.

b. Manage the financial aspects of the BMS Contract.

c. Coordinate as necessary with other trades.

d. Be responsible for the work and actions of the BMS workforce on site.

1.5 References

A. All work shall conform to the following Codes and Standards, as applicable:

1. National Fire Protection Association (NFPA) Standards.

2. National Electric Code (NEC) and applicable local Electric Code.

3. Underwriters Laboratories (UL) listing and labels.

4. UL 864 UUKL Smoke Control

5. UL 268 Smoke Detectors.

6. UL 916 Energy Management

7. NFPA 70 - National Electrical Code.

8. NFPA 90A - Standard For The Installation Of Air Conditioning And Ventilating

Systems.

9. NFPA 92A and 92B Smoke Purge/Control Equipment.

10. Factory Mutual (FM).

11. American National Standards Institute (ANSI).

12. National Electric Manufacturer’s Association (NEMA).

13. American Society of Mechanical Engineers (ASME).

14. American Society of Heating, Refrigerating and Air Conditioning Engineers

(ASHRAE).

15. Air Movement and Control Association (AMCA).

16. Institute of Electrical and Electronic Engineers (IEEE).

17. American Standard Code for Information Interchange (ASCII).

18. Electronics Industries Association (EIA).

19. Occupational Safety and Health Administration (OSHA).

20. American Society for Testing and Materials (ASTM).

21. Federal Communications Commission (FCC) including Part 15, Radio Frequency

Devices.

SECTION 23 81 00 PAGE 7

22. Americans Disability Act (ADA)

23. ANSI/EIA 909.1-A-1999 (LonWorks) 24 ANSI/ASHRAE Standard 195-2004 (BACnet)

B. In the case of conflicts or discrepancies, the more stringent regulation shall apply.

C. All work shall meet the approval of the Authorities Having Jurisdiction at the project site.

1.6 Submittals

Shop Drawings, Product Data, and Samples

1. Submittals shall be in accordance with Section 1330.

2. Equipment and systems requiring approval of local authorities must comply with such regulations and be approved. Filing shall be at the expense of the BMS Contractor where filing is necessary. Provide a copy of all related correspondence and permits to the Owner.

3. Prepare an index of all submittals and shop drawings for the installation. Index shall include a shop drawing identification number, Contract Documents reference and item description.

4. The BMS Contractor shall correct any errors or omissions noted in the first review.

5. At a minimum, submit the following:

a. BMS network architecture diagrams including all nodes and interconnections.

b. Systems schematics, sequences and flow diagrams.

c. Points schedule for each point in the BMS, including: Point Type, Object

Name, Expanded ID, Display Units, Controller type, and Address.

d. Detailed Bill of Material list for each system or application, identifying quantities, part numbers, descriptions, and optional features.

e. Control Valve Schedules including a separate line for each valve provided under this section and a column for each of the valve attributes: Code Number, Configuration, Fail Position, Pipe Size, Valve Size, Body Configuration, Close off Pressure, Capacity, Valve CV, Design Pressure, and Actuator Type.

f. Details of all BMS interfaces and connections to the work of other trades.

g. Product data sheets or marked catalog pages including part number, photo and description for all products including software.

1.8 Record Documentation

A. Operation and Maintenance Manuals

1. Three (3) copies of the Operation and Maintenance Manuals shall be provided to the Owner's Representative upon completion of the project. The entire Operation and Maintenance Manual shall be furnished on Compact Disc media, and include the following for the BMS provided:

a. Table of contents.

b. As-built system record drawings. PDF type record drawings shall represent the as-built condition of the system and incorporate all information supplied with the approved submittal.

SECTION 23 81 00 PAGE 8

c. Manufacturers product data sheets or catalog pages for all products including software.

d. System Operator’s manuals.

e. Archive copy of all site-specific databases and sequences.

f. BMS network diagrams.

g. Interfaces to all third-party products and work by other trades.

2. The Operation and Maintenance Manual CD shall be self-contained, and include all necessary software required to access the product data sheets. A logically organized table of contents shall provide dynamic links to view and print all product data sheets. Viewer software shall provide the ability to display, zoom, and search all documents.

1.9 Warranty

A. Standard Material and Labor Warranty:

1. Provide a one-year labor and material warranty on the BMS.

2. If within twelve (12) months from the date of acceptance of product, upon written notice from the owner, it is found to be defective in operation, workmanship or materials, it shall be replaced, repaired or adjusted at the option of the BMS Contractor at the cost of the BMS Contractor.

3. Maintain an adequate supply of materials within 100 miles of the Project site such that replacement of key parts and labor support, including programming.

Warranty work shall be done during BMS Contractor’s normal business hours.

2. Part 2 – Products

2.1 General Description

A. The Building Management System (BMS) shall use an open architecture and fully support a multi-vendor environment. To accomplish this effectively, the BMS shall support open communication protocol standards and integrate a wide variety of third-party devices and applications. The system shall be designed for use on the Internet, or intranets using off the shelf, industry standard technology compatible with other owner provided networks.

B. The Building Management System shall consist of the following:

1. Standalone Network Automation Engine(s)

2. Field Equipment Controller(s)

3. Input/Output Module(s)

4. Local Display Device(s)

5. Portable Operator's Terminal(s)

6. Distributed User Interface(s)

7. Network processing, data storage and communications equipment

7. Other components required for a complete and working BMS

C. The system shall be modular in nature, and shall permit expansion of both capacity and functionality through the addition of sensors, actuators, controllers and operator devices, while re-using existing controls equipment.

SECTION 23 81 00 PAGE 9

D. System architectural design shall eliminate dependence upon any single device for alarm reporting and control execution.

1. The failure of any single component or network connection shall not interrupt the execution of control strategies at other operational devices.

2. The System shall maintain all settings and overrides through a system reboot.

E. System architectural design shall eliminate dependence upon any single device for alarm reporting and control execution.

F. Acceptable Manufacturers

1) Building automation system (BAS) shall be compatible with current BAS (METASYS/SIEMENS) operating on Keesler AFB

2.2 BMS Architecture

A. Automation Network

1. The automation network shall be based on a PC industry standard of Ethernet

TCP/IP. Where used, LAN controller cards shall be standard “off the shelf” products available through normal PC vendor channels. No 3rd party BACnet.

2. The BMS shall network multiple user interface clients, automation engines, system controllers and application-specific controllers. Provide application and data server(s) as required for systems operation.

3. All BMS devices on the automation network shall be capable of operating at a communication speed of 100 Mbps, with full peer-to-peer network communication.

4. Network Automation Engines (NAE) shall reside on the automation network.

5. The automation network will be compatible with other enterprise-wide networks. Where indicated, the automation network shall be connected to the enterprise network and share resources with it by way of standard networking devices and practices.

B. Control Network

1. Network Automation Engines (NAE) shall provide supervisory control.

C. Integration

1. Hardwired

a. Analog and digital signal values shall be passed from one system to another via hardwired connections.

b. There will be one separate physical point on each system for each point to be integrated between the systems.

2. Direct Protocol (Integrator Panel)

a. The BMS system shall include appropriate hardware equipment and software to allow bi-directional data communications between the BMS system and 3rd party manufacturers’ control panels. The BMS shall receive, react to, and return information from multiple building systems, including but not limited to the chillers, boilers, variable frequency drives, power monitoring system, and medical gas.

b. All data required by the application shall be mapped into the Automation Engine’s database, and shall be transparent to the operator.

c. Point inputs and outputs from the third-party controllers shall have real-time interoperability with BMS software features such as: Control

SECTION 23 81 00 PAGE 10

Software, Energy Management, Custom Process Programming, Alarm Management, Historical Data and Trend Analysis, Totalization, and Local Area Network Communications.

3. BACnet Protocol Integration – BACnet (no 3rd party BACnet)

a. The neutral protocol used between systems will be BACnet over Ethernet and comply with the ASHRAE BACnet standard 135-2003.

b. A complete Protocol Implementation Conformance Statement (PICS) shall be provided for all BACnet system devices.

c. The ability to command, share point object data, change of state (COS) data and schedules between the host and BACnet systems shall be provided.

2.3 User Interface

A. Dedicated Web Based User Interface

1. Where indicated on plans the BMS Contractor shall provide and install a personal computer for command entry, information management, network alarm management, and database management functions. All real-time control functions, including scheduling, history collection and alarming, shall be resident in the BMS Network Automation Engines to facilitate greater fault tolerance and reliability. The computer shall be an extension of the existing Metasys ADX server and shall complete access to the databases and graphic storage files for all buildings.

2. Dedicated User Interface Architecture – The architecture of the computer shall be implemented to conform to industry standards, so that it can accommodate applications provided by the BMS Contractor and by other third party applications suppliers, including but not limited to Microsoft Office Applications.

Specifically it must be implemented to conform to the following interface standards.

a. Microsoft Internet Explorer for user interface functions.

b. Microsoft Office Professional for creation, modification and maintenance of reports, sequences other necessary building management functions

c. Microsoft Outlook or other e-mail program for supplemental alarm functionality and communication of system events, and reports

d. Required network operating system for exchange of data and network functions such as printing of reports, trends and specific system summaries

3. PC Hardware – The personal computer(s) shall be configured as follows:

a. Memory – 1 GB (512 MB Minimum)

b. CPU– Pentium 4 processor. 2.8 Hz Clock Speed (2.0 GHz minimum)

c. Hard Drive – 80 GB free hard drive space (40GB minimum)

d. Hard drive backup system – CD/RW, DVD/RW or network backup software provided by IT department

e. CD ROM Drive – 32X performance

f. Ports – (2) Serial and (1) parallel, (2) USB ports

g. Keyboard – 101 Keyboard and 2 Button Mouse

h. CRT configuration – 1-2 CRTs as follows:

◊ Each Display – 17” Flat Panel Monitor 1280 x 1024 resolution minimum

SECTION 23 81 00 PAGE 11

◊ 16 bit or higher color resolution ◊ Display card with multiple monitor support

i. LAN communications – Ethernet communications board; 3Comm or equal

4. Operating System Software

a. Windows XP Professional

b. Where user interface is not provided via browser, provide complete operator workstation software package, including any hardware or software keys. Include the original installation disks and licenses for all included software, device drivers, and peripherals.

c. Provide software registration cards to the Owner for all included software.

5. Peripheral Hardware

a. Reports printer:

◊ Printer Make - Hewlett ◊ Print Speed – 600 DPI Black, 300 DPI Color ◊ Buffer – 64 K Input Print Buffer ◊ Color Printing – Include Color Kit

B. Distributed Web Based User Interface

1. All features and functions of the dedicated user interface previously defined in this document shall be available on any computer connected directly or via a wide area or virtual private network (WAN/VPN) to the automation network and conforming to the following specifications.

2. The software shall run on the Microsoft Internet Explorer (6.0 or higher) browser supporting the following functions:

◊ Configuration ◊ Commissioning ◊ Data Archiving ◊ Monitoring ◊ Commanding ◊ System Diagnostics

3. Minimum hardware requirements:

◊ 512 MB RAM

◊ 2.0 GHz Clock Speed Pentium 4 Microprocessor ◊ 100.0 GB Hard Drive.

◊ 1 Keyboard with 83 keys (minimum).

◊ SVGA 1024x768 resolution display with 64K colors and 16 bit color depth ◊ Mouse or other pointing device

C. User Interface Application Components

1. Operator Interface

a. An integrated browser based client application shall be used as the user operator interface program.

b. The System shall employ an event-driven rather than a device polling methodology to dynamically capture and present new data to the user.

SECTION 23 81 00 PAGE 12

c. All Inputs, Outputs, Setpoints, and all other parameters as defined within Part 3, shown on the design drawings, or required as part of the system software, shall be displayed for operator viewing and modification from the operator interface software.

d. The user interface software shall provide help menus and instructions for each operation and/or application.

e. The system shall support customization of the UI configuration and a home page display for each operator.

f. The system shall support user preferences in the following screen presentations:

◊ Alarm ◊ Trend ◊ Display ◊ Applications

g. All controller software operating parameters shall be displayed for the operator to view/modify from the user interface. These include: setpoints, alarm limits, time delays, PID tuning constants, run-times, point statistics, schedules, and so forth.

h. The Operator Interface shall incorporate comprehensive support for functions including, but not necessarily limited to, the following:

◊ User access for selective information retrieval and control command execution ◊ Monitoring and reporting ◊ Alarm, non-normal, and return to normal condition annunciation ◊ Selective operator override and other control actions ◊ Information archiving, manipulation, formatting, display and reporting ◊ BMS internal performance supervision and diagnostics ◊ On-line access to user HELP menus ◊ On-line access to current BMS as-built records and documentation ◊ Means for the controlled re-programming, re-configuration of BMS operation and for the manipulation of BMS database information in compliance with the prevailing codes, approvals and regulations for individual BMS applications

i. The system shall support a list of application programs configured by the users that are called up by the following means:

◊ The Tools Menu ◊ Hyperlinks within the graphics displays ◊ Key sequences

j. The operation of the control system shall be independent of the user interface, which shall be used for operator communications only. Systems that rely on an operator workstation to provide supervisory control over controller execution of the sequences of operations or system communications shall not be acceptable.

2. Navigation Trees

a. The system will have the capability to display multiple navigation trees that will aid the operator in navigating throughout all systems and points connected. At minimum provide a tree that identifies all systems on the networks.

SECTION 23 81 00 PAGE 13

b. Provide the ability for the operator to add custom trees. The operator will be able to define any logical grouping of systems or points and arrange them on the tree in any order. It shall be possible to nest groups within other groups. Provide at minimum 5 levels of nesting.

c. The navigation trees shall be “dockable” to other displays in the user interface such as graphics. This means that the trees will appear as part of the display, but can be detached and then minimized to the Windows task bar or closed altogether. A simple keystroke will reattach the navigation to the primary display of the user interface.

3. Alarms

a. Alarms shall be routed directly from Network Automation Engines to PCs and servers. It shall be possible for specific alarms from specific points to be routed to specific PCs and servers. The alarm management portion of the user interface shall, at the minimum, provide the following functions:

◊ Log date and time of alarm occurrence.

◊ Generate a “Pop-Up” window, with audible alarm, informing a user that an alarm has been received.

◊ Allow a user, with the appropriate security level, to acknowledge, temporarily silence, or discard an alarm.

◊ Provide an audit trail on hard drive for alarms by recording user acknowledgment, deletion, or disabling of an alarm. The audit trail shall include the name of the user, the alarm, the action taken on the alarm, and a time/date stamp.

◊ Provide the ability to direct alarms to an e-mail address or alphanumeric pager. This must be provided in addition to the pop up window described above. Systems that use e-mail and pagers as the exclusive means of annunciating alarms are not acceptable.

◊ Any attribute of any object in the system may be designated to report an alarm.

b. The BMS shall annunciate diagnostic alarms indicating system failures and non-normal operating conditions.

c. The BMS shall allow a minimum of 4 categories of alarm sounds customizable through user defined wav.files.

d. The BMS shall annunciate application alarms at minimum, as required by Part 3.

4. Reports and Summaries

a. Reports and Summaries shall be generated and directed to the user interface displays, with subsequent assignment to printers, or disk. As a minimum, the system shall provide the following reports:

◊ All points in the BMS ◊ All points in each BMS application ◊ All points in a specific controller ◊ All points in a user-defined group of points ◊ All points currently in alarm ◊ All points locked out ◊ All BMS schedules ◊ All user defined and adjustable variables, schedules, interlocks and the like.

SECTION 23 81 00 PAGE 14

b. Summaries and Reports shall be accessible via standard UI functions and not dependent upon custom programming or user defined HTML pages.

c. Selection of a single menu item, tool bar item, or tool bar button shall print any displayed report or summary on the system printer for use as a building management and diagnostics tool.

d. The system shall allow for the creation of custom reports and queries via a standard web services XML interface and commercial off-the-shelf software such as Microsoft Access, Microsoft Excel, or Crystal Reports.

e. Provide the capability to view, command and modify large quantities of similar data in tailored summaries created online without the use of a secondary application like a spreadsheet. Summary definition shall allow up to seven user defined columns describing attributes to be displayed including custom column labels. Up to 100 rows per summary shall be supported. Summary viewing shall be available over the network using a standard Web browser.

f. Provide a focused set of reports that includes essential information required for effective management of energy resources within the facility.

Energy reports shall be configurable from predefined, preconfigured templates. Required includes but shall not be limited to:

Energy Overview Load Profile Simple Energy Cost Consumption Equipment Runtime Electrical Energy Energy Production

Reports shall be selectable by date, time, area and device. Each report shall include a color visual summary of essential energy information.

5. Schedules

a. A graphical display for time-of-day scheduling and override scheduling of building operations shall be provided. At a minimum, the following functions shall be provided:

◊ Weekly schedules ◊ Exception Schedules ◊ Monthly calendars

b. Weekly schedules shall be provided for each group of equipment with a specific time use schedule.

c. It shall be possible to define one or more exception schedules for each schedule including references to calendars

d. Monthly calendars shall be provided that allow for simplified scheduling of holidays and special days for a minimum of five years in advance.

Holidays and special days shall be user-selected with the pointing device or keyboard, and shall automatically reschedule equipment operation as previously defined on the exception schedules.

e. Changes to schedules made from the User Interface shall directly modify the Network Automation Engine schedule database.

f. Schedules and Calendars shall comply with ASHRAE SP135/2003 BACnet Standard.

SECTION 23 81 00 PAGE 15

g. Selection of a single menu item or tool bar button shall print any displayed schedule on the system printer for use as a building management and diagnostics tool.

h. Software shall be provided to configure and implement optimal start and stop programming based on existing indoor and outdoor environmental conditions as well as equipment operating history

6. Password

a. Multiple-level password access protection shall be provided to allow the user/manager to user interface control, display, and database manipulation capabilities deemed appropriate for each user, based on an assigned password.

b. Each user shall have the following: a user name (accept 24 characters minimum), a password (accept 12 characters minimum), and access levels.

c. The system shall allow each user to change his or her password at will.

d. When entering or editing passwords, the system shall not echo the actual characters for display on the monitor.

e. A minimum of five levels of access shall be supported individually or in any combination as follows:

◊ Level 1 = View Data ◊ Level 2 = Command ◊ Level 3 = Operator Overrides ◊ Level 4 = Database Modification ◊ Level 5 = Database Configuration ◊ Level 6 = All privileges, including Password Add/Modify

f. A minimum of 100 unique passwords shall be supported.

g. Operators shall be able to perform only those commands available for their respective passwords. Display of menu selections shall be limited to only those items defined for the access level of the password used to log-on.

h. The system shall automatically generate a report of log-on/log-off and system activity for each user. Any action that results in a change in the operation or configuration of the control system shall be recorded, including: modification of point values, schedules or history collection parameters, and all changes to the alarm management system, including the acknowledgment and deletion of alarms.

7. Screen Manager

a. The User Interface shall be provided with screen management capabilities that allow the user to activate, close, and simultaneously manipulate a minimum of 4 active display windows plus a network or user defined navigation tree.

8. Dynamic Color Graphics

a. The graphics application program shall be supplied as an integral part of the User Interface. Browser or Workstation applications that rely only upon HTML pages shall not be acceptable.

SECTION 23 81 00 PAGE 16

b. The graphics applications shall include a create/edit function and a runtime function. The system architecture shall support an unlimited number of graphics documents (graphic definition files) to be generated and executed.

The graphics shall be able to display and provide animation based on real-time data that is acquired, derived, or entered.

c. Graphics runtime functions – A maximum of 16 graphic applications shall be able to execute at any one time on a user interface or workstation with 4 visible to the user. Each graphic application shall be capable of the following functions:

◊ All graphics shall be fully scalable ◊ The graphics shall support a maintained aspect ratio.

◊ Multiple fonts shall be supported.

◊ Unique background shall be assignable on a per graphic basis.

◊ The color of all animations and values on displays shall indicate if the status of the object attribute.

d. Operation from graphics – It shall be possible to change values

(setpoints) and states in system controlled equipment by using drop-down windows accessible via the pointing device

e. Graphic editing tool – A graphic editing tool shall be provided that allows for the creation and editing of graphic files. The graphic editor shall be capable of performing/defining all animations, and defining all runtime binding.

◊ The graphic editing tool shall in general provide for the creation and positioning of point objects by dragging from tool bars or drop-downs and positioning where required.

◊ In addition, the graphic editing tool shall be able to add additional content to any graphic by importing backgrounds in the SVG, BMP or JPG file formats.

f. Aliasing – Many graphic displays representing part of a building and various building components are exact duplicates, with the exception that the various variables are bound to different field values. Consequently, it shall be possible to bind the value of a graphic display to aliases, as opposed to the physical field tags.

9. Historical trending and data collection

a. Each Automation Engine shall store trend and point history data for all analog and digital inputs and outputs, as follows:

◊ Any point, physical or calculated, may be designated for trending.

Three methods of collection shall be allowed:

Defined time interval Upon a change of value

◊ Each Automation Engine shall have the capability to store multiple samples for each physical point and software variable based upon available memory, including an individual sample time/date stamp.

Points may be assigned to multiple history trends with different collection parameters.

b. Trend and change of value data shall be stored within the engine and uploaded to a dedicated trend database or exported in a selectable data

SECTION 23 81 00 PAGE 17

format via a provided data export utility. Uploads to a dedicated database shall occur based upon one of the following: user-defined interval, manual command, or when the trend buffers are full. Exports shall be as requested by the user or on a time scheduled basis.

c. The system shall provide a configurable data storage subsystem for the collection of historical data. Data can be stored in either Microsoft Access or SQL database format.

10. Trend data viewing and analysis

a. Provide a trend viewing utility that shall have access to all database points.

b. It shall be possible to retrieve any historical database point for use in displays and reports by specifying the point name and associated trend name.

c. The trend viewing utility shall have the capability to define trend study displays to include multiple trends

d. Displays shall be able to be single or stacked graphs with on-line selectable display characteristics, such as ranging, color, and plot style.

e. Display magnitude and units shall both be selectable by the operator at any time without reconfiguring the processing or collection of data. This is a zoom capability.

f. Display magnitude shall automatically be scaled to show full graphic resolution of the data being displayed.

g. Trend studies shall be capable of calculating and displaying calculated variables including highest value, lowest value and time based accumulation.

h. The Display shall support the user’s ability to change colors, sample sizes, and types of markers.

11. Database Management

a. Where a separate SQL database is utilized for information storage the

System shall provide a Database Manager that separates the database monitoring and managing functions by supporting two separate windows.

b. Database secure access shall be accomplished using standard SQL authentication including the ability to access data for use outside of the Building Automation application.

c. The database managing function shall include summarized information on trend, alarm, event, and audit for the following database management actions:

◊ Backup ◊ Purge ◊ Restore

d. The Database Manager shall support four tabs:

◊ Statistics – shall display Database Server information and Trend, Alarm (Event), and Audit information on the Metasys Databases.

◊ Maintenance – shall provide an easy method of purging records from the Metasys Server trend, alarm (event), and audit databases by supporting separate screens for creating a backup prior to purging, selecting the database, and allowing for the retention of a selected number of day’s data.

SECTION 23 81 00 PAGE 18

◊ Backup – Shall provide the means to create a database backup file and select a storage location.

◊ Restore – shall provide a restricted means of restoring a database by requiring the user to log into an Expert Mode in order to view the Restore screen.

e. The Status Bar shall appear at the bottom of all Metasys Database Manager Tabs and shall provide information on the current database activity. The following icons shall be provided:

◊ Ready ◊ Purging Record from a database ◊ Action Failed ◊ Refreshing Statistics ◊ Restoring database ◊ Shrinking a database ◊ Backing up a database ◊ Resetting internet information Services ◊ Starting the Metasys Device Manager ◊ Shutting down the Metasys Device Manager ◊ Action successful

f. The Database Manager monitoring functions shall be accessed through the Monitoring Settings window and shall continuously read database information once the user has logged in.

g. The System shall provide user notification via taskbar icons and e-mail messages when a database value has exceeded a warning or alarm limit.

h. The Monitoring Settings window shall have the following sections:

◊ General – Shall allow the user to set and review scan intervals and start times.

◊ Email – Shall allow the user to create and review e-mail and phone text messages to be delivered when a Warning or Alarm is generated.

◊ Warning – shall allow the user to define the Warning limit parameters, set the Reminder Frequency, and link the e-mail message.

◊ Alarm – shall allow the user to define the Alarm limit parameters, set the Reminder Frequency, and link the e-mail message.

◊ Database login – Shall protect the system from unauthorized database manipulation by creating a Read Access and a Write Access for each of the Trend, Alarm (Event) and Audit databases as well as an Expert Mode required to restore a database.

i. The Monitoring Settings Taskbar shall provide the following informational icons:

◊ Normal – Indicates by color and size that all databases are within their limits.

◊ Warning - Indicates by color and size that one or more databases have exceeded their Warning limit.

◊ Alarm - Indicates by color and size that one or more databases have exceeded their Alarm limit.

j. The System shall provide user notification via Taskbar icons and e-mail messages when a database value has exceeded a warning or alarm limit.

12. Demand Limiting and Load Rolling

SECTION 23 81 00 PAGE 19

a. The System shall provide a Demand Limiting and Load Rolling program for the purpose of limiting peak energy usage and reducing overall energy consumption.

b. The System shall support both Sliding Window and Fixed Window methods of predicting demand.

c. The System shall support three levels of sensitivity in the Sliding Window demand calculations for fine tuning the system.

◊ Low Setting – Sheds loads later and over the shortest amount of time. Maximizes the time the equipment is on.

◊ Medium Setting – Sheds loads earlier over a longer amount of time than the Low Setting. Increases the time the equipment is on and decreases the probability of exceeding the Tariff Target over the Low Setting.

◊ High Setting – Sheds loads earlier over a longer amount of time than the Medium Setting. Minimizes the probability of exceeding the Tariff Target.

d. The System shall have both a Shed Mode and a Monitor Only Mode of operation.

◊ When the Shed Mode is engaged, the System shall actively control the Demand.

◊ When the Monitor Mode is engaged, the System will simulate the shedding action but will not take any action.

e. The Demand Limiting program shall monitor the energy consumption rate and compare it to a user defined Tariff Target. The system shall maintain consumption below the target by selectively shedding loads based upon a user defined strategy.

f. The Demand Limiting program shall be capable of supporting a minimum of 10 separate Load Priorities. Each load shall be user assigned to a Load Priority.

g. The Demand Limiting program shall be capable of supporting a minimum of 12 separate Tariff Targets defining the maximum allowed average power during the current interval.

h. The System shall support a Maximum Shed Time for each load as determined by the user. The system shall restore the load before the Maximum Shed time has expired.

i. The System shall support a Minimum Shed Time for each load as determined by the user. The system shall not restore the load sooner than the Minimum Shed Time has expired.

j. The System shall support a Minimum Release Time for each load as determined by the user. The System shall not shed the load until it has been off for the Minimum Release time.

k. The System shall support three user defined options if the meter goes unreliable.

◊ Shedding – The currently shed loads will be released as their

Maximum shed Times expire.

◊ Maintain the Current Shed Rate – The System will use the Demand

Limiting shed rate that was present when the meter went unreliable.

◊ Use Unreliable Meter Shed Rate – the system will control to a user defined Unreliable Shed Rate target.

SECTION 23 81 00 PAGE 20

l. The Load Rolling program shall sum the loads currently shed and compare it to a user defined Load Rolling Target. The system shall maintain consumption below the target by selectively shedding loads based upon a user defined Load Priority.

m. The Load Rolling program shall be capable of supporting a minimum of 10 separate Load Priorities. Each load shall be user assigned to a Load Priority.

n. The Load Rolling program shall be capable of supporting a minimum of 12 separate Tariff Targets defining the amount of power by which the demand must be reduced.

o. The System shall provide the user with a Load Tab that displays all of the Demand Limiting and Load Rolling parameters for any selected load.

p. The System shall provide the user with a Load Summary that displays all of the loads associated with the Demand Limiting and Load Rolling programs. Status Icons for each load shall indicate:

◊ Load is Offline ◊ Load is Disabled ◊ Load is Shed ◊ Load is Locked ◊ Load is in Comfort Override

q. The Load Summary shall include a Load Summary Runtime view listing the following load conditions:

◊ Load Priority ◊ Shed Strategy ◊ Load Rating ◊ Present Value ◊ Ineligibility Status ◊ Active Timer ◊ Time Remaining ◊ Last Shed Time

2.4 Network Automation Engines (NAE)

A. Network Automation Engine

1. The Network Automation Engine (NAE) shall be a fully user-programmable, supervisory controller. The NAE shall monitor the network of distributed application-specific controllers, provide global strategy and direction, and communicate on a peer-to-peer basis with other Network Automation Engines.

2. Automation network – The NAE shall reside on the automation network and shall support a subnet of system controllers.

3. User Interface – Each NAE shall have the ability to deliver a web based User Interface (UI) as previously described. All computers connected physically or virtually to the automation network shall have access to the web based UI.

a. The web based UI software shall be imbedded in the NAE. Systems that require a local copy of the system database on the user’s personal computer are not acceptable.

b. The NAE shall support up a minimum of four (4) concurrent users.

c. The web based user shall have the capability to access all system data through one NAE.

SECTION 23 81 00 PAGE 21

d. Remote users connected to the network through an Internet Service Provider (ISP) or telephone dial up shall also have total system access through one NAE.

e. Systems that require the user to address more than one NAE to access all system information are not acceptable.

f. The NAE shall have the capability of generating web based UI graphics.

The graphics capability shall be imbedded in the NAE.

g. Systems that support UI Graphics from a central database or require the graphics to reside on the user’s personal computer are not acceptable.

h. The web based UI shall support the following functions using a standard version of Microsoft Internet Explorer:

◊ Configuration ◊ Commissioning ◊ Data Archiving ◊ Monitoring ◊ Commanding ◊ System Diagnostics

i. Systems that require workstation software or modified web browsers are not acceptable.

j. The NAE shall allow temporary use of portable devices without interrupting the normal operation of permanently connected modems.

4. Processor – The NAE shall be microprocessor-based…