Asset management models give organizations a structured way to connect stakeholder expectations, organizational objectives and day-to-day asset decisions. In the Asset Management Council framework, three complementary models describe this connection: the Asset Management Concept Model, the Asset Management System Model and the Capability Delivery Model.
Each model addresses a different decision level. The Concept Model establishes strategic intent, the System Model creates governance and management controls, and the Capability Delivery Model turns plans into operational capability. Used together, the three asset management models create a line of sight from organizational purpose to asset performance, cost, risk and lifecycle decisions.
What Are Asset Management Models?
An asset management model is a structured representation of how an organization makes decisions about assets, establishes an asset management system and delivers value across the asset lifecycle. Models simplify a complex management environment by showing the relationships between stakeholders, objectives, governance, information, people, processes and operational work.
| Asset management model | Decision level | Core question | Primary focus | Typical outputs |
|---|---|---|---|---|
| Concept Model | Strategic | Why are the assets managed, and what outcomes should they support? | Stakeholder needs, principles, value and assurance | Strategic direction, decision criteria and expected outcomes |
| System Model | Tactical and governance | How will asset management be organized, controlled and improved? | Policy, objectives, roles, plans, information and performance evaluation | SAMP, asset management plans, governance controls and performance information |
| Capability Delivery Model | Operational | How will the required capability be acquired, operated, maintained and improved? | Demand, engineering, configuration, acquisition, operations and maintenance | Delivered capability, work plans, lifecycle activities and performance feedback |
The three models covered here were developed by the Asset Management Council for the management of physical assets. They should not be confused with financial asset allocation models, asset data models or software data structures. Their purpose is to explain how organizational needs become coordinated asset management decisions and actions.
The pyramid illustrates the relationship between the models rather than a rigid organizational hierarchy. Strategic decisions shape the management system, tactical controls guide delivery, and operational evidence feeds back into planning and improvement.
The Asset Management Concept Model
The Asset Management Concept Model describes the basis of successful asset management. It starts with the organization and its stakeholders, then connects their needs with principles, decision criteria and a recurring improvement cycle. Its role is to establish what the organization expects from its assets before policies, plans and operational processes are developed.
Stakeholder Needs and Decision Criteria
Stakeholders influence all three asset management models because their needs define the value that assets are expected to support. Relevant internal and external stakeholders may include:
- Asset owners and senior decision-makers
- Operators and maintenance teams
- Finance, procurement, technology and support functions
- Regulators and public authorities
- Contractors, suppliers, customers and communities
Their requirements can cover safety, service quality, output volume, financial performance, environmental impact, legal obligations, community expectations and acceptable risk. These needs should be translated into clear criteria that can be applied consistently when the organization evaluates investments, maintenance priorities, risk treatments and changes to asset capability.
The Plan-Do-Check-Act Cycle
The Concept Model uses the Plan-Do-Check-Act cycle to connect intent with action and feedback. The cycle keeps asset management responsive when stakeholder needs, operating conditions, asset performance or organizational priorities change.
- Plan – Identify the need for change, define the intended outcome, assess constraints and establish the resources, responsibilities and methods required.
- Do – Implement the plan, coordinate the work and retain the information needed to understand what was done and why.
- Check – Compare actual performance with objectives, decision criteria and stakeholder requirements.
- Act – Address deviations, improve the method, update assumptions and begin another cycle when further change is required.
PDCA is not limited to maintenance activity. It can be applied to policy, planning, investment decisions, data quality, asset performance, risk controls and the asset management system itself.
Principles and Outcomes Behind the Concept Model
The Asset Management Council’s AMBoK describes four principles associated with its asset management framework:
- Output Focus – Assets are managed to deliver defined and measurable outputs that support enterprise objectives.
- Capabilities – Value depends on what assets, people, processes and supporting systems can achieve together.
- Level Assurance – Decision-makers need confidence that assets are likely to deliver the required outcomes within accepted levels of risk.
- Learning Organisation – Leadership, culture and employee involvement allow the organization to learn from performance and improve its relationship with assets.
ISO 55000:2024 uses different terminology from the older diagram. It identifies value, alignment and leadership as asset management principles, while assurance, adaptability and sustainability are outcomes of effective asset management. Although the two frameworks are related, they are not the same classification.
Outputs of the Concept Model
The Concept Model does not produce one mandatory document. It establishes the inputs and decision logic that the other models need. Typical outputs include clarified stakeholder requirements, intended asset management outcomes, value and risk criteria, strategic priorities and an agreed basis for evaluating whether asset-related decisions support organizational objectives.
The Asset Management System Model
The Asset Management System Model explains how an organization establishes the governance, objectives, processes, information and controls needed to manage assets consistently. It converts strategic intent into a management system that coordinates responsibilities across leadership, asset management teams, operational functions and external service providers.
Core Elements of the Asset Management System
ISO 55001:2024 specifies requirements for establishing, implementing, maintaining and improving an asset management system. Its main management system clauses follow seven connected areas:
- Context of the organization
- Leadership
- Planning
- Support
- Operation
- Performance evaluation
- Improvement
The 2024 edition adds stronger and more explicit requirements for asset management decision-making and value, the Strategic Asset Management Plan, risk and opportunity, data and information, organizational knowledge, lifecycle operations and predictive action. These additions reinforce the connection between strategic objectives and operational decisions.
Leadership, Policy and Asset Management Objectives
Top management sets the direction of the asset management system and makes sure it supports the organization’s wider purpose. Leadership responsibilities include establishing the asset management policy, aligning asset management objectives with organizational objectives, assigning responsibilities, providing resources and supporting a culture in which asset-related decisions are understood across functions.
Asset management objectives should be specific enough to guide planning and performance evaluation. Depending on the organization, they may address service availability, reliability, safety, lifecycle cost, environmental outcomes, compliance, capacity, asset condition or customer experience. Objectives also need resources, timescales, ownership and a method for evaluating results.
The SAMP and Asset Management Plans
The Strategic Asset Management Plan, commonly called the SAMP, is a central planning artifact in ISO 55001:2024. It connects organizational objectives with asset management objectives and describes the management system, capabilities and planning approach needed to achieve them. Its planning horizon should be long enough to reflect relevant lifecycle consequences rather than only the next annual budget cycle.
Asset management plans translate that strategic direction into activities for an asset, asset class, asset system or portfolio. They normally define the work, resources and timing needed to achieve asset management objectives. The relationship should remain visible: organizational objectives inform the SAMP, and the SAMP guides the development and coordination of asset management plans.
Information, KPIs and Decision-Making
Asset management decisions need an agreed framework. Decision criteria should reflect value, risk, opportunity, performance, cost, stakeholder requirements and lifecycle consequences. The appropriate method can range from a routine rule to a multi-criteria investment assessment, but the criteria and authority should be clear before alternatives are compared.
Data supports decisions only when it is converted into usable information and interpreted with relevant knowledge. The organization therefore needs to determine what data is required, how it will be governed, how quality will be evaluated and how information will remain available to the people making decisions.
Key Result Areas identify the areas where results are critical to the organization. Key Performance Indicators measure selected aspects of performance within those areas. A useful KPI is connected to an objective and a decision. A large collection of measures with no threshold, owner or planned response creates reporting activity without improving asset management.
Risk, Roles, Competence and Process Management
The System Model depends on more than policies and plans. It also requires the organizational capability to apply them. Four areas are closely connected:
- Risk and opportunity management – Decisions consider uncertainty, potential consequences and opportunities to improve value.
- Organizational roles – Responsibilities and decision authority are defined across asset ownership, asset management and service delivery.
- Competence and involvement – People have the knowledge, skills, awareness and working relationships required to perform their roles.
- Process management – Repeatable processes coordinate work, information and controls across functions and suppliers.
Weakness in one area affects the others. For example, a well-designed investment process can still produce poor results when decision authority is unclear, asset information is unreliable or operational teams are not involved in defining requirements.
Monitoring, Internal Audit and Management Review
Performance evaluation provides evidence about whether the asset management system and its processes are achieving their intended results. The organization determines what will be monitored and measured, which methods will produce valid results, when monitoring will occur and when the results will be analyzed and evaluated.
ISO management system requirements do not prescribe a universal two-year internal audit cycle. Internal audits are conducted at planned intervals through an audit program that defines frequency, methods, responsibilities, scope and reporting. The program should consider the importance of the processes and the results of previous audits. Top management also reviews the system at planned intervals to confirm its continuing suitability, adequacy and effectiveness.
Documents and Outputs of the System Model
The exact document structure depends on the size and complexity of the organization. Common outputs include:
- Stakeholder requirements and asset management decision criteria
- Asset management policy
- Strategic Asset Management Plan
- Asset management objectives and plans
- Role, competence and communication requirements
- Data, information and knowledge requirements
- Performance measures, audit evidence and management review results
The System Model Within the Wider Organization
The asset management system operates within the organization’s broader management system. Its objectives and controls need to align with safety, environmental, quality, financial, risk, information technology and human resource systems. Integration prevents functions from optimizing one outcome while creating avoidable cost, risk or performance problems elsewhere.
The Capability Delivery Model
The Capability Delivery Model is the operational layer of the three asset management models. It presents the processes used to define, acquire, operate, maintain and improve the capabilities required by the organization. The Asset Management Council groups these processes into six disciplines: Demand Management, Systems Engineering, Configuration Management, Acquisitions, Operations and Maintenance, and Continuous Improvement.
Demand Management
Demand Management identifies the outputs and capabilities that the organization will need. It considers stakeholder demand, service requirements, forecast workload, capacity, timing, constraints and the capability already available. The result is a clearer basis for deciding what assets or services are required and when investment or change should occur.
Effective demand management also tests whether the requirement should be met by a new asset. Changes to operating methods, service levels, scheduling, technology or externally provided services may satisfy the need with a different cost and risk profile.
Systems Engineering
Systems Engineering converts stakeholder and user requirements into a solution that can be designed, built, verified and operated. The Systems Engineering V Model shows the relationship between definition on the left side and integration, verification and validation on the right.
- Definition and decomposition – Operational needs are translated into system, subsystem and component requirements, followed by detailed design.
- Implementation – Hardware, software, infrastructure or other solution components are created, configured or acquired.
- Integration and verification – Components and subsystems are assembled and checked against their specified requirements.
- System validation – The completed solution is evaluated against the original operational need and stakeholder expectations.
Systems Engineering supports lifecycle value by considering how design decisions affect capital expenditure, operating cost, maintenance, reliability, safety, supportability and future change.
Configuration Management
Configuration Management maintains an accurate understanding of what the asset or system is, how it should be configured and how it has changed. Relevant information may include asset specifications, approved baselines, component relationships, software versions, change records, maintenance history and performance records.
Core configuration activities include identification, baseline control, change evaluation, version control and status accounting. Together they create traceability between requirements, design, the installed asset and its current operating state. Without this traceability, maintenance teams can work from outdated information and decision-makers can compare options against an inaccurate asset baseline.
Capability Acquisition
Capability Acquisition obtains the assets, technologies, processes or services required to meet the defined need. Acquisition can involve purchase, leasing, internal development, construction, partnership or an externally provided service. The decision should assess more than the initial purchase price.
A fit-for-purpose acquisition considers expected outputs, lifecycle cost, risk, maintainability, support requirements, interoperability, data needs, disposal and the organization’s capacity to operate the capability. CAPEX and OPEX should be evaluated together so that a lower upfront cost does not create disproportionate operating or maintenance expenditure later.
Operations and Maintenance
Operations and Maintenance use the acquired capability to deliver the required service while preserving asset performance, safety and value. Business needs shape the engineering design and maintenance requirements. Those requirements inform the maintenance plan, task definitions, schedules, resource needs and work orders.
The equipment register and configuration information support planning and control. Failures, inspections, condition data and completed work provide feedback to maintenance planning and engineering. This feedback loop allows the organization to change tasks, intervals, spares, design or operating practices when evidence shows that the current approach is not delivering the intended result.
- Preventive maintenance – Planned work intended to detect or reduce deterioration through condition monitoring, scheduled activity and functional testing.
- Corrective maintenance – Work that restores function after a failure or defect, including immediate repair, planned repair and renewal.
- Statutory and regulatory maintenance – Inspections, tests and interventions required to meet applicable legal or regulatory obligations.
- Resource and work planning – Coordination of labor, contractors, spare parts, tools, access, budgets and operational windows.
Improvement and Performance Feedback
The Asset Management Council names the sixth Capability Delivery discipline Continuous Improvement. ISO management system terminology uses Continual Improvement to describe recurring improvement over time. In practice, both emphasize the need to measure results, analyze causes, act on evidence and review whether the change improved performance.
- Measure – Collect relevant information about asset, process and service performance.
- Analyze – Identify trends, failure mechanisms, constraints and opportunities.
- Act – Change maintenance, design, operating methods, resources or decision criteria.
- Review – Confirm whether the action improved the intended outcome and whether further change is required.
Methods such as Failure Mode, Effects and Criticality Analysis, Reliability-Centered Maintenance, Level of Repair Analysis, condition monitoring and maintenance task analysis can support this discipline. The method should match the decision and the available evidence rather than being applied as a standalone exercise.
Capability Delivery Outputs and Artifacts
The Capability Delivery Model produces two distinct categories of outputs: management documents and funded delivery requirements.
| Output type | Examples | Purpose |
|---|---|---|
| Engineering and configuration plans | Systems Engineering Management Plan, Configuration Management Plan | Define how requirements, design, verification, baselines and change will be controlled |
| Operations and support plans | Operations Management Plan, Integrated Logistics Support Plan, maintenance plans | Coordinate operation, maintenance, resources, spares and supportability |
| Specialist management plans | Safety, environmental and heritage management plans | Control discipline-specific objectives, risks and obligations |
| Funding requirements | Capital expenditure and operating expenditure | Provide the resources needed to acquire, operate, maintain, improve and renew capability |
How the Three Asset Management Models Work Together
The three asset management models are most useful when treated as one connected decision system. The Concept Model defines intent, the System Model organizes and controls the work, and the Capability Delivery Model performs the lifecycle activities that produce evidence and results.
| Stage | Model | Main input | Decision or activity | Main output |
|---|---|---|---|---|
| 1 | Concept Model | Organizational purpose and stakeholder needs | Define expected value, outputs, risk tolerance and decision principles | Strategic direction and decision criteria |
| 2 | System Model | Strategic direction and organizational objectives | Establish policy, objectives, roles, plans, information and controls | Governed asset management system and resourced plans |
| 3 | Capability Delivery Model | Asset management objectives and plans | Define demand, engineer, acquire, operate, maintain and improve capability | Asset and service performance |
| 4 | Feedback to all models | Performance, cost, risk, condition and stakeholder evidence | Evaluate results and update assumptions, plans or operational methods | Better decisions and continual improvement |
This sequence is not one-way. Operational evidence can change an asset management plan, expose a weakness in the management system or show that stakeholder expectations and strategic assumptions need to be reviewed. A functioning model therefore includes feedback from assets and service delivery back to tactical and strategic decision-making.
Asset Management Models in Practice
Consider a facilities organization responsible for a large portfolio of buildings. Stakeholders expect safe facilities, reliable services, regulatory compliance and controlled operating costs. The three models divide that challenge into connected decisions.
| Model | Facilities example |
|---|---|
| Concept Model | Define stakeholder outcomes, service expectations, safety priorities, value criteria and acceptable risk. |
| System Model | Establish policy, responsibilities, asset management objectives, SAMP, building-level plans, data requirements, KPIs and review processes. |
| Capability Delivery Model | Forecast demand, specify systems, plan renewals, acquire equipment, create maintenance programs, issue work orders and analyze performance feedback. |
If condition data shows repeated failures in a building system, the response does not stop with a repair. The operational team may adjust the maintenance task, engineering may review the design, planners may update renewal timing, and leadership may reconsider investment criteria or risk tolerance. This is how the three models turn operational data into coordinated maintenance, engineering, planning and investment decisions.
Common Gaps When Applying Asset Management Models
- Treating the models as separate frameworks – Strategy, governance and delivery become disconnected, so operational evidence does not improve future decisions.
- Reducing asset management to maintenance – Maintenance is one delivery discipline, while asset management also covers stakeholder value, objectives, risk, planning, acquisition, data and lifecycle decisions.
- Setting asset objectives without a line of sight – Teams can meet local targets while failing to support organizational objectives.
- Collecting data without decision requirements – More data increases effort but not value when no decision, threshold or action depends on it.
- Unclear decision authority – Investment, maintenance and risk decisions slow down or are repeated when roles and escalation routes are not defined.
- Optimizing initial cost – A low acquisition price can create higher lifecycle cost, reduced supportability or additional operational risk.
- Weak performance feedback – Plans remain unchanged even when asset condition, failures, service demand or stakeholder expectations have moved.
Frequently Asked Questions
What are the three main asset management models?
In the Asset Management Council framework, the three models are the Asset Management Concept Model, the Asset Management System Model and the Capability Delivery Model. They address strategic direction, governance and tactical control, and operational capability delivery.
What is the difference between an asset management model and an asset management system?
A model is a representation used to explain relationships and decision logic. An asset management system is the set of interrelated elements an organization uses to establish policy, objectives and processes for asset management. The System Model helps explain how that management system is structured.
Is the Capability Delivery Model an asset management operating model?
It can inform an asset management operating model because it describes operational disciplines and their relationships. The terms are not exact synonyms. An organization’s operating model can also include its specific structure, sourcing approach, technology, governance and service delivery arrangements.
Are asset management models the same as asset management types?
No. The three models explain how physical asset management works across strategic, tactical and operational levels. Asset management types can refer to different asset classes, management strategies or financial investment services, depending on the context.
Are asset management models the same as asset data models?
No. An asset data model defines how asset information, attributes and relationships are structured in a system. The Concept, System and Capability Delivery Models explain organizational decision-making and lifecycle management rather than database architecture.
How does ISO 55001 relate to the Asset Management System Model?
ISO 55001:2024 specifies requirements for an asset management system. The Asset Management System Model is a visual framework that helps explain how elements such as leadership, objectives, decision-making, information, risk, roles and performance improvement interrelate. The model supports understanding, while ISO 55001 provides requirements.
Conclusion
The Concept Model, System Model and Capability Delivery Model describe three connected layers of asset management. The Concept Model establishes purpose and decision principles. The System Model creates the governance, plans, information and controls needed to manage assets consistently. The Capability Delivery Model converts those plans into engineered, acquired, operated and maintained capability.
Together, these asset management models create a line of sight from stakeholder needs to operational performance. Their value comes from the feedback between the layers, where asset evidence improves plans, management controls and future strategic decisions.
Sources
- Asset Management Council – AMBoK Basics
- Asset Management Council – In-Depth Explanations of AM Models
- ISO 55000:2024 – Asset management – Vocabulary, overview and principles
- ISO 55001:2024 – Asset management – Asset management system – Requirements
- ISO/TC 251 – ISO 55000:2024 Updated Overview of Asset Management
- ISO/TC 251 – ISO 55001:2024 Updated Guidance on Asset Management System Requirements
- Asset Management Council – ISO 55001:2024 Companion Guide – Strategic Asset Management Plan
- ISO/IEC Harmonized Structure for Management System Standards
- Wikimedia Commons – Systems Engineering V Diagram
- The Asset Management College – The Asset Management Models
- The Asset Management College – Asset Management Concept Model
- The Asset Management College – Asset Management System Model
- The Asset Management College – Maintenance Management Model
Take the next step towards operational excellence
From preventive maintenance to real-time asset visibility, see how Asset Insider helps your organization achieve operational excellence.
