Pre-Launch Period Sample Clauses

Pre-Launch Period. 1. During the Pre-Launch Period, each of the parties shall perform all of the Checklist Item tasks designated on Schedule B as being its responsibility during the Pre-Launch Period with respect to the Long Distance Telecommunications Services described in Schedule C. With respect to each task involving the development of a definition, procedure or standard, the responsible party shall generate a detailed written guideline that will be applicable to the appropriate party and will be set forth in a list of standards, procedures and/or obligations to be observed by such party (the "AOL Performance List" and the "TS Performance List", respectively, and together, the "Performance Lists"). Each such guideline set forth in the Performance Lists shall be subject to the mutual agreement of the parties, not to be unreasonably withheld. With respect to Checklist Item tasks that are designated on Schedule B as the joint responsibility of TS and AOL during the Pre-Launch Period, TS and AOL shall work jointly in good faith to develop the appropriate guidelines and to allocate responsibilities thereunder to the appropriate Performance List. 2. The Pre-Launch Period shall commence promptly following the Effective Date and shall not end until completion of all of the Checklist Item tasks designated for completion during the Pre-Launch Period on Schedule B. If any such Checklist Item task remains uncompleted or if any guideline has not been agreed to as of * * * , the anticipated date therefor, the period for such completion may be extended by up to * * * at the request of either party.

Pre-Launch Period. During the Pre-Launch Period, Lead Agency, with support from FCO, will, in accordance with the timelines and standards set out in Foundry Policies: (a) Hire or appoint a Project Lead to oversee the Project from start-up to opening of the Centre; (b) Create and deliver to FCO for agreement a finalized charter document for the Project, which may be modified from time to time. Materially significant changes will be re - submitted for agreement; (c) Create and deliver to FCO, for agreement, a Centre Services and Supports Environmental Scan Report; (d) Create and deliver to FCO, for agreement a comprehensive description of the services planned for the Centre (e.g.“Program Description” or “Clinical Services Plan”), which may be modified as indicated by operational and community considerations, and when changes are made will be resubmitted for agreement; (e) Create and deliver to FCO, for agreement a plan to describe the functional, space and design requirements to support the clinical services plan and schematic design development (e.g.“Functional Program Plan”), which may be modified from time to time and if modified, shall be resubmitted for agreement; and (f) Create and deliver to FCO, for agreement a plan for operation of the Centre, the Foundry Services and Facility (e.g. “Operations Plan”), which may be modified from time to time and if modified, shall be resubmitted for agreement.