Wednesday, November 30, 2016

Earned Value Management (EVM) Part 1



1. INTRODUCTION
Earned Value Management (EVM) is an industry standard method of measuring a project's progress at any given point in time, forecasting its completion date and final cost, and analyzing variances in the schedule and budget as the project proceeds. It compares the planned amount of work with what has actually been completed, to determine if the cost, schedule, and work accomplished are progressing in accordance with the plan. 
As work is completed, it is considered "earned". The Office of Management & Budget prescribed that EVM is required on construction projects.



Earned Value Management (EVM) is a snapshot in time, which can be used as a management tool as an early warning system to detect deficient or endangered progress. It ensures a clear definition of work prior to beginning that work. It provides an objective measure of accomplishments, and an early and accurate picture of the contract status. It can be as simple as tracking an elemental cost estimate breakdown as a design progresses from concept through to 100% construction documents, or it can be calculated and tracked using a series of mathematical formulae. In either case, it provides a basis for course correction. 
It answers two key questions:

  1. At the end of the project, is it likely that the cost will be less than, equal to or greater than the original estimate?
  2. Will the project likely be completed on time?


2. Work Breakdown Structure (WBS)


Earned Value Management (EVM) works most effectively when it is compartmentalized, i.e. when the project is broken down into an organized Work Breakdown Structure, or WBS. The WBS is used as the basic building block for the planning of the project. It is a product-oriented division of project tasks that ensures the entire Scope of Work is captured and allows for the integration of technical, schedule, and cost information. It breaks down all the work scope into appropriate elements for planning, budgeting, scheduling, cost accounting, work authorization, progress measuring, and management control. The indirect costs of design, oversight, and management must be included in the WBS to reflect the full budget.



3. Calculating Earned Value

Earned Value Management measures progress against a baseline. It involves calculating three key values for each activity in the WBS:

  1. The Planned Value (PV), (formerly known as the budgeted cost of work scheduled or BCWS)—that portion of the approved cost estimate planned to be spent on the given activity during a given period.
  2. The Actual Cost (AC), (formerly known as the actual cost of work performed or ACWP)—the total of the costs incurred in accomplishing work on the activity in a given period. This Actual Cost must correspond to whatever was budgeted for the Planned Value and the Earned Value (e.g. all labor, material, equipment, and indirect costs).
  3. The Earned Value (EV), (formerly known as the budget cost of work performed or BCWP)—the value of the work actually completed.

These three values are combined to determine at that point in time whether or not work is being accomplished as planned. The most commonly used measures are the cost variance:

Cost Variance (CV) = EV - AC

and the schedule variance:

Schedule Variance (SV) = EV - PV

These two values can be converted to efficiency indicators to reflect the cost and schedule performance of the project. The most commonly used cost-efficiency indicator is the cost performance index (CPI). It is calculated thus:

CPI = EV / AC

The sum of all individual EV budgets divided by the sum of all individual AC's is known as the cumulative CPI, and is generally used to forecast the cost to complete a project.

The schedule performance index (SPI), calculated thus:

SPI = EV / PV

is often used with the CPI to forecast overall project completion estimates.

A negative schedule variance (SV) calculated at a given point in time means the project is behind schedule, while a negative cost variance (CV) means the project is over budget.

Earned Value Management System (EVMS)


A list of guidelines is provided which covers areas such as planning, scheduling & budgeting; accounting issues; management reports, and so forth, however there are no "approved" systems identified. But the basics of any EVMS are:

  1. A methodical, organized, thorough, and complete WBS
  2. A baseline schedule
  3. A baseline budget, organized into control accounts
  4. Measurement of the work by control account (e.g. $, units in place, man-hours, etc.)

Scheduling the authorized work is no different than in any large construction project—it is a necessary activity for the success of the project. However in an EVMS the schedule will integrate all of the technical, cost, and schedule aspects of the work, resulting in the expected sequence of work. Interdependencies are established that result in the total work time and reveal the critical path, which is also the shortest project duration.


Within each task it is then necessary to identify objective interim measures to allow for accurate performance assessment each month. A sufficient number of these interim measures will be defined after the detailed schedule is established to ensure the performance is measured as accurately as possible.



On at least a monthly basis, generate schedule variance data that provide visibility into root causes and establish actions to achieve project completion. The first intent if this criterion is to establish the fact that analysis, to remain viable, must be accomplished on a regular, periodic basis. The second intent is to foster analyses and identification of root cause and resulting impacts at the control account level."

The monthly performance report must include:

  • BCWS, BCWP, ACWP
  • Cost Variance (CV)
  • Schedule Variance (SV)
  • SPI (Schedule Performance Index)
  • CPI (Cost performance Index)
  • Variance at Completion (VAR)
  • A variance analysis narrative



Tuesday, November 29, 2016

Plan Cost Management

1. Plan Cost Management

This process established the policies, procedures and documentation for planning, managing, expending and controlling project costs. The key benefit of this process is that it provides Guidance and Direction on how the project costs will be managed throughout the project.

