2.2.1A Comfortview Single-User Software Guide Specifications

2.2.1A Comfortview Single-User Software Guide Specifications

Operator Interfaces (Field Installed)

ComfortVIEWTMSingle User Software

OperatorInterface (Single Terminal) - Guide Specifications (Controls)

2.2Operator Interface Software, Single Terminal

2.2.1Operating Software:
Multi-tasking, single user operating software shall be provided for the operators station, as shown in the contract documents. The vendor shall provide all required software, including the database. The PC shall be capable of running Either Windows 2000, or XP Professional operating system. All new PCs shall include Windows 2000, or XP operating software.

2.2.1.1Passwords:
The proposed system shall be capable of supporting a minimum of 100 unique operator Energy Management System (EMS) passwords. Each operator shall be assigned an access level. Each access level shall be customized to include the required control functions from the menu of all available functions (i.e., view only, force and auto points). Each operator’s access level shall be further customized based on an assignment of control exceptions for each area (i.e., full access in one building, view only access in another, and custom programming in another).

2.2.1.2Operator Interface:
The proposed system shall include screens with standard windows format, commands, menu conventions, and dialog boxes. The operator shall have access to a full array of help displays to assist while on-line, including context sensitive on-line help, based on the current cursor position. The Program Manager shall include a separate group icon for access into the EMS system with Program Item icons for access to an Alarm Manager, Network Manager, Reports, Graphic/Plot Display Manager, Log in/out, and EMS set-up.
The operator (if allowed by password) shall be capable of forcing/autoing of EMS points based on a pre-defined schedule setup by the operator.

2.2.1.3Wizards:
The proposed system shall include Help Wizards to assist an inexperienced operator.
Help Wizards shall be provided, as a minimum, for the following operator functions:

  • Reports
  • Alarms
  • Trends
  • ViewSPACE Databoxes
  • Operator Profiles
  • Network Manager:
    A Network Manager shall graphically display the EMS system, through the use of a directory with a branching structure, similar to the windows file manager. A double click on a network willexpand the directory tree and display the areas that make up the network. A double-click on an area shall display the list of controllers, then another double-click of a controller shall display the controller’s tables (status, maintenance, configuration, and service). A double-click of the controller’s table will result in dynamic updating of applicable values (i.e., point value displays, maintenance values, service information). All system operations shall allow penetration to any system operation by the operator if allowed by password. This shall allow the operator to penetrate to any desired system operation through the use of a hierarchy plan of system graphics or displays.
    The Network Manager shall also provide the main interface into the EMS networks. The following functions shall be provided as a minimum:
  • System and Point configuration
  • Custom unit assignment and generation
  • Viewing, forcing, or autoing of point status displays and maintenance tables
  • Assigning/removing controllers to different areas
  • Modification/copying of table values using DRAG and DROP Windows feature
  • Ability to create or modify a controller’s name and description
  • Copying and verifying controller configuration
  • Downloads/uploads and copying of database including batch uploadsand downloads
  • Assigning/modification of operators, operator profiles, and alarm filter and indication preferences
  • Dynamic Data Exchange (DDE) or equivalent, of controller point values tothird party software
    Point display screens shall include diagnostic information such as; point description, value, units, point status, force status, and an operator entered note for each EMS point. The operator shall be able to sort the controllers list based on address, sort key, or name.
  • Global Function Manager:
    A Global Function Manager shall be provided with the EMS software to allow operator(s) the ability to perform global functions, if allowed by their operator profile. When the operator selects the Global Function Manager, they shall be presented with the following global programs, to select from:
  • Timed Force W/Auto
  • Central Time Schedules
  • Point Transfer/Broadcast

A.Timed Force w/Auto
The proposed system shall allow the operator(s), if allowed by their operator profiles, to automatically “FORCE” and “AUTO” one or a group of points (any combination of different point types) based on a user specified time.Each group shall include a dialog box that lists all of the applicable points (including name and location), group name, force and auto time, force level, and the value of the force.The system shall support at least 300 separate force groups, as a minimum. A Force group dialog box shall include buttons for new, modifying, or deleting points.
The system shall automatically log all success and failures in the System Activity report. If a force or AUTO command fails to be acknowledged ComfortView shall initiate an alarm.

