This chapter focuses on PRISMA’s interpretation of the data fields listed in Table 4 of the ANNEX to the Implementing Regulation. PRISMA will assemble an Edig@s message for each order or trade report.

As stated within the REMIT Transaction Reporting User Manual (TRUM) and the REMIT reporting process issued by the Edig@s Workgroup not all the data fields are mandatory for all transactions. Data fields will be populated when applicable; any deviations to the required standards will be indicated in the table below.

In case of two reporting entities (shippers), trading with each other on the secondary market and having both signed a data reporting agreement with PRISMA, two trade reports with the respective contractual part of the transaction will be sent out.

Since all price values must be reported in the currency Euro, PRISMA will convert all non-Euro values before assembling the report by using the latest available FX rate (source of FX rates: European Central Bank).


  1. General Data Fields for Class ‘GasCapacityAllocations_Document’

Data field

Description

Description of accepted values

Type

Mandatory

Value description – PRISMA

Identification

Unique identifier of the message document assigned by the issuer.

EIC, timestamp

Alphanumeric (max. 35 characters)

Yes

The identification will be set to a concatenated string that consists of the shipper’s EIC, a separator (‘_’) and a timestamp (format: YYYYMMDDhhmmsszzz).

Version

The document version is used to identify a given version of a Gas Capacity Allocations Document.

 

Numeric (max. 3 characters)

Yes

The value is initially set to 1. 

The value shall be incremented by 1 in case an update message regarding the same object is performed and the update contains changes to the previous version. 

Each resend of the document will have the same version as the last message.

Type

The type of the Gas Capacity Allocations Document.

 

Alphanumeric (max. 3 characters)

Yes

The value is set to ‘ANI’ (= Capacity allocation information) for each message.

CreationDateTime

The timestamp of the message’s creation in xs:dateTime format.

UTC

Timestamp

Yes

The timestamp of the message’s creation in xs:dateTime format.

ValidityPeriod

The start and end date and time of the period of validity covered in the document.

UTC

Timestamp

Yes

This element shall contain the proposal’s creation date and time (SEC_TRADE_PROPOSAL.CREATED_AT) as well as the proposal’s expiration date and time (SEC_TRADE_PROPOSAL.EXPIRATION_DATE).

 The creation timestamp and the expiration timestamp are separated by ‘/’; the dates have format YYYY-MM-DD, the time has format hh:mmZ; dates and time are separated with ‘T’.

ContractReference

 

 

 

No

The element contractReference is optional and will not be used in the messages according to this document.

ContractType

 

 

 

No

The element contractType is optional and will not be used in the messages according to this document

ApplicationContext

 

 

 

No

The element applicationContext is optional and will not be used in the messages according to this document.


 

 

  1. Common Data Fields

The following data fields defined in the Transaction Reporting User Manual (TRUM) issued by ACER shall be part of any report to ACER. They will be complemented by additional fields from the REMIT Reporting Process issued by the Edig@s Workgroup.

 

 

#

Data field

Description

Description of 

accepted values

Type

Mandatory

Value description - PRISMA

1

Sender identification

The identification of the party who has issued the document which is the EIC of PRISMA.

In case, reporting through ACER channel is not part of this contract, the identification of the party which who has issued the document which is the the EIC of another RM.

EIC

Alphanumeric (max. 16 characters)

Yes

The element shall contain PRIMA’s EIC, that is ‘21X000000001225H’, if the ACER reporting channel is activated. The element shall contain another RRM’s EIC  if the ACER reporting channel is not activated.

The codingScheme attribute shall contain the code ‘305’.

1a[1]

Market role of issuer

Identification of the role that the party who has issued the document is playing. 

 

Alphanumeric (max. 3 characters)

Yes

According to the Edig@s Implementation Guidelines only the following codes are permitted: ZSO (System Operator), ZUJ (Auction Office) and ZUF (Capacity platform operator). Since none of the codes fits to the shipper/transport customer role, it is foreseen to use the code ‘ZUF’.

1b[2]

Recipient identification

The identification of the party who is receiving the document which is ACER. 

 

 

 

