FORCED OUTAGE REPORTING Clause Samples

The Forced Outage Reporting clause requires parties to promptly notify each other when an unexpected interruption or failure occurs in equipment or facilities that affects performance under the agreement. Typically, this involves providing details about the nature, cause, and expected duration of the outage, as well as any steps being taken to resolve the issue. The core function of this clause is to ensure transparency and timely communication, enabling both parties to manage operational risks and coordinate responses to minimize disruption.
FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify PG&E Merchant Generation desk verbally at (▇▇▇) ▇▇▇-▇▇▇▇ within ten (10) minutes of event or as soon as reasonably possible, after the safety of all personnel and securing of all facility equipment. Verbal notification shall include time of forced outage, cause, current availability and estimated return date and time. After verbally notifying PG&E Merchant Generation desk of the forced outage, Seller shall also put forth commercially reasonable efforts to notify PG&E Settlements via PG&E’s Website, as defined above. If PG&E’s Website is unavailable, submit the following information via email to ▇▇▇▇▇_▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇▇.
View SourceView Similar (16)
FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify PG&E merchant generation desk verbally at (▇▇▇) ▇▇▇-▇▇▇▇ within ten (10) minutes of event or as soon as reasonably possible, after the safety of all personnel and securing of all facility equipment. Seller will be responsible for reporting the following information when reporting Forced Outages to the PG&E merchant generation desk: Operator Name Specific Issue: outage or derate due to XXX. Total Plant Availability: the current MW value the plant can generate. Estimated Time of Return (“ETR”): Date (MMDDYYY) and time (HH:MM) in 24H format. After verbally notifying PG&E Merchant Generation desk of the forced outage, submit the following information via email to ▇▇▇▇▇_▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇▇.
View SourceView Similar (7)
FORCED OUTAGE REPORTING. I. Forced Outages - Seller shall notify PG&E Merchant Generation desk verbally within 10 minutes of event or as soon as reasonably possible, after ensuring the safety of all personnel and securing of all facility equipment. a. Verbal notification shall include time offorced Outage, cause, current availability and estimated return date and time. b. After verbally notifying PG&E Merchant Generation desk of the forced Outage, Seller shall also make commercially reasonable efforts to notify PG&E Settlements via PG&E's electronic website "PPIC". c. If the "PPIC website is unavailable, submit the following information via email to Bi1at_Sett ▇▇▇▇▇▇▇@▇▇▇.▇▇▇. i. Email subject Field: dd/mm/yyyy through dd/mm/yyyy XYZ Company Project #2 Outage Notification Ii. Email body:
View SourceView Similar (4)
FORCED OUTAGE REPORTING. Forced Outages - Seller shall notify PG&E Merchant Generation desk verbally \vithin 10 minutes of event or as soon as reasonably possible, after ensuring the satery of all personnel and securing of all facility equipment. a. Verbal notification shall Illc!ude time of forced Outage. cause, current availabi lity and estimated return date and time. b. After verbally notifying PG&E Merchant Generation desk of the forced Outage. Seller shall also make commercially reasonable etforts to notify PG&E Settlements via PG&E·s electronic website ·'PPIC". c. If the ·'PPIC website is unavailable, submit the follo.Wlllg mformation via emall to Bilat - ▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇▇. i. Entail mbject Field: ddimm/yyyy t/troug/t dd/mm/YYJY XYZ Compuny Project #2 Outage Notification
View SourceView Similar (4)
FORCED OUTAGE REPORTING. For Forced Outages immediately impacting availability, or impacting availability during the next forty-eight (48) hours:
View SourceView Similar (2)
FORCED OUTAGE REPORTING. SELLER shall notify PECO's System Operations Group of the occurrence, nature and expected duration of any forced outage as soon as practical but not later than one (1) hour after the forced outage begins. SELLER shall thereafter promptly inform PECO's System Operations Croup of any change in the expected duration of the forced outage unless relieved of this obligation by PECO's System Operations Group for the duration of that forced outage.
View SourceView Similar (2)
FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify TEA’s Real Time Desk verbally at insert information here within ten (10) minutes of event or as soon as reasonably possible, after the safety of all personnel and securing of all facility equipment. Verbal notification shall include time of forced outage, cause, current availability and estimated return date and time. After verbally notifying TEA’s Real Time Desk of the forced outage, Seller shall also submit the following information via email to insert information here. Email subject field: Company Name, Contract Name, Email Purpose, Date Range (For example: “dd/mm/yyyy through dd/mm/yyyy, XYZ Company Project #2, Daily Forecast of Available Capacity”) Email body: Type of Outage: Forced Outage Start Date and Start Time Estimated or Actual End Date and End Time Date and time when reported to TEA and name(s) of TEA representative(s) contacted. Text description of additional information as needed. Primary and secondary causes of Forced Outage, including a detailed description of specific equipment involved and the nature of the problem or condition. Equipment description and nature of work being performed. For generation outages, include NERC Generation Availability Data System (GADS) numbers (as available) that identify the specific equipment and type of work that affect restrictions. Include additional equipment designations as available. Text description of additional information as needed, including, but not limited to, changes to a previously scheduled Outage, links/cross-references to related outage cards and log entries, outage classifications per the CAISO Tariff, etc. Associated events, e.g. operation of Special Protection Schemes. Impact on CAISO-controlled Grid. This CONSENT AND AGREEMENT (“Consent and Agreement”) is entered into as of [_______ __, 2___], between REDWOOD COAST ENERGY AUTHORITY (“RCEA”), and [_________________] , as collateral agent (in such capacity, “Financing Provider”), for the benefit of various financial institutions (collectively, the “Secured Parties”) providing financing to [_______] (“Seller”). RCEA, Seller, and the Financing Provider shall each individually be referred to as a “Party” and collectively as the “Parties”.
View Source
FORCED OUTAGE REPORTING. I. Forced Outages - Seller shall notify PG&E Merchant Generation desk verbally within 10 minutes of event or as soon as reasonably possible, after ensuring the safety of all personnel and securing of all facility equipment. a. Verbal notification shall include time afforced Outage, cause, current availability and estimated return date and time. b. After verbally notifying PG&E Merchant Generation desk of the forced Outage, Seller shall also make commercially reasonable efforts to notify PG&E Settlements via PG&E's electronic website "PPIC".
View Source
FORCED OUTAGE REPORTING 
View SourceView Similar (5)

Related to FORCED OUTAGE REPORTING

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will ▇▇▇▇ ▇▇▇▇▇▇▇ Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at ▇▇▇▇▇▇▇▇▇▇@▇▇▇▇-▇▇▇.▇▇▇. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.

  • Progress Reporting a) RECIPIENT must satisfactorily demonstrate the timely use of funds by submitting payment requests and progress reports to ECOLOGY. ECOLOGY reserves the right to amend or terminate this Agreement if the RECIPIENT does not document timely use of funds. b) RECIPIENT must submit a progress report with each payment request. Payment requests will not be processed without a progress report. ECOLOGY will define the elements and frequency of progress reports. c) RECIPIENT shall use ECOLOGY’s provided progress report format. d) Quarterly progress reports will cover the periods from January 1 through March 31, April 1 through June 30, July 1 through September 30, and October 1 through December 31. Reports shall be submitted within thirty (30) days after the end of the quarter being reported. e) RECIPIENT must submit within thirty (30) days of the expiration date of the project, unless an extension has been approved by ECOLOGY, all financial, performance, and other reports required by the Agreement and funding program guidelines. RECIPIENT shall use the ECOLOGY provided closeout report format.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • CONTRACT SALES REPORTING Contractor shall report total Contract sales quarterly to Enterprise Services, as set forth below. (a) Contract Sales Reporting System. Contractor shall report quarterly Contract sales in Enterprise Services’ Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. (b) Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Contract. If there are no Contract sales during the reporting period, Contractor must report zero sales. (c) Due dates for Contract Sales Reporting. Quarterly Contract Sales Reports must be submitted electronically by the following deadlines for all Contract sales invoiced during the applicable calendar quarter: Quarter For Sales Made In Calendar Quarter Ending Contract Sales Report