My WebLink
|
Help
|
About
|
Sign Out
Home
Agmt 2010 Martin Industries Inc dba Climatech
CityHall
>
City Clerk
>
City Council
>
Agreements
>
2010
>
Agmt 2010 Martin Industries Inc dba Climatech
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/20/2012 5:22:37 PM
Creation date
11/3/2010 9:52:47 AM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Agreement
Document Date (6)
11/1/2010
Retention
PERM
Document Relationships
Reso 2010-135
(Approved by)
Path:
\City Clerk\City Council\Resolutions\2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
41
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
3. Alarms <br /> a. Alarms shall be routed directly from Network Automation Engines to PCs and <br /> servers. It shall be possible for specific alarms from specific points to be routed <br /> to specific PCs and servers. The alarm management portion of the user interface <br /> shall, at the minimum, provide the following functions: <br /> 0 Log date and time of alarm occurrence. <br /> 0 Generate a "Pop -Up" window, with audible alarm, informing a user that <br /> an alarm has been received. <br /> 0 Allow a user, with the appropriate security level, to acknowledge, <br /> temporarily silence, or discard an alarm. <br /> 0 Provide an audit trail on hard drive for alarms by recording user <br /> acknowledgment, deletion, or disabling of an alarm. The audit trail shall <br /> include the name of the user, the alarm, the action taken on the alarm, <br /> and a time /date stamp. <br /> 0 Provide the ability to direct alarms to an e-mail address or alphanumeric <br /> pager. This must be provided in addition to the pop up window <br /> described above. Systems that use e-mail and pagers as the exclusive <br /> means of annunciating alarms are not acceptable. <br /> 0 Any attribute of any object in the system may be designated to report an <br /> alarm. <br /> b. The BMS shall annunciate diagnostic alarms indicating system failures and <br /> non - normal operating conditions. <br /> c. The BMS shall allow a minimum of 4 categories of alarm sounds customizable <br /> through user defined way.files. <br /> d. The BMS shall annunciate application alarms at minimum, as required by Part <br /> 3. <br /> 4. Reports and Summaries <br /> a. Reports and Summaries shall be generated and directed to the user interface <br /> displays, with subsequent assignment to printers, or disk. As a minimum, the <br /> system shall provide the following reports: <br /> 0 All points in the BMS <br /> 0 All points in each BMS application <br /> 0 All points in a specific controller <br /> 0 All points in a user - defined group of points <br /> 0 All points currently in alarm <br /> 0 All points locked out <br /> 0 All BMS schedules <br /> 0 All user defined and adjustable variables, schedules, interlocks and the <br /> like. <br /> b. Summaries and Reports shall be accessible via standard Ul functions and not <br /> dependent upon custom programming or user defined HTML pages. <br /> Non - Professional Services Agreement between November 1, 2010 <br /> City of San Leandro and Martin Industries, Inc., OBA Climatech Page 15 of 28 <br />
The URL can be used to link to this page
Your browser does not support the video tag.