The element shall contain ACER’s EIC. The value is set to ‘10X1001B1001B61Q’ as per default.

The codingScheme attribute shall contain the code ‘305’.   

1c[3]

Market role of recipient

The role being played by the recipient of the document for this transmission. The recipient is ACER.

 

 

Yes

The element shall contain the value ‘ZUA’, which is the code for ‘Market Information Aggregator’.

2

Organised market place identification

Identification of the organised market place.

EIC

Alphanumeric (max. 16 characters)

No

The element shall contain the EIC of PRISMA. The value is set to ‘21X000000001225H’as per default.

The codingScheme attribute shall contain the code ‘305’.   

3

Process identification

The identification of the auction or other process as defined by the capacity allocation entity

ID that clearly identifies the auction

Alphanumeric (max. 35 characters)

Yes

The identification is set to the identification of the secondary proposal (SEC_TRADE_PROPOSAL.ID), regardless of whether the REMIT message was sent for a proposal, a response or a concrete trade.

4

Type of gas

Identifies the type of gas.

HC1 = High Calorific, LC1 = Low Calorific

Alphanumeric (max. 3 characters)

No

The following codes shall be used in accordance to the type of gas:

  • In case the type of gas is “H gas” the element shall contain the code ‘HC1’. In case the type of gas is “L gas” the element shall contain the code ‘LC1’.  

5

Transportation transaction identification

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. 

Deal ID Code

Alphanumeric (max. 35 characters)

Yes

There is a distinction of cases whether the message is sent for a proposal, a response or a trade. 

  • In case of a trade message the element shall contain the trade ID (SEC_TRADE.ID).
  • In case of a response message the element shall contain the string response ID  (SEC_TRADE_RESPONSE.ID).
  • In case of a proposal message the element shall contain the string proposal ID (SEC_TRADE_PROPOSAL.ID).

6

Creation date and time

Creation date and time of the transaction.

 

ISO 8601 date format using UTC time format

Timestamp (max. 30 characters)

Yes

The element shall contain the secondary proposal’s creation timestamp (SEC_TRADE_PROPOSAL.CREATED_AT) in xs:dateTime format (UTC).

7

Auction open date and time

The date and time that an auction is open for bidding. In case of a secondary procedure this shall be the date and time when the proposal was created, and it shall be used only the trading procedure is CFO.  

ISO 8601 date format using UTC time format

Timestamp (max. 30 characters)

Yes (left blank if the process of allocation does not involve an auction or call for orders)

The element shall contain the secondary proposal’s creation timestamp (SEC_TRADE_PROPOSAL.CREATED_AT) in xs:dateTime (UTC).

 

8

Auction end date and time

The date and time that an auction closes. In case of a secondary procedure this shall be the date and time when the proposal expires, and it shall be used only the trading procedure is CFO.  

ISO 8601 date format using UTC time format

Timestamp (max. 30 characters)

Yes (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)

The element shall contain the secondary proposal’s expiration timestamp (SEC_TRADE_PROPOSAL.EXPIRATION_DATE) in xs:dateTime (UTC).

 

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.

Refer to EDIGAS Code list document for valid codes

Alphanumeric (max. 3 characters)

Yes

The Edig@s Code “ZSZ” (= Secondary market procedure) will be used for any message.

10

Start date and time

Date and time of the start of the transportation transaction runtime.

ISO 8601 date format using UTC time format (YYY-MM-DDThh:mm:ssZ)

Timestamp (max. 30 characters)

Yes

There is a distinction of cases whether the message is sent for a proposal, a response or a trade. 

  • In case of a proposal message the element shall contain the proposal’s runtime start (date and time).
  • In case of a response message the element shall contain the trade’s, runtime start (date and time).
  • In case of a trade message the element shall contain the trade’s, runtime start (date and time).

11

End date and time

Date and time of the end of the transportation transaction runtime.

ISO 8601 date format using UTC time format (YYY-MM-DDThh:mm:ssZ)

Timestamp (max. 30 characters)

Yes

