PERIOD OF PERFORMANCE/EFFECTIVE DATE Sample Clauses

PERIOD OF PERFORMANCE/EFFECTIVE DATE. All work under this Task Order is to be performed from the effective date, which is the date of last signature through , unless changed by a duly executed Modification or terminated in accordance with the provisions of this Task Order or above-referenced Base Task Order Agreement.
AutoNDA by SimpleDocs
PERIOD OF PERFORMANCE/EFFECTIVE DATE. The period of performance for this Agreement is from the effective date, which is the date of the last signature through August 18, 2019, unless amended by a duly executed Amendment or terminated in accordance with the provisions of this Agreement. Any extension of this performance period requires the Contractor's written approval. Task Orders will contain their own start and end dates.

Related to PERIOD OF PERFORMANCE/EFFECTIVE DATE

  • PERIOD OF PERFORMANCE The period of performance for this contract begins , and ends . ARTICLE 4.

  • TASK ORDER PERIOD OF PERFORMANCE ‌ The period of performance for each Order placed under the Master Contract shall be specified in the individual Order. All the following conditions apply:

  • CONTINUATION OF PERFORMANCE THROUGH TERMINATION The Subrecipient shall continue to perform, in accordance with the requirements of the Agreement, up to the date of termination, as directed in the termination notice.

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

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

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

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

  • Availability of Performance Order If, and to the extent that, a breach of this contract has been caused by a Relevant Force Majeure Event, the Non-affected Party shall not be entitled to a Performance Order except to secure performance by the Affected Party of its obligations under this Clause 17.

  • Acceptance/Performance Test 4.7.1 Prior to synchronization of the Power Project, the SPD shall be required to get the Project certified for the requisite acceptance/performance test as may be laid down by Central Electricity Authority or an agency identified by the central government to carry out testing and certification for the solar power projects.

  • Performance Schedule The Parties will perform their respective responsibilities in accordance with the Performance Schedule. By executing this Agreement, Customer authorizes Motorola to proceed with contract performance.

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