B.Global Occupancy
In addition to the stand-alone time scheduling capability specified for each system element, the systems shall provide the capability for a Global Occupancy Time Schedule program. The master time schedules shall replace the local time schedules. The global time schedules shall be provided to allow the operator to quickly and easily override the master time schedules. The global occupancy schedules shall be automatically downloaded to the applicable system elements once a day or the operator may download at any time. Each master time schedule shall be linked to 366 override schedules (one for each day of the year), as required. If the master schedule determines that an override is required the master schedule will be overridden by the override schedule.

C.Central Point Transfer
The proposed system shall include the inherent capability to provide for the transfer of point values from one system element to another regardless if it is on a primary or secondary bus. When creating or modifying, the operator shall have the capability to select a SPEEDY ENTRY selection to speed and ease the task of configuration.
A point transfer dialog box shall display the read from and write to point names, addresses of the points, the frequency of the transfer, and the status of the last attempt.

2.2.1.6Alarm Manager
The Alarm Manager allows, through the selection of an icon, operator access tosystem alarms associated with the signed on operator(s) profile. The proposed system shall include thecapability to route alarms to specific EMS operators. Alarm filters shall be capable of routing alarms based on families (area, element, and level, including the use of wildcards) of alarms to be presented to each EMS operator. Each operator shall be assigned alarm filters on an area-by-area basis. The system shall also be capable of using alarm filters to route network alarms to a specific printer or printers. The alarm manager shall process all alerts and alarms automatically. The system shall support a minimum of eight levels of alerts and alarms.
When the operator has initiated the alarm manager by clicking its icon, the operator shall be presented with an alarm list window that shall allow the operator to easily perform such functions as sorting, printing, suppressing of alarms (timed), jumping to a Graphic/Plot, generating custom messages, exporting alarm files, acknowledging alarms, etc. Command icons shall be provided for the most commonly used operator commands. This includes exporting, printing, copying to clipboard, appending operator notes, exporting alarm files, acknowledging of alarms, deleting of alarms, etc. The Alarm manager shall also dynamically display how many alarms are in the alarm list and viewing buffer, and how the alarms are presently sorted.
Each alarm shall include the areas name, controller name, bus and element number, the alarm status and priority, time and date of occurrence, point name and explanatory text, plus a custom message. In addition to the alarm custom message, an operator entered/modified note shall be available for viewing, printed with the standard alarm message, or copied to the Windows Clipboard. The alarm note toolbar icon will change its characteristics, such that the operator can easily determine if a note was attached to an alarm. Each alarm shall also include command icons to provide the means of quickly jumping to a Graphic/Plot pertinent to the alarm condition, acknowledging alarms, viewing or appending operator notes, etc. The system shall be provided with the capability of providing a Dynamic Data Exchange (DDE) or equivalent, of alarm information to third party software.

2.2.1.7Alarm Notification
The proposed system shall be capable of assigning different alarm notification types. One type shall provide an audible tone or WAV file sound based on the type of computer speakers specified. A second type shall notify the operator by displaying a flashing alarm icon along with the level of the alarm (and audible beep). Another method shall be a pop-up window alarm display on top of the current window (and audible beep). The system shall also provide support for critical alarms. When a critical alarm occurs a full screen alarm pop-up window shall cover the existing window.
The operator shall have the capability of running third party software (e.g., Microsoft Excel, Word, etc.) and still receive alarm indication as described above.

