TRUM – Section 6.3 Data fields related to No-Bid auction time series (for primary allocation) This section includes the following fields: 28. Identification 29. Auction identification 30. Classification category Data Field No (28) Identification No. Field Identifier Description 28 Identification The identification of a time series instance. Description of Accepted Values Type Length Examples Time series Unique Identification Alphanumeric Maximum 35 1432_275_66_43_1207 This field provides an identification that uniquely identified the no-bid auction time series. There may be several no-bid auction time series classes for a total allocation results document. Each time series identifies an auction where no market participant bids have been received. Data Field No (29) Auction identification No. Field Identifier Description 29 Auction identification The identification of the auction where no bids have been received. Description of Accepted Values Type Length Examples Identification of a no bid auction. Alphanumeric Maximum 35 1432_275_66_44_1805 This field provides an identification of the auction where no bids have been received. Data Field No (30) Classification category No. Field Identifier Description 30 Classification category (if applicable) The category of the product as defined by the market rules. Description of Accepted Values Type Length Examples Refer to ENTSO-E Core Component Code list document for valid codes. The following codes have been initially defined: A01: Base A02: Peak A03: Off-peak A04: Hourly Alphanumeric 3 A01 This field provides the classification category identifying the type of auction that is being held in respect to a given time period. This field is mandatory if applicable. Last update: 09/05/2016
TRUM – Section 6.4 Data fields related to secondary rights time series (for secondary rights) This section includes the following fields: 31. Time series identification 32. Business type 33. In area 34. Out area 35. Rights holder 36. Transferee party 37. Contract identification 38. Contract type 39. Previous contract identification 40. Measure unit quantity 41. Auction identification 42. Currency 43. Measure unit price 44. Curve type Data Field No (31) Time series identification No. Field Identifier Description 31 Time series identification The identification of the time series instance. This must be a unique number that is assigned by the sender for each time series in the document. Description of Accepted Values Type Length Examples Time series Unique Identification Alphanumeric Maximum 35 RS123446928 or 1432_137_42_40_559 This field provides a unique number that is assigned by the sender for each time series in the document. This field is mandatory. Data Field No (32) Business type No. Field Identifier Description 32 Business type Identifies the nature of the time series, e.g. capacity rights, capacity transfer notification, etc. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. A57 = Resale pricing Alphanumeric 3 A57 This field indicates the nature of the time series concerning the rights. This field is mandatory. Data Field No (33) In area No. Field Identifier Description 33 In area The area where the energy is to be delivered (EIC Y Code). Description of Accepted Values Type Length Examples EIC Alphanumeric The maximum length of this information is 16 characters 10Y0000123456789 This field identifies the area where the energy is going (10Y code of area where the energy is going). This field is mandatory. Data Field No (34) Out area No. Field Identifier Description 34 Out area The area where the energy is coming from (EIC Y Code). Description of Accepted Values Type Length Examples EIC Alphanumeric The maximum length of this information is 16 characters 10Y0000123456789 This field identifies the area where the energy is coming from (10Y code of area where the energy is coming from). This field is mandatory. Data Field No (35) Rights holder No. Field Identifier Description 35 Rights holder Identification of the market participant who is owner of or has the right to use, the transmission rights in question (EIC X Code). Description of Accepted Values Type Length Examples EIC Alphanumeric The maximum length of this information is 16 characters 10Y0000123456789 This field identifies the Rights Holder by a unique coded identification. Whenever rights are transferred, the Rights Holder is the transferor of the rights. This field is mandatory. Data Field No (36) Transferee party No. Field Identifier Description 36 Transferee party (if applicable) Identification of the market participant to whom the rights are being transferred or the interconnection trade responsible designated by the transferor (as designated in the rights holder attribute) to use the rights (EIC X Code). Description of Accepted Values Type Length Examples EIC Alphanumeric The maximum length of this information is 16 characters 10Y0000123456789 This field identifies the Transferee party by a unique coded identification. In certain cases the transferee party also acts as Interconnection Trade Responsible. This field is mandatory in case of transfers. Data Field No (37) Contract identification No. Field Identifier Description 37 Contract identification The contract identification of the time series instance. This must be the number that has been assigned by the transmission capacity allocator, e.g. the TSO or auction operator, or allocation platform. Description of Accepted Values Type Length Examples Capacity Agreement Identifications (CAI) Alphanumeric Maximum 35 3105105CY601 This field provides the number that has been assigned by the Transmission Capacity Allocator. This field provides identification that uniquely identifies the allocation. This field is mandatory. Data Field No (38) Contract type No. Field Identifier Description 38 Contract type The contract type defines the conditions under which the rights was allocated and handled, e.g. daily auction, weekly auction, monthly auction, yearly auction, etc. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for the valid list of codes. A01 = Daily A02 = Weekly A03 = Monthly A04 = Yearly Alphanumeric 3 A01 This field defines the conditions under which the rights were allocated and handled. The significance of this type is dependent on the in area and out area specific coded working methods. The Transmission Capacity Allocator responsible for the area in question auctions defines the contract type to be used, e.g.: daily auction, weekly auction, monthly auction, yearly auction, Long term contract, etc. This field is mandatory. Data Field No (39) Previous contract identification No. Field Identifier Description 39 Previous contract identification (if applicable) The identification of a previous contract used to identify the transfer rights. Description of Accepted Values Type Length Examples Capacity Agreement Identifications (CAI) Alphanumeric Maximum 35 3105105CY601 This information identifies the previous identification that was used to identify the rights. This is only applicable if there was a change in Contract Identification information. Data Field No (40) Measure unit quantity No. Field Identifier Description 40 Measure unit quantity The unit of measure that is applied to the quantities in which the time series is expressed. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. Alphanumeric Maximum 3 MWH This field indicates the unit if measurement used for the quantities expressed within the time series. This field is mandatory. Data Field No (41) Auction identification No. Field Identifier Description 41 Auction identification (if applicable) The identification linking the capacity rights to a set of specifications created by the transmission capacity allocator, e.g. TSO or auction operator, or allocation platform. Description of Accepted Values Type Length Examples Unique Identification that clearly identifies the auction to which the bid is addressed. Alphanumeric Maximum 35 AT-CH-M-BASE——-140801-01 This field provides a unique identification of the set of specifications that clearly defines the auction to which the capacity rights submitted by the Capacity Trader are to be re-auctioned. Data Field No (42) Currency No. Field Identifier Description 42 Currency (if applicable) The currency in which the monetary amount is expressed. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. String Maximum 3 ISO 4217 EUR This field indicates the currency used for the monetary amount expressed within the time series. This information is mandatory if available. Data Field No (43) Measure unit price No. Field Identifier Description 43 Measure unit price (if applicable) The unit of measure in which the price in the time series is expressed. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. Alphanumeric Maximum 3 MWh This field indicates the unit if measurement used for the price expressed within the time series (MW per unit, MWh per unit, etc.). This information is mandatory. Data Field No (44) Curve type No. Field Identifier Description 44 Curve type (if applicable) Describes the type of the curve that is being provided for the time series in question, e.g. variable sized block or fixed sized block or point. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. A01 – Sequential fixed size blocks A02 – Points A03 – Variable sized blocs A04 – Overlapping breakpoints A05 – Non-overlapping breakpoints Alphanumeric Maximum 3 A01 This field represents the coded identification of the curve that is described in the Period and Interval class. If the “Curve Type” element is omitted in the XML instance a default value of “sequential fixed sized blocks” shall be understood. Sequential fixed size blocks (A01) curve is made of successive Intervals of time (Blocks) of constant duration (size), where the size of Blocks is equal to the Resolution of the Period. The value of the Quantity remains constant within each block. This information is mandatory if available. Last update: 09/05/2016
TRUM – Section 6.5 Data fields related to period for primary allocation and secondary processes This section includes the following fields: 45. Time interval 46. Resolution Data Field No (45) Time interval No. Field Identifier Description 45 Time interval This information provides the date and time of the start and end of the reported period. Description of Accepted Values Type Length Examples ISO 8601 date format using UTC time format. Date and Time 41 2009-03-01T13:00:00Z/2010-05-11T15:30:00Z This field identifies the start and end date and time of the time interval of the period in question. The time of the start and end of the period is expressed in UTC. There may be several period classes for a time series. The overall time interval covered by the period shall be within the complete rights time interval. The number of periods within a time series as characterised by the resolution must completely cover the period’s time interval. If a time series is suppressed then the interval quantities are all zeroed out. This field is mandatory. Data Field No (46) Resolution No. Field Identifier Description 46 Resolution The resolution defining the number of periods that the time interval is divided (ISO 8601). Description of Accepted Values Type Length Examples The resolution is expressed in compliance with ISO 8601. For example PT15M expresses a 15 minute resolution. Date and Time PnYnMnDTnHnMnS PT15M This field identifies the number of periods that the time interval is divided. Where nY expresses a number of years, nM a number of months, nD a number of days. The letter “T” separates the date expression from the time expression and after it nH identifies a number of hours, nM a number of minutes and nS a number of seconds. This information defines the resolution of a single period. The time interval must contain a whole number of periods as expressed by the resolution. This field is mandatory. Last update: 09/05/2016
TRUM – Section 6.6 Data fields related to interval for primary and secondary allocation processes This section includes the following fields: 47. Position 48. Quantity 49. Price amount 50. Bid quantity 51. Bid price amount Data Field No (47) Position No. Field Identifier Description 47 Position The relative position of a period within an interval. Description of Accepted Values Type Length Examples The relative position must be expressed as a numeric integer value beginning with 1. All leading zeros must be suppressed. The maximum number of characters is 6. 1 2 3 … 999999 Integer Maximum 6 1 This information provides the relative position of a period within an interval. This field is mandatory if available. Data Field No (48) Quantity No. Field Identifier Description 48 Quantity The quantity that has been allocated in the primary auction. The quantity that has been assigned to the nomination party for secondary rights. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark included). The number of decimal places identifying the fractional part of the quantity depends on local market rules. Numeric Maximum 17 10.8 This information defines the quantity that has been assigned to the nomination party for the interval in question and that is expressed in the Measurement Unit. 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 non-signed values. Data Field No (49) Price amount No. Field Identifier Description 49 Price amount (if applicable) The price expressed for each unit of quantity allocated through the primary allocation. The price expressed for each unit of quantity resold or transferred on the secondary market if applicable. Description of Accepted Values Type Length Examples The maximum length of this information is 17 numeric characters (decimal mark and sign, if used included). Numeric ISO 6093 17 1.8 This field indicates the price expressed for each unit. The price indicated in a resale document equal to or above which the quantity may be sold. This information defines the price expressed in the unit of measurement of Price per unit of quantity in compliance with the pricing scheme based on local market rules. 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 if available. Data Field No (50) Bid quantity No. Field Identifier Description 50 Bid quantity (if applicable) The quantity that was in the original bid document. 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 This information defines the quantity that was requested for the interval in question and that is expressed in the Measurement Unit Quantity. 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 non-signed values. The number of decimal places identifying the fractional part of the quantity depends on local market rules. This field is mandatory if available. Data Field No (51) Bid price amount No. Field Identifier Description 51 Bid Price Amount (if applicable) The original price expressed in the original bid for each unit of quantity requested. 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 This information reproduces the price expressed in the unit of measurement of Price per unit of quantity requested in the original bid. 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 if available. Last update: 09/05/2016
TRUM – Section 6.7 Data fields related to reason for primary allocation and secondary processes This section includes the following fields: 52. Reason code 53. Reason text Data Field No (52) Reason code No. Field Identifier Description 52 Reason code (if applicable) A code providing the status of the allocation or the rights. Description of Accepted Values Type Length Examples Refer to ETSO Code list document for valid codes. A75: Rights status information A71: Linked bid rejected due to associated bid unsuccessful A72: Original bid divided to permit acceptance A73: Bid accepted A74: Auction Status Alphanumeric Maximum 3 A75 This field provides the reason code provides the status of the rights identified. As many reason elements as necessary may be used. This information is at the time series level to provide related explanatory information. This field is mandatory if available. Data Field No (53) Reason text No. Field Identifier Description 53 Reason text (if applicable) Textual explanation of the reason code. Description of Accepted Values Type Length Examples If the code does not provide all the information to clearly identify the justification of the allocation then the textual information may be provided. Alphanumeric Maximum 512 Used only if the reason code is insufficient to identify an error. This field is mandatory if available. Last update: 09/05/2016
TRUM – Section 6.8 Data fields related to Bid header document and bid document fields for organised market places (applicable for secondary trading) This section includes the following fields: 54. Subject party 55. Subject role 56. Divisible 57. Linked bids identification 58. Block bid Data Field No (54) Subject party No. Field Identifier Description 54 Subject party The market participant for whom the bid is being submitted (EIC Code). Description of Accepted Values Type Length Examples EIC Alphanumeric Maximum 16 10X1001A1001A450 This field identifies the party that is the Capacity Trader for whom the bids are being submitted. The codification scheme used for the coded identification is indicated by the coding scheme attribute. This field is mandatory. Data Field No (55) Subject role No. Field Identifier Description 55 Subject role The role of the subject party Description of Accepted Values Type Length Examples Refer to ETSO Code list document for the valid list of codes. A29 = Capacity Trader Alphanumeric Maximum 3 A29 This field identifies the Role of the Subject Party. In this current implementation of ECAN the role shall always be A29, Capacity Trader. This field is mandatory. Data Field No (56) Divisible No. Field Identifier Description 56 Divisible An indication whether or not each element of the bid may be partially accepted or not. Description of Accepted Values Type Length Examples A01 : “Yes” A02: “No” Alphanumeric Maximum 3 A01 This field indicates whether or not each element of the bid may be marginal. That is to say that the quantity allocated to each element of the bid may be anything between0 and the quantity asked. If it is not divisible the quantity may be only 0 or the quantity asked. This is only applicable for last assessed bid. In the case of capacity auctions if the ATC limit is reached divisible means that it may be reduced to the ATC limit and partly accepted. This field is mandatory if available. Data Field No (57) Linked bids identification No. Field Identifier Description 57 Linked bids identification (if applicable) Unique identification associated with all linked bids. Description of Accepted Values Type Length Examples Unique linked bid identification. Alphanumeric Maximum 35 This field identifies a set of bids that are linked together signifying that they are either all accepted or are all rejected. This identification is defined by the bidder and must be unique for a given auction. The linked bid identification is only provided if a bid is associated with the current bid. Both bids must be cross linked to be valid. This field is mandatory if available. Data Field No (58) Block bid No. Field Identifier Description 58 Block bid An indication that the values in the period constitute a block bid and that they cannot be changed. Description of Accepted Values Type Length Examples A01 : “Yes” A02: “No” Alphanumeric Maximum 3 A01 This field indicates that all the time intervals in the time series are to be considered as a whole and that they cannot be subdivided. The default value for this attribute is A02 = No. This field is mandatory if available. Last update: 09/05/2016
TRUM – Section 6.9 Examples of transaction reporting In order to facilitate transaction reporting and the understanding of how to populate the data fields in Table 3 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 electricity transportation contracts and will provide more detailed information on this topic in subsequent updates of the TRUM, including additional trading scenarios in Annex II. Last update: 09/05/2016
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
