GasTerra OA 2018-2019 Final Clean - the ICE Agreement [contractLegalName] Definitions GasTerra OA...

Operating Agreement

[contractLegalName]

Preamble

Operating Agreement under the

[contractLegalName] between

[buyerLegalName]

and

[ENTITY]

Version [docVersion] Status: [docStatus]

© [docReleaseDate]

Operating Agreement

[contractLegalName]

Preamble

Preamble

This Operating Agreement is made [oADayOfWeek], [oADateMMMDDYYYY] in two originals between:

[ENTITY] hereinafter also referred to as “the Storage Services Provider” on the one part and

[buyerLegalName] hereinafter also referred to as “the Customer” on the other part.

Whereas the Parties on [contractDateMMMDDYYYY] entered into an agreement [con-tractLegalName], as amended from time to time (“hereinafter called the “SSA”), and

whereas the Parties hereby wish to further detail their operational procedure pursu-ant to article [articleOperationalProcedure] in the SSA.

Now therefore, it is hereby agreed as follows:

Operating Agreement

[contractLegalName]

Table of contents

Table of contents

1 Outline 1

1.1 General ............................................................................ 1

1.2 Purpose ............................................................................ 1

1.3 This document ................................................................... 1

2 Definitions 2

2.1 General definitions ............................................................. 2

2.2 Information exchange related definitions .............................. 4

2.3 Document definitions ......................................................... 6

3 General provisions 7

4 Dispatching procedure 9

4.1 Provisions ......................................................................... 9

4.2 Ordering ......................................................................... 10

4.2.1 Daily Ordering ............................................................ 10

4.2.2 Revised Availability ...................................................... 11

4.2.3 Revised Request ......................................................... 11

4.2.4 Revised Request Response ........................................... 12

4.3 Nomination at the system operator(s) ................................ 13

5 Trading procedure 14

5.1 Provisions ....................................................................... 14

5.2 Trading facility trades ....................................................... 14

5.2.1 Daily Ordering and Closing ........................................... 14

5.2.2 Revised Trade Confirmation .......................................... 15

6 Documents 16

6.1 Storage Availability Notice (SAN) ....................................... 16

6.2 Storage Request Notice (SRN) ........................................... 17

6.3 Storage Request Response Notice (SRRN) ........................... 18

6.4 Trades Confirmation Notice (TCN) ...................................... 20

6.5 Acknowledgment Notice .................................................... 21

6.6 Rejection Notice .............................................................. 21

7 Signatures 23

8 Appendix A – Operational Term Sheet 1

Operating Agreement

[contractLegalName]

Outline

GasTerra OA 2018-2019 Final Clean.docx page 1

1 Outline

1.1 General

1.1 Between [ENTITY] (Storage Services Provider) and [buyerLegalName] (Customer) a SSA exists under which the Storage Services Provider will provide Storage Services to the Customer.

Between [ENTITY] (Trading Facility Provider) and [buyerLegalName] (Trading Facility User) a Membership Agreement may exist under which the Trading Facility Provider will provide to the Trading Facility User access to the secondary market for Storage Services organised and governed by the Trading Facility Provider.

In order to operate the SSA, information between the Customer and the Storage Services Provider and between the Trading Facility Provider and Trading Facility User has to be exchanged.

Information may be exchanged using appropriate means of communication as set out in the Operational Term Sheet.

This Operating Agreement is entered into pursuant to 14.1 in the SSA.

1.2 Purpose

1.2 In this Operating Agreement under the SSA the following procedures are specified:

• Dispatching procedure.

• Trading procedure.

1.3 This document

1.3 Definitions of names and acronyms used in this Operating Agreement are described in chapter 2.

The general provisions are stated in chapter 3.

In chapter 4, the dispatching procedure is specified.

In chapter 5, the trading procedure is specified.

In chapter 6, the documents used in the procedures described in this Operating Agreement are specified.

In chapter 7, this Operating Agreement is signed.

In appendix A; the Operational Term Sheet (OTS), addresses, phone- and fax-numbers of the Parties’ operational units, contractual quantities and qualities, dead-lines, lead times, identifications and other data to be used for the procedures de-scribed in this Operating Agreement are specified.

Operating Agreement

[contractLegalName]

Definitions


2 Definitions

All definitions set forth in the SSA will apply for this Operating Agreement except otherwise indicated by the context in which they are used or otherwise defined in this Operating Agreement. In this Operating Agreement the terms listed below shall have the following meaning and include the plural as well as the singular:

2.1 General definitions

2.1 Business Day shall refer to a “werkdag” and means a day, not Saturday or Sunday, which is neither an official holiday as meant in Article 3, first paragraph, of the Dutch Act “Algemene Termijnenwet”, nor a day equal to an official holiday by virtue of the second or third subsection of the above mentioned Act.

2.2 Customer

shall mean the company entered into the SSA taking off Storage Services pro-vided by the Storage Services Provider.

2.3 Contractual Unit shall mean the energy classifying unit kWh in which the SSA is operated.

2.4 Curtailment

shall mean a temporary reduction or total breakdown of the service of the con-cerning system operator due to shortage of supply, shortage of capacity, inter-ruption of the service or mismatches in the nomination process.

2.5 Day (gas day)

shall mean a period beginning at 06:00 hours LET on any calendar day and ending at 06:00 hours LET on the following calendar day, taking into account the application of daylight savings time as agreed upon under the SSA. The reference date of any day is the date of the calendar day on which the day be-gins. Daily shall be construed accordingly. Day shall mean the day under reference.

2.6 Delivery Point

shall mean the virtual location in the GTS transmission network called “TTF” or “Title Transfer Facility” where the Storage Services Provider will provide Stor-age Services to the Customer and that will serve as an entry and exit point at which Parties can transfer gas.

2.7 Dispatching procedure

shall mean the procedure described in chapter 4 of this Operating Agreement.

2.8 Downstream shipper

shall mean a company receiving gas at a Point on behalf of a Party. For each Point, if predefined, the downstream shipper(s) are specified in the OTS at [4A.6.2].

2.9 Gas

refers to matter that at a temperature of 15 ˚C and at a pressure of 1.01325 bar is in a gaseous state and mainly consists of methane or other matter that due to its properties is equivalent to methane.

Operating Agreement

[contractLegalName]

Definitions


2.10 Gas Market Instrument Specifications

refers to a document provided by the Trading Facility Provider specifying the tradable Storage Services related instruments and informing about the process of trading such instruments.

