BP GROUP ENGINEERING

TECHNICAL PRACTICES
(ETPs)

ETP INTRODUCTION
February 2002
PREFACE

This ETP Introduction contains information and guidelines on the philosophy and use of
the BP Group Engineering Technical Practices (ETPs). The ETP Introduction, all the
ETPs, and other Technical Practice information on Internal and External Standards can
be found on the Technical Practices web site available via the BP Intranet:

http://technical_practices.bpweb.bp.com/?title=Technical%20Practices%20&%20Stds

Copyright © BP Group p.l.c.

All rights reserved. The information contained in this document is subject to the terms and
conditions of the agreement or contract under which the document was supplied to the
recipient's organisation. None of the information contained in this document shall be
disclosed outside the recipient's own organisation without the prior written permission of BP
Group Management, unless the terms of such agreement or contract expressly allow.

ETP INTRODUCTION Feb 2002

Page 1
 CONTENTS

Section Page

GENERAL FOREWORD ...................................................................................................3

1. ENGINEERING TECHNICAL PRACTICES (ETP).......................................4

1.1 Transparent ETP Structure ..............................................................................4
1.2 Classification and Categorization of ETP Documents.......................................7
1.2.1 Preamble (PR) to ETP Category ..........................................................7
1.2.2 Create a GP or a GIS? The Map...........................................................8
1.2.3 Guidance on Practice (GP) for ETP Sub-Categories.............................8
1.2.4 Guidance on Industry Standard (GIS) ................................................10
1.2.5 Commentary in the GP and GIS Documents.......................................12
1.2.6 Transparent Internal Technical Practice Categorization by
Group, Stream, Region and Business Unit .....................................................13
1.3 Guidelines For Users of BP Group ETPs .......................................................14
1.3.1 General Guidelines .............................................................................14
1.3.2 BP Group ETPs are Voluntary but Contain Requirements ..................14
1.3.3 Adapting to the BP Group ETPs ........................................................15
1.3.4 Referencing New ETPs before their Creations....................................15
1.3.5 Alternative Referenced Standards.......................................................15
1.3.6 ETP Shared Learnings Capture System (Feedback) ............................16
1.3.7 Use Of Language ...............................................................................17
1.3.8 Standard Definitions...........................................................................19

ETP INTRODUCTION Feb 2002

Page 2
 GENERAL FOREWORD

Introduction

The BP Group and heritage companies have developed over a number of years an engineering
knowledge base that includes a general standard of engineering design that has contributed to
the safe and successful operation of a wide range of petroleum and petrochemical plants and
facilities. BP Group Engineering Technical Practices (ETPs) composed of Guidance on
Practices (GPs) and Guidance on Industry Standards (GISs) capture this engineering design
and operating knowledge and transfer good practices across the entire BP Group.

The GPs provide guidance for engineering design, construction, installation, commissioning,
operation and maintenance, sharing experience and advising on alternatives for consideration
by technical professional and operations staff. The GISs are primarily guidance for developing
Stream, Regional, Business Unit (BU) and Project local technical specifications for application
and procurement of methods, systems, equipment and materials.

To continuously improve business and capital productivity performance by the sharing of

knowledge, the BP Group ETPs will be updated and maintained. This effort will occur under
the overall direction of the BP Group Head of Discipline Engineering located in BP’s Group
Technology of the Global Business Centre (Sunbury). Co-ordination of content and
publication of the BP Group ETPs is provided by the ETP Project Team located in Houston,
Texas USA and Sunbury, England U.K.

Objectives

The objective of the BP Group ETPs is to provide general technical and operational guidance
for the activities associated with the EPIC project process (engineering design, procurement,
installation, and construction) to achieve fitness of purpose, technical integrity and optimum
life cycle cost for building BP facilities. The ETPs will assist BP Projects (and 3rd party
engineering), BU site engineers and Stream Technology engineers to accomplish this objective
and provides Group management assurance that the objective will be met.

The users (local site or project Engineering Authority) of an ETP document are responsible for
determining what standards and practices are appropriate to be used for their location.
If it is decided to use (follow, apply, comply with) an ETP, the user must either fully meet the
requirements stated in the ETP or document deviations from those requirements. Deviations
should be based on local conditions, which (including organisational, customary practice and
regulatory) may dictate that other engineering approaches are more appropriate for the locality
in which the facility exists.

