<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/000350" xml:lang="en">
   <Header>
      <Title>Backgrounds on setup classes and setup states in LN</Title>
      <Keyword type="header" order="d1e2082957">
         <Level1>setup class</Level1>
      </Keyword>
      <Keyword type="header" order="d1e2082960">
         <Level1>setup state</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>An important means to save time during production is to cut down
		on setup times. The benefits of saving setup times during production can be
		enormous. Moreover, saving setup times as much as possible reflects the
		situation on the shop floor in reality. <Link href="/baanerp/ti/glossary/glossary#100103" role="glossary">Setup classes</Link> and <Link href="/baanerp/ti/glossary/glossary#100104" role="glossary">setup states</Link> are used in LN to achieve a cutdown on setup times.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>In short, setup classes and setup states enable you to group
		different items from different production orders based on characteristics that
		they have in common. The sequence in which production orders are handled is
		influenced so that an operation on the group of items can be carried out
		without changing the machine's setup.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <Paragraph>If you have defined <Link href="/baanerp/ti/glossary/glossary#GeneriItem_ti" role="glossary">generic items</Link> with <Link href="/baanerp/ti/glossary/glossary#100000" role="glossary">features</Link> and <Link href="/baanerp/ti/glossary/glossary#100001" role="glossary">options</Link>, you can generate a setup class for each feature
		and a setup state for each option. For more information, refer to <Link href="/baanerp/ti/onlinemanual/000358" role="manual">To define setup classes and setup states for product features</Link>.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <Paragraph>You can use setup states to plan with <Link href="/baanerp/ti/glossary/glossary#000377" role="glossary" Update="No">order blocks</Link>. Order blocks are sets of
		production orders with common setup states.</Paragraph>
   </GeneralSection>
   <ExampleSection>
      <SectionTitle>Example</SectionTitle>
      <Paragraph>If you want to spray-paint an item green during a specific
		operation, you must set up the required machine, which takes some time. If you
		subsequently use the same machine to spray-paint an item red, the machine must
		be set up again for the red paint. To reduce setup times, you can best schedule
		successively all production orders in which items are spray-painted red. The
		orders that involve green items can also be scheduled successively.</Paragraph>
      <Paragraph>Moreover, to set up a machine from using green paint to using
		red paint could cost more time than a machine’s changeover from red to green.
		In this example it means that you can better first process the red orders,
		after which you can process the green orders.</Paragraph>
   </ExampleSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000351" role="manual">To define setup classes and setup states</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000355" role="manual">Order-block planning</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>