2.11 Gasunie Transport Services B.V. or GTS shall mean the transmission system operator having its statutory seat in and officiating in Groningen, the Netherlands, offering gas transmission services in the Netherlands.

2.12 Hour

shall mean a period of 3600 consecutive seconds. Hourly shall be construed accordingly.

2.13 Injection (to inject) shall mean the delivery of Gas by Customer to Storage Services Provider at the Delivery Point and the transfer of that Gas from Customer portfolio at GTS to Storage Services Provider portfolio at GTS.

2.14 Membership Agreement

shall mean the duly executed agreement between Trading Facility Provider and the Trading Facility User pursuant to which they accept and are bound by the gas market rules of Trading Facility Provider as may be amended, supplement-ed or replaced from time to time.

2.15 Month

shall mean a period of time beginning each first day of a month at 06:00 hours LET and ending at 06:00 hours LET on the first day of the following month tak-ing into account the application of daylight savings time as agreed upon under the SSA. Monthly shall be construed accordingly.

2.16 Operating Agreement

shall mean this Operating Agreement including Appendix A.

2.17 OTS

shall mean the Operational Term Sheet as attached as Appendix A to this Op-erating Agreement.

2.18 Party

shall mean either the Storage Services Provider or the Customer.

2.19 Parties

shall mean both the Storage Services Provider and the Customer.

2.20 Point

shall mean a virtual or physical point where the Storage Services Provider will provide Storage Services to the Customer as defined under the SSA and speci-fied and described in the OTS at [4A.1].

2.21 Storage Services Provider

shall mean the company entered into the SSA providing Storage Services to the Customer.

2.22 Store

shall mean the Gas-in-Storage account as kept by the Storage Services Provid-er for the Customer under the SSA.

2.23 Shipper

shall mean a Downstream Shipper and/or an Upstream Shipper.

Operating Agreement

[contractLegalName]

Definitions


2.24 Shipper code

shall mean a code that identifies a Shipper in a unique way at the concerning system operator(s). The code has to be known to both Parties and to the sys-tem operator(s) at the concerning Point(s).

2.25 Shipper Pair

shall mean one Downstream Shipper and one Upstream Shipper at a Point.

2.26 Summer time period shall mean the period as defined by Directive 2000/84/EC of the European Par-liament and of the Council of January 19th 2001 on summer-time arrangements and as amended by the European Parliament or the Council from time to time.

2.27 Trading Facility shall mean the facility made available by the Trading Facility Provider to be used by the Trading Facility Users in order to trade tradable elements as de-fined in the SSA in C.1 under the conditions stated in the SSA in Appendix C.

2.28 Trading Facility Provider

shall mean the company ICE Endex Markets B.V. organising the trading on the secondary market of Storage Services.

2.29 Trading Facility User

shall mean a Customer having signed a Membership Agreement as stipulated by the Trading Facility Provider concerning the trading on the secondary market of Storage Services.

2.30 Trading Procedure

Shall mean the procedure described in chapter 5 of this Operating Agreement.

2.31 Upstream shipper

shall mean a company delivering gas at a Point on behalf of a Party. For each Point, if predefined, the upstream shipper(s) are specified in the OTS at [4A.5.2].

2.32 UTC

shall mean the solar time at the prime meridian (0º longitude).

2.33 Week

shall mean a period of time beginning each Monday at 06:00 hours LET and ending at 06:00 hours LET on the following Monday taking into account the ap-plication of daylight savings time as agreed upon under the SSA. Weekly shall be construed accordingly.

2.34 Withdrawal (to withdraw) shall mean the delivery of Gas by Storage Services Provider to Customer at the Delivery Point and the transfer of that Gas from Storage Services Provider port-folio at GTS to Customer portfolio at GTS.

2.2 Information exchange related definitions

2.35 Maximum Available Injection Capacity

shall mean the maximum quantity of Gas the Customer is able to inject into the Store under the SSA and is expressed in kWh.

Operating Agreement

[contractLegalName]

Definitions


2.36 Maximum Available Withdrawal Capacity

shall mean the maximum quantity of Gas the Customer is able to withdraw from the Store under the SSA and is expressed in kWh.

2.37 Maximum Injection Rate

shall mean the maximum flow rate at which the Customer is able to inject Gas into the Store and is expressed in kWh per Hour.

2.38 Maximum Withdrawal Rate

shall mean the maximum flow rate at which the Customer is able to withdraw Gas from the Store and is expressed in kWh per Hour.

2.39 Requested Firm Injection Quantity

shall mean the firm quantity of Gas the Customer requests to inject into the Store under the SSA in line with his contractual rights and obligations and is expressed per SSA in kWh per Day.

2.40 Requested Firm Withdrawal Quantity

shall mean the firm quantity of Gas the Customer requests to withdraw from the Store under the SSA in line with his contractual rights and obligations and is expressed per SSA in kWh per Day.

2.41 Requested Conditional Injection Quantity

shall mean the conditional quantity of Gas the Customer requests to inject ad-ditionally into the Store under the SSA in line with his contractual rights and obligations and is expressed per SSA in kWh per Day.

2.42 Requested Conditional Withdrawal Quantity

shall mean the conditional quantity of Gas the Customer requests to withdraw additionally from the Store under the SSA in line with his contractual rights and obligations and is expressed per SSA in kWh per Day.

2.43 Resultant Firm Injection Quantity

shall mean the firm quantity of Gas the Customer requests to inject or will re-ceive injected into the Store considering any change resulting from a lower maximum injection availability and is expressed in kWh per Hour.

2.44 Resultant Firm Withdrawal Quantity

shall mean the firm quantity of Gas the Customer requests to withdrawn or will receive withdrawn from the Store considering any change resulting from a low-er maximum withdrawal availability and is expressed in kWh per Hour.

2.45 Resultant Conditional Injection Quantity

shall mean the conditional quantity of Gas the Customer requests to inject ad-ditionally or will receive injected additionally into the Store and is expressed in kWh per Hour.

2.46 Resultant Conditional Withdrawal Quantity

shall mean the conditional quantity of Gas the Customer requests to withdrawn additionally or will receive withdrawn additionally from the Store and is ex-pressed in kWh per Hour.

Operating Agreement

[contractLegalName]

Definitions


2.3 Document definitions

2.47 Storage Availability Notice (SAN)

shall have the meaning as described in 6.1.

2.48 Storage Request Notice (SRN)


2.49 Storage Request Response Notice (SRRN)


2.50 Trades Confirmation Notice (TCN)


