Risk, uncertainty, chance, and related terms are regularly used in the course of daily work in the oil and gas industry. However, there are significant differences between individuals and companies regarding the definition and understanding of these terms, which makes it important to clarify them:

  1. is exposure to danger, harm or loss.  We generally think of risk in terms of financial loss, but there are also environmental, safety and reputational risks.
  2. is the range of possible outcomes, such as the range for permeability or tons of CO2 injected.
  3. is the probability of a given event.
  4. are material occurrences or changes in a particular set of circumstances.
  5. are any source of potential damage, harm or adverse health or other effects on something or someone.
  6. is accomplishing a favorable or desired outcome.
  7. is a project outcome from foreseen or unforeseen event(s) resulting in significant financial, reputational or other losses requiring significant corrections or project cessation.

For low frequency events, a forecast that nothing will happen is likely to be correct most of the time.  Except, of course, when it’s not.  And if the impact is massive, we might refer to it as a Black Swan event (per Nassim Taleb’s book).  Black Swan logic argues that what you don’t know is far more relevant than what you do know.

In fact, many Black Swans can be caused and exacerbated by being unexpected. We ignore or misinterpret early indications of such events and make no preparations to stop or mitigate them. Taleb stresses that time and time again we concentrate on things we know and fail to consider what we don’t know. We need to keep our apertures wide and recognize, as we study the landscape of project failures, that “if it happened, you must admit it’s possible”.

During exploration and appraisal, oil and gas companies accept that there will be failures due to dry holes and non-commercial discoveries. For this reason, they plan to drill enough independent prospects to ensure that the value associated with the commercial discoveries exceeds the program cost (including dry holes). This outcome is referred to as the portfolio effect.

The figure below illustrates the portfolio effect. It shows that as the number of wells drilled increases, the chance of zero geological and zero commercial discoveries decreases. Conversely, the chance of achieving a Net Present Value (NPV) greater than zero increases but is not certain.

We contend that the portfolio effect will not be acceptable to companies, regulators, or the broader societal interests in SCS projects. Failure to inject the contracted CO2 volumes or contain CO2 in the target reservoir or storage zone could result in significant mitigation actions or even project shutdown. The potential cost related to being unable to inject the contracted amount of CO2 is illustrated by the Gorgon project, where the operator has had to acquire and surrender millions of dollars in carbon credits.

To mitigate against this, a complete assessment of subsurface uncertainties and risks combined with estimates of the chance of success and failure are needed. These are discussed in subsequent postings beginning with the definitions for these terms.

An unplanned event, such as injected CO2 ending up in the wrong place, can affect much more than one SCS project.  Such events are publicized and remembered by a public that is skeptical about whether SCS is safe and necessary. This is further exacerbated by existing projects that have failed to deliver on their promises.  Consider, for example, the Gorgon SCS project in Western Australia.  J.P. Marshall (2022), in an article for Clean Technologies concluded that:

There is no indication that the Gorgon project, even if it is fully successful, will reduce the emissions from the fossil fuels it excavates and sells, and given the problems it faced, it seems unlikely that storing a significant amount of emissions produced by burning would be possible.

Opinions such as this highlight the challenge facing the emerging SCS industry. We must be complete, objective and transparent in our evaluations, and include a rigorous assessment of risk. This is especially important for complex, long-term projects where Social License to Operate over many decades is a requirement. In hydrocarbon exploration, we accept that there will be a certain number of failures and so we drill enough wells to take advantage of the portfolio effect. As we’ll discuss in our next posting, we don’t believe this will be acceptable to companies, advantage of the portfolio effect. As we’ll discuss in our next posting, we don’t believe this will be acceptable to companies, regulators, or the broader societal interests in SCS projects.

An Introduction

Have you ever wondered whether the techniques we use for assessing hydrocarbons can be applied to subsurface carbon storage (SCS)?  The methods we use to quantify the range of hydrocarbon volumes and chance of success (risk) have been established and refined over more than five decades. It is indeed possible to extend these to CO2 storage, but not without some modifications.

The objective of SCS projects is the permanent storage of CO2. This requires a framework to assess both uncertainties and risks over hundreds to thousands of years. The assessments must cover site identification and appraisal of the storage complex, injection of CO2, pressure monitoring, and post-injection monitoring to ensure long-term retainment. This very long-term risk assessment requires additional skills and methodologies that are not generally required for oil and gas projects.

