1. C. Mugnier, D. Lafarge, C. Perolini, R. Pilon, J. Ruiz-Cabezas
Corrective Maintenance Business Process Diagram in BPMN Notation – TO-BE
C. Mugnier, D. Lafarge, C. Perolini, R. Pilon, J. Ruiz-Cabezas

3. Harmonising maintenance processes methodology at CERN
C. Mugnier, D. Lafarge, G. Perinic, C. Perolini, R. Pilon, J. Ruiz-Cabezas 4
Methodology applied: HERMES project management method & business process theory
Abstract:
The analysis of the maintenance task in CERN’s technical sector within the framework of the recently launched Maintenance Management Project (MMP) has revealed a need for harmonisation of maintenance workflows across the different equipment groups.
This poster outlines the different steps that have been performed by the the MMP and the Maintenance Framework Implementation Office (MFIO) starting from the choice of the graphical and literal process description method and the ‘AS-IS’ capturing process that has been carried out with the different equipment groups to establish a library of workflows. It will then explain the steps towards harmonized “TO-BE” processes which comprise the agreement on common definitions and the elaboration of harmonised roles as well as the application of coherent configurations of all concerned systems including the layout database, the drawing repository, the engineering documentation management system (EDMS) and the computerized maintenance management system (CMMS) which compose together CERN’s maintenance management framework.
AS-IS Analysis: Documentation of the workflows as they are practiced in the different technical equipment groups.
Intentional
Organisational
Logics level
Physical level
System design
AS-IS analysis
AS-IS model
TO-BE model
Example 1 - AS-IS of Controls Group
Example 2 - AS-IS of Heavy Handling Group
Example 3 - AS-IS of Cooling and Ventilation Group
TO-BE Design: Elaboration of a harmonised workflow that incorporates the needs of the different groups and promotes the best practices that have been identified in the AS-IS processes.
1,2,7,8
* Steps concern the machine level and are not considered here. 5 6
PRIMARY TARGET
SPECIFICATION BASIS FOR THE DEVELOPMENT OF HARMONISED SOFTWARE MODULES AND STANDARDISED CONFIGURATION OF THE CMMS
The TO-BE process diagrams are the fundamental input for the development of the software components that shall assist the maintenance staff in setting up maintenance and in the daily maintenance management tasks.
At present the MMP and MFIO are involved in the development of software tools for:
naming,
labelling,
metadata collection (for registering existing components)
documentation management and
a CMMS user interface (EAM-light)
Corrective Maintenance Business Process Diagram in BPMN Notation – TO-BE 3
Pre-Analysis Phase: Identification and documentation of the user’s needs across CERN’s four technical departments
Departments :
BEams, ENgineering, TEchnology and General Services 9
CONCEPT
Summary of concepts 8 7 6 5 4 3 2 1
Common key-definitions
A common naming/coding reference
Description of maintenance processes in BPMN
The issue concept
The maintenance information concept
The metadata and search concept
Criticality ranking system oriented to the operation/equipment level
The roles concept
The Maintenance Implementation Office concept
BPMN: Business Process Model and Notation is a graphical representation for specifying business processes in a business process model. It’s main elements are:
Events
– i.e. what happens
Activities
– i.e. what is done
Connections
Pools and lanes
– to organise entities and roles
ROLES
Implementation of harmonised asset and maintenance management roles in all equipment groups.
Examples:
GCO - Group Coding Officer GMIO - Group Maintenance Information Officer
GQMO - Group Quality Methods Officer
GSPO - Group Spare Part Officer
Benefice:
new methods, procedures, tools and role specific training can be deployed efficiently
transversal networking can be steered
HARMONISED KEY-DEFINITIONS
A glossary of asset and maintenance related terms is elaborated and deployed to daily language, documents, tools, training etc.
Example:
ISSUE: An issue is a non-physical entity that traces information collected and activities performed by operation and intervention teams to re-establish functions of an equipment or of a system (e.g. an accelerator).
Benefice:
operation and maintenance staff, asset and maintenance managers communicate more efficiently
facilitates the harmonisation of tools, documentation, etc.
INTERFACE MANAGEMENT
Identification and documentation of interfaces between entities (various services, contractors, suppliers,…) as well as for the man machine interfaces is an important step towards coherent data management.
Benefice:
clarification of input, output and responsibilities for all stakeholders
identification and elimination of double data production
improvement of the quality of the information handed over at the interfaces
identification of potential sources of delay (i.e. identification of improvement potentials)
identification of automation needs
BUSINESS PROCESS LIBRARY
With the elaboration of a rising number of TO-BE processes, a library that covers all aspects of the maintenance task is being established for the participating departments.
Benefice:
increased process transparency (between services having similar functions and between service provider and their clients)
important resource for new process implementations
a step towards a better understanding of CERN’s overall business process
constantly increasing recognition of the impact of the « business process » on the maintenance efficiency
Some outcomes from the harmonisation process