Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 25

Document No.

GP 43-49
Applicability Group
Date Draft 23 October 2005

Guidance on Practice for


Pipeline Integrity Management Systems
(PIMS)

GP 43-49

BP GROUP
ENGINEERING TECHNICAL PRACTICES
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Foreword

This is the first issue of Engineering Technical Practice (ETP) BP GP 43-49. This Guidance on
Practice (GP) is newly created and is not based on heritage documents from the merged BP
companies.

Copyright  2005, BP Group. 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 organization. None of the information
contained in this document shall be disclosed outside the recipient’s own organization
without the prior written permission of Director of Engineering, BP Group, unless the
terms of such agreement or contract expressly allow.

Page 2 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Table of Contents
Page
1. Scope...................................................................................................................................... 6
2. Normative references.............................................................................................................. 6
3. Symbols and abbreviations.....................................................................................................6
4. Overview................................................................................................................................. 7
4.1. Setting up PIMS........................................................................................................... 7
4.2. The PIMS process........................................................................................................8
4.3. Application during project stages................................................................................10
4.4. Application during operations.....................................................................................11
5. PIMS documentation.............................................................................................................11
5.1. Overall approach........................................................................................................11
5.2. Contents of PIMS.......................................................................................................12
5.3. Pipeline system and PIMS overview...........................................................................13
5.4. Regulatory and BP group requirements.....................................................................13
5.5. System description.....................................................................................................14
5.6. Roles and responsibilities...........................................................................................14
5.7. BOD and operations...................................................................................................15
5.8. Risk management......................................................................................................16
5.9. Mechanical or structural integrity................................................................................16
5.10. Protective systems.....................................................................................................17
5.11. Project and operating procedures..............................................................................17
5.12. Emergency response.................................................................................................18
5.13. Incident reporting and investigation............................................................................18
5.14. MOC........................................................................................................................... 18
5.15. Performance management.........................................................................................19
5.16. Documentation and control procedures......................................................................19
6. Further guidance................................................................................................................... 20

Page 3 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Introduction

Pipeline systems onshore and offshore provide a safe and efficient means of transporting a wide range
of fluids from oil, gas petroleum products, to chemicals. They are found in all parts of the BP Group
from upstream production flow-lines, to export pipelines in all segments, including downstream
delivery of raw materials, chemicals, and refined products. Further guidance on what constitutes a
pipeline system is given in GP 43-00.

Effective Pipeline Integrity Management improves operational performance, through enhanced health,
safety, security, and environmental performance and business performance, through increased
availability and productivity. This enhances BP’s license to operate and our objective of being a
responsible operator.

Pipeline Integrity Management is an integrated process with many processes and procedures that are
interlinked (illustrated in Figure 1). It is process of continuous improvement that requires a clear
understanding of the design and operating parameters, risks and reliability, inspection requirements,
and of assessment for continued operation. This cannot be achieved without the use of experienced
people in all levels of our organization.

Figure 1 – Pipeline integrity management system

Audit and
Baseline Inspection &
Training
Assessment Maintenance

PIPELINE
INTEGRITY
Fitness for
Engineering MANAGEMENT
Service
& Design SYSTEM
PDAM
(PIMS)

Repair
Risk & Operation And
Reliability Control & Rehabilitation
Monitoring

To ensure the integrity and reliability of our operations, a management system is used for each
pipeline system. This is known as the Pipeline Integrity Management System (PIMS). This should not
be confused with leak detection or In Line Inspection which may form part of the overall process.

Pipeline Integrity is not something that can be left to the operating phase as many of the key decisions,
taken in the early project phase, directly affect the long term integrity of the pipeline system. These

Page 4 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

include flow assurance, corrosion control, and inspection requirements. Pipeline Integrity
Management is also not just about the physical hardware and the design for structural integrity it is
also about the safe and efficient operations, competency of people, and our response when things go
wrong.

This GP provides the framework for developing an effective Pipeline integrity management system. It
is to be read in conjunction with the wider suite of BP Group Technical practices which provide
specific guidance on many of the points referred to in this GP.

Across the world, regulatory requirements have moved in different directions. In the North Sea there
has been a focus on organisation, responsibilities, and risk based inspections, driven by the UK’s
Health and safety at work legislation. In North America the regulations have tended to focus on fixed
inspection and assessment intervals. This GP recognises the diverse approaches that exist across the
business segments in BP. More particularly the requirements of this GP have been developed based on
the requirements of the BP Group Standard on Integrity Management.

Page 5 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

1. Scope

GP 43-00 defines what a pipeline system is and stipulates that Pipeline Integrity Management System
(PIMS) is established for every pipeline system in use in the BP Group.

This GP provides guidance on the key elements when setting up PIMS as part of an integrated suite of
BP Engineering Technical Practices designed to ensure that the user has best access to best practices,
lessons leant, and other support tools in order to deliver optimum and continuing improvement in
performance.

