Elia Metering Messages file
The Elia Metering Messages file trigger is aimed at importing files whose structure is defined by Elia for metering data.
Supported files
This is the general purpose Elia file importer: it does not perform any data transformation and targets variables based on dynamic mapping config built from the file data.
The Elia Metering Messages trigger supports 4 file types :
- Access point messages
- Service point
- Metering Point
- CDS Access point
This means we cover message types for following roles:
- Grid User - GU (except Offshore Interconnection Point)
- Access Contract Holder - ACH
- Supplier - SUP
- Producer - PROD
- Balancing Service provider - BSP / Flexibility Service Provider - FSP (except Transfer of Energy Delivered volumes)
- CDS Operator - CDSO (except CDS Loop Losses)
Note
This trigger is based on the September 2021 version
Steps to use the Elia triger
- Ask the support to have the trigger on your account: https://help.opinum.com/tickets
- When the trigger is added to your account, create the triger you need.
- Create the source where you want the data to be sent.
- Create your source with the timezone XX
- The field EAN number must be filled
- Create variables The mapping config of each variables will be the key to process the files correctly:
- Access point messages
- Service point
- Metering Point
- CDS Access point
File name
File sent by Elia has the following structure : [RecipientRole][MsgType][EAN-code]M_M1[schedule-time]_Validity_Id.Extension
The trigger activates if the file uploaded to the Data Hub follows this structure: [any][MsgType][any].Extension. The [any] sections can contain anything the client chooses, as they do not affect the trigger. The possible messages types (MsgType) are as follows :
- Access point messages = AP
- Service point = SP
- Metering Point = MP
- CDS Access point = CA
Access point messages
Source EanNumber
The trigger searches for the source corresponding to a body line by comparing the source EanNumber with the Access Point identification code from the data section, column (4).
Variable mapping config
The trigger searches for the source's variable corresponding to mix between data and schedule line by comparing the variable MappingConfig with the string built from the line content.
The mapping config structure is as follow:
%direction%_%power_type%_%metering_type%_%compensation_type%_%profile_type%_%power_unit%_%validation%
| Field | Description | Values | Section |
|---|---|---|---|
| Direction | Identification of the direction of flow | PROD: Production of active energy (flow from client to Elia) / CONS: Consumption of active energy (flow from Elia to client) | Data |
| Power Type | Identification of the type of power | A: Active / I: Inductive / C: Capacitive | Schedule |
| Metering Type | Indication as to whether the values are net, gross or specific | N: Net / G: Gross / GG: “Green Gross” / GC: “Gross CIPU” | Schedule |
| Compensation Type | Indication as to whether the values compensated or not | NC: Non-Compensated. Used for metering purposes / C: Compensated. Used for billing purposes / A: Reserved for future use / CC: Compensated Corrected Used for specific purposes | Schedule |
| Profile Type | Indication of the load profile. This field is reserved for possible future use and has no significant meaning | ALP: Aggregated Load Profile / ULP: Undefined load profile | Schedule |
| Power Unit | Unit in which the power values are defined | KWT, KVR, W, KW, MW, VAR, KVAR, MVAR | Schedule |
| Validation | Indication as to whether the values are valid or not | True: validated by Elia / False: not validated by Elia | Schedule |
Example : CONS_A_G_C_ULP_KW_FALSE
Metering Point
Source EanNumber
The trigger searches for the source corresponding to a body line by comparing the source EanNumber with the Metering Point identification code from the data section, column (4).
Variable mapping config
The trigger searches for the source's variable corresponding to mix between data and schedule line by comparing the variable MappingConfig with the string built from the line content.
The mapping config structure is as follow:
%direction%_%power_type%_%metering_type%_%compensation_type%_%profile_type%_%unit%_%validation%
| Field | Description | Values | Section |
|---|---|---|---|
| Direction | Identification of the direction of flow | PROD: Production of active energy (flow from client to Elia) / CONS: Consumption of active energy (flow from Elia to client) | Data |
| Power Type | Identification of the type of power | A: Active / I: Inductive / C: Capacitive | Schedule |
| Metering Type | Indication as to whether the values are net, gross or specific | N: Net / G: Gross / GG: “Green Gross” / GC: “Gross CIPU” | Schedule |
| Compensation Type | Indication as to whether the values compensated or not | NC: Non-Compensated. Used for metering purposes / C: Compensated. Used for billing purposes / A: Reserved for future use / CC: Compensated Corrected Used for specific purposes | Schedule |
| Profile Type | Indication of the load profile. This field is reserved for possible future use and has no significant meaning | ALP: Aggregated Load Profile / ULP: Undefined load profile | Schedule |
| Power Unit | Unit in which the power values are defined | This depends on the quantity being measured | Schedule |
| Validation | Indication as to whether the values are valid or not | True: validated by Elia / False: not validated by Elia | Schedule |
Example : CONS_A_G_C_ULP_KW_FALSE