Identification of critical Beamline components for preventive maintenance plans at synchrotron SOLEIL CHABARD Jules, ROBERT Emmanuel, NICOLAS Christophe,

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
 Acceptance testing is a user-run test that demonstrates the application’s ability to meet the original business objectives and system requirements and.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Chapter 2 The Analyst as a Project Manager
Reliability Week 11 - Lecture 2. What do we mean by reliability? Correctness – system/application does what it has to do correctly. Availability – Be.
What is workflow?  A workflow is a structured way of defining and automating structures and procedures within an organization. What is workflow management.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
1 AMMW2013 workshop 13 d – 15 th of November, 2013 Asset management tools: use and improvement in SOLEIL – P. Betinelli Asset management tools: use and.
1 Prediction of Software Reliability Using Neural Network and Fuzzy Logic Professor David Rine Seminar Notes.
William H. Bowers – User-Centered Product Teams Torres 4.
Skill Management for accelerator operation and maintenance. Hiromi Inokuchi National Institute of Radiology Sciences, Japan
Software Engineering CS3003 Lecture 3 Software maintenance and evolution.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Slide 1 Teams l Most products are too large to be completed by a single software professional with the given time constraints l You will work within a.
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Formal Methods in Software Engineering
Developing Business/IT Solutions Chapter 12 McGraw-Hill/IrwinCopyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Computer Software Types Three layers of software Operation.
Oktalia Juwita, S.Kom., M.MT. SYSTEMS DEVELOPMENT Dasar-dasar Sistem Informasi – IKU1102.
EVA Leonardo Project Synthesis of Intermediate Results February 2011 mettre logo europe.
1 September 2007 – Tango Meeting – A.Buteau ICALEPS 2005 Status report SOLEIL September 2007.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Seungyu Rah (Pohang Accelerator Laboratory, POSTECH, Korea) Nov
Current Status of the Tracking Trigger Software Andrew W. Rose.
SDLC and Related Methodologies
Six Sigma Greenbelt Training
GCE Software Systems Development
Configuration Management
22/04/2018 SOLEIL PROGRESS IN PROVIDING REMOTE DATA ANALYSIS SERVICES Majid OUNSY: Data Analysis Software Project Leader.
Software Risk Management
Testing the System.
Machine operation and daily maintenance management in SOLEIL
Software Engineering (CSI 321)
Introduction Project Management.
WP13: Access to Plasma Beam testing facilities
Chapter 18 Maintaining Information Systems
PLC-based control systems at SOLEIL - ICALEPCS 2017
Configuration Management
The Systems Engineering Context
Software Reliability Definition: The probability of failure-free operation of the software for a specified period of time in a specified environment.
Managing the System PPT SOURCE : Shari L. Pfleeger Joann M. Atlee.
The Project Management Framework
FMEA.
FMEA PROCESS FLOW Causes/ failure mechanisms Product definition
Hélène ROZELOT, Y. M. Abiven, S. Blanchandin, J. Chabard, C
the CERN Electrical network protection system
Failure mode and effect analysis
Operation Reliability of SSRF and upgrade plan at SSRF
Experimental Facilities Planning
Chapter 1: Introduction
Software Engineering (CSI 321)
Introduction to Software Testing
Software Testing and Maintenance Maintenance and Evolution Overview
Chapter 13 Quality Management
Inspection and Review The main objective of an Inspection or a Review is to detect defects. (Not for Giving Alternative Solutions) This activity and procedure.
CS240: Advanced Programming Concepts
Welcome & Opening Remarks
Quality Measurable characteristic Cyclomatic complexity Cohesion
Introduction Project Management.
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 1 Mumtaz Ali Rajput +92 – 301-
SDLC and Related Methodologies
Failure Mode and Effect Analysis
Towards SOLEIL unique portal
Configuration management
Ian Evans SSRL Safety Office
Rapid software development
Presentation transcript:

Identification of critical Beamline components for preventive maintenance plans at synchrotron SOLEIL CHABARD Jules, ROBERT Emmanuel, NICOLAS Christophe, BOZEK John, GOURHANT Patrick, LENER Robin, CHAVAS Leonard M.G., ROZELOT Hélène

OUTLINES: Introduction Criticality matrices applied for PLEIADES and PROXIMA1 beamlines Conclusion and outlooks

But some technical convergences exist through 5 clusters: Introduction No dedicated maintenance service. However, maintenance plans already exist at SOLEIL. Each group is in charge of their own equipment. If this maintenance “culture” is more formal in the Engineering and Accelerators Division (corrective or preventive), it is not so usual at the level of the beamlines. But some technical convergences exist through 5 clusters: Hard X-ray spectroscopy (6 BLs) Soft X-ray spectroscopy / photoemission (5 BLs) Imagery (6 BLs) Diffraction (8 BLs) Gas, liquid, solid spectroscopy (4 BLs) 29 Beamlines 29 independent laboratories 29 different ways of operation

