Description_of_Requirement.docx

DESCRIPTION OF REQUIREMENT

HVAC Monitoring Equipment WADS, Joint Base Lewis-McChord

CLIN 0001 - Required Equipment:

CLIN 0002 - Required Equipment:

· System Server

· Loaded with most current applicable server operating system; hardware compatible with Comm Squadron supported hardware; operating system meeting DISA STIG and patching requirements using AF Standard Server Configuration as the base configuration

· Loaded with most current applicable HVAC monitoring software application

· Hardware configuration for optimal operating and HVAC monitoring software

· Compatible with 21” rack space

· Console pullout drawer with monitor/keyboard/mouse

· Supplied by 100-240 volts A/C

· Redundant power supplies

· 3 yr warranty including application/software patching and upgrades

CLIN 0003 – Required Equipment:

· Desktop client computer

· Intel family CPU

· Windows 10 Pro operating system

· Dual monitors; 21” minimum, DVI and HDMI inputs

· Operating system based on AF Standard Desktop Configuration

· W/wireless/bluetooth capability disabled

· Minimum 16GB RAM

· 1 TB 7200RPM Hard Drive

· Minimum of four USB 3.0 ports

· CPU Pass Mark score 6250 or higher

· DVI display output with video Pass Mark score 750 or higher Internal DVD+/-RW dual layer drive

· High definition integrated audio

· Gigabit NIC

· Mouse

· Keyboard

· Supplied by 100-240 volts A/C

· 3yr warranty including application/software patching and upgrades

CLIN 0004 – Required Equipment:

· Ruggedized Laptop

· Intel-family CPU

· Windows 10 Pro operating system

· Wireless/Bluetooth capability disabled

· Minimum 16GB RAM

· 1 TB 7200RPM Hard Drive

· Minimum Two USB 3.0 ports

· CPU Pass Mark score 6250 or higher

· 13.3” 1050 NITS TFT LCD Display

· Internal DVD+/-RW dual layer drive

· VGA Connection

· HDMI Connection

· Gigabit NIC

· Mouse

· Keyboard

· Supplied by 100-240 volts A/C

· Docking Station

· 3yr warranty including application/software patching and upgrades

CLIN 0005 – Required Equipment:

· Network Switch

· Compatible with Comm Squadron-supported hardware

· Fully Managed with Port Security Configuration

· Minimum 24 Ethernet Ports

· Supplied by 100-240 volts A/C

· 3yr warranty

CLIN 0006 – Required Equipment:

CLIN 0007 – Required Equipment:

CLIN 0008 – Installation:

· Due to unique building layout and 24/7 mission, site highly recommends site survey prior to installation

· Install server and console drawer in rack

· Connect server to standalone network

· Configure HVAC monitoring software

· Establish communications with supervisor and unit controllers

· Must be hardened in accordance with Air Force standards

· Include documentation of hardware inventory, software inventory and configuration, and security features enabled or disabled

· Provide rack elevation and network drawings showing connection of all installed components

CLIN 0009 – Service Contract:

· 5 Year period of service

· Biannual preventative maintenance of server

· Install all applicable updates to operating system

· Install all applicable updates to HVAC monitoring software

· Provide updates to documentation of hardware inventory, software inventory and configuration, and security features enabled or disabled

· Provide updates to rack elevation and network drawings

· Correct all hardware and software server faults within 24 hours of notification

Minimum Essential Characteristics CLIN 0001:

1. The Building Management System (BMS) as provided shall incorporate, at minimum, the following integrated features, functions and services:

a. Operator information, alarm management and control functions.

b. Enterprise-level information and control access

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

d. Diagnostic monitoring and reporting of BMS functions

e. Offsite monitoring and management access

f. Energy management

g. Standard applications for terminal HVAC systems

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

3. The BMS shall consist of the following:

a. Standalone Supervisory Controller(s)

b. Field Equipment Controller(s)

c. Input/output module(s)

d. Local Display Device(s)

e. Portable Operator’s Terminal(s)

f. Distributed User Interface(s)

g. Network processing, data storage and communications equipment

4. The system shall be modular in nature, and shall permit expansion of both capacity and functionality through the addition of non-proprietary sensors and actuators.

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

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

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

6. Dedicated Web Based User Interface

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

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

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

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

- Alarm

- Trend

- Display

- Applications

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

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

- Online access to user Help menus

- Online access to current BMS as-built records and documentation

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

b. Provide the ability for the operator to add custom trees. The operator will be able to define any logical grouping of systems and points and arrange them on the tree in any order. It shall be possible to nest groups within other groups. Provide at minimum five 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. A simple key stroke will reattach the navigation to the primary display of the user interface.

8. Alarms

a. Alarms shall be routed directly from Supervisor Controller to PC’s and servers. It shall be possible for specific alarms from specific points to be routed to specific PC’s 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 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

- Configuration of which controller offline alarms are seen by each user

- 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 four categories of alarm sounds customizable through user defined .wav files

9. 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 user defined and adjustable variables, schedules, interlocks and the like

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

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

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

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

10. Access, Authorization, and Password Management

a. Roles may be copied and altered to meet specific roles and permissions based on the particular policies.

b. The system shall allow password changes only by a master administrative password

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

d. A maximum of 150 categories may be used to determine or assign areas of responsibilities to each user account. A maximum of 13 (of the 150) named categories which are specifics such as “No Access, View, Advanced Review, Operate, Intervene, Diagnostic, Manage Item Events, Manage Every, and Configure Items”

e. A minimum of 100 unique passwords shall be supported

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

g. Operators shall be further limited to only access, command, and modify those buildings, systems, and subsystems for which they have responsibility. Provide a minimum of 100 categories of systems to which individual operators may be assigned

