Professional Documents
Culture Documents
ANG-RGN-OSS-QMS-PRO-0052 Rev A1 Angola Regional Anomaly Management Procedure PDF
ANG-RGN-OSS-QMS-PRO-0052 Rev A1 Angola Regional Anomaly Management Procedure PDF
Asset/Block: Angola
Author(s): Stuart Easton
Owner: Alistair Fox – Tony Hunt
th
Issue Date: 26 September 2012
Issuing Department: Subsea Operation – Integrity management
Abstract: This document defines the procedure that shall be used on Subsea systems to manage
anomalies via a process of monitoring and/or rectification.
Alistair Fox
om DN: cn=alistair.fox@uk.bp.com
Date: 2012.09.27 14:00:34 +01'00'
Revision Control
Revision Description Date Prepared Reviewed Approved
17-Sept- S Easton/ A
A1 Issued for review L Gifford A Fox
2012 Da Costa
CONTENTS
1 PURPOSE ....................................................................................................................... 4
2 SCOPE ............................................................................................................................ 4
3 ABBREVIATIONS........................................................................................................... 7
4 ANOMALY MANAGEMENT PROCEDURE................................................................... 8
4.1 Anomaly Management ................................................................................ 8
4.2 Anomaly Management Strategy .................................................................. 8
4.3 Overview of Procedure................................................................................ 8
4.4 Anomaly Management Procedure ............................................................... 9
4.4.1 Systems to detect or identify anomalies ........................................................9
4.4.2 Anomaly Allocation.......................................................................................10
4.4.3 Risk, Criticality & Status ...............................................................................10
4.4.4 Initial Anomaly Classification ........................................................................11
4.5 Formal Anomaly Risk Assessment ............................................................ 12
4.6 Feedback of Comments to the Subsea Contractor.................................... 13
4.7 Anomaly Management Documentation..................................................... 13
5 Process Flow Charts ................................................................................................... 15
5.1 Process Map Key....................................................................................... 15
5.2 Umbilicals, Risers, Flowlines (and Oil Offloading Lines for GtP) Team...... 16
5.3 Subsea Hardware Team ............................................................................ 18
5.4 Subsea Controls Team .............................................................................. 20
5.5 Flow Assurance Team ............................................................................... 22
6 KPI Build....................................................................................................................... 24
6.1 KPI build for ROV Identified Anomalies ..................................................... 24
6.2 KPI build for Excursion Anomalies ............................................................. 24
1 PURPOSE
This document details the management procedure by which subsea anomalies, identified
within BP Angola Subsea Operations, shall be assessed and rectified.
It defines the process for anomaly management by the assessment of risk through a
structured process of assessment, prioritisation, intervention and lessons learned.
2 SCOPE
BP employees and contractors with roles and responsibilities for the assessment,
prioritisation or remediation of anomalies within BP Angola Subsea Operations function.
The responsible Engineering team for specific equipment subsea and, as agreed, in the
interface with topsides is defined in the RAPID1 and should be referred to directly. However
the following may be assumed:
Subsea Hardware
• Subsea Structures including Trees and Manifolds
• Rigid Jumpers
• Valves & Connectors
Subsea Controls
• Hydraulic Fluid Distribution System, including the Topside interface
• Electrical Distribution System, including the Topside interface
• Subsea Control Modules
• Riser Base Gas Lift Control System and HRTMS
• ICS and Controls communications
• Data from Corrosion probes, MPFMs, FSMs
Flow Assurance
• Hydrate and slugging control
• Internal blockage
1
ANG-RGN-OSS-MTX-0001 IM Regional System Rapid A1
Integrity Management
• Internal corrosion of subsea equipment, structure and hardware
• Subsea Chemical Distribution System (skid managed by Asset Team)
3 ABBREVIATIONS
B18 Block 18
B31 Block 31
CP Cathodic Protection
FMC FMC Technologies Incorporated
FMECA Failure Modes, Effects and Criticality Analysis
FPSO Floating Production Storage and Offloading
FTA Flowline Termination Assembly
FSM Flowline Signature Monitoring
GtP Greater Plutionio
HRT Hybrid Riser Tower
HRTMS Hybrid Riser Tower Monitoring System
I Indicator
ILT In-line Tee
IM Integrity Management
IMMS Integrated Marine Monitoring System
KPI Key Performance Indicator
MPFM Multiphase Flowmeter
PI Performance Indicator
PMR Planned Maintenance Routine
PSVM Plutao, Saturno, Venus and Marte
NCR None Compliance Report
OMS Operating Management System
OOS Out of Straightness
OWP Offshore Work Pack
PE Principal Engineer
ROV Remotely Operated Vehicle
SLHR Single Leg Hybrid Riser
SIMS Subsea Integrity Management System
SPU Strategic Performance Unit; replaced in 2011 by regional Engineering and Technical
Authorities
URFOOL Umbilical, Risers, Flowlines and Oil Offloading Lines
WSE Written Scheme of Examination.
2
ANG-RGN-OSS-QMS-PRO-0042 Assessment, Prioritisation and Management of Risk Procedure
3
The BP Operating Management System Framework, Part 3 – OMS Performance Improvement
Cycle, GFD 0.0-0003
The review and modification of these documents is a separate activity that does not form
part of this document. It is, however, an input to their revision as shown in Figure 1.
Identifier Description
Riser Tower All structural items of Riser Towers from the flexible pipe riser hang-off to
the suction anchor (inclusive).
Riser All hard and flexible risers, inclusive of topsides pipe work up to the
emergency shut down valve, dynamic jumpers and spools from the
FPSO to FTAs
Flowline Flowlines and spools from Manifolds to FTAs and from Manifolds to ILTs
Jumper Spools and jumpers from Xmas trees to Manifolds and from Xmas trees
to ILTs
OOL GtP Oil Offloading Lines from FPSO to Calm Buoy
Umbilical All umbilicals including those to the FPSO.
Tree Xmas trees
Structures Manifolds, Flowline Termination Assemblies, In-Line Tees
RTMS Riser Tower Monitoring Systems including all instrumentation, controls,
sensors and acoustics
Controls All subsea control and monitoring systems (excl RTMS) including topside
related termination units and power supplies
Flow Assurance All flow assurance and internal corrosion
Once the BP anomaly identifier discipline code has been advised, all organisations involved
in the identification, assessment or rectification of anomalies shall include it in the title or
descriptive text of the anomaly.
4
GP32-40 In service Inspection and Testing - Common Requirements for Civil and Mechanical
Equipment
Anomaly Criticality
Error Anomaly entered in error
Low Anomaly which poses no Near or Medium term threat to the system
0 < Risk Score < 6 integrity, but may deteriorate and pose a threat in the Longer term
Medium Anomaly which does not pose a Near term threat to the system integrity
6 < Risk Score < 9 but may deteriorate and pose a threat in the Medium term
High Anomaly which poses a Near term threat to the system integrity
9 < Risk Score
Anomaly Status
Close out Error and Insignificant threats or anomalies that have been rectified and
need no further monitoring
Monitor Anomalies associated with Medium or Long Term degradation process
and which are managed by assessing degradation progress over time
Referred Anomaly for which additional information, calculation or analysis is
required before it can be given a Status of Monitor or Remediate
Remediate Anomaly for which Remediation is required to reduce Criticality
On identification anomalies are processed through two distinct steps. First they are given
an initial priority, which is agreed on by the relevant BP engineering team. This sets the
timeline on the KPI and defines how quickly the formal risk assessment must be completed.
Secondly, a formal technical evaluation is completed providing a detailed understanding
and risk assessment of the anomaly.
Error Classification
Error classification is used for anomalies which have mistakenly been identified and
entered into the anomaly management process.
Errors can be closed out by agreement at the monthly Anomaly Management Meetings
held with the Engineering Contractor. Reporting of close-out shall be included in the
Anomaly Management Report and a record of the error maintained in the Anomaly
Database.
Low Criticality
A Low Criticality anomaly is one that has a risk score of 6 or less on the standard BP
Group Risk Matrix2.
Low Criticality anomalies cannot be directly closed-out. Typically Low anomalies are
monitored in case of change pending assessment of the risk.
Low Criticality anomalies must be included in the Anomaly Management Report if they
are given a status of Referred or Remediate, however any Low criticality Anomaly may be
included in the Anomaly Management Report if deemed appropriate by the responsible
PE.
Medium Criticality
A Medium Criticality anomaly is one that has a risk score of between 6 and 9 on the
standard BP Group Risk Matrix2.
Medium Criticality anomalies are likely to be either Monitored or Referred for further work
to better understand the anomaly, its root cause and its deterioration timescale. Following
referral a Medium Criticality anomaly may have its criticality adjusted or may remain as
Medium. If it remains as Medium then status will be Monitor or Remediate.
Medium Criticality anomalies cannot be directly closed-out. A Medium Criticality anomaly
must be remediated to allow close-out.
The Anomaly Management Report summarises the status of the anomaly and details the
relevant supporting documentation. Supporting documentation shall be controlled with a
BP VNET document number referenced and/or appropriate substantiated references
documented in the Report.
High Criticality
A High Criticality anomaly is one that has a risk score greater than 9 on the standard BP
Group Risk Matrix2.
High Criticality anomalies are likely to be referred for immediate work to better understand
the anomaly, its root cause and its deterioration timescale. Following referral a High
Criticality anomaly may have its criticality adjusted or may remain as High.
If an anomaly remains at High Criticality following referral its Status will be Remediate.
All High Criticality anomalies shall have a Technical Document or Position Paper
produced and referenced in the Anomaly Management Report.
Technical Documents
All anomalies, other than those raised in error, shall be assessed and the results of the
assessment documented in a controlled Technical document. The approval of a technical
document confirms that any appropriate updates should be made to the FMECA. All
Technical Documents shall be given an official BP document number and stored on the
VNET file store. In the event of an anomaly being given the status of Refer or Remediate,
the anomaly may be re- assessed following the implementation of further actions and the
results of the assessment documented in an update to the initial Technical Document.
All Technical Documents are referenced in the Engineering Team Anomaly Management
Database and the Anomaly Management Report.
Scoping Documents
Should additional work be required from a third party a Scoping Document shall be
prepared to define the work required and brief the contracted party on what is expected of
it.
As with Technical Documents, Scoping Documents should be controlled via VNET with an
official BP file name a record of which is to be referenced in the Engineering Team
Anomaly Management Database and the Anomaly Management report.
And rule
Or rule
5
ARIS Quick Modelling Guide
5.2 Umbilicals, Risers, Flowlines (and Oil Offloading Lines for GtP) Team
URF anomalies are identified through the following routes:
ROV Inspection
Integrated Marine Monitoring System, IMMS (GtP only)
Alerts System (PSVM only)
Alarms System
Topsides Inspection and Testing
Pigging and In-line Inspection
ROV Surveys include but are not limited to visual inspection data available as video files
and screen grabs, cathodic protection measurements and positional scanning or recording.
The subsea contractor maintains a live Coabis database of all anomalies observed during
an inspection, including pipeline inspections. Each anomaly record shall as a minimum
contain sufficient information to define the extent and nature of the anomaly. Inspection of
anomalies observed in previous campaigns should be as consistent as reasonable
practicable with regards to the existing data to aid comparison over time.
The subsea contractor shall provide an inspection report as defined by the appropriate
inspection procedure. This should be issued on a timely basis and no later than 30 days
after the inspection.
The subsea contractor shall ensure that the offshore live database is included in the
company’s master Coabis database following any campaign of work.
As well as ROV surveys anomalies may be discovered through riser tower monitoring and
other systems. These anomalies will be added to the Coabis master database only if they
affect any subsea contractor work.
For GtP the upper of the two OOLs is instrumented to provide pipe stresses and
inclinations below the flex joint at the Calm Buoy end. The position of the GtP Calm Buoy,
both globally and with respect to the FPSO, is also continuously recorded. As for the GtP
RTMS both these systems are part of the overall GtP IMMS system.
GtP and PSVM have separate Alarm Systems that provide real time alarming in the FPSO
control rooms6. If any of these channels alarm the FPSO Subsea Supervisor will initiate an
appropriate level of response. Triggering of alarms and initial BP response fall outside the
Anomaly Management Process. However, spurious or false alarming can give rise to an
anomaly.
6
ANG-B18-CMM-SCH-013 Alarm and Trip Schedule for Subsea System
ROV Surveys include but are not limited to visual inspection data available as video files
and screen grabs, cathodic protection measurements and positional scanning or recording.
The subsea contractor maintains a live Coabis database of all anomalies observed during
an inspection, including pipeline inspections. Each anomaly record shall as a minimum
contain sufficient information to define the extent and nature of the anomaly. Inspection of
anomalies observed in previous campaigns should be as consistent as reasonable
practicable with regards to the existing data to aid comparison over time.
The subsea contractor shall provide an inspection report as defined by the appropriate
inspection procedure. This should be issued on a timely basis and no later than 30 days
after the inspection.
The subsea contractor shall ensure that the offshore live database is included in the
company’s master Coabis database following any campaign of work.
As well as ROV surveys anomalies may be discovered through riser tower monitoring and
other systems. These anomalies will be added to the Coabis master database only if they
affect any subsea contractor work.
GtP and PSVM have separate Alarm Systems that provide real time alarming in the FPSO
control rooms6. If any of these channels alarm the FPSO Subsea Supervisor will initiate an
appropriate level of response. Triggering of alarms and initial BP response fall outside the
Anomaly Management Process. However, spurious or false alarming can give rise to an
anomaly.
A live database of all anomalies is maintained. This contains anomalies observed during an
inspection, including topside and ROV equipment and pipeline inspections. The anomaly
record shall as a minimum contain sufficient information to define the extent and nature of
the anomaly. Inspection of anomalies observed in previous campaigns should be as
consistent as reasonable practicable with regards to the existing data to aid comparison
over time.
Anomalies identified via alarms and monitoring should also be included in the central
Subsea Controls Anomaly Database, stored on AngolaOne, as a single point of reference.
6 KPI Build
To effectively track the progress of an anomaly from detection to close out a series of
performance management indicators have been developed. These form a three tier
performance management system consisting of the following:
Indicators (I)
These are small, low level items which, whilst on their own not impacting on the overall
health of the anomaly management system they are indicative of a failure and can
provide an important guide as to where a problem lies, should one be identified.
Performance Indicators (PI)
These group together a series of Indicators. Whilst the PI can have its own definition
which must be met for it to be green it typically reflects the indicators it groups together. A
single red Indicator, however, does not necessarily affect the state of its PI; rather it
provides a guide. Should the PI not be met these may identify where the underlying
problem is.
Key Performance Indicator (KPI)
The KPI is a weighted summary of the Performance Indicators. A single red PI may cause
the KPI to be red.
Figure 3 KPI build for the URF and Subsea Hardware teams