Required Infrastructure Sample Clauses

Required Infrastructure. Neither (i) the Refinery (including the storage tanks, pipelines, racks, vessels, railroads, terminals and docks associated therewith) nor (ii) any of the storage tanks, pipelines, racks, vessels, railroads, railcars, railroad loading and unloading facilities, terminals, docks or other facilities, equipment and infrastructure that are necessary for MLC to fulfill its obligations under the Supply and Offtake Documents and the transactions contemplated thereby (such items in clauses (i) and (ii), collectively the “Required Infrastructure”) shall have been affected by loss or damage (whether or not covered by insurance) that reasonably would be expected to prevent the Borrower from storing crude oil at the Refinery, transporting crude oil to the Refinery, storing refined products at the Refinery or transporting refined products from the Refinery to delivery points for sales, except to the extent that such damage can be remedied within 30 days and the Borrower commits to make such repairs, in each case, in a manner and on terms reasonably satisfactory to the Administrative Agent.
AutoNDA by SimpleDocs
Required Infrastructure. (a) MLC’s obligations under this Agreement, the other PESRM Transaction Documents, the MLC-PESIC Secured Prepay Transactions, the CO Supply Contracts, the PESRM-MLC Secured Prepay Transactions, RP Sales Contracts and/or Cover Transactions to supply Crude Oil to PESRM, to sell Crude Oil to purchasers, to purchase Refined Products from PESRM, to sell Refined Products to purchasers identified by PESRM and to purchase Refined Products from suppliers identified by PESRM are, in all respects, subject to any limits imposed by the working capacity available to MLC at any time on any vessels, barges, docks, racks, railcars, railroads, railroad loading and unloading facilities, terminals, pipelines, storage tanks and other facilities and equipment that are necessary to the performance by PESRM or MLC of its obligations under the PESRM Transactions, the MLC-PESIC Secured Prepay Transactions, the CO Supply Contracts, the PESRM-MLC Secured Prepay Transactions, the RP Sales Contracts and/or the Cover Transactions, including any such facilities at the Refinery, the other Basic Infrastructure and the Butane Rail Facility (collectively, as of any date of determination, the “Required Infrastructure”), and any failure of performance by MLC under any such contracts or transactions that results, directly or indirectly, from any limits imposed by the working capacity allocated to MLC on Required Infrastructure shall be excused and shall not give rise to a MLC Event of Default.

Related to Required Infrastructure

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ICG, ICG shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks, and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from CBB to Verizon, CBB, at CBB’s own expense, shall:

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Connecting Transmission Owner’s Attachment Facilities Construction The Connecting Transmission Owner’s Attachment Facilities shall be designed and constructed in accordance with Good Utility Practice. Upon request, within one hundred twenty (120) Calendar Days after the Commercial Operation Date, unless the Connecting Transmission Owner and Developer agree on another mutually acceptable deadline, the Connecting Transmission Owner shall deliver to the Developer “as-built” drawings, relay diagrams, information and documents for the Connecting Transmission Owner’s Attachment Facilities set forth in Appendix A. The Connecting Transmission Owner [shall/shall not] transfer operational control of the Connecting Transmission Owner’s Attachment Facilities and Stand Alone System Upgrade Facilities to the NYISO upon completion of such facilities.

  • Connecting Transmission Owner’s Attachment Facilities Connecting Transmission Owner shall design, procure, construct, install, own and/or control the Connecting Transmission Owner’s Attachment Facilities described in Appendix A hereto, at the sole expense of the Developer.

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner.

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

Time is Money Join Law Insider Premium to draft better contracts faster.