Failures. The execution and implementation of this Agreement by the Buyer and the execution of its obligations as per this Agreement do not represent a violation or disruption, nor are they in conflict with, or make omission by any law, rule or regulation of any government authority or court, i.e. the provisions or regulations on partnership, or the Statute of the Buyer, i.e. any agreement, license, or any other act, written or oral, with the Buyer being one of the parties involved.
Failures. 2.11.1. An "ALKS failure" is any single failure specific to the operation of the ALKS (e.g. single sensor failure, loss of necessary calculation data for the driving path of the vehicle).
Failures. Failures of street cuts made under this agreement will be the responsibility of the City and be repaired at no cost to the Authority unless the failure is caused by a street subsurface failure, which will be repaired by the Authority at its cost.
Failures. In the event of any problem with the Network or the Connectivity Services or any failure of the Network or the Connectivity Services to perform in accordance with the Specifications (each a "Failure"), the Network Service Provider shall remedy the Failure within the time period provided for such Failure (depending on its severity) in the Specifications(the "Failure Resolution Time"). In the event of any Failure, the Network Service Provider shall further follow the incident management and escalation procedure more specifically described in Section 3.3 of the Technical Requirements. The Network Service Provider shall perform its obligations under this Article 6.6 irrespective of whether the Failure was reported to it by the Eurosystem or a Di.Co.A. or was detected by the Network Service Provider as a result of its monitoring of the Network and the Connectivity Services.
Failures. Arista is not liable or responsible for any failure resulting from Customer’s breach or negligence. At minimum, the Customer is obligated to ensure the following environmental failures do not impact MNDR Services. • Customer’s failure to adhere to Arista recommended configurations on the technology used to support the MDNR Service. • Customer’s use of the Products to screen more traffic than Customer originally purchased a license for as reflected in the order confirmation. • Customer’s failure to host the Products in a secure environment on-premise or in a remote facility assigned to the Customer, including appropriate mounting, cooling, theft, audit trails and wiring of the Hardware. • Service disruption or degradation failures caused by other Customer equipment, routing or firewall configurations, and telecommunications failures. • Service disruption or degradation failures caused by Customer configurations of Product in a manner that does not conform to the Documentation. • Changes to the Product resulting in degradation or failure without reasonable prior notification. • Customer’s failure to ensure the appropriate level of business continuity and disaster recovery as required for the MNDR Service.
Failures. Arista is not liable or responsible for any failure resulting from Customer’s breach of this Agreement or negligence. At minimum, the Customer is obligated to ensure the following environmental failures do not impact the operation of the Awake Security Platform: • Customer’s failure to adhere to Arista recommended configurations. • Customer’s use of the Products to screen more traffic than Customer originally purchased a license for as reflected in the order confirmation (“Excess Data”). • Customer’s failure to host the Products in a secure environment on-premise or in a remote facility assigned to the Customer, including appropriate mounting, cooling, theft, audit trails and wiring of the related Hardware. • Service disruption or degradation failures caused by other Customer equipment, routing or firewall configurations, and telecommunications failures. • Service disruption or degradation failures caused by Customer configurations of Product in a manner that does not conform to the Documentation or Specifications. • Changes to the Product resulting in degradation or failure without reasonable prior notification and written approval. Appendix B to AWAKE SECURITY SERVICES EXHIBIT FORM OF STATEMENT OF WORK Statement of Work Under Master Services Agreement This Statement of Work No. (this “Statement of Work”) is entered into between the Arista entity identified below on behalf of itself and its Affiliates (“Arista”) and the customer specified in the table below (“Customer”) and is effective as of the date of the last signature below (“SOW# Effective Date”). This Statement of Work is incorporated into, governed by and made a part of the Master Services Agreement dated by and between Arista and Customer (“Agreement”). Capitalized terms not defined herein have the same meanings set forth in the Agreement. In the event of a conflict between the terms of this SOW and the terms of the Agreement, the terms of this SOW shall prevail for this SOW only.
Failures. A student who fails a subject for the year must repeat and pass the subject in summer school or through private tutoring with an instructor certified in that subject area. Failure in summer school will necessitate automatic dismissal. The administration reserves the right to ask a student to withdraw from the school under the following circumstances related to failures:
Failures. Drug Substance not meeting the specifications established in the MPR will be handled as a failure and documented as such based on CBSB’s standard operating procedures. Actions taken to investigate the failure and to justify the CBSB’s Quality Review and Approval of the Batch of Drug Substance must be fully documented. The ICAR will be approved by both CBSB and Tercica as stated below. The approved ICAR will become part of the Batch Record for that specific Batch of Drug Substance. Any resulting corrective and preventative actions shall be followed through timely closure. Approval by the appropriate QA functions will be solicited and may be obtained via facsimile copy. Failure
Failures. Silver Spring will not be liable for failure to meet applicable Service Levels to the extent any such failure is attributable to any one or more of the following causes:
Failures. Instances of failures exceeding the failure criteria set forth in the TxDOT PMIS Rater’s Manual, including potholes, base failures, punchouts and jointed concrete pavement failures
