Contact us

Twiniti Wiki / Enterprise Asset Management / Asset lifecycle

Asset lifecycle

Physical assets move through creation and acquisition, operation, maintenance, and repurposing or disposal. ISO 55000 and ISO 55001 take a life-cycle view of value, cost, risk and performance; they do not publish a single numbered stage list. The citable stage map used here is group 6 Delivery of the Global Forum on Maintenance and Asset Management (GFMAM) Asset Management Landscape, third edition (English, June 2024, ISBN 978-1-7774676-8-5): eight subjects, 6.1–6.8.123

Enterprise asset management (EAM) software, in industry usage, is the system of record along that path. Capital / asset-investment planning (AIP) and asset-performance intelligence inform the replace-versus-repair decision; they are adjacent, not a computerized maintenance management system (CMMS) module by another name.456

Do not invent an ISO seven-box lifecycle diagram. Do not treat “acquire–operate–maintain–dispose” as an ISO model; it is a teaching reduction of GFMAM Delivery (see §3.3).

3.1 ISO talks about life cycles; it does not number the boxes

ISO 55000:2024 (Asset management — Vocabulary, overview and principles, ed. 2, 2024-07) is described on the ISO.org catalogue as providing overview, terminology and principles for managing assets over their life cycles and realising value. ISO.org FAQ language on that page (catalogue-page text, not clause 3) names a strategic approach throughout the lifecycle as a key element, together with aligning asset-management objectives with organisational objectives and using an asset management system (AMS) to realise value.2

ISO 55001:2024 (Asset management — Asset management system — Requirements, ed. 2, 2024-07) is the requirements document. Catalogue FAQ language (fetched in an earlier pass this date) states that effective asset management helps organisations control the lifecycle of assets, balancing performance, risk and expenditure.3

ISO/TC 251’s public “About” page summarises the 2024 update of ISO 55001 as adding clearer requirements on, among other themes, “life cycle operations.” That is a committee summary, not a clause number. Do not invent citations of the form “ISO 55000 clause 8 life-cycle operations.”7

ISO 55012:2024 (Guidance on people involvement and competence, ed. 1, 2024-07) is, at catalogue level, about personnel involvement around the strategic asset management plan (SAMP) and asset-management plans; TC 251 / catalogue language places that involvement “through different stages of the life cycle of an asset.” It is people guidance, not a stage model.8

Uncertainty. Verbatim ISO 55000:2024 / 55001:2024 clause text was not licensed for this draft. Life-cycle wording below is GFMAM (free PDF) plus catalogue/FAQ/committee summaries.

The Institute of Asset Management (IAM) Asset Management — an Anatomy, version 3 (December 2015, superseded), already warned that stage names vary:

There are many variations for the descriptions used for the stages of the life cycle. The naming and number of the stages, and the activities under each stage, can vary in different industry sectors. But a common principle is that the life cycle includes all aspects of managing assets from the initial concept through to disposal.9

Treat that as historical IAM guidance (Anatomy v3), not as 2024 ISO clause text and not as Anatomy v4. Anatomy v4 (IAM news, 1 Jul 2024) exists; its body is not quoted here.10

3.2 GFMAM Delivery 6.1–6.8 — the citable stage map

GFMAM’s Landscape “is designed to complement the ISO 5500x suite … which primarily focus on the implementation and use of a Management System.” It is a conceptual map of the discipline, not a compliance standard and not a software specification. Maturity “is not limited to the stages achieved in meeting ISO 55001 requirements.”1

Group 6 Delivery is titled in the PDF “The subjects relating to Life cycle delivery of AM.” The eight subjects, with the definition sentences as printed (free PDF; credit GFMAM):1

