Why track OEE by shift instead of by day?

Because the variation between crews is usually larger than a daily average suggests, gaps of ten to fifteen OEE points between shifts are common and invisible in a blended number. Per-shift tracking lets you learn from your best crew, support your struggling one, and spot shift-specific support gaps like missing night-shift maintenance cover.

How do you calculate OEE for a single shift?

Use that shift's own planned production time, run time, good output, and defects, then compute availability × performance × quality as usual. The key discipline is attribution: fix the shift boundaries, assign each stop to the shift it occurred in, and tag its loss category so comparisons stay fair.

How do you keep per-shift OEE fair to the shift that owns changeovers?

Split each shift's loss into inherited losses (changeover the schedule handed it, cold startup the day began with) and controllable losses (minor stops, slow running, quality). Compare crews on the controllable slice, rotate who owns changeovers and startup, and normalize for product mix so a shift running hard SKUs is not judged against one running easy ones.

What is a good per-shift OEE score?

The reference points are the same as for line-level OEE: the world-class 85% figure from the 90% x 95% x 99% split is a common yardstick, not an audited requirement. Applied per shift it mainly lets you compare crews on one scale. What counts as good depends far more on your process type than on the shift.

Is OEE defined by a standard?

Yes. ISO 22400-2:2014 defines OEE and its component ratios among 34 manufacturing KPIs, giving each a formula and a consistent basis. Per-shift tracking applies those same definitions to a narrower time window rather than changing them, which keeps every crew's number computed the same way.

Does per-shift OEE replace daily line OEE?

No, they are the same data at different zoom levels. Roll the shifts up and you get the daily line OEE for trend and targets; break the day down and you get the crew-level detail for action. A plant needs both, and reading them together keeps the crew comparison honest.

Per-Shift OEE Tracking

Q: What is per-shift OEE tracking?

It is running the OEE calculation once per shift instead of once per day, with each shift's availability, performance, and quality drawn only from the hours that crew worked. It produces a separate OEE for each shift, exposing crew-to-crew gaps that a blended daily average hides.

Splitting OEE by crew to expose shift-to-shift gaps, without punishing the shift that happens to own the changeovers and cold starts.

Per-shift OEE tracking calculates OEE separately for each crew's shift, using that shift's own planned production time, run time, good output, and defects. It exposes crew-to-crew performance gaps that a daily or line-level OEE average quietly hides.

A line that runs 72% OEE across a day almost never runs 72% on every shift. One crew is at 80%, another at 63%, and the blended number tells you none of that. Per-shift tracking splits the score by crew so the gap becomes visible and coachable. The catch is fairness: the shift that owns the morning cold-start or the mid-run changeover will look worse for reasons it does not control. This guide covers how to calculate OEE per shift, how to read the gaps, and how to do it without punishing the shift that happens to own the hard hours.

What is per-shift OEE tracking?

It is the same OEE calculation availability × performance × quality, run once per shift instead of once per day, with each shift's numbers drawn only from the hours that shift actually worked. Instead of a single daily figure, you get a first-shift OEE, a second-shift OEE, and a third, each standing on its own inputs.

The reason this matters is that a shift is the natural unit of a crew, a supervisor, and a set of habits. When OEE is aggregated above that level, every crew's result is averaged into everyone else's, and the plant loses the ability to see which practices work. Per-shift tracking restores that resolution. It turns OEE from a plant scorecard into a management tool, because now the number maps to a team you can actually talk to.

Why track OEE by shift?

Because the variation between crews is usually larger than the variation the plant is chasing everywhere else. Shift-to-shift gaps of ten or fifteen OEE points are common, and they hide inside a daily average that looks stable. When you cannot see the gap, you cannot learn from your best crew or support your struggling one, you just report a plant number that moves for reasons nobody can name.

Tracking by shift converts that fog into a comparison. The best shift becomes a working example of what the line can do with the same equipment and the same products; the lagging shift becomes a specific, solvable coaching problem instead of a vague plant-wide deficit. It also surfaces support gaps, a night shift with no maintenance cover or no material handler will show a distinct loss signature that a blended figure erases. The point is not to rank crews for its own sake; it is to find the transferable practice and the fixable constraint.

The dashed line is the daily average. It is true and useless: every crew's real result, and the gap worth managing, lives in the bars, not the line.

How do you calculate OEE per shift?

Run each factor on that shift's own hours, and be deliberate about the boundary. The mechanics are identical to a normal OEE calculation; the discipline is in attribution, deciding which shift owns a stop that starts in one and ends in another.

