1. Maintenance Management Project Status Report Follow Up Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

2. Open issues MMP Status Report 29.05.2012 MMP Status Report meeting minutes – 1221323 v.1.0 MMP Status Report meeting minutes – EDMS 1221323 v.1.0 MMP Concept Report - 1173942 v.1.0 MMP Concept Report - EDMS 1173942 v.1.0 Implementing MFIO concept and organization Coding / Issue / logbook / TREC / IMPACT / planβ context adds a new dimension (and complexity) to the project Infor EAM develops towards a more user friendly tool Resources ‘almost’ at a sustainable level but some ‘effort’ is still required Equipment criticality and KPIs need some clarification with the DHs

3. Agenda Introduction I. Rühl Introduction I. Rühl MFI Office concept & status report C. Mugnier MFI Office concept & status report C. Mugnier QA and data management Z. Zaharieva QA and data management Z. Zaharieva Infor EAM light interface S. Mallon-Amerigo Infor EAM light interface S. Mallon-Amerigo Resources summary and outlook I. Rühl Resources summary and outlook I. Rühl AOB G. Perinic AOB G. Perinic Conclusion I. Rühl Conclusion I. Rühl

5. Maintenance Management Project Status Report Follow Up MFI Office Concept & Status Report Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

6. Steering Board TE Maintenance Framework Implementation TE Maintenance Framework Implementation EN Maintenance Framework Implementation EN Maintenance Framework Implementation BE Maintenance Framework Implementation BE Maintenance Framework Implementation Maintenance Management Quality Assurance Maintenance Management Project C. MugnierD. LafargeM. Gourber-Pace I. Rühl, G. Perinic C. Delamare P. Bonnal, Z. Zaharieva Department Heads BE, EN, TE, GS Task force members Department Heads BE, EN, TE, GS Task force members Other existing CERN services Other existing CERN services The MMP Project 6 Documentation management Spare parts management Analysis & Reporting The analysis of needs and transcription as a specification is performed by 6 working groups: Asset management Work management Planning & scheduling

7. Steering Board MFI Office (Maintenance Framework Implementation ) TE Maintenance Framework Implementation TE Maintenance Framework Implementation EN Maintenance Framework Implementation EN Maintenance Framework Implementation BE Maintenance Framework Implementation BE Maintenance Framework Implementation Maintenance Management Quality Assurance Maintenance Management Project C. MugnierD. Lafarge M. Gourber-Pace I. Rühl, G. Perinic C. Delamare P. Bonnal, Z. Zaharieva Department Heads BE, EN, TE, GS Task force members Department Heads BE, EN, TE, GS Task force members The MFIO in the MMP project 7 Support and monitoring for: Administrative tasks and Quality Assurance Specific IT tools development Deployment and follow up Communication (between users, MMP team and existing CERN services) C. Mugnier D. Lafarge C.Perolini (TE engineer FSU 100%) J.Ruiz Cabezas (TE fellow 100%) R.Pilon (TE staff 60%) J.Sylvestre (EN fellow 50%) A.Metola (GS fellow 50%) B.Vercoutter (GS staff 50%) T.Klabi (GS staff 50%) Working groups: Asset management Work management Planning & scheduling Documentation management Spare parts management Analysis & Reporting Working groups: Asset management Work management Planning & scheduling Documentation management Spare parts management Analysis & Reporting Other existing CERN services Other existing CERN services

8. Communication Collects the requests (Ticketing service), summarizes and reports to MMP team Informs and supports users (Hot-line, Web-site, etc.) Implements specific training for maintenance management Communication Collects the requests (Ticketing service), summarizes and reports to MMP team Informs and supports users (Hot-line, Web-site, etc.) Implements specific training for maintenance management Roles Deployment and follow-up support Supports and monitors the implementation of the framework Collects the return of experience and reports to MMP Involves and provides support for the groups and sections - Mobilises the Stakeholders concerned by maintenance at each project step, Deployment and follow-up support Supports and monitors the implementation of the framework Collects the return of experience and reports to MMP Involves and provides support for the groups and sections - Mobilises the Stakeholders concerned by maintenance at each project step, Administrative and quality assurance support Elaborates the BPMN diagrams to formalize processes of maintenance Provides support for writing QA documents, procedures Administrative and quality assurance support Elaborates the BPMN diagrams to formalize processes of maintenance Provides support for writing QA documents, procedures 5 Specific IT tools development Elaborates temporary IT tools & defines needs for user interfaces Collects feedback from users and reports to MMP concerning the IT tools. Specific IT tools development Elaborates temporary IT tools & defines needs for user interfaces Collects feedback from users and reports to MMP concerning the IT tools.

