Agreement to Use Services Relating to Pipelines, Tankage and Loading rack Sample Clauses

Agreement to Use Services Relating to Pipelines, Tankage and Loading rack. The Parties intend to be strictly bound by the terms set forth in this Agreement, which sets forth revenues to HEP Tulsa and HEP Storage-Tulsa to be paid by ▇▇▇▇▇ Tulsa and requires HEP Tulsa and HEP Storage-Tulsa to provide certain transportation, storage and loading services to ▇▇▇▇▇ Tulsa. The principal objective of HEP Tulsa is for ▇▇▇▇▇ Tulsa to meet or exceed its obligations with respect to the Minimum Pipeline Revenue Commitment, to meet or exceed its obligations with respect to the Minimum Group 1 Tankage Revenue Commitment, and to meet or exceed its obligations with respect to the Minimum Group 1 Loading Rack Revenue Commitment. The principal objective of HEP Storage-Tulsa is for ▇▇▇▇▇ Tulsa to meet or exceed its obligations with respect to the Minimum Group 2 Tankage Revenue Commitment and to meet or exceed its obligations with respect to the Minimum Group 2 Loading Rack Commitment. The principal objective of ▇▇▇▇▇ Tulsa is for HEP Tulsa and HEP Storage-Tulsa to provide services to ▇▇▇▇▇ Tulsa in a manner that enables ▇▇▇▇▇ Tulsa to operate the Refinery.
View SourceView Similar (4)

Related to Agreement to Use Services Relating to Pipelines, Tankage and Loading rack

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.

  • Connecting Transmission Owner’s Scope of Work and Responsibilities The Connecting Transmission Owner will design, construct, own, operate and maintain all Connecting Transmission Owner’s Interconnection Facilities, except as otherwise stated above and in the Project Specific Specifications. The Connecting Transmission Owner will complete all engineering reviews, field verifications and witness testing, etc. in accordance with the ESBs and the Project Specific Specifications. Connecting Transmission Owner shall provide the revenue metering CT/PT units and meter socket enclosure. The Connecting Transmission Owner shall: • provide, run, and wire both ends of the color-coded cable for the revenue metering instrument transformer secondary wiring; • perform all terminations; and • supply and install the meter. The revenue meter may require a communications link to the RTU. The Connecting Transmission Owner will specify and run those communications cables. The Connecting Transmission Owner shall complete all wiring, testing and commissioning of the RTU.

  • 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.

  • 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