Maintenance Management Project3rd Status Report

Pierre Bonnal DG-DIChristophe Delamare GS-ASEMarine Gourber-Pace BE-CO

Damien Lafarge EN-HEChristophe Mugnier TE-EPC

Goran Perinić TE-CRGRegis Pilon TE-EPCIngo Ruehl EN-HE

Eric van Uytvinck EN-ELDavid Widegren GS-ASE

Zornitsa Zaharieva BE-CO

Maintenance Management Project

3rd Status Report17th October 2013

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

2

The MMP project

MMP RoadmapFeb 2012

MMP Concept Report

May 2012

Maintenance workshop Nov 2011

Methods office implementation

July 2012

CMMWGCMMSB

Aug 2010

Audi

t of t

he o

pera

tion

of L

HC

and

its in

ject

ors”

audi

t in

4 gr

oups

(Bal

ticBe

rg)

inte

rnal

TE

audi

t (C.

Mug

nier

)

project management method

Data mngmt.

Parts,assts.

Interv.workfl.

Conclusion – MMP Status report 29.05.2013

• Coding / Issue / logbook / TREC / IMPACT / planβ context adds a new dimension (and complexity) to the project

• Need of one central authority for QA CERN wide – QAWG?

• Resources ‘almost’ at a sustainable level but some ‘effort’ is still required

• Many phases at the same time …

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

6

News from the Maintenance Framework Implementation Office

Maintenance Management Project

3rd status report18th October 2013

Christophe Mugnier

https://edms.cern.ch/document/ Slide 7

MFIO activities Data Collection:

Objective Documentation Parts

Issue Management EIS

Observations

Contents

Slide 8

Data collection: Objective

Slide 9

EAM(Infor)

Layout-ServiceGS-ASEMFIO

Layout Service creates the layout with equipment

responsibles

EAM

EDMS

Naming-Service

Part MFIO-0002222 (MFIO code)

Classes, customs fields and

information are homogenised

Operational Documentation(Original and PDF files)

Parts and docs are collected in an

external data base .

Data collection: Objective

The layout is propagated and assets are created from parts

HCA…-001

HCA…-002

HCA…-003

HCA…-004

HCA…-001HCA…-002

HCA…-003

All files are stored in EDMS

HCQXXXXX

HCQXXXXX

HCQXXXXX

Formal codes are provided by Naming Service.

Part’s data are uploaded

in EAM

Docs are uploaded in

EDMS

Slide 10

Data collection: Docs

Slide 11

Distribution of documents

Documentation for the

maintenance and operational

activitiesDoc management

usersExternal systems

Homogenization, formatting

Doc collection: Strategy

Archives

Project Documentation

Objective: Constitute an operational

documentation

*Group Maintenance Information Officer

• A well defined perimeter • Documentation mainly dedicated to maintenance activities

• Specific treatmentDocuments and files are:• Formatted, identifiable• Stored in EDMS with predefined keywords

• Op. Doc. Management • GMIO* with specific IT tools is in charge of the

management• Docs and files are constantly updated, perennial,

available

Slide 12

• 1st : treatment of documentation in an external system• Collecting, sorting, cleaning, formatting of documents and files• Establishing the functional breakdown of the equipment (items, folders, assets)• Classification, metadata filling and storage of documents uniformly in DFS

Doc collection: Process

• Support provided by MFIO• A team of 2 experts to support and train the GMIO• A set of specific IT tools to treat documents• Methods and processes well defined for doc management

dfs

• 2nd : massive and automatic upload into EDMS:• Creation of empty EDMS documents • Insertion of the EDMS number into the PDF file (stamp)• Upload of metadata and files into the prepared EDMS documents EDMS

Slide 13

1) The functional breakdown is set-up in

DFS

2) EDMS functional breakdown is

automatically created from DFS

Doc collection Process: e.g. EN-HE Op. Documentation

Slide 14

• Activities carried out:• Creation of new documents and Sub documents EDMS trees, Link to Projects,

Items, and Asset Class with document utilities :

- EN/CV (Guillermo Peon) : 800 docs,

- EN/HE (Cathelijne Bal) : 2000 docs,

- EN/STI/TCD (Stephanos Athanasiadis) : 224 docs,

- TE/CRG (Sigrid Knoops and Maria del Pilar Herguedas) 1130 docs,

- TE/EPC (Ludovic Germain Bonne) : 632 docs,

