What EAM is

Enterprise asset management (EAM) is used in two overlapping senses: as a discipline of managing physical assets across their life, and as a software class that records hierarchy, work, materials and often cost. Neither sense is the object of the ISO 55000 family. That family specifies asset management (vocabulary, overview and principles) and an asset management system (a management system of policies, objectives and processes). Buying or configuring EAM software is neither necessary nor sufficient for ISO 55001 certification.¹²⁴

1.1 Three terms that are not synonyms

GFMAM states that its Landscape “is designed to complement the ISO 5500x suite … which primarily focus on the implementation and use of a Management System.”⁶ That is the conceptual map of the discipline. It is not a software specification and it is not a substitute for ISO 55001.

Uncertainty. Verbatim ISO 55000:2024 clause 3 definitions of “asset,” “asset management,” and “value” were not copied here (paywall; Online Browsing Platform preview not captured). Do not treat the catalogue FAQ or IAM public gloss as clause text.¹

1.2 Public glosses (labelled, not clause 3)

The Institute of Asset Management (IAM), on its public homepage (fetched 28 Aug 2026), states:

Assets are anything with actual or potential value to an organization. Asset Management is an organization's activity to realize value from its assets.¹⁰

Treat that as IAM’s public gloss, not a substitute for ISO 55000:2024 clause wording.

IAM’s superseded Asset Management — an Anatomy, version 3 (December 2015), quotes ISO 55000:2014 clause 3:

• Asset (3.2.1): “item, thing or entity that has potential or actual value to an organization.”
• Asset management (3.3.1): “the coordinated activity of an organization to realise value from assets,” with notes that realisation of value normally balances costs, risks, opportunities and performance benefits, and that “activity” can include approach, planning, plans and implementation.¹¹

2024 clause 3 was not licensed for this draft. 2014 wording is historical only. Anatomy v3 also warns that a web search for “asset management” yields finance and many physical-asset variants (strategic, property, facilities, infrastructure, enterprise asset management) but “the qualifying descriptors do not change the inherently consistent core,” and that asset management is “more than doing things to assets — it is about using assets to deliver value.”¹¹

ISO.org’s catalogue FAQ for ISO 55000:2024 (catalogue-page language, not clause text) describes the document as providing overview, terminology and principles for managing assets over their life cycles and realising value, and names as key elements: aligning asset-management objectives with organisational objectives; a strategic approach throughout the lifecycle; and use of an asset management system to realise value. ISO 55000 provides context for ISO 55001 (AMS requirements) and ISO 55002 (application guidelines).¹

ISO 55002 remains the 2018 edition (stage 90.92, to be revised; ISO/CD 55002.2 is in committee). There is no published ISO 55002:2024. Implementers use ISO 55001:2024 for requirements and ISO 55002:2018 as guidance that may not line up clause-for-clause.¹²

1.3 Scope: all asset types vs physical plant

ISO/TC 251 states that the 55000-family standards apply to all types of assets, not only plant and equipment.⁵ The predecessor UK specification, BSI PAS 55 (2003/2004, revised 2008, withdrawn 30 Jan 2015), was explicitly about physical assets; BSI presents it as transformed into the three-part ISO 55000/55001/55002 series.¹³ Physical-EAM software, IT asset management (ITAM), data-as-an-asset guidance, and financial fixed-asset registers must stay distinct:

• ITAM. ISO/IEC 19770-1:2017 specifies requirements for an IT asset management system and is described on the catalogue as a discipline-specific extension of ISO 55001:2014; conformance to 19770-1 does not imply conformance to 55001. The 19770-1 page was confirmed in 2024; whether it will be aligned to ISO 55001:2024 is not stated there.¹⁴
• Physical location vs cyber inventory. NIST Special Publication 1800-5 (September 2018) draws the contrast directly: “a physical asset management system can tell you the location of a computer” but cannot answer operating-system or vulnerability questions; ITAM ties physical and virtual IT assets for security and utilisation. That guide is a cybersecurity practice document for financial-services ITAM, not a plant-EAM standard.¹⁵
• Cyber “asset management” in NIST CSF 2.0 (CSWP 29, 26 Feb 2024) is the ID.AM category — identification of data, hardware, software, systems, facilities, services and people for cybersecurity. Useful to disambiguate the phrase “asset management”; not a definition of EAM.¹⁶
• Data as an asset. ISO 55013:2024 is guidance on managing data to support asset-management objectives. The catalogue abstract states that it does not provide methodologies to derive or appraise financial values for data assets.¹⁷
• Financial vs maintenance register. ISO/TS 55010:2024 is guidance on aligning financial and non-financial asset-management functions. GFMAM Landscape subject 1.3 treats costing (TOTEX through life) and accounting valuation (IFRS) as related but distinct processes.¹⁸⁶

