Non-Escalation Unless otherwise specified within the RFP documents, the unit prices reflected on the contract shall remain firm with no provision for price increases during the term of the contract.
TERMINATION CLAUSE In the event Contractor fails to carry out or comply with any of the terms and conditions of this Agreement, Hastings reserves the right to demand correction of any breach or default within ten (10) calendar days of notice to Contractor. In the event Contractor fails to correct the failure or default within the specified ten (10) day period, Hastings may terminate the Agreement without additional notice. Failure to terminate this Agreement is not to be deemed a waiver of the breach or default. Upon termination, Hastings shall compensate Contractor for Work rendered within thirty (30) days of termination of this Agreement.
DURATION CLAUSE A. This Agreement shall govern the rights of the Board and the Association from July 1, 2021, through June 30, 2022. This Agreement shall not be extended orally and it is expressly understood that it shall expire on the date indicated.
Escalation Procedure Tentative Rates for those species and products listed in A4a are subject to quarterly escalation in accordance with the following pro- cedures: The calendar quarter index average for each price index described in A5 is the arithmetic average of the three such monthly price indices preceding January 1, April 1, July 1, and October 1. The difference between calendar quarter index average and Base Index listed in A4a shall be the basis for quarterly escalation. To arrive at Current Contract Rates for timber Scaled during the preceding calendar quarter, Tentative Rates for each species shall be reduced or increased by such difference, except when the calendar quarter index average is:
Escalation If parties are unable to resolve the issue in a timely manner, as specified above, either Sourcewell or Supplier may escalate the resolution of the issue to a higher level of management. The Supplier will have 30 calendar days to cure an outstanding issue.
Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.
Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.