Moreover, we’d argue that a paradigm shift is required so we focus on the chance of geological failure, rather than the chance of geologic success. A failed petroleum exploration well can simply be plugged and abandoned. Not so with a CO2 injector if it was shut-in due to the CO2 ending up in the wrong place. This could impact adjacent subsurface operations, contaminate shallow aquifers, and pose significant legal liabilities. Such unplanned events can taint the entire emerging SCS industry.  We’ll discuss this in our next post.

by Gary Citron, PhD.

While writing his historical novel ‘Roots’, Alex Haley travelled back to his ancestral homeland to learn about a certain aspect of his history. However, to get to that aspect, he was required by the tribal chief to listen to their entire history. While writing this blog contributing to our series on assurance, I have a better understanding of why that is.

It helped me recall the associated circumstances of my first experience as a consultant to relay a key message: When starting an assurance review, please remember to let the team get their story out, the first time, without interruption. In other words, listen first. Reflecting upon memories, I would like to share my experience learning that message.

The Call to Action

In 1999, I was deployed to Tokyo by Pete Rose to consult with the Japanese NOC (now JOGMEC). That week in my hotel room I received a call from James Painter at Ocean Energy (OE) to help them implement a risk analysis system. This entailed (1) training their staff on assessment concepts, (2) demonstrating a prospect review process via our ‘surgical theatre’ template of reality checking a prospect characterization and (3) helping implement the central coordination process to compare the prospective apples of one group to the oranges of another via an assurance team.   

For a company like OE this was particularly important because of their diverse portfolio, built organically in the USA (from their Flores and Rucks heritage) and from their international opportunities that came in part from their purchase of Meridian Oil.

Their impressive assurance team staff included a stratigrapher with vast international experience from Shell, two very talented reservoir engineers and a relatively senior exploration manager who had the ear of their CEO James Hackett. Mr. Hackett went on to distinguish himself further at Devon Energy, which purchased OE in 2003, and particularly later when he joined Anadarko as their CEO. With their highly trained technical staff, savvy assurance team and executive support, they should be well positioned to succeed. Prediction accuracy success (or failure) would largely depend on assurance execution, and I was hired to assist on assurance design and implementation matters.

Seek First to Understand…

Part of my remit was to attend several of their initial assurance reviews and advise the assurance team on best practice. I found an alarming pattern from those reviews. The technical staff were upset that these talented assurance guys were dissecting their prospects before even hearing about the play context. The feedback I heard from the technical teams was that with the current behaviors by the assurance team the technical teams would be hard pressed to solicit further engagement, much less participate in future reviews.

To paraphrase, ‘what was the point of having them if we could not explain the nature of the opportunity’. That feedback was easy to compile, but hard to share with the assurance team. I suspect they hadn’t heard much criticism before in their careers, where they advanced to key technical and managerial roles rather rapidly.

Fortunately, the feedback was readily accepted (after some disbelief stated along the lines of “really?”), and the team made sure they structured their sessions with the discipline to wait until the key points were established, which then provided a foundation for questions and a critical review of the uncertainty and chance factors associated with key parameters.

The take-away we apply for other clients: assurance teams should issue engagement guidelines to the teams that generate opportunities. Such guidelines describe what (and the sequencing for what) they need to see for a review, and in return, what the assurance team provides.

Results

Overcoming the initial hiccup, OE established a state of prediction accuracy over the next three years that was enviable.

The percentile histogram (Enciso et al, 2003) represents virtually no estimation bias, perfection being a straight line across at 20%. As defined by Otis and Schneiderman (1997) in their landmark paper illustrating how an assurance team can make an impact, percentile histograms show the percent of discoveries that fall in prescribed buckets by measuring where the result for each discovery posts on each prospect file’s success case EUR distribution. 

This type of graph facilitates benchmarking against other companies to illustrate thematic estimation problems across the industry. We’ve noted in our prospect risk analysis course that many companies have percentile histograms where more than 40% of their discoveries fall below the forecast P80 of the EUR distribution. The next blog will delve into percentile histogram construction and diagnosis in more detail, so stay tuned.

While there are many attributes to successful assurance efforts (which we will further explore in this blog series), active but patient listening in an assurance review is a good start. 

references