2.2.1.8Reports
The Energy Management System shall include the inherent ability to store, view and print energy consumption data, runtime data, and trend analog or digital variables. These reports shall also include a summary of consumption and runtimes. Standard management reports shall be provided as well as the capability to provide custom reports. The operating system shall be multi-tasking such that the operator may select other programs to run in the operating system environment without losing report data. Reports shall be generated automatically or manually as selected by the operator. The daily, monthly, and yearly consumption report shall collect from either a digital or analog input point. The daily, monthly, and yearly runtime report shall allow digital inputs/outputs to be totaled to indicate the total runtime of a piece of equipment. The operator shall be able to reset the runtime total for each input. Trend data shall allow the operator to collect and display events for each digital or analog point. The proposed system shall provide a report panel window with icons for the operator to select from. The operator shall also be able to add an icon to initiate the execution of a custom report from a third party spreadsheet in addition to the supplied standard report icons.
Standard Windows type toolbars and dialog boxes shall be provided to ease the task of report definition. Dialog boxes shall also be provided to ease the task of report formatting and reports shall be displayed as they would be printed via a print preview command. The operator shall have the capability to change any value in the report or to hide any row or column in the report through standard Window type commands. The following additional reports shall be available through the File Menu’s Print command:

  • A list of all controllers in a selected area, including the controller’s name, address, and all tables
  • A listing of all configuration tables in a controller including its name,description, current value, high and low allowable entries, etc.
  • A snapshot of the currently displayed point status, maintenance, orconfiguration table window
  • A listing of Graphic/Plot characteristics
  • Tenant Billing report (if applicable)
  • Time Schedule report
    The system shall also provide a download error report and a controller vs. database difference report upon operator request.
    System Activity Report
    The operator shall have the ability to easily create and generate operator activity reports. The report shall have the ability to monitor and log all system operator activities such as; operator login/off, operator forces, modifications to setpoint/time schedules, changes to controllers, areas, etc. DDE POKE commands and DLL interface changes to setpoints or time schedules shall be identified as a third party in the Systems Activity Report.
  • Graphic/Plot Display Manager
    The Graphic/Plot Display Manager (GDM) shall allow the operator the ability to organize and view real time point data from multiple controllers all on one screen. The proposed system shall be supplied with standard and customized HVAC graphics as required. The following image formats shall be supported as a minimum; .BMP, .DIB, .GIF, .JPG, .PCX, .TIF, and .TGA.
    The graphic package shall provide for multiple link areas, bookmarks, speed buttons and the ability to command point override values through Window Dialog boxes. The operator shall be able to change text colors and fonts, through standard Window Dialog boxes, for such things as point name, value, alarm, force, etc.
    The GDM shall be capable of displaying multiple dynamic system graphics with point values, units, names, alarm status, configuration decisions, setpoints, etc., and also multiple point trends, all on one screen. The GDM shall allow the operator the ability to include and display DDE data from other applications. As point data changes the data to the DDE system or equivalent, shall also automatically update.
    The GDM shall also be capable of interfacing to third party DDE “POKE” messages. Third party access to setpoints and time schedules shall be via Dynamic Link Library (DLL)
    Each Trend shall include the capability for the operator to select pause, start, autostart on and a minimum sampling period of at least ten seconds.
    The GDM shall include standard window menus, tool bars, dialog boxes, drop down lists, etc. The operator shall be able to force or auto point values and watch how the system responds dynamically, all on one screen. The graphics screens shall include the ability to be linked with other graphic screens and shall support animated data boxes. The system shall also include the capability to assign different initial graphics for each operator after logging in. If an operator selects a graphic that represents a remote site, the system shall automatically connect to the remote site without any operator intervention.
  • Remote Access
    The system shall include the capability to permit remote communications to multiple remote EMS sites through phone modems and vendor specific software. When a remote EMS site is connected to the network, the operation of the EMS computer shall be unaffected. Alarms shall continue to be printed and logged to the database.
  • Log On/Off
    After successfully logging in to the Multi-tasking operating system, the operator shall not be granted access into the EMS system until the selection of the EMS log-in icon is made, and the operator successfully enters the assigned login name and password. (The system shall have the ability to eliminate this second step, if desired by the operator). When the operator has successfully logged in to the EMS system, an EMS logout icon shall be displayed at the bottom of the screen. The system shall also provide the capability to assign each EMS operator an EMS start-up application (i.e., Alarm Manager, Reports, Network Manager, etc.). After logging on to the system this function shall automatically open up to the function defined on start-up. The system shall include the capability to automatically log out an operator after a user specified inactivity time.
    The operator shall not need to be logged into the system for alarms to be annunciated or
    for automatic reports to be generated.