This GP provides a framework from which PIMS can be developed to meet both Regulatory and BP
Group expectations. It is not the intention of this GP to provide detailed guidance on each of the
elements that make up the framework of PIMS, as this is covered in the other Group Engineering
Technical Practices (ETPs).

It is primarily for use by those responsible for the pipeline system, at any stage of its life, and is
applicable for both project teams and operations. As such, it should be driven by the Engineering
Authority in each Project or Business Unit.

This GP shall be used by project engineering and operations staff whether employees of BP, agency
staff, or companies engaged by BP during a project or operation. If the pipeline is not operated by BP,
the BP representative shall endeavour to ensure that the components of the PIMS are implemented, as
detailed in this standard, and that an agreement is in place for any divergences.

2. Normative references

The following normative documents contain requirements that, through reference in this text,
constitute requirements of this technical practice. For dated references, subsequent amendments to, or
revisions of, any of these publications do not apply. However, parties to agreements based on this
technical practice are encouraged to investigate the possibility of applying the most recent editions of
the normative documents indicated below. For undated references, the latest edition of the normative
document referred to applies.

BP
IMS Group Integrity Management Standard.
GP 32-30 Guidance on Practice for Inspection and Testing of Equipment In Service
- Management Principles.
GP 43-00 Guidance on Practice for Pipeline Systems.
GP 43-06 Guidance on Practice for Responsibilities of an Operator.
MPCP Major Project Common Process.

American Petroleum Industry (API)


API RP 1160 Managing System Integrity for Hazardous Liquid Pipelines.

American Society of Mechanical Engineers (ASME)


ASME B31.8S Managing System Integrity of Gas Pipelines.

3. Symbols and abbreviations

For the purpose of this GP, the following symbols and abbreviations apply:

Page 6 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

BOD Basis of design

BU Business unit

EA Engineering authority

FIMS Facilities integrity management system

IM Integrity management

MAR Major accident risk

MOC Management of change

O&M Operations and maintenance philosophy

PIMS Pipeline integrity management system

TA Technical authority

SIMS Structural integrity management system

SOR Statement of requirements

SPA Single point accountability

WIMS Well integrity management system

4. Overview

4.1. General
Each Business Unit (BU) shall ensure that the approach taken for PIMS is consistent with the Group
policy document for HSE, the Group Integrity Management Standard, together with the Major
Accident Risk process in relation to risk assessment methodology.

When using this ETP reference still needs to be made to local and national regulatory requirements.
This document shall be read in conjunction with BP Group policies and Standards. It shall also be read
in conjunction with the full suite of Engineering Technical Practice documents relating to Pipelines,
Category 43 and in other referenced documents.

4.2. Setting up PIMS


a. The SPA shall ensure that clear roles and responsibilities are established for setting up a
PIMS organisation and delivering PIMS.
b. The PIMS process shall be a live, ongoing process from design to decommissioning. Key
factors for success include:
1. Ownership at the highest level within the BU.
2. Continuous support and input from all levels across the organisation.
3. Clarity on roles and responsibilities.
4. Competency of personnel to develop and meet the PIMS requirements.
5. Open and regular communication and engagement of personnel across all areas for
integrity.

Page 7 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

6. Allocation of sufficient funds and resources to deliver.


c. The PIMS organisation shall be distinctive with its focus being delivery of pipeline
integrity and thus the availability of the pipeline for operations.
The PIMS process is driven by the Pipeline Technical Authority or sometimes
known as the Pipeline Competent Person (PCP).
d. The Pipeline TA shall report directly to the EA (appointed by the SPA) who has
responsibility to ensure that:
1. All aspects of integrity are considered and assessed.
2. Regular communications are maintained across groups involved in the PIMS process.
3. Formal assessment is carried out and recommendations with regard to pipeline
integrity are reviewed, adopted, and implemented.
4. Action tracking is maintained.
5. Preparation of an annual summary integrity report on the pipeline for the SPA.
6. Arranging audits of PIMS.

4.3. The PIMS process


Every pipeline is different and requires detailed assessment and evaluation of the
operating conditions affecting the pipeline and how that compares with the original
design assumptions.
PIMS is an integrated continuous process throughout the life-cycle of the asset that
has at its centre: Risk management, Design and Operation, Inspection, and
assessment. This is supported by competent people with suitable processes and
procedures. The management system combines a number of distinct activities and
processes. The objective of the PIMS documentation and processes is to capture the
key design and operating conditions that may affect pipeline integrity. See Figure 2
below.

Page 8 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Figure 2 – The PIMS process

a. A key element of the PIMS process is formalised assessment that the pipeline system is fit
for continued operation:
1. GP 43-00 requires that the SPA shall establish a PIMS organisation and system for
each pipeline and that this shall be based on Group Standard for Integrity
Management.
2. The SPA shall ensure the technical integrity of the pipeline system during design,
construction, commissioning, and in operation, through the appointment of an EA
3. A formalised review of the pipeline condition and fitness assessment for continued
operation shall be carried out on an annual basis.
4. Recommendations and actions from the review shall be clearly recorded.
This review interval may be adjusted based on the pipeline risk assessment.

