« FIABILISATION & INDUSTRIALIZATION OF RISK ANALYSIS METHODS » A. MILI 1 ; S. HUBAC 1 ; S. BASSETTO 2 ; ;

Slides:



Advertisements
Similar presentations
RISK MGMT. Risk Inspection Risk Assessment Risk Analysis LET US CREATE A VALUE FOR BETTER TOMORROW RISK MANAGEMENT : TODAYS BUSINESS ESSENTIAL Our Strength.
Advertisements

Rolls-Royce supported University Technology Centre in Control and Systems Engineering UK e-Science DAME Project Alex Shenfield
Dependability analysis and evolutionary design optimisation with HiP-HOPS Dr Yiannis Papadopoulos Department of Computer Science University of Hull, U.K.
Medical Device Software Development
CIS 376 Bruce R. Maxim UM-Dearborn
P roblem S olving I nnovator Solving Tomorrows Problems Today Overview of how the 5 why automatically generates an FMEA & Control Plans 5 Why - FMEA Relationship.
Applications of Wireless Sensor Networks in Smart Grid Presented by Zhongming Zheng.
Failure Mode and Effect Analysis
Reliability Risk Assessment
Root Cause Analysis Presented By: Team: Incredibles
Popcorn Sample PFMEA: Process Flow
Fundamentals of Information Systems, Second Edition
Jw consulting SAP R/3 QM Workshop Rheinfelden Kurt Fantes Prototyp jw LIMS.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
Tony Gould Quality Risk Management. 2 | PQ Workshop, Abu Dhabi | October 2010 Introduction Risk management is not new – we do it informally all the time.
Lucas Phillips Anurag Nanajipuram FAILURE MODE AND EFFECT ANALYSIS.
Barry Murash MBBit Nortel 2007
F.M.E.A (Failure Mode and Effect Analysis)
SISIFO-GAS A COMPUTERIZED SYSTEM TO SUPPORT SEVERE ACCIDENTS TRAINING AND MANAGEMENT WGRisk Workshop March 29-31, 2004 Köln, Germany César Serrano.
Problems with reuse – Increased maintenance costs; lack of tool support; not-invented- here syndrome; creating, maintaining, and using a component library.
 Centre National de la Recherche Scientifique  Institut National Polytechnique de Grenoble  Université Joseph Fourier Laboratoire G-SCOP 46, av Félix.
FP OntoGrid: Paving the way for Knowledgeable Grid Services and Systems WP8: Use case 1: Quality Analysis for Satellite Missions.
What are the Benefits? Action AKA TPM, Total Preventative Maintenance Total Productive Maintenance Breakdowns 1 Setup / adjustment 2 Idling / minor stoppages.
TQM TECHNIQUES BENCHMARKING Target key areas for improvement within operations – Increase productivity, competitiveness, and quality – Quality results.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Analyze Opportunity Part 1
BELU, IONESCU, MISZTAL - Computer Aided Design Solution Based on Genetic Algorithms for FMEA … Amsterdam, 06 August 2015 COMPUTER AIDED DESIGN SOLUTION.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
Wednesday, 24 September 2008 P. David, V. Idasiak & F. Kratz PRISME Institute Team-project MCDS Reliability in Design: FMEA Derived from UML/SysML models.
Chapter 11 Analysis Concepts and Principles
Lecture 3 Software Engineering Models (Cont.)
1 Risk analysis for improving production ramp-up Bassetto 1, Mili 1, Siadat 2, Tollenaere
QUALITY RISK MANAGEMENT RASHID MAHMOOD MSc. Analytical Chemistry MS in Total Quality Management Senior Manager Quality Assurance Nabiqasim Group of Industries.
An Introduction to Software Engineering
RCM Tools Histogram Pareto Chart Cause and Effect Diagram FMEA.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
1 Improving the Risk Management Capability of the Reliability and Maintainability Program An introduction to the philosophy behind the AIAA S-102 Performance-Based.
Fault-tolerant Control Motivation Definitions A general overview on the research area. Active Fault Tolerant Control (FTC) FTC- Analysis and Development.
Software Engineering Lecture # 1.
Herriman High Computer Programming 1A Software Development Cycle Things to Know.
1 Experience from Studies of Software Maintenance and Evolution Parastoo Mohagheghi Post doc, NTNU-IDI SEVO Seminar, 16 March 2006.
Completing the Loop: Linking Software Features to Failures 31 July 2003 Copyright © 2003, Mountain State Information Systems, Inc. All rights reserved.
Using Total Quality Management Tools to Improve the Quality of Crash Data John Woosley Louisiana State University.
Building usable software through early testing. Objective Show the value of testing from the beginning of the development cycle. Consensus in the industry.
METODOLOGI SIX SIGMA PERTEMUAN 13 CONTROL PHASE
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
10 TOTAL PRODUCTIVE MAINTENANCE (TPM) Zulfa Fitri Ikatrinasari, Dr.
Fault-tolerant Control Motivation Definitions A general overview on the research area. Active Fault Tolerant Control (FTC) FTC- Analysis and Development.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
Failure Modes, Effects and Criticality Analysis
FAILURE MODE EFFECTIVE ANALYSIS. Introduction Failure Mode Effect Analysis is an analytical technique that goes in for combining Technology and Experience.
1 Approaches in the Area of Measurement Uncertainties.
Artificial Intelligence In Power System Author Doshi Pratik H.Darakh Bharat P.
Process engineering Quality controls.
Six Sigma Greenbelt Training
Software Project Configuration Management
An Efficient Algorithm for Incremental Update of Concept space
Experiences Informal Sector in National Accounts
FMEA PROCESS FLOW Causes/ failure mechanisms Product definition
FMEA PROCESS FLOW Determine Causes/ mechanisms failure
Failure mode and effect analysis
Quality Risk Management
GE 6757 TOTAL QUALITY MANAGEMENT
Software Quality Engineering
The Certified Quality Process Handbook Chapter 22: Preventive Action
The benefits to perform FMEA
Failure Mode and Effect Analysis
PFMEA Summary Process Steps
Chapter 14 Risk and resilience.
Presentation transcript:

