Page History

...

Firstly to trigger the threshold crossing module, it is necessary to configure the predefinedActivity "threshold even crossing". When the threshold crossing module runs it will look at the configured timeseriesset in the ThresholdValueSets file and check if any data was written to these timeseries. External timeseries Timeseries are only checked only for threshold crossings if the data has changed during this workflow run. during the current workflow run.values have changed. For external timeseries it is possible to skip the check for changes and always check for threshold crossings. This can be configured with option 'onlyCheckThresholdsOfChangedSeries' in the workflow descriptor file.

 Once a threshold crossing check has been triggered the threshold event is logged. The logging process works as follows:

1) Check if  a newly logged event is already in the list of logged events the flowing checks are preformed in given order:

check threshold type
check threshold direction
check time series type 
check event time
check event value. Difference has a allowed tolerance of 10% of value.
For forecasted timeseries check the taskrunid
check moduleInstanceId
check thresholdValueSetId
check thresholdId
check locationId
check parameterId
check eventActionId
check rateOfChange value

Definitions

• If a threshold only has an upWarningLevel or has upWarningLevelSeverity > downWarningLevelSeverity, then the threshold is called an "upCrossing threshold". This means that the threshold activates its upWarningLevel when there are data values above it (e.g. flood warning).
• If a threshold only has a downWarningLevel or has downWarningLevelSeverity > upWarningLevelSeverity, then the threshold is called a "downCrossing threshold". This means that the threshold activates a warning when there are data values below it (e.g. drought warning).
• If a threshold has upWarningLevelSeverity = downWarningLevelSeverity, then the threshold is called both an "upCrossing threshold" and a "downCrossing threshold". This means that the threshold activates its upWarningLevel if there is data above it and/or below it. It does not make sense to have upWarningLevelSeverity = downWarningLevelSeverity, but this is possible in the old thresholds configuration (not in the new improved thresholds configuration).

...