The Elsmar Cove Forum and Site Map The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page

Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > FMEA and Control Plans


The Elsmar Cove Forum SideBar!
Monitor the Forum
Monitor New Forum Posts
New Threads Feeds
RSS FeedRSS Feed
Sponsor Link










$ Contributor Forum Access
Courtesy Quick Links

Links that Elsmar Cove visitors will find useful in your quest for knowledge:


Howard's International Quality Services

Atul's Symphony Technologies

Dave Scott's Scott Quality Solutions

Praxiom Research Group


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest Portal

IEST - Institute of Environmental Sciences and Technology

ASQ - American Society for Quality


All the Important Standards and Related Web Sites in the World
Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 1 votes, 5.00 average. Display Modes
  #1  
Old 20th April 2002, 05:56 AM
Andrews Andrews is offline
Involved - Posts

Registration Date: Oct 2001
Location: Chennai - India
Age: 32
 
Posts: 293
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 39
Karma: 43
Andrews has less than 100 Karma points so far.
Let Me Help You What should the FMEA Occurence Rating be based upon?

Sub : Occurence rating
Should occurrence rating be based on the no. of times a failure occurs or no. of non-conforming parts i.e if a particular undersize problem had occurred twice when running a batch of 10,000 components and if on segregation we found 2000 components non-conforming then should we take the failure rate as 2/10,000 thereby assigning occurrence rating of 5 or should we take the failure rate as 2000/10000 ,thereby getting an occurrence rating of 10.Likewise an undersize problem could have occurred 10 times when running 10000 nos. but on segregation found only 100 pieces.In this case should the failure rate be taken as 10 / 10000 i.e occurrence rating of 7 or take failure rate as 100/10000 nos. i.e occurrence rating of 10.
Reply With Quote

Sponsored Links
  #2  
Old 20th April 2002, 08:52 AM
Atul Khandekar's Avatar
Atul Khandekar Atul Khandekar is offline
Forum Administrator

Registration Date: Mar 2000
Location: Pune, India
Age: 47
 
Posts: 1,073
Thanks Given to Others: 83
Thanked 84 Times in 55 Posts
Karma Power: 90
Atul Khandekar has disabled his/her Karma.
Send a message via Skype™ to Atul Khandekar
Ten

Andrews,

Is it 2 out of 10000 or 2 out of some sample size? In any case I think you should take the maximum number that you found (in this case after segregation) to decide the occurence rating. You would get an occurence rating of 10.

Occurence must always be seen in conjunction with detection. Segregation or 100% inspection would be an inefficient and expensive method of detection. If you are doing sampling or SPC, you should be able to get a close enough estimate (PPM) of non-conforming.
-Atul.
Reply With Quote
Sponsored Links

  #3  
Old 20th April 2002, 01:36 PM
Randy Benedict
Unregistered Guest

 
Posts: n/a
Default

Atlu,

Occurance happans before detection, therefore detection can't be assumed when rating occurance?

The detection may be the best in the world, but it only detects what has already occurred.

To reduce an occurance rating don't we need to implement improvement on the front end as opposed to the rear end (detection?)
Reply With Quote
  #4  
Old 20th April 2002, 03:46 PM
db's Avatar
db db is offline
Where's the shall?

Registration Date: Jul 2001
Location: Plymouth, MI
Age: 53
 
Posts: 2,202
Thanks Given to Others: 208
Thanked 166 Times in 128 Posts
Karma Power: 129
Karma: 2579
db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.db is appreciated, and has over 1700 Karma points.
Default What do you want to solve?

Andrews, I think you are mixing data (if I understand you properly). Here is the data as I see it:

10000 components
2000 nonconforming parts

2 process deviations (which lead to the 2000 n/c parts)
? possible process deviations

If you use the 10000 components, then your comparison must also be in components. If you are going to compare the number of process deviations, then you must have something to compare it with, for example the number of possible deviations. Let me explain.

Let’s say you produced 10 million parts. You had one process deviation that resulted in 100% of the parts being rejected. Would you say you had 1 deviation in 10 million parts? Probably not, it just would not make sense.

If your FMEA is looking for the number of possible deviations, then use the 2 versus what ever the number of runs.

One last thing. Normally, FMEAs are developed prior to the manufacture. The historical data can then be used to test the validity of the FMEA
__________________
Dave B (the other Dave)
Reply With Quote
  #5  
Old 22nd April 2002, 07:38 PM
Udawantsaraf Udawantsaraf is offline
Inactive Registered Visitor

Registration Date: Apr 2002
Location: Pune
Age: 46
 
Posts: 1
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 31
Karma: 10
Udawantsaraf has less than 100 Karma points so far.
Send a message via Yahoo to Udawantsaraf
Laughing Quality Assurance Supervisor


I would like to know details about
ISO 9000 , 90001, 9002, 9003, 90004 and 9005
Is that depends on type of industries ? If yes let me know which standards are using for which type of industies.

Narhari
Reply With Quote
  #6  
Old 23rd April 2002, 08:21 AM
D.Scott's Avatar
D.Scott D.Scott is offline
Super Moderator

Registration Date: Feb 2001
Location: Wellington, OH USA
Age: 69
 
