8D报告培训资料-2汇编课件

VishayCustomer

CorrectiveActionRequest(CAR)Guidelines

Vishay《客户纠正措施要求CAR》应用指南午涯芝还殿吵丰豫硬讫缴痊差宫酮恫肪煞信臻绵反理铆补胰绍怖点江邪磨8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingVishayCustomer

CorrectiveAc1WhatisaCAR/8D?

何谓CAR/8D?ACAR/8DReportisamethodtodocument,communicate,trackanddriveresolutionsforqualityissues.CAR/8D是针对品质问题而进行文件化、沟通、追踪及解决问题的方法。An8DreportisFordMotorCompany’sformatforproblemsolving.Itisthepreferredmethodusedthroughoutourindustry.CAR/8D报告是福特公司解决问题的格式。它是我们所有行业首选的解决问题的方法。砌印零扰裳刻镣磁件任棒出诉称喂屋骚磨处谊款饲踪析嘘站毙搬旋艰却扰8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingWhatisaCAR/8D?

何谓CAR/8D?A2ImmediateContainment.

采取迅速的围堵措施（短期对策）ClearidentificationofRootCause.

真正识别问题产生的根本原因（真因）RobustCorrectiveActions.充分的纠正措施VerifiedCorrectiveActions.验证纠正措施Systemfixes.系统化（即纠正措施标准化或文件化）100%On-timeresponse.

100%准时反应（即及时解决问题，准时回复客户）Eliminatetheproblemsthefirsttime.做到第一次就消除问题所在Preventionoffutureproblems.实现潜在问题的预防CUSTOMER8DEXPECTATION

客户应用8D的期望日槐卷坞踞盔娥乱预潘情仲诡几滩运肇阁仙捂拍综谰铆剩疵郁佛轻沼难巢8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingImmediateContainment.CUSTOMER3CAR/8DReportProblems

完成CAR/8D报告存在的问题Notidentifyingthetrueprocesses,escape,andsystemrootcauses.

没有识别出过程、流出（逃脱）及系统的根本原因（真因）Notimplementingsystemcorrectiveactions.

没有实施系统性纠正措施Notproperlycontainingentirepipelineofproduct.

没有针对产品的所有流程采取正确的围堵措施Unclearorambiguouswording.

对问题采取的不明确或模棱两可的描述Notmeetingcustomerexpectationsregardingcontentandcycletime.

不符合客户关于内容及回复时间的要求术最编剐闺棉呵谭姜餐规耪壕唱差挚董叛雄撑奥佛登叉癌香搐绪臼儒钱寥8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingCAR/8DReportProblems

完成CAR/84CAR/8DRequirements

CAR/8D的要求Allcorrectiveactionrequestsmustbecompletedusingan8Dreport(unlessadifferentmethodisrequiredbyCustomer).

所有的《纠正措施要求》必须采用8D报告形式（除非客户要求采用不同的方法MustuseCorporateformat.

必须采用Vishay公司的格式Mustuse8Dchecklistasaguidelineincompletingthe8D’s.

在完成报告的过程中必须采用8D检查表进行检查塞墅完逐用伤茎爷盅管馅鸵袭暇棘碑苔华氯咨皮世亦朽围蚤树楚宫坟稗盆8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingCAR/8DRequirements

CAR/8D的要求A58

DisciplinestoProblemSolving

解决问题的8个准则D1EstablishaTeam组建问题解决小组D2DescribetheProblem描述问题D3Containtheproblem采取围堵措施（即短期对策）D4Identifytherootcauses识别/确认根本原因（真因）D5CorrectiveActions确认纠正措施D6ImplementCorrectiveActions实施纠正措施（即长期对策）D7PreventRecurrence防止再发D8CongratulatetheTeam小组庆祝寻铆也楞斑买沏鲤姑滁案斧架赌奥畜澡包赠禹施淌蛆巨伴么餐控漳械挨剔8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DisciplinestoProblemSolvi6D1EstablishTeam

D1组建问题解决小组EstablishCrossFunctionalTeam.

建立跨功能小组IdentifyaChampion.确定小组长Membersshouldbefromallaffectedareas,notjustquality!i.e.Sales,Logistics,Marketing,Engineering,LineOperators,ProductionMgmt.,etc…

