SAP维护策略计划的应用案例

UsingMaintenanceStrategyPlansMarkW.ScottVestaPartnersLLC[LearningPointsCreatingmaintenanceStrategiesandPackagesUsingmaintenancestrategiesinTaskListsHowmaintenancestrategiesareusedinMaintenancePlansRealExperience.RealAdvantage.2[MaintenanceStrategiesRealExperience.RealAdvantage.[MaintenanceStrategy-DefinitionAmaintenancestrategydefinestherulesforthesequenceandfrequencyofmaintenanceactivities.Thestrategydoesnotprovideanydetailsabouttheactivity,objectordate.Maintenancestrategiesareassignedtoatasklistandalsoamaintenanceplan.Tasklistsbuiltwithamaintenancestrategycanonlybeusedonmaintenanceplansutilizingthatsamestrategy–thesearecalledstrategyplans.RealExperience.RealAdvantage.thesearecalledstrategyplans.YoucreateamaintenancestrategyandstrategyplanswhenyouhavetoperformmaintenanceactivitiesthatarebasedoneachotherorsupersedeeachotherStrategiescontainmaintenancepackageswhichdefinethedurationintime(e.g.weeks)orlevelofperformance(e.g.operatinghours)atwhichmaintenanceworkisrepeatedlyperformed.Therefore,strategiesareusedinbothtime-basedandperformance-basedmaintenanceandrepresentthemaintenance“cycle”.[MaintenanceStrategy–Definition(continued)Eachstrategythatiscreatedshouldhaveacommonunitofmeasure(e.g.weeks,months,hours,miles)–youshouldnevermixtheunitsofmeasurewithinagivenstrategy.Maintenancepackagesareassignedtotasklistoperations–anddefinethefrequencyandsequenceinwhichtasklistoperationswillappearasworkorderoperations.RealExperience.RealAdvantage.willappearasworkorderoperations.Maintenancepackagesareorganizedintoamaintenancepackagehierarchythatdetermineswhichmaintenancepackagesareperformedifseveralmaintenancepackagesaredueatonetime.Thehierarchycaneitherbe:Single-levelhierarchyMulti-levelhierarchy[MaintenanceStrategyTermsStrategyCodeDescriptionSchedulingIndicator(Type)StrategyUnitCallHorizonRealExperience.RealAdvantage.CallHorizonShiftFactorforLateCompletionToleranceforLateCompletionShiftFactorforEarlyCompletionToleranceforEarlyCompletionFactoryCalendar[SchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesSettingscanbeestablishedatthestrategylevelandtheywillcarryovertoeachindividualmaintenanceplanwhenitiscreated.MaintenanceStrategyvsSchedulingParametersRealExperience.RealAdvantage.[ComparingMaintenanceStrategytoPlanStrategyFieldChangeableorFixedinPlanSchedulingIndicator(Type)Limited(canchangebetween3typesoftimebased)(Cannotchangebetweentimebasedandperformance)StrategyUnitFixed–NochangesonPlanRealExperience.RealAdvantage.CallHorizonChangeableonPlanShiftFactorsChangeableonPlanShiftTolerancesChangeableonPlanFactoryCalendarChangeableonPlan(onlyonkeydateandfactorycalendarplans)[SchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesSchedulingTypes•Time-Based•E.g.–Every30calendardays•DoesNOTtakeintoaccountthefactorycalendar•Time-basedbykeydate•E.g.–Every30daysdoonthe28thofeachmonthMaintenanceStrategy-SchedulingTypeRealExperience.RealAdvantage.•E.g.–Every30daysdoonthe28thofeachmonth•Timebased–factorycalendar•E.g.–Every30workingdays,Optionforseasonality•Performancebased•E.g.–Every100Operatinghours,50,000tonsofcoalthrough,xxxxunitsmade,etc.[SchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesSchedulingTypeandParametersdefinedatStrategyLevelStrategies&PackagesmaintainedwithinIP11MaintenanceStrategies&Packages(Cycles)RealExperience.RealAdvantage.TimeBasedStrategyPackagesPerformanceBasedStrategyPackagesStrategyLevel[SchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesSettingscanbeestablishedatthestrategylevelandtheywillcarryovertoeachindividualmaintenanceplanwhenitiscreated.Unitdefinestimebasisonwhichschedulingcalculationsaremade.UsesameUnitwithinaStrategy.Oncethestrategyunitiscreateditcan’tbechanged.MaintenanceStrategy–UnitofMeasureRealExperience.RealAdvantage.[SchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesCallHorizon–PercentofthenextcyclethesystemwaitsbeforethenextcallobjectiscreatedCallhorizondetermineswhenamaintenancecallobject(e.g.WorkOrder,Notification)shouldbegenerated.Ifthedurationofthecycleis360daysandthecallhorizonis0%,80%,or100%,thesystemcreatestheorderafterthefollowingnumberofdays:•0%-Immediatecall(ordercreated360daysMaintenanceStrategy–CallHorizonRealExperience.RealAdvantage.•0%-Immediatecall(ordercreated360daysBEFOREplandate)•80%-Callafter288days,thatis80%of360daysorcreationoforder72daysbeforeplandate.•100%-Callafter360days,ontheplanneddate(canworkwellifcoordinatedwithIP30CallInterval)CallhorizonisdefinedinpercentagetermsonStrategyorindividualMaintenancePlan[CallHorizon–Example–Planwith30DayCycle100%HorizonCall&PlanDatesaresame50%HorizonCallDateis15DaysbeforePlanSchedulingParametersStrategySchedulingTypeActivityTypeActivityTypeActivityTypePackagesSAPMaintenanceStrategy–CallHorizonRealExperience.RealAdvantage.0%HorizonCallDateis30DaysbeforePlan[ShiftFactors&ToleranceTolerancedefinestheperiodwithinwhichlateorearlycompletionimpact