Professional Documents
Culture Documents
net/publication/305386440
Asset management in the oil and gas, process and manufacturing sectors
CITATIONS READS
4 2,944
1 author:
John Woodhouse
TWPL
20 PUBLICATIONS 176 CITATIONS
SEE PROFILE
All content following this page was uploaded by John Woodhouse on 17 January 2022.
Abstract
The European North Sea oil and gas sector was one of the first to explore and develop a
more integrated approach to asset management - with spectacular results. This chapter
outlines some of the key learning points and the business templates that have emerged. It
also covers some of the component methods that have been widely adopted in process and
manufacturing sectors to improve asset systems performance, reliability and whole life costs.
Keywords:
Asset Reference Plan, Asset Whole Life Plan, Asset Manager, Life Cycle Cost, RCM, RBI,
TPM
1.1 Introduction
Integrated, whole-life optimised asset management, as described in BSI PAS 55, has been
developed in various guises, to various degrees of success and maturity, in several process
and manufacturing industries. Most notable, however, has been the oil and gas exploration
and production sector, where much of the modern thinking on the subject was developed in
the first place (and is reflected in PAS 55 content and structure). Accordingly, this chapter
will focus primarily on the best practices and experiences gained in this industry and now
adopted much more widely.
What is perhaps strange, given the common oil company parentage in several cases, is that
the ‘downstream’ oil industry (refining and chemicals) has been among the slower sectors to
absorb the lessons and achieve the substantial performance gains that are increasingly
proven to be available. Similarly, whereas many manufacturing industries have adopted a
number of component methodologies and good practices (such as Lean, Total Quality
Management/6-sigma and Total Productive Maintenance), they often lack the overarching
model or structure to connect corporate long-term value strategies down to day-to-day
issues, actions and priorities. Toyota, for example, has a well-deserved fame in leading the
innovation of good practices in quality management, value focus and workforce teamworking.
General Electric, Motorola, Du Pont and others have also developed, derived or re-packaged
variants of such tools and approaches.
Sadly, however, the implementation records in other process and manufacturing sites is
littered with temporary enthusiasms, partial ‘solutions’, unfulfilled initiatives and the over-
selling of confusing acronyms and methodologies. This is at least partly due to very tight
commercial margins and volatility of the businesses, causing a short-termism and reactive
habit, sometimes compounded by high management turnover (each manager needing to
make his or her mark in a short window of opportunity). People find themselves too busy
fighting the crocodiles to have time to plan and drain the whole swamp. The good examples
of strategic asset management thinking therefore stand out particularly strongly. Later in this
chapter, I summarise some of these cases – and the methods that have proven particularly
effective when correctly targeted and implemented.
• A mining operation
• An oil and gas separation and processing facility
• A gas treatment unit
• A water treatment plant
• A compression/pumping station
• A power station
• A ship harbour
• A communications centre
• A heliport
• A hotel
• A workshop and store
• A clinic
• An emergency control centre
Such a diversity of component asset and system types, operational processes, people and
skill requirements comprise the dedicated Asset resources, whose cost is fully attributed to
the asset as a business unit. Similarly, it is the net total output of all these systems and
processes working together that represents the Asset’s performance.
Intermittently required resources and functional services that could be shared between two or
more Asset business units, were treated as external and discretionary – the Asset manager
holds the purse-strings and determines if, what and when such resources were worth paying-
for. Corporate functions and departments, therefore, lost their budgets altogether. The UK
Human Resources Director, for example, needed to ‘sell’ the value-adding services that his
team could provide to the various Asset ‘customers’. Like Total Quality Management (TQM)
methodologies, this power shift forced a better focus on real requirements, sensitive to the
individual Assets and their different needs or opportunities. In particular, such ‘overhead’
departments were forced to demonstrate positive value-for-money contributions compared to
obtaining of such services from the open market (Asset Managers were free to choose the
best value option). In a large organisation this represented a major culture shock and a 180º
reversal of the traditional ‘command and control’ style, whereby Human Resources,
Information Technology or Finance departments forced generic policies or methods onto
everyone, irrespective of local suitability or needs.
Subsequent maturity of understanding has since adapted this extreme model somewhat; now
some power and budget is still held by corporate/centralised functions to ensure the
spreading of best practices or adoption of processes that rely heavily on inter-asset alignment
(such as performance measures, data standards, recruitment and education requirements).
Such centralised resources or services, however, still have to demonstrate net positive value
compared to alternatives – such as outsourcing - and that the advantages of adopting a
common process outweigh the local opportunity variations of individual Assets.
Nevertheless, the organisational earthquakes resulting from the initial total transfer of
budgets and decision-making to the discrete asset management teams was a key factor in
shaking up old habits, challenging/terminating low-value activities and in focussing on what is
really worthwhile. It helped to break the cycle of just chasing efficiency gains from ‘doing the
same thing quicker/cheaper’ and forced a first-principles consideration of what was worth
doing in the first place.
The content of an ARP evolves over time (see Figure 1) from initial design stage (with lots of
assumptions and uncertainties) to infrastructure construction & commissioning, steady state
operations and ultimate decline (including any life extensions, re-usage and/or
abandonment). Nevertheless, this ‘live’ document acts as a maintained central register of the
knowledge, assumptions and plans for the asset, pooling the contributions of all relevant
parties and functional disciplines. Success in any one area of activity is only measured in
terms of the net impact on the total picture.
These elements map very closely into the requirements that have been incorporated into
PAS 55, and also align with the elements of asset management documentation that have
since emerged in other industry sectors.
Other Parties
Production and Planning Govt Depts Logistics
Hydrocarbon Register Unions Contracts
Production reports Contractors Purchasing
Modelling tools Land Owners Transport
Business reviews Service agreements
Operations
Field activities Maintenance
Treatment Plants Equipment Register
Oil Production Maintenance systems
Gas Production Asset Maintenance Management
Inspection schedules
Reference Performance Monitoring
Plant Availability
Engineering Plan
Infrastructure (ARP)
Projects Legal
Power supply Concessions
New installations Licences
Compliance
Development
Reservoir Models Human Resources
Production forecasts Manpower Requirements HSE
Technology Plans Competency Registers Legislation
Development Skills Registers Standards
Drilling schedules Employment practices Monitoring Reporting
Retention Strategies
Figure 2 Inputs to the ARP come from nearly all areas of the business
Once such a full picture is assembled (including recognition of uncertainties and risk
elements), both the immediate priorities and the long-term plans can be made to ensure best-
value delivery. So, for example:
o Capital investment requirements can be prioritized and justified with greater
credibility and relevance
o Human resource requirements can be met with adequate development
(recruitment and/or training) lead-times
o Physical infrastructure, equipment and facilities can be developed, operated
and maintained in line with the whole life business values.
o Future technology developments can be identified, explored and exploited
more flexibly
o New legal requirements, concession/license changes and other constraints
identified and mitigated more readily
o Information and data requirements specified more appropriately in relation to
identified needs (e.g. performance criteria or key uncertainties/vulnerabilities)
The ARP provides a consolidated view of the asset current status (and future plans) at a
specific moment in time. It cannot hold, of course, all the detail about all the activities – if it
did, it would be come totally unwieldy, unreadable and constantly out-of-date. This means
that a distilled summary of each contribution is needed at the ‘total picture’ level, creating a
good and useful discipline for each contributor, to encourage clear explanation of what is
needed in each area, why and when, with what likely or possible outcomes (and risks). Again,
the collective creation of an ARP acts as a valuable catalyst to improve individual
Team Values,
Principles,
14
Optimistic case
12 Most likely (P50)
10 Worst case
8 Opportunities
6
Risks
4
Finally, based on many cycles of developing such a cohesive, Asset-centric view of strategic
plans, a key requirement of the ARP development process has proven to be the
understanding and agreement of what is included in a credible Base Case. It is imperative
that, in compiling the Base Case, only realistic and approved development assumptions are
included, and ‘most likely’ costs estimated. ARP teams should not include immature
proposals which may have a low probability of success, or resource requirements/budgets
that include contingencies and spare capacity. Such project proposals or budget
contingencies should always be handled as possible variants from the Base Case; either as
improvement opportunities (with their individual cost/benefit/risk appraisals) or as identified
risks (with appropriate probability and severity consideration, and prevention/ mitigation/
contingency justification).
The longest standing formal adoption of the principles of whole life costing (a term used
interchangeably with LCC) has been in the defence sector – with military procurement
ostensibly based on the life cycle cost of ownership rather than just the ‘cheapest purchase
price’ option. Back in the early 1970’s the US Department of Defence MIL STD 1388 for
Logistics Support Analysis (now replaced by HDBK 502) introduced a requirement for
operating costs to be incorporated into acquisition decisions. The UK MOD standard (Def
Stan 00-60) has gone further, specifying that “The supportability of design options shall be
assessed and influenced, and the whole life-cycle cost shall be balanced against performance
in identifying the optimum support solution”. This also recognizes the need to consider
value-for-money differences that incorporate performance attributes, but it fails to go as far as
clarifying that identifying the ‘optimum solution’ is not a ‘balancing’ act, i.e. seeking an equality
of significance. It should be the summation of actual costs and ‘lost opportunity costs’ (due to
performance inadequacies, risks etc) and we are seeking the best value combination or total
business impact (see PAS 55:2008-2) over the asset life.
The adoption in other sectors, LCC has been selectively at best - usually involving some
pragmatic compromises such as pre-determining a constant assumed or required ‘life’ to
compare different options (whereas a common difference between an expensive option and a
cheaper alternative is the longevity achieved). Again, the North Sea oil and Gas sector has
done some interesting work in the field, with a ‘Joint Industry Project’ during the 1990’s that
involved over 20 operators, constructors and major equipment vendors in developing a
checklist and guidance documentation for major project whole life costing (now embodied in
ISO 15663). Application of these principles in, for example, the BP Andrew platform is
claimed to have achieved c.30% savings in total costs of ownership. Nevertheless, despite
the very large number of organisations professing to support and apply the principles of Life
Cycle Costing, relatively few can stand up and demonstrate a systematic implementation in
their procurement processes or capital investment projects.
The rigorous RCM process requires a multi-disciplined team to look at the very large number
of components and their failure modes, so it is very labour-intensive. As a result, many RCM
implementation programmes in manufacturing and process environments during the 1980’s
and 1990’s ran out of steam and failed to deliver the promised benefits. More mature
understanding in the last decade has led to much more selective use of the method, using a
criticality analysis of assets and their functions to determine which systems should be studied
in the first place, and to what level of detail.
There is also plenty of debate on the various flavours of RCM that have emerged, particularly
in the validity of ‘streamlining’ or reversing the process (i.e. starting with existing maintenance
tasks, and challenging their justification by looking for failure modes that might justify them).
Defendants of the ‘traditional’ approach argue that such short-cuts introduce risks of oversight
– allowing potentially significant failure modes to go un-analysed – and indeed some
streamlining methods sacrifice integrity for cost- and time-savings. Criticality-selective
studies, however, are largely accepted as necessary, and my own observations (a sample of
about 75 implementation programmes) is that full RCM rigour is worthwhile for about 30-50%
of the installed asset base if it comprises a mix of mechanical/electrical and rotating/static
systems. Higher dominance of static equipment and/or electrical systems leads to lesser
value from RCM-level review (and Risk-Based Inspection or Condition Based Maintenance
reviews become more appropriate). Lesser rigour methods (e.g. Reverse-RCM) and the use
of templated studies can account for the remainder of lower criticality items with little risk or
performance penalty but at a fraction of the analysis cost.
It should also be noted here that there are also some very unsafe messages sometimes being
taught as ‘facts’ within RCM training programmes – such as the proportions of components
that exhibit particular failure patterns. A study of 23,000 aircraft components in the 1960’s is
sometimes quoted as a universally applicable distribution of the ways in which components
fail, whereas other asset systems and industrial environments will have a very different mix of
failure patterns representing ‘infant mortality’ or maintenance-induced, random and
degradation-related risks. Similarly, a sometimes unnoticed weakness within RCM is the
reliance on subjective judgement to assign appropriate inspection or maintenance intervals to
the emerging tasks; the guidance that does exist is very shallow and can lead to inappropriate
budgeting, resourcing and downtime requirements.
Nevertheless, the core value of RCM discipline is undeniable: it is a concise summary of the
questions that need to be asked in order to determine what type of maintenance is likely to be
appropriate. Appropriately targeted to critical assets and asset risks, it has both reduced
maintenance costs and improved system reliability in many organisations. Where sensibly
applied in the process and manufacturing sector, it is credited with reductions of maintenance
costs in the 20-40% range, while simultaneously yielding system availability improvements of
between 2 and 15% compared to traditional ‘one size fits all’, fixed-interval maintenance
strategies.
All these elements are all in line with modern optimised asset management thinking, and they
encourage attention to detail, a whole life cycle view, cross-functional collaboration and a
more holistic OEE view (although this measure does not adequately incorporate risk and
sustainability attributes). This is why the TPM title is somewhat misleading – it is much more
than just improving awareness and role of the maintenance contribution.
I also group the Lean Manufacturing principles in this area of observed good practices within
the manufacturing sectors (and could extend the list to include Just-In-Time, the Theory of
Constraints, Kanban, Kaizan and a host of contributory techniques). Lean Manufacturing
shares its origins with TPM in the Toyota Production Systems, and contributes a useful
checklist of seven areas in which to seek and eliminate waste. It also reminds us (like Total
Quality Management covered below) of the need for strong and sustained customer focus.
➢ More data is not always good news – in some cases it simply yields more confusion
➢ Knowing how the information will be used is necessary before determining what data
to collect to supply such information
➢ Structured capture and use of existing ‘tacit’ knowledge (of subject matter experts:
often front-line employees) is often perfectly adequate
➢ Root cause analysis training and discipline is essential to avoid leaping to
conclusions, and not just in the major ‘post-mortem’ cases.
➢ Reliability data is good for identifying what? and where? of problems, but extremely
rarely helps with answering the ‘why?’ questions.
1.6 Conclusions
It can be seen, therefore, that the oil and gas, process and manufacturing sectors span the
extremes from fully-developed, integrated and even world-leading asset management
business models, to a patchwork of component technical or methodology ‘fixes’. The cycles
of enthusiasm and decay are certainly evident, with a fair amount of reinventing, or at least
rediscovery, of the wheel. Nevertheless an emerging consensus is slowly becoming apparent
and, providing we can see through the over-selling of contributory elements, it is gratifying to
see that PAS 55:2008 embodies many of these conclusions. There is not enough cross-
pollination between industries sectors yet, as most industries are still strongly tribal and prefer
to compare ‘like with like’ in their benchmarking activities, professional networking and
journals/conferences. Asset management good and ‘best’ practices are, however, highly
transferable across different asset types and industrial environments, albeit with different
stresses and implementation flavours. This chapter has, I hope, shown you just a little of
what others are doing, and given you a feel for the scope to learn from such environments.
John.woodhouse@twpl.com