Home › Technical articles

Đọc bằng tiếng Việt

ISA-18.2 alarm management software: shelving, alarm history, KPI reports in FactoryTalk, AVEVA, Ignition

TDL Industrial Automation · Last updated:

From the FactoryTalk View SE 16.00 and FactoryTalk Alarms and Events help, PlantPAx Analytics, AVEVA 2026 documentation and the Ignition 8.3 user manual: shelving, disabling, bulk alarm import, where alarm history is stored, KPI reports, change records, a function-by-platform table and what to log for the KPIs.

ISA-18.2 describes the work of managing alarms over their whole life, not a product, and no software makes a plant follow it on its own. Software supports that work, and the ISA-18.2 article maps its functions to the lifecycle stages. Here we look at what FactoryTalk Alarms and Events with FactoryTalk View SE, AVEVA System Platform with InTouch HMI and AVEVA Historian, and Ignition 8.3 document for each one. It is not a ranking: "not stated in the docs read" means we found nothing, not that the product cannot do it.

Where alarms go on three platformsThree columns: FactoryTalk Alarms and Events with FactoryTalk View SE 16, AVEVA System Platform 2026 and Ignition 8.3. Four rows from top to bottom. Row 1, where alarms are defined: Logix alarms and Tag Alarm and Event servers; Application Server objects; alarms on tags and UDTs. Row 2, shelve and disable: Alarm and Event Summary and Alarm Status Explorer; shelving by area and severity with AlarmModeCmd and AlarmInhibit; Alarm Status Table, system.alarm.shelve and the Enabled property. Row 3, alarm history: Alarm and Event Historian on SQL Server; AVEVA Historian history blocks and the InTouch Alarm DB Logger; Alarm Journal. Row 4, reports and KPIs: Log Viewer and PlantPAx Analytics; Historian Client Query Alarm Summary and Alarm Pareto; Alarm Journal Table, scripting and SQL queries, with no built-in KPI report stated in the docs read. Based on the FactoryTalk View SE 16.00 and FactoryTalk Services Platform 6.60 help, PROCES-AT101A-EN-P, AVEVA 2026 documentation and the Ignition 8.3 user manual.Where alarms go on three platformsFactoryTalkAlarms and EventsFactoryTalk View SE 16AVEVA System PlatformApplication Server,Historian 2026IgnitionIgnition 8.31 · Where alarms are definedLogix alarms,Tag Alarm and Event serverinstruction-based andtag-based; server tag-based;OPC UA alarmsApplication Serverobjectslimit alarms with deadband, onand off delay; priority mappedto severityAlarms on tags and UDTspriority, deadband,Active Delay, Clear Delay,Ack Mode2 · Shelve and disableAlarm and Event Summary,Alarm Status Explorershelve in minutes with acomment; enable,disable, suppressShelving,AlarmModeCmd,AlarmInhibitshelving by area and severity;enable, silence, disableAlarm Status Table,system.alarm.shelveshelve time picked from a list;Enabled property3 · Alarm historyAlarm and Event Historiana database definition peralarm server;Microsoft SQL ServerAVEVA Historianhistory blocksInTouch Alarm DB Loggerwrites to SQL ServerAlarm JournalSQL database, Internal oranother Gateway4 · Reports and KPIsLog Viewer,PlantPAx Analyticschattering, fleeting, flood,stale, top alarms; forPlantPAx 5.xHistorian Client Query,Alarm Paretoaverage alarms per hour, mostfrequent alarm, time to clearAlarm Journal Table,scripting, SQLno built-in KPI report stated inthe docs readBased on the FactoryTalk View SE 16.00 and FactoryTalk Services Platform 6.60 help, PROCES-AT101A-EN-P(Rockwell Automation), AVEVA 2026 documentation and the Ignition 8.3 user manual (Inductive Automation),read 15 November 2026. Not a ranking. Figure: drawn by TDL.
Figure 1: Where alarms go on three platforms. On a phone, swipe sideways to see the whole figure.

1. What was read

  • Rockwell Automation: FactoryTalk View SE 16.00 help; FactoryTalk Alarms and Events help (FactoryTalk Services Platform 6.60); PROCES-AT101A-EN-P (February 2025); PROCES-WP015B-EN-P (June 2017).
  • AVEVA: Application Server, System Platform, Historian and InTouch HMI, all 2026.
  • Inductive Automation: Ignition 8.3 user manual.

2. The functions to look for

Siemens' article on ISA-18.2 asks for an approved master alarm database, kept up to date, and a periodic comparison of the running configuration with it, so that a changed limit stands out. It asks for lists of shelved and out-of-service alarms, and for every HMI change to be logged with time, old and new value and user. Its statistics use at least 30 days of data. exida notes that IEC 62682 made shelving a capability the control system supplier must provide. In Rockwell's white paper an audit starts from the philosophy and the master alarm database, and a sample differences report marks each difference accept, reject or enforce. How the database is built is covered in Alarm rationalization.

3. FactoryTalk Alarms and Events with FactoryTalk View SE

