Document - european association of national research facilities

Recommendations

Info

ALBA: Maintenance at ALBA Synchrotron (L. Miralles) Lluis Miralles presented the organization of ALBA’s “Technical Support” division. The division is split into four “sections”: Infrastructure, R&D, Vacuum and Transversal. The group responsible for all maintenance at ALBA is in the Transversal section, and comprises only six technicians. Note that the Experiments division does not have any dedicated technicians. Maintenance operations are subcontracted, but maintenance management (scheduling of operations and so on) is handled in-house. Lluis Miralles described the features of the PRISMA 3 software used. This program features many of the typical functions of a CMMS, including topologies, stock, process workflow and statistics. He concluded with a presentation of conditional maintenance based on monitoring a number of parameters (pump pressures, motor vibrations, and so on) to trigger alerts that result in either preventive maintenance actions or warnings about potential breakages (predictive maintenance). SOLEIL: Maintenance & Reliability for the Process (P. Betinelli & L. Manciet) Pascale Betinelli started by explaining what SOLEIL wants from a CMMS and how it is used in practice. MAINTIMEDIA is an assembly of several modules (topology, stock, purchasing, process workflow and statistics). While each of the modules can be used independently, this approach is somewhat restrictive. The modules are in fact interconnected and the CMMS should be used as widely as possible to make the best use of the system. This implies that users must thoroughly understand and analyze their maintenance processes in order to make the best use of the CMMS. Pascale then displayed some data extracted with BO and showed that the use of the CMMS as a maintenance tool is very variable. She also mentioned other tracking tools used at SOLEIL, including MANTIS bug tracker, Excel, ELOG and MS Project. She emphasised the difficulty of imposing the use of a single tool or even defining rules for using each tool. Laurent Manciet then presented some more technical aspects of MAINTIMEDIA, including the Oracle database, the number of licences, the access rights defined, network architecture, and the technical problems encountered in particular last year (primarily slow database access). In their joint conclusion, Pascale and Laurent highlighted the general difficulties in using a CMMS, a program with complex functions that require users to define their requirements and processes properly beforehand. For this new modus operandi to be successful, teams must overcome their resistance to change. DIAMOND: Buildings & utilities maintenance – Contracted service or in-house staff (L. Walters) Lee Walters presented the organization of DIAMOND’s Support division, which includes the group responsible for infrastructure maintenance. He explained that maintenance operations, which had previously been contracted out, are now managed in-house, having fired the former contractors on site. He reviewed this situation, which has the advantage of enabling maintenance teams to be managed directly and makes the most of in-house resources. However, it requires considerable effort to set up, and also offers less flexibility in terms of available resources, in that external staff are required to handle peak loads. CERN: Maintenance for CERN’s cryogenic installations (S. Knoops) Sigrid Knoops presented the cryogenic equipment in use on the LHC, noting that the devices are prototypes designed by CERN. She reviewed how maintenance is organised, and who does what, depending on the complexity of operations: - Straightforward adjustments (e.g. setting a parameter) are handled by CERN in-house operators. Likewise, much more complex operations that require a redesign or that involve manufacturing new parts are handled in-house. - Conversely, standard operations (repairs, replacements, corrective and preventive maintenance) are contracted out. Her slides also included various operating statistics. INFORM EAM asset management software is used (http://www.infor.com/solutions/eam/). Data are extracted with Business
Objects, and the database is linked to the technical documentation system (Engineering Data Management System or EDMS). LASER MEGAJOULE: Maintenance at the facility (H. Graillot & I. Granet) Alongside synchrotrons, LMJ is a representative of another class of major research infrastructure (lasers). Although the infrastructure is still under construction, maintenancerelated aspects are already being taken into account. Almost 100,000 items of equipment have already been entered in the INFOR EAM database, ranging from ordinary devices to more complex systems such as the “target chamber“ with its 10-metre diameter. Hervé Graillot described the tool’s features (topology, stock, purchasing, process workflow and statistics) and explained that the CMMS is interconnected with the JIRA project tracking tool and the SIROCO technical database. Business Objects is also used to extract data which is analyzed to optimise maintenance procedures. In conclusion, Hervé noted that the CMMS as a whole (including purchasing, work order tracking and so on) is used throughout LMJ. He also noted that LIL, the Laser Integration Line used as a prototype for Laser MegaJoule, had used a different CMMS that its operators had found too complex to be workable. SOLEIL: Buildings & Utilities Maintenance (T. Didier) Thierry Didier, in charge of utilities at SOLEIL, presented the activities managed using the CMMS (general services, fluids and electricity), for monitoring and maintenance operations in particular. Certain preventive maintenance operations are mandated by regulations. This preventive maintenance entails drawing up work instructions, from which work orders are generated so as to schedule the group’s activities and required resources. Nonconformity sheets are drawn up where applicable. Thierry then presented the data extracted using BO and used for management purposes by team leaders. Lastly, he mentioned the motivational difficulties encountered and the steps taken to resolve them, including simplifying the technical data entered in the database, using work instructions suited to the group, and making extensive use of Business Objects. ESRF: Maintenance of Technical Infrastructures (T. Marchial) Thierry Marchial briefly presented the activities of the 30-strong Buildings and Infrastructure group, part of ESRF’s Technical Infrastructure Division. He described the equipment managed in the CMMS (using CARL Master software). This equipment is classified in 3 levels: - Equipment that could cause beam losses (accelerator and source) - Equipment that could affect users (beamlines and mains power) - Other equipment. He then reviewed the outsourced maintenance contracts managed in the CMMS (which do not include “primary maintenance” or regulatory inspections). These account for: - 33 documents - 4-year contracts, revisable annually - 14,000 hours of work on site in 2011. Contracts are managed using the Plan-Do-Check-Act (PDCA) quality system. Each incident is analyzed by the subcontractor and the Buildings and Infrastructure group, and corrections are made: - Identification of expected performance, - Quality control and tracking (in particular through indicators). A bonus/penalty system has also been set up for subcontractors. Orsay Proton Therapy Centre: Maintenance and reliability (S. Meyroneinc) Samuel Meyroneinc briefly presented the principles of proton therapy and the facilities at the Orsay Proton Therapy Centre (CPO). He emphasized the operational constraints (medical environment) which restrict maintenance to scheduled slots, and the need for a decisionmaking structure to analyze the potential impacts of maintenance work and how treatment results may be affected. He explained how reliability and maintenance can result in
Page 1: Maintenance and Reliability Worksho
Page 5 and 6: SECOND ROUND TABLE: What common ind

Document - european association of national research facilities

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?