2.51 Acknowledgment Notice (ACK)


2.52 Rejection Notice (REJ)


Operating Agreement

[contractLegalName]

General provisions


3 General provisions

3.1 This Operating Agreement shall not affect nor alter any of the rights and obligations of the Parties under the SSA. In case of conflict between the provisions of this Oper-ating Agreement and the SSA, the SSA shall prevail.

3.2 This Operating Agreement shall become effective upon signature and remain in force until the SSA is terminated or until a newer version of this Operating Agreement be-comes effective.

3.3 If any Party requests so, the Parties shall meet to evaluate in good faith the need of amending this Operating Agreement. Any modification of and/or addition to this Op-erating Agreement agreed upon shall be made in writing and the consent to it shall not be unreasonably withheld.

3.4 When not using electronic data interchange, any reference to time shall be in: UTC minus one (1) hour in Winter time periods, UTC minus two (2) hours in Summer time periods. When using electronic data interchange, any reference to time shall be in UTC.

3.5 Switching from winter to summer time will cause a Day having only 23 hours. Switching from summer to winter time will cause a Day having 25 hours. All other Days will have 24 hours.

3.6 The articles of the SSA concerning applicable law, amendments, confidential information, assignment, ineffective provisions, default and non-waiver, force majeur and arbitration shall apply for the purpose of this Operating Agreement, mutatis mu-tandis.

3.7 Any standardized information provided for herein shall be deemed to have been given properly if delivered in due time by the communication means as defined in the OTS.

3.8 All information exchange shall be in the English language.

3.9 In case a received document cannot be processed or has to be rejected, the receiving Party shall inform the other Party by issuing a Rejection Notice.

3.10 If a document has been received and can be processed, the receiving Party shall inform the other Party by issuing an Acknowledgment Notice.

3.11 The Parties will make reasonable endeavours to follow the relevant common business practices as issued by the European Association for the Streamlining of Energy Ex-change – gas (EASEE-gas), as such procedures may at any time and from time to time be in force. The implementation of relevant common business practices will be

Operating Agreement

[contractLegalName]

General provisions


agreed by both Parties and will depend on both Parties' ability to comply with the relevant common business practices.

Operating Agreement

[contractLegalName]

Dispatching procedure


4 Dispatching procedure

4.0 This Dispatching Procedure provides for the exchange of information which is required in order to make available, offtake and confirm the Storage Services in ac-cordance with the Parties’ rights and obligations as described in the SSA.

4.1 Provisions

4.1.1 For the efficient implementation of the SSA, the Parties shall cooperate in their dispatching operations.

4.1.2 The Customer shall request Storage Services in accordance with this Operating Agreement and the SSA and shall, to the extent made available, take what is re-quested. The Storage Services Provider shall cause Storage Services to be made available and delivered as requested by the Customer in accordance with this Oper-ating Agreement and the SSA.

4.1.3 The Parties agree that any notifications under the Parties’ agreements that concern the delivery and/or offtake of the relevant quantities hereunder, shall be consistent with the information resulting from this Dispatching Procedure.

4.1.4 The Parties shall inform each other about their respective dispatching representa-tives, if any, in due time.

4.1.5 The Parties shall seek close cooperation in the dispatching operations in order to optimize availability and reliability of the deliveries and offtakes under the SSA.

4.1.6 If in emergency situations one of the Parties or both Parties have to revise notified quantities, the Party or Parties in question shall as soon as possible notify the other Party by phone and issue the revised document.

4.1.7 If not agreed otherwise, any quantity notified under the procedures herein has to be communicated in the contractual unit, kWh.

4.1.8 If not notified otherwise or if agreed so under the SSA, Daily flow rates will be made available with even Hourly flow rates throughout the Day(s).

4.1.9 If a Curtailment situation at a Point is affecting the deliveries and/or offtakes under the SSA at this Point and this situation will appear after the agreed lead time before change at this Point, information will be exchanged in order to make available, deliv-er and offtake the changed quantities at this Point. In case this situation will appear within the agreed lead time, for the agreed lead time the nominated quantities will remain as notified and the allocation by the con-cerned system operator(s) will determine the deliveries and/or offtakes under the SSA for that period and Point and for the remaining time of the Curtailment situation information will be exchanged in order to make available, deliver and offtake the changed quantities at this Point.

Operating Agreement

[contractLegalName]



4.1.10 Both Parties shall verify the notified quantities against the contractual boundaries agreed upon and applicable for the concerning period and shall inform other Party in case of differences. Both Parties shall be responsible for the verification of the confirmations received from the concerning system operator(s) against the nominations and shall inform the other Party in case of differences.

4.2 Ordering

4.2 The Storage Services Provider informs the Customer about the availability of Storage Services under the SSA. The Customer answers with a request informing the Storage Services Provider about the firm and conditional quantity the Customer intends to offtake under the SSA. The Storage Services Provider thereupon confirms the re-quested quantity and the assigned conditional quantity. The quantities exchanged in the ordering process shall be used to nominate the transportation at the concerning system operator(s).

Information exchanged in an ordering process is binding.

4.2.1 Daily Ordering

4.2.1 Periodically a conversation concerning the usage of the SSA for the next period between the Storage Services Provider and the Customer takes place.

Storage Services Provider

Customer

| Storage Availability Notice |

| |

| Storage Request Notice |

| |

| Storage Request Response Notice |

| |

If specified so in the OTS at [7A.2.1] with a periodicity as specified in the OTS at [7A.1.2], the Storage Services Provider shall issue a Storage Availability Notice be-fore the deadline as specified in the OTS at [7A.2.3]. The Storage Availability Notice shall contain the availability for the next period, the period being as specified in the OTS at [7A.1.4].

If specified so in the OTS at [7A.4.1] with a periodicity as specified in the OTS at [7A.1.2], the Customer shall issue a Storage Request Notice before the deadline as specified in the OTS at [7A.4.3]. The Storage Request Notice shall contain the re-quested firm and, if applicable, conditional offtake for the next period, the period be-ing as specified in the OTS at [7A.1.4].

If the Storage Request Notice contains a valid request and if specified so in the OTS at [7A.5.1], the Storage Services Provider shall confirm the request by issuing a Storage Request Response Notice before the deadline as specified in the OTS at

Operating Agreement

[contractLegalName]



[7A.5.3]. The Storage Request Response Notice shall contain the confirmed request-ed firm and, if applicable, conditional offtake for the next period, the period being as specified in the OTS at [7A.1.4].