9. mfio@cern.chmfio@cern.ch; tel : 62185; Service Portal www.cern.ch/mmp www.cern.ch/mmpCommunication

10. 7 Additional resources, groups involvement Group maintenance management functions GCO Group Coding Officer GMIO Group Maintenance Information Officer GQMO Group Quality Methods Officer GSPO Group Spare Part Officer Group maintenance management functions GCO Group Coding Officer GMIO Group Maintenance Information Officer GQMO Group Quality Methods Officer GSPO Group Spare Part Officer EN department : Coaching: 3 experts (~ 40% FTE each) Data collection and deploym. teams: TBD* EN department : Coaching: 3 experts (~ 40% FTE each) Data collection and deploym. teams: TBD* TE department : Coaching: 6 experts (~ 20% FTE each) Data collection and deployment teams: ~ 4 FTE/Year provided by groups TBD TE department : Coaching: 6 experts (~ 20% FTE each) Data collection and deployment teams: ~ 4 FTE/Year provided by groups TBD BE TBD* BE TBD* C. Mugnier D. LafargeM. Gourber-Pace See § 3.6.2 of concept report MMP https://edms.cern.ch/file/1173942/1.0/2012-06-26_MMP_ConceptReport_v0.0.pdf * An important contribution by the equipment responsibles is required!

11. Power converter HCRPZBJ.250.ERQFT24 Convertisseur HCRPZBJ001 1.Functional breakdown & equipment codification (Layout & EDMS) 2.Spare Parts (Infor EAM) 3.Documentation (EDMS & MTF) 1.Functional breakdown & equipment codification (Layout & EDMS) 2.Spare Parts (Infor EAM) 3.Documentation (EDMS & MTF) Global steps for implementation 1/2 Systematic steps with newcomers

12. Global steps for implementation 2/2 4.Workflows (corrective and preventive maintenance, spares parts management, information management…) 5.Analysis & reporting 4.Workflows (corrective and preventive maintenance, spares parts management, information management…) 5.Analysis & reporting

13. Main MFIO Partner contacts EDMS support EDMS support GS CMMS developments GS CMMS developments Naming Service Naming Service Layout Service Layout Service CCC (Issue Management System) CCC (Issue Management System) GS AIS (Impact) GS AIS (Impact) IT & GS Service Management Support (Service Now), IT & GS Service Management Support (Service Now), Quality Assurance entity at Sector Level Quality Assurance entity at Sector Level Close collaboration is required with many external services in terms of maintenance matters. This comprises the definition of interfaces and deliverables.

14. MFIO activities during this summer

15. Pilot Project – BE/BI Equipment concerned Equipment concerned Electronic cards and crates (J. Emery, S. Grishin) Electronic cards and crates (J. Emery, S. Grishin) Actions Actions Refurbishment and clarification of functional breakdown defined in 2007 Refurbishment and clarification of functional breakdown defined in 2007 Update of existing codes and recording of new codes with CMMS service and Naming Service support Update of existing codes and recording of new codes with CMMS service and Naming Service support Recording of assets (tree structure, coding, metadata) Recording of assets (tree structure, coding, metadata) In progress In progress

16. Pilot Project – EN/HE Equipment concerned Equipment concerned Mobile handling equipment (J.M. Chevalley as GMIO) Mobile handling equipment (J.M. Chevalley as GMIO) Actions Actions Implementation of documentation recording processes Implementation of documentation recording processes Test of IT tools for documentation collection Test of IT tools for documentation collection Refurbishment of files and metadata Refurbishment of files and metadata Progressive recording of all documentation Progressive recording of all documentation Deadline 15/10 start of the batch recording Deadline 15/10 start of the batch recording

