Service inspections and preventive maintenance scenarios

	Service inspections and preventive maintenance scenarios Measurements are used to determine the value of an item's variable (measuring quantity) in a specific situation. Example Tire treads depth. When measurements are registered for serialized items during inspections, maintenance notifications are generated, based on pre-defined maintenance trigger. The type of the measurement determines whether a trend (estimated behavior) and a measurement unit are used. For alphanumeric measurement types, used for measuring conditions instead of absolute values, trend and measurement unit cannot be defined. Measurement types are used for: Inspections on work orders for serialized items Inspections on service orders for serialized items Inspections on serialized items only Expected measurements on planned activities for preventive maintenance Counter value on serialized items that can be used in service contracts on the contract coverage lines Maintenance triggers sets Maintenance Trigger Set is a set of maintenance triggers that is used to trigger maintenance notifications when performing measurements. A maintenance trigger set is linked to a measurement type. A maintenance triggers set can be linked to a counter reading that is linked to a serialized item. Maintenance triggers Maintenance Trigger is a trigger that determines when maintenance must be performed for an item. A maintenance trigger is linked to a measurement type and consists of 1 or more maintenance triggers. The relation between the measurement type and a maintenance trigger set is 1 to many. When a measurement is performed (using a measurement type), Infor LN checks whether a maintenance trigger is defined for a measurement. If a maintenance trigger is defined and triggered, a maintenance notification is generated. It is possible to assign the maintenance notification to a person responsible for the follow up actions of the notification. Maintenance trigger assignments are used to determine which trigger set is applicable for which item, item group, etc when performing a measurement for a specific position. Maintenance trigger set is a rule book with an effective/expiry dates. The order in which trigger set are selected is as follows: Maintenance trigger set specified on counter reading of serialized item. Maintenance trigger assignment rule book. Maintenance trigger on reference activity measurement type. Measurement type. The Simulate Maintenance Trigger Set Rules (tsmdm0276m000) session is used to determine which trigger set is used. Inspections Inspections can be created manually (directly for an item) or generated using web services or reference activities when planning service orders/work orders. Inspections (measurement types) can be defined in Reference Activity - Measurement Types (tsacm3160m000) session for Item – Reference Activity combinations. When defining a reference activity, with inspections on a service order activity or work order activity, inspections are generated in Inspections (tscfg3100m000) session. Inspections can be: Generated from a Measurement, meaning, it is an inspection that must be executed. Retrieved from the physical breakdown structure. Retrieved from another serialized item. Retrieved from other counter reading. Note For advance inspections, besides setting up measurement types and maintenance trigger sets, counter reading must also be defined. Counter groups Counter groups can be used to support advanced measurement scenarios. Counter groups are used for numeric measurement types only. You can use counter groups to: Calculate trends for maintenance to be performed in future Retrieve measurements from other items or other measurements Define multiple trigger sets for one measurement The counter group is used to default the counter readings when a serialized item is created. On a counter reading, it is possible to determine where the inspections are sourced from. Trend information can also be defined on the counter reading. Trend calculation can be used to predict when maintenance is necessary. Trend calculation is : Based on a manually entered trend Retrieved from physical breakdown (only applicable if the counter is retrieved from the physical breakdown structure). Retrieved from specific item (only applicable if the counter is retrieved from another serialized item). Retrieved from another measurement type of type counter (especially if the wear is based on the usage) When a serialized item is created, a default counter reading is created for the serialized item. Infor LN defaults the measurement type from the service item data. The counter value can be updated manually or the counter value can be reset. You can define reset rules to indicate how counter values can be reset. Maintenance notifications Maintenance notifications are generated based on maintenance triggers that are applicable when registering measurements for serialized items during inspection. Based on the measurement type and position of the measurement, the applicable maintenance trigger set is determined. Infor LN uses the following search logic: From the counter readings defined for serialized items From maintenance trigger set assignments From reference activity From the measurement type Maintenance notifications follow-up Based on the maintenance notification, you can decide the follow-up required for the maintenance. When a maintenance notification is generated it must be possible to set the maintenance notification to: Ignore for Now Always ignore Transfer to a planned activity, service order/work order and so on Transfer maintenance notifications Maintenance Notifications can have a follow-up activity defined indicating the next maintenance task that must be performed on the specific serialized item. These maintenance notifications can be transferred to various objects, such as, service orders, internal work orders, service order quotations and maintenance sales quotations. Preventive maintenance scenarios Preventive maintenance scenarios are used as the basis to generate planned activities. A maintenance scenario has scenario lines based on which planned activities can be generated; based on time (example 12 times a year), based on time according to a predefined pattern (example after 2 months small maintenance, after 3 months big maintenance, after 5 months small maintenance), and based on usage (example after 10000 km, execute maintenance or after profile of tire is below 3 mm). Preventive maintenance scenario lines Based on the preventive maintenance scenario lines, a maintenance plan is generated for the serialized item. You can define the following types of scenarios: Usage-based scenario For a usage-based maintenance scenario line, the scenario line is defined for a specific child item that matches with the item of the serialized item for which the plan is generated. The measurement type, maintenance trigger and counter readings are also defined. The counter reading must include trend information in order to calculate the planned activities. A maintenance trigger set is defined, and the applicable trend information is retrieved. For the defined counter value and start date, based on the trend data and maintenance trigger set, the first expected maintenance moment is determined. When this planned date is within the defined time fence, a planned activity is generated for the follow-up activity defined for the applicable maintenance trigger. This process is repeated, using the new planned date as the counter start date for the next iteration. When counter reset rules are defined for a default start value, the counter value used to calculate the next maintenance moment, is reset. This type can only be used for advanced inspection scenarios. Time-based scenario A time-based scenario is used to define the reference activity that must be planned and how many times within the time frame (example: inspection to be done 12 times per year). For a time-based maintenance scenario line, the process to generate a plan based on master routing is different from that of generating the plan for a reference activity. When generating the plan based on master routing, the default routing option is defined, in case multiple routing options exist. Otherwise, an error report is generated in Infor LN. The new start date is determined, based on the value the Start Maintenance Cycle field is set to, in the Generate Maintenance Plan (tsspc2200m000) session. If the start date is within the time fence, the routing operations are read from the master routing, in descending order, and planned in time. When the plan is generated for reference activities, the planned activity start date is determined using the same logic. Time-based with pattern scenario This scenario is used to define the pattern using the relative moments when a reference activity must be performed and a planned activity must be planned for it. When generating a maintenance plan based on a time-based pattern line, the process to generate a plan based on master routing is different from that of generating the plan for a reference activity. When generating the plan based on master routing, the default routing option is defined, in case multiple routing options exist. Else, Infor LN generates an error report. To determine the start date of the planned activity, the defined calendar moments in the activity pattern line are used. This process is repeated for each pattern line as long as the planned date is within the time fence. Preventive maintenance scenario line patterns Preventive maintenance can also be sometimes performed on an irregular basis. In such cases, a time-based pattern can be set up with relative moments defining when maintenance must be performed. Generate maintenance plan Use the Generate Maintenance Plan (tsspc2200m000) session to generate maintenance plans for serialized items for which a preventive maintenance scenario applies. The rule book for maintenance scenarios defines the applicable scenarios. Note A maintenance plan can be generated only if maintenance scenario is defined for the serialized item.