The SE 16.00 help names four alarm sources: Logix instruction-based and tag-based alarms, server tag-based alarms from a Tag Alarm and Event server, and OPC UA alarms.

  • Shelving. From the Alarm and Event Summary or the Alarm Status Explorer, the operator enters a duration in minutes and an optional comment; the alarm unshelves itself when the time runs out. The maximum, 480 minutes by default, is set in the Tag Alarm and Event Server configuration, and a longer entry is cut to it. Shelving needs the FactoryTalk Security permission Alarming > Shelve and Logix Designer version 21 or later.
  • Disable and suppress. The Alarm Status Explorer enables, disables, suppresses or unsuppresses alarms.
  • Bulk configuration. Tag Alarm and Event Server alarms are exported and imported as Excel or XML, with the Alarm Import Export Wizard in FactoryTalk View Studio or the Alarm Import Tool.
  • History. The FactoryTalk Alarm and Event Historian links each alarm server to a database definition; the help names Microsoft SQL Server. It logs alarm state changes, operator actions and tracking events such as enable, disable, acknowledge, reset, suppress and unsuppress. A shelve comment goes to the UserComment field. The Alarm and Event Log Viewer or SQL queries read the data.
  • Audit. Operator actions and changes to alarm definitions go as audit messages to the FactoryTalk Audit Log, for use with FactoryTalk AssetCentre.
  • KPI reports. PlantPAx Analytics reads the alarm history on SQL Server and shows a dashboard, top alarms, an alarm report with CSV download and KPIs it says follow ISA-18.2 guidelines: chattering (3 repeats within 60 seconds), fleeting (active less than 10 seconds), flood (more than 10 alarms in 10 minutes, ending below 5) and stale (active more than 24 hours). It is set up through FactoryTalk Hub and FactoryTalk DataMosaix, for PlantPAx 5.x with ControlLogix 5580P or CompactLogix 5380P process controllers.
  • Master alarm database. The 2017 white paper names the PlantPAx Alarm Builder among tools for data exchange between the control system and the master alarm database. The help pages we read describe no comparison with such a database.

4. AVEVA System Platform, InTouch HMI and AVEVA Historian

In Application Server 2026, alarms belong to objects. Limit alarms (HiHi, Hi, Lo, LoLo) have a value deadband, an alarm-on delay and, new in 2026, a separate alarm-off delay, which the release notes link to the on- and off-delay handling of ANSI/ISA-18.2-2009. By default, priorities 1 to 999 map to four severities.

  • Shelving. Configured in the Galaxy for chosen severities (by default 3, medium, and 4, low) and enabled on the Area object, it applies to single alarms, never to a whole area. Roles limit who may shelve, which severities and how many alarms. The system records user, workstation, reason, start and expiry, and shelved alarms are still historized.
  • Disable and silence. An object's AlarmMode makes its alarms enabled, silenced or disabled; it follows the most restrictive of its AlarmModeCmd, its AlarmInhibit and its parent's mode. AlarmInhibit, set by script, by hand or from an input, disables all alarms of the object and of the objects it contains.
  • Floods. Throttling on the WinPlatform caps alarm transitions per engine; transitions over the limit are not reported.
  • Bulk configuration. A Galaxy dump exports object instances to a .csv file, which is edited and loaded back.
  • History. All alarms are historized by default; historization can be switched off per severity and event type. AVEVA Historian stores alarms and events in history blocks; older systems used the A2ALMDB SQL Server database. InTouch's Alarm DB Logger writes to SQL Server and caches alarms while the connection is down.
  • Reports. The Historian Client Query has an Alarm Summary query: average alarm rate per hour, most frequent alarm per hour, where alarms occur, and average time to clear by severity or by user. It needs the high-speed alarms and events storage. InTouch's Alarm Pareto control charts the most frequent ones.
  • Change records. Each object has a Change Log in the IDE. Operator changes are logged as security-audit events, with the user's comment for Secured and Verified writes.

The System Platform 2026 docs mention AVEVA Alarm Adviser only in the installation order (versions 2014 R2 SP1 and earlier), without describing it.

5. Ignition 8.3

Alarms sit on tags and UDTs. Documented properties include Priority (Diagnostic to Critical), Deadband, Active Delay, Clear Delay, Ack Mode, Ack Notes Required, Shelving Allowed and Enabled, which can be bound to a tag or written at runtime.

  • Shelving. Operators shelve from the Vision or Perspective Alarm Status Table, picking a duration from a list set on the component; a shelved view lists shelved alarms for unshelving. The script function system.alarm.shelve defaults to 15 minutes, and system.alarm.getShelvedPaths returns who shelved each alarm and when the shelf expires.
  • Notification. Alarm pipelines of the Alarm Notification module route email, SMS or voice notifications, with delays and escalation.
  • History. The Alarm Journal writes active, clear and acknowledged events to a SQL database connection, to the local Ignition installation (Internal) or to another Gateway's journal. The default tables are alarm_events and alarm_event_data. Settings decide what is kept: Minimum Priority (default Low), Store Shelved Events (off by default), Store Enabled & Disabled Events and pruning (off by default). The Gateway's Live Event Limit (default 5) auto-acknowledges older events of a cycling alarm.
  • Bulk configuration. Tag exports in JSON or XML include alarms; CSV import does not. The Tag Report Tool lists tags with alarms as CSV.
  • Audit. Audit profiles log actions such as tag edit, tag write and project save.

