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 organizations 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 article with existing literature will ease the delivery of an asset register.

No abstract

The ability of a company to prioritize work orders is an essential part of managing work which in turn is vital when it comes to delivering maintenance services. The authors have drafted a tutorial paper that outlines a real‐world application of practices which determine asset criticality and work order prioritization. The paper initially provides a background on the estate of the featured facilities department. An approach is then provided to determine asset criticality across an asset register which factors in the importance of each site in relation to the overall mission of the estate. The final step is to use asset criticality, work urgency and a time factor to address work order prioritization. If a company wishes to adopt the approach in this paper but does not possess a Computerized Maintenance Management System (CMMS) with the required functionality, they could instead utilize a spreadsheet‐based approach incorporating data exports from their resident CMMS. While this paper features data from the facilities management industry, the approach is agnostic and can be implemented by maintenance departments regardless of the industry.