pm-006維修求和更正性訂單的創(chuàng)建流程maintain req.order process

Li·Contact文檔版本修訂描述文檔作者LiJuelinLiJuelinLiJuelinAPPROVAL日期 版本 人角色Approver 人 在流程層次結(jié)構(gòu)中的位置PositiononProcess 適用范圍Areaof 聯(lián)系人（關(guān)鍵用戶）Contact(Key- 術(shù)語 流程目的和范圍Processgoalsand MaintenanceOrder 業(yè)務(wù)步驟說明Descriptionofprocess 處理和資本性支出的判斷（子流程）流程說明InsuranceHandlingandCAPEXIdentificationSub-process 其他說明Other 改進(jìn)分析 其他相關(guān)文檔Crossreferenceto 接口程序 SAP系統(tǒng)修改和用戶出口程序SAPmodification, 使用技巧和竅門Hintsand -i

nt nt單的創(chuàng)建PLM.NOCMMaintenanceRequestandCorrectiveMaintenanceOrderThisprocessisusedformaintenancerequestandcorrectivemaintenanceworkinallproductionbranchntofHuaxincementCO., 朱KeyKeyKeyKeyofWuXue設(shè)備的影響程度分為M1、M2、M3和Z1共四種單據(jù)。Notifications:Notificationskeepoperationormalfunctioninformationofthemaintenanceobject,conveymaintenanceinformationandrequirements.Sometimesthenotificationcanbesupplementedandcompletedlater.Notificationsinclude4typesforimportantanddamageofthetechnicalobject:M1,M2,M3andZ1.PM01更正維修工單：用來執(zhí)行修理設(shè)備主要或次要功能故障的活PM04工單：將在倉庫的設(shè)備維修到象新的一樣狀態(tài)，為未來的Orders:Maintenanceordersareinstrumentsformaintenanceprocesscontrolandmanagement,guidemaintenancework,maintenancenandstrategy.Ordersareusedtonmaintenancetasksandnortrackthecostsincurred.Theorderusuallyreferstoatechnicalobject(functionallocationorequipment)andisconfiguredataworkcenter,butthenningfunctionsdonotnecessarily.Ordersandnotificationscanbeusedindependentlyofoneanother.However,theyareusuallycombinedtoutilizetheadvantagesofbothinstruments.MaintenanceorderswillbedefinedinSAP-PMwiththefollowingtypesanddescriptions. Corrective:Itiscreatedforanymaintenanceworkperformedonapieceofequipmenttorepairapartialorcompletefailureofanequipment'sprimaryorsecondaryfunctions,itisalsocreatedforanymaintenanceworkperformedonapieceofequipmentthatisamodificationoftheoriginaldesign,butthemaintenanceworkdoesnotmeettheguidelinesasdefinedincapitalexpendituresmaintenancerule. Preventive:Itiscreatedforanymaintenanceworkperformedonapieceofequipmentthatisperiodicorcyclicalinnature. RefurbishmentOrder:Itiscreatedforanymaintenanceworkperformedonapieceofequipmentormaterialthatwillcompleyrestoretheequipment'soperationalcapabilityto'like-new'conditionandthisequipmentormaterialisthenstoredinthewarehouse/storeroomforfutureuse. InvestmentOrder:ItiscreatedforanymaintenanceworkperformedthatmeetstheguidelinesasdefinedinHuaxincapitalexpendituresmanagementrule.Processgoals:Thisprocesswillrecordandconveymalfunctioninformationfasterandmoreaccurate,savemoretimetoperformthemaintenancework.流程范圍：本流程應(yīng)用于各生產(chǎn)的所有生產(chǎn)設(shè)備被發(fā)現(xiàn)發(fā)生了需要更正性維Processscope:ThisprocessisusedformaintenanceactivityfrommalfunctionfoundtocorrectivemaintenanceordercreatedorinvestmentorderprocessstartedinHuaxincementCO., .productionbranchnt. 無MaintenanceRequestandCorrectiveMaintenanceOrderprocess

nning名稱名稱PM-006-MaintenanceRequestandCorrectiveMaintenanceOrder步驟描述StepWhenisthestepFillininspectingnotification,andinformmaintenance1Walk-byInspectors(containproduct,mechanical,electricityandinstrument)fillintheirinspectingchecksheetAfterwalk-byinspectorsfindabnormalconditionofthemaintenanceobject.accordingabnormalconditionfoundworkstep2Productionshiftsuperintendent,andengineerallcancreatemaintenanceNotificationCreatorreceiveperiodicallychangenforequipment,ortechnicalimprovementinminiature3StartinsurancehandlingandCAPEXidentificationsub-processCreateorderwillandpurchaserequisitioninMMInforminspectorand4Maintenancennercreatesorderaccordingtomaintenancesolution,generatereservationsandpurchaserequisitions,andstartsthenextprocessSub-processresultisthatmaintainingneededanditisn’t5Maintenancennerinformstheinspectorintime,andinformsshiftmonitorifmaintenanceneeded6MaintenancennercloseAfternnerhasinformedtheNote:Duringthemaintenancework,ifmalfunctionpointorcausefoundisdifferentfrommaintenancesolution.Youcanchangethemaintenanceorderlater.處理和資本性支出的判斷（子流程）流程說明InsuranceHandlingandCAPEXIdentificationSub-processdescription步驟描述StepWhenisthestepBeforemaintenancework,equipmenthasbeeninsureddamageverification1 nnercheckequipmenthasbeinsuredalreadyaccordingthescopeofCheckifequipmenthasbeeninsuredalready2InsuranceatonceInformInsurancecontacttoaskforInsurancedoDamageVerification3InsurancecontactFillInInsuranceClaimFormFillInInsuranceClaimInsuranceClaimFormis 4MaintenancennersendsInsuranceClaimtofinancewillhandinsuranceclaimInsurance執(zhí)行，但如果發(fā)現(xiàn)是需要公司賠付的故障則需要等公司現(xiàn)場(chǎng)Thisstepcanbeperformedatthefirststep.ButifinsuranceneedstodoDamageVerification,itcanbeperformedlaterorin anditisCAPEX.nnercanandshoulddothemaintenancesolutionaccordingthechecksheetandnotification.Ifnecessary,hecandothefieldworkandcheckthemalfunctionpoint.5ifmaintainingneededanditisCAPEXbyhimselforwithhelpofothertechniciansaccordingtheruleofCAPEX.IfCAPEX,gototheinvestmentorderThedowntimeinZ1notificationswillbethedurationofthedowntimeoftheproductionTheZ1notificationanddataincludedwillbeusedfortheKPI工廠的任何員工都可以通過任何交流方式向部門或提出維修請(qǐng)求，萬一出現(xiàn)于已有單生成維修工單PM01類型。Anystaffinthentthroughanymeansofcommunicationcanraiseamaintenancerequesttoteamleaderorhigherlevel.Incaseofemergency,Productionsuperintendent,maintenancesuperintendent,andMaintenancennercancreatemaintenanceordertypePM01withnotificationtypeM2.therequestcanbemadebycall,afterwhichalldatawillberecordedtosystemafteramaintenancejobstart.MaintenanceordertypePM01canbecreatedforexistingnotificationinnormalcorrectivemaintenance.Regardlessofnnedorunnnedmaintenancejobs,amaintenancenotificationisrequiredinordertokeeptheinformationregardingthemaintenanceobjectandtodescribetheconditionofthemaintenanceobjectsuchasobjectpart,symptom,andcauseofdamage.Multiplenotificationsareabletorefertoonemaintenanceorder.Listofmaintenancenotificationswillbeselectedbystatusasoutstanding,inprocess,postponedandcompleted.Userscanlistthenotificationsbasedontheirselectionscriteria.MaintenancenotificationtypeM1-MaintenancerequestwillbeconvertedtomaintenanceordersoftypePM01afteritisjustifiedthatmaintenanceworkisrequired.Aftermaintenanceworkhasbeenfinished,maintenancennerhastoenter/updatethetechnicalfindinginformationsuchasobjectpart,symptom,causeofdamage,andactivitiesperformedinthenotificationbeforeclosing(includingmalfunctiondowntime).Notallmaintenancerequests(notification)willbeconvertedtomaintenanceorders.Itisuptothemaintenancennertoissueornottoissuemaintenanceordersfortherequests.Notificationsthatarenotconvertedintomaintenanceordercanstillberecordedtechnicalinformationorcanbedeleted(setdeletionflag).MAC-SAP4種維狀的信息，在這些描述中，不包含備件及原因。癥狀的代碼從HOLCIM公司中編輯的代SAP－PMM1，M2，M3Z1將使用相同的原因代碼，這些代碼是從幾家先進(jìn)的Holcim公司總結(jié)出來的。這些代碼希望找到（設(shè)備）失效的根信息。使用MAC－SAP標(biāo)準(zhǔn)表和代碼能夠幫助維修計(jì)劃員很容易的進(jìn)行故障和影響的分ThemandatorycatalogsthatrequiredbyMAC-SAPstandardsuchasObjectpartcatalogs,Symptomcatalogs,andCausecatalogswillbeapplied.TheSymptomcatalogsandcodeswillbethesameforallfourtypesofmaintenancenotifications.ThesameSymptomCatalogwillbeusedforallEquipmentTypes.TheSymptomdescriptionsincludeonlysymptominformation.TherearenoObjectPartsorCausesincludedinthesedescriptions.TheSymptomcodesareacompilationofcodesfrommanyoftheHolcimgroupcompaniesthatareusingtheSAPPMmoduleandwhohavedevelopedthesecodes.ThenotificationtypesM1,M2,M3andZ1willusethesameCausecatalogs.ThesecodesarebasedonacompilationofCausecatalogcodesfromseveralgroupcompaniesthathavedefinedthesecodes.Thesecodesareanattempttofindtherootcauseofafailure.However,pleasenotethatitcansometimesbepossibletofindalowerlevelcause.TheseCausesarestrictlyCausesanddonotincludeObjectPartorSymptominformation.UsingtheMAC-SAPstandardcatalogsandcodeshelpmaintenance alstoeasilyperformFMEA(FailureModeandEffectysis). Thisprocesswillrecordandconveymalfunctioninformationfasterandexacter,Easytosearchforthehistoricalinformationofequipment,Easytogroup,categorizeand yzeinformation.分為M1、M2、M3和Z1共四種單據(jù)，其使用原則如下所示：能，創(chuàng)建維修請(qǐng)求通知單M1；響，Z1均要使用。BusinessRuleforselectingnotificationtype:Notificationsinclude4typesforimportantanddamageofthetechnicalobject:M1,M2,M3andZ1M1-MaintenanceRequest:TheM1MaintenanceRequestnotificationiscreatedwheneverthereisanactivityneededtobeperformedbythemaintenancedepartmentandthisactivityisnottheresultofapartialorcompletefailureofanequipment'sprimaryorsecondaryM2-MalfunctionReport:TheM2MalfunctionRep