<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/000323" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Line sequencing and rule types in Assembly Control</Title>
		<Keyword><Level1>Line sequencing</Level1>
		</Keyword>
		<Keyword><Level1>Final assembly line sequencing</Level1>
		</Keyword>
		<Keyword><Level1>Assembly operations</Level1>
		</Keyword>
		<Keyword><Level1>Sequencing</Level1>
			<Level2>assembly orders</Level2>
		</Keyword>
		<Keyword><Level1>Types</Level1>
			<Level2>rule</Level2>
		</Keyword>
		<Keyword><Level1>Rules</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>Line sequencing is the process by which a sequence of assembly orders for an <Link href="/baanerp/ti/glossary/glossary#000000000000055" role="glossary">assembly line</Link> is generated in the most efficient sequence. The assembly line can either be dedicated to one model or to a mixed model. For example, a large number of product variants can be produced on the same assembly line.</Paragraph>
		<List><ListIntro>Four major aspects of line sequencing are discussed:</ListIntro>
			<ListItem>Sequence rules.</ListItem>
			<ListItem>Sequence process.</ListItem>
			<ListItem>Rescheduling.</ListItem>
			<ListItem>Line sequence status.</ListItem>
		</List>
		<GeneralSection><SectionTitle>SEQUENCE RULES</SectionTitle>
			<List><ListIntro>Sequence rules are made up of the following elements:</ListIntro>
				<ListItem>Mixing process.</ListItem>
				<ListItem>Mix rules, which exist in three types: <List><ListItem>Capacity restriction rules.</ListItem>
						<ListItem>Proportional rules.</ListItem>
						<ListItem>Relative proportional rules.</ListItem>
					</List>
				</ListItem>
				<ListItem>Placement rules, which exist in three types: <List><ListItem>Clustering rules.</ListItem>
						<ListItem>Blocking rules.</ListItem>
						<ListItem>Priority rules.</ListItem>
					</List>
				</ListItem>
			</List>
			<GeneralSection><SectionTitle>The (re)mixing process in <GUIRef role="module" href="/baanerp/ti/asc">Assembly Control</GUIRef></SectionTitle>
				<Paragraph>You can remix the orders within the <Link href="/baanerp/ti/onlinemanual/tiasc" role="module">Assembly Control (ASC)</Link> module by using the <Link href="/baanerp/ti/asl/tiasl3220m000" role="session">Remix Line Mix (tiasl3220m000)</Link> session. Rules are defined for particular <Link href="/baanerp/ti/glossary/glossary#000095" role="glossary">option combinations</Link>. Remixing attempts to schedule the orders so that the number of orders for each option combination is as close as possible to the maximum number of orders for each option combination. The better the mix, the better the sequence quality.</Paragraph>
			</GeneralSection>
			<GeneralSection><SectionTitle>Mix rules</SectionTitle>
				<Paragraph>There are three types of mix rules:</Paragraph>
				<GeneralSection><SectionTitle><GUIRef role="enum" href="/baanerp/ti/domains/asl.rtyp#cap.restriction">Capacity Restriction</GUIRef></SectionTitle>
					<Paragraph>The total capacity of the line is limited, for example: maximum 500 cars with option combination CityCar in one day.</Paragraph>
					<List><ListIntro>For <GUIRef href="/baanerp/ti/domains/asl.rtyp#cap.restriction" role="enum">Capacity Restriction</GUIRef> rules, you can select one of three types of dispersion:</ListIntro>
						<ListItem><GUIRef href="/baanerp/ti/domains/asl.mdis#avg.dispersion" role="enum">Average Dispersion</GUIRef> The option combination is spread evenly throughout the line sequence.</ListItem>
						<ListItem><GUIRef href="/baanerp/ti/domains/asl.mdis#slid.window.ad" role="enum">Sliding Window Avg. Disp.</GUIRef> A window is a certain number of adjacent sequence positions, which slides because the windows can overlap. In each window the option combination is dispersed as evenly as possible. For example, each group of 10 positions should have the same number of RedCars.</ListItem>
						<ListItem><GUIRef href="/baanerp/ti/domains/asl.mdis#slid.window.cr" role="enum">Sliding Window Cap. Resr.</GUIRef> Within each window, there is a limit to the number of orders for the option combination. For example, no more than two RedCars in any window of 10 positions.</ListItem>
					</List>
				</GeneralSection>
				<GeneralSection><SectionTitle><GUIRef role="enum" href="/baanerp/ti/domains/asl.rtyp#proportional">Proportional</GUIRef></SectionTitle>
					<Paragraph>Option combinations must be present in fixed proportion of the total order, for example, the ratio of CityCar to other orders must be 1:2.</Paragraph>
					<List><ListIntro>You can define two dispersion types for <GUIRef href="/baanerp/ti/domains/asl.rtyp#proportional" role="enum">Proportional</GUIRef> rules:</ListIntro>
						<ListItem><GUIRef href="/baanerp/ti/domains/asl.mdis#avg.dispersion" role="enum">Average Dispersion</GUIRef> The option combination is spread evenly throughout the line sequence.</ListItem>
						<ListItem><GUIRef href="/baanerp/ti/domains/asl.mdis#slid.window.ad" role="enum">Sliding Window Avg. Disp.</GUIRef> In each window, there is a maximum ratio of a given option combination and any other option combination. For example, for every RedCar option combination, there must be at least one other option combination within any four option combinations (ratio = 1:2, window =4).</ListItem>
					</List>
				</GeneralSection>
				<GeneralSection><SectionTitle><GUIRef role="enum" href="/baanerp/ti/domains/asl.rtyp#relative.prop">Relative Proportional</GUIRef></SectionTitle>
					<Paragraph>The same as <GUIRef href="/baanerp/ti/domains/asl.rtyp#proportional" role="enum">Proportional</GUIRef>, except that the <GUIRef href="/baanerp/ti/asl/tiasl1570m000#tiasl170.mdis" role="formfield">Method of Dispersion</GUIRef> is always <GUIRef href="/baanerp/ti/domains/asl.mdis#rel.dispersion" role="enum">Relative Dispersion</GUIRef>. You must specify a second option combination in which the first option combination is dispered in relation to. The option combination is placed in a particular relation to another option combination. For example, red cars and blue cars can only be assembled alternately; you cannot assemble two red cars in a row.</Paragraph>
				</GeneralSection>
				<Paragraph>During remixing, the priority of orders is taken into account, as described in one of the following paragraphs.</Paragraph>
				<Paragraph>Because rules can conflict with each other, it is possible that not all sequence rules can be met. In that case you can give some rules a higher priority. However, this results in a less efficient order sequence, and you must solve these conflicts by redesigning the assembly process, not by performing more line sequencing.</Paragraph>
			</GeneralSection>
			<GeneralSection><SectionTitle>Placement rules</SectionTitle>
				<Paragraph>Placement rules are used to determine how products are placed in relation to other products. There are three types of placement rules:</Paragraph>
				<GeneralSection><SectionTitle><GUIRef role="enum" href="/baanerp/ti/domains/asl.rtyp#clustering">Clustering</GUIRef></SectionTitle>
					<Paragraph>Use this rule to place option combinations next to each other with the same options, when changing between option involves a long change-over time. For example, place all blue cars next to each other, because changing painting color takes a long time. <Link href="/baanerp/ti/onlinemanual/tiasc" role="module">Assembly Control (ASC)</Link> clusters the option combinations (such as paint color), and a sequence number is assigned to every option combination.</Paragraph>
					<ExampleSection><SectionTitle>Example</SectionTitle>
						<Paragraph>In this example, the assembly orders and their option combinations are planned for a day on line segment 1.</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Order 1</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 2</TD>
									<TD>Optoion combination blue</TD>
								</TR>
								<TR><TD>Order 3</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 4</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 5</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 6</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 7</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 8</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 9</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 10</TD>
									<TD>Option combination red</TD>
								</TR>
							</TBODY>
						</TABLE>
						<Paragraph>The option combination list Color is defined in <Link href="/baanerp/ti/onlinemanual/tiasc" role="module">Assembly Control (ASC)</Link> as:</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Option combination red</TD>
									<TD>sequence 1</TD>
								</TR>
								<TR><TD>Option combination black</TD>
									<TD>sequence 2</TD>
								</TR>
								<TR><TD>Option combination blue</TD>
									<TD>sequence 3</TD>
								</TR>
							</TBODY>
						</TABLE>
						<Paragraph>When the assembly orders are sequenced in <Link href="/baanerp/ti/onlinemanual/tiasc" role="module">Assembly Control (ASC)</Link>, based only on the clustering rule Color, the result for line segment 1 is:</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Order 1</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 4</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 7</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 10</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 3</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 6</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 9</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 2</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 5</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 8</TD>
									<TD>Option combination blue</TD>
								</TR>
							</TBODY>
						</TABLE>
					</ExampleSection>
				</GeneralSection>
				<GeneralSection><SectionTitle><GUIRef role="enum" href="/baanerp/ti/domains/asl.rtyp#blocking">Blocking</GUIRef></SectionTitle>
					<Paragraph>Certain option combinations must not be placed next to other option combinations. For example, light colors must not be painted after dark colors to minimize effects of paint contamination.</Paragraph>
					<ExampleSection><SectionTitle>Example</SectionTitle>
						<Paragraph>In this example, the assembly orders and their option combinations are planned for a day on line segment 1.</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Order 1</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 2</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 3</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 4</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 5</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 6</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 7</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 8</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 9</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 10</TD>
									<TD>Option combination red</TD>
								</TR>
							</TBODY>
						</TABLE>
						<Paragraph>The option combination list Color is defined in <Link href="/baanerp/ti/onlinemanual/tiasc" role="module">Assembly Control (ASC)</Link> as:</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Option combination red</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Option combination red</TD>
									<TD>Option combination red</TD>
								</TR>
							</TBODY>
						</TABLE>
						<Paragraph>The list Color is linked to the blocking rule Color, which is linked to assembly line 1. This rule says that the color red cannot be followed by the color blue or by the color red.</Paragraph>
						<Paragraph>One result of this rule is the following sequence:</Paragraph>
						<TABLE border="1"><TBODY><TR><TD>Order 1</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 3</TD>
									<TD>Optoion combination black</TD>
								</TR>
								<TR><TD>Order 2</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 4</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 6</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 5</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 8</TD>
									<TD>Option combination blue</TD>
								</TR>
								<TR><TD>Order 7</TD>
									<TD>Option combination red</TD>
								</TR>
								<TR><TD>Order 9</TD>
									<TD>Option combination black</TD>
								</TR>
								<TR><TD>Order 10</TD>
									<TD>Option combination red</TD>
								</TR>
							</TBODY>
						</TABLE>
					</ExampleSection>
				</GeneralSection>
			</GeneralSection>
			<GeneralSection><SectionTitle>Priority</SectionTitle>
				<ProcedureList><ListIntro>Priority rules are enforced in the following order:</ListIntro>
					<ListItem>Orders with a later <GUIRef href="/baanerp/ti/asc/tiasc2100s000#tiasc200.rqod" role="formfield">Requested Offline Date</GUIRef> are given a lower priority.</ListItem>
					<ListItem>Orders that are sold (a demand order) have priority over orders not yet sold.</ListItem>
					<ListItem>Assembly orders with a lower priority number are processed first (for example, orders with a priority number of 1 are processed before orders with a priority number of 4). You define the order priority in the <GUIRef href="/baanerp/ti/asc/tiasc2100s000" role="session">Assembly Order (tiasc2100s000)</GUIRef> session.</ListItem>
					<ListItem>Cost function value.</ListItem>
				</ProcedureList>
			</GeneralSection>
		</GeneralSection>
		<GeneralSection><SectionTitle>THE SEQUENCING PROCESS</SectionTitle>
			<Paragraph>When you add new orders to an assembly line, SSA ERP generates in the <Link href="/baanerp/ti/asl/tiasl4200m000" role="session">Simulate and Create Line Sequences (tiasl4200m000)</Link> session an initial sequence for the line for the appropriate offline date.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>When you confirm a sequence, SSA ERP generates the As-built structure for the end item, such as the VIN number and header in the case of a car. You can edit the structure with the <Link href="/baanerp/ti/mfc/timfc0110m000" role="session">Serial End Item - As-Built Headers (timfc0110m000)</Link> and <Link href="/baanerp/ti/mfc/timfc0111m000" role="session">Serial End Item - As-Built Components (timfc0111m000)</Link> sessions. The serial numbers of the components are generated when you freeze the sequence. When you use the <GUIRef href="/baanerp/ti/asc/tiasc5450m000" role="session">Print Work Instructions (tiasc5450m000)</GUIRef> session, a space is provided on the printed form for you to enter the serial number of the components.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>RESCHEDULING</SectionTitle>
			<List><ListIntro>You can also manually alter the sequence with the <Link href="/baanerp/ti/asl/tiasl4220m000" role="session">Reschedule Assembly Orders (tiasl4220m000)</Link> session. The session uses two types of rules:</ListIntro>
				<ListItemHead>Move</ListItemHead>
				<ListItem>An order is taken from one position and inserted into another position. All orders in between the two positions are shifted one position towards the initial position.</ListItem>
				<ListItemHead>Swap</ListItemHead>
				<ListItem>Two orders are interchanged, and nothing else is changed.</ListItem>
			</List>
			<Paragraph>The automatic sequencing process uses the swap method. You can change the maximum swap/insert distance that is used in the automatic sequence generation in the <GUIRef href="/baanerp/ti/asl/tiasl4110m000" role="session">Remix/Sequence Parameters (tiasl4110m000)</GUIRef> session.</Paragraph>
			<Paragraph>When you have swapped orders to another line mix, you can run the <Link href="/baanerp/ti/asl/tiasl3220m000" role="session">Remix Line Mix (tiasl3220m000)</Link> session for a better sequence.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListItem>Only those assembly orders with the <GUIRef href="/baanerp/ti/domains/asc.asst#planned" role="enum">Planned</GUIRef> status can be moved.</ListItem>
					<ListItem>You cannot move an assembly order to an offline date in the past.</ListItem>
					<ListItem>You cannot move an assembly order with the status <GUIRef href="/baanerp/ti/domains/asc.asst#planned" role="enum">Planned</GUIRef> if it has a parent order linked to it.</ListItem>
					<ListItem>When you move an order, the supplying line orders are not moved automatically. Moving supplying line orders is performed during the synchronization phase of line sequencing.</ListItem>
					<ListItem>If you try to move an order so that the planned offline date occurs before the <GUIRef href="/baanerp/ti/asc/tiasc2100s000#tiasc200.cfdt" role="formfield">Reference Date</GUIRef>, SSA ERP asks you whether you want to continue the process.</ListItem>
				</List>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>LINE SEQUENCE STATUS</SectionTitle>
			<List><ListIntro>A line sequence can have one of the following statuses:</ListIntro>
				<ListItem><GUIRef href="/baanerp/ti/domains/asl.lsta#planned" role="enum">Planned</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/ti/domains/asl.lsta#started" role="enum">Started</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/ti/domains/asl.lsta#completed" role="enum">Completed</GUIRef>
				</ListItem>
			</List>
			<Paragraph>A line sequence has the status <GUIRef href="/baanerp/ti/domains/asl.lsta#planned" role="enum">Planned</GUIRef> when it is first created. When the first line-station order is completed, the status becomes <GUIRef href="/baanerp/ti/domains/asl.lsta#started" role="enum">Started</GUIRef>. When the last line station order is completed, the status of that segment becomes <GUIRef href="/baanerp/ti/domains/asl.lsta#completed" role="enum">Completed</GUIRef>.</Paragraph>
			<Paragraph>You can see the status in the <GUIRef href="/baanerp/ti/asl/tiasl4500m000" role="session">Line Segment - Line Sequence (tiasl4500m000)</GUIRef> session.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000301" role="manual">Assembly control overview</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000302" role="manual">Line station variants</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000303" role="manual">Assembly order costing</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000304" role="manual">Assembly backflushing</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000305" role="manual">Assembly line station utilization</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/000306" role="manual">Assembly orders</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
