This document describes the steps to calculate progress for an EPC project using Primavera P6.7. It includes:
1) Defining the work breakdown structure, activities, resources and costs to create a baseline schedule.
2) Weighting each project phase based on cost, with engineering weighted by man-hours. The phase weights are 10% for engineering, 20% for procurement, and 70% for construction.
3) Updating the schedule with a cut-off date, physical progress updates, and remaining durations to calculate earned value progress metrics.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100%(7)100% found this document useful (7 votes)
3K views
P6.7 - EPC Progress Calculation
This document describes the steps to calculate progress for an EPC project using Primavera P6.7. It includes:
1) Defining the work breakdown structure, activities, resources and costs to create a baseline schedule.
2) Weighting each project phase based on cost, with engineering weighted by man-hours. The phase weights are 10% for engineering, 20% for procurement, and 70% for construction.
3) Updating the schedule with a cut-off date, physical progress updates, and remaining durations to calculate earned value progress metrics.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11
Gustavo Paolini
Using Primavera P6.7 - Technical Notes
12/10/2010 Page 1 of 11 Good Day
Introduction This is an exercise to calculate progress based on Client requirements for a typical EPC Project. Data used on this sample are referential and were created just for better understanding of this Progress Calculation exercise. This is open to anybody for comment or improvements.
Client Requirements
An EPC Project is required to be scheduled and follow up each of its phase and based on these following requirements:
1. Project must start on Nov 1rst 2010 and must be done in 200 working days 2. Working Time will be 8h/d; 40 hours a week (Standard Calendar to make simple the exercise) 3. Phases must be weighted on cost except Engineering phase which will be weighted on man-hours to be expended (Effort) 4. Resources and Cost have to be established for all phases 5. The Weights of each Project phase must be: a. Engineering Design = 10% b. Procurement = 20% c. Construction = 70% 6. Schedule must show Progress Earned Values against Planned Progress Values 7. Schedule must show also a Graphical Baseline to evaluate future Project Performance and targets achievements 8. Progress figures to be reported are Physical and Earned Values 9. For Forecasting: Task endings dates will be given by using remaining durations
Note: The main purpose of this exercise is to show Progress Calculations. So, no actual values on resources and cost expenditure are being given
Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 2 of 11 Execution by steps: Figure 01 1. Define WBS, Activities, Resources and Cost (CTR) 2. Create Baseline
Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 3 of 11
WBS
Figure 02
GROUP & SORT
Figure 03 Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 4 of 11
Detail of Original Plan after assigning resources and cost
Figure 04 Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 5 of 11 3. Weight Assignment a) Create three new user defined fields (Enterprise\User Defined Fields) given the following titles:
% Progress Earn Value Planned % Complete Weight
Figure 05 Note: Once are created show them as on Figure 04 - Last 3 columns
b) Using Global Change (Tool\Global Change) create the following changes for each phase:
ENGINEERING PHASE Note: Parameter/value number which divides BLU comes from Figure 04 (BLU Column) Weight for Engineering = 10%
Figure 06
Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 6 of 11
PROCUREMENT PHASE Note: Parameter/value number which divides BTC comes from Figure 04 (BTC Column) Weight for Construction = 20%
Figure 07
CONSTRUCTION PHASE Note: Parameter/value number which divides BTC comes from Figure 04 (BTC Column) Weight for Construction = 70%
Figure 08
Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 7 of 11 c) Apply Global Changes one by one and then we will get the committed changes or weights:
Engineering = 10% Procurement = 20% Construction = 70% Figure 09 Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 8 of 11 4. Update the Schedule for: Figure 10 Cut Off date = February 1rst 2011 (Data Date) Give % Physical Progress And Remaining Durations
Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 9 of 11 5. Create and apply a Global Change to calculate % Progress Earn Value and % Planned Progress
Figure 11 Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 10 of 11 6. Check Progress results
Figure 12 Gustavo Paolini Using Primavera P6.7 - Technical Notes 12/10/2010 Page 11 of 11
FINAL COMMENTS:
1. If all the phases were weighted on cost only two global changes should be made 2. Usually weights are being frozen by the client before project stars therefore the Global Changes which calculate activity weights are being applied or done only one time 3. If there is any changes that affect Budgeted Labor Units (BLU) or Cost, weights have to be re calculated using again the Global Changes made for that purpose ( Advice: Always check the GC parameters/values field and update these values with those originated by the new changes to make sure you are weighting activities properly) 4. Every time the schedule is updated base on physical progress and remaining durations it is required to re calculate progress values by applying last Global change made for it (GC No. 4) 5. Weights can be calculate out of Primavera for example in Ms Excel and can be added to the Weight Column manually or using Primavera to import them from Excel Spreadsheet 6. Feel free to make any comments or suggestions
Additional information about this Project used as a sample