4.2.2 Revised Availability

4.2.2 The Storage Services Provider may have to revise the availability. In the OTS at [7B.1.5], [7B.1.6] and [7B.1.7] is specified if and the conditions under which Storage Services Provider may revise the availability.


Customer

| Storage Availability Notice |

| |


| |


| |

The Storage Services Provider shall revise the availability by issuing a revised Stor-age Availability Notice. The Storage Services Provider has to consider the agreed lead time as specified in the OTS at [7B.2.3] before any revision may become effec-tive and the Storage Availability Notice has to be sent by the Storage Services Pro-vider and received by the Customer prior to this lead time. The Storage Availability Notice shall contain the availability for the period containing the revision, the period being as specified in the OTS at [7B.1.4].

If the quantities as requested in the most actual Storage Request Notice not comply with the revised availability, the Customer thereupon shall revise its request and is-sue a revised Storage Request Notice. The Customer has to consider the agreed lead time as specified in the OTS at [7B.4.3] before any revision may become effective and the Storage Request Notice has to be sent by the Customer and received by the Storage Services Provider prior to this lead time. The Storage Request Notice shall contain the requested firm and, if applicable, conditional offtake for the period con-taining the revision, the period being as specified in the OTS at [7B.1.4].

If the Storage Request Notice contains a valid request, the Storage Services Provider will confirm the request by issuing a revised Storage Request Response Notice. The Storage Services Provider has to consider the agreed lead time as specified in the OTS at [7B.5.3] before any revision may become effective and the Storage Request Response Notice has to be sent by the Storage Services Provider and received by the Customer prior to this lead time. The Storage Request Response Notice shall contain the confirmed requested firm and, if applicable, conditional offtake for the next peri-od, the period being as specified in the OTS at [7B.1.4].

4.2.3 Revised Request

4.2.3 The Customer may have to revise the request. In the OTS at [7D.1.5], [7D.1.6] and [7D.1.7] is specified if and the conditions under which Customer may revise the re-quested quantities and/or Shipper(s).

Operating Agreement

[contractLegalName]




Customer


| |


| |

The Customer shall revise requested quantities and/or Shipper(s) by issuing a re-vised Storage Request Notice. The Customer has to consider the agreed lead time as specified in the OTS at [7D.4.3] before any revision may become effective and the Storage Request Notice has to be sent by the Customer and received by the Storage Services Provider prior to this lead time. The Storage Request Notice shall contain the requested firm and, if applicable, conditional offtake for the period containing the revision, the period being as specified in the OTS at [7D.1.4].

If the Storage Request Notice contains a valid request, the Storage Services Provider will confirm the request by issuing a revised Storage Request Response Notice. The Storage Services Provider has to consider the agreed lead time as specified in the OTS at [7D.5.3] before any revision may become effective and the Storage Request Response Notice has to be sent by the Storage Services Provider and received by the Customer prior to this lead time. The Storage Request Response Notice shall contain the confirmed requested firm and, if applicable, conditional offtake for the next peri-od, the period being as specified in the OTS at [7D.1.4].

4.2.4 Revised Request Response

4.2.4 The Storage Services Provider may have to revise the request response, changing the partitioning of the quantities over one or more Shipper Pair(s) or revising the as-signed conditional quantities. In the OTS at [7E.1.5], [7E.1.6] and [7E.1.7] is speci-fied if and the conditions under which Storage Services Provider may revise the re-quest response.


Customer


| |

The Storage Services Provider shall revise the request response by issuing a revised Storage Request Response Notice. The Storage Services Provider has to consider the agreed lead time as specified in the OTS at [7E.5.3] before any revision may become effective and the Storage Request Response Notice has to be sent by the Storage Services Provider and received by the Customer prior to this lead time. The Storage Request Response Notice shall contain the confirmed requested firm and, if applica-ble, conditional offtake for the next period, the period being as specified in the OTS at [7E.1.4].

Operating Agreement

[contractLegalName]



4.3 Nomination at the system operator(s)

4.3.1 The Storage Services Provider and the Customer shall instruct their respective Shipper(s) to use the confirmed firm and, if applicable, conditional quantities in the Storage Request Response Notice to nominate the transportation of the Storage Ser-vices at the concerning system operator(s). Transportation nominations for revised quantities and/or revised shipping information shall be issued as soon as possible. Both Parties assure that all necessary nominations towards the concerning system operator(s) are carried out in order to ensure a correct matching by the concerning system operator(s).

4.3.2 In case the information concerning this SSA in the transportation nomination(s) sent to the concerning system operator(s) by the Shipper(s) the Storage Services Provid-er uses for a Day differs from the information concerning this SSA in the transporta-tion nomination(s) sent to the concerning system operator(s) by Shipper(s) the Cus-tomer uses for the same Day, the information in the transportation nomination(s) sent by the Shipper(s) the Storage Services Provider uses prevail (single sided nomi-nations).

Operating Agreement

[contractLegalName]

Trading procedure


5 Trading procedure

5.0 This Trading Procedure provides for the exchange of information that is required in order to inform the Trading Facility User about the accepted and rejected trades per-formed by the Trading Facility User on the Trading Facility.

5.1 Provisions

5.1.1 For the efficient implementation of the SSA, the Trading Facility User, the Trading Facility Provider and the Storage Services Provider shall cooperate in their trading operations.

5.1.2 The Trading Facility User shall trade Storage Services in accordance with this Operating Agreement and the SSA.

5.2 Trading facility trades

5.2 The Trading Facility User uses the Trading Facility to enter orders for secondary trading of Storage Services. The Trading Facility Provider informs the Storage Ser-vices Provider and the Trading Facility User about the executed trades. The Storage Services Provider thereupon validates and administers the executed trades. The Storage Services Provider informs the Trading Facility User about approval and rejec-tion of executed trades.

Information exchanged in a trading process is binding.

5.2.1 Daily Ordering and Closing

5.2.1 Every Business Day during the trading window defined in the Gas Storage Market Instrument Specifications, the Trading Facility User may place trading orders on the Trading Facility. Trades concerning Gas Day D have to be traded on day D-2 in case D-2 is a Business Day or in case D-2 is not a Business Day, the first Business Day prior to D-2.

The Trading Facility matches trading orders, executes the trades and informs the Trading Facility User about executed trades. As the Trading Facility does not have information about the Store of the concerning SSA, the Trading Facility cannot vali-date the correctness of the executed trades.

