Calculation of Time to Restore performance Sample Clauses

Calculation of Time to Restore performance. The Time to Restore Service Level shall be measured on a per Priority basis. The Time to Restore Service Level target is calculated as follows: Time to Restore = (X / Y), where: X = is the total combined downtime of all Incidents relating to Services in table 1, measured on a per priority basis, logged on the Service Provider’s Incident management system and restored during the measured month, and Y = is the number of Incidents applicable to such measured priority relating to Services in table 1, logged on the Service Provider’s Incident management system and restored during the measured month.
AutoNDA by SimpleDocs

Related to Calculation of Time to Restore performance

  • Appropriation of Performance Security (i) Upon occurrence of a Contractor’s Default, the Authority shall, without prejudice to its other rights and remedies hereunder or in law, be entitled to encash and appropriate the relevant amounts from the Performance Security as Damages for such Contractor’s Default. (ii) Upon such encashment and appropriation from the Performance Security, the Contractor shall, within 30 (thirty) days thereof, replenish, in case of partial appropriation, to its original level the Performance Security, and in case of appropriation of the entire Performance Security provide a fresh Performance Security, as the case may be, and the Contractor shall, within the time so granted, replenish or furnish fresh Performance Security as aforesaid failing which the Authority shall be entitled to terminate the Agreement in accordance with Article 23. Upon replenishment or furnishing of a fresh Performance Security, as the case may be, as aforesaid, the Contractor shall be entitled to an additional Cure Period of 30 (thirty) days for remedying the Contractor’s Default, and in the event of the Contractor not curing its default within such Cure Period, the Authority shall be entitled to encash and appropriate such Performance Security as Damages, and to terminate this Agreement in accordance with Article 23.

  • Excuse from performance of obligations If the Affected Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Event, it shall be excused from performance of such of its obligations to the extent it is unable to perform on account of such Force Majeure Event; provided that: (a) the suspension of performance shall be of no greater scope and of no longer duration than is reasonably required by the Force Majeure Event; (b) the Affected Party shall make all reasonable efforts to mitigate or limit damage to the other Party arising out of or as a result of the existence or occurrence of such Force Majeure Event and to cure the same with due diligence; and (c) when the Affected Party is able to resume performance of its obligations under this Agreement, it shall give to the other Party notice to that effect and shall promptly resume performance of its obligations hereunder.

  • Prohibition of Performance Requirements 1. The provisions of the Agreement on Trade-Related Investment Measures in Annex 1A to the WTO Agreement (TRIMs), which are not specifically mentioned in or modified by this Agreement, shall apply, mutatis mutandis, to this Agreement. 2. Member States shall undertake joint assessment on performance requirements no later than 2 years from the date of entry into force of this Agreement. The aim of such assessment shall include reviewing existing performance requirements and considering the need for additional commitments under this Article.

  • Excuse of Performance Seller shall not be liable for delays in performance or for non-performance due to failure or interruption of computer or telecommunication systems, acts of God, war, riot, fire, terrorism, labor trouble, unavailability of materials or components, explosion, accident, compliance with governmental requests, laws, regulations, orders or actions, or other unforeseen circumstances or causes beyond Seller's reasonable control. In the event of such delay, the time for performance or delivery shall be extended by a period of time reasonably necessary to overcome the effect of the delay.

  • Time for Performance The term of this SOW Agreement shall begin on and end on _ (the “Initial Term”). The Initial Term may be extended as the parties may agree. The State may terminate this SOW for convenience upon thirty days prior written notice to the Contractor. If the Master Agreement should expire or otherwise terminate prior to the end of the term of this SOW Agreement, this SOW Agreement shall continue to the end of its existing term, unless or until terminated in accordance with the terms of this SOW Agreement, and the Parties acknowledge and agree that the terms of the Master Agreement shall survive and apply to this SOW Agreement.

  • Suspension of Performance Notwithstanding any other provision hereof, if an Event of Default or a Potential Event of Default has occurred and is continuing, the Non-Defaulting Party, upon written notice to the Defaulting Party, has the right (i) to suspend performance under any or all Transactions and (ii) to the extent an Event of Default has occurred and is continuing, to exercise any remedy available at law or in equity, except as limited be Section 5.7.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Limitations of Performance The Custodian shall not be responsible under this Agreement for any failure to perform its duties, and shall not be liable hereunder for any loss or damage in association with such failure to perform, for or in consequence of the following causes:

  • Commencement of Performance This Agreement is of no force and effect until signed by both parties and all JBE-required approvals are secured. Any commencement of performance prior to Agreement approval shall be at Contractor's own risk.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that: (i) Each and all of the services shall be performed in a timely, diligent, professional and skillful manner, in accordance with the highest professional or technical standards applicable to such services, by qualified persons with the technical skills, training and experience to perform such services in the planned environment. (ii) Any time software is delivered to the State, whether delivered via electronic media or the internet, no portion of such software or the media upon which it is stored or delivered will have any type of software routine or other element which is designed to facilitate unauthorized access to or intrusion upon; or unrequested disabling or erasure of; or unauthorized interference with the operation of any hardware, software, data or peripheral equipment of or utilized by the State. Without limiting the generality of the foregoing, if the State believes that harmful code may be present in any software delivered hereunder, Contractor will, upon State’s request, provide a new or clean install of the software. Notwithstanding the foregoing, Contractor assumes no responsibility for the State’s negligence or failure to protect data from viruses, or any unintended modification, destruction or disclosure. (iii) To the extent Contractor resells commercial hardware or software it purchased from a third party, Contractor will, to the extent it is legally able to do so, pass through any such third party warranties to the State and will reasonably cooperate in enforcing them. Such warranty pass-through will not relieve the Contractor from Contractor’s warranty obligations set forth herein.

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