BID_S-24-25_CPSC_AND_CAS_SERVER_UPGRADES.pdf

City of Cheyenne / Bid S-24-25 / Server Upgrades

CITY OF CHEYENNE / BID S-24-25 / HVAC AND MECHANICAL SYSTEMS MAINTENANCE

CHEYENNE PUBLIC SAFETY CENTER AND CHEYENNE AQUATIC CENTER

JOHNSON CONTROLS SERVER (SOFTWARE AND HARDWARE) UPGRADES

Upgrade the existing Johnson Controls server (Both software and hardware), network engines and graphics user interface at City of Cheyenne Public Safety and City of Cheyenne Aquatic Center to meet current IT security standards. Upgrade discontinued

Microsoft Silverlight graphics to HTTML graphics with functionality as described below (Graphical User Interface). Provide a software subscription for the upgraded Johnson Controls ADS or ADX server software equal to the term of the service contract to assure IT security. Upgrade Network Engines with hardware and software as described below. The contractor must Field verify quantity and capacity of existing network engines and replace with most current hardware and software including the same quantity and DDC point capacity as existing at City of Cheyenne Public Safety and City of Cheyenne Aquatic Center. The successful contractor will also be required to monitor the new Network Engine currently under contract to be installed\replaced to meet these specifications at Cheyenne Botanical Gardens. New Johnson Controls ADS or ADX Server Hardware shall be as specified below.

Maintain communication with existing customer User interface PCs. The owner will be responsible for upgrading browser software to the current version on existing customer interface PCs. Contractor to field verify existing conditions after award and advise customer if upgrades to Microsoft Edge or Google Crome are required.

Graphical User Interface

1. Dedicated Web Based User Interface

a. The BMS Contractor shall provide and install a personal computer for command entry, information management, network alarm management, and database management functions. Real-time control functions, including scheduling, history collection and alarming, shall be resident in the

BMS Network Engines and Data Server to facilitate greater fault tolerance and reliability.

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

i.Edge or Google Chrome or Safari for user interface functions.

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

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

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

c. PC Hardware/Software – The personal computer(s) shall be configured as specified in the

Computing Hardware and Software section.

d. Provide one operational device as herein specified and located on plans.

2. Mobile, Web Based, User Interface (MUI)

a. General i.All functionality as outlined within this section shall be provided as a standard catalog product software suite from the BMS manufacturer. Custom functionality development to meet these requirements is not acceptable.

ii.The mobile, web-based, user interface shall be HTML5-compliant and provide access to the system from smartphones, tablets, portable and desktop computers. User Interfaces that require software installation on the client device (e.g. Java, MicrosoftSilverlight®, Adobe® Flash®), or software downloads from an online app store shall not be acceptable for these purposes.

iii.The mobile user interface shall provide system operators with a simple space/zone/location-based navigation approach to finding information, including the ability to search for any location by name and to bookmark a location in a standard browser.

iv.The mobile user interface shall organize and display information using customer specific locations and spaces. At a minimum, the user interface shall provide:

• Organization of all space, equipment and point information in a familiar way (using standard equipment names and location descriptions), reducing the need for extensive training prior to use.

• A navigation mechanism or tree for users to select the specific location or space for accessing information – only spaces and locations in the navigation tree or equipment serving that space, nothing more.

• The ability to search for and/or bookmark any location, space, or equipment by name for quick access to critical or troublesome areas.

• Application of the same navigation mechanisms across any client device (e.g. Smart phone, tablet, personal computer) for consistency and ease of use.

v.The same user interface elements shall be accessible from any type of personal computer or mobile device running any type of operating system supported (e.g. iOS, Android, Windows®). It shall automatically adapt and optimize the display for the screen size and touch screen navigation.

b. Navigation Trees i.A dedicated location based navigation tree shall be provided as part of the user interface in order to navigate to specific places within the facility on a hierarchical basis (typ. Campus, Facility, Building, Wing, Floor, Room.)

ii.The location-based tree shall use place names familiar to the operator without training or familiarization regarding special codes and conventions utilized in the generation of the

BMS.

iii.Clicking or tapping on a location name in the tree shall display the home page associated with the space and simultaneously expand the tree to display the next level of spaces below the one selected.