In addition, industry standards (whether local, regional or international) contribute to the

solution. For internal BP Group ETPs, the approach is to rely as far as possible on
international industry standards and/or other industry standards and practices. BP engineers
are actively participating in developing or modifying these common external standards with

ETP INTRODUCTION Feb 2002

Page 3
particular focus on ISO/TC67, the International Standards Committee for “Materials,
Equipment and Offshore Structures for Petroleum and Natural Gas Industries”.

Consistent with the responsibility and freedom given to BP engineering authorities to establish
appropriate engineering practices, it follows that the BP Group ETPs are voluntary.

Shared Learnings and Feedback

Users of the ETPs are encouraged to use the ETP SHARED LEARNING CAPTURE system
to provide shared learnings and make comments or suggestions that could lead to
improvement and updating of the ETPs. Such feedback from BP Group technical and project
professionals assists materially in maintaining, updating, and enhancing the value of the ETP
documents for the BP Group. The feedback will serve to continuously improve the BP Group
capital productivity and business performance. Networks should be involved in this feedback
process and should promote the use of the shared learning capture system to add the most up-
to-date good practice and other information in their discipline area.

1. ENGINEERING TECHNICAL PRACTICES (ETP)

1.1 Transparent ETP Structure

The way forward for internal BP ETPs 2001 and beyond is to provide a
structure for our BP Streams and BUs to create transparent addendums
and variations from the worldwide BP Group ETPs. Stream, Region,
BU, and Project Specifications will be derived from the BP Group
ETPs to reflect local and country differences and regulations.

BP's internal ETP Policy is to rely if possible on international and

Transparent ETP Structure

Networks & Regional,

Regional,BU,
BU,
BU Knowledge and
andProject
Project
Feedback Specifications
Specifications BU AREA

BP Stream
BPGroup
Group Stream
Guidance Variation
Variation
Guidance
On Practice To
ToGroup
Group
On Practice
(GP) Addendum
Addendum
(GP)
Knowledge
STREAM
Knowledge
Transfer RESPONSIBILITY
Transferper
perETP
ETP BP
BPGuidance
Guidance
Category On
Category OnIndustry
Industry
Standards
Standards
(GIS)
(GIS)
GROUP COMMON
External
External
BASE AND Industry
Industry
RESPONSIBILITY Standards
Standards
And
And
Specifications
Specifications

ETP INTRODUCTION Feb 2002

Page 4
industry standards to achieve business objectives relating to capital
productivity, operations, and HSE performance. Should these industry
standards require qualification, a BP Group ETP (Guidance on
Practice-GP or Guidance on Industry Standard-GIS) is developed as a
transparent supplement to the external standard. BP’s GPs and GISs
capture knowledge or practice which is not available from industry
standards alone and that yields measurable business benefit.

The essential elements of the BP Group Internal ETPs are as follows:

(a) International industry standards or other applicable industry

standards are used if possible.

(b) If BP has more to say, the BP ETP either GP or GIS is

developed as a transparent supplement to the external standard.
'Transparent' means that the BP GP or GIS only adds to or
qualifies the external industry standard, and must be read in
conjunction with it.

(c) BP GPs and GISs are developed if no suitable external industry

standard document exists.

(d) BP internal Group ETPs are for worldwide and group-wide

application as far as possible.

(e) BP internal Group ETPs are maintained if value is added to BP

Businesses by having a BP Group document. The ETPs are,
however, not mandatory and each Stream and BU has the
autonomy to define its own set of engineering standards or
specifications.

(f) BP Group ETPs are maintained and kept up-to-date by Group

Technology drawing feedback from BP Group technical and
project professionals.

(g) The ‘Requirements’ identified in the clause text of the GPs or

GISs, will be backed up with a 'Commentary' to explain the
requirements and advise on options.

(h) The GIS primarily deals with procurement of material, equipment,

and systems and is written so that it can be sent to a vendor with the
project supplemental specification. When qualifying an industry
standard, the GIS can also discuss the full range of the EPIC project
process.

ETP INTRODUCTION Feb 2002

Page 5
 What ETP Set Up Will Provide
