{
  "version": "2026-08-29.1",
  "reviewed": "2026-08-29",
  "scope": "A source-row requirements map for deciding whether maintenance execution is the main procurement problem or whether full asset-lifecycle governance must be evaluated. The classifications and triage thresholds are Inzonex editorial logic, not ISO requirements or vendor performance results.",
  "sources": {
    "iso55000": {
      "label": "ISO 55000:2024 overview",
      "url": "https://www.iso.org/standard/83053.html",
      "type": "standards-body overview",
      "claim": "Asset management aligns asset objectives with organizational objectives and manages assets through their life cycles to realize value."
    },
    "iso55001": {
      "label": "ISO/TC 251 ISO 55001 overview",
      "url": "https://committee.iso.org/sites/tc251/home/projects/published/iso-55001.html",
      "type": "standards-body overview",
      "claim": "ISO 55001 specifies requirements for establishing, implementing, maintaining and improving an asset-management system; organizations determine the assets in scope."
    },
    "ibm_cmms": {
      "label": "IBM: What is a CMMS?",
      "url": "https://www.ibm.com/think/topics/what-is-a-cmms",
      "type": "vendor educational documentation",
      "claim": "CMMS core functions include work orders, preventive and predictive maintenance scheduling, spare-parts inventory, mobile access and reporting."
    },
    "ibm_eam": {
      "label": "IBM: What is enterprise asset management?",
      "url": "https://www.ibm.com/think/topics/enterprise-asset-management",
      "type": "vendor educational documentation",
      "claim": "EAM covers the asset lifecycle from procurement to disposal and combines maintenance with planning, supply-chain and EHS scope."
    },
    "sap_eam": {
      "label": "SAP: What is enterprise asset management?",
      "url": "https://www.sap.com/products/scm/asset-management-eam/what-is-eam.html",
      "type": "vendor educational documentation",
      "claim": "EAM connects lifecycle asset information across maintenance, operations, finance, planning and supply-chain processes."
    },
    "ibm_compare": {
      "label": "IBM: CMMS vs EAM",
      "url": "https://www.ibm.com/think/topics/cmms-vs-eam",
      "type": "vendor educational comparison",
      "claim": "CMMS focuses predominantly on maintenance, while EAM has broader lifecycle and cross-functional scope."
    }
  },
  "requirements": [
    {
      "id": "work_orders",
      "requirement": "Create, assign, prioritize and close work orders",
      "classification": "maintenance_core",
      "cmms_boundary": "Core documented CMMS function",
      "eam_boundary": "Also expected inside EAM maintenance scope",
      "decision_use": "Not a discriminator by itself",
      "sources": [
        "ibm_cmms",
        "ibm_eam"
      ]
    },
    {
      "id": "preventive_maintenance",
      "requirement": "Schedule preventive and condition-triggered maintenance",
      "classification": "maintenance_core",
      "cmms_boundary": "Documented CMMS function",
      "eam_boundary": "Also present in EAM work management",
      "decision_use": "Not a discriminator by itself",
      "sources": [
        "ibm_cmms",
        "sap_eam"
      ]
    },
    {
      "id": "spares",
      "requirement": "Track MRO inventory and spare-parts consumption",
      "classification": "maintenance_core",
      "cmms_boundary": "Documented CMMS function",
      "eam_boundary": "Can connect to wider supply-chain processes",
      "decision_use": "Integration depth matters more than the label",
      "sources": [
        "ibm_cmms",
        "sap_eam"
      ]
    },
    {
      "id": "maintenance_history",
      "requirement": "Keep asset maintenance history and audit evidence",
      "classification": "maintenance_core",
      "cmms_boundary": "Documented CMMS function",
      "eam_boundary": "Part of a broader governed asset record",
      "decision_use": "Not a discriminator until cross-functional records are required",
      "sources": [
        "ibm_cmms",
        "sap_eam"
      ]
    },
    {
      "id": "asset_hierarchy",
      "requirement": "Maintain a consistent asset register and hierarchy",
      "classification": "shared_foundation",
      "cmms_boundary": "Needed for reliable maintenance records",
      "eam_boundary": "Extended across lifecycle and enterprise processes",
      "decision_use": "Test hierarchy depth, ownership and synchronization",
      "sources": [
        "ibm_cmms",
        "sap_eam"
      ]
    },
    {
      "id": "condition_data",
      "requirement": "Use sensor, condition or predictive-maintenance data",
      "classification": "shared_foundation",
      "cmms_boundary": "Modern CMMS can ingest condition data and trigger work",
      "eam_boundary": "EAM can contextualize condition with enterprise plans",
      "decision_use": "Not a discriminator; test the exact data route",
      "sources": [
        "ibm_cmms",
        "ibm_eam"
      ]
    },
    {
      "id": "lifecycle_scope",
      "requirement": "Govern the asset from acquisition or design through retirement",
      "classification": "eam_signal",
      "cmms_boundary": "Maintenance-stage records may contribute",
      "eam_boundary": "Full-lifecycle scope is a defining EAM signal",
      "decision_use": "Add one EAM-scope signal",
      "sources": [
        "iso55000",
        "ibm_eam",
        "sap_eam"
      ]
    },
    {
      "id": "capital_planning",
      "requirement": "Link condition and cost evidence to capital replacement planning",
      "classification": "eam_signal",
      "cmms_boundary": "Can supply maintenance cost and condition history",
      "eam_boundary": "Capital and lifecycle planning are broader EAM scope",
      "decision_use": "Add one EAM-scope signal",
      "sources": [
        "iso55000",
        "ibm_eam",
        "sap_eam"
      ]
    },
    {
      "id": "financial_integration",
      "requirement": "Connect asset records to finance, procurement and total lifecycle cost",
      "classification": "eam_signal",
      "cmms_boundary": "Connector or ERP handoff may be sufficient",
      "eam_boundary": "Cross-functional financial and supply-chain context is a common EAM boundary",
      "decision_use": "Add one EAM-scope signal",
      "sources": [
        "ibm_eam",
        "sap_eam",
        "ibm_compare"
      ]
    },
    {
      "id": "enterprise_governance",
      "requirement": "Apply common asset definitions and governance across sites and business functions",
      "classification": "eam_signal",
      "cmms_boundary": "A multi-site CMMS may still satisfy the requirement",
      "eam_boundary": "Enterprise-wide governed asset data is a strong EAM evaluation signal",
      "decision_use": "Add one EAM-scope signal, then verify actual product scope",
      "sources": [
        "iso55001",
        "sap_eam"
      ]
    },
    {
      "id": "portfolio_risk",
      "requirement": "Align portfolio risk, assurance and asset decisions with organizational objectives",
      "classification": "eam_signal",
      "cmms_boundary": "Maintenance evidence is an input, not the whole management system",
      "eam_boundary": "Broader asset-management governance may require EAM plus process change",
      "decision_use": "Add one EAM-scope signal; software alone does not establish ISO conformity",
      "sources": [
        "iso55000",
        "iso55001"
      ]
    },
    {
      "id": "cross_functional_workflow",
      "requirement": "Coordinate maintenance, operations, finance, planning and supply chain on one asset context",
      "classification": "eam_signal",
      "cmms_boundary": "May be handled through integrations and operating procedures",
      "eam_boundary": "Cross-functional lifecycle coordination is a common EAM signal",
      "decision_use": "Add one EAM-scope signal",
      "sources": [
        "sap_eam",
        "ibm_eam"
      ]
    }
  ],
  "signals": [
    {
      "id": "lifecycle_scope",
      "label": "Lifecycle from acquisition/design through retirement"
    },
    {
      "id": "capital_planning",
      "label": "Capital replacement planning tied to asset evidence"
    },
    {
      "id": "financial_integration",
      "label": "Finance, procurement or lifecycle-cost integration"
    },
    {
      "id": "enterprise_governance",
      "label": "Common governance across sites and functions"
    },
    {
      "id": "portfolio_risk",
      "label": "Portfolio risk and assurance aligned to business objectives"
    },
    {
      "id": "cross_functional_workflow",
      "label": "Shared asset context across maintenance, operations and planning"
    }
  ],
  "faqs": [
    {
      "question": "What is the main difference between CMMS and EAM?",
      "answer": "CMMS concentrates on maintenance execution such as work orders, preventive schedules, spares and history. EAM evaluates the broader lifecycle and cross-functional governance of assets. Product boundaries overlap, so requirements and integrations matter more than the label."
    },
    {
      "question": "Can a multi-site company still use a CMMS?",
      "answer": "Yes. Site count alone does not prove that EAM is required. Test hierarchy, permissions, data ownership, finance and procurement integration, lifecycle planning and reporting across the actual sites."
    },
    {
      "question": "Does ISO 55001 require EAM software?",
      "answer": "No. ISO 55001 specifies requirements for an asset-management system, while an organization determines the assets and processes in scope. This page does not treat buying software as certification or conformity."
    },
    {
      "question": "Is predictive maintenance an EAM-only feature?",
      "answer": "No. Current CMMS documentation also describes condition data and predictive-maintenance workflows. Verify sensors, event handling, false alerts, work-order creation and evidence retention in the actual product."
    },
    {
      "question": "Is the decision result a product recommendation?",
      "answer": "No. It is an Inzonex triage of six scope signals. Use the downloadable checklist to verify requirements, integrations, commercial scope and acceptance evidence with shortlisted suppliers."
    }
  ],
  "reuse": "The original requirements compilation, triage logic, chart and blank checklist are CC BY 4.0 with attribution to Inzonex. Source facts, standards, vendor documentation and trademarks retain their respective rights."
}