iv.Provide a means for qualified users to view an all hardware items navigation tree of devices connected to the BMS network in order to enable troubleshooting of equipment and communications.

v.A click or tap on a device in the network tree shall display a dashboard for that device including information regarding related equipment and access to a separate focus view of commandable points associated with the piece of hardware. A click or tap on such a point shall display a control dialogue box allowing the user to modify or command that point as indicated. The dialog box shall contain an annotation box for describing why the action was taken or special circumstances that apply.

vi.Specific hardware and software types in the Network tree shall also include access to one or more the following views in their dashboard depending on hardware type or network element (e.g. MS/TP trunk):

• Summary View

• Diagnostic View

• Network View

• Trend View vii.Provide a means to hide the Network Tree and return to the Spaces Tree at any time by clicking on the Spaces Icon above the tree.

viii.Provide a means to restrict user access to any space in the Spaces Tree and thereby prevent manipulation of equipment associated with the space.

c. Dashboard Displays i.The user interface shall provide the ability to view equipment visualizations, floor plans, and/or other graphics on mobile or desktop client devices in a browser environment, without the need for additional plugins or software. Graphics shall be accessible via a space

(for floorplans, campus maps, etc.) or equipment dashboard.

ii.Standard dashboards shall be configured for each defined space including one of the following predefined or custom elements:

• Equipment Serving Space

• Potential Problem Areas

• Equipment Summary

• Graphic Display (if specified)

• Schedule iii.Standard dashboards shall be configured for each system or device (typ. mechanical or electrical equipment) including the following predefined or custom elements:

• Trend

• Equipment Activity Summary

• Equipment Relationships Summary

• Equipment Data

• Graphic Display

• Schedule iv.Users with appropriate permissions shall have access to a Dashboards Manager that can change the display order of Summaries and Data elements, add or remove elements and apply custom dashboards layouts to equipment and space by type.

v.Dashboard Manager shall apply dashboards to spaces or equipment based on the viewing platform (Desktop/Tablet or Phone) in order to tailor the user experience to the needs of the specific user base.

vi.Default dashboard displays by space and equipment type shall be created per the guidelines in this specification or by mutual agreement with the Owner’s representative.

d. Alarm Management i.The user interface shall provide a single display of all potential issues in a facility including items currently in alarm, warning, override, out-of-service and offline.

ii.The user interface shall provide notification of new alarms, visually and audibly.

iii.The user interface shall provide the ability to view a summary of alarms, including a chart of the number of alarms in each of the defined alarm priority ranges. The priority ranges should be filterable.

iv.The user interface shall provide the capability to view multiple occurrences of the same alarm, ultimately providing the ability to acknowledge or discard all occurrences of the alarm in a single action.

v.The user interface shall provide the capability to view, and filter on, all alarms present in a well-defined mechanical system using the equipment serving equipment relationships.

vi.The user interface shall provide the capability to acknowledge and discard all occurrences of at least 1000 alarms in one operation.

vii.The user interface shall provide the user with the understanding of what physical space is being affected when an alarm occurs. The user interface shall provide the ability to filter alarms by physical space affected when the alarm occurred.

viii.The user interface shall provide the capability to monitor alarms 24/7 without requiring an active login to the system, accessible via segregated web page. The user interface shall provide the capability to enabled or disable the 24/7 alarm monitor mode if desired.

ix.The user interface shall provide the capability to annotate alarms using a pre-defined selection list or by providing custom text.

x.The user interface shall provide the capability to filter down alarm list and bookmark the filtered list, allowing automatic filtering to be applied when the bookmark is accessed.

xi.Provide a means to export a .csv or .pdf copy of the currently displayed alarm list.

xii.Provide a means to set up an alarm escalation feature. If an alarm is not acknowledged or discarded by recipients within a user-selected time, the alarm shall be escalated to an additional set of recipients.

e. Send Announcement i.Administrative users should have the ability to alert staff of planned outages in advance. The communication avenues should include:

• Email

• A message shown on the login screen

• A banner shown to logged in users

f. Equipment Activity Summary i.The user interface shall provide a filterable, single display, of all activity related to a specific piece of equipment including user changes, discarded user changes, pending alarms, discarded alarms, and acknowledged alarms for at least one year of historical data.

