Common use of Project Manager's Responsibilities Clause in Contracts

Project Manager's Responsibilities. The Project Manager shall be responsible for the following activities, together with such other activities as the Parties may agree: (a) Managing all matters relating to the eSAS 2 Development Program under this eSAS 2 Addendum, including each Party’s respective responsibilities and contributions and receiving reports from the Project Leaders; (b) Providing written progress reports monthly to the Parties and presenting status reports to the Supervisory Board in accordance with Section 2.4.6 below; (c) Submitting and receiving the reports, materials and documents required to be delivered under this eSAS 2 Addendum; (d) Overseeing the process of proposing, and submitting to the Parties, any proposed modifications to the Product Requirements Document, Software Requirement Specifications, Technical Plan, Resource Plan or Budget, and in the event the Parties cannot agree, presenting the same to the Supervisory Board in an objective and neutral manner; (e) Arranging any meetings to be held between the Parties and participating, to the extent the Project Manager deems appropriate, in meetings of the Project Leaders; (f) Maintaining, for record keeping purposes, a log book or notes containing summaries and dates of all material communications and deliveries between the Parties of which the Project Manager is aware, consistent with the Parties’ protocol for such sharing of confidential information set forth in that certain Confidentiality and Joint Interest Agreement, by and between the Parties, dated as of October 30, 2001; (g) Implementing appropriate practices and procedures to manage the progress under this eSAS 2 Addendum; (h) Fostering good communication between the Parties. It is intended by the Parties that both Parties share, through reports from the Project Leaders to the Project Manager, in the information concerning the progress made in the eSAS 2 Development Program and the cause of any delays. It is expected that the Project Leaders will make recommendations to the Project Manager for preferred paths when substantial delays are identified and multiple paths forward are identified. Understanding that it takes time for information to flow up the chain of command, the Project Manager will inform Gen-Probe of delays and progress on resolution as soon as it becomes available to him; and (i) It is understood that both companies hold proprietary trade secret know-how and processes regarding their respective technologies that are not necessarily shared as part of this Agreement. On occasion it may occur that a full understanding of difficulties in the progress of development may require a detailed understanding of this proprietary know-how and processes. Each Party will endeavor to appraise the other of the outcomes and consequences of these difficulties, while protecting the confidentiality of the information.

Project Manager's Responsibilities. The Project Manager shall be responsible for the following activities, together with such other activities as the Parties parties may agree:: *CONFIDENTIAL TREATMENT REQUESTED (a) Managing all matters relating to the eSAS 2 WNV Development Program under this eSAS 2 West Nile Virus Addendum, including each Party’s party's respective responsibilities and contributions and receiving reports from the Project Leaders; (b) Providing written monthly progress reports monthly to the Parties parties and presenting status reports to the Supervisory Board in accordance with Section 2.4.6 below; (c) Submitting and receiving the reports, materials and documents required to be delivered under this eSAS 2 West Nile Virus Addendum; (d) Overseeing the process of proposing, and submitting to the Partiesparties, any proposed modifications to the Product Requirements Document, Software Requirement Specifications, Technical Plan, Resource Plan or Budget, and in the event the Parties parties cannot agree, presenting the same to the Supervisory Board in an objective and neutral manner; (e) Arranging any meetings to be held between the Parties parties and participating, to the extent the Project Manager deems appropriate, in meetings of the Project Leaders; (f) Maintaining, for record keeping purposes, a log book or notes containing summaries and dates of all material communications and deliveries between the Parties parties of which the Project Manager is aware, consistent with the Parties’ parties' protocol for such sharing of confidential information set forth in that certain Confidentiality and Joint Interest Agreement, by and between the Partiesparties, dated as of October 30, 2001; (g) Implementing appropriate practices and procedures to manage the progress under this eSAS 2 West Nile Virus Addendum; (h) Fostering good communication between the Partiesparties. It is intended by the Parties parties that both Parties parties share, through reports from the Project Leaders to the Project Manager, in the information concerning the progress made in the eSAS 2 WNV Development Program and the cause of any delays. It is expected that the Project Leaders will make recommendations to the Project Manager for preferred paths when substantial delays are identified and multiple paths forward are identified. Understanding that it takes time for information to flow up the chain of command, the Project Manager will inform Gen-Probe Chiron of delays and progress on resolution as soon as it becomes available to him; and (i) It is understood that both companies hold proprietary trade secret know-how and processes regarding their respective technologies that are not necessarily shared as part of this Agreement. On occasion it may occur that a full understanding of difficulties in the progress of development may require a detailed understanding of this proprietary know-how and processes. Each Party party will endeavor to appraise the other of the outcomes and consequences of these difficulties, while protecting the confidentiality of the information.

