FMEA在生產(chǎn)管理質(zhì)量中的作用英文_第1頁(yè)
FMEA在生產(chǎn)管理質(zhì)量中的作用英文_第2頁(yè)
FMEA在生產(chǎn)管理質(zhì)量中的作用英文_第3頁(yè)
FMEA在生產(chǎn)管理質(zhì)量中的作用英文_第4頁(yè)
FMEA在生產(chǎn)管理質(zhì)量中的作用英文_第5頁(yè)
已閱讀5頁(yè),還剩39頁(yè)未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

FMEASteps

1 DefinethescopefortheFMEA2 Identifyteammembers,customer,andknowledgeexperts3 Developrolesandresponsibilitiesforteammembers4 Studytheproduct/process/service5 DevelopratingscalesforSeverity,Occurrence,andDetection6 Brainstormfailuremodes,knownandpotential7 Listtheeffects,causes,andcurrentcontrolsforeachfailuremode8 AssignratingsforSeverity,Occurrence,andDetection9 CalculateRPN10 DecideonathresholdRPN11 PrioritizebasedonRPNandseverity,orasrequiredbythecustomer12 Identifycorrectiveactions13 Implementandverifyeffectivenessofcorrectiveaction14 Completethedocumentation1 DefinethescopefortheFMEA

Definetheboundarieswithinwhichtheproduct,process,orservicewillbe studied,identifyingtheoperatingassumptions,currentconditions,and constraintsifany.

Example1: ConductaProcessFMEAonPCBmanufacturingline1,startingwith operation10andendingwithoperation250. Theassumptionisthatdesignofpartsiscorrect,andnoshortages Thelineissetupasshowninprocessflowdrawing#809901 Example2: ConductDesignFMEAonthepressurereliefvalve(Part#JJJKKK) forpotentialfailuresunderextremeoperatingconditions Assumenopreventivemaintenancewillbeconductedonceinstalled

DocumentontheFMEAstartupform

FMEA;StepbyStep

ScopeoftheFMEAPointstoconsider:WhoarethecustomersfortheFMEA,andwhataretheirrequirements/expectationsExample:Conduct(Process)FMEAontheassemblylineforProductA,coveringoperations110through230 WhenwillthisFMEAbeconsideredcompleteunderthegivenconditions(Remember,FMEAsareconsideredlivingdocuments,assuchtheyneedtobeupdated/revisedasthingschange.)Example:FMEAwillbeconsideredcompletewhentheteamhasimplementedallcorrectiveactionsasagreeduponbasedontheRPNthreshold

Thiswillformthebasisfordecidingthelevelatwhichyoushouldconduct theFMEA,andthescopeofworkinvolved..SystemSubsystemComponentProcessServiceLevel Focus Failure Cause Effect ModeSystem Car Overheating Coolingsyst. Strandedon failure theroad SubSystem CoolingSystem Inadequate Thermostat CarOverheating coolantflow stuckclosedSubAssembly Thermostat Stuckclosed BiMetalSpring Inadequate broken coolantflowComponent BiMetalSpring Broken Fatigue Thermostat stuckclosed Important:Youmustbeabletoseeacascadingoffailuremodes,causes,andeffectssimilartoaboveExampleofaProduct

Safety,LubricationEngine,Braking,ExhaustTrans.,Cooling

Thermostat

Diaphragm,BiMetalSpringRadiatorPumpVBeltTheInfluenceofLevel

CompanyPlant1 Plant2 Plant3 Plant4PCBLine PowerSupplies FHPMotorsOp10 Op20 …. …. Op250FMEAcanbeconductedatanyoftheselevels;italldependsonyourobjectiveTheInfluenceofLevelLevel Focus Failure Cause Effect ModeSystem Factory(Plant2) LatedeliveriesLowFPY Lost tocustomer onLine2 business

SubSystem Line2(PowerSupplies) LowFPY HighRework Latedeliveries at/aftertesting Operation Testing Highrework Testingresults LowFPY Op210 inconsistent