h. The system shall automatically generate a report of logon/logoff 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

i. The system shall have the ability to provide a Department of Defense (DoD) specific warning banner for applicable sites that warns the user they are accessing a restricted site

j. After successful login to the Site Management Portal (SMP) the last time and date that user was previously logged in is shown on the screen

k. Each login attempt is recorded in the system audit log with the option to record the IP address of the PC that made the login

11. Screen Manager

a. The system will allow a customized image on the login screen (i.e. organization name, logo)

b. User view navigations can be displayed as either a set of tabs or a drop down list

c. Allows user preference for assigning of a background color for when an object is Out of Service which will enable the operator to quickly distinguish points that have been commanded to this state

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

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

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 (graphics 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 four 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 assigned on a per graphic basis

- The color of all animations and values on displays shall indicate the status of the object attribute

- Graphics that represent buildings or systems shall allow natural links and transitions between related detailed tabular views of data that complement the graphic

d. Operation from graphics – It shall be possible to change values (setpoints) and states in system controlled equipment directly from the graphic

e. Floor Plan graphics – The user interface shall provide non-proprietary graphic applications that summarize conditions on a floor. Floor plan graphics shall indicate thermal comfort using dynamic colors to represent zone temperature deviations from zone setpoint(s). Floor plan graphics shall display overall metrics for each zone in the floor

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

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

- The graphic editing tool shall provide a library of standard, non-proprietary, HVAC equipment, floor plan, lighting, security and network symbols

- The graphic editing tool shall provide for the creation and positioning of library symbols by dragging from tool bars or drop downs and positioning where required

- The graphic editing tool shall permit the importing of AutoCAD drawings for use in the system

- The graphic editing tool shall be able to add additional content to any graphic by importing images in the SVG, PNG or JPG file formats

Minimum Essential Characteristics CLIN 0002:

Must meet minimum essential requirements in description

Minimum Essential Characteristics CLIN 0003:

1. All points of user interface shall be on standard, non-proprietary, PC’s that do not require the purchase of and special software from the Building Management System (BMS) manufacturer. The primary point of interface on these PC’s will be a standard, non-proprietary, web browser.

Minimum Essential Characteristics CLIN 0004:

Must meet minimum essential requirements in description

Minimum Essential Characteristics CLIN 0005:

Must meet minimum essential requirements in description

Minimum Essential Characteristics CLIN 0006:

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

2. All controllers shall reside on the automation network.

3. Control networks shall provide either peer-to-peer, master slave, or token passing communications, and shall operate at a minimum communications speed of 9600 baud.

4. DDC controllers shall reside on the control network

5. Control network communications protocol shall be BACnet standard MS/TP Bus protocol ASHRAE SSPC-135

6. A BACnet Protocol Implementation Conformance Statement (PICS) shall be provided for each controller device that will communicate on the BACnet MS/TP Bus.

7. All controllers are programmable controllers that can communicate using BACnet/IP, MSTP, or N2 communications protocols.

8. Standalone controllers in applications that do not require a networked supervisory device or for network applications where it is preferred to have the scheduling, alarming, and/or trending performed locally in the field controllers.

9. Must utilize TGP type programming with real-time run data.

10. Universal input

a. Analog Input, Voltage mode, 0-10 VDC

b. Analog Input, Current mode, 4-20 mA

c. Analog Input, Resistive Mode, 0-2k ohm, RTD

d. Binary Input, Dry Contact Maintained Mode

11. Analog Output

a. Analog Output, Voltage mode, 0-10 VDC

b. Analog Output, Current mode, 4-20 mA

c. Binary Output, 24VAC Triac

Minimum Essential Characteristics CLIN 0007:

1. BACnet/IP communications,

2. Two Ethernet ports minimum

3. 10 Universal inputs

a. Analog Input, Voltage mode, 0-10 VDC

b. Analog Input, Current mode, 4-20 mA

c. Analog Input, Resistive Mode, 0-2k ohm, RTD

d. 6 Binary Inputs, Dry Contact Maintained Mode

4. 4 Analog Outputs

a. Analog Output, Voltage mode, 0-10 VDC

b. Analog Output, Current mode, 4-20 mA

c. 4 Binary Outputs, 24VAC Triac

5. 4 Configurable Outputs

a. Analog Output, Voltage mode, 0-10 VDC

b. Binary Output Mode, 24VAC Triac

6. Integral Real-time Clock

Minimum Essential Characteristics CLIN 0008:

1. The BMS installer shall be a BMS manufacturer owned branch office, who is factory trained and authorized by the BMS manufacturer to sell, service and support the BMS specified herein

2. The BMS contractor shall provide the following training services:

a. One day of onsite orientation by a system technician who is fully knowledgeable of the specific installation details of the project. This orientation shall, at a minimum, consist of a review of the project as-built drawings, the BMS software layout and naming conventions, and a walk through of the facility to identify panel and device locations

b. Half day orientation of the security features designed into the system, password and account management, system logging capabilities, and a review of the documentation of hardware inventory, software inventory and configuration, and security features

3. Fully commission all aspects of the Building Management System work

4. Acceptance Check Sheet

a. Prepare a check sheet that includes all points for all functions of the BMS as indicated on the point list included in this specification

b. Prepare a security engineering plan for the system

c. Submit the check sheet and security plan to the Engineer for approval

d. The Engineer will use the check sheet and security engineering plan as the basis for acceptance with the BMS Contractor

Minimum Essential Characteristics CLIN 0009:

1. The BMS contractor shall have the ability to provide complete maintenance and support services within 24 hours of notification.

*Note: Products must meet the minimum essential characteristics to be considered technically acceptable. Additionally, all brands listed are for reference only – “equal” products will be considered.