Configuring Routing Operations: Work Centers, Control Keys, and Sequences
Learn how to configure routing operations in practice, including work center assignment, standard value formulas, control keys, and sequence types, and how these choices affect scheduling, costing, and execution.
Explanation
Once the foundational concept of a routing is understood, the practical work of a PP consultant centers on configuring individual operations correctly so that scheduling, capacity planning, costing, and shop floor confirmation all behave as the business expects. This lesson goes deeper into the operational building blocks. Work center assignment: every operation must reference a work center (or, in some process industry contexts, a resource) that supplies capacity category, formulas for calculating durations, and a cost center/activity type link used for costing. When creating an operation, the consultant selects the work center and then enters standard values (e.g., setup time, machine time, labor time) whose meaning is governed by the formulas defined on that work center's capacity and costing views. If the operation's standard value key does not match the formulas maintained on the work center, scheduling and costing will fail or produce meaningless results (e.g., zero duration, missing activity postings). Control keys in depth: the control key is arguably the single most impactful configuration field at operation level because it is a bundle of yes/no indicators covering: scheduling relevance (should this operation contribute to lead time calculation), capacity planning relevance (should this operation generate capacity requirements), costing relevance (should this operation's activity consumption flow into product costing), confirmation relevance (can/must this operation be confirmed, and is confirmation mandatory before order technical completion), and print relevance (should this operation appear on shop floor papers). A consultant configuring a routing must select control keys operation by operation based on real process needs - for example, an inspection operation might be scheduling-relevant but not costing-relevant if inspection labor is not tracked separately, while a subcontracting operation typically needs a different control key set entirely to trigger purchase requisition creation logic (usually paired with subcontracting-specific settings elsewhere). Sequences: a standard sequence defines the primary linear flow of operations. Where the real process branches, two mechanisms exist: parallel sequences (operations that run concurrently with the standard sequence, useful for modeling simultaneous curing or drying steps that do not block the main flow) and alternative sequences (operations that replace part of the standard sequence under certain conditions, such as an alternate routing path for a rework scenario or a different lot-size band). Correctly modeling these avoids either overstating lead time (treating parallel work as sequential) or losing traceability of alternate paths. Standard values and formulas: standard values (like setup time = 30 minutes, machine time per unit = 2 minutes) are entered against parameter keys (e.g., labor, machine) whose interpretation is defined by scheduling and costing formulas at the work center. Getting the base unit of measure and formula parameters consistent across routing and work center is essential; mismatches lead to wildly incorrect scheduled durations or capacity requirements that are difficult to trace without checking both objects together. Runtime/document flow: when a production or process order is created (manually or via MRP conversion of a planned order), the system reads the released routing (respecting lot-size validity and status), copies the relevant operations, work centers, and standard values into the order, and then performs scheduling based on those copied values combined with the work center's capacity/shift data. Because these values are copied at that point in time, subsequent changes to the routing template do not retroactively affect the order; only new orders created afterward will reflect that routing. Troubleshooting: common issues include capacity requirements not appearing (control key not capacity-relevant, or work center capacity category mismatch), costing runs showing zero activity cost (control key not costing-relevant, or activity type/price not maintained), and confirmations being blocked or allowed unexpectedly (confirmation relevance flag misconfigured). Consultants should check the operation's control key first, then the work center's linked formulas and cost center/activity type assignment, before assuming a bug elsewhere.
Real project scenario
During a go-live for a make-to-order fabrication client, planners reported that capacity leveling in the planning table showed zero load for a critical welding operation despite orders being created. Root cause analysis by the consultant traced the issue to the operation's control key, which had capacity planning relevance switched off by mistake during a mass routing upload. Correcting the control key on affected operations (through a controlled mass change with proper testing on a sample order first) restored accurate capacity requirements without needing to touch work center or order data.
Common mistakes
• Assigning a work center to an operation without verifying that its formulas match the standard value keys used, causing scheduling or costing to silently compute incorrect durations. • Selecting a control key that turns off costing relevance for operations whose labor should be tracked, understating product cost. • Overusing parallel sequences to represent steps that are actually sequential, distorting lead time calculations. • Performing mass routing changes (e.g., via upload tools) without validating control key values afterward on a representative sample of operations. • Forgetting that already-created orders retain the operations copied at order creation time, then being confused why a routing correction did not fix an existing order.
Best practices
• Validate that standard value keys on operations align with the formulas maintained on the assigned work center before releasing a routing. • Choose control keys deliberately per operation type (production, inspection, subcontracting) rather than copying a default blindly across all operations. • Model genuinely concurrent process steps with parallel sequences and genuinely conditional paths with alternative sequences, rather than forcing everything into one standard sequence. • After any mass routing change or upload, spot-check control key values and run a test order through scheduling and costing before wide rollout. • Communicate to planners that routing changes affect only future orders, and define a process for handling in-flight orders when a routing correction is needed.
Interview angle
A common scenario question asks candidates to diagnose why capacity requirements or costing results are missing for a specific operation despite the routing looking otherwise correct. The expected reasoning path is: check the operation's control key relevance indicators first, then verify the work center's formulas and cost center/activity type assignment, and finally confirm whether the affected orders were created before or after any routing correction. Being able to walk through this diagnostic sequence demonstrates practical configuration depth beyond textbook knowledge.