Tag Archives: Data and Information Provision

Part 2: Are we progressing? Oil & Gas Data Management Journey

3 Replies

In my previous blog, I looked back to the 1960s, 70s, and 80s, and how E&P technical data was generated and stored. For those three decades, data management was predominantly and virtually exclusively on paper. As I looked to the 90s, I found them packed with events that affected all areas of data value chain, from generation to consumption to archival.

Early 90s: Driving Productivity Forward

The early 90s continued one dominant theme from the late 1980s: the relentless drive for increased productivity throughout the business. This productivity focus coincided with three technological advancements that made their way into the industry. First of all, dropping costs of hardware with their growing capacity meant that computers became part of each office with meaningful scientific programs on them. Second, the increased capabilities of “networks” and “server/client” opened up new possibilities by centralizing and sharing one source of data. Third, proven success of relational databases and the SQL offered sophisticated ways to access and manipulate more data.

All this meant that, by the early 90s, engineers and the majority of geoscientists were able to do an increasing portion of their work on their own computers. At that time, the world of computer was divided into two; UNIX for G&G professionals and PC for the rest. Despite the divide of technologies, increases in productivity were tangible. Technology had proven itself useful and helpful to the cause, and was here to stay.

Petroleum Geoscience- and Engineering- specific software applications started springing up in the market like Texas wild flowers in March. Although some companies built seismic and log interpretation software back in the 70s using Cray super computers and on DEC mini computers, not many could afford an $800,000 computer (yes, one computer that is) with limited capacity. “I remember selling software on time share for CGG back in the 80s” my friend commented, “companies had to connect to expensive super computers on extremely slow connections” he adds.  So when the computer became affordable and with the right power for E&P technical applications, the software market flourished.

The industry was thirsty for software and absorbed all of what was produced on the market and then some; operators who could afford it created their own. The big service companies decided they were not going to miss out. Schlumberger acquired Geoquest in 1992 for its seismic data processing services and tools, then also acquired Finder, Eclipse and a long string of other applications.

The only problem with all these different software applications was that they existed standalone; each application had its own database and did not communicate with another. As a result, working on each hydrocarbon asset meant multiple data entry points or multiple reformatting and re-loading. This informational and collaborative disconnect between the different E&P applications was chipping away the very productivity and efficiency the industry was desperate to harness.

Nevertheless, the standardization of defining, capturing, storing and exchanging E&P data was starting to be of interest to many organizations. PPDM in Canada and later POSC in the USA (now Energetics) were formed in 1988 and 1990 respectively. PPDM’s mission at the time was focused on creating an upstream data model that could be utilized by different applications. POSC’s mission was broader; to develop a standardized E&P data model and data exchange standards.

Schlumberger had a solution for its own suite of applications; it offered both Geoframe and Finder as answers to the data mess with Finder being the master database that fed Geoframe with information, and Geoframe integrated the various software applications together.

Mid-90s: Making Connections

In the mid-90s, Halliburton acquired Landmark Graphics and unveiled the OpenWorks platform for its suites of applications in April 1997 at the AAPG. Their market positioning? Integrated reservoir management and a data management solutions. OpenWorks offered similar data integration to GeoFrame but with its own set of scientific software. Geoframe and OpenWorks would butt heads for years to come, both promoting their vision of data management and integrated workflows. It seemed that the larger companies were either a Schlumberger or Landmark shop.

In 1997, the Open Spirit Alliance funded by a consortium (Schlumberger, Shell and Chevron) was born and interoperability was its mission. PrismTech was to develop and market an application integration framework that any company could utilize, it was to be open. Open Spirit platform was officially launched at the SEG in 1998.

Late 90s: Big Industry Changes

Come the late 90s, another drop in oil prices combined with other macroeconomics appeared to trigger a surge in “mega” M&A activities starting with Exxon acquiring Mobil in 1998, BP acquiring Amoco in 1999, and then Conoco acquiring Philips in 2000, these mega acquisitions continued through early 2000s.

All this M&A in the 90s added complexity to what was already a complex technical dataflow environment.

