Joint Operational Teams Sample Clauses

Joint Operational Teams. Upon the request of either Party hereto, the Parties shall promptly form joint operational teams as needed to develop the procedures, guidelines, specifications and standards necessary for the provision of services under this Agreement and for the specific implementation of each Party’s obligations hereunder. Once a joint operational team is established, each Party’s representatives to the team will work in good faith to resolve identified implementation issues in a timely manner. Agreements reached by such operational teams shall be documented, unless otherwise agreed upon by the Parties.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Joint Operational Teams. The JOC shall have the right to establish joint operational teams (“JOT”), which shall have the authority granted to them by the JOC and shall be comprised of members from both Parties.
Sample 1Sample 2Sample 3See All (5)
Joint Operational Teams. The JRC shall have the right to establish JOTs, which may include but will not be limited to a Research JOT.
Sample 1Sample 2Sample 3
Joint Operational Teams. From time to time the JSC may establish and delegate duties to other committees, sub-committees, or directed teams (each a “Joint Operational Team”) on an “as needed” basis to oversee particular projects or activities. It is envisaged that the JSC will establish a Joint Operational Team to oversee technology transfer and the implementation of the Transition Plan. Each such Joint Operational Team shall be constituted and shall operate as the JSC determines. Joint Operational Teams may be established on an ad hoc basis for purposes of a specific project, or on such other basis as the JSC may determine. Each Joint Operational Team and its activities shall be subject to the oversight, review and approval of, and shall report to, the JSC. The authority of the Joint Operational Team cannot exceed that specified for the JSC in this ARTICLE 2 (Overview and Management of the Collaboration). Any disputes within a Joint Operational Team shall be referred to the JSC for resolution.
Sample 1
Joint Operational Teams. The JRC and the JDC have the authority to establish joint operational teams (“JOT”) as necessary to prepare plans and to perform activities within the scope of such committee’s responsibility and authority for the applicable Program. JOTs shall not have decision making authority except to the extent delegated by the respective committee as applicable. Any disagreement between the members of Roche and Vividion on a JOT shall be referred to the applicable committee that formed the JOT for resolution. Each JOT shall perform such activities as decided by the respective committee. Each JOT shall consist of the members designated by each Party (with each Party having equal number of members, unless otherwise agreed) and each member shall have the expertise and knowledge sufficient to perform assigned activity. The Parties will establish a joint patent coordination team.
Sample 1
Joint Operational Teams. Each Committee may establish JOTs from time-to-time, with a defined scope and duration, to carry out the activities of such Committee. Each of the JOTs shall be composed of representatives designated by each Party and the Parties need not have the same number of representatives. The JOTs shall include individuals with expertise and responsibilities appropriate (in terms of their seniority, availability, function in their respective organizations, training and experience) for the tasks then being undertaken and the stage of the research, manufacture, development and commercialization of applicable Compounds and Products for which joint activities will be performed. Each Party shall designate one of its representatives as its primary contact for all JOT matters (such Party’s “JOT Co-Leader”). A Party may replace any or all of its representatives (and designated JOT Co-Leader) at any time by informing the other JOT Co-Leader in advance, in writing (which may be by email). Roche’s JOT Co-Leader for a given JOT shall be responsible for keeping minutes of any JOT meetings that record in writing all decisions made, action items assigned or completed, and other appropriate matters. Meeting minutes shall be sent to both Parties within [* * *] after a meeting for review, comment and approval by each Party.
Sample 1
Joint Operational Teams. Upon the request of either Party hereto, the Parties shall promptly form joint operational teams as needed to develop the procedures, guidelines, specifications and standards necessary for the provision of services under this Agreement and for the specific implementation of each Party’s obligations hereunder. Once a joint operational team is established, each Party’s representatives to the team will work in good faith to resolve identified implementation issues in a timely manner. Agreements reached by such operational teams shall be documented, unless otherwise agreed upon by the Parties. APPENDIX MERGER CONDITIONS TABLE OF CONTENTS 1. MERGER CONDITIONS 3 2. DEFINED TERMS; DATES OF REFERENCE 3
Sample 1
AutoNDA by SimpleDocs
Joint Operational Teams. The JSC and JCC shall have the right to establish joint operational teams (each a “JOT”), which shall include but will not be limited to a joint research and development team (the “JRDT”}. [***] Certain information in this document has been excluded pursuant to Regulation S-K, Item 601(b)(10). Such excluded information is not material and would likely cause competitive harm to the registrant if publicly disclosed.
Sample 1
Joint Operational Teams 
Sample 1Sample 2

Related to Joint Operational Teams

  • Teams One team for the purposes of the Event shall consist of one Vehicle. Each Vehicle can contain a maximum of three Team Members, provided such Team Members have entered into a Team Entry Agreement with the Company or have otherwise agreed in writing to participate in the Event upon and subject to the Terms of Entry and the Event Rules. For the avoidance of doubt, it is the sole responsibility of each Team to inform themselves of the maximum numbers of persons legally permitted to travel in the Vehicle under Relevant Law. The Company shall provide each Team with the contact details of the Approved Hirer who will be able to provide each Team with a Vehicle for use in the Event, subject to the Team entering into an agreement (the "Borrowing Agreement") with the Hirer outlining the terms of use of the Vehicle. Should the Vehicle not be delivered to the Designated Finish Point by 14:00 local time on 19th September 2021, then the team will be liable for the "Hire Costs" outlined below. Each Vehicle will be of a similar specification to that outlined in Schedule 4 to the Team Entry Agreement. For the avoidance of doubt, the Company shall make no representations or warranties as to the suitability of the Approved Hirer or of the Vehicle for participation in the Event and any rights or warranties which a Team may have or be granted in relation to the Vehicle shall be limited to those contained in the Rental Agreement or implied by any Relevant Law.

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

  • Project Steering Committee 1. For a sound implementation and management of the project, a steering committee shall be set up in line with provisions of the programme manual. 2. The steering committee is the decision-making body of the project and it shall be composed by representatives of the LP and all PPs duly authorised to represent the respective LP and PP institutions. It shall be chaired by the LP and it shall meet on a regular basis. Associated partners shall be invited to take part in the steering committee in an advisory capacity. External key stakeholders may also be invited to take part to one or more meetings in an observer/advisory capacity. 3. The steering committee shall at least: a. be responsible for monitoring and validating the implementation of the project and the achievement of the planned results as in the approved application form; b. perform the financial monitoring of the project implementation and to decide on any budget modifications as in § 11 of this agreement; c. monitor and manage deviations of the project implementation; d. decide on project modifications (e.g. partnership, budget, activities, and duration) if needed; e. be responsible for the settlement of any disputes within the partnership (as stipulated in § 22 of this agreement). 4. Further aspects, including the creation of sub-groups or task forces, may be set out in the rules of procedure of the steering committee.

  • Contractor’s Project Manager 7.2.1 The Contractor’s Project Manager is designated in Exhibit F (Contractor’s Administration). The Contractor shall notify the County in writing of any change in the name or address of the Contractor’s Project Manager. 7.2.2 The Contractor’s Project Manager shall be responsible for the Contractor’s day-to-day activities as related to this Contract and shall meet and coordinate with County’s Project Manager and County’s Contract Project Monitor on a regular basis.

  • 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 Concession Area, including its abandonment.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • 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 Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!