- TE/MPE (Bruno Puccio) : 120 docs,

- TE/MSC (Philippe Canard) : 513 docs

- TE/MSC (Vittorio Parma): ~ 5000 documents to scan and record in EDMS.

- TE/VSC (Alexandre Sinturel) : 6 docs

= 5425 new docs(~ 2000 docs since June 2013)

and~ 6000 refurbishment of

existing docs

Doc collection: Status

MFIO Team EN-HE GMIOSlide 15

• TE-CRG and EN-HE experiment: in both cases:• After 2 months of strong support from MFIO*, the GMIOs*

became autonomous.• The GMIOs are satisfied of the efficient IT tools. ( >1000 doc per

day could be treated and recorded).• The GMIO continues autonomously.• The MFIO continues to support upon request.

Doc collection: Feedback

Time

MFIO support upon request

GMIO

MFIO decreasing support

2 Months• Short term actions:• MFIO promotes this approach for all groups:

• 3 groups are now autonomous: EN/HE, TE/CRG, TE/EPC• First contacts with : BE/BI, BE/CO, BE/RF; EN/CV, EN/STI; TE/ABT, TE/MPE, TE/MSC, TE/VSC• EN/EL, EN/MME have their own documentation system and further actions remain to be

defined. (doc transfer, merging, synchronisation).• MFIO is prepared to accompany groups provided that a GMIO was appointed.

*Maintenance Framework Implementation Office*GMIO: Group Maintenance Information Officer

Slide 16

• How to use original CCD drawings for maintenance activities?

Seemingly no workflow for the management of "as-built” CDD drawings for maintenance purposes exists.

• Consequence: Difficulty to link components with the “as-built” versions of the drawings• Need: Rules and means to link documents from both contexts• Action: PLMWG has been consulted, understands the need and will give us some

recommendations ( No date given)

Doc collection: Open issues

Slide 17

• Status• Informatics tools and systems are fully operational (capacity ~1000 doc./day)• 2 MFIO members are in charge of registering operation/maintenance documentation• Since January about 11000 documents of 7 groups were recorded and/or refurbished• Possibility to outsource the scanning : “Société d’insertion - Genève” • GMIO and equipment responsible are key roles, 3 GMIOs are now autonomous (TE-EPC,

TE-CRG, EN-HE)

Doc. Collection: summary

• Open issues• Link between CDD drawings and operation/maintenance documentation

• Next steps• Estimation: ~ 5000 operation/maintenance documents per group • 9 groups to be trained• Objective for end 2014: 2000 documents recorded for each group and all GMIOs trained

and working autonomously

Slide 18

Data collection: Parts

Slide 19

Part collection: StrategyObjective:

Constitute a global catalogue of parts across Departments

*Group Coding Officer*Group Part Officer

• Perimeter • BE/TE/EN global rules and codification, to allow a global view

across department and groups

• Specific treatment of data• Classes and customs fields are predefined by a panel of experts, and

validated• Collection process is unified and well defined (BPMN)• All records are validated (by automatic means or expert checking)

• Part Management • GCO* and GSPO* roles are essential to manage parts at group level• EAM provides functionalities and specific user interfaces to manage

stores and guarantees the part traceability.

BE EN TE

EAM(Infor)

Slide 20

• 1st : treatment of records in an external system• Predefining and formatting classes and custom fields

• Support provided by MFIO• A team of 2 people to support and train the Group Part Officer (GSPO)• A set of specific IT tools to define classes and custom fields and to record parts• Methods and processes well defined for part recording and store management

dfs

EAM(Infor)

Parts collection: Process

• 2nd : in the field• Collecting, sorting parts and record the characteristics and pictures in the external

system• Attribution of MFIO temporary codes for provisional labelling

• 3rd : setting up store management with EAM• Formal code attribution by Naming Service• Massive upload into EAM by the means of web services• Implementation of an EAM integrated solution for store management, labelling and

traceability

Naming service code

MFIO code

Slide 21

MFIO COLLECTING DATA TOOLThe information is easily organized

within the application to help users to find the right part and obtain all the

information potentially needed.

Specifications (custom fields)

VDC max. 600 V

VAC max. 600 V

ADC max. 10 A

AAC max. 10 A

Ω max. 10 M ohms

Hz max. 50 kHz

Display Type LCD

True RMS Yes

Weight 550 g

….

Manufacturer: FLUKE

Manufacturer Part No: 117

Storage:

