FORCED OUTAGE REPORTING Sample Clauses

FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify PG&E Merchant Generation desk verbally at (000) 000-0000 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 Xxxxx_Xxxxxxxxxxx@xxx.xxx. 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:
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
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.
Sample 1Sample 2Sample 3See All (9)
FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify PG&E merchant generation desk verbally at (000) 000-0000 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 Xxxxx_Xxxxxxxxxxx@xxx.xxx. 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:
Sample 1Sample 2Sample 3See All (7)
FORCED OUTAGE REPORTING. For Forced Outages immediately impacting availability, or impacting availability during the next forty-eight (48) hours:
Sample 1Sample 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.
Sample 1
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. APPENDIX VII FORM OF CONSENT TO ASSIGNMENT CONSENT AND AGREEMENT 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”.
Sample 1
FORCED OUTAGE REPORTING. Forced Outages – Seller shall notify PG&E Merchant Generation desk verbally within 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 electronic website “PPIC”. If the “PPIC website is unavailable, submit the following information via email to Xxxxx_Xxxxxxxxxxx@xxx.xxx. Email subject Field: dd/mm/yyyy through dd/mm/yyyy XYZ Company Project #2 Outage Notification Email body:
Sample 1
AutoNDA by SimpleDocs
FORCED OUTAGE REPORTING 
Sample 1Sample 2Sample 3See All (5)

Related to FORCED OUTAGE REPORTING

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

  • Management Reporting (a) Provide periodic reports, in accordance with agreed upon frequency and content parameters, to the Funds. As reasonably requested by the Funds, the Transfer Agent shall furnish ad hoc reports to the Funds.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Performance Reporting The State of California is required to submit the following financial reports to FEMA:

  • IRS Reporting Ultimus will prepare and distribute appropriate Internal Revenue Service (“IRS”) forms for shareholder income and capital gains (including the calculation of qualified income), sale of fund shares, distributions from retirement accounts and education savings accounts, fair market value reporting on IRAs, contributions, rollovers and conversions to IRAs and education savings accounts and required minimum distribution notifications and issue tax withholding reports to the IRS.

  • Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event.

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following:

  • IRS Real Estate Sales Reporting Buyer and Seller agree that Escrow Agent shall act as “the person responsible for closing” the transaction which is the subject of this Agreement pursuant to Section 6045(e) of the Code and shall prepare and file all informational returns, including without limitation, IRS Form 1099-S, and shall otherwise comply with the provisions of Section 6045(e) of the Code.

  • Uncontrollable Events BISYS assumes no responsibility hereunder, and shall not be liable for any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control.

  • Rule 144 Reporting With a view to making available to the Holders the benefits of certain rules and regulations of the SEC which may permit the sale of the Registrable Securities to the public without registration, the Company agrees to use its best efforts to:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!