17 Key Features of Epcm and Delivery Partner Models
17 Key Features of Epcm and Delivery Partner Models
delivery models
Engineering, Procurement
and Construction
www.pwc.com.au
Key features of EPCM and
Delivery Partner Models
1.1 Introduction
Summary of key takeaways
Over the course of PwC’s experience working with clients
• There is no ‘one size fits all approach’ or definition of on large scale public infrastructure projects, it has become
the Engineering, Procurement and Construction apparent that there are significant differences in the
Management project delivery model (EPCM Model) application and understanding of both the EPCM and
and Delivery Partner Models. Both models are Delivery Partner Models. Rather than reporting on the
adaptable depending on client and project sometimes contradictory views, this paper provides a
requirements. description and discusses the application of the models,
• Neither model replaces traditional contracting incorporating PwC’s experience and observations in the
approaches for individual packages such as PPP, application of the models.
Alliance or D&C but rather supplements the risk It is also apparent from PwC’s experience that:
allocation achieved under the contracting
approaches with additional design development and • other than identified differences in the level of
a disaggregated, progressive approach to project accountability
packaging and procurement.
• the extent of self-performance of design
• The drivers for appointing an EPCM/Delivery Partner
the key features and drivers for using the EPCM and
vary in line with client and project specific
Delivery Partner Models are largely the same. Accordingly,
requirements and each client’s core business and
except where the context requires the models to be
level of experience and expertise in project delivery.
distinguished, this section uses the terms ‘EPCM/Delivery
• While EPCM/Delivery Partner means different Partner Models’ and ‘EPCM/Delivery Partner’
things to different market participants, commonly interchangeably. This paper is prepared on the basis that
accepted hallmarks of the EPCM/Delivery Partner the client is the project Principal.
approach are:
1.2 Overview of the EPCM/Delivery
– access to an additional pool of highly specialised
project delivery resources
Partner Models
– stage gated engagement across the project A recurrent theme from PwC’s industry experience is that
lifecycle there is no precise or universally accepted definition of
EPCM Model or Delivery Partner Model. The definition of
– detailed scope development prior to investment each model varies from project to project depending on
decision and going to market the project characteristics, delivery requirements and
resourcing needs of the client.
– end-to-end procurement and project delivery
focus based on overall critical path to completion The EPCM Model is a project delivery and client-side
resourcing approach for complex mega projects. It has
– application of accountability and incentive
been used extensively in the oil and gas, petrochemical
mechanisms
and mining and resources industries. The model is centred
– a disaggregated, more granular packaging on the staged engagement of a multi-disciplinary
approach to project delivery organisation (EPCM Partner) throughout the project
lifecycle under a professional services agreement. The
– enhanced management of client risk including EPCM Partner provides specialist project delivery
integration risk resources (including personnel, systems and processes)
– application of specialised systems and processes for the project engineering, procurement and construction
which span the project lifecycle. management interface and coordination functions.
Under both the EPCM and Delivery Partner Models, the • overall project and construction management, including
client adopts a disaggregated project procurement interface coordination and claims management.
strategy. With the assistance of the additional Further examples of typical EPCM/Delivery Partner
EPCM/Delivery Partner resources, the client activities over the project lifecycle are outlined in Section
disaggregates, and progressively procures the project 1.11. The scope of services and EPCM/Delivery Partner
scope with multiple Contractors and suppliers under accountability varies and is tailored for each project based
separate packages and potentially different delivery on a range of factors. These are discussed in further
models. This is opposed to a single point of responsibility detail below.
procurement approach where the client engages one
entity (or a consortium) under a single contractual 1.3 Integration with traditional
arrangement to deliver the entire project scope, creating a contracting and procurement
contractual layer and separation between the client and
the rest of the construction supply chain. approaches
The EPCM/Delivery Partner Model does not replace
The disaggregated procurement approach is traditional contracting and procurement approaches, such
predominantly selected where the scale of the as Construct Only, Design and Construct (D&C), Supply
project, combined with contracting market capacity and Install (S&I), Engineering, Procurement and
constraints and competition issues, preclude Construction (EPC), Public Private Partnerships (PPPs) or
procurement of the entire project scope under Alliance Contracting.
one package. Rather, the EPCM/Delivery Partner Model facilitates and
enables the appropriate use of traditional contracting and
procurement approaches for the various work packages
The disaggregated procurement approach is under a disaggregated project package structure.
predominantly selected where the scale of the project,
combined with contracting market capacity constraints and In the private sector, clients and EPCM/Delivery Partners
competition issues, preclude procurement of the entire have traditionally relied more upon Construct Only, D&C,
project scope under one package. However, S&I and EPC approaches for the procurement of those
disaggregation results in an increase in complexity works packages.
(particularly in respect of interface coordination) and client An example EPCM Model contractual framework diagram
retained risk to be managed. The EPCM/Delivery Partner for the delivery of a large, complex mine expansion, deep
is typically engaged by the client to manage these water port and heavy haul rail project in the private sector,
resultant factors by supplementing its internal project where these models have been extensively used in the
delivery capability and capacity with additional specialist past, is illustrated in Figure 1.
project delivery resources.
It shows the indicative project participants and contractual
EPCM/Delivery Partners are often engaged early in the relationships, together with the work packages for the
project feasibility analysis and early planning stage and main project scope components and contracting and
provide services for the remainder of the project lifecycle procurement approaches for each package. It also
on a staged engagement basis. In most instances, the illustrates how the EPCM Model incorporates multiple
client will have the option to end the engagement at key interfacing work packages.
project decision points which are aligned (such as the
outcomes of project feasibility studies or external finance
credit approval).
Finance
Sponsors
Guarantees
Mine, Port and Rail
Operators
Joint Venture
O&M
Agreements
Agreements Coordination of
Design, Construction
& Handover Inputs/
Finance Project Requirements
Lenders
Agreements Company
Train Unloading/
Crusher & Rail Overpass
Materials
Interface Agreements
Conveyors (DS&I) Bridges (D&C)
Handling (DS&I)
Coordination &
Track Laying
Process Plant (EPC) Wharf (D&C)
(Construct Only)
Signals &
Train Loading
Ship Loader (DS&I) Communications
Facilities (DS&I)
(DS&I)
Rolling Stock
(DSI&M)
In the public sector, clients and EPCM/Delivery Partners have relied upon a combination of multiple interfacing work
packages for separate contracting and procurement and, increasingly, PPP and Alliance approaches for the procurement of
major works packages (e.g. rolling stock). For example, each of Crossrail, Sydney Metro and, we understand, Western
Sydney Airport have adopted both PPP and Alliance contracting and procurement approaches for certain packages.
An example EPCM/Delivery Partner Model contractual framework diagram for the delivery of a mega transport project,
incorporating some of the traditional contracting approaches used by public sector clients, is illustrated Figure 2.
Franchise/ Franchisee/
State concession Operator
Agreement
Enabling Coordination of
Legislation Design, Construction &
Handover Inputs/
Requirements
Coordination &
Interface Agreements
Subcontract and supply Subcontract and supply Subcontract and supply Subcontract and supply
agreements agreements agreements agreements
Re
EPCM/Delivery
Partner Model
Pro ustry ,
t Ty &
Ind ation
Co
pe
Ris lexi
jec
be managed influences
While the detailed application and structure of the EPCM/Delivery Partner Model varies, there are a number of key features
that appear across mega projects. These are described in Table 1.
Feature Description
Engagement of • Rapid deployment of multi-disciplinary project resources drawn from a global employee pool
external that transfers from project to project and between different countries and regions based on
engineering and engagements.
project delivery
• Still requires integration with local subject matter expert and operations/maintenance
resources across
resources for certain project scope elements or location and industry specific requirements
the project
and nuisances.
lifecycle
• EPCM/Delivery Partner commonly brings proprietary and other project delivery processes and
systems which incorporate lessons learned from accumulated experience in project delivery
over many years. To a degree, these processes and systems can be tailored to integrate with
existing client systems and processes.
• Clients retain overall decision making and leadership control and continue to directly employ
and engage resources to perform project delivery functions that the client is better placed to
manage (i.e. planning and regulatory approvals, financial and legal advisory functions,
stakeholder negotiations etc).
Staged • EPCM/Delivery Partner engagement terms typically include progressive award of scope and
engagement commencements of services aligned to the client’s investment approval stage gates (with the
aligned to client’s client having the option to end the engagement at each gateway).
investment
• EPCM/Delivery Partner’s level of accountability and extent of commercial incentives increases
approval stage
as its engagement progresses through each stage gate.
gates
Staged • EPCM/Delivery Partner Model is typically only used on large complex projects where
procurement disaggregation of the project scope into multiple packages is unavoidable due to resourcing,
throughout the material supplier and contracting market competition constraints.
project
• Increased complexity and volume of work arises from having multiple packages and interfaces,
as opposed to contracting with one party for the entire scope.
• EPCM/Delivery Partner acts as the client’s representative while the client retains overall
accountability for the end-to-end integration and delivery of a project.
• Client retains overall project delivery accountability and control throughout the project lifecycle
rather than handing over accountability and transferring risk for project implementation to
another party.
• EPCM/Delivery Partner Model approach seeks opportunities to further disaggregate project
scope (either horizontally or vertically) and optimise work package sizes during FEED
development and procurement to align with Contractor specialisations and to maximise
Contractor and supply competition and broaden resource capability and capacity.
Developed scope • Client investment parameters and/or financier requirements generally dictate more advanced
and design prior scope development (i.e. in the order of 20-40% design development) to support the capital
to investment cost and programme estimates underpinning the investment decision.
decision and
• The scope development and FEED process incorporate constructability assessments,
going to market
operations and maintenance and procurement analysis from the outset and throughout the
design process to inform and optimise the design and engineering solutions and reduce risk of
scope creep in later stages of the project.
• Typically, more developed designs (for example issued for construction) are developed prior to
going to market. This is with a view to paying less upfront risk premiums to Contractors and
seeking to derive more value from progressive allocation of risk to the contracting market as
the design matures (i.e., rather than transferring risk to a Contractor at an earlier stage of
design development when scope is more uncertain and risks are less defined).
Feature Description
End-to-end • As the project is not delivered under one package with risk transferred to a single contracting
procurement and entity, there is a shift in focus from managing a single transaction and contracting entity to
project delivery managing multiple packages and interfaces and counterparties.
focus based on
• Resources, activities and procurement are allocated and prioritised based on the critical path
overall critical
to completion of the project rather than achievement of transaction milestones.
path to completion
• An EPCM/Delivery Partner is typically engaged from early in the project lifecycle and is
required to adopt an end-to-end project focus and incentivised to assist the client to achieve
whole-of-life project objectives, rather than a focus on achieving specific transaction
milestones (i.e. contractual or financial close).
Staged • The scope and procurement approach for each work package is identified in the project work
procurement of package breakdown structure. This remains a live document and is updated if required to
work packages respond to programme updates or market sounding and tender responses.
• Work package scope and battery limits are determined based on a combination of factors
including:
– the critical path to project completion i.e. the procurement of project scope is broken down
and prioritised based on what is needed to achieve overall project completion milestones
– maximising the pool of available Contractor resources for delivery and creating appropriate
levels of competition
– the number of other projects competing for resources at the same time and manufacturing
and materials availability.
• The drivers must be balanced against the client’s appetite for interface risk and financier
requirements for bundling of packages to reduce dilution of performance and completion
guarantees underpinning the project finance arrangements.
• The FEED process continues throughout the procurement phase to avoid gaps in scope and
ensure end-to-end design and system integration between work packages. A disciplined
approach to change management is required to ensure ongoing design changes are minimised
and scope creep that doesn’t deliver the required return on investment hurdle
rate is avoided.
Risk allocation • EPCM/Delivery Partners do not take overall project completion or performance risk which is
and incentive typical for professional services and project management arrangements.
mechanisms
• EPCM/Delivery Partners are generally incentivised by having a component of their fees and/or
bonuses at risk, aligned to achievement of project objectives. The extent of incentivisation and
skin in the game varies for each engagement. It is a point of distinction from standard technical
adviser and project manager engagements which are often only based on reimbursable fee for
services arrangements.
• Incentive regimes usually incorporate both behavioural and harder project outcomes based
Key Responsibility Areas (KRAs) and Key Performance Indicators (KPIs), assessed on both a
rolling and end of project basis.
• Extent of the EPCM/Delivery Partner risk and ‘skin in the game’ is influenced by the extent of
the role and fees to be generated and the level of accountability and ability to influence
project outcomes.
The EPCM/Delivery Partner ‘heavy’ approach outlined above is generally only adopted by clients where project delivery is
not their core business and their preference is to outsource the majority of the project delivery function rather than develop
in-house capability. This is most commonly the case in the oil and gas, petrochemical and mining and resources sectors.
The ‘heavy’ approach is not typically used where a client actively participates in project delivery and has a track-record in
delivering major projects with sophisticated project delivery frameworks and in-house capability. In those circumstances, the
client is more informed and better placed to take an active role and lead the project because it has delivered similar projects
before and can draw on proven success factors and lessons learned from those projects.
Chevron, Roads and Maritime Services, Crossrail and Sydney Metro demonstrate that even active project developers with
sophisticated internal project delivery capability see value in engaging an EPCM/Delivery Partner under a ‘light’ approach.
This is particularly in relation to accessing additional specialised resources to enhance or supercharge existing internal
capability and capacity for certain functions or in jurisdictions where the client has not previously delivered projects. Those
entities recognise there is a commercial trade-off between retaining overall project delivery control and authority and the
extent to which the entity can allocate risk of not achieving project objectives to the EPCM/Delivery Partner.
Commercial terms Typically employed on a ‘Fee for Long term contract with KPI regime tied to
of engagement Service’ basis. specific project outcomes including:
• Accuracy of cost estimates
• Adherence to planning requirements
• Staff retention
• Organisational/cultural cohesion
Ongoing commercial tension throughout project
lifecycle provided from stage gates, and the
Principal’s prerogative to expand or diminish
Delivery Partner’s role.
Market conditions Very high quality pool of existing resources. Limited existing Delivery Partner presence in
However, scale of current infrastructure Victorian civil infrastructure market. However
Programme means this market is at or deep pool of available expertise and
over capacity. appetite from:
• International DP/EPCM firms
• Resources currently working in other
sectors (mining/petrochemicals)
• Technical Advisers looking to scale up into
DP/EPCM Contractors
Resource Technical design and engineering expertise Ability to rapidly scale up DP capability using
mobilisation deployed in response to discrete tasks as international resources, including access to
procured by delivery authority. highly specialised technical skills.
Limited capability in procurement and
construction management.
Resource Ability to incentivise retention of key resources Can incentivise retention of key resources over
retention limited by ‘fee for service’ nature of contract. the project lifecycle through DP contract.
Design risk Varies depending on procurement method Design risk stays with the Principal, but allows
adopted. On PPP project, transferred to private cost control through value engineering and
sector through tender process. refinement throughout project delivery.
Procurement First major procurement milestones occur with First major procurement milestones occur
milestones tending and award of primary D&C/PPP during development phase, with appointment of
package(s). Delivery Partner.
Thin/passive • Delivery of projects is not the 1. Small or mid-cap mining company with extensive
client driver client’s core business or the client in-house exploration and mining expertise but limited
otherwise wants to retain a thin mining infrastructure delivery experience. Only has
organisational structure and one project with investment approval and does not
outsource the majority of the want to develop internal project delivery capability. Is
project delivery functions. also open to divesting interest in the project as it
progresses and is de-risked and wants to maintain
• Client does not see value in
minimal permanent overheads and to outsource
investing in developing its own
project delivery to an EPCM/Delivery Partner.
project delivery systems and
processes for one project and 2. Special purpose organisation or project vehicle
wants to leverage an established solely for the purpose of delivering one
EPCM/Delivery Partner’s purpose project. With a finite purpose and duration, the
built project delivery systems client’s preference is to only directly retain a number
and processes. of key personnel and outsource the balance of the
project delivery functions to an EPCM/
Delivery Partner.
Client-side • Booming market conditions with a 1. Mining company seeking to deliver a project during
resource large number of competing existing the mining boom. Is not able to recruit and retain the
constraints in projects and project in the pipeline. necessary resources to deliver its project by target
heated market deadlines. The resultant project delivery delays and
• Client needs rapid access to an
extended time frames risk the overall project viability
additional pool of client-side
as the client will lose sales if it is not able to
resources to properly staff its
complete the project and deliver ore earlier to
project and wants to leverage an
customers. Despite paying a premium it elects to
EPCM/Delivery Partner’s
engage an EPCM/Delivery Partner on the basis it
established network of existing
can rapidly deploy the necessary resources within
resources and expertise.
required timeframes.
2. Client has a number of large projects to deliver in
parallel. It has extensive internal project delivery
capability and experience. However, the scale,
complexity and number of parallel projects has
exhausted internal capacity. Rather than defer the
project until other projects are completed and
resources become available, the client elects to
engage an EPCM/Delivery Partner to assist it to
deliver one of its projects under the direction of a
client project leadership team.
Larger more • Client is forced to split the project 1. The project value is greater than AUD10 billion and
complex projects scope into a number in response to is too big even for a consortium of large Contractors
with greater specialised technology needed to wrap the delivery. Client also wants to restrict joint
disaggregation and/or contracting market venture arrangements to maintain competition. The
required constraints and competition issues. client is forced to split project scope into a large
number of smaller packages resulting in more
client-side work and resources required to manage
additional complexity and risks. Client has internal
project delivery capability and experience in
delivering projects of less than AUD3 billion in value
and wants to supplement that expertise with
additional EPCM/Delivery Partner resources with
complex mega project experience.
2. Client intends to deliver a highly complicated
petrochemical plant with multiple specialist
equipment suppliers and first of its kind technology. It
is not practical or commercially feasible to obtain a
wrap of all or major scope components. The client
has to break the project up into a large number of
smaller more manageable specialist trade packages.
While the client has internal project delivery
capability and experience, it does not have sufficient
resources currently available to manage the
additional complexity, volume of work and interface
risk. It elects to engage an EPCM/Delivery Partner to
assist it to manage these factors on a staged
engagement basis.
Project delivery in • Client is expanding its business 1. Client intends to deliver a petrochemical plant in a
foreign country or into new markets and needs to country in the Middle East. It has a core team of
different industry develop infrastructure assets in experienced project delivery personnel who have
sector or those countries to support the delivered similar projects that will be deployed to the
asset type business’ expansion. project location. However, it has not previously
delivered a project in the Middle East and elects to
• Client has significant internal
engage an EPCM/Delivery Partner which has a team
domestic project delivery
of personnel with a proven track-record of delivering
experience but limited experience
similar projects in the region which it will make
in those countries or access to
available for the project.
resources on the ground in those
locations. 2. Client is a mining company with assets in China. It is
in the process of a major mine expansion and needs
• Alternatively, the client may have
to develop new rail, port and power infrastructure to
delivered projects in the country
support the expansion and provide supply chain
but not the type assets needed.
certainty to customers. The client has delivered mine
infrastructure assets in China previously but not rail,
port or power assets. It engages an EPCM/Delivery
Partner to who was recently involved delivering
similar assets in another region of China.
Criticality of • Client is embarking on the delivery 1. Client has secured several major offtake agreements
achieving project of a major strategic infrastructure that will underpin its profits for the next ten years.
objectives and on asset that is critical to the overall Management is confident it has the resources it
time project business strategy. needs to deliver the infrastructure assets required to
delivery meet the commitments. However, the penalties
• The ramifications to the business if
under the offtake arrangements and consequential
the project is not delivered on time
business interruption impacts if the assets are not
and in accordance with other
delivered on time to deliver on supply commitments
objectives are such that it requires
are such that the Board requires a greater level of
an additional level of project
project assurance and directs the engagement of an
assurance and the client is
EPCM/Delivery Partner to supplement the internal
prepared to pay a premium to
resources.
secure the necessary resources.
2. Client is a special purpose government agency
• Client engages an EPCM/Delivery
established to deliver a major international sporting
Partner to gain access to additional
event. On time delivery of the required stadiums and
‘best in class’ global project
associated infrastructure is imperative and not
delivery to supercharge its existing
negotiable. In response, the government agency
project delivery capability with
engages an EPCM/Delivery Partner consortium to
experience and lessons learned
gain access to ‘best in class’ global project delivery
from delivering projects under
resources with experience and lessons learned from
similar brownfield conditions and
delivering projects under similar brownfield
levels of public scrutiny.
conditions and levels of public scrutiny.
Business Case Supporting or delivering the business • Basic and detailed engineering and design
case that underpins the project (often referred to as pre-feasibility/concept design
investment decision. and FEED).
• Constructability analysis.
• Materials and resource availability assessment and
contracting market sounding.
• Work package breakdown structure and
procurement approach recommendations in respect
of each package.
Procurement Procurement planning, package • Ongoing FEED, including development of work
preparation, implementation and package performance specifications, reference
management. designs and detailed designs for Construct Only
work packages).
• End-to-end design and systems integration of the
separate work packages.
• Further market sounding, preparation of tender
packages, tendering, tender evaluations and
recommendations for award of project packages.
• Dynamic updating of work package breakdown and
associated procurement approaches reflecting the
outcomes of market sounding and tender responses.
• Prioritising procurement of packages based on the
overall project critical path, maturity of design and
certainty of scope and stakeholder requirements.
• Overall procurement process management in
accordance with the client’s internal governance
frameworks and approved delegations of authority.
Concept Description
Staged Contracts are typically structured in such a way so as to permit the client, in its absolute discretion,
engagement with to instruct the EPCM/Delivery Partner to proceed to the next stage. For example, at the conclusion
optional phases of the feasibility stage, the client can elect to end the engagement and go to market regardless of
whether an incumbent EPCM/Delivery Partner has properly performed the services. Similarly,
where the project is to be financed through limited or non-recourse project financing, the client
must be entitled to terminate the contract in its absolute discretion if the Lenders do not give
finance approval or the clients cannot raise the required capital.
Terms establishing the process, consequences (including payment on termination outlined above)
and risks in the services undertaken during a particular phase will need to be clearly articulated in
the contract.
Project objectives The contract should include a description of the client’s overarching project goals, list of project
and project scope objectives and a detailed description of the scope and the client’s project requirements. This would
usually be aligned to the business case objectives, scope and assumptions underpinning the
investment decision.
Traditional provisions regarding obligations to use all reasonable endeavours to perform the
services to ensure the defined scope is delivered in accordance with the project objectives and
requirements should be included. This also becomes the reference point for determining whether a
change is material giving rise to a variation or adjustment to KRA and KPI targets upon which
incentive payments are based as discussed below.
Accountability In addition to the detailed scope of services and agreed personnel and resource schedules, the
matrix contract should include a detailed accountability matrix for each phase of the services.
This is typically in the form of a table and includes a detailed list of all key project tasks and
activities during each phase, and delineates, at a high-level, the accountability of the client,
EPCM/Delivery Partner and other key project participants for the performance of or contribution to
each task or activity. The accountability matrix must align with the client governance and
organisational structure and the agreed resources to be provided by EPCM/Delivery Partner. The
process of preparing it often provides a good opportunity to identify and correct any misalignment
between the parties in terms of respective roles and responsibilities.
Client reserve Provisions should be included in the contract which clarify the ‘reserve powers’ held by the client to
powers and manage and direct the project, including:
delegated
• approval of systems and procedures governing the project
authority
• urgent protection of people and property
• issuing bid documents
• awarding implementation contracts
• approving variations and extensions of time or
• any event likely to have a major impact on the operation or viability of the project etc.
The extent of the EPCM/Delivery Partner’s delegated authority (if any) also needs to clearly
articulated and remain subject to change at the client’s discretion. Terms establishing the process
and consequences (including any impact on incentive arrangements) for a change in the
EPCM/Delivery Partner’s delegated authority must be clearly articulated.
Retention of key The traditional provisions regarding key personnel (i.e. the EPCM/Delivery Partner cannot remove
personnel them without the client’s prior approval) are likely to be too inflexible for complex mega projects
delivered over several years. Consideration should be given to alternate arrangements such as
incentives or payment of a liquidated amount where senior key personnel leave or are taken off
the project within a certain period. There will typically be exceptions to such payment for illness,
incapacitation and resignation, or if the personnel are temporarily absent on, for example,
annual, sick, long service or compassionate leave (provided a suitable replacement is deployed to
the project).
Concept Description
Overall design Early consideration of the scope of the EPCM/Delivery Partner’s design obligations is vital. In
integration particular, a client must consider whether an EPCM/Delivery Partner is responsible for:
responsibility,
• the end-to-end design integration of the various work packages
constructability
warranties and • guaranteeing that, when integrated, the design of the various project scope elements will
novation of exiting enable the overall project to meet the client’s functional and performance requirements for the
design whole project.
If an EPCM/Delivery Partner is responsible for end-to-end integration, there will need to be certain
carve-out to the design warranties for latent errors or deficiencies in detailed engineering and
design performed by the works package Contractor and Suppliers.
Where the EPCM/Delivery Partner is permitted by the client to self-perform FEED and detailed
design, it should be required to provide design constructability warranties and also warrant that the
design of the works will be fit for the purposes it was intended for.
In the event a major proportion of the engineering and design for the project has already been
undertaken under separate design/consultancy packages let by the client (i.e. FEED during the
initial project feasibility phase), the client should consider avoiding potential gaps in liability by
creating a single point of responsibility for the performance of the FEED. This is achieved, in part,
through the novation of the existing design to the EPCM/Delivery Partner so that it has contractual
rights against those consultants. If the EPCM/Delivery Partner is to be a single point of
responsibility for the performance of the FEED, the client must allow sufficient time and budget for
the EPCM/Delivery Partner to verify and correct errors or deficiencies in the existing design. Field
engineers coordinate specialist design and engineering resources to resolve design and
engineering issues until the works have been fully commissioned.
Intellectual The contract intellectual property (IP) regime needs to reflect:
property
• the range of Contractor and Supplier background IP being contributed
• the range of project IP being developed at the work package and supply contract level
• the corresponding need for licences and rights to use and develop that IP, including ensuring
appropriate IP warranties and indemnities in the work package and supply contracts.
The client should also ensure it retains ownership of and rights to use and adapt the IP in the
FEED and other materials prepared by or on behalf of the EPCM/Delivery Partner as part of the
business case. This will prevent the client from being restricted in using that material in the event it
elects to terminate the EPCM/Delivery Partner’s engagement at the end of the feasibility and
business case phase. The client should also specify the format and form by which this IP is
handed over in the event of a termination of engagement.
Insurance The whole of project insurance strategy is critical and will impact on the contract risk allocation and
extent of insurances to be procured and maintained by the EPCM/Delivery Partner. In addition to
any project wide insurance policies, the EPCM/Delivery Partner will usually take out and maintain
public liability and professional indemnity insurance. In reality the scope of the professional
indemnity insurance may not underwrite all of the contractually assumed liabilities under the
contract, in particular EPCM/Delivery Partner warranties and indemnities. This may or may not
influence negotiations of contract terms, including liability cap, depending on the EPCM/Delivery
Partner’s balance sheet capacity to meet its liabilities. The EPCM/Delivery Partner’s liability caps
are sometimes limited to the amount recoverable under insurance policies maintained under the
contract. If this position applies, the EPCM/Delivery Partner’s policy must operate on an ‘each and
every claim basis’ rather than an ‘in the aggregate basis’.
Overall project The EPCM/Delivery Partner is usually required to prepare a capital cost budget and programme
cost and for the business case. Once approved, the EPCM/Delivery Partner becomes responsible for
programme monitoring and managing actual cost and progress against the approved budget and Programme,
control and for providing the Principal with regular costs and Programme updates. Although the
EPCM/Delivery Partner does not take the risk of delivering the project on time and on budget, it
generally has an obligation to use reasonable endeavours to do so, and is incentivised to manage
the budget and Programme to ensure project cost or Programme overruns are avoided or
minimised through incentive payments.
Concept Description
EPCM/Delivery EPCM/Delivery Partners are typically remunerated on an cost-reimbursable basis, including the
Partner following components:
remuneration
• Fixed Fee: Pre-agreed fixed fee or percentage of the estimated cost for each phase of the
project to cover margin and overheads.
• Actual Personnel Costs: Reimbursement for directly and reasonably incurred personnel
costs at pre-agreed rates or on an open book costs basis, with typical deductions for
duplication of work undertaken due to defects in the services or otherwise for the
EPCM/Delivery Partner’s default.
• Reimbursable Expenses: Reimbursement for a discrete list of reimbursable expenses,
subject to the client’s approval prior to the expense being incurred (i.e. pre-approved work
related travel).
The EPCM/Delivery Partner will typically also be entitled to bonuses (or subject to a reduction in
payment) under an agreed incentive regime as outlined below. The EPCM/Delivery Partner may
also agree to fixed-fee arrangement for certain activities where it is able to reasonably estimate
the extent of work and resources required. However, any fixed fee or capped fee arrangements
need to be considered carefully and structured in a way that does not create behaviours which are
not in the overall project’s best interests.
Material variations Not all project scope changes will constitute a variation under the Contract which should include
mechanisms for determining what amounts to a material variation (i.e. a major change to the
project scope or other material adverse event not contemplated by the parties) and the
corresponding cost consequences (i.e. adjustment to fixed fee and overhead component or
payment of direct costs only). This area becomes more important in relation to the achievement of
KRA and KPI targets and whether the target costs and time frames are to be adjusted. Pre-award
workshops are often conducted to define the limited nature of events giving rise to a variation.
Incentive Given the cost reimbursable nature of the contracts, without incentive mechanisms, it is difficult, if
arrangements not impossible, to instil the same sense of urgency and efficiency in the EPCM/Delivery Partner
and its personnel over a long period as compared to a fixed price model. Therefore, the regime will
be critical in incentivising the EPCM/Delivery Partner to perform in a safe, productive, efficient and
timely manner in order to ensure the client’s key objectives for the project are realised – usually a
combination of time, cost, quality, safety, environment, stakeholder and community management.
It is critical when formulating the targets and methods of measuring performance, that there is
sufficient clarity of project scope and the client’s requirements. Whenever possible, the Principal
must allow sufficient time and resources to agree and clearly articulate quantifiable KRA and KPI
targets and corresponding methods of measuring performance against those targets.
The incentive regime should focus on maximising productivity and timely delivery whilst striking a
balance between time and budget, without sacrificing quality or safety. We have seen very detailed
and sophisticated incentive regimes, particularly in an Alliancing or relationship contracting context
and where project deliverables are to be measured over long time frames. Conversely, some
parties prefer to move away from (or limit the extent and impact of) incentive regimes, because
they believe these arrangements can create uncertainty (and therefore some risks in a rising cost
market) and drive the wrong behaviours due to additional friction between the parties, which does
not foster co-operation or trust between the parties. Some EPCM/Delivery Partners are also
unwilling to put a material percentage of their remuneration at risk based on an incentive regime.
However, if the incentive regime is structured with proper recognition of the current market
conditions and the issues below are addressed then successful outcomes are achievable.
If you have any questions about this paper, please contact the editor, Damian McNair, Partner, Energy Transition.
PwC Australia has a dedicated Energy Transition business, consisting of a hub of 132 multidisciplinary and highly-skilled
experts helping to facilitate Australia’s successful transition to a decarbonised economy by 2050. We are helping accelerate
our clients through the energy transition and their related ESG priorities as Australia moves to a net zero economy.
© 2022 PricewaterhouseCoopers Consulting (Australia) Pty Limited. All rights reserved. PwC refers to PricewaterhouseCoopers Consulting
(Australia) Pty Limited, and may sometimes refer to the PwC network. Each member firm is a separate legal entity. Please see
www.pwc.com/structure for further details. This content is for general information purposes only, and should not be used as a substitute for
consultation with professional advisors. Liability limited by a scheme approved under Professional Standards Legislation. At PwC Australia
our purpose is to build trust in society and solve important problems. We’re a network of firms in 158 countries with more than 250,000
people who are committed to delivering quality in assurance, tax and advisory services. Find out more and tell us what matters to you by
visiting us at www.pwc.com.au.
D0404694