How to Change a Product's Lead Time in EDGEBIC

To change a product's lead time in EDGEBIC by User Solutions, open the Product tab, click the edit button on the product's row, change the Lead Time value in calendar days, and click Save. The number takes effect on screen at once: every job for that product redraws its delivery-ready tail and the dashboard re-judges lateness against the new end. Machine bookings do not move until the next scheduling run. For the wider picture of what planning attributes do, read products and planning attributes explained.

Before you start

• The product exists. If not, start with how to add a new product.
• You know what the number represents: the finishing window after the last operation before the item is genuinely ready to deliver.
• You have agreement on the value. Lead time changes promise dates for every open job on that product, so it is worth a conversation with whoever owns delivery commitments.
• Note whether any of that product's jobs are close to their due dates. Those are the ones that will flip status the moment you save.

Steps

1. Open the Product tab from the main navigation.
2. Find the product. Type a fragment of its identifier into the search panel above the grid, or use the Category filter in the toolbar to narrow the list.
3. Check the current value in the Lead Time column before you change anything. It saves a second trip if the value was already correct.
4. Click the edit button in the row's Actions column. The Edit Product dialog opens.
5. Change Lead Time to the new number of calendar days. Enter 0 if there is no post-production tail at all.
6. Click Save.

That is the task. If the product is procured rather than made, the same field records how long the item takes to arrive from the supplier, and you can record the supplier alongside it on the product record.

What changes when you save

Lead time is the gap between two dates the schedule grids show separately:

Saving a new value updates three things immediately and one thing later.

• Job View and the scheduler Gantt redraw the slate-colored "Lead Time" tail band after every affected job's last operation.
• Schedule grids recompute Job End while Item Start stays put.
• The dashboard re-judges lateness against the new delivery-ready end, so a borderline job can move from on-time to at-risk without any operation moving.
• Backward scheduling uses the new value on the next scheduling run. It aims the last operation at the due date minus the lead time so the finished item, tail included, is ready on the promise date. See how to schedule a job backward from its due date.

No work center booking moves on save. Product edits never trigger a reschedule on their own.

How to check it worked

1. Confirm the new number in the Lead Time column of the product grid.
2. Open Job View or the Gantt for any open job on that product. The tail band should read the new day count, and the label follows the value.
3. Compare Item Start and Job End on a schedule grid row for the product. The gap between them should equal the new lead time in calendar days, weekends included.
4. If you increased lead time on a product with tight due dates, check the dashboard for jobs that have just changed status. Those are the ones to talk about before the next run.

Common mistakes

Assuming working days. Lead time is calendar days. Two days across a weekend is still 48 hours, which surprises planners who are used to shift-aware queue time.

Padding for safety. Lead time is for real post-production time. Inflating it hides capacity problems inside master data and makes every promise look later than it needs to be. Keep buffers visible in the schedule instead.

Expecting jobs to move immediately. The tail redraws at once, but nothing reschedules until the next run. If you need the machines to react to a big lead-time change, run the scheduler.

Forgetting who else is affected. One product's lead time changes the promise date on every open job for that product at once, not just the job that prompted the edit.

More single-task recipes live in the EDGEBIC how-to library. To see how the delivery-ready date connects to finite capacity planning across the plant, visit the EDGEBIC product page.