MBCBP Transition Timeline Sample Clauses

MBCBP Transition Timeline. The Company shall have the following milestones/deadlines regarding the MBCBP election and transition: Milestone/Deadline Requirement July 31, 2023 Pension Plan amended to ensure pre-election closure of Pension Plan to Non-Participant Pilots. July 31, 2023 – May 30, 2024 Executed MBCBP document and amendments to other plans. January 30, 2024 “New year” Company communication to pilots regarding upcoming election with basic MBCBP information. March 31, 2024 Interim reminder communication regarding upcoming election. April 1, 2024 Summary Plan Description posted on website accessible to pilots. April 1 – 15, 2024 Election Packets (including FAQs or equivalent information) distributed via first-class mail to pilots. April 15 – May 30, 2024 45-day Election period (with access to online modeling tool and open call center). June 30, 2024 Confirmation of election statement sent to each pilot (via first-class mail) January 1, 2025 Start date of MBCBP. February 28, 2025 Compensation Credit Notification statement mailed to pilots, receiving “catch-up” credits, via first-class mail.
AutoNDA by SimpleDocs

Related to MBCBP Transition Timeline

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products

  • EPP transform-command RTT Refers to the RTT of the sequence of packets that includes the sending of a transform command plus the reception of the EPP response for only one EPP transform command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP transform commands are those described in section 2.9.3 of EPP RFC 5730. If the RTT is 5 times or more the corresponding SLR, the RTT will be considered undefined.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

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