The On-Time Delivery report in EDGEBIC by User Solutions is in the Reports hub under Executive / KPI: give it a date range and it scores finished jobs against their due dates, forecasts unfinished ones, and prints the on-time percentage on the subtitle bar. It is both a scorecard and an early-warning list, and the difference between the two halves is the whole skill of reading it.
For how this report sits alongside Late Jobs and Earned Value, see the reports that answer "are we on time?". Every reporting task is indexed on the EDGEBIC how-to hub.
Before You Start
- Due dates are set on the orders. A job without a due date is skipped entirely and will never count for or against you.
- Actuals are being logged, and jobs are being closed. The score is built from finished jobs, and a job counts as finished only when every operation is finished.
- Customers are attached to orders if you want the by-customer view to mean anything.
Step 1: Open It and Choose the Period
Open Reports and click On-Time Delivery in the Executive / KPI group. Set From and To in the range dialog, then click OK.
Choose the period to match the question:
| Question | Range |
|---|---|
| Monthly delivery performance | First to last day of the month |
| Quarterly management review | The calendar quarter |
| How are we trending right now | Last 30 days |
| What is coming at us | Today through the next 60 days, read the forecast statuses only |
Step 2: Read the Three Header Figures
The subtitle bar carries the total job count, the on-time count, and the percentage. That percentage is the number to quote, and it is built from completed deliveries: jobs with a recorded actual end inside the window.
This is deliberate and it is worth explaining once to anyone who asks. Jobs still in progress appear in the grid so you can see what is coming, but they cannot be counted as delivered on time, because they have not been delivered.
Step 3: Read the Four Statuses
Each row carries a status, and the four values split cleanly into results and forecasts.
| Status | Meaning | Counts toward the score? |
|---|---|---|
| On time | Finished, actual end on or before the due date | Yes |
| Late | Finished, actual end after the due date | Yes |
| On track | Unfinished, scheduled end meets the due date | No |
| Forecast late | Unfinished, scheduled end lands past the due date | No |
Read the top two as history and the bottom two as your work list. A month at 94% with a screen full of forecast-late rows underneath is not a good month, it is a good month followed by a bad one.
Step 4: Look at It by Customer
The grid groups by customer, which turns a plant average into a set of relationships. One customer at 100% and one at 62% is a very different situation from everyone sitting at 81%, and only the grouped view shows the difference.
Filtering here is safe for looking and unsafe for quoting. The header percentage does not recompute when you filter the grid, so for a per-customer figure, export the filtered rows and count them there.
Step 5: Export the Month
Click Export to Excel for the numbers or Export to PDF for the record. Reports are point in time and never cached: re-running the same window next week can return a different figure as jobs complete. If a number goes into a management pack or a customer conversation, export it the moment you read it.
What Changes When You Run It
Nothing at all. The report is read-only and queries fresh on open, so it is safe to run during production or in front of a customer.
The follow-up actions change things: moving work on the Gantt, adjusting capacity for a day, or re-running the scheduler. None of them move completed work, which is why last month's score cannot be altered by this month's replanning.
How to Check It Worked
Two checks confirm you read it correctly. First, the total job count should look like a plausible number of completed jobs for the window; if it is much smaller than you expected, jobs are not being closed. Second, cross-check the forecast-late rows against the late jobs report. The same job numbers should appear in both, since both are reading the same plan against the same due dates.
Common Mistakes
- Filtering the grid and quoting the header. The header covers the whole window regardless of what the grid is showing.
- Expecting in-progress jobs in the score. They appear as rows, not as results. That is the report being honest about what a delivery is.
- Missing due dates. An order with no due date is silently skipped, which quietly inflates the percentage.
- Reading a single month as a trend. One month at 86% is a reading; three months moving 92, 89, 86 is a problem. Run the same window shape each month and keep the exports.
See how the plan behind these dates is built on the EDGEBIC product page.
Expert Q&A: Deep Dive
Q: Management wants one on-time number for last month. What exactly do I run, and what do I say it covers?
A: Run the report from the first to the last day of the month and read three figures off the subtitle bar: total jobs, on-time jobs, and the percentage. Say plainly that it covers completed deliveries in that window, because the denominator counts jobs that actually finished. Unfinished work in the same period appears in the grid as On track or Forecast late but is deliberately excluded from the score, which is the honest treatment: a job that has not shipped cannot have shipped on time. Export the PDF into the month's records at the same moment, since the report is point in time and next week's run of the same window can differ as late work completes.
Q: Half the grid reads Forecast late for next month. What is that actually telling me?
A: That the plan, not the shop floor, is already missing the dates, and you have weeks rather than days to fix it. Forecast late means the job is unfinished and its scheduled end lands past its due date, so the lateness is structural: it exists in the plan before anyone is behind on the work. Take those job numbers into the Late Jobs report, which ranks them by how many days late and adds a blocker hint, then into Work Center Utilization to see which station the plan is queuing them behind. A month of forecast-late rows usually resolves to one overloaded station and two routings, not to fifty separate problems.
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.