Why this map matters

A plant can have excellent vibration analysts, disciplined planners and a polished capital process — and still lose value because those groups optimize different objectives. The Landscape is a common frame for seeing asset management as a connected management discipline, not a maintenance department with a larger name.

It is deliberately a landscape, not a recipe. It tells you the territory and gives consistent definitions. It does not prescribe one organization chart, software stack or certification route. That makes it useful across mining, utilities, transport, pharma and manufacturing.

Seven knowledge groups, forty subjects

The third edition clusters 40 subjects into seven knowledge groups. Read them as a chain rather than seven silos.

Knowledge groupQuestion it answers on site
Context & StakeholdersWhat value, obligations and constraints must the asset system serve?
GovernanceWho owns decisions, assurance and accountability?
Strategic PlanningHow do business goals become asset objectives and plans?
Decision-MakingHow are cost, risk, performance and life-cycle options traded off?
Life Cycle DeliveryHow are assets created, operated, maintained, renewed and retired?
InformationWhich data is required, trustworthy and usable for decisions?
Organization & PeopleWhich capabilities, culture and change mechanisms make it work?

Use it as a gap map, not a scorecard

Start with a value stream that hurts — for example chronic conveyor downtime. Trace it across the map: stakeholder requirements, risk criteria, capital decisions, maintenance strategy, work execution, asset information and competence. Mark every hand-off where evidence disappears or accountability becomes vague.

Then pick the smallest cross-functional intervention that repairs the chain. A new dashboard is rarely the answer when the real gap is that projects hand over assets without maintainable bills of material, or procurement rewards purchase price while operations carries life-cycle cost.

Field rule

Never turn all 40 subjects into 40 simultaneous initiatives. Use the Landscape to find the constraint around one business outcome, fix that constraint, then repeat.

What the Landscape will not do

It will not select a maintenance task, calculate an inspection interval or diagnose a bearing. Pair the map with technical methods: ISO 55000 for management-system requirements, RCM for consequence-based strategy, planning and scheduling for execution, and defect elimination for recurring loss.

Its value is architectural: it stops technically good work from becoming isolated shelfware. Four stars because it is one of the clearest panoramas of the profession — but a panorama only creates value when a team uses it to change a real decision.

References & further reading

This page is original explanatory writing. Follow the sources for the complete material and context.

  1. GFMAM. Asset Management Landscape v3.0 landing page and official downloads. Open source
  2. GFMAM. The Asset Management Landscape, Third Edition (English PDF), June 2024. Open source
  3. ISO. ISO 55001 Asset management overview. Open source

Disclaimer. This independent educational summary is written entirely in Rob Reliability's own words. It is not affiliated with or endorsed by the authors or organizations cited. No source figures or substantial source text are reproduced. This page is a field guide, not a substitute for the originals.

Done for you

Turn the map into an executable asset strategy

We connect business priorities to critical assets, failure modes and CMMS-ready actions.

Maintenance Strategy Optimization