The inputs, tools and techniques, and outputs of this process are described below.

1.1 Plan Cost Management: Input Phase
 This process requires the following inputs:

1.1.1 Project Management Plan
The following elements of the Project Management Plan are used:
  1. Scope Baseline
  2. Schedule Baseline
  3. Cost, Risk and Communications Management Plan
1.1.2 Project Charter
This  provides the summary budget from which detailed project cost are developed, as well as project approval requirement (particularly those dealing with project constrains).

1.1.3 Enterprise Environmental Factors
These include the organizational culture and structure, market conditions, currency ex-charge rates, commercial information such as cost rate information and published seller list prices.

1.1.4 Organizational Process Assets
These include financial control procedures, historical information and lessons learned from previous projects, as well as, cost estimating and budgeting-related policies, procedures and guidelines.

1.2 Plan Cost Management: Tools and Technique
There are three tools and techniques that can be used




1.2.1 Experts Judgement
This can involve any member of the project management plan may involve choosing strategic options to fund the project such as:
  1. Self funding
  2. Funding with equity
  3. Funding with Debt
The cost management plan may also details ways to finance project resources such as making, purchasing, renting or leasing. These decisions, like other financial decisions affecting the project, may affect project schedule and/or risk.




Organizational policies and procedures may influence which financial techniques are employed these decisions. Technique may include (but are not limited to): payback period, return on investment, internal rate of return, discounted cash flow, and net present value.

1.2.2 Meetings

These involve people who are responsible for cost management including the project manager, the project sponsors, selected project team members, selected stakeholders, anyone with responsibility for any of the cost management process, and others as needed.

Collective decision making is very important area of project management that the PMBOK (by PMI) does not go into any detail about which can make or break this part of the project. Almost all of the processes that for part of the project time management will involve meetings between the project manager, the team and others stakeholders in order to make decisions about the activity definitions and associated estimates. How well these meetings are conducted will have a major impact on how smoothly the project runs. 

1.3     Plan Cost Management:Outputs
This process will create the following output:

1.3.1  Cost Management Plan
The Cost Management Plan clearly defines how the costs on a project will be managed throughout the project's life cycle. It sets the format and standards by which the project costs are measured, reported and controlled.


This plan identifies who is responsible for managing costs and who has the authority to approve changes to the project or its budget. It also specifies how cost performance is quantitatively measured

and details reports formats, frequency and to whom they are presented.
The Work Breakdown Structures (W.B.S) is the basis for the cost management plan because the costs are totaled or rolled up from the costs for the individual work packages in the W.B.S.

Monday, November 28, 2016

WBS (Work Breakdown Structure)



1.1. Scopes

The Work Breakdown Structure (WBS) organizes and defines the total project work scope into a hierarchy of smaller and more manageable objects, down to the actual work task level, that can be scheduled, cost estimated, monitored, and controlled.

The WBS allows a hierarchical summation of costs, schedule and progress to allow Project Management practices to be applied consistently across the project.

The WBS allows work to be controlled at execution level while also providing consistent cost and schedule “roll up” to the sub projects and overall project. This “roll up” lets management understand the overall status of the project and provides information that supports decisions made to ensure that overall project objectives are achieved.

The WBS Key Procedure ensures consistent application and updating of the WBS as the project progresses.



1.1. WBS Development Process



  1. The Company Project Manager shall approve Basis of Design Documentation and develop Project Execution Plan as basis for developing WBS and assigning Codes of Accounts (COA).
  2. Based on approved Basis of Design and PEP Project Control Manager/Project Service Manager shall coordinate with Project Cost Control and Scheduler to develop WBS  and assign Codes of Account (COA)
  3. Project Cost Control shall validate and formalize SAP/Oracle COA interface.
  4. Project Manager shall approve WBS coding.
  5. Project Cost Control shall re-classify the Approved Budget into the WBS structure at the summary level.
  6. Project Control Manager and Project Cost Control will further breakdown the summary WBS/budget into the detailed project budget for Sub-Projects.
  7. Project Control Manager and Project Manager shall approve WBS/budget breakdown
 In case of potential WBS Deviation (Contract Strategy Changes, Execution Plan Changes, and Scope Adjustment) is recognized, Project Cost Specialist shall propose changes of WBS to the Project Control Manager. The Project Control Manager shall seek approval from the Project Manager.

1.2. Preparing a WBS

The Work Breakdown Structure (WBS) can be created new, or it can reuse components from other WBSs. When reusing existing components, WBS elements may be drawn from previous similar projects or from standard project templates that has been determined support accepted best practices.

The WBS evolves through an iterative consideration of the project’s purpose and objectives, functional/performance design criteria, project scope, technical performance requirements and other technical attributes. A high-level WBS can often be developed early in the conceptual stage of the project. Once the project is defined and specification are prepared, a more detailed WBS can be developed.

