Alarm and Event data acquisition workflow
- Last UpdatedMar 10, 2025
- 1 minute read
For every periodic interval of alarm and event acquisition, the Connector performs the following operations as shown in the workflow below:

Alarm Data acquisition Operations
-
Reading alarms
For user configured periodic interval, the connector reads the alarms from AVEVA Plant SCADA. -
Mapping alarm fields
The data structure of AVEVA Plant SCADA alarms is different from that of AVEVA Historian alarms. AVEVA Plant SCADA alarms are therefore processed and mapped to match the data structure of AVEVA Historian alarms. -
Writing alarms to AVEVA Historian
Once the data structure mapping is complete, AVEVA Plant SCADA alarms are written to AVEVA Historian. Users can view the alarms/events from AVEVA Historian using different approaches described in the AVEVA Historian documentation. -
Persisting alarms into local storage
The processed alarms from AVEVA Plant SCADA are stored in the Connector's local storage to support automatic backfill of AVEVA Plant SCADA alarms in case of connector restart. Alarms generated/state changed between connector stop and start times will be pushed to AVEVA Historian. This mechanism makes AVEVA Plant SCADA alarms available in AVEVA Historian.