1.4 What plants call “the EAM”

In operations, “the EAM” almost always means the application: the system of record for asset hierarchy, work orders, preventive-maintenance generation, spare-parts inventory, and often purchasing and cost settlement. ISO 55000:2024 does not define work-order fields, PM cron jobs, or storeroom min/max; those sit in maintenance-execution practice and in the product.¹¹⁹

Gartner Peer Insights (Enterprise Asset Management Software market, page updated June 2026) defines EAM software as “a category of business applications used mostly by asset-intensive industries to execute, track and optimize inspections, maintenance and repair of industrial plant and equipment,” “primarily a transactional workflow system designed for the purposes of management and execution of capital asset maintenance,” which “may be included or integrated with a wider ERP suite.”⁸

IBM Think (vendor article, labelled): EAM “emerged from CMMS early in the 1990s,” bringing maintenance planning and execution together with skills, materials and information “spanning asset design through to decommissioning.” Typical EAM coverage in that article: work orders, contract and labour management, planning and scheduling, condition monitoring, reliability analysis, supply chain, and often environment, health and safety (EHS) applications; EAM can link into enterprise resource planning (ERP). That is industry usage of the software class, not a standard.⁹

SAP’s product FAQ (vendor, labelled) describes EAM as managing “the lifecycle of physical assets including capital planning, procurement, installation, performance, maintenance, compliance, risk management, and asset disposal,” sitting inside supply-chain / ERP rather than as a standalone computerized maintenance management system (CMMS).²⁰

Octave’s Attune EAM FAQ (vendor, labelled) uses a similar software sense: “the software, services and systems an organization uses to manage and maintain physical assets and equipment,” with focus on managing an asset “across its entire lifecycle.”²¹

None of those vendor pages is an ISO definition. They are consistent enough to describe how the product class is sold.

1.5 What EAM software typically records

A defensible minimum, from public non-vendor and labelled-vendor sources combined:

• Register / hierarchy. Maintainable assets and locations (the inventory NASA’s CMMS definition starts with; GFMAM 6.2 names asset registers and as-built documentation as creation/acquisition artefacts).²²⁶
• Work. Requests, work orders, planning, scheduling, history. IBM Think’s work-order topic (vendor): work orders are the system of record for maintenance and service activity; the data feed asset history and later decisions.²³
• Materials. Item master, reservations and issues against work, often procurement. NASA NPR 8831.2F lists materials management among typical CMMS functions.²²
• Cost. Labour, materials and often settlement to a cost object; lifetime cost toward total cost of ownership is the EAM-side claim in IBM Think (vendor).⁹
• Interfaces. Finance / ERP, and increasingly condition and reliability tools. GFMAM subject 5.4: asset-management data and information systems “support Asset Management activities and decision-making”; “the holistic nature of Asset Management requires integration and interoperability across multiple asset information systems.”⁶

That list is a system of record. Strategy (what should be on a preventive-maintenance plan; which failure modes matter) lives in reliability methods such as SAE JA1011 (reliability-centred maintenance evaluation criteria) and in the organisation’s AMS — not in the cron that generates the work order.¹⁹²⁴

1.6 History in one paragraph

Paper and siloed files did not scale. IBM Think (vendor) dates CMMS to the 1960s as a response to that, with work-order, project and spare-parts functions expanding through the 1980s–2000s, and EAM emerging from CMMS in the early 1990s as the scope widened from installed-base maintenance to life-cycle cost, multi-site control and enterprise links.⁹ NASA still uses CMMS, not “EAM,” in NPR 8831.2F (facilities maintenance and operations management; effective 7 Oct 2015, expires 30 Jun 2027) — a US-agency procedure, not a global standard, but a complete public definition of work-control software.²²²⁵ PAS 55 (BSI, withdrawn 2015) then ISO 55000 (first published January 2014; 2024 edition July 2024 on ISO.org) standardised the management system for asset management, which is a different object from the software that plants nicknamed “the EAM.”¹¹³⁷

1.7 What this article is not

• It is not a claim that ISO 55000 “is the EAM standard.” ISO/TC 251 products speak of asset management and an asset management system. Software vendors and NASA (for facilities work control) speak of EAM / CMMS.¹²³²²
• It is not a buying recommendation, a Magic Quadrant, or a partner directory. No 2026 Gartner Magic Quadrant for EAM was located as a primary Gartner document for this pack.⁸
• Certification, where used, is of the organisation’s AMS. GFMAM publishes Guidance for an Asset Management System Scheme for Accredited Certification to ISO 55001 reflecting ISO 55001:2024 (publications index date 2026-06). ISO itself does not certify organisations.⁷