The following steps describe the general process for developing a WBS:
·       Step 1: Identify the final product(s) of the project – what must be delivered to achieve project success. A thorough review of high-level project scope documents (inputs such as statement of requirement (SOR), technical requirements documents, and so on) is recommended to ensure consistency between the WBS and the project requirements
·       Step 2: Define the product’s major deliverables, which are often predecessor deliverables necessary for the project, but that in themselves do not satisfy a business need (e.g. design specification)
·       Step 3: Decompose major deliverables to a level of detail appropriate for management and integrated control. These WBS elements normally tie to clear and discrete identification of stand-alone deliverable products.
·       Step 4: Review and refine the WBS until project stakeholders agree that project planning can be successfully completed and that execution and control will successfully produce the desired outcomes.

1.3. Establish Work Breakdown Structure

           1.3.1. General

a.   The overall WBS is split into two major components:
1)   The first component is to be used by the Company Project Management Team (PMT) and is used to roll up the work to the overall project, phase level and sub project level.
2)   The second component is to be used by the contractor(s) and breaks down the contractors’ work.
b.   The Contract Level (lowest level for the Company PMT and highest level for contractor(s)) is the level where the two intersect. This is the level where Company PMT will import the contractor’s work into Company PMT cost and schedule structures. TheProject shall ensure the overall project WBS is established for the project based on the following sections.
a.   Each WBS level is coded to obtain the WBS Oracle COA. The WBS Oracle COA should be defined by each Business Unit. The system allows 24 digits, and the mandated level of Standard Activity Breakdown shall be part of the WBS Oracle COA.
b.   If PMT decides to track the Component level, the WBS Oracle COA Mask may be required to have one digit for certain levels and/or dots.

1.3.2. WBS – First Component (to be used by the Company’s PMT)

This WBS is required through Level 4 (Work Type) with the Level 3 (Delivery Package) being optional.
(1.) Level 1 (Project Definition) – This is the highest level of the structure and shall be the level at which all project cost and schedule summaries shall be reported.
(2.) Level 2 (Delivery Area) - This shows the total project (delivery area) in more detail. Detail must be sufficient to distinguish between the concept and the options under consideration and describe the main interface and milestones. It shows management activities, such as old equipment procurement and permitting, in addition to the general scope. Example for this are:
§  Offshore / onshore
§  Local / abroad
§  Wells
§  Infrastructure
§  Owners
§  UAP
(3.) Level 3 (Delivery Package) – Sub-object is a further breakdown of Level 2 into more specific elements. Example for this are:
§  Topsides,
§  Substructure
§  Subsea /
§  Piles / Moorings
§  Submarine pipeline
§  Field production facility
(4.) Level 4 (Work Type) - further breakdowns of Level 3 are:
§  Engineering
§  Procurement
§  Fabrication
§  Construction
§  Transportation & Installation
§  Hook up & Commissioning
§  Surveying
§  General Support

1.3.3. Work – Second Component (to be used by the Contractors)

It is important to remember that Contractor participation in the project is not only during the EPCI execution, but also prior to that.

The Work Breakdown Structure developed for use by SINGLE CONTRACTOR consists of 5 levels as follows:
(1.) Level 0 (Contract) – This is the highest level of the structure that the Contractor(s) will roll up to. It will match either level 2 (Object Level) used by Company project teams depending on how the project was broken down.
(2.) Level 1 (Delivery Package) – This is a further breakdown of Level into more specific elements like the type of structure or facilities.
(3.) Level 2 (Work Type) – Engineering, Procurement, Fabrication, Construction, Installation, Commissioning, etc.
(4.) Level 3 (Discipline/Craft) - A further breakdown of Level 2 into engineering disciplines, construction, installation, and Hook Up & Commissioning crafts. Procurement is also broken down into major equipment groups and bulk material groups.
(5.) Level 4 (Deliverables) – Engineering deliverables, construction packages and a further breakdown of procurement. Further levels of the WBS are left up to the contractor(s) discretion and are the levels that the contractor shall use to control the project.
Levels 0, 1 and 2 are required; levels 3 & 4 are optional levels to be agreed between the Contractor(s) and the Company PMT.

The Work Breakdown Structure Developed for Use by MULTIPLE Contractors consists of Four (4) Levels as follows;

    •   Level 0 (Contract) – this is the highest level of the structure the contractor will roll up to. It will match either Level 3 (Sub Object) used by Company project teams depending on how the project was broken down.
    •   Level 1 (Work Type) – Engineering, Procurement, Fabrication, Construction, Installation, Commissioning, etc.
    •    Level 2 (Discipline/Craft) – A further breakdown of Level 1 into engineering disciplines, construction, installation, and Hook Up & Commissioning crafts. Procurement is also broken down into major equipment groups and bulk material groups.
    • Level 3 (Deliverables) – Engineering deliverables, construction packages and a further breakdown of procurement. Further levels of the WBS are left up to the contractor(s) discretion and are the levels that the contractor will use to control the project.