To find a job's scheduled dates in EDGEBIC, read the Start Date, Item Start and Job End columns on the Drive Schedule grid, or open the Job View tab for the date of every operation. The grid gives you the job-level window at a glance. Job View gives you the per-work-center breakdown. Knowing which date is which, and which one to quote a customer, is the whole skill here, and EDGEBIC by User Solutions keeps the planner's inputs and the engine's outputs as separate columns on purpose.
This is a reading task. For the run that produces these dates, see how to run the scheduler in EDGEBIC. The full library is at the EDGEBIC how-to hub.
Before You Start
- The job carries a Scheduled badge. An unscheduled job has no computed dates.
- You know the difference you are looking for: the job-level window, or the step-level detail.
Read the Job-Level Dates on the Grid
- Open the Schedule area and select the Drive Schedule tab.
- Read across the row:
| Column | What it tells you |
|---|---|
| Start Date | The job's start anchor. For jobs without one, the earliest scheduled start is shown. |
| Item Start | When the last work center operation ends: the moment the item physically exists. |
| Job End | Item Start plus the product's lead time in calendar days: the delivery-ready date. |
| Due Date | The promise. Blank due dates are filled once from the first planned end and never moved. |
| Days Late | The gap between Job End and Due Date, shown as a projection for open jobs. |
| Schedule Details | A one-line "Start: …" summary of the plan. |
That is enough to answer most questions: when does it start, when is it built, when can it ship, and is it going to be late.
Read the Step-Level Dates in Job View
- Open the Job View tab and pick the job in the Select Job dropdown.
- Read the summary panel for the whole-job window (Original Start and Original End) and the hours roll-up (Total Hours, Actual Hours, Remaining, % Complete).
- Read the per-operation grid below it: Sched Start, Sched End and Duration per work center step, alongside Actual Start and Actual End once the floor logs them.
- Set the date window with the Start and End pickers if operations fall outside the default view.
The Gantt beside the grid draws the same plan as bars, so you can read the dates as numbers or see them as a timeline.
What the Dates Are (and Are Not)
The scheduled Start Date and Item Start are the engine's output. The order's Start Time field is your input: the earliest the job may begin. EDGEBIC does not overwrite your Start Time with the computed dates, because doing so would quietly raise the earliest-start floor on every run and drift the job later and later. The two are meant to differ, and the grid keeps them apart.
How to Check It Worked
Confirm the row shows the Scheduled badge and the date columns are populated rather than blank. If Item Start and Job End are empty, the job is not scheduled yet, and there are no dates to find until you run it.
If the Job View step dates do not match what you see on the Gantt, check for unsaved drags. Job View reads the saved plan, so in-memory overrides you have not saved yet will not appear there until you save them.
Common Mistakes
Quoting Item Start when you mean the ship date. Item Start is when the item is built; Job End is when it can ship. If the product has a lead time, the two differ by that tail, and the customer cares about Job End.
Reading the order's Start Time as the scheduled start. Start Time is the earliest-start input, not the computed result. The scheduled start lives in Start Date and Item Start.
Expecting Job View to show unsaved drags. The step grid reads from the database. Save your Gantt changes first, or the step dates will lag what you moved on screen.
Treating a blank due date as an error. On a forward job it is not. The scheduler fills it once from the first planned end, giving you an honest baseline instead of a promise nobody made.
What to Do Next
If Days Late is not what you hoped, the checklist in how to see why a job is late finds the constraint. If a date change is what you actually need, how to change a job's due date is the task. The concept behind the two build dates is covered in end-item lead time: Item Start vs Job End, and the EDGEBIC product page covers the platform.
Expert Q&A: Deep Dive
Q: I need to tell a customer when their order ships. Which date do I quote?
A: Quote Job End, not Item Start. Item Start is when the last operation finishes and the item physically exists, but Job End adds the product's lead time in calendar days to reach the delivery-ready date, and that tail is real: it is packing, cure time, transit, or whatever the product's lead time represents. The Drive Schedule grid shows both columns side by side so you can see the gap. If Job End equals Item Start, the product has no lead time and the two dates coincide. Days Late is measured against Job End, so quoting that date keeps your promise and your lateness figure on the same clock.
Q: The grid shows the job-level dates but I need to know when a specific operation runs. How?
A: Open the Job View tab and select the job. The per-operation grid lists one row per work center step with Sched Start, Sched End and Duration, plus the actual dates once the floor logs them, and the Gantt beside it draws the same plan as bars. This is where you look to tell a machine operator when their step is due, or to see which day a particular work center is booked for this job. The grid on Drive Schedule only summarizes the whole job's window; the step-level truth lives in Job View, and it reads from the saved plan, so any unsaved Gantt drags will not appear there until you save them.
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
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.