Reporting Milestones Sample Clauses

Reporting Milestones. If Seller fails to achieve any Reporting Milestones within three (3) Months after its Milestone Date as set forth in Attachment B (Milestone Events) as extended for reasons of Force Majeure or as otherwise provided in this Agreement, then Seller shall within fifteen (15) Business Days thereafter submit for Company’s review and approval, which approval shall not be unreasonably withheld, a detailed plan which describes: (i) the reasons why such Reporting Milestone was not achieved; (ii) Seller's proposed measures for achieving such Reporting Milestone as soon as practicable thereafter; and (iii) Seller's proposed measures for meeting the Commercial Operation Date Deadline. Until such Reporting Milestone is met, Seller shall provide Company with Monthly Progress Reports as to the status of Seller's efforts to achieve such Reporting Milestone. Unless and until Seller substantially completes each Reporting Milestone to the reasonable satisfaction of Company, Seller shall not be deemed to have achieved the Commercial Operation Date.

Reporting Milestones. (See Section 2.4(A)(1) (Guaranteed Milestones Other than Commercial Operation Deadline) and Section 3.2(A)(2) (Milestone Dates) of the Agreement) The availability statistics are used in this Agreement to track the Available Capacity relative to the Firm Capacity. Capacity cannot be measured on the basis of energy delivery as energy is controlled by the Company Dispatch and thus energy produced is not necessarily equal to the Available Capacity. The basis for the methodology are the definitions of EAF and EFOR in 2011 NERC GADS. For determination of the components of the calculation of EAF and EFOR, the unmodified 2010 NERC GADS methodology and definitions are to be utilized except that Forced Outage Hours, Equivalent Forced Derated Hours, Equivalent Planned Derated Hours, and Equivalent Unplanned Derated Hours will exclude hours where the derating or forced outage is the result of conditions identified as excluded from EAF and EFOR calculations in Section 3.2(D)(2) (Equivalent Availability Factor), Section 3.2(D)(3) (Equivalent Forced Outage Rate) Section 4.2(B) (Company System Problems) and Section 4.2(C) (Review by Seller). Where there is no definition provided here, the unmodified 2011 NERC GADS methodology and definitions should be utilized. For example, the determination as to whether outages and derations are considered Forced Outages and derations versus Planned Outages and derations shall be made in accordance with the NERC GADS guidelines. The intent of the following definitions and descriptions is meant to clarify application of the NERC methodology for this particular facility and incorporate the impact of excluding certain derations and outages due to Force Majeure and Company System Problems as described in Section 3.2(D)(2) (Equivalent Availability Factor), Section 3.2(D)(3) (Equivalent Forced Outage Rate) Section 4.2(B) (Company System Problems) and Section 4.2(C) (Review by Seller).

Reporting Milestones. Reporting Milestone Date Description of Each Reporting Milestone

Reporting Milestones