For the data nerds

  • In the 90s, the industry rapidly evolved from hand-written scout tickets, and hand-drawn maps to electronic data.
  • The “E&P software spring” produced many silo databases. These databases often overlapped in what they stored creating multiple versions of the same data.
  • The IT department’s circle of influence was slowly but surely expanding to include managing E&P data. IT was building data systems, supporting them, uploading data to them and generating reports.
  • Engineers and Geoscientist still kept their own versions of data, but in MANY locations now. While hardcopies were the most trusted form (perceived to be the most reliable), technical data was also stored in disks, network drives, personal drives and in various applications’ databases and flat files. It compounded the data management problems of the years prior to computerization of processes.
  • Relational databases and SQL proved to be valuable to the industry. But it was expensive to support a variety of databases; many operators standardized and requested systems on Oracle (or SQLServer later).
  • Systems not on relational databases either faded away to the background or converted to relational databases that were accepted by operators.
  • Two standard data models emerged PPDM and POSC (now Energetics) and one data integration platform from the OpenSpirit (now part of the Tibco suite).
  • Geos and engineers validated and cleaned their own data (sometimes with the help of Geotechs or technical assistants) prior to their analyses.

 Stay tuned for the Millennium, and please add your own memories (and of course please correct me for what is not accurate ….)

Change Coming Our Way, Prepare Data Systems to Store Lateral’s Details.

Leave a reply

Effectively, during the past decade, oil and gas companies have aimed their spotlight on efficiency. But should this efficiency be at the expense of data collection? Many companies are now realizing that it shouldn’t.

Consider the increasingly important re-fracturing effort.  It turns out, in at least one area, that only 45% of re-fracs were considered successful if the candidates were selected using production data alone.  However, if additional information (such as detailed completion, production, well integrity and reservoir characterization data) were also used a success rate of 80% was observed. See the snip below from the Society of Petroleum Engineer’s paper “SPE 134330” by M.C Vincent 2010).

Capture

Prepare data systems to store details, otherwise left in files.

Measurements while drilling (MWD), mud log – cuttings analysis and granular frac data are some of the data that can be collected without changing drilling or completion operations workflow and the achieved efficiency.  This information when acquired at the field will make its way to petrophysicists and engineers. Most likely it ends up in reports, folders and project databases.  Many companies do not think of this data storage beyond that.

We argue, however, to take advantage of this opportunity archival databases should also be expanded to store this information in a structured manner. This information should also funnel its way to various analytical tools. This practice will allow technical experts to dive straight into analyzing the wells  data instead of diverting a large portion of their time in looking for and piecing data together. Selecting the best re-frac candidates in a field will require the above well data and then some. Many companies are starting to study those opportunities.

Good data practices to consider

To maximize economic success from re-stimulation (or from first stimulation for that matter) consider these steps that are often overlooked:

  1. Prepare archival databases to specifically capture and retain data from lateral portions of wells. This data may include cuttings analysis, Mud log analysis, rock mechanics analysis, rock properties, granular frac data, and well integrity data.
  2. Don’t stop at archiving the data, but expose it to engineers and readily accessible to statistical and Artificial Intelligence tools. One of those tools is Tibco Spotfire.
  3. Integrate, integrate, integrate. Engineers depend on ALL data sources; internal, partners, third party, latest researches and media, to find new correlations and possibilities. Analytic platforms that can bring together a variety of data sources and types should be made available. Consider Big Data Platforms.
  4. Clean, complete and accurate data will integrate well. If you are not there yet, get a company that will clean data for you.

Quality and granular well data is the cornerstone to increasing re-frac success in horizontal wells and in other processes as well.  Collecting data and managing it well, even if you do not need it immediately, is an exercise of discipline but it is also a strategic decision that must be made and committed to from top down. Whether you are drilling to “flip” or you are developing for a long term. Data is your asset.

 

Capture The Retiring Knowledge

Leave a reply

The massive knowledge that is retiring and about to retire in the next five years will bring some companies to a new low in productivity. The U.S. Bureau of Labor Statistics reported that 60% of job openings from 2010 to 2020 across all industries will result from retirees leaving the workforce, and it’s estimated that up to half of the current oil & gas workforce could retire in the next five to ten years.

