1. Interpretation of this Schedule



Similar documents
PN /16/ CRITICAL PATH METHOD PROGRESS SCHEDULE

MATERIALS: The Contractor shall provide the latest version of Primavera SureTrak software.

UNIFIED FACILITIES GUIDE SPECIFICATIONS ************************************************************************** SECTION TABLE OF CONTENTS

Chapter 9 Computer Scheduling Projects should be scheduled one byte at a time

MODEL SCHEDULING SPECIFICATION

763XXX Timing Analysis, Critical Path Method (CPM) Project Schedule

Memorandum. Jeff Jasper, P.E. Director, Division of Design. Technical Support TEBM, Division of Construction. From: Jeremiah Littleton, P.E.

Scheduling Glossary Activity. A component of work performed during the course of a project.

108-C-215 CRITICAL PATH METHOD SCHEDULE. (Revised )

Spec. Standard: 11/27/ Revision: 11/27/06

SECTION PROJECT PLANNING AND SCHEDULING PART 1: GENERAL 1.1 DEFINITIONS

EXHIBIT 2-2-C PROGRESS SCHEDULES

Alexandria National Cemetery SECTION NETWORK ANALYSIS SCHEDULE

UNIFIED FACILITIES GUIDE SPECIFICATIONS

Basic CPM Calculations

Table 2-1: Elements of the Project Management Plan

Region of Waterloo Stage 1 Light Rail Transit Project. Design and Construction Performance Output Specifications Article 19 Project Schedule

SECTION COST LOADED CRITICAL PATH SCHEDULE

USER CONVERSION P3, SURETRAK AND MICROSOFT PROJECT ASTA POWERPROJECT PAUL E HARRIS EASTWOOD HARRIS

Guidelines for Accessing and Using the VDOT Scheduling Application (Primavera P6)

Microsoft Project Professional

CRITICAL PATH METHOD (CPM) SCHEDULES

Software Project Management Fifth Edition

WORK PROGRAM GUIDELINES

powerproject 24 REASONS TO USE ASTA POWERPROJECT RATHER THAN PRIMAVERA FOR MANAGING CONSTRUCTION PROJECTS

Mastering Microsoft Project 2010

BOARD NOTICE COUNCIL FOR THE BUILT ENVIRONMENT. Notice No

SECTION a - CONSTRUCTION PROGRESS DOCUMENTATION

Project Management Guidelines

Test Fragen. October 2003 Project Management Wilhelm F. Neuhäuser IBM Corporation 2003

Agenda. CPM Scheduling at CDOT Laura Zamora, P.E. February 24, 2016

SPECIFICATIONS - DETAILED PROVISIONS Section Project Control Schedule C O N T E N T S

Project Management Glossary

CONTRACT MANAGEMENT FRAMEWORK

TRICKS AND TRAPS PRESENTATION

TABLE OF CONTENTS CHAPTER DESCRIPTION PAGE

MnDOT Project Management Office Presents: Schedule Float. Presenter: Jonathan McNatty, PSP Senior Schedule Consultant DRMcNatty & Associates, Inc.

NE-50413B Mastering Microsoft Project 2010

Collaborative Scheduling using the CPM Method

Schneps, Leila; Colmez, Coralie. Math on Trial : How Numbers Get Used and Abused in the Courtroom. New York, NY, USA: Basic Books, p i.

Importance of Project Schedules. matter what happens on a project. projects, especially during the second half of projects

8. COMPUTER TOOLS FOR PROJECT MANAGEMENT

IJSRD - International Journal for Scientific Research & Development Vol. 3, Issue 10, 2015 ISSN (online):

technical tips and tricks

CONSTRUCTION PROGRESS DOCUMENTATION (SCHEDULING)

SECTION CONSTRUCTION PROGRESS DOCUMENTATION PART 1 - GENERAL 1.1 RELATED DOCUMENTS

U.S. Department of Veterans Affairs. Facilities Management. Critical Path Method. Guidelines for Preparation of CPM Schedule Volume I

SCHEDULE 16. Exit Plan. sets out the strategy to be followed on the termination (including Partial Termination) or expiry of this Agreement; and

Oracle Primavera. P6 Resource Leveling Demo Script

Use project management tools

Chapter 6. (PMBOK Guide)

Test Fragen + Antworten. October 2004 Project Management Wilhelm F. Neuhäuser IBM Corporation 2003

