Revving Up Efficiency in the Warehouse
March 01, 2018
Rob DeStefano | Product Marketing Manager | Ivanti
Aaron Bolton | VP | Procensis
Monty Burrell | Director of Operations | Dorman Products
Ed Kennedy | President | Procensis
Opportunities for supply chain productivity come from various sources. We’ll explore how voice, a mix of mobile device types and operating systems are elevating performance across Dorman Products workforce. Spend 40 minutes with us as we walk through the use cases, performance objectives, and solutions that are helping raise productivity for this leading automotive aftermarket parts supplier.
Explore different use cases within Dorman Products, and the various Ivanti solutions included within, including:
- Speakeasy for voice-enabled apps
- Velocity to ease the migration to new Android devices
- Managing these diverse mobile deployments with Avalanche
Rob: Let's get started. Hello, everybody. Welcome to today's webinar, Revving up Efficiency in the Warehouse. I'm Rob DeStefano, Product Marketing Manager for Ivanti's supply chain mobility business. We have a great webinar today, very excited to share with you a customer success discussion. So, let's dive right in and get started. We've got a couple of just upfront housekeeping items. First of all, certainly during this conversation, you'll probably have some questions so, by all means, up in the upper right-hand corner of the console you'll fine the Q&A icon. Just click on that.
And at any time during the webinar, please type in your questions and we'll answer a few at the end, and if we don't answer yours don't worry, we will follow-up with you separately after the webinar. If you'd like to follow us, in general, what activities we have going on across Ivanti you can follow us on Twitter, see our Twitter handles up there both for everything Ivanti @GoIvanti. And @IvantiWavelink is our supply chain mobility focused Twitter handle. And if you're out and about around the world our next event that we will be attending is SITL in Paris in March. So, if you're going to be on the European side of the Atlantic, please look us up over there.
And we always do a number of webinars for our users, our momentum webinar series is a great place for folks to get tips and tricks on the products that they're already using and learn a little bit more of the solutions that are available to them from Ivanti. So, stand by and watch for emails for those, and you can also find out more about our momentum series on our website. So, I have the great opportunity to be remote today out in the field with our partner Procensis and our special guest customer Dorman Products. So, today with us here on the webinar are Monty Burrell and Greg Bowen form Dorman Products. Welcome, gentlemen.
Greg: Thank you.
Rob: And also Ed Kennedy and Aaron Bolton from Procensis. Great to have this opportunity to be together.
Rob: All right, with that said, let's get started. Let's get into what the folks on the webinar are interested in hearing about.
Monty: Good morning. My name is Monty Burrell, I'm Director of Operations with Dorman Products. Dorman Products packages and distributes hard-to-find automotive parts and fasteners to retailers, warehouse distributors, and DIYers. We currently have five warehouses in the domestic U.S. Currently, I oversee Pennsylvania and the North Carolina facilities. We also have facilities in Tennessee and Kentucky, Kentucky being our largest facility. It's well over 750,000 square feet. In PA we operate out of 230,000 square feet.
Rob: Great, awesome. Now, as you were looking at new technology, right, tell us a little bit about what were some of the improvements that you were looking? What kind of challenges were you looking to address and solve?
Monty: So, about a year and a half ago our senior VP of operations challenged his team. He wanted to ensure that we were trying to take human error in non-value added steps out of our processes. So, we had a vision what we were coining as radar picking, and radar picking did just that. It was eliminating a lot of non-value added steps and it was ensuring that the system was driving our accuracy and not the human.
So, basically, what we wanted to achieve was pick a contributor, have a signal to drive them to a location, to pick a quantity, and then move onto the next location. That was basically it, three steps that was our goal. So, I went on an exhaustive search and spoke to I don't know, four or five different companies. And no one could really come up with what I was looking for, but partnering with Procensis they were able to, you know, listen to what I wanted and actually come up with a solution that came pretty much to what I wanted. It's not exactly where we wanna be. We're gonna get there. But right now gen 1 it's working our greatly.
Rob: Awesome, awesome. And from the Procensis side, when you had the opportunity to walk through, can you tell us a little bit about, you know, some of the areas that you saw and identified as, "Hey, this is where we see some opportunities to help you improve."?
Aaron: Sure, so when we meet with the client one of the things that we like to do is a full assessment. Now, we were fortunate in 2016 we partnered with Dorman Products and we implemented a new wireless LAN. So, they had the robustness of a great network in place. And so when I met with Monty and the team in January of last year we took more of a holistic approach not just simply, you know, how we can improve the picking process, but what we both recognize is that the current AIDC equipment was at its end of its lifecycle no longer to be able to buy. The support on some of the equipment was getting rather more difficult. And additionally, you know, with the announcement about Microsoft ending the support for Windows operating systems, we knew that we had to present a solution to Dorman that touched all those areas.
Rob: Awesome. Very cool. So, let's dive into the first of those solutions here. There's a voice element, a voice use case for your workers. Can you tell us a little bit about...you're no stranger to voice, you've already had voice in your facilities. Can you talk about what voice was doing and what you were looking forward to do when you started this current project?
Monty: So, let me just touch on where we were prior to voice. We were strictly using RF handhelds. There was a lot of waste obviously using the RF handhelds. So, ultimately, we decided to move the voice to eliminate that waste. And we did, we went live with a voice picking system back in February of 2016. It took us about three and a half to four months to really hit our stride with voice.
We did become more productive with voice actually pretty significantly more productive with voice. But we really weren't getting the accuracy gain that we expected. We improved just slightly with voice, but again, you know, not where we needed to be from an accuracy perspective. So, that's why we wanted to move from another solution to address the problems I originally talked about.
Rob: Okay, cool. Now, as you moved to your new voice implementation, obviously, you're using Ivanti's Speakeasy which is, well, the use case we're showing here actually on the screen right now. Hardware, looks like that's a Zebra TC8000 trace solution.
Monty: Zebra TC8000, correct.
Rob: Okay, so can you talk a little bit about the whole setup to it?
Aaron: So, when we met with Monty he shared his vision of the radar picking. And we realized that the only way we were gonna get there is we were gonna have to...to get that accuracy is we would have to scan every UPC barcode. But the challenge was we couldn't slow them down because they already recognized an efficiency gain from voice. So, Procensis evaluated the technology that was on the marketplace and we came to Dorman and presented them a solution made by Zebra. And the TC8000 encompasses a few things.
Number one, it's the device itself and the second if you see in the picture there it's mounted in the cradle, and while it's mounted in the cradle it activates what's called their proximity reader, and subsecond it turns on the scanner. So, basically, we think about like the grocery scanner when you wave something in front of it, it activates it. So, we had to stay hands-free, okay?
And so we felt this is the best solution to meet what Dorman was looking for, an increase in accuracy and at the same time keep the efficiency there. And then lastly, the TC8000 also brought another element that was new to them and something they had maybe in RF but they didn't have in their existing voice system, and that was visual. And so with the TC8000, we refer to as a multi-modal solution, and so by incorporating voice and kind of like the best of RF we're able to deliver this type of solution.
Monty: And that was pretty huge the whole visual piece because when we were picking voice if there was any delays with our legacy system the contributors will get confused and they're just waiting and waiting so there was downtime and then going back to the order control desk which is where our leadership was to ask them what was going on with the system. Now, with the visual, they can control their own destiny, understand what the problem is, and not have that downtime of going back to find the leader.
Aaron: And for things like error messages and things that don't come up every day. Sometimes it's difficult the first time you're hearing it to understand what's going on there. But with this, they say, "Oh, wait, let me just take a quick look at the screen." They take a walk over to the screen and immediately know what's going on if it's something they didn't understand in the voice piece.
Rob: Very cool, very cool. And the back-end system you're connecting all this back to your WMS?
Rob: ASP-based system?
Rob: How did that implementation experience go?
Aaron: Implementing the voice picking system and using Velocity actually worked out really well because one is that they're using SAP Console which has the advantage of being very lightweight and very quick and with the ability to use the Velocity scripting tools we were able to basically take what they wanted from the screens of their existing system and present it in the unified way for the end user.
So, one of the things that was great about that was that one, we initially did like for like, meaning field for field, label for label, button for button, but then we were able to as the users got a chance to actually work with that and test that we were able to, you know, reduce some of the screen items, make some changes and modifications to colors and to buttons and so forth that allowed us to basically provide a leaner and more efficient presentation to the end user that didn't change a thing on the back-end.
So, there's no changes required back-end to make any of these improvements and to do this implementation. And it was pretty quick because I mean we were able to work with Greg to get screens that we needed. It literally took like a day and as new things came up we're able to grab those pretty quickly and make changes and be able to deploy them back down into the device.
Ed: Yeah, we were up and running very fast as compared to a previous solution it was three months in development before we could even see anything. Well, not see because there's voice, but be able to even pilot that solution.
Rob: That's interesting because that was my question is you had a previous voice system, a legacy voice application. You moved over to...not only moved to Android you introduced the Velocity framework and then add voice on top of that. You only implemented that legacy voice application in early 2016 and by late 2017 you're already moving over to Speakeasy and seeing, you know, improvements because you mentioned the accuracy piece before, right? From the user's perspective you introduced a voice application initially two years ago, now you're bringing them something new. How do the users receive the Speakeasy-based voice application? Is voice-enabled Speakeasy easier for them to learn? What did you find?
Monty: I'll touch on it briefly and Greg can go into details but when we first deployed voice picking back in 2016 most of the contributors or employees, excuse me, did not wanna use it. They wanted to go back to traditional RF picking which blows my mind but they hated it. With the Speakeasy solution everyone loved it, so Greg if you can just elaborate on that.
Greg: Yeah, our previous solution it took weeks of developing procedures, making cheat sheets, and then after we had all of that then we had to go into training them. And it was several hours in training for each user. So, we'd have to go through, have them train a template. It was difficult. If they didn't say the word right in the template training they had to go back and retrain it. If they had a cold, if anything was slightly different it required us to go back and redo training. It was miserable in the first month or so of getting users acquainted with the new system versus with the Speakeasy solution 15 minutes of a quick overview if they have any questions, "What can I say here?" They just look at the screen. Everything on the screen they could say it so they have that quick reference. Training was phenomenally easy with the new system.
Aaron: You know, one of the things as Monty mentioned earlier is the senior leadership team was looking to eliminate, you know, that human element to improve that accuracy. So, they do batch picking or group picking and so when they're directed to a bin location and they're told to pick 20, in the previous system they would have to count out 20 items, okay? And so yes, we're scanning but also what we're doing on the TC8000 is we're decrementing. So, we have the ability to control anything on that screen and then we can make things in various different colors and we can make larger.
So, we made the decrementing in a large number. So, it started out 20 and as they scanned an item it decrements, and once it gets down to the last it automatically goes to the next location to do a pick. So, the users like that because if you think about it, the contributors are incented to hit certain levels of accuracy or efficiency and then they have an opportunity to even make more. And so now they know they can trust in this system, right, because it's accurate in accounting for them.
Monty: Yeah, and just, you know, three weeks we reduced our incorrect item pick by 86%, 86%.
Rob: That's awesome. That's awesome.
Monty: And they're still, you know, getting used to the system.
Rob: That's great. Wow, that's really impressive.
Monty: So, ultimately, you know, we're running around 99.8% shipping picking accuracy. The goal by the end of April is to be at 99.95%. And I'm confident we're gonna get there. The last two days we didn't have any errors which is a first. We always have one or two errors. We didn't have any errors at all the last two days.
Rob: Excellent. Excellent. That's great news.
Greg: I think Monty can also touch as far as the indirect labor benefit from the solution as well.
Monty: Yeah, so currently we have four auditors which is obviously non-value added. The goal is to get down to one auditor by the end of the year and by 2019 not have any auditors because the bottom line is when you're picking you're auditing.
Rob: You're doing your own...
Monty: So, we're eliminating all that indirect labor, now I can take those non-value added tasks and move it into direct labor.
Rob: Yeah, that's awesome. We hear that a lot with our Speakeasy product as the self-driven QA [SP] because the way the operation workflow can go. That's great, but that's an amazing statistic.
Monty: And one of the other things that we looked at was we looked at one of our top four customers and, you know, we looked at a December snapshot of how we were performing with them versus just last week. And we improved by 14% to 15% with that one customer in picking.
Greg: And that's on top of the improvement need from the previous voice so I mean it's...
Greg: I mean you could potentially be in the 20% plus range going from traditional RF right to the TC8000 [SP] with the Speakeasy solution.
Rob: That's great.
Monty: And the moral it contributes to, right? Because they don't have to worry about, "Am I gonna get called back to the audit desk? Did I make an error today?" You know, they have that fear in the back of their mind constantly, and people get terminated obviously for poor performance.
Rob: So, it's a for them?
Monty: Yeah, so they're excited. They're like, "Wow, this is great. I don't have to worry about going back sitting in front of my leader talking about my accuracy."
Rob: That's great. That's very cool. Very cool. Great metrics. You ticked my next question off which is perfect, which is perfect. So, let's shift gears if we can. We talked about obviously, you voice-enabled use case in an Android-based system. There's another use case for vehicle mounts. Can we talk a little bit about your experience with5 Android mobility, in particular, that use case now?
Aaron: So, when I visited Dorman back in January 2017 they were using what most people use, we refer to as the traditional vehicle mount computer meaning it's powered by the forklift, it's permanently mounted, it presents a keyboard that's what you see is what you get, and it does a single task, okay? So, it's strictly doing just the WMS transactions, okay? And so from Procensis perspective, that when we introduce a new solution we don't like to just offer what we refer to as life for life, what we're trying to do is how can we provide our clients a new solution that can give them much more than what they currently have today, and secondly, how can we make it even work better than what they have?
Greg: Right, and a lot of the ways that you guys did that was with... I mean, going from the RF term that's in black in white that you have to use the function keys to navigate through your processes you guys were able to take out whatever fields you don't use to expand the fields that we do use, make them bold, make them stand out in different colors. Some of that has even been driven from user requests. And so once we go through there you'd think, "Well, you still have your function keys." But they turned all the function keys into buttons, so now they're navigating instead of F3 back they're hitting a button that says "back." So, a new contributor, yeah, a new person using it, it makes sense, it works. I know Monty brought it up before but it works just like your phone. So, it's great.
Rob: For the folks on your phone you can see a little bit of a closeup of an application screen on the screen there, and that's exactly what Greg's referring to is those orange buttons down at the bottom you see being able to replace those function buttons with what the function actually does, right?
Monty: And we talk about waste, right? Waste is everywhere in a warehouse operation. And you know, this is gonna help take away waste where, you know, they can use SAPgui on that unit. They can go to different URL's where, you know, prior to that they would have to run through a desktop somewhere and jump on SAPgui or go through a URL. So, we can have them go into many applications on that one device and they're much more self-sufficient and dependent.
Rob: And that travel time is a big waste, right?
Monty: Exactly. Huge, huge.
Rob: Because there's a lot of lost time in any warehouse, right?
Greg: So, one thing I'd like to point out you see on the screen there, you know, it is an Android product, okay, but we're not leveraging like an Android keyboard where you swipe left, you swipe right. And if you notice on the screen that right now the cursor's sitting at the quantity field. So, we don't need to display alpha letters on there, we only need to display what they need to do and that's numeric, okay? And then we color code whatever they like and how they want it. So, the backspace, the enter key. As you can see, we made the enter key larger. So, we can position the keys where they want them, we can make things larger. We have the ability to make it...if they so desire that particular field is scan only and they do not want someone to type, we can make it scan only.
Rob: That's great. Yeah, and that ties into what Velocity does, we call that MOMS framework, right? That's a lot of the optimization piece, right, being able to have those customize keypads that fit the field as you mentioned, the quantity field, for example, right, be able to provide just the keys that the user's going to need to enter data into that field and make them... Accuracy goes up, right, because there's less risk for typo, right, you're not gonna hit the Q button when you mean to hit the 1 button right on a full Qwerty keypad, right?
But being able then to set the rules that if it's numeric, it's numeric, if I need a yes and no I can make the field that right? Being able to have that expertise to put that implementation in place is a great example there. So, we talked a bit about this framework also with the picking application obviously because you go right through to speech, but here just to make sure to capture it all for the attendees, same WMS system you're connecting to?
Greg: Same WMS system is still SAP Console underneath, nothing changing on the back-end. And what's interesting about the fork truck unit is because it uses so many more different types of functions like bin to bin or putaways it as other transactions that are in SAP so we're able to, you know, even if those transactions on the SAP Console side might look a little bit different from the GUI perspective, from the Velocity perspective, it looks exactly the same to the end user. It doesn't matter what the methods are.
They're still using the same label buttons and using the same type of colors and methods and so forth. Plus, you have the ability to use the scripting that's built into Velocity to do, you know, some custom business logic into the transactions that doesn't normally exist on the back-end, but because they're contributor recommendations or, you know, desire to do something that make them more efficient then you can take that scripting and kind of add some functionality that doesn't again touch the back end. It can be very quick to implement.
And just from a results perspective when I was talking with Monty earlier this week is if they brought on a new hire today and to learn the new voice solution they have those people up and running in 4 to 5 days, and with the previous voice solution it was 8 to 10 days. So, onboarding a new associate is half the time. And why is it half the time? It's because, you know, this MOMS type approach. Every day the user use buttons, and they're used to the technology that's on the phone and navigation through any application on the phone. And so we're kind of mimicking that using the products from Ivanti.
Monty: I mean we're trying to get the best talent, and the best talent is gonna migrate to systems in technology of this nature.
Rob: They wanna use what they know are gonna be able to, right, and as it goes, right, "Hey, give me the best tools to do my job."
Aaron: That's a challenge that Procensis sees every single day, you know, wherever there's distribution centers there's other distribution centers. And then, you know, the people walking and wanna work in those type environments has become fewer and fewer. It's a challenge that we've seen for a long time, and so by incorporating this type of technology that they can embrace from the users perspective they can be successful. I mean that's what it's all about, they wanna be successful there, too.
Rob: Now, just out of curiosity from a user perspective with the phone move over to Android across these use cases, there's a lot of talk about, "Well, sure our millennials really like to go Android." How about our more experienced users? They're embracing it as well, you know, [inaudible 00:25:55] to use the Android operating system that they're already familiar with it too, right?
Monty: Yes, we actually have a very diverse culture and a lot of our non-American born contributors have been able to embrace it very quickly. Again, voice was a little bit of a struggle for most of our users but this was very simple and easy and they embraced it early on.
Greg: Yeah, I mean it's like if you go to another country and somebody's speaking a different language, even if you know it and you're fluent in it you still have that delay of, "I have to translate this in my head." Versus if I'm hearing it and seeing it, it just makes the world of difference to them.
Rob: Gotcha. Gotcha. That's great. Any metrics on the forklift non-use case today that you're able to share?
Monty: No, not at this point. It's too early.
Rob: Early, yeah. Yeah, that's okay. I know we're working on a follow-up case study for this too, so then we look forward to being able to share that with the audience when that becomes available. From the experience across both these use cases and putting these new Android-based devices and applications, monetized applications into their hands, right, for those on the phone who listening and thinking about, you know, making the move to Android and ready to make their migrations say, "Okay, well Dorman's done this so they have experience with it and presents it as a solution provider," has had the opportunity to work with this and very comfortable with it, obviously. What types of recommendations would you give to a member of our audience who is looking at potentially migrating to Android now? Any quick tips that you think they should look at as part of their...and consider?
Ed: Sooner than later. I wish we went this route instead of going our previous voice solution route would've saved us a lot of time and efficiency, you know, the efficiency gains that we're having today.
Rob: That's cool. That's great. What about from the prospective Procensis, your thoughts on?
Aaron: Well, a couple of things. Again, it's not about the whole experience, okay, so even from a post-support perspective. So, for example, if the TC8000 goes out to repair versus their current hardware today they have to go find someone today who goes into the device and puts manually all the settings in. Here, when a device comes back it simply can scan two barcodes and it's up and running, so they don't even have to go find someone, they can come right into the returns area, it's being issued right back to the floor where it goes, and then a supervisor can get that device back out into production.
Rob: Great. Yeah, and that's a good segue into our next segment here. So, you've got TC8000's picking use case, Android tablets from Panasonic, right, in a different use case. Voice with Speakeasy, Velocity-based application, right, Velocity on both sides. Managing both these deployments, right, managing all your mobility right here with Avalanche. Talk about that experience. Talk about the experience with NDM, how has that gone as the?
Aaron: Well, one of the things that Procensis had decided early on, you know, several years ago was the fact that if we were gonna do Android that we would definitely work towards supporting, you know, and having our customers using a mobile device management platform because the difference is in the way that Android does things versus Windows mobile it makes a lot of sense to have, you know, a mobile device management platform and with Avalanche, you know, being a mature product you have the ability to manage devices from some of your old legacy products but also being able to manage the newer and the current Android products.
And being able to work with the methods that you have available for that which is great because it allows you to install applications without having to have any user intervention, you can, you know, update integration files like, for example, when we developed an update, some sort of efficiency or something that we're given by Dorman to improve their workflow, we can send that out to, you know, an organized test group and then be able to deploy it to, you know, a larger subset and then deploy to everybody on the staged and timed out method so that Avalanche gives us that ability to get the updates out to the device as quickly and easily, allows us to organize, you know, the test groups that we need to have to do proper testing before it's distributed to the general population. And what's nice about that is also that you know, you have the ability to do remote controls if you need to see end users that's having a specific problem you can remote control to a device.
If a contributor is having an issue with a TC8000 or something like that where, you know, before you would have to send somebody out onto the floor or even with the legacy devices having a remote control it wasn't utilized as much as it is today. Today, people are a lot more comfortable using something like remote control because of the use or RDP, the use of, you know, all these other types of remote control and remove meeting applications, so it makes it a lot easier to use those types of things as well. It's much quicker. It's much quicker much easier not having touch a device, being able to use staging barcodes to get a device up and running and not have to actually stick a device in a cradle to get something loaded is a great benefit to our customers and to us for being able to manage them.
Ed: To put it into perspective, I think this was a week or two ago Aaron had made a couple of changes for us, sent it over and we put it on the test device, and that was around 9:30. It went through, confirmed that it worked, and at 10:00 break... Well, around 9:45 relayed that everything was working well. So, at 10:00 break he said, "I'll push out the new version to all the users." So, they have break at 10:00 and by the time they came back at 10:10 every device was updated with the new version and Aaron was able to do that remotely.
Aaron: I mean it just minimizes the downtime that you have for users. You could take advantage of scheduling that you have in Avalanche to do updates and basically make sure that time isn't wasted. So, if they're at break and they're not using their devices anyway, what a great window of opportunity to make a change and see an immediate improvement.
Rob: Great, great. Okay, we're gonna go onto the wrap up here. I wanna thank everybody for spending time with us here. So, for everybody on the call everything you hear in here we're excited to be able to share out with you as a follow-up there'll be a case study we'll be able to share with everybody here around Dorman's success working with Procensis and the Ivanti product portfolio to get these systems up and rock and rolling.
With that, I'd like to move us into the Q&A stage of this webinar. So, if you have questions, by all means, please type them into the Q&A icon at the upper right-hand side of the console. And while we're waiting for some of those questions to come on in, I'm a New Yorker surrounded by Philadelphia area folks, and if our folks seeto indulge me for a minute with an American sports question for four folks in the Philly area you just said you celebrated a victory in the Super Bowl which for fun, which of your teams is next?
Male: I think the 76ers.
Male: [crosstalk 00:34:09].
Male: I was kinda hoping the Flyers.
Rob: They get Lebron James. Yeah, they got three billboards up in Cleveland so that will be fantastic.
Male: The 76ers are playing in Cleveland tonight.
Rob: Are they really? All right, well we've got a couple of good questions coming in. And again, we'll answer a couple here and then if we don't get to yours, fear not, we will definitely follow-up with you after the webinar as well. So, first question I think is just a good clarification question. Question came in, "Key difference between Avalanche and Velocity?"
For those who are not familiar I'll just kind of give a quick explanation of the two products and then, by all means, we'll get into more of the details but Avalanche is a mobile device management solution that's been part of our portfolio since the early '90s, right, so 25 plus years of enterprise mobile device management. Velocity is our framework for moving applications to the Android platform, right? So, those applications are telephone-based or if they're browser-based. But that's the difference between the products at their core. Aaron, what would you like to add further in how it's used?
Aaron: Well, basically, it's one of the things also that with Avalanche being your mobile device management platform and Velocity being the application platform it also gives you the ability to scripting and those types of things that you know, normal traditional terminal emulation applications or even just an industrial browser can't really do. So, the Velocity framework is much more than just an application presentation platform, it's a kind of robust customization platform as well.
Rob: Cool. Another question we've got here is for the folks here at Dorman. "How do you confirm that you're putting products into the right order in the batch?" Into your workflow.
Greg: So, each order has...some people call them different things. We call them a handling unit, some people call them a license plate. So, as they're picking the order there's a trigger that comes up on the screen and also they're able to get it just via asking for it if they're picking a grouped order, if they're picking several orders at once that it would give them which handling unit to put which product into.
Rob: Cool. Another question here, and I think you gave some detail on this before, Monty, but if you wouldn't mind, "Did your productivity remain the same when you switched to Speakeasy?" I think you said it went up but I...
Monty: It went up with a particular customer but when we first piloted productivity stayed exactly the same. When we rolled it out obviously there's a learning curve so we slipped back a little bit but we're starting to come back and we're actually again with that one customer we're 14% to 15% better than where we were. There are some customers currently all because of our system we're having some SAP issues that have slowed us down. Once we get those corrected this weekend we expect to be much more productive with all of our customers that were picking.
Rob: Great, great. Yeah, I think you mentioned before too that one of the big motivators here was the accuracy piece, right?
Monty: That was the biggest.
Rob: Right. That's huge, that's huge. Another question here, "Is there a server between the host and the mobile device?"
Aaron: I'll take that question. The great thing about the Velocity product is that there is no server involved. All the screen translations and all the work is actually done on the device itself, and what's great about that is that a lot of these new Android handheld devices you get coming out today have great processes. They're very fast, they've got lots of memory, and being able to do the voice translation and being able to do the scripting and all the other things that the rendering and so forth on the device itself takes advantage of that devices horsepower. I mean if you're gonna move to Android why not take advantage of the power? And simplicity because now you have one less point of failure so if there's a problem it's usually just with that one specific device. No server involved and that is a great plus.
Rob: And that's true not a Velocity-based application but even for the voice piece for Speakeasy.
Aaron: Absolutely, it's all done on the device. It's pretty quick.
Rob: Yeah, and it's great, right, because, you know, probably now the last 8, 10 years, right, there's been enough horsepower in the devices even going back to the Windows mobile device being able to have voice processing on the device, but now as you go to Android, right, being able take full use, full advantage of all that power for application side of Velocity and then with Speakeasy.
Aaron: Absolutely. It makes it a lot more affordable too because you're not buying new servers for upgrades versus with the past solution we did have to do that.
Rob: That's a great point too on that eliminating that is a risk, right, having that piece in the middle that could be a potential bottleneck.
Aaron: Or a single point of failure I mean you could put all your workers down if you had that server go down.
Rob: Right, right. All right, time for one last question. You talked about the use cases and what you have deployed. Number of users that you have today running the system?
Monty: The voice.
Rob: The voice system.
Monty: About 65.
Rob: About 65 users in that facility?
Rob: Great, great. Ready for enterprise size. Awesome, very cool.
Monty: Yeah, our ultimate goal is to, you know, proof it out, totally proof it out here in Pennsylvania and move it to our other GC's because we all have the same problems from a waste standpoint and an accuracy standpoint.
Rob: Okay, that was the one question I was gonna ask to wrap up which is what's next, and that's awesome. So, very cool. There you have it, folks. Systems up rock and rolling and again, everybody who's on here we'll make sure to get your copy of the case study that accompanies this webinar when it's published which will be shortly. Thank you very much for joining us, Monty, Greg.
Monty: Thanks for having us.
Greg: Thank you.
Rob: Aaron, Ed.
Aaron: Our pleasure.
Rob: Very much appreciated it. Folks, for anybody who has any additional questions you think of later, take note on the screen, certainly feel free to drop an email to myself or to Ed. You see both of our contacts on the screen as well. Follow us on Twitter up on what's going on mobility. With that, we thank everybody who has taken the time out this morning to spend time with us. And thank you all again, gentlemen for joining me here for this webinar. Thanks, everybody. We'll talk to you again soon. Take care.