Up to now, we have been discussing how to implement an alarm strategy in a hierarchical manner. This approach requires you to identify alarm areas by physical divisions and create an overview picture. However, if your alarm requirements do not warrant a hierarchical approach, you may find it easier to enable alarming for your most process-critical blocks. This action prioritizes your alarms, conserves system resources, and keeps the number of alarms to a minimum.
Depending on the number of database blocks that report alarms, you may also want to assign alarm areas according to the descriptions in the following table.
|
If you have a... |
You may want to... |
|
Small number of blocks that report alarms |
Accept the default alarm area, ALL, or assign the pre-named alarm areas A through P, if you require more than one alarm area. |
|
Large number of blocks that report alarms |
Create alarm areas by physical or functional divisions. |
