<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000132" xml:lang="en">
   <Header>
      <Title>Preventive Maintenance</Title>
      <Keyword type="header" order="d1e2417688">
         <Level1>Introduction</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>This module enables you to use preventive maintenance (Service
		Planning and Concepts SPC) for assets in an effective and efficient way. These
		assets can belong to your customers or can be your own internal assets. The
		planned activities can be covered by service contracts. These activities could
		be agreed with the customers and, therefore, must be automatically controlled
		by the service order system.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>You can define a unique maintenance concept for each product.
		The supported preventive maintenance policies are as follows:</Paragraph>
      <List>
         <ListItem>Usage-based maintenance (UBM), based on periods or based on
		  counter readings.</ListItem>
      </List>
      <Paragraph>A trigger for service can be based on the number of kilometers,
		mileage, or working hours. After a specified usage, the predefined service
		activities must be carried out. Measurements can be used to track the usage and
		to plan next activities. Agreements can be based on the usage of assets.</Paragraph>
      <List>
         <ListItem>Condition-based maintenance (CBM) based on visits and
		  measurements or reported measurements.</ListItem>
      </List>
      <Paragraph>Condition-based maintenance depends on the condition of the
		asset, including components, or configuration lines. You can register several
		measurements to describe the condition of the asset. You can carry out
		condition monitoring based on the reports generated from inspections or
		inspection history, which you can obtain from Service Order
		Control.</Paragraph>
      <Paragraph>To support the definition of maintenance concepts, a library
		with (reference) maintenance concept can be consulted. For items, (reference)
		maintenance concepts can be defined and stored in a library for ease of use.
		When the maintenance concept is set up and agreed upon, the corresponding
		Maintenance Predictions can be generated, and maintenance planning can
		subsequently be generated.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <FigIntro>The following figure provides an overview of the LN Service Planning and Concepts (SPC) module.</FigIntro>
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="397" width="587"
                   SRC="../images/tr_graph_spcoverview.jpg"
                   alt="[...]"/>
      </Figure>
      <Paragraph>At the upper-left corner of the figure, you see two key elements
		that serve as a basis for setting up maintenance concepts. Maintenance concepts
		are sets of activities that must be carried out in line with a particular
		maintenance policy, which includes reference activities and anonymous items or
		service items. Reference activities identify the type of work and the resources
		required for carrying out specific maintenance activities. You can link these
		reference activities to specific anonymous items or service items. Maintenance
		concepts are used to plan preventive maintenance activities.</Paragraph>
      <Paragraph>You can use the generic maintenance concept to generate a
		prediction of the activities that must be carried out. This prediction
		contains, on a relative time scale, the expected moments for these activities.
		You can generate these predictions by anonymous item, by usage class, and by
		combinations of anonymous item and class. This generation results in a more
		specific maintenance concept, which in turn can be used for the actual
		maintenance planning.</Paragraph>
      <Paragraph>Maintenance planning can be triggered from the Planning and
		Concepts (SPC) module. However, configurations that are linked to contracts
		must be initiated from the Contract Management (CTM) module.</Paragraph>
      <Paragraph>For each of the selected clusters, LN checks what
		serialized items are linked to the clusters. If serialized items are found, the
		related anonymous items or service items can be identified, through which the
		maintenance concepts that must be used can also be found. The generated
		planning provides the activities that must be carried out. When the planned
		activities are released, these activities can be transferred into actual
		service orders.</Paragraph>
   </GeneralSection>
</ManualTopic>