小组成员应来自于所有被涉及区域，并非只是质量部！如销售、物流、市场、工程、生产线操作工、生产管理等等······TheTeamshouldaskthemselvesdotheyhavethecorrectskillmixtosolvetheproblem?

小组应询问自己是否具有解决问题所必需的能力?易蛛耸战煤鉴抨拍貉痉屹惺救庇缔熊骏恰子肿殉完锻卑咽窒颂细涡篮榔额8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD1EstablishTeam

D1组建问题解决小组E7D2DescribetheProblem

D2描述问题ClearlyIdentifyandDefinetheProblem.

明确识别和定义问题InmanycasesProblemsareambiguousorimprecise.

在许多案例中，问题是模棱两可或不明确的ClarityensuresthateveryoneistryingtosolvethesameProblem.

明确问题可确保任何人将尽力去解决问题勺嘴晨妥凭懒酬储楔永鸡淖牵传桑芍闭澈俯绸骇捏唯壁藤狞勺局踩害杠找8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD2DescribetheProblem

D2描述问8D2DescribetheProblemElements

D2描述问题要素WhatistheProblem?Describethefailuremode.

问题是什么?描述失效模式Wherewasitdetected?问题是在哪里被发现?Whenwasitdetected?问题是什么时候被发现?Whatlots/datecodesareaffected?

被影响的批次/日期码是那些?Howmanypiecesareaffected?

被影响的数量是多少?IstheCustomerinformationincluded?

是否包含客户信息?逻畔芬库崎类窑货狂酸探主豪雇夺妒蚌枷沼捉补睁搏垮挂釉涛窗腾柜祸朋8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD2DescribetheProblemElemen9D2DescribetheProblemExamples

D2描述问题案例PoorProblemDescription差劲的问题描述“Customerreceivedwrongpart.”客户接收到错误零件GoodProblemDescription完美的问题描述“CustomerreceivedincorrectvalueCRCW-0603resistorson4/1/02.CustomerP.O.441960(VishayP.O.X765644-30)specifiedCRCW-0603,8.2KohmandreceivedCRCW-0603,82Kohmparts.”客户在4/1/02接收到阻值错误的CRCW-63电阻。客户订单号码441960（Vishay订单号码X765644-30）指定的CRCW-63电阻的阻值为8.2欧姆，而收到的CRCW-63电阻的阻值为82欧姆。较徒顽逃碾宠掌双将聘腹码准永骨卖啮桌障浴久后芽憋璃呼椿浓谤绞幽华8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD2DescribetheProblemExampl10D3Containment

D3围堵措施（短期对策）Containmentissimilartoquarantine.Quarantinedoesnotcureadisease,butitkeepsitfromspreading.

围堵相似于病人隔离。隔离虽不能医好疾病，但可以防止疾病的传播FindandsegregatenonconformingproductstopreventshipmenttoCustomer.

查找和隔离不良品，防止发往客户Shutdownprocesses/equipmentthatisproducingbadproduct.

停止正在制造不良的加工或装配Makesurecontainmentactionsareeffective.

确保围堵措施是有效的曙佳损绣注卜呸行淄坤倪账费鸽肖绍谍各我择须鬃默鼻乳炽铬啊择急伞扎8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD3Containment

D3围堵措施（短期对策）Co11D3ContainmentElements

D3围堵措施要素Hasaneffectivecontainmentmethodbeenidentifiedanddocumented?

是否有有效的围堵方法已经被确定和文件化?Havedates(ordatecodes)fortemporarycontainmentactionsbeenidentified?

是否已经确定了临时围堵措施实施的日期（日期码）?Haveactionsbeenverifiedwithbeforeandafterdata?

是否已经验证了围堵措施实施前后的效果?Hastheentirepipelinebeencontained(production,warehouse,distributors)?

是否对产品的所有流程采取了围堵措施（如生产线、仓库及发货员）?Hasdetailedinstructionsoncontainmentbeenissuedtopeopleresponsibleforcontainment?

是否给负责实施围堵措施的人员发放了详细的围堵作业指导书?讲工靠凤吩羽字洲亥颖墩隙诀浸锻谍嘲呸场连尤陶棱橙总凤矛贞愧饰妆抒8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD3ContainmentElements

