How to Schedule a Single Job in EDGEBIC

To schedule a single job in EDGEBIC, tick only that row on the Drive Schedule tab and press the schedule button, or open the Job View tab and click Re-Schedule. Either path re-plans that one job while every other job keeps its dates and its reserved capacity. This is the most useful discipline in the whole product: narrow scope means fewer bars move, and a plan that does not churn is a plan the shop floor believes. EDGEBIC by User Solutions makes the scope explicit at every step.

For the general run, read how to run the scheduler in EDGEBIC. For what the engine does inside a pass, inside an EDGEBIC scheduling run goes further. Every task guide is indexed at the EDGEBIC how-to hub.

Before You Start

• The job exists on the Drive Schedule grid, scheduled or not.
• At least one active shift exists, otherwise the run stops and offers to create one.
• The job's product has a routing. An order with no routing is reported as a failure and dropped from the run.
• Work center calendars and capacity are current, because the pass plans against them as they are right now.

Path A: From the Drive Schedule Grid

1. Open the Schedule area and select the Drive Schedule tab.
2. Tick the Select checkbox on that one row. Untick everything else. If a filter is active, make sure the row you ticked is the row you think it is.
3. Press the schedule button.
4. Read the Confirm Scheduling dialog. It states how many jobs are new (first-time scheduling) and how many existing jobs will be rescheduled. For a single job it should read 1. If it reads more, answer no and check your selection.
5. Confirm and watch the progress overlay. The grid is locked while the pass runs, and the Cancel button is always safe: nothing partial is kept.

Path B: From the Job View Tab

1. Open the Job View tab and pick the job in the Select Job dropdown.
2. Click Re-Schedule on the control bar.
3. Confirm the prompt, which asks whether to re-schedule that job and states that it will clear and regenerate the schedule for it.
4. Read the completion message confirming the job was re-scheduled.

Path B is the better habit when you are already looking at the job's operations, because there is no selection to get wrong.

What Changes When You Save

That fourth row is worth dwelling on. Because unselected jobs keep their reservations, a single-job run does not get to use hours that other jobs already claimed. Your job fits into the genuinely free space, which is exactly the answer you want when you are asking "can this one job move without breaking anything else".

How to Check It Worked

On the Drive Schedule row, read Start Date, Item Start, Job End and Days Late. Then spot-check a neighbor: pick a job you did not touch and confirm its dates are identical to what they were before. If a job you did not select moved, your scope was wider than you intended.

On the Job View tab, the per-operation grid shows Sched Start, Sched End, Actual Start and Actual End per step. Recorded actuals should be unchanged; only the remaining steps should carry new planned times.

Common Mistakes

Pressing the button with nothing ticked. The Schedule All Orders prompt then offers to include every order, and answering yes turns a one-job task into a plant-wide reshuffle. Tick first, or answer no.

Ticking while a filter is active. Selection follows the rows on screen. If you filter, tick, then change the filter, verify what the confirm dialog says before you commit.

Blaming the run for moving completed work. It cannot. Recorded work is never moved. What moved is the remaining work, resuming from the actual finish rather than from the old plan. Compare Actual Start and Actual End on the operation rows and the picture becomes clear.

Re-running one job repeatedly to chase a date. If it lands later than you want, the constraint is upstream of the run. Work the checklist in how to see why a job is late instead of running again and hoping.

What to Do Next

If the single job is urgent enough to displace others, how to schedule a rush order covers the priority sequence. To verify what a pass actually altered before you hand dates to the floor, see how to check what a scheduling run changed. For the wider argument about scope discipline, how EDGEBIC reduces schedule churn and the EDGEBIC product page are the next reads.