E‐maintenance and information logistics: aspects of content format

Abstract

PurposeThe purpose of this paper is to describe aspects of content sharing within e‐maintenance, with a view to merging the two areas of maintenance and ICT in a content management perspective.Design/methodology/approachThe approach is an explorative literature study covering aspects of ICT. The analysis is founded on theories related to maintenance and maintenance support. The conclusions of the study are corroborated by experiences from earlier software development and testing.FindingsMost existing contributions to the e‐maintenance debate seem to suffer from too wide a gap between data processing and knowledge management. This tendency can be due to too great a focus on data collection, without any clear identification of the stakeholders' requirements. Hence, a mature e‐maintenance solution should focus on the enhancement of service‐oriented information logistics based on content sharing for an output‐based information strategy.Research limitations/implicationsThis study focuses on the needs of content format and transformation content, which includes data format, data structures and data type for objects that are relevant for the maintenance process. Hence, further research could include aspects of infrastructure and service architecture, which are on a higher level of an e‐maintenance solution.Practical implicationsThe paper contributes with knowledge that supports decisions about content format in the development of an e‐maintenance solution. This can in turn support a reduction of maintenance‐related hazards through the improved use of ICT.Originality/valueThis paper describes the importance of content management within the e‐maintenance approach. Hence, the paper has implications for both practitioners and researchers as described above.

No Fault Found events in maintenance engineering Part 1: Current trends, implications and organizational practices

“…References Fault diagnostics [1,2,3,6,7,8,9,10,11,12,13,14,15,16,17,18,19] System design [1,13,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32] Human factors [1,20,32,33,34,35,36,37] Data management [1,20,37,38,39] 1 [1,26] are review papers on the NFF.…”

Perancangan Sistem Informasi Perawatan Mesin Pada PT XYZ

“…Akan tetapi, risiko terbesar dari corrective maintenance adalah tingginya downtime dan penurunan level produksi yang tidak diharapkan (Bartz et al, 2014). Menurut Karim et al (2009), risiko tersebut menjadikan perlunya pengembangan metode perencanaan perawatan lain agar bisa mengiringi kompleksitas evolusi teknologi peralatan. Kondisi tersebut mendorong munculnya berbagai konsep manajemen perawatan pada era setelahnya.…”

No Fault Found events in maintenance engineering Part 2: Root causes, technical developments and future research

“…Engineers have recently empathized that there is need for 'on-field experience' to be shared within a troubleshooting workflow repository [21]. Aspects of content sharing (such as e-maintenance [56]) can be beneficial for other maintenance personnel who will then be able to identify the cause of a problem on their first attempt, whenever (or wherever) it next occurs. Furthermore, the captured knowledge, over time, can assist designers in improving the reliability of the equipment.…”