17. Pilot Project – EN/STI Equipment concerned Equipment concerned Collimator electronics (C. Mitifiot) Collimator electronics (C. Mitifiot) Collimator mechanics (R. Bebb) Collimator mechanics (R. Bebb) Actions Actions Recording of assets (tree structure, coding, metadata) Recording of assets (tree structure, coding, metadata) Recording of spare parts (links to assets, coding, metadata) Recording of spare parts (links to assets, coding, metadata) Training for usage of Infor assets and spare parts modules Training for usage of Infor assets and spare parts modules Recording of documentation foreseen Recording of documentation foreseen Intervention management with Infor foreseen Intervention management with Infor foreseen Deadline to be defined Deadline to be defined

18. Pilot Project – TE/CRG Equipment concerned Equipment concerned All group operational documentation (S. Knoops as GMIO) All group operational documentation (S. Knoops as GMIO) Actions Actions Implementation of documentation recording processes Implementation of documentation recording processes Test of IT tools for documentation collection Test of IT tools for documentation collection Refurbishment of files and metadata Refurbishment of files and metadata Progressive recording of all documentation Progressive recording of all documentation Refurbishment of equipment codes with Naming Service Refurbishment of equipment codes with Naming Service Deadline 15/10 start of the batch recording Deadline 15/10 start of the batch recording

19. Pilot Project – TE/VSC Equipment concerned Equipment concerned Leaks detectors (A. Sinturel) Leaks detectors (A. Sinturel) Vacuum chambers & Seals (A. Caio) Vacuum chambers & Seals (A. Caio) Sector valves (G. Schneider) Sector valves (G. Schneider) Actions Actions Recording of assets (tree structure, coding, metadata) Recording of assets (tree structure, coding, metadata) Labeling of equipment Labeling of equipment Definition of specific BPMN for traceability of equipment Definition of specific BPMN for traceability of equipment Recording of documentation Recording of documentation GCO (E. Page) nominated by Group Leader GCO (E. Page) nominated by Group Leader Deadline 30/10 presentation to Group Leader Deadline 30/10 presentation to Group Leader

20. MFIO IT tools IT Tools for batch documentation treatment IT Tools for batch documentation treatment Specific temporary tool for formatting documentation files and metadata (Praxis) Specific temporary tool for formatting documentation files and metadata (Praxis) Integration EDMS + Praxis => batch upload of documentation into EDMS Integration EDMS + Praxis => batch upload of documentation into EDMS Ticketing service launched Ticketing service launched

21. MFIO processes defined Labelling Labelling BPMN analysis and formalization of process BPMN analysis and formalization of process Formats of stickers, templates and data Formats of stickers, templates and data Options to print labels (central support or group internal) Options to print labels (central support or group internal) Various BPMN analyses and formalization Various BPMN analyses and formalization Coding Coding Documentation recording Documentation recording Planned interventions Planned interventions Traceability of mobile equipment (leak detectors) Traceability of mobile equipment (leak detectors)

22. Projection MMP/MFIO 1.Identify needs in term of support from external services: Naming and Layout Service Naming and Layout Service EDMS & EAM Support EDMS & EAM Support Quality Assurance entity at Sector Level Quality Assurance entity at Sector Level 2.Specify the Issue Management System with CCC and Crisis Management WG 3.Specify a scheduling tool synchronized with IMPACT 4.Deploy Infor EAM with associated tools 5.Define standard for KPIs (criticality of assets) and associated management rules in line with LHC Reliability WG

24. Maintenance Management Project Status Report Follow Up Quality Assurance & Data Manangement Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

25. Quality Assurance & Data Management Establishing an effective data management is a prerequisite for the success of the MMP Establishing an effective data management is a prerequisite for the success of the MMP Technology Technology Data itself – structure, metadata, content, quality Data itself – structure, metadata, content, quality Unifying business processes & practices Unifying business processes & practices Integration of data between Infor EAM and IMPACT on-going activity (CMMS and GS-AIS teams) Integration of data between Infor EAM and IMPACT on-going activity (CMMS and GS-AIS teams) Engineering Documentation & Assets Maintenance Management MTF/Infor EAM EDMS / Agile CDD / SmarTeam IMPACT Z. Zaharieva CERN, 30.08.2012 25

