How to Schedule a Rush Order in EDGEBIC

To schedule a rush order in EDGEBIC, give it a priority number lower than the jobs it must beat, save, then run the scheduler with the affected jobs ticked. Priority is the lever: the engine sorts the queue by priority and plans each job completely before the next, so on a loaded plant the number is the plan. There is no expedite mode and no mode picker. EDGEBIC by User Solutions expedites through the ordinary run, which means the same safety nets apply and you always see the cost to the jobs the rush order displaces.

This post is the rush-order sequence. For the mechanics of the run, read how to run the scheduler in EDGEBIC; for the priority field itself, how to set a job priority is the companion. Everything is indexed at the EDGEBIC how-to hub.

Before You Start

• The rush order exists, or you are ready to create it. How to create a manufacturing order covers the entry.
• You know which existing jobs share the rush order's work centers, because those are the ones it will displace.
• At least one active shift exists and the rush order's product has a routing.

The Steps

1. Open the Schedule area and select the Drive Schedule tab.
2. Set the rush order's priority below the jobs it must beat. Type the number into the Priority cell, or drag the row above them with the grip handle. With priority bands (10, 20, 30) you can slot it in at 5 or 15 without renumbering anything else.
3. Set the due date to the promised ship date if it is not already set.
4. Click Save Changes on the filter bar.
5. Tick the right scope. Tick the rush order and the jobs it will displace on the shared work centers, so their new dates are computed in the same run.
6. Press the schedule button and read the Confirm Scheduling dialog: it states how many jobs are new and how many will be rescheduled.
7. Confirm and let the progress overlay finish.

What Changes When You Save

The displaced jobs are the honest part of the trade. Expediting is not free: the hours the rush order needs come out of the same finite capacity everything else uses. Including the displaced jobs in the run, and reading their Days Late, is what turns a blind promotion into an informed decision.

How to Check It Worked

Read Days Late on the rush order first. Zero means the plan makes the date. A positive number, shown before the date passes, means even at the front of the queue the plant cannot build it in time.

Then read Days Late on the jobs you displaced. If promoting the rush order just pushed three other promises past their dates, you have swapped one late job for three, and that may not be the trade you wanted. The grid shows you the whole cost in one view.

Common Mistakes

Promoting the rush order without including the jobs it displaces. If you tick only the rush order, the displaced jobs keep their old dates on screen even though the plant reality has changed. Include them, so their new Days Late is computed and visible.

Expecting priority to add hours. Priority buys the front of the queue, not extra capacity. If the constraining work center is out of hours in the window, no number changes that. The real lever then is a per-day capacity override adding overtime on that machine for those days.

Using dense priority numbering. Inserting a rush job into a 1, 2, 3 list forces every row below it to renumber. Number in bands so a rush job is a single edit.

Forgetting to save before running. Priority edits are staged. If you leave Save Changes unpressed and run anyway, the queue is still the old one.

What to Do Next

If the rush order lands late even at priority 1, the constraint is not sequencing: work the checklist in how to see why a job is late. If the bottleneck is a specific machine, how to flag and schedule around a bottleneck covers anchoring it. Rush orders carry real cost beyond the schedule, and the real cost of rush orders in the job shop makes that case. The EDGEBIC product page covers the platform.