Mastering Microsoft Project B; 3 days, Instructor-led

SOUTH FLORIDA WATER MANAGEMENT DISTRICT CONTRACTOR CPM SCHEDULE SUBMITTAL - DISTRICT REVIEW General Contractor CPM Schedule

Dashboards and Reporting for Program Management

DCMA 14-Point Assessment Metrics

Software Application: Information System Elements. Project Management in Information Technology (IT) Projects. Project Scheduling basics

Project Implementation Plan (PIP) User Guide

Project Control System Manual. Jefferson Science Associates, LLC. 600 Progress Status. Project Control System Manual Revision

PROJECT MANAGEMENT IN PRIMAVERA P6 WEB ACCESS REL 7

CALCULATION DIFFERENCES WHEN IMPORTING FROM INTO ORACLE PRIMAVERA P6 VERSION 7 PAUL E HARRIS EASTWOOD HARRIS

MnDOT Project Management Office Presents: Schedule Updates. Presenter: Eric Costantino Senior Schedule Consultant DRMcNatty & Associates, Inc.

Administration. Welcome to the Eastwood Harris Pty Ltd MICROSOFT PROJECT 2010 AND PMBOK GUIDE FOURTH EDITION training course presented by

MISSISSIPPI STATE UNIVERSITY Office of Planning Design and Construction Administration

SCHEDULE 3. Milestones and Deliverables. Redacted Version

Mastering Microsoft Project 2013

LONG INTERNATIONAL. Long International, Inc Whistling Elk Drive Littleton, CO (303) Fax: (303)

Microsoft Project 2010

Appendix A of Project Management. Appendix Table of Contents REFERENCES...761

S-1 (1803) PROGRESS SCHEDULES-CRITICAL PATH METHOD (CPM) The provisions of MnDOT 1803 are deleted and replaced with these Special Provisions.

Mastering Microsoft Project 2013 Course: 55054A Course Length: 3 Days

Template K Implementation Requirements Instructions for RFP Response RFP #

Scheduling Best Practices

Project Planning, Scheduling and Control: Assignment 2 D. U. Singer Hospital Products Corp.

Project Time Management

Egypt Scholars Presented by Mohamed Khalifa Hassan Jan 2014

Construction Project Scheduling: Keys to Success

Retained Fire Fighters Union. Introduction to PRINCE2 Project Management

MS Project Tutorial for Senior Design Using Microsoft Project to manage projects

Project Management Using Earned Value

Contents. iii. ix xi xi xi xiii xiii xiii xiv xv xvi xvii xix

Project Management Tools

The Amazing History of Primavera Software

Precedence Diagram Method. CSTM 462 Planning & Scheduling

Scheduling Best Practices. Proper Use of Milestones and Constraints By Paul Brough, Vice President of Warner s Scheduling Group

plans based on actual cost, schedule and technical progress of work [1, 9].

Errata. 133 Figure 5-15 Corrected the output for 8.3 Control Quality to read verified deliverables

CONVERTING TO AND FROM PRIMAVERA SURETRAK AND P3 TO MICROSOFT PROJECT MPX & MPP FORMAT PAUL E HARRIS EASTWOOD HARRIS. REVISED 4 August 2003

Rekoop Limited Standard Terms of Business

Develop Project Charter. Develop Project Management Plan

TECHNIQUES FOR MANAGING COMPLEX PROJECTS WITH PLANNING AND SCHEDULING SOFTWARE PAUL E HARRIS EASTWOOD HARRIS

Project Completion Report (PCR) User Guide

Chapter 2: Project Time Management

5. Creating a Gantt Chart

Designer & Builder Symposium Construction Scheduling. Glenn Saito NAVFAC Pacific Construction Division December 1, 2010

PROFESSIONAL SERVICES SPECIFICATION

Transcription:

Schedule 6 Programming Requirements 1. Interpretation of this Schedule 1.1 Primavera The following capitalised terms used in this Schedule 6 have the meanings given to them in the proprietary computer software known as Primavera P6 or higher Primavera Project Management software, produced by Primavera Systems, Inc: Activity; Activity ID; Actual Dates; Calendar; Constraint; Critical; Critical Path; Critical Path Network; Early; Float; Free; Lag; Late; Lead; Logic; Logic Link; Milestone; Network; Percent Complete; Planning Unit; Predecessor; Remaining Duration; Successor; and Total Float. 1

