Defining Services to Describe the Jobs that are Performed on an Object

Outcome

A service for either an object or a general service is defined, the location where the service is performed, what materials are used, how long it takes to perform, and how many workers are required is specified.

A work order is always based on a service. You can convert a service into work orders in these ways:

• Automatically by meter readings in 'Equipment. Report Meter Reading' (MOS160)
• Manually from 'Service. Open' (MOS300)
• Manually in 'Work Order. Enter' (MOS001)
• Manually in 'Work Request. Open' (MOS170)
• Manually in 'Work Request. Quick Entry' (MOS185).

You can link a service to maintenance objects. This means that a service is automatically suggested when the object should be serviced.

Information about services is stored in these files:

• Services (MPDSCF)
• Service facility (MPDSRC)
• Maintenance limits (MOMPGL).

Before you start

• If you want to link a service to a serialized item or piece of equipment, this must be defined in 'Equipment/Serialized Item. Open' (MMS240).
• If you want to link a service to an item, this must be defined in 'Item. Open' (MMS001).
• If you want to link a service to a configuration position, this must be defined in 'Model/Site. Connect Position' (MOS440).
• A work order type must be defined in 'Work Order Type. Open' (MOS120).
• A planning policy must be defined in 'Planning Policy. Open' (MMS037).
• Event types must be defined in 'Event Type. Open' (MOS320).
• If you want to use a process type, this must be defined in 'Process Type. Open' (CRS256).
• If you want to use a service group, this must be defined in 'Service Group. Open' (MOS325).
• If you want to use an accounting control object, this must be defined 'Control Object. Open User-defined' (CRS335).
• A work center must be defined in 'Work Center. Open' (PDS010).
• If you want to use a default meter, this must be applied in 'Settings - Maintenance 1' (CRS788) if you use the H panel at entry.

Follow these steps to define new service - standard entry

This entry method is usually used when the system is configured for maintenance of components, for example aircraft, trains, and buses.

1. Define Basic Service Data

   Define services in 'Service. Open' (MOS300/EF). When you define a service, you specify basic service information such as the validity dates for the service, how often and a planned service should be performed and how it should be scheduled, which facility the service should be connected to, which order type the service should use, the rules for planning the work, and how comprehensive the service is.

   You can also specify service revisions, warranties, and grouping criteria for each service.

2. Connect Operations

   The different steps in a service are described in 'Product. Connect Materials/Operations' (PDS002). Each service can consist of several smaller jobs. For example, a repair of a pump may consist of three steps. First the pump needs to be cleaned, then taken apart, and put back together.

   For each step, you also specify the work center in which the work is performed, the time it takes to perform the work, and the skill required.

   You can describe each step by its elements. This is done in 'Operation. Connect Operation Elements' (PDS027). The operation element level is also used to connect tools, skills, drawings, and permits to an operation.

3. Connect Materials or Spare Parts

   The material used in each service is also described for each operation in (PDS002). For example, a regular car service might use engine oil, spark plugs, and brake pads. Some of these materials might be held in stock, while others might have to be purchased.

Follow these steps to define new service - quick entry

This entry method is usually used when the system is configured for plant maintenance.

1. Define Basic Service Data

   Define services in 'Service. Open' (MOS300/H) when using quick entry. When you define a service, you specify basic service information such as the validity dates for the service, how often a planned service should be performed according to the default meter, how it should be scheduled, which facility the service should be connected to, which order type the service should use, and the rules for planning the work.

   You also define the work center in which the job is performed, the planned run time of the job, and optional alarm limits and trend limits.

2. Connect Materials or Spare Parts

   The material used in each service is also described for each operation in (PDS002). For example, a regular car service might use engine oil, spark plugs, and brake pads. Some of these materials might be held in stock, while others might have to be purchased.

Additional service data

This section describes some of the related data that can be connected to services using the available related options in (MOS300). See related documents under the Related topics section.

