<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/000314" xml:lang="en">
   <Header>
      <Title>Production order lead-times (transfer batch
      quantity)</Title>
      <Keyword type="header" order="d1e2082394">
         <Level1>Production-order operation</Level1>
      </Keyword>
      <Keyword type="header" order="d1e2082397">
         <Level1>Planning, and transfer batch quantities</Level1>
      </Keyword>
      <Keyword type="header" order="d1e2082400">
         <Level1>Transfer batch quantities and production order lead-time</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>In <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> you
      can plan the <Link href="/baanerp/ti/glossary/glossary#000000000000052" role="glossary">operations</Link> of a production orders in a
      successive way. In this case, an operation must have been finished for all the
      items of the order, before the next operation can start. However, you can also
      plan the routing operations of a production order in a semi-parallel way, which
      means that you define the amount of items for which an operation must have been
      finished as the time point on which the next operation can start, called a <Link href="/baanerp/ti/glossary/glossary#000360" role="glossary">transfer batch quantity</Link>.</Paragraph>
      <Paragraph>To use a transfer batch
      quantity, select the <GUIRef href="/baanerp/ti/sfc/tisfc0110m000#tisfc010.tlyn" role="manual">Transfer Batch Less Than Production Batch</GUIRef> check box
      in the <GUIRef href="/baanerp/ti/sfc/tisfc0110m000" role="session">Production Planning (tisfc0110m000)</GUIRef> details session, and define a value in the <GUIRef href="/baanerp/ti/sfc/tisfc0110m000#tisfc010.trls" role="manual">Transfer Batch Qty</GUIRef> field.</Paragraph>
      <Paragraph> LN plans the
      production order lead-time somewhat differently if you use transfer batch
      quantities than when it plans the routing operations in a successive way.
      Figure 1-1 illustrates the method LN applies to plan operations with a
      transfer batch quantity in a forward planning situation. Figure 1-2 illustrates
      the method LN applies in a backward planning situation</Paragraph>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You cannot select the <GUIRef href="/baanerp/ti/sfc/tisfc0110m000#tisfc010.tlyn" role="manual">Transfer Batch Less Than Production Batch</GUIRef> check box
        for an operation if you selected the <GUIRef href="/baanerp/ti/sfc/tisfc0110m000#tisfc010.fdur" role="manual">Fixed Duration</GUIRef> check box for the preceding operation.
        Of course, this is also impossible in practice: if you bake bread rolls in an
        oven, all the bread rolls must stay in the oven for the full fixed period
        time.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Forward planning: normal situation</SectionTitle>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="252" width="648"
                   SRC="../images/tr_graph_tiom000314a.gif"
                   alt="[...]"/>
         <FigCaption>Figure 1-1</FigCaption>
         <FigLegend>
            <LegendEntry>
               <Symbol>QT</Symbol>
               <Desc>queue time</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>ST</Symbol>
               <Desc>setup time</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>RT</Symbol>
               <Desc>run time</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>WT</Symbol>
               <Desc>wait time</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>MT</Symbol>
               <Desc>move time</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>A</Symbol>
               <Desc>queue start date</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>B</Symbol>
               <Desc>setup + run start date</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>C</Symbol>
               <Desc>setup + run restart date</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>D</Symbol>
               <Desc>wait start date</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>E</Symbol>
               <Desc>move start date</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>F</Symbol>
               <Desc>queue start date (next
            operation)</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>G</Symbol>
               <Desc>setup + run start date (next
            operation)</Desc>
            </LegendEntry>
         </FigLegend>
      </Figure>
      <Paragraph>Figure 1-1 shows a normal planning situation in which operation
      20 starts at the time point on which operation 10 is finished for the entire
      production batch. However, the situation is not always as simple as this. The
      following sections describe how LN plans the operations if a long operation
      is followed by a short operation, and you want to use the transfer batch
      quantity concept.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <GeneralSection>
         <SectionTitle>Forward planning with transfer batch quantity</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="360" width="576"
                      SRC="../images/tr_graph_tiom000314b.gif"
                      alt="[...]"/>
            <FigCaption>Figure 1-2</FigCaption>
            <FigLegend>
               <LegendEntry>
                  <Symbol>QT</Symbol>
                  <Desc>queue time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>ST</Symbol>
                  <Desc>setup time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>RT</Symbol>
                  <Desc>run time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>WT</Symbol>
                  <Desc>wait time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>MT</Symbol>
                  <Desc>move time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>A</Symbol>
                  <Desc>queue start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>B</Symbol>
                  <Desc>setup + run start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>C</Symbol>
                  <Desc>setup + run restart date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>D</Symbol>
                  <Desc>first transfer batch
              finished</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>E</Symbol>
                  <Desc>wait start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>F</Symbol>
                  <Desc>move start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>G</Symbol>
                  <Desc>queue start date (next
              operation)</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>H</Symbol>
                  <Desc>setup + run start date (next
              operation)</Desc>
               </LegendEntry>
            </FigLegend>
         </Figure>
         <Paragraph>Figure 1-2 is a graphical reproduction of a forward planning
        situation in which you defined a product routing consisting of operation 10 and
        operation 20. For operation 10, you defined a transfer batch
        quantity.</Paragraph>
         <Paragraph>Figure 1-2 shows that LN cannot always simply schedule the
        starting point of operation 20 (G) based on the time point on which the first
        transfer batch quantity rolls out of operation 10 (D). The figure shows that
        the run time (RT) of operation 20 is much shorter than the run time of
        operation 10. The oblique arrow indicates that a conflict occurs if LN plans operation 20 after the first transfer batch is ready from operation 10.
        It would implicate that operation 20 is finished before operation 10 ends.
        Obviously, this can never be true.</Paragraph>
         <Paragraph/>
         <ProcedureList>
            <ListIntro>To avoid this unrealistic planning situation, the planning
          mechanism of LN performs the following correctional steps:</ListIntro>
            <ListItem>Offset the minimum production finish date (I): To do so, LN takes into account the queue start date of the next operation (G) of
          operation 10. From there, LN offsets the production time of one transfer
          batch quantity (the last one that rolls out of operation 10) for operation 20
          backward. This results in the minimum production finish date.</ListItem>
            <ListItem>Check if correction is required (II): Numeral II shows that LN must perform a correctional step, because the wait start date (E) of
          operation 20 (not corrected) falls before the minimum production finish date
          found in the previous step. It is obvious that the wait start date must
          coincide with the production finish date,</ListItem>
            <ListItem>Postpone operation 20 (III): The result of step 2 was
          affirmative, which means that LN must postpone operation 20 to let the wait
          start date of operation 20 coincide with the production finish date.
          Subsequently, LN offsets the lead-time elements of operation 20 backward to
          find the start date and time of operation 20.</ListItem>
         </ProcedureList>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Backward planing with transfer batch
        quantity</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="360" width="576"
                      SRC="../images/tr_graph_tiom000314c.gif"
                      alt="[...]"/>
            <FigCaption>Figure 1-3</FigCaption>
            <FigLegend>
               <LegendEntry>
                  <Symbol>QT</Symbol>
                  <Desc>queue time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>ST</Symbol>
                  <Desc>setup time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>RT</Symbol>
                  <Desc>run time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>WT</Symbol>
                  <Desc>wait time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>MT</Symbol>
                  <Desc>move time</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>A</Symbol>
                  <Desc>queue start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>B</Symbol>
                  <Desc>setup + run start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>C</Symbol>
                  <Desc>setup + run restart date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>D</Symbol>
                  <Desc>first transfer batch
              finished</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>E</Symbol>
                  <Desc>wait start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>F</Symbol>
                  <Desc>move start date</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>G</Symbol>
                  <Desc>queue start date (next
              operation)</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>H</Symbol>
                  <Desc>setup + run start date (next
              operation)</Desc>
               </LegendEntry>
            </FigLegend>
         </Figure>
         <Paragraph>Figure 1-3 is a graphical reproduction of a backward planning
        situation in which you defined a product routing consisting of operation 10 and
        operation 20. For operation 10, you defined a transfer batch
        quantity.</Paragraph>
         <Paragraph>In a backward planning situation, LN offsets in the
        opposite direction: the end point of the production activity is known, and LN must calculate when it must start, which means that you must read Figure
        1-3 from the bottom to the top.</Paragraph>
         <Paragraph>Therefore, starting from the end time of operation 20, LN offsets all lead times of operations 20 and 10 until the start time of
        operation 10. Figure 1-2 shows that planning operation 10 this way (operation
        10 not corrected) can lead to an unrealistic planning situation: in this
        example, operation 10 would end after operation 20 is finished.</Paragraph>
         <ProcedureList>
            <ListIntro>To avoid such an unrealistic planning situation, LN performs the following steps:</ListIntro>
            <ListItem>Offset the maximum allowed finish date of the preceding
          operation (I): to do so, LN offsets the production time of one transfer
          batch quantity (the last one of operation 20) backward from the wait start date
          (E) of operation 20. This results in the maximum allowed finish date for
          operation 10. This is the time point on which the move time of operation 10
          must end to be able to produce the last transfer batch quantity on operation
          20.</ListItem>
            <ListItem>Offset the calculated finish date of the preceding operation
          (II): to do so, LN first offset the move time and the wait time of
          operation 10 backward from the queue start date of operation 20. Next, from the
          time point where the first transfer batch quantity is planned to roll out of
          operation 10 (D), LN offsets the production time of the total order
          quantity minus one transfer batch quantity, plus the wait time and the move
          time, forward. This results in the calculated finish date of operation 10. The
          looped tail of the arrow shows the procedure of step 2.</ListItem>
            <ListItem>Check if correction is required (III): LN compares the
          maximum allowed finish date found in Step 1 with the calculated finish date
          found in Step 2. If the calculated finish date falls after the maximum allowed
          finish date, LN must perform a correctional step on the planning of
          operation 10.</ListItem>
            <ListItem>Advance the preceding operation (IV): if the result of Step 3
          is affirmative, LN advances operation 10 to an earlier time to realign the
          operation with operation 20 to make sure that the end of the move time of
          operation 10 (G) coincides with the maximum allowed finish date found in Step
          1.</ListItem>
         </ProcedureList>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The solution described in the previous section implies a
          simplification of reality, in which LN plans the total lead time of the
          production order in a consistent way. In practice, however, the short operation
          could start directy when the first batch arrives, and then wait a short time to
          be able to continue with processing the following batch. However, LN does
          not support this level of detail in the planning.</Paragraph>
         </Note>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000000000000011" role="manual">Lead times in Manufacturing</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000053" role="manual">To calculate production times of operations</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000074" role="manual">To calculate remaining production time</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>