General Timing

At the core of Prognosis, all data collected, transported and displayed is based on timing events and triggers. This applies to Data Views which are used in common functions such as Collections, Displays, Thresholds and Databases. Less common functions also rely on Data Views and these include Analysts, Atlas' and Dispatch Manager.

These system functions rely on interval triggers that lie at the heart of Prognosis.

Data is collected and displayed in Intervals, Data Views and other system configurations include the setting of Intervals, Refresh Rates or other timing triggers.

The way these triggers are used is common throughout the product, each interval starts on a predictable time segment, which will always be relative to a standard wall clock. What this means is that no matter what time a system function is started, the interval will always align to a known time.

For example:

A Threshold with a Check Interval time set to 5 minutes, will always be processed at 5 minutes past the hour, then 10 minutes past the hour, etc..

A Display with a Refresh rate of 30 seconds, will always be processed at precisely every minute and 30 seconds past the minute.

For the most part, this underlying behavior is just routine and users need not know about the fundamentals, however in some cases, like Thresholds, it is important to understand when a trigger will occur so that the timing can be configured correctly.

Provide feedback on this article