The Age Watchdog application

The Age Watchdog application monitors specific telemetered points within an Omnicomm process to ensure that they are actively being krunched.

Communication connections to remote devices are generally managed by Omnicomm, which polls and receives data depending on the connection type. It is important that Omnicomm remain active, polling the remotes and krunching their data. If Omnicomm or one of the remotes it manages fails, the integrity of the data in the system is compromised.

The Age Watchdog application monitors the points it owns by checking their timestamps at a defined interval and comparing them against the current time. If the difference is longer than the configured acceptable timespan, the application responds according to event and alarm configuration for the point.

Whenever a monitored point has not been updated within the expected timespan, it is declared suspect. Suspect points result in a demand poll to the remote if Demand Polling is enabled. If the monitored point is not updated within a specified period of time, the ageWatchdog record in the Advanced Database Editor (ADE) is declared old. When a record is declared old, the data quality of its monitored point is considered potentially invalid and the Age Watchdog application performs the following actions:

• Issues an ageWatchdog related alarm against the point's remote if it is not alarm-inhibited.

• Issues an ageWatchdog related event against the point's remote if it is not event-inhibited.

• Issues an ageWatchdog related event against the monitored point if it is not event-inhibited.

• Stales the remote of the monitored point.

• Stales the monitored point and all points that belong to the same remote.

• Sets the state of the ageWatchdog record associated with the monitored point to "Stale Data".

• Triggers an Historical data collection of all staled points.