There is a distinction of cases whether the message is sent for a proposal, a response or a trade. 

  • In case of a proposal message the element shall contain the proposal’s end (date and time).
  • In case of a response message the element shall contain the trade’s runtime end (date and time).
  • In case of a trade message the element shall contain the trade’s runtime end (date and time).

12

Offered capacity

The quantity of capacity available in the auction or call for orders expressed in the measure unit. Only relevant for bidding behaviour monitoring within primary allocation process.

 

Numeric (max. 17 characters, including a decimal point)

Yes (if applicable)

Does not have to be provided since this applies to Primary Allocation Process only.

13

Capacity category

Applicable capacity category

Refer to EDIGAS Code list document for valid codes

Alphanumeric (max. 3 characters)

Yes

The following codes shall be used for the capacity categories:

  • ‘Z06’ for “firm” 
  • ‘ZFB’ for “firm additional” 
  • ‘ZEQ’ for “FZK” 
  • ‘ZEQ’ for “FZKc” 
  • ‘ZFB’ for “FZKinc” 
  • ‘ZER’ for “bFZK” 
  • ‘ZES’ for “BZK” 
  • ‘ZET’ for “DZK”
  • ‘Z05’ for “interruptible”
  • ‘ZFA’ for “interruptible level 1”
  • ‘ZFA’ for “interruptible level 2”
  • ‘ZFA’ for “interruptible level n”
  • ‘ZFA’ for “backhaul capacity”
  • ‘ZFA’ for “backhaul level 1”
  • ‘ZFA’ for “backhaul level 2”
  • ‘ZFA’ for “backhaul level n”
  • ‘ZFA’ for “uBZK”
  • ‘ZFA’ for “UKc”
  • ‘ZEQ’ for “FZKunrab”
  • ‘ZES’ for “BZKunrab”
  • ‘ZET’ for “DZKunrab”
  • ‘ZER’ for “bFZKunrab”
  • ‘ZFA’ for “UKunrab”

In case of bundled capacity where different combinations of capacity categories may occur, only the main classification of “firm” (code ‘Z06’) and interruptible (code ‘Z05’) capacity shall be considered.


 

  1. Data fields for lifecycle reporting

The following data fields shall be part of any report to ACER regarding transaction reporting lifecycle events:

#

Data field

Description

Description of 

accepted values

Type

Mandatory

Value description - PRISMA

14

Action Type

Status code of the report to be reported in accordance with current applicable industry standards as specified in Gas Network code on Interoperability and Data Exchange.

Refer to EDIGAS Code list document for valid codes

 

Alphanumeric (max. 3 characters)

Yes

The following codes shall be used in accordance to the ACER status of the message:

  • In case the message shall have the status ‘NEW’ the element shall contain the code ‘62G’. In case the message shall have the status ‘CANCELLED’ the element shall contain the code ‘63G’.

 

 

 

 

 

 


 

  1. Data fields for quantity and price reporting

The following data fields shall be part of any report to ACER regarding capacity quantity and price:

#

Data field

Description

Description of 

accepted values

Type

Mandatory

Value description - PRISMA

15

Quantity

Total number of units allocated with the transportation transaction as expressed in the measure unit.

 

Numerical (max. 17 characters, including decimal point)

Yes

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

  • In case of a proposal message the element shall contain the proposal’s quantity amount.
  • In case of a response message the element shall contain the trade’s quantity amount.
  • In case of a trade message the element shall contain the trade’s quantity amount.

16

Measure unit

The unit of measurement used for all the quantities expressed within a time series.

Refer to EDIGAS Code list document for valid codes

Alphanumeric (max. 3 characters)

 

Yes

There is a distinction of cases regarding the physical unit of the network point to which the trade or proposal belongs. 

  • In case the physical unit of the secondary proposal / secondary trade is “kWh/h” the code ‘KW1’ shall be used. Values in kWh/d will be converted in kWh/h (see value description of respective fields below).

17

Currency

The currency in which the monetary amount is expressed (currency of the price using the smallest denomination in the currency system). The reported currency is always expressed in EUR.

