Project Team To accomplish Owner’s objectives, Owner intends to employ a team concept in connection with the construction of the Project. The basic roles and general responsibilities of team members are set forth in general terms below but are more fully set forth in the Design Professional Contract with respect to the Design Professional, in the Program Management Agreement with any Program Manager, and in this Contract with respect to the Contractor.
Joint Project Team As soon as possible after the Effective Date, the Parties shall establish a joint project team (the “JPT”) which shall be initially responsible for the day-to-day operations of the Initial Target Program. The JPT shall also be responsible for the day-to-day operations of all other Collaboration Programs when they become ***Portions of this page have been omitted pursuant to a request for Confidential Treatment and filed separately with the Commission. effective; provided, that if multiple JPTs are needed due to different Targets or disease areas, then the Parties may establish separate JPTs for different Collaboration Programs. The JPT shall be comprised of representatives from each of GSK and Adaptimmune with the appropriate scientific expertise with respect to the conduct of the Development Plans (and such representatives may vary depending on the relevant Project Phase) and shall meet on a monthly basis (or more or less frequently as agreed by the Parties) at Adaptimmune’s facilities, GSK’s facilities or via teleconference at such times as may be agreed by the Parties during the term of the applicable Collaboration Program. The JPT will report to the JSC and will be responsible for the day-to-day management of the conduct of the Development Plans including any non-material changes to the Development Plans, overseeing the conduct of experiments and reviewing data resulting from such experiments as set forth in the Development Plans, proposing amendments to the Development Plans, proposing new Development Plans to the JSC for new Collaboration Programs for JSC approval, discussing potential Lead Candidates and Development Candidates for proposal to the JSC. All decisions of the JPT on matters for which it has responsibility shall be made unanimously. In the event that the JPT is unable to reach a unanimous decision within ten (10) Business Days after it has met and attempted to reach such decision, then either Party may, by written notice to the other, have such issue submitted to the JSC for resolution in accordance with Section 4.5. Each Party will bear all expenses it incurs in regard to participating in all meetings of the JPT, including all travel and living expenses. Each JPT shall automatically cease to exist on completion of the relevant Collaboration Programs that it supports and exercise or expiry of all Collaboration Program Options applicable to such Collaboration Programs.
Project Leaders Within [**] Business Days after the Effective Date, each Party will appoint (and provide written notice to the other Party of the identity of) a senior representative having a general understanding of biopharmaceutical discovery and development issues to act as its project leader under this Agreement (each, a “Project Leader”). The Project Leaders will serve as the contact point between the Parties with respect to the Research Program, and will be primarily responsible for: (a) facilitating the flow of information and otherwise promoting communication, coordination of the day-to-day work and collaboration between the Parties; (b) providing single point communication for seeking consensus internally within the respective Party’s organization; and (c) raising cross-Party or cross-functional disputes in a timely manner. The Project Leaders shall conduct regular telephone conferences as deemed necessary or appropriate, to exchange informal information regarding the progress of the Research Program. Each Party may change its designated Project Leader from time to time upon prior written notice to the other Party. Each Project Leader may designate a substitute to temporarily perform the functions of that Project Leader by prior written notice to the other Party.
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.
Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.
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 Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.
Development Committee As soon as practicable, the Parties will establish a joint development committee, comprised of at least one (1) and up to two (2) representatives of Omega and at least one (1) and up to two (2) representatives of Acuitas (the “JDC”). One such representative from each Party will be such Party’s Workplan Leader. Each Party may replace its Workplan Leader and other JDC representatives at any time upon written notice to the other Party, provided, however, that each Party shall use reasonable efforts to ensure continuity on the JDC. With the consent of the other Party (which will not be unreasonably withheld, conditioned or delayed), each Party may invite non-voting employees and consultants to attend JDC meetings as necessary, subject to consultant’s agreement to be bound to the same extent as a permitted subcontractor under Section 3.1(i).
Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.
Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.
