Coordination of Scheduled Outages Sample Clauses

Coordination of Scheduled Outages. 9.1 Coordinating Outages Operating Protocols. 35.9.1
AutoNDA by SimpleDocs
Coordination of Scheduled Outages. Buyer and Seller shall cooperate with each other to use commercially reasonable efforts to coordinate the scheduled outages of the Facility and other major maintenance or overhaul activities that may require a partial or complete reduction in the output of the Facility with any scheduled temporary shut down or other anticipated reduction in the operations of the Bayway Refinery so
Coordination of Scheduled Outages. The coordination of planned transmission or generation outages for maintenance and other anticipated requirements will assure that Parties are aware of anticipated events on each other’s systems that could affect the other Party’s own analyses and planning. Pursuant to Article 6, the Parties shall exchange the most current information on proposed scheduled outage information and provide a timely response on potential impacts of proposed scheduled outages as well as provide information independently on approved and anticipated scheduled outages formatted as required for the SDX System, i.e., the system used by NERC to exchange system data.36 If changes to scheduled outages create issues on the system, the Parties jointly will develop remedial steps.37 The coordination of scheduled outages provisions are consistent with XXXx accepted by the Commission.38 In addition to scheduled outages, the Parties have also agreed to notify each other of emergency maintenance or forced outages by reporting an outage in SDX or Reliability Coordinator Information Systems, as soon as the conditions are identified, but not to exceed 30 minutes.39 This provision is consistent with other XXXx accepted by the Commission.40 30 JRCA § 5.3.2. 31 See JRCA, Attachment 1. 32 JRCA § 5.3.1. 33 Tennessee Valley Authority Act of 1933, 16 U.S.C. §§ 831- 831ee. 34 See id. 35 JRCA § 5.5. 36 JRCA § 6.1.1. 37 JRCA § 6.1.2. 38 See ER19-1905 Order (accepting Duke Energy Progress-PJM JOA §§ 7.1 - 7.1.2); ER19-2282 Order (accepting NYISO-PJM JOA § 35.9); ER16-1304 Order (accepting MISO-PJM JOA § 5.1.1). 39 JRCA § 6.1.3. 40 See ER19-1905 Order (accepting Duke Energy Progress-PJM JOA § 8.1.1); ER16-1304 Order (accepting MISO-PJM JOA § 7.1). Xxxxxxxxx Xxxxxxxx X. Bose June 6, 2023
Coordination of Scheduled Outages 

Related to Coordination of Scheduled Outages

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Commencement of Work Engineer shall not commence any field work under this Contract until he/she/it has obtained all required insurance and such insurance has been approved by County. As further set out below, Engineer shall not allow any subcontractor/subconsultant(s) to commence work to be performed in connection with this Contract until all required insurance has been obtained and approved and such approval shall not be unreasonably withheld. Approval of the insurance by County shall not relieve or decrease the liability of Engineer hereunder.

  • Force Majeure Delays In any case where either party hereto is required to do any act (other than the payment of money), delays caused by or resulting from Acts of God or Nature, war, civil commotion, fire, flood or other casualty, labor difficulties, shortages of labor or materials or equipment, government regulations, delay by government or regulatory agencies with respect to approval or permit process, unusually severe weather, or other causes beyond such party’s reasonable control the time during which act shall be completed, shall be deemed to be extended by the period of such delay, whether such time be designated by a fixed date, a fixed time or “a reasonable time.”

  • Monitoring System In each case in which the Custodian has exercised delegated authority to place Assets with a Foreign Custodian, the Custodian shall establish a system, to re-assess or re-evaluate selected Foreign Custodians, at least annually in accordance with Rule 17f-5(c)(3).

  • Standard Operating Procedures Over approximately the past eight years, the Parties have been supplying select Products to one another for use in the operation of their respective businesses within the United States of America, Canada and Mexico. The Parties developed and been following certain standard operating procedures in connecting with, among other topics, forecasting, production planning, ordering, delivering and resolving claims on the Products supplied to one another (the “Current SOPs”). The Parties will be updating their respective business systems over the next six months, and the updates to these business systems will require the Parties to modify the Current SOPs. Once the Parties have completed the updates to the business systems and agreed on the necessary modifications to the Current SOPs, the Parties will sign a written amendment to this Agreement appending the updated standard operating procedures (the “Updated SOPs”). Until the Parties have signed a written amendment appending the Updated SOPs, the parties will continue to follow the Current SOPs. The Parties will comply with the applicable SOPs in connection with the purchase and sale of products identified in a Purchase Schedule. The Parties may add terms and conditions to, and amend the terms and conditions of, the SOP in a Purchase Schedule, but any additional and amended terms and conditions in a Purchase Schedule supplementing and modifying the SOP will only apply the specific products identified in that Purchase Schedule for its duration.

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