Pilot and Program Launch Sample Clauses

Pilot and Program Launch. The parties contemplate a three-phase rollout of the Program as follows: (i) an initial pilot (the “Pilot”) projected to start in the date set forth in each Addendum (the “Pilot Launch”), consisting of the number of courses set forth in each Addendum with working titles set forth in each Addendum and including no more than the number of students set forth in each Addendum for the initial Session, in order to give both parties the opportunity to further develop the Program; (ii) a launch of the Program projected to start in the date set forth in each Addendum (the “Program Launch”), consisting of the number of courses set forth in each Addendum with working titles set forth in each Addendum; and (iii) a launch of such additional courses in the Program as the parties may mutually agree (the “Additional Courses Launch”), projected to start as set forth in each Addendum. Subject to Section 1.H and 1.I, the parties shall agree in good faith when the Program is ready for Pilot Launch and for Program Launch.
AutoNDA by SimpleDocs
Pilot and Program Launch i) The Pilot Launch will be in September 2010; it shall contain one course. The parties shall reasonably agree on the working titles of the courses in the Pilot Launch. The number of students for the initial Session shall not exceed 60.
Pilot and Program Launch. The parties contemplate a three-phase rollout of the Program as follows: (i) an initial pilot (the “Pilot”) projected to start in January 2009 (the “Pilot Launch”), consisting of two courses with working titles “Framing Experiences” and “Social Contexts A” and including no more than fifty (50) students for the initial semester, in order to give both parties the opportunity to further develop the Program; (ii) a launch of the Program projected to start in June 2009 (the “Program Launch”), consisting of three courses with working titles “Framing Experiences,” “Social Contexts A” and “Learning Theory”; and (iii) a launch of such additional courses in the Program as the parties may mutually agree, projected to start in October 2009. Subject to Section 1.H and 1.I, the parties shall agree in good faith when the Program is ready for Pilot Launch and for Program Launch.
Pilot and Program Launch. 2U shall produce up to forty-five (45) credits for the DSW Program as determined by USC, and each course shall be worth three (3) credits. USC may include up to three (3) additional dissertation/capstone courses for which USC shall be solely responsible to create and produce.

Related to Pilot and Program Launch

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones)

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • REVIEW OF WORK The Consultant shall permit the City, its agents and/or employees to review, at any time, all work performed pursuant to the terms of this Agreement at any stage of the work;

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Safety Program The Contractor shall design a specific safety program for the Work for the site(s). The Contractor shall establish and require all Subcontractors to establish reasonable safety programs. The Contractor shall also submit its standard monthly safety reports to the Owner and Design Professional. No imposition of responsibility on the Contractor for safety under this Contract shall relieve any subcontractor of its responsibility for safety of persons or property on or near the Project Site. The Contractor shall include in his plant he names of the person in charge of Safety.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Pilot Programs The Employer may develop voluntary pilot programs to test the acceptability of various risk management programs. Incentives for participation in such programs may include limited short-term improvements to the benefits outlined in this Article. Implementation of such pilot programs is subject to the review and approval of the Joint Labor-Management Committee on Health Plans.

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