<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ff/manufacturing/manufacturing_ff_asc" xml:lang="en">
   <Header>
      <Title>Assembly Control</Title>
      <Keyword type="header" order="d1e431664">
         <Level1>Functions and features</Level1>
         <Level2>assembly control</Level2>
      </Keyword>
      <Keyword type="header" order="d1e431669">
         <Level1>Assembly Control</Level1>
         <Level2>functions and features</Level2>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>
         <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> is intended for use by companies that produce many variants of
		complex products in a flow assembly line, although it can also be used in
		low-volume assembly environments if order-specific transaction handling is
		used.</Paragraph>
   </AimSection>
   <GeneralSection>
      <SectionTitle>Line station variants</SectionTitle>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Clustered Line Station Orders</SectionTitle>
      <GeneralSection ID="/baanerp/ti/onlinemanual/000302#clustered_lso">
         <SectionTitle>Clustered line station order</SectionTitle>
         <Paragraph>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.</Paragraph>
         <Paragraph>In Assembly Control, transactions can be carried out per line
		  station and per period, instead of per order. ERP Enterprise 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>
         <Paragraph>CLSOs are used in
		  assembly part allocation and in backflushing to combine materials for a
		  line-station order (for a day).</Paragraph>
         <List>
            <ListTitle>Parameters</ListTitle>
            <ListIntro>The <GUIRef href="/baanerp/ti/asc/tiasc0100m000#tiasc000.trpr" role="manual">Transaction Processing</GUIRef> parameter determines the use
			 of CLSOs. This parameter is defined in the <Link href="/baanerp/ti/asc/tiasc0100m000" role="session">Assembly Control Parameters (tiasc0100m000)</Link> session, and can have the following values:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/ti/domains/asc.trpr#line" role="option">Line Station Based</GUIRef> Only one
			 CLSO is created for each line station each day.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/ti/domains/asc.trpr#order" role="option">Order Based</GUIRef> One CLSO is
			 created for each assembly order.</ListItem>
         </List>
         <Paragraph>CLSOs are used in
		  assembly part allocation and in backflushing to combine materials for a line
		  station order. A CLSO covers an entire day, in line-station based transaction
		  processing, or an assembly order, in order-based transaction processing. The
		  data for each time bucket is kept seperate. In line-station based transaction
		  processing, each time bucket results in a separated warehousing order line for
		  the assembly part allocation. In order-based transaction processing, an
		  individual warehouse order is generated for each CLSO.</Paragraph>
         <List>
            <ListIntro>Through the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu you can perform the following
			 actions:</ListIntro>
            <ListItem>Change the status of a
			 CLSO from <GUIRef href="/baanerp/ti/domains/asc.alst#closed" role="option">Closed</GUIRef> to <GUIRef href="/baanerp/ti/domains/asc.alst#open" role="option">Open</GUIRef>.</ListItem>
            <ListItem>Start the <Link href="/baanerp/ti/asc/tiasc7140m000" role="session">Clustered Line Station Order - Assembly Part Requirements (tiasc7140m000)</Link> session to view the assembly part
			 requirements for each CLSO.</ListItem>
         </List>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Partial freeze</SectionTitle>
      <Paragraph>Assembly orders can be partially frozen, this means that
		depending on the position of the assembly order in the process, some parts of
		the assembly order will no longer be refreshed. The frozen parts of the order
		can still be manually changed.</Paragraph>
      <Paragraph>Other parts can still be refreshed by linking a time fence to a
		line segment.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Multisite assembly</SectionTitle>
      <Paragraph>In many mixed-model-flow companies, the assembly process is
		performed over multiple companies that have their own logistical data set.
		These companies can have several assembly lines in different logistical
		companies. A generic subitem is assembled on a supplying line and supplied to
		the main line on which the final end item is assembled.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Line Sequencing</SectionTitle>
      <AimSection ID="/baanerp/ti/onlinemanual/000323#line_sequence_rules_aim">
         <Paragraph>Assembly orders generated by APL can be sequenced by using the
		sequencing engine, resulting in a line mix and line sequence. During this
		sequencing process, line rules are taken in to account like clustering assembly
		orders based on items characteristics, or blocking assembly orders based on
		capacity rules.</Paragraph>
      </AimSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Manual change of the sequence</SectionTitle>
      <Paragraph>The sequence is recorded in an easy to use control panel which
		can be used to manually change the generated sequence. Orders can be moved to
		another position in the line or the position of thwo orders can be
		exchanged.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Inventory check</SectionTitle>
      <Paragraph>An optional inventory check can be performed. A list of problem
		parts and orders having shortages can be displayed.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Work instructions</SectionTitle>
      <Paragraph>For each operation work instructions can be printed. This is
		handled through process-triggered workflow. The user can partially determine
		what kind of information is printed on these instructions.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Material supply</SectionTitle>
      <List>
         <ListIntro>ASC distinguishes internal and external supply:</ListIntro>
         <ListItem>Internal supply is the movement of assembly parts from a main
		  warehouse to the line.</ListItem>
         <ListItem>External supply is the movement of goods from a supplier to the
		  line.</ListItem>
      </List>
      <Paragraph>From pulling materials from supplier of warehouse to the
		correct destination triggers can be used. For some supplying methodes these
		triggers can be based on events in production.</Paragraph>
      <List>
         <ListIntro>Different supplying methods can be used and are defined per
		  item/shop floor warehouse combination.</ListIntro>
         <ListItemHead>Time phased order point</ListItemHead>
         <ListItem>The supply is triggered by a SIC run for the shop floor
		  warehouse involved. When the time phased inventory drops below a certain point,
		  material supply must be performed.</ListItem>
         <ListItemHead>Order controlled/batch</ListItemHead>
         <ListItem>Material supply is performed anonymously for multiple orders
		  simultaneously based on triggers in the assembly process.</ListItem>
         <ListItemHead>Order controlled/supply in line sequence</ListItemHead>
         <ListItem>Through this method you can supply items as part of a KIT.
		  Mateiral supply is performed separately for every assembly order based on
		  triggers in the production process, even though a single trigger can be used to
		  generate kit supply for a number of consecutive orders in the assembly
		  schedule.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Time-horizon-driven material supply</SectionTitle>
      <Paragraph>Instead of initiating material supply based on process triggers,
		this can also do this based on time fences. Material supply is initiated for a
		line station order when that line station order coincides with a predefined
		time fence. Several time fences are defined to control the generation and
		update of supply massages.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Closed loop</SectionTitle>
      <Paragraph>The ASC call-offs are stored in sales schedules and sales
		releases. These releases (shipping and sequenced shipping schedules) are
		communicated to the supplier through EDI. Additionally, a unique reference per
		KIT, station, and part is included in that information. At the supplier's
		system, this information is tored in sales schedules and sales releases. After
		sending the parts, they can be received by reference ID.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Progress overview per line segment</SectionTitle>
      <Paragraph>A planner is responsible for a segment and can be lined to a
		specific segment. All information related to assembly orders will be visible
		per segment planner.</Paragraph>
      <Paragraph>The status/progress overview per segment shows orders on the
		segment based on line sequence whereby toggle mode is available to show the
		orders in various modes.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Progress overview per buffer</SectionTitle>
      <Paragraph>A control panel is available on which the schedule orders per
		buffer are displayed. A troggle function allows you to select different
		overviews.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Progress overview per line station</SectionTitle>
      <Paragraph>Similar to the progress overview per buffer, the progress can be
		monitored per line station.</Paragraph>
      <Paragraph>This can be used to report line station orders that contain the
		work on that order.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Process triggering</SectionTitle>
      <AimSection ID="/baanerp/ti/onlinemanual/000668#proc_trigger_defin">
         <Paragraph>In mixed model flow production environments many activities are
		based on the progress information of individual orders. When an event selected
		by the user occurs for an order on a certain line station another activity can
		be started. In the system, process triggering covers the automatic start and
		execution of a process baded on an event.</Paragraph>
      </AimSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Hours backflush</SectionTitle>
      <AimSection ID="/baanerp/ti/onlinemanual/000206#backf_hours_aim">
         <Paragraph>The calculation of the man and machine hours that must be
		backflushed differs for high-volume and low-volume. For high-volume situations
		backflushing is based on the rate specified for a line and the number of
		employees. In low-volume situations backflushing is based on the duration of
		every operation and the number of employees required per operation.</Paragraph>
      </AimSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Line surcharges</SectionTitle>
      <List>
         <ListIntro>During the assembly process line surcharges can be booked.
		  Surcharges booked on an assembly line are:</ListIntro>
         <ListItem>Assembly line for line station based on transaction
		  processing.</ListItem>
         <ListItem>Assembly line and generic item for order-based transaction
		  processing.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>WIP transfers</SectionTitle>
      <AimSection ID="/baanerp/ti/onlinemanual/000065#wip_transfer_aim">
         <List>
            <ListIntro>WIP transfers between lines are supported and the following
		  steps are distinguished:</ListIntro>
            <ListItem>Generation of a WIP transfer warehouse order line.</ListItem>
            <ListItem>Issuing of the WIP from the last line station of the
		  line.</ListItem>
            <ListItem>Receipt of WIP on the first line station of the next
		  line.</ListItem>
         </List>
      </AimSection>
   </GeneralSection>
</ManualTopic>