TRUM – Section 7 Reporting of gas transportation contracts The reporting of gas transportation contracts to ACER between two balancing zones within the European Union will be mandatory from 7 April 2016 onwards. In this Chapter, the Agency provides information on how the data fields listed in Table 4 of the Annex to the Implementing Acts should be populated. In subsequent editions of the TRUM, the Agency will also provide further guidance on how to report gas transportation contracts. It should be noted that Table 4 of the Annex to the Implementing Acts shall be used for the reporting of both standard and non-standard gas transportation contracts. It is worth noting that not all the data fields are mandatory for all transactions. Data fields are expected to be populated when applicable according to this manual. The Agency has prepared a list of trading scenarios to show what is expected and applicable to each scenario. The trading scenarios are listed in ANNEX II. The information shall be provided for the following bookable points of the transmission system: (a) all interconnection points; (b) entry points of production facilities; (c) for exit points connected to a single customer; (d) entry and exit points to and from storage; (e) entry and exit points to and from LNG facilities and physical hubs. In case of bundled capacity each reporting entity reports its contractual part of the transaction. The “Description of Accepted Values” only contains examples of values. Last update: 09/05/2016
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
TRUM – Section 7.2 Data fields for lifecycle reporting This section includes the following fields: 14. Action type Data Field No (14) Action type No. Field Identifier Description 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. Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. 62G = Active. 63G = Cancelled. 66G = Changed. Alphanumeric Maximum 3 62G This information provides the status of the document. The sender indicates if the report submitted is valid and never modified, updated or not valid anymore: 62G = Active. This data means that the report is valid and has never been updated 63G = Cancelled. This data means that the report is not valid anymore 66G = Changed. This data means that the report is valid after being updated. This field is mandatory. This field corresponds to the field PROCESS_TRANSACTION.ACTION_STATUS.CODE in the schema. Last update: 09/05/2016
TRUM – Section 7.3 Data fields for quantity and price reporting This section includes the following fields: 15. Quantity 16. Measure unit 17. Currency 18. Total price 19. Fixed or floating reserve price 20. Reserve price 21. Premium price Data Field No (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 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 (“.”). All quantities are unsigned values. Numerical 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. 20.5 This field is mandatory. This field corresponds to the field CONTRACT_QUANTITY.AMOUNT in the schema. Data Field No (16) Measure unit No. Field Identifier Description 16 Measure unit The unit of measurement used. Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. 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 Maximum 3 KW1 The unit of measurement used for all the quantities expressed within a time series. This field is mandatory. This field corresponds to the field QUANTITY_MEASUREUNIT.CODE in the schema. Data Field No (17) Currency No. Field Identifier Description 17 Currency The currency in which the monetary amount is expressed. Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. List of international ISO 4217 currency codes. Maximum 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). The schema only accepts one value for this field. The reported currency is always expressed in EUR. This field is mandatory. This field corresponds to the field CURRENCY.CODE in the schema. Data Field No (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 The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field indicates the total price. Each TSO would reports one leg of bundled transaction. Those transactions are matched through data field no 5, i.e. transportation transaction identification. This field is mandatory. This field corresponds to the field TOTAL_PRICE.AMOUNT in the schema. Data Field No (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 Refer to EDIGAS Code list document for valid codes. Z07 = Fixed Price Z08 = Floating Price Alphanumeric Maximum 3 Z07 This field is mandatory if there is a reserve price (field 20). This field corresponds to the field RESERVE_PRICE.TYPE in the schema. Data Field No (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 The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed Numeric ISO 6093 17 1.8 This field identifies the reserve price for the auction. Each TSO would report one leg of bundled transaction. This field is mandatory for auctions. This field corresponds to the field RESERVE_PRICE.AMOUNT in the schema. Data Field No (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 The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 The additional amount on top of the reserve price as agreed between TSO and the market participant. Each TSO would report one leg of bundled transaction. This field is mandatory for auctions. This field corresponds to the field PREMIUM_PRICE.AMOUNT in the schema. Last update: 09/05/2016
TRUM – Section 7.4 Data fields for identification of location and market participant This section includes the following fields: 22. Network point identification 23. Bundling 24. Direction 25. TSO 1 identification 26. TSO 2 identification 27. Market participant identification 28. Balancing group or portfolio code Data Field No (22) Network point identification No. Field Identifier Description 22 Network point identification Within a network system according to the EIC code. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC measurement point code. Alphanumeric The maximum length of the connection point identification is 35 alphanumeric characters. The maximum length of the coding scheme is 3 alphanumeric characters. 10Y0000123456789 Both the connection point identification and the coding scheme are mandatory. This field corresponds to the field PROCESS_TRANSACTION.CONNECTIONPOINT.IDENTIFICATION – CODINGSCHEME in the schema. Data Field No (23) Bundling No. Field Identifier Description 23 Bundling Specification of bundling Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. ZEO for Bundled, ZEP for Unbundled Alphanumeric Maximum 3 ZEO This field is represented in the Edigas schema as “CapacityType” and the code for “bundled” is “ZEO” and that for unbundled is “ZEP”. This field is mandatory for auctions. This field corresponds to the field PROCESS_TRANSACTION.CAPACITYTYPE.CODE in the schema. Data Field No (24) Direction No. Field Identifier Description 24 Direction Specification of direction. Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. Z02 = Input Quantity Z03 = Output Quantity Alphanumeric Maximum 3 Z02 This field specifies the direction of the transportation transaction. The TSO sells capacity with a direction in both bundled and unbundled capacity. For bundled capacity the direction is that of the reporting TSO’s side. This field is mandatory. This field corresponds to the field DIRECTION.CODE in the schema. Data Field No (25) TSO 1 identification No. Field Identifier Description 25 TSO 1 identification The identification of the TSO for which the data reporting is made. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC party code. Alphanumeric The maximum length of a responsible TSO’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. 10Y0000123456789 This field identifies the TSO for which the data reporting is made. Both the identification and the coding scheme are mandatory. This field corresponds to the field PROCESS_TRANSACTION.RESPONSIBLETSO_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema. Data Field No (26) TSO 2 identification No. Field Identifier Description 26 TSO 2 identification The identification of the counter TSO. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC party code. Alphanumeric The maximum length of an adjacent TSO’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. 10Y0000123456789 This field is mandatory if the field 23 is filled in with ZEO. Both the identification and the coding scheme are dependent. This field corresponds to the field PROCESS_TRANSACTION.ADJACENTTSO_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema. Data Field No (27) Market participant identification No. Field Identifier Description 27 Market participant identification The market participant to which the capacity is assigned. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC party code. Alphanumeric The maximum length of a primary market participant’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. 10X1001A1001A450 This field identifies the market participant the capacity is assigned. This field is mandatory for primary allocations. This field corresponds to the field PRIMARY_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema. Data Field No (28) Balancing group or portfolio code No. Field Identifier Description 28 Balancing group or portfolio code The balancing group (or balancing groups in case of bundled products) to which the shipper belongs or the portfolio code used by the shipper if a balancing group is not applicable. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “ZSO” for a TSO managed code or the code “305” for an EIC Account code. Alphanumeric The maximum length of an internal account’s identification is 35 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. This field is mandatory and used only where balancing group portfolio or accounts apply. Internal account needs to be reported. “Internal account TSO” code is equivalent to TSO 1 Identification. Internal account is assigned by TSO 1 Identification. This field corresponds to the field PRIMARY_MARKETPARTICIPANT.ACCOUNT.INTERNALACCOUNT in the schema. Last update: 09/05/2016
TRUM – Section 7.5 Data fields applicable only for secondary allocations This section includes the following fields: 29. Procedure applicable 30. Maximum bid amount 31. Minimum bid amount 32. Maximum quantity 33. Minimum quantity 34. Price paid to TSO (underlying price) 35. Price the transferee pays to the transferor 36. Transferor identification 37. Transferee identification Data Field No (29) Procedure applicable No. Field Identifier Description 29 Procedure applicable Specification of procedure applicable. Description of Accepted Values Type Length Examples Refer to EDIGAS Code list document for valid codes. A01 = CFO, call for orders A02 = FCFS, first come first served A03 = OTC, Over the counter A04 = sublet Alphanumeric Maximum 3 A01 This field is mandatory only in the case of secondary market allocations. This field corresponds to the field PROCESS_TRANSACTION.SECONDARYMARKET_PROCEDURE.CODE in the schema. Data Field No (30) Maximum bid amount No. Field Identifier Description 30 Maximum bid amount The maximum the transferee would be willing to offer, expressed in the currency per measure unit. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field is mandatory for “Call for orders” procedure. This attribute may be used only in the case of a secondary market transaction. This field corresponds to the field MAXIMUMBID_PRICE.AMOUNT in the schema. Data Field No (31) Minimum bid amount No. Field Identifier Description 31 Minimum bid amount The minimum the transferor would be willing to offer, expressed in the currency per measure unit. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field is mandatory for “Call for orders” procedure. This attribute may be used only in the case of a secondary market transaction. This field corresponds to the field MINIMUMBID_PRICE.AMOUNT in the schema. Data Field No (32) Maximum quantity No. Field Identifier Description 32 Maximum quantity The maximum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). Numeric ISO 6093 17 1.8 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 (“.”). All quantities are unsigned values. This field is mandatory for“Call for orders” procedure. The maximum quantity the transferee/transferor would be willing to acquire/sell. This attribute may be used only in the case of a secondary market transaction. This field corresponds to the field MAXIMUMBID_QUANTITY.AMOUNT in the schema. Data Field No (33) Minimum quantity No. Field Identifier Description 33 Minimum quantity The minimum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 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 (“.”). All quantities are unsigned values. This field is mandatory for “Call for orders” procedure. The maximum quantity the transferee/transferor would be willing to acquire/sell. This attribute may be used only in the case of a secondary market transaction. This field corresponds to the field MINIMUMBID_QUANTITY.AMOUNT in the schema. Data Field No (34) Price paid to TSO (Underlying Price) No. Field Identifier Description 34 Price paid to TSO (underlying price) Only applicable when there is an assignment expressed in the currency per measure unit which must be kWh/h. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field indicates the price paid to the TSO. This field is mandatory if the secondary market procedure (field 29) is CFO, FCFS or OTC. This field corresponds to the field UNDERLYINGTSO_PRICE.AMOUNT in the schema. Data Field No (35) Price the transferee pays to the transferor No. Field Identifier Description 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. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field is mandatory for secondary market transactions. This field corresponds to the field TRANSFER_PRICE.AMOUNT in the schema. Data Field No (36) Transferor identification No. Field Identifier Description 36 Transferor identification The market participant giving up the capacity. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC party code. Alphanumeric The maximum length of a transferor market participant’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. 10X1001A1001A450 This field is mandatory only in the case of secondary market reporting. The Edigas implementation guide only caters for EIC codes, it does not allow any other identification codes. This field corresponds to the field TRANSFEROR_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema. Data Field No (37) Transferee identification No. Field Identifier Description 37 Transferee identification The market participant receiving the capacity. Description of Accepted Values Type Length Examples The codification scheme used for the coded identification is indicated by the coding scheme attribute and shall indicate the code “305” for an EIC party code. Alphanumeric The maximum length of a transferee market participant’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters. 10X1001A1001A450 This field is mandatory only in case of secondary market reporting. This field corresponds to the field TRANSFEREE_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema. Last update: 09/05/2016
TRUM – Section 7.6 Data fields applicable only for orders placed at auctions for primary allocations This section includes the following fields: 38. Bid ID 39. Auction round number 40. Bid price 41. Bid quantity Data Field No (38) Bid ID No. Field Identifier Description 38 Bid ID Numerical identifier of the bid as assigned by the reporting entity. Description of Accepted Values Type Length Examples The format and length of the identifier depends on the reporting entity. Alphanumeric Maximum 35 8552448 This field is mandatory. If there is no auction sequence there is no bid. The bid identification should only be present if auction round number is present. This field corresponds to the IDENTIFICATION field in the schema. Data Field No (39) Auction round number No. Field Identifier Description 39 Auction round number An integer that increments every time an auction achieves no result and is re-run with different parameters starting at 1. To be left blank in case of auctions without binding rounds, e.g. day-ahead auctions. Description of Accepted Values Type Length Examples An integer value starting with 1. 1 2 3 … 999 Integer Maximum 3 1 This field identifies the specific order assigned by the System Operator for the capacity rights. In an ascending clock auction this is a sequential value starting from 1 that is assigned by the Auction Office. An integer is a number that is written without a fractional component (for example, 21, 4, and −2048 are integers; 9.75 and 5½ are not integers). In case of uniform price auctions (without biding rounds) the bidding round number should be 1. (e.g. day-ahead auction). This field is mandatory. This field corresponds to the SEQUENCE field in the schema. Data Field No (40) Bid price No. Field Identifier Description 40 Bid price The price bid for each unit of capacity excluding the reserve price. Expressed in the currency and measure unit. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 This field indicates the Price Step in case of an auction. This field is mandatory. This field corresponds to the field BID_PRICE.AMOUNT in the schema. Data Field No (41) Bid quantity No. Field Identifier Description 41 Bid quantity The quantity being bid for expressed in the measure unit. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. Numeric ISO 6093 17 1.8 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 (“.”).The number of decimal places identifying the fractional part of the quantity depends on local market rules. This field is mandatory. This field corresponds to the field BID_QUANTITY.AMOUNT in the schema. Last update: 09/05/2016
TRUM – Section 7.7 Examples of transaction reporting In order to facilitate transaction reporting and the understanding of how to populate the data fields in Table 4 of the Annex to the Implementing Acts, the Agency provides a number of examples of transaction reports. The examples can be found in ANNEX III of this document. It is worth noting that not all the data fields are mandatory for all transactions. The data fields are expected to be reported only when it is applicable according to this manual. The Agency has prepared an extensive list of trading scenarios to show what is expected and applicable to each scenario. However, the Agency is aware of the fact that, given the characteristics of some transactions, not all the possible trading scenarios have been covered in this manual. The Agency will continue to work with relevant stakeholders on the reporting of gas transportation contracts and will provide more detailed information on this topic in subsequent editions of the TRUM, including additional trading scenarios in Annex II. Last update: 09/05/2016
