Operation Sequencing: Parallel Sequences, Alternative Sequences, and Reference Operation Sets

Explanation

A basic routing with a strictly linear sequence of operations (0010, 0020, 0030...) is sufficient for many products, but real manufacturing processes often involve branching, concurrent work, or shared operation blocks that a linear model cannot represent efficiently. Routing supports three structural tools to handle this: parallel sequences, alternative sequences, and reference operation sets. Parallel sequences let you model operations that happen concurrently on different work centers, feeding back into a main sequence at a defined point. For example, two sub-assemblies might be prepared simultaneously on separate lines before being joined at a final assembly operation. Each parallel sequence has its own sequence number and is linked to the main sequence through a 'branch' operation (where it splits off) and a 'return' operation (where it rejoins). Scheduling logic calculates the parallel branches independently, and the join operation cannot start until both branches finish, similar to a fork-join pattern in workflow modeling. This is critical for accurate lead time calculation: if two parallel operations each take 3 hours, the joined operation starts after 3 hours elapsed, not 6, because they run concurrently rather than sequentially. Alternative sequences represent a different way of producing the same output for a portion of the routing, typically used for exception handling such as rework, a different work center when the primary one is at capacity, or a process variant for certain lot sizes. Unlike parallel sequences, only one alternative sequence executes per production order; you don't run both concurrently. The alternative sequence is defined with a 'from operation' and 'to operation' referencing the standard sequence, and a validity or lot-size range that determines when it is used instead of the standard sequence. This is commonly used for a rework loop: the standard sequence continues normally, but for units that fail an inspection, an alternative sequence routes them through additional rework operations before rejoining the main flow. Reference operation sets are reusable blocks of operations that are not tied to a specific material but can be inserted into multiple routings. This is valuable when many materials share an identical sub-process, such as a standard packaging sequence or a quality inspection block. Instead of duplicating the same three or four operations across dozens of routings, you maintain the reference operation set once and insert it by reference into each routing. Changes to the reference set propagate to all routings using it, which significantly reduces maintenance effort and the risk of inconsistency. Reference operation sets are maintained similarly to a routing but without header material assignment, and are inserted using an operation type indicating reference. From a system perspective, all three constructs affect scheduling (via basic dates and capacity requirements calculations), costing (since reference set operations still carry activity types and standard values), and confirmation (operators confirm against the actual sequence executed, including alternative sequence operations when applicable). Capacity planning must correctly interpret parallel sequences so that capacity load is not double-counted or serialized incorrectly. Getting these structures wrong leads to inflated lead times, incorrect capacity requirements at work centers, or missed rework tracking. Understanding when to use each construct rather than defaulting to complex conditional logic in a single linear sequence is a key routing design skill, particularly for discrete and repetitive manufacturing environments with genuine parallel processing or frequent exception paths.

Code example

Example structural layout illustrating sequence numbering: Main sequence (Sequence 0, standard): 0010 Cutting - Work Center CUT01 0020 (branch point) - triggers parallel sequences 0040 Final Assembly - Work Center ASM01 (join point) 0050 Packing - Work Center PACK1 Parallel sequence (Sequence 1): 0021 Sub-assembly A prep - Work Center PREP1 returns to main sequence at operation 0040 Parallel sequence (Sequence 2): 0022 Sub-assembly B prep - Work Center PREP2 returns to main sequence at operation 0040 Alternative sequence (Sequence 3, rework): Valid from operation 0010 to 0040 Lot size validity: used only when quality flag indicates rework required 0015 Rework Inspection - Work Center QC01 0016 Rework Cutting - Work Center CUT01 Reference operation set 'STD_PACK_SET': 0005 Label Print 0010 Carton Assembly 0015 Final Pack Check -> Inserted into routing at operation 0050 by reference

Real project scenario

An electronics assembler manufactures a product where two sub-assemblies (a power module and a control module) are built on separate lines and joined at final assembly. Initially the routing was modeled as a single linear sequence, causing the system to calculate lead time as if the two sub-assemblies were built sequentially, overstating lead time by several hours and causing MRP to schedule production earlier than necessary, tying up capacity and inflating work-in-process. The PP consultant restructured the routing using two parallel sequences feeding into the final assembly operation, correcting the scheduled lead time and freeing up capacity visibility in the capacity planning table. Separately, a rework alternative sequence was added for units failing an in-process inspection, allowing quality-flagged production orders to route through additional rework steps without altering the standard routing used for normal-flow orders, while keeping confirmation and cost tracking accurate for the rework population.

Common mistakes

• Modeling genuinely concurrent operations as a single linear sequence, causing scheduling to overstate lead time by summing durations that actually run in parallel • Forgetting to define both a branch operation and a return operation for parallel sequences, leaving the join point ambiguous and causing scheduling errors • Using an alternative sequence for concurrent work instead of parallel sequence, resulting in the system attempting only one path when both should execute • Not maintaining validity or selection criteria for alternative sequences, so the system cannot determine when to trigger them at order creation or confirmation • Duplicating reference operation set content directly into individual routings instead of inserting by reference, which multiplies maintenance effort and creates drift over time • Overlooking that reference operation set changes propagate to all routings using it, causing unintended changes to costing or scheduling in unrelated materials

Best practices

• Use parallel sequences only for genuinely concurrent physical operations to get accurate scheduled lead times • Clearly define branch and return operations for every parallel sequence and validate scheduling results against expected lead time • Reserve alternative sequences for exception paths such as rework, alternate work centers, or lot-size-driven variants, with explicit selection criteria • Use reference operation sets for any operation block repeated across three or more routings to reduce maintenance and improve consistency • Document the business rationale for each parallel or alternative sequence directly in routing text fields so future maintainers understand intent • Test capacity evaluations after introducing parallel sequences to confirm capacity requirements are not duplicated or miscalculated

Interview angle

Interviewers assess whether candidates understand the structural difference between parallel and alternative sequences and can articulate the business scenarios that justify each, since misuse is a common real-world design flaw. Be ready to explain how parallel sequences affect scheduled lead time calculation differently from sequential operations, and how alternative sequences support rework or exception paths without disturbing the standard flow. Knowledge of reference operation sets as a maintenance efficiency tool, and the risk of unintended mass impact from a single change, demonstrates practical governance awareness valued in senior roles.