Schedule 16 (Change Protocol Sample Clauses

Schedule 16 (Change Protocol in the case of a Delay Event referred to in Clause 30.3.1 (Delay Events and Compensation Events ) (subject always to the provisions of Clause 33 (Changes in Law)); or
AutoNDA by SimpleDocs

Related to Schedule 16 (Change Protocol

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

  • Selection Criteria for Awarding Task Order The Government will award to the offeror whose proposal is deemed most advantageous to the Government based upon an integrated assessment using the evaluation criteria. The Government will evaluate proposals against established selection criteria specified in the task order RFP. Generally, the Government's award decision will be based on selection criteria which addresses past performance, technical acceptability, proposal risk and cost. Among other sources, evaluation of past performance may be based on past performance assessments provided by TO Program Managers on individual task orders performed throughout the life of the contract. The order of importance for the factors will be identified in the RFP for the specified task order.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

  • Milestone schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.

  • Table 7b - Other milestones and targets Reference Number Select stage of the lifecycle Please select target type from the drop-down menu Description (500 characters maximum) Is this a collaborative target? Baseline year Baseline data Yearly milestones (numeric where possible, however you may use text) Commentary on your milestones/targets or textual description where numerical description is not appropriate (500 characters maximum)

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • CHANGE IN CLASSIFICATION SPECIFICATIONS Section 1. The Employer shall notify the Union of intended classification studies.

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

  • Salary Schedule Progression Employees shall progress from step to step in salary grade on the basis of satisfactory job performance based upon established standards of performance. Seasonal employee's initial anniversary date shall be established after being in pay status for two thousand eighty (2,080) hours. Such date shall then be used for annual performance evaluation and step progression consideration. When an employee's anniversary date falls on any day from the first day of a pay week through Wednesday of the pay week, the employee's merit increase shall be effective as of the first day of the pay week within which the anniversary date falls. Otherwise, the merit increase shall be effective on the first day of the next pay week. Grievances arising from the denial of merit increases shall not be arbitrable under this Agreement but shall be processed as follows:

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