<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/ti/glossary/glossary" xml:lang="en">
   <Header>
      <Title>Glossary for Manufacturing</Title>
   </Header>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ActiviManage_ti">
      <Term>activity manager</Term>
      <Definition>A person responsible for planning or carrying out a project
		activity.</Definition>
      <Keyword type="glentry" order="d1e2027255">
         <Level1>activity manager</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000361">
      <Term>actual completion date</Term>
      <Definition>The date on which the items of a production order are
		(partially) completed or rejected for each operation in the <Link href="/baanerp/ti/onlinemanual/tisfc" role="manual">Shop Floor Control (SFC)</Link> module. The user can overwrite the date.</Definition>
      <Keyword type="glentry" order="d1e2027260">
         <Level1>actual completion date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000328">
      <Term>actual input</Term>
      <Definition>The total input quantity of a work center/machine for
		operations that are <GUIRef href="/baanerp/ti/domains/sfc.opst#ready.to.start" role="option">Ready to Start</GUIRef> during the target period.</Definition>
      <Keyword type="glentry" order="d1e2027268">
         <Level1>actual input</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000329">
      <Term>actual output</Term>
      <Definition>The total output quantity that is reported complete, for
		operations at a work center/machine during the target period.</Definition>
      <Keyword type="glentry" order="d1e2027276">
         <Level1>actual output</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000330">
      <Term>actual queue</Term>
      <Definition>The actual input minus the actual output of a work
		center/machine. Note that the queue includes active operations as well as
		operations waiting to be carried out.</Definition>
      <Keyword type="glentry" order="d1e2027281">
         <Level1>actual queue</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000319">
      <Term>added costs</Term>
      <Definition>The increase in value of an item when the item passes through a
		stage in the production process. Added costs are posted to detailed cost
		components whereas non-added costs are posted to aggregated cost components.</Definition>
      <SimpleSection>
         <List>
            <ListItem>For purchased items, added costs are costs of materials plus
			 surcharges.</ListItem>
            <ListItem>For items transferred between warehouses, added costs are
			 the warehouse surcharges.</ListItem>
            <ListItem>For manufactured items, added costs are operation costs plus
			 surcharges.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027286">
         <Level1>added costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Aggregate_ti">
      <Term>aggregate</Term>
      <Definition>To total figures or amalgamate amounts; to merge items in a
		higher plan level. Opposite of explode, disaggregate.</Definition>
      <Keyword type="glentry" order="d1e2027299">
         <Level1>aggregate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000343">
      <Term>aggregated cost component</Term>
      <Definition>A cost component that contains aggregated costs.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Each item has cost components which have been added together
			 for the following costs:</ListIntro>
            <ListItem>Materials costs (contains raw materials costs)</ListItem>
            <ListItem>Operations costs (contains operations costs and
			 subcontracting costs)</ListItem>
            <ListItem>Surcharges (contains item surcharges and warehouse
			 surcharges)</ListItem>
         </List>
         <Paragraph>In inventory, value of goods is calculated and posted by the
		  three aggregated cost components. However, operation costs, production
		  variances, and production surcharges are calculated and posted by detailed cost
		  component.</Paragraph>
      </SimpleSection>
      <Antonym>detailed cost component</Antonym>
      <Keyword type="glentry" order="d1e2027304">
         <Level1>aggregated cost component</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2027304">
         <Level1>detailed cost component</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2027983">
      <Term>aggregated cost component</Term>
      <Definition>See: <Link href="#000344" role="internal">detailed cost component</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="PlanniBillOf_ti">
      <Term>aggregation relationships</Term>
      <Definition>A specification, expressed as a percentage, how items are
		aggregated or disaggregated.</Definition>
      <SimpleSection>
         <Paragraph>To aggregate items means that different items are grouped to
		  form product families for planning purposes. This is also called a planning
		  bill of material. To disaggregate items means that a product family is split up
		  into smaller families, or into items.</Paragraph>
         <Paragraph>Aggregation relationships can have the same structure as a
		  single-level bill of material. However, similar to production bills of
		  materials, also multilevel structures can be created.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="387" height="233"
                      SRC="../images/tr_graph_tiglossary_02.gif"
                      alt="[...]"/>
         </Figure>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2027323">
         <Level1>aggregation relationships</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="Allocation_ti">
      <Term>allocation</Term>
      <Definition>An item quantity that is assigned to a specific order but that
		is not yet released from the warehouse to production.</Definition>
      <Keyword type="glentry" order="d1e2027338">
         <Level1>allocation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000376">
      <Term>alternative material</Term>
      <Definition>A substitute for a BOM material that the system can select in
		case the standard material is out of stock.</Definition>
      <SimpleSection>
         <Paragraph>An alternative material is supposed to meet the same
		  specifications, but only in the context of a BOM for a specific main item.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/tc/glossary/glossary#AlternItems_tc" role="glossary">alternative items</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2027344">
         <Level1>alternative material</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000046">
      <Term>alternative tool type</Term>
      <Definition>A substitute for a tool type that is not available for use, for
		example, when a tool is being refurbished.</Definition>
      <Keyword type="glentry" order="d1e2027355">
         <Level1>alternative tool type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000015">
      <Term>anonymous item</Term>
      <Definition>An item with an <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef> order policy. This means that the item is
		produced or purchased before a customer order is received. If an anonymous item
		is a manufactured item, it is produced in a make-to-stock production
		environment.</Definition>
      <SimpleSection>
         <Paragraph>A generic item is typical for a to-order environment. The
		  order policy can be <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> but also <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef>. In case a generic item is anonymous, a product
		  variant is configured without using a PCS project.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027360">
         <Level1>anonymous item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Answer_ti">
      <Term>answer</Term>
      <Definition>The response in a question-and-answer type of user/system
		interaction (in the <GUIRef href="/baanerp/ti/grt" role="module">Product Classification</GUIRef> (GRT) module).</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The response can be of three types:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/ti/domains/grt.antp#number" role="option">Numeric</GUIRef>
            </ListItemHead>
            <ListItem>For example, 5</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/ti/domains/grt.antp#alpha" role="option">Alphanumeric</GUIRef>
            </ListItemHead>
            <ListItem>For example, RED</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/ti/domains/grt.antp#dependent" role="option">Answer &amp; Follow-up</GUIRef>
            </ListItemHead>
            <ListItem>Based on an answer a new question is raised.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027377">
         <Level1>answer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="AnswerGroup_ti">
      <Term>answer group</Term>
      <Definition>A set of predefined answers from which an user can select an
		value in the classification process.</Definition>
      <Keyword type="glentry" order="d1e2027404">
         <Level1>answer group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000069">
      <Term>antedating</Term>
      <Definition>To enter a date in the past when recording the issue of
		materials or deliveries of end products into inventory.</Definition>
      <SimpleSection>
         <Paragraph>This is useful if the user is updating the system some time
		  after the actual manufacturing process took place.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027409">
         <Level1>antedating</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000091">
      <Term>aspect</Term>
      <Definition>An aspect is a specification of a feature.</Definition>
      <Keyword type="glentry" order="d1e2027417">
         <Level1>aspect</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000338">
      <Term>assembly assignment</Term>
      <Definition>The set of resources assigned to an assembly line for a
		particular period of the day. The resources are divided over the line stations
		to create a balanced line.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Assignments are defined for an assembly line. For each
			 assignment, you specify the cycle time and its activity ranges, which are the
			 period and time ranges for which the assignment is effective. The process
			 characteristics that you define for an assignment include:</ListIntro>
            <ListItem>Man occupation</ListItem>
            <ListItem>Machine occupation</ListItem>
            <ListItem>Work team</ListItem>
            <ListItem>Operations</ListItem>
         </List>
         <Paragraph>These process characteristics are linked to other assignments
		  that are, in turn, linked to the assembly assignment. When an assignment is in
		  effect, the assignments that are linked to it are also in effect.</Paragraph>
      </SimpleSection>
      <SimpleSection>
         <SectionTitle>assignment types</SectionTitle>
      </SimpleSection>
      <SimpleSection>
         <Paragraph>Two types of assignments exist, both of which exist at the
		  same time. The average assignment is used for more general purposes, whereas
		  the nonaverage assignment has a very specific period and time range.</Paragraph>
         <List>
            <ListItemHead>Average assignments</ListItemHead>
            <ListItem>Use an average cycle time that is based on the cycle times
			 of the nonaverage assignments for the day. The average assignment is used in
			 planning. Planning is based on cycle time, calendar, and availability type.</ListItem>
            <ListItemHead>Nonaverage assignments</ListItemHead>
            <ListItem>
               <Paragraph>Use time-based cycle times that are based on the
				operations performed on the line. The cycle time can vary according to the time
				range that is provided for the assignment.</Paragraph>
               <Paragraph>Nonaverage assignments are used to define order content.
				For generated (nonfrozen) orders, the order content is based on the first
				active, nonaverage assignment. For frozen orders, the order content is based on
				the nonaverage assignment that is in effect at the time that the order is
				frozen.</Paragraph>
               <Paragraph>Nonaverage assignments are also used to offset the lead
				time during sequencing. When the order is sequenced, a lead time is calculated
				for every order. This lead time is based on the cycle times, and the applicable
				cycle time is retrieved from the nonaverage assignment.</Paragraph>
            </ListItem>
         </List>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>An average cycle time is not a mathematical average, but is a
		  value that you consider to be a suitable average for the nonaverage cycle times
		  over the course of a full day.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2027422">
         <Level1>assembly assignment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000072">
      <Term>assembly item</Term>
      <Definition>An item with default supply source <GUIRef href="/baanerp/tc/domains/srce#assembly" role="option">Assembly</GUIRef>.
		The production of assembly items is controlled by an assembly order. Assembly
		orders are executed on an assembly line.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>An assembly item can have item type <GUIRef href="/baanerp/tc/domains/kitm#generic" role="option">Generic</GUIRef>, <GUIRef href="/baanerp/tc/domains/kitm#manufacture" role="option">Manufactured</GUIRef>, or <GUIRef href="/baanerp/tc/domains/kitm#engineering" role="option">Engineering Module</GUIRef>.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2029969">
         <Level1>assembly item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000000000000055">
      <Term>assembly line</Term>
      <Definition>A set of consecutive line stations in which FAS (Final Assembly
		Schedule) items are manufactured. The items are manufactured by passing the
		items from line station to line station and by carrying out operations at each
		line station. An assembly line is subdivided into a number of line segments
		separated by buffers. An assembly line can be either a main line or a supplying
		line.</Definition>
      <Keyword type="glentry" order="d1e2027467">
         <Level1>assembly line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000001">
      <Term>assembly-material issue note</Term>
      <Definition>An order document used to report the estimated, allocated, and
		issued quantities of required materials for the production of FAS items,
		arranged by line segment.</Definition>
      <Keyword type="glentry" order="d1e2027498">
         <Level1>assembly-material issue note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000073">
      <Term>assembly part</Term>
      <Definition>A component used on an assembly line.</Definition>
      <SimpleSection>
         <Paragraph>An assembly part forms the link between <GUIRef href="/baanerp/cf" role="package">Configurator</GUIRef> and <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>. <GUIRef href="/baanerp/cf" role="package">Configurator</GUIRef> generates the
		  requirements for assembly parts and <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> plans the production or
		  purchase of the item.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027472">
         <Level1>assembly part</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000002">
      <Term>assembly routing sheet</Term>
      <Definition>An order document that lists the assembly operations for the
		production of FAS items, arranged by line segment.</Definition>
      <Keyword type="glentry" order="d1e2027492">
         <Level1>assembly routing sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000320">
      <Term>available capacity</Term>
      <Definition>The total capacity available, for either a day or a week,
		usually based on the work center calendar.</Definition>
      <Keyword type="glentry" order="d1e2027503">
         <Level1>available capacity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000363">
      <Term>average setup time</Term>
      <Definition>The time required for setting up or changing over a machine
		before you start running the machine. Setup time can be long, for example, if
		you change over from using black paint to using white paint. Setup time can be
		short, for example, if you change over from using white paint to using yellow
		paint. The setup time must indicate an average of all possible setup times.</Definition>
      <Keyword type="glentry" order="d1e2027508">
         <Level1>average setup time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Backflushing_ti">
      <Term>backflushing</Term>
      <Definition>The automatic issue of materials from inventory, or accounting
		for the hours spent manufacturing an item, based on theoretical usage and the
		quantity of the item reported as complete.</Definition>
      <Keyword type="glentry" order="d1e2027513">
         <Level1>backflushing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Backlog_ti">
      <Term>backlog</Term>
      <Definition>All the customer's orders that are received but not yet
		shipped. Sometimes they are referred to as open orders on the order board. In
		assembly line production, orders which are behind schedule.</Definition>
      <Keyword type="glentry" order="d1e2027518">
         <Level1>backlog</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="BaseUnit_ti">
      <Term>base unit</Term>
      <Definition>If quantities expressed in alternative units are used in
		calculations or formulas, these quantities are first converted to the base
		unit.</Definition>
      <SimpleSection>
         <Paragraph>For each company, base units must be defined for weight,
		  length, surface area, volume, and time.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027523">
         <Level1>base unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="BasicCapaci_ti">
      <Term>basic capacity</Term>
      <Definition>The normal daily number of operation hours of the resource
		units of a work center (resource). A resource unit can be a machine or an
		employee.</Definition>
      <Keyword type="glentry" order="d1e2027531">
         <Level1>basic capacity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2028589">
      <Term>basic capacity</Term>
      <Definition>See: <Link href="#NormalCapaci_ti" role="internal">normal capacity</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2027567">
      <Term>BCM</Term>
      <Definition>See: <Link href="#000081" role="internal">bill of critical materials</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="BillOfCritic_ti">
      <Term>bill of critical capacities</Term>
      <Definition>Bills of critical capacities (BCC) indicate the work centers
		that are regarded as critical in the Master Planning processes. Critical
		capacities are usually the bottlenecks in a routing.</Definition>
      <SimpleSection>
         <Paragraph> 
            <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the bill of critical capacities to generate the rough
		  capacity requirements for critical capacities.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027536">
         <Level1>bill of critical capacities</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000081">
      <Term>bill of critical materials</Term>
      <Definition>A bill of critical materials (BCM) indicates the components
		which are regarded as critical during the production process of a plan item.</Definition>
      <SimpleSection>
         <Paragraph>A bill of critical materials is a kind of summary of the BOM,
		  which contains only the more important components.</Paragraph>
         <List>
            <ListIntro>Typical examples of critical materials are:</ListIntro>
            <ListItem>Components with long lead times</ListItem>
            <ListItem>Subassemblies with a high capacity load for the internal or
			 external production system</ListItem>
         </List>
         <Paragraph>The <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> package uses the bill of critical materials to generate the
		  critical material requirements for critical materials.</Paragraph>
      </SimpleSection>
      <Synonym>BCM</Synonym>
      <Keyword type="glentry" order="d1e2027547">
         <Level1>bill of critical materials</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2027547">
         <Level1>BCM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="BillOfMateri_ti">
      <Term>bill of material (BOM)</Term>
      <Definition>A list of all parts, raw materials, and subassemblies that go
		into a manufactured item and show the quantity of each of the parts required to
		make the item. The BOM shows the single-level product structure of a
		manufactured item.</Definition>
      <Keyword type="glentry" order="d1e2027569">
         <Level1>bill of material (BOM)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000047">
      <Term>blocking reason</Term>
      <Definition>The reason an operation is temporarily not allowed to proceed.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Reasons for blocking are:</ListIntro>
            <ListItem>The quality must be inspected.</ListItem>
            <ListItem>The equipment has failed.</ListItem>
            <ListItem>The customer did not pay the last installment.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027574">
         <Level1>blocking reason</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="BomLevel_ti">
      <Term>BOM level</Term>
      <Definition>When a product is manufactured, components are assembled into
		subassemblies, and those subassemblies are in turn assembled into the final
		product. The components that go together at each stage are described in a bill
		of material. Each stage is one level in the bill of material.</Definition>
      <SimpleSection>
         <Paragraph>The listing of the wheel components is one level in the bill
		  of material. The listing of the subassemblies of the bicycle is the highest
		  level, and is frequently referred to as level zero.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>A bicycle has one frame and two wheels. The frame is made of
		  three tubes. The wheels are each made of one rim, one hub, and 35 spokes.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2027590">
         <Level1>BOM level</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="BomUnit_ti">
      <Term>BOM quantity</Term>
      <Definition>The number of manufactured items to which a bill of materials
		(BOM) applies. The BOM quantity enables you to specify very small item
		quantities as BOM components.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>You need very small amounts of certain colors to mix one
		  liter of a specific paint, Cotton White. Therefore, a BOM quantity of 1000
		  liter is defined. The component quantities for the paint can then be as
		  follows:</Paragraph>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TD colspan="2" width="208" rowspan="1">Paint Cotton White, 1000 liter:</TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="86" rowspan="1" colspan="1">White</TD>
                  <TD width="118" rowspan="1" colspan="1">999 liter</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="86" rowspan="1" colspan="1">Yellow</TD>
                  <TD width="118" rowspan="1" colspan="1">0.6 liter</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="86" rowspan="1" colspan="1">Red</TD>
                  <TD width="118" rowspan="1" colspan="1">0.2 liter</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD width="86" rowspan="1" colspan="1">Blue</TD>
                  <TD width="118" rowspan="1" colspan="1">0.2 liter</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Synonym>BOM unit</Synonym>
      <Keyword type="glentry" order="d1e2027603">
         <Level1>BOM quantity</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2027603">
         <Level1>BOM unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="SequenNumber_ti">
      <Term>BOM sequence number</Term>
      <Definition>The BOM sequence number allows you to define more than one
		component item for each position. These interchangeable components can have
		different dates when they are valid.</Definition>
      <SimpleSection>
         <Paragraph>LN also uses sequence numbers when you replace items in BOMs.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Say, you make bicycles and use frames that you buy from
		  supplier A until August. However, after August you will use identical frames
		  that you buy from supplier B. Do not use a new BOM position number for the
		  second frame. Instead, use a new sequence number.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2027640">
         <Level1>BOM sequence number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2027638">
      <Term>BOM unit</Term>
      <Definition>See: <Link href="#BomUnit_ti" role="internal">BOM quantity</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="BottleWorkce_ti">
      <Term>bottleneck work center</Term>
      <Definition>A work center that determines or limits the production rate of
		an RPT item when scheduling orders. The work center calendar determines the
		maximum number of hours per day for planning orders of repetitive items.</Definition>
      <Keyword type="glentry" order="d1e2027653">
         <Level1>bottleneck work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000304">
      <Term>bucket</Term>
      <Definition>A quantity of time used for planning and backflushing.</Definition>
      <Keyword type="glentry" order="d1e2027658">
         <Level1>bucket</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000082">
      <Term>budget</Term>
      <Definition>A cost estimate in the preproduction stage of projects.
		Includes an estimate of future costs and revenues related to expected
		activities.</Definition>
      <SimpleSection>
         <Paragraph>A budget is linked to a calculation group. Budgets within the
		  same calculation group can therefore be used for simulation purposes.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027663">
         <Level1>budget</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Buffer_ti">
      <Term>buffer</Term>
      <Definition>An assembly line workstation where no operations are carried
		out, and where orders are waiting to enter the following work station.</Definition>
      <SimpleSection>
         <Paragraph>You can use buffers to change the sequence of products from
		  one line segment to another. Buffers in LN are random access
		  type.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027671">
         <Level1>buffer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000348">
      <Term>buffer (FIFO)</Term>
      <Definition>The orders that came in first go out first. As a result this
		buffer is just a 'pipeline' which can have a certain capacity. No planned
		sequence change can take place so no line rules can be linked to FIFO buffers.</Definition>
      <Keyword type="glentry" order="d1e2027679">
         <Level1>buffer (FIFO)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000347">
      <Term>buffer (random access)</Term>
      <Definition>Buffers with random access places. During the sequence process, LN checks these access
		places to achieve a proper sequence on the next line segment. Line rules can be
		linked to random access buffers. Line rules sequence the assembly orders which
		enter the random access buffer.</Definition>
      <Keyword type="glentry" order="d1e2027684">
         <Level1>buffer (random access)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000414">
      <Term>bus component</Term>
      <Definition>A bus components is an entry in an LDAP directory service. The
		bus component contains information about the server/client that uses <GUIRef href="/baanerp.integration.long" role="package">Infor Integration</GUIRef>, indicating the name, address, message queues, ports and
		so on. In addition, each component has one or more connection points that link
		the <GUIRef href="/baanerp.integration.adapter" role="package">Integration Adapter</GUIRef> for that component to the actual transport layer.</Definition>
      <Keyword type="glentry" order="d1e2029958">
         <Level1>bus component</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="ti" ID="000421">
      <Term>buydesign</Term>
      <Definition>BuyDesign is a third party configurator, that is integrated
		with LN to
		configure an item. The integration can be used only as part of the web user
		interface.</Definition>
      <Keyword type="glentry" order="d1e2030010">
         <Level1>buydesign</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000092">
      <Term>calculation</Term>
      <Definition>Calculations are used in GRT to answer questions in a numeric
		way. The questions are linked to feature aspects. For example, the surface of a
		seat can be calculated by answering two questions: width and length. When the
		two answers are multiplied, the result is a return code for the classification.</Definition>
      <Keyword type="glentry" order="d1e2027689">
         <Level1>calculation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000042">
      <Term>calculation group</Term>
      <Definition>A code representing a group of projects the user wants to
		compare financially.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>You can assign a calculation group to:</ListIntro>
            <ListItem>A budget</ListItem>
            <ListItem>A main project (as long as the calculation group is not
			 assigned to another project or single project)</ListItem>
            <ListItem>A single project (as long as the calculation group is not
			 assigned to another main project or single project)</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027694">
         <Level1>calculation group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000053">
      <Term>calculation office</Term>
      <Definition>A work center that determines the enterprise unit for a project
		or production order and that has an administrative function.</Definition>
      <SimpleSection>
         <Paragraph>For production orders, operations can be carried out in the
		  calculation office, because the calculation office can act as a regular work
		  center.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027710">
         <Level1>calculation office</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000103">
      <Term>calculation office variance</Term>
      <Definition>The variance in financial production results that is not
		accounted for by the price variance and the efficiency variance.</Definition>
      <SimpleSection>
         <Paragraph>A calculation office variance can be caused by an alteration
		  of an end item's Fixed Transfer Price (FTP), or by differences between the
		  estimated and the actual surcharges.</Paragraph>
         <Paragraph>The calculation office variance is used to empty the WIP so
		  that all costs are accounted for.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027718">
         <Level1>calculation office variance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CalibrInterv_ti">
      <Term>calibration interval</Term>
      <Definition>The interval between one calibration and the next. The interval
		shows when the next calibration will take place: after n days, or after n times
		used.</Definition>
      <Keyword type="glentry" order="d1e2027728">
         <Level1>calibration interval</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CapaciUnit_ti">
      <Term>capacity unit</Term>
      <Definition>The unit in which the capacity of an inventory location is
		registered. It usually applies to the physical quantity area, volume, or weight
		and can be converted into the inventory unit.</Definition>
      <Keyword type="glentry" order="d1e2027733">
         <Level1>capacity unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000003">
      <Term>checklist</Term>
      <Definition>An order document to check whether everything is present for
		the release of a production order. It lists the required materials, tools,
		machines, and so on.</Definition>
      <Keyword type="glentry" order="d1e2027738">
         <Level1>checklist</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000087">
      <Term>classification</Term>
      <Definition>A process to group items according to predefined features. This
		also results in a coding system by which item codes can be generated. The
		reason for doing this is to easily retrieve items, matching certain features.</Definition>
      <Keyword type="glentry" order="d1e2027743">
         <Level1>classification</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2027759">
      <Term>CLSO</Term>
      <Definition>See: <Link href="#000305" role="internal">clustered line station order</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000305">
      <Term>clustered line station order</Term>
      <Definition>Represents all the material requirements for a line station for
		a day. A CLSO consists of user-defined buckets. The material requirements are
		combined for each bucket.</Definition>
      <SimpleSection>
         <Paragraph>In <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>, transactions can be carried out per line station and per
		  period, instead of per order. LN can combine the same materials for a specific period into one
		  material line. After doing so, the cumulated quantity is stored in the CLSO.
		  This accumulation reduces the number of transactions that are necessary,
		  because the transactions are performed for a specific bucket.</Paragraph>
      </SimpleSection>
      <Acronym>CLSO</Acronym>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000304" role="glossary">bucket</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2027748">
         <Level1>clustered line station order</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2027748">
         <Level1>CLSO</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000004">
      <Term>collective cutting list</Term>
      <Definition>A list to cut materials for multiple production orders that are
		made from the same material. A cutting list is sorted by material code and item
		group. Using a cutting list can save time.</Definition>
      <Keyword type="glentry" order="d1e2027764">
         <Level1>collective cutting list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000005">
      <Term>collective sawing list</Term>
      <Definition>A list to saw materials for multiple production orders that are
		made from the same material. A sawing list is sorted by material code and item
		group. Using a sawing list can save time.</Definition>
      <Keyword type="glentry" order="d1e2027769">
         <Level1>collective sawing list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="000339">
      <Term>compile</Term>
      <Definition>To translate all the source code of a program from high-level
		language into object code prior to execution of the program. Object code is an
		executable machine code or a variation of machine code.</Definition>
      <Keyword type="glentry" order="d1e2027774">
         <Level1>compile</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="CompleDate_ti">
      <Term>completion date</Term>
      <Definition>The date on which the work on a project or order is finished.</Definition>
      <SimpleSection>
         <List>
            <ListItem>The completion date of a <Emphasis>production</Emphasis> order is the date on which the order receives the status <GUIRef href="/baanerp/tc/domains/osta#completed" role="option">Completed</GUIRef>.</ListItem>
            <ListItem>The completion date of a <Emphasis>project</Emphasis> is the
			 date on which the project receives the status <GUIRef href="/baanerp/tc/domains/psts#finished" role="option">Finished</GUIRef>.</ListItem>
         </List>
         <Paragraph>You can still perform certain financial transactions on the
		  order, after it is completed, until you close it. The same is true for
		  projects.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027779">
         <Level1>completion date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Constraint_ti">
      <Term>constraint</Term>
      <Definition>A set of decision rules (constraints) that control the
		translation of the customer requirements into the product structure of the
		variant. These constraints indicate which components and operations will be
		used in a specific product variant.</Definition>
      <Keyword type="glentry" order="d1e2027805">
         <Level1>constraint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100003">
      <Term>constraint</Term>
      <Definition>In LN,
		a means to check, restrict, or compel to avoid or perform some action.</Definition>
      <SimpleSection>
         <Paragraph>In the <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module, a constraint is every possible decision rule or
		  calculation conceivable that can be carried out during the definition of the
		  product variants. You can use constraints in the product model for product
		  features, generic BOMs, routings, price lists, and item data. You can use a
		  constraint editor to define constraints.</Paragraph>
         <Paragraph>Among other things, constraints allow you to indicate under
		  which conditions certain combinations of options are acceptable, mandatory, or
		  not acceptable for product features. You can also indicate which bill of
		  material components and/or operations must be included or excluded, what the
		  purchase or sales price structure for a product variant is, and so on.</Paragraph>
         <Paragraph>In the <GUIRef href="/baanerp/ti/grt" role="module">Product Classification</GUIRef> module, a constraint consists of one or more constraint
		  lines that define the conditions under which certain return values or
		  calculation results are included in the classification code during item
		  classification.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027810">
         <Level1>constraint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000093">
      <Term>constraint</Term>
      <Definition>In the <GUIRef href="/baanerp/ti/grt" role="module">Product Classification</GUIRef> module, a constraint consists of one or more constraint
		lines that define the conditions under which certain return values or
		calculation results are included in the classification code during the
		classification of items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>For example:</ListIntro>
            <ListItem>If the chair is red, include r in the classification code.</ListItem>
            <ListItem>If the chair is blue, include b in the classification code.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027828">
         <Level1>constraint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="100007">
      <Term>constraint identification code</Term>
      <Definition>The code that uniquely identifies a constraint of a generic
		item.</Definition>
      <Keyword type="glentry" order="d1e2027844">
         <Level1>constraint identification code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100006">
      <Term>constraint validation message</Term>
      <Definition>Error messages during the configuration process that can be
		used in constraints (constraint rules). During the configuration process, LN checks if the
		selected feature or option comply with the conditions defined by the
		constraints.</Definition>
      <SimpleSection>
         <Paragraph>If the selection does not meet these conditions, LN will issue one of
		  the messages recorded in this session to indicate which options are allowed.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027849">
         <Level1>constraint validation message</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100002">
      <Term>constraint validation message</Term>
      <Definition>System messages showing the constraint rules during
		configuration. These rules are part of constraint texts, in the form of either
		codes or text. Constraint validation messages only refer to constraint sections
		of type <GUIRef href="/baanerp/tc/domains/cnss#validation" role="option">Validation</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2027857">
         <Level1>constraint validation message</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000105">
      <Term>container</Term>
      <Definition>A vessel used to store or move material.</Definition>
      <Keyword type="glentry" order="d1e2027865">
         <Level1>container</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000367">
      <Term>costing work center</Term>
      <Definition>A work center, when linked to a planning work center, that is
		used to calculate the end item unit costs, WIP transfers, and production
		results. The financial transactions related to production orders are then
		posted to the costing work center.</Definition>
      <SimpleSection>
         <Paragraph>The link between a costing work center and a planning work
		  center enables you to replan production order operations. If required, you can
		  change the work center that is used to carry out an operation without
		  disturbing the costing process.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027885">
         <Level1>costing work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000107">
      <Term>cost item</Term>
      <Definition>An item which is not kept in stock but to which costs are
		allocated. Example,
		water, electricity.</Definition>
      <Keyword type="glentry" order="d1e2027870">
         <Level1>cost item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CostPrice_ti">
      <Term>cost price</Term>
      <Definition>The original price of an item, the total outlay of costs
		required to produce or purchase the item.</Definition>
      <Keyword type="glentry" order="d1e2027875">
         <Level1>cost price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CostPriceSur_ti">
      <Term>cost price surcharge</Term>
      <Definition>The amount charged in addition to the usual cost incurred when
		manufacturing or purchasing a single item.</Definition>
      <Keyword type="glentry" order="d1e2027880">
         <Level1>cost price surcharge</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="CountPoint_ti">
      <Term>count point</Term>
      <Definition>An operation in a routing where the quantity of completed and
		rejected items must be determined explicitly. If an operation is a count point,
		completion of that operation must be reported separately. The quantity
		completed in follow-up operations must not exceed the quantity completed in the
		count point.</Definition>
      <SimpleSection>
         <Paragraph>If an operation is not a count point, it can be set to <GUIRef href="/baanerp/ti/domains/sfc.opst#completed" role="option">Completed</GUIRef> automatically
		  upon completion of a follow-up operation. The quantities completed and rejected
		  are then determined by the completed quantity in the count point.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027894">
         <Level1>count point</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000028">
      <Term>covering note</Term>
      <Definition>The order document that accompanies a product during the
		manufacturing process, and that is used for identification purposes.</Definition>
      <Keyword type="glentry" order="d1e2027905">
         <Level1>covering note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CriticBOMLev_ti">
      <Term>critical BOM level</Term>
      <Definition>The lowest level at which the relevant plan item appears in the
		bill of critical materials.</Definition>
      <Keyword type="glentry" order="d1e2027910">
         <Level1>critical BOM level</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000321">
      <Term>critical work center</Term>
      <Definition>A work center that is defined by the user as a bottleneck.</Definition>
      <Keyword type="glentry" order="d1e2027915">
         <Level1>critical work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000322">
      <Term>current operation</Term>
      <Definition>The operation currently carried out with the earliest start
		date. If more than one operation meets this criterion, the operation with the
		lowest operation number is the current operation. There can be only one current
		operation at any one time.</Definition>
      <Keyword type="glentry" order="d1e2027920">
         <Level1>current operation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="CustomItem_ti">
      <Term>customized item</Term>
      <Definition>An item produced on a customer specification for a specific
		project. A customized item can have a customized BOM and/or a customized
		routing and is normally not available as a standard item. A customized item
		can, however, be derived from a standard item or a generic item.</Definition>
      <Keyword type="glentry" order="d1e2027925">
         <Level1>customized item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000006">
      <Term>cutting list</Term>
      <Definition>An order document that lists the materials to be cut from a
		larger piece of material, for example, a sheet of metal.</Definition>
      <Keyword type="glentry" order="d1e2027930">
         <Level1>cutting list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="000000000000057">
      <Term>cycle time</Term>
      <Definition>In LN,
		the time between completion of two separate units of production. For example,
		the cycle time of motors assembled at a rate of 120 per hour is 30 seconds.</Definition>
      <SimpleSection>
         <Paragraph>The cycle time is also equal to the time that a product stays
		  in one position on a assembly line, or the time that an operation is carried
		  out on an item in a work station (excluding setup time).</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027935">
         <Level1>cycle time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000017">
      <Term>delivery date</Term>
      <Definition>The date the finished items are finished according to the
		planning.</Definition>
      <Keyword type="glentry" order="d1e2027943">
         <Level1>delivery date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000337">
      <Term>demonstrated load factor</Term>
      <Definition>Combined efficiency and utilization. The ratio of actual output
		to available capacity, for an operation performed at a given work center or
		machine.</Definition>
      <Keyword type="glentry" order="d1e2027948">
         <Level1>demonstrated load factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="DeprecCode_ti">
      <Term>depreciation code</Term>
      <Definition>The depreciation system according to which depreciation, value
		reduction, revaluation, and so on are calculated.</Definition>
      <Keyword type="glentry" order="d1e2027953">
         <Level1>depreciation code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000334">
      <Term>desired queue</Term>
      <Definition>The difference that the user wants between the output and input
		of a work center. This value is the default for initial queue calculations.</Definition>
      <Keyword type="glentry" order="d1e2027959">
         <Level1>desired queue</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2027321">
      <Term>detailed cost component</Term>
      <Definition>See: <Link href="#000343" role="internal">aggregated cost component</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000344">
      <Term>detailed cost component</Term>
      <Definition>A cost component that contains non-aggregated costs.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>These costs originate directly from:</ListIntro>
            <ListItem>Surcharges</ListItem>
            <ListItem>Operations</ListItem>
            <ListItem>Purchase</ListItem>
         </List>
         <Paragraph>Detailed cost components result in a price structure where
		  all costs have been broken down.</Paragraph>
         <Paragraph>Production order costs, production variances, and production
		  surcharges are calculated and posted by detailed cost component. However, in
		  inventory, the goods are calculated and posted by the three aggregated cost
		  components.</Paragraph>
      </SimpleSection>
      <Antonym>aggregated cost component</Antonym>
      <Keyword type="glentry" order="d1e2027964">
         <Level1>detailed cost component</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2027964">
         <Level1>aggregated cost component</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Dissagregate_ti">
      <Term>disaggregate</Term>
      <Definition>A process that splits a family into smaller families, or into
		items.</Definition>
      <SimpleSection>
         <Paragraph>Disaggregation is used in planning procedures, for example,
		  to split the demand plan or the production plan.</Paragraph>
         <List>
            <ListIntro>The split is based on a disaggregation rule, such as one of
			 the following:</ListIntro>
            <ListItem>Planning percentages (defined in the aggregation
			 relationships)</ListItem>
            <ListItem>Inventory</ListItem>
            <ListItem>CTP volume</ListItem>
         </List>
         <Paragraph>You can also disaggregate items that are not part of a
		  family.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2027985">
         <Level1>disaggregate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="EarlieFinish_ti">
      <Term>earliest finish date</Term>
      <Definition>The earliest date an activity can end, taking into account
		previous and next activities and the company calendar.</Definition>
      <SimpleSection>
         <Paragraph>The earliest finish date can be calculated for activities in
		  the network planning and for operations in the production planning.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028004">
         <Level1>earliest finish date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000076">
      <Term>effective date</Term>
      <Definition>The first date on which the relevant standard cost price takes
		effect.</Definition>
      <Keyword type="glentry" order="d1e2028012">
         <Level1>effective date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000084">
      <Term>effective date</Term>
      <Definition>The date on which the validity of the materials or the
		operations is checked.</Definition>
      <SimpleSection>
         <Paragraph>LN considers a material or operation to be valid if this date falls between the
		  effective date and the expiry date of a material or operation.</Paragraph>
         <Paragraph>The effective dates are used in the explosion process to
		  create demands for the correct items.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028017">
         <Level1>effective date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="EfficiVarian_ti">
      <Term>efficiency variances</Term>
      <Definition>A part of the production result that is created by differences
		between the estimated and actual material quantities and hours.</Definition>
      <SimpleSection>
         <Paragraph>The efficiency variance shows how efficiently materials and
		  resources are used.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028027">
         <Level1>efficiency variances</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2028053">
      <Term>E-item</Term>
      <Definition>See: <Link href="#EngineItem_ti" role="internal">engineering item</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000110">
      <Term>end item</Term>
      <Definition>An item that is ready to be delivered to a warehouse. An end
		item is produced at the end of a dangle routing (co-products and by-products)
		or a main routing.</Definition>
      <Keyword type="glentry" order="d1e2028035">
         <Level1>end item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="EngineItem_ti">
      <Term>engineering item</Term>
      <Definition>An item in the process of development.</Definition>
      <SimpleSection>
         <Paragraph>You can define multiple revisions of an engineering item.
		  Typically, the most recent revisions are still in a design or test phase,
		  another revision may have been taken into production, and older revisions are
		  obsolete.</Paragraph>
         <Paragraph>A normal item can only become revision-controlled when it is
		  copied from the <GUIRef href="/baanerp/ti/edm" role="module">Engineering Data Management</GUIRef> module.</Paragraph>
      </SimpleSection>
      <Synonym>E-item</Synonym>
      <Keyword type="glentry" order="d1e2028040">
         <Level1>engineering item</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2028040">
         <Level1>E-item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="EngineItemRe_ti">
      <Term>engineering item relationships</Term>
      <Definition>A link between a particular E-item revision and one or more
		standard or customized items. You can use the relationship to implement a
		design change incorporated in a new E-item revision by copying the E-item data
		to the item defined in the relationship.</Definition>
      <Keyword type="glentry" order="d1e2028055">
         <Level1>engineering item relationships</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="ti" ID="000401">
      <Term>engineering module</Term>
      <Definition>In <GUIRef href="/baanerp/ti/apl" role="module">Assembly Planning</GUIRef>, a system, or, in other words, a logical unit of assembly
		parts, that is typically not manufactured as a separate physical unit.</Definition>
      <SimpleSection>
         <Paragraph>For example, the electrical system of a car is the logical
		  unit of all parts required for the electrical system. It is, however, not
		  manufactured as a separate physical unit, but integrated in the dashboard,
		  doors, and so on.</Paragraph>
         <Paragraph>An engineering module has no routings, assembly lines,
		  options, and so on, and is for design and planning purposes only. In the bill
		  of materials (BOM), the engineering module is the top layer of the
		  nonconfigurable section of the BOM.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028060">
         <Level1>engineering module</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000323">
      <Term>enterprise planning order group</Term>
      <Definition>A user-defined group of planned production orders.</Definition>
      <Keyword type="glentry" order="d1e2028074">
         <Level1>enterprise planning order group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000057">
      <Term>estimated quantity</Term>
      <Definition>The quantity of an item that is planned for use in a particular
		production order.</Definition>
      <SimpleSection>
         <Paragraph>The estimated quantity is made up of the net quantity plus
		  any additional quantities used to compensate for anticipated material losses.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028079">
         <Level1>estimated quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000310">
      <Term>exchangeable configuration</Term>
      <Definition>A configuration is exchangeable with another configuration at a
		particular point on the assembly line, if at that point the two configurations
		have the same specifications.</Definition>
      <Keyword type="glentry" order="d1e2028087">
         <Level1>exchangeable configuration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ExponeSmooth_ti">
      <Term>exponential smoothing</Term>
      <Definition>A demand forecast method that takes account of recent data over
		and above past data.</Definition>
      <Keyword type="glentry" order="d1e2028092">
         <Level1>exponential smoothing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000088">
      <Term>family</Term>
      <Definition>In <GUIRef href="/baanerp/ti/grt" role="module">Product Classification</GUIRef>, a collection of items with common features.</Definition>
      <Keyword type="glentry" order="d1e2028097">
         <Level1>family</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000089">
      <Term>family structure</Term>
      <Definition>A multilevel hierarchy (tree) of product families. Product
		families are part of a main family group. Lower family groups can be linked to
		a higher family.</Definition>
      <Keyword type="glentry" order="d1e2028105">
         <Level1>family structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000018">
      <Term>FAS item</Term>
      <Definition>A generic item with the FAS (Final Assembly Scheduling) order
		system.</Definition>
      <SimpleSection>
         <Paragraph>FAS items are produced in a mixed model flow process on an
		  assembly line.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028110">
         <Level1>FAS item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000090">
      <Term>feature</Term>
      <Definition>A property of an item which is used when you classify items.
		For example, a frame and a wheel are features of the item bike.</Definition>
      <Keyword type="glentry" order="d1e2028118">
         <Level1>feature</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100000">
      <Term>feature</Term>
      <Definition>Characteristics which can be combined and subsequently be
		linked to configurable items to compose a product variant. An example of a
		feature is color.</Definition>
      <Keyword type="glentry" order="d1e2028123">
         <Level1>feature</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Finalize_ti">
      <Term>finalize</Term>
      <Definition>The final action when you actually copy data from engineering
		bills of material (EBOMs) to production bills of material.</Definition>
      <SimpleSection>
         <Paragraph>To copy data, you can either use mass BOM changes (MBCs), or
		  manually copy the BOM lines.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028128">
         <Level1>finalize</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000075">
      <Term>fixed costs</Term>
      <Definition>Expenses that do not vary with the production volume. Examples
		of these costs are the depreciation costs of machines and buildings, rent, and
		property taxes. Operation rates and surcharges can be attributed to the
		variable costs or the fixed costs.</Definition>
      <SimpleSection>
         <Paragraph>Antonym: variable costs</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028136">
         <Level1>fixed costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2029856">
      <Term>fixed costs</Term>
      <Definition>See: <Link href="#000340" role="internal">variable costs</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000353">
      <Term>fixed duration</Term>
      <Definition>An indication whether the production time is fixed, or is
		dependent on the order quantity. If the production time has a fixed duration,
		then it equals the cycle time. If it is indicated that the production time does
		not have a fixed duration, the cycle time is multiplied by the order quantity.</Definition>
      <SimpleSection>
         <Paragraph>For example, baking one bread in the oven takes one hour.
		  Baking a hundred breads at once also takes a fixed duration of one hour.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028145">
         <Level1>fixed duration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000402">
      <Term>flatten</Term>
      <Definition>To bring down a multilevel structure to one level. As a result,
		all elements of the hierarchical structure are the direct children of the
		parent item. This process can be used to enhance the calculation of assembly
		part requirements.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Once in while, a product structure is flattened, and the
		  result is stored separately. This way, LN does not need to
		  browse the structure each time the assembly part requirements are calculated,
		  because all parts that are required can be read at once.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028153">
         <Level1>flatten</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="FloatTimeNet_ti">
      <Term>float time</Term>
      <Definition>The time between two activities, expressed in days.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>If activity A and activity B have a end-start relationship
		  with a delay of three, the network planning shows that activity B starts three
		  days after activity A has finished.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028163">
         <Level1>float time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="FloorStock_ti">
      <Term>floor stock</Term>
      <Definition>A stock of inexpensive material present on the shop floor that
		can be used in production without recording each issue of material
		individually. Floor stock is not backflushed and is not part of the estimated
		costs.</Definition>
      <Keyword type="glentry" order="d1e2028173">
         <Level1>floor stock</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000354">
      <Term>freeze</Term>
      <Definition>To deactivate line stations, line segments, line station
		orders, and the like. If something is frozen, no changes are allowed. For
		example, a line station order can be frozen because the production process is
		too far advanced to be able to process the change.</Definition>
      <Keyword type="glentry" order="d1e2028178">
         <Level1>freeze</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000038">
      <Term>FTP inventory valuation method</Term>
      <Definition>Fixed transfer pricing is an inventory valuation method. The
		fixed transfer price is a calculated inventory value, based upon calculated
		material costs, operation costs, and surcharges. The FTP valuation price
		includes the surcharges by warehouse.</Definition>
      <Keyword type="glentry" order="d1e2028183">
         <Level1>FTP inventory valuation method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="GeneriItem_ti">
      <Term>generic item</Term>
      <Definition>An item that exists in multiple product variants. Before any
		manufacturing activities are performed on a generic item, the item must be
		configured to determine the desired product variant.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Generic item: electric drill</Paragraph>
         <List>
            <ListIntro>Options:</ListIntro>
            <ListItem>3 power sources (batteries, 12 V or 220 V)</ListItem>
            <ListItem>2 colors (blue, gray).</ListItem>
         </List>
         <Paragraph>A total of 6 product variants can be produced with these
		  options.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028188">
         <Level1>generic item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="100008">
      <Term>generic price list</Term>
      <Definition>A product variant that is generated from customer
		specifications can have a detailed sales price based on the selected options.
		Purchase prices for generic items can also be generated. The purchase price is
		used to calculate the cost price. Matrices can be defined if options exist for
		different product features that have mutual relationships that influence the
		purchase or sales price.</Definition>
      <Keyword type="glentry" order="d1e2028207">
         <Level1>generic price list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000007">
      <Term>inspection note</Term>
      <Definition>An order document on which the inspected and approved
		quantities of finished products can be recorded.</Definition>
      <Keyword type="glentry" order="d1e2028212">
         <Level1>inspection note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Instrument_ti">
      <Term>instrument</Term>
      <Definition>A tool that is used during quality tests to measure particular
		characteristics of an item.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="2">
               <TR no="1" isLast="false">
                  <TH width="122" rowspan="1" colspan="1">Instrument</TH>
                  <TD width="111" rowspan="1" colspan="1">acidimeter</TD>
               </TR>
               <TR no="2" isLast="true">
                  <TH width="122" rowspan="1" colspan="1">Characteristic</TH>
                  <TD width="111" rowspan="1" colspan="1">pH value</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028217">
         <Level1>instrument</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000412">
      <Term>item subcontracting</Term>
      <Definition>The entire production process of an item is outsourced to a
		subcontractor.</Definition>
      <Keyword type="glentry" order="d1e2028237">
         <Level1>item subcontracting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ItemSurc_ti">
      <Term>item surcharge</Term>
      <Definition>An item surcharge is the basis for extra costs or discounts (in
		terms of percentage of fixed amounts) in the cost/valuation price structure for
		items belonging to the given item group or warehouse. Surcharges are linked to
		a price calculation code.</Definition>
      <Keyword type="glentry" order="d1e2028243">
         <Level1>item surcharge</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PullNote_ti">
      <Term>Kanban label</Term>
      <Definition>A document that authorizes the movement of goods to the shop
		floor, between operations, or from the shop floor. Previously called pull note.</Definition>
      <Keyword type="glentry" order="d1e2028248">
         <Level1>Kanban label</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="LeadTime_ti">
      <Term>lead time</Term>
      <Definition>The time between the production start date and the delivery
		date. The lead time can include order preparation time, transportation time,
		and inspection time.</Definition>
      <Keyword type="glentry" order="d1e2028253">
         <Level1>lead time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="LeadTimeOffs_ti">
      <Term>lead-time offset</Term>
      <Definition>The cumulative lead time of the production process, calculated
		from the production stage where the relevant critical material or critical
		capacity is required to the final stage of the production process. The
		lead-time offset is a factor in determining the start date of the critical
		material or critical capacity requirement.</Definition>
      <SimpleSection>
         <Paragraph>The lead-time offset can be expressed in days or
		  hours.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028258">
         <Level1>lead-time offset</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000138">
      <Term>lifetime serial number</Term>
      <Definition>A number to identify a tool. A lifetime serial number can be,
		for example, a combination of the functional number and the year of purchase.
		Lifetime serial numbers are used to group the components of a multipiece tool.</Definition>
      <SimpleSection>
         <Paragraph>Multipiece tools without a lifetime serial number can have
		  components linked either with or without lifetime serial numbers.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>A multipiece tool X has a life time serial number 1990. One
			 of the following must be true for the tool's components:</ListIntro>
            <ListItem>The lifetime serial number of the components is the same as
			 the multipiece tool (that is, 1990).</ListItem>
            <ListItem>The components that are linked to the multipiece tool do not
			 have a lifetime serial number.</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028266">
         <Level1>lifetime serial number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="LineMix_ti">
      <Term>line mix</Term>
      <Definition>A set of production orders that are produced successively on an
		assembly line. Before production starts, the line mix is sequenced to determine
		the order of production.</Definition>
      <Keyword type="glentry" order="d1e2028284">
         <Level1>line mix</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000019">
      <Term>line segment</Term>
      <Definition>A set of consecutive assembly-line work centers on an assembly
		line between two buffers. The first buffer is the beginning of the segment, the
		next buffer is the first part of the next segment.</Definition>
      <Keyword type="glentry" order="d1e2028289">
         <Level1>line segment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000034">
      <Term>line sequencing</Term>
      <Definition>The determination of the sequence order used to start the
		production of items in a segment of a production line. The sequence order may
		be changed from one line segment to the next.</Definition>
      <Keyword type="glentry" order="d1e2028294">
         <Level1>line sequencing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="LineStatio_ti">
      <Term>line station</Term>
      <Definition>A work center that is part of an assembly line. A line station
		is used in the production of FAS (final assembly schedule) items. A line
		station can have multiple positions, which enables more than one item to be
		present in one line station.</Definition>
      <Keyword type="glentry" order="d1e2028299">
         <Level1>line station</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000311">
      <Term>line station order</Term>
      <Definition>Production order for an assembly line station.</Definition>
      <Keyword type="glentry" order="d1e2028304">
         <Level1>line station order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000306">
      <Term>line-station variant</Term>
      <Definition>Holds identical operations and materials that are used at a
		specific line station for multiple assembly orders. In this manner, the
		identical operations and materials are stored only once, rather than for each
		assembly order. When line station variants are used, less data storage is
		required, and the performance is enhanced.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>You produce cars with various features, including two types
		  of wheels: broad and narrow. In the wheel line station, in which the wheels are
		  fitted, all cars with broad wheels are one line station variant, and cars with
		  narrow wheels are another line station variant, regardless of any other
		  specifications, because the other specifications are not relevant to the wheel
		  line station.</Paragraph>
      </ExampleSection>
      <Synonym>LSV</Synonym>
      <Keyword type="glentry" order="d1e2028309">
         <Level1>line-station variant</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2028309">
         <Level1>LSV</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2028319">
      <Term>LSV</Term>
      <Definition>See: <Link href="#000306" role="internal">line-station variant</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="Machines_ti">
      <Term>machine</Term>
      <Definition>In LN,
		a mechanical object on which operations can be carried out to produce items.</Definition>
      <SimpleSection>
         <Paragraph>Machines are linked to operation rates. The operation rate
		  and the labor rate together form the basis for the actual costing of production
		  orders.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028322">
         <Level1>machine</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="6.0a" ContextApps="ti" ID="100109">
      <Term>machine hours</Term>
      <Definition>The machine capacity in hours required to carry out the
		operation.</Definition>
      <SimpleSection>
         <Paragraph>The formula LN applies to calculate the machine hours depends on whether or not
		  the operation has a fixed duration. If the operation has a fixed duration, LN applies the
		  following formula to calculate the machine hours:</Paragraph>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="108" width="648"
                      SRC="../images/tr_graph_tiglossary_100109a.gif"
                      alt="[...]"/>
         </Figure>
         <Paragraph>If the operation does not have a fixed duration, LN applies the
		  following formula to calculate the machine hours:</Paragraph>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="108" width="720"
                      SRC="../images/tr_graph_tiglossary_100109b.gif"
                      alt="[...]"/>
         </Figure>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028330">
         <Level1>machine hours</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000096">
      <Term>main assembly line</Term>
      <Definition>An assembly line that produces end products. An assembly line
		is a set of consecutive line stations where FAS (Final Assembly Schedule) items
		(and sometimes other item types) are manufactured.</Definition>
      <Keyword type="glentry" order="d1e2028344">
         <Level1>main assembly line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="MainItem_ti">
      <Term>main item</Term>
      <Definition>The end result of a production order.</Definition>
      <SimpleSection>
         <Paragraph>A main item is either be changed to an end item (for delivery
		  to a warehouse), or delivered directly to the customer in bulk.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028349">
         <Level1>main item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="MainWorkCent_ti">
      <Term>main work center</Term>
      <Definition>A work center that is subdivided into subordinate work centers.</Definition>
      <Keyword type="glentry" order="d1e2028357">
         <Level1>main work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="6.0a" ContextApps="ti" ID="100108">
      <Term>man hours</Term>
      <Definition>The man capacity in hours required to carry out the
		operation.</Definition>
      <SimpleSection>
         <Paragraph>The formula LN applies to calculate the man hours depends on whether or not the
		  operation has a fixed duration. If the operation has a fixed duration, LN applies the
		  following formula to calculate the man hours:</Paragraph>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="108" width="648"
                      SRC="../images/tr_graph_tiglossary_100108a.gif"
                      alt="[...]"/>
         </Figure>
         <Paragraph>If the operation does not have a fixed duration, LN applies the
		  following formula to calculate the man hours:</Paragraph>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="108" width="720"
                      SRC="../images/tr_graph_tiglossary_100108b.gif"
                      alt="[...]"/>
         </Figure>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028362">
         <Level1>man hours</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000326">
      <Term>mass BOM change</Term>
      <Definition>A mechanism to simultaneously make multiple changes to the
		engineering bills of material of several items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>You can use mass bill of material changes to concurrently
			 carry out several of the following actions:</ListIntro>
            <ListItem>Modify EBOM lines</ListItem>
            <ListItem>Copy E-item revisions to production items</ListItem>
            <ListItem>Copy EBOMs to productions BOMs</ListItem>
         </List>
      </SimpleSection>
      <Synonym>MBC</Synonym>
      <Keyword type="glentry" order="d1e2028376">
         <Level1>mass BOM change</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2028376">
         <Level1>MBC</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="ti" ID="000405">
      <Term>master company</Term>
      <Definition>In a multicompany situation, a master company is used to
		synchronize data in all companies. Data that is entered or generated in the
		master company, for example, the line structure, can be replicated to the other
		companies. The master company can either be one of the companies of the
		assembly lines, or a separate company.</Definition>
      <Keyword type="glentry" order="d1e2028393">
         <Level1>master company</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Material_ti">
      <Term>material</Term>
      <Definition>The raw materials, components, and subassemblies used to
		manufacture an item. A cost item, for example, electricity, can also be treated
		as a material.</Definition>
      <Keyword type="glentry" order="d1e2028398">
         <Level1>material</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000008">
      <Term>material issue note</Term>
      <Definition>An order document that reports the estimated, allocated, and
		issued quantities of required materials for a production order.</Definition>
      <SimpleSection>
         <Paragraph>If you are using SFC order groups, you can combine the
		  material for all the production orders in the group into one document, the
		  collective material issue note.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028403">
         <Level1>material issue note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000009">
      <Term>material list</Term>
      <Definition>An order document that is used to report the material
		requirements of a production order. The document reports both the estimated
		quantities and the inventories on hand of the materials.</Definition>
      <Keyword type="glentry" order="d1e2028411">
         <Level1>material list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000080">
      <Term>mathematical operator</Term>
      <Definition>Denotes or performs a mathematical operation or function; for
		example, add (+) and subtract (-).</Definition>
      <Keyword type="glentry" order="d1e2028417">
         <Level1>mathematical operator</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2028391">
      <Term>MBC</Term>
      <Definition>See: <Link href="#000326" role="internal">mass BOM change</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000364">
      <Term>microrouting</Term>
      <Definition>A series of steps that is linked to a routing operation to
		which you can connect instructions, tools information, and process information.
		When a production order is released, the information that is linked to the
		operation steps is given to, for example, the shop floor operators to support
		their jobs.</Definition>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000365" role="glossary">operation step</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2028422">
         <Level1>microrouting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="MinimuOrderQ_ti">
      <Term>minimum order quantity</Term>
      <Definition>The minimum quantity of items to be purchased or produced. When
		planned orders are generated, the quantity of items to be purchased or produced
		is never less than the minimum order quantity. The minimum order quantity
		prevents the purchase or production of this item in quantities that are too
		small.</Definition>
      <Keyword type="glentry" order="d1e2028430">
         <Level1>minimum order quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000085">
      <Term>module</Term>
      <Definition>A planning unit for a customized, manufactured, or purchased
		part, for which the logistical planning is related directly to the project
		network planning. A module may be a more or less complex compound part or a
		single part, such as a long delivery time part.</Definition>
      <Keyword type="glentry" order="d1e2028435">
         <Level1>module</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B5.2b" ContextApps="ti" ID="100102">
      <Term>move time</Term>
      <Definition>The time that a semifinished good is in transit from one
		operation to the next operation. After the last operation, the move time is the
		time to transfer the finished good to the warehouse.</Definition>
      <SimpleSection>
         <Paragraph>Move time is one of the lead-time elements LN plans according to a
		  specific calendar.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028440">
         <Level1>move time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="MovingAverag_ti">
      <Term>moving average</Term>
      <Definition>The average value of the present inventory, which is used in
		order to calculate the administrative price when you issue inventory. The
		inventory value is based on historical purchase prices.</Definition>
      <Keyword type="glentry" order="d1e2028448">
         <Level1>moving average</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="MultilBillOf_ti">
      <Term>multilevel bill of material</Term>
      <Definition>A BOM that lists the subcomponents of the components, and any
		eventual subcomponents.</Definition>
      <SimpleSection>
         <Paragraph>In the multilevel BOM, the final product is at level zero.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028453">
         <Level1>multilevel bill of material</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="MultiPieceTo_ti">
      <Term>multipiece tool</Term>
      <Definition>A tool with detachable components that operate together during
		an operation.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You can group the elements of a multipiece tool with a life
		  time serial number.</Paragraph>
      </Note>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>A die is used for fixture. The die is made up of the
			 following components:</ListIntro>
            <ListItem>Top die</ListItem>
            <ListItem>Bottom die</ListItem>
            <ListItem>Punches</ListItem>
            <ListItem>Guide pillars</ListItem>
         </List>
         <Paragraph>The die is defined as the multipiece tool, and the pieces are
		  defined as the components.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028461">
         <Level1>multipiece tool</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000056">
      <Term>net quantity</Term>
      <Definition>The quantity of a component or material that is theoretically
		required to make a certain quantity of a product.</Definition>
      <SimpleSection>
         <Paragraph>This quantity is referred to as the net quantity because in
		  practice you may need more than this quantity to make up for certain losses of
		  the material or the product.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028488">
         <Level1>net quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="NetworPlanni_ti">
      <Term>network planning</Term>
      <Definition>The network planning includes all the activities required to
		carry out (plan and control) a project. The relations within the network show
		the interdependent activities.</Definition>
      <Keyword type="glentry" order="d1e2028496">
         <Level1>network planning</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="NormalCapaci_ti">
      <Term>normal capacity</Term>
      <Definition>The average capacity of a machine or work center that is used
		as the basis for the capacity utilization.</Definition>
      <Synonym>basic capacity</Synonym>
      <Keyword type="glentry" order="d1e2028584">
         <Level1>normal capacity</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2028584">
         <Level1>basic capacity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="NormTable_ti">
      <Term>norm table</Term>
      <Definition>A table that contains the times required to perform a task
		(norm times), or the numbers of times that a task can be performed in a
		specific unit of time (norm units). The norm times or norm units depend on two
		series of values presented in the columns (X-axis) and the rows (Y-axis) of the
		table.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The time that it costs to drill a hole depends on the
		  material's thickness, and the hole's diameter. A norm table that contains norm
		  times can look like this:</Paragraph>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TD width="119" rowspan="1" colspan="1"> </TD>
                  <TH colspan="4" width="148" rowspan="1">Thickness (mm)</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TH width="119" rowspan="1" colspan="1">Diameter (mm)</TH>
                  <TD width="32" rowspan="1" colspan="1">1</TD>
                  <TD width="36" rowspan="1" colspan="1">2</TD>
                  <TD width="33" rowspan="1" colspan="1">3</TD>
                  <TD width="35" rowspan="1" colspan="1">4</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="119" rowspan="1" colspan="1">0.5</TD>
                  <TD width="32" rowspan="1" colspan="1">1.2</TD>
                  <TD width="36" rowspan="1" colspan="1">1.4</TD>
                  <TD width="33" rowspan="1" colspan="1">1.6</TD>
                  <TD width="35" rowspan="1" colspan="1">1.8</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="119" rowspan="1" colspan="1">1.0</TD>
                  <TD width="32" rowspan="1" colspan="1">2.2</TD>
                  <TD width="36" rowspan="1" colspan="1">2.5</TD>
                  <TD width="33" rowspan="1" colspan="1">2.8</TD>
                  <TD width="35" rowspan="1" colspan="1">3.1</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD width="119" rowspan="1" colspan="1">1.5</TD>
                  <TD width="32" rowspan="1" colspan="1">3.1</TD>
                  <TD width="36" rowspan="1" colspan="1">3.5</TD>
                  <TD width="33" rowspan="1" colspan="1">3.9</TD>
                  <TD width="35" rowspan="1" colspan="1">4.3</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>The norm time to drill a hole with diameter 1.0 in a material
		  with thickness 2 is 2.5.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028501">
         <Level1>norm table</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000065">
      <Term>norm time</Term>
      <Definition>The time that is required to perform a task. That time is
		determined on the basis of two values in the norm table.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>To drill a hole with a diameter of 5 mm (first value) in a
		  sheet with a thickness of 8 mm (second value) takes 0.5 minute (norm time).</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028564">
         <Level1>norm time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000066">
      <Term>norm unit</Term>
      <Definition>The number of times that a task can be carried out for a
		specific unit of time (minute or hour). That number of times is determined on
		the basis of two values in the norm table.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Each minute, 5 boards with a thickness of 5 mm (first value)
		  and a width of 60 mm (second value) can be sawn. Consequently, the norm unit is
		  5.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028574">
         <Level1>norm unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000000000000041">
      <Term>offset</Term>
      <Definition>The cumulative lead time of the production process. The offset
		is calculated from the production stage, which requires the relevant critical
		material or critical capacity, to the final stage of the production process.
		The lead-time offset is a factor in determining the start date of the critical
		material or critical capacity requirement.</Definition>
      <Keyword type="glentry" order="d1e2028591">
         <Level1>offset</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000307">
      <Term>offsetting</Term>
      <Definition>To plan orders to account for the cumulative lead-time of the
		production process.</Definition>
      <Keyword type="glentry" order="d1e2028596">
         <Level1>offsetting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000000000000052">
      <Term>operation</Term>
      <Definition>One of a series of steps in a routing that are carried out
		successively to produce an item.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following data is collected during a routing operation:</ListIntro>
            <ListItem>The task. For example, sawing.</ListItem>
            <ListItem>The machine used to carry out the task (optional). For
			 example, sawing machine.</ListItem>
            <ListItem>The place where the task is carried out (work center). For
			 example, woodwork.</ListItem>
            <ListItem>The number of employees required to carry out the task.</ListItem>
         </List>
         <Paragraph>This data is used to compute order lead times, to plan
		  production orders and to calculate cost prices.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028601">
         <Level1>operation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000010">
      <Term>operation note</Term>
      <Definition>An order document that contains all the information required to
		carry out an operation. This document is also called a job sheet.</Definition>
      <Keyword type="glentry" order="d1e2028620">
         <Level1>operation note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="OperRate_ti">
      <Term>operation rate</Term>
      <Definition>A rate that is determined by labor costs, machine costs, or
		overhead costs. The operation rate can be linked to work centers or tasks by an
		operation rate code.</Definition>
      <Keyword type="glentry" order="d1e2028625">
         <Level1>operation rate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="OperatRateCo_ti">
      <Term>operation rate code</Term>
      <Definition>A code that identifies operation rates (labor costs, machine
		costs, or overhead costs). The code can be linked to a task or work center.
		Each cost price calculation code can comprise multiple operation rate codes and
		associated operation rates.</Definition>
      <Keyword type="glentry" order="d1e2028630">
         <Level1>operation rate code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000324">
      <Term>operation set</Term>
      <Definition>A set of operations consecutively carried out at the same work
		center.</Definition>
      <Keyword type="glentry" order="d1e2028635">
         <Level1>operation set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000058">
      <Term>operation status</Term>
      <Definition>The status assigned to an operation. For example, <GUIRef href="/baanerp/ti/domains/sfc.opst#planned" role="option">Planned</GUIRef>, <GUIRef href="/baanerp/ti/domains/sfc.opst#ready.to.start" role="option">Ready to Start</GUIRef>, or <GUIRef href="/baanerp/ti/domains/sfc.opst#completed" role="option">Completed</GUIRef>. This status
		indicates how far an operation has proceeded.</Definition>
      <Keyword type="glentry" order="d1e2028640">
         <Level1>operation status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000365">
      <Term>operation step</Term>
      <Definition>A suboperation connected to a routing operation.</Definition>
      <SimpleSection>
         <Paragraph>An operation step can contain information such as,
		  instructions, process information, and tools information.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000364" role="glossary">microrouting</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2028655">
         <Level1>operation step</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000411">
      <Term>operation subcontracting</Term>
      <Definition>The work on one or more operations in an item's production
		process is outsourced to a subcontractor.</Definition>
      <Keyword type="glentry" order="d1e2028666">
         <Level1>operation subcontracting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100001">
      <Term>option</Term>
      <Definition>Options per product feature are aspects that specify the
		product feature. For instance 'red' can be an option of the feature 'color'.</Definition>
      <Keyword type="glentry" order="d1e2028671">
         <Level1>option</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000095">
      <Term>option combination</Term>
      <Definition>A specific combination of product options, for example, color
		or style, that are related to an assembly order.</Definition>
      <SimpleSection>
         <Paragraph>Each option combination is either a single option, or a
		  combination of other option combinations.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028676">
         <Level1>option combination</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100011">
      <Term>option set</Term>
      <Definition>Identifies a set with product features and options for a
		configurable item within the product structure.</Definition>
      <Keyword type="glentry" order="d1e2028684">
         <Level1>option set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000377">
      <Term>order block</Term>
      <Definition>A group of production orders that have the same setup states
		and are produced on the same machine.</Definition>
      <SimpleSection>
         <Paragraph>Production orders with the same setup states can be executed
		  on a machine without changing the machine’s setup.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#100104" role="glossary">setup state</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2028689">
         <Level1>order block</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="OrderCosts_ti">
      <Term>order costs</Term>
      <Definition>The (administrative) costs for placing an order. Order costs
		include the handling and transportation costs. The costs of the purchasing
		department, production planning department, and control department incurred by
		a production order or a purchase order.</Definition>
      <Keyword type="glentry" order="d1e2028700">
         <Level1>order costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="OrderInterv_ti">
      <Term>order interval</Term>
      <Definition>The number of workdays or working hours for which all the
		requirements of a specific item are bundled in one (planned) order, during an
		order planning run. LN calculates the order interval from the day when the first requirement occurs.
		Order intervals are used to prevent an excessive number of planned orders in
		one time period.</Definition>
      <Keyword type="glentry" order="d1e2028705">
         <Level1>order interval</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="OrderQuantiM_ti">
      <Term>order quantity increment</Term>
      <Definition>The size of the step by which the order quantity can be
		increased.</Definition>
      <SimpleSection>
         <Paragraph>The recommended order quantity must be a multiple of the
		  quantity that you specify as the order quantity increment. LN verifies this when
		  planned orders are generated.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>If the required order quantity is 62 and the order quantity
		  increment is 8, then LN recommends an order quantity of 64.</Paragraph>
      </ExampleSection>
      <Synonym>order quantity multiple of</Synonym>
      <Keyword type="glentry" order="d1e2028710">
         <Level1>order quantity increment</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2028710">
         <Level1>order quantity multiple of</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2028723">
      <Term>order quantity multiple of</Term>
      <Definition>See: <Link href="#OrderQuantiM_ti" role="internal">order quantity increment</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="ti" ID="000420">
      <Term>parallel assembly operations</Term>
      <Definition>An assembly line network in which you can perform same
		operations on different assembly lines simultaneously or model a network in
		which a supply line feeds multiple supply lines which again converge at a later
		stage into a single line.</Definition>
      <Keyword type="glentry" order="d1e2030005">
         <Level1>parallel assembly operations</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PartiaDelive_ti">
      <Term>partial delivery</Term>
      <Definition>The delivery of a part of the total order quantity.</Definition>
      <Keyword type="glentry" order="d1e2028725">
         <Level1>partial delivery</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000313">
      <Term>penalty cost</Term>
      <Definition>Theoretical costs for not meeting rules on an assembly line.</Definition>
      <Keyword type="glentry" order="d1e2028730">
         <Level1>penalty cost</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ManHours_ti">
      <Term>person hours</Term>
      <Definition>The unit of work equal to one person working for one hour. The
		terms man-hours and person-hours are used interchangeably.</Definition>
      <Keyword type="glentry" order="d1e2028736">
         <Level1>person hours</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Phantom_ti">
      <Term>phantom</Term>
      <Definition>An assembly that is produced as part of a manufactured item,
		and that can have its own routing.</Definition>
      <SimpleSection>
         <Paragraph>A phantom is usually not held in inventory, although
		  occasionally some inventory can exist. The planning system does not create
		  material requirements for a phantom, but drives the requirements straight
		  through the phantom item to its components. Phantoms are mainly defined to
		  create a modular product structure.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The door of a refrigerator is defined as a phantom item in
		  the bill of material of a refrigerator. The materials of the door are listed on
		  the production order's material list for the refrigerator.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028741">
         <Level1>phantom</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000067">
      <Term>physical location</Term>
      <Definition>The room, building, or construction site where an operation is
		carried out.</Definition>
      <Keyword type="glentry" order="d1e2028754">
         <Level1>physical location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000314">
      <Term>pivot segment</Term>
      <Definition>The segment from which LN starts generating
		sequences.</Definition>
      <Keyword type="glentry" order="d1e2028759">
         <Level1>pivot segment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="PlanItems_ti">
      <Term>plan item</Term>
      <Definition>An item with the order system <GUIRef href="/baanerp/tc/domains/osys#mps" role="option">Planned</GUIRef>.</Definition>
      <SimpleSection>
         <Paragraph>The production, distribution, or purchase of these items is
		  planned in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> based on the forecast or the actual demand.</Paragraph>
         <List>
            <ListIntro>You can plan these items by means of the following:</ListIntro>
            <ListItem>Master-based planning, which is similar to master production
			 scheduling techniques.</ListItem>
            <ListItem>Order-based planning, which is similar to
			 material-requirements planning techniques.</ListItem>
            <ListItem>A combination of master-based planning and order-based
			 planning.</ListItem>
         </List>
         <List>
            <ListIntro>Plan items can be one of the following:</ListIntro>
            <ListItem>An actual manufactured or purchased item.</ListItem>
            <ListItem>A product family.</ListItem>
            <ListItem>A basic model, that is, a defined product variant of a
			 generic item.</ListItem>
         </List>
         <Paragraph>A group of similar plan items or families is called a product
		  family. The items are aggregated to give a more general plan than the one
		  devised for individual items. A code displayed by the item code's cluster
		  segment shows that the plan item is a clustered item that is used for
		  distribution planning.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028764">
         <Level1>plan item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PlanLevel_ti">
      <Term>plan level</Term>
      <Definition>The level within a hierarchical planning structure.</Definition>
      <SimpleSection>
         <Paragraph>When you plan on a higher plan level, plans are general and
		  less detailed.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="390" height="231"
                      SRC="../images/tr_graph_tiglossary_01.gif"
                      alt="[...]"/>
         </Figure>
         <Paragraph>Plan level 1 is the highest plan level; the higher the
		  number, the lower the plan level.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028798">
         <Level1>plan level</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000331">
      <Term>planned input</Term>
      <Definition>The total input quantity of a work center/machine for
		operations that is planned to be Ready to Start during the target period.</Definition>
      <Keyword type="glentry" order="d1e2028813">
         <Level1>planned input</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="ti" ID="000049">
      <Term>planned offline date</Term>
      <Definition>The date when an assembly item is planned to roll off the
		assembly line.</Definition>
      <SimpleSection>
         <Paragraph>Initially, the planned offline date equals the requested
		  offline date, but the planned offline date can be changed later for planning
		  reasons.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029997">
         <Level1>planned offline date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000332">
      <Term>planned output</Term>
      <Definition>The total output quantity that you plan to report complete, for
		operations at a work center/machine during the target period.</Definition>
      <Keyword type="glentry" order="d1e2028818">
         <Level1>planned output</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000333">
      <Term>planned queue</Term>
      <Definition>The planned input minus the planned output of a work
		center/machine.</Definition>
      <Keyword type="glentry" order="d1e2028823">
         <Level1>planned queue</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PlanniPercen_ti">
      <Term>planning percentage</Term>
      <Definition>The planning percentage determines how a plan item is
		disaggregated over its subitems.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="387" height="229"
                      SRC="../images/tr_graph_tiglossary_03.gif"
                      alt="[...]"/>
         </Figure>
         <Paragraph>If the total demand for bicycles is disaggregated over the
		  various types of bicycles, the demand for racing bikes is 49% of the total
		  demand.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028828">
         <Level1>planning percentage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PriCalCod_ti">
      <Term>price calculation code</Term>
      <Definition>A specification of how a cost price, valuation price, or sales
		price is calculated. The code stores specific cost calculation data.</Definition>
      <SimpleSection>
         <Paragraph>The price calculation code that is defined in the Cost Price
		  Calculation (CPR) Parameters determines the standard cost price. Other price
		  calculation codes are used for simulation purposes. The price calculation code
		  for customized items is stored by project.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Specific operation rates</ListItem>
            <ListItem>Subcontracting rates</ListItem>
            <ListItem>Simulated purchase prices</ListItem>
            <ListItem>Surcharges</ListItem>
         </List>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028840">
         <Level1>price calculation code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100010">
      <Term>price list matrix</Term>
      <Definition>During the product configuration or product generation process
		price list matrices can be used to determine specific purchase and sales
		prices. Price list matrices can be used for recording prices, price factors,
		and also surcharge and discount percentages for a product variant.</Definition>
      <SimpleSection>
         <Paragraph>Tables with prices which are based on the values of a
		  physical quantity on the X-axis and the values of a physical quantity on the
		  Y-axis.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028861">
         <Level1>price list matrix</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="PriceVarian_ti">
      <Term>price variances</Term>
      <Definition>The price variance of a production order is the part of the
		production result created by differences between the estimated and actual price
		of an item or hour.</Definition>
      <SimpleSection>
         <Paragraph>The price variance indicates the effect of changing rates and
		  prices on the production result.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028869">
         <Level1>price variances</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000301">
      <Term>primary work center</Term>
      <Definition>A work center that does not have any physical resources and
		cannot be modeled in a routing. It is used for capacity planning and displays
		the total capacity requirements of the shared work centers. The work is
		actually carried out in shared secondary work centers, which can be in the same
		or a different logistical company than the primary work center. This enables
		you to plan and carry out work in several different logistical companies (if
		you define several secondary work centers) without having to use sales orders
		and purchase order.</Definition>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000300" role="glossary">shared work center</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2028877">
         <Level1>primary work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000125">
      <Term>process-triggered workflow</Term>
      <Definition>Workflow in which actions are triggered by an activity, or
		batch or activities, in another line station.</Definition>
      <Keyword type="glentry" order="d1e2028893">
         <Level1>process-triggered workflow</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000366">
      <Term>process variable</Term>
      <Definition>A setting or an input value related to a machine, a tool, or to
		process quality that is relevant to carry out an operation or an operation
		step. For example, cutting depth, cutting speed, and temperature.</Definition>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000365" role="glossary">operation step</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2028885">
         <Level1>process variable</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ProducExpiry_ti">
      <Term>product expiry date</Term>
      <Definition>The date that indicates an item's shelf life.</Definition>
      <Keyword type="glentry" order="d1e2028898">
         <Level1>product expiry date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ProducFamily_ti">
      <Term>product family</Term>
      <Definition>An item that represents a group of similar plan items (or
		families). The items are aggregated to give a more general plan than the one
		devised for individual items.</Definition>
      <SimpleSection>
         <Paragraph>The aggregation relationships specify the percentage of each
		  plan item in the product family.</Paragraph>
         <Paragraph>Use product families with care. A product family does not
		  normally have its own BOM or routing. However, you can create production orders
		  or sales orders for a product family, though this can lead to inconsistencies
		  in the planning.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028903">
         <Level1>product family</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ProducBom_ti">
      <Term>production BOM</Term>
      <Definition>An alternative term for the bill of material and is used to
		distinguish the Production BOM from the Engineering BOM.</Definition>
      <Keyword type="glentry" order="d1e2028943">
         <Level1>production BOM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ProdItem_ti">
      <Term>production item</Term>
      <Definition>An item that occurs in any module of <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>. It is a
		purchased, manufactured, or generic item that is used in a generic/production
		bill of material or in a generic/production routing.</Definition>
      <Keyword type="glentry" order="d1e2028948">
         <Level1>production item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000022">
      <Term>production order</Term>
      <Definition>An order to produce a specified quantity of an item on a
		specified delivery date.</Definition>
      <Keyword type="glentry" order="d1e2028956">
         <Level1>production order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000021">
      <Term>production order status</Term>
      <Definition>The status assigned to a production order, which indicates how
		far a production order has been processed. For example, <GUIRef href="/baanerp/tc/domains/osta#planned" role="option">Planned</GUIRef>, <GUIRef href="/baanerp/tc/domains/osta#printed" role="option">Documents Printed</GUIRef>, or <GUIRef href="/baanerp/tc/domains/osta#in.prod" role="option">Released</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e2028961">
         <Level1>production order status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="000000000000045">
      <Term>production rate</Term>
      <Definition>The quantity of items that is produced for a specific time
		unit.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The production rate can be, for example, 300 gallons per
		  hour, or 20 pieces per minute.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2028975">
         <Level1>production rate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000094">
      <Term>production schedule</Term>
      <Definition>A range of time to which production orders are assigned whose
		delivery dates fall in that period. The production orders can apply to an RPT
		item or a scheduling area.</Definition>
      <SimpleSection>
         <Paragraph>The period length can be defined by the user.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028985">
         <Level1>production schedule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ProducTime_ti">
      <Term>production time</Term>
      <Definition>The lead time required to carry out an operation.</Definition>
      <SimpleSection>
         <Paragraph>The production time includes the setup time and the run time.
		  The formula LN uses to
		  calculate the production time depends on whether or not the corresponding
		  operation has a fixed duration.</Paragraph>
         <List>
            <ListItem>
               <Paragraph>In case of a fixed duration, the formula LN applies to calculate
				the production time is:</Paragraph>
               <Formula space-and-orientation="indented-estimated">
                  <Paragraph>average setup time + cycle time </Paragraph>
               </Formula>
            </ListItem>
            <ListItem>
               <Paragraph>If the operation does not have a fixed duration, the
				formula LN applies is:</Paragraph>
               <Formula space-and-orientation="indented-estimated">
                  <Paragraph>average setup time + (cycle time * quantity planned input) / routing quantity </Paragraph>
               </Formula>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028993">
         <Level1>production time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ProducModel_ti">
      <Term>product model</Term>
      <Definition>Used in the definition of the product variant in making a sales
		order or quotations by translating the customer requirements into a product
		variant</Definition>
      <Keyword type="glentry" order="d1e2028913">
         <Level1>product model</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000074">
      <Term>product structure</Term>
      <Definition>The sequence of steps by which components are put together to
		form subassemblies, until the finished product is produced.</Definition>
      <SimpleSection>
         <Paragraph>The product structure is defined by a multilevel bill of
		  materials, sometimes in combination with routing data.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028918">
         <Level1>product structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="100014">
      <Term>product variant identification code</Term>
      <Definition>The unique identification of a product variant.</Definition>
      <SimpleSection>
         <Paragraph>Product variant codes make it possible to generate various
		  variants for a configurable item. Specially if a customer wants information
		  about options and prices without any obligation. In the implementation stage of
		  the product model, it is also used to execute system tests.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028926">
         <Level1>product variant identification code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000400">
      <Term>product variant structure</Term>
      <Definition>The structure of the product variant, which consists of one
		configurable end item that is related to several configurable sub-items and/or
		engineering modules.</Definition>
      <SimpleSection>
         <Paragraph>Configurable sub-items can also have their own configurable
		  sub-items and/or engineering modules. The configurable items represent the
		  product and the subassemblies of the product. The engineering modules are used
		  for assembly items and represent logical units that may not constitute
		  independent products, such as an electrical system. The product variant
		  structure is generated by LN and, dependent on the options, holds a part of the bill of
		  material.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2028934">
         <Level1>product variant structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000023">
      <Term>project</Term>
      <Definition>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
            <ListItem>Customized item data (BOMs and routings)</ListItem>
            <ListItem>Project planning (activity planning)</ListItem>
         </List>
         <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029014">
         <Level1>project</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ProjecActivi_ti">
      <Term>project activity</Term>
      <Definition>An activity that is relevant for the (rough) planning of a
		project. Activities are used to plan the rough material and capacity
		requirements of the project. Activities are also used to control the (final)
		assembly planning of the project.</Definition>
      <Keyword type="glentry" order="d1e2029032">
         <Level1>project activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000098">
      <Term>project item</Term>
      <Definition>An item that is produced or purchased for a particular sales
		order. The item's project provides a link with the sales order.</Definition>
      <SimpleSection>
         <Paragraph>A project item can be recognized by its item code. If a code
		  has been entered in the project segment, the item is a project item.</Paragraph>
         <Paragraph>Project items are created when you enter a sales order for an
		  item with an <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy.</Paragraph>
         <Paragraph>A project item can be customized to the specifications of a
		  customer, but it can also be a standard-to-order item.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029037">
         <Level1>project item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ProjecPart_ti">
      <Term>project part</Term>
      <Definition>A separate part of the project structure that is linked to a
		project. A project part is the basis that is used in order to determine the
		estimated costs of a project. Not to be confused with a subproject.</Definition>
      <Keyword type="glentry" order="d1e2029052">
         <Level1>project part</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ProjecStruct_ti">
      <Term>project structure</Term>
      <Definition>The project structure indicates the subprojects that belong to
		the main project. Project structures are especially important where there are
		extensive projects in an engineer-to-order situation.</Definition>
      <SimpleSection>
         <Paragraph>Project structures can be important for network planning.
		  This is because the start dates and finish dates of subprojects can depend on
		  the computed start dates and finish dates of the main project's activities.</Paragraph>
         <Paragraph>The costs of subprojects are aggregated to the relevant main
		  project in the project calculation.</Paragraph>
         <Paragraph>The project structure only applies to a project with a type
		  other than <GUIRef href="/baanerp/tc/domains/kopr#budget" role="option">Budget</GUIRef>.</Paragraph>
         <Paragraph>You can only delete a project structure if the main project
		  has the <GUIRef href="/baanerp/tp/domains/pdm.psta#free" role="option">Free</GUIRef> or <GUIRef href="/baanerp/tp/domains/pdm.psta#archived" role="option">Archived</GUIRef> status.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029058">
         <Level1>project structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000063">
      <Term>quantity extra</Term>
      <Definition>The product quantity that is assumed to have disappeared in the
		operation due to a limited yield, for example, the quantity lost through
		evaporation. This only applies if a yield has the type <GUIRef href="/baanerp/ti/domains/ydtp#continuous" role="option">Continuous</GUIRef>.</Definition>
      <SimpleSection>
         <Paragraph>The quantity is referred to as quantity extra, because an
		  extra quantity of the product must be planned to compensate for the loss.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029081">
         <Level1>quantity extra</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000041">
      <Term>quantity ordered</Term>
      <Definition>The quantity to be produced in a production order.</Definition>
      <Keyword type="glentry" order="d1e2029092">
         <Level1>quantity ordered</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="5.2b" ContextApps="tt" ID="100105">
      <Term>quantity planned input</Term>
      <Definition>The quantity that should be given as input to an operation to
		get the required output, taking into account scrap quantity and yield
		percentage, and quantities reported completed and rejected.</Definition>
      <SimpleSection>
         <Paragraph>The quantity planned input is the quantity of products on
		  which calculations of materials and hours are based.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029097">
         <Level1>quantity planned input</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="5.2b" ContextApps="tt" ID="100106">
      <Term>quantity planned output</Term>
      <Definition>The quantity of the product that you expect to come out of the
		operation, taking into account scrap quantity and yield percentage, and
		quantities reported completed and rejected.</Definition>
      <SimpleSection>
         <Paragraph>When LN creates a production order, the quantity planned output of the
		  last routing operation is set equal to the order quantity of the production
		  order. When the operation is not the last one, the quantity planned output is
		  equal to the quantity planned input of the next operation.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029105">
         <Level1>quantity planned output</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Question_ti">
      <Term>question</Term>
      <Definition>A question is used during the classification of, and search for
		items. The user must respond with an answer. In the <GUIRef href="/baanerp/ti/grt" role="module">Product Classification</GUIRef> module (GRT), LN asks
		the question with a question-and-answer type of user/system interaction.</Definition>
      <Keyword type="glentry" order="d1e2029113">
         <Level1>question</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000335">
      <Term>queue deviation</Term>
      <Definition>The difference between the planned queue and the actual queue
		on the generation date, that is actual queue minus planned queue.</Definition>
      <Keyword type="glentry" order="d1e2029121">
         <Level1>queue deviation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="000351">
      <Term>queue time</Term>
      <Definition>The amount of time that an order remains at a work center
		before setup or work is performed on it.</Definition>
      <Keyword type="glentry" order="d1e2029126">
         <Level1>queue time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000011">
      <Term>receipt note</Term>
      <Definition>An order document on which the completed quantities of the
		products can be recorded.</Definition>
      <Keyword type="glentry" order="d1e2029131">
         <Level1>receipt note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ReceivSite_ti">
      <Term>receiving site</Term>
      <Definition>The site (plant) on a receiving point of the supply chain.</Definition>
      <Keyword type="glentry" order="d1e2029136">
         <Level1>receiving site</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="100110">
      <Term>reference designator</Term>
      <Definition>Indicates the location to insert a component on an item, for
		example, where to mount an electronic component on a Printed Circuit Board.
		Reference designators are often used in electronics, and can originate from a
		Computer-Aided Design (CAD) station.</Definition>
      <Keyword type="glentry" order="d1e2029141">
         <Level1>reference designator</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="100013">
      <Term>reference type</Term>
      <Definition>A product variant may relate to a sales quotation, sales order,
		budget or project, or it may concern a standard variant.</Definition>
      <Keyword type="glentry" order="d1e2029147">
         <Level1>reference type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Refurbishing_ti">
      <Term>refurbishing</Term>
      <Definition>The renovation of a tool after a number of usages.</Definition>
      <Keyword type="glentry" order="d1e2029152">
         <Level1>refurbishing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000060">
      <Term>rejected item</Term>
      <Definition>A product that does not meet the quality standards set for the
		end product or subassembly. Also called a reject</Definition>
      <Keyword type="glentry" order="d1e2029157">
         <Level1>rejected item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="RepetiItem_ti">
      <Term>repetitive item</Term>
      <Definition>A repetitive item (also called RPT item) is a manufactured item
		whose production is controlled by schedules. A schedule contains multiple
		production orders that can be viewed, released, reported as complete, and so
		on, in one session.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A repetitive item usually has the following
			 characteristics:</ListIntro>
            <ListItem>It is produced in large quantities.</ListItem>
            <ListItem>It is subject to repetitive demand.</ListItem>
            <ListItem>The production is based on a rate.</ListItem>
            <ListItem>The lead time is short.</ListItem>
         </List>
         <Paragraph>Anonymous items as well as to-order items can be repetitive.
		  However, only to-order items that are <GUIRef href="/baanerp/tc/domains/cpge#sto" role="option">Standard-to-Order</GUIRef> can be used in RPT schedules. You cannot
		  use generic items or <GUIRef href="/baanerp/tc/domains/cpge#eto" role="option">Engineer-to-Order</GUIRef> items in an RPT schedule.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029162">
         <Level1>repetitive item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000048">
      <Term>requested offline date</Term>
      <Definition>The date when an assembly item must roll off the assembly line
		in order to meet the delivery date on the sales order line.</Definition>
      <Keyword type="glentry" order="d1e2029992">
         <Level1>requested offline date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="RescheMessag_ti">
      <Term>rescheduling message</Term>
      <Definition>An order signal that informs the planner whether an order must
		be expedited (rescheduled in), delayed (rescheduled out), or canceled.</Definition>
      <Keyword type="glentry" order="d1e2029187">
         <Level1>rescheduling message</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Result_ti">
      <Term>result</Term>
      <Definition>The financial results of, for example, a project or a
		production order. The results are reported in terms of variances. A variance is
		the difference between the expected (budgeted or planned) value and the actual
		value. You can distinguish between price variances, efficiency variances, and
		additional calculation-office variances.</Definition>
      <Keyword type="glentry" order="d1e2029192">
         <Level1>result</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ReturnValue_ti">
      <Term>return value</Term>
      <Definition>The code that is included in the classification code as a
		result of the selected answer.</Definition>
      <Keyword type="glentry" order="d1e2029197">
         <Level1>return value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Revision_ti">
      <Term>revision</Term>
      <Definition>A version or revised version of an engineering item (E-item) or
		a revision-controlled item, that is, an item linked to an E-item. Several
		revisions of an E-item can exist.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>E-item: Mountain bike E-MB01</Paragraph>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TH width="73" rowspan="1" colspan="1">Revision</TH>
                  <TH width="186" rowspan="1" colspan="1">Description</TH>
                  <TH width="112" rowspan="1" colspan="1">Status</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="73" rowspan="1" colspan="1">A1</TD>
                  <TD width="186" rowspan="1" colspan="1">Draft drawing of bike</TD>
                  <TD width="112" rowspan="1" colspan="1">Not released</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="73" rowspan="1" colspan="1">A2</TD>
                  <TD width="186" rowspan="1" colspan="1">Drawing of bike</TD>
                  <TD width="112" rowspan="1" colspan="1">Not released</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="73" rowspan="1" colspan="1">A3</TD>
                  <TD width="186" rowspan="1" colspan="1">Parent E-item of bike MB01</TD>
                  <TD width="112" rowspan="1" colspan="1">Released</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD width="73" rowspan="1" colspan="1">A4</TD>
                  <TD width="186" rowspan="1" colspan="1">Obsolete bike</TD>
                  <TD width="112" rowspan="1" colspan="1">Canceled</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2029202">
         <Level1>revision</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="RevisiContro_ti">
      <Term>revision-controlled</Term>
      <Definition>The revision-controlled items are items in continuous
		development. To identify the item's version, add a revision number to the item
		code.</Definition>
      <SimpleSection>
         <Paragraph>If a revision-controlled item is selected, the current
		  version is used. The obsolete versions are no longer manufactured and
		  prototypes are not sold yet.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029249">
         <Level1>revision-controlled</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000025">
      <Term>rework order</Term>
      <Definition>A production order to fix or upgrade an already produced or
		purchased item. The item that must be reworked is both input and output of the
		production order.</Definition>
      <Keyword type="glentry" order="d1e2029257">
         <Level1>rework order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000350">
      <Term>roll-off line</Term>
      <Definition>The assembly line where a product is completed.</Definition>
      <Keyword type="glentry" order="d1e2029262">
         <Level1>roll-off line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Routing_ti">
      <Term>routing</Term>
      <Definition>The sequence of operations required to manufacture an item.</Definition>
      <SimpleSection>
         <Paragraph>For each operation, the task, machine, and work center are
		  specified, as well as information about setup time and cycle time.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029268">
         <Level1>routing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000000000000024">
      <Term>routing code</Term>
      <Definition>A code that is linked to a routing. A routing code can be
		linked to a standard routing or an item-specific routing.</Definition>
      <Keyword type="glentry" order="d1e2029276">
         <Level1>routing code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000000000000030">
      <Term>routing quantity</Term>
      <Definition>The quantity of the manufactured item on which the routing is
		based. A routing quantity enables you to include very short operation times in
		the routing of an item.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="2">
               <TR no="1" isLast="false">
                  <TD width="127" rowspan="1" colspan="1">Routing quantity</TD>
                  <TD width="106" rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="2" isLast="true">
                  <TD width="127" rowspan="1" colspan="1">Cycle time</TD>
                  <TD width="106" rowspan="1" colspan="1">60 minutes</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>In a 60 minute time span, 100 items are produced.
		  Consequently, the operation time of one item is 0.6 minute.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2029281">
         <Level1>routing quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000012">
      <Term>routing sheet</Term>
      <Definition>An order document that lists all the operations required to
		manufacture an item, as well as the required tools. A routing sheet can also
		contain microrouting information that provides the operators with instructions
		or process information.</Definition>
      <Keyword type="glentry" order="d1e2029303">
         <Level1>routing sheet</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000316">
      <Term>rule</Term>
      <Definition>Logical condition determining action.</Definition>
      <Keyword type="glentry" order="d1e2029308">
         <Level1>rule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="6.0a" ContextApps="ti" ID="100107">
      <Term>run time</Term>
      <Definition>The time required to process a piece or lot at a specific
		operation.</Definition>
      <SimpleSection>
         <Paragraph>Run time does not include setup time.</Paragraph>
         <Formula space-and-orientation="indented-estimated">
            <Paragraph>run time = production time - setup time</Paragraph>
         </Formula>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029313">
         <Level1>run time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000422">
      <Term>safety time</Term>
      <Definition>The time that you can add to the normal lead time to protect
		delivery of goods against fluctuations in the lead time so that an order can be
		completed before the order's real need date.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The duration of the linked activity is 30 days, and the
		  earliest finish date of the activity is Jan, 30. If you specify 10% safety
		  time, then GOP will plan the material on 3 working days before Januari,
		  30.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2030015">
         <Level1>safety time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="100012">
      <Term>sales price structure</Term>
      <Definition>Gives insight into the structure and composition of the sales
		prices for product variants.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The sales price structure:</ListIntro>
            <ListItem>Is used when calculating the sales price for a product
			 variant on a sales order or sales quotation.</ListItem>
            <ListItem>Provides insight into the price structure and can be
			 displayed in the <GUIRef href="/baanerp/ti/pcf/tipcf5530m000" role="session">Product Variant Sales Price Structure (tipcf5530m000)</GUIRef> session. In addition to or instead of the product
			 variant options, it can be printed on sales order documents.</ListItem>
         </List>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Product variant options show the technical aspects of a
		  particular product variant, whereas the sales price structure is a commercial
		  representation of the chosen product variant options.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2029324">
         <Level1>sales price structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000013">
      <Term>sawing list</Term>
      <Definition>An order document that lists the materials that must be
		obtained to saw a specified length of material from a large piece, for example,
		a pipe or a bar.</Definition>
      <Keyword type="glentry" order="d1e2029346">
         <Level1>sawing list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ScheduArea_ti">
      <Term>scheduling area</Term>
      <Definition>A physical area or part of the production line for which a
		production schedule has been defined. Scheduling areas are defined for
		repetitive items.</Definition>
      <Keyword type="glentry" order="d1e2029351">
         <Level1>scheduling area</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Scrap_ti">
      <Term>scrap</Term>
      <Definition>Unusable material or rejects of intermediate products, for
		example, because of faulty components, or products lost in cutting or sawing
		operations. The gross material requirements and/or an operation's input
		quantity must be increased to account for anticipated scrap.</Definition>
      <SimpleSection>
         <Paragraph>In the BOM, you can define scrap as a percentage of the net
		  material requirements, which is the scrap factor, and as a fixed quantity,
		  which is the scrap quantity. A scrap quantity is mostly used to define the
		  amount of material that is lost every time when you start producing, for
		  example, to test the equipment.</Paragraph>
         <Paragraph>For an operation, you can only define the scrap as a fixed
		  quantity.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029356">
         <Level1>scrap</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000302">
      <Term>secondary work center</Term>
      <Definition>An operational work center where the work is actually carried
		out. The secondary work center can be in a different logistical company as the
		primary work center to which it is linked. This enables you to plan the work to
		a work center in your own logistical company, but have it carried out in a
		different logistical company without having to use sales orders and purchase
		orders. For each primary work center, you can have several secondary work
		centers. See shared work center.</Definition>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000300" role="glossary">shared work center</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2029366">
         <Level1>secondary work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000408">
      <Term>segment schedule</Term>
      <Definition>A schedule that indicates when assembly parts are required.
		Based on the offline date of the assembly order, and the segment for which the
		assembly parts are required, the segment schedule indicates when the parts must
		be delivered to the line. Segment schedules are used for a rough calculation of
		assembly part requirements, when high volumes are processed, and the
		performance of the calculation is critical.</Definition>
      <Keyword type="glentry" order="d1e2029375">
         <Level1>segment schedule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000061">
      <Term>semifinished item</Term>
      <Definition>The product of a phantom routing, which is passed on to the
		next operation in the routing network.</Definition>
      <Keyword type="glentry" order="d1e2029380">
         <Level1>semifinished item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B5.2b" ContextApps="ti" ID="100103">
      <Term>setup class</Term>
      <Definition>A type of item characteristic that indicates how a machine must
		be set up to produce the item. The setup class determines the changeover time
		for a machine or a tool between two operations. A setup class consists of a
		series of setup states. In a matrix of setup states the specific changeover
		times can be defined.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Examples of setup classes are color and thickness. If your
		  setup class is color, the setup states can be red, green, white, black, and so
		  on.</Paragraph>
      </ExampleSection>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#100104" role="glossary">setup state</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2029385">
         <Level1>setup class</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B5.2b" ContextApps="ti" ID="100104">
      <Term>setup state</Term>
      <Definition>An item's characteristic that is linked to an operation.
		Depending on the setup states of two successive operations, a machine's
		changeover takes longer or less long. A series of setup states form a setup
		class.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>If your setup class is color, examples of setup states are
		  red, green, white, black, and so on.</Paragraph>
      </ExampleSection>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#100103" role="glossary">setup class</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2029398">
         <Level1>setup state</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000300">
      <Term>shared work center</Term>
      <Definition>A work center that can be used across multiple production sites
		and that has a relationship with a work center in the same or a different
		logistic company. You can use this relationship to plan work in one (or more)
		logistic companies that is actually carried out in a different company. If this
		relationship is defined, you need not use sales orders and purchase orders to
		transfer work between work centers in different companies. The hypothetical
		work center without physical resources, which is used for capacity planning, is
		the primary work center, and the operational work centers where the work is
		carried out, are the secondary work centers.</Definition>
      <CrossRef>
         <Link href="/baanerp/ti/glossary/glossary#000301" role="glossary">primary work center</Link>, <Link href="/baanerp/ti/glossary/glossary#000302" role="glossary">secondary work center</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2029411">
         <Level1>shared work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="WIPWareho_ti">
      <Term>shop floor warehouse</Term>
      <Definition>A warehouse that stores intermediate inventory in order to
		supply work centers. A shop floor warehouse is linked to one or more work
		centers and can be supplied with goods by means of replenishment orders, or by
		pull-based material supply.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The pull-based material supply methods are:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#batch" role="option">Order Controlled/Batch</GUIRef> (only applicable in <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>).</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/sups#sils" role="option">Order Controlled/SILS</GUIRef> (only applicable in <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>).</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/sups#single" role="option">Order Controlled/Single</GUIRef> (only applicable in <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef>).</ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#kanban" role="option">KANBAN</GUIRef>.</ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#tpop" role="option">Time-Phased Order Point</GUIRef>.</ListItem>
         </List>
         <Paragraph>The items stored in the shop-floor warehouse are not part of
		  the work in process (WIP). When items leave the shop floor warehouse for use in
		  production, their value is added to the WIP.</Paragraph>
      </SimpleSection>
      <Synonym>WIP warehouse</Synonym>
      <Keyword type="glentry" order="d1e2029422">
         <Level1>shop floor warehouse</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2029422">
         <Level1>WIP warehouse</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000133">
      <Term>shrinkage</Term>
      <Definition>The percentage of material lost due to a continuous process,
		such as evaporation or absorption.</Definition>
      <Keyword type="glentry" order="d1e2029467">
         <Level1>shrinkage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="SimPurPri_ti">
      <Term>simulated purchase prices</Term>
      <Definition>A simulated purchase price can be used to experiment with
		purchase prices and to compute the results.</Definition>
      <Keyword type="glentry" order="d1e2029472">
         <Level1>simulated purchase prices</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="SimulaN_ti">
      <Term>simulation</Term>
      <Definition>The process of doing calculations using simulated figures
		instead of the actual ones to see what would be the result if certain figures
		were changed. Opposite term is actual or operational.</Definition>
      <Keyword type="glentry" order="d1e2029477">
         <Level1>simulation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="SingleBomTi_ti">
      <Term>single-level BOM</Term>
      <Definition>An overview of components that are directly used in a parent
		item. A single-level BOM shows only the relationship one level down.</Definition>
      <Keyword type="glentry" order="d1e2029482">
         <Level1>single-level BOM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="SlackTime_ti">
      <Term>slack time</Term>
      <Definition>The time between the queue start date of the next operation and
		the setup + run start date of the next operation, calculated by LN.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Difference between the slack time and the queue time on the
			 next operation can occur if:</ListIntro>
            <ListItem>The calendars of the work centers differ.</ListItem>
            <ListItem>You apply a transfer batch quantity.</ListItem>
         </List>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Negative slack on the last operation can occur if the planned
		  delivery date falls after the requested delivery date.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2029487">
         <Level1>slack time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000403">
      <Term>solve</Term>
      <Definition>In <GUIRef href="/baanerp/ti/apl" role="module">Assembly Planning</GUIRef>, the process to determine the specific generic items and
		engineering modules that make up a generic end item. The result of the solving
		process is the product variant structure. Generic items and engineering modules
		are stored in a generic bill of materials (BOM). The solving process selects
		generic items and engineering modules from the generic BOM based on effective
		dates and unit effectivity exceptions.</Definition>
      <Keyword type="glentry" order="d1e2029507">
         <Level1>solve</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000303">
      <Term>standard configuration</Term>
      <Definition>If an object (for example, a BOM line or a routing line) has a
		standard configuration, that object is selected when you are not using <Link href="/baanerp/tc/glossary/glossary#000306" role="glossary">unit effectivity</Link>.</Definition>
      <Keyword type="glentry" order="d1e2029515">
         <Level1>standard configuration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="StandaCostPr_ti">
      <Term>standard cost price</Term>
      <Definition>The sum of the following item costs as calculated by the
		standard price calculation code:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Material costs</ListItem>
            <ListItem>Operational costs</ListItem>
            <ListItem>Surcharges</ListItem>
         </List>
         <Paragraph>Prices that are calculated against other price simulation
		  codes are simulated prices. The cost price is used for simulation purposes and
		  in transactions when no actual price is available.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029523">
         <Level1>standard cost price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="StandaItem_ti">
      <Term>standard item</Term>
      <Definition>A purchased item, material, subassembly, or finished product
		that is normally available.</Definition>
      <SimpleSection>
         <Paragraph>All items that are not built according to customer
		  specification for a specific project are defined as standard items. Opposite
		  term is customized item.</Paragraph>
         <List>
            <ListIntro>A standard item can have the following order policies:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029538">
         <Level1>standard item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000026">
      <Term>standard-to-order (STO)</Term>
      <Definition>The production of non-customized items after receiving a
		customer order.</Definition>
      <Keyword type="glentry" order="d1e2029555">
         <Level1>standard-to-order (STO)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000000000000026">
      <Term>subassembly</Term>
      <Definition>An intermediary product in a production process that is not
		stored or sold as an end product, but that is passed on to the next operation.</Definition>
      <SimpleSection>
         <Paragraph>For subcontracting purposes, a manufacturer can send a
		  subassembly to a subcontractor to carry out work on the subassembly. This
		  subassembly has its own item code defined in the <GUIRef href="/baanerp/tc/ibd" role="module">Item Base Data</GUIRef>.</Paragraph>
         <Paragraph>After work is finished, the subcontractor sends the
		  subassembly back to the manufacturer. Also this reworked subassembly has its
		  own item code defined in the <GUIRef href="/baanerp/tc/ibd" role="module">Item Base Data</GUIRef>.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029565">
         <Level1>subassembly</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000044">
      <Term>subcontracting</Term>
      <Definition>Allowing another company (the subcontractor) to carry out work
		on an item. This work can concern the entire production process, or only one or
		more operations in the production process.</Definition>
      <Keyword type="glentry" order="d1e2029581">
         <Level1>subcontracting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000014">
      <Term>subcontracting note</Term>
      <Definition>An external order document that specifies a subcontracted
		operation and the corresponding data, such as the subcontractor, tasks,
		routing, and required materials.</Definition>
      <Keyword type="glentry" order="d1e2029586">
         <Level1>subcontracting note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000413">
      <Term>subcontracting purchase order</Term>
      <Definition>In LN,
		subcontracting is considered as purchasing a service from a subcontractor.
		Therefore, when subcontracting, a subcontracting purchase order is generated to
		record the subcontracted operation(s) and the associated costs.</Definition>
      <Keyword type="glentry" order="d1e2029591">
         <Level1>subcontracting purchase order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="SubcRate_ti">
      <Term>subcontracting rate</Term>
      <Definition>The rate that is used to calculate the subcontracting costs.
		How LN uses the
		subcontracting rate in the calculation depends on the calculation
		method:</Definition>
      <SimpleSection>
         <List>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/cmsc#fix.amount" role="option">Fixed Amount by Product</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/cmsc#oper.rate" role="option">Operation Rate</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/cmsc#man.hr.rate" role="option">Man Hour Rate</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/cmsc#mach.hr.rate" role="option">Machine Hour Rate</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029602">
         <Level1>subcontracting rate</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000000000000050">
      <Term>subcontracting rate factor</Term>
      <Definition>The subcontracting rate factor, together with the
		subcontracting base rate, determines the cost of subcontracting.</Definition>
      <Keyword type="glentry" order="d1e2029596">
         <Level1>subcontracting rate factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Subitem_ti">
      <Term>sub-item</Term>
      <Definition>A means to further classify items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A sub-item can either be:</ListIntro>
            <ListItem>A component item used in a bill of material.</ListItem>
            <ListItem>A material used in a formula.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029621">
         <Level1>sub-item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="SubPlanItem_ti">
      <Term>sub plan item</Term>
      <Definition>The identification of a plan item at a lower plan level.</Definition>
      <Keyword type="glentry" order="d1e2029560">
         <Level1>sub plan item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000070">
      <Term>subsequent delivery</Term>
      <Definition>The quantity of the material that must be issued for the
		production order at a future date or time.</Definition>
      <Keyword type="glentry" order="d1e2029634">
         <Level1>subsequent delivery</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="SummarBomTi_ti">
      <Term>summarized BOM</Term>
      <Definition>A form of multilevel bill of material that lists all the parts
		and the quantities required in a BOM. Unlike the full multilevel bill of
		material, a summarized BOM does not list the levels of manufacture, and lists a
		component only once for the total quantity used. Phantom items are not listed.</Definition>
      <SimpleSection>
         <Paragraph>A summarized BOM only contains purchased items, because all
		  the manufactured items are made from purchased items.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029639">
         <Level1>summarized BOM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000097">
      <Term>supplying assembly line</Term>
      <Definition>An assembly line which produces subassemblies that are used in
		another assembly line. It may additionally produce items that are not used on
		any assembly line. An assembly line is a set of consecutive line stations where
		FAS (Final Assembly Schedule) items (and sometimes other item types) are
		manufactured.</Definition>
      <Keyword type="glentry" order="d1e2029652">
         <Level1>supplying assembly line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000308">
      <Term>supply in line sequence</Term>
      <Definition>The supply of assembly parts or assembly kits to a shop floor
		warehouse, so that they are delivered to the line station in the same sequence
		as the assembly orders.</Definition>
      <Keyword type="glentry" order="d1e2029647">
         <Level1>supply in line sequence</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000043">
      <Term>surcharge</Term>
      <Definition>The indirect costs of an item, for example, overhead costs,
		storage costs, handling costs, and machine-maintenance costs. Surcharges can be
		defined as a percentage or as a fixed amount and can contribute to fixed and
		variable costs.</Definition>
      <Keyword type="glentry" order="d1e2029657">
         <Level1>surcharge</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000341">
      <Term>surcharge base</Term>
      <Definition>A set of cost components to which an item surcharge is applied.</Definition>
      <Keyword type="glentry" order="d1e2029662">
         <Level1>surcharge base</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000325">
      <Term>target period</Term>
      <Definition>A user-defined period of whole numbers of days or weeks for
		which input/output data is generated.</Definition>
      <Keyword type="glentry" order="d1e2029667">
         <Level1>target period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Task_ti">
      <Term>task</Term>
      <Definition>An activity to manufacture or repair an item. For example,
		sawing, drilling, or painting.</Definition>
      <SimpleSection>
         <Paragraph>A task is carried out on a work center, and can be related to
		  a machine.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029672">
         <Level1>task</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Test_ti">
      <Term>test</Term>
      <Definition>An examination or check done on a characteristic. You can link
		one or more tests to a characteristic.</Definition>
      <Keyword type="glentry" order="d1e2029680">
         <Level1>test</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000407">
      <Term>time fence</Term>
      <Definition>A reference date against which processes or statuses are
		evaluated.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>The assembly order time fence on an assembly line defines the
		  end date of the period for which assembly orders must be created. If this time
		  fence is 100 days, assembly orders must be created for product variants whose
		  planned offline date is between now and 100 days. Similarly, a time fence can
		  define when line station orders must be frozen, updated, and so on.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2029686">
         <Level1>time fence</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="TimeUnit_ti">
      <Term>time unit</Term>
      <Definition>The unit that is used to specify the physical quantity time.</Definition>
      <Keyword type="glentry" order="d1e2029696">
         <Level1>time unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Tool_ti">
      <Term>tool</Term>
      <Definition>A reusable resource that is used to perform manufacturing
		and/or service tasks. When you have finished with the tool, it is returned to
		inventory to be used for the next requirement. The tool's life is reduced each
		time you use it.</Definition>
      <SimpleSection>
         <Paragraph>A tool can be identified in LN as a unique
		  combination of tool type and tool serial number.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029701">
         <Level1>tool</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Component_ti">
      <Term>tool component</Term>
      <Definition>A part of an assembled group of tool types.</Definition>
      <Keyword type="glentry" order="d1e2029709">
         <Level1>tool component</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ToolKit_ti">
      <Term>tool kit</Term>
      <Definition>A set of specific tools required to perform a single task. A
		tool kit can be linked to a machine, a task, and/or a routing operation to
		specify the tool(s) required to perform the task and/or operation.</Definition>
      <Keyword type="glentry" order="d1e2029714">
         <Level1>tool kit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="Toolslife_ti">
      <Term>tool life</Term>
      <Definition>The capacity of the tool expressed in the number of hours or
		times it can be used.</Definition>
      <Keyword type="glentry" order="d1e2029719">
         <Level1>tool life</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ToolNumber_ti">
      <Term>tool number</Term>
      <Definition>A number to identify a tool. The combination of a tool type,
		for example, hammer, and a tool serial number, for example, 1, is unique, and
		identifies a tool in LN.</Definition>
      <Keyword type="glentry" order="d1e2029724">
         <Level1>tool number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000051">
      <Term>tool request</Term>
      <Definition>A tool request is created when a tool is required. One request
		is created for each tool/work center combination.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A tool request displays data relating to:</ListIntro>
            <ListItem>Request number.</ListItem>
            <ListItem>Tool type</ListItem>
            <ListItem>Tool serial number</ListItem>
            <ListItem>Work center / service center</ListItem>
            <ListItem>Request status</ListItem>
         </List>
         <Paragraph>How, where, and when the tool is used in the work center is
		  determined by the tool request details, which can be found in the <GUIRef href="/baanerp/ti/trp/titrp0516m000" role="session">Tool Request - Lines (titrp0516m000)</GUIRef> session.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029729">
         <Level1>tool request</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000052">
      <Term>tool request details</Term>
      <Definition>The tool request specifies at which work center or service
		center the tool is used. In addition, the tool request details specify when,
		where, and how the tool is used at the work center. The following production
		order details are displayed:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Request number</ListItem>
            <ListItem>Request date/time</ListItem>
            <ListItem>Order type</ListItem>
            <ListItem>Order number</ListItem>
            <ListItem>Operation</ListItem>
            <ListItem>Line number</ListItem>
            <ListItem>Activity line</ListItem>
            <ListItem>Presence of the tool at the work/service center</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029753">
         <Level1>tool request details</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000137">
      <Term>tool serial number</Term>
      <Definition>A number to identify a tool. The combination of a tool type,
		for example, hammer, and a tool serial number, for example, 1, results in a
		unique identification of a tool in LN.</Definition>
      <Keyword type="glentry" order="d1e2029776">
         <Level1>tool serial number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="ToolType_ti">
      <Term>tool type</Term>
      <Definition>The tool type is the first level that is used to identify the
		tool in the coding system for tools.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Some examples of tool types are:</ListIntro>
            <ListItem>Hammer</ListItem>
            <ListItem>Screwdriver</ListItem>
            <ListItem>Wheelbarrows</ListItem>
         </List>
         <Paragraph>Hammer 1, screwdriver 2 and wheelbarrow 3 are examples of
		  tool types in combination with a tool serial number, and represent unique
		  tools.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029781">
         <Level1>tool type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000360">
      <Term>transfer batch quantity</Term>
      <Definition>The quantity or percentage of items for which an operation must
		be finished before you can start with the next operation. Even though an
		operation is not yet finished for all items in a production order, you can
		start the next operation for the items that are already finished.</Definition>
      <SimpleSection>
         <Paragraph>In a production environment where kanban is used, the
		  transfer batch quantity equals the kanban size (which is the standard
		  container, or the standard lot size).</Paragraph>
         <Paragraph>The transfer batch quantity replaces the previously used
		  concept of overlap percentage on operation.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029799">
         <Level1>transfer batch quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000375">
      <Term>use-up material</Term>
      <Definition>A material that has been replaced by another item in all BOMs.</Definition>
      <SimpleSection>
         <Paragraph>After the use-up material's last allowed order date elapses,
		  any remaining stock is used up; then, the replacement material will be used.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029809">
         <Level1>use-up material</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000317">
      <Term>utilization</Term>
      <Definition>The percent of a resource (for example, hours capacity) that is
		used in production.</Definition>
      <Keyword type="glentry" order="d1e2029817">
         <Level1>utilization</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000135">
      <Term>valid</Term>
      <Definition>You can use a specific entity. For example, if a date is
		between an effective date and an expiry date, the date is valid, and the entity
		can be used.</Definition>
      <Keyword type="glentry" order="d1e2029822">
         <Level1>valid</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000000000000058">
      <Term>validity</Term>
      <Definition>The operating period between the effective date and the expiry
		date.</Definition>
      <Keyword type="glentry" order="d1e2029827">
         <Level1>validity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="ValuatPrice_ti">
      <Term>valuation price</Term>
      <Definition>The actual price of an item, which is used in all financial
		transactions that involve the item.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The transactions include:</ListIntro>
            <ListItem>Cost price of goods sold</ListItem>
            <ListItem>Inventory transfer</ListItem>
            <ListItem>Issue to work-in-process value</ListItem>
         </List>
         <Paragraph>The valuation price must be distinguished from the cost
		  price, which is used for other purposes.</Paragraph>
         <Paragraph>The valuation price is calculated by using one of the actual
		  costing methods (LIFO, FIFO, MAUC and Lot costing), or by using a fixed
		  transfer pricing (FTP) method.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029832">
         <Level1>valuation price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000340">
      <Term>variable costs</Term>
      <Definition>Expenses that vary with the production volume. The materials
		needed for the production of end items, are always variable costs. Operation
		rates and surcharges can be attributed to the variable costs or the fixed
		costs.</Definition>
      <Antonym>
         <Link href="/baanerp/ti/glossary/glossary#000075" role="glossary">fixed costs</Link>
      </Antonym>
      <Keyword type="glentry" order="d1e2029851">
         <Level1>variable costs</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2029851">
         <Level1>fixed costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="ti" ID="000352">
      <Term>wait time</Term>
      <Definition>The time that an order remains at a work center after an
		operation is completed until it is moved to the next operation.</Definition>
      <SimpleSection>
         <Paragraph>LN does not plan wait times according to a specific calendar. Planning of the wait
		  time is based on a 7 * 24 hours week schedule.</Paragraph>
         <Paragraph>A typical example is the time required for drying after the
		  application of paint.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029859">
         <Level1>wait time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000077">
      <Term>warehouse transfer</Term>
      <Definition>A warehousing order to move an item between warehouses.</Definition>
      <SimpleSection>
         <Paragraph>A warehouse transfer consists of a warehousing order of
		  inventory transaction type <GUIRef href="/baanerp/tc/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029869">
         <Level1>warehouse transfer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2029927">
      <Term>WIP</Term>
      <Definition>See: <Link href="#000031" role="internal">work in process</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000059">
      <Term>WIP transaction</Term>
      <Definition>Any action that affects the work in process (WIP) of a
		production order or work center.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>WIP transactions can be any of the following:</ListIntro>
            <ListItem>Issue of materials for a production order.</ListItem>
            <ListItem>Booking of hours on a production order.</ListItem>
            <ListItem>Delivery into inventory of finished products.</ListItem>
            <ListItem>WIP transfers between work centers.</ListItem>
            <ListItem>Application of a surcharge.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029880">
         <Level1>WIP transaction</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000054">
      <Term>WIP transfer</Term>
      <Definition>The transfer of the value of the work in process from one work
		center to the next, in accordance with a physical transfer of a subassembly to
		the work center where the next operation must be performed.</Definition>
      <Keyword type="glentry" order="d1e2029899">
         <Level1>WIP transfer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2029465">
      <Term>WIP warehouse</Term>
      <Definition>See: <Link href="#WIPWareho_ti" role="internal">shop floor warehouse</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="ti" ID="000000000000036">
      <Term>work center</Term>
      <Definition>A specific production area consisting of one or more people
		and/or machines with identical capabilities, that can be considered as one unit
		for purposes of the capacity requirement planning and detailed scheduling.</Definition>
      <Keyword type="glentry" order="d1e2029905">
         <Level1>work center</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000031">
      <Term>work in process</Term>
      <Definition>The unfinished goods in a production process including issued
		materials, or the value assigned to these goods. These items are not yet
		completed but either just being fabricated or waiting in a queue for further
		processing or in a buffer storage.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>LN distinguishes two types of WIP:</ListIntro>
            <ListItemHead>Production WIP</ListItemHead>
            <ListItem>The materials, hours, and other production resources that are
			 consumed on the shop floor to manufacture items that are not yet received in
			 the warehouse. When the goods are received in the warehouse, the WIP decreases.</ListItem>
            <ListItemHead>PCS WIP</ListItemHead>
            <ListItem>The amount of materials, hours, and other costs related to
			 orders that are linked to a specific PCS project. When an order is invoiced,
			 the WIP decreases.</ListItem>
         </List>
      </SimpleSection>
      <Abbreviation>WIP</Abbreviation>
      <Keyword type="glentry" order="d1e2029910">
         <Level1>work in process</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2029910">
         <Level1>WIP</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="Yield_ti">
      <Term>yield</Term>
      <Definition>The usable output from a operation expressed as a percentage of
		its input.</Definition>
      <SimpleSection>
         <Paragraph> Example 1: An operation in the production
		  process for light bulbs has a yield of 98%. So, out of every 100 light bulbs
		  produced, 98 are good on average. The remaining light bulbs are faulty, and
		  will therefore be rejected.</Paragraph>
         <Paragraph> Example 2: Steel wires are twisted together to
		  produce a steel cable. Due to the twisting, the cable is 10% shorter than the
		  wires from which it is produced. So, the yield is set to 90%.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029929">
         <Level1>yield</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="ti" ID="000062">
      <Term>yield type</Term>
      <Definition>Determines if and how lost products come out of production if
		the yield percentage is below 100%.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Two yield types are available:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/ti/domains/ydtp#discrete" role="option">Discrete</GUIRef>
            </ListItemHead>
            <ListItem>Lost products come out of production as rejected
			 products.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/ti/domains/ydtp#continuous" role="option">Continuous</GUIRef>
            </ListItemHead>
            <ListItem>Lost products disappear completely, for example, through
			 evaporation.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2029939">
         <Level1>yield type</Level1>
      </Keyword>
   </GlossaryEntry>
</Glossary>