Project Planning Meetings Sample Clauses

Project Planning Meetings. After both parties have signed this Agreement, the parties shall meet at COMPANY or at a mutually convenient location or through video conferencing and at a mutually convenient date and time to discuss project planning. The parties shall endeavor to hold this meeting within one week after both parties have signed this Agreement.
AutoNDA by SimpleDocs
Project Planning Meetings. PURPOSE: In an effort to enhance and improve communication and coordination between Utah XXXX and EPA the attached master agenda for project-specific planning meetings has been developed. This agenda identifies the major elements that should be considered during the planning stages of a major Superfund project. These meetings will provide a forum for Utah and EPA Region 8 representatives to discuss issues that are pertinent to project planning for individual projects, and ensure that both parties clearly understand their roles and expectations with respect to the various topics that will be covered in the meetings. It is expected that engaging in these discussions will improve communication between the agencies and minimize delays in accomplishing the goals for the projects. MEETING FORMAT: Project managers and support personnel will engage in discussions regarding the agenda topics prior to the actual meeting and will present options during the meeting with a discussion of advantages and disadvantages of the various options. The presentation should include a brief written summary each agenda item. A preferred course of action will also be presented. It is expected that the discussions in these meetings will center on broad concepts and will not include exhaustive detail. PARTICIPANTS: Attendees at the meetings will typically include project managers for the State and EPA, community relations representatives, enforcement personnel, specialized technical support staff and appropriate managers from each organization. It is expected that meetings will be held near the beginning of a project before a preferred course of action is implemented, when a decision document is initiated, and at the beginning of remedy design. Additional meetings may be necessary during the course of a project if major modifications of the plan become necessary or unanticipated controversies arise. PROJECT PLANNING MEETING AGENDA REVISED 2/3/97 OVERALL GOALS: Identify the short term and long term goals for the project. Issues to consider may include; short term stabilization needs, access control, future land use (residential, commercial, industrial, etc.), groundwater, ARARs, cleanup standards, etc. OVERALL STRATEGY: Present the strategy that is preferred by the team. Discuss the advantages and disadvantages of the various approaches that are available (traditional process, removal, combination, State program). The strategy should be revisited periodically and revised as appropriate.

Related to Project Planning Meetings

  • Regulatory Meetings The Regulatory Lead Party shall provide the other Party with notice of all meetings, conferences, and discussions (including FDA advisory committee meetings and any other meeting of experts convened by the FDA concerning any topic relevant to a Product, as well as Product labeling and post-Regulatory Approval Product labeling discussions with the FDA) scheduled with the FDA concerning any pending Drug Approval Application or any material regulatory matters relating to a Product within [****]* after the Regulatory Lead Party receives notice of the scheduling of such meeting, conference, or discussion (or within such shorter period as may be necessary in order to give the other Party a reasonable opportunity to participate in such meetings, conferences and discussions). The other Party shall be entitled to be present at, and to participate in, all such meetings, conferences or discussions. PDL’s and BMS’ respective members of the JDC shall use reasonable efforts to agree in advance on the scheduling of such meetings and on the objectives to be accomplished at such meetings, conferences, and discussions and the agenda for the meetings, conferences, and discussions with the FDA. The Regulatory Lead Party shall also include the other Party in any unscheduled, ad-hoc meetings, conferences and discussions with the FDA concerning any pending IND, Drug Approval Application or any material regulatory matters relating to a Product. * Certain information on this page has been omitted and filed separately with the SEC. Confidential treatment has been requested with respect to the omitted portions.

  • JSC Meetings The JSC will meet at least [**], or more or less frequently as mutually agreed by the Parties, at such times as may be agreed to by the Parties. The JSC will determine its meeting locations, and whether to conduct a meeting in-person, by teleconference, or videoconference. Each Party is responsible for all costs and expenses incurred by it in connection with its participation in the meetings of the JSC. Each Party shall have the right to call a special meeting of the JSC at any time as necessary or desirable to address disputes or other matters within the scope of the JSC’s responsibilities by providing the other Parties with written notice to that effect. The JSC Chairs shall schedule and convene such special JSC meeting as soon as practicable following such notice. Each Party may, from time-to-time and with prior written notice to the JSC members of the other Parties, invite Project Team members and/or others of its employees, consultants or agents to attend relevant portions of a JSC meeting as necessary. The Sponsoring Party shall notify the other Parties in writing in the event that it wishes to invite a Third Party to attend a JSC meeting. Any such notice shall be provided at least [**] business days prior to the relevant JSC meeting and shall identify the relevant Third Party and briefly describe the reasons that the Sponsoring Party wishes to include the Third Party in the meeting. The attendance and participation of such Third Party shall be subject to the prior written consent of the Parties receiving such notice (such consent not to be unreasonably withheld). Any such consent granted by a Party shall be conditioned upon the consultant or contractor being bound by a written confidentiality and non-use agreement that is reasonably acceptable to the consenting Party. In the event the Sponsoring Party requires the attendance of such Third Party at subsequent JSC meetings, approval shall not be required for any Third Party who was previously approved by the other Parties and remains bound by an appropriate written confidentiality and non-use agreement at the time of the Project Team meeting, provided that the Sponsoring Party gives the other Parties prior notice of such attendance and the other Parties do not revoke their consent. The Parties’ respective JSC Chairs (as defined below) shall be responsible for ensuring compliance with the foregoing.

  • Member Meetings (a) There shall be no meetings of the Members unless called by the Board or as otherwise specifically required by the Delaware Act. No Members or group of Members, acting in its or their capacity as Members, shall have the right to call a meeting of the Members.

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

  • 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 Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

  • Condominiums/Planned Unit Developments If the Mortgaged Property is a condominium unit or a planned unit development (other than a de minimis planned unit development) such condominium or planned unit development project such Mortgage Loan was originated in accordance with, and the Mortgaged Property meets the guidelines set forth in the Originator's Underwriting Guidelines;

  • 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 Development Committee The Parties shall form a joint development committee (the “Joint Development Committee” or “JDC”), made up of an equal number of representatives of Merck and BioLineRx, which shall have responsibility of coordinating all regulatory and other activities under, and pursuant to, this Agreement. Each Party shall designate a project manager (the “Project Manager”) who shall be responsible for implementing and coordinating activities, and facilitating the exchange of information between the Parties, with respect to the Study. Other JDC members will be agreed by both Parties. The JDC shall meet as soon as practicable after the Effective Date and then no less than twice yearly, and more often as reasonably considered necessary at the request of either Party, to provide an update on the progress of the Study. The JDC may meet in person or by means of teleconference, Internet conference, videoconference or other similar communications equipment. Prior to any such meeting, the BioLineRx Project Manager shall provide an update in writing to the Merck Project Manager, which update shall contain information about the overall progress of the Study, recruitment status, interim analysis (if results available), final analysis and other information relevant to the conduct of the Study. In addition to a Project Manager, each Party shall designate an alliance manager (the “Alliance Manager”), who shall endeavor to ensure clear and responsive communication between the Parties and the effective exchange of information, and shall serve as the primary point of contact for any issues arising under this Agreement. The Alliance Managers shall have the right to attend all JDC meetings and may bring to the attention of the JDC any matters or issues either of them reasonably believes should be discussed, and shall have such other responsibilities as the Parties may mutually agree in writing. In the event that an issue arises and the Alliance Managers cannot or do not, after good faith efforts, reach agreement on such issue, the issue shall be elevated to the Head of Clinical Oncology for Merck and the Vice President of Medical Affairs or Business Development for BioLineRx.

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