Configure plant state-based alarms
- Last UpdatedJul 16, 2024
- 1 minute read
You can map alarm modes on a per-Galaxy basis to different plant operational states to control how alarms are reported. Five plant states are pre-defined, and have default alarm states associated with them:
|
Plant state |
Default alarm state |
Available alarm states |
|---|---|---|
|
Running |
Enable |
Enable |
|
Maintenance |
Disable |
Enable / Silence / Disable |
|
Startup |
Silence |
Enable / Silence / Disable |
|
Shutdown |
Disable |
Enable / Silence / Disable |
|
Testing |
Silence |
Enable / Silence / Disable |
You can define new plant states, rename plant states, or remove existing plant states, except the "Running" state (you can, however, rename "Running"). The alarm state for Running is read-only and cannot be changed from Enable.
After you have defined plant state-based alarm configurations for the Galaxy, you can assign plant state-based alarming to area objects in the Galaxy. This is done by setting the PlantState attribute for each area object that will use plant state-based alarming. The area object will automatically update its PlantAlarmMode attribute to match the alarm state that is set for the PlantState currently assigned to it.
|
Attribute |
Definition |
|---|---|
|
PlantState |
The name of the currently assigned plant state (Running, Maintenance, etc.). |
|
PlantStateAlarmMode |
The alarm state of the assigned plant state (enable, silence, or disable). This attribute is read-only at runtime. |