Vers. Exec. Store Bin Qty Min Qty UOM

001 01 Build.866 C3-02 2 1 pc

ID: MMP-0000011

Code HCHxxxx

FLUKE - 117 - MULTIMETER, DIGITAL, HAND HELD, 6000

E-CATALOGUEThe goal is to provide an “e-catalogue”

of part datasheets with:designation, picture, characteristics,

EDMS links, storage information

Parts collection: e.g. External User Interfaces

Slide 22

Objective: Collect data of all parts stored in building 7 (EN/HE)

More than 30 racks with 21 shelves each

Part collection process: e.g. EN-HE store management

Building 7

Slide 23

Documentation

How do we organize the collection process?

Part collection process: e.g. EN-HE store management

• MFIO code linked to the old codes (if exist)

• MFIO labels (with barcode)• Store, rack, bin (position)• Quantity• Picture

Basic data

• Part description• Class/Custom Fields• Manufacturer/ Part code-number• Supplier• Use cases

Complementarydata

This phase can be sped up by automating some activities.

We do not need any knowledge about the stock to

perform this phase.

This phase is more laborious and requires help from the store

experts.

Slide 24

• More than 3500!! parts have been registered and labelled with the MFIO code

• Old codes have been included

• More than 15000 pictures have been taken and are now available

• More than 500 bins have been created

• Manpower invested – 3 man-months

Part collection process: e.g. EN-HE store management

All parts have been counted which means that there is a trustable and updated understanding of the stock

inventory.

Slide 25

Part collection process: e.g. EN-HE store management

iPadBarcode readerPortable computer

CameraPortable printer

Equipment used

Slide 26

Part collection process: e.g. EN-HE store management

External expert from TE/EPC

EN/HE GSPO

MFIO Team

People involved

Slide 27

Part collection process: e.g. EN-HE store management

All parts are now labelled. The data stored in the DB is easily accessible

with a barcode reader.

Professional pictures help to identify the parts without visiting

the store and provides complementary information.

As result

Slide 28

• EN/HE and EN/STI part collection:• Equipment and a part of the required IT tools are now ready• MFIO team masters the process of parts recording and is ready to support other groups

provided that a GSPO was appointed, is trained and available

Part collection: Feedback

• Next steps:• Store management implementation

• GE-ASE will lead the implementation of the EN/HE and EN/STI store management and part traceability with Infor EAM as from the 25th of October

• Data collection• MFIO and GS/ASE continue to develop IT functionalities and user interfaces• MFIO will contact TE/MSC and TE/VSC, which have already a well organized storage area

Slide 29

• Formal codes part & asset attribution:A large number of systems need to be synchronized in the framework of the MMP which requires a synchronized and harmonized coding system. This problem is amplified by historical constraints.• Result: The current processes are not yet sufficiently fluent for code part and asset attribution,

which causes delay and makes the part recording difficult. • Need: Simplified rules in a QAP context and automatic providers for an immediate attribution of

95% of codes. • Action: A new working group led by P. Bonnal will study a strategy to harmonize the coding

systems

Part collection: Open issues

• Different processes for part recording, MMP sets new standards for the harmonization of records, however, previously established processes continue to exist.• Result: Data format and quality can be divergent• Need: Review of all the data input processes• Action: Common effort of MFIO and GS-ASE required

Slide 30

• Functional breakdown (Layout)The rules to perform layouts are not defined in all areas• Result: It is difficult to know the relevant granularity at which it must be created in the different

systems. Functional breakdown across facilities are not homogenous• Need: A service with an expert knowledge of the best practices in the domain and that is able to

assist the equipment responsibles• Action: Layout Service, GS/ASE, MFIO and QAWG shall find means to provide this support

Part Management: Open issues

Slide 31

• Status• A part of the required informatics tools are ready, the development continues• Processes for part collection are well defined and based on EN/HE experience• A MFIO team of 2 members is in charge of the part collection with possibility to create a

second one if necessary • 3500 parts recorded in 1 month with 3 FTE• Group Coding Officers, Group Part Officer and responsible of equipment are key roles for this

activity• 3 GCO and 3 GSPO are now autonomous (TE-EPC, TE-CRG, EN-HE)

Part collection: Summary

• Open issues• Formal code attribution• Harmonization of the different processes to record parts• Rules and bests practices to establish layouts for functional positions