Page 9 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

5. The review should be lead by the SPA for the pipeline supported by the EA and
Pipeline TA.
6. The review shall include inspections and reports made throughout the year and should
include each of the elements described in clause 6.
7. Although the pipeline may have many different sections and components for
ownership, design, operation, inspection, and emergency response, the pipeline shall
be addressed and reviewed as one system from the source of pressure to the point of
discharge.
8. The review should include representatives from upstream and downstream facilities
to ensure that the pipeline system can be considered as a whole and that
communications and interfaces are effective.
9. Incidents affecting pipeline safety, integrity, or operation shall be investigated,
recorded, and be included in the review process.
10. The use of PEER assists and reviews should be part of the overall process to ensure
that critical elements have been appropriately identified and that assurance processes
are working effectively and are appropriate for the identified risks.
Based on the results of successive assessments, the risk assessments, inspection
scheme and intervention works may need to be modified.

4.4. Application during project stages


Pipeline integrity starts in the Project phase and continues into Operations. This
cannot be done in isolation and an effective PIMS process can only be developed if
projects and operations personnel are jointly engaged in developing PIMS from the
Appraise Stage of a project.
Whilst the Project focus is often on capital cost and delivery of the assets it is
important that longer term operational factors are also considered. The
consequence of failure including safety, environment, and business risk often
exceeds the savings made at an early stage in a project life.
The design intent and critical design features are often lost in volumes of project
documentation and as a consequence pipeline integrity is often compromised
through poor communication.
a. During the Project phase, the EA with Operations personnel in the project team shall
therefore address the following areas:
1. Early assessment and management of risks is essential for providing longer term
integrity management of the pipeline.
This is discussed more in GP 43-17 on pipeline risks and in GP 43-01 and
GP 43-02 for the design of onshore and offshore pipelines.
2. The use of an appropriate and effective pipeline route selection should reduce many
of the geotechnical risks and the use of appropriate designs and selection of materials
reduces risks of corrosion or the consequences of third party impact damage.
3. Consider how the condition of the pipeline will be assessed during operation to verify
that the pipeline is fit for continued operation.
The ability to clearly convey the design and construction intent to operation
personnel on handover is a crucial step in what should be a seamless process for
pipeline integrity. Inclusion of Operators in the project team in Select ensures this
happens.
The PIMS framework provides a basis on which key documentation can be pulled
together to provide an integrated and accessible system.

Page 10 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

4. Develop and deliver many of the documents and procedures required to operate the
pipeline. These documents shall be clear and concise, reflecting the key risks and
processes to manage them to ensure that the pipeline integrity is not compromised
during the design life.
5. Key risks and design aspects shall be clearly communicated to operational personnel
and inspection processes and procedures shall be established to verify that the
pipeline is fit for continued operation.
6. If specific designs have been developed, it is important that requirements shall also be
developed to verify that the design is performing as planned and when intervention
works may be required.
7. If designs use materials at the limits of current technology and may have a higher
fatigue element, inspection processes, if not currently available, shall be developed as
part of the project deliverables.
8. Ensure that quality control during construction effectively addresses the risks
identified and does not compromise the longer term integrity of the pipeline system.
Pipeline coating damage, weld defects, or changes to the design can affect the
integrity of the pipeline system.

4.5. Application during operations


a. During the operations phase, PIMS provides the basis for managing the residual risks and
maintenance of the facilities to provide an efficient operation and verification that the
pipeline is fit for continued operation. To achieve this, formalised inspections and
revalidation shall be implemented.
This may include formalised processes to satisfy regulatory authorities.
There have been many incidents recorded across the industry which relate to
failures in operating procedures, competency of personnel, or how we manage the
changes that occur to the facilities during their operating life.
b. The PIMS process is not just about the condition of facilities and the review process shall
therefore address the wider elements included in Integrity Management Standard.
c. If pipeline systems have not had any formal assessments for a number of years and the
condition is unknown, a baseline survey shall be required.
Baseline surveys may include internal inspection, but in many cases in which lines
are not piggable, direct assessment techniques may be needed.
Further guidance on the application of PIMS during operations is given in
GP 43-06.

5. PIMS documentation

5.1. Overall approach


a. PIMS documentation and processes shall reflect and capture the key design and operating
conditions that may affect pipeline integrity and shall provide data in a format that will
assist a formalised annual assessment process verifying fitness for continued operation.
b. Responsibility for each document in the system shall clearly be stated together with how
and when they should be reviewed and updated.
There is no prescriptive style or format available for the suite of documentation and
processes that constitute PIMS.

Page 11 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