Refer to EDIGAS Code list document for valid codes

 

List of international ISO 4217 currency codes (max. 3 characters)

 

Yes (if available)

The element shall contain the code ‘EUR’.

18

Total price

Reserve price at time of the auction plus auction premium or regulated tariff in case of other allocation mechanism than auction. Each Transmission System Operator(s) would report their part of a bundled transaction.

 

Numeric ISO 6093 (max. 17 characters)

Yes (if available)

The value ‘0.0’ shall be used as predefined default value for all messages.

19

Fixed or floating reserve price

Identification of the type of reserve price.

FIX = Fixed Price

FLO = Floating Price

Alphanumeric (max. 3 characters)

Yes (if available)

The element reserve_Price.type is optional and will not be used in the messages.

20

Reserve price

The identification of the reserve price for the auction. Each Transmission System Operator would report their part of a bundled transaction.

 

Numeric ISO 6093 (max. 17 characters)

Yes (if available)

The element reserve_Price.amount is optional and will not be used in the messages.

21

Premium price

The additional amount on top of the reserve price as agreed between Transmission System Operator(s) and the market participant. Each Transmission System Operator would report their part of a bundled transaction.

 

Numeric ISO 6093 (max. 17 characters)

Yes (if available)

The element premium_Price.amount is optional and will not be used in the messages.

 

  1. Data fields for identification of location and market participant

The following data fields shall be part of any report to ACER regarding identification of location and market participant:

#

Data field

Description

Description of 

accepted values

Type

Mandatory

Value description - PRISMA

22

Network point identification

The identification of the network point or bundled network point expressed as EIC.

EIC

Alphanumeric (max. 16 characters)

Yes

The EIC for the network point or for the bundled network point respectively is used for this element. In case there is no EIC (for the network point or bundled network point respectively) the message will not be generated and thus will not be sent.

23

Bundling

Specification whether or not the proposal/response/trade belongs to a bundled network point.

 

Alphanumeric (max. 3 characters)

No

The following codes shall be used in accordance to the type of bundling:

  • In case of an ‘unbundled’ secondary proposal / response / trade the element shall contain the code ‘ZEP’.
  • In case of a ‘bundled’ secondary proposal/response/trade the element shall contain the code ‘ZEO’.  

24

Direction

Specification of direction of transportation transaction

Refer to EDIGAS Code list document for valid codes

Alphanumeric (max. 3 characters)

Yes (if applicable)

The following codes shall be used in accordance to the type of bundling:

  • In case of an ‘unbundled’ secondary proposal / response / trade the element shall contain the code ‘Z03’ if the direction is “exit” or ‘Z02’ if the direction is “entry”. In case of a ‘bundled’ secondary proposal/response/trade the element shall contain the code ‘Z03’ as a default because there is no other code for bundled network points available.  

25

TSO 1 identification

The identification of the Transmission System Operator for which the data reporting is made. 

EIC

Alphanumeric (max. 16 characters)

Yes 

There is a distinction of cases whether or not the proposal/response/trade belongs to a network point or bundled network point. 

  • In case of an ‘unbundled’ secondary proposal/response/ trade the element shall contain the EIC of the according Transmission System Operator.
  • In case of a ‘bundled’ secondary proposal/response/trade the element shall contain the EIC of the Transmission System Operator that belongs to the exit network point.  

The codingScheme attribute shall contain the code ‘305’.

26

TSO 2 identification 

The identification of the counter Transmission System Operator.

EIC

Alphanumeric (max. 16 characters)

Yes (if field 24 is filled with an ‘Y’)

The element shall only be used in case of a ‘bundled’ secondary proposal/response/trade and in that case it shall contain the EIC of the Transmission System Operator that belongs to the entry network point.  

The codingScheme attribute shall contain the code ‘305’.

27

Market participant identification

The market participant to which the capacity is assigned.

EIC

Alphanumeric (max. 16 characters)

Yes (for primary allocations)

The element primary_MarketParticipant.identification is optional, however, shall contain the EIC of the shipper on whose behalf the report is sent.

28