BU SITE and PROJECT
BP Group Common Base ENGINEERING
Knowledge of Options
and Alternatives
BP
BPGroup
Group on What to Select
Guidance
Guidance
On Practice Engr.
On Practice Engr.&& Purchase Specifications
(GP)
(GP) Const.
Const. to Vendors for
Knowledge Transfer Rqmts.
Knowledge Transfer BP Rqmts. Engineered Equipment
per ETP Category
per ETP Category BPGuidance
Guidance
On
OnIndustry
Industry
Standards
Standards Project
Commentary Project
Commentary (GIS)
(GIS) Purchase
Purchase
Spec.
Spec.
External Commentary
Commentary
External
Industry
Industry Filled
Filled
Standards
Standards Out
OutData
Data
And BP Blank Sheet
And BP Blank Sheet
Specifications Data Sheet
Specifications Data Sheet
Form
Form

The name for the BP Group ETP document set is the 'BP Group
Engineering Technical Practices' (ETPs). In engineering circles they
can still be referred to simply as ‘BP standards’. The ETP document set
is divided into categories for specific subject areas as shown below:
ETP Categories (Subject Area) Index
00 Administration 42 Piping
02 Casing, Tubing & Drillpipe 43 Pipelines
04 Civil & Geotechnics 44 Plant Layout & Design
06 Corrosion 46 Pressure Vessels
10 Drilling Equipment 47 Process Design
11 Well Fluids and Cements 48 Processes & Procedures
12 Electrical 50 Quality & Conformity Assessment
13 Engineering Documentation 52 Insulation
14 Environmental & Noise 56 Steam Plant
18 Fabrication & Welding 58 Storage Tanks
22 Fired Heaters 59 Telecommunications
24 Fire Protection 60 Utilities

ETP INTRODUCTION Feb 2002

Page 6
 26 Heat Exchangers 62 Valves
28 Hoses 64 Measurement
30 Instruments & Control 66 Offshore Structures
31 Analysers 68 Overhauls
32 Inspection & Testing 70 Procurement
34 Rotating Equipment 72 Refractory
35 Maintenance & Reliability 74 Reuse of Equipment
36 Materials Selection 76 Safety and Loss
38 Mechanical Handling 78 Subsea Equipment
40 Packaged Equipment 80 Wellheads & Christmas Trees

1.2 Classification and Categorization of ETP Documents

Each of the BP Group ETP documents is classified and categorized as

follows, according to its characteristics:

1.2.1 Preamble (PR) to ETP Category

The PR document shall define the overall context of the category, give
directions to the user, and map the structure of the documents within
the category to the EPIC project process. If there are multiple GP
documents, these PR clauses shall provide guidance to the user to
facilitate choices that may be needed within the category to select the
appropriate subcategory.

The PR document shall reference general information on the category,

the industry standard documents within the category, the BP documents
within the category, BP policy relevant to the category, frame
agreements on equipment and commodities within the category, internal
networks and the list of BP experts on the category, and other relevant
publications. Hot links to the ETP electronic library of experience and
design will be used to provide quick access to the information
referenced above.

The PR document may contain several clauses. No organization for

these clauses is pre-defined. The clauses might be organised by the
various individual subcategories or perhaps by topics cutting across the
various subcategories. The language of the PR document is non-
mandatory in nature. Words such as should, and may are common.
Mandatory words such as shall are forbidden.

ETP INTRODUCTION Feb 2002

Page 7
1.2.2 Create a GP or a GIS? The Map

GP
Is there an
GP
Industry Standard
associated ?
NO
E, I, C,O GP
Industry Standard
YES

,O
Referenced only.
BP Good Practice

E, I, C

E,
I, C
(Category) GP references entire
C, O document or multiple

,O
NO E, I, references of sections are
Is BP practice NO made from the GP
Qualifying the
Does BP good Industry Standard ?
Practice discuss
Procurement
YES
GIS
requirements? E, I, C,
O GIS
YES GIS
E – Engineering BP GIS is read
P side by side with
P - Procurement the industry standard
I – Installation GIS
C – Construction
O – Operations & Maintenance Qualifying means:
Adding to, substituting,modification of, or
deletion of industry standard information on
a clause by clause basis.

1.2.3 Guidance on Practice (GP) for ETP Sub-Categories

The GP document facilitates knowledge transfer of BP proven

