PROJECT TEAM LIST Sample Clauses

PROJECT TEAM LIST. List the business name, mailing address, phone number, and email address, and personnel, along with their title or role, involved in the project of each Consultant and/or sub-consultant, who contributed to the Work Product.
AutoNDA by SimpleDocs
PROJECT TEAM LIST. The list of key project team members shall be defined. The project team list documents roles and contact information for each team member contributing to the completion of the project.

Related to PROJECT TEAM LIST

  • 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 Managers The JBE’s project manager is: [Insert name]. The JBE may change its project manager at any time upon notice to Contractor without need for an amendment to this Agreement. Contractor’s project manager is: [Insert name]. Subject to written approval by the JBE, Contractor may change its project manager without need for an amendment to this Agreement.

  • 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 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.

  • 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.

  • Alliance Managers In addition to the foregoing governance provisions, each of the Parties shall appoint a single individual to serve as that Party’s alliance manager (“Alliance Manager”). The role of each Alliance Manager will be to participate and otherwise facilitate the relationship between the Parties as established by this Agreement. A Party may replace its Alliance Manager from time to time upon written notice to the other Party.

  • Steering Committee The Project Manager shall set up a Steering Committee for the Project, consisting of representatives from the Department, the Contractor, and any other key organisations whom the project will impact on, to be agreed between the parties. The function of the Steering Committee shall be to review the scope and direction of the Project against its aims and objectives, monitor progress and efficiency, and assess, manage and review expected impact and use of the findings from the Project. The Committee shall meet at times and dates agreed by the parties, or in the absence of agreement, specified by the Department. The Contractor’s representatives on the Steering Committee shall report their views on the progress of the Project to the Steering Committee in writing if requested by the Department. The Contractor’s representatives on the Steering Committee shall attend all meetings of the Steering Committee unless otherwise agreed by the Department.

  • 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.

  • Program Managers See Section 14.1.

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