Enterprise Asset Management data model

  • Release version: Australia
  • Updated March 25, 2026
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Enterprise Asset Management data model

    The Enterprise Asset Management (EAM) data model offers a structured framework for representing, tracking, and managing physical assets and their relationships throughout their entire life cycles. It is composed of interconnected entities and relationships that guide the flow of asset-related data from initial definition to procurement, operation, maintenance, and retirement. This model distinguishes between standardized asset definitions (enterprise models) and actual physical objects (enterprise assets), ensuring clarity and control over asset information.

    Show full answer Show less

    Core Components

    • Enterprise Model Classes: Tables storing standardized asset type definitions, including specifications and structural compositions, supporting consistent data standardization through inheritance.
    • Enterprise Asset Classes: Tables storing real-world asset records categorized by asset type to facilitate maintenance strategies, compliance, and life-cycle workflows.
    • Configuration Management Database (CMDB) CI Classes: Tables storing configuration item records linked to enterprise models and assets via model categories, providing a unified asset view across EAM and CMDB.
    • Model Categories: These define mappings between enterprise model classes, asset classes, and CMDB CI classes, enabling integrated workflows throughout the asset life cycle.

    System Architecture and Functional Components

    The EAM system architecture extends beyond the data model to support end-to-end asset management processes, including procurement, maintenance, and disposal. Key components include:

    • Model Management: Features standardized asset definitions, content libraries, and model classifications.
    • Discovery: Capabilities such as Service Graph Connectors and CI discovery aligned with enterprise model categories.
    • Asset Management: Encompasses asset creation, categorization, linear asset management, and bi-directional synchronization between assets and CIs, along with financial tracking.
    • Functional Modules: Support workflows and tasks in areas like life-cycle management, analytics, inventory, work and procurement management, contracts, and location hierarchies.
    • Capabilities: Include asset onboarding, stockroom management, and other operational functions within the modules.

    Additional Organizational Features

    • Model Classification: Organizes enterprise models and assets consistently across the ServiceNow platform.
    • Model Types: Define structural characteristics of enterprise models, such as standalone assets, consumables tracked by quantity, or complex assemblies with multiple components.
    • Asset Groups: Organize assets based on functional relationships and physical locations to enhance data integrity, maintenance planning, life-cycle tracking, reporting, and access control.
    • Linear Assets: Enables management of assets that are linear in nature, expanding asset management capabilities.

    Practical Benefits for ServiceNow Customers

    This comprehensive data model and its associated system architecture allow ServiceNow customers to systematically manage diverse asset types with standardized definitions and classifications. By linking enterprise models, assets, and configuration items, customers gain a unified and consistent view of their asset portfolio. This supports improved maintenance strategies, compliance adherence, lifecycle management, and operational efficiency across procurement, usage, and retirement phases.

    The Enterprise Asset Management data model provides a structured framework for representing, tracking, and managing physical assets and their relationships throughout their life cycles.

    Enterprise Asset Management data model overview

    The Enterprise Asset Management data model defines how asset-related data is created, classified, synchronized, and governed. It is not a single table or diagram. Instead, it is a connected set of entities and relationships that act as guardrails for how asset-related data flows from initial definition through procurement, operation, maintenance, and retirement.

    Enterprise models and assets

    The Enterprise Asset Management data model uses enterprise models and assets to separate standardized asset definitions from real-world physical objects.
    • An enterprise model defines an enterprise asset type. Each enterprise model contains a set of asset specifications, attributes, and structural compositions, including information about whether its associated assets are standalone or multi-component.
    • An enterprise asset represents a real-world physical object that is purchased, received, deployed, and tracked throughout its operational life. Every enterprise asset is created from an enterprise model.

    Core components of the Enterprise Asset Management data model

    The Enterprise Asset Management data model is built around three core structural components: enterprise model classes, enterprise asset classes, and Configuration Management Database (CMDB) CI classes.

    Enterprise model classes

    Enterprise model classes are tables that store enterprise model records. Records are organized by model type, such as the facility model or medical model. Each enterprise model class defines a set of attributes that are common to all enterprise model records stored within the given table. Extended enterprise model classes inherit attributes from their parent model classes, enabling consistent data standardization across related model types.

    For more information on enterprise model classes, see Enterprise model and asset classes.

    Enterprise asset classes

    Enterprise asset classes are tables that store enterprise asset records. Records are organized by asset type, such as industrial assets or medical assets. Enterprise asset classes categorize assets based on their function or usage, helping you define maintenance strategies, compliance rules, and life-cycle workflows for different asset types.

    For more information on enterprise asset classes, see Enterprise model and asset classes.

    CMDB CI classes

    CMDB CI classes are tables that store configuration item (CI) records. Each CMDB CI class maps to corresponding enterprise model and asset classes through model categories, creating a unified view of assets across the Enterprise Asset Management application and the CMDB.

    For more information on the CMDB and CMDB CI classes, see Configuration Management Database (CMDB).

    These core components link to each other through enterprise model categories. Each enterprise model category maps an appropriate enterprise model class, enterprise asset class, and CMDB CI class together for a given enterprise asset type. The associated models, assets, and CIs can then work together across various workflows throughout the asset life cycle, including procurement and maintenance. For more information on model categories, see Model categories.
    Figure 1. Relationship between enterprise models, enterprise assets, and CIs
    Overview of how enterprise models, enterprise assets, and CIs link to each other.

    Enterprise Asset Management system architecture

    The system architecture of the Enterprise Asset Management application is comprised of components that extend beyond the core data model components. Together, these components support the end-to-end asset management process, from procurement to disposal.

    Figure 2. Enterprise Asset Management system architecture
    Enterprise Asset Management system architecture.
    Table 1. Enterprise Asset Management system architecture components
    Component Description
    Model management Supported model management features and capabilities:
    • Standardized asset definitions
    • Enterprise Asset Management Content Library
    • Enterprise model classifications
    Discovery Supported discovery features and capabilities:
    • Service Graph Connectors
    • CI discovery aligned with enterprise model categories
    Asset management Supported asset management features and capabilities:
    • Asset creation
    • Categorization of assets by asset type
    • Linear asset management
    • Bi-directional asset and CI synchronization
    • Financial data tracking
    Functional modules Supported functional modules in which you can perform tasks and complete workflows:
    • Life-cycle workflows
    • Analytics
    • Inventory management
    • Work management
    • Procurement management
    • Contract management
    • Location hierarchies and indoor maps
    Capabilities

    Supported capabilities within each functional module. Examples include asset onboarding and stockroom management.

    For the complete list of capabilities within each module, refer to the previous Enterprise Asset Management system architecture diagram.