engineering design concepts and BP good operating practices.
Primarily, the GP document is written to provide guidance to technical
design engineers and project professional staff of both BP and the
engineering contractors. As such, the GP document is not normally sent
to equipment suppliers or vendors, but is used by construction or
installation contractors. BP operations and maintenance staff in BP
facilities played an important part in the GP development. Their good
operating practices were incorporated into the document content to
provide optimum life cycle cost knowledge.
A GP document shall provide guidance on the engineering design,
manufacture, construction, installation, commissioning, inspection,
testing, operation, and maintenance associated with the main ETP
category equipment and systems. The GP document shall not provide
procurement requirements as those requirements are set forth in the
GIS documents associated with the GP. GPs can also be referred to as
sub-categories. Several GPs should be written per main ETP category
to limit the number of pages of information contained in one GP
document. GP content can be separated into different GPs by content
area (GP-Engineering Design, GP-Installation, GP-Equipment Type),
project phase, or by content audience (GP-Maintenance, GP-
Construction). Cross-references shall be included. The GP documents

ETP INTRODUCTION Feb 2002

Page 8
may reference one or more industry standards and other category GPs.
If industry standards are referenced by a GP, then the GP shall provide
minimum or no qualifications to those standards. The GP may reference
the entire industry standard document or the GP may make multiple
references to different sections of the industry standard document.
If a main ETP category has many industry standards that cover the
subject area and many GISs are developed, then only one GP may exist.
The one GP is called the category name general and serves as a
selection guide directing the user to the GISs to be used for the user’s
situation.

The GP content clauses shall capture BP good practice in engineering

and operation (focussed on optimum life cycle cost) by discussing or
providing the following;
• Guidelines for the selection or evaluation of equipment or
systems (what is best to use when or under what conditions)
• Advantages, limitations, options and selection criteria and
guidelines in the mechanical or process engineering design of
equipment and systems
• Offers information and descriptions of equipment types to aid in
appropriate system design
• Indicates areas that need attention and provides rules for design
• Values for design are given as ranges with upper and lower
limits
• Recommended practices that provide safe and reliable facilities
assuring technical integrity
• Recommended practices that maximise life-cycle value or
reduce life cycle cost
• Maintenance and operation recommendations
• Options and recommendations associated with installation of
equipment, materials, and instrumentation
• Construction guidelines and what to look for when managing
construction activities
• Manufacturing guidelines without getting into specification
• Mechanical design and selection criteria for materials of
construction
• Descriptions of how the guidance is conditional due to varying
external environmental conditions, varying fluid and process
conditions, etc.
The language of the GP document is both mandatory and non-
mandatory in nature and shall be written in a narrative style. Words
such as should and may are common. The term “shall” shall be used if a
requirement is considered to be necessary to claim compliance with the
GP document being created. The GP document may contain several
clauses. No organization for these clauses is pre-defined. The clauses
might be organised by the various individual references or perhaps by
topics such as those listed above that might cut across the various
references.

Paragraphs within these clauses may also have an associated

commentary paragraph that provides the rationale for why the stated
provisions are appropriate and that identifies the circumstance under

ETP INTRODUCTION Feb 2002

Page 9
 which the stated provisions might be different. The commentary
(section 1.2.5 below) can also be used to:
• Identify the actual normal requirement of a stream, region,
country, or process specific requirement if it differs from the
BP Group recommendation
• Hot-link to the stream level guidelines and specifications for
the sub-category content being discussed

The guidance information contained in the GP is not intended to

preclude the need for applying sound engineering judgement as to when
and where the GP information should be used nor to limit the use of
new technology and new methods. Under the direction of the BP
Engineering Authority, auditable dispensations from requirements in the
GPs can be taken.

1.2.4 Guidance on Industry Standard (GIS)

The Guidance on Industry Standard (GIS) document is a transparent

supplement that primarily deals with the procurement of equipment,
materials, and systems and is associated with a GP sub-category. The
GIS can also be a document that qualifies or provides an addendum or
supplement to an industry standard related to the following subject
areas: engineering design, construction, installation, maintenance, and
operations.

A GIS document discussing procurement shall provide guidance on