CodeSubjectDefinition (GFMAM Landscape v3, as printed)Life-cycle role
6.1Systems Engineering“an interdisciplinary, collaborative approach to derive, evolve, and verify a whole life cycle balanced system solution which satisfies stakeholder expectations and meets organizational outcomes and targets.”Requirements, design, verification and validation, interfaces, handover artefacts
6.2Asset Creation & Acquisition“encompasses activities during the planning, acquisition, design, supply, change management, manufacturing, installation, and commissioning of assets and related systems as well as the transition through the stages of the asset life cycle.”Plan, acquire, design, install, commission, register
6.3Integrated Reliability“a holistic collection of policies, principles, processes, and systems used to deliver, monitor, and improve reliability, Asset Management and life cycle delivery activities towards a system or asset.”Reliability through life (failure modes, criticality, RCA, spares analysis)
6.4Asset Operation“the policies, processes, procedures used by an organization to operate their assets and achieve Asset Management strategic objectives.”Operate within design / service-level / legal parameters
6.5Maintenance Delivery“the management of maintenance work activities for tangible and intangible assets throughout their intended life cycle.”Identify, plan, schedule, execute, analyse maintenance work
6.6Incident Management and Response“a structured approach for addressing incidents in a systematic manner, guided by the severity, risk or criticality of the incident,” covering identification through investigation, remediation and data gathering.Disruptions; not the same as 3.9 contingency planning
6.7Asset Repurposing or Disposal“the processes used by an organization to decommission, retire, repurpose, reclaim, and dispose of assets.”End of life / reuse; residual liabilities
6.8Supply Chain Management“the process used by an organization to ensure the provisioning of all equipment, tools, and resources to perform Asset Management activities are aligned with the Asset Management objectives.”Materials and services through life

Those eight subjects sit inside a seven-group Landscape (Context & Stakeholders; Governance; Asset Management Planning; Leadership and People; Data and Information; Delivery; Value Realization). The seven groups are the Landscape’s subject areas, not an ISO life-cycle cartoon. Do not collapse Landscape subjects with ISO 55001 clauses.111

3.3 The four-word teaching shorthand is a reduction of GFMAM

Teaching shorthand acquire / operate / maintain / dispose is acceptable if labelled as shorthand. It maps onto GFMAM 6.2, 6.4, 6.5 and 6.7 only. It drops 6.1 Systems Engineering, 6.3 Integrated Reliability, 6.6 Incident Management and Response, and 6.8 Supply Chain Management. Do not present the four words as GFMAM-complete, and do not present them as ISO.1

IAM Anatomy v3’s example chains (identify-need → select/purchase → install → operate/maintain → sell/recycle/replace; and identify-need → design → construct → commission → operate/maintain → decommission → residual liabilities) illustrate the same point: naming varies; the common principle is concept-through-disposal. Historical, v3.9

3.4 What each Delivery subject actually covers (PDF body, not a cartoon)

6.1 Systems Engineering. Context in the PDF: requirements analysis, design, verification and validation for system integration and interfaces; continuous across phases; master data and accurate technical information. Named artefacts include a systems-engineering management plan, system requirements, design deliverables, verification and validation strategy, concept of operations, and transition/handover documents. Relevant standards GFMAM lists: ISO/IEC 15288, ISO 10007, ISO 21500 series, ISO 31000, GFMAM Maintenance Framework.1

6.2 Asset Creation & Acquisition. The PDF places this as the stage where the organisation decides specifications and required outputs “to deliver against requirements, Asset Management objectives, and the capability of an asset across the life cycle.” It includes funding, handover to operations, capture of actual costs and benefits, maintainability and reliability requirements, and obsolescence of major systems. Artefacts named: Acquisition Strategy, Acquisition Agreement, asset information records, asset registers and as-built documentation. If commissioning does not write the asset into the register, later reliability statistics have no population (see §3.7).112

6.3 Integrated Reliability. The PDF defines reliability of an asset or system as “its ability to perform and operate as intended for its projected life cycle, in a specific environment or under certain conditions.” Integrated Reliability applies engineering techniques “to identify and mitigate potential failure modes, minimize downtime, and optimize performance throughout the whole life cycle.” It includes reliability/availability/maintainability programmes, failure-mode and criticality-based task selection, MRO spares analysis, management of change / configuration control of technical changes, data collection and interpretation, and root-cause analysis of asset-failure incidents. Artefacts named include asset criticality and risk, spares analysis, asset maintenance strategy, reliability modelling, and root-cause analysis. This is the Landscape home for reliability-through-life; it is not a definition of “APM software.”1

