Outage Report Clause Samples

The Outage Report clause requires one party, typically a service provider, to formally notify the other party about any service interruptions or outages. In practice, this clause outlines the process for reporting outages, including the timeframe for notification, the information that must be included in the report (such as the cause and expected resolution time), and the method of communication. Its core function is to ensure transparency and timely communication during service disruptions, enabling the affected party to respond appropriately and manage any resulting impacts.
Outage Report. Within five (5) Business Days after the end of the month, Seller shall prepare, maintain and deliver to PGE a schedule that identifies all Planned Outages, Unplanned Outages, and deratings that occurred during the month. The data reported must meet all requirements specified in the NERC Generating Availability Data System (GADS) manual. In the event of any disagreement between PGE and Seller concerning the schedule prepared by Seller, the Parties shall promptly confer to resolve the disagreement.
Outage Report. 5.1 To request a Credit Note from DCLUX, the Customer shall send an email detailing the outage or the Virtual Private Server Service interruption to ▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇.▇▇ (“the Outage Report”). In any cases where the Outage Report will be considered as valid by DCLUX, the Customer will be granted the applicable Credits in the form of a discount to be applied on its next invoice following the monthly period during which the Outage occurred. The Customer understands and agrees that Outage Reports shall be made in good faith and warrants therefore that they will abstain from making inaccurate report. The Customer further agrees that DCLUX may levy an hundred (100) euros fee for any inaccurate Outage Report made by the Customer. 5.2 In order to be considered by DCLUX, an Outage Report shall be sent within thirty (30) days following the outage and bare the following information: • Reference of the Ticket opened with DCLUX Support service • Virtual Private Server affected • Name of the Customer’s representative who has contacted DCLUX support service
Outage Report. Within five (5) Business Days after the end of the month, Seller shall prepare, maintain and deliver to Buyer a schedule that identifies all Planned Outages, Unplanned Outages, and deratings that occurred during the month. The data reported must meet all requirements specified in the NERC Generating Availability Data System (GADS) manual. In the event of any disagreement between Buyer and Seller concerning the schedule prepared by Seller, the Parties shall promptly confer to resolve the disagreement.
Outage Report. 5.1 To request a Credit Note from MIXvoip, the Customer shall send an email detailing the outage to ▇▇▇▇▇▇▇@▇▇▇▇▇▇▇.▇▇▇ (“the Outage Report”). In any cases where the Outage Report will be considered as valid by MIXvoip, the Customer will be granted the applicable Credits in the form of a discount to be applied on its next invoice following the monthly period during which the Outage occurred. The Customer understands and agrees that Outage Reports shall be made in good faith and warrants therefore that they will abstain from making inaccurate report. The Customer further agrees that MIXvoip may levy an hundred (100) euros fee for any inaccurate Outage Report made by the Customer. 5.2 In order to be considered by MIXvoip, an Outage Report shall be sent within thirty (30) days following the outage and bare the following information: - Reference of the Ticket opened with MIXvoip Support service - Virtual Private Server affected - Name of the Customer’s representative who has contacted MIXvoip support service

Related to Outage Report

  • Usage Reports The Contractor shall submit usage reports on an annual basis to the assigned Deputy Purchasing Agent of the County of Orange user agency/department. The usage report shall be in a format specified by the user agency/department and shall be submitted 90 days prior to the expiration date of the contract term, or any subsequent renewal term, if applicable.

  • Progress Report By March 1 of each year, ***** will submit a written annual report to Stanford covering the preceding calendar year. The report will include information sufficient to enable Stanford to satisfy reporting requirements of the U.S. Government and for Stanford to ascertain progress by ***** toward meeting this Agreement’s diligence requirements. Each report will describe, where relevant: *****’s progress toward commercialization of Licensed Product, including work completed, key scientific discoveries, summary of work-in-progress, current schedule of anticipated events or milestones, market plans for introduction of Licensed Product, and significant corporate transactions involving Licensed Product. ***** will specifically describe how each Licensed Product is related to each Licensed Patent.

  • Problem Statement School bus fleets are aging, and our communities have poor air quality. Replacing school buses with zero emission school buses will address both of these issues.

  • Engineering Report Lender shall have received a current Engineering Report with respect to the Property, which report shall be in form and substance reasonably satisfactory to Lender.

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.