c. The approach to documentation should be integrated and decisions often made during the
project phase can directly affect both accessibility to data and ease of updating details.
Systems may be paper driven, but there is a clear preference for systems to be web
based and integrated with pipeline GIS records.
d. Reference should be made to BP Group Procurement and Supply chain management and to
procurement initiatives and to Group Digital Communications Technology when
establishing new systems.
Each section of PIMS requires particular documentation to be developed and
maintained.
e. Clear ownership and the procedure by which PIMS is maintained and updated shall be
established.
f. Data inputs shall be addressed in the quality assurance and quality control procedures.
The ability to access current and relevant data is fundamental to the process of
assessment of the condition of the pipeline. High quality, reliable data is a
fundamental requirement for any assessment of fitness for continued operation.
g. Security of information and control of access to information shall require specific
attention.
h. Use of proprietary systems shall be considered although there is a clear preference to
standardise systems across the group if possible.
There are a number of proprietary systems available and examples of best practice
can be obtained through the EPTG pipeline network with links to a number of
recognised systems.
If electronic systems are used, it should be recognised that data from inspection
sources may change over time as will reporting requirements.
i. Whatever system is used, it should be flexible and shall be suitable for external review,
e.g., by regulatory authorities.

5.2. Contents of PIMS


Each system shall require specific documentation and may require increased focus in some
areas. Based on existing regulatory requirements, the Integrity Management Functional
Standard, and best practice observed across the BP group, the following list provides a basis for
the key processes and documentation that should be collated in PIMS:
a. Pipeline system and PIMS overview.
b. Regulatory and BP Group requirements.
c. System description.
d. Roles and responsibilities.
e. Basis of Design and Operations.
f. Risk management.
g. Mechanical and structural integrity.
h. Protective systems.
i. Project and Operating Procedures.
j. Emergency response.
k. Incident tnvestigation.
l. MOC.

Page 12 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

m. Performance management.
n. Documentation and control procedures.

5.3. Pipeline system and PIMS overview


a. The overall structure and the context in which the pipeline system is operated shall be
provided, including:
1. An overall diagram of the pipeline system.
2. A statement on the objectives and purpose of the pipeline system.
3. Ownership and relation to upstream and downstream assets.
4. PIMS objective.
5. A flowchart for the PIMS process.
6. Reporting and formalised review requirements.
b. If the pipeline systems form just one part of an integrated system, the overall framework
shall be given and it should be noted where common processes are used.
The requirement for the pipeline system is often interpreted differently. In some
instances, this could be a means of facilitating an upstream development.
Conversely, it could be provided for environmental reasons for the capture of CO 2.
The objective of the PIMS is to improve operational performance through enhanced
health, safety and environmental performance, and business performance through
increased availability and productivity.
The overview text can be effectively presented in a number of diagrams and
illustrations to aid the reader.

5.4. Regulatory and BP group requirements


a. The framework and constraints for operation shall be clearly stated. These shall include:
1. A concise statement on planning and controls and which regulatory requirements
apply as these may affect the design, operating, and reporting requirements.
2. Reference to BP Group requirements.
3. Reference to any specific inspection or revalidation requirements.
b. Responsibility for and custodianship of documentation shall be clearly stated. Such
documentation shall be tracked for changes and updates.
c. Reference shall be made to where and how legal documents and permits relating to the
pipeline are kept and maintained.
It is noted that not every country has an established regulatory framework and that
if they do exist, these differ across the world. In the absence of any specific
guidance, GP 43-00, GP 43-01, and GP 3-02 provide an effective basis for the
design and operation of any pipeline system.
BP Group requirements included in the Code of Conduct and Group Standards may
exceed local requirements. It is important to recognise if differences occur.
d. As the pipeline system is developed, there may be specific requirements or restrictions
imposed on the operation as part of the permits to operate, and these shall be captured so
that the Basis of Operation is clearly understood by all those involved. This may include
limits of the life of the pipeline and actions to be taken at the end of the asset life.
e. Legally required documentation shall be clearly identified and documentation shall be
maintained to allow formal review.

Page 13 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Regulations and permits may have specific requirements for maintaining records;
some documentation requirements.
This should include a register of legal documents and details of where these are
kept and updated.
The absence of a legal requirement for maintaining documentation should not
preclude the process of maintaining records, particularly if this relates to critical
safety equipment.

5.5. System description


a. Each pipeline system shall be clearly identified with system limits and interfaces.
b. This shall address both upstream and downstream components from the source of pressure
to the point of discharge.
c. Physical limits of the system shall be identified to ensure that there are no gaps (or
overlaps) in the system.
Most pipeline systems have multiple interfaces; and, there is potential for critical
information to get lost between.
If the pipeline system forms part of a larger integrated system, it is important to set
the overall framework and note where common processes are used.
d. Interfaces shall address design and operability and shall distinguish between ownership
and operation.
e. Separate interfaces shall be established for the components or facilities associated with the
pipeline system.
f. Interfaces shall be clearly established for inspection schemes and between PIMS and
FIMS, WIMS or SIMS.
g. Interfaces shall be clearly identified by a physical point and responsibilities shall be
assigned for each side of the interface together with the process for communication and
transfer of information.
h. Each pipeline system shall be divided into a number of components and may be a
combination of pipe-work and equipment (e.g., topside pumps and pipe-work, pig trap,
riser, sub sea spool piece, SSIV, 500 m (550 yd) zone, etc.).
Components may be based either on physical assets or they may represent a
different level of external threat (e.g. earthquake fault zone).
i. Each pipeline shall require documentation and formalised review.

