Manuals > Monitoring System Construction Guide > Building the Main Functions > Daily Reports > Building the Daily Report Function > Using the Quality Check Function > Quality Check of Calculations > Quality Check of Static Calculations (Calculated Fields)

Calculated Field Quality Check Configuration Parameters

The processing of calculated fields is divided into calculation processing and aggregation processing. Specifically, calculations according to the formula in the calculated field are performed only when the daily report is compiled from RAW data, while the aggregation processing is performed when the monthly and yearly reports are compiled.

The quality check for calculation processing is set using the parameters in the aggregation log section of the summary master. In addition, by specifying the ExpressionQualityCheckTypeFieldMaster parameter, the type of quality check for each calculated field can be defined individually on the calculated field master side. To set the quality check for aggregation processing, specify the QualityCheckType parameter and QualityCheckTypeFieldMaster parameter in each aggregation log section of the summary master, just like in "Aggregation Quality Check", and define the QualityCheckType column in the calculated field master as necessary.

■Specifying the quality check type during calculation (ExpressionQualityCheckType parameter)

The type of quality check processing during calculation of a calculated field is defined in the ExpressionQualityCheckType parameter. By setting this parameter, if the data to be calculated contains NULL values or unreliable values, the calculation result data can be unreliable or NULL values. This parameter can be defined in each aggregation log section.

The types of quality checks that can be specified are:

Setting Value	Contents
NONE	No quality check.
NULLTONULL	If a NULL value exists in the calculation data, it is treated as a NULL value.
NULLTOBAD	If a NULL value is present in the calculation data, it is treated as an unreliable value (such as *123).
BADTONULL	If the calculation data contains unreliable values (such as *123), the value is treated as NULL.
BADTOBAD	If an unreliable value (such as 123) is present in the calculated data, it is treated as an unreliable value (such as 123).

When a calculation is performed, the judgment will be made according to the content specified in this parameter. For example, if "NULLTOBAD" is specified, if there is even one NULL value record in the calculation data, the calculation result will be unreliable.

If you want to apply multiple conditions, you can specify them by enumerating them with commas (e.g. NULLTOBAD,BADTOBAD). Note that if multiple conditions are specified like "XxxTONULL,XxxTOBAD", and both conditions are met (if NULL records exist and untrusted values exist), XxxTONULL will take precedence.

In addition, if you specify "F" in the [UncertainIsZero] column of the calculation field master, the calculation result will be NULL if a NULL value exists. For more information on this matter, please refer to the description in "Calculation Field Master".

ExpressionQualityCheckType=NULLTOBAD

■Define the quality check type during calculation in the calculation field master (ExpressionQualityCheckTypeFieldMaster parameter)

The quality check type of a calculated field can also be defined individually for each field in the calculated field master. When defining a quality check type in the calculated field master, first define the column name of the calculated field master that stores the quality check type definition in the ExpressionQualityCheckTypeFieldMaster parameter in each aggregation log section of the summary master. Then, prepare a column for the quality check type with the column name specified earlier in the calculated field master, and define the check type individually for each field. Note that if both "ExpressionQualityCheckType" and "ExpressionQualityCheckTypeFieldMaster" are defined, the calculated field master side takes priority for fields in rows where the quality check type is specified in the calculated field master. For fields in rows where an empty string is specified as the quality check type, the ExpressionQualityCheckType from the summary master is adopted.

Example

ExpressionQualityCheckTypeFieldMaster=[ExpressionQualityCheckType1]

Example of calculation quality check settings

Below is an example of a calculation quality check setting.

・Define the quality check type of the calculated field in the calculated field master.

Summary Master (*Example when RAW data is 1 minute interval)

[COMMON]

: : :

[RAW]

: : :

[RAW::DAY]

SummaryUnit=1HOUR

: : :

CalculationType =[Expression]

ExpressionQualityCheckType=NONE

ExpressionQualityCheckTypeFieldMaster=[ExpressionQualityCheckType1]

: : :

[DAY::MONTH]

SummaryUnit=1DAY

: : :

CalculationType =[SummaryType1]

QualityCheckType=NONE

QualityCheckTypeFieldMaster=[QualityCheckType1]

: : :

[MONTH::YEAR]

SummaryUnit=1MONTH

: : :

CalculationType =[SummaryType1]

QualityCheckType=NONE

QualityCheckTypeFieldMaster=[QualityCheckType1]

: : :

Calculated Field Master (Example)

[Name],

[Comment],

[Expression],

[DecimalNum1],

[ExpressionQualityCheckType1],

[UncertainIsZero],

[QualityCheckType1],

[TermOfValidity],

[SummaryType1]

[ReportHeader1],

[ReportHeader2],

[ReportHeader3],

[ReportHeader4]

C000,

Calculation tag 1,

T000 + T001,

NULLTOBAD,

BADTOBAD,

AVERAGE,

Calculation 1,

T000＋T001,

C001,

Calculation tag 2,

C000 / 2,

NULLTONULL,

AVERAGE,

Calculation 2,

average,

Quality check of static calculations (calculated fields)

Quality check of static calculations (calculated fields)