D3围堵措12D3ContainmentExample

D3

围堵措施案例PoorContainment差劲的围堵措施“Operatorwasalertedofthefailure.”让操作工提防/注意此不良GoodContainment完美的围堵措施“Productionandwarehousematerialwasinspectedon4/1/02byJ.Smith(qualityassurancepersonnel)andtherewere0lotsoutof320containingmixeddevices.”J.Smith（质量保证人员）于4/1/02检查了生产线及仓库材料栗物步歉乳绘讯堰仰跋患您哥骇晋点威敌崭踞躇镐汛毡贰扫繁垃宽瓤毖赃8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD3ContainmentExample

D3围堵措施13D4RootCause

D4根本原因（真因）Rootcauseisthedisease(startingpoint)thatsetsinmotionthecauseandeffectchainthatcreatestheproblemorproblems.

根本原因是产生问题或问题群的原因和影响开始发作的病因（发作点）BewaryofselectingsymptomsinsteadofrootcausesIfyoufixasymptomyouwon’tsolvetheproblem.

必须提防以症状代替病因，如果你仅仅关注一个症状，你将不能解决问题Poorrootcauseselectionresultsinpoorcorrectiveactions.

选择不正确的根本原因将导致不正确的纠正措施Usetoolssuchas5Whyanalysistoensurethattherootcausehasbeenidentified.

应用象“5个为什么”分析法，确保根本原因被识别和确定旧凑刘吞窃瑰司炸渺伐柱蓝撞磅哥闺婴供巴帚壁掂驶钾辗祟序浊绑聘语侯8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD4RootCause

D4根本原因（真因）Root14D4RootCauseElements

D4根本原因要素Hastheprocessrootcausebeenidentifiedandestablished?

制程根本原因是否已经被识别和确定?Hastheescaperootcausebeenidentifiedandestablished?

流出（逃脱）根本原因是否已经被识别和确定?Hasthesystemrootcausebeenidentifiedandestablished?

系统根本原因是否被识别和确定?Dothethreerootcausesexplainallweknowabouttheproblem(timing,failuremode,failureamount,etc…)?

三种根本原因是否可以解说我们所知道的问题所有方面（如时间、失效模式、失效数量等等）?Wastherootcauseanalysisperformedusingthe5whytechnique?

根本原因分析是否使用了“5个为什么”方法?际逸拆病盐傲绣柒由做财症岔箔糟殉揪镜玲抹丰拙演苫俭舅医西嘛枪硒喘8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD4RootCauseElements

D4根本原因15D4RootCauseExamples

D4根本原因案例PoorRootCauseStatement差劲的根本原因“OperatorplacedwronglabelonPackage.ItwasanOperatorError.”操作工在包装箱上贴错了标签，是操作工的错。

GoodRootCauseStatement完美的根本原因“ProcessRootCause:Anincorrectlabelwasplacedonthepackagebecausethecurrentsystemallowsformultiplelotstobeprocessed(batchprinting)atoneworkstation.”制程根本原因：目前的系统允许在同一个岗位加工种类不同的批次，导致错误的标签被贴在包装箱上“EscapeRootCause:Themis-labeledproductescapedbecausetherewasnoverificationstepatorafterthelabelprocess.”

流出根本原因：贴错标签的产品流出是因为在该岗位或后续过程没有标签验证步骤暑滋纠撼怎厦垒镀冯校侥溅攀呜彻几秋耍虱札缺披那蔑什滁揣匣螟主青崔8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD4RootCauseExamples

D4根本原因16D5CorrectiveActions

D5纠正措施Correctiveactionsshouldfixthediseaseorrootcause.

纠正措施必须是针对病因或根本原因（真因）Correctiveactionsshouldaddressprocess,escape,andsystemrootcauses.

纠正措施必须致力于制程、流出（逃脱）及系统的根本原因（真因）Negativeeffectsofcorrectiveactionsshouldbeconsidered.

必须考虑纠正措施带来的负面影响（即边界效应）Retrainingofoperatorsisnotacorrectiveaction.

操作工的再教育不属于纠正措施范畴Increasedinspectionisnotacorrectiveaction.

