Technical Failures Sample Clauses

Technical Failures. 26.1. The Company, with all its available resources, will prevent any possible malfunctioning in the site. However, the Company does not guarantee that the site will be free from technical failures glitches, and/or malfunctions during the course of this Agreement.
AutoNDA by SimpleDocs
Technical Failures. The Camera Operator takes no responsibility for the failure of equipment if operated correctly. Failing/corrupt media, overheating equipment, dropped frames etc. are examples of such failures. Although rare, technical failures do occur and is considered out of the Camera Operator’s control. If you have any questions about the information in this document, please contact Jaco: 000 000 0000 / Wimpie: 083 717 3356 / xxxx@xxxxxxxxxxxxxxx.xx.xx
Technical Failures. Notwithstanding anything to the contrary in this Agreement, Provider shall use the technology tools that Google provides with respect to restrictions and limitations on the exhibition of Provider Content, and Google shall be responsible for any failures, breaks or flaws of such technology tools.
Technical Failures. From and after the Commencement Date, in the event that the Transmission Facilities suffer an unexpected failure, such that the Sharee’s Station must temporarily cease broadcasting or operate at reduced power levels, Sharer shall promptly notify Xxxxxx and use commercially reasonable efforts, consistent with past practices, to repair the Transmission Facilities to return the Sharee’s Station, as quickly as practicable, to operations at its full authorized power subject to any restrictions contained in the Transmission Facilities Lease.
Technical Failures. From and after the Commencement Date, in the event that the Transmission Facilities suffer an unexpected failure, such that the Sharee’s Station must temporarily cease broadcasting or operate at reduced power levels, Sharer sha... (e)
Technical Failures. It is possible that you may face disruptions, including, but not limited to errors, disconnections or interferences in communication in the internet services, software or hardware that you have used to avail our services. Trell is not responsible for such factors in the disruption or interruption in the services and you take full responsibility with complete knowledge for any risk of loss or damages caused due to interruption of services for any such reasons.

Related to Technical Failures

  • Epidemic Failure Warranty Supplier warrants all Products against Epidemic Failure for a period of three years after DXC’s Acceptance. Epidemic Failure means the occurrence of the same failure, defect, or non-conformity with an Order in 2% or more of Products within any three-month period.

  • Mechanical Breakdowns 15.1 Any mechanical problems associated with the Vehicle must be reported to Apollo as soon as possible in order to give Apollo the opportunity to rectify the problem during the rental period. Equipment failure must also be reported to Apollo.

  • Power Failure Power Failure means the failure of power or other utility service if the failure takes place off the "residence premises". But if the failure results in a loss, from a Peril Insured Against on the "residence premises", we will pay for the loss caused by that peril.

  • Safety, breakdowns and accidents 17.5.1 The Concessionaire shall ensure safe conditions for the Users and passengers, and in the event of unsafe conditions, it shall follow the relevant operating procedures and undertake removal of obstruction and debris without delay. Such procedures shall conform to the provisions of this Agreement, Applicable Laws, Applicable Permits and Good Industry Practice.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Critical Illness Three (3) days per year, with pay, shall be granted in the case of a critical illness or accident to a member of the employee's immediate family as defined in Section 9.4.2. A statement by the physician verifying the need for the employee to be present with the immediate family member shall be attached to the absence form.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Failure to Achieve Commercial Operation If the Large Generating Facility fails to achieve Commercial Operation, but it or another generating facility is later constructed and makes use of the Network Upgrades, the Participating TO shall at that time reimburse Interconnection Customer for the amounts advanced for the Network Upgrades. Before any such reimbursement can occur, the Interconnection Customer, or the entity that ultimately constructs the generating facility, if different, is responsible for identifying and demonstrating to the Participating TO the appropriate entity to which reimbursement must be made in order to implement the intent of this reimbursement obligation.

  • Force Majeure Failure Buyer shall have the right, but not the obligation, to terminate this Agreement after the occurrence of the following:

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

Time is Money Join Law Insider Premium to draft better contracts faster.