Subscribe
Share
Share
Embed
You are listening to the Value Gene Insight Conversations, AI-hosted podcasts by Value Gene Consulting Group. We are a boutique consulting firm focused entirely on the food industry. Our mission is to deliver strategic solutions that yield significant, rapid, and sustainable outcomes for Food Brands, Manufacturers and Distributors. In this series, we share our perspective on key market trends and the challenges facing the industry. Join us for practical strategies that deliver rapid, sustainable results.
In part three of the manufacturing misconceptions series, out AI hosts, Alice and James, focus on physical assets and explain why plant performance often stalls not because machines fail, but because belief driven decisions allow small issues to drift into chronic losses. They unpack four misconceptions about budgets, veteran know how, bottlenecks, and changeovers, then show how leaders can regain economic control by treating asset performance as an engineered system.
Keywords: Food Manufacturing, Asset Reliability, Asset Performance, Machines Fail, Maintenance Strategy, Patching Economics, Bottleneck Management, Changeovers, Poka-yoke, Downtime reduction, Yield Loss, OEE Improvement
Why physical assets fail quietly through drift
James (00:06): Welcome to Value Gene Insight Conversations.
Alice (00:08): Today we're moving into the third part of our series on manufacturing misconceptions.
James (00:13): We've already spent some time dissecting the hidden beliefs that can limit performance in, process design and people management.
Alice (00:21): And today we're turning our attention to the hardware, the physical assets.
James (00:26): Which is such a critical piece of the puzzle.
Alice (00:29): It is. When we look at food manufacturing specifically, performance challenges, they rarely stem from a lack of hard work or even technical know how.
James (00:37): Right.
Alice (00:38): Plants invest capital, teams are working incredibly hard, yet throughput and cost performance, they often stall.
James (00:45): And in our work, we find that these gaps trace back to hidden assumptions.
Alice (00:49): Which brings us to the core thesis of this whole series.
James (00:52): It's rarely the machine's fault. It's the belief system running the machine.
Alice (00:56): Exactly. We're looking at this concept of drift. When we talk about physical assets, conveyors, ovens, fillers, the damage rarely comes from some, you know, catastrophic explosion that makes the evening news.
James (01:08): It's much quieter than that.
Alice (01:09): It is. It's the cumulative effect of treating misconceptions as valid decision rules. And the cost, it gets paid in minutes lost, in yield waste, and in reliability issues that just become part of the background noise.
James (01:24): The normalization of problems. You stop seeing the crack in the wall because it's always been there. So looking at the research and the fieldwork, we've identified four major misconceptions regarding physical assets. Let’s start with the money. The first one is the tight budget trap.
Misconception: the tight budget trap
Alice (01:38): We see this constantly. It's usually framed as discipline. A plant manager or a VP of operations will say, our budget is tight this year. We need to focus on affordable fixes.
James (01:48): Just keep things running. The big spend can wait.
Alice (01:51): Exactly. And on the surface, that sounds responsible. It sounds like prudent management.
James (01:56): Right. It feels like being a good steward. You aren't asking for a massive CapEx capital expenditure check from headquarters. You're just keeping the line moving with what you have. Yeah.
James (02:05): So why do we consider that a trap?
Alice (02:07): Because if you dig deeper, what looks like discipline is actually just normalized mediocrity. Breakdowns, they stop being treated as signals that the system is failing, and they start being treated as features of the plant. The operators adapt, maintenance compensates, and the schedule just gets built around all the interruptions.
James (02:25): So you're paying for the problem, you're just not fixing it.
Alice (02:28): Precisely. We call this the economics of patching. Recurring, affordable fixes. They often cost significantly more than a rebuild would have over the same period.
James (02:40): But because the loss leaves the building in small increments
Alice (02:43): A belt here, a bearing there, a few hours of overtime
James (02:46): It never triggers a major decision event.
Alice (02:48): Exactly.
James (02:50): That conveyor belt example from the notes, I mean that feels like a classic death by a thousand cuts scenario.
Alice (02:56): It's a perfect case. This was a facility where they were replacing belts on a line every single month.
James (03:02): Every month.
Alice (03:02): Every month. Now, the expected life of those belts was nine months. So they were getting what? About 11% of the asset's life cycle?
James (03:09): And nobody flagged this. That seems like an incredible waste of material.
Alice (03:13): No one flagged it because the cost of a single belt is relatively low. It flies under the procurement radar.
James (03:18): I see.
Alice (03:19): But when we looked at the data, that gap meant eight extra stoppages over the life cycle. Each stoppage was about seven hours of downtime.
James (03:28): Seven hours each. So that's 56 of production lost capacity that the plant just absorbed.
Alice (03:35): Just absorbed it. And what was the root cause? Was it just a bad machine?
James (03:38): That was the assumption, right? It's an old machine, it eats belts.
Alice (03:42): That was the story. But the reality was lack of standards. The belts were being forced onto full length conveyors and basically micro damaged during installation.
James (03:51): So not the asset's age, it was the process.
Alice (03:53): It was the installation process. But because the fix was cheap, no one investigated the cause.
James (03:59): There's another example here that I think is even more damaging because it hits revenue, not just maintenance costs. The industrial oven.
Alice (04:06): This is where that tight budget trap gets really dangerous for the business model. We saw a plant with a large oven that had a hot spot on the left side. It was consistently over baking the product.
James (04:18): And the fix was too expensive, I assume?
Alice (04:20): The rebuild was considered too high for that fiscal year. So operations just compensated. They ran the oven slower or they accepted higher scrap rates.
James (04:28): But here's what they missed.
Alice (04:30): They missed that sales started losing accounts. Customers complained about inconsistent browning. The plant thought they were saving say 50,000 on a repair, but they were bleeding hundreds of thousands in lost contracts.
James (04:44): That is a terrifying disconnect between the factory floor and the bottom line.
Alice (04:48): It is.
James (04:49): We see a similar dynamic with utilities, right? Specifically HVAC. In food manufacturing, temperature control is obviously critical, yet it seems to the first thing cut from the budget.
Alice (05:00): It's viewed as a luxury. We observed a plant that refused to invest in proper HVAC upgrades. The system would fail, but only during the extremes, maybe two months out of the summer.
James (05:11): And leadership just treated a proper fix as optional. We can push through it.
Alice (05:15): That was the mindset. But pushing through implies you can maintain standards, which, of course, they could not. During those two months, waste quadrupled.
James (05:24): Quadrupled.
Alice (05:25): The temperature fluctuations affected the line's stability. You know, think of chocolate or dough behavior. And product consistency just tanked.
James (05:33): And the raw material got blamed. The operators got blamed.
Alice (05:37): But the system itself remained unchallenged. They were saving money on CapEx but bleeding cash and operational waste.
James (05:43): So why does this happen? If the math is so clear to us looking at the spreadsheets now, why isn't it clear to the leadership teams on-site?
Alice (05:52): It comes down to risk and incentives. Managers are often judged on very short term results, quarterly or annually.
James (05:59): And a major CapEx proposal invites scrutiny.
Alice (06:01): A lot of scrutiny. You have to build a business case. You have to defend your assumptions to a board. And if it fails, it's on you. It's a personal risk.
James (06:08): Whereas a repair invoice is just the cost of doing business.
Alice (06:11): Exactly. A recurring repair invoice flies under the radar. It doesn't trigger a board meeting. So the rational choice for a manager trying to minimize personal exposure is to keep patching.
James (06:22): True discipline isn't about spending avoidance then.
Alice (06:25): No, it's about financial intelligence distinguishing an investment from a recurring loss.
Misconception: the veteran knowledge ceiling
James (06:30): That leads us right into the second misconception, which is about who makes these decisions. Often, when we walk into a plant, there's that one person, the veteran.
Alice (06:40): The belief here is our veteran has been here thirty five years. He knows every bolt, every bearing. He knows what to invest in and what to fix.
James (06:49): And to be fair, we have immense respect for those veterans. They're often the reason the plant is still running at all.
Alice (06:55): Absolutely. Their institutional knowledge is invaluable, but there is a danger.
James (07:00): The danger is when that experience becomes the ceiling for improvement.
Alice (07:05): Exactly. The plant improves only within the bounds of what that veteran already knows.
James (07:09): It creates a situation where the solution space is limited to how we've always done it.
Alice (07:14): We saw a perfect example of this in a raw material handling process. This plant was feeding raw material bags into the process using a forklift.
James (07:22): Okay.
Alice (07:23): Every batch required waiting for the lift, loading the pallet, positioning it. It caused a recurring delay of about twenty to twenty five minutes per cycle.
James (07:30): But because it didn't technically break, nobody saw it as a problem to be fixed.
Alice (07:35): Precisely. It was just how the process works. The veteran operational leadership, they didn't see it as a problem because it was reliable, even if it was slow.
James (07:44): They weren't aware of other options.
Alice (07:46): Right. They weren't aware that vacuum conveying systems had evolved to the point where they could move that same material in two to three minutes.
James (07:53): That's a massive reduction in variability.
Alice (07:55): It is. But because the veteran didn't know the technology, the option was never on the table. We see this capability erosion often. Plants stop keeping up with the outside world.
James (08:07): They rely on internal memory rather than external engineering standards.
Alice (08:11): And there was another example of this with a viscous liquid line pumping something thick like syrup or batter. This plant had a recurring issue where the piping would clog. The veteran solution was manual intervention. Get the rod, take the pipe apart, clean it out.
James (08:27): It was hard work, but they were good at it.
Alice (08:29): They optimized the manual cleaning, but they completely missed the engineering solution.
James (08:34): Which was?
Alice (08:34): Modern inline sensors and automated flushing systems could have prevented the clog entirely. They could sense pressure changes and react before the blockage formed. They were optimizing a task that shouldn't have even existed.
James (08:46): And this reliance on internal know how, it often leads to that we can do it ourselves mentality. We see organizations avoiding external engineering support to save on fees.
Alice (08:58): That's a classic trap. We worked with the site that finally approved a major investment in new machines, a big step forward. They decided to manage the execution internally to save on engineering costs.
James (09:10): How did that play out?
Alice (09:11): Poorly. Three months before the machines were set to arrive, the factory was completely unprepared. Electrical work was incomplete. The layout wasn't resolved. Vendors hadn't been managed.
James (09:21): And the pressure mounted.
Alice (09:22): Two of their internal engineers actually quit. So the savings on that engineering overhead evaporated and then some. Costs inflated through delays and change requests. We had to bring in a specialist team to rebuild the layout and sequencing. And the interesting part is, once we applied proper engineering rigor, the revised design actually made space for two extra machines within the same budget.
James (09:44): That's the takeaway. Organizations have to combine that experience with modern engineering capability. You can't let how we've always done it prevent you from redesigning your constraints.
Misconception: the "static" bottlenecks
Alice (09:55): And speaking of constraints, that brings us to misconception number three: The idea of the obvious bottleneck.
James (10:03): This is one we hear in almost every kickoff meeting. We ask, Where's the bottleneck? And the team immediately points to a machine. It's the filler or it's the oven.
Alice (10:11): The belief is our bottleneck is obvious and static. We invest where it is slow.
James (10:15): But our perspective challenges that immediately.
Alice (10:18): Right. Bottlenecks are not static. They shift based on SKU mix. They shift based on ambient conditions. And very often they shift based on staffing.
James (10:26): That concept of the manufactured bottleneck is fascinating. It implies management decisions, not equipment limits, are often the true governor on output.
Alice (10:35): We see this all the time in labor intensive areas of food manufacturing like packaging or decoration. We had an engagement focused on revenue uplift where the site claimed they were at 100% capacity. They were telling sales, we can't ship any more product.
James (10:50): But the reality on the floor was different.
Alice (10:52): We looked at the decoration station. It was staffed with one person. That single person capped output at roughly 45 units per hour.
James (11:00): And that was the constraint?
Alice (11:02): That was the constraint on revenue. By adding a second person, output jumped to 90 units per hour.
James (11:07): Wow.
Alice (11:08): That simple labor decision likely made months ago to save a headcount was actually costing them double the throughput on a high demand SKU.
James (11:16): It seems like plants often lack what we call a living constraint view. Can you explain what that means?
Alice (11:22): A living constraint view just means understanding that your max speed isn't one number. Your rates have to be defined by SKU family and by staffing standards.
James (11:32): So it's a matrix.
Alice (11:33): It's a matrix. If you don't have that, you're measuring yourself against historical peak hours that might have happened under completely different conditions. You need to know, if we run SKU A with three people, the rate is X. If we run SKU B with four people, the rate is Y. Without that, you're flying blind.
James (11:50): So if you're a listener running a plant, you need to stop asking what is the bottleneck and start asking where is the bottleneck right now with this crew?
Alice (11:58): Exactly.
Misconception: non-standardized changeovers
James (11:59): So we've discussed budgeting, we've discussed reliance on history, and we've discussed bottlenecks. The fourth misconception is one that drives operational folks crazy. The art of changeovers.
Alice (12:11): This is the belief that the guys know where the parts go and setups take as long as they take. It treats the changeover as a performance by the operator like an art form rather than an engineered process.
James (12:22): It accepts non repeatability. It assumes that if a certain operator does the setup it takes thirty minutes, but if another one says it takes an hour, and that's just life.
Alice (12:31): Right. If a changeover relies on memory, then you're managing uncertainty, not a process. We worked with a confectionery plant where changeovers were routinely running over 150 minutes.
James (12:43): Two and a half hours. That kills your efficiency.
Alice (12:46): It does. And it wasn't because the operators were lazy, it was because there was no defined ready state.
James (12:50): They were just figuring it out as they went.
Alice (12:52): They were searching for parts, choosing which tool to use, and correcting adjustments in real time. They were effectively reinventing the machine setup every single time.
James (13:02): And we also see the missing prerequisite failure here. This is where planning falls apart.
Alice (13:08): This is critical. You can plan the downtime on the schedule, but if the prerequisites aren't managed, that planned downtime immediately becomes unplanned downtime.
James (13:17): Sure.
Alice (13:17): We see lines sitting idle because a spare part is missing, or a vendor wasn't scheduled, or a special tool is locked in a cabinet nobody has the key to.
James (13:26): The mechanical work was planned, but the readiness was not. So how do we fix this? How do we move from art to science?
Alice (13:34): Changeovers have to be treated as an engineered system. First, you need concrete, ready to run definitions. Second, you need poka yoke.
James (13:43): Poka yoke.
Alice (13:44): It's a Japanese term for mistake proofing. Think of a USB plug or a SIM card tray. It only fits one way. In a factory, this means labeling and keying parts so you cannot put the guide rail in the wrong spot.
James (13:58): You're designing the error out of the process.
Alice (13:59): You're removing the guesswork. And finally, we need to manage the prerequisites, parts, tools, vendor windows, just as strictly as we manage the production schedule itself.
James (14:09): So if the tool isn't at the line thirty minutes before the stop, the stop shouldn't happen yet.
Alice (14:13): It shouldn't happen.
The shift to redesign constraints
James (14:14): So what does this all mean for the leaders listening today? We've walked through these four misconceptions. The budget trap, the veteran ceiling, the static bottleneck, and the art of changeovers.
Alice (14:25): If we synthesize these insights, the goal is not just to reduce maintenance costs or speed up a single line. The goal is to restore economic and operational control.
James (14:34): It feels like a shift from defense to offense.
Alice (14:36): That's a great way to put it. Most plants are stuck in a mode of managing around constraints. They're coping. They're patching the belt. They're relying on the veteran to bypass the issue. They're accepting the bottleneck.
James (14:53): Moving from coping mechanisms to actual engineering solutions.
Alice (14:57): Precisely. Whether it's using data to justify a rebuild instead of a patch, bringing external expertise to leapfrog an old process, or defining your changeovers as a system, it's all about taking back control of the asset's economics.
James (15:12): And that economic control is what allows a food manufacturer to compete, regardless of whether they have the newest factory on the block or a legacy site.
Alice (15:21): The legacy sites can be incredibly profitable and efficient, but only if they shed these misconceptions. If you treat the old machine as an excuse, you lose. If you treat it as an asset to be engineered and optimized, you win.
James (15:33): That's a powerful place to leave it. It's about mindset as much as it is about machinery.
Alice (15:37): It always is.
James (15:38): Thank you for listening to Value Gene Insight Conversations. To deep dive, please see the show notes. For more on food industry topics, visit varyugeneconsulting.com or subscribe wherever you get your podcasts. If today's discussion resonated with you, please do not hesitate to reach out to us to continue this dialogue. Have a great day.