Why Our Way To Develop Projects Fails To Minimize CAPEX
Why Our Way To Develop Projects Fails To Minimize CAPEX
Oil & Gas facilities projects are developed in 2 steps: a Front End
Engineering Design (FEED) services contract followed by an
Engineering, Procurement and Construction (EPC) contract.
I would like to share with you why this scheme does not fulfill the
requirements to lower Oil & Gas facilities CAPEX and which
alternate scheme, which I see becoming the future, does.
First of all, when contracting a FEED as a LS, one obtains the bare
contractual minimum in terms of studies done, alternatives reviewed,
if any, and deliverables. This not only results in lack of project
definition but also in missed opportunities to save CAPEX.
The lack of project definition is hard to spot and challenge. How can
one tell if enough thought has been put into a drawing? For instance,
how do we know if all constraints (1) have been duly considered
while establishing the Plant Layout and producing the Plot Plan
drawings?
The missed opportunities result from the fact that the FEED
contractor has no interest to spend hours to find alternatives to
optimize the design. The FEED contractor also has no interest to
propose alternates/deviations to Company specifications.
This last aspect is very unfortunate in the current context of low oil
prices and due to the fact that Companies have, over the last decades,
develop very extensive sets of specifications containing stringent
technical requirements. As cost was not an issue then, additions of
technical requirements to these specifications were not much
challenged. This resulted in numerous onerous and sometimes
unnecessary requirements which only a joint review between
contractor, that is aware of the cost, and Company, which is aware of
the operational requirements, could discard.
The quality of the FEED documents will directly affect the quality of
the EPC bids. FEED deliverables are indeed the basis that will be
used by the EPC bidders for their quotations. EPC bidders do not have
time to review documents and revise them, as required, before to use
them as a basis for cost estimation. The cost estimate is therefore
based on the FEED documents. As we know: sh#t in, sh#t out.
As not enough effort has been spent at FEED stage to precisely define
technical requirements, or some studies not done or not documented,
the EPC bidder would need to make assumptions. As these
assumptions are made by technical personnel, who are not always
fully aware of the cost impact and who are chiefly responsible for the
technical soundness, assumptions are often made on the safe side.
In spite of the fact that the FEED quality level is unknown to the EPC
bidder, and that it has been contracted under a LS scheme fostering
low quality, the EPC bidders are required to endorse it, i.e., to take
full responsibility for any error or omission. The EPC bidders have no
time to thoroughly check the FEED during the bidding period. They
therefore include contingencies in their quotations, inflating the
Project cost for the Client.
Even though one readily sees that having the FEED done under a LS
contract and demanding such endorsement of the FEED by EPC
bidders are clearly conflicting, it is the norm today.
This will be the first step in the improved project execution scheme. I
will explain how to improve the next step (EPC) in my next article.
https://www.linkedin.com/pulse/why-our-way-develop-projects-fails-
minimize-capex-herve-baron