Enciso, G., Painter, J. and Koerner, K.R., 2003, Total Approach to Risk Analysis and Post-audit Results by an Independent, Poster presentation to the AAPG International Convention,  Barcelona, Spain.

Otis, R., and N. Schneidermann, 1997, A Process for Evaluating Prospects, AAPG Bulletin, v. 81, n. 7, pp. 1087-1109.

About the Author

Gary served on Amoco’s assurance team from 1994 to 1999. In 2001 he became Pete Rose’s first partner in Rose & Associates. He helped create the Risk Coordinators Workshop series in 2008, which remains active.

by Peter Carragher

I have been engaged with teams in reviewing and assuring plays and prospects since the late 1990s. I think it’s important to keep the title of this brief note front and center as a constant reminder that there is always something to learn. Continuing to learn will improve your ability to be effective in prospect evaluation and remain a valued contributor. Here are four areas to consider.

Learning from Failures

A prerequisite for learning from failures is the absolute necessity for rigorous written documentation of the pre-drill assessment. That must include all the pre-drill geological and geophysical assumptions, as well as the actual parameters and chance assessment logic you and the team used to build the assessment. Particularly instructive is writing down the possible failure modes for the prospect so you can determine if the actual failure was a surprise or not. The assignment of chance to the individual elements should reflect these concerns. Over time, you can determine the dominant failure modes in your program and take steps to address those issues with technology, or with different decisions.

Learning From Successes

Over estimation of discovered resources is a common problem, sometimes offset in a portfolio by underestimation of the chance of success, a classic case of two wrongs sort of making a right. What is happening here is that the relative ranking of prospects is incorrect, and that has consequences in the management decisions about the portfolio. For example, a company decided to drill a prospect at 100% and reject a valid farm-in / interest swap offer because the prospect resource and value was estimated to be very large. Unfortunately, one of the major risks was not recognized pre-drill. Not only was the well a dry hole, but the counterparty well was a commercial discovery.

Learning From Teams

One of the benefits of positive interaction in an assurance review is that the experience of the assurance team can help the project team in their technical work, prospect description and communications. Less well appreciated, is the necessity that the assurance team learns from the project team. Project teams bring diversity of thinking, new technology, different visualizations, new interpretation models, and the details of local geoscience data to bear on prospects. Careful, respectful listening and seeking to understand that point of view is a prerequisite for long term success in assurance.

Learning From Other Disciplines

Technological advances in the geosciences contribute towards increased specialization. Special effort is required to really learn what is going on in these specialized sub-disciplines, and how they interact with each other. For example, a 3D oil and gas migration model is critically dependent not only on the geochemistry of the source rock, but also the crustal mode that drives the temperature profile, biostratigraphy determining the ages of the burial sequence, geophysics generating depth maps and sequence stratigraphy predicting the distribution of permeability that controls migration vectors.

There is also much to learn from the wider set of disciplines involved in subsurface projects. You will become a better geoscientist if you take the time and put in the effort to learn from your colleagues in reservoir engineering, reservoir modeling and simulation, drilling, and production engineering, to list some of the opportunities. Assurance teams are best served by individuals who have taken this step, integrating learning across disciplines.

Summary

Whether you are involved as an assurance team member, or as a project team member, assurance presents a series of great opportunities to learn something new. Take them!

About the Author

Pete Carragher has been the Managing Partner of Rose & Associates LLP since July 2014. Prior to joining R&A in 2010, his last role at BP was VP of Geoscience and Exploration, working as a member of BP’s global exploration leadership. Pete and his team introduced systematic risk and volume assessment, and assurance, into Amoco in 1990. Since then, he has evaluated hundreds of prospects from most of the world’s productive and frontier basins.

by Juliet Irvin, Guest Contributor

As an experienced assurance professional, I have seen many different approaches to assurance over the years, some more successful than others. The first part of this article explores when and how assurance can be most effective, the role of the outsider, the importance of putting things into context and testing assumptions.

Early Engagement

Early engagement between the assurance team and the technical team is absolutely key. For example, if the assurance team sees the prospect for the first time in the technical reviews (when usually a large proportion of the work has already been completed), it may be too late to steer the analysis and correct any errors, thus exposing a business decision to an incomplete or flawed evaluation.