• Short term actions until end of 2014:• Continue the development of IT tools and user interfaces (MFIO, GS/ASE)• Support and training for part collection of the 9 remaining groups (MFIO) • Set-up the store management and part traceability with EAM: GS/ASE

Slide 32

Issue Management

Slide 33

Two different processes synchronized by well managed exchanges

Cern Control Center

Issue management: Reminder• Intervention efficiency to reduce downtime by:

• optimization of the exchanges between CCC and EQT team• the provision of IT tools as decision support and information provider

• Issue traceability for homogeneous statistics and reporting across all equipment and groups

Slide 34

Group Type of equipment Complex QuantityBE/ABP Proton source PS (Linac2) 1

BE/RF Electron source (CTF3), RF cavities PS, LHC 1+6

BE/BI MTV screens PS 2

TE/EPC Power converters PS, SPS, LHC 65

TE/VSC Vacuum valves PS, LHC 8

TE/MSC Bending, septa magnets PS, SPS, LHC 58

TE/ABT Septa, kicker magnets PS, SPS, LHC 8

EN/STI Beam stoppers, TBSE, TED, laser shutters

PS, SPS, LHC 39

EN/MEF Magnetic lenses (CNGS) SPS 2

EN/MEF, EN/STI

TAX, movable shielding (CNGS), vacuum shutter (CNGS)

SPS 9

Slide 35

Contact: A. Funken and S. Hutchins

Issue management: EIS*

*EIS: Éléments importants pour la sécurité

Inventory of the EIS

• On site stickers• EIS pictogram• EDMS maintenance associated procedure number

• Database systems

• LAYOUT Service → done

(Functional Position, Identification)

• MTF, CMMSMTF link → doneTE-MSC, TE-EPC → implementedOther clients EN-TE → on-going EAM INFOR → to be defined

• BPMN processes corrective intervention → described https://edms.cern.ch/document/1259123/1

maintenance planned → described https://edms.cern.ch/document/1283067/1

DSO test → on-going DSO EDMS conventions → on-going

1234567

Issue management: EIS Status Implementation

Slide 36

4. EIS web portal proposal BE/CO + GS/ASE October

5. Pilot group implementation BE-EN-TE tbc November

6. Deployment to other groups BE-EN-TE owners, January 14

DSO-MFIO & MMP experts

Issue management: Next steps

Formalization – Convention – Coordination – Quality A. Funken R. Pilon

done

1. EIS statement Layout & Naming BE/CO-GS/ASE-EN/MEF-DSO

2. BPMN processes validation BE-EN-TE owners - DSO

3. LAYOUT DB BE/CO

EAM INFOR – MTF GS/ASE

CCC tools, LASER BE/CO + CCC

Slide 37

Issue management: Status

• Status:• CCC side, I. Laugier has been nominated to specify the needs of the 4 control rooms• MFIO: BPMNs for corrective interventions have been done with 6 groups TE/EPC,

TE/CRG, TE/VSC, EN/CV, EH/EL et EN/HE• Éléments Importants pour la Sécurité (EIS): 90% of the implementation is performed

• Next steps:• MFIO: complete group consultations and work on the field processes• MFIO and I. Laugier: Define and specify common requirements of CCC and equipment

groups

Slide 38

Observations

Slide 39

https://edms.cern.ch/document/1287822/3

Transversal functions inside groups

Slide 40

Observations 1• Maintenance management maturity of equipment groups

increases • GLs created several transversal functions at group level to manage documentation, spare parts and

quality issues• Papers and presentations have been written in various groups• Working groups are organized on specific topics of maintenance management• The technical training organized under the MMP is successful• Maintenance skills are more often used in job descriptions

• Outside the accelerators sector, the project is observed• DG-RPC is interested in asset inventories $$$ (L. Van den Boogaart)• GS/SE came to see our document management process (Y. Robert)• HSE asked for help to classify safety inspections

• People are ready to re-organize the management of their maintenance activity and to look for support and software tools to assist them in this task.

Slide 41

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

43

CMMS tools – An update of recent improvements and news

MMP status presentation

EDMS 1292183

Global usage of CMMS: 2013

* Equipment means Assets, Functional Positions and Systems

** Licenses are timed-out (and rotated) after 180 minutes of inactivity.

2013 (Jan-Sep) 2012

WOs Created 150.000 122.000

WOs Completed 98.000 83.000

New Equipment* 271.000 118.000

New Parts 2.200 3.050

CCC/TI Service Desk

