About the data exchange parser
- Last UpdatedNov 18, 2025
- 3 minute read
The MeasUtil.FileImportParser.DataExchangeParser.dll is used to parse measurement data according to a defined XML Schema Definition (XSD) and insert it into AVEVA Measurement Advisor.
In order to understand the input format, more information is provided in the Software Development Kit (SDK) directory provided here: %DNAInstallRoot%\MeasurementAdvisor\sdk\MeasurementAdvisorDataExchange.
This directory contains the following:
-
MeasurementAdvisorDataExchange.xsd — the definition of the Extensible Markup Language (XML) document with notes
-
MeasData.xml — an XML file generated from the XSD with sample data for all of the fields. This is designed to give an example of what the XML file should look like.
-
CASE1_METER.xml — an example XML file that loads meter and gas quality (GQ) data along with a property change and event.
-
CASE1_METER.fileImport.sql — a Microsoft SQL file that will create an example file import that will load CASE1_METER.xml.
The Data Exchange Parser operates in accordance with these base assumptions:
-
If the XML does not conform to the XML Schema Definition (XSD), the entire file will be rejected.
-
In cases where both epochTime and fieldTime are provided, epochTime will be used.
-
If epochTimeEnd/fieldTimeEnd is provided for an end of period Unit Profile, then it is used for the time given to AVEVA Measurement Advisor (unless you are using an irregular meter).
-
userDefinedNumber can be used to specify extra columns that you have added in the tableColumnDesc table.
-
DoubleValueUnit fields contain a unit field but this is currently ignored. The units are assumed to be the units of the specified Unit Profile or object's Input Unit Profile.
-
Many of the fields in the XSD are there for output and are ignored by File Import. The MeasurementAdvisorDataExchange.xsd file outlines the fields that are there for the output.
Understanding how the data exchange parser treats each data type
There are four different types of data that can be loaded using this parser: meter data, GQ data, event data, and the properties. If appropriate, the GQ data can be loaded as part of the meter data. Event data and properties can be loaded for either a meter, the GQ or the measuring station.
|
Data type |
Description |
|---|---|
|
Meter |
Several columns will map into the rawValue, intermediateValue, primaryFactor, miscValue, and rawValueAccum columns. For more information about these columns, see Information from the EFM database used by meter type. For example, differentialPressure will be inserted into the rawValue field for Orifice Meters and pulseCount will be inserted into the rawValue field for Pulse meters. Depending on the unit profile you have selected, gaugePressure or absolutePressure will be used. |
|
Gas Quality |
If the GQ name is not given, the Reading.name is used. If the GQ reading is submitted as part of the Analysis record, the name must be provided. If GQ data is given with meter data, the GQ data will be sent to AVEVA Measurement Advisor for processing before sending the meter data. |
|
Properties |
An organization name can be provided for the conversion of a third-party meter/GQ name to the AVEVA Measurement Advisor name, but a separate propertyOrganization is given specifically for the property. This allows for an organization to pass through flow computer properties without having to convert them all to a common name. If the propertyOrganization is given, AVEVA Measurement Advisor will lookup the AVEVA Measurement Advisor name in the objItemOrgAliasDesc table using meteringMethod, volumetricCalc, and orgItemName to resolve the AVEVA Measurement Advisor subgroup and property name, so you will have to configure this table. It will be configured in the Object Registry in the objectRegFiles. For Properties where there is a string value, this will use the objItemDomainOrgAliasDesc to resolve the alias. For example, a Metering Method of "Orifice Meter" may have an alias of "Orifice". It will be configured in the Object Registry in the objectRegFiles. Meter Properties are specified with a Metering Method and Volumetric Calculation to help determine the AVEVA Measurement Advisor property. For example, if only the property name is given, the Metering Method and Volumetric Calculation can be used to determine the sub group. Depending on the type of property, only one of the numericValue, booleanValue or stringValue will be used. |
|
Events |
The following fields will be appended to the message in the following order for storage in AVEVA Measurement Advisor . The string that is created will be truncated at 255 characters. If these fields have not been filled in, they will not be appended.
|