Designing Buildings - The Construction Wiki

Search

Subjects

Tools / info

Edit this article

Last edited 24 Jan 2022

See full history

Main author

JFJ Afitac Other Consultant Website

Reliance data in EPC contracts

The starting point of many engineering procurement and construction (EPC) tenders and contract negotiations is as follows: the owner/employer provides the contractor with the data they have in their possession regarding the project together with a specific statement that 'the employer does not give any warranty as to the completeness, accuracy or fitness for purpose' of that information.

They do this to avoid any claim by the contractor during the project execution on the basis that the provided information is inaccurate or incorrect. Sometimes the situation is even worse and the owner/employer simply tries to avoid giving any information.

In practice, withholding information is counterproductive as it does not enable the EPC contractor to quote properly, with reasonable efforts. Contractors may walk away from the tender, overprice or underestimate the project’s cost. In the latter case, contractors often create trouble during the execution phase in an attempt to limit their losses.

FIDIC 1999 Silver Book (Clause 5.1) requires the contractor to scrutinise the employer’s requirements prior to the bid submittal. The employer shall not be responsible for any error, inaccuracy or omission of any kind in the employer’s requirements except for data and information which are stated as immutable or the responsibility of the employer and also except for data and information which cannot be verified by the contractor. Having some data on which the contractor may rely (reliance data) is therefore good industry practice and in line with the contract standards.

The difficulty starts when identifying precisely the 'reliance data', 'baseline data' or whatever word is defined in the contract to introduce the same concept. The data is usually parked in an appendix containing a limited list of data for which the employer takes responsibility. An objective methodology to establish 'reliance data' is to look at the project (to be executed) as a 'black box':

Whatever is in the box are the works to be executed. These are defined in a functional, not detailed, not prescriptive specification. The reliance data should not include any information from within the project 'black box'.
The project 'black box' is somehow connected to, and interacting with, its surroundings/environment. It is physically attached to/founded on the outside world. It also receives some inflow. The 'black box' can be impacted/shaken-up by the outside environment. The quality, magnitude and characteristics of these foundations, inflows, connections and impacts are data that can, and often should, become reliance data.

In case of building a hydro power plant for example, the following can be reliance data:

Geo-technical baseline data: reference characteristics of subsurface conditions like rock classes ('foundations').
Water quality: chemical composition of water quality for which the penstocks and turbine equipment should be designed; maximum water temperature to be taken into consideration for the design of the cooling system; hydrological data ('inflow').
Grid connection information: data related to the transmission line and grid characteristics (voltage, frequency). The electric grid often still has to be expanded under a separate contract ('connections').
Maximum wind speed or seismic acceleration coefficient: design requirements that the 'black box' will have to withstand ('impacts').

Some concept of reliance data is healthy for a balanced EPC contract. It is necessary to minimise the information to those design inputs that are essential and cannot reasonably be verified by the contractor during the tender stage. This includes information that is the result of long-term data series or unaccessible or needing unreasonable efforts and resources to obtain during the tender stage (when the contractor is not sure to be awarded the contract).