A production order reaches drilling with yesterday’s route attached, even though engineering has added an inspection before release to packing. Control manufacturing routing by matching the job to an approved route version and retaining each operation’s identity, required predecessor, resource, and instruction reference. Compare the instructions on the order with the route that applies to its product, site, and date. Updating a master record alone does not demonstrate that the floor received the change.
The bill of materials identifies the components and quantities needed for a build. The route identifies the work required to process them and the handoffs between operations. Keep the two linked through their approved product configuration, while preserving separate revision identities so a process change does not become an unexplained material change.
Engineering defines identifiable operations and handoffs
Give the route a stable identifier, version, item applicability, and site. Give every operation its own identifier within that version. Retain the sequence, required resource or resource class, and reference to the safe work instruction. A description such as “finish” is too ambiguous to join with a machine log when several operations use it. Map the source operation ID instead of matching descriptions alone.
ERPNext’s Routing documentation describes a reusable template containing operations, workstations, operation times, and batch sizes. Its Sequence ID enforces predecessor completion through Job Cards. Confirm the equivalent sequence and completion behavior in your installed configuration before relying on a numbered list as a release control.
Define the output of each operation and what permits the next one to begin. Include the inspection result or approval when a quality gate controls movement. ERPNext’s Manufacturing Operation documentation supports a default workstation and a quality inspection template carried into the operation’s Job Card. The inspection owner still needs to define the acceptance criteria and disposition authority; an attached template is not a passed inspection.
Planning selects the version that applies to the order
Document how the plant selects a route version. The applicability rule may refer to a production date, product configuration, or another approved condition; name the actual rule and retain its inputs. Microsoft’s Business Central routing documentation describes routing versions with unique version codes and starting dates. A version code without the selection rule leaves a reviewer unable to explain why that version was chosen.
Consider a hypothetical job J520 for 50 brackets at one site. It was created on November 16 and is planned to start November 19. Assume the plant’s approved rule selects the route effective on the planned start date. Route R7 version B becomes effective November 18 and adds a final inspection; version A lacks that operation. The date rule selects B even if J520 copied A when the job was created.
Before release, have the planner compare the order’s actual operation list with the selected version. Record the approved correction and verify the regenerated traveler or electronic instructions. If work already started under A, ask engineering and quality to decide which units need review and how the remaining work should proceed. Do not overwrite completed operation records to make them appear to have followed B.
Preserve a dated baseline of the order’s route as well as the master version reference. Oracle’s work definition version documentation warns that changes to an operation effective across several versions can apply across those versions. That behavior makes a version label alone insufficient evidence of the exact instructions used. Retain the operation details and approved changes that establish the job’s history.
Planning keeps setup, unit time, and sequence separate
For J520, assume version B contains the sequential operations below. Each operation handles all 50 pieces before the next begins. Setup occurs once per operation for this single batch, and run time is stated per piece. Use one resource at a time per operation, with no scrap, rework, overlapping lots, or extra setup. The actuals are hypothetical resource-occupancy minutes measured on the same basis as the standards.
| Operation / resource | Setup per batch | Run per piece | Standard for 50 | Actual |
|---|---|---|---|---|
| 10 / cut at saw | 20 minutes | 1 minute | 20 + 50 × 1 = 70 minutes | 75 minutes |
| 20 / drill at drill press | 30 minutes | 2 minutes | 30 + 50 × 2 = 130 minutes | 155 minutes |
| 30 / inspect at gauge bench | 10 minutes | 0.5 minutes | 10 + 50 × 0.5 = 35 minutes | 35 minutes |
| Total resource time | 60 minutes | 3.5 minutes across operations | 235 minutes | 265 minutes |
The standard is 60 setup minutes + 50 × 3.5 run minutes = 235 resource-minutes. Microsoft’s routing time fields distinguish fixed setup time from per-unit run time. This example assumes one batch triggers each setup once. If the same 50 pieces instead require two separate setups at every operation, the standard becomes 2 × 60 + 50 × 3.5 = 295 minutes under that revised batch assumption.
Keep the unit basis beside every time. An ERP field that states minutes for a batch of pieces needs its batch quantity before conversion to minutes per piece. Multiplying an entire batch duration by the order quantity would overstate the work. Setup minutes (charged once per batch in this example) must also stay out of the per-piece multiplier.
Resource load and elapsed lead time answer different questions. In Business Central, Microsoft documents wait and move time as extending elapsed duration without consuming work-center capacity in the same way as setup and run time in its routing reference. The example’s 235 minutes excludes queues, transfers, and calendar gaps. It is not a promised finish time.
State whether steps are sequential, independent branches, or permitted to overlap on partial lots. An inspection requiring drilled pieces cannot start on pieces that have not reached it. Independent preparation may overlap if it has its own qualified resources and inputs. Preserve those dependencies and any transfer-batch rule; sorting all operations by number and adding durations cannot represent a parallel process or establish resource availability.
Supervision verifies the resource and inspection handoff
Before an operation starts, have the supervisor verify the order, route version, operation ID, and instruction revision at the work location. Check that the assigned resource and tools match the approved method. An alternate machine needs its own accepted applicability and time basis; a spare machine with a similar description does not establish an approved substitution.
At the handoff, retain the quantity transferred, operation result, and required signoff. In J520, completion of drilling sends pieces to the inspection operation added by B. The inspection result authorizes the next disposition under the plant’s rule. If a printed traveler still omits inspection, stop that discrepancy for review even when the master route on screen is correct.
Use the manufacturing work order process for material issues, accepted output, and order closeout. Keep this handoff focused on whether the next operation has the right identity, inputs, and permission to proceed. That separation lets the route remain reusable while each order retains its own production history.
The analyst compares actuals with the released baseline
J520 records 265 actual resource-minutes against 235 standard minutes, a difference of 30. Cutting contributes five extra minutes and drilling contributes 25; inspection matches its standard. Those differences identify the operations to review. They do not establish whether the cause was tool condition, an outdated standard, or an execution problem without supporting records.
Match actual entries by order, operation, resource, and the route baseline that ran. Keep setup and run records distinct where the source supports them, along with reversals and approved rework. Compare like quantities and units before calculating a difference. A 50-piece standard cannot be assessed against a partial operation posting without accounting for what that posting covers.
Preserve the original timing events when a reported duration looks wrong. The cycle time measurement article distinguishes machine duration, operator cycles, and completion intervals. An elapsed queue before drilling should not become extra drill run time unless the approved measurement definition includes it. Keep an unknown delay unclassified until the owner can support its cause.
Engineering disposes exceptions before changing the master
Return recurring operation differences to engineering with the order references and actual evidence. Engineering decides whether to change a standard, qualify another resource, revise an instruction, or retain the method while another owner fixes an execution issue. Production control records which open orders the decision affects. A faster observed job is evidence for review, not permission to replace the approved standard.
Keep the change reference, approver, effective condition, and affected operation identities with the revision. Recheck orders already created and work already started as separate populations. The first may need a controlled instruction update; the second may need a quality disposition or approved remaining-work route. Preserve both decisions so a new master version cannot erase what happened under the earlier one.
Permute: match route versions to job evidence
Permute sells connected business data, custom applications, and governed analysis. We can combine permitted route, production-order, and operation-result extracts while reconciling their identifiers. The join can retain source company, site, route version, and operation so repeated operation numbers on different routes do not become the same step.
We can apply your declared applicability and timing rules in repeated reviews. An operations lead can ask which orders carry an unexpected route version and inspect the source baseline, selected version, and approved exception within their permissions. Claude, ChatGPT, or Copilot can use that prepared evidence while engineering retains ownership of the process decision.
Bring one route and its job records together
Start with permitted route versions, order operations, and the timing evidence used in your current review.
Keep safe methods and route approval with engineering
We do not approve safe work instructions, qualify resources, choose engineering revisions, or certify inspection results. This workflow reads source records for review and does not promise to revise or release a production route. Any external action requires a supported provider/action scope, current permissions, and approval. The owning plant workflow remains responsible for instructions and disposition.
Manufacturing routing keeps an order on an approved operation path when its version and handoffs remain identifiable. Resolve the obsolete-route problem by checking the operations carried by the job, then preserve the baseline and the decision about affected work. The bracket example assigns 235 standard resource-minutes under one batch assumption and exposes a 30-minute actual difference without inventing its cause. Carry those identities and assumptions into the next revision review so a changed master does not rewrite the job’s history.
Review an order that diverged from its route
Bring the selected route, released operation list, and unresolved revision or timing evidence to a scoped review.
Questions about production routes and revisions
Will changing a master route update existing orders?
Check the behavior of your ERP and the order’s current status. Preserve the order baseline, verify its actual operation list, and use the approved change process for the affected work. A correct master route is not evidence that existing travelers or electronic instructions changed.
Can operations run in parallel?
They can when the approved process allows it and the required inputs and resources are available. Retain branch dependencies and any partial-lot handoff rule. The example assumes full-batch sequential processing, so its time sum does not model an overlapping schedule.
Should actual operation times replace routing standards?
Keep actuals as evidence against the baseline that applied to the job. Review differences for scope, recording errors, and operating conditions before engineering decides whether a standard needs revision. Preserve the approved change and its effectivity instead of applying a new time to completed history.