Professional Documents
Culture Documents
This paper was prepared for presentation at the SPE Digital Energy Conference and Exhibition held in The Woodlands, Texas, USA, 3–5 March 2015.
This paper was selected for presentation by an SPE program committee following review of information contained in an abstract submitted by the author(s). Contents
of the paper have not been reviewed by the Society of Petroleum Engineers and are subject to correction by the author(s). The material does not necessarily reflect
any position of the Society of Petroleum Engineers, its officers, or members. Electronic reproduction, distribution, or storage of any part of this paper without the written
consent of the Society of Petroleum Engineers is prohibited. Permission to reproduce in print is restricted to an abstract of not more than 300 words; illustrations may
not be copied. The abstract must contain conspicuous acknowledgment of SPE copyright.
Abstract
This paper presents examples of the principles of “analytics” applied to well integrity, and the experiences
gained in using the results over the past 10 years to manage certain risks associated with well operations.
Analytics are implemented using a system that generates a collection of reports and are distributed daily
to subscribers, including engineers, listing wells with potentially anomalous conditions. Example anom-
alies include wells with annuli pressure above specified operating limits, annuli missing pressure readings
or defined pressure limits, and annuli exhibiting pressure behavior indicating potential communication
between annuli. The analytical engine queries databases containing pressure entries, operating limits,
planned actions, and other well integrity data repositories to generate the reports.
The resulting reports are a component of an integrated work process that manages wells with potential
anomalies. The reports are distributed to engineers and managers for their review and initiation of
appropriate actions, including annulus bleeds, well intervention tests, and risk assessments.
Introduction
A definition of “analytics” is the discovery and communication of meaningful patterns in data. Especially
valuable in areas rich with recorded information, analytics relies on the simultaneous application of
statistics, computer programming and operations research to quantify performance. Analytics often favors
data visualization to communicate insight. (Reference 1)
Managing the integrity of a large collection of wells is a good application of analytical principles. A
variety of well performance information is collected, including tubing and annulus pressures, up-time,
well tests for production volumes, sand production rates, valve tests, and inspections of surface equip-
ment. Parameters are specified for wells such as annulus pressure limits, allowable sand rate, known
defects, required tests, preventative maintenance, and inspection frequency. For a large well stock,
monitoring the relationship of all the performance information with the parameters is a daunting task.
Application of analytical principles provides a methodology to effectively utilize all the information to
manage well integrity.
2 SPE-173434-MS
Data Sources
A key requirement in the application of analytics is data. Information is needed, in a format that can be
queried, before any meaningful application of analytics can be done. From a well integrity perspective,
necessary information includes:
● List of wells.
● Annulus pressure values and limits.
● Well test and injection rates.
● On/off status.
● Safety valve locations, test frequency and status.
● Annulus bleeds.
● Intervention activity.
● Well barrier status.
● Anomaly reports.
Responsibility for collecting and maintaining the needed information is shared by multiple teams
(Figure 1). The Production Engineering (PE) team maintains the list of wells, and the annulus pressure
threshold that will initiate additional review. The Operations team conducts well tests, starts and shuts-in
wells, checks and bleeds annulus pressure, and tests surface and sub-surface safety valves (SSV & SSSV).
Information relating to these activities is also maintained using dedicated applications. The Wells team
conducts intervention activities, investigates anomalous conditions, and maintains inventories of well
equipment including SSSVs. Dedicated solutions (or applications) that read/write to databases are used to
improve data collection processes. Access to this information is managed through a “Data Integration
Layer”, simplifying access to the information and streamlining troubleshooting.
specified information presented. The My Reports system consists of report generation and distributed
modules. At a system-specified time, code modules query databases containing pressure entries, operating
limits, planned actions, and other well integrity information contained in databases. Filters are applied and
variables are compared as specified in each report section. The resulting list of wells is assembled into
tables with pertinent information, the reason for well being included in the listing is highlighted, and the
table is then inserted into the body of an email. Once all the sections included in the particular report have
been generated, the email is distributed to the users subscribed to the report.
A user interacts with the My Reports system to select and manage desired reports. The “Catalog”
screen presents a list of reports available for a user to subscribe (Figure 2). The user selects a report,
completes any user-preference options and selects “Subscribe” (Figure 3). The user then starts receiving
the reports in their email at the specified delivery frequency. If a user no longer desires to receive a report,
they return to MyReports and access the “Subscriptions” page that lists their current reports. They then
select “Unsubscribe” to stop receiving the report (Figure 4).
Figure 4 —The My Reports page where a user maintains report preferences and can unsubscribe from a report.
To keep the report to a manageable size a number of acronyms are used. These include:
● T, A, B, C, D: tubing or annulus pressure.
● NO: Not Operable, a well not authorized to be operated due to a well integrity defect.
The Notes sections make heavy use of acronyms. These are defined and described in the specific field
operating procedures.
Example analytical reports include:
SPE-173434-MS 5
Anomaly report
The intent of this section is to identify wells that have been identified and reported through a separate
anomaly reporting tool with their corresponding notes. The anomaly tool is available to many users and
is intended to allow logging initial anomalous observations. In the reporting tool, the user enters the well
name, selects the assigned action group from a dropdown list (e.g., well integrity engineer, petroleum
engineer), and enters the initial anomalous observation. A summary of the record is then emailed to the
assigned action group for review and further updates. This report section then lists the well name, the
number of days the anomaly record has been open and who is responsible for further progress to address
the well anomaly.
Not Operable wells with annulus pressures greater than 500 psi
This report section helps prioritize risk mitigation efforts on wells with well barrier defects. The section
displays wells with the highest annulus pressures at the top to focus attention and efforts.
Figure 11—Not Operable Wells with annulus pressure greater than 500 psi
AxB pressures within 100 psi and A pressures above 250 psi
The intent of this section is to identify potential AxB annulus communication. Wells with A and B annulus
pressures within 100 psi, and the A annulus pressure above 250 psi are listed. The additional criteria of
the A annulus pressure above 250 psi helps to exclude shut-in wells with no or low annulus pressures.
Figure 13—AxB pressures within 100 psi and A pressures above 250 psi
Figure 15—An annulus pressure plot. One is provided for each well listed in the TxA report.
SPE-173434-MS 9
Compliance work
This report section lists wells with testing due within the next 90 days. This includes testing required by
both regulatory agencies and by company standards. The report is further delineated to display wells that
are due within the next 30 days to aide in work prioritization.
Figure 22—Wells that have had a WI Status change in the last 24 hours
combine pertinent report sections into a single email. These are distributed daily (or at the user specified
interval) from the MyReports system via email to the WI, Ops and PE Team members. The reports list
wells that are being evaluated for potential integrity problems, due dates for compliance and conformance
testing, well anomalies under investigation and what team has the action to progress evaluation. Plots of
annulus pressure versus time for wells exhibiting potential well barrier element issues are included. Also
listed are well integrity key performance indicators (KPIs) such as number of wells under evaluation and
that are not operable. The reports are reviewed daily in detail by the Well Integrity and Operations team
members, and actions are appropriately initiated.
The reports are utilized to identify and respond to various types of potential anomalies in producing,
injecting and disposal wells. Wells with indicated anomalies are reviewed, and a determination is made
regarding the appropriate course of action to take. For example, a well with high annulus pressure may
be bled and monitored. Wells with an annulus pressure close to other annuli pressure may have pressure
added to increase the pressure differential to evaluate if communication is present. Additional methods
such as inflow testing, positive pressure testing of annuli, wellhead seal pressure testing, and fluid level
monitoring are employed to help diagnose well problems. Field teams available to investigate the
anomalies include specialists trained in well evaluation in the “Downhole Diagnostic” (DHD) team, and
wellhead technician from the original equipment manufacturer. The reports are also used by Well Integrity
and Operations to identify compliance and conformance due dates for injector annulus testing, surface and
subsurface safety valve testing, and suspended well site inspections.
Observations and Conclusions
The term “analytics” is often used, but its application to well integrity and managing well risk is frequently
not fully applied. The collection of reports described in this paper provides practical examples of how
analytical principles can be effectively applied to a collection of wells to identify potential issues.
Experience with this system indicates it is effective in reducing the tendency of organization to “silo”,
or work in a non-integrated manner. There is more transparent communication of well status and the work
process used to manage wells with potential anomalies. Engineers have easy access, delivered to the email
inbox daily, of wells with potential anomalies, along with the planned evaluation activities and the role
in the organization responsible for implementation of the action. Managers receive reports indicating
progress in well evaluation and can more readily identify areas where additional resources may be
appropriate. This has resulted in driving behaviors to effectively manage these well risks and encourage
a “One Team” approach to managing wells.
Acknowledgements
The authors would like to thank BP management of permission to publish and present this information.
In addition, a number of people have contributed to the development and implementation of these systems,
including but not limited to Arlen Ayojiak, Doug Cismoski, Laurie Climer, Ryan Daniel, Harry Engel,
Paul Green, Lee Helzer, Justin Oprish, Tom Pickard, Teresa Parks, Torin Roschinger, Chris Tzvetcoff,
and the many engineers that have worked in the Alaska well integrity team.
References
1. “Analytics”, Wikipedia article, http://en.wikipedia.org/wiki/Analytics
2. Anders, J. et alet al. Well Integrity Operations at Prudhoe Bay, Alaska. Paper SPE presented at
the SPE Annual Technical Conference and Exhibition held in San Antonio, Texas USA, 24-27
September 2006.
3. Anders, J. et alet al. Enhancing Collaboration Between Engineering and Operations - A Case
Study of Alaska Work Processes. Paper SPE 95813 presented at the SPE Annual Technical
Conference and Exhibition held in Dallas, Texas USA, 9-12 October 2005.