6.4 Asset Operation. Operations are to ensure the asset or system meets functional requirements; is operated within required service levels and design/specified parameters; meets legal and technical requirements (health, safety, environment, security, reliability); achieves defined physical, functional and financial performance; and provides evidence for continual improvement. Artefacts: Asset Operation Strategy, Asset Operations Plan, standard operating procedures.1

6.5 Maintenance Delivery. Identification, planning, scheduling, execution and analysis of maintenance work. Strategies “align to the asset life cycle stage, criticality, and risk” and “may change as the asset ages or if the operational context changes.” Shutdowns, turnarounds and major outages are called out as a significant delivery activity with their own planning, scheduling, approval and stakeholder communication (cross-ref Landscape 3.8). Maintenance delivery “contributes to organizational value through the balance of cost, risk, and performance.” Artefacts include asset maintenance plans, work-management policies, and an STO (shutdown / turnaround / outage) strategy.1

6.6 Incident Management and Response. Whole incident life cycle: identification, escalation, reporting, response, investigation, remediation, data gathering. May draw on pre-established contingency plans (Landscape 3.9). Objectives named: people (on-site and community), environment, assets, reputation. Distinct from 6.3 (reliability of the asset) and from 3.9 (contingency / resilience planning before the event).1

6.7 Asset Repurposing or Disposal. Triggers listed: deterioration, technology improvements, obsolescence, or changes in performance, legal, regulatory and/or capacity requirements. Context: integration with organisational strategic planning; environmental and social focus on reuse, reclamation, recycling and waste/carbon reduction; financial and risk implications as inputs to strategic and asset-management decisions. Artefacts include environmental impact analysis, land rehabilitation plan, SAMP, asset disposal plan, and a maintenance plan for decommissioned assets.1

6.8 Supply Chain Management. Acquire, manage, maintain and enforce contract and supplier management over the entire life cycle, “taking total cost of ownership into consideration.” Includes purchasing, inventory, warehousing, and contracting (requirements, contractor selection, outsourcing/insourcing, claims). Artefacts: forward works / forecast plan, purchasing policy, contractor and service-contract policies. Related Landscape subject 3.7 (Resourcing Strategy and Management) covers people, tools, materials and services needed to deliver asset-management plans; 6.8 is the delivery-side provisioning loop.1

3.5 Costing through life (TOTEX) is not the same as accounting valuation

GFMAM subject 1.3 Asset Costing and Valuation splits two processes:1

The same subject says it is important to keep a close link between accounting systems and asset-management systems, with consistent mechanisms for cost and valuation, and to consider TOTEX as CAPEX plus OPEX through life (including end-of-life). Valuation processes “are typically the responsibility of the organisation’s internal financial department.” Relevant standards GFMAM lists include IFRS and the ISO 5500x series.1

ISO/TS 55010:2024 (Guidance on the alignment of financial and non-financial functions in asset management, ed. 2, 2024-07) is the ISO guidance for that alignment. It is a Technical Specification, not a certifiable requirements standard. Committee-catalogue search extract this pass: stage 90.92 (to be revised); an individual-page search extract listed 60.60. Treat as published Ed. 2, 2024-07; flag the stage letter until a clean catalogue fetch. ISO/AWI 55010 is registered to replace it. TC 251’s project page: the TS “is not developed as a certifiable specification, it has no requirements as such.”1314

ISO 55013:2024 (Guidance on the management of data assets) is not a financial-valuation method for data. Catalogue abstract: it “does not provide methodologies to derive or appraise value for data assets”; “does not provide methodologies to derive financial values for data assets”; “does not provide direction to organizations on the need (or not) for calculating financial values for asset data.”15

Landscape subject 3.6 Life cycle Value Realization is the planning-side counterpart: activities “to ensure the best total value from investments and benefits in different physical and non-physical asset acquisition, creation, operations, maintenance, improvements, renewals, and disposals across all asset life cycle stages.”1

3.6 Where the EAM sits on that path

ISO 55000:2024 does not define work-order fields, PM generation, or storeroom min/max. Those sit in maintenance-execution practice and in the product.2

In industry usage (not ISO), EAM software is the transactional system of record for hierarchy, work, materials and often cost from acquisition toward end-of-life. IBM Think (vendor article, labelled): EAM is “an asset lifecycle management solution focused on optimizing the overall lifetime performance of assets from acquisition to end-of-life”; it provides data on lifetime costs (purchasing, maintenance, repair, servicing) toward total cost of ownership; CMMS is “dedicated to MRO … once an asset has been installed.”4

