Basic Documentation

Table Of Contents
Disclaimer: These are sample drawings and sequences. Designers are responsible for
finalizing the content for their particular projects.
made at the user-interface of Building Controllers shall be automatically uploaded to the
workstation, ensuring system continuity.
5. System configuration, programming, editing, graphics generation shall be performed on-
line from the operator workstation software.
6. User shall be able to edit point configuration online within a dedicated editor application.
The editor shall allow the user to create, view existing, modify, copy, and delete points
from the database.
7. User shall be able to edit point configuration of any configurable BACnet point that
resides in a devices that supports external editing.
8. The software shall also allow the user to configure the alarm management strategy for
each point. The editor shall provide the ability for editing the point database directly
online with the Building Controllers.
9. The operator interface software shall also provide the capability to perform bulk
modification of point definition attributes to a single or multiple user-selected points.
10. Control program configuration shall be available to the user within a dedicated control
program editor application. The editor shall allow for creation, modification and deletion
of control programs. The editor shall also include the ability to automatically compile the
program to ensure its compatibility with the Building Controllers. The editor shall
provide the ability to selectively enable or disable the live program execution within the
Building Controllers.
11. Users shall have the ability to view the program(s) that is\are currently running in a
Building Controller. The display shall mark the program lines with the following:
disabled, comment, unresolved, and trace bits.
T. Event Management
1. Event Routing shall allow the user to send event notification to selected printers or
workstation location(s) based on event severity, or point type.
2. Event Notification shall be presented to each workstation in a tabular format application,
and shall include the following information for each event: name, value, event time and
date, event status, priority, acknowledgement information, and alarm count. Each event
shall have the ability to sound an audible notification based on the category of the event.
3. Event List shall have the ability to list and sort the events based on event status, point
name, ascending or descending activation time.
4. Directly from the Event List, the user shall have the ability to acknowledge, silence the
event sound, print, or erase each event. The interface shall also have the option to inhibit
the erasing of active acknowledged events, until they have returned to normal status. The
user shall also have the ability to navigate to all information related to a selected point in
order to command, launch an associated graphic or trended graphical plot, or run a report
on a selected point directly from the Event List.
5. Each event shall have a direct link from the Event List to further user-defined point
informational data. The user shall have the ability to also associate real-time electronic
annotations or notes to each event.
U. Remote Notification Software (RENO)
1. Workstations shall be configured to send out messages to numeric pagers, alphanumeric
pagers, phones (via text to speech technology), SMS (Simple Messaging Service, text
messaging) Devices, and email accounts based on a point's alarm condition.
2. There shall be no limit to the number of points that can be configured for remote
notification of alarm conditions and no limit on the number of remote devices which can
receive messages from the system.