WOs Created / month ~620 ~820

Infor EAM EAM Light

Concurrent users per day** ~45 ~15

Different users logged (since 05/2013) >400

CMMS usage by group: 2013

Work Orderscompleted 2013*

*excluding MTF

Work Orders created 2013*

CMMS usage by group: 2013

New Equipment created 2013*

Total number of Equipment (Top 15)*

*excluding MTF

CMMS usage by group: 2013

New Partscreated 2013

EDMS documentscurrently linked in

Infor EAM*

*excluding MTF

Tools & integrations• Barcode label printing solution provided (Jan 2013)

• Solution with CodeSoft Enterprise and tailored database views demonstrated and proposed by GS/ASE in Jan 2013.

• Successful tests by TE/CRG validating this solution finalized in May.

• EDMS Offline Viewer improvements delivered (Jan/Jun 2013)• Several improvements and bug fixes provided.• Version 2.1 (Jan)

• Support for data extraction on Windows 64-bit• Several bug fixes (printing, visualization, etc.)

• Version 2.2 (June)• Support for data extraction with Java 7.

Tools & integrations• Links between EAM Parts and EDMS Items in place. (April 2013)

• EAM Part references now displayed on EDMS Item page.• Possibility to create/edit Part-Items links from Infor EAM interface.

• Additional EDMS web services implemented (May 2013)• 3 new web services provided to attached documentation to:

• Parts, Categories & Preventive Maintenance (PM) Schedules

• “Consolidated” EDMS document view (in test since July 2013)• Better overview of EDMS documents attached to EAM equipment as defined in

EDMS 1218700.• Will provide easier access to available related documentation. (For example

documentation attached to equipment of the same type.)• Accessible from both Infor EAM and EAM Light.• Currently tested by EN/HE.

Tools & integrations• IMPACT and PlanBook integration (July 2013)

• Possible to associate Work Orders and IMPACT Activity Requests.• Planning of Work Orders now possible in PlanBook.• Web services provided to GS/AIS and new fields made available in both

Infor EAM and EAM Light. • Bulk update tools in EAM Light for Work Orders based on IMPACT data.• Required effort risk to grow once the integration is starting to be used.

EAM Light Infor EAM

Tools & integrations• New Risk & Reliability module configured in TEST (Aug 2013)

• Allows automated calculations of criticality rankings for equipment based on the CERN formulas proposed by Pierre Bonnal and Ingo Ruehl (EDMS 1235070).

• Available for testing in the Infor EAM 10.1 TEST environment.• Will be available in production with version 10.1.2 of Infor EAM (Q4 2013)

EAM Light • 380 different users has logged into EAM Light since May 2013. • Several new versions delivered – mainly based on user input.

• Version 1.6 (Feb 2013)• Possibility to edit custom fields, support for Standard Work Orders, possibility to create Work Order

from Equipment page, etc.)

• Version 1.7 (April 2013)• Possibility to personalize columns shown in search results, minor bug fixes and navigation

improvements (Work Order – Equip. Links).

• Version 1.8/1.9 (June 2013)• Improved Work Order search (more input possibilities and more available columns in result listing)

and GIS integration. Mobile view for Tablets & Smartphones.

• Version 1.10 (July 2013)• Possibility to enter Parts used for Work Orders, Uploading of pictures (also from Tablets and

Smartphones) and IMPACT Activity Requests show for Work Orders.

• Version 2.0 (Oct 2013)• New Parts page, Input of Meter readings, Searching based on custom fields, navigation links

between Parts and Assets, Bulk update of Scheduled dates for Work Orders, etc.

EAM Light

New graphical reports in EAM• Meter readings and inspection results can now be represented graphically

directly from Infor EAM using the EAM Light framework. (Jun 2013)

Before:After:

Improved GIS integrationNew “Show on Map” function (Jun 2013)• Possible to locate equipment geographically using CERN’s GIS.• Available in both EAM Light and Infor EAM.• Depending on available information different displays are proposed.

• Shows exact location on map (in the right portal) if coordinates have been stored in GIS.

• Shows only location (building/ovrage) on Map if no coordinates have been stored.

Improved GIS integrationNew CMMS GIS Portal (Sep 2013)• Possible to search for equipment in GIS Portal.• Direct links from a location or equipment in GIS to EAM Light listing:

• All Equipment in this location • All open Work Order in this location• Equipment information (technical details, history, documentation, etc)