5.6. Roles and responsibilities


a. Roles and responsibilities shall be clearly established for each section and for each activity
on the pipeline.
b. Clear responsibilities shall be established for Technical Integrity and for Operations.
Many pipelines have functions reporting back to different organisations and, as a
consequence, sight is lost of the overall condition of the pipeline or the impact that
can be caused when one component fails or is not available; for this reason the
pipeline system should be reviewed as a whole.
c. The SPA shall ensure that all people in the organisation are competent and have the tools
and support for the work requested of them.
d. The EA shall establish an assurance process to establish the effectiveness of PIMS and the
competency of personnel to fill the roles.

Page 14 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

e. A Pipeline TA shall be established for the pipeline system.


The Pipeline TA may in some parts of the world be referred to as the Pipeline
Competent Person.
f. The Pipeline TA will report to the EA.
When looking at leading roles and professional engineers there is need to recognise
the need for continued professional development. The Pipeline TA may not have all
of the experience necessary and it may be necessary to supplement this with
experience from outside of the BU.
The role of the project team is given in GP 43-06. The roles and responsibilities of
the EA and Pipeline TA are detailed in the Integrity Management Standard and
guidance notes.
Responsibilities of the Operator are detailed in GP 43-06. This provides guidance
on typical systems and organisations required to deliver PIMS.

5.7. BOD and operations


a. A separate document shall be established in the project Select phase that records the
pipeline system technical design and commercial requirements and operating limits.
This is referred to as the BOD.
b. The BOD shall be based on the operations requirements given by the SOR and O&M
Philosophy.
c. The BOD shall be maintained as a living document.
d. It should describe the current installation design, process, and operating philosophy with
any restrictions or limitations.
e. Typical contents shall include:
1. System description.
2. Current operating service and any future use or intent.
3. Legal or permit requirements.
4. Operational history including (pressures, water cuts, CO 2 and H2S levels).
5. Alignment drawings, process flow diagrams and P&IDs.
6. Materials of construction and as-built records.
7. Hydrotest records.
8. Engineering design and process description.
9. Design and operating parameters and assumptions.
10. Equipment details and performance data.
11. Environmental and soil data.
12. Corrosion management strategy.
13. Pipeline hydraulics.
14. Operating and maintenance philosophy.
15. SOR.
16. Inspection assessment and repairs strategy.
f. The document shall capture any design assumptions and external conditions to provide a
basis for review and MOC.

Page 15 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

g. Information should be only what is required for daily operations.


h. Information should be collated for each component of the system.
i. The future requirements of the system shall be clearly stated (e.g., the need to hand the
pipeline over at the end of a stated period “in good condition”).
This could affect strategies for material selection and corrosion management).

5.8. Risk management


a. The risk management process and the assessments that have been carried out shall be
clearly stated.
b. These shall include clear statements on the assumptions made, level of risk, and actions
needed to mitigate the risk.
c. The assessments shall be carried out on the pipeline system in accordance with Group
Standard Practices and shall address both the threats and consequences.
The MAR is a high level assessment that addresses the whole system and not as
components or segments.
d. To be able to manage risks along the pipeline threats and consequence shall be addressed
along the whole pipeline.
Specific guidance on pipeline risk is given in GP 43-17 and for the MAR process.
e. A risk register shall be established which shall be kept up to date and used to drive all
aspects of the pipeline design and operation.
f. The risk assessment process shall be clearly stated and shall include periodic reviews and
updates as the risk profile changes with time and experience.
The level of risk may be such that a change of design is needed or the inspection
requirements change over time.
g. The risk management process shall clearly state how incidents, other pipelines, or
infrastructure will be recognised and assessed.
Data from other pipeline systems may indicate a particular problem with materials
or a risk that had not previously been recognised. This information may result in
early assessment and intervention.
h. A record shall be kept of the reviews carried out, suitable for audit, the actions taken, and
how the risks have been mitigated in design, construction and operation.

5.9. Mechanical or structural integrity


a. The basis for inspection and assessment of mechanical or structural integrity shall be
clearly stated and shall be based on a risk management process.
b. Each component of the pipeline line system shall be identified and distinctions shall be
made to identify safety critical systems and sections or areas that have a higher risk.
c. Inspection requirements shall be established for each component of the pipeline system
stating the type of inspection, frequency, and anomaly reporting criteria to be used.
d. Interfaces with the inspection requirements for facilities, structures, and well integrity
management systems shall be clearly stated.
Some components may be covered by separate inspection systems such as riser
clamps or floatation supports on flexible risers. It is important that the overall
system is considered when reviewing pipeline integrity.
e. The inspection programme shall comply with GP 32-30.