ExampleofaProcessOp120OpA20OpA10Op10Op210Op240Op250Important:Youmustbeabletoseeacascadingoffailuremodes,causes,andeffectssimilartoaboveTheInfluenceofLevel2 Identifyteammembers,customer,andknowledgeexpert/sGettheteamtogether,identifythecustomerandinvolvethemintheprocess.Somepreliminaryworkmustbedonetounderstandtheproduct/process/service,sotherightteamcanbeassembled.

Example: TeammembersincludeJohnPatton,KiritChawla(Customerrep)KimHeaston,andBettyChung(TeamLead)Nooneknowsenoughabouttheprocessatthistime.DocumentontheFMEAstartupform

FMEA-StepbyStep3

Developrolesandresponsibilitiesforteammembers

Whodoeswhatintheteam.Clearlydefinetherolesandresponsibilities foreachoftheteammembers.Atthistime,itisimportanttoconsiderthe strengthsofeachindividualandleveragethesame.

Example: TeamLead: Coordinatetheactivitiesoftheteam,andkeepontrack Actascheerleader,andinterfacewithmanagement Ensurethedecisionsaremadewithconsensus

Customer: Definerequirements Participateindevelopingratingscales,especiallyfor SeverityKnowledge Expert: Asconsultantprovideinfoondetailsofproduct/ processorservice

FMEA-StepbyStep4 StudytheProduct/Process/Service

Theobjectiveofthisstepistoacquireasmuchknowledgeaspossible. Itishighlyrecommendedthatallteammembersdelveintothis,since thereisnootherwaytofamiliarizeyourselfwiththeproduct/process/service.

Example1: TheteamresponsibleforconductingProcessFMEAongaspanels productionlinespends2weeksonthelinebuildinggaspanels, andtestingthesame.

Example2: TheFMEAteamresponsibleforDesignFMEAonamedicalimplant studiesthewaytheproductisgoingtobehandledinthe operatingroom,andusedbythesurgeon.

Example3: FouroutoffivemembersoftheFMEAteamspend3dayswiththe phoneoperators,andorderprocessinggrouptogetfirsthand understandingofallthestepsinvolvedinbookinghotelrooms.FMEA-StepbyStep