ii.Items shall be listed in timed order with the latest activity at the top of the list.

iii.Filters shall allow only specific activities for specific data points occurring within a specific time and date window to be displayed.

iv.Provide a means to export a .csv copy of the currently displayed summary by clicking or tapping on the export icon.

v.Provide a means to create a custom trend graph containing the data shown in the currently displayed summary by tapping or clicking on the trend icon in the header bar and selecting the specific points to trend in the resulting selection panel.

vi.Clicking on the information icon in front of any displayed activity listed in the summary shall expand the display to include the name of the user, server time, value prior to the activity, the ability to annotate the activity and a user selectable icon for displaying a trend graph of the point.

g. Equipment Relationships Summary i.The user interface shall provide a summary of all equipment and spaces related to the operation of the system or device currently selected for viewing.

ii.The user interface shall include the capability to navigate to the home page of any related piece of equipment or space with a single click or tap on the desired element.

h. Equipment Data Summary i.The user interface shall provide a summary of all data pertaining to a particular piece of mechanical or electrical equipment in a tabular format. Clicking or tapping on any value in the summary shall display a related command panel allowing the user to command, override, or change service condition of the point selected and to annotate such actions for future reference.

ii.Provide a means to export a .pdf copy of the report with a single click on the associated export icon.

i. Equipment Serving Space Summary i.The user interface shall provide a summary of all mechanical and electrical equipment as defined in the points list that serves a selected space from the navigation tree.

ii.The summary shall be capable of including a subset of the viewable points for each system representing the key elements of interest to operators without subjecting them to long lists of points irrelevant to basic operation.

iii.Clicking or tapping on any item in the summary shall navigate to the item’s assigned home page in the user interface.

iv.Provide a means to view a custom trend of information contained in the summary with a single click of the trend icon residing in the title header.

v.Provide a means to display specific systems and points by filtering equipment types desired.

vi.Because the data is intended to be a snapshot of the current conditions in the space it shall not dynamically update but a click or tap on the update icon at any time performs that function.

j. Potential Problem Areas Summary i.The user interface shall provide a summary of all points in the system related to the space that are not operating correctly (e.g. alarm, off normal or not communicating correctly) in order to provide the operator with a quick update on current conditions.

ii.The information shall include:

• Point status (via color)

• Point name

• Value of the point when the summary was taken

• Equipment that contains the offending point

• Space that is served by that equipment iii.Data points in the summary may be filtered by one or more types of off-normal condition

(e.g. above setpoint, offline and overridden).

iv.The summary may be exported in .csv format for inclusion in spreadsheets or other documents.

k. Equipment Summary i.The user interface shall provide a summary that allows the user to compare all similar equipment that serves the space as well as downstream (child) spaces in order to evaluate conditions quickly and determine patterns for troubleshooting purposes.

ii.Each unique equipment type shall be selectable and display a representative set of values along with the space(s) being served by the device. Equipment types can be selected from a dropdown menu in the summary.

iii.Clicking or tapping on a selected device in the summary shall navigate to the home page for that piece of equipment while clicking or tapping a data point shall display the command panel for that point.

iv.Provide a means to export a .pdf copy of the currently displayed summary by clicking or tapping on the export icon.

v.Provide a means to create a custom trend graph containing the data shown in the currently displayed summary by clicking on the trend icon in the header bar and selecting the specific points to trend in the resulting selection panel.

vi.Provide a means to sort data within the summary by clicking on the desired column heading, allowing to sort from lowest to highest value or vice versa.

vii.Provide a means to edit the column types and column order within the summary to provide relevant information in accordance with Operators’ preferences.

viii.Provide a means to link to an advanced search and reporting function directly from the

Equipment Summary that will pre-populate the advanced report with the data from the

Equipment Summary.

l. User Defined Summaries i.Provide the capability to view, command, and modify large quantities of similar data in summaries without the use of a secondary application (e.g. a spreadsheet). These summaries shall be generated automatically or user defined.

m. Trend i.The user interface shall provide the capability to view historical trend data from multiple pieces of equipment in both bar and line formats.

