Progress Meetings and Reports Sample Clauses
POPULAR SAMPLE Copied 1 times
Progress Meetings and Reports. 9.1 For the purposes of the Contract in addition to the provisions of DEFCON 604 and DEFCON 642 progress meetings, progress reports and final reports shall be required as appropriate, to the requirements and acceptance of the Dstl Demand Owner and subject to the following requirements:
9.1.1 All Reports included as Deliverables under the Contract e.g. Progress and/or Final Reports etc. must comply with the Defence Research Reports Specification (DRRS) @ ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/guidance/submit-a-report-to-athena which defines the requirements for the presentation, format and production of scientific and technical reports prepared for MOD.
Progress Meetings and Reports. For the purposes of this Contract in addition to the provisions of DEFCON 604 and DEFCON 642 the following shall apply:
Progress Meetings and Reports. During construction, the ENGINEER will schedule and conduct monthly progress meetings with MADISON COUNTY, Contractor and appropriate subcontractors, if any, to discuss progress, scheduling problems, conflicts and observations of all parties involved. ENGINEER shall also prepare minutes of the meeting. ENGINEER shall also prepare a construction progress report monthly which shall be submitted to MADISON COUNTY by the 10th day of each month for the preceding month's work. This report shall accompany the Contractor's and Engineer's monthly payment requests.
Progress Meetings and Reports. The Project Managers shall meet regularly, at least once a month, to discuss the progress of the Project. Minutes of such meetings shall be recorded by COMPUWARE's Project Manager, with a copy provided to CLIENT's Project Manager within five (5) days of the meeting. Any additions or deletions to the minutes shall be provided within (3) three days of receipt of the minutes by the CLIENT's Project Manager. The minutes shall include, but are not limited to, the progress of the work, any anticipated problems (resolved or unresolved), and any indication of delay in fixed or tentative schedules. Approximately once a month, the parties shall meet for a formal progress presentation, at which time COMPUWARE shall describe the status of the Project work. Such presentation shall provide projections of the time of completion and shall address any issues and their possible resolution. The CLIENT shall, where applicable, promptly provide COMPUWARE with (and warrants that it is entitled to do so) accurate and complete information concerning Project requirements, answers to queries, decisions and approvals required by COMPUWARE in connection with the Project. COMPUWARE staff shall have access to CLIENT personnel and premises at all reasonable times as required by COMPUWARE for the performance of the services. Failure by CLIENT to provide the assistance referred to in this paragraph may prohibit effective action by COMPUWARE and render COMPUWARE unable to perform. In such circumstances, COMPUWARE shall be under no liability to perform its obligations under this Agreement to the extent that performance is prohibited by such failure of CLIENT.
Progress Meetings and Reports. The Contractor shall submit technical reports, signed on his behalf by a person authorised to commit the Contractor as follows:-
Progress Meetings and Reports. During construction, the ENGINEER will schedule and conduct monthly progress meetings with the CLIENT, Contractor and appropriate subcontractors to
Progress Meetings and Reports. During the term of the Agreement, the Library’s technical liaison will plan and schedule biannual progress meetings with the University’s technical liaison to discuss the progress made by the University and the Library in the performance of their respective obligations. At each such meeting, the University shall provide the Library with a written status report summarizing progress made towards completion of the objectives set forth in the Scope of Work (Appendix 1) and identifying any problems or circumstances encountered by the University, or of which the University gained knowledge during the period since the last such status report, which may prevent the University from completing any of its obligations. The University shall identify the cause of any identified problem or circumstance and the steps taken to remedy same. Similarly, the Library shall provide the University with a written report identifying any problems or circumstances encountered by the Library which may interfere with its ability to complete its obligations under this Agreement, and the steps being taken by the Library to remedy the situation. The University shall also provide NHP program updates as necessary to satisfy the Library’s reporting requirements to the Library Commission, the Governor’s Office, the Montana State Legislature, and as required by Library contracts and other agreements that directly affect the NHP.
Progress Meetings and Reports. Once every month during the term of the Project (or more or less frequently as the Parties shall mutually agree in writing) the MIMEDX Project Manager shall meet with the RTI Project Manager via teleconferences or at a mutually agreed upon location to discuss the progress made by MIMEDX and RTI in the performance of their obligations under this Agreement during the preceding month. At such meeting, each Project Manager shall prepare and submit to the other Project Manager a written report summarizing the current status of the Project and the progress to date. Such report shall follow a format to be reasonably agreed upon between RTI and MIMEDX, but in any event shall specify in detail the following:
(a) a listing of any milestones met, deliverables achieved, or results found during the prior month; and
(b) any issue or circumstance encountered, or of which the Party first learns, during the prior month that may prevent or tend to prevent the Party from completing any part of the Project within the time frame estimated in Exhibit A (Statement of Work); and
(c) the estimated length of delay which may result from any such issues identified pursuant to subparagraph (a) above; and
(d) to the best of the Party’s knowledge the cause of any such issue and the specific steps taken or proposed to be taken by the Party to address any such issue. Each Party shall bear all of its own costs associated with preparing for and attending such meetings.
Progress Meetings and Reports. Until completion of Installation of the sites in Attachment A, ACS and SiriCOMM representatives shall meet once a week in person or by conference call
13.1 SiriCOMM will provide a monthly reports on the failure for transmission of data between sites. Additional reports may be necessary and/or required and mutually agreed upon throughout the term of this contract.
Progress Meetings and Reports. 26.1. Until completion of Installation of the sites in Attachment 6, MCI and Nasdaq representatives (including one management level representative able to discuss status, resolve problems, and accept responsibility for completion of action items from each of: the MCI International Data Networks Group (or its successor(s)) and MCI Project Management) shall meet once a week in person or by conference call. MCI must produce before the meeting, a written progress report outlining status and known material problems. MCI shall produce, before the next meeting, minutes and a list of action items coming out of each meeting.
26.2. During the effectiveness of this Agreement, MCI and Nasdaq representatives (including one management level representative able to discuss status, resolve problems, and accept responsibility for completion of action items from each of: the MCI Network Operations; and Project Management) shall meet in person or by conference call once every other week or as mutually agreed to by the Parties. MCI shall produce, before the next meeting, minutes and a list of action items coming out of each meeting.
