2 3
Does This Look Level to You?
Most preventive maintenance Intervals for service are intertwined.
In other words, the 500-hour service includes the 250-hour service and
some other requirements. The 750-hour service may include another 250-
hour service and some other requirements. There is almost a nesting
quality of the PM schedule. Knowing that most Intervals of a PM Program
are variables of one another, the shop manager may not want the
redundancy of PM Requests if he/she knows that relationship.
B2W Maintain allows the flexibility to approach this in two ways. The first
is to set a Level on each Interval in a Program. Levels in Maintain have a
hierarchical relationship; the higher the Level, the higher the priority when
Intervals collide. To illustrate this, we know that the 250-hour Service
will trigger a PM Maintenance Request every 250 hours, but, do we really
want a 250-hour PM Maintenance Request AND a 500-hour PM
Maintenance Request to deal with? If the answer is no, then Levels are
used. Each Interval is assigned a Level. The more frequent the PM Service
is, the lower the Level number.
In the above example, the 500-hour PM Maintenance Request will trigger
when the appropriate meter threshold is crossed, but B2W Maintain will
suppress the 250-hour PM Maintenance Request from triggering, because
it is included in the 500-hour PM Service. This relieves the administrative
cost of managing redundant PM Maintenance Requests.
Assigning Levels is a good
way to prioritize Preventive
Maintenance Intervals and avoid
redundant PM Requests.
TIP