requirements and considerations associated with the subject industry
standard in order to implement BP good practice and provide applicable
standardized methods in the procurement of systems, equipment and
materials. The GIS assists the user in creating project and site
procurement specifications from the Group and worldwide viewpoint.
The GIS is written so that it can be provided to a supplier or vendor
with the site or project supplemental procurement specification.

If an industry standard is not available, a GIS can still be written to

assist the user (BP Business or non-BP Group company) to develop a
fit-for-purpose technical specification for enquiry or purchase by
providing instructions to suppliers or manufacturers of equipment,
materials, or systems.
The GIS documents shall always be associated with a GP and may
cover the following scenarios in order of preference:

1. References a single industry standard in a single GIS document

covering an entire GP sub-category, is a purchase guide, and an
ISO industry standard is referenced
2. References a single industry standard in a single GIS document
covering an entire GP sub-category, is a purchase guide, and an
API, ASME, EEMUA or other industry standard is referenced
3. References multiple industry standards in a single GIS document
covering an entire GP sub-category, is a purchase guide, and
ISO, API, ASME, EEMUA or other industry standards are
referenced
4. References a single or multiple industry standards in a single
GIS document covering only part of a GP sub-category, is a

ETP INTRODUCTION Feb 2002

Page 10
 purchase guide, and either one or several ISO, API, ASME,
EEMUA or other industry standards are referenced. In this
instance, two or more GISs are associated with one GP.
5. No industry standard yet exists, but BP and industry knowledge
does. A single BP GIS document is written covering an entire
GP sub-category as a purchase guide.
6. A non-purchase related GIS document referencing single or
multiple industry standards related to GP subjects and covers all
or a portion of the GP sub-category.
7. A GIS document shall not be written if no GP on the subject
matter exists.

The GIS document may contain several clauses associated with the
clauses of the industry standard it qualifies or when there is no industry
standard, the subject GP. These clauses shall capture BP good practice
(which provides optimum life cycle cost) and provide guidance on
conditional choices inherent in the subject industry standard. If the
choices or modifications are conditional due to varying environmental,
process specific applications, etc., these conditions and the resultant
choices and modifications shall also be discussed.

For EPIC or operation GIS documents that qualify an external industry

standard, the GIS document is written as a 'transparent' supplement to
the external industry standard document(s). The GIS clauses provide
guidance information as 'addition', ‘deletion’, 'substitution',
‘replacement’, or 'clarification' to the relevant paragraph or subject area
of the lead document. In these cases, the preferred method is to have
the GIS numbering system match exactly the lead external industry
standard document numbering system. If not possible, the numbering
system is independent and follows the heading and sub-heading subject
structure of the industry document as close as possible. The BP
document makes sense only when read side-by-side with the external
document. The GIS should facilitate and provide to the user the
information to make sound engineering choices that are needed to
effectively apply the industry standard to BP facilities.

When a GIS discussing procurement is written and no industry standard

exists, the clause organization shall follow the topics, headings, and
sub-headings of the subject GP with which it is associated.
The language of the GIS document shall be narrative style and shall
clearly identify requirements. An exception style of writing shall not be
used. Requirements are typically identified through use of the word
shall. Non-mandatory words such as should and may, are not forbidden,
but use in the body of the text should be rare. However, use of should
and may is common in commentary clauses. The term “shall” shall be
used if a requirement is considered to be necessary to claim compliance
with the GIS document being created.
Unless it is obvious or obvious from context, each paragraph within
these clauses shall also have an associated commentary paragraph that
provides the rationale for why the stated choices and modifications are
appropriate and circumstance under which the stated choices and
modifications might be different.

ETP INTRODUCTION Feb 2002

Page 11
1.2.5 Commentary in the GP and GIS Documents

Requirements set forth in the GP and GIS documents are the

recommended minimum conditions of satisfaction for Group application
on a worldwide basis. The Requirements are intended to promote
simplicity and standardization. In order to meet minimum local country
standards or regulations, the BP Group requirements may need to be
revised or supplemented. To help the user determine the basis of the
requirements stated in the GPs and the GISs, Commentary is provided.
The content of the Commentary is based on what is advisory or
optional or provides the “why” the requirements were made and helps
the user make an informed decision. The user examines the
Commentary to determine if there are any further requirement choices
to specify for the application. Commentary is shown in an italicised
type-face, and is interleaved with the clauses for ease of comprehension.

