How to Run the Late Jobs Report in EDGEBIC

The Late Jobs report in EDGEBIC by User Solutions lives in the Reports hub under the Supervisor / Planner group, asks for no date range, and ranks every scheduled job whose scheduled end lands past its due date, worst first. It is the shortest useful report in the catalog and the one most planners open before anything else in the morning. This is the task, start to finish: run it, read a row correctly, and turn the top of the list into a decision.

For the wider picture of which report answers which question, see the reports that answer "are we on time?". Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Jobs have been scheduled at least once. The report reads the plan, so an empty plan produces an empty report.
• Due dates are set on the orders you want tracked. A job with no due date can never appear here.
• Actuals are being logged. Percent complete and the status label compare logged work against plan, so without actuals both read as if nothing has happened.

Step 1: Open the Report

Open Reports from the main navigation. The hub shows one tile per report under four group headers. Click Late Jobs in the Supervisor / Planner group.

No date range dialog appears. Late Jobs is a snapshot report: it describes the plan as it stands at the moment you click, the same way a stock count describes a shelf. That also means it queries fresh every time, so re-opening it is the refresh.

Step 2: Read the Ranking Before the Rows

The grid arrives sorted by Days Late descending, so the worst job is the first row. Days late is the whole number of days between the scheduled end of the job's last operation and its due date. A job whose plan meets the date is excluded entirely, which is why the report is usually short even in a busy shop.

Resist re-sorting immediately. The delivered order is the one the report was designed around, and re-sorting by customer or product before you have read the top five turns a triage list back into a data dump.

Step 3: Read One Row Properly

Days late and percent complete have to be read together. Nine days late at 82% complete is a finishing problem. Four days late at 0% is a starting problem, and it grows every day nobody touches it.

Step 4: Use the Blocker Hint

The hint is generated per row from the job's own numbers, and it names the fastest place to look:

• No actuals, never started. The job is in the plan and nothing has been logged against it. Confirm with the shop floor whether it truly has not begun or whether actuals simply are not being logged.
• Significantly behind plan. Work started but progress is well short of where the plan expected it by now. Check capacity on the operations still open.
• Schedule slipped. The dates moved. The reschedule history report will tell you when and by how much.

Step 5: Drill Into the Worst Row

From a late job, three drills answer nearly everything:

1. Job Progress, to see percent complete and the daily pieces track for the whole job.
2. Work Center Progress filtered to that job, to see which specific operation is holding it. That is the difference between "the job is 60% done" and "the mill step has 41 of 101 hours logged and nothing in three days".
3. Work Center Utilization, to see whether the station holding the job is over 100% loaded and what else is queued on it.

Full method for the first two is in how to check a job's progress.

Step 6: Export the Evidence

Click Export to PDF (or Export to Excel) in the report window footer if the list is driving a decision. Reports are point in time. Tomorrow's list will be different, and a dated export is what makes "we knew on Monday" provable.

What Changes When You Act

The report itself changes nothing. It is read-only, like every report in the catalog, and running it never touches a schedule.

The change happens where you act: move an operation on the Gantt, adjust a work center's capacity for a day, or re-run the scheduler. Whichever you choose, work already completed is never moved by a reschedule, so the fix lands on remaining work only.

How to Check It Worked

Re-run the schedule after your fix, then re-open Late Jobs. One of three things happens:

• The row is gone. The plan now meets the due date.
• Days late shrank. The fix helped but was not enough, and the new number tells you by how much.
• Nothing moved. The constraint is somewhere you have not looked yet, usually a station running above 100% for the whole window.

Common Mistakes

• Treating days late as a delivery fact. This is a projection from the current plan, not a record of a missed shipment. For delivered performance, use the on-time delivery report, which judges finished jobs by their actual end.
• Assuming an empty report means nothing is late. It can also mean due dates are missing. Spot-check a few orders before celebrating.
• Quoting the blocker hint as a cause. It is a heuristic pointer generated from the row's own numbers. It tells you where to look, not what is wrong.
• Reading percent complete on a shop that does not log actuals. Percent complete is built from logged hours. No logging means every job reads as barely started, and the hint on every row will say so.

See what EDGEBIC does with these numbers across the whole plant on the EDGEBIC product page.