Integrating New Automation- Part 1

Getting new equipment can be a game changer, but it can also be disruptive.
Automation is on everyone’s minds as companies look to boost efficiencies and operate with less labor. A big concern with any automation project, however, is how to integrate without disrupting day-to-day operations. The answer to that dilemma varies by company, and also by current levels of automation.
If you’re a smaller company and just getting started with automation, one of the first things to consider is where your pain points are, and what potential solutions can help. This amounts to a series of small, incremental steps, rather than the implementation of a widespread, fully automated facility. Or, if the end goal is to fully automate in five years, how do you start and then build upon that entry point?
Once you identify your pain points and how you’d like to go about adding automation to the equation, you need to define a path to getting there. This is true whether you’re going small, large, or somewhere in the middle with automation. Working with your OEM or integrator, you’ll want to schedule a site visit to walk through your operations, mapping things out from receiving on through shipping to follow the product or widget from inbound to outbound.
The goal with this activity is to make sure you are not just solving one problem and creating another. You don’t want to get into a cycle of throwing solutions at your issues and hoping one sticks. As you get a solution in place, you’ll want to determine how it is affecting other areas of your business.
Then, you can begin addressing how to keep things operational while implementing your new automation. Say you are going to work on your SLAM line—the final 100 feet of operations. You’ll need to clear the area for the physical implementation and figure out what your interim operations plan will be. It can be helpful to draw out a schematic of your floor so that you can envision what a temporary fix would look like for the intended period of implementation. Make sure to insert details on how much space you need (and for how long), how much labor, and any other details so that you’re mapping out the best alternative, temporary solution as well as a contingency plan should things not go accordingly.
Work closely with all your customers who might be impacted to allow them to prepare for any slowdowns or disruptions to their orders—ideally, that impact will be minimal.
Your initial planning period leading up to the actual integration of new automation will vary—it could involve anywhere from a couple of months to an entire year. But that’s time well spent on the front end to avoid or minimize disruptions for the go-live moment.
You should assemble the right team to integrate new automation, as well. Your integration partner will identify a main point of contact, and you should, too. This will keep everyone on the same page and with good communication flows.
New automation can be impactful in both good and bad ways—preparation is the key to ensuring success.
For more information about the Solutions Community: mhi.org/solutionscommunity
For further articles from the Solutions Community:
Implementing a Warehouse Control System (WCS)
Is it the Right Time to Automate Your DC?
Condition Monitoring is Expanding
Warehouse Execution Software Implementation
Mitigating Damage from Many Directions
Are You Data Rich, Intelligence Poor?
For a Successful Software Implementation, Focus on the People