Dynamic Schedule Flows Clause Samples

The Dynamic Schedule Flows clause establishes a framework for adjusting project timelines and task sequences in response to changing circumstances or new information. It typically allows parties to modify deadlines, reorder deliverables, or shift resource allocations as project needs evolve, often through a formal notification or approval process. This clause is essential for maintaining project flexibility and minimizing disruptions, as it provides a structured method for adapting schedules without breaching the contract.
Dynamic Schedule Flows. Requirements: Each Party agrees to provide the other Party with the actual amount and future projection of dynamic schedule flows. All dynamic schedule flows and tags will be submitted in accordance with NERC reliability standards and NAESB business practices.
View SourceView Similar (10)
Dynamic Schedule Flows. Requirements: Each Party agrees to provide the other Party with the actual amount and future projection of dynamic schedule flows commencing no later than sixty (60) days from the signing of this Agreement. All dynamic schedule flows and tags will be submitted in accordance with NERC policy and procedures.
View SourceView Similar (6)
Dynamic Schedule Flows. Each Party shall provide the other Party with the actual amount and future projection of dynamic schedule flows. All dynamic schedule flows and tags shall be submitted in accordance with NERC policy and procedures. ARTICLE SIX - RECIPROCAL COORDINATION OF FLOWGATES 6.1 Reciprocal Coordination of Flowgates Operating Protocols.
View SourceView Similar (2)
Dynamic Schedule Flows. MAPPCOR and MISO shall provide each other with the actual amount and future projection of dynamic schedule flows. All dynamic schedule flows and tags will be submitted in accordance with NERC policy and procedures. 4/16/04 ▇▇▇▇▇ ▇▇▇▇▇ Draft 1 Initial draft 11/30/04 ▇▇▇ ▇▇▇▇▇▇▇▇▇ 4.1 Conform draft to current PJM-MISO CMP implementation practices and FERC Orders. 01/11/05 RFWG Changes for MAPPCOR-MISO SOA • Participating Operating Entities will agree to observe limits on an extensive list of coordinated external Flowgates • Like all Control Areas, Market-Based Operating Entities will have Firm Gen-to- Load Flows upon those Flowgates. • Market-Based Operating Entities will determine these Firm Gen-to-Load Flows using the published analysis process, and constrain their operations to limit Firm Gen-to-Load Flows on the Coordinated Flowgates to no more than the calculated Firm Gen-to-Load Limit established in the analysis. • In real-time, Market-Based Operating Entities will calculate and monitor when the one-hour ahead projected and actual flows exceed the Firm Gen-to-Load Limits established in the day-ahead process. • Market-Based Operating Entities will post to the IDC the actual and the one-hour ahead projected market flow, consisting of the Firm Gen-to-Load Flow and the additional Non-Firm Economic Dispatch Flow, for both internal and external Coordinated Flowgates. • Market-Based Operating Entities will provide to the IDC detailed representation of their marginal units, so that the IDC can continue to effectively compute the effects of all tagged transactions regardless of the size of the market area. These tagged transactions will include transactions into the market, transactions out of the market, and tagged grandfathered transactions within the market. • When there is a TLR 3a or higher called on a Coordinated Flowgate, and the Market-Based Operating Entity’s actual/one-hour ahead projected Market Flows exceed the Firm Gen-to-Load Limits, Market-Based Operating Entities will • When there is a TLR 5a or 5b, all Transmission Providers will curtail or redispatch their respective systems to provide their shares of NNL reductions as directed by the IDC. • Because the IDC will have the real-time/one-hour ahead projected flows throughout the Market-Based Operating Entity’s system (as represented by the impacts upon various Coordinated Flowgates), the effectiveness of the IDC will be greatly enhanced. • The above processes refer to the “Congestion Management” ...
View Source

Related to Dynamic Schedule Flows

  • Schedule Updates the Contractor agrees to maintain the Work duration schedule updates on an ongoing basis and, when the County requests it, include the updates in its payment request. The Contractor may be required to submit a narrative report with each monthly update which shall include a description of current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective action taken or proposed. Failure to do so may be considered a material breach of the Contract. Any additional or unanticipated costs or expense required to maintain the schedules shall be solely the Contractor’s obligation and Contractor agrees not to charge the County.

  • CONVERSION SCHEDULE The Original Issue Discount Senior Convertible Debentures due on March 1, 2018 in the aggregate principal amount of $330,000 are issued by Legend Oil and Gas, Ltd., a Colorado corporation. This Conversion Schedule reflects conversions made under Section 4 of the above referenced Debenture.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (‘SLA’): (a) we are liable for any remedy or rebate allowed to you under the SLA; and (b) subject to clauses 34 to 38, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Expected Amortization Schedule for Principal Unless an Event of Default shall have occurred and be continuing on each Payment Date, the Indenture Trustee shall distribute to the Holders of record as of the related Record Date amounts payable pursuant to Section 8.02(e) of the Indenture as principal, in the following order and priority: (1) to the holders of the Tranche A-1 Recovery Bonds, until the Outstanding Amount of such Tranche of Recovery Bonds thereof has been reduced to zero; (2) to the holders of the Tranche A-2 Recovery Bonds, until the Outstanding Amount of such Tranche of Recovery Bonds thereof has been reduced to zero; (3) to the holders of the Tranche A-3 Recovery Bonds, until the Outstanding Amount of such Tranche of Recovery Bonds thereof has been reduced to zero; provided, however, that in no event shall a principal payment pursuant to this Section 3(c) on any Tranche on a Payment Date be greater than the amount necessary to reduce the Outstanding Amount of such Tranche of Recovery Bonds to the amount specified in the Expected Amortization Schedule set forth on Schedule A hereto for such Tranche and Payment Date.