Project Manager's Responsibilities. The Project Manager shall be responsible for the following activities, together with such other activities as the Parties parties may agree: (a) Managing all matters relating to the eSAS 2 WNV Development Program under this eSAS 2 West Nile Virus Addendum, including each Party’s party's respective responsibilities and contributions and receiving reports from the Project Leaders; (b) Providing written monthly progress reports monthly to the Parties parties and presenting status reports to the Supervisory Board in accordance with Section 2.4.6 below; (c) Submitting and receiving the reports, materials and documents required to be delivered under this eSAS 2 West Nile Virus Addendum; (d) Overseeing the process of proposing, and submitting to the Partiesparties, any proposed modifications to the Product Requirements Document, Software Requirement Specifications, Technical Plan, Resource Plan or Budget, and in the event the Parties parties cannot agree, presenting the same to the Supervisory Board in an objective and neutral manner; (e) Arranging any meetings to be held between the Parties parties and participating, to the extent the Project Manager deems appropriate, in meetings of the Project Leaders; (f) Maintaining, for record keeping purposes, a log book or notes containing summaries and dates of all material communications and deliveries between the Parties parties of which the Project Manager is aware, consistent with the Parties’ parties' protocol for such sharing of confidential information set forth in that certain Confidentiality and Joint Interest Agreement, by and between the Partiesparties, dated as of October 30, 2001; (g) Implementing appropriate practices and procedures to manage the progress under this eSAS 2 West Nile Virus Addendum; (h) Fostering good communication between the Partiesparties. It is intended by the Parties parties that both Parties parties share, through reports from the Project Leaders to the Project Manager, in the information concerning the progress made in the eSAS 2 WNV Development Program and the cause of any delays. It is expected that the Project Leaders will make recommendations to the Project Manager for preferred paths when substantial delays are identified and multiple paths forward are identified. Understanding that it takes time for information to flow up the chain of command, the Project Manager will inform Gen-Probe Chiron of delays and progress on resolution as soon as it becomes available to him; and (i) It is understood that both companies hold proprietary trade secret know-how and processes regarding their respective technologies that are not necessarily shared as part of this Agreement. On occasion it may occur that a full understanding of difficulties in the progress of development may require a detailed understanding of this proprietary know-how and processes. Each Party party will endeavor to appraise the other of the outcomes and consequences of these difficulties, while protecting the confidentiality of the information.

Project Manager's Responsibilities. The Project Manager shall be responsible for the following activities, together with such other activities as the Parties parties may agree: (a) Managing all matters relating to the eSAS 2 Ultrio Development Program under this eSAS 2 Ultrio Addendum, including each Party’s party's respective responsibilities and contributions and receiving reports from the Project Leaders; (b) Providing written monthly progress reports monthly to the Parties parties and presenting status reports to the Supervisory Board in accordance with Section 2.4.6 below; (c) Submitting and receiving the reports, materials and documents required to be delivered under this eSAS 2 Ultrio Addendum; (d) Overseeing the process of proposing, and submitting to the Partiesparties, any proposed modifications to the Product Requirements Document, Software Requirement Specifications, Technical Plan, Resource Plan or Budget, and in the event the Parties parties cannot agree, presenting the same to the Supervisory Board in an objective and neutral manner; (e) Arranging any meetings to be held between the Parties parties and participating, to the extent the Project Manager deems appropriate, in meetings of the Project Leaders; (f) Maintaining, for record keeping purposes, a log book or notes containing summaries and dates of all material communications and deliveries between the Parties parties of which the Project Manager is aware, consistent with the Parties’ parties' protocol for such sharing of confidential information set forth in that certain Confidentiality and Joint Interest Agreement, by and between the Partiesparties, dated as of October 30, 2001; (g) Implementing appropriate practices and procedures to manage the progress under this eSAS 2 Ultrio Addendum; (h) Fostering good communication between the Partiesparties. It is intended by the Parties parties that both Parties parties share, through reports from the Project Leaders to the Project Manager, in the information concerning the progress made in the eSAS 2 Ultrio Development Program and the cause of any delays. It is expected that the Project Leaders will make recommendations to the Project Manager for preferred paths when substantial delays are identified and multiple paths forward are identified. Understanding that it takes time for information to flow up the chain of command, the Project Manager will inform Gen-Probe Chiron of delays and progress on resolution as soon as it becomes available to him; and (i) It is understood that both companies hold proprietary trade secret know-how and processes regarding their respective technologies that are not necessarily shared as part of this Agreement. On occasion it may occur that a full understanding of difficulties in the progress of development may require a detailed understanding of this proprietary know-how and processes. Each Party party will endeavor to appraise the other of the outcomes and consequences of these difficulties, while protecting the confidentiality of the information.