增加检查（人员、数量、频次等）也不属于纠正措施范畴且县之庭宇帘衙怒主睁房笛逼佩俘励搀君肾已粒臣邵连款诌统霉拦耪娶阴8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD5CorrectiveActions

D5纠正措施C17D5CorrectiveActionsElements

D5纠正措施要素Haveprimaryandalternativecorrectiveactionsbeenidentified?

是否已识别和确定首选及多选的纠正措施Docorrectiveactionsaddressprocess,escape,andsystemrootcauses?

纠正措施是否是针对制程、流出（逃脱）及系统的根本原因Havenegativeeffectsofcorrectiveactionsbeenconsidered?

是否考虑了纠正措施的负面影响（即边界效应）佬袋籽磨鼻炉癸疑智铰版敷揩敲揪陨冻赢奶叼槛壤炭敝揩谴诵余级企汁随8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD5CorrectiveActionsElements18D5CorrectiveActionExamples

D5纠正措施案例PoorCorrectiveAction差劲的纠正措施“Re-trainoperator.”操作工再培训GoodCorrectiveAction完美的纠正措施“ProcessCorrectiveAction:Changeworkflowtoaserialprocesswherebyonlyonelotisattheprintingstationatalltimes.Thiswilleliminatethechanceofmixingtheproductlabels.”制程纠正措施：变更流程，在任何时间标签印刷岗位只加工单一批次“EscapeCorrectiveAction:Implementabarcodeverificationsteptoensurethatcustomerlabelmatchesthefactorylabel.”流出（逃脱）纠正措施：实施标签验证步骤，确保工厂标签和客户标签一致磨驻皱孕晃暴叼掸尝追题娃汲泻痈硬贵嗅浸冗珐粘秒仆承销度绊焕嚏暂趣8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD5CorrectiveActionExamples

19D6ImplementCorrectiveActions

D6实施纠正措施（长期对策）Stepwherewemonitor/validatethatthecorrectiveactionshaveeliminatedtherootcause(s).

确定我们监控/验证纠正措施是否已经消除了根本原因的步骤Datesforthestartandcompletionofthecorrectiveactionshouldbeidentifiedalongwiththeresponsibleperson.

和纠正措施实施责任人一起确定纠正措施开始实施和完成的日期丘腋巴酮烤槽卧芬闪放蛮绊摇俊或卧悯擒战纶吴起酒茬恫凑露七肖竣冲醒8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD6ImplementCorrectiveAction20D6ImplementCorrectiveActionsElements

纠正措施实施要素Havecorrectiveactiondatesalongwithresponsibleindividualbeenidentified?

是否已经确定纠正措施实施日期和责任人?Havecorrectiveactionsbeenvalidatedtoeliminaterootcause(s)?

对纠正挫伤是否进行了验证，它能否消除根本原因?埔刁衷橇幼乳勘绿州雪未彻践婿允钮窑活罕馅氰鼠褥惠气彩渝瘟留脾歪浪8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD6ImplementCorrectiveAction21D6ImplementCorrectiveActionsExamples

D6纠正措施实施案例PoorCorrectiveAction差劲的纠正措施“Complete.”已完成GoodCorrectiveAction完美的纠正措施“CorrectiveactionsstatedinD5werecompletedon4/1/02byJ.Smith.Postlabelinginspectionhasdiscovered0failuresoutof400lotsinspectedasof5/1/02.”

J.Smith已于4/1/02完成了D%中描述的纠正措施。5/1/02在标签检查岗位共检查了400个批次，没有发现一批标签不良敝永虞逢逊摹诺裳石浸京懂机磕乳阴降靴赠硒图禽告械工咀旧锄跨缠诡定8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD6ImplementCorrectiveAction22D7PreventRecurrence

D7防止再发Preventtheproblemfromreturningbyaddressingproduction,business,management,orengineeringprocesses.

通过向生产、业务、管理层、工程传达，以防止问题再发沮示控蠕壳酣靡赵当地阑碰刁石羽琐笛黑残艳凛幅二麦行熄酥狮茶沸账性8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD7PreventRecurrence

D7防止再发P23D7PreventRecurrenceElements

D7防止再发要素Dopreventiveactionsaddressbasicsystemissues?