Balancing group or portfolio code

The balancing group (or balancing groups in case of bundled products) to which the buying shipper belongs or the portfolio code used by the buying shipper if a balancing group is not applicable.

 

Alphanumeric (max. 35 characters)

Yes (left blank where balancing group and portfolio do not apply)

There is a distinction of cases whether or not the proposal/response/trade belongs to a network point or bundled network point. 

  • In case of an ‘unbundled’ secondary proposal / response / trade the element shall contain the balancing group (if applicable) or portfolio code (if applicable) that belongs to the buying shipper.
  • In case of a ‘bundled’ secondary proposal/response/trade the element shall contain the balancing group(s) (if applicable) or portfolio code(s) (if applicable) that belongs to the buying shipper. 

The codingScheme attribute shall contain the code ‘ZSO’.


 

 

  1. Data fields applicable only for secondary allocations

The following data fields shall be part of any report to ACER regarding identification of location and market participant:

#

Data field

Description

Description of 

accepted values

Type

Mandatory

Value description - PRISMA

29

Procedure applicable

Specification of procedure applicable. 

 

Refer to EDIGAS Code list document for valid codes 

A01 = CFO 

A02 = FCFS 

A03 = OTC 

Alphanumeric (max. 3 characters)

No

The following codes shall be used in accordance to the trading procedure:

  • In case of ‘CFO’ the element shall contain the code ‘A01’.
  • In case of ‘FCFS’ the element shall contain the code ‘A02’.In case of ‘OTC’ the element shall contain the code ‘A03’.

30

Maximum bid amount

The maximum the transferee would be willing to offer, expressed in the currency per measure unit. 

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (if applicable to CFO procedure)

There is a distinction of cases: 

  • In case of a proposal message (proposal to buy) the element shall contain the proposal’s price.
  • In case of a response message (response to proposal to sell) the element shall contain the response’s price.
  • In case of a trade message (response to proposal to sell) the element shall contain the trade’s price.

In case the measurement unit of the price is not “kWh/h” but “kWh/d” the price shall be divided by 24 (or 23 or 25 on clock change days).

The price shall be expressed in Euro; thus, in case the price is given for Euro Cent the price shall be divided by 100 and into Euro in case it is expressed in a currency other than Euro.

31

Minimum bid amount

The minimum the transferor would be willing to offer, expressed in the currency per measure unit. 

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (if applicable to CFO procedure)

There is a distinction of cases: 

  • In case of a proposal message (proposal to sell) the element shall contain the proposal’s price.
  • In case of a response message (response to proposal to buy) the element shall contain the response’s price.
  • In case of a trade message (response to proposal to buy) the element shall contain the trade’s price.

In case the measurement unit of the price is not “kWh/h” but “kWh/d” the price shall be divided by 24 (or 23 or 25 on clock change days).

The price shall be expressed in Euro; thus, in case the price is given for Euro Cent the price shall be divided by 100 and into Euro in case it is expressed in a currency other than Euro.

 

32

Maximum quantity

The maximum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. The element is optional and shall only be used in case of a proposal to buy or a response to a proposal to sell.

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (if applicable to CFO procedure)

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

  • In case of a proposal message (proposal to buy) the element shall contain the proposal’s quantity amount.
  • In case of a response message (response to proposal to sell) the element shall contain the response’s quantity amount.
  • In case of a trade message (response to proposal to sell) the element shall contain the trade’s quantity amount.

33

Minimum quantity

The minimum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. The element is optional and shall only be used in case of a proposal to sell or a response to a proposal to buy.

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (if applicable to CFO procedure)

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

  • In case of a proposal message (proposal to sell) the element shall contain the proposal’s quantity amount.
  • In case of a response message (response to proposal to buy) the element shall contain the response’s quantity amount.
  • In case of a trade message (response to proposal to buy) the element shall contain the trade’s quantity amount.

34

Price paid to TSO (underlying price) 

 

The price paid to the Transmission System Operator (underlying price) is only applicable when there is an assignment expressed in the currency per measure unit which must be kWh/h.

