Mid-Alberta Pipeline Clause Samples

Mid-Alberta Pipeline. If, at any time during the period ending two (2) years from the date hereof, Seller or any other member of the BP Group acquires ownership of the Mid-Alberta Pipeline currently owned by Imperial Oil, Seller shall provide notice thereof to Buyer. PipelineCo or an Affiliate of PipelineCo shall have the option, exercisable upon written notice to Seller at any time within thirty (30) days following receipt of notice, to purchase the Mid-Alberta Pipeline from Seller or the applicable member of the BP Group at the all in cost paid by Seller or the applicable member of the BP Group and otherwise on the same terms and conditions, mutatis mutandis, as such pipeline was acquired by Seller or the applicable member of the BP Group.

Related to Mid-Alberta Pipeline

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • Natural Gas 21.1 Subject to Article 21.2, the Indian domestic market shall have the first call on the utilisation of Natural Gas discovered and produced from the Contract Area. Accordingly, any proposal by the Contractor relating to Discovery and production of Natural Gas from the Contract Area shall be made in the context of the Government's policy for the utilisation of Natural Gas and shall take into account the objectives of the Government to develop its resources in the most efficient manner and to promote conservation measures. 21.2 The Contractor shall have the right to use Natural Gas produced from the Contract Area for the purpose of Petroleum Operations including reinjection for pressure maintenance in Oil Fields, gas lifting and captive power generation required for Petroleum Operations. 21.3 For the purpose of sales in the domestic market pursuant to this Article 21, the Contractor shall have freedom to market the Gas and sell its entitlement.

  • Logistics The Client shall arrange their own transportation and accommodation, unless Client and Performer agree otherwise. If requested, the Performer shall arrange transport within Ostrava, and provide accommodation in a hotel.

  • Electric Storage Resources Developer interconnecting an electric storage resource shall establish an operating range in Appendix C of its LGIA that specifies a minimum state of charge and a maximum state of charge between which the electric storage resource will be required to provide primary frequency response consistent with the conditions set forth in Articles 9.5.5, 9.5.5.1, 9.5.5.2, and 9.5.5.3 of this Agreement. Appendix C shall specify whether the operating range is static or dynamic, and shall consider (1) the expected magnitude of frequency deviations in the interconnection; (2) the expected duration that system frequency will remain outside of the deadband parameter in the interconnection; (3) the expected incidence of frequency deviations outside of the deadband parameter in the interconnection; (4) the physical capabilities of the electric storage resource; (5) operational limitations of the electric storage resources due to manufacturer specification; and (6) any other relevant factors agreed to by the NYISO, Connecting Transmission Owner, and Developer. If the operating range is dynamic, then Appendix C must establish how frequently the operating range will be reevaluated and the factors that may be considered during its reevaluation. Developer’s electric storage resource is required to provide timely and sustained primary frequency response consistent with Article 9.5.5.2 of this Agreement when it is online and dispatched to inject electricity to the New York State Transmission System and/or receive electricity from the New York State Transmission System. This excludes circumstances when the electric storage resource is not dispatched to inject electricity to the New York State Transmission System and/or dispatched to receive electricity from the New York State Transmission System. If Developer’s electric storage resource is charging at the time of a frequency deviation outside of its deadband parameter, it is to increase (for over-frequency deviations) or decrease (for under-frequency deviations) the rate at which it is charging in accordance with its droop parameter. Developer’s electric storage resource is not required to change from charging to discharging, or vice versa, unless the response necessitated by the droop and deadband settings requires it to do so and it is technically capable of making such a transition.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three