System related tasks• Simulation of data growth completed (April 2014)

• Data was increased x2 for all of the systems tables used.• No degradation of speed could be seen. (EDMS 1291901)

• Upgrade to version 10.1.2 (On-going)• Test installation in place since mid June.• Preliminary target date (depending on tests): Q4 2013

• Improved access rights management by deploying the “Department Security” option. (On-going)• Strongly demanded by several groups (EN/CV, etc.)• First study being finalized: EDMS 1284364 • Tests and implementation: Q4 2013

Projects shared with MFIO• Examples of support projects managed together with MFIO

• BE/CO – Racks management, in collaboration with Z. Zaharieva • EN/STI – Collimator equipment, in collaboration with D. Lafarge• EN/HE – Parts and Documentation, in collaboration with D. Lafarge

• We believe joint support projects with participation from both the MFIO and GS/ASE is the way forward. (EDMS 1242004)

• Examples of other activities together with MFIO• Procedures for handling CDD drawings for maintenance.• Input to Equipment/Part data collection tool.

Projects outside the MMP scopeExamples of projects not directly linked to the MMP project

• IT/CS - TETRA• TETRA equipment being registered in EAM and setup to be done for

basic corrective maintenance.• Status: Test environment being put in place.

• CERN Crisis rooms – Preventive maintenance & Inspections• The crisis rooms equipment in building 65 will be periodically checked

and maintained. (Mainly equipment from IT/CIS & GS/SE.) • Status: Test environment being put in place.

• IT/CF – Asset management of CERN´s data centers• Tracking of assets and parts in s our 3 data centers in with Infor EAM.• Status: Tests successfully completed. Preparing production environment.

Projects outside the MMP scope• GS/SE – Site/Facility Management

• A significant effort has been launched in order to improve the current maintenance processes for the sites and facilities.

• A new generic information structure for each buildings is proposed.• Focus is currently put into storing and linking technical documentation as

well as identifying Parts used for maintenance (currently not traced in Infor EAM).

• Overall approach very similar to the MMP. • Status: Pilot buildings being prepared for

validation of concept.

Inforum - Infor conference• Inforum is the annual conference for all Infor products. (April 2013)

• Organized for the 3rd time, this time in Orlando, 4 days ~6.000 attendees, ~ 500 participants in the EAM track

• Possibility to maintain our excellent contacts with the Infor top management.

• Several CERN presentations delivered with positive feedback.

• CERN received an Excellence in Action Award in Operational Excellence for our web-service based integration of the Service Desk and CCC/TI with Infor EAM.

62

CERN presentations: • EDMS 1277479• EDMS 1276617

All EAM related slides:• EDMS 1285363

Visit report:• EDMS 1283295

CERN Infor EAM User Meetings• The first Infor EAM User Meeting was held on 27 June 2013 with

some 50 participants.• The purpose is to inform current users of the new functions and

extensions to the system.• Our idea is to idea of organizing meetings on a regular basis 3-4

times per year – in a similar way as for CATIA/Smarteam users.• Very positive feedback. Next meeting scheduled for 19 November.

• Agenda and slides from June meeting:

• Preliminary agenda for November meeting:https://indico.cern.ch/conferenceDisplay.py?confId=255226

https://indico.cern.ch/conferenceDisplay.py?confId=277048

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

65

Communication, training and workshops

• Maintenance management courseEnglish version – pilot course in January – first session in June – very positive feedbackFrench version – prepared – first session foreseen in DecemberWe receive excellent support by HR (S. Schuh-Erhard)!

• A&T seminar “Maintenance management” Held on 7th February 2013 – very good participation

• Presentation and posters at the ARW2013 workshop in April 2013“The maintenance management project at CERN” G. Perinic, I. Rühl“Harmonising maintenance processes methodology at CERN” C. Mugnier et al.

• Asset and maintenance management magazine “maintworld” The CERN library is supporting the MMP with a subscription of the magazine “maintworld” and its distribution in selected CERN magazine displays.

• Proposal for A&MM seminar seriesThe MMP proposes to launch a seminar series on topics within the scope of the project aimed at asset and maintenance management stakeholders.

COMMUNICATION ST

66

Poster at the ARW2013

Communication, training and workshops

• CERN asset and maintenance management workshop AMMW2013

13th-15th November 2013So far 20 external participants from Cells, DESY, ESS, European XFEL, ITER, MaxLab, ITER27 talks plus keynote by former astronaut M. Tognini