2. Works Program 2.1 Form of the Works Program The Works Program must be prepared in accordance with the detailed requirements set out in this Schedule 6 and otherwise in accordance with any other requirements reasonably requested by the State or the Independent Certifier. 2.2 Content of the Works Program The Works Program must: contain the information specified in and otherwise satisfy the requirements of Sections 2.3 to 2.5; identify all Project activities from the date of the Agreement to 12 Months after the Date of Stage 2 Commercial Acceptance including: (vi) (vii) (viii) all Project milestones; all activities that form part of the Design Development Process; all construction activities; the Transition Period; activities in respect of FF&E including selection, procurement, manufacture, installation, commissioning and testing; commissioning and testing generally; Project Co mobilisation in preparation for the provision of the Services upon the Operational Commencement Date; and activities in respect of the financing of the Project and all other material commercial arrangements, such as the provision of all parent company guarantees, timing for various tranches of financing and dates for Insurance Policy renewals; and provide any other information reasonably requested by the State and the Independent Certifier. 2.3 Construction activities The Works Program must identify and be a single point of reference for all construction activities that comprise the Works including: (construction activities): all construction activities (which must be grouped into activities and show a commencement and completion milestone for each of those activities); (Authorisation): any Authorisations which must be obtained prior to Stage 2 Commercial Acceptance or during the construction of the Works; (d) (Construction Sites): all Construction Sites establishment activities; (Remediation works): all Remediation works that are the responsibility of Project Co; 2

(e) (f) (adjacent projects and Adjacent Site): works that interface with adjacent projects and the Adjacent Sites; and (other information): all other information reasonably requested by the State. 2.4 Design Development Sub-Program The Works Program must contain a separately identifiable Design Development Sub-Program that is consistent with the current Design Development Plan and will be a single point of reference for all activities associated with the Design Development Process including: all activities that form part of the Design Development Process; the timing for: conducting the Design Development Process; all meetings with the Facility User Group; all Design Development Presentations; and the review of Design Packages by the State; and all other information concerning the Design Development Process reasonably requested by the State. 2.5 Completion activities The Works Program must relate to the Completion Plans and identify: (d) (e) commissioning and testing generally; the timing for the conduct of the Completion Tests; the timing for the conduct of the Outstanding Items; the timing for the conduct of all other activities which must be carried out as a precondition to Completion; and all other information concerning Completion reasonably requested by the State. 3. General requirements for the preparation of the Works Program 3.1 Software system Project Co must prepare the Works Program by using a recognised specialist proprietary programming computer software system which has been approved in advance by the State. Any references to the provision of an electronic copy of a document produced by computer software means an electronic copy of that document in the format of the software in which the document was originally created that has been configured to allow the person to whom the electronic copy is provided to access and amend the information contained therein in the same manner as could the original creator(s) of that document. 3

3.2 Bid Project Management Plan The Works Program must reflect the requirements of the bid Project Management Plan set out in Attachment 3 to the Agreement (Bid D&C Documents) and all subsequent revisions of the Project Management Plan. 3.3 Primavera and Microsoft software systems Without limiting the general nature of Section 3.1, the State approves the use of the proprietary computer software known as: Primavera P6 or higher Project Management software, produced by Primavera Systems, Inc; and "Microsoft Project" (2007), produced by Microsoft Corporation. 3.4 Form of Works Programs generally The Works Program must: (actual progress): at all times reflects the actual progress of the Works being undertaken; (clear and sufficient detail): be clear and sufficiently detailed for the State to easily identify: the Critical Path for the execution of the Works; the responsible party for each Activity and Milestone in connection with the delivery of the Works or pertaining to the Services; all Activities that involve the State, the State Associates or the Independent Certifier, including the date by which Project Co requests any review by the State (which must be consistent with the terms of the Agreement); all Activities or Milestones that are dependent on external third party events including the obtaining of approvals (Precursor Events); and the nature, time for completion of, and the identity of any third party responsible for completing each Precursor Event; (d) (e) (f) (g) (Milestone): contain a single overall start Milestone and a single overall finish Milestone; (Critical Path Network): be in the form of a Critical Path Network that enables the Critical Path to be calculated automatically by the computer software; (days as Planning Unit): use days as its Planning Unit (or such other period of time approved in writing by the State); (Calenders): contain Calendars which enable planned working and non-working periods in the future to be identified; (Activities Logically Linked): demonstrate that all the Activities in the programs, apart from the start and finish Milestones, are Logically Linked; 4