Imagine an alternative approach, where a member of the assurance team is involved from the beginning of the prospect characterisation and can assist the technical team throughout. Together they can frame the business questions which must be addressed and design an evaluation that is fit for purpose and adds value. For example, there is little value to be had from a very detailed prospect assessment, separating out every fault and reservoir segment, when the business decision at hand is whether to bid a 2D seismic survey to secure a block in a frontier area. This would be a significant waste of time and resources that could have been easily avoided.

The Role of the Outsider

There have been many discussions about project teams conducting their own assurance process while evaluating prospects, vs. the need for external assurance. Which method works best? Having been involved with several hundred prospect assessments, I’m convinced that assurance works most effectively when an impartial and independent person is involved, and that person can contribute by:

  • Being independent and ideally objective
  • supporting the technical team
  • avoiding linkage to rewards and motivations with the decision given their independence
  • providing fit-for-purpose assurance, tailored to the project requirements, organisation size, and skills mix of the prospecting teams
  • having strong facilitation skills
  • testing risk & uncertainty inputs for bias and suggesting mitigations as needed
  • testing assumptions inherent in evaluation
  • benchmarking prospect metrics against others in the portfolio
  • bringing relevant analogues for consideration of reality checks
  • facilitation of the above to converge upon agreed prospect parameters

Putting the Assessment in Context / More than the Numbers

Any prospect assessment is only as good as the inputs (“garbage in, garbage out”), so another key aspect of assurance is understanding what is behind the numbers.  For example:

  • What geological model is being risked?
  • What assumptions form the basis of the parameter ranges?
  • Which parameters have the greatest impact on the volumetrics?

We will now take a closer look at each of these components to explore how impartial assurance, and hence an outsider view, can be an integrated and valuable part of project evaluation.

What is the Geologic Concept for the Prospect?

This may sound like an obvious question, but when this is not clearly understood, it can cause significant problems. To avoid different assumptions, it is important to describe explicitly the geologic model of the prospect being assessed. For example, are we assessing the chance of sand or the chance of a specific environment of deposition? These are not necessarily the same thing. Are there additional geologic models / scenarios, which could yield a success case? Do they need to be characterised at this stage, to maximise understanding of the value of the prospect? Drawing out this clear description up front ensures a common understanding for the technical, management, and assurance teams, and helps to mitigate erroneous assumptions.

When considering analogues, it is vital to consider how likely those scenarios are to occur. For example, if they are highly optimistic cases, management need to be aware of that for subsequent valuation and decision purposes.

Testing Assumptions – What is the Basis of Parameter Ranges?

When conducting a prospect assessment, the technical team will provide a range of values for each of the input parameters, e.g. porosity, net-to-gross (NTG), saturation, etc. Understanding the basis of these ranges is an important part of the assurance process. 

For example: when characterising the NTG, we are usually looking to describe the full range it can average across the prospect, given success. Often the ranges in the assessment do not honour this concept – for example, we may get a maximum NTG value from a single well, or a minimum NTG value seen in a core sample, without considering if those values could represent the minimum to maximum average for the prospect as a whole.

In my experience, a useful way of testing for plausible ranges is to ask geoscientists to draw minimum and maximum NTG maps depicting the environment of deposition (Figure 1). This requires the interpreter to explicitly describe the geologic scenarios which would give rise to those extremes and consider if they are appropriate, and then modify their assessments if needed.

Figure 1. Reservoir geologic scenarios for a prospect (dashed outline) in the SE quadrant of the map

Which parameters have the greatest impact on the output volumes?

“Assess early and assess often” was a mantra often heard from one of my mentors, and it ties in directly with another one: “what business question are we trying to answer?”

Most technical evaluations have both a divergent ideas stage and a convergent stage. Initially the teams are using their creativity, seeking all available information and coming up with ideas of which areas and reservoirs may be prospective. When concepts start to converge, this is a useful stage to engage with the assurance team, to conduct an early prospect assessment, and explore which aspects of the evaluation have the biggest impact on the results.  Figure 2, for example, shows that GRV has the greatest impact on the estimated resources with Recovery Factors influence being minimal.

  • Porosity, net-to-gross
  • GRV
  • Hydrocarbon column height
  • Fluid properties
  • Recovery Factors

Figure 2. Resource parameters and their influence on the resource assessment.

This can ensure the remaining work effort is focused on the most impactful inputs (in this case, GRV), thus avoiding spending time and resources on work that will make little difference to the business decision.

