The shop made every unit in the weekly target, but three scheduled orders still missed their planned completion deadlines. To measure production schedule adherence at the work order level, divide the number of frozen-plan orders completed in full by their scheduled deadline by the number of frozen-plan orders due in the period. Multiply by 100. A rush job can add to weekly output without increasing this score.
Freeze the schedule before work starts so every order keeps the quantity and deadline it had when the shop accepted the plan. Keep a live schedule for dispatching changes. The frozen copy gives you the basis for reviewing whether the original work was finished (including work that was moved or canceled after the freeze).
Freeze the scheduled orders and their deadlines
Save the plan version, snapshot time, reporting window, order key, planned good quantity, and due date and time. Use a stable operation key if your unit of measurement is a scheduled operation. Keep the definitions for the plant’s shifts and time zone with the snapshot. A Sunday night shift can cross into Monday on the calendar while belonging to the same production day.
SAP documents an operation completion status that distinguishes work included at the schedule freeze from work dispatched in addition. The order-level calculation here applies that same separation to the work orders due in the reporting window. When the shop moves an order after the freeze, keep its original deadline for scoring and store the revised deadline for dispatch.
State when an order counts as complete. In this example, the rule requires the scheduled quantity of accepted units by the frozen deadline and gives credit for early completion. If your production sequence limits early builds, define a permitted window and record early work outside that window as its own exception. Use the confirmation event that represents accepted output so closing the order later does not move the time at which the shop finished the work.
Compare planned completions with actual output
Assume one line froze five orders due this week for a combined 330 units of the same item. Two orders finished by their deadlines. One completed after the week, one was short at its deadline, and one was still open when the week closed. The shop also completed a 120-unit rush order during the week that arrived after the freeze.
| Order | Frozen quantity | Accepted in the week | On time in full? |
|---|---|---|---|
| A | 100 | 100 | Yes |
| B | 80 | 80 | Yes |
| C | 60 | 0 | No, late |
| D | 50 | 30 | No, partial |
| E | 40 | 0 | No, open |
| Rush order | Outside the frozen plan | 120 | Outside the cohort |
Production schedule adherence is 2 ÷ 5 × 100 = 40%. Weekly output is 330 ÷ 330 × 100 = 100% of the original unit target because the rush order made up the shortfall in volume. Both readings describe the same week. The first keeps the original work in view and the second answers how many units the line made.
Names vary across tools. Oracle documents a workstation plan adherence metric that compares actual with target operation quantities during a shift. Label the measure here “frozen orders completed on time in full” when both approaches appear in a report. If you also publish unit attainment, restrict unit totals to comparable items or use an approved common basis.
Record what changed after release
Start the shift review with orders that missed the original deadline. A delay caused by a documented shortage calls for a different discussion from one caused by an approved rush order. Tie the reason and approval to the order, and distinguish incomplete physical work from a missing confirmation. If a completion posted the next morning, inspect the event time and the time the system received it before classifying it.
Keep canceled and split orders visible. Apply a declared cancellation policy and reconcile exclusions to the frozen total. When a frozen order is split into several jobs, link the jobs back to the original order before testing quantity and deadline. Counting child jobs as separate commitments can inflate both sides of the fraction. If no frozen orders were due, show that the metric is unavailable for that period because there is no denominator.
Use the production schedule template to record the next work center plan and its constraints. Include who approved a change so the next shift can tell which jobs to dispatch and which dates belong to the frozen comparison.
When the same order appears in snapshots for two successive weeks, attribute each score to its own due cohort. The miss from the first week stays visible. If the order is rescheduled and due again in the next frozen plan, label it as carryover so the team can distinguish a repeated commitment from a new job. Count a job once per cohort even if it has several confirmations.
A manufacturing dashboard can show the adherence score beside output and a breakdown of misses by reason. Keep the number of orders due next to the percentage. A week with one missed order out of five has the same percentage as a week with twenty misses out of a hundred, but the number of orders to investigate differs.
Before releasing the report, reconcile the scheduled orders to those completed on time, missed, or excluded under the declared policy. Keep added work outside that reconciliation. If an order has a confirmation but its key cannot be matched to the plan, investigate the key or record the exception before assigning credit.
Inspect how orders are confirmed in one source
Connect a supported source and check which permitted records carry the accepted quantity, order ID, and confirmation timestamp.
Where Permute fits in schedule review
Permute is the context layer we sell between business records and the AI tools people use. We can connect supported sources and relate the frozen schedule, order confirmations, and revision records you provide.
We can apply the same declared completion and cancellation rules across reporting periods. Show missed commitments and added work as separate categories and retain the source rows behind each result.
A production supervisor can ask which frozen orders missed and inspect the deadlines, completion records, and exceptions they’re allowed to see.
Keep dispatch decisions on the shop floor
We read connected sources and do not write back to the system of record. The production team owns changes to the live schedule, and the shop or quality team confirms the physical quantities completed.
Review original commitments alongside weekly output
Production schedule adherence checks whether the orders accepted at the freeze were completed by their original deadlines. The example reaches the unit target because it includes a rush order, while just two of the five frozen orders finished on time in full. Retain both views with the plan version and confirmations so the shift review can distinguish recovery work from commitments that were met.
Review a schedule miss with Permute
Bring the frozen snapshot and the completion and revision records for one line or shift.
Questions about scoring schedule changes and exceptions
Does a late completion improve the score for the original period?
Under the original-deadline rule it clears outstanding work and still counts as a miss in the period it was due. Use the completion record to show when the order recovered.
Is this the same as customer on-time in-full delivery?
The example checks internal work order completion. Customer delivery uses a shipping or delivery event and a customer commitment, which can have different dates.