Changes in Performance Standards by PM Sample Clauses

Changes in Performance Standards by PM. PM, with the prior written approval of GMCBL, may change the Performance Standards either in general or in a particular case in case it is considered necessary to achieve the overall objectives set out in Clause 2.3 either to maximize utilization of regular passenger services or to achieve efficiency of resources allocated to regular passenger services.
AutoNDA by SimpleDocs

Related to Changes in Performance Standards by PM

  • Performance Standards The Contractor agrees to perform all tasks and provide deliverables as set forth in the Contract. The Department and the Customer will be entitled at all times, upon request, to be advised as to the status of work being done by the Contractor and of the details thereof.

  • 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.

  • Performance Standard Contractor shall perform all work hereunder in a manner consistent with the level of competency and standard of care normally observed by a person practicing in Contractor's profession. County has relied upon the professional ability and training of Contractor as a material inducement to enter into this Agreement. Contractor hereby agrees to provide all services under this Agreement in accordance with generally accepted professional practices and standards of care, as well as the requirements of applicable federal, state and local laws, it being understood that acceptance of Contractor’s work by County shall not operate as a waiver or release. If County determines that any of Contractor's work is not in accordance with such level of competency and standard of care, County, in its sole discretion, shall have the right to do any or all of the following: (a) require Contractor to meet with County to review the quality of the work and resolve matters of concern; (b) require Contractor to repeat the work at no additional charge until it is satisfactory; (c) terminate this Agreement pursuant to the provisions of Article 4; or (d) pursue any and all other remedies at law or in equity.

  • Performance Measures and Metrics This section outlines the performance measures and metrics upon which service under this SLA will be assessed. Shared Service Centers and Customers will negotiate the performance metric, frequency, customer and provider service responsibilities associated with each performance measure. Measurements of the Port of Seattle activities are critical to improving services and are the basis for cost recovery for services provided. The Port of Seattle and The Northwest Seaport Alliance have identified activities critical to meeting The NWSA’s business requirements and have agreed upon how these activities will be assessed.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Employee Performance Evaluations Any employee performance evaluation shall be prepared by the employee's supervisor who has the responsibility and authority to prepare such reports. Employee performance evaluation reports shall be discussed with the employee prior to finalization of each category of the report. An employee will receive an appointment with his/her department's reviewing officer to discuss the evaluation by signing the evaluation form in the space provided. Each department shall make a reasonable effort to ensure that the reviewing officer for this purpose has not been a party to the preparation of the evaluation. In no case shall the reviewing officer sign the evaluation form until a review has occurred. Any regular or special evaluation with a rating of "unsatisfactory" shall include plans for employee development. Except in cases of termination, release from probation, or leave of absence, employees who receive an unsatisfactory performance evaluation must receive a follow-up evaluation. The follow-up evaluation shall cover a period of time no greater than ninety (90) calendar days from the date of the final review of the initial unsatisfactory evaluation. An employee shall have the right to submit written comments regarding any evaluation and to have such comments included in his/her personnel file along with the evaluation.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Contractor Performance Evaluations The Contract Administrator will evaluate Contractor’s performance as often as the Contract Administrator deems necessary throughout the term of the contract. This evaluation will be based on criteria including the quality of goods or services, the timeliness of performance, and adherence to applicable laws, including prevailing wage and living wage. City will provide Contractors who receive an unsatisfactory rating with a copy of the evaluation and an opportunity to respond. City may consider final evaluations, including Contractor’s response, in evaluating future proposals and bids for contract award.

  • EMPLOYEE PERFORMANCE EVALUATION Purpose: To provide the policy and procedures for assessing employee performance and communicating the results of assessment to the employee and to others using assessment information in personnel decisions, and further to express the mutual commitment of the parties to the University’s values.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that:

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