Conclusions

It is very easy to plug numbers into a volumetric software package and calculate a range of outcomes. But are the outcomes meaningful? Do they address the relevant business questions? This is where assurance can help, contributing with early and active engagement, an outside facilitator, an open listening mindset, and some techniques to practically engage with the technical team.

In my view, a key sign of success is when there are no major surprises at the final project reviews, because all relevant aspects of the assessment have already been tested, documented, and addressed along the way with an analysis that has directly addressed the business questions in order to support timely and appropriate decision making.

Management decisions are more informed when the assurance team participates as an advisor, participating in discussions to understand any concerns and provide an independent view of the technical inputs into the analysis and the associated justifications, identify any biases that may have been in play, and communicate the critical risks and uncertainties with the prospect. This can help ensure the conversation is focused on the geologic concepts underlying the analysis, rather than just the numbers coming out. If management concerns are still valid, the assurance team can work with the technical team to address and revise the evaluation if appropriate.

At the end of the day, all technical assessments should help the decision makers make better business decisions by having the right information and analysis available.

About the Author

Juliet is an advanced Risk and Uncertainty Specialist and Geoscientist. She has 22 years’ experience with ExxonMobil (1998-2021) spanning Oil & Gas Exploration, Development, Production, Research and IT, and has been an Assessment and Assurance advisor / specialist for over 10 years. She also has more than 14 years’ experience running professional training classes including Risk & Uncertainty and Prospect and Play Assessment. 

by Bruce Appelbaum (Mosaic Resources), Guest Contributor

My association with Texaco’s exploration program began in 1990 with the offshore Gulf of Mexico group in New Orleans. At the time, Texaco’s yearly exploration budget was a portion of the producing divisions’ stipend, with only informal communication among the exploration groups except at yearly budget meetings. Those meetings consisted of prospect presentations with little commonality and process largely independently determined by the division originating the prospects. The prospects were presented with the originator’s bias and inconsistent risking methodology. Gamesmanship was rampant as success was determined by the amount of budget committed from a pot controlled by the global exploration managers’ group. The process was akin to getting dinner at the boarding house table. Coal bed methane projects competed with rank offshore wildcats for limited capital. Given the bias and gamesmanship, global exploration success was predictably poor.

new orleans takes a new approach

In New Orleans, portfolio analysis was taken seriously, and risk analysis training was brought in as a standard tool in the planning process.  Pete Rose was invited in as the entire division was put through his flagship course on prospect evaluation. Concurrently, a process was emplaced which led to the formation of a small group of risk specialists that produced an independent view of prospect size and chance before the prospect was added to the portfolio. The group also reviewed and evaluated individual prospects being developed for OCS sales in the Gulf of Mexico. Metrics were developed to indicate what was needed to both replace our produced reserves and grow reserves at a significant rate. The increasing success of the division was noticed at our New York corporate HQ, and the credibility of the New Orleans offshore group grew in great measure.

One of the problems holding the offshore group back was a history of expensive dry holes in deeper Gulf waters and a fear at HQ of further deep-water drilling. This was during the period of initial success by Texaco’s major competitors. The company had to get in the deep-water game if it was to have a chance at elevating to top quartile performance among its peers. At the time, the perception was that HQ believed the division was throwing darts at a map of the Gulf to pick its drill sites!

To change this perception, we demonstrated our exploration process and risking technique to management in New York. A plot of our top six deep-water prospects was constructed. Given the individual risks of the prospects shown, we had a 60% probability of achieving at least one discovery with the portfolio presented. The group was duly impressed, we won the day, and the deep-water Gulf frontier was added to our purview. The revamped focus led to Petronius, Tahiti, Blind Faith and the Perdidio area discoveries, to name a few.

my challenge as head of global exploration

In 1996 a newly created global exploration job in Houston was assigned to me, with an ambition to elevate the company’s exploration success both domestically and internationally. As part of my preparation, I evaluated the more successful programs of our peers and interviewed several of our competitors. Amoco was an extremely successful exploration force at the time, with notable success in West Africa, the North Sea and other areas. I visited my Amoco counterpart David Work, and we chatted through Amoco’s process. It started with a global risk team that reviewed both pre-drill and post-drill the world-wide portfolio of projects.