After closure of the trading window, Trading Facility Provider informs the Storage Services Provider about the executed trades during such trading window. The Stor-age Services Provider thereupon validates the notified executed trades and informs the Trading Facility User about the approval and rejection of the single executed trades by sending a Trades Confirmation Notice to the Trading Facility User before the deadline as specified in the OTS at [8A.2.3].

Operating Agreement

[contractLegalName]

Trading procedure


Trading Facility Provider

Trading

Facility Us-er


| Trade Order | |

| | |

| Trade Execution | |

| Notification | |

| Trade Execution | |

| Notification | |

| | Trades Confirmation |

| | Notice |

5.2.2 Revised Trade Confirmation

5.2.2 The Storage Services Provider might have to revise the Trades Confirmation Notice, revising the results of the validations performed. The Storage Services Provider in-forms the Trading Facility User about the revised approval and rejection of the single executed trades by sending a revised Trades Confirmation Notice to the Trading Fa-cility User as soon as reasonably possible but ultimately before the start of the next Day.

Operating Agreement

[contractLegalName]

Documents


6 Documents

6.1 Storage Availability Notice (SAN)

General purpose

6.1.1 The Storage Availability Notice shall be issued by the Storage Services Provider to inform the Customer about the availability of the Storage Services under the SSA. The Storage Availability Notice is also issued by the Storage Services Provider to in-form the Customer about any revision thereof.

Content of the document

6.1.2 For the relevant period as specified in the OTS at [7A.1.4] and [7B.1.4], the Storage Availability Notice shall contain:

• Maximum Available Injection Capacity.

• Maximum Available Withdrawal Capacity.

If these quantities are not available for each Hour of the relevant period, these quan-tities shall be specified for each Hour of the relevant period.

If for the relevant period maximum flow rates apply the Storage Availability Notice shall also contain:

• Maximum Injection Rate.

• Maximum Withdrawal Rate.

If these rates are not available for each Hour of the relevant period, these rates shall be specified for each Hour of the relevant period.

Notification procedure

6.1.3 The initial Storage Availability Notice shall be issued by the Storage Services Provider before the deadline as specified in the OTS at [7A.2.3].

A Storage Availability Notice revising a previous Storage Availability Notice shall be issued by the Storage Services Provider considering the agreed lead time as specified in the OTS at [7B.2.3] before any revision may become effective and the Storage Availability Notice has to be sent by the Storage Services Provider and received by the Customer prior to this lead time.

If a revised Storage Availability Notice affects the last Storage Request Notice con-cerning the same period, the Customer shall respond by issuing a revised Storage Request Notice.

If for the SSA for the relevant period a Storage Availability Notice is issued, such Storage Availability Notice shall replace any previous Storage Availability Notice for the SSA for the relevant period.

Fallback procedure

Operating Agreement

[contractLegalName]

Documents


6.1.4 If the Customer does not receive an agreed periodic Storage Availability Notice the Customer will instantaneously issue a wake up call. If, after the call, a Storage Avail-ability Notice is still not received, the quantities as agreed upon in the SSA and specified in the OTS at [3.3.4.4] and [3.3.5.4] for such situations will apply. The maximum available quantities shall be deemed to have been notified to be for each Hour of the concerning period the maximum quantities as defined in the OTS at [4A.3.4.3] and [4A.3.5.3] and shall be available in a steady flow.

6.2 Storage Request Notice (SRN)

General purpose

6.2.1 The Storage Request Notice shall be issued by the Customer to inform the Storage Services Provider about the requested firm, and if applicable, conditional quantity of Storage Services which Customer intends to offtake under the SSA for the concern-ing period, the Shipper Code(s) which Customer intends to use and the correspond-ing flow rates. The Storage Request Notice will also be issued to inform about any revision thereof.


6.2.2 For the relevant period as specified in the OTS at [7A.1.4], [7B.1.4] and [7D.1.4], the Storage Request Notice shall contain:

• Requested Firm Injection Quantity.

• Requested Firm Withdrawal Quantity.

For the relevant period, if conditional quantities are requested, the Storage Request Notice shall contain:

• Requested Conditional Injection Quantity.

• Requested Conditional Withdrawal Quantity.

For each of the concerning Shippers the Customer intends to use, the Storage Re-quest Notice shall contain:

• Resultant Firm Injection Quantity. Each Resultant Firm Injection Quantity shall refer to a specific Upstream Shipper Customer intends to use.

• Resultant Firm Withdrawal Quantity Each Resultant Firm Withdrawal Quantity shall refer to a specific Downstream Shipper Customer intends to use.

If conditional quantities are requested, for each of the concerning Shippers the Cus-tomer intends to use, the Storage Request Notice shall contain:

• Resultant Conditional Injection Quantity. Each Resultant Conditional Injection Quantity shall refer to a specific Upstream Shipper Customer intends to use.

• Resultant Conditional Withdrawal Quantity Each Resultant Conditional With-drawal Quantity shall refer to a specific Downstream Shipper Customer in-tends to use.

If quantities are not requested in a steady hourly rate over the relevant period, these quantities shall be specified in an hourly rate for each Hour of the relevant period.

Operating Agreement

[contractLegalName]

Documents



6.2.3 The initial Storage Request Notice shall be issued by the Customer before the deadline as specified in the OTS at [7A.4.3].

A Storage Request Notice revising a previous request shall be issued by the Custom-er considering the agreed lead time as specified in the OTS at [7B.4.3] before any revision may become effective and the Storage Request Notice has to be sent by the Customer and received by the Storage Services Provider prior to this lead time.

If the Storage Services Provider receives a Storage Request Notice, the Storage Ser-vices Provider shall respond by issuing a Storage Request Response Notice.

If for the SSA for the relevant period a Storage Request Notice is issued, such Stor-age Request Notice shall replace any previous Storage Request Notice for the SSA for the relevant period.

Fallback procedure

6.2.4 If Storage Services Provider does not receive an agreed periodic Storage Request Notice or if Storage Services Provider does not receive a Storage Request Notice af-ter Storage Services Provider issued a revised Storage Availability Notice, the Stor-age Services Provider will issue a wake up call. If, after the call, a Storage Request Notice is still not received, the requested quantities shall be deemed to have been requested to be for each Hour the injection and or withdrawal as requested in the last validated and approved received Storage Request Notice containing requested quantities for the concerning period. If no such Storage Request Notice is available to the Storage Services Provider the requested quantities shall be deemed to be zero for each Hour.

6.3 Storage Request Response Notice (SRRN)

General purpose

