The client is building a plant — say, a chocolate factory; why not.
The client engages an EPC contractor to give the project
turnkey liability, i.e. end-to-end responsibility sitting
with the EPC contractor.
First, because that is convenient; second, because project lenders
are not always willing to provide financing where the plant is built
on a multi-lot basis, i.e. with many contractors. Why? Because for
project lenders — the banks — that means risk: the more contractors
in the project, the higher the probability that one of them will
miss deadlines or fail to perform other contractual obligations,
which in turn increases the risk of late commissioning of the
chocolate factory and, behind it, the risk of borrower default.
Designing the chocolate factory
Several vectors are possible on the design side. Let us examine each
of them under both Russian law and English law as applied to the EPC
contract.
Vector 1 · Designing in-house. The EPC contractor
designs the project with its own resources. This is rare but does
happen. The EPC contractor does not subcontract a design institute;
its staff includes designers. This is the ideal scenario for all
parties to the EPC contract, because if the EPC contractor makes a
calculation error in developing the FEED or design documentation,
and the plant therefore fails to reach the guaranteed figures
either during the 72-hour tests or by any other date set by the EPC
contract, the responsibility lies entirely with the EPC contractor.
Vector 2 · The EPC contractor engages designers. In
practice, this is the most common picture: the EPC contractor enters
into subcontracts with one or more designers.
Depending on the technological complexity of the EPC project, the
designer (usually foreign) may develop only the FEED package (front
end engineering design), i.e. basic or preliminary design with the
production technology built in, and the EPC contractor itself adapts
the basic package to Russian design norms in line with Resolution 87
of 16 February 2008, “On the Composition of Sections of Design
Documentation and the Requirements for Their Content.”
Alternatively, the EPC contractor subcontracts a Russian designer to
adapt the basic design to Russian design norms, and receives back a
package of design documentation that complies with the Russian
standards.
Vector 3 · The client supplies FEED documentation as input
data. Cases occur where the client signs the basic-design
contract directly with the licensor (the technology holder) and then
passes the FEED package across to the EPC contractor as input data,
to be incorporated, in adapted form, into the Russian design
documentation.
What rely upon and non rely upon information mean in a project
Sometimes the EPC contractor does not want to bear responsibility for
the technological decisions “sitting” in the design. Take our
chocolate factory. The EPC contractor is most often not the
licensor: it knows how to build the factory but does not know which
technological decisions need to be designed in so that the factory
produces chocolate with specified characteristics.
So the EPC contractor engages a licensor — the party that holds the
technology to produce chocolate with the required characteristics.
The licensor delivers pre-FEED or FEED design, and the EPC contractor
adapts the basic design to the Russian norms.
“I am willing to be liable for the chocolate factory’s failure to
reach the guaranteed figures, except where the failure is caused by
an error in the FEED. The licensor’s basic design is, for me,
rely upon information.”
What to do with this
Whether any given input data is rely upon information or non rely
upon information is, in most cases, a matter of commercial
negotiation. There are also a number of technical aspects on which
it is hard to influence.
This topic is particularly sensitive — and important — for EPC
contractors at the moment of accepting input data from the client
before the project starts. The EPC contractor needs to understand
clearly, and to record in writing in the EPC contract, which input
data delivered by the client the EPC contractor is to verify and
which it is not.
- Non rely upon information — information that cannot be relied on and that must be verified.
- Rely upon information — information that should be relied on and that need not be verified.
Why is this needed? Any error in the input data from the client,
discovered during project execution, can lead to a significant
extension of the construction period for that chocolate factory. And
if the EPC contractor has not recorded in the EPC contract which
input data it is to be liable for the accuracy of, then
de jure it will be liable for everything — especially if
English law applies to the EPC contract.
Example: an ancient settlement beneath the foundations
Say the client hands the EPC contractor the results of surveys
(geology, geodesy) carried out by a separate contractor. When
construction works begin, the EPC contractor discovers an ancient
settlement that the survey contractor did not find.
What does this mean for the project? Correct: a suspension of works
of up to a year. These are so-called subsurface risks. But
who is liable for the construction delay if the EPC contract says
nothing about whether the EPC contractor must verify input data for
accuracy? In the example, the EPC contractor finds itself in a very
bad position.
When we represent the EPC contractor on a project, we always sit
down with its technical team and explain why we need an appendix
clearly demarcating which input data is to be verified by the EPC
contractor and which is not. For example, all survey results we
treat as rely upon information. So if pile-driving uncovers an
ancient settlement, the EPC contractor is not liable for the delay
and does not pay the client delay liquidated damages.
The criterion of reasonableness and common sense is also important
here. In theory, the contractor could verify the survey results by
re-excavating the site, but that is not reasonable — which is why,
in international EPC practice, the so-called subsurface risks sit
with the EPC client as the site owner.
From the client and lender side
When we represent the client in an EPC project, the rely upon
information question also plays an important role — for the client
and for the project lenders. Often the client company’s shareholders
are not aware that they have selected an EPC contractor who, after
several months of negotiations, casually mentions over a coffee break
that it is only responsible for its part of the design, the Russian
part. The basic design package produced by the foreign licensor —
whom the EPC contractor itself engaged — the contractor is not going
to check.
So if the chocolate factory produces less chocolate than was agreed
in the technical specification, and an expert review concludes that
the error “sits” in the FEED package that “underpins” the Russian
design documentation, there will be no one from whom to recover the
performance liquidated damages for failure to reach the guaranteed
figures.
Lenders will say that such a provision makes the EPC contract
non-bankable — in plain language, no money will be lent to build a
factory on those terms.
Direct contract between client and licensor for the FEED package
There are cases in which the client engages the foreign designer
directly to develop the basic design package and then hands that
package to the EPC contractor for adaptation to Russian design
norms. If, on that model, the EPC contractor states that it will not
verify the FEED package because it lacks the expertise, the client
can in such a case pursue the foreign designer for damages.
This route, however, will not be liked by lenders and is
commercially poor for the client, because the foreign designer’s
liability cap will be calculated from the price of the contract with
that designer — which, by definition, will be lower than the EPC
contract price. The client will therefore recover a smaller amount
of damages than it could from the EPC contractor.
To sum up: before spending months preparing and negotiating EPC
terms, include in the tender package or the term sheet a clause
addressing which input data the EPC contractor is, in the client’s
view, to be responsible for the accuracy of — paying particular
attention to verification of the basic design from the licensor.