Page 16 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

f. The assessment and reporting process shall be clearly stated including any reporting to
meet regulatory requirements and how anomalies will be reported and assessed.
g. Documentation requirements shall include how the basis of design and operations will be
updated
h. The basis on which periodic revalidation of the pipeline shall be stated.
Guidance on what should be inspected is developed from the SOR, and Basis of
Design and risk assessment. Protective systems are addressed separately.
i. Clear reporting lines and actions shall be established in the event that an anomaly is
reported.
Guidance on the inspection and assessment of pipelines is given in GP 43-52 and
methods of repair are addressed in GP 43-53.

5.10. Protective systems


a. The pipeline protective systems shall be identified, documented, inspected, and tested to
ensure they meet the design requirements and provide primary containment and protection
to personnel and the environment.
b. Records of assessments, maintenance, and testing shall be kept and changes to set points
shall be clearly recorded and communicated across the pipeline system.
Definitions of what constitutes protective equipment are given in the Integrity
Management Standard implementation guide. Typically, these include shutdown and
over pressure protection equipment and require SIL assessments and routine testing
and maintenance. Records are often required to demonstrate regulatory
compliance.
In many instances safety protective systems are located upstream of the pipeline
(e.g., pressure reduction facilities or compressor shut down) and may be included.
The intent of the PIMS process is to ensure that the system is treated as a whole and
that the pipeline operator is aware of any changes or set points that may have been
made that could affect the integrity of the pipeline. Similarly limitations on the
pipeline (such as corrosion damage) may require changes to the set points.

5.11. Project and operating procedures


a. The policy for maintaining and updating Project and Operating procedures shall be clearly
stated.
b. Operating procedures shall be established during the project for the operational phases of
the pipeline.
In the project, phases producing these procedures should be focused on delivery of
pipeline integrity within the approved budget and schedule; (i.e. interaction between
operations project personnel and the project designers achieves an operable system
of high integrity).
c. During operations, the formal operating procedures in place shall focus on operating within
safe limits and the operating response in the event of an anomaly or incident.
Detailed guidance on operating procedures is given in GP 43-06. Specific guidance
is provided for commissioning activities and the introduction of hydrocarbons into
the system.
Although many view the point at which hydrocarbons are introduced into the system
as being the effective time for handover, Operating procedures should be in place
by the time pipe is placed in the ground to avoid external corrosion or to provide
inspection to prevent third party damage following completion of hydro-test.

Page 17 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

d. The procedures shall address how the pipeline risks and condition are managed over time
and how these are reviewed and assessed.
e. Reference shall be made to the more detailed risk management process outlined in 5.8.
f. Separate operations requirements and procedures shall be established for wax and hydrate
management, corrosion, pigging, and the control of liquid inventories as conditions dictate.
GP 43-50 discusses pipeline pigging and facilities design. The condition of the
pipeline may be affected by wax, hydrates, and deposits left in the line which can
reduce the effectiveness of inhibitors. Many operators have failed to recognise the
need for routine pigging to clean the line before the start of operations (i.e. pre
commissioning) and at best this is too little and too late to provide an effective
corrosion management system. Routine pigging during operations is recommended
for many pipeline systems.

5.12. Emergency response


a. Emergency response procedures shall be established for both the project and operational
phases of the pipeline.
b. These shall be tested on a regular basis, the nature, frequency, and scale of which are
driven by the risk assessment.
c. The policy and process for maintaining and updating emergency procedures shall be
clearly stated.
d. Details of what should be included in the procedures are given in GP 43-06.

5.13. Incident reporting and investigation


a. A formal process shall be established for reporting and investigating incidents.
b. This shall include clear guidelines as to what needs to be investigated and the process to be
followed.
c. Typical components may include:
1. Injury to personnel.
2. Loss of containment.
3. Excursions from the design or operating basis.
4. Operation procedures failures.
5. Protective system failures.
6. Detection of unexpected damage or rates of damage (e.g. high corrosion rates).
d. The procedures shall address the responses needed following an incident.
e. A register of incidents shall be available to allow evaluation of risks and procedures.
f. Lessons and incidents from other projects or operations should also be made available and
included in the process of evaluating risks.
g. Lessons learnt shall be clearly recorded.
An incident or near miss may indicate that the PIMS is inadequate, and is not being
followed. It may arise from a previously unrecognised risk or it could be a failure to
follow-up and close earlier action items.

5.14. MOC
a. A formally documented system for management of change shall be established for the
pipeline system.

Page 18 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

b. This should include changes to:


1. PIMS.
2. BOD and Basis of Operation including change of use.
3. Changes to the Risk Register (such as population density changes or previously
unrecognised risk).
4. Physical modifications.
5. Operations including temporary changes to operation procedures or maintenance
procedures.
6. Inspection and maintenance intervals or assessment techniques.
7. Organizational changes including roles and responsibilities.

5.15. Performance management


a. A documented performance management system shall be established with clear and
achievable targets.
b. Key Point Indicators (KPIs) should reflect the key risks that need to be managed.
c. These should include:
1. System maintenance (planned and unplanned interventions).
2. Procedure adherence (e.g. permits, pigging frequencies).
3. Condition of equipment (testing of safety critical equipment, repairs or use of
clamps).
4. Changes in external risk (number of encroachments with or without permits).
5. Inspection timing and follow up (timing of inspection, reporting, and response).
6. Non conformance report tracking.
7. Timing of inspections, reviews, and formalised assessments.
d. The KPIs shall be periodically assessed and used in the annual pipeline assessment for
fitness for continued operation.
e. The effectiveness of PIMS shall be verified by regular audit and review and included in the
overall business performance process.

5.16. Documentation and control procedures


a. Documentation and control procedures used in the development and management of PIMS
shall be clearly documented.
b. Controls shall be established for data entry and quality; access and security.
c. Audit protocols shall be established to demonstrate regulatory compliance and
conformance to Group reporting requirements and quality assurance.
d. The ability to access data from construction to abandonment shall be established at an
early stage in the project development.
e. Suitable provision shall be made for maintenance of long term records and for maintenance
of legal documentation, including permits, approvals, and easement details.
f. Audit protocols shall be established for each part of PIMS.

Page 19 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

6. Further guidance

a. Reference has been made to other GPs throughout this document.


b. Specific reference on PIMS can be found in API 1160 for liquid systems and
ASME B31.8S for and gas systems.
c. Further guidance can be found in Guidelines for Setting up and Operating a Pipeline
Integrity Management Scheme.
d. The principle requirements of the guidelines have not changed and many of the templates
and roles and responsibilities could be used.
e. A useful web link is
http://integritymanagement.bpweb.bp.com/technical_integrity/pipeline_IM/original/Pipelin
e%20Intergrity%20Management_V2/PIMS%20Manual%20%20%20Pipeline%20Integrity
%20Management%20V2.pdf

Page 20 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Annex A
(Normative)
Annual assessment

The formal assessment for continued operation shall typically address the following:

a. Timing: Annually following preparation of the statement on pipeline operation and


condition. Timing may be dictated by regulatory or shareholder requirements.
b. Attendees: SPA, EA, Pipeline Operator and Pipeline TA, Inspection Authority,
Representatives from across the system (e.g., Platform, pipeline, Terminal).
Typical agenda:

a. Report on operations and condition of the pipeline system including surveys and
revalidation work carried out in the past year and the current operating status including
protective systems.
b. Review of changes that may affect the operation of the pipeline system including
regulations, Group requirements, physical modifications, and operating conditions.
c. Review of the incidents that affect the pipeline, the risk register, and anything that may
affect major accidents assessments, operating procedures, inspection or preventative
measures.
d. Review of emergency response preparedness.
e. Current condition of the pipeline including the adequacy of protective systems such as
chemical inhibition, cathodic protection and maintenance pigging.
f. Status of current operating procedures and competency of personnel.
g. Statutory reporting requirements.
h. Assessment of whether the pipeline is fit for continued operation.
i. Actions needed to allow continued operation included inspection or revised operating
conditions.
j. Date of next review.
The minutes of the meeting should be formally recorded including those present, key points of
discussion, actions to be taken, and a statement of fitness for continued operation.

Page 21 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Annex B
(Normative)
Key roles and responsibilities

Role Key roles and responsibilities associated with PIMS


