How to Update the Routing on a Scheduled Job in EDGEBIC

To update the routing on a scheduled job in EDGEBIC by User Solutions, open the Scheduled Job BOR tab, compare the job's frozen copy against the master routing, then apply one of three controls: edit the copy, reset it from the master, or tell the job to follow the master on the next run. All three are per job. None of them can move completed operations. This post is the procedure, in order, with the decision rules that keep it from becoming a bulk operation you regret.

If you have not met the mechanism, production routing snapshots covers what is frozen and why. If your question is specifically about adding or retiming steps on one live order, editing a live job's routing is the narrative version of that task.

Step 1: Find the Job's Copy

Open the Scheduled Job BOR tab and pick the job in the job selector. The tab has three modes.

Data Grid is where you inspect and edit. Designer is where structural changes are easier to see. Actual Live is for watching, not changing, and it is covered in logging actual hours and pieces.

The grid shows the copy exactly as the scheduling engine reads it. That is the point of looking: what is on this screen is what the next reschedule will plan against, regardless of what the master routing says today.

Step 2: Read the Context, Not Just the Steps

Expand a step and you get more than its timings. The copy carries the scheduling context captured when it was written: the date and time the job was scheduled, the order quantity that was used, the scheduling mode, the original due date, and the work center utilization, instance count, and efficiency in force at the time.

A reschedule counter also increments each time the job is re-planned. Together those fields answer the question that usually prompts someone to open this tab in the first place: is this copy from before or after the change we are arguing about.

Step 3: Compare Against the Master

Before changing anything, find out what is actually different. The comparison runs the job's copy against the current master routing step by step and reports which fields differ.

Read the output with three questions.

• Did a work center change? This is the highest-impact difference, because it invalidates whatever is physically set up on the floor.
• Did timings change materially? A cycle time cut by half is a real improvement worth adopting. A 4 percent adjustment is noise and rarely worth disturbing a live job.
• Did steps appear or disappear? Structural changes need a look at sequencing, not just at the step in isolation.

Most refresh decisions become obvious once the differences are in front of you. Most bad refresh decisions happen because nobody looked first.

Step 4: Decide by Job Status

The right control depends on where the job has reached, not on how important the routing change feels.

The bias should be toward leaving live jobs alone. The frozen copy exists because the floor's setup and paperwork were built against it, and every refresh spends some of that stability.

Step 5: Apply One of Three Controls

Update this Job BOR

Edits the job's own copy, in Data Grid or Designer mode. Use this when the change applies to this job only: a one-off substitution, an extra inspection step a customer asked for, a corrected time for this quantity.

The master routing is untouched. The next reschedule plans against your edited copy.

Two cautions. A step added on the Designer canvas needs its end product association to be correct, or the engine will not plan it. And the sequencing links matter: a new step has to be wired into the flow, not just dropped on the canvas. Steps scheduled out of sequence covers the symptoms when that goes wrong.

Reset BOR from Global

Throws away the job's copy and takes a fresh snapshot of the current master routing.

This is the blunt instrument. It is the right call when the copy has drifted somewhere unhelpful and you want a clean start against the current standard. It is the wrong call when the copy holds per-job customizations somebody deliberately made, because those are discarded without a prompt and there is no version history to recover them from.

Note or export the copy before using it on anything you are unsure about.

Use Global BOR on Reschedule

Ticks a flag on the job. The next scheduling run reads the master routing instead of the copy, and the copy refreshes to match what was used.

This is the most common of the three in practice, because it makes the adoption happen as part of a normal run rather than as a separate edit. It is also the one to use when you want several jobs to adopt a change: tick them, then run a targeted reschedule covering only those jobs.

Step 6: Reschedule and Verify

Refreshing a copy does not change any dates by itself. Run a reschedule, preferably targeted to the jobs you touched, then check four things.

1. The routing on screen matches what you intended. Back on the Scheduled Job BOR tab, the copy should now show the version you chose.
2. Completed operations did not move. They cannot, but confirm it anyway on the Job View. Actual hours and actual dates unchanged.
3. The remaining sequence makes sense. Particularly after a structural change. A removed step should be absent; an added step should sit where you put it.
4. The audit trail records the run. Job Audit shows the reschedule with old and new dates side by side.

The full verification routine is in how to reschedule safely.

Step 7: Tell the Floor

This step gets skipped and it is the one that causes the phone call.

A shop floor terminal compares the live routing against the job's copy and raises a banner when the work center, setup time, cycle time, or queue time differ. That banner is the system's attempt to close the loop, and it fires before the operator starts. But it is a notification, not a work instruction.

If you refreshed a job whose traveler names the old machine or the old times, reprint the traveler. If the change moves an operation to a different work center, tell the supervisor who staged the setup. The scheduling system can update its plan in seconds; a fixture cannot.

Doing This for Several Jobs

A routing revision usually touches more than one open order. The sequence that keeps a rollout from becoming an incident:

1. List the affected jobs and sort them by status. No actuals, running, complete. The three groups get three different answers and the sort takes a minute.
2. Do one job from the running group first. Refresh it, reschedule, verify. If the result is not what you expected, you have learned it on one job rather than eleven.
3. Batch the no-actuals group. Tick the follow-master flag on each, then run one targeted reschedule covering only those jobs. Every other job on the plant keeps its plan and its reserved capacity.
4. Leave the complete group alone. There is no remaining work to re-plan and no benefit to touching the record.
5. Collect the paperwork consequences in one pass. Note every job whose traveler names something that changed, and reprint them together rather than one at a time as complaints arrive.

Resist the instinct to reset everything from the master to "get clean". Reset discards per-job customizations without a prompt, and on a rollout of eleven jobs the odds that at least one carried a deliberate customization are high.

A Worked Decision

Valve order, three steps: lathe 4.0 hours, mill 6.0 hours, QC bay 1.0 hours. The job is 60 percent complete with the lathe and mill carrying actuals. Engineering has moved QC from the QC bay to a test cell and cut its time to 0.75 hours.

Compare first: one work center change and one timing change, both on the only remaining step.

Decide: the QC operation has not started, so nothing is set up against the old version. Refreshing is safe and the 0.25 hour saving is real.

Apply: tick Use Global BOR on Reschedule on this job.

Run: a targeted reschedule. The QC step re-plans onto the test cell at 0.75 hours. The lathe and mill steps keep their logged dates and hours exactly.

Verify and communicate: confirm the copy now shows the test cell, confirm the completed steps are untouched, and reprint the traveler because it names the QC bay.

Five minutes, and the change lands where it should without surprising anyone.

Where to Go Next

Production routing snapshots covers what is captured and why. Why frozen routings protect in-flight jobs explains the write rules and the hybrid merge with worked numbers. Routing snapshot mistakes covers the traps this procedure avoids.

For routing structure generally, production routing is the primer, and the graphical routing designer tour covers the canvas. The platform overview is the complete guide to EDGEBIC. Bring a routing revision and a list of open orders to a demo of EDGEBIC and we will work the decision together.