Works Report. (a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include: (i) an executive summary describing the general status of the Works and progress made over the relevant month; (ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Requirements; (iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes; (iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise; (v) an update on those matters set out in Schedule 33 – Works Report Requirements; and (vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule. (b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 2 contracts
Samples: Project Agreement, Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority HMQ Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress an updated Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Requirementsboth summary and detailed formats;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution ProcedureSection 22, or otherwise;a LEED progress report; and
(v) an update on those matters set out in Schedule 33 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting AuthorityHMQ, acting reasonably. For greater certainty, for all updates and revisions to the Project Works SchedulesSchedule, Project Co must most provide a revised critical path reflecting the updated or updated/revised Baseline Works Schedule.
(b) HMQ will be establishing an On-line (web-based) Project Management (“OCPM”) software system prior to Financial Close. The Project shall be used to establish and verify the various components/modules of the OCPM. In addition to the Web Based Project Management System to be established by Project Co in accordance with Section 3.2 of Schedule 10 – Review Procedure, Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) OCPM software system specified by Contracting AuthorityHMQ. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – - Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 12 – Service Quality Plan Outline, Schedule 22 – - Variation Procedure Procedure, and Schedule 33 – - Works Report Requirements and other processes as determined by Contracting Authority in its sole discretionHMQ may require.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following the end of each calendar month from Financial Close until the last Final Completion Date, Project Co shall provide to the Contracting Authority IO Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress an updated Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Requirementsboth summary and detailed formats;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution ProcedureSection 21, or otherwise;a LEED progress report; and
(v) an update on those matters set out in Schedule 33 – 34 - Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting AuthorityIO, acting reasonably. For greater certainty, for all updates and revisions to the Project Works SchedulesSchedule, Project Co must provide a revised critical path reflecting the updated or updated/revised Baseline Works Schedule.
(b) IO will be establishing an On-line (web-based) Project Management (“OCPM”) software system prior to Financial Close. The Project shall be used to establish and verify the various components/modules of the OCPM. Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) OCPM software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 12 – Service Quality Plan Outline, Schedule 22 – Variation Procedure Procedure, and Schedule 33 34 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretionIO may require.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co;
(iii) a Current Progress Works Schedule, updated Works Schedule Progress Report, Look- ahead Schedule and a Look-ahead Schedule, updated Works Schedule Assumptions Report all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iiiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(ivv) a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(vvi) an update on those matters set out in Schedule 33 – Works Report Requirements;
(vii) a progress report comparing Project Co’s actual Construction Activities and procurement activities relating to the New Metrolinx Infrastructure with LEED Rating System requirements;
(viii) the information described in Section 4.21(c);
(ix) a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.16 and 11.17; and
(vix) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact withuse, and shall ensure that the Construction Contractor uses and interacts withuses, the On-line (web based) Project Management (“OCPM”) contract management software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:
(i) include: an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) ; a table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co; a Current Progress Works Schedule, updated Works Schedule Progress Report, Look- ahead Schedule and a Look-ahead Schedule, updated Works Schedule Assumptions Report all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iii) ; a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) ; a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) ; an update on those matters set out in Schedule 33 – Works Report Requirements; and
(vi) a progress report comparing Project Co’s actual Construction Activities and procurement activities relating to the New Metrolinx Infrastructure with LEED Rating System requirements; a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.16 and 11.17; and any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact withuse, and shall ensure that the Construction Contractor uses and interacts withuses, the On-line (web based) Project Management (“OCPM”) contract management software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier Consultant a works report (each, a “"Works Report”"), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – 19 - Works Schedule Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(viv) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality ManagementPlans, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(b), in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority SMH Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by SMH and/or Project Co;
(iii) an updated Works Schedule in summary and detailed formats in accordance with Section 7.1 of Appendix A – Minimum Design and Construction Submittal Requirements of Schedule 10 – Review Procedure;
(iv) a narrative with detailed descriptions of the progress of the Works, including:
(A) the progress towards achieving the Works Milestones;
(B) key deliveries to the Site;
(C) construction, erection, testing and commissioning;
(D) a discussion of the basis for any required changes to the sequencing of the Works, interdependencies or original activity durations set out in the Works Schedule, which changes, for clarity, shall be incorporated into the updated Works Schedule;
(E) comparisons of the actual versus the planned progress of the Works, with a brief commentary on any actual or forecasted delays or problems that might have an impact on the scheduled completion dates of the Works in the Works Schedule and a Look-ahead Schedulediscussion of the measures being (or to be) adopted by Project Co to overcome them, all in accordance with Schedule 12 – Works Schedule Requirementsand
(F) any other information specifically requested by SMH on the progress of the Works;
(iiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;; and
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;
(vvi) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting AuthoritySMH, acting reasonably. For greater certainty, for all updates and revisions to the Project Works SchedulesSchedule, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthoritySMH. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority SMH in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) an update on those matters set out in Schedule 33 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – –Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes Dispute related to the Works, including any action that has taken place over the relevant month to resolve such DisputesDispute;
(iv) a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.,
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co;
(iii) Current Progress Works Schedule, updated Works Schedule Progress Report, Look- ahead Schedule and a Look-ahead Schedule, updated Works Schedule Assumptions Report all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iiiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(ivv) a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g) , in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(vvi) an update on those matters set out in Schedule 33 – Works Report Requirements;
(vii) a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.16 and 11.17; and
(viviii) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact withuse, and shall ensure that the Construction Contractor uses and interacts withuses, the On-line (web based) Project Management (“OCPM”) contract management software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co;
(iii) a Progress Works Schedule and a Look-ahead Schedule, Basis of Works Schedule Report, and Works Schedule Report all in accordance with Schedule 12 – Works Schedule Requirements;
(iiiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(ivv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(d), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(vvi) an update on those matters set out in Schedule 33 – Works Report Requirements;
(vii) a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.18 and 11.19; and
(viviii) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to any of the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Project Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority CTC Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule table indicating and a Lookresponding to items of non-ahead Schedulecompliance and noted deficiencies, all as identified by the CTC Representative and/or Project Co, in accordance with Schedule 12 – Works Schedule Requirementsongoing works;
(iii) an updated Works Schedule, in both summary and detailed formats;
(iv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;; and
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authoritythe CTC, acting reasonably. For greater certainty, for all updates and revisions to the Project Works SchedulesSchedule, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authoritythe CTC. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority the CTC in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(b), in accordance with Schedule 27 – Dispute Resolution Procedure, or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co;
(iii) a Progress Works Schedule and a Look-ahead Schedule, Basis of Works Schedule Report, and Works Schedule Report all in accordance with Schedule 12 – Works Schedule Requirements;
(iiiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(ivv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(d), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(vvi) an update on those matters set out in Schedule 33 – Works Report Requirements;
(vii) a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.18 and 11.19; and
(viviii) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to any of the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Project Works Schedule.
(b) Project Co shall use and interact withuse, and shall ensure that the Construction Contractor uses and interacts withuses, the On-line (web based) Project Management (“OCPM”) contract management software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority HMQ Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress an updated Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Requirementsboth summary and detailed formats;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.6, in accordance with Schedule 27 – Dispute Resolution ProcedureSection 22, or otherwise;a LEED progress report; and
(v) an update on those matters set out in Schedule 33 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting AuthorityHMQ, acting reasonably. For greater certainty, for all updates and revisions to the Project Works SchedulesSchedule, Project Co must most provide a revised critical path reflecting the updated or updated/revised Baseline Works Schedule.
(b) HMQ will be establishing an On-line (web-based) Project Management (“OCPM”) software system prior to the Financial Close. The Project shall be used to establish and verify the various components/modules of the OCPM. In addition to the Web Based Project Management System to be established by Project Co in accordance with Section 3.2 of Schedule 10 – Review Procedure, Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) OCPM software system specified by Contracting AuthorityHMQ. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – - Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 12 – Service Quality Plan Outline, Schedule 22 – - Variation Procedure Procedure, and Schedule 33 – - Works Report Requirements and other processes as determined by Contracting Authority in its sole discretionHMQ may require.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 15 Business Days following after the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Independent Certifier and submit to the Contracting Authority Representative and the Independent Certifier in accordance with Schedule 10 – Review Procedure a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a table setting out and responding to items of Project Agreement non-compliance and deficiencies in ongoing Works as identified by Contracting Authority and Project Co;
(iii) a Current Progress Works Schedule, updated Works Schedule Progress Report, Look- ahead Schedule and a Look-ahead Schedule, updated Works Schedule Assumptions Report all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iiiiv) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(ivv) a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(vvi) an update on those matters set out in Schedule 33 – Works Report Requirements;
(vii) a progress report comparing Project Co’s actual Construction Activities and procurement activities relating to the New Metrolinx Infrastructure with LEED rating requirements;
(viii) a detailed, narrative description of all issues relating to Warranty Work and warranties set out in Sections 11.16 and 11.17; and
(viix) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact withuse, and shall ensure that the Construction Contractor uses and interacts withuses, the On-line (web based) Project Management (“OCPM”) contract management software system specified by Contracting Authority. It is contemplated that Authority for certain processes identified in the OCPM software system will automate Project Agreement, including certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Quality Management, Schedule 22 – Variation Procedure Procedure, and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretionRequirements.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at At Risk Matter that has not been resolved pursuant to Section 14.614.6(g), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting AuthorityIO. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 19 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(b), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) an update on those matters set out in Schedule 33 17 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – Design Quality ManagementPlan and Construction Quality Plan, Schedule 22 – Variation Procedure and Schedule 33 17 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement
Works Report.
(a) Project Co shall continuously monitor the progress of the Works in relation to the Baseline Works Schedule and, within 10 Business Days following the end of each calendar month from Financial Close until the Final Completion Date, Project Co shall provide to the Contracting Authority Representative and the Independent Certifier a works report (each, a “Works Report”), which will include:include:
(i) an executive summary describing the general status of the Works and progress made over the relevant month;
(ii) a Current Progress Works Schedule and a Look-ahead Schedule, all in accordance with Schedule 12 – Works Schedule Scheduling Requirements;
(iii) a narrative description of any Disputes related to the Works, including any action that has taken place over the relevant month to resolve such Disputes;
(iv) a narrative description of the status of any Proceeding at Risk Matter that has not been resolved pursuant to Section 14.614.6(f), in accordance with Schedule 27 – Dispute Resolution Procedure, Procedure or otherwise;
(v) an update on those matters set out in Schedule 33 – Works Report Requirements; and
(vi) any other information specifically requested by Contracting Authority on the progress of the Works, all in form and substance satisfactory to Contracting Authority, acting reasonably. For greater certainty, for all updates and revisions to the Project Works Schedules, Project Co must provide a revised critical path reflecting the updated or revised Baseline Works Schedule.
(b) Project Co shall use and interact with, and ensure that the Construction Contractor uses and interacts with, the On-line (web based) Project Management (“OCPM”) software system specified by Contracting Authority. It is contemplated that the OCPM software system will automate certain aspects of the processes identified in Schedule 10 – Review Procedure, Schedule 11 – –Quality Management, Schedule 22 – Variation Procedure and Schedule 33 – Works Report Requirements and other processes as determined by Contracting Authority in its sole discretion.
Appears in 1 contract
Samples: Project Agreement