• Forum on “Asset and Maintenance Management”

A mailing list based forum has been prepared and will be launched at the AMMW2013.

67

New skillsTraining

InformationNetworks

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

69

70

Resources

MMP core team MMP extended team MFIO Support teamsIngo Rühl (Project Leader) Stephan Petit Christophe Mugnier (Office leader) GS/ASE/EDS Goran Perinić (Project Leader) Cathelijne Hazelaar-Bal Damien LAFARGE (Deputy leader) GS/ASE/EPSDavid Widegren Sigrid Knoops Regis Pilon Layout ServiceChristophe Delamare Tahar Klabi Ludovic Germain-Bonne Naming ServiceZornitsa Zaharieva Coralie Perolini (FSU) GS/AIS/PMMarine Gourber-Pace Javier Ruiz Cabezas (Fellow) Pierre Bonnal Joaquim Sylvestre (Fellow) Christophe Mugnier Patrice Bailly Eric Van Uytvinck Irene Alonso-Canella (Fellow) Damien Lafarge Solomon Goldstein (Ext.) Bastien Digonzelli (FSU) Marc Bomont Sophian Sabri (FSU) Sebastien Delpree Lidia Sarazua (Summer student)

2.5 FTE 8.5 FTE

Agenda

• Introduction I. Rühl

• MFIO news C. Mugnier

• CMMS status report C. Delamare

• Communication, training, workshops G. Perinic

• Resources I. Rühl

• Conclusion I. Rühl

72

73

Conclusion• Slower progress than hoped

• Delay for creating (MFIO) and interfacing (GS-ASE) customized SW tools• Identifying non compatibilities between existing well established processes

(i.e. layout and naming service) wrt to specific maintenance requirements• All tools and processes will be tested and validated by end of 2013 • General acceptance of MMP within the AT sector (and beyond) growing we

need to deliver!!!• Need of QAWG / PLMWG to tackle linked processes and procedures• Not all fixed objectives will be met by end of LS1

• Estimated 6 months delay to original planning• MFIO has done well to put priority on quality and procedures over planning• Purely maintenance issues were not yet tackled at all• MFIO structure will be required well beyond LS1 to assure:

• a continuous coherent CMMS implementation process• the quality of entered data• the support of equipment groups

MERCIYOUR QUESTIONS AND COMMENTS

PLEASE?!

75

77

SPARE SLIDES

• Develop a modular MMF interfaced with CERN’s key technical management systems (e.g. Layout Database, EDMS, IMPACT, ...)

• Time target 2 years (from early 2012)

Modular Maintenance Management Framework (MMF)

• Define and approve a method for identifying critical assets • Identify at least 95% of the critical assets• Handle their spare parts, material lists and technical documentation

within the framework• Define standards for critical assets to reduce spare part diversity• Review maintenance requirements for the identified critical assets

Critical assets

• Define the technical documentation required for maintenance purposes

Technical documentation

Purpose, Objectives and Impact of the Project

GLOBAL OBJECTIVES 1/4

25/1

1/20

11

G. Perinić P. Bonnal et al. — MM Workshop 78

• Handle within the MMF50% of A&T sector’s technical assets

Assets

• Manage within the MMF50% of the spare parts

Spare parts

• Make available through the MMF50% of the existing technical documentation required for maintenance activities

Technical documentation

Purpose, Objectives and Impact of the Project

FUNDAMENTAL OBJECTIVES 2/4

25/1

1/20

11

G. Perinić P. Bonnal et al. — MM Workshop 79

• Define and implementpreventive maintenance plans of critical assets (where applicable)

• Define and implement condition based maintenance tasks (where applicable)

Preventive and condition based maintenance

• Calculate through the MMF key performance indicators of at least all critical assets calculated and managed

Key performance indicators (KPIs)

Purpose, Objectives and Impact of the Project

ADVANCED OBJECTIVES 3/4

25/1

1/20

11

G. Perinić P. Bonnal et al. — MM Workshop 80

• Develop the MMF in line with existing quality assurance plans

Quality assurance

• Pursue the principle of coherent data management between the technical information systems - e.g. avoid double data entries

Data management

• Design, develop and deploy an organization for addressing the remaining assets as from late 2014, and for operating the MMF on the longer term

Maintenance management organisation

Purpose, Objectives and Impact of the Project

FRAMEWORK AND NEXT STEP OBJECTIVES 4/4

25/1