ii.The user shall have the ability to navigate to a selection list of frequently viewed trends.

iii.Trend graphs shall have to ability to be smartly auto-generated based on equipment and space relationships.

iv. The user shall have the ability to view up to 3 graphs of differing units of measurement in a single screen and select which data points to plot on each to help with readability.

v.Each graph shall include a dedicated selection icon to export a copy of the graphic and data in .pdf format or the data only as a .csv file.

vi.Trend graphs shall allow the plotting of non-trended point’s default values.

vii.The user shall have the ability to add any trended to point a custom trend graph.

viii.The user shall have the ability to save trend graphs for reference later.

ix.The user shall be able to specify the duration of time and aggregation period for each trend line.

x.The user shall have the ability to decide whether to show raw or aggregate trend data.

n. Operator Access i.The user interface shall provide the ability to segment access to building data based on the space(s) or location(s) the user is physically located in and/or manages. The user interface shall provide the capability to assign “inherited” space permissions and the ability to assign user’s space based access in bulk.

ii.The user interface shall provide the ability to segment access to building data based on the space(s) or location(s) the user is physically located in and/or manages. The user interface shall provide the capability to assign “inherited” space permissions and the ability to assign user’s space based access in bulk.

o. Graphics i.The user interface shall display an equipment visualization or graphic within the context of its associated space (building, floor, room, etc.) or equipment dashboard.

ii.Graphics shall include the ability to define individual information layers for operator selection in order to clarify systems status and simplify operation on mobile devices. Where desired a master layer may be defined to include important information about the facility on all graphic screens.

iii.Graphics shall support the use of photo-realistic symbols as well as color change and animation to match the status of the related system control point.

iv.Provide a means to export a time stamped .pdf file of the graphic being viewed in order to communicate the current conditions in the space or the equipment being viewed and to provide a historic record.

v.An integral graphic manager shall be provided including the following features and capabilities:

• Creation and modification of graphics from any HTML5 capable browser without the need for additional plug-ins or software packages.

• Access to a full suite of pre-defined templates for air and water sourced

HVAC applications as well as the ability to add custom templates as created for other use. Pre-aliased graphic templates may be defined and saved for repetitive representations of common mechanical and electrical equipment.

• A full suite of pre-defined three dimensional symbols for mechanical and electrical systems as well as all line, text and shape tools required for integration into a graphic with zoom and pan capabilities on multiple platforms and in multiple browsers.

• The ability to search and replace items in multiple graphics with a single command.

• The ability to import and insert photos and images into the graphic.

• The ability of the graphics manager to create and edit graphics including the ability to bind graphic elements to the values and conditions of system points in both an on-line and off-line mode.

• The ability to create and import custom SVG symbols that can be selectable from the graphical palette and rendered at runtime.

vi.As required, the BMS Contractor shall provide software licenses in the name of the owner for programming, configuration and graphics building tools to allow designated representatives to make changes, modifications or additions to the system. While future updates or revisions may require an update fee, the owner shall incur no additional cost if they choose not to update. Systems that require any annual or time-limited licensing fees shall not be permitted.

p. Scheduling i.The user interface shall provide the capability to display, in a singular view, all of the effective schedules in the context of the space (building/floor/room, etc.) or equipment that the schedule effects. The software should have the ability to display an effective schedule, for the present, or a future date.

ii.The user interface shall provide a report of all schedules affecting a space or equipment.

The report shall provide the user details of events that comprise the weekly schedule and exception schedule(s). The report shall provide a means of viewing individual breakout scheduling elements for Weekly Schedule, Exceptions and Default Commands.

iii.The user interface shall provide the capability to efficiently change or modify schedules in mass quantities. This includes the capability to add, in bulk, exceptions to schedules, in addition to assigning, in bulk, weekly schedules.

q. Command and Control i.Provide a means to command system analog and binary points via a dropdown menu accessed by clicking or tapping on the value shown in any equipment summary or graphic display and completing the task in the resultant menu including an optional annotation.

ii.Commanding multiple points shall be possible on displays where multiple like system elements can be chosen.

iii.The user interface shall support users adding notes on their commands.

iv.The user interface shall support a choice of either permanent or temporary commands.