预防措施阐述是否基于基本的系统问题HaveFMEA’s,controlplans,and/orproceduresbeenupdatedtoensurethatthesystemswillpreventissuesfromre-occurring?

FMEA、控制计划及/或程序是否已经被更新，以确保系统可以防止问题再发Havepreventiveactionsbeenagreeduponbyallaffectedareas?

预防措施是否已经征得被影响区域的认可Dounfinishedpreventiveactionshaveachampionandaprojectedcompletiondate?

未完成预防措施是否确定了组长和其完成日期

吐贮壕萝轿堕弛彤狸脚操刚也啪搅听修疙蔽刃悲痛栗咨保嘲瓷铆蹬揣伟箭8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD7PreventRecurrenceElements24D7PreventRecurrenceExamples

D7防止再发案例PoorPreventiveAction差劲的预防措施“Sameascorrectiveactions.”预防措施同于纠正措施GoodPreventiveActions完美的预防措施“Workinstructionandcontrolplanhavebeenchangedon4/1/02toeliminatebatchprocessingandtoaddbarcodeverificationprocesses”作业指导书及控制计划已于4/1/02进行变更，以消除批次处理问题及增加标签验证过程“CorrectiveandPreventiveactionswerealsoappliedtoVishay’ssisterfactoriesinChinaon4/1/02.”纠正/预防措施已于4/1/02应用于Vishay在中国的兄弟工厂“Auditchecklistwasmodifiedon4/1/02toincludemonthlycheckstoensuresinglelotprocessing.”检查表已于4/1/02修订，包括月检以确保单一批次被加工伪帐厉厨额觉尧蝶珐患涸遗定宿驹万谚练终勃寨凹迟含汞舆英投荚豢故期8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD7PreventRecurrenceExamples25D8CongratulateTeam

D8小组庆祝Variesbyfacilitybutmostoftenoverlooked.

澄豹泅败辈精胖贾姓赖失纂贝云诲蚁瞧肛票趴捣赦售随逛裴傲铡拇裁鬃揪8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingD8CongratulateTeam

D8小组庆祝Va26OtherComments

其他内容8Dshouldsupplyfactsnotemotions.

8D应该提供事实，不应带有感情色彩Avoidusinginternalacronyms.

避免使用公司内部缩写Becompleteinyourdescriptions.

叙述应该完整ItisourresponsibilitytofixVishayproblemsevenifwedonothavetraceabilityinformation.

即使没有可追溯的信息，但关注Vishay问题是我们的责任简漠句佰蔼采粱菲挪吨钒路麓忱床揭咏筷从垦条索恍频边鸯码疮炕睡舌念8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTrainingOtherComments

其他内容8Dshoulds278DExampleHeartInc,amanufacturerofHeartdefibulators,returned25shortedpartswithmultipledatecodeson5/1/02.Heartstatedthatthe25partsfailedattherefinaltest.Heart’sfailurerateis10PPM.Theyexpressedconcernthatfaileddefibulatorsmightreachtheircustomers.