Heading
BP Heritage
RPSE Clause – (applicable to all Streams)
BP ETPs Commentary
• Upstream
• Regional
Amoco
• Country
Heritage ACES GP • Offshore
• Process specific
Conflicts in the GP or GIS • Chemicals
• Regional
• Country
PTA - Chemicals GIS • Process specific
• Downstream
GOM-DW - Upstream • Regional
• Country
• Process specific
The Commentary may be used for various purposes, as follows:

(a) To explain the BP Requirements if the reasoning for the

requirement is not immediately obvious to a competent
professional engineer.

(b) To specify such further BP requirements as may sometimes be

applied to advantage, and to state the circumstances in which
they should be applied;

(c) To advise on when to select which option if alternatives are

offered by the base external standard;

(d) To specify and explain any further options that may be

appropriate in particular circumstances, to allow the user to
select what is fit for purpose;

ETP INTRODUCTION Feb 2002

Page 12
 (e) To be the BP Group 'memory' by identifying the actual normal
requirement of a stream, region, country, or process specific
requirement if it differs from the BP Group recommendation

(f) To provide hot-links to the stream level guidelines and

specifications for the sub-category content being discussed

(g) To include procedural aspects, in particular related to

occupational health, safety and environment as and if relevant
and essential to the subject;

The Commentary should be omitted if sending the GIS documents to

suppliers or vendors with project or site purchase specifications.

1.2.6 Transparent Internal Technical Practice Categorization by Group,

Stream, Region and Business Unit

The BP Group ETP documents are categorized as being applicable to

the entire BP Group and useable worldwide or international. The
commentary in the ETP documents is used to identify Stream, Regional
(geographical) and Business Unit applicability or deviations from the
Group ETP document content. The ETP documents should be used as
the Group common basis for creation of other guidance and
specification sets within the streams, regional areas, BUs and projects.
The ETPs can be adapted for the more specific applications.

a) Target applicability shall be determined from Table 1.

Table 1 — Target Applicability

Extent of ETP application Target applicability Example of target
applicability
More that one stream Group Group (only)
One stream Stream Upstream, Chemicals,
Downstream, Gas & Power
One region Region Alaska, GOM, North Sea
One business unit Business unit PTA, GOM-DW
One location Location Hull, Texas City
One project Project In Salah Gas, Kapok,
Florida River

b) Target applicability of a technical practice shall be indicated on

the cover page.
c) Target applicability of a technical practice does not preclude
usage in other applications.

ETP INTRODUCTION Feb 2002

Page 13
1.3 Guidelines For Users of BP Group ETPs

1.3.1 General Guidelines

This section provides general information to users of BP Group ETPs.

The general guidelines are used to assist the user in creating an
application-specific document from the BP Group ETP document.

The BP Group ETPs are written as guidance documents and suggest

taking a risk based approach to engineering design. The ETPs do not
fully detail a single solution to a multiple application environment.
Rather, they seek to guide the user to make the right decisions that will
result in a fit for purpose and lowest life cycle cost solution for the
given application. Under different environments and for specific
business or technical conditions the ETPs will require interpretation for
application to the specific facility to be built. The factors to be taken
into consideration when making interpretations are generally discussed
in the commentary of the document.

1.3.2 BP Group ETPs are Voluntary but Contain Requirements

BP Group ETPs are not mandatory, but do contain requirements. The

site or project Engineering Authority is responsible for the choice of
standards and practices to be used. If the user decides to use (follow,
apply, comply with) an ETP, the user must either fully meet any
requirements stated in the ETP, or document a deviation from the
requirements. The use of the word "shall" shall not be avoided on the
grounds that compliance with the standard is considered voluntary.

Getting HSE right Element 5 articulates the need for "using recognized
standards" and Element 5.3 includes the expectation that "Design,
procurement and construction standards are formally approved by the
designated technical/engineering authority". To "use", "utilize",
"follow" (or even "comply with") an ETP or any other technical
practice or standard means to have addressed the requirements of that
document.

BP Group ETPs contain requirements where the relevant BP subject