Introduction Could we find a unique procedure or tool, which could suite all the beamlines and help them in their maintenance plan? Apprenticeship of Jules Chabard (2ème année DUT Qualité, Logistique Industrielle et Organisation) under the supervision of H. Rozelot He interacted with two different beamlines : PLEAIDES and PROXIMA1. He introduced to the beamline the concept of criticality. He worked with the beamline teams and helped them build their own criticality matrix .

PROXIMA 1 and PLEIADES Beamlines PROXIMA 1 (hard X-ray) PLEAIDES (soft X-ray) Macromolecular crystallography beamline Spectroscopy in the diluted phase “Fixed geometry” with one optical branch and with one experimental endstation The users bring just their samples Average users beamtime few hours Three optical branches with three permanent endstations, with two open ports for users set-ups Multiple interchangeable sources (gas cell, nanoparticles beam, clusters beam, liquid jet, oven) Users can bring their set-ups as well Average users beamtime 5 days or more

Criticality matrix for scientists To keep it simple (and not scare the scientists), the detection factor is dropped (no calculation of a risk priority number). We will focus only the criticality. Criticality = Occurrence (O) * Severity (S) O\S Minor (1) Moderate (2) Critic (3) Catastrophic (4) Occurrence d (4) 4 8 12 16 Occurrence c (3) 3 6 9 Occurrence b (2) 2 Occurrence a (1) 1 With Occ. a < Occ. b < Occ. c < Occ. d Class equipment Type of maintenance 3 Critic Strong preventive actions 2 Standard Preventive action 1 Ordinary Corrective action or run to failure

Criticality Matrices The first step is to list equipment specific to the endstations. Before the endstations, the support groups (ECA, ICA, Vacuum, etc.) have their own maintenance plans !! For many beamlines, including PLEIADES, the scientific equipment is not in a database !! Proposed by Jules Equipment Nb Spare S O Criticality PLEIADES It is also important to know: nb of channels the nb of channels in use Spare in stock Spare belonging to endstations Time needed for a return to service weighted criticality

Criticality Matrices X The first step is to list equipment specific to the endstations. Before the endstations, the support groups (ECA, ICA, Vacuum, etc.) have their own maintenance plans !! For many beamlines, including PLEIADES, the scientific equipment is not in a database !! Proposed by Jules Equipment Nb Spare S O Criticality PROXIMA 1 It is also important to know: Spare in stock Spare belonging to support groups Age of equipment Nb of failures X True Occurrences

Criticality Matrices PLEIADES PROXIMA 1 O \ S Minor (1) Moderate (2) Critic (3) Catastrophic (4) > 2 times / year (4) 4 8 12 16 1 à 2 times / year (3) 3 6 9 3 à 4 times / 10 years (2) 2 Unlikely (1) 1 PLEIADES O \ S No influence on the experiment (1) Downgraded experiment (2) Very downgraded experiement (3) Experiement Stoped(4) [0,75 ; 1 et +] 4 8 12 16 [0,5 ; 0,75] 3 6 9 [0,25 ; 0,5] 2 [0 ; 0,25] 1 PROXIMA 1 The flexibility of the criticality matrix can suit the needs of very different beamlines

PROXIMA 1 Criticality Matrix

PLEIADES Criticality Matrix Really helped to formalize where the problems could be. But still mainly on memories of the staff and feelings!!

Conclusions Criticality matrices are not scary, even for beamline scientists They are flexible enough, in their building, to fit the specific requirements of different beamlines Need to identify and include the equipment in the CMMS software (Manpower)

Outlooks For PLEIADES: Tests procedures for critical equipment need to be written Start to work on maintenance plan document

Outlooks This work was presented to different internal meetings: To cluster 5 beamlines To the executive coordinators from the EDA To the ‘groupe fonctionnement” from the EDA To the quality cell of SOLEIL It has been very well received Cluster 5: Beamlines are interested, but scared of the work needed to identify and include the equipment in the CMMS software To evaluate this work, a summer job (1 month) was dedicated to include all the equipment of PLEIADES endstations and sources in the CMMS. This highlighted two things: It is very difficult for a non-beamline staff (and even for new beamline staff, who do not know the history of the beamline) to include the equipment, but it is possible and will also benefit the other beamlines (Spares available at SOLEIL). The homogenization in the definition of equipment gets lost with time (a power supply could have various names, even including the group name: RF_powersupply)