6.3.1 The Storage Request Response Notice shall be issued by the Storage Services Provider to confirm the firm quantities as requested by the Customer for the relevant period in the Storage Request Notice issued by the Customer and to notify and con-firm the quantities assigned based upon the conditional quantities as requested by the Customer for the relevant period in the Storage Request Notice issued by the Customer and will notify the Shipper Pair(s) involved in the delivery and/or offtake of Gas and will be issued to inform about any revision thereof.


6.3.2 For the relevant period, for each involved Shipper Pair, the Storage Request Response Notice shall contain:

• Resultant Firm Injection Quantity. Each Resultant Firm Injection Quantity shall refer to a specific Upstream Shipper Customer intends to use and a spe-cific Downstream Shipper Storage Services Provider intends to use.

Operating Agreement

[contractLegalName]

Documents


• Resultant Firm Withdrawal Quantity. Each Resultant Firm Withdrawal Quantity shall refer to a specific Downstream Shipper Customer intends to use and a specific Upstream Shipper Storage Services Provider intends to use.

If conditional quantities have been requested, for the relevant period, for each in-volved Shipper Pair, the Storage Request Response Notice shall contain:

• Resultant Conditional Injection Quantity. Each Resultant Conditional Injection Quantity shall refer to a specific Upstream Shipper Customer intends to use and a specific Downstream Shipper Storage Services Provider intends to use.

• Resultant Conditional Withdrawal Quantity. Each Resultant Conditional With-drawal Quantity shall refer to a specific Downstream Shipper Customer in-tends to use and a specific Upstream Shipper Storage Services Provider in-tends to use.

If quantities are not to be offtaken or delivered in a steady hourly rate over the rele-vant period, these quantities shall be specified in an hourly rate for each Hour of the relevant period.

The quantities and Shipper Pair(s) specified in the Storage Request Response Notice shall be used by the concerning Shippers to nominate transportation at the relevant system operator(s).


6.3.3 The initial Storage Request Response Notice shall be issued by the Storage Services Provider before the deadline as specified in the OTS at [7A.5.3].

A Storage Request Response Notice revising a previous Storage Request Response Notice shall be issued by the Storage Services Provider considering the agreed lead time as specified in the OTS at [7B.5.3] before any revision may become effective and the Storage Request Response Notice has to be sent by the Storage Services Provider and received by the Customer prior to this lead time.

If for the SSA for the relevant period a Storage Request Response Notice is issued, such Storage Request Response Notice shall replace any previous Storage Request Response Notice for the SSA for the relevant period.

Fallback procedure

6.3.4 If Customer does not receive an agreed periodic Storage Request Response Notice or if Customer does not receive a Storage Request Response Notice after Customer is-sued a revised Storage Request Notice, the Customer will issue a wake up call. If, after the call, a Storage Request Response Notice is still not received, the confirmed quantities shall be deemed to be for each day the requested firm quantities as re-quested in the most actual Storage Request Notice and the default Shipper(s) will be used.

Operating Agreement

[contractLegalName]

Documents


6.4 Trades Confirmation Notice (TCN)

General purpose

6.4.1 The Trades Confirmation Notice shall be issued by the Storage Services Provider to inform the Trading Facility User about the approval and rejection of executed trades.


6.4.2 For each executed trade, the Trades Confirmation Notice shall contain:

• SSA identification.

• Trade execution date and time stating the time the trade was executed on the Trading Facility.

• Original order identification identifying the order given by the Trading Facility User.

• Instrument type specifying the type of SSA component traded.

• Instrument duration specifying the duration in case of duration related in-strument types.

• Quantity defining the quantity traded.

• Unit of measurement.

• Settlement date and time specifying the date and time the SSA component changes ownership.

• Trade action (buy or sell).

• Price (amount and currency).

• Conclusion specifying whether the executed trade has been approved or re-jected.

• Rejection reason.


6.4.3 The initial Trades Confirmation Notice shall be issued by the Storage Services Provider before the deadline as specified in the OTS at [8A.2.3].

A Trades Confirmation Notice revising a previous Trades Confirmation Notice shall be issued by the Storage Services Provider as soon as reasonably possible but ultimate-ly before the start of the next Day.

If for the SSA for the relevant period a Trades Confirmation Notice is issued, such Trades Confirmation Notice shall replace any previous Trades Confirmation Notice for the SSA for the relevant period.

Fallback procedure

6.4.4 If the Trading Facility User did conclude trades on the Trading Facility but does not receive a Trades Confirmation Notice, the Trading Facility User will instanteanously issue a wake up call. If, after the call, a Trades Confirmation Notice is still not re-

Operating Agreement

[contractLegalName]

Documents


ceived, the executed trades are to be considered as rejected by the Storage Services Provider.

6.5 Acknowledgment Notice

General purpose

6.5.1 The Acknowledgment Notice shall be issued by one Party to inform the other Party about the receipt and or acceptance of a document sent by the latter Party.


6.5.2 The Acknowledgment Notice shall contain:

• An identification of the document that is acknowledged.

• The reason of the acknowledgment:

o Document has been received.

o Document has been processed and awaits approval.

o Document has been processed and approved (accepted).


6.5.3 If no electronic data interchange is in place, the acknowledging Party shall as soon as possible notify the other Party by phone and issue the Acknowledgment Notice thereupon. If electronic data interchange is in place, the acknowledging Party shall as soon as possible notify the other Party by issuing the Acknowledgment Notice.

Fallback procedure

6.5.4 If electronic data interchange is in place and the Acknowledgment Notice is sent but considered not to be received by the other Party, the acknowledging Party will notify the other Party by phone.

6.6 Rejection Notice

General purpose

6.6.1 The Rejection Notice shall be issued by one Party to inform the other Party about the rejection of a document sent by the latter Party.


6.6.2 The Rejection Notice shall contain:

• An identification of the document that has been rejected.

Operating Agreement

[contractLegalName]

Documents


• The reason of the rejection.


6.6.3 If no electronic data interchange is in place, the rejecting Party shall as soon as possible notify the other Party by phone and issue the Rejection Notice thereupon. If electronic data interchange is in place, the rejecting Party shall as soon as possible notify the other Party by issuing the Rejection Notice.

Fallback procedure

6.6.4 If electronic data interchange is in place and the Rejection Notice is sent but considered not to be received by the other Party, the rejecting Party will notify the other Party by phone.

Operating Agreement

[contractLegalName]

Signatures


7 Signatures

7.0

Place Date

