Asset management — Guidance on the management of data assets
ISO 55013 gives guidance on managing data so that it supports asset-management and organizational objectives.
What the authority record establishes
ISO 55013 gives guidance on managing data so that it supports asset-management and organizational objectives.
Voluntary guidance
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
It makes asset identity, provenance, quality, ownership, access, retention, and decision fitness material requirements in CMMS, EAM, APM, and analytics programs.
Affected operating stages
- Data Strategy
- Ownership
- Quality
- Access
- Use
- Retention
- Improvement
Capabilities to examine
Asset Registry And Hierarchy
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset registry and hierarchy.
Failure Codes And Maintenance History
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for failure codes and maintenance history.
Asset Health And Performance Analytics
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset health and performance analytics.
ERP MES SCADA And Historian Integration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP MES SCADA and historian integration.
Document Control And Audit Trails
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for document control and audit trails.
API And Data Export
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for API and data export.
Maintenance Knowledge And Assisted Triage
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for maintenance knowledge and assisted triage.
Affected buyer audiences
- asset data owners
- maintenance systems
- IT and OT
- assurance teams
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
The standard does not appraise financial value of data assets or validate the completeness or fitness of a particular system's data.