How to Set a Job Priority in EDGEBIC

To set a job priority in EDGEBIC, type a number into the Priority cell on the Drive Schedule grid or drag the row by its grip handle, then click Save Changes and run the scheduler. Lower numbers schedule first: priority 1 is planned before priority 2. On a loaded plant this single column does more work than any other setting, because EDGEBIC by User Solutions plans one job at a time and each job claims real capacity as it goes. The queue order is the plan.

This is the mechanics of the field. For the strategy behind the numbers, job priority and sequencing strategy goes deeper, and the EDGEBIC how-to hub indexes every task post.

Before You Start

• The jobs you want to reorder exist on the Drive Schedule grid.
• You know which jobs are already running. Recorded work is never moved by a re-run, so reprioritizing a job that is half built only affects its remaining steps.
• You are ready to run the scheduler afterwards, because priority edits do not move bars on their own.

The Steps

Option A: type the number

1. Open the Schedule area and select the Drive Schedule tab.
2. Click into the Priority cell on the row you want to change.
3. Type the new number. Lower means more important.
4. Repeat for any other rows.
5. Click Save Changes on the filter bar. The button appears only while there are unsaved edits.

Option B: drag the row

1. Find the grip handle, the six-dot column at the left edge of the row. Its tooltip reads "Drag to reorder priority".
2. Drag the row up or down. An insert indicator shows where it will land.
3. Drop it. Every affected priority renumbers automatically to match the new order.
4. Click Save Changes.

Then plan

5. Tick the jobs whose plans should reflect the new order. Unticked jobs keep their existing schedules and their reserved capacity.
6. Run the scheduler and confirm the job counts in the dialog that appears.

What Changes When You Save

The scope rule is the part planners underuse. Ticked rows define what gets re-planned. If you promote one job and tick only that job, everything else keeps its dates, and your promoted job fits into whatever capacity is genuinely free. If you tick everything, the whole plan is rebuilt against the new queue, which is more powerful and more disruptive.

How to Check It Worked

Run the scheduler, then compare the Start Date, Item Start and Job End columns before and after on the two jobs whose relative order you changed. The promoted job should start no later than it did. On a busy work center it should also visibly displace the demoted job.

If nothing moved at all, check the obvious cause first: the constrained work center may have had free capacity for both jobs anyway, in which case priority was never the binding constraint. Then check that you actually clicked Save Changes before running.

Common Mistakes

Navigating away without saving. Inline edits are staged, not auto-saved. If you leave the grid while Save Changes is still showing, the edits are lost and nobody tells you afterwards why the run ignored your reordering.

Using dense numbering. Number in bands: 10, 20, 30. Inserting a rush job between 10 and 20 becomes a single edit instead of renumbering the whole list. The engine only reads the order, so gaps cost nothing.

Expecting priority to move bars by itself. It does not. Priority edits change master data, and the plan reflects the change only after the next run. This catches people who reorder ten rows, glance at an unchanged Gantt, and conclude the feature is broken.

Reprioritizing after the run instead of before it. Setting the queue first and running once is one movement of the bars. Running, disliking the sequence, reordering, and running again moves them twice, and the floor notices.

Leaving deliberate ties. Ties break by start date then due date, which may or may not match your intent. If the order matters, give the jobs different numbers.

What to Do Next

Priority is the first lever when a job needs to jump the queue; how to schedule a rush order walks the whole sequence for a genuine emergency. If a job is landing later than expected even at priority 1, the checklist in how to see why a job is late will find the real constraint. For background on sequencing rules as a discipline, priority rules in the job shop covers the classic approaches, and the EDGEBIC product page covers the platform.