26. CERN, 30.08.2012 Data Management Domains The Asset Maintenance Management domain is not isolated The Asset Maintenance Management domain is not isolated Documentation & Operational Data Layout & Infrastructure Controls Configuration QA Assets Maintenance Alarms LASER MTF/Infor EAM EDMS / Agile CDD / SmartTeam IMPACT Layout Management Controls Configuration DIAgnostics & MONitoring LogBooks Logging Measurements ABS OASIS Settings Management Postmortem Entities and Signals Naming TIM 26 GEOSIP

27. Integrated Data Management Environment – Key to Success Consistent naming and vocabulary throughout the data management domains Consistent naming and vocabulary throughout the data management domains Coordination amongst the processes of the different Information systems Coordination amongst the processes of the different Information systems Establish one source of data – avoid data duplication Establish one source of data – avoid data duplication Coherent communication between the Information systems Coherent communication between the Information systems There should be no direct competition between information systems There should be no direct competition between information systems QA CERN, 30.08.2012 Z. Zaharieva 27

28. Avoid isolated data Maintenance Management Avoid isolated data Maintenance Management By establishing interfaces between systems By establishing interfaces between systems Improve the data management => improve the efficiency of all business processes Improve the data management => improve the efficiency of all business processes Correlate data across domains to gain insight Correlate data across domains to gain insight Data Information Knowledge Data Information Integrated Data Management Environment QA CERN, 30.08.2012 Z. Zaharieva 28

29. 29 Z. Zaharieva CERN, 30.08.2012 MMP Interfaces with Naming DB Established the codification process for equipment types (Group Coding Officer) Established the codification process for equipment types (Group Coding Officer) Being applied in practice by: TE-CRG, TE-VSC, BE-CO Being applied in practice by: TE-CRG, TE-VSC, BE-CO Improve the functionalities of the Naming Portal Improve the functionalities of the Naming Portal To ease the search of equipment codes To ease the search of equipment codes Single source of equipment codes Single source of equipment codes

30. 30 Z. Zaharieva CERN, 30.08.2012 MMP Interfaces with Layout DB Established the process for the data management integration between the Assets Maintenance and Layout domains Established the process for the data management integration between the Assets Maintenance and Layout domains The CMMS team and the Layout responsible (Pascal Le Roux) have worked on improving the integration between Infor EAM and Layout DB The CMMS team and the Layout responsible (Pascal Le Roux) have worked on improving the integration between Infor EAM and Layout DB

31. Interfaces with Controls Configuration and Operational Domains MMP interfaces with the Controls Configuration domain - first user BE-CO MMP interfaces with the Controls Configuration domain - first user BE-CO Requests received for MMP interfaces with the Alarms DB (existing functionality for TIM alarms) Requests received for MMP interfaces with the Alarms DB (existing functionality for TIM alarms) To be further investigated: Logbooks and Issue management system To be further investigated: Logbooks and Issue management system Documentation & Operational Data Layout & Infrastructure Controls Configuration QA Assets Maintenance CERN, 30.08.2012 Z. Zaharieva 31

33. Maintenance Management Project Status Report Follow Up Infor EAM Light Interface Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

34. Recent system news C. Delamare EAM Light in production since mid August. EAM Light in production since mid August. More details in following slides! More details in following slides! New tool for batch update of requested start dates for Work Orders in production since mid August. New tool for batch update of requested start dates for Work Orders in production since mid August. First step towards EAM–IMPACT integration. Tested by EN/CV. First step towards EAM–IMPACT integration. Tested by EN/CV. Significant data cleaning in order to improve performance Significant data cleaning in order to improve performance More than 1.3M MTF Work Orders deleted. Over 1M custom fields removed. More than 1.3M MTF Work Orders deleted. Over 1M custom fields removed. RCM (Reliability Centered Maintenance) module evaluation licenses available since end June. RCM (Reliability Centered Maintenance) module evaluation licenses available since end June. New improved functionality concerning criticality ranking of equipment. New improved functionality concerning criticality ranking of equipment.