r. Cyber Health Dashboard i.The Cyber Health Dashboard shall provide a centralized view of potential cybersecurity related issues or system issues, grouped into critical issues, potential risks, and informational items.

ii.The Cyber Health Dashboard shall identify user account information, including:

a. Total number of users

b. Dormant users

c. Active users

d. Locked users

e. Temporary users

f. Disabled users

g. Users with Administrator role

h. Policy related information iii.The Cyber Health Dashboard shall indicate out-of-date software.

iv.The Cyber Health Dashboard shall identify when security certificates are set to expire.

v.The Cyber Healthy Dashboard shall provide insight into user activity such as number of successful logins, unsuccessful logins, and locked out accounts.

s. Involvement i.The user interface shall provide in a single screen, a way to visualize all interactions (I.e. -commands, writes, references) with a single object.

ii.The interface shall provide the ability to filter out any interactions (i.e. commands, writes, references) that are not pertinent.

iii.The user interface shall allow seamless navigation between one object’s Involvement view to another object’s.

t. System-level Activity i.The user interface shall provide a timeline view of all audits that occur in the system, including:

a. Logins attempts with user specified

b. Add, delete, modification of objects

c. Commands

u. Search i.Typing a text string in the Search box shall display a list of all occurrences of that string in the mobile user interface. When a string is represented in the description of a space or network element, selecting it shall display its default dashboard.

ii.Clicking or tapping on the Advanced Search Icon shall display the Advanced Search dialog box permitting the following:

• Search by Space and Equipment, Equipment Definition or Network

Reference

• Filter the search by wildcard name or object type

• Multi-selection of objects for commanding or the creation of reports including Trend, Alarm, Audit and Activity for a specific period of time

• Creation of reports in PDF or CSV formats which can be instantaneously downloaded or emailed, or scheduled to be sent at Operator-selected intervals (daily/weekly/monthly)

Network Engine General

a. The Network Engine shall be a fully user-programmable, supervisory controller. The

Network Engine(s) shall monitor the network of distributed equipment controllers, provide global strategy and direction, and communicate on a peer-to-peer basis with other Network Engine(s).

b. Automation network – The Network Engine(s) shall reside on the automation network and shall support a subnet of system controllers.

d. User Interface – Each Network Engine shall have the ability to deliver a web-based User

Interface. All computers connected physically or virtually to the automation network shall have access to the web-based user interface.

e. Processor – The Network Engine(s) shall be microprocessor-based with a minimum word size of 32 bits. The Network Engine(s) shall be a multi-tasking, multi-user, and real-time digital control processor. Standard operating systems shall be employed. Network Engine(s) size and capability shall be sufficient to fully meet the requirements of this Specification.

f. Memory – Each Network Engine shall have sufficient memory to support its own operating system, databases, and control programs, and to provide supervisory control for all control level devices.

g. The Network Engine(s) shall prevent malicious or unauthorized software applications from loading during the system startup process.

h. The Network Engine shall provide the capability to download a new image and database to a network engine while the engine is still running and controlling the building.

i. User Authentication – The Network Engine(s) shall support local user authentication.

j. Password Security – Access to the Network Engines’ embedded user interface shall require a password of 8 to 50 characters including a minimum of one lower case letter, one upper case letter, one number, and one special character. An alarm shall be generated after three unsuccessful attempts within 15 minutes, and the user shall be denied access until permission is renewed by a system administrator.

k. Network Security – Communication between the Network Engine and other system networked devices including additional Network Engines, Application and Data Servers, Open Data

Servers (BACnet listed OWS), and user interface clients shall be encrypted and support HTTPS with

Transport Level Security (TLS) Version 1.2. Self-signed certificates are to be provided with the option of configuring trusted certificates.

l. Hardware Real Time Clock – The Network Engine(s) shall include an integrated, hardware-based, real-time clock, with a supercapacitor to maintain time for a minimum of 72 hours during a power loss. Controllers using a battery to maintain time during a power loss shall not be acceptable.

m. Diagnostics – The Network Engine(s) shall continuously perform self-diagnostics, communication diagnosis, and diagnosis of all panel components. The Network Engine(s) shall provide both local and remote annunciation of any detected component failures or repeated failures to establish communication.

