<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000534" xml:lang="en">
   <Header>
      <Title>Service inspections and preventive maintenance scenarios</Title>
      <Keyword type="header" order="d1e2784536">
         <Level1>Measurement</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>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.</Paragraph>
      <Paragraph>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.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>Measurement types are used for:</Paragraph>
      <List>
         <ListItem>Inspections on work orders for serialized items</ListItem>
         <ListItem>Inspections on service orders for serialized items</ListItem>
         <ListItem>Inspections on serialized items only</ListItem>
         <ListItem>Expected measurements on planned activities for preventive
		  maintenance</ListItem>
         <ListItem>Counter value on serialized items that can be used in service
		  contracts on the contract coverage lines</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Maintenance triggers sets</SectionTitle>
      <Paragraph>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.</Paragraph>
      <GeneralSection>
         <SectionTitle>Maintenance triggers</SectionTitle>
         <Paragraph>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), Infor10 ERP Enterprise 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.</Paragraph>
         <Paragraph>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:</Paragraph>
         <List>
            <ListItem>Maintenance trigger set specified on counter reading of
			 serialized item.</ListItem>
            <ListItem>Maintenance trigger assignment rule book.</ListItem>
            <ListItem>Maintenance trigger on reference activity measurement
			 type.</ListItem>
            <ListItem>Measurement type.</ListItem>
         </List>
      </GeneralSection>
      <Paragraph>The <Link href="/baanerp/ts/mdm/tsmdm0276m000" role="session">Simulate Maintenance Trigger Set Rules (tsmdm0276m000)</Link> session is used to determine which trigger set is used.</Paragraph>
      <GeneralSection>
         <SectionTitle>Inspections</SectionTitle>
         <Paragraph>Inspections can be created manually (directly for an item) or
		  generated using web services or reference activities when planning service
		  orders/work orders.</Paragraph>
         <Paragraph>Inspections (measurement types) can be defined in <GUIRef href="/baanerp/ts/acm/tsacm3160m000" role="session">Reference Activity - Measurement Types (tsacm3160m000)</GUIRef> 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 <GUIRef href="/baanerp/ts/cfg/tscfg3100m000" role="session">Inspections (tscfg3100m000)</GUIRef> session.</Paragraph>
         <Paragraph>Inspection can be generated from:</Paragraph>
         <List>
            <ListItem>Measurement, meaning, it is an inspection that must be
			 executed.</ListItem>
            <ListItem>Retrieved from the physical breakdown structure.</ListItem>
            <ListItem>Retrieve from another serialized item.</ListItem>
            <ListItem>Retrieve from other counter reading.</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>For advance inspections, besides setting up measurement
			 types and maintenance trigger sets, counter reading must also be
			 defined.</Paragraph>
         </Note>
         <Paragraph/>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Counter groups</SectionTitle>
         <Paragraph>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:</Paragraph>
         <List>
            <ListItem>Calculate trends for maintenance to be performed in
			 future</ListItem>
            <ListItem>Retrieve measurements from other items or other
			 measurements</ListItem>
            <ListItem>Define multiple trigger sets for one measurement</ListItem>
         </List>
         <Paragraph>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.</Paragraph>
         <Paragraph>Trend information can also be defined on the counter reading. <Link href="/baanerp/ts/glossary/glossary#000453" role="glossary">Trend</Link> calculation can be used to predict when maintenance is necessary. Trend
		  calculation is based on:</Paragraph>
         <List>
            <ListItem>A manually entered trend</ListItem>
            <ListItem>Retrieved from physical breakdown (only applicable if the
			 counter is retrieved from the physical breakdown structure).</ListItem>
            <ListItem>Retrieved from specific item (only applicable if the counter
			 is retrieved from another serialized item).</ListItem>
            <ListItem>Retrieved from another measurement type of type counter
			 (especially if the wear is based on the usage)</ListItem>
         </List>
         <Paragraph>When a serialized item is created, a default counter reading
		  is created for the serialized item. Infor10 ERP Enterprise 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.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Maintenance notifications</SectionTitle>
         <Paragraph>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 <Link href="/baanerp/ts/glossary/glossary#000444" role="glossary">position</Link> of the measurement, the applicable maintenance
		  trigger set is determined. Infor10 ERP Enterprise uses the following search
		  logic:</Paragraph>
         <ProcedureList>
            <ListItem>From the counter readings defined for serialized items</ListItem>
            <ListItem>From maintenance trigger set assignments</ListItem>
            <ListItem>From reference activity</ListItem>
            <ListItem>From the measurement type</ListItem>
         </ProcedureList>
         <GeneralSection>
            <SectionTitle>Maintenance notifications follow-up</SectionTitle>
            <Paragraph>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:</Paragraph>
            <List>
               <ListItem>Ignore for Now</ListItem>
               <ListItem>Always ignore</ListItem>
               <ListItem>Transfer to a planned activity, service order/work order
				and so on</ListItem>
            </List>
            <GeneralSection>
               <SectionTitle>Transfer maintenance notifications</SectionTitle>
               <Paragraph>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.</Paragraph>
            </GeneralSection>
            <GeneralSection>
               <SectionTitle>Preventive maintenance scenarios</SectionTitle>
               <Paragraph>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 Usage
				based ( Example after
				10000 km, execute maintenance or after profile of tire is below 3 mm).</Paragraph>
            </GeneralSection>
            <GeneralSection>
               <SectionTitle>Preventive maintenance scenario lines</SectionTitle>
               <Paragraph>Based on the preventive maintenance scenario lines, a
				maintenance plan is generated for the serialized item. You can define the
				following types of scenarios:</Paragraph>
               <List>
                  <ListItem>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.</ListItem>
                  <ListItem>Time based scenario: 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. Else, Infor10 ERP Enterprise generates an error report. The new start date is
				  determined, based on the value the <GUIRef href="/baanerp/ts/spc/tsspc2200m000#method" role="manual">Start Maintenance Cycle</GUIRef> field is set to, in the <Link href="/baanerp/ts/spc/tsspc2200m000" role="session">Generate Maintenance Plan (tsspc2200m000)</Link> 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.</ListItem>
                  <ListItem>Time based with pattern scenario: 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, Infor10 ERP Enterprise 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.</ListItem>
               </List>
               <GeneralSection>
                  <SectionTitle>Preventive maintenance scenario line patterns</SectionTitle>
                  <Paragraph>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.</Paragraph>
               </GeneralSection>
               <GeneralSection>
                  <SectionTitle>Generate maintenance plan</SectionTitle>
                  <Paragraph>Use the <Link href="/baanerp/ts/spc/tsspc2200m000" role="session">Generate Maintenance Plan (tsspc2200m000)</Link> 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.</Paragraph>
                  <Note>
                     <SectionTitle>Note</SectionTitle>
                     <Paragraph>A maintenance plan can be generated only if
					 maintenance scenario is defined for the serialized item.</Paragraph>
                  </Note>
               </GeneralSection>
            </GeneralSection>
         </GeneralSection>
      </GeneralSection>
   </GeneralSection>
</ManualTopic>