Progress Meetings and Reports Sample Clauses

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) @ xxxxx://xxx.xxx.xx/guidance/submit-a-report-to-athena which defines the requirements for the presentation, format and production of scientific and technical reports prepared for MOD.
AutoNDA by SimpleDocs
Progress Meetings and Reports. For the purposes of the Contract in addition to the provisions of DEFCON 604 and DEFCON 642 the following shall apply:
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. 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. During construction, the ENGINEER will schedule and conduct monthly progress meetings with the OWNER, Contractor and appropriate subcontractors, if any, to discuss progress, scheduling problems, conflicts and observations of all parties involved. The ENGINEER shall also prepare minutes of the meeting. The ENGINEER shall also prepare a construction progress report monthly which shall be submitted to OWNER by the 10th day of each month for the preceding month's work. This report shall accompany the Contractor's and the ENGINEER'S monthly payment requests.
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.
AutoNDA by SimpleDocs
Progress Meetings and Reports. The Engineer shall schedule meetings to review the progress of the Work, coordinate future efforts, discuss compliance with the Progress Schedule and resolve miscellaneous problems. The Engineer or Resident Project Representative, Contractor, and all Subcontractors actively working at the Project Site shall attend each meeting. Representatives of suppliers, manufacturers, and other Subcontractors may also attend at the discretion of the Contractor. The Contractor shall record the details of each meeting in a Progress Report. The format of this report shall be developed by the Contractor, approved by the Engineer, and included in the Work Plan. The progress meetings and reports shall be scheduled according to the Special Provisions.
Progress Meetings and Reports. During construction, the ENGINEER will schedule and conduct monthly progress meetings with the CLIENT, 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 CLIENT 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. • Construction Review Representative: ENGINEER shall furnish a Construction Review Representative (CRR), assistants and other field staff to assist ENGINEER in observing work performance of the Contractor. The Construction Review Representative shall make visits to the site at intervals appropriate to the various stages of construction as he deems necessary in order to observe as an experienced and qualified design professional the progress and quality of the various aspects of Contractor's work. Through more extensive on-site observations of the work in progress and field checks of materials and equipment by the CRR and assistants, ENGINEER shall endeavor to provide further protection of CLIENT against defects and deficiencies in the work; but, the furnishing of such services will not make ENGINEER responsible for or give him control over construction means, methods, techniques, sequences or procedures or for safety precautions or programs, or responsibility for Contractor's failure to perform the work in accordance with the Contract Documents. The duties and responsibilities of the CRR are limited to those of the ENGINEER in his agreement with CLIENT and in the construction Contract Documents, and are further limited and described as follows: o General: XXX is ENGINEER's agent at the site and will act as directed by and under the supervision of ENGINEER and xxxx xxxxxx with ENGINEER regarding XXX's actions. XXX's dealings in matters pertaining to the on-site work shall in general be with ENGINEER and Contractor keeping CLIENT advised as necessary. CRR's dealings with Subcontractors shall only be through or with the full knowledge and approval of Contractor. CRR shall generally communicate with CLIENT with the knowledge of and under the direction of ENGINEER.
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.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!