Prompt Performance All actions required to be taken (including payments) by any party under this Agreement shall be performed within the time prescribed for performance in this Agreement, or if no period is prescribed, such actions shall be performed promptly.
Consideration for Performance The consideration to be paid to the Contractor under this Agreement will be compensation for all the Contractor’s expenses incurred in the performance of this Agreement, unless otherwise expressly provided.
Non-Performance The obligation of ECOLOGY to the RECIPIENT is contingent upon satisfactory performance by the RECIPIENT of all of its obligations under this Agreement. In the event the RECIPIENT unjustifiably fails, in the opinion of ECOLOGY, to perform any obligation required of it by this Agreement, ECOLOGY may refuse to pay any further funds, terminate in whole or in part this Agreement, and exercise any other rights under this Agreement. Despite the above, the RECIPIENT shall not be relieved of any liability to ECOLOGY for damages sustained by ECOLOGY and the State of Washington because of any breach of this Agreement by the RECIPIENT. ECOLOGY may withhold payments for the purpose of setoff until such time as the exact amount of damages due ECOLOGY from the RECIPIENT is determined.
CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.
Performance Management 17.1 The Contractor will appoint a suitable Account Manager to liaise with the Authority’s Strategic Contract Manager. Any/all changes to the terms and conditions of the Agreement will be agreed in writing between the Authority’s Strategic Contract Manager and the Contractor’s appointed representative.
17.2 The Contractor will ensure that there will be dedicated resources to enable the smooth running of the Framework Agreement and a clear plan of contacts at various levels within the Contractor's organisation. Framework Public Bodies may look to migrate to this Framework Agreement as and when their current contractual arrangements expire. The Contractor will where necessary assign additional personnel to this Framework Agreement to ensure agreed service levels are maintained and to ensure a consistent level of service is delivered to all Framework Public Bodies.
17.3 In addition to annual meetings with the Authority's Strategic Contract Manager, the Contractor is expected to develop relationships with nominated individuals within each of the Framework Public Bodies to ensure that the level of service provided on a local basis is satisfactory. Where specific problems are identified locally, the Contractor will attempt to resolve such problems with the nominated individual within that organisation. The Authority's Strategic Contract Manager will liaise (or meet as appropriate) regularly with the Framework Public Bodies' Contract Manager, and where common problems are identified, it will be the responsibility of the Contractor to liaise with the Authority's Strategic Contract Manager to agree a satisfactory course of action. Where the Contractor becomes aware of a trend that would have a negative effect on one or more of the Framework Public Bodies, they should immediately notify the Authority's Strategic Contract Manager to discuss corrective action.
17.4 Regular meetings, frequency to be advised by Framework Public Body, will be held between the Framework Public Bodies' Contract Manager and the Contractor's representative to review the performance of their Call-Off Contract(s) under this Framework Agreement against the agreed service levels as measured through Key Performance Indicators (KPIs). Reports will be provided by the Contractor to the Framework Public Bodies' Contract Manager at least 14 days prior to the these meetings.
17.5 Performance review meetings will also be held annually, between the Authority's Strategic Contract Manager and the Contractor's representative to review the performance of the Framework Agreement against the agreed service levels as measured through Key Performance Indicators. A summary of the quarterly reports will be provided by the Contractor at least 14 days prior to these meetings.
17.6 The Authority will gather the outputs from contract management to review under the areas detailed in the table below. Provision of management reports 90% to be submitted within 10 working days of the month end Report any incident affecting the delivery of the Service(s) to the Framework Public Body 100% to be reported in writing to FPB within 24 hours of the incident being reported by telephone/email Prompt payment of sub-contractors and/or consortia members (if applicable). Maximum of 30 from receipt of payment from Framework Public Bodies, 10 days target 100% within 30 days
Continuing Performance (a) The obligations under this Agreement continue until satisfied in full and do not merge with any action performed or document executed by any Party for the purposes of performance of this Agreement.
(b) Any representation in this Agreement survives the execution of any document for the purposes of, and continues after, performance of this Agreement.
(c) Any indemnity given by any Party under this Agreement:
(i) constitutes a liability of that Party separate and independent from any other liability of that Party under this Agreement or any other agreement; and
(ii) survives and continues after performance of this Agreement.
EVALUATING PERFORMANCE 7.1 The Performance Plan (Annexure A) to this Agreement sets out:
7.1.1 the standards and procedures for evaluating the Employee’s perfor- xxxxx; and
7.1.2 the intervals for the evaluation of the Employee’s performance.
7.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force.
7.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames.
7.4 The Employee’s performance will measured in terms of contributions to the goals and strategies set out in the Employer’s IDP.
7.5 The annual performance appraisal will involve:
7.5.1. Assessment of the achievement of results as outlined in the perfor- xxxxx plan:
(a) Each KPA should be assessed according to the extent to which the specified standards or performance indicators have been met and with due regard to ad hoc tasks that had to be performed under the KPA.
(b) An indicative rating on the five-point scale should be provided for each KPA.
(c) The applicable assessment rating calculator (refer to paragraph 7.5.3. below) must then be used to add the scores and calculate a final KPA score.
Employee Performance Review When a formal review of an employee’s performance is made, the employee concerned shall be given an opportunity to discuss, sign and make written comments on the review form in question and the employee is to receive a signed copy to indicate that its contents have been read. An employee shall be entitled to a minimum of two (2) work days to review the performance review prior to providing any response to the Employer, verbally or in writing, with respect to the evaluation.
Responsibility for Performance Participation in state Centralized Contracts by Authorized Users is permitted upon the following conditions: (i) the responsibility with regard to performance of any contractual obligation, covenant, condition or term thereunder by any Authorized User other than State Agencies shall be borne and is expressly assumed by such Authorized User and not by the State; (ii) a breach of the Contract by any particular Authorized User shall neither constitute nor be deemed a breach of the Contract as a whole which shall remain in full force and effect, and shall not affect the validity of the Contract nor the obligations of the Contractor thereunder respecting non-breaching Authorized Users, whether State or otherwise; (iii) for a breach by an Authorized User other than a State Agency, the State specifically and expressly disclaims any and all liability for such breach; and (iv) each non-state agency Authorized User and Contractor guarantees to save the State, its officers, agents and employees harmless from any liability that may be or is imposed by their failure to perform in accordance with its obligations under the Contract.
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.
