Välkommen, welcome, huān yíng, welkom, Bienvenue, willkommen, fogadtatás, benvenuto, velkommen, powitanie, bem-vindo, croeso, bienvenido, vítejte Advanced.

Slides:



Advertisements
Similar presentations
24-26 July 2006EE2006 Conference, Liverpool, UK1 Dr T. Laoui 1, John ODonoghue 2 University of Wolverhampton 1 School of Engineering and Built Environment.
Advertisements

Operation & Maintenance Engineering Detailed activity description
What the Search Engines are up to Now: same ingredients different recipes Karen Blakeman RBA Information Services, UK 02 June 20141Karen Blakeman
PeopleSoft Ping David Kurtz
FAILURE MODES & EFFECTS ANALYSIS
“Workflow” in Data Access and Integration An OGSA-DAI/DAIS Perspective Mario Antonioletti EPCC
SBS FMEA Database FMEA Background SBS Database Features and Benefits
© 2001 empolis UK1 Topic Maps, NewsML and XML: Possible Integration and Implementations. By Soelwin Oo.
Debates in HE ASS 3. Aims To describe development of HE post- war To analyse the “widening participation” debate.
Pitching for finance Social Enterprise North West February 2014.
Good Salespeople johnpc ltd: John Cunningham.
‘Lean’ methodologies in facilities Approaches, effects, problems and compliance. Dave Gaster December
Where does Failure Mode and Effects Analysis (FMEA) come from?  Developed by the Aerospace industry in the1960s  Spread to the Automotive industry 
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
1 MANUFACTURING AND PRODUCTION OF BIOLOGICAL PRODUCTS (ERT 455) HAZARD ANALYSIS AND CRITICAL CONTROL POINT (HACCP) SYSTEM Munira Mohamed Nazari School.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Reliability Risk Assessment
Overview Lesson 10,11 - Software Quality Assurance
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
SIM5102 Software Evaluation
Six Sigma Quality Engineering
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.
Functional Testing.
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
Failure Mode and Effects Analysis FMEA
What is Business Analysis Planning & Monitoring?
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Software Project Management
Chapter 16 Software Quality Assurance
 Contoso is working on Wireless 1xEvDo application to handle high speed 3G application data transfer (voice, video data) in mobile phones while working.
Extreme Programming Software Development Written by Sanjay Kumar.
1 Shawlands Academy Higher Computing Software Development Unit.
Requirements Analysis
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Analyze Opportunity Part 1
Kanban/Pull System As Part of the Continuous Improvement Process at Whirlpool Corporation - Findlay.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Failure Modes Effects Analysis (FMEA). 2 Definition of FMEA Failure Modes Effect Analysis (FMEA) is a structured approach to: Predict failures and prevent.
Risk Management & Corporate Governance 1. What is Risk?  Risk arises from uncertainty; but all uncertainties do not carry risk.  Possibility of an unfavorable.
FACILITATOR Prof. Dr. Mohammad Majid Mahmood Art of Leadership & Motivation HRM – 760 Lecture - 25.
Drive by Wire – “What Will Be Its Impact On Tomorrow’s Vehicles?” Craig Stephens Ford Motor Company.
The Software Development Process
An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit V October 30 – November 1, 2002.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Failure Modes and Effects Analysis (FMEA)
Failure Modes, Effects and Criticality Analysis
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
FMEA Training.
Process engineering Quality controls.
Product Lifecycle Management
Failure Mode & Effect Analysis (FMEA)
FAILURE MODES AND EFFECTS ANALYSIS - FMEA
Software Development and Safety Critical Decisions
Software Quality Assurance
SEVERITY & PRIORITY RELATIONSHIP
FMEA.
IENG 461 – System Safety I Lecture 8 – Failure Modes and Effects Analysis (FMEA) James R. Harris, Ph.D., P.E.
Failure mode and effect analysis
Chapter 21 Software Quality Assurance
Quality Risk Management
GE 6757 TOTAL QUALITY MANAGEMENT
Välkommen, welcome, huān yíng, welkom, Bienvenue, willkommen, fogadtatás, benvenuto, velkommen, powitanie, bem-vindo, croeso, bienvenido, vítejte The following.
Chapter 21 Software Quality Assurance
Välkommen, welcome, huān yíng, welkom, Bienvenue, willkommen, fogadtatás, benvenuto, velkommen, powitanie, bem-vindo, croeso, bienvenido, vítejte The following.
RISK REDUCTION PROCESS
Reliability Calculations
Integrating TS Requirements
Failure Mode and Effect Analysis
Reliability Calculations
Presentation transcript:

Välkommen, welcome, huān yíng, welkom, Bienvenue, willkommen, fogadtatás, benvenuto, velkommen, powitanie, bem-vindo, croeso, bienvenido, vítejte Advanced Powertrain Control Symposium 9 th July /07/2013www.fmea.co.uk1

The Effective Application of FMEA Who am I? What is FMEA? Why do FMEA? Application of FMEA A Structured Approach Effective FMEA Use Software for FMEA Use an FMEA Facilitator 05/07/2013www.fmea.co.uk2

