Define Settings for Maintenance 1 (CRS788)

… the consolidated facility that, along with the work center type, is used for planning and defining services regardless of the work center in which the work is performed. When maintenance work orders are planned, the work center type determines the actual work center in which the order is performed.

Use a consolidated facility when M3 is to be used for maintenance within several facilities, for example when you have a number of shops where similar jobs are performed. When you use a consolidated facility, you only have to define services against this facility. When the work order is created this information is used for the other facilities where the service should be performed.

When working with plant maintenance it is most common to leave this field blank.

… whether scheduled services should be included in 'Work Request. Open' (MOS170). Scheduled services are jobs that have meter limits.

This setting is normally selected.

… whether unscheduled services should be included in the master schedule.

Select this setting if you want unscheduled work to appear in (MOS170). Normally, this is not selected.

… whether engineering orders should be included in the master schedule.

If you use the system for plant maintenance this setting is normally not selected.

… whether planned work orders/work requests should be generated for equipment or components that are not installed, but are kept in the warehouse when the master schedule is regenerated.

If this setting is selected, planned work orders/work requests are generated for services with inventory maintenance 1 or 2 in (MOS300/E).

This setting is normally selected.

… the warehouse to be used when components are installed in an aircraft or a plant. This warehouse permits helps track components and parts while they are installed in a plant or an aircraft. No accounting takes place when removal and installations are done from and to the plant or aircraft. This warehouse is used when Inventory Accounting Equipment (IAC) are created.

This warehouse should be unique for this purpose, and you should not use a real warehouse. When an equipment or component is installed within the equipment structure, or in for example an aircraft, it is stored within this warehouse, when it is not installed in the warehouse then it can be in another warehouse such as, for example, a motor warehouse. 'Balance Identity. Display' (MMS060) and 'Balance Identity. Open Toolbox' (MWS068) can be used to see the IAC equipment which is installed in the plant and also in the warehouse. This warehouse is effectively a 'logical' warehouse so that M3 thinks IAC equipment installed in the plant or aircraft is actually in a warehouse. The contents of this warehouse is automatically excluded from stock valuation reports. One suggestion here is that this installed warehouse is linked to a facility created especially for linking to this warehouse (rather than linking it to a general facility).

A warehouse must be specified in this field.

… a location that is defined per warehouse and is thus below a warehouse in a tree structure.

The location is part of the key identity for the balance IDs. Those are created when items are received and correspond to a combination of warehouse and location.

A location must be specified here and be connected to the warehouse for installed items.

… a transaction type that is used to define a number of settings that determine how removal transactions are processed. This acts as a default in 'As-built Structure. Update Removal/inst' (MOS125). If movements are regularly carried out then this order type should be one defined for install and removal rather than just removal.

This order type must be specified.

… a transaction type that is used to define a number of settings that determine how installation transactions are processed.

See also description in the previous section.

… a location where a component is to be stored after being removed to determine if an error can be re-created or repeated.

This provides a default for the removal and installation process in (MOS125) when the installation and removal order type (MOS123) used in (MOS125) has the 'still serviceable' flag selected. This location should be in a 'real' warehouse and be set with the status proposal flag as 1 or 3 (not 2) in 'Stock Location. Open' (MMS010).

A location should be specified here.

… a location where a component/equipment is to be stored while waiting to be shipped for maintenance work.

This provides a default for the removal and installation process in (MOS125) when the installation and removal order type (MOS123) used in (MOS125) has the 'still serviceable' flag blank. This location should be in a 'real' warehouse and be set with the status proposal flag as 1 or 3 (not 2) in 'Stock Location. Open' (MMS010).

… the character(s) you wish to use to separate the product number for display purposes in (MOS300).

Example: To display product number (ABC456) as (ABC-456), specify three blank spaces followed by a dash (-).

This field is normally left blank.

… the character(s) you wish to use to separate the service ID for display purposes in (MOS300).

Example: To display service ID (REP489) as (REP-489), specify three blank spaces followed by a dash (-).

This field is normally left blank.

… the unique identification of a customer. It can contain up to ten positions, and is alphanumeric.

For temporary customers (customer type 9), the customer number must be within a defined range where only customers with customer type 9 can be specified.

This field is normally left blank.

... the structure type to be used as the installation structure.

In order for the configuration structure to be used, it must be defined in (MOS445). It must also be specified in (CRS788).

This applies if you use the system for plant maintenance:

This must be defined in order to create the plant structure. The Site Browser, (MOS446), uses the structure type to decide which spare parts to display in the structure. For Plant Maintenance, if structure types are enabled in (CRS787) then they must be used. Whatever structure type is used here, the structure type used in parameter 17 must be different.

... the structure type to be used for the complaint analysis.

In order for the configuration structure to be used, it must be defined in (MOS445). It must also be specified in (CRS788).

This structure type must not be the same as the structure type for installation.

This field is left blank if you do not use complaints, which would normally be the case for plant maintenance installations.

... whether to carry out a check to ensure that material and operations have been reported.

The valid alternatives are:

0 = No

1 = Yes, and issue warning if material and operations have not be reported

2 = Yes, and require the material or operations to be reported before allowing the transaction to be completed.

This should be selected to receive a warning message when a work order operation is reported in 'Work Order Operation. Report' (MOS070) whilst outstanding material transactions remain or when closing a work order in 'Work Order. Close' (MOS050) when outstanding material or operations remain. To provide a warning only then option '1' can be selected. It is however suggested that option '2' be defined as this forces the user to cancel or complete the outstanding transactions before the operation or work order is closed. This then avoids undue build up to old material requirements or incomplete operations.

This field can be updated at any time.

... whether F16 must be used in order to update components/equipment to serviceable status when a work order is closed.

This field is normally not selected.

... whether to display the date when entering the configuration structure.

This field is normally not selected.

... the general service costing model. The costing model is defined in 'Costing Model. Open' (PCS025). A different costing model can be specified per service facility record in 'Service. Connect to Facility' (MOS301/F).

The maintenance cost model normally includes materials (AXX), labor (BXX) and contractors (DXX). You should discuss the requirements for this parameter with the FAM consultants. The maintenance cost model is displays in components such as 'Product Costing. Display' PCS300 and 'Work Order Costing. Display' (CAS305) when called from maintenance components.

A costing model should be specified here.

... the separating character between the configuration position and the service in (MOS300).

This feature is not used. The field should be left blank.

... the related service to be automatically generated when a related service is created automatically. This service must be defined in (MOS300).

This would normally be used when a component must be removed before the main service can be performed.

A related service is automatically generated when these conditions are met:

- Parameter Create related ser in (MOS300/P) is activated.

- The main service requires that a component be removed before the actual service can be performed. This requirement is identified by the field Component installed in (MOS300/F).

This field is normally left blank when using the system for plant maintenance.

... whether there must be a customer order reference on all work orders (WOs).

If this parameter is selected, the reference is checked in these programs:

- 'Work Request. Quick Entry' (MOS185)

- (MOS170)

- 'Work Order. Reschedule' (MOS010)

- 'Work Order Operation. Report' (MOS070).

This field is normally not selected when using the system for plant maintenance.

This parameter should be selected if maintenance customer orders are used.

... how the system should process meters when more than 1 exist against a service in (MOS300). A competing meter can be compared to a car service, that is every 6 months or 10,000Km.

The valid alternatives are:

1=Earliest occasion should trigger the service

2=Latest occasion should trigger the service

3=Compete as in alternative 1 after first threshold has been reached

Using option 1, the car service would become due when the first meter becomes due, parameter 2 would trigger when the latest became due.

If you select option 3, the service is triggered when the first meter reaches its limit after the threshold has been reached. With this setting, the interval meters compete after the threshold has been reached.

This parameter acts as a default for (MOS300/F).

... whether to accumulate the balance for items connected to the same function number.

This parameter is normally not selected for plant maintenance.

... whether the basic data should be checked to ensure that a WO can be established for the individual item/equipment at the selected facility.

This parameter should only be selected during system setup as it may as it may affect system performance.

... the level of integration to the 'fixed asset module' when an equipment or component is scrapped.

The valid alternatives are:

0 = No integration

1 = Send a mail for each transaction

2 = Start each component in the fixed asset module

If M3 Fixed Assets are not used then this option should not be selected (alternative 0). If fixed assets are installed then this option can be used to send a mail, or option 2 can be used to start each fixed asset component (FAS145).

The integration occurs when these transactions are done: - Removal and installations (MOS125) - Sales (COS100) - Scrap (MOS890).

... a site to be created.

Entry of this code automatically configures the system for use in plant maintenance. Be careful when entering this code - it is time consuming to remove the configuration if the wrong characters have been specified and the Enter key pressed!!! For muti-site installations, there are 2 ways in which you can use the site. One way is to have one site per facility, the other is to have multiple sites per facility. One site = one facility is likely to be the better solutions.

