<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/ts/glossary/glossary" xml:lang="en">
   <Header>
      <Title>Glossary for Service</Title>
   </Header>
   <GlossaryEntry ID="000022" Version="B60adoc1" ContextApps="ts">
      <Term>acknowledgment sheet</Term>
      <Definition>A letter about a service order that is planned to be carried
		out, used to inform the business partner. For this purpose, a user-dependent
		layout (template) can be defined in the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2771243">
         <Level1>acknowledgment sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ActiviGroup_ts" Version="B60adoc1" ContextApps="ts">
      <Term>activity group</Term>
      <Definition>A user-defined category created to group reference activities
		or planned activities, based on their common features.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>A group of assembly activities.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2772984">
         <Level1>activity group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000466">
      <Term>activity set</Term>
      <Definition>Group of service order activities, work order activities, or
		planned activities.</Definition>
      <Keyword type="glentry" order="d1e2773930">
         <Level1>activity set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000059" Version="B60adoc1" ContextApps="ts">
      <Term>actual problem</Term>
      <Definition>The real problem as determined by the service/support engineer.</Definition>
      <Keyword type="glentry" order="d1e2771442">
         <Level1>actual problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000060" Version="B60adoc1" ContextApps="ts">
      <Term>actual solution</Term>
      <Definition>The definitive solution as determined by the service/support
		engineer, which solved the actual problem.</Definition>
      <Keyword type="glentry" order="d1e2771447">
         <Level1>actual solution</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000129" Version="B60adoc0" ContextApps="ts">
      <Term>allocated calls</Term>
      <Definition>The number of calls for service activities that were performed
		but that have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771965">
         <Level1>allocated calls</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000132" Version="B60adoc0" ContextApps="ts">
      <Term>allocated call units</Term>
      <Definition>The number of call units for service activities that have been
		performed but which have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771987">
         <Level1>allocated call units</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000085" Version="B60adoc0" ContextApps="ts">
      <Term>allocated costs</Term>
      <Definition>The sum of costs due to service activities that have not been
		financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home currency.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Service orders</ListItem>
            <ListItem>Traveling costs</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771671">
         <Level1>allocated costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000087" Version="B60adoc0" ContextApps="ts">
      <Term>allocated discount</Term>
      <Definition>The sum of discounts derived from service activities that have
		not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home
		currency.</Definition>
      <Keyword type="glentry" order="d1e2771703">
         <Level1>allocated discount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000124" Version="B60adoc0" ContextApps="ts">
      <Term>allocated distance</Term>
      <Definition>The total distance for service activities that were performed
		but which have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771934">
         <Level1>allocated distance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000106" Version="B60adoc1" ContextApps="ts">
      <Term>allocated hours</Term>
      <Definition>The number of hours that were spent on service activities but
		that have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771842">
         <Level1>allocated hours</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000108" Version="B60adoc0" ContextApps="ts">
      <Term>allocated quantity</Term>
      <Definition>The quantity of material used for service activities which has
		not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771855">
         <Level1>allocated quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000086" Version="B60asy04" ContextApps="ts">
      <Term>allocated sales</Term>
      <Definition>The sum of the sales amounts due to service activities that
		have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>,
		expressed in the home currency.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Service orders</ListItem>
            <ListItem>Traveling costs</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771687">
         <Level1>allocated sales</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000111" Version="B60asy04" ContextApps="ts">
      <Term>allocated visits</Term>
      <Definition>The number of visits that were performed for service activities
		but which have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771863">
         <Level1>allocated visits</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000029" Version="B60adoc1" ContextApps="ts">
      <Term>answer</Term>
      <Definition>The reply a customer gives to a question asked by the support
		person who attempts to diagnose the call. You can list the answers to diagnose
		subsequent incoming calls. You can enter a diagnostic tree to structure
		questions and the corresponding answers in order to find the expected problem
		and expected solution(s).</Definition>
      <Keyword type="glentry" order="d1e2771282">
         <Level1>answer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000037" Version="B60asy04" ContextApps="ts">
      <Term>appointment sheet</Term>
      <Definition>Appointment sheets can be printed if in the order header it is
		stated that an appointment has been made. This letter can be sent to the
		business partner. For this document a template can be defined in the SOC
		parameters.</Definition>
      <Keyword type="glentry" order="d1e2771326">
         <Level1>appointment sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000311" Version="B60asy04" ContextApps="ts">
      <Term>as-built structure</Term>
      <Definition>The actually built structure of a product including the serial
		numbers.</Definition>
      <Keyword type="glentry" order="d1e2772171">
         <Level1>as-built structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000316" Version="B60asy04" ContextApps="ts">
      <Term>assembly</Term>
      <Definition>Components that are built together and form a unit on which
		maintenance can be done.</Definition>
      <Keyword type="glentry" order="d1e2772197">
         <Level1>assembly</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000437">
      <Term>assignment</Term>
      <Definition>A short message, entered by a field engineer, which informs the
		planner or dispatcher as to whether the field engineer can be
		paged.</Definition>
      <Keyword type="glentry" order="d1e2772974">
         <Level1>assignment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ATP_ts">
      <Term>ATP</Term>
      <Definition>The item quantity that is available to be promised for a
		customer either immediately, or at a specific time in the future.</Definition>
      <Keyword type="glentry" order="d1e2773751">
         <Level1>ATP</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ATPcheck_ts">
      <Term>ATP check</Term>
      <Definition>A check on the quantity that can be promised to a customer
		based on the allowed demand. The main purpose of the ATP check is to reserve a
		certain quantity of the spare part or item.</Definition>
      <Keyword type="glentry" order="d1e2773756">
         <Level1>ATP check</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000467">
      <Term>attribute</Term>
      <Definition>A field of service order, work order, or planned activity in
		the context of group planning. Example Installation Group.</Definition>
      <Keyword type="glentry" order="d1e2773935">
         <Level1>attribute</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000468">
      <Term>attribute value</Term>
      <Definition>The field value of an order. Example ‘Floor
		K1’</Definition>
      <Keyword type="glentry" order="d1e2773940">
         <Level1>attribute value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000374" Version="B60adoc1" ContextApps="ts">
      <Term>Automation Server</Term>
      <Definition>Automation Server provides the bridge between the ERP Enterprise application and any
		Windows application running on the Microsoft Windows platform. This enables you
		to use the functionality of, for example, Microsoft applications such as Word,
		Excel, and Outlook, with ERP Enterprise applications.</Definition>
      <Keyword type="glentry" order="d1e2772520">
         <Level1>Automation Server</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000302" Version="B60asy04" ContextApps="ts">
      <Term>average usage factor</Term>
      <Definition>A factor that expresses the average use of a configuration.</Definition>
      <Keyword type="glentry" order="d1e2772125">
         <Level1>average usage factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="BadFix_ts" Version="B60adoc1" ContextApps="ts">
      <Term>bad fix</Term>
      <Definition>A call from the same customer about a previously solved problem
		regarding the same item.</Definition>
      <Keyword type="glentry" order="d1e2772994">
         <Level1>bad fix</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000400" Version="B60adoc1" ContextApps="ts">
      <Term>blanket agreement</Term>
      <Definition>A high level agreement that describes the terms and conditions
		applicable for the item for which service is provided by a third-party
		organization.</Definition>
      <SimpleSection>
         <Paragraph>After the blanket agreement is defined, the details will be
		  provided to the organization for which items must be subcontracted. The blanket
		  agreement can become the basis for a subcontract agreement.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772722">
         <Level1>blanket agreement</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="BlankServicJ_ts" Version="B60adoc1" ContextApps="ts">
      <Term>blank service order sheets</Term>
      <Definition>A document that a service engineer uses to register the service
		order, the service order activities and the requirements when a service order
		is not yet created. A blank service order sheet can be booked in ERP Enterprise later as a formal
		service order.</Definition>
      <SimpleSection>
         <Paragraph>This can be used, for example, when during a night shift of
		  24 hour service, the service engineer is directly informed by a customer about
		  a malfunction. He will then solve the call at once, while an office worker will
		  enter the related service order (activity) in ERP Enterprise the next (working)
		  day.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772999">
         <Level1>blank service order sheets</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000078" Version="B60adoc1" ContextApps="ts">
      <Term>blocking reason</Term>
      <Definition>The reason why a call or an order cannot be processed
		(temporarily).</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Calls or orders can be blocked for one or more of the
			 following reasons:</ListIntro>
            <ListItem>The credit limit of the invoice-to business partner has been
			 exceeded.</ListItem>
            <ListItem>The credit review period has been exceeded.</ListItem>
            <ListItem>The invoice-to business partner has overdue invoices.</ListItem>
            <ListItem>The status of invoice-to business partner is doubtful.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771598">
         <Level1>blocking reason</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000342" Version="B60adoc1" ContextApps="ts">
      <Term>BP identification</Term>
      <Definition>A serial number, specified and used by the item's owner as an
		alternative to the item's manufactured serial number.</Definition>
      <Keyword type="glentry" order="d1e2772335">
         <Level1>BP identification</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000433" Version="B60adoc1" ContextApps="ts">
      <Term>BSS</Term>
      <Definition>
         <Emphasis>Infor Service Scheduler</Emphasis>, a graphical planning
		tool used by dispatchers to assign service orders and/or activities to service
		engineers.</Definition>
      <Keyword type="glentry" order="d1e2772949">
         <Level1>BSS</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000071" Version="B60asy04" ContextApps="ts">
      <Term>budgeted costs</Term>
      <Definition>The estimated cost that will be incurred while servicing items.
		The amount is expressed in the home currency.</Definition>
      <Keyword type="glentry" order="d1e2771534">
         <Level1>budgeted costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000090" Version="B60asy04" ContextApps="ts">
      <Term>budgeted discount</Term>
      <Definition>The sum of the discounts that are associated with the indicated
		service type or cost type.</Definition>
      <SimpleSection>
         <Paragraph>The amount is expressed in the currency chosen in the
		  contract header.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771743">
         <Level1>budgeted discount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000072" Version="B60asy04" ContextApps="ts">
      <Term>budgeted sales</Term>
      <Definition>The expected sales amount from providing services under this
		contract.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The amount is:</ListIntro>
            <ListItem>Expressed in the currency that is chosen in the contract
			 header.</ListItem>
            <ListItem>Determined by information provided by the <GUIRef href="/baanerp/ts/spc" role="module">Service Planning &amp; Concepts</GUIRef> module.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771539">
         <Level1>budgeted sales</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000020" Version="B60asy04" ContextApps="ts">
      <Term>business partner priority factor</Term>
      <Definition>The business partner priority divided by 100.</Definition>
      <Keyword type="glentry" order="d1e2771135">
         <Level1>business partner priority factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Call_ts" Version="B60adoc1" ContextApps="ts">
      <Term>call</Term>
      <Definition>A question, complaint, or malfunction that is communicated to
		the party responsible for the service or maintenance of the item concerned.</Definition>
      <Keyword type="glentry" order="d1e2773007">
         <Level1>call</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CallGroup_ts" Version="B60adoc1" ContextApps="ts">
      <Term>call group</Term>
      <Definition>A category used to group calls for selection purposes.</Definition>
      <Keyword type="glentry" order="d1e2773013">
         <Level1>call group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000079" Version="B60adoc1" ContextApps="ts">
      <Term>call-out charge</Term>
      <Definition>The fee that the sold-to business partner (customer) must pay
		when a service engineer visits the Installation
		group's location to carry out service or maintenance.</Definition>
      <Keyword type="glentry" order="d1e2771615">
         <Level1>call-out charge</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000112" Version="B60asy04" ContextApps="ts">
      <Term>call-out charge</Term>
      <Definition>The combination of the mileage costs and the engineer's costs.
		If a callout charge is defined, it is used in place of these separate costs,
		and the travel sales amount is made equal to it.</Definition>
      <Keyword type="glentry" order="d1e2771871">
         <Level1>call-out charge</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000391" Version="B60adoc1" ContextApps="ts">
      <Term>call priority</Term>
      <Definition>Depending on the assessment of the malfunction consequence, a
		support employee assigns a particular priority to the call.</Definition>
      <Keyword type="glentry" order="d1e2772648">
         <Level1>call priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000092" Version="B60adoc1" ContextApps="ts">
      <Term>ceiling amount</Term>
      <Definition>The agreed limit up to which the costs are covered by the
		contract, quotation, order, or warranty.</Definition>
      <Keyword type="glentry" order="d1e2771760">
         <Level1>ceiling amount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ChangeMethod_ts" Version="B60asy04" ContextApps="ts">
      <Term>change method</Term>
      <Definition>The manner in which the item structure is changed: replace,
		remove, or install an item.</Definition>
      <Keyword type="glentry" order="d1e2773018">
         <Level1>change method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000317" Version="B60asy04" ContextApps="ts">
      <Term>change order</Term>
      <Definition>Orders that are used to record, approve, and carry through all
		kinds of changes.</Definition>
      <SimpleSection>
         <Paragraph>For example, a change order can be related to engineering
		  matters or to business processes.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772202">
         <Level1>change order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Checklist_ts" Version="B60adoc1" ContextApps="ts">
      <Term>checklist</Term>
      <Definition>Lists the points to which the service engineer must pay
		attention during the execution of a service activity. Checklists are used to
		group specific checks so that more than one check can be defined for a
		reference activity. According to the answers expected from the check, space is
		provided when printing the document related to the service order.</Definition>
      <Keyword type="glentry" order="d1e2773023">
         <Level1>checklist</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ChecksByChec_ts" Version="B60adoc1" ContextApps="ts">
      <Term>checks by checklist</Term>
      <Definition>A number of specific checks which you define for a checklist.
		You can link the checklist to a reference activity, so when a service engineer
		executes the service activity they must carry out and fill in the checks listed
		on the checklist.</Definition>
      <Keyword type="glentry" order="d1e2773028">
         <Level1>checks by checklist</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000095" Version="B60asy04" ContextApps="ts">
      <Term>child object</Term>
      <Definition>A child object is part of a parent object, and is linked to
		this parent object through an object relation.</Definition>
      <Keyword type="glentry" order="d1e2771770">
         <Level1>child object</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ConditBasedM_ts" Version="B60asy04" ContextApps="ts">
      <Term>condition-based maintenance</Term>
      <Definition>Preventive maintenance that takes place if a required
		measurement does not meet the specified norm value. Acronym: CBM</Definition>
      <Keyword type="glentry" order="d1e2773033">
         <Level1>condition-based maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000461">
      <Term>condition based measurement type</Term>
      <Definition>A condition based measurement type measures a state/condition
		of an item. Example profile of a tire, acid level in fluid. The condition based measurement type
		can be either numeric or alphanumeric.</Definition>
      <Keyword type="glentry" order="d1e2773905">
         <Level1>condition based measurement type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000304" Version="B60asy04" ContextApps="ts">
      <Term>configuration</Term>
      <Definition>The identification of a set of serialized items on which
		service and maintenance activities can be carried out.</Definition>
      <Keyword type="glentry" order="d1e2772135">
         <Level1>configuration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Configuratio_ts" Version="B60adoc1" ContextApps="ts">
      <Term>configuration</Term>
      <Definition>An
