Required Infrastructure Clause Samples

The Required Infrastructure clause defines the specific facilities, equipment, systems, or resources that must be provided or maintained to support the performance of obligations under an agreement. This may include items such as internet connectivity, hardware, software, or physical workspace, depending on the nature of the contract. By clearly outlining these requirements, the clause ensures that both parties understand what infrastructure is necessary, thereby preventing disputes and ensuring smooth project execution.
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.
View SourceView Similar (2)
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. (b) In the event that working capacity allocated to MLC on Required Infrastructure becomes unavailable for any reason (including any provision of this Section 6.05 or Section 6.04), PESRM shall be required to use commercially reasonable efforts to secure replacement capacity at PESRM’s sole cost and expense as necessary to permit MLC to meet its delivery, receipt and resale 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, as applicable.
View SourceView Similar (2)
Required Infrastructure. Any user of the Services shall obtain and maintain all computer hardware, software and communications equipment needed to receive the Services (such as the Enabling Equipment) and to keep such infrastructure functioning and virus-free, and Barco shall bear no liability for any non-performance of the Services due to a lack of adequacy, accuracy, concurrency or other matters related to user’s infrastructure.
View Source

Related to Required Infrastructure

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • 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

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.

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