We use first and third-party cookies and other tracking technologies partner (Microsoft Clarity, Google Analytics, and Microsoft Advertising) to better undersand how you use and interact with our website. We use this information for site optimization, fraud/security purposes, and advertising. For more information, visit the Privacy Statement. Close

 
OEE · Continuous Improvement · Case Study

OEE Visibility That Drove a $2M Capacity Decision

Proficy OEE data gave a potato chip manufacturer the confidence to invest in a new line — because they could finally prove where the constraint actually was.

+14 pts
OEE improvement on the constrained line in 90 days
$2M
Capital decision justified with live Proficy OEE data
6 wks
From Proficy go-live to first board-ready OEE report
Industry: Snack Food — Potato Chips
Products: Proficy Plant Applications · Proficy OEE
Timeline: 12-week implementation
Team: Rain Engineering — Implementation & Education

A plant running hard — but nobody knew how hard

This scenario represents outcomes typical of our Proficy OEE engagements in snack food manufacturing. This regional snack food producer had been running three kettle chip lines at what every supervisor described as “near capacity.” Demand was outpacing output, and the operations director had a decision to make: invest $2 million in a fourth line, or find a way to squeeze more out of the existing three.

The problem was, the data didn’t exist to answer that question honestly. Downtime was tracked in spreadsheets — when it was tracked at all. Shift supervisors had their own definitions of “a good run.” The maintenance team was chasing fires without any visibility into whether those fires were getting worse or better. Corporate was asking for OEE numbers, and the plant was producing estimates.

The operations director’s words in the first meeting: “We think Line 2 is our bottleneck, but we’re not certain. And I’m not going to ask the board for $2 million based on a hunch.”

The Core Problem
“We think Line 2 is our bottleneck — but we’re not certain. And I’m not going to ask the board for $2 million based on a hunch.”

Line OEE — Baseline vs. Post-Implementation

90 days before and after Proficy Plant Applications go-live
Proficy OEE Data
Overall Equipment Effectiveness by Line
Line 1 — Tortilla Chips Before: 71%  |  After: 78%
Line 2 — Kettle Chips (Identified Constraint) Before: 54%  |  After: 68%
⚠ Confirmed constraint — identified by Proficy within first 2 weeks of data collection
Line 3 — Cheese Puffs Before: 67%  |  After: 74%
Line 2 Loss Analysis — Where the Time Was Going
Availability
62%
Unplanned stops were eating 38% of scheduled time. Primary culprit: seasoning applicator jams averaging 23 min/event.
Biggest gap found
Performance
81%
Line ran at 81% of rated speed — minor speed losses from belt tension changes during flavor changeovers.
Quality
97%
Quality rate was strong. Not the problem — critical to confirm before chasing it.

Connect the equipment. Let the data speak.

Rain Engineering’s first task was getting clean, real-time data from the floor into Proficy Plant Applications. The three lines ran a mix of older Allen-Bradley PLCs and a newer Siemens S7 installation — all of which needed to be talking to Proficy’s OEE module consistently before any analysis could begin.

We also spent time at the beginning of the engagement doing something that often gets skipped: agreeing on definitions. What counts as an unplanned stop? How long does a slowdown have to last before it’s logged? What’s the standard batch size for each SKU? Without these agreements in place, OEE numbers mean different things to different people — and they can’t be trended over time.

Within two weeks of go-live, the data told a story that surprised even the supervisors who had been on Line 2 for years: availability was the problem, not throughput rate. The line wasn’t running slow — it was stopping too often, and the stops were concentrated around one specific piece of equipment.

1
Weeks 1–2 · Discovery
Equipment audit & definition alignment
Mapped all data points from PLCs to Proficy tags. Ran workshops with operations, maintenance, and quality to align on OEE definitions — the step most implementations skip and later regret.
2
Weeks 3–5 · Implementation
Proficy Plant Applications go-live across all three lines
Configured downtime reason codes, production schedule integration, and real-time OEE dashboards for each shift supervisor. Operators began logging reasons on touch panels — no more paper sheets.
3
Week 6 · First Insight
Proficy confirms Line 2 as the constraint — with specifics
The seasoning applicator on Line 2 was responsible for 61% of all unplanned downtime across the plant. Not suspected — proven. Maintenance had the part numbers ordered within 48 hours.
4
Weeks 7–10 · Improvement
Targeted maintenance and process adjustments on Line 2
With the constraint identified, the maintenance team implemented a PM schedule specific to the seasoning applicator. OEE on Line 2 climbed from 54% to 68% — a 14-point gain in 90 days.
5
Week 12 · Decision
Board presentation: the data supports a fourth line
Even with Line 2 improved, Proficy’s forward projection models showed the plant could not meet next-year demand without additional capacity. The operations director presented to the board with 90 days of live OEE data. The $2M line was approved.

“We didn’t buy a fourth line because we guessed we needed it. We bought it because Proficy showed us, with 90 days of data, that we’d already found every efficiency gain available — and demand still outpaced us.”

Operations Director · Regional Snack Food Manufacturer · Southeastern U.S.

What 90 days of honest data delivered

+14 pts
OEE Gain on Line 2
From 54% to 68% in 90 days — achieved by fixing the identified seasoning applicator issue, not by buying new equipment.
$2M
Capital Decision Justified
Board approved a fourth production line — with confidence — because the data proved existing lines were genuinely at their recoverable ceiling.
To First Board-Ready Report
From Proficy go-live to a presentation-quality OEE trend report the operations director could put in front of executives.
61%
Downtime Concentrated in One Root Cause
Of all unplanned downtime across three lines, 61% was traceable to a single component — invisible before Proficy, obvious after two weeks of data.

The honest part of the story

The technology was the easy part. Proficy Plant Applications is a mature, capable platform — it does what it’s designed to do when it’s configured correctly. What made this engagement different was the time we spent before the first tag was mapped.

Getting operations, maintenance, and quality in the same room to agree on what “availability” means — before anyone sees a dashboard — is the work that most implementations skip. When those definitions are missing, you end up with OEE numbers that supervisors argue about instead of act on.

The other factor was patience with the data. The operations director gave the system 90 days before drawing any capital conclusions. That discipline — not reacting to the first week of numbers — is what produced a defensible, trend-backed story for the board. Proficy gave them the data. They gave themselves the time to let it mean something. This scenario represents outcomes typical of our Proficy OEE engagements in snack food manufacturing.

Is your OEE data telling you the truth?

We do a free, no-obligation Proficy readiness assessment for snack food manufacturers. 90 minutes with your ops team. You leave knowing exactly where your data gaps are.