For companies that do not have their processes defined and weaved into their everyday culture and systems — relying on their engineers and geoscientists knowledge instead — retirement of these professionals will cause a ‘brain drain,’ potentially costing these companies real down time and real money.

One way to minimize the impact of “Brain Drain” is by documenting a company’s unique technical processes and weaving them into training programs and, where possible, into automating technology. Why are process flows important to document? Process flow maps and documents are the geographical maps that give new employees the direction and the transparency they need, not only to ramp up a learning curve faster, but also to repeat the success that experienced resources deliver with their eyes closed.

For example, if a reservoir engineer decides to commission a transient test, equipment must be transported to location, the well is shut down and penetrated, pressure buildup is measured, data is interpreted, and BHP is extrapolated and Kh is calculated.
The above transient test process, if well mapped, would consist of: 1) Decisions 2) Tasks/ Activities 3) A Sequence Flow 4) Responsible and Accountable Parties 5) Clear Input and Output 6) and Possible Reference Materials and Safety Rules. These process components, when well documented and defined, allow a relatively new engineer to easily run the operation from start to end without downtime.

When documenting this knowledge, some of the rules will make its way in contracts and sometimes in technology enablers, such as software and workflow applications. The retiring knowledge can easily be weaved into the rules, reference materials, the sequence flow, and in information systems.

Documenting technical processes is one of the tools to minimize the impact of a retiring workforce. Another equally important way to capture and preserve knowledge is to ensure that data in personal network drives is accumulated, merged with mainstream information, and put in context early enough for the retiring workforce to verify its accuracy before they leave.

Processes and data  for a company make the foundation of a competitive edge, cuts back on rework and errors, and helps for quickly identifying new opportunities.

To learn more about our services on Processes or Data contact us at info@certisinc.com

Bring It On Sooner & Keep It Lifting Longer. Solutions To Consider For ESPs (Or Any Field Equipment)

Leave a reply

Settled on average 6,000 feet below the surface, electrical submersible pumps (a.k.a ESPs) provide artificial lift for liquid hydrocarbons for more than 130,000 wells worldwide.
Installing the correct ESP system for the well, installing it precisely, and careful monitoring of the system is paramount to reducing the risk of a premature end to an ESP life cycle. But the increasingly long laterals of horizontal wells, along with rapid drilling in remote areas, is creating challenges for efficient operations and the ESP’s life span. Implementing the correct processes and data strategies will, undoubtedly, be the cheapest and fastest way to overcome some of the challenges.

1- Implement A Process Flow That Works, Break The Barriers

When a decision is made to install an ESP in a well, a series of actions are triggered: preparing specifications, arranging for power, ordering equipment, scheduling operations, testing, and finally installing it in a well, to state a few. These actions and decisions involve individuals from multiple departments within an organization as well as external vendors and contractors. These series of actions form a process flow that is sometimes inefficient and is drawn out, causing delays in producing revenue. In addition, sometimes processes fall short causing premature pump failures that interrupt production and raise operational costs.
Research of many industry processes shows communication challenges are one of the root causes for delays, according to LMA Consulting Group Inc. Furthermore, communication challenges increase exponentially when actions change hands and departments. A good workflow will cut across departmental barriers to focus on the ultimate goal of making sure Engineering, Procurement, Logistics, accounting, vendors, contractors and field operations all are on the same page and have a simple and direct means to communicate effectively. But more importantly, the workflow will allow for the team to share the same level of urgency and keep stakeholders well informed with the correct information about their projects. If you are still relying on phones, papers and emails to communicate, look for workflow technology that will bring all parties on one page.

A well-thought through workflow coupled with fit-for-purpose technology and data is critical, not only to ensure consistent successful results each time but also to minimize delays in revenue.

2- ESP Rented Or Purchased, It Does Not Matter… QA/QC Should Be Part Of Your Process

