ORIGINAL EFFECTIVE AND EXPIRATION Sample Clauses

ORIGINAL EFFECTIVE AND EXPIRATION. DATES OF THE MATCH: Effective Date: November 28, 2020 Expiration Date: May 28, 2022
Sample 1See All (5)
AutoNDA by SimpleDocs
ORIGINAL EFFECTIVE AND EXPIRATION. DATES OF THE MATCH Effective Date: November 25, 2019 Expiration Date: May 24, 2021 V. RENEWAL AND NEW EXPIRATION DATES Renewal Date: May 25, 2021 New Expiration Date: May 24, 2022
Sample 1Sample 2See All (4)
ORIGINAL EFFECTIVE AND EXPIRATION. DATES OF THE MATCH Effective Date: May 31, 2021 Expiration Date: November 30, 2022 The above effective and expiration dates are based on Article XV of the CMA (“Duration and Modification of the Agreement”), paragraphs A (“Effective Date”) and B (“Duration”).
Sample 1
ORIGINAL EFFECTIVE AND EXPIRATION. DATES OF THE MATCHING PROGRAM Effective Date: August 28, 2019 Expiration Date: February 27, 2021
Sample 1
ORIGINAL EFFECTIVE AND EXPIRATION. DATES OF THE MATCH: Effective Date: December 20, 2019 Expiration Date: June 19, 2021 The above effective and expiration dates are based on the expiration of the 30-day public comment period following ED's November 20, 2019 publication of notice of this matching program in the Federal Register.
Sample 1

Related to ORIGINAL EFFECTIVE AND EXPIRATION

  • Termination and Expiration 17.1 This Agreement shall become effective upon the Effective Date.

  • Commencement and Expiry (a) This Agreement will commence seven days after approval by the Fair Work Commission and will nominally expire on 30 June 2020.

  • Term and Expiration This Agreement shall be effective as of the Effective Date and unless terminated earlier pursuant to Section 9.2 or 9.3, this Agreement shall continue in effect until expiration of all royalty obligations hereunder. Upon expiration of all royalty obligations under this Agreement, such licenses to Merck pursuant to Sections 3.1(a), 3.1(b) and 3.2 as were in effect immediately prior to such expiration shall become fully paid-up, perpetual licenses. *** Confidential Treatment Requested

  • Duration and Expiry 1. This Agreement shall remain effective for a period of ten (10) years from the date of the notification under Article 13 and shall remain in force for a further period of five (5) years thereafter, save if one of the two Contracting Parties withdraws in writing by not later than one year before its expiry date.

  • Cancellation and Expiration Notice Insurance required herein shall not expire, be canceled, or be materially changed without 30 days’ prior written notice to the City.

  • Execution of Agreement and Effective Date The Agreement shall become effective (i.e., final and binding) upon the date of signing of this Agreement and the CAP by the last signatory (Effective Date).

  • Effect of Agreement Termination or Expiration Termination or expiration of this Agreement in whole for any reason will immediately terminate Partner’s participation in any and all Programs. Upon such termination or expiration, Partner will immediately (i) cease referring to itself as a Red Hat Partner, or any other title associated with the Program, and using those titles in any communication or advertising; (ii) to the extent applicable, cease all promotion, demonstration, sale(s) and distribution of the Red Hat Products and/or Services; (iii) cease all use of the Red Hat Marks; (iv) return or destroy, at Red Hat’s option, all printed materials containing Red Hat Marks, including all documentation and Promotional Materials; and (v) remit all fees due to Red Hat within fifteen (15) days of such termination or expiration. If the termination is not the result of a Partner breach, the Partner will be entitled to sell, for a period of no longer than sixty (60) days after termination, any of its inventory of Red Hat Products (subject to this Agreement) for which Red Hat has been fully paid and that are required to fulfill any unperformed contracts of Partner outstanding at the date of termination or expiration. All rights and obligations of the Parties under this Agreement and all applicable Program Appendices will terminate immediately, except that obligations under Sections 6, 7, 8.2, 10, 11.2 – 11.5, 12, 13.3 - 13.4, 14.1 - 14.3, 14.6, 15, and 17 hereof, and any Partner payment obligations will survive such termination or expiration. Termination of this Agreement shall not affect any agreements between Red Hat and any End User.

  • WAIVER AND EFFECTIVE DATE PJM requests that the Commission grant any and all waivers of the Commission’s rules and regulations necessary for acceptance of this filing and the enclosed Amended Service Agreements. Additionally, PJM requests a waiver of the Commission’s 60-day prior notice requirement to (i) allow the effective date of the Amended ISA to remain January 28, 2019; and

  • Data Transfer Upon Termination or Expiration Provider will notify the Division of impending cessation of its business and any contingency plans. Provider shall implement its exit plan and take all necessary actions to ensure a smooth transition of service with minimal disruption to the Division. As mutually agreed upon and as applicable, Provider will work closely with its successor to ensure asuccessful transition to the new equipment, with minimal downtime and effect on the Division, all such work to be coordinated and performed in advance of the formal, transition date.

  • Duration of Agreement and Protected Data Upon Termination or Expiration The Master Agreement commences on the date of signature. • Upon expiration of the Master Agreement without renewal, or upon termination of the Master Agreement prior to its expiration, Vendor will securely delete or otherwise destroy any and all Protected Data remaining in the possession of Vendor or any of its subcontractors or other authorized persons or entities to whom it has disclosed Protected Data. If requested by the District, Vendor will assist the District in exporting all Protected Data previously received back to the District for its own use, prior to deletion, in such formats as may be requested by the District. • In the event the Master Agreement is assigned to a successor Vendor (to the extent authorized by the Master Agreement), the Vendor will cooperate with the District as necessary to transition Protected Data to the successor Vendor prior to deletion. • Neither Vendor nor any of its subcontractors or other authorized persons or entities to whom it has disclosed Protected Data will retain any Protected Data, copies, summaries or extracts of the Protected Data, or any de-identified Protected Data, on any storage medium whatsoever. Upon request, Vendor and/or its subcontractors or other authorized persons or entities to whom it has disclosed Protected Data, as applicable, will provide the District with a certification from an appropriate officer that these requirements have been satisfied in full. Challenging Accuracy of Protected Data: Parents or eligible students can challenge the accuracy of any Protected Data provided by the District to Vendor, by contacting the District regarding procedures for requesting amendment of education records under the Family Educational Rights and Privacy Act (FERPA). Teachers or principals may request to challenge the accuracy of APPR data provided to Vendor by following the appeal process in the District’s applicable APPR Plan. Data Storage and Security Protections: Any Protected Data that Vendor receives will be stored on systems maintained by Vendor, or by a subcontractor under the direct control of Vendor, in a secure data center facility located within the United States. The measures that Vendor (and, if applicable, its subcontractors) will take to protect Protected Data include adoption of technologies, safeguards and practices that align with the NIST Cybersecurity Framework, and safeguards associated with industry standards and best practices including, but not limited to, disk encryption, file encryption, firewalls, and password protection.

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