Fix the shift boundaries and stick to them. Define exactly when each shift's clock starts and stops, including how overlap and handover minutes are assigned. Ambiguity here is where per-shift numbers stop being comparable.
Use each shift's own planned production time. Subtract that shift's breaks and planned downtime from its scheduled time. A shift with a scheduled deep-clean has less planned production time, not a worse score.
Attribute each stop to the shift it occurred in. A breakdown that spans the handover is split at the boundary or assigned by a written rule, decide once and apply it every day.
Tag the loss category, not just the minutes. Record whether the lost time was changeover, cold start, breakdown, or minor stops. This is what makes fair comparison possible later.
Compute availability, performance, and quality per shift. Three factors, three crews, from each shift's own inputs. Multiply for that shift's OEE.
Compare the loss mix, not only the headline. Read where each shift lost its points before ranking the totals. The number tells you who; the loss mix tells you why.

How do you avoid punishing the shift that owns changeovers or startup?

Separate the losses a shift causes from the losses it merely inherits. The unfairness in naive per-shift OEE is structural: the first shift often absorbs the cold start-up losses for the whole day, and whichever shift runs the schedule's changeovers eats availability that has nothing to do with how well its crew works. Compare raw headline OEE across those shifts and you will "discover" that the hardest-working crew is the worst, a conclusion that is both wrong and corrosive.

Two shifts can post identical OEE loss for opposite reasons. The loss mix, not the headline, tells you which crew to coach and which to support.

The fix is to read the loss categories you tagged. Split each shift's loss into inherited (changeover the schedule handed it, startup the day began with) and controllable (minor stops, slow running, and quality the crew influences). Compare crews on the controllable slice, and treat the inherited slice as a plant problem to engineer away, not a crew failing to punish. Two other guardrails help: rotate which shift owns changeovers and startup so the burden does not sit permanently on one crew, and normalize the comparison by product mix, since a shift that ran only hard SKUs is not losing to a shift that ran easy ones. Done this way, per-shift OEE becomes a fairness-aware coaching tool instead of a blame generator. The controllable slice is where performance loss analysis earns its keep.

What is a good per-shift OEE, and where does OEE come from?

The reference points are the same as for line-level OEE, applied per crew. The widely cited world-class OEE figure is 85% from the 90% availability × 95% performance × 99% quality split traced to Seiichi Nakajima's Total Productive Maintenance work, a reference standard, not an audited requirement. Applied per shift, it is less a target than a common yardstick that lets you compare crews on the same scale and see how far the spread runs. What a good OEE score is depends far more on your process type than on the shift.

For a formal definition of the metric itself, OEE is standardized. ISO 22400-2:2014 the international standard for manufacturing operations KPIs defines OEE and its component ratios among 34 production indicators, giving each a formula and a consistent basis. Per-shift tracking does not change any of those definitions, it simply applies them to a narrower time window. Anchoring your per-shift method to the standard keeps every crew's number computed the same way, which is the whole point of comparing them.

What do per-shift OEE gaps usually reveal?

Once the comparison is fair, the gaps tend to point at a short list of causes, and almost none of them are "one crew is lazy." The recurring findings:

Method variation. The strong shift has a better way of doing a setup, a clear, or a restart, and it has never been written down. This is the best kind of gap to find, because the fix is to standardize the good crew's method across the others.
Support asymmetry. Nights run without a maintenance tech or a material handler that days take for granted, so a stop that days clear in minutes strands nights for an hour. The gap is in staffing the shift, not in the crew.
Handover leakage. Minutes and context bleed out at the shift change, a machine left mid-fault, a note never passed. A disciplined shift handover process recovers loss that no single crew is causing.
Training depth. A shift carrying several newer operators runs slower and reworks more until they are trained, which shows as a temporary, closable performance gap rather than a permanent deficit.

Every one of these is a system fix, not a disciplinary one. That is the quiet payoff of per-shift OEE done fairly: it consistently converts what looks like a people problem into a method, staffing, or training problem you can actually solve.

How does per-shift OEE connect to the bigger picture?

Per-shift OEE is the resolution layer under your plant metrics, not a separate report. Roll the shifts up and you get the daily line OEE you already track; break the day down and you get the crew-level detail you need to improve it. The two views are the same data at different zoom levels, and a plant needs both, the aggregate for trend and targets, the per-shift for action. Reading per-shift results next to your broader plant KPIs keeps the crew comparison honest, because a shift that runs a harder product mix or absorbs more downtime is not simply worse.

The whole approach depends on capturing stops, counts, and reason codes automatically at the shift boundary, because hand-logged per-shift data is exactly where attribution errors and end-of-shift guesswork creep in. When run time and stops are recorded from machine signals with the shift stamped on every event, the boundary is exact and the loss categories are trustworthy, which is what makes the fairness adjustments above possible at all. Harmony logs shift-stamped stops and counts with operator-confirmed reasons (see the platform or the CLS results). From there, decompose the biggest losses with the six big losses and pressure-test targets in the OEE calculator.