I determined that a global exploration group separate from the producing divisions was necessary at Texaco. This would allow a focus to fund the most prospective projects within a single inventory of competitive, properly risked opportunities. Part of that effort was a fully dedicated Global Risk and Standards Team (GRST) charged with properly evaluating the risk attributes of all projects in the global exploration portfolio. Jim Mackay, Paul Haryott, Michael Joseph, Dave Taber and Jim Varnon were all part of iterations of the risk team. Ultimately, Paul led the team at Texaco and continued as the first manager of Chevron-Texaco’s assurance effort, called the Exploration Review Team. 

Concurrent with the new portfolio methodology, Texaco evolved a focused approach concentrated on several basins which played to our strengths, and abandoned those plays that sapped our financial and technical resources. We allocated about three quarters of our resources to the Gulf of Mexico, offshore West Africa, and offshore Brazil, which had just opened to international investment. The remaining quarter was targeted at the Australian Northwest Shelf, the North Sea, Trinidad, and several emerging high potential arenas. We retreated from efforts in Italy, Poland, Thailand, Viet Nam and several other venues which could not meet our metrics. Though highly prospective, we chose not to enter Venezuelan exploration because of the restrictive licensing terms.

The period from 1997 to the Chevron merger in 2001 bore out our reconstituted exploration efforts and Texaco indeed achieved top quartile exploration metrics. Texaco added approximately four billion BOE net through exploration in this period, including giant discoveries at Agbami in deep water Nigeria as well as Janz on the Australian Northwest Shelf. Janz is part of the Gorgon LNG project and remains the largest gas discovery ever made in Australia. Many of the discoveries were in initial phases of development when the merger talks with Chevron heated up. I believe these resources were a very large driver for the ultimate combination of Texaco with Chevron.

Post-merger, I understand that Texaco’s exploration process was largely adopted by the combined company. While the terminology may have been different, there is no question that the assurance process, driven by consistent, dispassionate risk assessment by a great crew of geoscientists and engineers was a key component of a great company’s last independent successes. All who worked at Texaco during this period can be justifiably proud of what their efforts produced and its foundation for Chevron-Texaco’s continued success.

about the author

Dr. Bruce Appelbaum has enjoyed a long and successful career in the oil and gas industry, culminating in his being named a Vice President and corporate officer of Texaco Inc. He has served on the Board of Directors of the CQS Rig Finance Fund and Input/Output. Additionally, he is a Distinguished Trustee of the American Geosciences Institute Foundation. He is a Member of the AAPG Corporation and an AAPG Foundation Trustee Associate. His advisory positions include the School of Geosciences at Texas A&M, the Dean’s Advisory Council at the State University of New York at Buffalo, and formerly, the School of Earth Sciences at Stanford University. He is currently a member of the Baker Institute Roundtable at Rice University.

by James Handschy, Guest Contributor

All companies want predictable results. The exact definition of predictability may differ slightly, but accurately predicting E&P results is universally considered a positive business attribute. Risk and probabilistic volume analysis tools have greatly improved our ability to consistently evaluate and compare exploration opportunities. That said, no matter how robust the tools, they often suffer limitations from:

  1. Incomplete and/or highly uncertain input data,
  2. Limited experience with the specific geology of a new opportunity,
  3. A short timeframe to do the analyses,
  4. The need to make assumptions about some geologic and engineering parameters.

One of the best ways to minimize the negative impacts of these limitations is through an assurance process that leverages broader knowledge and experience than any individual explorationist or subsurface team has. Assurance processes generally fall into three categories: A) tool based, B) corporate team based, and C) local team based.

corporate culture and assurance process

My work in three different corporate cultures and with more than 40 partner companies taught me that assurance programs can succeed or fail in any company. What works well in one company may not work well in another company. Even within the same company, assurance processes need to evolve when the corporate culture changes. Success depends on how well the assurance process is embraced by all levels in the company which, in turn, is a function of how well it fits into the culture. Most corporate culture assessments published in the Harvard Business Review can be distilled into a simple 4-quadrant diagram like the one shown in Figure 1.

Some E&P companies clearly map into the Process Oriented quadrant. However, many E&P companies map toward the middle of the diagram. They are dominated by one culture but have traits of one or more adjacent cultures. Almost all companies believe that their culture differentiates them from their competitors and gives them a competitive advantage.