5 DevelopratingscalesforSeverity,Occurrence,andDetection Onceyouhavegainedenoughknowledgeabouttheproduct/process/service andaboutthewayitmaybeusedbythecustomer/enduser,youarein apositiontodevelopmeaningfulratingscales. Mostratingscalesareonascalefrom1to10,howeversomemayusea1to5 scale.Whichofthetwo,islessimportantthanensuringthatthesamescale isusedthroughoutthecompany. Youmayhavetodevelop/adaptthescalestosuityourneeds Forexamples,seenextpageFMEA-StepbyStepCausesFailureModes*EffectsOccurrenceDetectionSeverityHowfrequent?Whohasthemostinfo?Ifeliminated,willfailurebeavoided?Howeasytodetectwithcurrentcontrols?Whohasthemostinfo?Ifpreventedwilleffectsbeeliminated?Howsevere?Whohasthemostinfo?QuantifyingFailureModes,EffectsandCauses*CausesmaybeusedinplaceofFailureModesinsomecases5DevelopratingscalesforSeverity,Occurrence,andDetectionExamplefromDesignFMEA:SeverityOccurrenceDetectionEffectCauseFailureModeorCause1Remotechance,<1ppm2Verylow1to53Verylow5to104Moderate10to1005Moderate100to1K6High1Kto10K7High10Kto100K8VeryHigh100Kto1M9VeryHigh1Mto10M10Almostcertain…………..1Certaintobedetected2Veryhighchanceofdetection3Highchanceofdetection4Moderatelyhighchanceof..5Moderatechanceofdetection6Lowchanceofdetection7Verylowchanceof...8Remotechanceof…….9Veryremotechanceof...10Slipsbyundetected1Noeffect2Minoreffect-fit/cosmetics3Majoreffect-fit/cosmetics4MinorreductioninFunction5Customerdissatisfied6Majorreductioninfunction7Totallydysfunctional8Presentsminorhazard9Presentsinjuryhazard10FatalifusedNOTE:TheabovewereusedbytheauthorwithamanufacturerofhomeelectricalappliancesforaDesignFMEAFMEA-StepbyStep5DevelopratingscalesforSeverity,Occurrence,andDetectionExamplefromProcessFMEA:Severity-effect1Noeffectonoperators,users,orcurrentanddownstreamprocesses2Minorreworkatcurrentstep/nodysfunctionintroducedinproduct3Reworkatcurrent/subsequentstepscausingsomedelayedschedules,orproductisrenderedpartiallydysfunctional4Heavyreworkatsubsequentoperation,majordelaysinschedules,orproductfunctionisseverelyimpacted5RiskofinjuryorfatalOccurrence-cause1Veryrareoccurrence,X00ppboroncein3to5years2Rareoccurrence,XtoX000ppm,2to5occurrencesin3years3Frequentoccurrence,X000toX0,000ppm,1to3occurrencesin1year4Highfrequencyofoccurrence,X0,000toXMppm,over4occurrencesperyear5AlmostcertainDetection-failuremode(orcauseinsomecases)1Certaintobedetected,beforeanymeasurabledamageisdone2Automatedinspection/detectionorstrongprocesscontrolsexistatcurrentsteporwithinthesystemboundaries3Samplingplansusedforinspectionpurposes4100%manualinspectionmethodsusedwithinsystemboundaries5Defectunlikelytobedetected,willslipbyunnoticedNOTE:TheabovewereadaptedfromoneoftheProcessFMEAapplicationsledbytheauthor5DevelopratingscalesforSeverity,Occurrence,andDetectionSeverityOccurrenceDetectionEffectCauseFailureModeorCauseNOTE:ThisblankisforusebyparticipantsinclassFMEA-StepbyStep6Brainstormfailuremodes,knownandpotentialFailuremodesshouldbedescribedin““physical”ortechnicalterms,notasasymptomnoticeablebythecustomer.Theideaistoidentifyasmanyfailuremodesaspossible.Thiswillinvolvegettingallteammembersandstakeholdersinvolved,however,theproperapproachtobrainstormingmustbeused.Deferalljudgment,maybeeventoasubsequentmeeting.Thebiggestriskinthisstepisthatparticipantswillstartmixingupfailuremodeswithcauses,andeffects.Topreventthis,itishighlyrecommendedthatthemeetingleaderdoadryruntofamiliarizethegroupwiththedifferencesbetweenfailuremodes,effects,andcauses.Alistingoftheproduct/process/services’specifications,oroutputsandrequirementswillbenefithere..Postitpadsareaconvenientwayofcollectingthisinformation,andgroupingitintologicalgroups.Ifyouwritetheseonaworksheet,makesureyouleaveenoughspaceforeffectsandcausesFMEA-StepbyStep6Brainstormfailuremodes,knownandpotentialfortheProduct/DesignExample:OverheatingSlowaccelerationSkidsCatchesfireExcessivestoppingdistancePoorgasmileageWobbles50mphPoorcorneringOilleakRattlingofreardoorLatchdoesnotholdWipersineffectiveHorndoesn’tworkStiffsteeringandsoon…..Question:Arealltheabovefailuremodesforthecar?FMEA-StepbyStep

CausesFailureModesEffectsCarandit’sperformancerequirementsUsers/Customers

Componentparts,&sub-systems

Leadto LeadtoKeepingadistinctionbetweenthethreewillpreventyoufromgettingintocircularloops.Whenyousensegettingintosuchaloop,askWhatproduct/designistheFMEAbeingconductedon(focus)?Whataretheperformancerequirements/specificationsofthe(focus)?SeparatingFailureModes,EffectsandCauses6Brainstormfailuremodes,knownandpotentialfortheProcess:Example:ExcessivebacklashNoiseexceedsspecificationsDefectsperunit25%inexcessofstandardTestfixtureoperationunsafeOilleaksQuestion:Arealltheabovefailuremodesfortheprocess?Op120OpA20OpA10Op10Op210Op240Op250MachineWeldbracketsIntegrationTestingCrate&ShipAssembleAxleMountWheelsSystemBoundariesFMEA-StepbyStep

CausesFailureModesEffectsOperation240Users/Customers/OperatorsDownstreamoperationsPlantdeliverables

WorkinstructionsOperatorerrorsPrioroperations

