Time to Submit the Baseline Performance Schedule Sample Clauses

Time to Submit the Baseline Performance Schedule. The Buyer shall prepare and submit to the Contracting Officer a finalized baseline performance schedule within seven (7) days after the Contract start date. The baseline performance schedule shall incorporate the latest revisions to all tasks and shall take into account all other work in the Buyer's facility or scheduled to arrive at the facility that directly impacts the Obsolete Vessel performance schedule. The Buyer shall include a narrative report addressing all constraints to the Obsolete Vessel performance schedule incurred as a direct result of all other work in the Buyer's facility. Upon acceptance of the finalized baseline schedule by the Contracting Officer the Buyer shall manage the project under this schedule. The baseline schedule shall be used for the development of the required reports, progressing methodology and determining progress payments if necessary. The baseline schedule shall not be altered or changed during the performance period.
AutoNDA by SimpleDocs

Related to Time to Submit the Baseline Performance Schedule

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

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

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

  • Annual Performance Review The Employee’s performance of his duties under this Agreement shall be reviewed by the Board of Directors or a committee of the Board of Directors at least annually and finalized within thirty (30) days of the receipt of the annual audited financial statements. The Board of Directors or a committee of the Board of Directors shall additionally review the base salary, bonus and benefits provided to the Employee under this Agreement and may, in their discretion, adjust the same, as outlined in Addendum B of this Agreement, provided, however, that Employee’s annual base salary shall not be less than the base salary set forth in Section 4(A) hereof.

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

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

  • SCHEDULE FOR PERFORMANCE REVIEWS 8.1 The performance of each Employee in relation to his/her performance agreement shall be reviewed on the following dates with the understanding that reviews in the first and third quarter may be verbal if performance is satisfactory:

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

  • Annual Performance Evaluation On either a fiscal year or calendar year basis, (consistently applied from year to year), the Bank shall conduct an annual evaluation of Executive’s performance. The annual performance evaluation proceedings shall be included in the minutes of the Board meeting that next follows such annual performance review.

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

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