Choosing or designing an effective assurance program means understanding what will work best in your corporate culture. People and Creativity oriented cultures thrive with bottom-up, employee driven processes while Process and Market oriented cultures work fine with top-down, management driven processes. It is also important to understand how specific attributes of your corporate culture (e.g., performance metrics, business unit empowerment, etc.) might present impediments to one type of assurance process relative to another.

Because the same set of eyes does all the assurance work, corporate or head office level assurance teams (often referred to as centralized assurance teams) are the easiest to implement and often the most comfortable for senior executives to work with. They are generally successful in Process and Market oriented cultures with the main difference being that the assurance team needs to be more agile and quick to evaluate new opportunities in a Market Oriented culture. Head office assurance teams can also work well in People and Creativity oriented cultures. However, in those cultures, the assurance team needs to take on more of a mentoring and training role instead of a policing role. Asking “why not” is just as important as asking “why.” In People and Creativity cultures the head office assurance team needs to be humbler and more collaborative. They should view themselves as peers with broader experience instead or experts or authorities.

Local or business unit specific assurance teams are often easier to implement in People and Creativity oriented cultures. They empower those local organizations and their people. However, they often don’t benefit from the breadth of experience a head office team brings and it is much harder to ensure truly consistent evaluations between different local teams. In People and Creativity cultures it is often a best practice to have a local assurance team working in conjunction with a corporate assurance team. Recent improvements in remote collaboration tools make this much easier today than it was a few years ago.

Smaller companies are more likely to fall into the People and Creativity oriented quadrants. In these smaller companies, or even mid-sized companies with only one E&P office location, the corporate and local teams essentially become one and the same. In these situations, it may be important to ask the question “is our team’s experience as diverse as it needs to be?” If the answer is “no” or “we’re not sure,” it might be worthwhile resourcing some broader experience from consultants or partners to fill the niche that a corporate team would provide in a large company.

Tools and assurance

Regardless of the human side of the assurance process you choose, tools should play a very important role. At a minimum the tools should provide a diverse set of questions that need to be answered in every evaluation and generate consistent documentation across all projects. More elaborate tools linked to global databases and leveraging big data analysis techniques can be very powerful for risk, volumetrics, and value assessments. While these more complicated tools often require more human assurance oversight, they do not necessarily mean that the overall assurance process needs to be more time consuming. If the assurance teams know how to use the complex tools well, the tools can help streamline the assurance process.

assurance in partnerships with different corporate cultures

In partnerships it is highly likely the partner companies will have different corporate cultures and different assurance processes. I have participated in many multi-company assurance reviews, some required by one of the partner companies and some required by the host government. Based on my experiences, the best practice in these situations is for each company to follow their own internal evaluation and assurance processes, develop clear documentation about the project and its uncertainties, and go into the joint assurance meetings with the objective of using the different partner perspectives to develop a better overall understanding of the project, its risks, and its uncertainties.

assurance team members skills

Finally, a few comments about the assurance team members. Obviously, the personality traits of the assurance team members need to fit with the goals and the corporate culture the team is designed for. For example, you might want to choose more decisive personalities for a corporate assurance team in a Process Oriented culture and gentler, collaborative, and mentoring personalities for a corporate assurance team in People or Creativity oriented cultures. It is also important to make sure that the team members’ individual performance metrics reflect their service time on the team and reinforce the behaviors you want them to exemplify while on the team.

Best wishes for future success!

about the author

James W. (Jim) Handschy started his career in the reservoir engineering department at the original El Paso Natural Gas Company. After getting a PhD in geology and geophysics from Rice University he worked for Shell Oil Company in both E&P and Research, where he started his work in risk analysis, volumetric analysis, and assurance. In 1998 Jim joined Phillips Petroleum, later ConocoPhillips, where he served as global chief geologist for 12 years with oversight of subsurface assurance processes around the world. Jim also spent five years as an E&P general manager where he was a customer of the ConocoPhillips assurance teams and processes.

By Henry S. Pettingill

Prior blogs of this series provided the context for assurance. This article delves into one of the most challenging aspects of assurance: balancing technological aspects of an evaluation with the human ones. This balance may sound simple, but I have found it to be a complex issue, fraught with emotions and organizational challenges.

People-process-technology framework

