Configure priority ranges for alarm historization, mapping, and shelving

The Alarms and Events Configuration dialog lets you:

• Map alarm severities to priority ranges.

• Enable alarm shelving by priority range.

• Enable or disable historization of both alarm severities and event types. All alarms are historized by default.

  Default Alarm Mapping and Historization Values
  Severity	Description	Shelve	Historize	From Priority Range	To Priority Range
  1	Critical	N	Y	1	250
  2	High	N	Y	251	500
  3	Medium	Y	Y	501	750
  4	Low	Y	Y	751	999
  5	Uncategorized

Shelving, historization and priority ranges are configurable.

Mapping alarm severity to priority

• Severity 1 starts at priority 1 by default. Severities can be mapped to priorities in ascending or descending order. For example, severity 1 can map to priority range 1–250 or it can map to priority range 999-751.

• Severity 4 ends at 999 by default, but 999 is not required to be the end-of-range number. For example, severity 4 can end at 900, leaving a priority range above 900. In this case, alarms with a priority range above the 900 are automatically mapped to severity 5.

• Alarms in the severity 1 through 4 ranges are aggregated to the area that contains the object that is in alarm. For more information about aggregation, see Aggregated alarm information. The number of alarms and their severities are shown in the OMI navigation app (NavTree and/or BreadCrumb Control).

• Any alarm with a priority outside the configured priority ranges will return severity 5.

• Severity 5 alarms are viewable in the OMI Alarm App and in the InTouch Alarm Client as both current and historized alarms, but are not aggregated to the owning area and not shown in the OMI navigation app.

  Prior to System Platform 2023 R2 SP1 P01, alarms outside the configured priority ranges were not mapped and were categorized internally as severity 0. While current severity 0 alarms could be viewed in the OMI Alarm App and InTouch Alarm Client, the alarms were not historized and could not be queried.

  Note: Mapped alarm severities are not shared across galaxies in a multi-galaxy environment. Each galaxy in the environment has its own priority to severity mapping.