Please insert at least 3 characters

TRUM – Section 7.1

Data fields related to common data for total primary and secondary allocation process

This section includes the following fields:

1. Sender identification
2. Organised market place identification
3. Process identification
4. Type of gas
5. Transportation transaction identification
6. Creation date and time
7. Auction open date and time
8. Auction end date and time
9. Transportation transaction type
10. Start date and time
11. End date and time
12. Offered capacity
13. Capacity category

 

Data Field No (1) Sender Identification

No. Field Identifier Description
1 Sender identification Identification of the party that is the owner of the document and is responsible of its content.

 

Description of Accepted Values Type Length Examples
EIC Alphanumeric Maximum 16 10X1001A1001A450

 

This field indicates the identification of the owner and sender of the document. The sender of the document is identified by a unique coded identification. This code identifies the party that is the “owner” of the information being transmitted in the document and who is responsible for its content. In general this identifies the bidder or its representative. EDIGAS message includes “Standard header information”.

It should be borne in mind that for the reporting of transportation contracts, the Agency had to rely on existing industry schemas which were originally defined for different purposes and therefore have to be understood in a way that they comply with the REMIT transaction reporting regime. For its original purpose, the field and its values assume that the sender is normally a TSO or another market participant.

However, for the purpose of reporting under REMIT, the sender may not only be a self-reporting market participant, but also a third-party RRM. When the reporting entity is a third-party RRM, the third-party RRM has certain responsibilities for the document content as they have to validate the data they receive from market participants, ensure completeness, accuracy and timely submission of the data according to Article 11(2) of Commission Implementing Regulation (EU) No 1348/2014 and, if necessary, correct and resubmit the rejected data in line with Article 11(2) of Commission Implementing Regulation (EU) No 1348/2014. This is why the sender identification has to identify the third-party RRM in cases where a third-party RRM reports.

This field is mandatory.

 

Data Field No (2) Organised market place identification

No. Field Identifier Description
2 Organised market place identification Identification of organised market place.

 

Description of Accepted Values Type Length Examples
EIC Alphanumeric Maximum 16 10X1001A1001A450

 

The field should be populated with “21X-XXXXXXXXXXXY” if the capacity was allocated outside of an organised market place.

The current schema is designed to provide the identification of the organised market place operator as opposed to the organised market place. This is in conformity with the code provided in the example which is an EIC Party code.

This field corresponds to the field ORGANISEDMARKETPLACE_MARKETPARTICIOANT.IDENTIFICATION in the schema.

 

Data Field No (3) Process identification

No. Field Identifier Description
3 Process identification The identification of the auction or other process as defined by the capacity allocating entity.

 

Description of Accepted Values Type Length Examples
Unique Identification that clearly identifies the auction. Alphanumeric Maximum 35 590825

 

This field is mandatory if the capacity was allocated bilaterally (shipper – shipper) and outside of organised market place. An identification of the allocation should be provided.

 

This field corresponds to the PROCESS_TRANSACTION.IDENTIFICATION field in the schema.

 

Data Field No (4) Type of gas

No. Field Identifier Description
4 Type of gas Identifies the type of gas.

 

Description of Accepted Values Type Length Examples
High (H-gas) or Low (L-gas) calorific gas.
HC1 = High Calorific
LC1 = Low Calorific
Alphanumeric Maximum 3 characters. HC1

 

This field is mandatory for an auction.

This field corresponds to the field PROCESS_TRANSACTION.TAXONOMY.ENERGYPRODUCTTYPE in the schema.

 

Data Field No (5) Transportation transaction identification

No. Field Identifier Description
5 Transportation transaction identification A uniquely assigned identification number for the capacity allocation as assigned by the organised market place or TSO.

 

Description of Accepted Values Type Length Examples
Unique Identification that clearly identifies primary capacity allocation as assigned by the organized market place or TSO. Alphanumeric Maximum 35 Prisma identification number (Deal ID Code)

 

This field provides the identification of the transportation transaction. This data field is used only for successful auctions/other processes.

For secondary allocations, the following applies: A uniquely assigned identification number for the allocation made between the transferor and transferee as assigned by the Platform Operator or as agreed between the Balancing group(s)/shipper(s) for bilaterally agreed capacity allocations.

This field is mandatory.

This field corresponds to the RULES GOVERNING THE TRANSPORTATION_TRANSACTION CLASS field in the schema.

 

Data Field No (6) Creation date and time

No. Field Identifier Description
6 Creation date and time Creation date and time of the transaction.

 

Description of Accepted Values Type Length Examples
ISO 8601 date format using UTC time format. Date and Time 30 2014-01-29T10:35:56Z

 

This field indicates the date and time of the creation of the record indicating time zone as expressed by ISO 8601 date format / UTC time format. For secondary transaction it means the moment the two counter parties agree upon the conclusion of the deal.