The element is used only in case the proposal’s transaction type is ‘Assignment’ and either it is a proposal to sell or a response to a proposal to buy.

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (left blank in case Transportation transaction type is ‘Transfer of use’ or ‘Sublet’)

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

  • In case of a proposal message (proposal to sell) the element shall contain the sum of the regulated tariff and auction surcharge (if applicable) of the underlying deal.  
  • In case of a trade message or a response message (response to proposal to buy) the element shall contain the sum of the regulated tariff and auction surcharge (if applicable) of the underlying deal.  
  • In all cases, if the underlying regulated tariff is empty the regulated tariff of the according network point shall be used (or the sum of tariffs in case of a bundle respectively.

35

Price the transferee pays to the transferor 

Price the transferee pays to the transferor expressed in the currency per measure unit which must be kWh/h.

 

Numeric ISO 6093 (max. 17 characters, including decimal mark)

Yes (if available)

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

In case the measurement unit of the price is not “kWh/h” but “kWh/d” the price shall be divided by 24 (or 23 or 25 on clock change days).

The price shall be expressed in Euro; thus, in case the price is given for Euro Cent the price shall be divided by 100.  

The price shall be converted in Euro in case it is expressed in a currency other than Euro.

The format of the price shall be xs:decimal with a total number of 17 digits.

36

Transferor identification

The market participant giving up the capacity as expressed by the LEI, EIC, GS1, BIC or ACER Code(s). 

 

EIC

Alphanumeric (max. 16 characters)

 

EIC of the Initiating Shipper (Proposal to Sell) or of the Responding Shipper (Proposal to Buy); in case of anonymous trading, only populate this field if the data is sent on behalf of the transferor.

37

Transferee identification

The market participant receiving the capacity from the transferor.

 

EIC

Alphanumeric (max. 16 characters)

 

EIC of the Initiating Shipper (Proposal to Buy) or of the Responding Shipper (Proposal to Sell); in case of anonymous trading, only populate this field if the data is sent on behalf of the Transferee.[4]

38

BID ID

The identification of the bid as defined by the reporting entity.

 

 

Yes

There is a distinction of cases whether the message is sent for a proposal, a response or a trade. 

  • In case of a proposal message the element shall contain the proposal ID.
  • In case of a response message the element shall contain the response ID.
  • In case of a trade message the element shall contain the trade ID.

39

Auction round number 

The auction round number is an integer that increments every time an auction achieves no result and is re-run with different parameters - starting at 1.

 

Integer

Yes

The value is set to per default for all cases.

40

Bid price

The price bid for each unit of capacity excluding the reserve price. Expressed in the currency and measure unit.

 

 

Yes

There is a distinction of cases:

  • In case of a proposal message the element shall contain the proposal’s price.
  • In case of a response message the element shall contain the response’s quantity amount.
  • In case of a trade message the element shall contain the trade’s quantity amount.

In case the measurement unit of the price is not “kWh/h” but “kWh/d” the price shall be divided by 24 (or 23 or 25 on clock change days).

The price shall be expressed in Euro; thus, in case the price is given for Euro Cent the price shall be divided by 100.  

The price shall be converted in Euro in case it is expressed in a currency other than Euro.

41

Bid quantity

The quantity being bid for expressed in the measure unit.

 

 

Yes

There is a distinction of cases whether the message is sent for a proposal, a response, or a trade. 

  • In case of a proposal message the element shall contain the proposal’s quantity amount.
  • In case of a response message the element shall contain the response’s quantity amount.
  • In case of a trade message the element shall contain the trade’s quantity amount.


 


[1] Not defined TRUM field; defined within the REMIT Reporting Process, Version 5.1 issued by the Edig@s Workgroup 

[2] Not defined TRUM field; defined within the REMIT Reporting Process, Version 5.1 issued by the Edig@s Workgroup 

 

[3] Not defined TRUM field; defined within the REMIT Reporting Process, Version 5.1 issued by the Edig@s Workgroup 

[4] In case of anonymous trading either data field 36 or 37 are left blank in order to not be reported to the counterparty