GFMAM subject 5.4 Asset Management Data & Information Systems: those systems “support Asset Management activities and decision-making”; “the holistic nature of Asset Management requires integration and interoperability across multiple asset information systems.” They should integrate “across functional areas, the asset life cycle, and internal and external stakeholder systems.” The EAM application is one such system, not the AMS.1

Landscape subject 3.4 Planning specifies that asset-management plans name “the asset life cycle activities an organization intends to undertake,” with costs, resources and time horizon, and that plans are held “in enterprise systems e.g., financial systems, resource management systems and Asset Management systems.”1

Subject 3.1 places the organisation’s whole-life-cycle approach in the SAMP: the Asset Management Strategy “is contained in the Strategic Asset Management Plan (SAMP).” The SAMP “describes the organisation’s whole life cycle approach to the management of the assets defined by the organization within the scope of their Asset Management system.”1

3.7 Commissioning and retirement must hit the register

If the asset is never written to the hierarchy at commissioning, or never removed at retirement, later mean-time-between-failures (MTBF) arithmetic is fiction: the population (count of identical units in service, with install/remove dates) is the denominator.

ISO 14224:2016 (Petroleum, petrochemical and natural gas industries — Collection and exchange of reliability and maintenance data for equipment, ed. 3, 2016-09, confirmed 2022) is the data-collection standard for that job. Catalogue abstract: it provides a basis for collecting reliability and maintenance (RM) data “during the operational life cycle of equipment”; defines a “reliability language”; treats failure modes in the normative part as a “reliability thesaurus”; and requires a minimum of equipment data (taxonomy/attributes), failure data (cause, consequence) and maintenance data (action, resources, downtime). Stated field of application is petroleum, natural gas and petrochemical; the taxonomy is widely borrowed. It does not cover direct cost data.12

A consultancy navigator (iFluids, 20 Jun 2026 — not the standard text) restates four record types: equipment inventory, failure events, maintenance events, and population (in-service count with install/remove dates). Omitting churn inflates MTBF. Use that as a labelled secondary; buy ISO 14224 before quoting annex tables.16

NASA NPR 8831.2F Appendix E (US agency procedure, not ISO): work orders can be written against a location or against equipment at a location; “using locations allows for tracking the equipment’s life cycles (history).” Chapter 6 makes facility/equipment inventory an essential CMMS function. Commissioning and retirement are hierarchy events, not optional metadata.1718

GFMAM 6.2 artefacts already name “Asset Registers and As-Built documentation.” GFMAM 6.7 artefacts name an asset disposal plan and a maintenance plan for decommissioned assets. Configuration management (Landscape 5.5) is “establishing and maintaining consistency of an asset’s physical and functional attributes with its design and operational information throughout its life cycle.”1

3.8 Capital / asset investment planning is adjacent

Replace-versus-repair, life extension, and portfolio capital allocation are decision problems (Landscape 3.5 Decision-Making; 3.6 Life cycle Value Realization). They are not a CMMS work-order type.

IBM Think (vendor, labelled) describes asset investment planning as deciding, over a medium-to-long horizon, how to allocate capital and resources to minimise total lifecycle costs, including end-of-life risk; inputs include “failure history and work orders from EAM/CMMS.” IBM also sells Maximo Asset Investment Planning as a product that consumes Maximo Manage registry, work history and failure codes — product adjacency, not a definition of EAM.6

IFS (vendor, labelled) treats AIP and EAM as distinct capabilities inside a wider asset-lifecycle-management offer: AIP “helps organizations prioritize and allocate resources for infrastructure and equipment investments” balancing cost, risk and performance; EAM is described as managing the lifecycle of physical assets “from acquisition to disposal.” Copperleaf is presented as IFS’s AIP product, fed from EAM/ERP data — again adjacency, not a CMMS module renamed.519

Do not relabel AIP “EAM.” Do not treat vendor “end-to-end ALM” slogans as ISO.

3.9 Dependability programmes sit in the same life cycle; they are not the AMS

