The Normalize Alarm History Data feature can be set on individual Alarm expression instances attached to your profiles. This option causes the BSLM Engine to break out the alarm fields into normalized tables, which can then be accessed by third-party reporting packages. To reduce overhead on the Operations Center server, alarm breakout events are first queued to the BSAAlarmQueue table, then processed in batches by a lower priority maintenance thread to maximize database throughput.
Alarms queued to the BSAAlarmQueue table are retrieved in a first‑in/first‑out order. Alarm fields specified in the Alarm expression are extracted from the serialized object (BSAAlarmData.AlarmBlob), and stored to the BSAAlarmXML table. One row is added per alarm and contains an XML representation of the alarm.