Development of a complementary framework for implementing asset register solutions

Lar English*, Akilu Yunusa-Kaltungo, Moray Kidd, Ashraf Labib

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

7 Downloads (Pure)

Abstract

A correctly compiled asset register within an Asset Information Management System (AIMS) provides the foundation for a successful asset data solution. The lack of correctly structured asset registers within organisations is acknowledged among research and communities of practice. A case study identified anomalies that emerge when using established standards, after which a comprehensive solution for hierarchies, naming conventions and attributes was offered. While standards such as BS ISO 1007 and ISO 14224 provide overarching solution principles, such provisions are not all-encompassing and exist across several sources, which makes the task of developing asset registers error-prone and laborious. Challenges associated with software applications were highlighted through combining personal industrial experience as well as consultations with the existing body of knowledge. Recommendations that enable successful deployment of AIMS, with emphasis on its accommodation of a reliable asset register were then proffered. Scalability was addressed which enables an asset register to expand. This study describes a novel and simplified approach embodied within a single document. Combining the prescriptions of this paper with existing literature will ease the delivery of an asset register.
Original languageEnglish
Article numbere12493
Number of pages17
JournalEngineering Reports
Volume4
Issue number6
Early online date21 Dec 2021
DOIs
Publication statusPublished - 1 Jun 2022

Keywords

  • asset data
  • asset resigster
  • asset management
  • asset hierarchy
  • configuration management
  • CMMS

Fingerprint

Dive into the research topics of 'Development of a complementary framework for implementing asset register solutions'. Together they form a unique fingerprint.

Cite this