Body of knowledge

Asset management, applied to data centers

Asset management is the coordinated activity of an organisation to realise value from its assets. In a data center, that value is a service that does not stop — delivered at a cost, risk and carbon position the business can sustain.

This page sets out the framework as ISO 55000 and the IAM define it, and then shows what each part means for the equipment in your electrical and mechanical plant rooms. Nothing here is proprietary; the discipline is public. The engineering is in applying it accurately to a facility that cannot be switched off.

Request an assessment

Asset management, applied to data centers

What asset management actually is

ISO 55000 defines an asset as an item, thing or entity that has potential or actual value to an organisation, and asset management as the coordinated activity of an organisation to realise value from assets. Value is not the same as condition, and not the same as uptime: it is the balance of performance, cost, risk and opportunity across the whole life of the asset.

Four fundamentals underpin the discipline: value (assets exist to deliver a purpose, not for their own sake), alignment (technical decisions must translate organisational objectives), leadership (asset management works only where authority and accountability are real), and assurance (the assets, and the system managing them, must be demonstrably fit for purpose).

Asset management is therefore not maintenance with a broader budget. Maintenance is one of the levers. Design, procurement, operation, data, spares, competency, renewal and disposal are the others.

Line of sight: from business objectives to a breaker

The framework's central idea is line of sight. Organisational objectives produce an asset-management policy; the policy produces the Strategic Asset Management Plan (SAMP); the SAMP produces asset-management objectives; those objectives produce Asset Management Plans; the plans produce work — inspections, tasks, projects, replacements.

The test of line of sight is that it works in reverse. Anyone should be able to take a scheduled task and trace it upward to the objective it protects. Where that trace fails, the task is either unnecessary or the objective is not real.

Organisational objectives: Service commitments, regulatory obligations, cost and carbon targets.
Asset-management policy: The principles and constraints leadership commits to.
SAMP: How the asset portfolio will be managed to meet those objectives.
Asset Management Plans: What will be done, to which assets, when, by whom, at what cost.
Work: Tasks, inspections, monitoring, projects, renewals and their evidence.

The asset lifecycle

Asset management spans acquisition, utilisation, maintenance and renewal or disposal. Most of an asset's cost and nearly all of its reliability are committed in the earliest phase, when specification, layout, isolation and maintainability are decided — and when the operating organisation is usually least involved.

Whole-life thinking means the decision to buy is a decision to maintain, to stock spares, to train people, to hold data and eventually to replace.

The ISO 55000 family, plainly

ISO 55000 provides the overview, principles and terminology. ISO 55001 sets the requirements for an asset-management system — the auditable clauses. ISO 55002 gives guidance on applying 55001. Certification, where an organisation seeks it, is against 55001.

An asset-management system is not software. It is the set of interrelated elements — policy, objectives, plans, processes, information, roles and controls — through which the organisation directs and controls asset activity.

The three parts of the ISO 55000 family

ISO 55000

Overview and terms

Purpose: Defines asset management, value, alignment, assurance and leadership.
Use it for: Shared vocabulary across engineering, finance and operations.
Auditable: No

ISO 55001

Requirements

Purpose: States what a management system must contain, clause by clause.
Use it for: Gap assessment, internal audit, certification if it is wanted.
Auditable: Yes

ISO 55002

Guidance

Purpose: Explains how the requirements may be applied, proportionate to risk and scale.
Use it for: Designing a system that fits one facility rather than a template.
Auditable: No

Only ISO 55001 is auditable. The other two explain and advise.

Context (Cl. 4): Stakeholders, scope of the asset-management system, and the SAMP.
Leadership (Cl. 5): Policy, authority, accountability and organisational roles.
Planning (Cl. 6): Risks and opportunities, asset-management objectives and the plans to achieve them.
Support (Cl. 7): Resources, competence, awareness, communication and — heavily — asset information requirements.
Operation (Cl. 8): Operational planning and control, management of change, outsourcing.
Evaluation (Cl. 9): Monitoring, measurement, internal audit and management review.
Improvement (Cl. 10): Nonconformity, corrective action, preventive action and continual improvement.

The IAM subject landscape

The Institute of Asset Management's conceptual model groups the discipline into six subject areas: strategy and planning; asset-management decision-making; lifecycle delivery; asset information; organisation and people; and risk and review. It is a useful map of the whole discipline, wider than the 55001 clauses, and it is the fastest way to see which parts of an organisation are strong and which are absent.

In our experience with data-center operators, lifecycle delivery is usually competent, asset information is usually weak, and asset-management decision-making — the criteria by which capital is allocated between competing assets — is usually undocumented.

Risk and criticality as the allocation rule

Asset management is explicitly risk-based. Criticality — the consequence of failure, considered in the context of the whole service chain — is the mechanism that decides where analysis, monitoring, spares and capital go.

Criticality is not the same as size, cost or how much noise an asset makes when it fails. It is a function of what stops, for how long, and what that costs in service, safety, compliance and reputation.

Asset information and ISO 14224

Decisions cannot be better than the data underneath them. ISO 55001 treats asset information as a managed asset in its own right: requirements defined, quality controlled, and specified by the decisions it must support rather than by what a system happens to capture.

ISO 14224 provides the structure for reliability and maintenance data — equipment boundaries, taxonomy levels, failure modes, failure causes, detection methods and maintenance activity coding. Adopting its discipline is what makes failure history comparable between sites and over time, and what makes any later analytics or reliability modelling possible.

Taxonomy: Consistent hierarchy from facility to maintainable item.
Boundaries: An agreed definition of where an asset starts and stops.
Failure modes and causes: Coded consistently so patterns can be counted.
Detection method: How the failure was found: operator, alarm, inspection, condition monitoring.
Downtime and repair time: Recorded separately so restoration capability can be measured.

Maturity: knowing which problem you are solving

Organisations progress from innocent (activity is reactive and undocumented) through aware, developing and competent to excellent (asset decisions are optimised and continuously improved). Attempting an advanced technique from a low maturity base is the most common way asset-management programmes stall.

Predictive analytics on top of an unreliable asset register produces confident, wrong answers. Hierarchy and criticality come first, always.

Where asset-management programmes fail

The recurring patterns are not technical. A SAMP written to satisfy an audit and never used to allocate money. A criticality workshop whose output never changes a maintenance frequency. A CMMS implementation treated as an IT project. Improvement actions with no owner. And measurement built entirely on lagging indicators, which cannot warn anybody about anything.

Apply the framework to your facility

An assessment establishes where your asset-management practice actually sits, which gaps carry service risk, and what the first 90 days of improvement should contain.

Request an assessment See the methods