Alarm Management Sample Clauses
Alarm Management.
1. Contractor shall submit for Review as stated in Section 3.2 an Alarms Management Plan.
2. The Rail Infrastructure System shall issue, distribute, and direct alarms and notifications as defined in the Contractor’s Alarms Management Plan.
3. The Rail Infrastructure System shall detect and display an alarm whenever an alarm condition or state occurs. Alarm conditions shall include, but not limited to, the following:
a. Failures with a potential to affect the safe operation of the System;
b. Any failure, where a second failure in an associated system may cause a service interruption;
c. Un-commanded or unexpected changes of state of any monitored devices;
d. Loss of any communication channels;
e. Communication errors resulting in loss of data;
f. Predictive maintenance alarms; and
4. Alarms shall be integrated into the User Interface
5. Alarms shall be assigned to one of the following alarm priorities, but not limited to:
Alarm Management. Each Programmable controller shall perform its own limit and status monitoring and analysis to maximize network performance by reducing unnecessary communications.
G. Air Handling Unit (AHU) Controllers:
1. AHU Controllers shall support the specified sequence of operation and requirements as described in the "Sequence of Operation" section of the specifications, and for future expansion.
2. AHU Controllers shall support all the necessary point inputs and outputs to perform the specified control sequences in a totally standalone fashion.
3. AHU Controllers shall have a library of control routines and custom program logic to perform the sequence of operation as described in the "Sequence of Operation" section of the specifications.
4. AHU Controllers shall support the following types of point inputs and outputs in addition to air handling unit functions:
a. Proportional Heating and Cooling Outputs for air handling unit and fan coil unit control.
b. Fan Control Output (On/Off Logic, or Proportional Series Fan Logic)
c. Damper and Control Valve actuation
d. Analog and Binary Sensor Inputs
5. AHU Controllers shall support the following library of control strategies to address the requirements of the sequences described in the "Execution" portion of this specification, and for future expansion:
a. Daily Schedules
b. Comfort/Occupancy Mode c. Economy Mode d. Standby Mode SRU PROJECT NO. UP-401 / IKM PROJECT NO. 16-110 JANUARY 2017 e. Unoccupied
Alarm Management. ▇. ▇▇▇▇▇▇ will be divided into three categories: informational, warning and critical.
B. Informational refers to operator induced changes, such as points disabled or overridden.
C. Warning alarms refer to general alarms that, when activated, will annunciate at the workstation and display on the system graphic panel.
D. Critical alarms, when activated, will annunciate at the workstation and display on the equipment graphic. Critical alarms will be intentionally setup to be triggered by events that would cause disruption to a major building system or indicate that mechanical damage may be eminent.
E. Critical and non-critical alarms will be indicated by red colored text on the equipment graphic or floor plan.
F. The BAS will continuously monitor itself for system integrity. If any controller fails to communicate, a critical alarm will be sent to indicate the specific controller(s) that have lost communication. This will be a critical alarm. G. Specific alarms will be identified under each system sequence. Critical alarms will be identified in bold face.
Alarm Management. Each AHU Controller shall perform its own limit and status monitoring and analysis to maximize network performance by reducing unnecessary communications.