Installation
		group of items that share the same location or
		customer.</Definition>
      <SimpleSection>
         <Paragraph>For example, a configuration could consist of all items that
		  are controlled for a specific customer, or all items that are in the same
		  location.</Paragraph>
         <Paragraph>Grouping items into a configuration enables you to maintain
		  them collectively.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773059">
         <Level1>configuration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000309" Version="B60asy04" ContextApps="ts">
      <Term>configuration activity trigger</Term>
      <Definition>The initiator that indicates the moment on which the reference
		activity for the Installation
		must be carried out.</Definition>
      <Keyword type="glentry" order="d1e2772160">
         <Level1>configuration activity trigger</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ConfigStruct_ts" Version="B60asy04" ContextApps="ts">
      <Term>configuration structure</Term>
      <Definition>The relationships among items in an
		Installation
		group.</Definition>
      <Keyword type="glentry" order="d1e2773038">
         <Level1>configuration structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000305" Version="B60asy04" ContextApps="ts">
      <Term>configuration type</Term>
      <Definition>The type of the configuration.</Definition>
      <Keyword type="glentry" order="d1e2772140">
         <Level1>configuration type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ConfigVersio_ts" Version="B60asy04" ContextApps="ts">
      <Term>configuration version</Term>
      <Definition>The current status of the configuration's structure. This can
		be useful for history purposes. Structure changes within a certain
		configuration, to which an active contract applies, take place under a new
		configuration version.</Definition>
      <SimpleSection>
         <Paragraph>No new configuration version is generated for changes on the
		  component level (item).</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773051">
         <Level1>configuration version</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000318" Version="B60asy04" ContextApps="ts">
      <Term>constraint</Term>
      <Definition>A predefined condition for a configuration to perform a certain
		activity. For example: If a battery check must be carried out, the constraint
		is that the external power must be switched off.</Definition>
      <Keyword type="glentry" order="d1e2772210">
         <Level1>constraint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000319" Version="B60asy04" ContextApps="ts">
      <Term>consumable item</Term>
      <Definition>Materials that are used during service or maintenance of an
		item. These materials do not appear in a physical breakdown or item breakdown.
		For example: Lubricants.</Definition>
      <Keyword type="glentry" order="d1e2772215">
         <Level1>consumable item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ContraCovera_ts" Version="B60asy04" ContextApps="ts">
      <Term>contract coverage</Term>
      <Definition>The method indicating how the service order costs are covered
		by the contract.</Definition>
      <Keyword type="glentry" order="d1e2773069">
         <Level1>contract coverage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000397" Version="B60adoc1" ContextApps="ts">
      <Term>contract discount scheme</Term>
      <Definition>If services or terms of a warranty overlap with the services of
		a contract agreement for an item, a discount or reduction in terms on the
		contract price can be offered. The discount scheme defines the contract's
		discount percentage during the period when the warranty is valid for the item.
		This enables you to include an initial warranty period during which no invoices
		are sent to the customer. You can also use a discount scheme independently from
		a warranty, for example, if you agree on a once-only discount with the
		customer.</Definition>
      <Keyword type="glentry" order="d1e2772706">
         <Level1>contract discount scheme</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000004" Version="B60adoc1" ContextApps="ts">
      <Term>contract duration</Term>
      <Definition>The period of time over which the contract runs. The contract
		duration is defined by a numeric value in combination with a period unit, for
		example 2 Month.</Definition>
      <Keyword type="glentry" order="d1e2771150">
         <Level1>contract duration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000054" Version="B60asy04" ContextApps="ts">
      <Term>contract history</Term>
      <Definition>The information stored for a particular contract.</Definition>
      <Keyword type="glentry" order="d1e2771413">
         <Level1>contract history</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000381" Version="B60adoc0" ContextApps="ts">
      <Term>contract installment</Term>
      <Definition>Period over which the contract revenues (installment amounts)
		and the forecast contract costs are distributed. Contract installments are
		defined by year and contract.</Definition>
      <Keyword type="glentry" order="d1e2772577">
         <Level1>contract installment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ContraQuotat_ts" Version="B60adoc1" ContextApps="ts">
      <Term>contract quotation</Term>
      <Definition>A quotation to a business partner for the provision of a
		service contract.</Definition>
      <Keyword type="glentry" order="d1e2773074">
         <Level1>contract quotation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000140" Version="B60asy04" ContextApps="ts">
      <Term>contract-quotation documents</Term>
      <Definition>The documents that are printed in the <GUIRef href="/baanerp/ts/ctm/tsctm2400m000" role="session">Print Contract Quotation Documents (tsctm2400m000)</GUIRef> session.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Two types can be printed:</ListIntro>
            <ListItem>External documents</ListItem>
            <ListItem>Internal documents</ListItem>
         </List>
      </SimpleSection>
      <SimpleSection>
         <SectionTitle>External document</SectionTitle>
         <Paragraph>This type of document is used to print the actual documents
		  that must be sent to the business partner. The status of the quotation is
		  changed to Printed, at which point the details become fixed and changes to the
		  quotation terms are prevented.</Paragraph>
      </SimpleSection>
      <SimpleSection>
         <SectionTitle>Internal document</SectionTitle>
         <Paragraph>This type of document is used to print a copy for internal
		  use of the actual document that must be sent to the business partner. The
		  status of the quotation is unchanged.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>The quotation can receive separate financial approval before
			 printing the final documents.</ListItem>
            <ListItem>The quotation details can still be amended after review.</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2772046">
         <Level1>contract-quotation documents</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000138" Version="B60asy04" ContextApps="ts">
      <Term>contract quotation header</Term>
      <Definition>The contract quotation header contains all the data that is
		entered in <GUIRef href="/baanerp/ts/ctm/tsctm2100m000" role="session">Contract Quotations (tsctm2100m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2772030">
         <Level1>contract quotation header</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000378" Version="B60adoc1" ContextApps="ts">
      <Term>contract renewal</Term>
      <Definition>Changes to service contracts that are the result of a new
		duration period.</Definition>
      <Keyword type="glentry" order="d1e2772541">
         <Level1>contract renewal</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000099" Version="B60asy04" ContextApps="ts">
      <Term>contract sequence number</Term>
      <Definition>The number used to identify the cost term of the coverage term.
		The default step size is 10.</Definition>
      <Keyword type="glentry" order="d1e2771808">
         <Level1>contract sequence number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ContraTempla_ts" Version="B60asy04" ContextApps="ts">
      <Term>contract template</Term>
      <Definition>A standard set of contract terms and conditions. A template can
		be used as a basis for contract quotations and service contracts.</Definition>
      <Keyword type="glentry" order="d1e2773080">
         <Level1>contract template</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000137" Version="B60asy04" ContextApps="ts">
      <Term>contract template header</Term>
      <Definition>The contract template header contains all the data that is
		entered in the <GUIRef href="/baanerp/ts/ctm/tsctm0150m000" role="session">Contract Templates (tsctm0150m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2772022">
         <Level1>contract template header</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ContraTypes_ts" Version="B60adoc1" ContextApps="ts">
      <Term>contract type</Term>
      <Definition>A way of categorizing contracts based on similarities and
		shared characteristics.</Definition>
      <SimpleSection>
         <Paragraph>Each contract type is identified by an alphanumeric code of
		  up to three characters.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773085">
         <Level1>contract type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CorrecMainte_ts" Version="B60asy04" ContextApps="ts">
      <Term>corrective maintenance</Term>
      <Definition>The maintenance that is carried out to restore an item to a
		serviceable condition by fixing a known or suspected malfunction and/or defect.</Definition>
      <Keyword type="glentry" order="d1e2773093">
         <Level1>corrective maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000083" Version="B60adoc1" ContextApps="ts">
      <Term>cost-covering method</Term>
      <Definition>A method that determines how the costs of the service order are
		covered by the service contract.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following cost-covering methods are available:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#fixed" role="option">Fixed Price</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#ceilpric" role="option">Ceiling</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#disc" role="option">Coverage Percentage</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#ceildisc" role="option">Ceiling on Coverage Percentage</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#exclusion" role="option">Exclusion</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.ccov#own.risk" role="option">Own Risk</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771625">
         <Level1>cost-covering method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000434" Version="B60adoc1" ContextApps="ts">
      <Term>cost currency</Term>
      <Definition>The monetary unit in which the cost price is expressed.</Definition>
      <Keyword type="glentry" order="d1e2772956">
         <Level1>cost currency</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CostLines_ts" Version="B60asy04" ContextApps="ts">
      <Term>cost lines</Term>
      <Definition>An estimated or actual cost line that represents the costs for
		materials, labor, or other that is required to carry out an activity.</Definition>
      <Keyword type="glentry" order="d1e2773098">
         <Level1>cost lines</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000114" Version="B60asy04" ContextApps="ts">
      <Term>cost price</Term>
      <Definition>The cost price of the term expressed in the home
		currency.</Definition>
      <Keyword type="glentry" order="d1e2771876">
         <Level1>cost price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000056" Version="B60asy04" ContextApps="ts">
      <Term>cost terms</Term>
      <Definition>A detailed specification of a coverage term.</Definition>
      <Keyword type="glentry" order="d1e2771437">
         <Level1>cost terms</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000403" Version="B60adoc1" ContextApps="ts">
      <Term>cost type</Term>
      <Definition>Categories that are used to register the type of costs. Cost
		types enable you to have a more detailed view of the source of costs.</Definition>
      <Keyword type="glentry" order="d1e2772740">
         <Level1>cost type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000303" Version="B60asy04" ContextApps="ts">
      <Term>counter interval</Term>
      <Definition>The time span between two maintenance moments. This interval is
		expressed in a usage-related unit, for example, operating hours, kilometers.
		The actual moment of maintenance is when the counter norm-value is reached.
		Actual moments can be predicted.</Definition>
      <Keyword type="glentry" order="d1e2772130">
         <Level1>counter interval</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000442">
      <Term>counter measurement type</Term>
      <Definition>Measurement based on a counter that can be decreasing or
		increasing.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Mileage and Machine hours</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773779">
         <Level1>counter measurement type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000450">
      <Term>counter on meter</Term>
      <Definition>The last known value on the meter. This is applicable for
		counter based measurement types. This must be a separate counter, because a
		meter can be replaced and there can be a difference between meter value on the
		meter and the counter value.</Definition>
      <Keyword type="glentry" order="d1e2773849">
         <Level1>counter on meter</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000320" Version="B60asy04" ContextApps="ts">
      <Term>counter reading</Term>
      <Definition>The reading on a configuration's or serialized item's counter.</Definition>
      <Keyword type="glentry" order="d1e2772220">
         <Level1>counter reading</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000451">
      <Term>counter reading group</Term>
      <Definition>A group of counter readings. The counter reading group is used
		to default the counter reading information for a serialized item. This group
		can be linked to a service item or service item default and when a serialized
		item is created, the counter readings are copied from the counter reading
		group.</Definition>
      <Keyword type="glentry" order="d1e2773854">
         <Level1>counter reading group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000452">
      <Term>counter readings</Term>
      <Definition>A combination of a measurement type and position that is linked
		to a serialized item and holds information such as counter value.</Definition>
      <Keyword type="glentry" order="d1e2773859">
         <Level1>counter readings</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000464">
      <Term>counter start date</Term>
      <Definition>Date when the counter value is started with counting or when
		the item is in use.</Definition>
      <Keyword type="glentry" order="d1e2773920">
         <Level1>counter start date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000301" Version="B60asy04" ContextApps="ts">
      <Term>counter type</Term>
      <Definition>A general characterization of a measurement on a configuration.
		For example, the production hours of a machine or the flight cycles of an
		airplane. Counter types that are linked to an average usage factor unit enable
		you to plan maintenance activities for a configuration.</Definition>
      <Keyword type="glentry" order="d1e2772120">
         <Level1>counter type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CounteValue_ts" Version="B60adoc1" ContextApps="ts">
      <Term>counter value</Term>
      <Definition>Preventive maintenance takes place at a constant interval. This
		interval is expressed in a usage-related unit, for example, operating hours,
		kilometers. The actual moment of maintenance is when the norm value of the
		counter is reached. These actual moments can be predicted.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>A car that must be serviced every 20,000 km.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773103">
         <Level1>counter value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000449">
      <Term>counter value</Term>
      <Definition>The summarized value of all measurements performed for a
		numeric measurement or the last known measurement of an alphanumeric
		measurement.</Definition>
      <Keyword type="glentry" order="d1e2773844">
         <Level1>counter value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000328" Version="B60asy04" ContextApps="ts">
      <Term>coverage</Term>
      <Definition>A classification of the activities and costs related to a call,
		according to the terms that have been defined in the contract.</Definition>
      <Keyword type="glentry" order="d1e2772264">
         <Level1>coverage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000411" Version="B60adoc1" ContextApps="ts">
      <Term>coverage lines</Term>
      <Definition>Lines that store the information on the costs incurred, amounts
		to be invoiced, and the amounts covered by the applicable contract and/or
		warranty. Most coverage lines are added through the maintenance sales order
		process, but can also be manually entered.</Definition>
      <Keyword type="glentry" order="d1e2772781">
         <Level1>coverage lines</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CoveraPhases_ts" Version="B60adoc1" ContextApps="ts">
      <Term>coverage phases</Term>
      <Definition>A coverage term can be phased in time or it can be made
		dependent on the counter value of an item. It is possible to specify for each
		phase another covering method.</Definition>
      <Keyword type="glentry" order="d1e2773113">
         <Level1>coverage phases</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000084" Version="B60adoc1" ContextApps="ts">
      <Term>coverage-term number</Term>
      <Definition>For a service type / term type combination, this is a unique
		sequence number.</Definition>
      <SimpleSection>
         <Paragraph> Default value of step size: 10</Paragraph>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>The default value can be changed if required.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2771658">
         <Level1>coverage-term number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CoveraTerms_ts" Version="B60adoc1" ContextApps="ts">
      <Term>coverage terms</Term>
      <Definition>A coverage term stores agreements on the duration, the cost
		covering method and the costs of these agreements. This can be created for (a
		combination of) a service contract (quotation), Installation
		group, coverage type, term type, or sequence number.</Definition>
      <SimpleSection>
         <Paragraph>The cost amounts and sales amounts of the term are also
		  stored.</Paragraph>
         <Paragraph>The defined coverage terms are valid for the entire duration
		  of the service contract. It is also possible to phase these terms, depending on
		  time or on the value of the main counter of a counter model.</Paragraph>
         <Paragraph>The coverage terms can be further specified in the so-called
		  cost terms.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773118">
         <Level1>coverage terms</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000390" Version="B60adoc1" ContextApps="ts">
      <Term>coverage type</Term>
      <Definition>A financial classification that indicates to what extent work
		is covered under warranty or contract, and what part of the activities can be
		charged.</Definition>
      <Keyword type="glentry" order="d1e2772643">
         <Level1>coverage type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000127" Version="B60adoc1" ContextApps="ts">
      <Term>covered calls</Term>
      <Definition>The number of calls that are covered by the contract or
		warranty.</Definition>
      <Keyword type="glentry" order="d1e2771952">
         <Level1>covered calls</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000130" Version="B60asy04" ContextApps="ts">
      <Term>covered call units</Term>
      <Definition>The number of call units that are covered by the contract or
		warranty.</Definition>
      <Keyword type="glentry" order="d1e2771974">
         <Level1>covered call units</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000115" Version="B60asy04" ContextApps="ts">
      <Term>covered hours</Term>
      <Definition>The current total of the hours spent on service activities.</Definition>
      <Keyword type="glentry" order="d1e2771881">
         <Level1>covered hours</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000116" Version="B60asy04" ContextApps="ts">
      <Term>covered quantity</Term>
      <Definition>The quantity of an item covered by the contract.</Definition>
      <Keyword type="glentry" order="d1e2771886">
         <Level1>covered quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000104" Version="B60adoc1" ContextApps="ts">
      <Term>covered time</Term>
      <Definition>The time that the contract covers.</Definition>
      <Keyword type="glentry" order="d1e2771829">
         <Level1>covered time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000117" Version="B60asy04" ContextApps="ts">
      <Term>covered visits</Term>
      <Definition>The number of visits covered by the contract or warranty.</Definition>
      <Keyword type="glentry" order="d1e2771891">
         <Level1>covered visits</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000050" Version="B60asy04" ContextApps="ts">
      <Term>credit review period</Term>
      <Definition>Within this period the invoice-to business partner must pay his
		invoices. This can be seen as a so-called overdue invoice period.</Definition>
      <Keyword type="glentry" order="d1e2771393">
         <Level1>credit review period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000332" Version="B60asy04" ContextApps="ts">
      <Term>critical resource</Term>
      <Definition>The resource on which the continuity and progress of (planned)
		maintenance activities depends.</Definition>
      <Keyword type="glentry" order="d1e2772284">
         <Level1>critical resource</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000395" Version="B60adoc1" ContextApps="ts">
      <Term>CTI</Term>
      <Definition>Acronym of <Emphasis>Computer Telephony Integration</Emphasis>.
		Combining data with voice systems in order to enhance telephone services. For
		example, automatic number identification (ANI) allows a caller's records to be
		retrieved from the database while the call is routed to the appropriate party.
		Automatic telephone dialing from an address list is an outbound example.</Definition>
      <Keyword type="glentry" order="d1e2772690">
         <Level1>CTI</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000002" Version="B60asy04" ContextApps="ts">
      <Term>customer priority</Term>
      <Definition>An alphanumeric code that identifies the priority of a
		customer.</Definition>
      <Keyword type="glentry" order="d1e2771120">
         <Level1>customer priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000333" Version="B60asy04" ContextApps="ts">
      <Term>cycle item</Term>
      <Definition>A components that circulates between configurations,
		maintenance shops, and warehouses, depending on the demand and the component
		being serviceable or not.</Definition>
      <Keyword type="glentry" order="d1e2772289">
         <Level1>cycle item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000023" Version="B60asy04" ContextApps="ts">
      <Term>default item data</Term>
      <Definition>Item data that is the same for a range of items.</Definition>
      <Keyword type="glentry" order="d1e2771252">
         <Level1>default item data</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000415" Version="B60adoc1" ContextApps="ts">
      <Term>deferred call</Term>
      <Definition>Either of the following: A non-blocked call with status <GUIRef href="" role="manual">Registered</GUIRef> for which the current time is past the registration
		time plus time fence specified in the <GUIRef href="/baanerp/ts/clm/tsclm0100m000" role="session">Call Parameters (tsclm0100m000)</GUIRef> session; A non-blocked call with status <GUIRef href="" role="manual">Assigned</GUIRef> for which the current time is past the assigned time
		plus time fence specified in the <GUIRef href="/baanerp/ts/clm/tsclm0100m000" role="session">Call Parameters (tsclm0100m000)</GUIRef> session.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Deferred calls use a 24 hours calendar.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2772804">
         <Level1>deferred call</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000435" Version="B60adoc1" ContextApps="ts">
      <Term>deferred emergency service order</Term>
      <Definition>A released emergency service order that has not been attended
		by a service engineer within the order escalation time as defined in the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2772961">
         <Level1>deferred emergency service order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="DeliveType_ts" Version="B60adoc1" ContextApps="ts">
      <Term>delivery type</Term>
      <Definition>Indicates how the material that is required to carry out the
		activities, must be delivered, or what will happen to the defective item.</Definition>
      <Keyword type="glentry" order="d1e2773130">
         <Level1>delivery type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000036" Version="B60adoc1" ContextApps="ts">
      <Term>dependent norm value</Term>
      <Definition>The dependent norm value determines the moment when maintenance
		is required for an item in a configuration.</Definition>
      <SimpleSection>
         <List>
            <ListItem>In case of predicted inspections (PI): If the measured value
			 does not meet the norm value, a maintenance activity is required. You can
			 immediately plan a service order that carries out the required maintenance, or
			 a follow-up activity.</ListItem>
            <ListItem>In case of counter value (CV) and predicted activities (PA):
			 The maintenance must be carried out when the norm value is reached.</ListItem>
         </List>
         <Paragraph> Example (CV): If a car must be inspected every
		  20,000 km. the first norm value is 20,000 km, the second 40,000 km, and so on.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771313">
         <Level1>dependent norm value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000032" Version="B60adoc1" ContextApps="ts">
      <Term>dependent variable</Term>
      <Definition>A unit of measurement, which together with a norm value (and
		start value) determines when maintenance activities must be carried out.</Definition>
      <Keyword type="glentry" order="d1e2771292">
         <Level1>dependent variable</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="DepotRepair_ts" Version="B60asy04" ContextApps="ts">
      <Term>depot repair</Term>
      <Definition>Repair that is carried out in a repair shop.</Definition>
      <Keyword type="glentry" order="d1e2773135">
         <Level1>depot repair</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000118" Version="B60asy04" ContextApps="ts">
      <Term>derived-from SPC</Term>
      <Definition>If this check box is selected, the term is derived from
		a maintenance concept or a maintenance plan in the <GUIRef href="/baanerp/ts/spc" role="module">Service Planning &amp; Concepts</GUIRef> module.</Definition>
      <Keyword type="glentry" order="d1e2771897">
         <Level1>derived-from SPC</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000334" Version="B60asy04" ContextApps="ts">
      <Term>detailed maintenance planning</Term>
      <Definition>Planning of the lowest level activities included in the
		activity aggregation relationships.</Definition>
      <Keyword type="glentry" order="d1e2772295">
         <Level1>detailed maintenance planning</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="DiagnoTree_ts" Version="B60adoc1" ContextApps="ts">
      <Term>diagnostic tree</Term>
      <Definition>An information structure that matches questions about a
		customer's problem, to a list of related answers. To each related answer you
		can link an expected problem, an expected solution, or a follow-up question.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The use of a diagnostic tree enables:</ListIntro>
            <ListItem>Fast call resolution.</ListItem>
            <ListItem>Reuse of existing knowledge.</ListItem>
            <ListItem>Accurate management information, which you can feed back into
			 planning decisions.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773140">
         <Level1>diagnostic tree</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="DistanZones_ts" Version="B60adoc1" ContextApps="ts">
      <Term>distance zones</Term>
      <Definition>With the help of distance zones users can specify traveling
		costs. A distance zone can be divided in several zone classes.</Definition>
      <Keyword type="glentry" order="d1e2773155">
         <Level1>distance zones</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000417" Version="B60adoc1" ContextApps="ts">
      <Term>downtime</Term>
      <Definition>The time during which an item or product is not available for
		use by the customer. This value is used in service contracts with an uptime
		agreement.</Definition>
      <Keyword type="glentry" order="d1e2772861">
         <Level1>downtime</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000026" Version="B60adoc1" ContextApps="ts">
      <Term>downtime ratio</Term>
      <Definition>The percentage of an activity's duration that an item will be
		out of operation when the activity is carried out on the item. The downtime
		ratio can be used for internal maintenance to determine the work-center
		capacity. For the percentage of the activity's duration, the capacity of the
		work center is reduced.</Definition>
      <Keyword type="glentry" order="d1e2771267">
         <Level1>downtime ratio</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000402" Version="B60adoc1" ContextApps="ts">
      <Term>effective date</Term>
      <Definition>Depending on its context, an effective date can be the first
		day on which a contract quotation is valid, the first day on which a service
		contract is active, or the first day on which you can use a template for
		quotations or contracts. The effective date often includes the effective time.</Definition>
      <Keyword type="glentry" order="d1e2772735">
         <Level1>effective date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000051" Version="B60asy04" ContextApps="ts">
      <Term>effectivity period</Term>
      <Definition>The number of days a contract quotation is valid.</Definition>
      <Keyword type="glentry" order="d1e2771398">
         <Level1>effectivity period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="OccupaFactor_ts" Version="B60asy04" ContextApps="ts">
      <Term>efficiency rate</Term>
      <Definition>The number of service employees required to carry out an
		activity or a task. You can calculate the duration of the reference activity
		based on the efficiency rate.</Definition>
      <Keyword type="glentry" order="d1e2773341">
         <Level1>efficiency rate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000416" Version="B60adoc1" ContextApps="ts">
      <Term>emergency</Term>
      <Definition>A call that requires immediate action and for which a service
		order is generated to inform the field service engineer.</Definition>
      <Keyword type="glentry" order="d1e2772826">
         <Level1>emergency</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000098" Version="B60asy04" ContextApps="ts">
      <Term>end date</Term>
      <Definition>The last date on which the terms are valid. It is displayed
		when the contract status changes from Free to Active.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListIntro/>
            <ListItem>If more than one phase exists for this term, the end date of
			 the last phase is displayed.</ListItem>
            <ListItem>If a warranty is linked to one of the items or configurations
			 in the contract, the date is equal to the start date plus the warranty period.</ListItem>
         </List>
      </Note>
      <Keyword type="glentry" order="d1e2771794">
         <Level1>end date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="escalated_call">
      <Term>escalated call</Term>
      <Definition>Depending on the time agreement with the customer, one of the
		following: A non-blocked and non-waiting call with status <GUIRef href="" role="manual">Registered</GUIRef> or <GUIRef href="" role="manual">Assigned</GUIRef> for which the current
		time is past the reaction time; A non-blocked and non-waiting call with status <GUIRef href="" role="manual">Registered</GUIRef> or <GUIRef href="" role="manual">Assigned</GUIRef> for which the current
		time is past the solution start time; A non-blocked and non-waiting call with
		status <GUIRef href="" role="manual">Registered</GUIRef>, <GUIRef href="" role="manual">Assigned</GUIRef>, <GUIRef href="" role="manual">In Process</GUIRef>, or <GUIRef href="" role="manual">Transferred</GUIRef> for which the current time is
		past the solution finish time.</Definition>
      <Keyword type="glentry" order="d1e2772831">
         <Level1>escalated call</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000420" Version="B60adoc1" ContextApps="ts">
      <Term>escalated call</Term>
      <Definition>A call that is registered or assigned, but for which no action
		was taken within the contract or warranty response time.</Definition>
      <Keyword type="glentry" order="d1e2772876">
         <Level1>escalated call</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000426" Version="B60adoc1" ContextApps="ts">
      <Term>execution finish time</Term>
      <Definition>The time at which the support engineer plans to finish working
		on the call.</Definition>
      <Keyword type="glentry" order="d1e2772907">
         <Level1>execution finish time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000425" Version="B60adoc1" ContextApps="ts">
      <Term>execution start time</Term>
      <Definition>The time at which the support engineer plans to start working
		on the call.</Definition>
      <Keyword type="glentry" order="d1e2772902">
         <Level1>execution start time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000465">
      <Term>expected maintenance moment</Term>
      <Definition>Moment when maintenance must be executed on the
		item.</Definition>
      <Keyword type="glentry" order="d1e2773925">
         <Level1>expected maintenance moment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000418" Version="B60adoc1" ContextApps="ts">
      <Term>expected problem</Term>
      <Definition>The problem as assessed and classified by the support engineer.</Definition>
      <Keyword type="glentry" order="d1e2772866">
         <Level1>expected problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000419" Version="B60adoc1" ContextApps="ts">
      <Term>expected solution</Term>
      <Definition>The solution to the expected problem as determined by the
		support engineer.</Definition>
      <Keyword type="glentry" order="d1e2772871">
         <Level1>expected solution</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000005" Version="B60adoc1" ContextApps="ts">
      <Term>expiry date</Term>
      <Definition>Depending on its context, an expiry date can be: The last day
		on which a contract quotation is valid. The default expiry date for a quotation
		is the quotation date + effectivity period of quotations [days], as set in the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session; The last day on which a service
		contract is active. After this date it becomes expired; The last day on which
		you can use a template for quotations or contracts. Note that the expiry date
		often includes the expiry time.</Definition>
      <Keyword type="glentry" order="d1e2771155">
         <Level1>expiry date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000077" Version="B60asy04" ContextApps="ts">
      <Term>expiry date</Term>
      <Definition>Depending on its context, the last day on which the contract
		quotation is valid or the last day on which the service contract is active.
		After this date it is expired.</Definition>
      <Keyword type="glentry" order="d1e2771593">
         <Level1>expiry date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000052" Version="B60adoc1" ContextApps="ts">
      <Term>expiry warning period</Term>
      <Definition>The number of days warning that is given to the service
		organization of the contract that is ending. ERP Enterprise uses the expiry date
		when service contracts that are about to expire, are printed.</Definition>
      <Keyword type="glentry" order="d1e2771403">
         <Level1>expiry warning period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ExternMainte_ts" Version="B60asy04" ContextApps="ts">
      <Term>external maintenance</Term>
      <Definition>
         <Link href="/baanerp/ts/glossary/glossary#PrevenMainte_ts" role="glossary">Preventive maintenance (PM)</Link> activities of an item done by a <Link href="/baanerp/ts/glossary/glossary#ServicEngine_ts" role="glossary">service engineer</Link> at
		the customer's site. This activity is defined in a contract.</Definition>
      <Keyword type="glentry" order="d1e2773161">
         <Level1>external maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ExternProble_ts" Version="B60adoc1" ContextApps="ts">
      <Term>external problem</Term>
      <Definition> 
         <Link href="/baanerp/ts/glossary/glossary#CorrecMainte_ts" role="glossary">Corrective maintenance</Link> carried out on an item done by a <Link href="/baanerp/ts/glossary/glossary#ServicEngine_ts" role="glossary">service engineer</Link> at
		the customer's site.</Definition>
      <Keyword type="glentry" order="d1e2773171">
         <Level1>external problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000043" Version="B60asy04" ContextApps="ts">
      <Term>external service-order documents</Term>
      <Definition>External service order documents include announcement sheets,
		appointment sheets, and repair reports.</Definition>
      <Keyword type="glentry" order="d1e2771351">
         <Level1>external service-order documents</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="failureanalysis_ts">
      <Term>Failure Analysis</Term>
      <Definition>Failure Analysis is defined as gathering up-to-date historic
		data related to confirmed failures and this data is used to understand the
		previous occurrence of failures.</Definition>
      <Keyword type="glentry" order="d1e2773740">
         <Level1>Failure Analysis</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="FieldChangeO_ts" Version="B60adoc1" ContextApps="ts">
      <Term>field change order (FCO)</Term>
      <Definition>An order to collect and modify, repair, or replace an item (for
		example, a product recall). You can apply the order to one or more customers.
		The order can be created by marketing, sales, or manufacturing.</Definition>
      <Keyword type="glentry" order="d1e2773187">
         <Level1>field change order (FCO)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="FielChanOrLi_ts" Version="B60adoc1" ContextApps="ts">
      <Term>field change order object lines</Term>
      <Definition>A field change order line specifies the serialized item that
		must be modified by the field change order (FCO), and the sold-to business
		partner who owns it. If a service order has been created for the FCO, the
		service order's number is displayed on the FCO line.</Definition>
      <Keyword type="glentry" order="d1e2773182">
         <Level1>field change order object lines</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000448">
      <Term>follow up</Term>
      <Definition>The follow-up activity required based on the maintenance
		trigger. Based on the maintenance trigger following decision can be taken for
		the notification.</Definition>
      <SimpleSection>
         <List>
            <ListItem>Do nothing</ListItem>
            <ListItem>Create planned activity</ListItem>
            <ListItem>Create work order</ListItem>
            <ListItem>Create service order and activity</ListItem>
            <ListItem>Link to existing work order</ListItem>
            <ListItem>Link to existing service order</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773825">
         <Level1>follow up</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000035" Version="B60asy04" ContextApps="ts">
      <Term>follow-up activity</Term>
      <Definition>The activity that must be carried out if the measured value of
		the inspection-measurement does not meet the norm value.</Definition>
      <Keyword type="glentry" order="d1e2771308">
         <Level1>follow-up activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000336" Version="B60asy04" ContextApps="ts">
      <Term>follow-up order</Term>
      <Definition>An order that is triggered by another order.</Definition>
      <Keyword type="glentry" order="d1e2772305">
         <Level1>follow-up order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000431" Version="B60adoc1" ContextApps="ts">
      <Term>follow-up work order</Term>
      <Definition>The work order that is used to carry out additional work on the
		material if the delivery type is <GUIRef href="/baanerp/ts/domains/wcs.dltp#followup" role="option">Follow-up Work Order</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772932">
         <Level1>follow-up work order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000337" Version="B60asy04" ContextApps="ts">
      <Term>forecast requirement factor</Term>
      <Definition>The factor that measures the probability that the resource is
		required.</Definition>
      <Keyword type="glentry" order="d1e2772310">
         <Level1>forecast requirement factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000338" Version="B60asy04" ContextApps="ts">
      <Term>functional breakdown</Term>
      <Definition>A multilevel or single-level display of a configuration's
		functional related components, elements and serialized items.</Definition>
      <Keyword type="glentry" order="d1e2772315">
         <Level1>functional breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000350" Version="B60adoc1" ContextApps="ts">
      <Term>functional element</Term>
      <Definition>A grouping of exchangeable items with identical functions.
		Functional elements can be used in item breakdowns, physical breakdowns, and
		reference activities.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>When a maintenance activity is defined for a configuration, a
		  functional element can be specified. This way, the activity applies to all
		  items covered by that functional element, and multiple, identical reference
		  activities for similar items are avoided.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2772371">
         <Level1>functional element</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000352" Version="B60asy04" ContextApps="ts">
      <Term>functional failure</Term>
      <Definition>The configuration or part of a configuration fails to meet its
		function.</Definition>
      <Keyword type="glentry" order="d1e2772386">
         <Level1>functional failure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000353" Version="B60asy04" ContextApps="ts">
      <Term>global maintenance planning</Term>
      <Definition>Long-term maintenance planning on a high level of activity
		aggregation.</Definition>
      <Keyword type="glentry" order="d1e2772391">
         <Level1>global maintenance planning</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000047" Version="B60adoc1" ContextApps="ts">
      <Term>global SRP</Term>
      <Definition>Global service resource planning (SRP) is the long-term
		planning phase for service orders that are defined in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, and planned for the
		mid-to-long term (months).</Definition>
      <Keyword type="glentry" order="d1e2771375">
         <Level1>global SRP</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000370" Version="B60adoc1" ContextApps="ts">
      <Term>graphical browser framework</Term>
      <Definition>A tool that is used to display a hierarchical structure in the
		form of a tree. Often, this tool also enables you to perform drag-and-drop
		operations.</Definition>
      <SimpleSection>
         <Paragraph> Example: To display a breakdown structure.</Paragraph>
         <Paragraph>Acronym: GBF</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772486">
         <Level1>graphical browser framework</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000382" Version="B60asy04" ContextApps="ts">
      <Term>graphical planning board</Term>
      <Definition>A table that graphically illustrates a planning.</Definition>
      <Keyword type="glentry" order="d1e2772582">
         <Level1>graphical planning board</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="GrossMarginG_ts" Version="B60adoc1" ContextApps="ts">
      <Term>gross margin</Term>
      <Definition>The difference between the sales amount and the standard costs
		against standard costs.</Definition>
      <SimpleSection>
         <Paragraph>How the gross margin is calculated depends on the setting of
		  the <GUIRef href="/baanerp/ts/soc/tssoc0100m000#tssoc000.gmba" role="manual">Margin Base</GUIRef> field in the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session.</Paragraph>
         <Paragraph>Acronym: GM</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773192">
         <Level1>gross margin</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000469">
      <Term>group</Term>
      <Definition>A group of activity sets.</Definition>
      <Keyword type="glentry" order="d1e2773945">
         <Level1>group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000375" Version="B60adoc1" ContextApps="ts">
      <Term>header data</Term>
      <Definition>The general information of a service contract, a service
		contract quotation, a service order or a service order quotation. The header
		data can consist of descriptive, business partner, financial, invoice, and
		duration data.</Definition>
      <Keyword type="glentry" order="d1e2772525">
         <Level1>header data</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="HelpDesk_ts" Version="B60asy04" ContextApps="ts">
      <Term>help desk</Term>
      <Definition>A direct support center, staffed by maintenance engineers who
		solve customer's questions and problems.</Definition>
      <Keyword type="glentry" order="d1e2773208">
         <Level1>help desk</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000376" Version="B60adoc1" ContextApps="ts">
      <Term>incidental changes</Term>
      <Definition>A type of service contract change that results from adding or
		removing items. or from adding, removing, or changing coverage terms and/or
		cost terms.</Definition>
      <Keyword type="glentry" order="d1e2772530">
         <Level1>incidental changes</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000119" Version="B60adoc1" ContextApps="ts">
      <Term>included</Term>
      <Definition>This indicates whether the term is included (or covered) in the
		contract. If the term is not included it must be invoiced.</Definition>
      <Keyword type="glentry" order="d1e2771905">
         <Level1>included</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000049" Version="B60adoc1" ContextApps="ts">
      <Term>independent variable</Term>
      <Definition>In the case of counter values (CV) or predicted activities
		(PA), the measurement type's independent variable of a will be of type time. In
		case of predicted inspections (PI), it can also be usage related.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>A tire has two variables: the number of kilometers traveled,
		  and the depth of its tread. Each kilometer traveled by the tire decreases its
		  tread depth. In this case, the independent variable is the number of kilometers
		  traveled by the tire, and is usage related. The dependent variable is the
		  tire's tread depth.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771383">
         <Level1>independent variable</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000377" Version="B60adoc1" ContextApps="ts">
      <Term>indexation</Term>
      <Definition>To raise or to lower contract prices by means of a user-defined
		percentage.</Definition>
      <Keyword type="glentry" order="d1e2772535">
         <Level1>indexation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000373" Version="B60adoc0" ContextApps="ts">
      <Term>Infor Mobile
		Service</Term>
      <Definition>An optional, remote extension to <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, Infor Mobile Service is
		an off-the-shelf, fully configurable, mobile field service automation
		application based on the client-agent-server architecture. By means of wireless
		mobile networks or landline dial-up, the field service engineer, who uses Infor Mobile Service,
		has access to information resources that are available in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772509">
         <Level1>Infor Mobile Service</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000427" Version="B60adoc1" ContextApps="ts">
      <Term>initiating work order</Term>
      <Definition>The work order from which the current work order is derived.</Definition>
      <Keyword type="glentry" order="d1e2772912">
         <Level1>initiating work order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000355" Version="B60asy04" ContextApps="ts">
      <Term>in-line maintenance</Term>
      <Definition>Maintenance activities that are carried out during operational
		use (between actual usage) of a configuration. In-line maintenance is carried
		out on location.</Definition>
      <Keyword type="glentry" order="d1e2772401">
         <Level1>in-line maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000362" Version="B60asy04" ContextApps="ts">
      <Term>inspection</Term>
      <Definition>A specific activity that is carried out to determine the
		condition and the status of a (part of a) configuration or process. Inspection
		activities can be based on inspection norms that are specified in documents.
		The inspection activities and inspection intervals are specified in the
		maintenance program.</Definition>
      <Keyword type="glentry" order="d1e2772445">
         <Level1>inspection</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000463">
      <Term>inspection</Term>
      <Definition>The actual measurement that takes place.</Definition>
      <Keyword type="glentry" order="d1e2773915">
         <Level1>inspection</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000042" Version="B60adoc1" ContextApps="ts">
      <Term>inspection report</Term>
      <Definition>A report that can be used to register the measured values on an
		item in case an inspection must be carried out.</Definition>
      <Keyword type="glentry" order="d1e2771346">
         <Level1>inspection report</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MeasurTypesB_ts" Version="B60asy04" ContextApps="ts">
      <Term>inspection templates</Term>
      <Definition>A set of measurements that you must carry out on items during
		an inspection. Inspection templates include the norm values that trigger the
		reference activities. If an inspection is carried out and the norm value that
		is defined for the dependent variable is exceeded, one or more reference
		activities must be performed.</Definition>
      <Keyword type="glentry" order="d1e2773312">
         <Level1>inspection templates</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000307" Version="B60adoc1" ContextApps="ts">
      <Term>installation</Term>
      <Definition>The list of (serialized) items that belong to an
		
Installation
		group.</Definition>
      <Keyword type="glentry" order="d1e2772150">
         <Level1>installation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ConfigTopObj_ts" Version="B60adoc1" ContextApps="ts">
      <Term>installation</Term>
      <Definition>Item on the highest level in the configuration structure.</Definition>
      <SimpleSection>
         <Paragraph>The top item can be defined as an item or as a serialized
		  item. The top item has only child relations and no parent relations.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773043">
         <Level1>installation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000308" Version="B60asy04" ContextApps="ts">
      <Term>installation
		activity</Term>
      <Definition>A reference activity that is part of a maintenance program to
		configure the Installation group .</Definition>
      <Keyword type="glentry" order="d1e2772155">
         <Level1>installation activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000306" Version="B60adoc1" ContextApps="ts">
      <Term>installation
		group</Term>
      <Definition>A set of serialized items that have the same location and are
		owned by the same business partner. Grouping serialized items into an
		
Installation
		group enables you to maintain them collectively.</Definition>
      <Keyword type="glentry" order="d1e2772145">
         <Level1>installation group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000133" Version="B60asy04" ContextApps="ts">
      <Term>installation
		group availability</Term>
      <Definition>Indicates the time that the Installation
		group is available for servicing or maintenance.</Definition>
      <Keyword type="glentry" order="d1e2771995">
         <Level1>installation group availability</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Installation_ts" Version="B60asy04" ContextApps="ts">
      <Term>installations</Term>
      <Definition>A unique object that can consist of a number of separate
		components. These components can have their own serial numbers. Installations
		are defined by making a description, by assigning the installation to an
		installation type, and by recording the location.</Definition>
      <Keyword type="glentry" order="d1e2773213">
         <Level1>installations</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000009" Version="B52asy16" ContextApps="ts">
      <Term>installment template</Term>
      <Definition>A template specifying an invoice method, the interval between
		two installments, the installment variant and the method in which the number of
		financial periods of an installment should be specified. The template can be
		used in contract quotations and service contracts.</Definition>
      <Keyword type="glentry" order="d1e2771163">
         <Level1>installment template</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="InternMainte_ts" Version="B60adoc1" ContextApps="ts">
      <Term>internal maintenance</Term>
      <Definition>The maintenance activities carried out on internal production
		devices.</Definition>
      <Keyword type="glentry" order="d1e2773218">
         <Level1>internal maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="InternProble_ts" Version="B60asy04" ContextApps="ts">
      <Term>internal problem</Term>
      <Definition>The corrective maintenance carried out on an internal
		production device.</Definition>
      <Keyword type="glentry" order="d1e2773223">
         <Level1>internal problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000393" Version="B60adoc1" ContextApps="ts">
      <Term>invoice interval</Term>
      <Definition>A limit on the amount of time that a customer can be billed
		from the total amount of time spent solving the call.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>If the time spent solving a call is lower than the minimum
			 time set in the invoicing interval, no invoice is made.</ListItem>
            <ListItem>If the amount of time spent solving the call is greater than
			 the maximum time set in the invoice interval, only the maximum time value in
			 the invoicing interval will be invoiced.</ListItem>
         </List>
      </Note>
      <Keyword type="glentry" order="d1e2772663">
         <Level1>invoice interval</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000075" Version="B60asy04" ContextApps="ts">
      <Term>item</Term>
      <Definition>A standard maintenance item.</Definition>
      <Keyword type="glentry" order="d1e2771587">
         <Level1>item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000300" Version="B60adoc1" ContextApps="ts">
      <Term>item breakdown</Term>
      <Definition>A standard item's list of constituent components. The item
		breakdown can be displayed as a multilevel structure or as a single-level
		structure, and can be used as input for a physical breakdown.</Definition>
      <Keyword type="glentry" order="d1e2772115">
         <Level1>item breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000366" Version="B60asy04" ContextApps="ts">
      <Term>item category</Term>
      <Definition>A classification by the item's form, fit, and function.</Definition>
      <Keyword type="glentry" order="d1e2772465">
         <Level1>item category</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000396" Version="B60adoc1" ContextApps="ts">
      <Term>ITU</Term>
      <Definition>Acronym of <Emphasis>International Telecommunications
		Union</Emphasis>. Formerly the CCITT (Consultative Committee for International
		Telephony and Telegraphy), the ITU is an international organization founded in
		1865 and headquartered in Geneva that sets communications standards.</Definition>
      <Keyword type="glentry" order="d1e2772698">
         <Level1>ITU</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000357" Version="B60asy04" ContextApps="ts">
      <Term>job quotation</Term>
      <Definition>A written proposal to a business partner for carrying out a set
		of maintenance activities.</Definition>
      <Keyword type="glentry" order="d1e2772412">
         <Level1>job quotation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000439" Version="B60adoc1" ContextApps="ts">
      <Term>job sheet</Term>
      <Definition>In <Emphasis>Infor Mobile Service</Emphasis>, a list of service order
		activities that are lined up for the service engineer.</Definition>
      <Keyword type="glentry" order="d1e2772417">
         <Level1>job sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="LaborRate_ts" Version="B60adoc1" ContextApps="ts">
      <Term>labor rate</Term>
      <Definition>The labor rate code, defined in the <GUIRef href="/baanerp/tc/ppl/tcppl0190m000" role="session">Labor Rate Codes (tcppl0190m000)</GUIRef> session in <GUIRef href="/baanerp/bp" role="package">People</GUIRef>. A sales rate and cost rate can be specified in
		this labor rate code.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>You can assign labor rates on a wider scale to, for
			 example,</ListIntro>
            <ListItem>A service department, for all work done by the service
			 department.</ListItem>
            <ListItem>An
Installation
			 group, for all work carried out on the Installation
			 group.</ListItem>
         </List>
         <List>
            <ListIntro>In the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session, default labor rate search paths
			 can be set for the following:</ListIntro>
            <ListItem>Estimated sales rate</ListItem>
            <ListItem>Estimated cost rate</ListItem>
            <ListItem>Actual sales rate</ListItem>
            <ListItem>Actual cost rate</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773239">
         <Level1>labor rate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="LabReqPlaAct_ts" Version="B60asy04" ContextApps="ts">
      <Term>labor requirements by planned activity</Term>
      <Definition>The tasks and/or service employees that are required to carry
		out an activity on an item.</Definition>
      <Keyword type="glentry" order="d1e2773228">
         <Level1>labor requirements by planned activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="LabReqRefAct_ts" Version="B60asy04" ContextApps="ts">
      <Term>labor requirements by reference activity</Term>
      <Definition>The tasks that are required to carry out an activity on an
		item. The labor requirements are used to plan the available capacity of labor
		(versus manpower). It can also can be used as a reference for quotations.</Definition>
      <Keyword type="glentry" order="d1e2773233">
         <Level1>labor requirements by reference activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000018" Version="B60adoc1" ContextApps="ts">
      <Term>labor type</Term>
      <Definition>The classification of work performed, and the time of day at
		which the work is performed (either normal working hours or overtime). Based on
		the kind of work and the hour type, you can use labor types to specify
		surcharges so that ERP Enterprise can
		calculate the actual labor costs in <GUIRef href="/baanerp/bp" role="package">People</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771230">
         <Level1>labor type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000358" Version="B60asy04" ContextApps="ts">
      <Term>life cycle</Term>
      <Definition>The item's economic lifetime.</Definition>
      <Keyword type="glentry" order="d1e2772425">
         <Level1>life cycle</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000383" Version="B60adoc1" ContextApps="ts">
      <Term>location</Term>
      <Definition>A physical, recognizable area in a maintenance shop, a service
		department, or a work center where parts are temporarily stored. Inbound and
		outbound handling is not registered in ERP Enterprise.</Definition>
      <Keyword type="glentry" order="d1e2772587">
         <Level1>location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000429" Version="B60adoc1" ContextApps="ts">
      <Term>maintainable quantity</Term>
      <Definition>The number of maintainable items/parts which must be repaired
		on the work order.</Definition>
      <Keyword type="glentry" order="d1e2772922">
         <Level1>maintainable quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000430" Version="B60adoc1" ContextApps="ts">
      <Term>maintained quantity</Term>
      <Definition>The number of maintained items/parts which went successfully
		through one or all steps of the work order process.</Definition>
      <Keyword type="glentry" order="d1e2772927">
         <Level1>maintained quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Maintenance_ts" Version="B60asy04" ContextApps="ts">
      <Term>maintenance</Term>
      <Definition>The actions required to restore an item to its serviceable
		condition. This includes inspection, modification, repair, overhaul, and
		servicing.</Definition>
      <Keyword type="glentry" order="d1e2773292">
         <Level1>maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000359" Version="B60asy04" ContextApps="ts">
      <Term>maintenance activity</Term>
      <Definition>The smallest unit of work that form the base for all
		maintenance to be carried out.</Definition>
      <Keyword type="glentry" order="d1e2772430">
         <Level1>maintenance activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MainteConcep_ts" Version="B60adoc1" ContextApps="ts">
      <Term>maintenance concept</Term>
      <Definition>A maintenance specification for non-customized items, stating
		which activities must be carried out during the maintenance cycle of the item.</Definition>
      <SimpleSection>
         <Paragraph>Also, the requirements needed to carry out the activities can
		  be specified. A single specific concept can cover various maintenance policies.</Paragraph>
         <Paragraph>A maintenance concept serves as a reference for long-term
		  maintenance planning of configurations and items.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773272">
         <Level1>maintenance concept</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000321" Version="B60asy04" ContextApps="ts">
      <Term>maintenance contract</Term>
      <Definition>A document that is used to register long-term agreements
		between a maintenance company and a customer. Such a document outlines the
		maintenance activities that are carried out on configurations. The contract
		also covers the agreed prices and discounts.</Definition>
      <Keyword type="glentry" order="d1e2772225">
         <Level1>maintenance contract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000322" Version="B60asy04" ContextApps="ts">
      <Term>maintenance document</Term>
      <Definition>A document that is required to restore an unserviceable item to
		the serviceable condition.</Definition>
      <SimpleSection>
         <Paragraph>For example Component Maintenance Manual (CMM) or an Overhaul
		  Manual (OM/OHM).</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772230">
         <Level1>maintenance document</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000323" Version="B60asy04" ContextApps="ts">
      <Term>maintenance event</Term>
      <Definition>A set of maintenance activities on a high aggregation level
		that can clearly be distinguished in time.</Definition>
      <Keyword type="glentry" order="d1e2772239">
         <Level1>maintenance event</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000447">
      <Term>maintenance notification</Term>
      <Definition>A notification that is generated based on a measurement and a
		related maintenance trigger.</Definition>
      <Keyword type="glentry" order="d1e2773819">
         <Level1>maintenance notification</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000324" Version="B60asy04" ContextApps="ts">
      <Term>maintenance order</Term>
      <Definition>A schedule of maintenance activities.</Definition>
      <Keyword type="glentry" order="d1e2772244">
         <Level1>maintenance order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MaintePlanni_ts" Version="B60adoc1" ContextApps="ts">
      <Term>maintenance planning</Term>
      <Definition>The list of activities planned for serialized items/Installation
		groups
		for the purpose of long term preventive maintenance.</Definition>
      <Keyword type="glentry" order="d1e2773282">
         <Level1>maintenance planning</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MaintePredic_ts" Version="B60adoc1" ContextApps="ts">
      <Term>maintenance prediction</Term>
      <Definition>The expected moments, on a relative timescale, when a specific
		measurement type does not meet specific norm values. As a result, specific
		reference activities must be carried out by way of preventive maintenance. A
		maintenance prediction can be a part of a maintenance concept, and is used for
		condition-based maintenance (CBM) in the first place, and for fine-tuning the
		maintenance concept in the second place. Maintenance predictions are optional
		to use. If present, maintenance predictions serve as input for the maintenance
		plan.</Definition>
      <Keyword type="glentry" order="d1e2773287">
         <Level1>maintenance prediction</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000325" Version="B60asy04" ContextApps="ts">
      <Term>maintenance program</Term>
      <Definition>A list of recurring maintenance activities that are prescribed
		and approved.</Definition>
      <Keyword type="glentry" order="d1e2772249">
         <Level1>maintenance program</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000414" Version="B60adoc1" ContextApps="ts">
      <Term>maintenance sales order</Term>
      <Definition>Orders that are used to plan, carry out, and control the
		maintenance on customer-owned components, products and the logistic handling of
		spare parts.</Definition>
      <Keyword type="glentry" order="d1e2772799">
         <Level1>maintenance sales order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000410" Version="B60adoc1" ContextApps="ts">
      <Term>maintenance sales order lines</Term>
      <Definition>Lines that store all details of the items that must be
		maintained, loaned, replaced, delivered, or received.</Definition>
      <Keyword type="glentry" order="d1e2772775">
         <Level1>maintenance sales order lines</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000445">
      <Term>maintenance trigger</Term>
      <Definition>The trigger for maintenance that must be performed for an item.
		This is linked to a measurement. When maintenance is triggered, a maintenance
		notification is generated.</Definition>
      <Keyword type="glentry" order="d1e2773809">
         <Level1>maintenance trigger</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000446">
      <Term>maintenance trigger set</Term>
      <Definition>The set of maintenance triggers that is used to trigger
		maintenance notifications during measurements.</Definition>
      <Keyword type="glentry" order="d1e2773814">
         <Level1>maintenance trigger set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000388" Version="B60adoc1" ContextApps="ts">
      <Term>master routing</Term>
      <Definition>A set of operations that can be carried out. The reference
		activities based on which operations are added to a master routing, must have
		the same characteristics, such as item, functional element, and service
		department.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>All the inspections, tests, cleaning activities, assembly
		  activities, disassembly activities, and repair activities that you can carry
		  out on an engine.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2772612">
         <Level1>master routing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000326" Version="B60asy04" ContextApps="ts">
      <Term>material management</Term>
      <Definition>The control of the serviceable and unserviceable components
		flow in a shop maintenance environment.</Definition>
      <Keyword type="glentry" order="d1e2772254">
         <Level1>material management</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000030" Version="B60adoc1" ContextApps="ts">
      <Term>material requirements by planned activity</Term>
      <Definition>The required materials to carry out an activity on a specific
		item or serialized item. This data can be used for the replenishment orders of
		new items.</Definition>
      <Keyword type="glentry" order="d1e2771287">
         <Level1>material requirements by planned activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MeanTimeBetw_ts" Version="B60asy04" ContextApps="ts">
      <Term>Mean Time Between Failure</Term>
      <Definition>The average time interval between failures of a repairable
		product for a defined unit of measure. For example: operating hours, cycles,
		kilometers, or miles. Acronym: MTBF</Definition>
      <Keyword type="glentry" order="d1e2773297">
         <Level1>Mean Time Between Failure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000125" Version="B60adoc1" ContextApps="ts">
      <Term>Mean Time To Repair</Term>
      <Definition>The average time interval between the moment a failure is
		registered and the moment that the failure is solved. For example, the failure
		is registered by means of a call and is solved by means of a service order.
		Acronym: MTTR</Definition>
      <Keyword type="glentry" order="d1e2771942">
         <Level1>Mean Time To Repair</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Measurement_ts" Version="B60asy04" ContextApps="ts">
      <Term>measurement</Term>
      <Definition>A standard measurement that consists of a measuring quantity
		and a measuring characteristic. The determination of the value of a certain
		dependent measuring quantity of an item in a specific situation.</Definition>
      <Keyword type="glentry" order="d1e2773317">
         <Level1>measurement</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000462">
      <Term>measurement</Term>
      <Definition>The actual measurement that takes place.</Definition>
      <Keyword type="glentry" order="d1e2773910">
         <Level1>measurement</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000010" Version="B60adoc1" ContextApps="ts">
      <Term>measurement type</Term>
      <Definition>A particular measurement that is used to determine the value of
		an item's variable (measuring quantity) in a specific situation. Example: Tire tread
		depth.</Definition>
      <Keyword type="glentry" order="d1e2771169">
         <Level1>measurement type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000460">
      <Term>measurement type</Term>
      <Definition>Kind of measurement that must be done. Example measure profile,
		acid level, mileage.</Definition>
      <Keyword type="glentry" order="d1e2773900">
         <Level1>measurement type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000313" Version="B60adoc1" ContextApps="ts">
      <Term>measurement unit</Term>
      <Definition>Units used to express measurements. The unit can be
		user-defined or selected from the list of units in <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772184">
         <Level1>measurement unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000443">
      <Term>measurement unit</Term>
      <Definition>Unit of the measurement.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Kilometers, Hours, Millimeters and so on.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773789">
         <Level1>measurement unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MeasurQuanti_ts" Version="B60asy04" ContextApps="ts">
      <Term>measuring quantities</Term>
      <Definition>A measuring quantity is a measurable (physical) variable that
		identifies the units of this variable. For example: pressure in kPa. Measuring
		quantities can be used to define measurements.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The measurement exhaust temperature interval results in a
		  value of the measuring quantity temperature in Celsius.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773302">
         <Level1>measuring quantities</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000327" Version="B60asy04" ContextApps="ts">
      <Term>modification</Term>
      <Definition>Activities that are carried out on the operation of a
		configuration or on a part of a configuration.</Definition>
      <Keyword type="glentry" order="d1e2772259">
         <Level1>modification</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000329" Version="B60asy04" ContextApps="ts">
      <Term>modification directive</Term>
      <Definition>Documents that specify the requirements for technical or
		operational improvements on configurations. These requirements can affect
		certain maintenance activities.</Definition>
      <Keyword type="glentry" order="d1e2772269">
         <Level1>modification directive</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000330" Version="B60asy04" ContextApps="ts">
      <Term>multilevel breakdown</Term>
      <Definition>A lists of components on all levels.</Definition>
      <Keyword type="glentry" order="d1e2772274">
         <Level1>multilevel breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000335" Version="B60asy04" ContextApps="ts">
      <Term>offline/online indicator</Term>
      <Definition>An indicator that specifies if a configuration can be
		maintained during operations, during standstill, or during both operations and
		standstill.</Definition>
      <Keyword type="glentry" order="d1e2772300">
         <Level1>offline/online indicator</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000331" Version="B60asy04" ContextApps="ts">
      <Term>offline maintenance</Term>
      <Definition>Maintenance activities for which the configuration is taken out
		of active operation to carry out maintenance.</Definition>
      <Keyword type="glentry" order="d1e2772279">
         <Level1>offline maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000339" Version="B60asy04" ContextApps="ts">
      <Term>on-condition maintenance</Term>
      <Definition>A primary maintenance policy in which repetitive inspections or
		tests are carried out to determine the condition of the units, systems, or
		portions of a structure with regard to continued serviceability. If the item's
		condition falls outside specified values, corrective action is taken.</Definition>
      <Keyword type="glentry" order="d1e2772320">
         <Level1>on-condition maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000404" Version="B60adoc1" ContextApps="ts">
      <Term>operation</Term>
      <Definition>A step in a master routing. Based on a reference activity, an
		operation is identified by a unique sequence number.</Definition>
      <Keyword type="glentry" order="d1e2772745">
         <Level1>operation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000340" Version="B60asy04" ContextApps="ts">
      <Term>operational schedule</Term>
      <Definition>A scheme that specifies the use of a configuration for
		operational and maintenance purposes.</Definition>
      <Keyword type="glentry" order="d1e2772325">
         <Level1>operational schedule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000432" Version="B60adoc1" ContextApps="ts">
      <Term>order escalation time</Term>
      <Definition>The period of time after which a released emergency service
		order will be treated as a deferred emergency service order. For an emergency
		service order not yet attended by a service engineer, when the order release
		date/time plus the order escalation time occurs in the past, that order is
		treated as a deferred emergency service order. The list of such orders can be
		viewed using the <GUIRef href="/baanerp/ts/soc/tssoc2502m000" role="session">Deferred Emergency Service Orders (tssoc2502m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2772941">
         <Level1>order escalation time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000394" Version="B60adoc1" ContextApps="ts">
      <Term>order procedure</Term>
      <Definition>Classifies the nature of the service activities that are
		required. In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef> two
		procedures are predefined: <GUIRef href="/baanerp/ts/domains/mdm.odpr#normal" role="option">Normal</GUIRef> and <GUIRef href="/baanerp/ts/domains/mdm.odpr#emergency" role="option">Emergency</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772676">
         <Level1>order procedure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Other_ts" Version="B60asy04" ContextApps="ts">
      <Term>other</Term>
      <Definition>All service activities that are not covered by the following
		service types: help desk, internal problem, external problem, internal
		maintenance, external maintenance, depot repair, and claim processing.</Definition>
      <Keyword type="glentry" order="d1e2773370">
         <Level1>other</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="OthReqPlaAct_ts" Version="B60asy04" ContextApps="ts">
      <Term>other requirements by planned activity</Term>
      <Definition>All other requirements (such as, tooling, traveling, and
		subcontracting) for carrying out the activity on the item.</Definition>
      <Keyword type="glentry" order="d1e2773346">
         <Level1>other requirements by planned activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="OthReqRefAct_ts" Version="B60asy04" ContextApps="ts">
      <Term>other requirements by reference activity</Term>
      <Definition>All other requirements needed to carry out the activity.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following requirements are predefined:</ListIntro>
            <ListItem>Tooling</ListItem>
            <ListItem>Traveling</ListItem>
            <ListItem>Subcontracting</ListItem>
            <ListItem>Help desk</ListItem>
            <ListItem>Other</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773351">
         <Level1>other requirements by reference activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000341" Version="B60asy04" ContextApps="ts">
      <Term>overhaul</Term>
      <Definition>All the maintenance and service activities that must be carried
		out on a component to make it serviceable again.</Definition>
      <Keyword type="glentry" order="d1e2772330">
         <Level1>overhaul</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000413" Version="B60adoc1" ContextApps="ts">
      <Term>paging</Term>
      <Definition>A messaging system, where short messages are sent by dialing a
		phone number and putting in a message. The message, which is received using a
		pager or another paging-enabled device, can either be a numeric code or a text
		message. In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, paging
		is used to inform the field service engineer of the service order to be carried
		out.</Definition>
      <Keyword type="glentry" order="d1e2772791">
         <Level1>paging</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000310" Version="B60adoc1" ContextApps="ts">
      <Term>physical breakdown</Term>
      <Definition>A serialized item's composition and structure, defined by the
		parent-child relationships of its constituent items. The physical breakdown can
		be displayed in a multilevel structure or a single-level structure.</Definition>
      <Keyword type="glentry" order="d1e2772165">
         <Level1>physical breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000024" Version="B60adoc1" ContextApps="ts">
      <Term>planned activities</Term>
      <Definition>The fixed moments on which preventive maintenance, by means of
		planned activities, must be carried out on serialized items/Installation
		groups. Service maintenance planning shows the demand
		of service activities in the long term and can be used as input for the service
		order procedure. Maintenance planning can be generated from the maintenance
		concept.</Definition>
      <Keyword type="glentry" order="d1e2771257">
         <Level1>planned activities</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000444">
      <Term>position</Term>
      <Definition>The point where the measurement is performed.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Measuring profile of a tire, specify Left Front/ Right Front
		  and so on.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773799">
         <Level1>position</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000012" Version="B60adoc1" ContextApps="ts">
      <Term>predicted activity</Term>
      <Definition>On a relative timescale the expected moments that certain
		measurement types do not meet their norm values. As a result, certain reference
		activities must be carried out as a matter of preventive maintenance. A
		maintenance prediction can be a part of a maintenance concept. A maintenance
		prediction is used for condition-based maintenance (CBM) in the first place and
		to fine-tune the maintenance concept.</Definition>
      <SimpleSection>
         <Paragraph>The maintenance intervals are based on the predicted progress
		  of a specific measuring quantity's value (dependent variable). This value is
		  based on measuring data from the past (history data). This method optimizes the
		  maintenance intervals. The measuring data that is obtained during maintenance
		  can be filled into history again. So, the maintenance prediction is
		  continuously amended with the latest measurements. You can compare the
		  predicted activities with counter value (CV) activities.</Paragraph>
         <Paragraph>You can also use service maintenance concepts as a reference
		  for the service maintenance planning of items.</Paragraph>
         <Paragraph>The effectivity period of a maintenance prediction is limited
		  by the period length which is recorded by the reference item.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>After selling a car, the first maintenance activity is due
		  one month (or 1,000 km) after the sale.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771179">
         <Level1>predicted activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000455">
      <Term>preferred engineer</Term>
      <Definition>Service engineer selected to perform the
		activities.</Definition>
      <Keyword type="glentry" order="d1e2773874">
         <Level1>preferred engineer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PreferEngine_ts" Version="B60adoc1" ContextApps="ts">
      <Term>preferred service employee</Term>
      <Definition>A service engineer who is qualified to maintain a specific Installation
		group and/or serialized item. This makes sure that the
		Installation
		group and/or serialized item is always (if possible)
		maintained by the same service engineer.</Definition>
      <Keyword type="glentry" order="d1e2773375">
         <Level1>preferred service employee</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PrevenMainte_ts" Version="B60asy04" ContextApps="ts">
      <Term>Preventive Maintenance (PM)</Term>
      <Definition>The maintenance activities that are carried out on a regular
		basis to prevent malfunctions or failures.</Definition>
      <Keyword type="glentry" order="d1e2773380">
         <Level1>Preventive Maintenance (PM)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000441">
      <Term>preventive maintenance scenario</Term>
      <Definition>The scenario that can be used to generate planned activities.
		Preventive maintenance scenario can be of the following type:</Definition>
      <SimpleSection>
         <List>
            <ListItem>time based scenario - Example maintenance
			 scenario occurs 12 times a year.</ListItem>
            <ListItem>counter based scenario - Example after 10000 km
			 execute maintenance.</ListItem>
            <ListItem>condition based scenario - Example after profile of tire is below 3
			 mm.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773766">
         <Level1>preventive maintenance scenario</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000409" Version="B60adoc1" ContextApps="ts">
      <Term>pricing method</Term>
      <Definition>The method indicating how the sales order price is determined.</Definition>
      <Keyword type="glentry" order="d1e2772770">
         <Level1>pricing method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PricinMethod_ts" Version="B60adoc1" ContextApps="ts">
      <Term>pricing method</Term>
      <Definition>The method indicating how the contract price is
		determined.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following pricing methods are available:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.prmt#sales" role="option">Sales Value of Configuration</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.prmt#budget" role="option">Budgeted Service Costs</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/ctm.prmt#template.price" role="option">Installation Group/Item Pricing</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773385">
         <Level1>pricing method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000392" Version="B60adoc1" ContextApps="ts">
      <Term>priority factor</Term>
      <Definition>The priority factor is calculated from any priorities assigned
		to the call.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>The item priority is either the serialized item priority or
		  the priority of the Installation
		  group to which the item belongs.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2772653">
         <Level1>priority factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ProbabilityAnalysis_ts">
      <Term>Probability Analysis</Term>
      <Definition>Diagnostic tools which calculates the probability of a
		specified solution solving a known problem. The data captured from the
		completed service order and the solved calls is used to calculate the
		probability.</Definition>
      <Keyword type="glentry" order="d1e2773696">
         <Level1>Probability Analysis</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000343" Version="B60asy04" ContextApps="ts">
      <Term>problem</Term>
      <Definition>A source or symptom of malfunction or disturbance.</Definition>
      <Keyword type="glentry" order="d1e2772340">
         <Level1>problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ProbleCatego_ts" Version="B60asy04" ContextApps="ts">
      <Term>problem category</Term>
      <Definition>A call can be a question, complaint, or malfunction.</Definition>
      <Keyword type="glentry" order="d1e2773406">
         <Level1>problem category</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000001" Version="B60asy04" ContextApps="ts">
      <Term>problem priority</Term>
      <Definition>An indicator that designates the urgency of the problem.</Definition>
      <Keyword type="glentry" order="d1e2771115">
         <Level1>problem priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000021" Version="B60asy04" ContextApps="ts">
      <Term>problem-priority factor</Term>
      <Definition>The problem priority divided by 100.</Definition>
      <Keyword type="glentry" order="d1e2771140">
         <Level1>problem-priority factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ProducLifeCy_ts" Version="B60asy04" ContextApps="ts">
      <Term>product life cycle</Term>
      <Definition>The item's lifetime.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>After exceeding the lifetime, the item</ListIntro>
            <ListItem>Must be scrapped and replaced by a new item.</ListItem>
            <ListItem>Can be sent for waste recycling.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773411">
         <Level1>product life cycle</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000312" Version="B60asy04" ContextApps="ts">
      <Term>project-breakdown structure</Term>
      <Definition>A charge (element) breakdown structure or an element structure
		that is defined in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772176">
         <Level1>project-breakdown structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000028" Version="B60adoc1" ContextApps="ts">
      <Term>question</Term>
      <Definition>A question that a support engineer can ask a customer who calls
		the call center.</Definition>
      <Keyword type="glentry" order="d1e2771277">
         <Level1>question</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000053" Version="B60asy04" ContextApps="ts">
      <Term>quotation history</Term>
      <Definition>The information from a particular quotation.</Definition>
      <Keyword type="glentry" order="d1e2771408">
         <Level1>quotation history</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000089" Version="B60asy04" ContextApps="ts">
      <Term>quotation status</Term>
      <Definition>The stage a contract quotation is at:</Definition>
      <SimpleSection>
         <Paragraph> 
            <GUIRef href="/baanerp/ts/domains/ctm.squo#free" role="option">Free</GUIRef>: the quotation is in the
		  process of being developed, and can be modified as required.</Paragraph>
         <Paragraph> 
            <GUIRef href="/baanerp/ts/domains/ctm.squo#printed" role="option">Printed</GUIRef>: the quotation has
		  been finalized and can now be sent to the business partner. On receipt of the
		  quotation, the business partner can accept it, reject it, or request
		  modification.</Paragraph>
         <Paragraph> 
            <GUIRef href="/baanerp/ts/domains/ctm.squo#accepted" role="option">Accepted (for Contract)</GUIRef>: the quotation has been accepted by the business partner,
		  and can now be processed into a quotation.</Paragraph>
         <Paragraph> 
            <GUIRef href="/baanerp/ts/domains/ctm.squo#processed" role="option">Processed</GUIRef>: the quotation
		  has been processed into a contract, and can now be posted to history.</Paragraph>
         <Paragraph> 
            <GUIRef href="/baanerp/ts/domains/ctm.squo#canceled" role="option">Canceled</GUIRef>: the quotation
		  has been canceled by the business partner, and can now be posted to history.</Paragraph>
         <Paragraph/>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771711">
         <Level1>quotation status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000421" Version="B60adoc1" ContextApps="ts">
      <Term>reaction time</Term>
      <Definition>The time by which the call center must react to a customer's
		call.</Definition>
      <Keyword type="glentry" order="d1e2772882">
         <Level1>reaction time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ReactiTime_ts" Version="B60adoc1" ContextApps="ts">
      <Term>reaction time</Term>
      <Definition>The time by which the call center must respond to a customer's
		call.</Definition>
      <Keyword type="glentry" order="d1e2773424">
         <Level1>reaction time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000096" Version="B60asy04" ContextApps="ts">
      <Term>reference A</Term>
      <Definition>The reference by which the sold-to business partner identifies
		the purchase order. This reference is printed on the service contract or
		quotation.</Definition>
      <Keyword type="glentry" order="d1e2771775">
         <Level1>reference A</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000405" Version="B60adoc1" ContextApps="ts">
      <Term>reference activity</Term>
      <Definition>The smallest unit of work that is required to carry out
		maintenance.</Definition>
      <Keyword type="glentry" order="d1e2772750">
         <Level1>reference activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="RefereActivi_ts" Version="B60adoc1" ContextApps="ts">
      <Term>reference activity</Term>
      <Definition>A group activity or a single activity (directive) that is
		planned for a serialized item or Installation
		group. A list of reference activities for an item
		forms a maintenance concept.</Definition>
      <Keyword type="glentry" order="d1e2773435">
         <Level1>reference activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000011" Version="B60asy04" ContextApps="ts">
      <Term>reference activity by item</Term>
      <Definition>Maintenance specification (lines) stating, when reference
		activities should be carried out on specific items. Also specified are the
		materials and means required to carry out these reference activities. One
		specific concept can cover different maintenance policies. A maintenance
		concept serves as a reference for long-term maintenance planning of
		configurations/items.</Definition>
      <Keyword type="glentry" order="d1e2771174">
         <Level1>reference activity by item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000384" Version="B60adoc1" ContextApps="ts">
      <Term>reference activity condition</Term>
      <Definition>The setup of an item that is required to carry out a reference
		activity.</Definition>
      <Keyword type="glentry" order="d1e2772592">
         <Level1>reference activity condition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000344" Version="B60asy04" ContextApps="ts">
      <Term>reference activity constraint</Term>
      <Definition>An activity that must be carried out to activate or de-activate
		a certain constraint.</Definition>
      <Keyword type="glentry" order="d1e2772345">
         <Level1>reference activity constraint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="RefActGroup_ts" Version="B60adoc1" ContextApps="ts">
      <Term>reference activity group</Term>
      <Definition>A group of reference activities with similar characteristics.
		For example, the Cleaning reference activity group or the Inspection reference
		activity group.</Definition>
      <Keyword type="glentry" order="d1e2773430">
         <Level1>reference activity group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000345" Version="B60asy04" ContextApps="ts">
      <Term>reference activity structure</Term>
      <Definition>A set of reference activities linked through sequential and
		hierarchical relationships and dependencies.</Definition>
      <Keyword type="glentry" order="d1e2772351">
         <Level1>reference activity structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000438">
      <Term>reference B</Term>
      <Definition>The reference by which the subcontractor identifies the
		subcontract agreement.</Definition>
      <Keyword type="glentry" order="d1e2772979">
         <Level1>reference B</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000440">
      <Term>reference item</Term>
      <Definition>The item for which the specifications are same as an existing
		customized item or a standard item which is not produced currently.The
		reference item is the base item which is referred to when you create a
		customized item.</Definition>
      <Keyword type="glentry" order="d1e2773761">
         <Level1>reference item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000063" Version="B60asy04" ContextApps="ts">
      <Term>related answer</Term>
      <Definition>An answer in the diagnostic tree that is related to another
		question, which is relevant to the current problem.</Definition>
      <Keyword type="glentry" order="d1e2771453">
         <Level1>related answer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000379" Version="B60adoc1" ContextApps="ts">
      <Term>renewal with indexation</Term>
      <Definition>If the contract change type is <GUIRef href="" role="manual">Renewal with Indexation</GUIRef>, contract is renewed and indexed simultaneously. Indexation
		is applied to all configuration lines irrespective of the pricing
		method.</Definition>
      <Keyword type="glentry" order="d1e2772546">
         <Level1>renewal with indexation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000346" Version="B60asy04" ContextApps="ts">
      <Term>repair</Term>
      <Definition>To make a component serviceable again.</Definition>
      <Keyword type="glentry" order="d1e2772356">
         <Level1>repair</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000347" Version="B60asy04" ContextApps="ts">
      <Term>repairable item</Term>
      <Definition>An item that can be economically restored to its serviceable
		condition and which can consist of replaceable parts.</Definition>
      <Keyword type="glentry" order="d1e2772361">
         <Level1>repairable item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000040" Version="B60asy04" ContextApps="ts">
      <Term>repair report</Term>
      <Definition>A report that informs the business partner about the findings
		of the service orders, in case repairs have been carried out on specific items.
		A template of the letter can be defined in the SOC parameters. For each
		activity an appendix (standard layout) will be printed. This appendix is
		printed in the language of the business partner.</Definition>
      <Keyword type="glentry" order="d1e2771336">
         <Level1>repair report</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Repairwarranty_ts">
      <Term>Repair Warranty</Term>
      <Definition>The service provider's guarantee that the product is repaired
		free of charge, if the repair done earlier on the product is not satisfactory
		or not proper.</Definition>
      <Keyword type="glentry" order="d1e2773746">
         <Level1>Repair Warranty</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000064" Version="B60asy04" ContextApps="ts">
      <Term>reported problem</Term>
      <Definition>The problem initially reported by the business partner.</Definition>
      <Keyword type="glentry" order="d1e2771458">
         <Level1>reported problem</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000424" Version="B60adoc1" ContextApps="ts">
      <Term>reported time</Term>
      <Definition>The date and time when a call was received and registered.</Definition>
      <Keyword type="glentry" order="d1e2772897">
         <Level1>reported time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000065" Version="B60adoc1" ContextApps="ts">
      <Term>required activity</Term>
      <Definition>The action required, as determined by the service/support
		engineer, to solve the call.</Definition>
      <Keyword type="glentry" order="d1e2771463">
         <Level1>required activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000457">
      <Term>required capacity</Term>
      <Definition>The total available capacity of the service
		engineer.</Definition>
      <Keyword type="glentry" order="d1e2773884">
         <Level1>required capacity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000033" Version="B60adoc1" ContextApps="ts">
      <Term>requirement lines</Term>
      <Definition>The lines that specify the resources required to carry out an
		activity. Requirement lines can comprise material, tool, and other
		requirements.</Definition>
      <Keyword type="glentry" order="d1e2771297">
         <Level1>requirement lines</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Requirements_ts" Version="B60adoc1" ContextApps="ts">
      <Term>requirements</Term>
      <Definition>The material, labor and other requirements can be defined for
		a reference/planned activity.</Definition>
      <Keyword type="glentry" order="d1e2773440">
         <Level1>requirements</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000470">
      <Term>resource</Term>
      <Definition>A service engineer that executes a service order or a
		department that is responsible for executing a planned activity or work
		order.</Definition>
      <Keyword type="glentry" order="d1e2773951">
         <Level1>resource</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000389" Version="B60adoc1" ContextApps="ts">
      <Term>resource requirement</Term>
      <Definition>The resource that is required for a reference activity. You
		can specify resource requirements by using one of the following resource types: <GUIRef href="/baanerp/ts/domains/acm.rtyp#material" role="option">Material</GUIRef>, <GUIRef href="/baanerp/ts/domains/acm.rtyp#labor" role="option">Labor</GUIRef>, <GUIRef href="/baanerp/ts/domains/acm.rtyp#tool" role="option">Tool</GUIRef>, <GUIRef href="/baanerp/ts/domains/acm.rtyp#subcon" role="option">Subcontracting</GUIRef>, or <GUIRef href="/baanerp/ts/domains/acm.rtyp#other" role="option">Other</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2772623">
         <Level1>resource requirement</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ResponTime_ts" Version="B60adoc1" ContextApps="ts">
      <Term>response time</Term>
      <Definition>A response time defines, from the time a call is registered,
		the period of time within which: The service provider must react to the call; A
		solution to the call's problem must be started; A solution to the call's
		problem must be finished.</Definition>
      <Keyword type="glentry" order="d1e2773445">
         <Level1>response time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ReturnMateri_ts" Version="B60asy04" ContextApps="ts">
      <Term>return material authorization</Term>
      <Definition>Expected return of material from the customer to the service
		provider. Acronym: RMA</Definition>
      <Keyword type="glentry" order="d1e2773450">
         <Level1>return material authorization</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Revenue_ts" Version="B60asy04" ContextApps="ts">
      <Term>revenue</Term>
      <Definition>The amount received or gained, usually measured in money.</Definition>
      <Keyword type="glentry" order="d1e2773455">
         <Level1>revenue</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000387" Version="B60adoc1" ContextApps="ts">
      <Term>routing option</Term>
      <Definition>A subset of master routing. A predefined set of operations that
		can be carried out. Each operation is identified by a unique sequence number.</Definition>
      <Keyword type="glentry" order="d1e2772607">
         <Level1>routing option</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000458">
      <Term>rule book for maintenance scenarios</Term>
      <Definition>The book that contains rules that defines which maintenance
		scenarios must be used when a maintenance plan is generated.</Definition>
      <Keyword type="glentry" order="d1e2773889">
         <Level1>rule book for maintenance scenarios</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000349" Version="B60asy04" ContextApps="ts">
      <Term>salvation analysis</Term>
      <Definition>Activities carried out to determine whether or not it is
		feasible to repair a component after an initial decision to destroy it. The
		salvation analysis for configurations that require a high safety level are
		different than for configurations that only have an economic value.</Definition>
      <Keyword type="glentry" order="d1e2772366">
         <Level1>salvation analysis</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000351" Version="B60asy04" ContextApps="ts">
      <Term>scheduled maintenance</Term>
      <Definition>Maintenance activities of which the time of execution has been
		fixed together with a proper activity assignment and activity sequencing.</Definition>
      <Keyword type="glentry" order="d1e2772381">
         <Level1>scheduled maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000354" Version="B60asy04" ContextApps="ts">
      <Term>scheduling</Term>
      <Definition>To determine the sequence in which maintenance activities must
		be performed.</Definition>
      <Keyword type="glentry" order="d1e2772396">
         <Level1>scheduling</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000356" Version="B60adoc1" ContextApps="ts">
      <Term>scrap</Term>
      <Definition>The components that are outside their original specifications
		and that are impractical to repair.</Definition>
      <Keyword type="glentry" order="d1e2772406">
         <Level1>scrap</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000082" Version="B60adoc1" ContextApps="ts">
      <Term>search argument</Term>
      <Definition>An alternative form of a description used for convenience
		during searching. A search key is usually an abbreviation, an acronym, or a
		mnemonic alternative to a full description.</Definition>
      <Keyword type="glentry" order="d1e2771620">
         <Level1>search argument</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000371" Version="B60adoc1" ContextApps="ts">
      <Term>search engine</Term>
      <Definition>A program that searches for configurations based on search
		criteria such as sold-to business partner code/name/address/ZIP code, (service)
		department, service area, responsible engineer, and so on.</Definition>
      <Keyword type="glentry" order="d1e2772496">
         <Level1>search engine</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Objects_ts" Version="B60asy04" ContextApps="ts">
      <Term>serialized item</Term>
      <Definition>An item that is uniquely identified by the item code
		(manufacturer part number) in combination with the serial number.</Definition>
      <Keyword type="glentry" order="d1e2773336">
         <Level1>serialized item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000134" Version="B60asy04" ContextApps="ts">
      <Term>serialized-item availability</Term>
      <Definition>Indicates the time that the serialized-item is available for
		servicing or maintenance.</Definition>
      <Keyword type="glentry" order="d1e2772000">
         <Level1>serialized-item availability</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ObjectGroup_ts" Version="B60asy04" ContextApps="ts">
      <Term>serialized item group</Term>
      <Definition>A group of serialized items with similar features.</Definition>
      <Keyword type="glentry" order="d1e2773322">
         <Level1>serialized item group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000003" Version="B60asy04" ContextApps="ts">
      <Term>serialized-item priority</Term>
      <Definition>An indicator that designates the urgency of a problem that
		occurs to a serialized item.</Definition>
      <Keyword type="glentry" order="d1e2771125">
         <Level1>serialized-item priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000019" Version="B60adoc1" ContextApps="ts">
      <Term>serialized-item priority factor</Term>
      <Definition>The serialized-item priority divided by 100.</Definition>
      <Keyword type="glentry" order="d1e2771130">
         <Level1>serialized-item priority factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000386" Version="B60adoc1" ContextApps="ts">
      <Term>serialized-item range</Term>
      <Definition>One or more serial numbers that are defined for a particular
		serialized item.</Definition>
      <Keyword type="glentry" order="d1e2772602">
         <Level1>serialized-item range</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000315" Version="B60adoc1" ContextApps="ts">
      <Term>serialized-item range group</Term>
      <Definition>A group that can be used to link activities and documents to a
		range of items including different serial numbers.</Definition>
      <Keyword type="glentry" order="d1e2772192">
         <Level1>serialized-item range group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ObjectRelati_ts" Version="B60adoc1" ContextApps="ts">
      <Term>serialized item relations</Term>
      <Definition>The indication of a serialized item's position in a physical
		breakdown, by means of parent-child relations. A serialized item in a physical
		breakdown is above its child item(s) and below its parent item.</Definition>
      <SimpleSection>
         <Paragraph>In a structure, a child item can only have one parent item,
		  whereas a parent item can have multiple child items.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773327">
         <Level1>serialized item relations</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SerialNumber_ts" Version="B60adoc1" ContextApps="ts">
      <Term>serial number</Term>
      <Definition>A number that, together with the item code or manufacturer part
		number, uniquely identifies a component, an item, a machine, or an
		installation.</Definition>
      <SimpleSection>
         <Paragraph>This serial number is usually shown together with the
		  manufacturer part number and other identification data on an identification
		  plate that is attached to the item.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773460">
         <Level1>serial number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000360" Version="B60asy04" ContextApps="ts">
      <Term>serviceable item</Term>
      <Definition>A condition of an item that indicates that the item can be used
		in a configuration.</Definition>
      <Keyword type="glentry" order="d1e2772435">
         <Level1>serviceable item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicActivi_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service activity</Term>
      <Definition>An activity with tasks and cost lines linked to it. This
		activity can be also be a linked to a coverage type.</Definition>
      <Keyword type="glentry" order="d1e2773499">
         <Level1>service activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000025" Version="B60adoc1" ContextApps="ts">
      <Term>service activity price list</Term>
      <Definition>A price list, used to define the contract price or the price of
		individual service orders. Service costs are calculated on the basis of
		standard price lists. In a price list, both the cost price and the sales price
		can be recorded for an item, a reference activity, a service type, or a
		combination of these elements.</Definition>
      <Keyword type="glentry" order="d1e2771262">
         <Level1>service activity price list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicArea_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service area</Term>
      <Definition>A specific geographic area that is covered by one or more
		service engineers (employees). A service area can be linked to a service
		center.</Definition>
      <Keyword type="glentry" order="d1e2773504">
         <Level1>service area</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000027" Version="B60adoc1" ContextApps="ts">
      <Term>service BOM</Term>
      <Definition>A bill of material with the information about the components of
		the service (parent) item. The service BOM structure can be compared to a
		production BOM structure. The so-called parent-child relations make the service
		BOM structure. The service BOM usually lists the items on which service
		activities can be carried out.</Definition>
      <Keyword type="glentry" order="d1e2771272">
         <Level1>service BOM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicCar_ts" Version="B60asy04" ContextApps="ts">
      <Term>service car</Term>
      <Definition>Means of transport, linked to a service employee, for
		transportation from and to the customers work site.</Definition>
      <Keyword type="glentry" order="d1e2773509">
         <Level1>service car</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicContra_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service contract</Term>
      <Definition>A sales agreement between a service organization and a customer
		for a specific period, that states the configurations (Installation
		groups or serialized items) to be maintained, the
		coverage terms, and the agreed price.</Definition>
      <Keyword type="glentry" order="d1e2773519">
         <Level1>service contract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000380" Version="B60asy04" ContextApps="ts">
      <Term>service contract change</Term>
      <Definition>Following are the types of contract changes:</Definition>
      <SimpleSection>
         <List>
            <ListItem>
               <GUIRef href="" role="manual">Renewal</GUIRef>: The option allows you to extend the
			 contract period beyond its current validity duration.</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Incidental Changes</GUIRef>: The option allows you to
			 implement changes to an existing contract. Changes such as addition/deletion of
			 one or more configuration lines, changes to price and discounts, and so on are
			 categorized as incidental changes.</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Indexation</GUIRef>: The option allows you to change
			 the contract price based on the changes in the value of consumer price
			 index.</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Renewal with Indexation</GUIRef>: The option allows
			 you to perform indexation and renewal at the same time.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772554">
         <Level1>service contract change</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000141" Version="B60adoc1" ContextApps="ts">
      <Term>service-contract documents</Term>
      <Definition>The documents that are printed in the <GUIRef href="/baanerp/ts/ctm/tsctm3400m000" role="session">Print Service Contract Documents (tsctm3400m000)</GUIRef> session.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Two types can be printed:</ListIntro>
            <ListItem>External documents</ListItem>
            <ListItem>Internal documents</ListItem>
         </List>
      </SimpleSection>
      <SimpleSection>
         <SectionTitle>External document</SectionTitle>
         <Paragraph>This type of document is used to print the actual documents
		  that must be sent to the business partner.</Paragraph>
      </SimpleSection>
      <SimpleSection>
         <SectionTitle>Internal document</SectionTitle>
         <Paragraph>This type of document is used to print a copy for internal
		  use of the actual document that must be sent to the business partner.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>The contract can receive separate financial approval before
			 printing the final documents.</ListItem>
            <ListItem>The contract details can still be amended after review.</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2772080">
         <Level1>service-contract documents</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000139" Version="B60adoc0" ContextApps="ts">
      <Term>service contract header</Term>
      <Definition>The service contract header contains all the data that is
		entered in the <GUIRef href="/baanerp/ts/ctm/tsctm3100m000" role="session">Service Contracts (tsctm3100m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2772038">
         <Level1>service contract header</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000406" Version="B60adoc1" ContextApps="ts">
      <Term>service department</Term>
      <Definition>The department that is responsible for the execution of a work
		order.</Definition>
      <Keyword type="glentry" order="d1e2772755">
         <Level1>service department</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicCenter_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service department</Term>
      <Definition>A department that consists of one or more persons and/or
		machines with identical capabilities, that can be considered as one unit for
		the purposes of service and maintenance planning.</Definition>
      <Keyword type="glentry" order="d1e2773514">
         <Level1>service department</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicEmploy_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service employee</Term>
      <Definition>Person(s) working for the service department.</Definition>
      <Keyword type="glentry" order="d1e2773524">
         <Level1>service employee</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicEngine_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service engineer</Term>
      <Definition>A trained technician who carries out the service activities
		within his/her own organization or on the customer's site.</Definition>
      <Keyword type="glentry" order="d1e2773529">
         <Level1>service engineer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000014" Version="B60adoc1" ContextApps="ts">
      <Term>service item</Term>
      <Definition>A product that serves as a repository when you define
		serialized items, maintenance concepts, and service contract terms.</Definition>
      <SimpleSection>
         <Paragraph>In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, the items are specified by the item code. Item
		  codes enable you to the use the ERP Enterprise functionality for purchase and inventory
		  control. For service and maintenance applications, you must separately identify
		  the various states in which items can occur in the process. For example, you
		  must be able to identify defect items and repaired items.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771201">
         <Level1>service item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicItemDa_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service-item data</Term>
      <Definition>Information about the service item.</Definition>
      <Keyword type="glentry" order="d1e2773534">
         <Level1>service-item data</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicItemGr_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service item group</Term>
      <Definition>Groups of service items with common characteristics that are
		used in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>.</Definition>
      <SimpleSection>
         <Paragraph>Service item groups can be used to define the material terms
		  for a group of items. The material terms are used in service-contract
		  templates, service-contract quotations, service contracts, service-order
		  quotations, and warranties.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773539">
         <Level1>service item group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicKit_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service kit</Term>
      <Definition>A mobile warehouse in which components used during service
		activities are stored.</Definition>
      <Keyword type="glentry" order="d1e2773550">
         <Level1>service kit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000015" Version="B60asy04" ContextApps="ts">
      <Term>service kit type parts</Term>
      <Definition>The components that are used during the maintenance of an item.</Definition>
      <Keyword type="glentry" order="d1e2771212">
         <Level1>service kit type parts</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicKitGro_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service-kit types</Term>
      <Definition>A classification of similar <Link href="/baanerp/ts/glossary/glossary#ServicKit_ts" role="glossary">service kits</Link> into groups that can be used to carry out service/maintenance
		activities on a maintenance item.</Definition>
      <SimpleSection>
         <Paragraph>In defining a set of available items for a service kit type,
		  it is assumed that all service kits belonging to that service kit type, also
		  contain the same set of items.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The Washing machines service kit type contains all service
		  kits that are required to maintain the washing machines of a certain type.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773555">
         <Level1>service-kit types</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000401" Version="B60adoc1" ContextApps="ts">
      <Term>service office</Term>
      <Definition>A department clearly identified within the company business
		model to manage the sales relations of the business partner. The service office
		is used to identify the locations that are responsible for the service
		activities within the organization.</Definition>
      <Keyword type="glentry" order="d1e2772730">
         <Level1>service office</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicOrder_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service order</Term>
      <Definition>Orders that are used to plan, carry out, and control all repair
		and maintenance on configurations as present on customer sites or as present
		with the company.</Definition>
      <Keyword type="glentry" order="d1e2773572">
         <Level1>service order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000046" Version="B60adoc1" ContextApps="ts">
      <Term>service-order activity line</Term>
      <Definition>The smallest unit of activity that can be carried out for a
		service order. Multiple activities can be defined per service order. This can
		be useful, for example, to combine calls with planned maintenance activities.</Definition>
      <Keyword type="glentry" order="d1e2771369">
         <Level1>service-order activity line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000044" Version="B60adoc1" ContextApps="ts">
      <Term>service order data</Term>
      <Definition>The data defined that is defined in the service-order header,
		service-order activity line, and the requirement line.</Definition>
      <Keyword type="glentry" order="d1e2771356">
         <Level1>service order data</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000102" Version="B60asy04" ContextApps="ts">
      <Term>service order document</Term>
      <Definition>Used within a service organization, a document that can contain
		service order sheets, inspection reports, or checklists. Used to inform
		customers, a document that can contain announcement sheets, appointment sheets,
		or repair reports.</Definition>
      <Keyword type="glentry" order="d1e2771818">
         <Level1>service order document</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000045" Version="B60adoc1" ContextApps="ts">
      <Term>service order header</Term>
      <Definition>The service order header contains all the data that is entered
		in the <GUIRef href="/baanerp/ts/soc/tssoc2100m000" role="session">Service Orders (tssoc2100m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2771361">
         <Level1>service order header</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServOrderHis_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service-order history</Term>
      <Definition>Detailed information about the service orders that are posted
		to history.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The historical service order data comprises the data that
			 is defined in the:</ListIntro>
            <ListItem>Service-order header</ListItem>
            <ListItem>Service-order activity line</ListItem>
            <ListItem>Requirement lines</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773468">
         <Level1>service-order history</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000103" Version="B60asy04" ContextApps="ts">
      <Term>service-order labor costs</Term>
      <Definition>The costs of the labor that is required to carry out the
		service order.</Definition>
      <Keyword type="glentry" order="d1e2771823">
         <Level1>service-order labor costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServOrderMat_ts" Version="B60asy04" ContextApps="ts">
      <Term>service-order material costs</Term>
      <Definition>The costs of the materials that are required to carry out the
		service order.</Definition>
      <Keyword type="glentry" order="d1e2773483">
         <Level1>service-order material costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServOrderOth_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service-order other costs</Term>
      <Definition>The costs required to carry out a service order, that cannot be
		classed as material costs or labor costs.</Definition>
      <Keyword type="glentry" order="d1e2773488">
         <Level1>service-order other costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServOrderQuo_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service-order quotation</Term>
      <Definition>A service-order quotation is a statement of price, terms of
		sale, and description of services and materials, that can be sent to a
		prospective business partner. The business partner data, payment terms and
		delivery terms are listed in the header. The data about the activities and
		materials are entered on the quotation lines.</Definition>
      <Keyword type="glentry" order="d1e2773493">
         <Level1>service-order quotation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000041" Version="B60adoc1" ContextApps="ts">
      <Term>service order sheet</Term>
      <Definition>A sheet that informs the service engineer about the work that
		must be carried out.</Definition>
      <Keyword type="glentry" order="d1e2771341">
         <Level1>service order sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicOrgani_ts" Version="B60asy04" ContextApps="ts">
      <Term>service organization</Term>
      <Definition>A part of a company or an independently operating company to
		maintain production means and/or installations.</Definition>
      <Keyword type="glentry" order="d1e2773577">
         <Level1>service organization</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicPrice_ts" Version="B60asy04" ContextApps="ts">
      <Term>service price</Term>
      <Definition>The price of service activities or maintenance activities
		carried out at regular intervals as part of periodic maintenance of an
		installation.</Definition>
      <Keyword type="glentry" order="d1e2773582">
         <Level1>service price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServiceResolutionHistory_ts">
      <Term>Service Resolution History</Term>
      <Definition>The history of all service orders and solved calls. This data
		includes the details equipment, problems, and solutions for a service order
		activity or a call.</Definition>
      <Keyword type="glentry" order="d1e2773701">
         <Level1>Service Resolution History</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ServicType_ts" Version="B60adoc1" ContextApps="ts">
      <Term>service type</Term>
      <Definition>The service classification that service providers offer. The
		service type determines which availability type applies to a service order
		header, and provides a default order procedure and coverage type.</Definition>
      <Keyword type="glentry" order="d1e2773587">
         <Level1>service type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000361" Version="B60asy04" ContextApps="ts">
      <Term>shop maintenance</Term>
      <Definition>Maintenance that takes place in a maintenance department.</Definition>
      <Keyword type="glentry" order="d1e2772440">
         <Level1>shop maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000363" Version="B60asy04" ContextApps="ts">
      <Term>single-level breakdown</Term>
      <Definition>A display of components that are directly used in a parent
		item. A single-level breakdown shows only the relationship one level down.</Definition>
      <Keyword type="glentry" order="d1e2772450">
         <Level1>single-level breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Skills_ts" Version="B60adoc1" ContextApps="ts">
      <Term>skill</Term>
      <Definition>The specific knowledge or technical expertise that a service
		engineer must have to carry out service or maintenance activities. For example,
		knowledge of electricity, specific equipment, and so on. Service skills can be
		used as constraints when planning orders.</Definition>
      <Keyword type="glentry" order="d1e2773592">
         <Level1>skill</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000013" Version="B60asy04" ContextApps="ts">
      <Term>skill factor</Term>
      <Definition>An indication of the productivity of the service engineer, for
		information purposes only.</Definition>
      <Keyword type="glentry" order="d1e2771196">
         <Level1>skill factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000017" Version="B60adoc1" ContextApps="ts">
      <Term>skills by service employee</Term>
      <Definition>The expertise of an individual service engineer. ERP Enterprise uses this data to
		match service orders and service engineers.</Definition>
      <Keyword type="glentry" order="d1e2771225">
         <Level1>skills by service employee</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000101" Version="B60asy04" ContextApps="ts">
      <Term>skill status</Term>
      <Definition>The skill condition indicates if the skill is mandatory or
		required.</Definition>
      <Keyword type="glentry" order="d1e2771813">
         <Level1>skill status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000408" Version="B60adoc1" ContextApps="ts">
      <Term>slack time</Term>
      <Definition>The time between the earliest start time and the planned start
		time of an activity, and between the latest finish time and the planned finish
		time of an activity. Slack time is deliberately introduced by the planner to
		reduce the risk that a delay in a single activity is passed on to subsequent
		activities and, as a result, disturbs the overall planning.</Definition>
      <Keyword type="glentry" order="d1e2772765">
         <Level1>slack time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Solutions_ts" Version="B60adoc1" ContextApps="ts">
      <Term>solution</Term>
      <Definition>Codes on calls and service orders that enable you to analyze
		the orders.</Definition>
      <Keyword type="glentry" order="d1e2773602">
         <Level1>solution</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000423" Version="B60adoc1" ContextApps="ts">
      <Term>solution finish time</Term>
      <Definition>The time by which the support engineer must finish solving the
		call.</Definition>
      <Keyword type="glentry" order="d1e2772892">
         <Level1>solution finish time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000422" Version="B60adoc1" ContextApps="ts">
      <Term>solution start time</Term>
      <Definition>The time by which the support engineer must start solving the
		call.</Definition>
      <Keyword type="glentry" order="d1e2772887">
         <Level1>solution start time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SolutiTime_ts" Version="B60adoc1" ContextApps="ts">
      <Term>solution time</Term>
      <Definition>The agreed maximum time that can elapse between the
		registration of a call and the time the problem must be solved.</Definition>
      <Keyword type="glentry" order="d1e2773597">
         <Level1>solution time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000364" Version="B60asy04" ContextApps="ts">
      <Term>spatial breakdown</Term>
      <Definition>A list of components grouped by location or zone. A spatial
		breakdown consists of spatial elements and serialized items.</Definition>
      <Keyword type="glentry" order="d1e2772455">
         <Level1>spatial breakdown</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000365" Version="B60asy04" ContextApps="ts">
      <Term>spatial element</Term>
      <Definition>A component of a spatial breakdown.</Definition>
      <Keyword type="glentry" order="d1e2772460">
         <Level1>spatial element</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000367" Version="B60asy04" ContextApps="ts">
      <Term>spatial resource</Term>
      <Definition>Available space in terms of height, floor area, and so on that
		can serve as a constraint for the acceptance and execution of maintenance
		activities.</Definition>
      <Keyword type="glentry" order="d1e2772471">
         <Level1>spatial resource</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000372" Version="B60asy04" ContextApps="ts">
      <Term>spatial resource type</Term>
      <Definition>A classification that is used to group spatial resources.</Definition>
      <SimpleSection>
         <Paragraph>For example: Spatial resource type Operations; All the rooms
		  in which testing activities take place.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2772501">
         <Level1>spatial resource type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000128" Version="B60asy04" ContextApps="ts">
      <Term>spent calls</Term>
      <Definition>The number of calls spent on service requests that have been
		financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771957">
         <Level1>spent calls</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000131" Version="B60asy04" ContextApps="ts">
      <Term>spent call units</Term>
      <Definition>The number of calls that are spent on support activities that
		have been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771979">
         <Level1>spent call units</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000073" Version="B60adoc1" ContextApps="ts">
      <Term>spent costs</Term>
      <Definition>The sum of costs due to service activities that have been
		financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home currency.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Service orders</ListItem>
            <ListItem>Traveling costs</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771555">
         <Level1>spent costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000091" Version="B60asy04" ContextApps="ts">
      <Term>spent discount</Term>
      <Definition>The sum of discounts arising from service activities that have
		been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home
		currency.</Definition>
      <Keyword type="glentry" order="d1e2771752">
         <Level1>spent discount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000121" Version="B60asy04" ContextApps="ts">
      <Term>spent distance</Term>
      <Definition>The current total of the distance covered due to service
		activities that has been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771910">
         <Level1>spent distance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000122" Version="B60asy04" ContextApps="ts">
      <Term>spent quantity</Term>
      <Definition>The current total of the quantity of material used due to
		service activities that has been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771918">
         <Level1>spent quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000074" Version="B60adoc1" ContextApps="ts">
      <Term>spent sales</Term>
      <Definition>The sum of sales amounts due to service activities that have
		been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the
		currency chosen in the contract header.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Service orders</ListItem>
            <ListItem>Helpdesk calls</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2771571">
         <Level1>spent sales</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000105" Version="B60adoc1" ContextApps="ts">
      <Term>spent time</Term>
      <Definition>The time spent on service activities that have been financially
		approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771834">
         <Level1>spent time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000123" Version="B60asy04" ContextApps="ts">
      <Term>spent visits</Term>
      <Definition>The current number of visits made on service activities that
		have been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2771926">
         <Level1>spent visits</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000097" Version="B60asy04" ContextApps="ts">
      <Term>start date</Term>
      <Definition>The date on which the terms become valid. It is displayed when
		the contract status changes from Free to Active.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListIntro/>
            <ListItem>If more than one phase exists for this term, the start date
			 of the first phase is displayed.</ListItem>
            <ListItem>If a warranty is linked to one of the items or configurations
			 in the contract, the date is on or after the date of installation.</ListItem>
         </List>
      </Note>
      <Keyword type="glentry" order="d1e2771780">
         <Level1>start date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Statistics_ts">
      <Term>Statistics</Term>
      <Definition>The number of times a particular combination of</Definition>
      <SimpleSection>
         <List>
            <ListItem>Serialized Item Group</ListItem>
            <ListItem>Item</ListItem>
            <ListItem>Service Item Group</ListItem>
            <ListItem>Call Group1</ListItem>
            <ListItem>Call Group2</ListItem>
            <ListItem>Reported Problem</ListItem>
            <ListItem>Expected Problem</ListItem>
            <ListItem>Actual Problem</ListItem>
            <ListItem>Expected Solution</ListItem>
            <ListItem>Actual Solution</ListItem>
            <ListItem>Reference Activity</ListItem>
         </List>
         <Paragraph>was used to solve a problem. A valid combination is formed
		  depending on the fields that are selected in <GUIRef href="" role="manual">Call Parameters (tsclm0100m000)</GUIRef> session. The statistics is built from the completed
		  service order activities and the solved calls.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2773706">
         <Level1>Statistics</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000368" Version="B60asy04" ContextApps="ts">
      <Term>subassembly</Term>
      <Definition>Assemblies that are part of other assemblies.</Definition>
      <Keyword type="glentry" order="d1e2772476">
         <Level1>subassembly</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Subcontract_ts" Version="B60adoc1" ContextApps="ts">
      <Term>subcontract</Term>
      <Definition>Arrange for part or all of the work to be carried out by a
		third party.</Definition>
      <Keyword type="glentry" order="d1e2773607">
         <Level1>subcontract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000398" Version="B60adoc1" ContextApps="ts">
      <Term>subcontract agreement</Term>
      <Definition>The agreement between the service organization and the
		subcontractor.</Definition>
      <Keyword type="glentry" order="d1e2772711">
         <Level1>subcontract agreement</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000399" Version="B60adoc1" ContextApps="ts">
      <Term>subcontractor</Term>
      <Definition>A third-party service provider. The subcontractor is referred
		to as buy-from business partner, because he is considered to be a business
		partner from whom services are bought.</Definition>
      <Keyword type="glentry" order="d1e2772716">
         <Level1>subcontractor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SuccesPercen_ts" Version="B60asy04" ContextApps="ts">
      <Term>success percentage</Term>
      <Definition>An indication of the chance that a quotation is accepted.</Definition>
      <Keyword type="glentry" order="d1e2773612">
         <Level1>success percentage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SupporEngine_ts" Version="B60asy04" ContextApps="ts">
      <Term>support engineer</Term>
      <Definition>A trained technician responsible for executing helpdesk
		activities.</Definition>
      <Keyword type="glentry" order="d1e2773617">
         <Level1>support engineer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000055" Version="B60adoc1" ContextApps="ts">
      <Term>surcharge/discount</Term>
      <Definition>A <Emphasis>surcharge</Emphasis> can be made, if, for example,
		a special response time is requested. A <Emphasis>discount</Emphasis> can be
		given, if, for example, a quantity of a given item is requested as opposed to a
		single item.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>If a surcharge is applied to an item or order, it is added to
			 the original costs.</ListItem>
            <ListItem>If a discount is applied to an item or order, the original
			 costs are lowered.</ListItem>
         </List>
      </Note>
      <Keyword type="glentry" order="d1e2771418">
         <Level1>surcharge/discount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Task_ts" Version="B60adoc1" ContextApps="ts">
      <Term>task</Term>
      <Definition>A specification of the type of work that is carried out by a
		service employee. You can use tasks to specify the labor required to carry out
		an activity. A specific labor rate can be linked to a task.</Definition>
      <Keyword type="glentry" order="d1e2773622">
         <Level1>task</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000436" Version="B60adoc1" ContextApps="ts">
      <Term>tax country</Term>
      <Definition>The country in which you must pay/report the value-added tax
		(VAT). The tax country can be different from the country where services or
		goods are delivered.</Definition>
      <Keyword type="glentry" order="d1e2772969">
         <Level1>tax country</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000002" Version="B60asy04" ContextApps="ts">
      <Term>tax indicator</Term>
      <Definition>The type of tax processing that is applied to the selected
		contract type, since service, rental, and sales can each be taxed differently.</Definition>
      <Keyword type="glentry" order="d1e2771145">
         <Level1>tax indicator</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Terms_ts" Version="B60adoc1" ContextApps="ts">
      <Term>terms</Term>
      <Definition>A set of contract, quotation or warranty conditions, related to
		a type of maintenance.</Definition>
      <SimpleSection>
         <Paragraph>Per coverage type and term type, conditions and price
		  agreements are stored in the coverage terms, which can be further specified in
		  the cost terms.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>All conditions related to:</ListIntro>
            <ListItem>Long cyclic maintenance</ListItem>
            <ListItem>Helpdesk support</ListItem>
            <ListItem>Field problem solving</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773628">
         <Level1>terms</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000070" Version="B60adoc1" ContextApps="ts">
      <Term>term type</Term>
      <Definition>Categories used to group costs. Term types enable you to have a
		more detailed view of the source of costs.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The <GUIRef href="/baanerp/ts/ctm" role="module">Contract Management</GUIRef> module in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef> distinguishes the following term types:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#material" role="option">Material</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#labor" role="option">Labor</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#tool" role="option">Tooling</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#travel" role="option">Traveling</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#subcon" role="option">Subcontracting</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#helpdesk" role="option">Help Desk</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#other" role="option">Other</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#uptime" role="option">Uptime</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/ts/domains/mdm.cotp#all" role="option">All</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771483">
         <Level1>term type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000454">
      <Term>territory</Term>
      <Definition>An area by which objects are grouped.</Definition>
      <Keyword type="glentry" order="d1e2773869">
         <Level1>territory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000459">
      <Term>territory</Term>
      <Definition>An area by which objects are grouped</Definition>
      <Keyword type="glentry" order="d1e2773895">
         <Level1>territory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000094" Version="B60adoc0" ContextApps="ts">
      <Term>tolerance period</Term>
      <Definition>The tolerance period can be used to increase the planning
		period of a reference activity when it is planned.</Definition>
      <Keyword type="glentry" order="d1e2771765">
         <Level1>tolerance period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000038" Version="B60adoc1" ContextApps="ts">
      <Term>tool maintenance</Term>
      <Definition>The maintenance activities that are carried out on tooling.</Definition>
      <Keyword type="glentry" order="d1e2771331">
         <Level1>tool maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000428" Version="B60adoc1" ContextApps="ts">
      <Term>top work order</Term>
      <Definition>The very first work order from which the initiating work order
		of the current work order was derived.</Definition>
      <Keyword type="glentry" order="d1e2772917">
         <Level1>top work order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000068" Version="B60adoc1" ContextApps="ts">
      <Term>total amount</Term>
      <Definition>The sum of the sales amounts of all coverage terms that are
		associated with the indicated service type or term type.</Definition>
      <Keyword type="glentry" order="d1e2771468">
         <Level1>total amount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000069" Version="B60adoc1" ContextApps="ts">
      <Term>total costs</Term>
      <Definition>The sum of the cost amounts of all coverage terms that are
		associated with the indicated service type or term type.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>The amount is expressed in the home currency.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2771473">
         <Level1>total costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000126" Version="B60asy04" ContextApps="ts">
      <Term>total distance</Term>
      <Definition>The return distance to the site where the configuration is
		situated, multiplied by the number of visits required.</Definition>
      <Keyword type="glentry" order="d1e2771947">
         <Level1>total distance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000107" Version="B60asy04" ContextApps="ts">
      <Term>traveling specification type</Term>
      <Definition>Indicates whether the traveling cost lines are specified in
		distance, time, total or call-out charge.</Definition>
      <Keyword type="glentry" order="d1e2771850">
         <Level1>traveling specification type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000453">
      <Term>trend</Term>
      <Definition>The information that is necessary to calculate the trend of
		numeric measurements.</Definition>
      <Keyword type="glentry" order="d1e2773864">
         <Level1>trend</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000369" Version="B60asy04" ContextApps="ts">
      <Term>unserviceable item</Term>
      <Definition>An item that must be inspected before it can be used.</Definition>
      <Keyword type="glentry" order="d1e2772481">
         <Level1>unserviceable item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="UsageClass_ts" Version="B60adoc1" ContextApps="ts">
      <Term>usage class</Term>
      <Definition>Usage classes categorize the use of an
Installation
		group, configuration, or (serialized) item, based on
		environmental factors or frequency of use.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>You can use usage classes to:</ListIntro>
            <ListItem>Predict the maintenance required for a Installation
			 group, configuration, or (serialized) item, based on
			 its usage.</ListItem>
            <ListItem>Define more than one maintenance concept to
			 configure the Installation group, and generate a
			 maintenance plan based on the concept.</ListItem>
         </List>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>The usage class of a truck can be national or
			 international. The required maintenance for national use is different than that
			 for international use, for example:</ListIntro>
            <ListItem>Difference in number of kilometers</ListItem>
            <ListItem>Difference in climate</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2773648">
         <Level1>usage class</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="UseBasedMain_ts" Version="B60adoc1" ContextApps="ts">
      <Term>use-based maintenance</Term>
      <Definition>Preventive maintenance that takes place after a certain period
		of use, independent of the condition of the item at that moment. Acronym:
		UBM</Definition>
      <Keyword type="glentry" order="d1e2773671">
         <Level1>use-based maintenance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000019" Version="B60asy04" ContextApps="ts">
      <Term>user defaults (service)</Term>
      <Definition>The default data recorded by the user, which substantially
		affects the creation of service order and contract quotations, service orders,
		contracts including quotations, and order lines. The user defaults determine
		the method of order entry, the default values during order input, the degree of
		acceptance after order entry, and so on.</Definition>
      <Keyword type="glentry" order="d1e2771238">
         <Level1>user defaults (service)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000034" Version="B60adoc1" ContextApps="ts">
      <Term>use trend</Term>
      <Definition>A qualification of an item's usage based on the trend of the
		dependent measurement unit (dependent variable) in relation to the value of the
		independent measurement unit (independent variable). The use trend enables you
		to generate a maintenance prediction.</Definition>
      <Keyword type="glentry" order="d1e2771302">
         <Level1>use trend</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Warranty_ts" Version="B60adoc1" ContextApps="ts">
      <Term>warranty</Term>
      <Definition>A guarantee that a component is repaired free of charge or at
		reduced costs if it does not work according to the agreed specifications within
		a warranty period.</Definition>
      <Keyword type="glentry" order="d1e2773691">
         <Level1>warranty</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="WarranDurati_ts" Version="B60asy04" ContextApps="ts">
      <Term>warranty duration</Term>
      <Definition>Warranty period. The period that the warranty is valid,
		expressed in time units.</Definition>
      <Keyword type="glentry" order="d1e2773676">
         <Level1>warranty duration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="WarranLimit_ts" Version="B60asy04" ContextApps="ts">
      <Term>warranty limit</Term>
      <Definition>Warranty terms can be restricted by relating them to a specific
		norm value of a certain measuring quantity that is an indication of the use of
		the item (for example, 80% warranty on the first 5,000 kilometers of a private
		car).</Definition>
      <Keyword type="glentry" order="d1e2773681">
         <Level1>warranty limit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="WarranTerms_ts" Version="B60asy04" ContextApps="ts">
      <Term>warranty terms</Term>
      <Definition>The warranty specifications for an item when the item is sold
		to the customer. They can include a period or a number of operating hours that
		the warranty is valid, or the response times on a service call.</Definition>
      <Keyword type="glentry" order="d1e2773686">
         <Level1>warranty terms</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000407" Version="B60adoc1" ContextApps="ts">
      <Term>work center</Term>
      <Definition>The subdepartment of the service department that is responsible
		for the execution of a work order.</Definition>
      <Keyword type="glentry" order="d1e2772760">
         <Level1>work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000135" Version="B60adoc1" ContextApps="ts">
      <Term>work in process</Term>
      <Definition>In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>,
		the amount of work to do is indicated per service center by means of: The
		number of calls with the <GUIRef href="/baanerp/ts/domains/clm.stat#assign" role="option">Assigned</GUIRef> status; The
		service orders with the <GUIRef href="/baanerp/ts/domains/soc.osta#planned" role="option">Planned</GUIRef> status and <GUIRef href="/baanerp/ts/domains/soc.osta#released" role="option">Released</GUIRef> status. Acronym:
		WIP</Definition>
      <Keyword type="glentry" order="d1e2772005">
         <Level1>work in process</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000456">
      <Term>workload</Term>
      <Definition>The total workload of the planned activities, service order and
		unexpected workload.</Definition>
      <Keyword type="glentry" order="d1e2773879">
         <Level1>workload</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000385" Version="B60adoc1" ContextApps="ts">
      <Term>work order</Term>
      <Definition>Orders that are used to plan, carry out, and control all
		maintenance on items in a maintenance shop or in a repair shop. A work order
		consists of at least one work order header, and can have a number of activities
		that must be carried out on a repairable service item.</Definition>
      <Keyword type="glentry" order="d1e2772597">
         <Level1>work order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000412" Version="B60adoc1" ContextApps="ts">
      <Term>work order document</Term>
      <Definition>A document that can contain the activities, checklists,
		measurements, material, tools, subcontracting, and other costs.</Definition>
      <Keyword type="glentry" order="d1e2772786">
         <Level1>work order document</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000016" Version="B60adoc1" ContextApps="ts">
      <Term>zone class</Term>
      <Definition>A set of configurations of a customer around the home base of a
		service organization.</Definition>
      <SimpleSection>
         <Paragraph>Within a zone class, a sales rate (also called call-out
		  charge) can be defined for traveling costs, effective from a specific date. A
		  zone class is specified with an upper distance limit and can be assigned to
		  each configuration.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2771217">
         <Level1>zone class</Level1>
      </Keyword>
   </GlossaryEntry>
</Glossary>