HierarchyĤ.7 Hierarchy short text – Here we can define short text for the hierarchy.Ĥ.8 Offset- Here we can define the offset of the package. Or a non-hierarchical maintenance strategy. 1 Monthly, 1 Weekly, etc.Ĥ.5 Cycle short text – Here we can define the shot text of the task frequency.Ĥ.6 Hierarchy – Here we can define the packages that will follow a hierarchical maintenance strategy Hierarchy Monthy, Weekly, etc.Ĥ.4 Maintenance cycle text – we can enter a short description of the task frequency.
1,2,3…Ĥ.2 Cycle length- Here we can define the task frequency.Ĥ.3 Unit- Here we need to define the Unit of the task frequency. To create a new maintenance package we need to fill some fieldsĤ.1 Package no- We need to define the Consecutive number of the maintenance packages. Package sequence- Here we need to define different packages with their frequency.
So in between two 1 monthly call objects, there will be gaps for 30 working days, not 30 calendar days) PlanDateĤ. PlanDateįor the maintenance strategy with a Time- factory caldr-based scheduling indicator the call object’s (work order or notification) planned date will be calculated based on the frequency but holidays will not be counted. PlanDateįor the maintenance strategy with a Time- Key date-based scheduling indicator the call object’s (work order or notification) planned date will be calculated based on the frequency but the planned date will be the same date. For measuring counter (Like running hour) based maintenance strategy we will use scheduling indicator “Activity”.(For the maintenance strategy with a Time-based scheduling indicator the call object’s (work order or notification) planned date will be calculated based on the frequency.
For a time-based maintenance strategy, we can use the following scheduling indicators, “Time”, ” Time – Key date” & ” Time – factory caldr”. Scheduling indicator (Mandatory field ) – We have a total of four types of scheduling indicators. Description ( Mandatory field) – we can use this field to identify whether it’s a hierarchy or non-hierarchy-based maintenance strategy.ģ. Name ( Mandatory field) – To identify the maintenance strategy we need to provide the name.Ģ. To create a new maintenance strategy we need to fill some mandatory fields and some non-mandatory fields.ġ. Or through Fiori App “MAINTAIN MAINTENANCE STRATEGIES” To create a maintenance strategy we use TCODE IP11. the higher frequency tasks do not include the lower frequency tasks like the below table Let’s consider another situation where we need to use a non-hierarchical maintenance strategy, i.e. in the work order, we would see only one task which is the highest frequency task in the particular call. We could see in the higher frequency tasks, the lower frequency tasks are also included, so for the above situation we can use a hierarchical maintenance strategy, i.e. Let’s consider a situation where the maintenance tasks for a Pump define as belowģM task – Greasing + Seal inspection + Coupling inspectionĦM task – Greasing + Seal inspection + Coupling inspection + Alignmentġ2M task – Greasing + Seal inspection + Coupling inspection + Alignment + Internal inspection We can define a maintenance strategy as hierarchical or non-hierarchical or as a combination of both of them. If the tasks have only one frequency we might not use a maintenance strategy.īefore creating a maintenance strategy we may need to analyze how the tasks have been defined by the reliability team. If we need to perform some maintenance tasks on a piece of equipment or a group of equipment or a system based on some predefined frequency (more than one frequency) we use a maintenance strategy. I am trying to capture some information related to maintenance strategy in this blog post.
0 kommentar(er)