This field must not be left blank if you use the system for plant maintenance, but it may be blank if you use the system for depot service or aviation.

... the standard numbering system to be used for plant structures.

This code validates the structure of the position and equipment numbering systems. Even if the numbering system is unstructured a code must still be defined. This is defined in 'Standard Numbering System. Open' (CRS247) and 'Standard Numbering Level. Open' (CRS248).

This is a mandatory field.

... how far into the future service requirements planning is done.

This determines how far forward service definitions are generated when (MOS999) or (MOS170/F18) are used. It would be normal to generate for maybe 365 days ahead. This default is copied to the equipment when created. Each equipment/component can have a different value by using (MMS240) and editing the equipment directly.

This is a mandatory field.

... a period frame template which is used to group days in appropriate periods.

Each template ID is user-defined and can include up to 50 periods/columns with varying lengths. The period frame template specified per planning unit is also used for forecast distribution, if appropriate.

Each period template is defined by entering three pieces of information in four intervals:

- Number of periods/columns

- Unit multiplier, that is the number of units that form the period/column

- Unit, expressed in one of these alternatives:

1 = Days, 2 = Weeks, 3 = System periods.

Note that each template can contain a maximum of 400 buckets.

In addition, you can determine the manner in which eventual changes from one unit to another should be processed by specifying whether overlapping should be used.

It may be logical to use existing codes defined for manufacturing. This field only affects non-calendar based inspections, such as running hours. Each equipment/serialized item can have a different value by using (MMS240) and editing the equipment directly.

This is a mandatory field.

... how material forecasting is done. The parameters defined for each forecast logic mainly determine how reservations should be matched against forecasts.

Forecast calculation methods are defined in 'Forecast Logic. Open' (FCS305).

It may be logical to use existing codes defined for manufacturing. This field only affects non-calendar based inspections, such as running hours. Each serialized item/equipment can have a different value by using (MMS240) and editing the equipment directly.

This is a mandatory field.

... the default unit of measure for all automatically generated items/equipment in 'Item. Open' (MMS001).

All balance information for the current item is always stored in this unit.

This is a mandatory field.

... whether the equipment/product spare parts structure in 'Product. Connect Materials/Operations' (PDS002) is updated automatically when a work order is closed. If this parameter is set, the System compares the parts usage from the work order in 'Work Order. Open Line' (MOS101) against the equipment's/product's parts structure in (PDS002). If additional items exist against the work order they are added to the end of the list. This field can be updated at any time. The processing also checks the item's type in 'Item Type. Open' (CRS040), if the item's type does not allow additions to the structure then overrides this parameter.

This parameter is normally selected.

... the planned work order created when inspection values that are outside the expected range are reported in 'WO Operation. Report Inspection Result' (MOS085). If this value is not specified then no alarm services are created.

Note that only services with the structure type set in 'Settings - Product Structures' (CRS787) can be selected. Alternatively, a service can be specified in 'Quality Inspection Result. Connect Value' (PDS043) if another type of service is to be triggered.

This field can be updated at any time.

... the default meter for new service records.

A meter should be specified here. The field can be updated at any time.

... a default response for inspections which do not require a numeric feedback (such as pressure, temperature etc).

If the maximum, minimum and trend fields are left blank when an inspection is defined in (MOS300) then the System automatically uses the one defined here.

... the planning facility that the equipment will belong to and acts as a default when the site is created and then for each equipment created in that site.

The default can be changed in (MMS240) for the 'site item'. If multiple sites are to be created then this code may have to be changed each time.

... whether components/equipment should be continually re-planned. Re-planning is done for work order requests and material requirements for an equipment/component if circumstances changes which would have an impact on the planning process.

This setting acts as a default in (MMS240), but can be changed for each record.

... the default item type that is used when the site is created (the site is stored in (MMS001) where this code is mandatory).

This code is also set as a default for new equipment when they are created in (MMS240).

MIMA = 1 (miscellaneous cost items):

1. Create misc cost items in 'Item. Open' (MMS001). The items must be non-stocked and have a non-material item category. The non-material type must be set to 6 (Expense).

2. Expenses can be predefined in 'Product. Connect Materials/Operations' (PDS002), 'Service Revision. Connect Operation and Materials' (ECS312), 'Work Request. Open Line' (MOS171) and 'Work Order. Open Line' (MOS101) by creating material lines for the expense items. Predefined expenses appear in 'Report Miscellaneous Cost. Open' (COS155) for reporting.