experts, representing the relevant discipline networks that extend
throughout BP businesses, consider that it is important for BP projects
and operations to address the requirement; and either comply (do it) or
document a dispensation that can be audited. Therefore a requirement
is not mandatory, because a dispensation is permitted. And the
document is not mandatory, because the subject experts can not foresee
all the circumstances that an Engineering Authority must consider when
deciding on what is appropriate for the particular project or operation.
ETPs also capture BP knowledge and good practice. It is valid to use
guidance and knowledge from an ETP without addressing the
requirements. However it is not then possible to claim that the ETP as
such has been "used"; only that some of the knowledge has been
extracted from the ETP. The manner of use (or non-use) should be
determined by the relevant site or project Engineering Authority.

ETP INTRODUCTION Feb 2002

Page 14
1.3.3 Adapting to the BP Group ETPs

For site specific application, the BP Group ETPs are required to be

adapted or supplemented with site specific requirements that may, for
example, arise from:

(a) Specific process requirements based on the fluid being handled

(b) Local factors, including relevant regulations and standards.
(c) Technical/commercial factors, e.g. nominated suppliers.
(d) Technical requirements that are specific, and possibly unique, to
the particular project.
(e) Technical requirements that are becoming BP standard or good
practice, but have not yet been incorporated into the BP Group
ETP documents.

The user of the ETP document should consider what if any

documentation or other requirements to place on the
supplier/contractor. The Commentary may give guidance on other
requirement choices that could be made. The user is therefore expected
to ‘edit’ the BP document in order to create a job-specific document for
his/her project, site, Business Unit, Region, Country, or Stream.

It is strongly recommended that users of BP Group ETPs are members

of the ETP Community of Interest (old STANDARDSLINE) in order
to ensure that new issues and revisions of BP Group ETP documents
are received promptly and consistently.

1.3.4 Referencing New ETPs before their Creations

Since the ETP documents for all categories will be developed over a
period of 3 to 4 years, there will be times when a newly created ETP
will need to reference a to be created or future ETP document.

Example: The instrument and control core team was creating the
control room document. They needed to reference an ETP document
that was not created yet in the Telecommunications area. The ETP
category number for Telecommunications is 59. The current RPSEs
cover the need. Reference – In the control document you can reference
ETP GP-59-13. You can further identify in brackets the current
available heritage document that the new GP in the future would
replace. Therefore, the reference would be written as;
“control room telecommunications should be covered by
ETP GP-59-13 (RP 59-13) …..”. You may also reference the applicable
ACES or APCES or other heritage document in the parentheses.

1.3.5 Alternative Referenced Standards

Referenced standards may be replaced by equivalent standards that are

recognised at the point of application provided that it can be shown to

ETP INTRODUCTION Feb 2002

Page 15
 the satisfaction of the purchaser's professional engineer that they meet
or exceed the requirements of the referenced standards.

Standards from differing sources, even if covering the same scope, are
rarely fully equivalent or identical in application. This is seen
particularly in engineering material specifications. A useful concept is
to list 'acceptable alternative' standards that may be regarded as
equivalent for a particular set of stated service conditions; however,
differing supplementary conditions may be needed for each alternative
standard.

1.3.6 ETP Shared Learnings Capture System (Feedback)

Any need for the updating of existing documents or for the

development of new documents, is dependant upon the feedback of
shared learnings and information from users. The ETP Project Team
has developed a lessons learned and BP knowledge and know how
capture system. The ETP Shared Learnings Capture System is based on
the following user needs:

• Provides lessons learned data base categorized per the ETP

categories, sub-categories, headings, streams, regions, etc.

• User friendly capture of lessons through e-mail integration and

other COE documents

• User input is of simple consistent format and is not time

consuming

• Current lessons can be easily incorporated in the new system

• Web based application and accessible from all BP locations

• Technical Networks engaged to validate lessons with one

individual as primary

• Can capture site specific lessons & know-how and share across
all BP Streams and BUs

ETP INTRODUCTION Feb 2002

Page 16
 Shared Learnings Capture System
BP Knowledge Lesson
Lesson BP Experience
email,
email,memo,
memo,
document,
document,etc.
etc.

Input Template < 10-15 Within

minutes
Original
BU
Lesson Lesson
Not Valid
Within
Stream
BU’s
Technical
Fully
Networks
Lesson
Searchable Validated
Database Cross
Stream Group
ETP

The shared learning capture system can take several forms of attached
COE documents after the input template is filled out :