(h) (j) (labour resource histogram): provide a labour resource histogram that is consistent with the work depicted in the program. The labour histogram should be able to categorise the various trade resources and Project Co s own resources; (develop planned and actual resource s-curves): develop planned versus actual resource s-curves by phase; (Activities): clearly identify: (vi) Activities, their order, duration and interrelationship; the durations and Total Float of all Activities; if known, the impact, and the estimated potential impact of any delaying events or circumstances; all phases and sub-phases of each D&C Phase; the contingency allowed within the Works Program for potential delays; and any other matters which may have a material effect on the time required to complete the Works; (k) (l) (m) (staging and/or construction methodology): show the proposed staging and/or construction methodology of the Works; (other information): contain all other information reasonably requested by the State or Independent Certifier; and (prior State approval): not contain, without prior approval by the State: (vi) (vii) (viii) (ix) any Activities of durations of longer than 30 Business Days; any Constraints that fix the Early or Late start or finish dates of Activities or override the dates that would otherwise be calculated in accordance with Critical Path Network Logic (except for the overall start Milestone); any Lags that extend beyond more than 50% of the duration of the Predecessor Activity of the Lag; any Free Float Constraints or Total Float Constraints; any other programming Activities or methodologies which have the effect of creating false Criticality or constraining the program from reacting dynamically to changes; any Logic Links containing negative Lags (except where a negative Lag is used to indicate the time for an action by the State); more than 1200 Activities; Activities without finish Successors (except for the overall finish Milestone); or Activities without start Predecessors (except for the overall start Milestone). 5

4. Updating the Works Program 4.1 Timing for submission of updated Works Program Project Co must update and submit to the State and the Independent Certifier the Works Program: within 5 Business Days of Project Co being: granted an extension to any Date for Completion in accordance with Clause 16 of the Agreement or instructed to accelerate the Works in accordance with Clause 16.11 of the Agreement; or directed to carry out a Modification in accordance with Clause 34 of the Agreement; within 2 Business Days of Project Co deciding to make any material changes to the information contained in a Works Program; or no later than 5 Business Days prior to each meeting of the Management Team to reflect the changes to the progress of the Works being undertaken or any other changes to the activities, times, durations or other information contained in the Works Program to accurately reflect actual progress of the Works, provided that such updates must comply with this Schedule 6 and the other requirements of the Agreement and must not adjust any Date for Completion (unless an extension of time has been granted in accordance with the Agreement). 4.2 Submission of Works Program on request If requested by the State at any time, Project Co must within 5 Business Days submit to the State and the Independent Certifier the updated Works Program showing the actual status and progress of the Works as against the original baseline of the Works Program. 4.3 Content and format of updated Works Program Project Co must submit to the State and the Independent Certifier the updated Works Program in the following forms: 2 paper copies (which must be submitted on an A1 size sheet reduced to A3 and appropriately time scaled across the sheet so as to detail the sequence, duration and interaction of design, procurement, construction and commissioning); 1 electronic versions in.pdf format; and 3 electronic versions in original primavera xer file format. The updated Works Program must: clearly identify the Percent Complete and the Remaining Duration of each Activity; clearly identify the Activities that had started and which Activities had finished during the reporting period and the dates on which those Activities started and finished; be updated to the end of the previous reporting period using the software to record Actual Dates and the Percent Complete of Activities; 6

identify if Project Co will not achieve Completion until after any Date for Completion; and incorporate and display the version of the Works Program produced at the end of the previous reporting period as a baseline reflecting the actual status and progress of the Works. 4.4 Submission of report with any updated Works Program With each update of any Works Program, Project Co must submit to the State and the Independent Certifier a written report reconciling the updated Works Program with the version of the Works Program produced for the previous reporting period. The report referred to in paragraph must as a minimum: identify and explain for Activities that are on the Critical Path, the reason for any changes to: A. the duration of Activities since the previous reporting period; B. the presence or absence of Logic Links or their Leads or Lags; C. the presence or absence of program Activities or their Activity IDs; and D. the timing of Activities; summarise the material changes to any Activities that are not on the Critical Path; identify the estimated timing for the achievement of key Project stages including the completion of each of the design and construction stages and any Date for Completion; and contain any other information reasonably requested by the State or the Independent Certifier. 7