Preventing Data Lag
Keep your SLAM line running smoothly.
Automating the final 100 feet of your warehouse—the scan, label, apply and manifest (SLAM) tasks—is one of the best improvements you can make to ensure efficient shipping. Despite all the gains you can make with SLAM, you still need to be on guard for potential hiccups, including the potential for data lags. This is especially true during peak season or during any outages you might experience. But having an awareness of the potential, and a plan for mitigating the issue, can be a big assist.
When everything is running smoothly and as is, your SLAM line can operate quickly and efficiently. Sometimes, the SLAM line can acquire the data it needs from a scan, print a label and then apply it in a matter of seconds. When there’s a lag in the data acquisition and response, however, that slows the entire line and that’s where trouble begins. Fully in motion systems with no room for forgiveness are most prone to these issues.
For instance, if your OEM or integrator has set up control software and it knows packages will come down the line every two seconds, when that backs up, the WCS will alert users of the problem. Users and their automation partner can log into the dashboard and see the response time on every package. If it’s longer than the two seconds, your automation partner can build in a buffer to the rules.
There are effective rules and ineffective rules, however. Often, if the rules aren’t holding and taking too long, then the SLAM line will add a label that might read “server timed out,” and send that package to the “hospital” or “error” lane. Or if there’s a second rule that orders a shutdown of the SLAM line when packages break the time rules, you’ll end up with additional packages in that hospital area. This is an untenable situation, and you’ll need to avoid it with other approaches.
One workable solution is to set up a longer conveyor if you need more time and space between packages. For instance, if it takes two seconds or longer to make a label, when you make the conveyor longer, no one will notice the latency between packages. You are now able to capture the data farther upstream, set up the labeler farther downstream, and fix your problem. This is idea when you are operating a high-speed system with an in-motion scale and a high volume of packages.
Another option is to use a zoned accumulation conveyor. Each package remains in its own zone and snakes its way through the line. When the package arrives at the labeler, it briefly pauses—for just a few seconds—to allow for labeling/data capture. Because each zone will run independent of the others, this also prevents any backups in the SLAM line.
Through trial and error with your software and OEM, you can determine the right pace for your SLAM line to prevent any data lags or downtime.
To learn more about MHI’s SLAM industry group: www.mhi.org/slam
More information about Scanning, Labeling, Applying, Manifesting:
SLAM Solutions in the Pharmaceutical Industry
Order Personalization with SLAM
How SLAM Can Help with Returns
How SLAM Helps Get the Order Right
Using Peak Season for Next Season
Podcast: Elevating Order Fulfillment: VRCs & SLAM Efficiency in the Modern Warehouse
