This will sync and/or purge alarms.

NOTICE! Concerning these Alarm Settings, the term “Sync” means importing alarms from the Remote Project to the Local Project.

Alarm Sync

Subscribes to all remote devices, polling for any changes in alarms every five seconds. All alarms that match the Alarm Sync filter will be kept in sync, with the remote device acting as the "master" for the alarm.  The local copy can be acknowledged, which will inform the remote device to perform the same ack, by the current user. The alarmable points need to exist in the local instance for alarms to be synced.

NOTICE! When using the F200, by default an alarm purge is performed every 30 days. Change this scheduling in Settings under the Alarm tab.

Alarm Purge

For example, the purge task can be scheduled to occur daily at 12:15 AM (system time), at which time the system will purge all alarms older then the given limit in the local database.

Enable Alarm Purge

Enables or disables the alarm purge module

Run Alarm Purge

Will execute the alarm purge task immediately, using the given parameters. It is also independent of the schedule frequency.

Alarm Max Age

How old the alarm data has to be for purging

Enable Alarm Sync

Enables or disables the alarm sync module.

Note

When alarm sync is enabled, all remote devices will notify the local FIN when an alarm changes (alarm state change, ack, alarm is re-written, alarm deleted, etc) and that changes will be propagated into the local database with an additional tag referencing the source of the alarm. Additionally when a sync’d alarm is acked, it will notify the original device of the alarm about the ack and it get’s acked on the remote system.

 

 

Alarm Sync Filter

Filter for tags on incoming alarms
Example: if the filter is set to toSync then only alarms with a toSync tag will be synced