• Maintenance program

  Connect maintenance programs to services in 'Maintenance Program. Open' (MOS310).

  Maintenance programs are company-specific keys that identify all related maintenance requirements. A typical maintenance program is based on: different types of operations, changes based on seasonal demands, different customer demands, and manufacturer recommendations. The maintenance program is specified for each serialized item, and is normally related to the highest level of the structure (for example, aircraft). If necessary, you can specify exceptions on any level. Maintenance programs are also included in customer order information and are used to manage functions with maintenance-program dependencies.

  You can connect several maintenance programs to a single service, making it possible to use different maintenance limits depending on, for example, different conditions where the equipment is used.

  Using the F13 setting 'Numbering system', you can define a logic for the naming rule for maintenance programs.

  You can use several fields from (MMS240) to define the usage of a maintenance program. These fields can also be used to find a similar maintenance program that you want to copy to a new maintenance program for similar equipment. (Customer, Agreement, Fleet, Environment, Industry Application, Equipment Group, Equipment Class, Equipment type)

  When copying a maintenance program, including ECO-managed services (maintained in 'Service Revision. Open' (ECS300)), specific functionality is available.

  When performing 'Copy', you can select 2='Yes, MOS300 and ECS300' from the 'Copy/del rel' dropdown list. This means that ECO-managed services are copied and revised based on the included services in 'Maintenance Program. Connect Services' (MOS323) connected to the 'From' maintenance program. If a service is found to be ECO managed, it is revised in (ECS300) and a maintenance limit is added to that service against the new maintenance program. Other related information, such as related services, document references, modification applicability, are also copied to the new maintenance program. Each revised ECO-managed service remains in status 10 to allow the responsible engineer to validate whether the service is to be included in the new maintenance program. If not, the new revision of the service can be deleted, and the corresponding record in (MOS323) is deleted. The engineer can also update related information for the service before releasing it to production. To facilitate finding all the services revised in the background, the maintenance program in the settings panel can be activated. If the 'Display filters' field is activated on the B panel, the maintenance program is used as a filter field, in combination with the other filter fields.

• Maintenance limits

  For each service, you can define different limits in 'Service. Connect Maintenance Limits' (MOS311) by specifying the interval at which the services should be performed.

  If the service record was created using the quick-entry H panel, the defaulted service meter must be edited in (MOS311) since the service record is locked once it is created. Additional meters can also be connected to the service in this program.

  If a maintenance limit is added against a maintenance program, a record is automatically created in (MOS323).

• Related service

  You can use related services to link services together. Related services are, for example, used when you want the main service to trigger other services. You can define service relations in different ways depending on their use.

  Connect related services to a main service in 'Service. Connect Related' (MOS309).

• Service prices

  You can specify a price for each service in (MOS300). This function is normally used when you sell maintenance to external customers. This makes it easy to use fixed prices on maintenance customer orders since the price specified on the service is proposed.

  Specify service prices in 'Service. Enter Prices' (MOS306).

• Events

  You can use events to speed up the order entry process for internal orders. You can specify only the event, and by doing so, trigger several different services with the same linked event.

  Connect events to services in 'Service. Connect Event' (MOS305).

• Warehouse priority

  You can define a priority to determine the warehouse from which materials defined in the service product structure should be issued. The service warehouse priority is defined for each facility and overrides any warehouse priority specified on customer agreements.

  Define warehouse priority rules in 'Service. Connect Warehouse Priority' (MOS315).

• Alternate facility

  You can connect a service to more than one facility. This is generally done when you can perform the service in more than one facility.

  Connect alternate facilities in 'Service. Connect to Facility' (MOS301).

• Service dates

  You can specify certain dates on which a service is supposed to be scheduled. These dates can either be manually specified or calculated automatically.

  Service dates are specified in 'Service. Connect Service Dates' (MOS322).

• Document references

  You can connect a document reference to each service in 'Service. Connect Documents' (MOS303). Such documents are, for example, service bulletins and engineering orders.

