EDGEBIC How-To

How to Change a Job's Due Date in EDGEBIC

User Solutions TeamUser Solutions Team
|
7 min read

To change a job's due date in EDGEBIC, type the new date into the Due Date cell on the Drive Schedule grid, click Save Changes, then re-run the scheduler for that job. Due Date is one of three fields you can edit inline without opening a dialog, alongside Priority and Direction. The edit changes the promise. It does not move a single bar until you plan again, which is how EDGEBIC by User Solutions keeps a live plan from rewriting itself under the floor's feet.

This post covers the one task. For the run that follows it, read how to run the scheduler in EDGEBIC; the full task library is at the EDGEBIC how-to hub.

Before You Start

  • The job exists on the Drive Schedule grid.
  • You know the job's scheduling direction. Backward jobs require a due date and cannot be saved without one.
  • You know whether the job is closed. The Days Late column always reads 0 for completed jobs, so a due date change on a closed job has no visible effect there.

The Steps

  1. Open the Schedule area and select the Drive Schedule tab.
  2. Click into the Due Date cell on the job's row and type or pick the new date. The Save Changes button appears on the filter bar as soon as there is an unsaved edit.
  3. Repeat for any other rows whose promises are moving. Inline edits stage together.
  4. Click Save Changes. The dates are written to the orders.
  5. Tick the affected rows and run the scheduler. Read the Confirm Scheduling dialog: it reports how many jobs are new and how many existing jobs will be rescheduled.
  6. For a single job, use the Re-Schedule button on the Job View tab instead. It re-plans that job alone and leaves every other job's reservations alone.

If you prefer a dialog, click the edit button in the row's Actions column and change Due Date in the Edit Manufacturing Order window, then click Save Order.

What Changes When You Save

SurfaceEffect
The orderThe due date is written. Nothing else moves.
The planUnchanged until the next scheduling run for that job.
Days LateRecomputes as soon as the job has both a due date and a planned Job End.
Backward jobsThe due date is the anchor the whole plan works back from, so a change here changes where every operation lands on the next run.
AuditThe change is recorded in the job's history, readable from the row's audit trail button.

The direction of the job decides how much the new date actually matters to the engine. A forward job starts as early as it can and compares its end to the promise. A backward job works back from the promise itself, so moving the date moves the whole plan. That difference is covered in how to schedule a job backward from its due date.

How to Check It Worked

Read three columns on the row after the run: Due Date shows the new promise, Job End shows the delivery-ready date the plan produces, and Days Late shows the gap. Days Late of 0 means the plan makes the date. A positive number, shown before the date has passed, means it does not.

If Days Late did not move at all, check that the job carries a Scheduled badge. An unscheduled job has no Job End to compare against.

Common Mistakes

Filling in a due date you have not actually promised. A blank due date on a forward job is not a gap in the data. The scheduler fills it once from the job's own first planned end, which gives you a baseline that reflects reality. Type in a hopeful date instead and Days Late starts warning about a commitment nobody made.

Expecting the scheduler to move the date back for you. It fills a blank field once and never touches a populated one again. If the plan cannot make the date, EDGEBIC tells you with Days Late rather than quietly relaxing the promise. That is the behavior you want when a customer asks whether the date is still good.

Changing the date and not re-running. The plan does not react to master data edits by itself. Until you run, the bars, the dashboards and anything you printed still describe the old world.

Reading Days Late against Item Start. It compares against Job End, which is Item Start plus the product's lead time in calendar days. A job whose last operation finishes on the due date but whose product carries a two day lead time reads as two days late, correctly. The distinction is worth understanding before you argue with the number.

What to Do Next

If the new date is not achievable, the fastest lever is usually the queue: how to set a job priority in EDGEBIC explains what changing the number actually does. If you want to understand why the plan lands where it does, work the checklist in how to see why a job is late. For the wider picture of promising dates you can keep, on-time delivery with scheduling and the EDGEBIC product page both help.

Expert Q&A: Deep Dive

Q: The customer pulled a delivery in by a week. What do I change and in what order?

A: Change the date first, then re-plan, then read the result before you promise anything back. Type the earlier date into the job's Due Date cell, click Save Changes, tick that job, and run the scheduler. Now look at Days Late. If it reads 0, the plan already makes the new date and you can confirm. If it reads a positive number, the plan cannot make it as things stand, and you have three honest levers: raise the job's priority so it claims capacity ahead of others, add capacity on the constraining work center for those days, or go back with a date the plan can actually hold.

Q: I set the due dates on ten jobs but Days Late still reads 0 everywhere. Is the column broken?

A: Almost certainly not. Days Late compares Job End against Due Date, and Job End only exists once a job has been scheduled. If those ten rows still carry the Unscheduled badge, there is no planned end to compare against and the column correctly reads 0. Closed jobs also always read 0 by design. Run the scheduler for the ten jobs and the column becomes meaningful. Note that Job End is Item Start plus the product's lead time, so a job whose machining finishes on the due date but carries a two day tail reads as two days late.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together