Production Attainment

Production attainment is actual good output divided by planned output for a period, expressed as a percentage. Hit the plan and attainment is 100%; make 900 good units against a 1,000-unit plan and attainment is 90%. It is the plant's daily heartbeat: did we make what we said we would?

Attainment is the metric a plant manager checks before coffee. It is blunt on purpose, one number that says whether yesterday landed. But its bluntness is also its trap: attainment tells you whether you hit the plan, never why you missed, and it can be gamed by softening the plan or running extra hours. This post defines attainment cleanly, walks the calculation, separates it from schedule attainment and adherence to plan, and shows why it belongs next to OEE rather than in place of it.

What is production attainment?

Production attainment is the ratio of what you actually produced to what you planned to produce, over a defined window, a shift, a day, a week. The standard form counts good units only, so scrap and rework do not paper over a miss:

• Actual output = good units produced in the period. Counting total units instead of good units flatters attainment and hides quality loss, so define it as first-pass good wherever you can.
• Planned output = the units the schedule committed to for that period, from the production plan or master schedule.
• Attainment = actual good output ÷ planned output, capped or uncapped by policy. Most plants cap at 100% so overproduction on an easy day cannot mask a shortfall elsewhere.

Attainment is a lagging, output-level indicator, it sits alongside the rest of a plant's manufacturing KPIs. It answers the demand-facing question (did we serve the schedule?) rather than the equipment question (how effectively did the asset run?). Those are different questions, and conflating them is where attainment gets misused.

How do you calculate production attainment?

Fix the period, fix the plan, count good units, divide. The discipline is in holding the plan and the counting rule steady:

1. Set the period and the plan before the period starts. Attainment measured against a plan revised mid-shift measures nothing. Lock the planned number when the shift begins.
2. Define "output" as good units. First-pass good, ideally, the same good-count logic OEE's Quality factor uses. Decide once whether reworked units count, and write it down.
3. Count actual good output from the line, not from memory. Counters or machine signals beat an end-of-shift tally, which drifts toward the plan number by wishful rounding.
4. Divide and, by policy, cap at 100%. Attainment = actual ÷ planned. Capping stops a 115% day from averaging out a 70% day into a comfortable-looking week.
5. Roll up by day, week, and product, not into one blended average. A blended plant attainment hides which line or SKU is missing. Track the mix.
6. Log the miss reason at the point of the miss. Attainment without a reason code is a scoreboard with no game plan; a short cause list turns each miss into something you can Pareto.

How is attainment different from schedule attainment and adherence to plan?

They are cousins that answer slightly different questions, and the difference is what the numerator forgives. Production attainment cares about total quantity; schedule attainment and adherence to plan care about making the right things in the right order.

The distinction bites in real plants. A line can hit 100% production attainment by overrunning an easy product to cover a shortfall on a hard one, total quantity looks fine while the customer waiting on the hard product still gets nothing. Schedule attainment catches that; raw production attainment does not. If your attainment is green but shipments are late, you are measuring quantity when you should be measuring the schedule.

What is a good production attainment percentage?

There is no universal number, and any published benchmark is folklore rather than an audited standard. Attainment is best judged against your own plant's history and against the honesty of your plan. Two cautions matter more than any target:

• Consistency beats height. A line that runs 92% every day is easier to schedule around than one that averages 100% by alternating 120% and 80%. Variability in attainment is itself a cost, it forces safety stock and overtime downstream.
• A plan you always beat is a soft plan. Attainment stuck at 105–115% usually means the plan is padded, not that the line is excellent. The number then measures sandbagging, not performance. Attainment is only meaningful against a plan set to true demonstrated capability.

For macro context on how much of installed capacity plants actually run, the Federal Reserve's monthly G.17 release is the authoritative U.S. reference, a reminder that real plants operate well below theoretical maximums no matter which metric you use.

Why do lines miss attainment?

Attainment misses trace back to the same loss families every plant fights, and naming them is the first step to fixing them. When a shift lands short, the cause is almost always one of these, in rough order of how often it goes unlogged:

• An unrealistic plan. Before blaming the floor, check the plan. A plan set above true demonstrated capability guarantees a miss no matter how the line runs, and it corrodes trust in the metric. The fix is planning to takt and demonstrated cycle time, not to hope.
• Downtime and changeovers. Every minute the line is stopped is output it will not recover without overtime. Long changeovers eat attainment quietly because they are "planned," so they rarely get counted as the culprit until someone totals the minutes.
• Speed losses and minor stops. A line running 8% below its true rate, or stalling for thirty seconds every few minutes, bleeds attainment without a single dramatic event. These are the losses paper logs never see.
• Quality fallout. Because attainment counts good units, scrap and rework subtract directly. A quality problem upstream shows up as an attainment miss downstream, which is why the two metrics have to be read together.
• Material and labor starvation. The line can only attain the plan if parts and people are there. A missing component or an unfilled shift caps attainment before the equipment ever gets a chance.

The pattern across all five: attainment is the symptom, not the diagnosis. The same shift that reports 88% attainment is also generating downtime records, count data, and reject tallies that name the cause, if those are being captured. That is precisely why attainment lives best next to OEE rather than alone.

How does production attainment relate to OEE?

Attainment tells you that you missed; OEE tells you where the time went. They are complementary, and using one without the other is how plants chase the wrong fix. A line can miss attainment for reasons OEE decomposes precisely, breakdowns and changeovers (Availability), slow cycles and micro-stops (Performance), or scrap and rework (Quality). The OEE calculation splits the miss into those three buckets; the six big losses name the specific culprits.

The dangerous case is attainment hitting 100% while OEE is poor. It happens when a plant covers a low-effectiveness line by throwing more hours or more machines at the plan, output lands, but the cost per unit quietly balloons and the capacity headroom is gone when demand rises. Attainment says "fine"; OEE says "you paid for it in overtime." Read together, they separate a genuinely healthy plan hit from an expensive one. Put your numbers through the OEE calculator to see which factor is eating the shortfall.

Attainment is also only as trustworthy as the count behind it, and end-of-shift attainment is an autopsy, the shift is over, the plan is missed, and nobody can act. Live attainment, updating hour by hour against the plan, turns the metric from a verdict into a warning: at hour four you can see the line is tracking to 88% and still do something about it. Plants that compute attainment and OEE from the same source signals, the way Harmony reads counts and stops straight off the floor rather than from a spreadsheet (see the platform), get one consistent story instead of a quantity number and an effectiveness number that disagree. For a worked customer example of that shift from paper to live floor data, see the CLS case study. Pair attainment with steady downtime tracking and the misses start explaining themselves.