35. EAM Light C. Delamare EAM Light is a simple web interface that allows Infor EAM users to view, update and create Work Orders. EAM Light is a simple web interface that allows Infor EAM users to view, update and create Work Orders. The interface can be accessed by all devices with a web browser – including smartphones and tablets. The interface can be accessed by all devices with a web browser – including smartphones and tablets. EAM Light will not replace Infor EAM but will provide an alternative to users when working with Work Orders, which is the main use of the system for a lot of maintenance personnel and contractors. EAM Light will not replace Infor EAM but will provide an alternative to users when working with Work Orders, which is the main use of the system for a lot of maintenance personnel and contractors. The application can be used on its own or be called from other applications/reports to update or create new Work Orders. The application can be used on its own or be called from other applications/reports to update or create new Work Orders.

36. EAM Light C. Delamare EAM Light was put in production on 14 August and several pilot groups are currently using it: TE/CRG, EN/CV & GS/ASE. EAM Light was put in production on 14 August and several pilot groups are currently using it: TE/CRG, EN/CV & GS/ASE. How to access it: www.cern.ch/eam-light For more details about EAM Light, please see the overview presentation in EDMS 1163713. How to access it: www.cern.ch/eam-light For more details about EAM Light, please see the overview presentation in EDMS 1163713.www.cern.ch/eam-light A web version of EAM Light customized for smartphones will be released during September. A web version of EAM Light customized for smartphones will be released during September.

37. EAM Light C. Delamare

39. The web application is displayed in a “mobile friendly” format if accessed from a mobile device and also adapts to the specific devices (iOS, Android, WP) This is an example of how looks from an IPhone. Under development

41. Maintenance Management Project Status Report Follow Up Resources Summary and Outlook Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

42. Resources Summary & Outlook – Budget I. Rühl EN MMP budget 2012BC 54027 Maintenance document management24,000 BPMN maintenance training (C. Braesch/Univ. H. Savoy)7,300 Technical student A. Rosemann6,500 Equipment for fellows and FSU8,000 MFIO set up (Printer, office supplies etc.)3,000 Consulting 'Maintenance strategy' (A. Stuber)3,000 Consulting maintenance best practice 'Documentation'8,000 Total59,800 For the continuation of the MFIO office (1FSU), the crucial development and implementation of maintenance documents, the possibility to hire technical students and to provide specific trainings and seminars an annual budget of 160 kCHF shared by the EN and TE and BE(!) department will be necessary. TE MMP budget 2012BC 99003 Consulting ‘BPMN maintenance application’(BalticBerg)5’000 MFIO set up (Furnitures etc.)3’000 FSU Engineer36’000 Total44,000 GS operation budget 2012BC Maintenance Infor EAM40,000 New licences or modules13,000 Consulting 'Infor EAM' or BO9,000 PJAS33,000 Others8,000 Total103,000 Expected increase in Infor EAM developments may trigger the need of additional budget for licenses, consultancy work etc. in the GS department. GS MMP project budget?!

43. Resources Summary & Outlook – Manpower I. Rühl Staff GS-ASE Tahar Klabi since November 2011 Staff GS-ASE-EDS-2012-78-LD (SB today) Fellow GS-ASE Ada Alexandre-Metola since January 2012 Fellow EN-HE Joaquim Sylvestre since June 2012 Fellow TE-CRG Javier Ruiz Cabezas since July 2012 Techn. Students (PURESAFE) DG-DI since January 2012 Techn. Student EN-HE Adrian Rosemann since March 2012

44. Additional Manpower Request I. Rühl TE 4 FTEs (staff operators/technicians/secretaries; FSU) 1 QA Engineer / MFIO (Portuguese Trainee program) EN 1 Maintenance Engineer (Portuguese Trainee program) BE To be defined

46. Maintenance Management Project Status Report Follow Up AOB Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