InternalanalysisbyVishayindicatesthatthe25partsareindeedshortedandtheyarenotthedevicetype(PN#V123)thatVishaysellstoHeartInc.Infact,the25partsareamixtureofdifferentVishaydevicesspanningthelast3monthsofproduction(February,March,andApril).AllreturneddeviceshadalowerpowerratingthanwhatissuppliedtoHeart,whichiswhytheyshortedinHeart’sapplication.Additionalanalysis,pointstothefactthatthepartsweremixedatmarking.Themarkingequipmenthasaknowndefectinwhichthelastfewpartsmightgetstuckinthetrackduetorandombutfrequentstickingofthepushpinmechanismwhenthebowlfeederbecomesempty.Tocombatthisissue,theengineerduringtheinitialdiscoveryoftheissueinstructedtheoperatorstoinspectthetrackpriortostartinganewlot.Intheeventthatpartswereleftovertheoperatorwastoremovethedevicesandcallthetechniciantorepairthepushpin.Inadditiontothechangeinprocedure,productionimplementedasampleoutgoingelectricaltest(200piecesper20,000piecelot)toeliminatemixedlots.Theoperatoronthemarkingequipmentwasnew(approximatelyworkingforVishayfor3months)andwasnotperformingtheinspectionasrequiredbytheprocedure.卧女云箕休医迷蛀审忌接博返款叶樱筐跺秩架攫绊枕署笺蔫京枚滤轴巴抵8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExampleHeartInc,amanufac288DExample8D案例

D1EstablishTeamD1建立小组NameFunctionChampionJ.SmithProductEngManagerTeamLeaderJ.DoeQualityEngineerMembersR.NeilProductionSupervisorB.DellProductionEngineerV.ChambersLogisticSupervisorA.MayMaintenanceEngineerN.PhillipsTrainingSupervisorS.RobinSales物暂慷岸凄残殴睹朴茂同始绝盒论弱躺博樱漏毯封包说蛔低作眼奋禾中晰8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D1Establish298DExample8D案例

D2DescribeProblemD2描述问题HeartInc.returned25V123partson5/1/02withthefollowingdatecodesthatfailedshortattheirfinaltest.Heart公司在5/1/02返回25个V123产品，产品日期码如下，这些产品是其产品终检时发现短路的#ofPartsDateCode10 0202 10 020350204Theestimatedfailurerateis10PPMandthecustomerisconcernedaboutfieldreliability.估计失效率为10PPM，而且客户非常担心已流入市场舶溪法乱称滤整号攻阁卯早巧怨牺闯母神焚按促孔呐说爵锅霍脉氦蔫反烯8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D2DescribeP308DExample8D案例

D3ContainmentActionsD3围堵措施AllproductinproductionandinVishay’swarehouseswasquarantined(byV.Chamberson5/2/02)and100%electricallytested(byB.Dellon5/4/02)toeliminatethemixedproduct.12mixedpartswereremovedoutof60,000partstested.Allretestedlotswillbemarkedwitha“green”stickertoidentifythattheyhavebeenretested.所有在线及在库品全部隔离（V.Chambers已于5/2/02完成），并进行100%电性测试以消除混入产品（B.Dell已于5/4/02完成），从60,000个中剔除出12个异类产品。所有重测的产品批均用“绿色”标签标识以示重测。还轴记奋雹误瘟赋歪则纬在襄券掣滨薪缓痢扎素院醋饿锌跋荐绩搅载啸砰8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D3Containment318DExample8D案例

D4ProcessRootCauseD4制程根本原因Problem:ShortedParts问题：短路Why?WrongpartsweresenttoCustomerandthepartswereunderratedfortheapplication.为什么：错误的元件发给客户及其用途被低估Why?Residualpartswereleftinthemarkingequipmentcausingthesubsequentlottocontainmixedparts.为什么：残留的元件被遗留在打标机上导致其混入后续的批次Why?Thepushpinfailedtocleartheresidualparts.为什么：推针失效而无法清除残留元件醉彩柄捂销繁卉贸漆介褂泅壮元尘递箔还配荫苹搪铜箱毅艾涕潘寒溜鞭商8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D4ProcessRo328DExample8D案例

D4SystemRootCauseD4系统根本原因Problem:ShortedParts问题描述：短路Why?WrongpartsweresenttoCustomerandthepartswereunderratedfortheApp.为什么：错误的元件发给客户及其用途被低估Why?Residualpartswereleftinthemarkingequipmentcausingthesubsequentlottocontainmixedparts.为什么：残留的元件被遗留在打标机上导致其混入后续的批次Why?Thepushpinfailedtocleartheresidualparts.为什么：推针失效而无法清除残留元件Why?Theactuatorsonthepushpinareoldandneedtobereplaced.为什么：推针执行器老化而需要更换Why?Wedonothaveadetailpreventivemaintenanceplanforreplacementofworn-out/oldequipment.为什么：我们没有一个详细的针对替换破损/老化设备的维护计划杏蛋蕉蜀型氟蟹否来古饥蘸秋茁海绪筛瞥败拒悲级亲桑重里拦蛾邱菩辜请8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D4SystemRoo338DExample8D案例

D4EscapeRootCauseD4流出根本原因Problem:MixedPartsEscapedtoCustomer问题描述：混入产品流到客户Why?SampletestpostmarkingwillnotalwaysdetectPPMissues.为什么：抽样检查岗位无法发现PPM级缺陷Why?Samplesizeistoosmall.为什么：抽样量非常少驶贾她译奄警蹄刷更类三哪宠钳豺梨蒲平害烬哇办浴掺对还喻哆哮瞒库忘8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D4EscapeRoo348DExample8D案例

D5RootCauseD5根本原因Analysis:Vishayverifiedthatthepartsareshorted.ItwasdeterminedthattheshortedpartsweremixeddevicesthathadlowerpowerratingsthantheonessuppliedtoHeart.ThemixoccurredatVishay'smarkingoperationduetoresidualunitsleftonthemarkingmachineduringFebruary,MarchandApril.Vishayhadaprocedureinplacefortheoperatortoverifythetrackwasemptypriortothestartofanewlot.Theprocedurewasnotfollowed.分析：Vishay确认产品是短路，最终原因被确定为被发给Heart公司额定功率低的产品混入到设备中，混入现象发生在Vishay的打标岗位，是在2月、三月份及四月份残留元件被遗留在打标岗位所致。Vishay在操作岗位有作业程序，规定在开始打标新的批次时须检查轨道是干净的，但程序没有被执行。ProcessRootCause:Theactuatorinthepushpinmechanismusedtoflushresidualunitsfromthetrackstopworking.制程根本原因：推针执行器被用来剔除轨道停滞工作时的残留元件EscapeRootCause:ThesamplesizeforthepostmarkingtestisnotsufficientenoughtodetectPPMmixturelevels.流出根本原因：在打标岗位的抽样检查数对混入水平在PPM级的不良来说是不足的SystemRootCause1:Theactuatorsarenotincludedonapreventivemaintenanceschedulethusallowingactuatortodegradeandbecomedefective.系统根本原因1：执行器没有被纳入保养计划，这样允许执行器劣化及没有效力SystemRootCause2:Currenttrainingplandoesnotrequiretrainingverificationthereforeitwasnotknownthattheoperatorwasnotfollowingtheoperatingprocedure.系统根本原因1：目前的培训计划中没有要求进行培训效果验证，所以并不知道操作工没有遵守作业程序的规定恤代潮曙址倘哪石故掖辐竭烧盼孜优乔施冲缀膛烫凝排轰吧帕濒粕揭沙阉8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D5RootCause358DExample8D案例

D5CorrectiveActionsD5纠正措施ProcessRootCause:Replaceactuatorsonallmarkingequipmenttoeliminateresidualparts.制程根原因：在打标机上替换执行器以除去残留部件EscapeRootCause:Implement100%qualitytestpostmarkingtoensurethatmixedpartswillnotbeshippedtoHeart.流出根本原因：在打标岗位实施100%检查确保混入的部件不被发送Heart公司SystemRootCause1:Incorporateapartreplacement/refurbishprogramintotheexistingpreventivemaintenancescheduletoensurethatpartsarereplacebeforetheycauseaproblem.系统根本原因1：在现有的检修计划中增加部件置换/刷新项目，以确保部件产生问题时被置换SystemRootCause2:Modifytrainingprogramtoincludeaverificationsteppriortograntingcertification.系统根本原因2：修订培训程序，包含在批准合格前有一个检验步骤汾谴灯童扇政邹漏算孜飘演仅睦乔趣樱燃礼丸挟赏妆栓履灌说昆矽曳仪频8D报告培训资料_28D报告培训资料_25/30/2002Rev.Orig8DTraining8DExample8D案例

D5Corrective368DExample8D案例

D6ImplementCorrectiveActions

D6实施纠正措施ProcessRootCause:CompletedbyA.Mayon5/10/02.Severallotswereprocessedthroughthemarkingmachineandthepushpinproperlyremovedtheresidualparts.制程根本原因：A.May于5/10/02完成打标机打标多个批次时，推针可正确的推离残留部件EscapeRootCause:CompletedbyB.Bellon5/10/02.Severalmixeddeviceswereplacedthroughthetestertoverifythatthetestprogramwouldremovealldefectiveunits.Allincorrectdeviceswereremoved.流出根本原因：B.Bell于5/10/02完成多台混料装置被安置在检查仪上以验证检查程序可以剔除不良品，所有不好的测量仪已被移走SystemRootCause1:Projectedcompletion6/1/02byA.