Storage Services Provider Storage Services Provider

[Entity]

[ENTITY}

Name Name Title Title

Place Date

Customer Customer

[buyerLegalName]

[buyerLegalName]

Operating Agreement

[contractLegalName]

Operational Term Sheet

GasTerra OA 2018-2019 Final Clean.docx OTS I

8 Appendix A – Operational Term Sheet

Validity of this Operational Term Sheet

Valid from (including) gas day 01.04.2018

Valid to (including) gas day 31.03.2019

[buyerLegalName] information 1 Identification 1.1

[buyerLegalName] identification 1.1.1 [buyerId]

Identification coding system 1.1.2 Edigas

Operational unit A 1.2A Operational unit B 1.2B

Short name 1.2A.1 [buyerOPSUnitA] Short name 1.2B.1 [buyerOPSUnitB]

Visiting address 1.2A.2

Visiting address 1.2B.2

Phone 1.2A.3 Phone 1.2B.3

Phone (backup) Phone (backup)

Fax (ordering) 1.2A.4 Fax (ordering) 1.2B.4

Fax (backup) Fax (backup)

Email 1.2A.5 Email 1.2B.5

Email (ordering) 1.2A.6 Email (ordering) 1.2B.6

Contact 1.2A.7

Contact 1.2B.7

Responsible 1.2A.8

Responsible 1.2B.8

EDI format 1.2A.9

EDI format 1.2B.9

EDI protocol 1.2A.10

EDI protocol 1.2B.10

Shipper code 1.2A.11

[ENTITY] information 2 Identification 2.1

[ENTITY] identification 2.1.1 [sellerID]

Identification coding system 2.1.2 Edigas

Operational unit A 2.2A Operational unit B 2.2B

Short name 2.2A.1 Gas Storage Operations Short name 2.2B.1 Trading Operations

Visiting address 2.2A.2

Visiting address 2.2B.2

Phone 2.2A.3 Phone 2.2B.3

Phone (backup) Phone (backup)

Fax (ordering) 2.2A.4 Fax (ordering) 2.2B.4

Fax (backup) Fax (backup)

Email 2.2A.5 Email 2.2B.5

Email (ordering) 2.2A.6 Email (ordering) 2.2B.6

Contact 2.2A.7

Contact 2.2B.7

Responsible 2.2A.8

Responsible 2.2B.8

EDI format 2.2A.9

EDI format 2.2B.9

EDI protocol 2.2A.10

EDI protocol 2.2B.10

Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS II

Contract information 3

Identification 3.1

Legal contract name 3.1.1 [contractLegalName]

Identification used by [buyerLegalName] 3.1.2

Identification used by [ENTITY] 3.1.3

Contract details 3.2

Type of contract 3.2.1 Storage Service Agreement

Time definition 3.2.2 UTC + 1

Daylight savings time (DST) system used 3.2.3 European

Start of gas day 3.2.4 06:00

Start of gas week 3.2.5 Monday

Start date/time 3.2.6 dd.mm.ccyy hh:mm

End date/time 3.2.7 dd.mm.ccyy hh:mm

Ordered by 3.2.8 [buyerLegalName]

Delivery terms 3.2.9 firm (with a possibility to request conditional additional quantities)

Flexible or fixed rate 3.2.10 flexible

Contractual unit 3.2.11 kWh

Contract balance usage 3.2.12 Y/N

DST influences daily quantity? 3.2.13 Yes

Delivery source 3.2.14 Fixed (TTF)

Maintenance option 3.2.15 none

Agreed quantities 3.3

Quantities per 3.3.1

Output quantities 3.3.4

From Day To Day Average 3.3.4.1 Maximum 3.3.4.2 Minimum 3.3.4.3 Fallback 3.3.4.4

The quantity of Gas-in-Storage as defined in the SSA in article 2.2.

Input quantities 3.3.5

From Day To Day Average 3.3.5.1 Maximum 3.3.5.2 Minimum 3.3.5.3 Fallback 3.3.5.4

The quantity of Available Space minus the quanti-ty of Gas-in-Storage as defined in the SSA in article 2.2.

Balance (quantities in kWh) 3.3.6

From Day To Day Maximum 3.3.6.1 Minimum 3.3.6.2

Additional information 3.4

Quantities depend on the number of SBUs allotted to the agreement, the quantity of Gas-in-Storage, the rules concerning daily difference, the withdrawal factor definition and trades done on the secondary market.

Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS III

Delivery/Redelivery point information 4A

Identification 4A.1

Name 4A.1.1 Title Transfer Facility

Identification 4A.1.2 TTF

Identification coding system 4A.1.3 System operator

Details 4A.2

Usage under the contract 4A.2.1 delivery and redelivery

Physical/non-physical 4A.2.2 non-physical

Delivery terms 4A.2.3 firm (with a possibility to request conditional additional quantities)

Flexible or fixed rate 4A.2.4 Flexible (applying the rules as defined in the Storage Services Agreement)

Nomination at system operator 4A.2.5 both parties, of which nominaion of [ENTITY} will be a single-sided nomination

Lead time before change 4A.2.6 no change for gas day D allowed after 11:00 LET on D-1

Commodity 4A.2.7 Storage Services

Agreed quantities 4A.3

Quantities in unit 4A.3.1

Output quantities 4A.3.4

From Day To Day Maximum 4A.3.4.1 Minimum 4A.3.4.2 Fallback 4A.3.4.3 Max rate 4A.3.4.4 Min rate 4A.3.4.5

0

Input quantities 4A.3.5

From Day To Day Maximum 4A.3.5.1 Minimum 4A.3.5.2 Fallback 4A.3.5.3 Max rate 4A.3.5.4 Min rate 4A.3.5.5

0

Agreed qualities 4A.4

Property Unit Maximum 4A.4.1 Minimum 4A.4.2

Upstream shipper(s) 4A.5

Flexible or predefined 4A.5.1 flexible taking into account informing [ENTITY] at least 3 business days before using a new shipper code.

Code default shipper 4A.5.2

Codes additional shippers 4A.5.3

Downstream shipper(s) 4A.6

Flexible or predefined 4A.6.1 flexible taking into account informing [ENTITY] at least 3 business days before using a new shipper code.

Code default shipper 4A.6.2

Codes additional shippers 4A.6.3

Additional information 4A.7

Quantities depend on the number of SBUs allotted to the agreement, the quantity of Gas-in-Storage, the rules concerning daily difference, the withdrawal factor definition and trades done on the secondary market. [ENTITY] will always and only use shipper code GSSFLEX.

Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS IV