Leadto LeadtoKeepingadistinctionbetweenthethreewillpreventyoufromgettingintocircularloops.(EffectsofFailurearedefinedastheeffectsofthefailuremodeonthefunction,asperceivedbythecustomer.)Whenyousensegettingintosuchaloop,askWhatpartoftheprocessistheFMEAbeingconductedon(focus)?Whataretheperformancerequirements/specificationsofthe(focus)?SeparatingFailureModes,EffectsandCausesFailureMode2Cause1Cause2Cause3Cause4Effect1Effect2Effect3FailureMode1FailureMode3Multiplicitywillexistforcauses,failuremodes,andeffects(CauseofFailureisdefinedasanindicationofadesignweakness,theconsequenceofwhichisthefailuremode.)FailureModes:Willsharecauses,andeffectsCauses:Thereasonsforfailure,canbeoneormanyforagivenfailuremodeEffects:Theresultsofthefailure,canbeoneormanyforagivenfailuremodeSeparatingFailureModes,EffectsandCausesProductFMEAOverheatingBrakesbindingCause2LowtirepressureCause4PoorGasMileageStalledonroadEffect3PooraccelerationFailureMode3CauseFailureModeEffectSeparatingFailureModes,EffectsandCausesProcessFMEAImproperSeatingMissingInstructionsCause2LooseNutsCause4FailstorquetestUnsafeatTestingEffect3AssembledbackwardsFailureMode3CauseFailureModeEffectSeparatingFailureModes,EffectsandCauses7Listtheeffects,causes,andcurrentcontrolsforeachfailuremodeTocapturetheeffects,causes,andexistingcontrolsifanyforthefailuremodeinquestion.Inputfromcustomer,knowledgeexpertswillbeespeciallyhelpfulatthisstep.Caution:Manyteamscommiterrorsofwishfulthinkinghere,especiallywithregardtocurrentcontrols.Youshouldfocusonthecurrentstate,andnotonwhatcouldbedone,orwhatoughttobedone.Nowstartdocumentingontheworksheet,knowingthateachfailuremodecanhavemultipleeffects,andmultiplecauses.FMEA-StepbyStep7Listtheeffects,causes,andcurrentcontrolsforeachfailuremodeExample:FMEA-StepbyStep8AssignratingsforSeverity,Occurrence,andDetectionHereweaccomplishtheconversionofeachofthesefactorsintoanumericalvalue.Dependingonthequalityoftheratingscalesthisstepcanbeveryeasyorsomewhatfrustrating.Therewillbetimeswhentheteamwilldisagreeonthevaluesassignedtoaparticularcause,effect,orfailuremode.Ratherthanvoting,itisrecommendedthattheteamtrytoreachconsensus.Incaseofdisagreements,knowledgeexpert’’sopinioncanbeusedtoincreaseunderstanding,ormoredatacanbesought.Inanycasetheteam’sdecisionshouldprevail.DocumentontheworksheetFMEA-StepbyStep8AssignratingsforSeverity,Occurrence,andDetectionExample:FMEA-StepbyStep9CalculateRPNSimplyassigningratingsforSeverity,Occurrence,andDetectiondoesn’thelpquantifytheriskintoasinglemeasurablevalue.Multiplyingtheratingscoresthusfillsthisgap.NotethatinthisapproachwehavemaintainedequalweightforeachofthethreeS,O,andD.Example:FMEA-StepbyStep10DecideonathresholdRPN,withoutignoringhighseverityfailuremodesIdentifythefailuremodesyouwillchoosetoworkon.Itmaynotbepracticaltoaddressallofthem.Thiscriticalstepmustbeconductedwithcustomerinvolvement,andconsensusbuilding.Manyteamsrunintodifficultieshere,especiallywhenthecustomerinsistsallitemsneedtobeaddressed.Itneedstobeunderstoodthatsomeelementofriskwillalwaysbepresent.Thequestionthereforeis“Whatlevelofriskisacceptable”?Someofthedifferentapproachesthathavebeenusedtodefinethethresholdare;ParetoAnalysis,Topcauseforeachfailuremode,etc.DocumentonFMEAstartupformtoindicatethiswasdiscussed,andagreementreachedonthethresholdvalue.FMEA-StepbyStep10DecideonathresholdRPN,withoutignoringhighseverityfailuremodesExampleusingParetoChart:CausesCumulativeRPNCumulativeRPNCurve80%ofCumulativeRPNFMEA-StepbyStep10DecideonathresholdRPN,withoutignoringhighseverityfailuremodesExampleusingRPN>=200foreachfailuremode:FMEA-StepbyStep11PrioritizebasedonRPNandseverity,orasrequiredbycustomerArriveattheorderinwhichyouwillstartaddressingthefailuremodesandcausesforcorrectiveaction.AlthoughRPNandseveritybasedprioritizationseemsthemostlogical,yourdecisiontoproceedmustbemadewithcustomerinput.Thisstepiseasilyaccomplishedbysortingthedata,indescendingorder.Youcandothiswithineachfailuremodetomaintaindataintegrity.Documentationonworksheetisimportanttoensurethewholeteamisinsync.FMEA-StepbyStep11PrioritizebasedonRPNandseverity,orasrequiredbycustomerExampleofsortedworksheetbyRPNwithineachfailuremodeFMEA-StepbyStep12IdentifycorrectiveactionInthisstepyouidentifythecorrectiveactionsneededtoeliminate/controlthecauses,andreducetheriskleveltoorbelowtheagreeduponthreshold.Therewillbetimeswhenyoucannotworkontherootcause;insuchcasesthebestcourseofactionwillbeviaadditionofcontrols/adequatewarningdevices/mechanismsofimpendingfailure.Re-evaluatetheratingsforS,O,andD,followedbyRPNcalculation.Discussionwiththecustomerisimportantagainsincethecorrectiveactionswillimpactthem.Knowledgeexpertsmayalsoprovidevaluableinputastowhatkindsofcorrectiveactionwillbebestsuitedforthegivencause/failuremode.Finally,fromallpossiblecorrectiveactions,theteammaychooseonebasedoncost/benefitanalysis,speedofimplementation,andthenewlevelofrisk.FMEA-StepbyStep12IdentifycorrectiveactionExample-allcauseswithRPN>=200areaddressed:FMEA-StepbyStep12IdentifycorrectiveactionQuestions:Whydidthecauseofworntireshaveanactionitem,althoughtheRPNwas160?TraininginadvanceddrivingtechniquesreducestheRPNfrom350to200,shouldheteamstophere?Whyisitthattheseverityratingdoesnotreducealthoughtraininginadvanceddrivingtechniquesisprovided?Doyouthinktheteam’sworkisdone?13ImplementandverifytheeffectivenessofcorrectiveactionCorrectiveactionsidentifiedoughttobeimplementedlikeprojects-withadefinitestartandend.Inmanycasesaprojectteamsmaybeformedtocarryouttheimplementation.TheseprojectteamsmayhavemembersfromoutsidetheFMEAteam,howeveratleastonemembershouldbedrawnfromtheFMEAteam.Acheckontheeffectivenessofthecorrectiveactionisimportant,intheabsenceofwhichyouwillnothaveaclosedloopfeedbackonwhatreallytranspired.ThischeckshouldbeconductedbytheFMEAteamafterthecorrectiveactionshavebeeninplaceforsometime.Thisissobecausethecorrectiveaction,likeachange,maynotlast.Ittakesdiligentefforttoensurethechangewillhavepermanence.Ifthecorrectiveactionisnoteffectiveenough,youmayneedtoimplementsomemorecontrols/takemoreactions.13ImplementandverifytheeffectivenessofcorrectiveactionExampleofadditionalactiontakentoreduceriskfromdrivinghabits:14Completethedocumentationandsaveinarchives/databasesThislaststepisoverlookedbymanyoftheFMEAteams.Whileitisunderstandablethatthenextprojectneedstobeworkedon,itisalsoimportantnottolosetheknowledgegainedbytheteam.Thebestwaytodocumentistousearchivingsystemsinthecompanyiftheyexist,electronicstorageisnowacceptedbymostregulatoryagenciesnow.Itemsthatshouldbesavedinclude:FMEAstartupformFMEAworksheetsMeetingminutesProcessflowDesignspecs,andvoiceofcustomerDetailsofprojectscreatedandimplementedaspartofactionitemsPortab

溫馨提示

  • 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。

評(píng)論

0/150

提交評(píng)論