資產管理在數據中心的應用

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.

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.

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.

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.

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.

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.

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.

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.

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.