Shown below is the well-known ‘People-Process-Technology’ framework, first published by Leavitt (1964). In this framework, the presence of all three components is critical, as is balance between them – sometimes referred to as the ‘sweet spot’ or ‘golden triangle’. I have found this balance to be a critical success factor for any assurance or peer-review process. Let’s look at each component as they relate to prospect peer review and assurance.

technology

Prospects are based on technical data and the interpretations of those data. In this regard, I consider technology to include not only the acquisition and application of state-of-the-art technology, but also applying ‘technical know-how’ as well as considering the availability and assessment of technical data (these latter two are also dependent on people).

people

Prospects are all about data and how we interpret that data, and the proper use of statistics to unambiguously characterize the data. However, all this is not done by computers, it’s done by human beings, who apply their expertise to interpretations, judgements, and decisions all along the way—so in the end, prospects are inventions of people.

You can’t have a prospect without physical data to describe it and allow understanding of risks and uncertainties, nor can you have a prospect without a person to aggressively seek all necessary relevant data, make observations, and interpretations. And only humans can properly integrate all the pieces of technology and quantification, all the while making judgements under conditions of uncertainty. Furthermore, a prospect is only as good as the prospector’s technical abilities, intuition, and objectivity, so this component relies heavily on the experience and training of your staff. Finally, prospects do not have feelings, but people do, and recognizing and respecting that all prospects are ‘someone’s baby’ is a make-or-break aspect of assurance.

process

Underlying any E&P decision is the process that results in that decision. Subsurface excellence depends on having a consistent and well-understood process. It has been well-demonstrated that exploration success starts with selecting the best prospects from an inventory (Pettingill, 2005). That in turn requires discipline and consistency within the selection process. Equally important is the learning process and associated predictive performance tracking, which provide the foundation of positive change. Finally, a process is only sound when it is communicated effectively and transparently to those who must follow it (back to people!). In this regard, simplicity is a great friend.

framework balance

Now let’s look at what happens when our diagram lacks balance.

people and technology dominate over process

This results in inconsistency which by itself usually leads to poor project selection, continued pursuit of inferior prospects (which burns resources!) and finally inhibits organizational learning. Another aspect that can be lost is diversity of opinions, which reduces bias and often launches healthy debates that identify issues that would otherwise be missed. Often this results in dry holes.

people and process dominate over technology

When the underlying technology, understanding of it, or application of it is not sound, the final evaluation product (upon which decisions are made) will be inferior and unsound. More dry holes!

process and technology dominate over people

This leads to a host of issues, both short-term and long-term. In the immediate term, peer review meetings can become mechanical, which in turn have several effects: 1) the intuition of the subsurface professionals is not captured, 2) the meeting can have a backdrop of fear, hostility, reluctance to share thoughts, or even 3) tactics that ultimately undermine the process. Longer term effects can set in, such as lack of confidence in the assurance process (or even resentment of it) and staff morale issues – even to the point of causing staff attrition and with it, loss of subsurface ‘know-how’ and excellence. More dry holes!

examples

Have you ever witnessed examples of these three ‘imbalance’ scenarios? I certainly have, and in every case, they resulted in an unfortunate decision that I wish I had not been a part of. In more than one case, a dry hole resulted that I realized should not have been drilled.

In summary, if our assurance process is to succeed, we must hit the sweet spot of People, Process and Technology. If we fail to concentrate on all three, it will be very difficult for us to achieve sustained excellence.

next time

The next article in the series, contributed by James Handschy who was responsible for the subsurface Assurance process at ConocoPhillips, will address how corporate culture can influence the assurance process.

references

Leavitt, H. J., 1964, Applied Organization Change in Industry: structural, technical and human approaches. In W. Cooper, H. J. Leavitt & M. W. I. Shelly (Eds.), New Perspectives in Organization Research, pp. 55-71, New York: John Wiley.

Pettingill, H.S., 2005, Delivering on exploration through Integrated portfolio management:  The whole is not just the sum of the holes, SPE AAPG Forum, Delivering E&P Performance in the Face of Risk and Uncertainty: Best Practices and Barriers to Progress. Galveston, Texas, Feb. 20-24, 2005.

about the author

Henry was the head of technical assurance for Repsol from 1996 until 2000, and for Noble Energy from 2002 until 2013. He was an Explorationist with Shell, Repsol and Noble for 35 years before joining Rose & Associates in 2018, where his primary role is chairman the company’s DHI Consortium.