This document explains how you connect one or more related services to a main service revision and sequence the jobs to be performed. This allows you to have a group of services that are triggered by the main service and that are performed together with the main service. Related services are always kept together and are not rescheduled if one of them is performed earlier.
Use this instruction when you want to connect related services to a main service.
Refer to the concept document listed under the See Also section for further information on relation type Z.
Related services are connected to service revisions. The relation type determines how the related services are to be generated when the main service is triggered.
The service relation structure will be copied to (MOS309) when the service revision is transferred to the production environment.
Information about service relations is stored in the Related services (AOMPGR) table.
Start 'Service Revision. Open' (ECS300/B).
Highlight the service revision record to which you want to connect related services and select option 21='Related service' to display 'Service Revision. Connect Related' (ECS309/B).
Specify a maintenance program and a structure type, if applicable.
Specify a sequence number for the related service. Select New to display the E panel.
On the E panel, select a product for which the related service is valid and, if applicable, a structure type.
A product other than the product specified in the main service can be specified. For example, the main service can be related to an engine and the related service might contain work that you have to perform on the aircraft as a result of the work on the engine.
Specify the related service and the relation between the main service and the related service.
Note that if alternative B is selected, only the related service is generated. The other services are generated after the first service has been closed.
Specify whether the relationship is mandatory. Press Enter to finish.
If yes is selected on the B panel before you press Enter, then the related service is always generated when the main service is created. If no is selected, the related service is only referenced when the main service is created.
|Program ID/Panel||Field||The field indicates …|
… how the service relates to another service.
The valid alternatives are:
A = Perform the related service AFTER the main service is performed. This is suitable, for example, for re-torque services. Note that the related service should be defined as a non-scheduled service, but with an interval.
B = Perform service BEFORE the main service. Note that the main service will not be displayed in (MOS170) until the related service is completed.
C = Service related with CORRECTING deficiencies detected during inspection, operational tests or functional test.
F = Cannot finish service until related service is FINISHED.
I = Related services will only be created if the item is INSTALLED. This means that a related service is only created for items that are installed in a configuration. This relation type is mainly used for installations and removals.
P = Service PRECLUDES related service (information only).
S = Cannot finish service until related service is STARTED.
T = TRIGGERED by main service. If T is used, this scheduled service will only start when the main service is performed. Competing type 3 has to be used in (ECS300/F) on the related service.
W = Perform the service WITH the related service. This relation type is used when services are possible or convenient to perform together. The relation can be mandatory or non-mandatory. If non-mandatory, a prompt in (MOS170) can be used to select services to perform together.
Z = ZERO set of related service. This relation can be used for zero setting of other services. If configuration is not used, it is only possible to have Z relations on the individual that is specified on the main service. If configuration is used, it is possible to have Z relations on configuration positions, which makes it possible to zero set different individuals. Note that the main service and the related service must be defined and treated as stand-alone services. The service history will be updated for the Z-related service when any of the related services are updated.
If alternative B is selected, then only the related service will be generated. The other services will be created in (MOS100) after the previous service has been performed and closed.
If any of the other alternatives are selected, the related services will be generated together with the main service.