SPA (sometimes known as the The SPA is responsible for:
Pipeline Responsible Person) • The overall safe operation and condition of the pipeline system (May also be
Typically this will be the legally responsible for the pipeline system).
Performance Unit Leader • Delegation of responsibility where appropriate.
(PUL) or the Business Unit
leader (BUL) depending on the Ensuring that roles and responsibilities are clear and that people are competent to
size of the asset. carry out their roles.
If multiple pipeline systems are • Ensuring that adequate resources and funding are available for maintaining the
in operation, the detailed pipeline in a condition that is fit for continued operation or takes actions as
review may be delegated; necessary to remove it from service.
however, the SPA is still • Ensuring that a PIMS process is in place and that a formal assessment process is
responsible for the safe in place to verify that the pipeline is in a fit condition to allow continued operation.
operation of the overall system • Ensuring that the standards of operation and procedures meet regulatory
and each section in it. requirements and BP Group requirements.
This role is applicable to both • Ensuring that actions arising from the assessment of the pipeline system are
the Projects and Operational implemented.
phases for a pipeline system.
• Issuing formal reports on the condition of the pipeline to the regulator and
shareholders.
EA Appointed by the SPA, the EA’s role for pipeline system typically includes the
following:
• Coordinates the efforts of all TAs to ensure delivery of their responsibilities under
PIMS and ensures regular communications are maintained across the groups.
• Ensures that all aspects of integrity are routinely considered and assessed for the
pipeline system and reports any non compliance to the SPA.
• Ensures technical compliance with Group Standards and Site Technical Practices
and the competence of TAs.
• Prepares the annual summary integrity report on the pipeline fitness for continued
operation for the SPA.
• Ensures that formal assessments, audits and reviews are carried out for the whole
pipeline system and PIMS processes.
• Ensures that recommendations affecting pipeline integrity are implemented in a
timely manner.
Pipeline TA The Pipeline TA is a pipeline discipline specialist who supports the EA. In this
(Pipeline competent person) A context this person is typically responsible for the following:
senior pipeline engineer • Carrying out technical assessments of the pipeline system.
recognised by peers • Completing an integrity review of all collated inspection and testing data, and
collating information on control of production processes, fluid variations, and
monitoring pressure, temperature, and flow rates on an ongoing basis.
• Provides specialist technical input into the development of integrity performance
standards, inspection and test strategies and programmes including suitable
acceptance criteria.
• Coordinates the efforts of other TAs to ensure delivery of their responsibilities
under PIMS.
• Assesses the effect of any process or equipment changes on pipeline integrity.
• Acts as the custodian of all auditable records.
• Makes recommendations to the EA & SPA to assure the ongoing integrity of the
pipeline.
• Issues a statement on integrity assurance in the form of an annual status report,
supported by recommendations if appropriate, to ensure overall integrity.

Page 22 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Role Key roles and responsibilities associated with PIMS


Inspection Authority (IA) Reporting to the Pipeline TA the IA typically:
This role may be as a • Develops and maintains inspection and maintenance requirements for each
contracted position, pipeline section. May also coordinate inspections for FIMS, SIMS and WIMS.
Independent Inspection • Plans and executes of the approved inspections and/or testing programmes to
Authority (IIA) such as Lloyds meet the integrity performance standards.
or DNV. It may be an in-house
role that coordinates inspection • Reviews and approves inspection contractors’ work-scopes and procedures.
activities. The IA may report to • Reviews and interprets inspection results.
the EA if they cover assets • Assesses reported defects and other condition information.
across the Business or
• Reports findings against the set Acceptance Criteria (including updating the
performance Unit.
Maintenance Management System) and advising if the findings affect the integrity of
This role may be combined the pipeline system.
with that of the Pipeline TA for
• Prepares periodic reports on the status of the pipeline system and inspections
smaller systems.
carried out.
• Maintains historical databases of inspection and test results.
• Informs Pipeline TA of Inspection results and any non conformance issues.

Page 23 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Annex C
(Informative)
Typical time-line for PIMS

This supplements the information and requirements of GP 43-00, GP 43-01, and


GP 43-02.
CVP Stage Typical Actions relating to PIMS
Appraise SOR in place.
Concept pipeline design developed with initial route selection.
Overall project risk assessment carried out.
Select BOD and PEP prepared. SOR updated.
Route selection with major geotechnical risks identified.
Preliminary hydraulics completed.
Corrosion risk assessment completed.
Operations Philosophy developed.
Inspection strategy developed.
Risk assessment and register developed.
Define QRA (if required), risk assessment and register updated.
Pipeline Route finalised.
Materials selected with QA/QC in place.
Integrity Management Strategy and high level procedures developed.
Operations Procedures identified and developed.
Preliminary Emergency Response Plan developed.
Execute QA/QC in place during construction.
MOC in place.
Documentation system fed with key data.
Operations procedures completed.
Detailed Integrity Management Plan developed.
Maintenance and inspection plan completed.
Operator and technician training in place with competency assessments.
Emergency response plan procedures finalised and tested.
Procurement of Repair materials, spares& inspection services.
Risk register updated.
Operate IM Standard requirements in place, including PIMS.
Risk register reviewed and maintained.
Operations & Maintenance Procedures in place.
Formal review of pipeline fitness for operation.

Page 24 of 25
Draft 23 October 2005 GP  43-49
Guidance on Practice for Pipeline Integrity Management Systems (PIMS)

Bibliography

[1] GP 43-01 Guidance on Practice for Principles of Onshore Pipeline Design and Project Execution.

[2] GP 43-02 Guidance on Practice for Principles of Offshore Pipeline Design and Project Execution.

[3] GP 43-17 Guidance on Practice for Pipeline Risk Management.

[4] GP 43-52 Guidance on Practice for Pipe Wall Inspection and Analysis of Results.

[5] GP 43-53 Guidance on Practice for Pipeline Intervention and Repair.

[6] GP 48-50 Guidance on Practice for Major Accident Risk.

Page 25 of 25

You might also like