Posts: 1,604
Thanks Given to Others: 80
Thanked 289 Times in 172 Posts
Karma Power: 149
Karma: 4082
D.Scott is appreciated, and has over 1700 Karma points.
D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.D.Scott is appreciated, and has over 1700 Karma points.
Send a message via Yahoo to D.Scott
Default Udawantsaraf

Try this link for some good background on what ISO 9000 is and how it can apply to a your company:

http://www.iso.ch/

This is another good link:

http://www.qualitydigest.com/html/iso9000.html

If you are an automotive company, look at TS16949.

Hope this gives you enough information to get you started.

Dave
Reply With Quote
  #7  
Old 23rd April 2002, 10:20 AM
Sam's Avatar
Sam Sam is offline

Registration Date: Sep 1999
Location: Oklahoma
Age: 67
 
Posts: 1,437
Thanks Given to Others: 1
Thanked 29 Times in 17 Posts
Karma Power: 90
Karma: 1020
Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.Sam is appreciated, and has over 900 Karma points.
Default

Andrews,

"Occurrence is the likelihood that a specific cause /mechanismof failure will occur".

The fact that that you had two failures during the run and 2000 after sorting only indicates that you chose the wrong occurrence number.

You chose a particular Occ. no. based on something, past history, detection process in place or a "gut feeling". This was found to be incorrect during the sorting process.
The information you gathered during sorting is not used to change the Occ. no., it should be used to improve the process.
__________________
Sam Goody
Reply With Quote
  #8  
Old 27th May 2002, 04:03 AM
Andrews Andrews is offline
Involved - Posts

Registration Date: Oct 2001
Location: Chennai - India
Age: 32
 
Posts: 293
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 39
Karma: 43
Andrews has less than 100 Karma points so far.
Question

I feel the thread is going in a different direction. Maybe because I did not project my problem properly.Let me explain my problem with a hypothetical example.

Example :Let us assume that we work from 8.30 a.m to 5.00p.m (8hrs with an 1/2 hr lunch break) and that 'X' job was running from 8.30 a.m on 21.03.2002 after setting approval and we had detected a hole undersize problem during the hourly inspection (DETECTION method) that was conducted at 11.30 a.m whereas during 10.30 inspection we did not have this failure.Since we keep the items that ran between the last hourly check and the present check separately,we were able to quarantine the quantity between 10.30 inspection and 11.30 inspection.So maximum number of non-conforming products is the quantity that will run between 10.30 check and 11.30 check (say 1000 nos.).After correcting the problem we ran the machine till 2.30 p.m without a problem.But at 2.30 hourly inspection we detected the SAME problem.We quarantine the quantity between 1.30 inspection and 2.30 inspection.Let us say we again got 1000 defective pieces.We correct the problem and run this machine till 9.00 next day without this or any other problem.Totally we have got the same failure (hole undersize) twice during the production run of 10000 pieces and the total no. of defectives is 1000+1000=2000nos.
Based on this case what is the occurence rating I should give and why?
Reply With Quote
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > FMEA and Control Plans

Bookmarks


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
PFMEA rating - Occurence Rating and Detection Rating - Some clarification Chennaiite FMEA and Control Plans 8 9th September 2009 11:47 AM
The Origin of the FMEA Detection Rating phelix FMEA and Control Plans 7 14th February 2008 04:39 PM
Medical Device FMEA Occurence Rating Scale Justification jenna FMEA and Control Plans 3 5th May 2007 01:10 PM
FMEA Severity Rating - Will a Process Design Change also Change the Severity Rating? sowmya FMEA and Control Plans 21 30th August 2006 09:20 AM
Supplier Analysis - Rating using an FMEA - Anyone ever try something like this? Andy Nutt Supplier Quality Assurance and other Supplier Issues 11 18th October 2004 12:18 PM



The time now is 10:43 PM. All times are GMT -4.
The time zone can be changed in your UserCP --> Options.



   

All Y'All Come Back Now, Y' Hear?

Made With A Mac! FreeBSD OS Powered by Apache!
Using php4 Forums provided and maintained by Marc Smith Database by MySQL

FAIR USE and CORRECTNESS NOTICE: This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe herein constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit to those who have expressed a prior interest in receiving the included information for research and educational purposes. For more information go to: http://www.law.cornell.edu/uscode/17/ If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. In addition, I do not guarantee the correctness of the content. The risk of using content from the Elsmar Cove web site and forums remains with the user/visitor.

Responsibility Statement: Each person is responsible for anything they post in the Elsmar Cove forum. Neither I, Marc Timothy Smith, nor any of the forum Moderators, are responsible for the content of posts people make. Liability for post content resides with the poster as does interpretation and/or acceptance and/or use of advice by the reader.

Complaints: If you have a complaint with a post in a forum discussion thread, including Content in general, fighting, flaming, copyright infringement, defamation and/or 'slander', please use the 'Report This Post Report This Post Button button which appears at the top of every post in every thread.

Site courtesy of:
Marc Timothy Smith - Cayman Business Systems, 8466 Lesourdsville-West Chester Road, West Chester, Ohio 45069-1929 - USA
(513) 341-6272

To contact me, click the Google Voice link below, enter Your Name and Your Phone Number and Google will ring your phone and connect you for free!

The Elsmar Cove Web Site is *CopyFree*
no new posts