Professional Documents
Culture Documents
Scope of Effectiveness
PPL and its subsidiaries
Document BE–FW–VAF–001
Number
Revision History
Date Version Description
First Project Evaluation and Approval Process (PEAP) was approved by PPL Board of Directors, in its
meeting held on 14 May 2015, to formalize decision-making process for all the investments worth more
than PKR 500 million and divestitures having value greater than PKR 100 million.
This was applicable to both the PPL and Partner Operated Assets. In subsequent years, certain process
improvements, based on process learnings, were carried out through separate internal office
memorandums. However, process gap analyses carried out at different stages showed incoherence
among different PEAP aspects, approved process improvements and the associated business processes.
In July 2016, an internal memo to the MD/CEO was approved regarding Partners Operated Areas (POA),
where it was directed that PPL would not approve AFEs having PPL investment value greater than PKR 500
million without Gate Approval; however, budget would be approved with a caveat that project AFE would
be approved after full review and prior to start of work.
In November 2017, procedure regarding Authorization for Expenditure (AFE) was approved as a part of
the Control framework to create business value and minimize risk. This procedure set a limit of USD 50,000
for any work activity approved in the company budget to be endorsed through an AFE prior to work
initiation. Further, as an added control measure, any work costing above USD 5 million would have to go
through the Peer Review (or Value Assurance) process prior to AFE initiation.
PEAP or the value assurance process was reviewed for gap identification and improvements by ERM
Function with its observations & recommendations submitted to the Executive Committee in November
2018; lack of process ownership was identified as one of the process gaps. Through an inter-office
memorandum issued by MD on PEAP ownership, DMD (TS) was nominated as PEAP owner (responsible
for overall compliance of process and strengthening it by continuous improvements) and the Reservoir
Modelling department as the PEAP documents custodian.
Enterprise risk regarding Investment Authorization (inadequate due diligence resulting in undertaking
nonoptimal exploration and development projects) has been a part of Enterprise Risk Register since 2015-
16, and different risk response plans have been included over different fiscal years. Development of a
comprehensive Value Assurance Framework was first included in Risk Register in FY 2018–19, and since
then, efforts have been made in multiple phases to develop the same.
In 2020, ERM again undertook a detailed review of the existing value assurance process and gave a total
of 17 recommendations to optimize capital allocation, avert potential value losses, improve decision
quality, facilitate risk-informed decision making and achieve strategic alignment.
A detailed review of the industry’s best practices and applicable standards, carried out by Business
Excellence Function in year 2023, resulted in developing a unified Value Assurance Framework covering
all the unaddressed areas of the existing PEAP.
Aug 2023
APPROVED BY
Managing Director &
7 Imran Abbasy Chief Executive Officer
[MD/CEO]
f DEFINITIONS …………………………………………… 14
1 OVERVIEW …………………………………………… 17
1.1 Objective …………………………………………… 17
1.2 Projects & Assets Classification …………………………………………… 17
1.3 Scope of Application …………………………………………… 18
1.3.1 … Exceptions …………………………………………… 19
1.4 Purpose of the Document …………………………………………… 19
1.5 Relevant Codes, Standards, & Guidelines …………………………………………… 19
1.6 Internal References …………………………………………… 20
1.7 Supersedure …………………………………………… 21
1.8 Document Review Requirements …………………………………………… 21
1.9 Framework Rollout …………………………………………… 21
1.9.1 … Purpose of the Transition Period …………………………………………… 22
1.9.2 … Conclusion of the Transition Period …………………………………………… 22
Section A 26
New Projects in Existing Businesses
ANNEXURES 76
A DEFINITIONS …………………………………………… 77
A.1 Terms relating to ‘General Category’ …………………………………………… 77
A.2 Terms relating to ‘Organization / Companies’ …………………………………………… 77
A.3 Terms relating to ‘Management Systems’ …………………………………………… 78
A.4 Terms relating to ‘Project, Program and Portfolio …………………………………………… 78
Management’ and ‘Value Assurance Process’
A.5 Terms relating to ‘Risk Management’ …………………………………………… 80
For the purposes of this document, the terms and definitions that apply are included in the
Annexure A.
For the purposes of this document, the following terms and definitions apply.
1.1 OBJECTIVE
This document aims at developing a comprehensive framework for making or enabling effective
business decisions on investment and divestiture proposals and conducting Independent Gate
Reviews (IGRs) & Execution Progress Reviews (EPRs) for Exploration and other Capital Projects.
Implementation of this framework will reasonably ensure that the IGRs & EPRs for major projects
(as defined in the Section 1.2) are planned and conducted in a standardized and consistent way
throughout Company to improve decision making process.
PPL identifies and executes a significant number of high value projects in the pursuit of achieving
its business objectives, and it is imperative that the capital associated with these projects is
carefully managed to give the best possible outcome with the minimum of waste and rework.
This framework defines the requirements for corporate governance and management and the
delegation of authority (approvals mandate) in this regard.
The thresholds should be reviewed periodically (at the yearend after every 2 years) based on
Company’s market capitalization (in USD terms), investment capacity and other associated
factors.
• Investment threshold for projects’ review is defined as lower of (a) USD 5 million or (b)
1% of Company’s market capitalization (rounded off to the closest multiple of USD 5
million).
• Divestiture projects’ threshold will be 20% of the limit set for investments case.
Same thresholds should be referred to for initiation or requirement of Value Assurance process
in associated business processes, such as ‘Authorization for Expenditure (AFE)’.
• The entire Company including all the departments and PPL’s subsidiaries within Pakistan
or abroad (and their branch offices) together with its Joint Ventures.
• Equity investments in an associated (or Associate) company or Joint Venture where PPL
may or may not be the Operator.
• Associated companies, only when their Board of Directors concur to its adoption. For
Associate Companies, PPL should enforce procedural requirements, in case any approval
by the Associate Company goes beyond the approved investment limits.
Figure 1-1 below illustrates the overall management framework for Value Creation efforts in PPL.
FIGURE 1-1: Value Creation for PPL
Value Creation
for Company
• Projects may cover, but will not be limited to, Exploration, Appraisal, Development,
Facilities Engineering and Projects, Well Engineering and Well Operations.
• (Business Development) Opportunities may pertain to merger, acquisition, creation of
new entities or expansion in Core business (Exploration or Production assets) and/or
Diversification businesses.
The current version of VAF covers value creation opportunities within Existing Businesses, as
shown above in Figure 1-1). Business Development and Financial Investment opportunities will
be included in the scope of VAF, which will then be revised, based on process learnings post
implementation of the VAF.
1.3.1 Exceptions
Exceptions to the area of application of this document are:
(a) Projects falling under Corporate Social Responsibility (CSR) category, such as Community
development.
However, decision for the exception for projects falling within this class will be made by EBEC on
case basis after review.
• Provide governance framework for investment and divestiture value assurance related
activities,
• Identify the roles and responsibilities of the stakeholders involved in this process, and
• Provide reasonable assurance that with its implementation Company will be able to
allocate its Capital in the most optimized manner.
Category References
Standards, 1. Standard for Portfolio Management, PMI, third edition, 2013
Guidelines and 2. Standard for Program Management, PMI, fourth edition, 2017
Frameworks 3. Standard for Organizational Project Management, PMI, 2018
4. ISO 21500:2012 – Guidance on project management
Category References
5. BS 6079:2019 – Project management - Principles and guidance for the
management of projects
6. ISO 10006 – Quality management (in projects)
7. ISO 19008:2016 – Standard cost coding system for oil and gas production
and processing facilities
8. 18R–97 – Cost Estimate Classification System as applied in Engineering,
Procurement, and Construction for the Process Industries – Association
for the Advancement of Cost Engineering (AACE) International
9. Petroleum Resources Management System (PRMS) – 2022 Update
Rules & Regulations 10. Public Sector Companies (Corporate Governance) Rules, 2013
11. Public Procurement Regulatory Authority (PPRA) Ordinance, 2002
1.7 SUPERSEDURE
This document supersedes following corporate directives and other documents issued prior to
approval of this Framework.
TABLE 1-3: Supersedure
• Classification of the projects for deciding on the applicable value assurance process roadmap.
• Handling of documents related to the process and implementation of workflows in an
integrated information environment.
This Committee, made up of the decision makers, will be constituted for each project at each
tollgate. Committee will consist of up to a maximum of 7 members and the selection of the
members will be in accordance with project nature. Committee size must be an odd number.
DGRC will essentially be a multifunctional team, external to the project, charged with:
a) Reviewing the recommendations of the project team at each decision gate (as described
in Section 4) before these are passed to the next stage of the project.
b) Recommending a Proceed, Hold, Reframe or Kill decision at each decision gate for the
projects under review. Hold or Kill decisions may be targeted for review by MD; however,
DGRC must provide plausible explanation for such decisions.
For more details regarding Proceed, Hold, Reframe or Kill decisions, please refer to the Section f
– ‘Definitions’ and Section 6.1.2 – ‘Tollgate Decisions (Table 6-1).
Project information dossier should be submitted to the DGRC for pre-read, at least, five business
days prior to the Decision Gate meeting. After the Decision Gate meeting including presentation
of project information to the DGRC members, queries or additional information requests should
be raised by the DGRC within seven business days. DGRC will be required to finalize its Tollgate
decision within seven business days after receipt of complete information dossier.
5 7 7
business days business days business days
(at most)
Project Decision Gate Queries or Receipt of Tollgate
information meeting requests for complete project decision by
dossier additional information from DGRC
submitted to information raised Project Sponsor
DGRC by DGRC
Project execution will be reviewed by EPRC, which will be responsible for recommending the
need for course corrections, if any; however, responsibility for ensuring the achievement of the
project objectives will be Project Owner’s. EPRC review frequency is defined in the Section
6.2.4.2. To maintain consistency and accuracy of the review, the EPRC will remain same
EPRC will also review project risks and will recommend escalating any growing project risk to
higher management level for timely risk treatment, if needed. At the project end, DGRC and EPRC
will be responsible for recording of unbiased lessons learnt for future improvements.
EPRC will submit its review recommendations to the project team (Project Sponsor and Manager)
through Business Excellence Department. This will be required to ensure VA process trail for all
such reviews.
3
SECTION’S REVISION HISTORY
3.2 OBJECTIVES
This process seeks to achieve two main goals:
Project authorization will be that point in the project lifecycle where Company will
commit the majority of the project’s capital investment and contracts. FID will also be the
point where overall project risks should have been identified and sufficiently mitigated to
support project funding approval.
As described further below, FEL will start when the project idea is first conceived. After
the initial concept is organized into a project strategy, organized and collaborative
interaction and development will be required among the various project stakeholders to
create and assemble a project design-basis package suitable for subsequent
authorization, i.e., FID.
At the end of each phase, there will be decision gates or often called stage gates. These
decision gates have been formally established by PPL as the operating Company
authorizing or funding the project. These formal gates will allow for continuity across the
enterprise for authorization of additional funding for the next phase of engineering and
project definition. FID will follow Company corroboration that the project has achieved
or exceeded the minimum requirements for level of definition, risk exposure, capital cost,
investment rate of return, and execution planning.
Engineering, Procurement & Construction (EPC): This implementation stage of project
follows once the FEL is completed, and the most value-adding project design is achieved
In E&P industry (Operators and Contractors), these two major categories of activities are also
referred to as FEL and EPC projects for identification as project activities with separate nature.
Figure 3-1 illustrates the decision gates or stage gates for capital projects.
Figure 3-1 Objectives and key activities of the phases
Determine Generate and Finalize cost, Produce an Start-up, Plan for wind-
potential value select the scope, asset operate, evaluate down,
of the project preferred schedule and consistent with asset to ensure mothball or
and alignment project get the project scope, cost and performance dismantling
with the alternatives funded schedule specifications and disposal of
business and maximum asset, or
strategy return to strategic
stakeholders are farmout
achieved
ABANDONMENT
REVIEW &
INVITATION TO
RESPONSIBLE
BENEFITS
REALIZATION
TENDER
TENDER
E E
FEED-ID FID
= FEED investment = Final investment decision (FID)
decision (FEED-ID) = Authorization for expenditure (AFE)
= Sanction
Phase 6
3.3.1 PHASE 1 (FEL-1) – INITIATE Dispose
Phase 1 focuses on framing the goal. Project Sponsor or Initiator should look for key boundary
conditions; that are from a corporate financial perspective, a project perspective, or other key
stakeholders’ perspectives. This latter view is valuable when working in international
FEED Investment Decision (FEED-ID) will be taken at the end of Phase 2 ‘Select’ for the selected
alternative.
In this framework, end of the phase 3 ‘Define’ will be referred to as ‘Final Investment Decision’
(FID).
PHASE 6 OBJECTIVES
• Abandon the asset in a commercially, environmentally and socially responsible manner.
In continuation of the above section, it may please be noted that following alternate
terminologies are also used in the process industry for these project phases and may be used
interchangeably to refer to the same project phase.
Figure 3-2 Link between influence over costs and the project stage
For scenarios where the project cost escalates due to any unforeseen reasons or otherwise, the
causes of cost increases should be captured in the information package describing what went
wrong. Decision support package should include information regarding sunk cost, causes of cost
deviations against FID and lessons learned.
For Oil & Gas E&P business, there are primarily three main activity streams (each shown as a
separate row in the illustration):
• Exploration Business
• Exploration and Appraisal Activities
• Field Development
Sub-activities from each of these activity streams are mapped below against Tollgate process
phases.
Table 3–2 presents a synoptic view of all the business activities, information gathering & decision
requirements. This stage–gate process is aimed at helping decision makers reach to the best
course of action regarding the final decision of interest (well drilling, facility development, etc.).
For deciding the economic value associated with information gathering activities such as seismic
surveys, etc., “value of information” analysis will be required to determine if the proposed
information gathering activity for its given cost is worthwhile or not. Please refer to Annexure C
– “Value of Information (VoI) Analysis”.
Majority of these decisions involve expenditures that are CAPEX in nature; however, some of the
projects may be Special OPEX, such as production well workover, etc.
DISPOSE
Development Development
Program Project
Identify Select Define Drill the Handover Dispose
[Section A] the concept. project development to the asset
project: specifications well or Operations or
assess . Obtain FID. develop the execute
options. facility. strategic
farmouts
FEL EPC
DISPOSE
Diversification
Develop new Identify the Select Define Deliver the Handover Dispose
Diversification diversification investment concept project promise. to the asset
Program options specification Operations
business s. Obtain
[Section to be FID
included later]
DISPOSE
Figure 3-4 Mapping of typical Development Project activities on Tollgate process phases
Long lead item (LLI) is a term from supply chain management, which refers to those items (the
equipment, product or system) that have a lengthier procurement lead time of more than 12
months – as defined in PPL’s Procurement Manual – revision July 2016. Procurement lead time is
defined as the duration from the raising of purchase requisition (PR) to the required item
delivery.
Timely delivery of LLIs is vital for delivering the project on time. They need to be identified at the
earliest stage of a project to have a reasonably accurate estimate of the overall completion
timeline of the project.
No LLIs should be procured before any project (exploratory well, development well, etc.) passes
the FID approval stage (stage gate 3 – ‘DEFINE’). For projects with LLIs having very long lead times,
the project sponsor must arrange for the project’s FID approval well in time to initiate the
procurement process. Further, it must be noted that the requirement for gate review and value
assurance process roadmap will be decided based on the project’s challenge level (total
investment size and complexity level), not only the cost of LLIs that are a part of the overall
project costs.
Further, cost of contingent inventory item(s), which are purchased upfront should be accounted
for in the project economics (dry-hole branch of the project’s decision tree) during FID review
gate.
Any exception to the above, based on proper justification, such as a portfolio of wells with nearby
processing facilities, etc., will be approved by MD.
PPL Investment
Threshold
Low Medium High Class-1
Minor
>100
25 – <100
5 – <25
<5
Medium 13 – 20
Complexity levels of projects will initially be determined by Project Owner and reviewed by
Business Excellence to determine final complexity and assign the appropriate roadmap.
All the projects, minor or otherwise, should be classified accordingly by the VA process custodian
(Business Excellence function) before their proposals are presented before Budget Review
Committee (BRC) for capital allocation approval. It should be noted that the project classification
is not the only requirement for presenting any proposal before BRC, and governing corporate
document for financial budgeting and planning should be referred to for any other requirements.
Process custodian should also develop a mechanism to monitor changes in project classification
basis as the project progresses. One such critical point is tender or bids’ commercial evaluation
to see if the project investment does not cross the class threshold, which was selected earlier.
Such checks could be incorporated in Procurement Committee (PC) reviews.
The roadmaps are graded from a simple scope (1) to a full-scale toll gating process (3). This
defines the level of management control to be applied to the project.
The projects or opportunities should be screened at the Initiate gate to assess the applicable
roadmap. The number of decision points (independent gates reviews) for a project are defined
on the basis of project categorization according to the scheme illustrated below (Figure 4–2).
Class-3
HO
Projects
Class-2
Projects HO
Class-1
Projects HO
FEED-ID
Minor
HO
Projects
FEED-ID FID
GR – Gate Review
EPR – Execution Progress Review
PIR – Post Implementation
Review
For any roadmap, regardless of Decision Gate requirements, DOA approvals will be required for
every project phase. Instances, where decision gates are not required but management approvals
in line with DOA are still required, include FEED-ID for Class-1 and Minor Projects, and FID for
Minor Projects.
S
5.1 APPROVAL MATRIX
t
a
Following matrix (Figure 5-1) defines the approvers for corporate approvals required in the value
r
assurance process, i.e., voting rights in review committees’ different classes / gates.
t
The approvers change, as shown below, according to the project challenge level for each decision
gate or phase.
No decision gate approval No decision gate approval No decision gate approval No decision gate approval
Minor required. required. required. required.
The key customer is the project’s Decision Gate Review Committee (DGRC). DSP will also
summarize the work completed, the key decisions made, and the rationale for those decisions,
which are useful for purposes such as onboarding new DGRC members. DSP will be required for
all the phase-gate decisions that will be reviewed and made by DGRC.
Objective of these deliverables is to ensure that the highest quality of decisions is reached. DGRC
members may ask for more documents that could support them in improving the decision
quality. Project sponsor may request for waiver of any standard deliverable(s) from DGRC if there
is any appropriate justification available.
A simple and effective format will be to present the DSP in following sections:
1. An executive summary that clarifies the decision(s) the DSP is addressing and presents
the recommendations with key supporting reasons. This is typically no more than about
one page.
2. A list of supporting documentation and other deliverables for reference in case a reader
needs further information.
DSP content will vary from phase to phase and with the size and nature of the project.
Further, it should be noted that phase deliverable requirements, as mentioned in the next
sections, are meant to serve as indicative baseline to DGRC. The committee may ask for more or
less information depending on the project nature or type.
The decision will be made by the DGRC. In case of disagreement, decision of majority of the
members of the team will be carried forward. All findings or observations or action items arising
from the tollgate review must be resolved before the project could proceed to the next phase.
6.2.1.2 – Description
In FEL-1, the emphasis is to determine the basic economic viability of the conceptual project
before committing to more-definitive engineering and study expense. The FEL-1 phase will also
emphasize confirmation that the preferred conceptual process flow scheme and supporting
economics fulfill the business case that caused its initiation. This phase also will involve
determining the suitable site or short list of candidate sites for the project that have the best
combination of location attributes to best support the planned construction and operational
environment that will fulfill the project business drivers. For each candidate site, a conceptual
plot plan can be generated that will confirm the area requirements for processing units and
systems, area to support construction operations, and operations and maintenance activities
once the facility is operational. Once this work is defined adequately, generation of a
representative cost estimate and milestone schedule for the entire project is possible.
The emphasis in Phase–1 is on thinking widely, not deeply / in a very detailed manner. This
tollgate at the end marks the transition to Phase–2 for generating alternative project designs as
well as alternative projects / opportunities and selecting the best investment option at portfolio
level.
j) Scope & Constraints: What has already been decided or fixed for this project and what
are constraints?
Phase 1 DSP needs to provide the information to support these decisions and typically includes
the following:
• Project Initiation Note (or Project Charter) that would serve as opportunity framing
document. This should cover the following:
o Project Scope (project boundaries, potential project sites, block flow diagrams,
process schemes, etc.)
o Business assessment, including strategic fit checks for core and diversification
projects.
o Project assumptions and constraints
o Project success criteria
o Project risks
o List of internal and external stakeholders
o Preliminary Overall Plan (Level-1 EPC Project Schedule, as defined in Chapter 10)
o Preliminary economics based on Class-5 cost estimations. This should include a
reference case (Do Nothing scenario) which reflects the current operating plan for
the asset or business without the investment proposal (to correctly estimate the
value created by the investment proposal)
o A summary of the lessons gathered from relevant projects (such as analogs to
other assets)
o Preliminary Project Execution Plan (PEP) covering Staffing and resources (LLIs,
etc.)
For projects related to exploratory, appraisal and development wells, following may be needed:
In FEL-2, the emphasis regarding design of the project is on determining the best technical and
economic flow scheme, associated technology, and support systems required to provide the
necessary annual production rate at the sales quality required in case of gas processing facility /
minerals development projects. This is done after the generated options / alternatives are
assessed in detail against the possible outcomes under uncertainties (oil price, reservoir
performance, market trends for hydrocarbons/minerals, etc.).
One of the deliverables of this phase in case of an exploratory well is to take decision for
carrying out seismic survey; this is counterpart of FEED in case of a facility development project.
For projects related to exploratory, appraisal & development wells, following may be needed:
1. Description of block/field including geographical accessibility, lease status, license
management, work program commitment details, etc.
2. Infrastructure Map showing available gas processing facilities, compressors, gas pipeline
network, etc. to identify possible synergies.
3. Seismic Interpretation & Mapping (if already acquired)
4. Geological Review and Details
o Petroleum play concept with details
o Depositional setting of the area
o Petrophysical property used for estimating Hydrocarbon volumes should be
consistent and derived from analog or field data.
o Uncertainty ranges should be estimated from analog/ field data for allocating in
REP sheet.
5. Prospect Risking
o Chance of Success
o HC In-Place Volume estimations
6. Proposed Well location [coordinates at surface location and targeted depth]
o Subsurface Map with Coordinates (porosity & permeability maps etc.). Clearly
mention constraints if any.
o Surface location Map with coordinates
o Well Trajectory
7. Tentative Well construction design
8. Production Profile and Economic Evaluation based on Class-4 estimates
o Resources / Reserves and related Production Profile
o Assumptions related to Point of Delivery, compression and/or processing plant
requirements, Extended Well Testing requirement and equipment rentals,
o Planned cost for the project CAPEX and OPEX with cost breakup
9. A summary of economic assumptions for project execution (Petroleum Policy, Discount
Factor, Cost escalation/inflation criteria, Oil Price, Anticipated tax benefits etc.)
10. Yearly and Cumulative Cash Flow Profiles
6.2.3.2 – Description
In FEL-3, the emphasis is on achieving a “best practical” level of project definition that includes a
good-quality project estimate, schedule, and a detailed EPC phase project execution plan that
For projects related to exploratory, appraisal and development wells, following may be
needed:
Once this phase 4 is successfully completed, key role will move back to the Project Sponsor for
operating the newly developed asset and deliver the business value as envisaged.
The thinking during EXECUTE is all about delivering the promise and about preventing internal
and external factors having a negative impact on that promise. Execution Progress Reviews (EPRs)
are meant to identify the gaps between plan and execution and help with devising way forward.
During course of execution, EPRs will be focused on monitoring project’s progress using
techniques such as Earned Value Analysis (S-curves). It is important that review teams remind
themselves regularly that they are part of governance. EPRs should predominantly be forward
looking.
Requirement for calling EPR: It is the responsibility of Project Owner to call EPRs, which will be
called at the lapse of the 25%, 50% and 75% of the total Project execution time for facility
development project. In addition to the above, following conditions will require an EPR to be
called by Project Owner:
1. Cost variance of 10%.
2. Schedule variance of 10%.
3. Change in the original SOW.
4. Risk propinquity changes.
5. Significant quality issues found.
At current maturation level of the process, EPR will not be applicable to wells; however, the same
may be requested by Asset Owner if so needed.
At the end of this phase, the project or the asset will be handed over to the Operations team.
Before this handover, pre-startup audit review is a mandatory requirement to ensure that all the
systems have been successfully commissioned as designed and can be operated safely for the
design life of the project. This will be undertaken by Project Manager and is not included in the
scope of EPRC.
The deliverable at the end of Phase 4, will be the documentation to support the handover to
operations, to facilitate project lookbacks, and to close out the project. These documents do not
constitute a DSP; rather they meet specific EPC project management needs.
Figure 6-1 illustrates S-Curve that is used to assess the progress and performance of a project
through the use of Earned Value Management (EVM). S-curves are typically created as part of
EVM process and serve as the foundation for evaluating project's progress & performance.
• Planned Value (PV) refers to the amount (in monetary units) which is planned to be spent
on a certain percentage of planned project completion.
• Earned Value (EV) is the amount which was planned to be spent on a certain percentage
of actual project work performed.
• Actual Costs (AC) is the amount which is spent on work that is actually performed.
(Cost) Variance at
Completion (VAC)
Budget at Completion (BAC)
Forecasted
Schedule
Actual Costs (AC)
Slippage
Cost
Planned Value (PV) Variance CV = EV – AC
(CV)
Schedule SV = EV – PV
Variance (SV)
Earned Value (EV) CPI = EV / AC
SPI = EV / PV
EAC = BAC + VAC
Actual TCPI = (BAC – EV) ÷ (BAC – AC)
Schedule
Slippage
Project Completed A
Interim Closeout at
Is it a Yes Review Meeting
Commercial Production
Plant?
Commencement Stage • To be called once feedback is
received.
No
Final Closeout after
Performance Testing A
To be initiated by Asset Project Close Out
Phase 5 will also include continuous monitoring of project value delivery during asset operation,
i.e., post-investment reviews, to determine if the project objectives (NPV, etc.) are being
achieved or not. Such reviews could be linked with other associated activities, such as, risk
appetite testing for Capital Creation. This will be done by Asset owner at suitable intervals to be
determined in accordance with nature of the project.
6.2.5.3 – Review Questions for the Phase
a) Did the project achieve the predicted objectives and performance?
b) What can be learned from the project and what further opportunities are there?
6.2.6.2 – Description
Plan should be in place for socially and environmentally responsible abandonment of the asset.
This may include mothballing, relocation of the asset for use in some different business
application, sale of the asset at salvage value, etc. Project location should be restored in an
environmentally zero footprint manner.
For divestitures pertaining to strategic farmout, DISPOSE (or DIVESTITURE) decision gate will be
arranged for all the divestments above the threshold as described under Section 1.2, ‘Projects &
Assets Classification’. For exploration assets and undeveloped discovered / producing assets,
there is currently an approved procedure in place as listed under the section 1.6 ‘Internal
References’.
7.1 DEFINITION
This chapter serves to provide general guidelines on cost estimation. Project cost estimation is
the process of predicting the quantity, cost, and price of the resources required by the scope of
a project. Since cost estimation is about the prediction of costs rather than counting the actual
cost, a certain degree of uncertainty is involved.
This uncertainty arises from the fact that the project scope definition is never entirely complete
until the project has been finished, at which point all expenses have been made and an
accountant can determine the exact amount of money spent on resources.
7.2 REQUIREMENT
These cost estimates are required for investment decisions, comparing alternative plans,
budgeting, cost control, and validation.
Cost estimates are prepared at different stages throughout the project lifecycle. Upfront, the goal
is to provide input for investment decisions. The cost estimate is used to determine the size of
the required investment to create or modify assets. It is also during the early phases that
alternative plans are considered that need to be priced. The cost estimate is a deliverable that
serves the decision-making process at each gate of the project lifecycle.
Later in the project, the budget is determined from a more extensive cost estimate that also
serves as a baseline for project controls and earned value measurement. As such, it is maintained
up-to-date and in synchronization with the planned schedule. By comparing expenses and
progress information with the baseline estimate, an indication of the project’s performance is
obtained that allows the cost control and project management to steer the project.
Cost estimates are classified into different accuracy classes that are related with the maturity
level of project definition. Figures 7-1 and 7-2 illustrate the trend of cost estimate accuracies with
the increasing level of project scope definition as project phases progress.
Concept Concept
Detailed Tendering &
Feasibility Screening / Definition / FEED
FEED Operation Abandon
Design Construction
Selection Pre-FEED
ESTIMATES
Class 1
Class 2
Class 4
Class 5
Class 3
COST
FIGURE 7-2 Illustration of the Variability in Accuracy Ranges for Petroleum E&P Industry
Estimates
80% Confidence Interval Accuracy Range after inclusion of P50
This table presents standard cost estimate classification matrix. PPL may adjust this matrix to
reflect Company-specific impacts over time.
While the class estimates are defined on the basis of level of detailing, efforts should be made to
capture the expected cost variations due to market factors while preparing project estimates.
Table 7-3 below provide detailed descriptions of the five estimate classifications as applied in the
petroleum E&P industry. They are presented in the order of least-defined estimates to the most-
defined estimates.
TABLE 7-3 Characteristics of the estimate classes as applied in the petroleum E&P industry
(Reference: AACE Standard 18R-97 for Cost Estimate Classification System)
Estimate Description End Usage Estimating Alternate
Class Methodology Name(s)
Class 5 Class 5 estimates are generally Class 5 Class 5 estimates Preliminary
prepared based on very limited estimates are generally rely on economic
information, and subsequently have prepared for available internal and assessment,
wide accuracy ranges. Class 5 any number of industry data for similar geological study
estimates are generally based on strategic previous projects. Gross estimate, order of
unclarified contingent resources business unit costs may be magnitude
defined by preliminary exploration planning applied to drilling and estimate, capacity
drilling and appraisal and general purposes, such completion. Factoring factor estimate,
experience with related projects to as but not techniques may be used conceptual study,
comply with disclosure standards. This limited to to extend major facility venture analysis,
would include a simple geological market costs to include all scoping study,
model and estimated recovery and studies, equipment, preliminary
quality of products produced. A simple assessment of commodities, and gross evaluation.
drilling and completion plan is then initial viability, unit costs applied to
prepared that covers drilling method; evaluation of building volumes,
gross production schedules; nominal alternate pipeline, and other
facility capacity; assumed block flow schemes, elements. Cost/capacity
diagrams and process rates; and rough project methods may be used
conceptual definition of infrastructure screening, for some plant
needs. Substructure design concepts project elements. Indirect costs
are selected. There may be a location are factored from
minimum of coring work and studies, and directs based on internal
geotechnical, analogues or other back long-range and industry experience
up studies available. No design capital with typical cost ratios
drawings or equipment specifications planning. and other parametric
may be prepared beyond some rough and modeling
notes and sketches by the project techniques utilized.
engineer, perhaps little more than
proposed plant type, capacity and
location. Class 5 estimates, due to the
requirements of end use, may be
prepared within a very limited amount
of time and with little effort
expended— sometimes requiring less
than an hour to prepare.
Class 4 Class 4 estimates are generally Class 4 Major equipment costs Pre-feasibility or
prepared based on limited information estimates are are based on recent preliminary
and subsequently have fairly wide vitally budget prices from feasibility,
accuracy ranges. A Class 4 estimate is important to vendors using intermediate
usually carried out using development E&P investors preliminary economic study
8.1 DEFINITION
Project Schedule is a time, cost and resource control and management tool that identifies
activities for entire project with time scales, required budget and resources, and relations with
dependencies. The Project Schedule is a plan for completion of a project, list of planned activities
to be done within allowed timeframe, usually with intended start and finish dates that serves as
a tool to assist project management in achieving project goals through efficient use of available
resources.
8.2 LEVELS OF SCHEDULE
There are five (5) levels of Project Schedule as widely used in the E&P industry for projects
planning, monitoring, and reporting. As described below, increasing level corresponds to the
higher level of details and breakdown included for project activities, milestones, and deliverables.
The Master or Project Summary Schedule (Level 1) is typically one of the contract documents,
and the Control Level Schedule (Level 3) is one of the EPC project baseline documents.
• Organizing the continuous progress of the project risk management; coordinating with
Project Manager to plan and implement the risk management process
• Maintaining alignment across functional areas and organizing identification sessions,
assessment, qualitative/quantitative risk models and reporting
• Leading risk sessions and ensuring mapping of risks to Risk Owners
• Providing support to Risk Owners, as required
• Coordinating overall risk management team and monitoring effectiveness of the overall
risk management process
• Facilitating Risk Owners to update the risk register
• Ensuring lessons learned related to project risk are incorporated
The Project Risk Manager role can be undertaken by the Project Sponsor or Project Manager.
However, for very large projects, individual Risk Managers or Leaders can be assigned by the
Project Sponsor or Manager. The Risk Manager should report directly to the Project Manager in
order to ensure independence from any other function.
• Ensuring that risks are appropriately identified, analyzed, evaluated, and treated
• Ongoing assessment of consequences, likelihood and level of risk
• Developing risk mitigation plans and obtaining approvals and resources from the Project
Manager for their implementation
• Assigning an action owner to undertake the mitigating action, as required
The Risk Owner should generally be the relevant manager or team member responsible for the
area or discipline involving the risk.
Contractors are responsible for their own risk management and for participating in the risk
management process, including the effective implementation of the risk mitigation actions
assigned to them during ‘Execution’ phase.
9.4 RISK MANAGEMENT PROCESS
Project Risk Management will comprise of the following five steps. Please refer to the Corporate
ERM Framework for their detailed description.
• Risk preparation
• Risk identification
• Risk assessment
• Risk mitigation
• Risk monitoring, reporting and review
• Risk feedback
Projects value assurance process should be linked with the other related business processes, such
as long-term strategy setting, annual budgeting, etc. The lack of linkage between these processes
could potentially lead to a misalignment of the project objectives Company’s overall goals and
strategy, and result in wasted resources and failure in achieving the desired outcomes.
Company’s long term strategic plan, i.e., Five Year Plan (FYP), will be developed using the project
proposals based on class-5 cost estimates.
In initial rollout of VA process, project proposals will not need to go through any gate(s) of the
Value Assurance Process for inclusion in the strategic plan. The requirement will be determined
based on process learnings and included in VAF.
Flow chart for the approved Budgeting process, as documented in Accounting & Internal Control
Manual, is presented below in Figure 10-1.
While it is mandatory for PPL to not approve AFEs without tollgate process for large investments,
budget can be approved for planning but with a caveat that project AFE will only be approved
after full review and VA approval prior to start of work. In case of a facility development project,
an amount sufficient for carrying out FEED will be released by BRC and the rest kept as contingent
budget and released upon conclusion of the FEED and taking FID.
However, even for any project to be presented before Budget Review Committee (BRC) for
inclusion and approval as part of the budget, it is mandatory that it should pass the Initiate and
Select gates prior to BRC meeting. Following illustration, Figure 10-1, shows this sequence of
events.
Annual budget should be consistent with the project assumptions used in the projects value
assurance process. Any deviation from the approved assumption should be documented and
approved in the VA process as well.
In November 2017, procedure regarding Authorization for Expenditure (AFE) was approved as a
part of the Control framework to create business value and minimize risk. AFE management is
core to the function of all E&P companies and deals largely with the costing and budgetary
approvals.
This procedure set a limit on USD 50,000 for any work activity approved in Company budget to
be endorsed through an AFE prior to work initiation.
Further, as an added control measure, any work costing above USD 5 million (as per 2017 AFE
Procedure approval) would have to go through the Peer Review (or Value Assurance) process
prior to AFE initiation. However, this limit of USD 5 million must now conform to the investment
threshold defined in the Value Assurance Framework (VAF) for investments and divestitures.
Flow chart for the approved AFE process, presented below in Figure 10-2, illustrates its
connection with the Value Assurance business process.
2.01 Senior / Top Person or group of people who directs and controls an
Management organization at the highest level.
[Source: BS EN ISO 9000:2005, 3.2.7]
A.4 Terms relating to ‘Project, Program and Portfolio Management’ and ‘Value
Assurance Process’
4.02 Project Sponsor Person responsible for obtaining the resources and
executive decisions to enable success (of the project); in
other words, responsible for initiating, planning, and
budgeting the project.
[Source: ISO/TR 21506:2018, 3.78]
4.08 Time to Market the period of time between the project / opportunity
identification and startup.
4.09 Performance Tests Formal testing of the plant (or part of it) at the start of
operations to verify that the characteristics guaranteed
by the contract in terms of production capacity,
functionality, quality, limits and tolerances, etc. have
been met.
4.11 Final Acceptance Moment when the development (project) activities are
concluded, both in terms of completion of a project's
authorized scope of work and in terms of support to the
activities of the relevant operations functions.
4.12 Hold Decision To pause the proceedings of the project until (a) some
awaited information is received, or (b) the internal or
external environment for the project decision changes.
4.15 Project On Hold The project has not finished, and work on the project
has been temporarily suspended.
5.04 Financial Risk Effect of uncertainty on objectives that arises from the
effect of market forces on financial assets or liabilities,
and includes market, credit, price and liquidity risks.
5.05 Operational Risk Effect on uncertainty on objectives that arises from the
effect of people, processes, systems, or controls, and
includes people, IT, management oversight and
business processes risks.
5.06 Risk Assessment The overall process of risk identification, risk analysis
and risk evaluation.
5.09 Risk Matrix Tool for ranking and displaying risks by defining ranges
for consequence and likelihood
Acquiring information about uncertain events has value because it has the capacity to reduce
uncertainty (i.e., change our beliefs, as quantified by probability) and thereby change a decision.
This principle underlies the application of decision tree analysis to calculating the economic value
of information, i.e., how much one should pay for acquiring any piece of knowledge that could
potentially reduce uncertainty.
Decision makers, who face projects with uncertain outcomes, can address the uncertainty
impacting their decisions by gathering data and information with the intention of reducing
the uncertainty.
“Information” here in a broad sense refers to cover acquisition of data, performing technical
studies, hiring consultants, performing diagnostic tests, etc. Examples of gathering information
to reduce uncertainty include
• conducting a seismic study,
• coring a well,
• running a well-test analysis,
• consulting an expert,
• running logging surveys,
• doing a pilot flood,
• drilling additional appraisal wells,
• doing a reservoir simulation study, and
• learning from other fields, companies, or people.
The intuitive reason for gathering information is straightforward: If the information can reduce
uncertainty about future outcomes, decisions with better chances can be made for a good
outcome. In fact, the only other valid reason for information collection or technical analysis can
be to meet regulatory requirements.
However, such information gathering is often costly. Questions that arise include the following:
The fundamental question for any information-gathering process is whether or not the expected
reduction in uncertainty is worth the cost of obtaining the information. The Value of Information
(VoI) technique is designed to answer this question.
This decision analysis will help to distinguish between constructive and wasteful information
gathering. The purpose of a VoI calculation is to estimate the value of a proposed information-
gathering exercise so that the decision of whether or not to implement it is made on an economic
basis.
Bayes’ theorem is applied for updating probability estimates. VoI can then be applied as a means
of putting a value on this ability to gather new information and update probabilities. It can be
thought of as the value attributed to the updated probabilities. In calculating this value, the
following information is needed:
1. Current, or a priori, probability estimates of the possible outcomes the quantity can take.
2. Reliability (likelihood) estimates of the efficacy of the information in predicting the
outcomes.
3. Project values in monetary terms for each of the possible combinations of outcomes
1. Calculate the expected value of the decision to be made as it currently stands (i.e.,
without the information). This calculation will be termed as the value of the base project.
It is usually depicted using a decision tree.
2. Formulate the structure of the decision situation to include the new information. Start by
adding a new branch to the first node of the decision tree to represent the choice to
acquire information. This branch should lead to an uncertainty node, the uncertain event
This is the trickiest part of the procedure — To ensure that the decision situation has been
correctly formulated with the anticipated information included.
3. Calculate the Value of Perfect Information. This can be done either by inspection of the
decision tree in Step 2, or by entering 1 and 0 for the revised probabilities in Step 4. If the
expected value of perfect information (EVPI) is negligible, or less than the cost of acquiring
the information (if known at this stage), decide not to collect the information and choose
the highest-value alternative in the base project. Otherwise, proceed to Step 4.
4. Calculate the value of the project with the real, imperfect information. This step has the
following sub-steps:
a. Estimate the reliability (likelihood) probabilities—P (info says | real world is).
b. Calculate updated (posterior) probabilities for the outcomes.
c. Enter updated probabilities in the decision tree and solve for the project value.
D.1 BACKGROUND
All risks should be organized according to the Risk Breakdown Structure (RBS) in the Project’s Risk
Register.
The RBS reflects all stakeholders' perspectives and is structured to distinguish between risks
during all phases of the project. RBS allows a systematic way to distribute risks between the
various areas of the projects. RBS is common across all projects, and as a result allows project
risks to be consolidated in a common Risk Database, and then used as support for future projects.
Please refer to the next section D.2 for the table detailing RBS.
The list below is non-exhaustive, and additional items can be added in the future revisions of this
framework.
E.1 DEFINITION
Project charter is defined as “a document issued by the project initiator or sponsor that formally
authorizes the existence of a project and provides the project manager with the authority to
apply organizational resources to project activities.” The key word in this definition is “authority.”
It authorizes both the project and the project manager.
Following list mentions key information that the charter should provide, either directly or by
reference, including:
• Requirements
• Business needs
• Summary schedule
• Assumptions and constraints
• Business case, including return on investment
This section presents standard template for Project Charter that should be used as a part of Value
Assurance (VA) Process.
PROJECT CHARTER
Month - Year