47. Bulletin article Article is based on an interview of the MMP team done by Antonella Rosso Article is based on an interview of the MMP team done by Antonella Rosso Thank you for your approvals Thank you for your approvals Article with the requested corrections shall be published in the issue of the 10.09.2012 Article with the requested corrections shall be published in the issue of the 10.09.2012

48. Maintenance Workshop 2013 First workshop was held at Soleil, Saclay in November 2011 First workshop was held at Soleil, Saclay in November 2011 45 participants from Soleil, Cells, CERN, LMJ, ESRF, MAXLAB, IPNO, CPO, Diamond 45 participants from Soleil, Cells, CERN, LMJ, ESRF, MAXLAB, IPNO, CPO, Diamond 2 x 0.5 days plenary session + 0.5 day visits 2 x 0.5 days plenary session + 0.5 day visits Next workshop proposed at CERN Next workshop proposed at CERN target date October 2013 (with a bit of distance to the open days) target date October 2013 (with a bit of distance to the open days) expected participation from synchrotron and fusion facilities, possibly 50-80 participants expected participation from synchrotron and fusion facilities, possibly 50-80 participants length 2 days - 2 x 0.5 days for plenary sessions, 0.5 days for working group sessions complemented by 0.5 days for visits length 2 days - 2 x 0.5 days for plenary sessions, 0.5 days for working group sessions complemented by 0.5 days for visits

49. Maintenance training Management training - addressed to the maintenance managers, section leaders, etc. Management training - addressed to the maintenance managers, section leaders, etc. Introduction to the main principles of maintenance management Introduction to the main principles of maintenance management Introduction to the CERN maintenance management framework Introduction to the CERN maintenance management framework length 1-2 days, several sessions to be programmed for 2013 length 1-2 days, several sessions to be programmed for 2013 HR has signalled their support for the course management HR has signalled their support for the course management Search of external trainer under way Search of external trainer under way Planning: choice of trainer before end 2012, preparation of course Jan-Mar 2013 Planning: choice of trainer before end 2012, preparation of course Jan-Mar 2013 Technical training Technical training Various methods will be combined – teaching, tutoring, self-learning Various methods will be combined – teaching, tutoring, self-learning Training modules will be developed by the MFIO alongside with the advancement of the development and implementation Training modules will be developed by the MFIO alongside with the advancement of the development and implementation

51. Maintenance Management Project Status Report Follow Up Conclusion Pierre Bonnal DG-DI Christophe Delamare GS-ASE Marine Gourber-Pace BE-CO Damien Lafarge EN-HE Christophe Mugnier TE-EPC Goran Perinić TE-CRG Regis Pilon TE-EPC Ingo Ruehl EN-HE Eric van Uytvinck EN-EL Zornitsa Zaharieva BE-CO EDMS Maintenance Management Project Status Report 29 th May 2012 Follow up 30 th August 2012

52. Conclusion 1/2 I. Rühl Need MMP steering board approval for Need MMP steering board approval for MFIO concept and organization and that main actors can continue with their new tasks MFIO concept and organization and that main actors can continue with their new tasks Annual MMP budget by EN, TE and BE increased to 160 kCHF as from 2013 Annual MMP budget by EN, TE and BE increased to 160 kCHF as from 2013 MMP will lead to increased need of Infor EAM licenses, maintenance, etc. – GS MMP project budget?! MMP will lead to increased need of Infor EAM licenses, maintenance, etc. – GS MMP project budget?! Need enhancement by the MMP steering board to Need enhancement by the MMP steering board to Promote MFIO Promote MFIO Promote maintenance specific roles in the equipment groups (GQMO, GMIO, GMCO,GSPO) Promote maintenance specific roles in the equipment groups (GQMO, GMIO, GMCO,GSPO)

53. Conclusion 2/2 I. Rühl MMP team proposes that the use of smart phones and tablets is harmonized CERN wide as it is done with portable phones MMP team proposes that the use of smart phones and tablets is harmonized CERN wide as it is done with portable phones Moving from rather theoretical work to crucial practical work Moving from rather theoretical work to crucial practical work  active role by GS-ASE  close and active collaboration with external services - naming and layout service; EDMS; IMPACT etc.