Frequency of occurrence of performance failures Sample Clauses

Frequency of occurrence of performance failures. 9.3.1 The frequency of occurrence of performance failures, together with the risk ratings, will determine whether a financial abatement is to be: applied immediately or; a percentage of the Performance Linked Fee withheld or; nil financial abatement is to be applied.
AutoNDA by SimpleDocs

Related to Frequency of occurrence of performance failures

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Frequency of Evaluation Short form employees shall be evaluated one (1) time per year, which evaluation shall be completed no later than June 1.

  • Frequency of Evaluations 36.2.1 Employee work performance will be evaluated during probationary and trial service periods and annually thereafter. If the supervisor identifies a performance concern during the evaluation period, the supervisor may provide feedback. The supervisor will provide written documentation to the employee with a copy kept in the supervisor’s working file.

  • Subprojects 1. The Borrower shall make Grants to Beneficiaries (Small Farmers, Municipalities and Organizations) for Subprojects (Farmers’ Business Initiatives, Infrastructure Subprojects and Environmental Subprojects) in accordance with eligibility criteria and procedures acceptable to the Bank as further detailed in the Project Operational Manual.

  • No Default for Force Majeure Neither Party will be in default in the performance of any of its obligations set forth in this Agreement, except for obligations to pay money, when and to the extent failure of performance is caused by Force Majeure.

  • Uncontrollable Events BISYS assumes no responsibility hereunder, and shall not be liable for any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

  • Offense Level Calculations i. The base offense level is 7, pursuant to Guideline § 2B1.1(a)(1).

  • Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11:

  • Short Changeover Premium (a) If shifts are scheduled so that there are not twenty-four (24) hours between the start of an employee's shift and the start of his/her next shift, a premium calculated at the overtime rates will be paid for hours worked on the succeeding shift within the twenty-four (24) hour period.

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