n. Power Failure – In the event of the loss of normal power, the Network Engine(s) shall continue to operate for a user adjustable period of up to 10 minutes after which there shall be an orderly shutdown of all programs to prevent the loss of database or operating system software.

i.During a loss of normal power, the control sequences shall go to the normal system shutdown conditions. All critical configuration data shall be saved into Flash memory.

ii.Upon restoration of normal power and after a minimum off-time delay, the controller shall automatically resume full operation without manual intervention through a normal soft-start sequence.

o. Certification – The Network Engine(s) shall meet and be listed to the UL 916 Standard for

Energy Management Equipment and be FCC Compliant to CFR47, Part 15, Subpart B, Class A.

p. Device Integration – The Network Engine(s) shall support integrating networked devices using the following communication protocols on the device/controller network:

i.Primary protocol support: The Network Engine(s) shall support BACnet Standard MS/TP

Bus Protocol ASHRAE SSPC-135 on the controller network.

• The Network Engine(s) shall support Remote Field Bus integration via a BACnet IP to MS/TP router.

• The Network Engine(s) shall be tested and BTL listed/certified as a

BACnet Building Controller (B-BC).

• A BACnet Protocol Implementation Conformance Statement shall be provided for the Network Engine(s).

ii.The Network Engine(s) shall optionally support integration of networked devices using the following networking protocols:

• Johnson Controls N2 or third party N2 Open devices.

• LonTalk

• MODBUS RTU

• MODBUS TCP

• KNX

• M-Bus

• OPC UA

q. The Network Engine(s) shall include multi-color, flashing LEDs to indicate important operating conditions and status such as heartbeat, fault, Ethernet activity, Ethernet comm speed, site director status, BACnet IP message communication status, USB port usage, Control network usage.

r. The Network Engine shall support up to 50, 100 or 200 supervised devices across all supported integrations via flexible sizing options. Provide 20% spare capacity within installed engines for future addition of supervised devices.

s. Communications Ports – The Network Engine(s) shall provide the following ports for connecting networkable devices i.Two (2) USB ports ii.One (1) or Two (2) RS-485 ports iii.One (1) Ethernet port

t. Provide Johnson Controls SNE10501, SNE11001 or SNE22001 or approved equal.

Johnson Controls ADS or ADX Server Hardware

1. Application and Data Server Application and Data Server (ADS)

a. One Application and Data Server shall be provided for this project to upgrade existing to current IT security standards. Provide server hardware platform recommended by Manufacturer meeting current IT security standards. .

b. The Application and Data Server shall be a software and hardware solution designed to manage the collection and presentation of the user interface, large amounts of trend data, event messages, operator transactions, and system configuration data on the BMS.

c. The Application and Data Server shall act as site director for consolidating BMS information from Network Engines for integrated storage and presentation. The ADS shall not restrict access to the individual Network Engines ensuring optimal BMS accessibility in the event of individual component failure or a loss of communication.

d. The Application and Data Server shall act as a server for the following functionality as described in these specifications:

• Mobile user interface providing user friendly access to system information via site navigation by place or device.

• Site Management Portal functions and applications.

• System Configuration Tool controller configuration and programming.

e. Network Security – Communication between the Network Engines, Application and Data

Server, and user interface clients shall be encrypted and support HTTPS with Transport Level

Security (TLS) Version 1.2. Self-signed certificates are to be provided with the option of configuring trusted certificates. The Application and Data Server shall be capable of supporting up to 5 to 10 simultaneous users via Web client access to match existing server capacity.

b. Supported Web Client operating systems:

i.Microsoft Windows 7, 8.1, 10 (Professional, Enterprise, Ultimate, Anniversary.)

ii.Apple OS X 10.8, 10.9, 10.10, 10.11.

c. Supported Web Browsers:

i.Google Chrome ii.Microsoft Internet Explorer 11 iii.Microsoft Edge iv.Apple Safari 11 or later

d. User Authentication – The Application and Data Server shall support local, Active

Directory, and Microsoft 365 authentication.

e. Computer shall be configured as specified in the Computing Hardware and Software section of this specification.

f. Provide Johnson Controls MS-ADS MS-ADX to replace\upgrade existing server.