What Is a Routing Snapshot? Definition and Example

A routing snapshot is a frozen, point-in-time copy of a product's bill of routing that is saved together with the schedule of a specific job, so that later changes to the master routing never retroactively rewrite a plan that was already made. Think of it as a photograph of the recipe card taken at the moment the batch went into the oven: if the chef later revises the recipe, the photo still shows exactly how that batch was cooked. The snapshot is what lets a job reschedule against the routing it was planned with rather than a routing that shifted after the fact.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of production planning, see the manufacturing glossary.

How a Routing Snapshot Works

A master bill of routing is a living document. Engineering adds steps, retimes operations, swaps work centers, and adjusts setup times as the process matures. That is healthy for future jobs and dangerous for jobs already in flight.

The snapshot resolves the tension by copying the routing at the moment a job is scheduled and storing that copy with the job's plan. From then on the job has two references: the master routing that keeps evolving, and its own frozen snapshot that never changes. When you reschedule, the engine reads the snapshot by default, so the reschedule sees the same steps, the same times, and the same routing structure the job was originally built with.

This matters most during a reschedule with actuals. If Steps 1 and 2 are finished and Step 3 has not started, rescheduling against the snapshot keeps the finished work coherent and picks up Step 3 exactly where the original plan intended. Rescheduling against a routing that gained a new step or changed a machine could break that coherence and confuse the floor.

A Concrete Example

A job for 100 brackets schedules on Monday against a three-step routing: cut, drill, paint. At that instant EDGEBIC freezes a snapshot of those three steps and stores it with the plan.

On Wednesday, engineering revises the master routing to insert a deburr step between drilling and painting, because a customer complaint flagged sharp edges. The in-flight bracket job has already cut and drilled. When the planner reschedules it that afternoon:

• The engine reads the job's snapshot, which still has three steps, so the finished cut and drill stay intact and painting picks up next.
• A brand-new bracket order entered Thursday reads the current master routing, so it gets four steps including deburr.

Same product, two jobs, two correct outcomes. The snapshot is the reason the running job is not silently rewritten while the new job gets the improvement.

How EDGEBIC Uses It

In EDGEBIC the routing snapshot is stored with each job's production schedule and consumed on every reschedule.

• The snapshot is the default reschedule basis. The engine reads the preserved routing so routing changes since the original run do not alter a committed plan.
• You can choose current or hybrid. A scheduling run can be set to use the live routing instead, or a hybrid where completed steps keep the snapshot and remaining steps pick up current edits, when you actually want to fold changes into an in-flight job.
• It underpins variance and history. Because a completed job keeps its own routing basis, plan-versus-actual comparisons stay meaningful, and last month's jobs are never disturbed by this month's routing edits.
• It survives every converter. A job's binding to its snapshot carries through reschedules, so the plan's basis is never lost between runs.

The snapshot works hand in hand with actuals preservation on reschedule: the snapshot keeps the routing steady while preservation keeps the finished work steady. The routing snapshots explained walkthrough shows the mechanism in detail, and forward versus backward scheduling covers the direction the remaining steps are then placed. When the live routing has moved away from the snapshot, the difference is labeled by BOR change type, which says whether the work center, the timing, the requirements, the sequence, or the structure changed.