Cover Page

Petrophysics:
A Practical Guide

 

Steve Cannon

 

 

 

 

 

 

 

logo.gif

Dedication

 

 

For Janet, as ever

Preface

This book has been written for those studying petroleum geology or engineering, for whom the role of the petrophysicist can become a lucrative and satisfying career. The handbook will be equally useful to students and practioners of environmental science and hydrogeology, where the understanding of groundwater flow is an important part of their technical remit. There is a comprehensive reference list included in the handbook that will cover some of the historic developments in petrophysics over the last 70 years; the book could bear the subtitle ‘from Archie to anisotropy’ and still include all the basic ideas captured in its pages. The handbook is subtitled ‘a practical guide’, and that is what I have set out to try and do: look at the pitfalls and obstructions encountered in any reservoir evaluation study and suggest alternative solutions and works-around.

It has also been developed in response to the needs of many younger colleagues who have not yet had the opportunities and experiences of an older generation of petroleum geologists and engineers. Most experienced petrophysicists in the industry have developed their own routines and preferred solutions to specific interpretation problems, and some of these different ideas will be reviewed for specific types of reservoir and the fluids they contain. Specialist petrophysicists and log analysts steeped in the details of wireline tool physics can sometimes lose the essential requirement of an interpretation, which is to provide usable input for some other static or dynamic model of a hydrocarbon reservoir.

I will quote one anecdote that may help explain what I mean. When learning how to use a new piece of log analysis software, I was afforded the opportunity by a colleague working for an oil company to test the software on a complete suite of wireline logs supported by core and sedimentological data, including XRD and SEM analysis. I had every tool then known to mankind available to employ on the usual problem of establishing porosity and water saturation in a well. I ran the log analysis software; the state-of-the-art software that used elemental analysis combined with a stochastic interpretation to generate the required results. My simple first-pass results were adequate, but no better than the previous deterministic solution I had generated. I was able to call upon the assistance of an expert log analyst in the service company with 20 years of experience in this field. I showed him the input data, the logs, the core analysis, XRD, etc., and my initial results; he felt that we could do better. After a couple of initial runs he said, ‘I think I will relax the neutron a little’, and my sandstone reservoir became a limestone; my comment was, ‘it’s a good job we have the core data; at least we know it is supposed to be sandstone!’. This was a life-changing event! I learnt that it is not enough to quality control the input data, you must quality control the output and make sure the results are sensible; often less experienced users of software solutions do not appreciate what the results should look like.

Until the 1980s, there were very few petrophysicists outside the oil company research laboratory: there were log analysts, core analysts, geologists and petroleum engineers, all of whom dabbled in the interpretation of wireline and core data. Log analysts had generally worked as field engineers with one of the many service companies, often being graduates in physics and electronics and thus well grounded in tool physics and data acquisition. It was with the development of computer-processed interpretations that log analysis became a tool of the many: often geologists with the basic knowledge to run the software but not always the experience to recognize bad data, the classic garbage-in, garbage-out syndrome.

There are also many oilfield service companies that provide wireline and/or LWD services from acquisition, through processing to interpretation. The biggest international companies are Baker Hughes, Halliburton, Schlumberger and Weatherford, and all provide services used in the evaluation of reservoirs; there are many other smaller and local companies that provide similar services. Throughout the book I have tried not to be biased towards one company or another; however, this is not always easy as some products or tools become associated with one or other company – my apologies should I appear to favour one organization over another, this is unintentional.

In writing this practical guide, I have started with the basic data acquisition and quality control of log and core data before moving into the actual interpretation workflow. Before starting an interpretation, however, it is crucial to establish a consistent database, and I give some suggestions on how this may be done, albeit this stage is often software dependent. The interpretation workflow follows a widely accepted series of steps from shale volume estimation, through porosity determination and finishes with the evaluation of water saturation. At each step I have presented a number of methods or techniques that may be selected depending on the available input data; these are not the only solutions, only the most common or simplest, so readers are invited to develop their own solutions for their own reservoirs. I have also tried to cover some of the more specialist log interpretation methods and their applications in reservoir characterization, especially how petrophysics links seismic data through a geological model to the dynamic world of reservoir simulation.

There are many people who have helped and guided me through my career, many no longer with us, so to them all I say, ‘thank you’. I especially want to thank Roman Bobolecki, Andy Brickell, John Doveton, Jeff Hook, Mike Lovell, Dick Woodhouse and Paul Worthington, all proper petrophysicists! Finally, my thanks go to Andy Jagger and Nigel Collins of Terrasciences, who have supported me in many ways over the last 25 years, not least in providing a copy of T-Log for my use while writing this book.

Steve Cannon