(a) Electronic Mail notes, excel, power point slides

(b) Technical reports and word documents
(c) 'Incident' reports.
(d) Project Safety Reviews
(e) Network discussions

1.3.7 Use Of Language

Throughout the BP Group ETPs, the words 'will', 'may', 'should', 'shall'
and 'must', when used in the context of actions by BP or others, have
specific meanings as follows:-

(a) 'Will' is used normally in connection with an action by BP, rather

than by a contractor or supplier.
(b) 'May' is used where alternatives are equally acceptable.
(c) 'Should' is used where a provision is preferred.
(d) 'Shall' is used where a provision is mandatory.
(e) 'Must' is used only where a provision is a statutory requirement.

The meanings above do not apply to the Commentary, where the

language is flexible as in normal English usage except where clauses
suitable for inclusion in the Requirements may be given.
In general, the use of language guidelines as noted in the excerpt from
the ISO Directive below apply for the ETP documents. However, due
to the nature of the ETP documents as Group, Requirements are more
likely specified as “should” rather than the more mandatory “shall”.

ETP INTRODUCTION Feb 2002

Page 17
 ISO Directives Part 2:2001 - Annex G
(normative)
Verbal forms for the expression of provisions
NOTE Only singular forms are shown.

The verbal forms shown in Table G.1 shall be used to indicate requirements
strictly to be followed in order to conform to the standard and from which no
deviation is permitted.

Table G.1 - Requirement

Verbal form Equivalent expressions for use in exceptional cases

shall is to

 is required to

 it is required that

 has to

 only … is permitted

 it is necessary

shall not is not allowed [permitted] [acceptable] [permissible]

 is required to be not

 is required that … be not

 is not to be

Do not use “must” as an alternative for “shall”. (This will avoid any confusion between the
requirements of a standard and external statutory obligations.)
Do not use “may not” instead of “shall not” to express a prohibition. 

To express a direct instruction, for example referring to steps to be taken in a test method, use the
imperative mood in English.
EXAMPLE “Switch on the recorder.”

The verbal forms shown in Table G.2 shall be used to indicate that among
several possibilities one is recommended as particularly suitable, without
mentioning or excluding others, or that a certain course of action is preferred
but not necessarily required, or that (in the negative form) a certain
possibility or course of action is deprecated but not prohibited.

Table G.2 - Recommendation

ETP INTRODUCTION Feb 2002

Page 18
 Verbal form Equivalent expressions for use in exceptional cases

should it is recommended that

 ought to

should not it is not recommended that

 ought not to

In French, do not use “devrait” in this context. 

1.3.8 Standard Definitions

The BP Group ETP documents generally utilize the following

standardized definitions to maximise consistency in the applicable
documents. ETP documents may however list other definitions and
these definitions are included explicitly in the ETP document.

The following standard definitions are recommended for general use.

But note that any specific application of the terms and responsibilities
for the parties defined is a matter for the relevant Conditions of
Contract.

BP The BP p.l.c., an associate or subsidiary, or other

organization as defined in the Conditions of
Contract on a project.

contractor a main contractor responsible to BP for the

design and/or supply of goods or services, for a
complete project or installation.

inspector the person appointed by the supplier or the

purchaser to carry out engineering inspection in
the supplier's works

project a specific task to be completed to a specification

within an agreed time and to an agreed budget.

purchaser a contractor acting on behalf of BP, or BP itself

in the case of a direct purchase.

Quality assurance all those planned and systematic actions

(QA) necessary to provide adequate confidence that a
product or service will satisfy given requirements
for quality.

ETP INTRODUCTION Feb 2002

Page 19
quality manual a document setting out the general quality
policies, procedures and practices of an
organisation.

quality plan a document setting out the specific quality

practices, resources and sequence of activities
relevant to a particular product, service, contract
or order.
quality system the organisation structure, responsibilities,
activities, resources and events that together
provide organised procedures and methods of
implementation to ensure the capability of the
organisation to meet quality requirements.
supplier the organisation, company or agency that is
contracted to provide goods or services to BP.
third party an impartial body, possessing the
inspectorate necessary competence to verify that designs
and/or manufacture satisfy the specification and
purchase order requirements.
vendor the main body responsible for supply and/or
manufacture.

ETP INTRODUCTION Feb 2002

Page 20