1/20

11

G. Perinić P. Bonnal et al. — MM Workshop 81

Z.Zaharieva Naming and Layout Services activities helping MMP 17.10.2013 82

The Accelerators Entities Naming Service

“in a nutshell”• Responsible: P. Le Roux, Z. Zaharieva (BE-CO-DA), S. Chemly

(EN-MEF-DC)

• Standard mechanism for codes requests and help: Accelerators-Naming.Service@cern.ch

• Hide the complexity of the Coding from the users and serve as a unique point of reference

82

Z.Zaharieva Naming and Layout Services activities helping MMP 17.10.2013 83

Naming Portal improvements: https://cern.ch/service-acc-naming

83

• To help the user community, including the MMP project• Incorporated CDD code search into the Common Codes Search• New Advanced Codes Search report• Publishing the list of the Group Coding Officers on the Portal• Publishing the procedure to follow for a request of a new code and the BPMN

process diagram

Z.Zaharieva Naming and Layout Services activities helping MMP 17.10.2013 84

MMP related request to Naming Service

84

• Cryogenics Equipment Codes consolidation (working with TE-CRG)• > 500 new Cryo codes declared and updated on the Naming Portal

• Power Converters Equipment Codes publication (working with TE-EPC)• > 400 new Power Converters codes published on the Naming Portal• Synchronization between the Naming DB and ALIM DB

• Handling Codes - agreed on a policy with the users (working with EN-HL)• Published the first batches of codes

• New Collimators codes publications (EN-STI) for the needs of the Layout and MTF

• A lot of other ‘business as usual’ requests treated, which are not listed here (e.g. Vacuum, Magnets, etc.)

Z.Zaharieva Naming and Layout Services activities helping MMP 17.10.2013 8585

• Responsible: P. Le Roux, E. Fortescue-Beck, Chris Roderick (BE-CO-DA); Samy Chemli, Sonia Bartolome Jimenez, Thomas Birtwistle (EN-MEF-DC)

• Standardized channel for Layout functionality requests and help: layout-service@cern.ch

• Standard mechanisms for definition of functional positions into the Layout and propagation to MTF/Infor

The Layout Service

“in a nutshell”

Z.Zaharieva Naming and Layout Services activities helping MMP 17.10.2013 8686

• EN/EL functional positions data integration in Layout• Implemented a process for data exchange between Layout and Infor

• EN/STI Collimator functional position declared in Layout and propagated to MTF (> 1000 slots provided to MTF/Infor)

• EIS equipment functional positions integration into the Layout • ~ 1800 EIS identified so far• Public EIS Layout navigator: https://cern.ch/layout/default.aspx?navigator=eis• Layout EIS Editor: https://apex.cern.ch/pls/htmldb_accdb/f?p=eiseditor

• TE-EPC functional positions data - automated daily mechanism for integration into Layout and propagation to MTF/Infor

• Continue working with other Layout users in a business as usual manner (e.g. Cryogenics, Vacuum, etc.)

MMP related requests to the Layout Service

Executive Committee

Team CMMS development

MFI Office(Maintenance Framework

Implementation )

TE Maintenance Framework

Implementation

EN Maintenance Framework

Implementation

BE Maintenance Framework

Implementation

Maintenance ManagementQuality Insurance

Maintenance Management

Project

C. Mugnier D. Lafarge M. Gourber-Pace

I. Rühl, G. Perinic

C. DelamareP. Bonnal,

Z. Zaharieva

Department Heads BE, EN, TE, GSTask force members

Organizational Structure MMP/MFIO

87/21

• Support and monitoring :• Quality assurance and administrative activities.• Design/Definition of new tools.• MMP deployment and activity monitoring.

• Communication and training support for CERN groups.

C. Mugnier (TE staff 80%)

D. Lafarge (EN staff 25%)

C.Perolini (TE Engineer FSU 100%)

J.Ruiz Cabezas (TE fellow 100%)

J.Sylvestre (TE fellow 100% since June 2013)

S. Goldstein (Consultant 50%)

R. Pilon (TE staff 80%)

M. Bomont, P. Bailly, L. Germain Bonne (TE staff 50%)

B. Di Gonzelli &S. Sabri (FSU 100%)

Working group :

• Asset management

• Work management

• Planning & scheduling

• Information management

• Spare parts management

• Analysis & Reporting

https://edms.cern.ch/document/1287822/3

Observations 2Others CERN services