IEC 60300-1:2024 (Dependability management – Part 1: Managing dependability, ed. 4.0, 2024-06-11) is the head document of IEC/TC 56. Webstore abstract (free): guidance on the meaning of dependability from a business, technical and financial perspective; achieving dependability by adapting organisational management systems “such as those described in ISO 9001 … and ISO 55001”; activities integrated into management systems and life-cycle processes; planning and implementing dependability activities throughout the life cycle. Applicable to any system, product or service; addresses hardware, software, data, processes, facilities, materials and personnel. Paywalled body not quoted.20

IEC/TC 56’s public catalogue notes treat dependability as “ability to perform as required when required,” list IEC 60300-3-3:2017 (life-cycle costing) and IEC TS 62775:2016 (implementing AM systems with dependability / IFRS / ISO 5500x tools). Those are complementary technical documents, not replacements for ISO 55001.21

IAM warning on design lock-in (Anatomy v3, not independently re-measured): Anatomy v3 states that “the design phase, which can determine as much as 80% of the total life cycle costs of an asset.” That is IAM’s statement in a superseded document, not an ISO measurement and not a universal constant. Flag, do not promote as a law of physics.9

Sources

  1. GFMAM, The Asset Management Landscape, 3rd ed., English, June 2024, ISBN 978-1-7774676-8-5. Free PDF; credit GFMAM. Fetched 28 Aug 2026. Purpose statement (complements ISO 5500x); maturity not limited to ISO 55001; subject 1.3 (TOTEX / valuation); 2.2 (AMS); 3.1 (SAMP, whole-life-cycle approach); 3.4 (asset life-cycle activities in plans); 3.6 (life-cycle value realization); 5.4 (data and information systems); 5.5 (configuration management); group 6 Delivery, subjects 6.1–6.8 in full (definitions, context, artefacts). — https://gfmam.org/sites/default/files/2024-06/GFMAM_AM_Landscape_v3.0_English_2024.pdf
  2. ISO 55000:2024 catalogue — https://www.iso.org/standard/83053.html — Asset management — Vocabulary, overview and principles, ed. 2, 2024-07 (CMS lifecycle 2024-07-03), stage 60.60. Abstract/FAQ free; full text paywalled. HTML body Cloudflare-blocked 28 Aug 2026 on some fetches; title, date and FAQ extract from search/catalogue metadata plus earlier pack.
  3. ISO 55001:2024 catalogue — https://www.iso.org/standard/83054.html — Asset management — Asset management system — Requirements, ed. 2, 2024-07. Fetched in an earlier pass this date (18 pages; previous ISO 55001:2014 withdrawn). FAQ: 55000 = overview/terminology; 55001 = AMS requirements; 55002 = application guidance; lifecycle control / cost-risk-performance.
  4. IBM Think, “CMMS vs. EAM” — https://www.ibm.com/think/topics/cmms-vs-eam — vendor article. Fetched 28 Aug 2026. Industry usage: EAM from acquisition to end-of-life; lifetime costs toward TCO. Product close on that page is not used as evidence.
  5. IFS, Asset Lifecycle Management / EAM portfolio — https://www.ifs.com/en/products/alm and https://www.ifs.com/en/products/alm/eam — vendor. AIP vs EAM as distinct capabilities. Copperleaf as AIP: https://www.ifs.com/en/insights/news/ifs-copperleaf-accelerate-program (16 Oct 2024) and https://www.ifs.com/en/insights/assets/introducing-true-end-to-end-asset-lifecycle-management. Not a ranking.
  6. IBM Think, “How asset investment planning drives better capital decisions” — https://www.ibm.com/think/insights/asset-investment-planning-drives-better-capital-decisions — vendor. AIP uses EAM/CMMS failure history and work orders; Maximo AIP as a product adjacency.
  7. ISO/TC 251 About — https://committee.iso.org/home/tc251 — 2024 launch (3 Jul 2024); “life cycle operations” among 55001 themes; “all types of assets.” Cloudflare on some fetches; wording from search extract of the same URL plus earlier pack.
  8. ISO 55012:2024 catalogue — https://www.iso.org/standard/82454.html — Guidance on people involvement and competence, ed. 1, 2024-07, stage 60.60. Abstract: personnel involvement / SAMP / plans / competence; applicable even if AM is not run as a formal AMS. Search-index extract of the catalogue URL (iso.org HTML Cloudflare-blocked this pass).
  9. IAM, Asset Management — an Anatomy, v3, Dec 2015 (superseded) — https://theiam.org/media/1781/iam_anatomy_ver3_web.pdf — §2.3.5 life-cycle stage-name variation; design-phase cost lock-in statement. Historical only. Do not treat as Anatomy v4 or as ISO 55000:2024.
  10. IAM news, “Release of version 4 of the IAM Asset Management Anatomy,” 1 Jul 2024 — https://theiam.org/news/release-of-version-4-of-the-iam-asset-management-anatomy/ — v4 dated; GFMAM Landscape 3rd ed. released 5 Jun 2024; 10-box capabilities model. Body of v4 not opened / not quoted. Landing: https://theiam.org/knowledge-library/asset-management-an-anatomy/ · short URL https://theiam.org/AMA
  11. Assetivity, “Asset Management Landscape v3 — implications for asset managers” — https://www.assetivity.com.au/articles/asset-management/asset-management-landscape-v3-implications-for-asset-managers/ — labelled secondary on Landscape vs ISO 55000-family (Landscape is not a compliance standard). Primary remains the GFMAM PDF 1.
  12. ISO 14224:2016 catalogue — https://www.iso.org/standard/64076.html — RM data collection, operational life cycle, reliability language, failure-mode thesaurus, min. equipment/failure/maintenance data. Ed. 3, 2016-09, confirmed 2022. Abstract free; body paywalled. Sector-titled (oil/gas/petrochemical).
  13. ISO/TS 55010:2024 catalogue — https://www.iso.org/standard/84051.html — Guidance on the alignment of financial and non-financial functions in asset management, ed. 2, 2024-07, stage 90.92. Replaces ISO/TS 55010:2019 (withdrawn). ISO/AWI 55010 will replace the 2024 TS.
  14. ISO/TC 251 project page, ISO/TS 55010 — https://committee.iso.org/sites/tc251/home/projects/published/isots-55010.html — not a certifiable specification; no requirements as such; intended to bridge finance and non-finance.
  15. ISO 55013:2024 catalogue — https://www.iso.org/standard/82455.html — Guidance on the management of data assets, ed. 1, 2024-07. Abstract: no methodologies to derive or appraise value / financial values for data assets. Fetched via search-index extract of the catalogue URL this pass.
  16. iFluids, “ISO 14224 reliability failure data guide,” 20 Jun 2026 — https://ifluids.com/standard/iso-14224-reliability-failure-data-guide/ — consultancy navigator, not the standard. Population as denominator; mode ≠ mechanism ≠ cause. Buy ISO 14224 before quoting annexes.
  17. NASA NPR 8831.2F Appendix E — https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_8831_002F_&page_name=AppendixE — locations vs equipment; tracking equipment life cycles / history. Free (US government). Agency procedure, not ISO.
  18. NASA NPR 8831.2F Chapter 6 — https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_8831_002F_&page_name=Chapter6 — CMMS essential inventory function. Appendix A definitions: https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_8831_002F_&page_name=AppendixA
  19. IFS EAM product page — https://www.ifs.com/en/products/alm/eam — vendor. Used only to show AIP ≠ CMMS. Outline also pointed here for Copperleaf as AIP.
  20. IEC 60300-1:2024 webstore — https://webstore.iec.ch/en/publication/66489 — ed. 4.0, 2024-06-11. Abstract free; text paywalled (CHF 380). Points at adapting ISO 9001 and ISO 55001; life-cycle dependability activities.
  21. IEC/TC 56 dependability standards — https://tc56.iec.ch/dependability-standards/ — 60300-1 as head document; 60300-3-3:2017 LCC; IEC TS 62775:2016 AM systems × dependability × IFRS × ISO 5500x.

Not used. Invented ISO seven-box diagrams; Anatomy v4 body; pirate / iteh full-text PDFs (iteh catalogue abstracts were used where iso.org HTML was blocked; paid body was not quoted); Twiniti or IBM-partner claims.