The job status donut in EDGEBIC by User Solutions lives on the Capacity dashboard tab, in the Overview area's Active Alerts panel: it sorts every active job into one of four colored slices, Late, Overdue, On time, or Early, so you can see the health of the whole order book at a glance. Each job lands in exactly one slice, and the list beside the donut ranks them worst first.
The donut is one signal on the Capacity tab, which also carries the capacity load view covered in reading a red day on the capacity view. Misreading dashboard signals is common enough to warrant its own guide in dashboard misreading mistakes. Every task in this library is mapped on the EDGEBIC how-to hub.
Before You Start
- Jobs are scheduled. The donut classifies against the schedule, so an unscheduled job has nothing to place.
- Due dates are set. The four buckets are all defined relative to the due date.
- You have refreshed the tab. The dashboard does not auto-update, so a stale donut reflects the last time the tab was activated.
Step 1: Open the Capacity Tab
Open the Dashboard section from the main navigation. The Capacity tab is the default landing tab. In the Overview area, find the Active Alerts panel; the job status donut sits there with the Active Jobs list beside it.
Step 2: Read the Four Slices
Each slice is a schedule-margin bucket, and only active jobs are counted:
| Slice | Color | What it means |
|---|---|---|
| Late | Red | The job finished after its due date, or its current plan overruns the due date, flagged even before the due date arrives |
| Overdue | Amber | The plan meets the due date, but the due date has already passed with the job unfinished |
| On time | Green | The due date is still open and the plan lands exactly on it, or the job finished on or before it |
| Early | Teal | The due date is still open and the plan finishes before it, with slack |
Step 3: Work the Active Jobs List
The list beside the donut sorts worst first, so red Late jobs sit at the top. Each row carries an In progress badge when the job has physically started, which is shown separately from the slice because starting a job does not change whether it is on time. Read the badge and the slice together: a started job in the Late slice is running and behind, a Late job with no badge has not begun and is already structurally late.
Step 4: Read the Ready Date
The donut and the list classify against the delivery-ready end, which is the scheduled end plus the product's end-item lead time, and show a Ready date. This is why the buckets agree with the days-late column on the Drive Schedule grid: both account for the lead time a product needs after its last operation, not just the raw scheduled end.
How to Check It Worked
The donut is a read-only view, so nothing is saved. Confirm it worked by checking that a job you know is comfortably ahead reads Early or On time, and that a job whose plan overruns its due date reads Late even though its due date is still in the future. If the donut disagrees with the Drive Schedule grid, refresh the tab; the two are computed on the same delivery-ready basis and should line up.
Common Mistakes
- Reading On time as having a buffer. On time means the plan lands exactly on the due date with no slack. Early is the only bucket with real margin.
- Expecting a started job to change slice. Starting a job shows the In progress badge but does not move it between buckets. The slice is about dates, not activity.
- Confusing Late with Overdue. Late is a plan overrunning the due date, which can be true today. Overdue is a due date already past. Late is the earlier warning.
- Trusting a stale donut. The tab does not auto-refresh. Refresh before you read it against a fresh schedule run.
Related Reading
- Reading a red day on the capacity view: the capacity-load signal on the same tab.
- How to use the EDGEBIC dashboard tabs: the tour of all four cockpit tabs.
- EDGEBIC platform overview: where the dashboard fits in the wider system.
Expert Q&A: Deep Dive
Q: A job's plan finishes exactly on its due date. Why does it read On time rather than Early?
A: Because Early is reserved for plans that finish before the due date with genuine slack, while a plan landing exactly on the due date has no slack and is therefore On time, not Early. The distinction matters because a job sitting exactly on its due date has zero margin: any slip at all pushes it to Late. So On time here is not a comfortable state, it is a no-margin state. If you want a real buffer, the plan needs to finish before the due date, which is what moves it into the teal Early slice. Reading On time as safe and Early as safe-with-room is the right way to interpret the two green-family buckets.
Q: The donut disagrees with what I see on the Drive Schedule grid's days-late column. Which is right?
A: They should agree, and if they do it is because both classify against the delivery-ready end, which is the scheduled end plus the product's end-item lead time, not the raw scheduled end. A product that needs several days of lead time after its last operation finishes later than its schedule shows, and both the donut and the days-late column account for that, showing a Ready date. If they genuinely disagree, the usual cause is a stale view: refresh the dashboard, since it does not auto-update. Once refreshed against the same schedule, the donut's buckets and the grid's days-late figures line up because they are computed on the same delivery-ready basis.
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.