« FIABILISATION & INDUSTRIALIZATION OF RISK ANALYSIS METHODS » A. MILI 1 ; S. HUBAC 1 ; S. BASSETTO 2 ; ; 1 STMicroelectronics – 850 rue Jean Monnet, Crolles Cedex. 2 Laboratoire des Sciences pour la Conception, l'Optimisation et la Production - ENSGI-INPG, 46 Avenue Félix Viallet, Grenoble. We are at early phase of deployment. The futur model for risk management is complete. It consist of capitalizing in a data base the information concerning breakdowns and the risk analysis data in the objective of facilitating their exploitation. We have chosen a pilot workshop to start deployement and test the level of data transfert from CMMS data base to risk management system. We search after the test period to duplicate this … I- Introduction Context: - Very important equipment cost - Wafer production costs - Variability of scrap number per month  Continuous control and tool improvement to achieve the objectives in term of quality and due dates.  Using powerful means of control and monitoring in real times and standard methods of risk analysis management (FMEA – Failure Mode and Effects Analysis, 8D…) Objectives: - Minimizing tool variability and remove accidental breakdowns - Deployement of the risk analysis method (FMEA) within Crolles2 alliance - Initiating a system for automatic risk analyses update according to events related to the process control in line. II- FMEA Management The aim of this study consist on setting up a risk management system within Crolles2 Alliance. Based on a standard method (FMEA), it was applied on three levels: products (FMEA Recipe ), processes (FMEA Module ) and equipment (FMEA Block Hardware ). model for all workshops and the goal is to have a standart method for all. In second step, we aim to update our risk data base with informations of defects on product, client reclaim and all data at the origin of real or imminent risk. This new method allow us to quantify the benefit of risk analysis method on process. It symplifies also the control of the actions through reports generated automatically from database. V- Conclusion Use of FDC parameters: We propose to establish the link between FDC variables and the risk detection in the FMEA to set up a function g which allows starting from the whole variables of the machine (V = {V1, V2,… Vn}), the fulfilled function (F) and the risk (R), to determine the subset of potential parameters (X) at the origin of the dysfunction. III- APPROACH - Define the priority of actions axes - Use equipment events to define real or emminent risk - Standardise the language of the three parts: FMEA, maintenance interventions and FDC- Fault Detection and Control. A prototype application was developed allowing the automatic re-evaluation of the risks analyses according to the machines breakdowns. The coding used in the CMMS and the FMEA being very similar, the automatic translation could be carried out. The test of this operation during 100 days, shows that 6670 risks were generated, 4923 were identified beforehand. Their occurrences were updated, and 1747 new risks were identified, among which some with evaluation exceeding the threshold of action's release (RPN > 125). Fig 2. Risk management model Fig 1. Scrap evolution UNSHEDULED DOWN Maintenance LITHO REPORT ( PARETO OF FAILURE) REPORT ( PARETO OF FAILURE) ENG. REPORT CMMS FMEA Report (FMEA BH) Incoherent data with FMEA Formalism Inalienable information in risk analysis Fig 3. Maintenance data and FMEA Block Hardware Fig 4. Link between CMMS date and FMEA analyses Process Tool (F) X = g (F, V, R) Silver Box V = {V 1, V 2, …, V n } Fig 5. Control parameters