The 8.3 pages we read describe no built-in alarm KPI report and no comparison with a master alarm database; the journal is read with the Alarm Journal Table, scripting or SQL.

6. Side by side

Function FactoryTalk Alarms and Events / View SE AVEVA System Platform 2026 Ignition 8.3
Master alarm database and comparison Not stated in the help read; 2017 white paper names PlantPAx Alarm Builder Not stated in the docs read Not stated in the docs read
Bulk import of alarm settings Excel or XML, Tag Alarm and Event Server Galaxy dump and load, .csv JSON or XML tag export with alarms
Shelving Minutes plus comment; maximum 480 min by default; security permission Per area and severity; role limits; user, node, reason recorded Status Table or script, default 15 min; Shelving Allowed per alarm
Disable, suppress Alarm Status Explorer: enable, disable, suppress AlarmModeCmd, AlarmInhibit Enabled property, bindable
Alarm history Alarm and Event Historian, SQL Server Historian history blocks; InTouch Alarm DB Logger Alarm Journal: database, Internal or remote
KPI reports PlantPAx Analytics (PlantPAx 5.x) Historian Client Query Alarm Summary; Alarm Pareto Not stated in the docs read
Change and action records Tracking events; FactoryTalk Audit Log Object Change Log; security-audit events Audit profiles

In the pages we read, none of the three uses the ISA-18.2 term "out of service"; the closest documented function is disabling.

7. Logging for the KPIs

The KPIs in the ISA-18.2 article need, for every alarm, when it became active, was acknowledged and cleared, its priority and its area or console. Siemens also counts unauthorised suppression and attribute changes, so shelve, disable and configuration events belong in the log too, for at least 30 days.

  • FactoryTalk: the SQL Server database of each alarm server's database definition; PlantPAx Analytics also needs history enabled on the FactoryTalk Linx server.
  • AVEVA: AVEVA Historian history blocks or the InTouch alarm database. Check that no severity is excluded from historization; throttled transitions never reach the log.
  • Ignition: the Alarm Journal. Turn on Store Shelved Events and Store Enabled & Disabled Events if those counts are needed, and set pruning to keep the period you analyse.

What we check first

This is TDL's practice, not a requirement of ISA-18.2.

  • We check that alarm history is switched on, where it goes and how long it is kept.
  • We look for settings that keep events out of the log.
  • We export 30 days of history as a baseline before changing anything.
  • We list who may shelve, disable or change limits, and whether a comment is required.
  • We find where the master alarm database lives and test the import path on a copy.
  • We check that server and controller clocks agree.

How TDL works with these platforms

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork, a System Integrator member of the AVEVA Partner Ecosystem and an Ignition Certified Integrator. Platforms side by side: AVEVA vs Ignition vs FactoryTalk View SE; alarms on the screen: ISA-101 explained; process history: What is a process historian. Services: SCADA and historian, Rockwell Automation system integrator, AVEVA system integrator and Ignition integrator.

Frequently asked questions

Does FactoryTalk, AVEVA or Ignition make a plant follow ISA-18.2?

No software does that on its own. ISA-18.2 describes the work of the alarm lifecycle. The platforms provide functions such as shelving, disabling, alarm history and, for some, KPI reports, which the plant uses within that work.

Which platform has built-in alarm KPI reports?

Rockwell documents PlantPAx Analytics for PlantPAx 5.x, with chattering, fleeting, flood, stale and top alarm reports. AVEVA documents an Alarm Summary query in the Historian Client Query and the Alarm Pareto control. The Ignition 8.3 pages we read describe no built-in KPI report; the Alarm Journal can be queried with SQL.

How long can an alarm be shelved in FactoryTalk Alarms and Events?

The operator enters a duration in minutes. The maximum is set in the Tag Alarm and Event Server configuration, 480 minutes by default, and a longer entry is cut to that maximum. The alarm unshelves itself when the time runs out.

Where does Ignition store alarm history?

In the Alarm Journal, which writes to a SQL database connection, to the local Ignition installation or to another Gateway. The default tables are alarm_events and alarm_event_data. Shelved events are stored only if Store Shelved Events is turned on.

Can alarm settings be imported from a master alarm database spreadsheet?

Each platform documents a bulk path: Excel or XML for a Tag Alarm and Event Server, a Galaxy load from .csv in System Platform, and JSON or XML tag import in Ignition, where CSV import carries no alarms. None of the pages we read describes an automatic comparison with a master alarm database.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
SCADA & historian Rockwell Automation (Allen-Bradley) AVEVA (Wonderware) Ignition (Inductive Automation)