• Specific requirements

  You can use the specific requirement, together with the category, for sorting and selecting maintenance orders in (MOS170). You can use the specific requirement category to group specific requirements such as panel, zone, or equipment. Some specific requirements are predefined, and you can use them in (MOS120) to sort and split the work orders.

  Connect specific requirements to services in 'Service. Connect Specific Requirements' (MOS302).

• Modification applicability

  Some services might become obsolete as a result of an engineering order, and some services might be the result of an engineering order. You can specify whether a service is valid before or after engineering orders are performed on the maintenance object in 'Service. Connect Modif Applicability' (MOS307).

• Certified service

  Some work must be approved by an authorization and have an approval tag printed for it. This is common within industries that are regulated by law, such as the aviation industry and nuclear power production.

  Connect an authority in 'Service. Connect Authority Certification' (MOS304).

• Alternate supplier

  You can connect an alternate supplier if a supplier is specified in (MOS301). This information should be used for information only.

  Connect alternate suppliers in 'Supplier. Connect Item' (PPS040).

• Service revision

  You can use service revisions to track changes when a service is modified. Using revisions allows you to modify an existing service without disturbing ongoing work. The new revision is transferred to production when it is fully modified. A new revision of a service is, for example, created when an operation, material, or the time consumption in a service is changed.

  Service revisions are created in (ECS300).

Service level

The service level is a way to describe how comprehensive a service is. The service level is used together with the calculation method to determine how future service requirements are calculated.

The valid service levels are:

0 = No service level

1-9 = Service level used and level 1 is the highest controlling level.

The maintenance interval for a service is recalculated when another service of a higher service level is performed. The calculation method determines how this calculation is performed.

Example:

In the example, the major service is more comprehensive than the minor service and is assigned level 1. When the major service is performed, it can affect the planning of minor services with a higher service level. A typical result is shown in the next example.

Since the major service is performed every 1,000 hours, the minor service does not need to be performed until 300 hours after the major service (at 1,300 hours).

Calculation method

The calculation method determines how the service is affected by other services and service levels.

The valid alternatives are:

0 = This service does not affect the calculation of the next service. This option should only be used for services without a maintenance interval.

1 = This service is only affected by more comprehensive services. A level 5 service is reset by services with level 4, 3, 2, and 1.

2 = This service is affected by services with the same level and services with a higher service level. A level 5 service is reset by services with level 5, 4, 3, 2, and 1.

3 = This service is not affected by other services and levels. Note that if alternative 3 is selected, the service level must be set to 9.

Adjustment code

The adjustment code determines how the next scheduled service is affected by the most recent service if it was performed prior to, or after, its original planned date. You can adjust the next service to keep the maintenance interval and move to an earlier or a later point according to the service planning meter.

Maintenance intervals are usually defined according to calendar time or another accumulative meter.

The valid alternatives are:

0 = Maintain the original schedule and ignore the completion date of the previous service. A service that is planned to be performed each Monday always falls out on the Monday, regardless of when the previous service was reported.

1 = Allow the next service to be rescheduled earlier or later based on the completion date of the previous service (float permitted both earlier and later). In this case the maintenance interval is always kept. If a service has an interval of seven days, the next service is planned seven days after the previous service was reported.

2 = As alternative 1, but only allow the next service to be rescheduled to an earlier date (float permitted to an earlier date). If the previous service is performed earlier than its planned date, the next service is moved to an earlier date and the interval is kept. If the previous service is reported later than its planned date, the next service falls out on its original planned date and the maintenance interval is shorter.

3 = As alternative 1, but only allow the next service to be rescheduled to a later date (float only permitted to a later date). If the previous service is reported earlier than its planned date, the next service falls out on its original planned date and the maintenance interval is longer. If the previous service is reported later than its original planned date, the next service is moved to a later date and keep the maintenance interval.