...
Example for "Rate of Rise" and "Temporary Shift" validation rules
Use of <timeSeries> instead of <timeSeriesSets>
Since 2023.02 it is possible to use the <timeSeries> element instead of the <timeSeriesSets> elements.
The <timeSeries> element works like a more general filter on all time series instead of the more explicitly defined <timeSeriesSet> element.
The most useful part of the <timeSeries> is the fact that multiple parameters can be defined instead of just the single one in a <timeSeriesSet>.
This can be done by defining multiple single parameters or even 1 or more parameter groups:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<validationRuleSet validationRuleSetId="SetWithTimeSeriesFilter" timeZone="GMT">
<extremeValues>
<hardMax constantLimit="20"/>
<hardMin constantLimit="0"/>
<softMax constantLimit="10"/>
<softMin constantLimit="2"/>
</extremeValues>
<timeSeries>
<moduleInstanceId>moduleA</moduleInstanceId>
<valueType>scalar</valueType>
<parameterGroupId>ParGroupA</parameterGroupId>
<parameterId>Par1</parameterId>
<parameterId>Par2</parameterId>
<locationSetId>locationSetA</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour"/>
</timeSeries>
</validationRuleSet> |
Examples of validation rules
...