![Sample our Economics, Finance,Business & Industry journals, sign in here to start your access, latest two full volumes FREE to you for 14 days]({"type":"image" , "src" : "/sda/5931/TOC-Subject-Sample-2021-Economics-Finance-Business-Industry.jpg"})
Abstract
E-maintenance is an emerging concept generally defined as ‘a maintenance management concept whereby assets are monitored and managed over the Internet’. Nevertheless a lot of complementary definitions exist in which are introduced the principles of collaboration, knowledge, intelligence, etc. There is no consensus and the number of references and work is hugeFootnote1 without a unique repository to ensure consistency. Consequently the aim of this research and review note is to define more precisely the emerging concept of e-maintenance and then to propose and discuss a conceptual e-maintenance framework based on a Zachman framework. Such a framework can facilitate a widespread understanding of e-maintenance and provide useful guidance for supporting e-maintenance deployment through services, processes, organisation and infrastructure. It should serve as a reference for an inventory on all the work related to this topic.
Acknowledgements
E-maintenance is a research topic we initiated approximately six years ago on the basis of previous research on maintenance engineering. This evolution is the consequence of reading of publications issued mainly from the ‘intelligent maintenance system’ community (led by J. Lee). This evolution has taken shape on the basis of several exchanges made (a) during meetings or scientific events at (French) National level (CNRS-MACOD, PENTOM), at international level (intelligent manufacturing system, intelligent maintenance system, IFAC-TC4.4., IFAC-TC5.1, CIRP TC A), (b) during European projects in which we were involved (REMAFEX, EIAM-IPE, IMS-NOE, DYNAMITE, DEPEN-IMPRO) and (c) during collaborations we had with industrial people (PREDICT, ATOS, EDF, DCN). Thus the authors would like to thank all of these groups, collaborations, projects who contributed to the emergence of these thoughts on e-maintenance.
Notes
Notes
1. This paper is based on a first e-maintenance overview developed in a survey entitled ‘On the concept of e-maintenance. Review and current research’ and accepted in the Reliability Engineering and System Safety journal (Muller et al. Citation2008b).
3. Proceedings of the NFS Workshop on ‘Tether-free Technologies for e-manufacturing, e maintenance and e-service’ organised by NFS I/UCR Centre for Intelligent Maintenance Systems at University of Wisconsin, 1–2 October 2001. Report of the Ideal Factory Session on ‘New model and technologies to select and improve a cost-effective condition-based maintenance policy practically’, by B. Iung, B. Al Najjar, A. Airnaiz, IMS-FORUM2004-Como, Italy, 19 May 2004.
7. An integrated set of elements that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services, and other support elements.
8. Another way will be to use the Model Driven Architecture approach based on 4 levels of models (CIM, PIM, PSM models).
10. See white paper ‘MEGA and Zachman framework’.
11. The value chain is described by a sequence of transformation activities
12. An objective is a goal that a company/organization wants to achieve, or is the target set by a business process or an operation. An objective allows one to highlight the features in a business process that require improvement. An objective can be quantitative (directly measurable) or qualitative.
13. EIF (European Interoperability Framework) proposes to consider three aspects of the interoperability: Semantic, organisational and technical.
15. ‘The purpose of these standards is to provide formal models of diagnostic information to ensure unambiguous access to an understanding of the information supporting system test and diagnosis’ (IEEE Std 1232-2002).
16. A procedure describes the method of implementing all or part of the business process required to make a product or handle a flow. A procedure is represented by a sequence of operations triggered by the receipt of a message. An operation is a step in a procedure, executed by an org-unit within the context of an activity.
17. An org-unit represents a person or group of persons participating in the business processes or information system of the enterprise. An org-unit can be internal or external to the enterprise. An org-unit can send and receive messages. It is located on a site; it can intervene in a business process or a procedure. It can draw on resources to handle an activity. It accesses databases to carry out operations using an application. It can be specialised.
18. In the workflow is also introduced the concept of role that is the requester of a service, or it can represent a sub-contractor carrying out processing outside the service. A role is an integral part of the object that it describes, and is not reusable. It can subsequently be assigned to an org-unit internal or external to the organisation or to an IT component.
20. A (software) application is available for a given org-unit or is used to execute a business process or procedure. An application helps performing an operation.
21. A service is a component of an application that is available to the end user of that application. A component is an element in the implemented system; it can be a software package, a program, a code unit, or a physical element such as a working document.
22. CASIP (http://www.predict.fr); ENIGMA (http://www.enigma.com); ICAS-AME (http://www.esrgtech.com/Documentation/DODSymposium_GreatIdeas.pdf); IMS/D2B™ http://www.imscenter.net/, Remote Data Sentinel http://www.technilog.com/en/produits/rds.htm; QUESTRA http://www.questra.com/; DEXTER http://www.macsea.com/