Ordering procedure 7

Daily Ordering 7A.1

Periodically/Conditional/Optional/Not used 7A.1.1 Periodically

periodicity when periodically 7A.1.2 Daily

condition(s) when conditional 7A.1.3

Concerning period 7A.1.4 Week

Storage Availability Notice (SAN) 7A.2

Mandatory/Conditional/Not used 7A.2.1 Mandatory


Deadline receipt notice 7A.2.3 10:00 on 1 Days before beginning of the concerning period

Sender 7A.2.4 Gas Storage Operations

Recipient (a)/Copy recipient (b) [buyerOPSUnitA]/[buyerOPSUnitB]7A.2.5a [buyerOPSUnitA]/[buyerOPSUnitB] 7A.2.5b

Format and protocol Excel sheet by email 7A.2.6a 7A.2.6b

Backup format and protocol Fax 7A.2.7a 7A.2.7b

Storage Request Notice (SRN) 7A.4




Sender 7A.4.4 [buyerOPSUnitA]

Recipient (a)/Copy recipient (b) Gas Storage Operations 7A.4.5a 7A.4.5b



Storage Request Response Notice (SRRN) 7A.5




Sender 7A.5.4 [Department]




Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS V

Ordering procedure - continued 7

Revised Availability 7B.1

Periodically/Conditional/Optional/Not used 7B.1.1 Optional

periodicity when periodically 7B.1.2

condition(s) when conditional 7B.1.3

Concerning period 7B.1.4 Week

Number of availability revisions allowed 7B.1.5 Unlimited

thereof after 1st lead time for period 7B.1.6

Special revision provisions 7B.1.7

Storage Availability Notice (SAN) 7B.2

Mandatory/Conditional/Not used 7B.2.1 Mandatory


Lead time before change 7B.2.3 10:00 on 1 Days before beginning of the concerning period

Sender 7B.2.4 [Department]

Recipient (a)/Copy recipient (b) [buyerOPSUnitA]/[buyerOPSUnitB]7B.2.5a [buyerOPSUnitA]/[buyerOPSUnitB] 7B.2.5b

Format and protocol Excel sheet by email 7B.2.6a 7B.2.6b

Backup format and protocol Fax 7B.2.7a 7B.2.7b

Storage Request Notice (SRN) 7B.4




Sender 7B.4.4 [buyerOPSUnitA]/[buyerOPSUnitB]

Recipient (a)/Copy recipient (b) [Department] 7B.4.5a [Department] 7B.4.5b



Storage Request Response Notice (SRRN) 7B.5








Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS VI

Ordering procedure - continued 7

Revised Request 7D.1

Periodically/Conditional/Optional/Not used 7D.1.1 Optional

periodicity when periodically 7D.1.2

condition(s) when conditional 7D.1.3

Concerning period 7D.1.4 Week

Number of request revisions allowed 7D.1.5 Unlimited

thereof after 1st lead time for period 7D.1.6

Special revision provisions 7D.1.7

Storage Request Notice (SRN) 7D.4

Mandatory/Conditional/Not used 7D.4.1 Mandatory


Lead time before change 7D.4.3 11:00 on 1 Days before beginning of the concerning period

Sender 7D.4.4 [buyerOPSUnitA]/[buyerOPSUnitB]

Recipient (a)/Copy recipient (b) [Department] 7D.4.5a [Department] 7D.4.5b

Format and protocol Excel sheet by email 7D.4.6a 7D.4.6b

Backup format and protocol Fax 7D.4.7a 7D.4.7b

Storage Request Response Notice (SRRN) 7D.5

Mandatory/Conditional/Not used 7D.5.1 Mandatory


Lead time before change 7D.5.3 13:30 on 1 Days before beginning of the concerning period

Sender 7D.5.4 [Department]

Recipient (a)/Copy recipient (b) [buyerOPSUnitA]/[buyerOPSUnitB]7D.5.5a [buyerOPSUnitA]/[buyerOPSUnitB] 7D.5.5b

Format and protocol Excel sheet by email 7D.5.6a 7D.5.6b

Backup format and protocol Fax 7D.5.7a 7D.5.7b

Revised Request Response 7E.1

Periodically/Conditional/Optional/Not used 7E.1.1 Optional

periodicity when periodically 7E.1.2

condition(s) when conditional 7E.1.3

Concerning period 7E.1.4 Week

Number of req. response revisions allowed 7E.1.5 Unlimited

thereof after 1st lead time for period 7E.1.6 Unlimited

Special revision provisions 7E.1.7

Storage Request Response Notice (SRRN) 7E.5

Mandatory/Conditional/Not used 7E.5.1 Mandatory

condition(s) when conditional 7E.5.2

Lead time before change 7E.5.3 13:30 on 1 Days before beginning of the concerning period

Sender 7E.5.4 [Department]

Recipient (a)/Copy recipient (b) [buyerOPSUnitA]/[buyerOPSUnitB] 7E.5.5a [buyerOPSUnitA]/[buyerOPSUnitB] 7E.5.5b

Format and protocol Excel sheet by email 7E.5.6a 7E.5.6b

Backup format and protocol Fax 7E.5.7a 7E.5.7b

Operating Agreement

[contractLegalName]


GasTerra OA 2018-2019 Final Clean.docx OTS VII

Trading procedure 8

Daily Ordering and Closing 8A.1

Periodically/Conditional/Optional/Not used 8A.1.1 Conditional

periodicity when periodically 8A.1.2

condition(s) when conditional 8A.1.3 If Trading Facility User concluded trades during the trading window.

Trades Confirmation Notice (TCN) 8A.2

Mandatory/Conditional/Not used 8A.2.1 M


Deadline receipt notice 8A.2.3 As early a reasonably possible put no later than the next day at 10:00 LET.

Sender 8A.2.4 [Department]




Revised Trade Confirmation 8B.1

Periodically/Conditional/Optional/Not used 8B.1.1 Conditional

periodicity when periodically 8B.1.2

condition(s) when conditional 8B.1.3 If previous sent TCN has to be revised.

Trades Confirmation Notice (SRN) 8B.4

Mandatory/Conditional/Not used 8B.4.1 M






GasTerra OA 2018-2019 Final Clean - the ICE Agreement [contractLegalName] Definitions GasTerra OA...

Documents

Transcript of GasTerra OA 2018-2019 Final Clean - the ICE Agreement [contractLegalName] Definitions GasTerra OA...