7.3 Data fields for quantity and price reporting

7.3 Data fields for quantity and price reporting

This section includes the following fields:

Field No. Field name Primary allocation Secondary allocation
15 Quantity M M
16 Measure unit M M
17 Currency M M
18 Total price M M
19 Fixed or floating reserve price M* -
20 Reserve price M* M*
21 Premium price M* M*

M = mandatory; O = optional; - = does not apply; * = conditionally required; DV = default value specified in TRUM

Data Field (15) Quantity

No. Field Identifier Description
15 Quantity Total number of units allocated with the transportation transaction as expressed in the measure unit.
Description of Accepted Values Type Length Examples
Up to 17 numerical digits (decimal mark included) in the format xxxxx.yyyyy. Number Up to 17 20.5

This field identifies the quantity or capacity (energy per unit of time) for the contract, i.e. the contract size. The value that shall be reported in this field is the energy per time unit, e.g. the number of kW (i.e. kWh/h), expressed in the measure unit indicated in Data Field (16).

In case of unmatched orders (“unsuccessful MP”), that does not ends with a transaction and thus with allocated capacity, this field should be populated with “0” (zero).

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. The number of decimal places identifying the fractional part of the quantity depends on local market rules. A decimal point value may be used to express values that are inferior to the defined unit of measurement. The decimal mark that separates the digits forming the integral part of a number from those forming the fractional part (ISO 6093) shall always be a period (“.”).

This field is mandatory for primary and secondary allocations.

This field corresponds to the field CONTRACT_QUANTITY.AMOUNT in the schema.

Data Field (16) Measure unit

No. Field Identifier Description
16 Measure unit The unit of measurement used.
Description of Accepted Values Type Length Examples

 

  • KW1 = Kilowatt - hour per hour (kWh/h)
  • KW2 = Kilowatt - hour per day (kWh/d) HM1 = Million cubic meters per hour
  • HM2 = Million cubic meters per day
  • TQH = Thousand cubic meters per hour
  • TQD = Thousand cubic meters per day
  • MQ6 = Normal cubic meters per hour
  • MQ7 = Normal cubic meters per day
  • KWH = Kilowatt hour (KWh)
  • GWH= Gigawatt hour (GWh)
Alphanumeric 3 KW1

This field identifies the unit of measurement used for the reported quantity in Data Field (12), Data Field (15) and Data Field (41).

In case of allocations concluded on an organised market place or on a booking platform, the value reported in this field should correspond to the unit as advertised by the auction platform.

This field is mandatory for primary and secondary allocation.

This field corresponds to the field QUANTITY_MEASUREUNIT.CODE in the schema.

Data Field (17) Currency

No. Field Identifier Description
17 Currency The currency in which the monetary amount is expressed.
Description of Accepted Values Type Length Examples
  • EUR = Euro
  • BGN = Bulgarian lev

  • CHF = Swiss franc

  • CZK = Czech koruna

  • DKK = Danish krone

  • GBP = Pound sterling

  • HUF = Hungarian forint

  • ISK = Icelandic króna

  • NOK = Norwegian krone

  • PLN = Polish złoty

  • RON = Romanian new leu

  • SEK = Swedish krona/kronor

  • USD = U.S. dollar
 
Text 3 EUR

This field identifies the currency in which the monetary amount is expressed (currency of the price using the smallest denomination in the currency system).

If needed, the Agency recommends using the last available European Central Bank foreign exchange reference rate for the currency conversion valid for the day of the execution of the transaction.

This field is mandatory for primary and secondary allocations.

This field corresponds to the field CURRENCY.CODE in the schema

Data Field (18) Total price

No. Field Identifier Description
18 Total price Reserve price at time of the auction plus auction premium or regulated tariff in case of other allocation mechanism than auction.
Description of Accepted Values Type Length Examples
Up to 17 numerical digits (decimal mark included) in the format xxxxx.yyyyy. Number Up to 17 1.8

This field indicates the total price of the unit of allocated capacity, being primary or secondary. In case of allocation of bundled capacity, each TSO should report the relevant individual share of the price of the transaction. The individual contributions to the price of those transactions are matched through Data Field (5), i.e. transportation transaction identification.

The price reported in this field shall be expressed in the currency reported in Data Field (17). It is worth noticing that the reported Total price value should be valid for one unit of the contracted capacity but not for the price of the total volume of the contracted capacity per network user.

In case of both bundled and unbundled capacity, the value reported in this field should correspond to the sum of Data Field (20) and Data Field (21). The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

This field is mandatory for primary and secondary allocations.

This field corresponds to the field TOTAL_PRICE.AMOUNT in the schema.

Population of Data Field (18) in case of zero premium and reserve price

The Agency is aware that on some occasions it is possible to have a zero (0) reserve price according to the tariff methodologies, e.g. for in-country points or points connected to storage facilities. In such cases, if the auction ends without premium, the total price reported in Data Field (18) would be also equal to zero.

Data Field (19) Fixed or floating reserve price

No. Field Identifier Description
19 Fixed or floating reserve price Identification of the type of the reserve price.
Description of Accepted Values Type Length Examples

 

  • Z07 =  Fixed Price
  • Z08 = Floating Price
Alphanumeric 3 Z07

This field is mandatory if Data Field (20) Reserve price is populated in primary allocations. The field qualifies the type of the reserve price reported in Data Field (20).

This field corresponds to the field RESERVE_PRICE.TYPE in the schema.

Data Field (20) Reserve price

No. Field Identifier Description
20 Reserve price The identification of the reserve price for the auction.
Description of Accepted Values Type Length Examples
Up to 17 numerical digits (decimal mark included) in the format xxxxx.yyyyy. Number Up to 17 1.8

This field identifies the reserve price for the auction, if applicable. In case of bundled capacity, each TSO should report the relevant individual share of the price of the transaction.

The price reported in this field shall be expressed in the currency reported in Data Field (17) per unit of measurement as indicated in Data Field (16).

This field is mandatory for allocations occurring via auctions (primary allocations and secondary if occurred via auctions) where a reserve price applies.

This field corresponds to the field RESERVE_PRICE.AMOUNT in the schema.

Data Field (21) Premium price

No. Field Identifier Description
21 Premium price The identification of the premium price for the auction.
Description of Accepted Values Type Length Examples
Up to 17 numerical digits (decimal mark included) in the format xxxxx.yyyyy. Number Up to 17 1.8

This field identifies the additional amount on top of the reserve price as agreed between TSO and the market participant. In case of bundled capacity, each TSO should report the relevant individual share of the premium of the transaction.

The price reported in this field shall be expressed in the currency reported in Data Field (17) per unit of measurement as indicated in Data Field (16).

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

This field is mandatory for allocations occurring via auctions (primary allocations and secondary if occurred via auctions) where a premium applies.

This field corresponds to the field PREMIUM_PRICE.AMOUNT in the schema.

Updated: 
13/03/2024