Coke’s new take on voice technology
An order selector begins by logging on to a VoIP phone. The order selector is then directed by the phone to a picking location. After orders are picked, the selector prints out labels at a kiosk.
In 2007, CCR began to investigate different technologies that would improve accuracy without sacrificing efficiency. “We targeted the largest 100 facilities,” says Jacks. “Since there are a wide variety of facilities in terms of age, sophistication and layout, we needed a solution that was flexible enough to adapt to all of those different scenarios.” After investigating voice, pick-to-light, RFID and bar code scanning, they agreed they wanted a solution that allowed for heads-up, hands-free operation by the order selectors. Voice made the most sense. “Bar code scanning delivered the accuracy we wanted, but it wasn’t hands free,” says Jacks. “RFID wasn’t economical, and most of our facilities weren’t set up to accommodate pick-to-light.”
Voice, on the other hand, allowed order selectors to work hands free. What’s more, says Gross, with the ubiquity of cell phones “voice is a natural form of communication today. People are used to talking on their cell phones and using headsets.”
CCR’s initial investigation of voice led it to the leading providers of traditional voice solutions for the warehouse as well as tours of a number of food warehouses using traditional voice solutions. Jacks and Gross initially assumed that’s the direction they would take. At the same time, CCR had made a corporate commitment to a VoIP infrastructure for its business.
Once the voice team began talking to SAP, Cisco and Avaya, CCR’s strategic partners for its voice infrastructure, they decided to create their own solution. “We found there were a lot of similarities in the way that voice providers deployed their solution,” says Jacks. “We have a sophisticated IT staff and felt we could leverage our infrastructure and come up with something ourselves.”
In the spring of 2007, the group was in the process of evaluating vendors for the different components they would need when several members attended SAP’s annual user conference in Orlando. During a meeting with SAP, they learned about Datria’s VoIP voice solution. That was followed by a trip to Denver and a challenge to the voice provider to develop a server-based solution that would integrate with SAP, deliver instructions to workers within CCR’s workflow structure, use off-the-shelf hardware and leverage CCR’s existing VoIP infrastructure. Six weeks later, Datria came up with an application.
Going live with voice
The primary difference between CCR’s solution and a traditional voice solution is in where the voice application resides (for a more detailed explanation, see p. 22). In a traditional voice application, an instance of the software resides on every operator’s mobile computer, which is typically worn on a belt. In a VoIP solution, one instance of the software is loaded onto a central server. Instead of a mobile computer, a mobile worker dials into the solution with a VoIP handset—in essence, an industrialized cell phone.
Where many voice solutions use proprietary mobile computing devices and headsets, a VoIP solution works with off-the-shelf handsets. These are considerably less expensive than traditional voice hardware. There is, however, a tradeoff. A company may need to build out a WiFi infrastructure to accommodate the VoIP solution. Indeed, CCR realized it would have to provide additional access points in each facility to work with the new system. However, since CCR had already committed to VoIP on a corporate-wide basis, most of the infrastructure was already in place and paid for. In this instance, the distribution operations could leverage an investment the corporation had already made.
Remember those big numbers we talked about in the introduction? Despite the quick turnaround by Datria, CCR wanted to prove the solution before committing to an approach that had not been done on this scale in the past.
The bottler launched two 60-day pilots to pit VoIP against traditional voice: a pilot in Jacksonville, Fla., got underway on June 15, 2007, while a competing pilot began on July 15 in Ft. Worth, Texas. In August, halfway through the second pilot, CCR had enough data to commit to VoIP.
Over the next month, CCR identified 23 sites for the initial roll out in addition to Ft. Worth and Jacksonville and organized four deployment teams. The actual deployments got underway in September and by the end of December, 25 sites were up and running.
By the end of 2008, the voice system was up and running in an additional 75 facilities, bringing the total to 100.
As with any early adopter of a technology, there have been lessons learned.
One is that the system is very much speech independent. In a traditional voice implementation, a process known as speech dependent, each user records a sample of his voice. In a speech independent implementation, those voice samples are unnecessary.
Yet, CCR says that its system will pick up just about anyone’s voice. “We had a person on our team who spoke English with a heavy French accent,” says Jacks. “I dialed in, did some pallet picks and then handed the phone to that person. He was able to pick up where I left off.” Not having to record speech samples for 3,000 separate employees sped up the implementation process.
At the same time, some experimentation was involved in getting a phone suitable for an industrial setting. For instance, CCR initially was getting just four to five hours out of a battery; through some adjustments, the team figured out workarounds to get 12 hours between charges. By then, Jacks says, Cisco came out with an extended life battery that is good for 16 hours.
Initially, CCR had to have individual battery chargers for each phone that was going to be charged. Since then, Cisco has developed a six-port charger that will hold two batteries per port, or 12 batteries at a time.
Likewise, the initial off-the-shelf phones were designed for call centers and not a rugged industrial setting. CCR workers regularly wore out the jacks on the phone. Today, after working with Cisco engineers, CCR is using a Bluetooth-enabled, ruggedized phone with a battery-powered Bluetooth headset that is doing the job.
As to the $2 million in hardware savings, Jacks and Gross agree that the installation required more access points to get the density of coverage required than would be required in a typical RF warehouse using bar code scanning. Those additional costs, however, were more than offset by the savings on hardware. That’s where the scale of the CCR implementation comes in to play. “To enable 3,000 workers across multiple shifts, we purchased 3,000 handheld devices,” says Gross. “The savings across that many units was substantial.”
Now that picking operations have been enabled, CCR is developing a strategic roadmap for extending voice to other processes in its distribution and logistics operations. Route delivery is a possibility. Field service is another. There are other transactions in the SAP warehouse management system that might also be enabled by voice. “Because we have this architecture in place, if we have a solution that is going to drive a significant ROI, we can make a recommendation and accelerate the adoption,” says Gross.
And while VoIP may not be right for everyone, it has delivered for CCR. “All of the benefits we anticipated, from a savings on the hardware to improved accuracy and efficiency, we’re realizing,” says Jacks.
How VoIP works at Coca-Cola
The system uses wide area and local area networks to direct operations on the floor of warehouses across the enterprise.
VoIP or traditional voice: Which solution is better?
Which voice technology solution is right for your facility?