End-item lead time is the delivery, cure, or ship tail that follows the last work-center operation of a job, measured in calendar days: it separates the moment the item physically exists from the delivery-ready date, and it consumes no work-center capacity. It is the two quiet days between a part coming off the final machine and landing on the customer's dock, modeled honestly without pretending those days are a machine operation.
This entry is part of the EDGEBIC by User Solutions glossary; the broader dictionary lives in the manufacturing glossary.
Why a Job Needs a Tail
A part is rarely shippable the instant it leaves the last machine. Paint has to cure. Adhesive has to set. Finished goods have to travel from the plant to the customer. That gap between "off the machine" and "ready for the customer" is real time the schedule must account for, but it is not machine time: no work center is busy while paint dries or a truck rolls.
Modeling that gap as a fake operation would be wrong, because it would consume capacity that is not actually used and distort machine load. End-item lead time is the honest alternative: a calendar delay attached to the product, not a step on a machine.
Two Dates, One Tail
End-item lead time splits a job's finish into two distinct dates:
- The item start date is the end of the last work-center operation. This is the moment the manufactured item physically exists, and it is when the lead-time clock starts.
- The job end date is the item start date plus the end-item lead time, applied forward in calendar days. This is the delivery-ready date.
When lead time is zero, the two dates coincide. When it is nonzero, the job end date sits later by exactly the tail. Critically, lateness is always judged against the job end date, so the dashboard, the Gantt, and the days-late figure all agree on whether a job made its promise.
On the Gantt, the tail renders as a display-only muted bar from the item start date to the job end date. It marks the delivery window visually while occupying no machine and blocking no capacity.
A Concrete Example
A product carries a 2-day end-item lead time for paint curing. A job's final machining operation finishes Wednesday at 4 PM.
The item start date is Wednesday 4 PM: the part now exists. The job end date is Friday: two calendar days of cure later, the part is delivery-ready. If the customer due date is Friday, the job is on time, even though the last machine stopped Wednesday. The dashboard classifies it against the Friday job end date, and the Gantt shows a muted tail bar stretching Wednesday to Friday so the cure window is visible to anyone reading the plan.
How EDGEBIC Uses It
In EDGEBIC, end-item lead time is a product-level value in calendar days that models the delivery, cure, or ship tail after a job's last operation. It creates the item-start-date to job-end-date split, drives the muted lead-time tail on the Gantt, and is the date every surface uses to classify a job as late, on time, or early.
Lead time also shapes just-in-time planning. When a job schedules backward, the engine subtracts the lead time from the due date to form the due anchor, so manufacturing finishes early enough for the tail to land the part on the due date. Distinct from a lead-time tail, which happens after the last step, is transit time, which is a delay between two steps mid-routing. For the full backward-scheduling mechanism and how the tail is reserved in front of the due date, see the backward scheduling overview.
End-item lead time is the delivery, cure, or ship tail that follows the last work-center operation of a job, measured in calendar days. It models the time between when the part comes off the final machine and when it is actually ready for the customer, such as paint curing for two days or freight taking three. It consumes no work-center capacity; it simply separates the moment the item physically exists from the delivery-ready date the schedule is judged against.
The item start date is the end of the last work-center operation, the moment the manufactured item physically exists and the lead-time clock starts. The job end date is the item start date plus the end-item lead time, applied forward in calendar days, which is the delivery-ready date. When lead time is zero, the two are the same. Lateness is always judged against the job end date, so every screen agrees on whether a job is on time.
No. The lead-time tail is a calendar delay, not a machine operation, so it books no work-center hours and blocks no capacity. On the Gantt it shows as a display-only muted bar from the item start date to the job end date, marking the delivery tail without occupying a machine. It only affects dates: when the item is ready to ship and how backward scheduling reserves time in front of the due date.
Expert Q&A: Deep Dive
Q: Our painted parts need two days to cure before they can ship, but that is not a machine step. How do we model it without inventing a fake operation?
A: Set the product's end-item lead time to 2 calendar days. That models the cure as a delivery-ready tail after the last operation, without adding a phantom work-center step that would consume capacity it does not actually use. The item start date lands when the part comes off the final machine, and the job end date sits two days later. Backward scheduling reserves those two days in front of the due date automatically, and the Gantt shows the tail as a muted bar so everyone can see the cure window.
Q: A job's last machine step finished Wednesday but the dashboard still calls it on time for a Friday due date. Why?
A: Because lateness is judged against the job end date, not the item start date. If the product carries a 2-day end-item lead time, the item start date is Wednesday, when it came off the machine, and the job end date is Friday, when it is delivery-ready. The dashboard, the Gantt, and the days-late calculation all classify against the job end date, so a Wednesday machine finish plus a 2-day tail is correctly on time for Friday.
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
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.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.