Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Measurement Advisor

Configure additional columns in the historical data tables

Configure additional columns in the historical data tables

  • Last UpdatedDec 29, 2025
  • 2 minute read

This section outlines how to add columns to the Meter and/or Gas Quality history tables.

The AddColumnExample (configDesc.CD_ADD_EXTRA_GQ_COLUMN) in the configDesc table of the measConfig tool is designed to help you configure additional columns in the historical data tables.

Note: The configDesc.CD_ADD_EXTRA_GQ_COLUMN example should not be edited, it is merely shown as an example of a new column set up.

This will enable you to configure additional columns in the client.

These components are included:

  • The tableColumnDesc entry defines the data columns. It is where the new column needs to be added to the history tables.

  • The objItemDesc entries, which define the properties required for validation and default estimation.

  • The objItemDesc.sysdefNumericValue information, which enables you to configure the default numeric values for the properties.

  • The objItemDomainDesc, which enables you to configure the Invalid and Flagged severity values for the validation checks.

  • The objItemDesc.sysdefDomainDesc information, which enables you to set the default severity.

    Note:There are no additional objItemDomainDesc properties required for GQ validation. Therefore, they will not be any entries in the objItemDomain file or the objItem.sysdefDomainValue files for a gas quality.

  • The tableColumnDesc.alter files, which update the tableColumnDesc entry.

    There are two .alter files: tableColumnDesc.alterValidation and tableColumnDesc.alterEstimation. These files enable you to link the new column with a validation check or estimation property using a prefix.

    Consider the properties defined for the GQ reasonability check. The value of the objItem.objItemDefine column file all begin with the following prefix: OID_GQACERC. For example, OID_GQACERC_ENABLE. This prefix is then specified in the tableColumnDesc.alterValidation file to associate these properties with the check.

    We recommend using the following naming convention for the prefixes. Our recommendations are as follows, using OID_GQACERC as the example.

    OID_ This is an abbreviation for objItemDesc.

    GQ The abbreviation of the object type. Use GQ for gas quality, and MTR for meter.

    ACE The abbreviation of the Add Column Extra columnName used in the example.

    RC The abbreviation of the validation check. In this example, the reasCheck is being customized.

    The naming convention for the objItemDomainDesc entries begins with OIDD_

    The naming conventions for the objItemSubGroupDesc table begins with OISGD_

    The tables below provide additional examples of proper prefix format and usage, using the Add Column Example column name (ACE). Examples for gas quality and meter records are shown.

    Gas Quality Check Name

    Prefix Format

    reasCheckPrefix

    OID_GQACERC

    operCheckPrefix

    OID_GQACEOC

    histAvgCheckPrefix

    OID_GQACEHAC

    frozCheckPrefix

    OID_GQACEFC

    dailyAggCheckPrefix

    OID_GQACEDAC

    defaultEstimation

    OID_GQRED

    Meter Check Name

    Prefix Format

    reasCheckPrefix

    OID_MTRACERC

    operCheckPrefix

    OID_MTRACEOC

    histAvgCheckPrefix

    OID_GQACEHAC

    rocCheckPrefix

    OID_MTRACEROCC

    frozCheckPrefix

    OID_MTRACEFC

    hourlyReasCheckPrefix

    OID_HACEC

    hourlyFrozCheckPrefix

    OID_HACEFC

    hourlyAggPrefix

    OID_MTRACEHAGGC

    dailyReasCheckPrefix

    OID_DACEC

    dailyFrozCheckPrefix

    OID_DACEFC

    dailyAggCheckPrefix

    OID_MTRACEDAC

    defaultEstimation

    OID_MTRED

TitleResults for “How to create a CRG?”Also Available in