This field is mandatory.

This field corresponds to the PROCESS_TRANSACTION.TRANSACTION_DATETIME field in the schema.

 

Data Field No (7) Auction open date and time

No. Field Identifier Description
7 Auction open date and time The date and time when an auction opens for bidding.

 

Description of Accepted Values Type Length Examples
ISO 8601 date format using UTC time format. Date and Time 30 2014-01-29T10:35:56Z

 

This field indicates the date and time when an auction opens for bidding. Auction open date and time expressed by ISO 8601 date format / UTC time format.

This field is mandatory but shall be left blank if the process of allocation does not involve an auction or call for orders.

This field corresponds to the PROCESS_TRANSACTION.AUCTIONOPEN_DATETIME field in the schema.

 

Data Field No (8) Auction end date and time

No. Field Identifier Description
8 Auction end date and time The date and time when an auction closes.

 

Description of Accepted Values Type Length Examples
ISO 8601 date format using UTC time format. Date and Time 30 2014-01-29T10:35:56Z

 

This field indicates the date and time when an auction closes for bidding. Auction End Date and Time as expressed by ISO 8601 date format / UTC time format.

This field is mandatory but shall be left blank if the process of allocation does not involve an auction or in case the auction is cancelled or in case of call for orders.

This field corresponds to the PROCESS_TRANSACTION.AUCTIONEND_DATETIME field in the schema.

 

Data Field No (9) Transportation transaction type

No. Field Identifier Description
9 Transportation transaction type The type identifies the nature of transportation transaction to be reported in accordance with current applicable industry standards as specified by Gas Network code on Interoperability and Data Exchange.

 

Description of Accepted Values Type Length Examples
Refer to EDIGAS Code list document for valid codes.
ZSW = Ascending clock auction
ZSX = Uniform price auction
ZSY = First come first served
ZSZ = Secondary market procedure
Alphanumeric Maximum 3 ZSX

 

This field is mandatory.

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

 

Data Field No (10) Start date and time

No. Field Identifier Description
10 Start date and time Date and time of the start of the transportation transaction runtime.

 

Description of Accepted Values Type Length Examples
ISO 8601 date format using UTC time format. Date and Time 30 2014-01-29T10:35Z

 

This field indicates the start date and time of the transportation transaction runtime. Date and time shall be expressed as: YYYY-MM-DDThh:mmZ. EDIGAS message provides one field to specify the start and end date and time. Fields 10 and 11 are specified by one field in EDIGAS message.

This field is mandatory.

This field corresponds to the TIMEINTERVAL field in the schema.

 

Data Field No (11) End date and time

No. Field Identifier Description
11 End date and time Date and time of the end of the transportation transaction runtime.

 

Description of Accepted Values Type Length Examples
ISO 8601 date format using UTC time format. Date and Time 30 2014-01-29T10:35Z

 

This field indicates the end date and time of the transportation transaction runtime. Date and time shall be expressed as: YYYY-MM-DDThh:mmZ. EDIGAS message provides one field to specify the start and end date and time. Fields 10 and 11 are specified by one field in EDIGAS message.

This field is mandatory.

This field corresponds to the TIMEINTERVAL field in the schema.

 

Data Field No (12) Offered capacity

No. Field Identifier Description
12 Offered capacity The quantity of capacity available in the auction expressed in the measure unit. Only relevant for bidding behaviour monitoring.

 

Description of Accepted Values Type Length Examples
The maximum length of this information is 17 numeric characters (decimal point included) Numeric Maximum 17 200.5

 

The Quantity of capacity available in the auction or call for orders expressed in the Measure unit. Measure unit is indicated in field 17. Only for primary allocation process.

This field is mandatory.

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

 

Data Field No (13) Capacity category

No. Field Identifier Description
13 Capacity category Applicable capacity category.

 

Description of Accepted Values Type Length Examples
The following types are permitted:
Z04 = Available total firm capacity
Z05 = Interruptible (booked)
Z06 = Firm (booked)
ZEQ = Freely allocable capacity (FZK)
ZER = Capacity with capacity allocation restrictions and capacity usage restrictions (bFZK)
ZES = Restricted-allocable capacity (BZK)
ZET = Dynamically allocable capacity (DZK)
ZEU = Temperature related and restricted capacity (TAK)
ZEW = published technical capacity
ZFA = Available interruptible capacity
ZFB = Available firm capacity
ZFD= Available total interruptible capacity
(Reference Edig@s AvailabilityType code list)
Alphanumeric Maximum 3 Z06

 

This field is mandatory for auctions.

This field corresponds to the PROCESS_TRANSACTION.TAXONOMY.AVAILABILITYTYPE field in the schema.

Last update: 09/05/2016   RSS_Icon Subscribe to this Page’s RSS