Sigma - Device Monitoring, Alarm Priorities, and Functionality

[Product_Support]

Issue

Understanding the configuration and limitations of Device Monitoring alarms, including alarm priorities and functionality in Sigma systems.

Product Line

Satchwell BAS & Sigma

Environment

Sigma versions 4.04 and later.

Cause

Clarification is required on whether the Device Monitor alarm in Sigma can have its priority or functionality modified.

Resolution

Sigma 4.04 and Earlier

• The Device Monitor alarm is fixed at priority level 29.
• Alarm priority cannot be changed in these versions.

Sigma 4.05 and Later

• A configuration file named deviceMonitor.xml is introduced.

• This file contains parameters such as polling frequency, retry attempts, and alarm priority.

• Example configuration snippet:

  <DeviceMonitor>
      PollFrequency="1001"
      NumberRetrys="3"
      AlarmPriority="29"
      MaxDelayResponse="5000"
      LogLongDelays="0"
  </DeviceMonitor>

  Note: Do not modify these settings without consulting support and fully understanding the implications.

• Important: Any changes to deviceMonitor.xml require a Sigma server restart to take effect.

---

Functional Limitations

• The Device Monitor alarm is not controller-based, which means:
  • It does not support routing like plant alarms.
  • It cannot have “actions” applied.
  • There is no object associated with each controller.
  • It cannot be displayed on graphics or used in control schemes.

Recommendation

If enhanced functionality is required, consider using the legacy method where controllers are monitored by other controllers. This approach allows for more flexible alarm handling and integration into control strategies.