What is FMEA? Contrary to popular belief FMEA is actually an acronym for a risk analysis called Failure Modes & Effects Analysis, and not Five Men Endlessly Arguing. Failure Modes & Effects Analysis is an activity that brings minds together in a collaborative and pre-emptive way in order to avoid failure of a system! FMEA is a systematic procedure that focuses on a system(s) in order to uncover weaknesses, i.e. what can go wrong, what could possibly cause it and what are the potential effects. FMEA then focuses on these weaknesses with the objective of making them obsolete, or by reducing the likelihood of failure (or risk of failure) though the implementation of corrective methods, which in turn optimises the system. 05/07/2013www.fmea.co.uk3

What is FMEA? FMEA is a living document and if used correctly records: intellectual property weaknesses within the system quantified risk of system failure mistakes made solutions to problems responsibility for controls methods Failure are any potential errors or defects within a process, design, or part, especially ones that affect the customer, environment and law. 05/07/2013www.fmea.co.uk4

What is FMEA? 1949 – US Military (MIL-P-1649) 1963 – NASA 1965 – Aerospace Industry 1975 – Nuclear Industry 1977 – Ford Motor Company 1980 – DIN – VDA Volume – Ford, Chrysler & GM 2008 – AIAG Is universally accepted as an engineering tool 05/07/2013www.fmea.co.uk5

Why do FMEA? Cost reduction and increased profits Demand for higher quality Extended warranty periods Product liability Quality standard demands Retention of knowledge Make processes more robust Enhanced communication within the business, customer & suppliers Shorter development times Functional Safety & Reliability 05/07/2013www.fmea.co.uk6

Application of FMEA 05/07/2013www.fmea.co.uk7

Application of FMEA There are two main schools of thought about the methodology to use and which is most effective? Rose with a different name Procedure Document formats Adherence to ISO / TS Basis for ISO / TS /07/2013www.fmea.co.uk8

Application of FMEA To get the best out of FMEA you should have: Cross functional team FMEA Moderator / Facilitator Props and documentation Structured approach FMEA Software Management Support! 05/07/2013www.fmea.co.uk9

A Structured Approach 05/07/2013www.fmea.co.uk10

Effective FMEA Step 1: Visual representation of the scope 05/07/2013www.fmea.co.uk11

Effective FMEA Step 2: Runs in line with other engineering techniques, such as Function Analysis System Technique (FAST) How? Why? Effects Causes Mode 05/07/2013www.fmea.co.uk12

Effective FMEA Focus on functions provide guidance for the analysis of failures, or step 3. Loss of Voltage stimulus Corrupted Voltage stimulus Voltage stimulus when not required Signal stuck at ground Signal stuck at specified voltage Signal is corrupted Short Open Effects Causes Mode 05/07/2013www.fmea.co.uk13

Effective FMEA Step 3: Efficient construction of effective possible failure scenarios EffectsCauses Mode 05/07/2013www.fmea.co.uk14

Effective FMEA Step 4: Possible failure scenarios are displayed in a fashion that is consistent with previous steps Failure Effect(s)SFailure ModeFailure Cause(s) 05/07/2013www.fmea.co.uk15

Effective FMEA AIAG form can be unintentionally misleading Mode Causes Effects 05/07/2013www.fmea.co.uk16

Effective FMEA VDA form is logical Effects Mode Causes E=MC 2 05/07/2013www.fmea.co.uk17

Effective FMEA Step 4: Ensuring that only the controls that are currently in fruition are considered when calculating the risk 05/07/2013www.fmea.co.uk18

Effective FMEA Step 4: Analysis of the data using RPN is not just , there are 120 values that can result from S x O x D, which may not reflect criticality. 05/07/2013www.fmea.co.uk19

Effective FMEA Common sense shall prevail by looking at the risk assessment results in a different way e.g.: 05/07/2013www.fmea.co.uk20 Automotive risk model

Effective FMEA Step 5: Reduction of the risk is displayed in a Chronological order 05/07/2013www.fmea.co.uk21

Effective FMEA Create your own descriptions of the risk factors of Severity (S), Occurrence (O) and Detection (D): Reflect what you do as a business Reflect the product you make Is there a customer mandate? Using rule of thumb statements & benchmark examples Use AIAG descriptions as guidance* 05/07/2013www.fmea.co.uk22

Use Software for FMEA Due to the complexities of modern products & processes, software is essential. Many companies use MS Excel, but dedicated software can provide a visual representation of: the system analysed interfaces between sub-systems, plus inputs and outputs complex relationships between the failures 05/07/2013www.fmea.co.uk23

Use Software for FMEA In addition to this dedicated software allows the FMEA to: be filtered or colour coded according to your own criteria produce additional statistical data and additional quality documentation as a consequence Switch easily between FMEA form layouts handles variances Supports delegation and tracking of corrective measures 05/07/2013www.fmea.co.uk24

Use an FMEA facilitator Experienced FMEA facilitation will ultimately save time and make meetings more focused & constructive. An experienced FMEA facilitation minimises digression into different types of FMEA. An external FMEA facilitator may ask the stupid questions that may have been overlooked as they may be thinking outside of the box An effective FMEA records intellectual capital for the future developments (semantics) 05/07/2013www.fmea.co.uk25

Penkridge, Stafford, ST19 5TE. UK tack, thanks, xièxie, dank u wel, merci, danke, köszönöm, grazie, tak, dzi ę kuj ę, obrigado, diolch, gracias, děkuj, ďakujem 05/07/2013www.fmea.co.uk26