BOOST Your ERP Podcast
BOOST Your ERP Podcast
BOOST Your ERP Featuring Daverick Wagstaff, ChemBio's Planning and ERP Systems Supervisor
Get ready to unlock the secrets of a successful ERP system implementation! Our guest, the remarkable Daverick Wagstaff, planning and ERP systems supervisor at ChemBio, opens the vault to share his hands-on experience. As we navigate through NetSuite's customizable features, automation capabilities, and scripting, Daverick's insights illuminate the path to a seamless integration in a regulated industry.
But that's not all. Ever wondered about the obstacles a NetSuite administrator tackles every day? We offer a candid look into their world. From tracking support cases to resolve potential snags, to mastering work order building and consumption systems, our conversation peels back the layers of this complex role. We even delve into the nitty-gritty of how transactions interact within the system and how to simplify this for end users.
As we conclude, we delve into the crux of technology, change management, and the hard work needed to drive success. We share a bit of advice on adapting to technology, the power of keyboard shortcuts, and the value that lies in execution. Our chat on change management highlights the importance of engaging people in the process and keeping it compelling. We close off with a round of appreciation for NetSuite admins and a salute to ChemBio's partners at goVirtualOffice. Join us, and take away a wealth of insights!
Well, welcome to the Boost ERP podcast. Today I'm delighted to have Daverick Wagstaf fro m ChemBio. He's been one of our customers with Boost for a while and he's actually one of our favorite admins. Daverick is not only a pleasure to work with, but understands ChemBio's business and their needs and really good detail, and it's always been able to communicate well with our staff. And I was deciding to have you on Daverick. Just like I said before, we started here just to be able to talk about what it's like to live in your shoes, and so everybody's listening, Daverick. He's a supervisor of planning and ERP systems and he's been our primary contact since we started. So, Daverick, welcome to the podcast. So let's start out. I always like to give out the list. There's kind of an idea of who you are and where you come from. So tell me a little bit about yourself. Where did you come from School, what's your story?
Daverick Wagstaff:Yeah, yeah, no problem. So I'm originally from Way Upstate, New York, about 15 minutes from the Canadian border, currently on Long Island a.
Daverick Wagstaff:So now the meeting, the decision to go to net uite was made before I've been started at ChemBio. Our previous CFO had experience with net suite, so he is the only actually wanted to make the change. By the time that I, by the time that I started at come by, we'd already been about a year and a half in the development of going live. We did like a slow launch, started with like the procurement module and stuff like that, you know, got the core of financials in there and Ben's rolled out manufacturing. So yeah, that decision was made before I even at ChemBio .
Todd Parrish:Got it in in just a general, just talking about nested in general, what? What are some of the favorite things that you've seen in this, or what were the things that you like the most about nested? I'm just curious.
Daverick Wagstaff:So I really like the fact that it's called base Our, our old ERP system. It was awful to log into it. You had to be on the terminal server, so maybe you know working remotely and it, you know, very, very slow because you'd have to sign into our terminal server in order to sign into the, you know, erp system. Besides that, I love how customizable it is. We have a lot of customizations in it. Being such a Regulated industry as we are, you have a lot of rules that we have to follow regarding what materials can be used, where they can be used, expiration dates up like that, you know, call quality management system flows, and that's what it is able to. You know gives you the ability to Customize workflows.
Daverick Wagstaff:You know certain record types. You know different order of events that you know help us Maneuver our day-to-day activities in a lot more efficient manner than the way that it was done before, because we are able to set up systems and records to talk to Each other. Where you know, before you had to do everything quite manually we can have one record automatically. You know create 50 different records if we wanted to, because we know what the rules are and do you have a lot of scripting in your nest, with account or no? Yeah, we do have a decent amount of scripting and that scripting you know really just helps, you know, with the efficiency of everything. We have a lot of scripting that automatically, will, you know, submit different Orders for approval. We have some scripting that you know reassigned regions based on our region assignments. We have numerous scripts that you know just help the end users day-to-day life.
Todd Parrish:Yeah, some of them I think was done before we we actually came in because we didn't help you guys implement. You know came to us later. But do you know, with that are a lot of those scripts or were those workflows? Do you know, was there workflows involved or was a lot of it scripting?
Daverick Wagstaff:a Lot of it scripting, and then there's a few workflows here and there. So a lot of the stuff that was done for us, you know, to get set up, a lot of it is script based. And then a lot of the stuff that I'm doing now is I'm doing the last more. You know I'm learning that you can do a lot of stuff with workflows. So you know I'm resorting to scripting when you know, when really needed. But for the most part, you know most of the development I'm doing right now is all workflow based because I can get the automation you know that I want out of, you know, setting of simple workflows.
Todd Parrish:Yeah, and you know it's always easy. You know hindsight is always 20 20. So with that scripting, looking back, what would you have done differently with some of the scripting other than maybe use other workflows? Is there anything they like? Lessons learned for people that are looking at scripting? What recommendations or advice to give?
Daverick Wagstaff:Um, you know I would. I would just honestly just figure, you know, just make sure that the script is needed. Obviously, you know, because if you can get it done with a workflow, I would personally just do it in a workflow because I think that you know, when it's just a lot more simpler, you know it's a lot more visible. On scripting, a lot of stuff can be done in the background and people lose sight of it. So that's another thing that I would say is also you know, just make I know it sounds silly, but make sure you're keeping track of all the scriptings that you're doing. Make sure that there's, you know, some database of them and you know what they're doing. Just because as time progresses, you know, five years after you're implemented, you know people that set up these scripts might know, might no longer be with the company and all of a sudden nobody knows what these things are Doing in the background.
Todd Parrish:So I think that's very important as well, yeah, and one thing that you know people mess great advice because a lot of people do forget. People move on or what have your Changed roles? And in people that don't change role, you know we're also busy and there's so much to go through your head he kind of forget the details. But you know, just keeping a list of those. But then also, I've always recommended make sure you keep the requirements. You know, and even if it's a workflow or if it's a script, really either way you want to have what the requirements were. Because a lot of times we see people are like why did we even do that? And in, and it's really hard when you lose some of that context.
Todd Parrish:So you know, always recommend, like if you're gonna go down, that you know Whether you do it yourself with a workflow or like somebody like us writes a script for you, that like make sure you keep track of those initial Requirements. That's why we always try to put in the proposals so everybody can always go back and say what was this supposed to do in the first place. Because you know, at times we get version control where you know people don't do version control, like oh, we made a change a year afterwards that if you can at least have some starting point, you can put together the pieces. But that's always really, you know, my biggest piece of advice is Keep the documentation some player access neutral that everybody can get to, and it really does save a lot of time and headaches down the road.
Daverick Wagstaff:Yeah, no, of course. And then another thing that I would also add is that you know a lot of our, a lot of our scripts will be based off of same searches. So making sure that you know if you're safe if you use scripts that are based off your safe searches. Make sure somewhere in that safe search it says like do not delete, do not modify, because someone goes in. They think that they're doing Someone's like oh, I really want an extra column added to this report. I think would make my you know day to day a lot more helpful. But little do you know that that's actually powering something else. You go in, you make that change. All of a sudden somebody else is complaining because One of you know one of their scripts didn't function properly.
Todd Parrish:Yeah, and what's really interesting is that I always had a branding whenever I was it, when I was an active consultant, like anything for like a KPI Scorecard, I literally put KPI colon in front of the name. So if anybody saw it they knew that it was for a KPI and our INT for internal or things of that nature, and everybody has their own little you know acronyms or what have you. But that's a really good call-up because you see that and all of a sudden Something makes that little tweak and all since something goes down. Yeah, is that sweet? No, it's actually in the script in the safe search. That's that's a really good call it as well. And so now, as an S we'd admin, so what, what is your typical week look like as an SNS we'd admin?
Daverick Wagstaff:My typical week looks like some troubleshooting, getting emails from end users. This record has this issue. Just because amount of data that we have in our system there's so much to compete with, we might have records that are cut. One of the biggest things is we might have customers that we've made in Actives. We haven't been busy with these customers for a while and they might have, since we made them in Active, we might have also made like an item on the record in Active. For example, we'll have a sales rep that goes in they try to remake them in Active, add new pricing or update their information and stuff, and they can't save the record. They'll email me and then I'll look into it and I'll be like, okay, yes, because we have this outdated item on the record, update everything.
Daverick Wagstaff:A lot of it's troubleshooting day-to-day. It's working on new modules. I'm currently working on setting up my account, the customer portal, working on that. Then it's looking into outside solutions for these integrations. Now that I'm doing the my Account, we got to figure out a payment processor that we'll be using to actually allow customers who pay through it. That talks to Netsuite. So then that opened up another can of worms. So a lot of it's new module development, new product development, customization, request report development.
Daverick Wagstaff:I get a lot of people asking me can you make this report for me? I like this report. Is there a way that you can make this? But add this Then, besides that, user setup, user auditing, making sure that people are using their licenses properly. We only have a certain amount of licenses, so once in a while I'll go in and make sure that everyone's at least utilizing the access that they're being given. Otherwise say, hey, do you really need this? If not, we'll find someone else that's going to make a use of it. Besides that, there's a million things that I can list off that I do on a weekly basis. I'll just a matter on where to begin.
Todd Parrish:Yeah, you mentioned one thing third-party products, and that's really an underlooked part of the Netsuite ecosystem. When people are looking at Netsuite as a product, I'm curious how do you or do you have a vetting process when you start looking at third-party products and what does that? Look like.
Daverick Wagstaff:My vetting process normally goes by obviously scouring the web, trying to find any information to make sure I get an idea, making sure getting a good feel that the organization has some professionalism to them, making sure that it's even worth my time to begin with. So if I see a website that doesn't really look like profession it doesn't, then I'm not going to waste my time with it. But I can't really see any other information, any other people talking about it, any good reviews on it, then obviously I'm not going to proceed on it. So that's what I'll do at the very beginning. Then, honestly, what I'll do next after I might meet with them. I might do a demo, might just have a chat with them, and then I'll also reach out to your team at GoVirtual. I'll reach out and say, hey, I'm looking into a solution for this. Have you guys familiar with this company that I'm talking to you right now? Do you have any other companies that you guys have personally worked with that you might recommend over them? So that's my methodology.
Todd Parrish:Yeah, and we do take a lot of what our clients say, because we of course, get bombarded just like you do as an SV user with different third-party products and stuff like that. But we do take a lot of credit in what our end users are saying, like this has worked well or this has not worked well. What third-party products would you recommend, or is there any that stick out that you like working with particularly?
Daverick Wagstaff:So right now. So one of the suggestions that. So one of the problems that I've faced is we're going through looking. We went through an area of trying to figure out how we can automate our direct labor tracking against the work orders. Right, Because one of the modules I'm working on is within routing, where you have all your manufacturing routing. You want to assign labor to it. But now it gets to the point where I don't want people to have to manually enter their own labor for that work order at the end of every day. I want it to all be automated.
Daverick Wagstaff:So one of the issues is we wanted a way to do it like scanning, where it's automatically tracked. People kind of just punch in, punch out and it'll automatically back flush into NetSuite. And your team actually suggested R of Smart to me and R of Smart actually showed me a demo of it that works perfectly well. We haven't gone forward with it yet just because I'm working and getting the my Account or not my Account the Whippin' Row module set up first to where now we can begin the testing for all the labor tracking. But the solution that they showed me was perfect, that our business needs exactly what I was looking for. So, based on what I saw, I would recommend that solution If anybody is looking for a way to track labor automatically and have it back flush back into NetSuite, because it really saves the headache. We do a lot of that manually. Right now we have manual Excel spreadsheet suggest. I know that once we get onto that it's going to be a real time saver.
Todd Parrish:Yeah, and we've actually have Ruth on this podcast from RF Smart and because that is one of our favorite third-party products and they are really solid company, solid product, good staff, good implementation methodology. So, yeah, I'm glad you brought them up. They're really solid, so okay. So when your people, when they have an issue, do they route that to your case or how do they let you know? Do you email? How do you generally get your request from your people?
Daverick Wagstaff:Normally it's always through email. I mean, I do sit at a desk, I am in the office. A lot of people do love to call me on my desk, but I try to tell people it's an emergency, call me. But if it's something that's like a net sweet issue, that's not life or death emergency, send me an email. Normally I tell them if it's in net sweet, send me a screenshot, send me a link to the record.
Daverick Wagstaff:It's one of the biggest things to get end users to understand is that you might be looking at a report that, for example, I'm looking at my open orders report. Your open orders report might be different than my open orders report. Just send me the link to it, because we've got so many different state searches because people like things a certain way, so I might have 10 different open orders reports. Send me the link to the one that you're having an issue with so that way I know which one to help you with. Because if I just look up open order report, I don't know which one I'm gonna fix and I'm probably gonna fix the wrong one. So, yeah, a lot of it's through email. And then I actually set up case management in net sweet so I just automatically. If it's, I just automatically pump it in a case. That way they can be updated as I'm working on it and don't be notified when it's resolved.
Todd Parrish:That's awesome and I still. I've always said for years and years that support cases is probably the least used functionality in net. Sweet, but every I don't care what industry you're in, what you do you can find and use for it internally at least, if not even externally. But yeah, that's super awesome to have every time. I love the cases.
Daverick Wagstaff:Yeah, no, it's great. And, like you mentioned earlier, we're doing things like we're doing so many things a day all the time where the good thing about me tracking these things with the cases is that a year from now, someone might have the same issue and I'll be like wait a minute, okay, I remember exactly what I did. Let me go to that, my notes on that and be like all right, now I don't have to waste two more hours refiguring out and resolving the problem. I can just be like oh okay, this is what I did last time.
Daverick Wagstaff:Let me see if it works this time and then save myself the time.
Todd Parrish:You know, and for those that are looking at it, I've always said that support cases really should be like the canary and the coal mine, because if you start to get enough data collecting, you know, like, what the issues are or problems are. Then you can start to see, well, I'm having a consistent problem in this area of my business, or a vendor or a report or what have you, or sort of like tracking, like scripts or things of that nature that it really should give you an idea of like, hey, there's something deeper going on in my business, because I started to see different data points on that. Exactly, exactly, yes, 100%, yeah, so that's awesome. So what's the most challenging thing for your staff? So, if you had to pick, you know maybe one or two things. What are your staff as an admin Like? What are their biggest problems? Is it Nesweed? Is it training? Is it understanding the system? What do you fight the most?
Daverick Wagstaff:It's honestly, it's remembering to do you know things properly in the system, knowing that you know. One of the biggest things is a lot of the times our manufacturing departments aren't doing their consumptions on work orders accurately or on time. So, you know, one of the biggest issues we want we encountered when we went live is that you know people weren't even building their work orders on time. So I had to create a like rule basically that would block you know them from being able to build the work order if it wasn't on the day that it was released. You know, and then you know set up alerts and reports to email. You know people every day that the work order wasn't built on time. So that was one of the biggest issues that we had when we went live. Then that got resolved because you know we set up those controls and now they're all built on time. And now it's a matter of you know making sure that they're done properly, making sure you're consuming the stuff, because now you know people, the end users, can be so funny because you can set up these rules, but eventually they're going to find a way to try to like keep the system. So we set up that thing and they're like okay, well, so he wants us to build the work orders on time every day, so we'll just build them, get the build made. We won't consume anything, but at least now it says that the work order is built. So you know it's. You know making sure that you're keeping track of the people, getting people to understand that how transactions you know cascade down throughout the rest of the you know system. Another big issue is, you know, speaking on that is teaching people how transactions communicate with each other is huge because, dealing with inventory, we get a lot of I get a lot of negative inventory emails. I have an alert that tells me hey, you have negative inventory, you know in, you know dislocation, so I have to go and look at it.
Daverick Wagstaff:And a lot of the time it's because in our, in our manufacturing environment, we do a lot of pre-yielding and post-yielding.
Daverick Wagstaff:So when they initially build the work order, they'll build it what they should yield, consume what they should be consuming, and then when it's finished, they'll, like you know, fine tune it. You know, build what was actually built and consume what was actually consumed. So all of the yields, all the yields get based off of that and so when they're post-yielding the post-yield as long as they're consumed. They basically what they would end up be doing is they end up consuming everything they did in the pre-yield on the next build and so after, when they lower the quantity on the initial build, now I have negative inventory because they consumed everything on the next one. So it's getting them to understand like, hey guys, if you're doing this build and then you're doing that one, make sure you go back and fix the one that you you know are lower because you can't consume. You can't consume 2000 of something you only made 1500 of, because now I have negative 500 in the system and we got to fix that.
Daverick Wagstaff:So a lot of it. It's just really getting people to understand. You know how the system works. The system can be user friendly, really user friendly. It's just that you know. You got to put you know good information into the system in order to get good information out of it.
Todd Parrish:Yeah, and you know you've done a nice job, like I said, over the years. Is there anything that really helped prepare you to get to this point, Like because, like I said, you do a great job with your team? Is there anything that is somebody want to be like an admin, like in the role you're in? What could they do to, like, help herself prepare themselves for that role?
Daverick Wagstaff:Honestly, a hands-on experience, a lot of looking into trying to solve your own problems, looking into it yourself. I spend a lot of time. We have access to my Learn, the NetSuite my Learn. I'm using the my Learn a lot, especially with new modules, development stuff like that. I look into different forums. I go on Reddit sometimes there's a NetSuite subreddit where I can literally look up questions that I'm having and I can find actual people other admins most of the time or consultants, different people, different experts that have the same exact issue and have a solution In order to get prepared for it. It's just getting your hands dirty, honestly. It's getting down and getting into it, partnering with you guys and your team, figuring out different solutions for different issues that come around, making sure that it's just not me just throwing the ball over the fence and asking you guys to catch it. I'll play a game of catch with you.
Daverick Wagstaff:I'm not just going to toss it over.
Todd Parrish:Correct, that's. One thing that we've talked about in the past is that we have a good relationship because it's two-sided. I've always made the comment that we thrive when there is an admin not that there has to be an admin on the other side, but we have that great admin in place that really can do wonders for the velocity of how fast we work. You mentioned before you're not just throwing up what has worked well for you. For those listening, we have a managed application services contract where we have a certain amount of hours that we help the average and their team. How do you best utilize our consume from GBO? What has worked well for you?
Daverick Wagstaff:What's really worked well for me is basically figuring out what my high-level projects are, figuring out what those big goals are within that suite and trying to partner with you guys to get those done, get those worked on. Like I said, I handle all the day-to-day the troubleshooting, the emails, all of these smaller issues you're in there, managed by me. I like to get the best use of our hours on those higher-scale, more in-depth solutions because, like I said, I know how to do all the troubleshooting Every once in a while. Maybe there's an issue that it might take me a little bit longer to figure out because I haven't dealt with it before, but more or less I have all of that covered. I like to utilize our monthly allocated hours on large-scale projects that are basically changing how we do different processes in the system for the better of our company, because to me that's the best value for what we're paying.
Todd Parrish:Absolutely Okay. We'll switch gears a little bit here then. Been in technology, been went to school for this and stuff like that. What's some of the best technology advice that anybody's ever given you, or anything you would share with other people?
Daverick Wagstaff:Well, just from the beginning, some of the best technology advice is just to always be ready to adapt and evolve. With technology, I mean technology. It's always moving at a rapid pace. It's constantly growing and evolving. It's important that you're adapting to the growth and you evolve. With this You're always getting the most out of it. Generically, I would say that's some of the best advice I've gotten. Then, actually, specifically regarding a piece of technology, like with computers, when I started leveraging computers like keyboard shortcuts, it's a game changer. That's not one of the hidden gems, I'd say.
Daverick Wagstaff:If you're not utilizing and leveraging keyboard shortcuts, they save you a lot of time Moving that mouse around. It sounds silly. It's a second here and there, but those seconds add up if you can just do it on your keyboard shortcut. I actually even have a Chrome extension for NetSuite that I programmed certain key codes to relate to different records in NetSuite. If I just type in these three keystrokes automatically, it just opened up an inventory adjustment form. I didn't even have to move my mouse at all. I quickly typed three keys and there it is.
Todd Parrish:It's open for me Wow, that's cool. I'm going to have to check out that Chrome extension because I wasn't aware of that, but that's really cool.
Daverick Wagstaff:Yeah, it's really helpful.
Todd Parrish:I just used the simple one, just like copy and paste. I was just sitting there thinking if I actually had to go in and highlight in copy right-click, I just like the control-s-control-c. I can't imagine doing anything without that. That's really cool. How about for a business In Kenobi? You've gone through some different changes and things like that. What's some of the things that you've learned that you think that Kenobi is a business that's just doing really well? Or any business advice that you give?
Daverick Wagstaff:So I guess I'll take it as two different ways. So what Cambio does really well is it really does adapt to its changes, because the market's always changing. So Cambio is really good at adapting to the different market trends. Like I said, I think we handled the COVID and no market is like really well as good as we could have given the place that we were in at the time. So I think that's something that Cambio does really well.
Daverick Wagstaff:And then just some good business advice is kind of something I alluded to earlier. But it's that you're not really going to be able to rely on reading all this information and looking for, I guess, a secret sauce to business success, because there's not really any. You know you're not really going to be able to find just an answer like that. A lot of it comes from getting your boots on the ground, getting your boots dirty. You got to go through, you're going to have some failures with it before you see success, but like that's really where it's going to come from. You can spend all the time in the world reading and researching, but then all of a sudden you're in the scenario and you know the textbook didn't really prepare you for this.
Todd Parrish:Yeah, and what's interesting is I do think that times people get focused on an idea and like there's a million dollar idea and there's no lack of million dollar ideas, but there is a lack of execution on million dollar ideas and that's really what I've learned in my seat here at Ten Years at GVO is like those that can take that idea and execute that and automate it you know, like talk before and things of that nature that's really what I've seen. The difference between those that are closed, that are way past you know the finish line on getting that, is really just getting in there, figuring out a way to execute it and work with the team to pull it off. That's and you're right. There is no secret sauce, right.
Daverick Wagstaff:Yeah, exactly.
Todd Parrish:There's a lot of hard work and there's really not much of a you know a short cuts with that. And you know one thing that's really mentioned that there's a lot of different technology and learning, and you know, and rolling with that sweet, that's always been one thing that I've always thought is really important, like two new releases. There's two releases every year, you know, taking advantage of that, and there's always a cliche, but you don't know what you don't know. So it's good to pay attention, but what part of that challenge, though whether it's the million dollar idea and how it executed is really comes down to change management, and we see that at times as the struggle. So how do you at ChemBio help with the change management, like whether it's something you've come to GBO with and we're helping you with, or something internally what's worked well for you, getting that change across with your users?
Daverick Wagstaff:So, when it comes to change management, I really think that there is like there's two key key strategies or two key ways to go about it. One is it's always got to put the people first. The people are the ones that are experiencing the change. When the change, you know, is, you know when the change is live, right, you know they're the ones that fuel it. The change gets easier when you engage them in it. So, like, if people aren't involved and they don't understand or believe in the change, you know the change really, you know it can only go so far, right. And then I'd say the other strategy is you know you got to make the change compelling and exciting, right? So many people have that mindset. If it's not broken, why fix it Right?
Daverick Wagstaff:So, like you know, the biggest, the biggest thing that, like you know, we heard when we were implementing that tweet, was our old, our old systems. Like you know, why do we have to do this? Like, why do I have to learn how to do it this way? But once you know, you show them that, hey, you know, yes, this is, you're learning a new thing completely. It's a completely different system. Right, you're not nearly going to be spending as much time doing tedious stuff that you were doing or you are doing in this current system. And once you put it in a perspective that is easy for them to understand, like that, where you know they see it as a way of they're getting something out of it, then you know the change is a lot more receptive by them. So I think, as long as you know you put in the people first and you're making that change exciting. I think that you know it's. You know it's really hard to have an unsuccessful change management.
Todd Parrish:Yeah, and to me, you can always win the boughs but lose the war. You know the war is getting them to want that and see the benefit of that, so that's really cool. Well, the last question I have is really what are you excited about in the future? What do you see coming in Nest Leader and Business? What are you excited about? What's on the future horizon?
Daverick Wagstaff:So it's really exciting for Kim Bio as a company. We just got acquired by BioCinex, which is a French market leader that also specializes in the distribution of rapid tests. So with that new partnership it comes up a lot of new synergies and exciting business opportunities for us. So that's what is. That's an opportunity that I see for our company. And then you know, regarding Netsuit, like I said, I'm working on a couple modules right now. We got some exciting stuff cooking up. We got some projects that I'm working on with your guys' team we're working on.
Daverick Wagstaff:You know, one of our business needs is one of our challenges is Bin transfers, and Netsuit are kind of done automatically, where if you enter a Bin transfer you know it automatically goes from one bin to another. Right, but we kind of do business Bin transfers in our department, at our company, so we don't really want one person to just be doing it and being done in the system. So GVO is actually helping us to create a kind of a Bin transfer request form where the end user can request it and then our warehouse team can do the movement. It's kind of like a transfer order but an interlocation transfer order more or less. So that's pretty exciting.
Daverick Wagstaff:It's going to be exciting to get that solution on board because right now, you know, for those interlocation, interdepartment Bin transfers it has to be done through an email. So it's an email, can you please move this? And then the person that moves it will do the Bin transfer. So that'll be a nice little solution when we get that. And then the two modules that I'm working on the my Account module for the customer portal it's going to be exciting to get that live start getting customer feedback on that, you know. And then Whip and.
Daverick Wagstaff:Routing. You know Whip and Routing. It's a huge undertaking. It's a big project that I've been working on for a while. But I know that once I get that done, once I got it perfected and it's live, the financial reporting on it, the demand planning, benefits that I'm going to get from it, they're going to all be worth it. So those are the exciting opportunities that I see.
Todd Parrish:Awesome, and I'm excited to see Whip and Routing, though we've been talking about that for a little bit. I did not know about you guys implementing my Account, which was literally one of my favorite modules. I love that and, once again, if you have any customers that need to get access to similar information, it's a great portal. It's a really good product, so looking forward to see your feedback on that. So any final parting words to ever gain anything you want to share with other NetSuite admins.
Daverick Wagstaff:No, I mean I think we covered a lot. Thank you again for having me Other NetSuite admins out there. Like I said, it gets down to putting your boots on the ground looking into it. There's so many resources out there for getting the information that you need, and Go Virtual is a great team to partner with as well. We've got a bunch of great minds that I work with weekly and I highly recommend them.
Todd Parrish:Well, thank you, I appreciate the kind words and, like I said before, it goes both ways and good partnerships are solid on both sides. So well, thanks a lot, daverick. I really appreciate you having on the call and wish you the best with the new purchase and hope everything goes good. So, thanks a lot, all right.
Daverick Wagstaff:Take care Bye.
