The Equipment Didn't Fail. The Process Outgrew It.
- John Stikes
- 3 days ago
- 6 min read

You can walk into a plant and see an older machine still doing exactly what it was built to do.
The motors turn. The conveyor runs. It cycles the same way it always has.
What changed is everything around it.
The product mix changed. Volumes changed. Somebody moved a workstation. Packaging changed. A manual step got added. The layout got tighter. The people learned how to work around the system instead of with it.
Then the machine gets blamed.
Sometimes that is fair. Sometimes it is not.
A lot of the time, the equipment did not fail. The process outgrew it.
That matters, because once people decide the machine is the problem, the next move is usually to price a replacement. Big capital. Long lead times. Downtime. Then you risk buying another rigid system that fits today's process and struggles with the next one.
Sometimes replacement is the right call. It just should not be the first one.
The first question is simpler:
What still works?
The Process Changes Before the Equipment Does
Most automation gets built around a certain way of working.
At the time, it makes sense. The products are consistent. The workstations are where they need to be. Volumes are manageable. The team knows the system.
Then the business changes.
A new product line gets added. More orders start coming through the same area. A department gets moved. Somebody adds an inspection step. Now the company is handling more variation than the original system was built for.
That does not automatically mean the equipment is bad.
It means the conditions changed.
That is where things start to drift. The machine is still doing its job, but that job may not fit the workflow anymore. Now it feeds the wrong area. Or it moves material too slowly for what comes next. Or it creates extra handoffs. Or it becomes the bottleneck.
The equipment is still running.
The operation just is not getting the same value from it anymore.
The Workarounds Tell the Real Story
You learn a lot by watching what people do when the system no longer fits the job.
Material gets staged in the aisle. A station gets bypassed. Somebody grabs a cart to move what the system was supposed to move. A spreadsheet shows up because the screen does not tell them what they need to know. The same one person gets called every time something goes sideways.
None of that is random.
That is the operation telling you where the process outgrew the original design.
When I walk a facility, I want to see the official process, but I really want to see the unofficial one. The worn path on the floor usually tells the truth faster than the process map. The walking the building on the overnight shift helps see the real process.
Where are people walking? Where are pallets sitting? What parts of the building are really dirty or dusty? What areas are constantly changing? Where does material get handled twice? What station is always backed up? What happens when the system hits an exception?
That is where the real conversation starts.

Start With an Honest Equipment Check
Before you decide to replace anything, break the problem apart.
The mechanical side may still be solid. The controls may be outdated. The sensors may not be giving you enough information. The software may not talk to the rest of the operation. The layout itself may be the real issue.
Those are not the same problem, so they should not all get the same answer.
Look at the machine. Look at the moving parts. Look at the controls. Look at where flow slows down. Look at what the current setup is costing you in labor, overtime, damage, or delay. Ask whether the system can handle today's product sizes and weights. Ask whether it can be moved, reworked, or tied into something else. Ask whether a small add-on would clear the bottleneck.
That is the point of the review.
Not to make old equipment look new. Just to figure out what still has value and what does not.
An installed-base evaluation can help separate a controls problem from a mechanical problem, and a process problem from both. Automation World makes the same point in its overview of retrofit and upgrade decisions: the right path depends on the condition of the equipment, the cost of downtime, the budget, and the functionality that is actually needed.
There is no prize for replacing a good machine.
The Bottleneck May Be Beside the Machine
A lot of people look straight at the machine and stop there.
But plenty of times, the machine is not the real problem.
A conveyor can be running at the right speed, and operators still cannot get material to it fast enough. An automated storage system can retrieve inventory just fine, but the next station cannot keep up. A packaging machine can be doing its job while the real mess is the manual movement before it or after it. A robot can be reliable, but the product mix changed and now it needs different tooling, new instructions, or a better handoff.
That is why this kind of review has to start with workflow, not a parts catalog.
The goal is not to freshen up every old panel in the building. The goal is to remove waste. Extra walking. Extra searching. Waiting. Double handling. Unplanned staging. Paper checks. Overtime. Downtime. Dependence on one person's memory.
If an existing machine is helping create those problems, a small mobile robot, a better sensor package, a controls update, or a cleaner interface may do more for the operation than tearing the whole thing out.
Reconfigure Before You Rebuild
Sometimes the best retrofit is not a new robot or a new control system.
Sometimes you just need to change the setup.
Move a workstation. Relocate a pickup point. Change a route. Rework a storage area.
Pull a manual step out of a sequence that no longer makes sense.
That sounds basic because it is basic.
That is also why it works.
Automation does not need to be a grand transformation to be useful. It needs to fit the work.
This is where flexible equipment helps. An AMR can take over a material run without locking you into a permanent conveyor path. A collaborative robot can support a station without rebuilding the whole line. A modern sensor can give you information the old system never had. A software connection can help two separate pieces of equipment work together.

These are additions. Not a declaration that the whole operation has to start over.
At Approach Automation, that is how we think about it. People first. Processes second. Equipment and technology third. Which gives us automation deployed like equipment, not projects.
Solve one real problem at a time. Put something useful on the floor in weeks when you can. Do not wait through a multi-year transformation just to find out the plan did not match reality.
The People Who Know the Old System Matter
When the one person who really understood the old system is gone, the machine can suddenly look a lot worse than it did before.
Maybe that person knew how to clear a fault, adjust a setting, work around a product variation, or restart the machine after a certain error. A lot of that stuff never gets written down.
Then everybody says the system is unreliable.
Sometimes it is. Sometimes the knowledge just walked out the door.
A retrofit is a good time to fix that. Clearer screens. Better alarms. Better documentation. Easier access to data. Simpler recovery steps.
The point is not to make people more dependent on the automation team. It is the opposite.
Good automation should be understandable enough to use and maintain.
If the only person who can keep it running is gone, the system was never as flexible as people thought.
When Replacement Really Is the Right Answer
Sometimes the old equipment really is done.
If the mechanical structure is worn out, the safety systems cannot be updated in a reasonable way, spare parts are impossible to get, or the process changed so much that the machine no longer has a useful job, then replacement may be the right move.
The important part is making that call off facts.
Do not replace a system just because it is old.
Do not keep it just because replacing it sounds expensive.
Look at the condition of the equipment. Look at the workflow you have now. Look at the recurring costs. Look at the downtime risk. Then compare the real options.
A targeted retrofit may be enough. A supplemental system may be better. A full replacement may be necessary.
That answer should come from the operation, not from somebody's default sales pitch.
Make the Existing Equipment Useful Again
The best automation decision is not always the newest machine.
It is the one that removes the most waste with the least disruption.
Before you tear out an old system, look hard at what it can still do. Figure out what part still matters. Figure out where the process moved around it. Then decide whether the gap gets closed with a reconfiguration, a controls update, a new connection, or a small piece of flexible equipment.
That is practical automation.
We clean stuff. We move stuff. We store stuff. We track stuff.
The tools can change. The idea stays the same. Solve the recurring problem in front of you.
Sometimes the smartest automation investment is not starting over.
Sometimes it is helping the equipment you already own catch up with the business you have now.




Comments