Glossary (EDGEBIC)

What Is Schedule Attainment? EDGEBIC Definition and Formula

User Solutions TeamUser Solutions Team
|
6 min read

Schedule attainment is the fraction of jobs completed in a window that finished on or before their due date. It is the delivery-outcome half of a pair of shop metrics: where schedule adherence asks whether work started when the plan said, attainment asks whether the work landed when it was promised. EDGEBIC by User Solutions computes it on the Planner dashboard tab over a rolling 14 day window, with a target of 85 percent or better.

This entry is part of the EDGEBIC glossary series introduced on the platform overview; the broader vocabulary index sits in the manufacturing glossary. Its partner metric is schedule adherence, and its customer-facing cousin is the on-time delivery rate.

How Schedule Attainment Works

Cooking a dinner party makes the pair easy to hold apart. Adherence is whether each dish went into the oven at the time the plan said. Attainment is whether dinner reached the table at seven. You can follow every step of the plan and still serve late because a step was underestimated, and you can improvise wildly and still serve on time. Two questions, two numbers.

Attainment counts jobs, not operations. Every job that reached a completed state inside the window is a candidate. For each one, EDGEBIC compares the job's end time against its due date. If the end is on or before the due date, the job counts as attained. Divide attained jobs by completed jobs and multiply by 100.

Three properties follow from that definition, and each one saves an argument later.

Only completed jobs count. A job still running does not appear, however late it is heading. That is what keeps attainment an outcome metric rather than a forecast. The forward-looking view of jobs whose plan already misses its date belongs to the Late Jobs report instead.

The comparison is against the job's own due date, not against a customer promise. A job can miss its internal date and still reach the customer on time when the promise carried a delivery tail or the order allowed slack. When attainment slips without customer complaints, what you are watching is a buffer being consumed.

The tile is labeled Plan, not Live. Until kiosk completions fully replace the scheduler's projected end, the finish date being compared is a projection. EDGEBIC marks that provenance on the tile rather than presenting a projection as a captured fact.

A Concrete Example

Take a 14 day window, June 1 to June 14, on a shop that runs a few dozen jobs a fortnight.

In that window, 22 jobs reached completion. Checking each one's end against its due date, 18 finished on or before it and 4 finished after.

Schedule attainment = 18 divided by 22, times 100 = 81.8 percent.

That sits below the 85 percent target, so the tile colors amber. Beside it on the same tab, adherence over the same window reads 70.8 percent: 120 operations were scheduled to start, 85 started within an hour of plan, and 35 had no logged actual start at all.

Read together the two numbers tell a story neither tells alone. Execution is drifting badly at the operation level, and delivery is only just holding. The four missed jobs are not yet a crisis, but the adherence figure says the shop is running on judgment rather than on plan, and the buffer that is currently absorbing that drift is finite. If adherence stays at 70, attainment usually follows it down.

How EDGEBIC Uses Schedule Attainment

Attainment is one of the two headline metrics on the Planner tab of the dashboard cockpit, rendered as a KPI tile with a 30 day sparkline, a target summary reading "Target 85 percent or better", and a data quality chip. A few behaviors matter in daily use:

  • There is no auto-refresh. The tab loads a snapshot, so after a schedule run you click Refresh to see the new picture. Comparing the two headline numbers before and after a run is the fastest way to tell whether a reschedule genuinely improved things.
  • The sparkline is the signal, not the value. A single fortnight's attainment moves with job mix; the 30 day trend is what tells you whether the shop is drifting.
  • It sits beside the late-jobs count. Attainment reports what already happened; the late-jobs tile reports what the current plan is about to do. Reading them together separates a historical problem from a live one.

The step by step tour, including how the two headline tiles and the forward load heatmap fit on one screen, is in how to use the planner dashboard. For how the whole cockpit is assembled across its tabs, see the EDGEBIC dashboards guide.

Schedule attainment is the fraction of jobs completed in a window that finished on or before their due date. It measures delivery outcome rather than execution discipline: did the work actually land on time, whatever route it took to get there. EDGEBIC computes it on the Planner dashboard tab over a rolling 14 day window with a target of 85 percent or better.

Adherence measures start timing, attainment measures finish outcome. Adherence asks whether each operation began within an hour of its planned start, so it catches the plan drifting operation by operation. Attainment asks whether completed jobs met their due dates, so it reports the delivery result. EDGEBIC shows both side by side on the Planner tab, adherence targeting 90 percent and attainment targeting 85 percent, because a shop can score well on one and badly on the other.

Because the finish date it compares against the due date is the scheduler's projected end until kiosk completions fully replace it. EDGEBIC labels every dashboard tile with its provenance: Live for a persisted real event, Plan for a projection from the schedule, Estimate for a heuristic, and Offline when the source data does not exist yet. Attainment reads Plan, so it becomes more trustworthy as actuals flow in from the floor.

Expert Q&A: Deep Dive

Q: Adherence reads 70 percent but attainment reads 90 percent. What is that combination telling me?

A: That the floor is departing from the sequence but still hitting due dates, which is the softer of the two failures. Three operations in ten are not starting within an hour of plan, so the plan is not being followed closely, yet the jobs still finish on time. Usually that means operators are resequencing with judgment that happens to work, or the plan carries enough slack to absorb the drift. It is worth understanding why the plan is being ignored, because that slack is a buffer you may be relying on without knowing it, but it is not the fire that low attainment would be.

Q: Attainment dropped this week but no customer complained. Should I act on it?

A: Yes, and early. Attainment counts jobs against their internal due dates, and a job can miss its due date while still reaching the customer on time because the promise date carries a delivery tail or the sales order allowed slack. That gap is a buffer being spent, not a problem being avoided. A sustained fall in attainment tells you the shop is now finishing later than planned as a matter of routine, which usually shows up as a customer conversation a few weeks after the metric does.

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

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.

Let's Solve Your Challenges Together