Although ESPs are rented and the vendor will switch out non-performing ones, ensuring that the right ESP is being installed for a well should be an important step of the operator’s process and procedures. Skipping this step means operators will incur the cost of shut downs and tempering of reservoir conditions that may otherwise be stabilized – not to mention exposure to risks each time a well is penetrated.
More importantly a thoughtful workflow ensures a safe and optimal life span for ESPs regardless of the engineers or vendors involved, especially in this age of a mass retiring of knowledge.

At today’s oil prices, interrupted production for a well of 1,000 barrels per day will cost an operator at least $250,000 of delayed revenue for a 5 day operation. Predictive and prescriptive analytics in addition to efficient processes can keep the interruption to the minimum if not delay it altogether.

3- Know Why And How It Failed Then Improve Your Processes – You Need The Data And The Knowledge

One last point in this blog: Because ESPs consist of several components, a motor, a pump, a cable, elastomer, etc… ESP failure can, therefore, be electrical, mechanical, thermal or fluid/gas composition. Capturing and understanding the reasons for a failure in a system to allow for effective data analysis provides insight that can be carried forward to future wells and to monitoring systems. Integrating this knowledge into systems such as predictive analysis or even prescriptive analytic to guide new engineers will have an effect on operator’s bottom-line. A few vendors in the market offer these kind of technology, weaving the right technology, data and processes to work in synergy is where the future is.

On how to implement these solutions please contact our team at info@certisinc.com.

Related articles

How an E & P Subsidiary took its Information Communications from Risky to Efficient

Leave a reply

It starts with chatter around the workplace. A company is growing. Procedures that were once “nice to have” are now serious money bleeds. That is exactly what Certis found when they revamped a major E&P subsidiary’s communication procedures.

When an oil and gas company plants itself in any nation to explore for business opportunities, its communications with the nation’s government and with its JV partners can be, understandably, informal for the early stages of the project. As the company moves from Exploration and Appraisal phases towards a full fledge Development and Operation, what once worked with lax communications becomes a risky endeavor.

While these risks can be underplayed next to health and safety hazards, we discovered they warranted immediate action if the company is to survive long term. Consider these two real situations, to name a few:

1)      Sensitive information leaks, for example, at early stages of exploration efforts, any discovery would have a large impact on a company’s stock price (if public) and serious implications on their competitor’s behavior.

2)      Growing companies’ watch millions of dollars become billions of dollars almost overnight. Those large dollar amounts require complete technical data and timely communications to appease the government and the JV partner. The flow of information becomes crucial.

Knowing something is broken isn’t the same as understanding how it is broken and how to fix it.

Most employees can feel the weak spots in their company. When you start to sense problems, the cost of fixing them seems outlandish. But overtime the scales tip. Often, when the scales tip, the problem has grown to overwhelming proportions for employees to handle alone.

The scale had long ago tipped for this client.  Our team’s role was to quickly identify causes of communication problems, and orchestrate a long-term plan and processes to mitigate risks.

Over a period of few weeks, we surveyed the office, field, and rigs in two different continents. We went through a full cycle of process improvement. At the end we were able to divide their information communications needs into four process categories: 1) Documents and Data Management 2) Decisions Documentation 3) Security and Access Management 4) Request Management.

Our plan started with ‘Quick Wins’ that changed the way the subsidiary did business in the first month. Imagine being able to institute relevant changes in your company in one month. Yes, it was that easy to solve. The rest of the implementation plan spanned over 4 months. Communication policies, standards and procedures were to be defined and complied to across the organization.

We all know that the cost of fixing is cheap compared to the cost of cleaning up a huge mess later.

The costs of missed opportunities, reduced stock prices, or the cost of million-dollar lawsuits make this kind of projects important, combine that with the relevant low fixing cost, makes this project a “high” priority.

I believe a company needs to do more than simply comply with government or JV partner contracts. To build strong relationships, you must be able to readily prove your compliance. That’s just good business.

Our client’s new transparent business practices allow the government to view them as a serious and trusted part of the country’s future. It is impossible to put a price on a valued relationship. But successful business people know that gaining trust means big business over time.

What about your company? Is it starting to feel the risks of outdated communication systems?