Managing Related Services with Relation Type Z

This document explains how Z-related services are set up, related to each other, and used.

Outcome

Minor, less comprehensive services that are included in larger, more comprehensive services are moved, thus ensuring that the maintenance interval is kept.

Z-related services provide a means of facilitating long-term service planning and budgeting.

Records are adjusted in 'Work Request. Open' (MOS170). Load and material requirements are also updated.

Before you start

Purpose

Z relations are used for long-term service planning in order to avoid planning identical jobs on a maintenance object at intervals that are too short.

When

Z relations can be used when a maintenance object has a service structure with services that have intervals and are more or less comprehensive. The more comprehensive services include the less comprehensive services. This means, for example, that if a smaller service contains an oil change and a meter reading check, then the larger service also contains these jobs, as well as extra jobs that are not included in the smaller service.

How

This example illustrates how the relation can be set up for a maintenance object with three different services. Note that more levels can be added.

Product Service Repeat Interval
Locomotive A - small 10,000 km
Locomotive B - medium 50,000 km
Locomotive C - large 100,000 km

The large service in the example includes the small and medium services and the medium service includes the small service.

The diagram below illustrates how these services will be planned when Z relations are not used.

As indicated by the diagram, the smaller services are not automatically moved in the service plan in (MOS170), and operations that are included in both the more comprehensive and the less comprehensive service are doubled. However, if these services were related with relation type Z, the result would be as indicated in the diagram below:

As indicated, the less comprehensive services are automatically adjusted in the service plan in (MOS170).

Structure

  1. Service Notes

    Service level: Services that should be related to each other with relation type Z must all be defined with the defaulted service level. Once you start defining the relations, the service level will automatically be adjusted and the most comprehensive service will be assigned service level 1.

    Calculation method: The calculation method must be set to 3 when the services to be related are defined.

    Adjust code: The adjust code on the (MOS300/F) panel must be set to 0 when the services to be related are defined.

    Note that all the services that are to be included in the Z-type relation structure should initially be defined as stand-alone services, that is, have the service level set to 9 and the calculation method set to 3 (Not affected by other services) in (MOS300/E).

  2. Service Relation Notes

    Always start by relating services to the most comprehensive service. Continue with the second most comprehensive service and work your way down to the least comprehensive service. The relations should be defined in 'Service. Connect Related Services' (MOS309), as illustrated below for the locomotive's services mentioned in the previous example.

    Relations for Service C

    Seq. No. Prod. No. Stp Service Rel. Man.
    001 Locomotive XXX A Z 1
    002 Locomotive XXX B Z 1

    Relations for Service B

    Seq. No Prod. No. Stp Service Rel. Man.
    001 Locomotive XXX A Z 1

    Note that you should only relate services that are less comprehensive to a service.

Limitations

If configuration is not used, it is only possible to use Z relations on the individual item that is specified on the main service. If configuration is used, it is possible to use Z relations on configuration positions. This will allow zero setting of different individuals.

Related topics