| Flexible Alarm Attribute Design |
| |
CAMS allows users to define attribute identifiers and sort out alarms quickly and effectively. In addition, further value-added information can be defined for specific alarms to help operators take agile role-based action. |
| |
|
| |
Example of alarm attribute identifiers: |
| |
• To filter alarms and deliver necessary alarms only |
| |
| - |
Purpose of monitoring (e.g. safety, environment, economic efficiency) |
| - |
Operation mode to be monitored (e.g. at the time of plant startup, during steady-state operation) |
|
| |
|
| |
• To deliver alarms to the right people |
| |
| - |
User name |
| - |
Duty position |
|
| |
|
| |
• To provide alarms at the right time |
| |
| - |
Maximum allowable time to respond |
| - |
Estimated amount of loss |
| - |
Alarm priority |
|
| |
|
| |
Examples of further value-added information: |
| |
| - |
Root causes of alarm occurrence |
| - |
Role-based actions to be taken |
| - |
Previous action procedure |
|
| |
|
| |
|
| EEMUA#191 Compliant Alarm Definition |
| |
CAMS for HIS provides an engineering environment that allows users to define truly necessary alarms only. This engineering environment is in accordance with EEMUA Publication 191. |