Video: Streamlining Driver Payroll with Argano’s Oracle Cloud Solution for the Transportation Industry | Duration: 2872s | Summary: Streamlining Driver Payroll with Argano’s Oracle Cloud Solution for the Transportation Industry | Chapters: Webinar Introduction (3.84s), Introductions and Agenda (78.785s), AI in Incentive Compensation (232.46s), Industry Challenges Overview (521.48s), Payroll System Considerations (856.67s), Streamlining Driver Payroll (1347.59s), Wrapping Up Benefits (2239.825s), Audience Q&A Session (2519.285s), Legacy System Integration (2697.45s), Closing and Appreciation (2810.66s)
Transcript for "Streamlining Driver Payroll with Argano’s Oracle Cloud Solution for the Transportation Industry":
Hello, everyone, and thank you for attending today's webinar, streamlining cyber payroll with, you know, support. Before we begin, I wanted to let you if you have technical or content related questions during the presentation, please use the q and a box, and we will address them. Closed captioning is available by hovering over the stage area and clicking the cc button at the bottom of the screen. To access today's resource materials, simply select the docs tab on the right hand side of your screen. All registrants attending today will receive a link to the recording post webinar. Now I would like to introduce you to today's first presenter, Richard Swartz, who oversees our HCM business development at Argano. Richard, welcome. You may now begin. Thank you, Carrie. Thrilled to be here, and good afternoon, everyone. Thank you for joining our webinar today. We're thrilled to have you with us. We have three amazing speakers today, and I'd like to have each of them do a quick introduction. So, Ryan, please introduce yourself. Thanks, Richard. Hello, everyone. This is, my name is Ryan Connor. I'm a regional manager, at Oracle. I've been with Oracle for, seven years, based in Atlanta, Georgia, and I'm responsible for our travel, transportation, and logistics vertical here at Oracle. Thank you, Richard. Thanks, Ryan. Kathy? Hi. My name is Kathy Murray. I'm part of the HCM, practice here at Argano, and work very closely from the sales to delivery and within the transportation area on how to solve the challenges we see, specifically around the payroll, but all the way back up to HR. And so happy to be here, and we'll talk about the different areas, throughout the hour. Great. Thank you, Kathy. And Shondra will be joining momentarily, so we'll just continue on. So here's today's agenda, and we're gonna, go through a, a very, organized order here of our driver payroll solution, and I'm gonna start with the Argano introduction. So, Argano's Oracle business unit covers the complete Oracle cloud offering, all the pillars, and you're actually gonna hear about three of those pillars today, HCM and, and CX, excuse me, two of the pillars, two of the four pillars. But we are a twenty five year partner with Oracle, have over 800 people. We achieved a very high net promoter score, one of the highest in the industries, and that's where customers have been asked would they do business with Argano again. So we're very proud of our score. We have many awards for for excellence, for excellence and have done over a thousand cloud implementations. One of our awards is from this year's Oracle, I should say, or last year Oracle's Cloud World, which you probably now know is, for the upcoming year, Oracle AI World. We won at last year's, Oracle showcase a twenty twenty four partner award. This highlighted our achievement for innovation. And this is just one example you're gonna hear today of the many innovative solutions that Argano brings to the table with Oracle and our customers. So with that, I'm gonna pass it to Ryan Connor from Oracle. Ryan? Thanks, Richard. Yeah. I can't, say enough good things about Argano. I think the true test of a a really, strong systems integrator and a and a partner is, is seeing customers sign up for phase not only to do phase one, but also do additional phases in phase two. So, Argano's, is implemented in several of my clients, ERP, HCM, and and even supply chain. So, but just to talk a little bit about, Oracle's industry perspective, can we go to the next slide? Awesome. Thank you. So AI is probably artificial intelligence is probably one of the most important, areas of investment here at Oracle. Larry l Ellison, the founder of Oracle, believes that AI is the most important discovery in human history, because he thinks that the next generation of AI will reason, it will discover insights, and conduct tasks much faster than humans ever could. And so Larry's perspective is important because he drives Oracle strategy, and AI is the top is his top innovation priority. And so, you know, if you think about where Oracle has, is really putting a lot of, putting a lot of emphasis is that we build our applications to be AI first with a single complete suite that includes finance, supply chain, HR, cell service, and marketing, as well as industry specific applications. So this means, when we deliver AI use cases, whether predictive, whether generative, or age agentic use cases, your data is already in one spot. So there's no room to move any of your data. And in addition, there's no need to define security or access rules because all of these things, have already been done with inside of your Oracle Fusion applications. And so as such, the easiest and the most cost effective way to really start taking advantage of AI is with these embedded use cases and Fusion applications. That includes predictive AI, generative AI, and AI agents, as well as AI agents teams. Can We go to the next slide. Thank you. So I'm gonna drill down now to kinda start talking about the, specific, solution that we have around incentive compensation. This is one of our areas that, we've got a very strong presence in the market, especially when it comes to transportation and logistics because of the high number of drivers that have to be paid on a variable model. And the the beauty of Oracle is that because we have such a broad and deep platform, you have your HR as part of your fusion application suite, as well as a lot of the, calculations that take place to to generate compensation, all in the same suite as your ERP, which actually is your actual. So, being able to deliver a very, accurate, comp variable compensation to your employees is is something, that, is is very is a result of really having everything on a single instance, on a single application. And what's even more important is what we're doing with AI because everything's on that scene that same platform, and all of your, you know, all of your data, all of your business rules, all of your employees, all of that context is is kept on the same application platform. And because of that, we can drive really, really strong reporting, not only which I think the use case we're gonna focus on today is really around drivers, but with the same concept can be taken to, your sales staff as well, and when you start thinking about, you know, variable compensation, incentive compensation around commissions. So, can we go to the next slide, please? And that might be my last one. I'm gonna pass it back over to to the r oh, there's one more here. Yeah. So I just wanted to call out some of the, meaningful business benefits that our customers receive, from, this incentive compensation, variable calculation tool. So, you know, you can see that, they're strong there's a strong ROI when you start paying your employees accurately, and there is very, you know, there's a workflow that can support, you know, if there is any kind of service request because of you know, if there's ever any kind of, I don't wanna use the word inaccuracies, but if there's any questions or or additional, discussion that needs to be handled and managed through a service request, you know, you have that capability too. So, with that, I'm gonna turn it over to Argano. Thank you for the time. Great. So as we look at today and we talk about what are the issues, what are we seeing within the industry, There's a lot of unique challenges, that we could be solving. Every organization that we've talked to is trying to solve something different. And so what we're gonna talk about today is just the complexity that lives within, the ecosystem within transportation, whether it's playing not just employees, but owner operators and the independent contractors that are you're working with or just being able to calculate visibility. And then just regulatory compliance, making sure you've got your licenses up to date and you're putting your drivers out there in a safe place. So there's a lot of different challenges that we'll talk through, as we go through. One of the things we think about as we go through beginning of talking to the customer is what are they trying to solve? Everyone has a different area and different pieces to the puzzle that we're flexible on how we work with them. So we try to bucket a couple different key challenges that we see that different organizations are solving. So we talk about the classifications and ownership. So this is, do you have or you just have employee drivers that you're going to be paying, or do you have independent contractors? Are they bringing their own trucks that we then gotta manage contracts with them, making sure the maintenance is up to date on their trucks, being able to calculate their pay? So we talk about what is our workforce classifications that we need to be solving for. As well as we talk about those drivers, what are the regulatory compliance that needs to be in place? How are you monitoring that? How do we make sure we have the right insurances, licenses, and certifications that are real time updated and making sure we're dispatching our drivers, we're dispatching those that are up to date. Other things that we're looking for is when we're talking about the payment and data complexity around the different driver operations. So how do you pay your drivers? What are the systems that they're in? Are we looking to change those systems? How different are they? Are they based on the company wide? Are they based on the contract that you're working with? So all different variations as to how we might need to be paying our drivers. Do you pay them different first versus an employee owned versus an independent driver? So that all comes with different complexities. How do we handle different contracts? How do we make sure the employee understands how they will be paid or the contractor know that they're gonna be paid? And then the visibility of not just where is my route, what am I gonna get paid, but how did that calculation happen. The bonuses that are paid to drivers, keeping your drivers in place. Right? So much of it depends on they wanna be paid and compensated for what they're working and being able to see that immediately. So in the end, right, we're looking at we got drivers. We got a software. We need to have a system that can really allow connectivity at any point, whether we are offline, online, giving them the access, and they want the real time. You know, I finished that trip. How much am I gonna get paid for it? Or I might want to understand what will I be paid as I'm going through. So the visibility into not just what is my route, but how much am I gonna be paid, what is my paycheck going to look like as I'm progressing through the week, all that information is there's different ways we can solve for within the cloud. So these are starting to open up the different discussion points as we talk about what is the right solution for an organization, how complex of a, transformation are we looking for? Is it HCM specific? Is it ERP? Is it holistic? Even doing the dispatching. So when we say what's the solution, we hang out. We have a lot of different challenges. What are the different solutions that we can look at? So one of the things that we've really thought about is everybody's at a different place, and we wanna be able to meet organizations where they wanna be at and where they need to be at to start maybe start the journey, or they're halfway through a journey. And so the way we've really looked at this is that we are looking to build scalability within the organization and how an organization might transition throughout the process. So we focus on we need employees and maybe HCM is first. And so whether we look at first an HCM only implementation, that really we're focusing on being able to have, drivers in the system, whether they're independents, whether they're your own employees that were they're recruiting or were coming through Tenth Street being able to bring in all the data, track the drivers, make sure we've got all the licenses, and that we have our regulate regulations all up to date on the employees. That could be a step one. Just paying them. Right? And so that could be a step one in the process. As we go down, we talk about, okay. Maybe this is an HCM and ERP. We're gonna keep dispatching. We're gonna keep wherever your trips are calculated today and we receive it. That's a fine next step too. Right? And so we see these inter inter interrelationships that can happen. When we start to say, hey. I'm looking at I'm looking to replace, and I wanna have a trip calculator that's that's I wanna get rid of maybe a green screen that's doing it today for you. Oracle has the capabilities, and we'll talk about how Oracle can calculate the trips, how it can receive information from a dispatching system, where the trip started, where it ended, how many miles are calculated, how many drops and hooks and different assessorial pays that might be tied to the trip can be visually there and then connect directly back into HCM and ERP. And finally, if you wanted to do dispatching, you can do all of that. So there's different pieces, that we've seen different organizations. We have not seen one size fits all. Everyone's in a different position of where they're looking to start their journey or pick up on their journey. As we start, you know, there's different building blocks. We talk about alright. Great. Like, I wanna start HCM or maybe HCMDRP or trip. Right? We start to then break down how do we start even thinking about design. What are the design considerations? What are we really thinking about maybe from a footprint perspective? So we start the conversations early in the sales cycle to understand what are the right footprint of modules and capabilities that you were really looking to to bring on to the cloud. One of the first conversations we start with is legacy systems. What are we replacing? How much information is there? What is the knowledge of those? Right? So maybe we've got, you you know, we've got a on homegrown system where you're finding a hard time being able to staff up and replace those. The employees are currently supporting that. That's one of the biggest things we are seeing, within the industry is, you know, our knowledge and the backfill of capabilities on those legacy systems is a reason why companies are starting to change. And it's is it all in there? Is it partial? And so the legacy systems of understanding, is it just dispatching? Is it trip calculation? Is it my employee? Is it my ERP? I've understand what are those legacy systems, and what processes do they hold within. So what are the end to end pieces? So legacy systems, we start working through, and then we start talking about what are the type of workers. Do we have independent contractors that you are going to be processing? Do we need to have assets in there? Do we are they bringing trucks? How do we maintain our trucks in our in our fleet? How do we gonna interact with our employees? Are the processes different between different types of workers? And so we're talking about our types of workers, which leads us into the operations. This is really where we see a lot of the discussion around will our how will dispatching, trip calculations start to change, stay the same, where are you guys at in that journey? And a lot of this then we'll talk about when we talk about specifically payroll. This operations to payroll, there's a lot of different options between this this box and the rate determination of how do we understand what is our payroll specific solution going to look like, where where are rates stored, who owns rates today, Is it a time system? Is it a payroll system? Is it the trip sheet that's really calculating it? How are miles calculated? How are they communicated to employees? How much information does employee need to see or driver need to see ahead of time? And then we talk about rates, how many different rates? Are they negotiated by contract? Are they negotiated at an organization level, seniority level? What are those different components of rates so that we're able to best solution where they should live once we understand ownership of them? So a lot of different considerations specifically when we start talking around the payroll, which then ultimately opens up to what is the right solution from a footprint within the Oracle software, to start, to build on, and to continue the journey. So we build out a couple different examples that we've seen. We're gonna kinda high level show. These are more when we see a full implementation minus the dispatching side of it. What have we seen? And we'll kinda give you a high level from company drivers versus independent contractors just if you do have those independent contractors, how they can be managed differently. So from a company driver perspective, I won't go detail box by box, but a lot of times, we still are seeing a lot of drivers still utilizing 10 street within companies. And so we've worked attention and understand the 10 street of being able to ensure that we're coming back and forth with data accurately through, the recruiting system, bringing on employees, making sure that we've got everybody up to date on information. We are dispatching employees, making sure that when we dispatch the latest and greatest operations, wherever that dispatching's happening, has good information. They know who can be dispatched, and then where they are throughout the process. We then talk about, like, being able to have our, trip calculated. Do we need to have any adjustments? How do adjustments gets handled? If there are any adjustments, like, do we need to go through accounts receivables for any capabilities? And then going through the payroll calculation, making sure payroll's processed, having settlement sheets, trip sheets, however your organization calls them that matches our payroll rate, making sure those two are in alignment and that, the drivers really understand the breakdown of not just, you know, this is my payroll account, but the trip that relates directly to my payroll. So when we're on one system, the payroll then is directly going to GL. We can manage cash management through everything to make sure everything's one stop shop. None of this is custom integrations. This is just native functionality when we start using the full application. So pretty seamless throughout the application of being able to throw, like, flow through hiring, dispatching an employee, calculating their payments with overseas down to handling adjustments, and then making sure the GL is accounting for, the for the payroll transactions that occurred. When we talk about, come independent drivers that are bringing, trucks, we really start to see a different dynamic and really plugging a lot more into the ERP applications and really building out what do I need to know about them. And you'll see in here, you'll see the word pass. That is an extension that, you know, Argano is built on to make sure we're connecting all the information about a contractor and the contracts and the the agreements that they're signing and making sure everything's buttoned up as to what needs to happen. So similar path as an employee. A lot of similar pieces of being able to come in through Tenth Street. The recognizing as independent contractor, we are not necessarily paying them through a payroll perspective, but they need to they're gonna be paid through AP as a supplier. So being able to have a dual record of I have a supplier and I have a a person essentially that I'm able to dispatch and be able to put onto a truck and track them, you'll see the difference around two around the, you know, the contract maintenance, making sure that the contract's up to date. We might be registering their asset within the system to know that we can maintain it, track it to make sure that the life cycle of that asset, even though the company might not own it, is on track and on target. As we go through, right, we talk about in those maintenance contracts, if you have those, contractors that are bringing their trucks, you might be wanting to hold payments back to ensure if there's an issue with the truck, they have paid the the ability to pay. So being able to make sure that we've got deductions almost coming out of a potential independent driver's, payments, right, to supply that if there is any issues, we can handle those. And then we start to see as after the pay calculation that comes through, they're getting the same settlement sheets that a a employee driver might get, but they're really then going down the route of going to be paid through AP, and being able to be still tracking the GL at the end together, but we are pushing them a different route. The business process around their day to day, activity can follow the exact same business process as an as an employee driver. So just a little bit about how the the different life cycles, different applications, and how we can solve different, areas within the solution of what might need to be, solutions throughout the project. But any of these can, you know, also integrate with other components outside of Oracle if there was not only an HCM or an ERP component that was going first. So I'll hand this over to Chandra who'll talk about the trip calculation, how we built that out. Thank you, Kathy. That was actually a wonderful walk through of the HCM side of the solution. Thank you, Richard, for the beautiful introduction and Carrie for the organization of this. Yes. This trip calculation is the most important part that, we tend to foresee because, most of the time, it's the dynamic derivation of data real time to the drivers that which actually pays a lot of, information and in into the motivation as well. So, ideally, I would, say, you know what? We've we've taken care of the payroll system. We've organized the data. What's the next for us? Streamlining the driver payroll engine, basically. A lot of the times that I've seen across us in these systems, the effectiveness of delivering the amounts paid or, using the the type of pay that we have to use and the number of stops that are part of the journey, or maybe you get in a last minute trip added to your route as well. How do you really make sure the driver is happy and he gets to see how he's getting paid? Oracle's incentive comp framework, actually, it's really dynamic and robust as well. Over the period of time, it really became a really excellent engine, not only for the capability of, calculating, it also optimizes, data derivation versus some key steps. Like, when Kathy's team is ready to push the data into the payroll side, are we ready to see the data? Yes. We can see the data right away. Is the driver really assigned to the right payroll engine? All of that, of payroll plan. And once the data is ready, are we ready for calculation? This incentive comp framework for Oracle's engine networks as the backbone for making this this, for real time experience. So this this engine not only for powers, it also keeps we are also ready an update for the AI challenges. Well, you know, the efficient, engine is basically powered by for the payroll or the admin who's maintaining the application, he has a guided creation. He has the enhanced usability with embedded generative AI. And at the same time, the agile deployment and AI driven after that creation. Where does it help me? Yes. You can build couple of agents for the dispute side of the driver. It helps you to really understand where does if he has questions, because this being a volumetric business, process, because you have thousands of drivers, a part of the system. If they really wanted to see where they stand or what's what's the he's not sure about the amount of money that he got paid for a particular trip, and how do I really get? I can build an AI agent that basically helps me to look at that particular what my plan is, what did I make last month, what did I look at it, and how do I get, how do how how am I making it in this right now? All those information can be driven, by the AI agents as well. See, if you really look at it, this is the high level flow that once we have, the driver, hired into the system, So, you know, it might be a vendor based driver. It might be an employee driver. It might be your own contractor. Once that has been settled in the system, you tend to see that, how do I really try to, automate this into the calculation? How does it happen? Are if the the ICM's framework has a beautiful assignment engine, it looks at the qualified attributes that belong to the person. And based on these, values that are assignments that it belongs to, the respective plan is basically assigned to him. Or automatically, when he's on board and he's he's on a trip, that data comes in through the system on the data side. The metadata is coming from the payroll side. Both come in and they call into the plan, and the bucket looks at it and says, oh, this is this is what he's entitled for this week. Here is the number. And it prob it also has a capability to send an approval to the manager and say, okay. You have this particular payroll coming in for the weekly or the daily payroll or the monthly payroll. Look at them and see if you can calculate it or approve it. And sometimes there's some wrong information. It has the capability to over to check that particular validation, and you have an approval in place that really looks through the process. So that's the beauty of this engine. If you look at this end to end flow, is, that's where the trip has been calculated. They're an adjustment. That's the beauty of this engine. Like, they're not happy with it, and you have to reprocess the data. And he says that, hey. I I have I've, talked to the payroll. They forgot to pass through it. They might wanted to do an adjustment manually to this particular process. That's the is the framework gives you the capability to really put that extra feed into that plan, and you can recalculate our if if you don't want to recalculate, it picks up when the next calculation runs in. It calculates the amount and gets it pushed. If you've already paid the payroll, don't worry. It'll be there in the next payroll, and it's adjust to the next payroll as well. You have a high visibility, and it explains the differences in the components as what's paid before and what's paid now as well. The another part that I've always felt, looking through this industry is reporting capability. Reporting not only, for the drivers to see what they're earning, it's for the payroll admins, the ad or the driver admins or the managers. They wanted to see how the the numbers come through, what are the you want to have a detailed perspective of how he performed on a route and what type of rates has he been paid on. And because, obviously, when you're on a route with a different set of, metrics, each has the different variable rate component that is attached to it and which we build it in a system to dynamically derive during the, the calculation rate derivation, for the week, and it calculates that amount and shows it to you. Now how do I explain it to it? Unless there is a clean-cut, perfect reporting that this Oracle provides, you can really, have a in-depth view of what's happening around the route. And there's a sense of, you know, less less work for the admin team and more satisfaction for the sales rep as well. Quite recently, I've seen because we are in the age of competition and, you know, a lot of business processes. How do you really try to compete, with the industry? And, you know, the key things that I've seen is attrition, driver attrition, satisfaction, loss of interest, and how do you or you've been on the same job for a longer period of time. How do I really, boost those, productivity, you know, more, you know, confidence levels or show them that you really work for them or you create that interest in the, whatever job they're doing because we have to keep motivating every now and then. So we run the the incentive comm framework, looks at these data that's already pushed in, use that data driven, and analyzes it, and we can build contest on that. What does this contest do? You can use those contest as, you know, as a widgets, to the, to the incentive comp mobile application if your driver has the capability. I know some of these drivers are part of a vendor, and they don't have the capability. Maybe the vendor can have the capability to see the the contest and say, okay. These are my key performers. He has he has the least number of, tickets or he doesn't speed. And, it it gives you this engagement constant engagement, which not only helps us to understand, improve the productivity of it, it also has the indirect proposition by reducing the operational cost. That that is what we've seen when there's a large volume, you have to constantly motivate them by which also has this indirect benefit for the organization. Gamification. Exactly. Engaging them in challenges, sending real time information. And, you know, all these, engaging challenges that I've I've seen across in the past in the industry is constantly making them training or, you know, having them and to get into a situation, where in the being part of these contests or the day like, daily, competition rewards and having a real time feedback like surveys. How do they do it? Are they being part of it? Or maybe have even the customer also be part of the show and say, okay. How did my driver do? I always see, in behind these trucks, you know, how did my driver do? And a lot of these 800 numbers. These are what we try to gather out and provide that perfect driver rating experience. Not only calculating, but we ensure that we use this information to go that extra mile and, you know, with AI in place, we can use this data for predictive modeling as well. I I'm good. Thank Kathy, it's great. Good. Alright. So payroll. Right? We the payroll people on the phone, we are the end result of a lot of information. So, when we talk about the payroll side, there I have been a part of four transportation projects, and I will tell you not one of them was the exact same. So it is every there's there's very different ways that we can solve all the payroll needs. But in the end, when we start talking about fundamentally from a payroll perspective, what we're really trying to get down to is payrolls engine, payrolls a calculator. Let's if we break it down simplistic side of it, we are looking for data to come in to understand how many miles were driven or how many accessorial items need to be paid. Do I have any vacation time? Right? Those pieces still need to be in place. When it comes to payroll, when we talk about the different options from a solution perspective, I mentioned it before, a lot of it's gonna come down to understanding the variety of rates, how your rates are generated, what exceptions do you have to rates, and where the best place to store them are. So there's different solutions available, whether it's fully in HCM. Right? If we are fully in HCM, those are generally when we are based on years of seniority, the type of whether I'm driving single or team. Right? If a single or team comes in and I get paid a certain rate based on my years of seniority, I can automatically have that rate available. And during the payroll calculation, it can dynamically figure out what to pay. If I've got combo drivers, I might be working on doc, might be work, might be driving. I might have different rates for them and understanding them as a person lives in HR, I can still dynamically store those rates and calculate. So when we talk about, like, the left side of storing rates and calculating, that is generally we see those solutions mostly around the organization, has calculated and determined rates that we are gonna be paid based on something that lives on their record, and then it comes in based on the activity. So the activity, as you see, how many miles did I drive, the drops, the breakdown. There's a rate tied behind each of those that I can say how how you know, again, your scenario is probably the most common one we've seen. That's a really great solution to store everything within the payroll process. Where we start to see what Chandra was working through and where we see the power of having incentive comp in play is when every single one of our, our programs in which we associated in a driver to be paid can be very dynamic. So it's not just based on maybe seniority. It might be I'm hired specifically to drive for x driver or x type of work, and my payment package is essentially unique to me, or there's nothing about my employment record that ever tell me that's how to be paid. That's when the incentive compensation can really understand these pay packages, create pay packages, the calculation identifying the rate to be paid can be handled within that trip calculation, and the end result is passed in the in the payroll. So then payroll is receiving not just You Drove Out Smiles, but at this rate to be paid because that paid that the pay profile, essentially, or the payment that you've been agreed that you're gonna receive is outlined within the the the trip calculation or incentive comp in this case. So that's within Oracle. They can hand in hand back and forth. Right? So I can tie people to different programs, and that program then has the background sitting in instead of comps. So from an HR perspective, I can still understand, give me everybody on this program. I don't need to have the rates and everything tied to it, but I know who are on those programs. And then I'm not storing the rates all in, the HCM side of the house. And then the last one we see is when, we will have not using sign of comp. We're not using any Oracle. There's still a homegrown system or another system that is really doing all the calculation, and we are just being receiving the rates, the amounts, the miles, everything is coming in, and payroll is just fundamentally processing gross to net. Within all this, you can have a combination. So I might be storing some rates and some of my periods be coming in. So it's very flexible in terms of what the right what the right solution for each organization will be. But it's a lot of the upfront design is understanding what are your pay practices, how many exceptions do we have, what is the easiest route for maintenance, how do we understand adjustments over time, flexibility, and all of that with the intention that this can still continue to grow. And as your business changes, you're able to shift, and payroll is not a problem that we're redesigning. So a lot of different options there. No right answer, and a combination of all these is sometimes the correct solution there. So I think as we start to wrap up and, answer a couple of questions, the the biggest piece we want, you know, the audience understand really is we are building to meet you where you are and design that to continue to take you further in whatever aspect you wanna do, where it might be starting small, going bigger as you go, or it might be a big bang and everything's done at at one time. When we talk about there's there's a lot of, benefits to putting everything in a full suite or starting where you have the capability to move to a full suite, the real time analytics, it is at this point in our, society, people want real time. They wanna know how much I'm gonna get paid. They wanna be able to calculate. They might wanna be able to receive that payment daily if needed. So not just being able to have real time analytics, but to be able to actually pay on demand as needed and letting those employees or drivers be able to, you know, whether it's taken in advance or pay early, the real time, really important. Chandra, I mean, if you wanna hit the next couple one as a wrap up there a little bit more on the incentive comp. Yep. Can you hear Chandra? Yeah. Yes. Sorry. So so, if this is what I talked earlier to where the after we do all these beautiful processes, the biggest, you know, setback I see is how can I really see what's happening around me? Where's my data? That's real time analytics that Oracle provides. I've always seen that the the efficiency of it is, such a beautiful engine, and we always provided some, crisp, real time solutions for the customers. It gives us a comprehensive KPI view, like, the contest. You know, I had the customers ask me, basically, like, oh, can we do it for, the call center business too? Because you've done such a good thing on the payroll side and on the commission side. Because it gives you that edge of real time, and there hit the route at seven in the evening. At eight, you can see that the eight or whenever the data processing happens, if it's that day evening, the next day morning, you can see if you run a context, it shows you the real time rendering of the information. That powerful gamification is, you know, right around the corner because the end to end connectivity being on the same ERP, having the r two and also data connectivity from the driver, whatever systems we use for calculating the driver, actual routes and connected to the trucks, basically. And the final part, the driver mobile experience. You know, Oracle CX and HCM both have a beautiful, the mobile experience, which you can for for the for the mobile, commission commission experience or, you know, how the driver has made to that rate, he can view toward. And all of these provide some cutting edge, you know, benefit to the customer. You know? These are things that value proposition that come out of using this efficient solution. Scarcity. Perfect. So as we kinda wrap right this, this is as Chandra says, we're kinda going through here. The one platform gives you the full visibility into how, how your organization is running. We are able to handle w two ten ninety nine. Workforce, gives you that compliance, making sure you're dispatching appropriately, the transparency into the payments, and the operations, how you know, can I run better routes? Who are my most efficient employees? And then with all the AI that's available and continues to be released, it's it's a complex industry with a lot of, I'm sure, questions from the drivers of how are we getting paid? How do I do x y z? With all the AI coming out? All those questions, you can really reduce your your staffing on the side of answering those questions and allow the system to be able to answer on behalf of the organization. So, overall, it's it's a solution that's growable that we found has been working successfully within the transportation industry. But it's, you know, where do you need to start and where where are you gonna be? So if there's any questions Thanks, Kathy. At this time, we'd like to open it up for questions from the audience. You could submit a question by, putting it in the q and a box located at the right hand side of your screen. Our first question is, does your solution require all these pieces on day one, or can we grow into it? We would say most are growing into. We have a couple that have done this big bang, but it is we'll meet you where you need to be and where those platforms are. If there's, a lot of times when we start the conversation with customers, it might be the desire is from one part of the organization is really excited or has a dire need to start their implementation. So they might be the focus, but as we do the design, we will understand what is the life expectancy of the other areas of do we have another system that is expiring that maybe they're not this year, but they are two years out. And how do we start to understand the design now for them so that we're not having to go back, and redesign anything. But it is not required to have all of them, by any means. Excellent. And the next question is, when would you recommend using Oracle incentive compensation? It's, this is exactly what we always say. Right? Where once we, feel that, you know, the volume is high and you wanted some real time information, you wanted some of these context, you wanted some gamification, efficiency, basically, in the end to end process. And the key thing that I always see is, you're on a payroll. You hired a driver today, and the process is up and running. And he tomorrow, he is running the truck. He expects his payment to be there by the end of the week. It all looks though I'm not ready for it, and that's where we decide, you know what? This is where why we need an efficient end to end system. And this ICM framework provides that backbone. It keeps that capability, real time assignment, and pushing it. At at the same time, even the admins or the analysts have the capability to look through it and say, okay. This is the right amount, and I'm happy. We we we noticed that the admins actually save a lot of time and by using this end to end process. So I would probably call it, like, right around the time when you need to compress the time between hiring a person to paying the payment or he goes on a route to payment. That's when we'd say, let's have the system. Excellent. What if they already have legacy systems they want to keep? Do they have to move everything to Oracle Cloud? No. Nope. That's probably very common. I would say we're still seeing a lot of dispatching systems stay on the legacy, and we real time feed them information between between an HCM system and dispatching. The one the one thing that we talk a lot about of when it is a dispatching system, and there's always a critical piece of information that they just need to update. We talk a lot about about data ownership. Who should own the data? What does the data need to be? Does it need to back feed? So if I if I feed over a bunch of information, the dispatching has a little bit more information or more granular, Do I ever need it back in my HCM system? So it's really breaking down and understanding any of the systems that do stay in place. What is the data that's flowing back? And if there's any additional information that one system has the other, is there any need for, you know, an HCM system and CENTCOMP and your piece system to really understand those additional pieces and make sure we do not have data that can be changed and not back fed and have systems that do not represent each other anymore. So that's, not a problem to keep the Leggett systems. We just talk about the design and the attributes, pretty heavily there. Great. And there are no question other questions at this time. K. You ready to close it out? I think Yes. There are two questions. So I wanna first thank my amazing Argano team. Thank you, Oracle, for joining us as well. If you request any further information about what you learned today, feel free to reach out to us, and, we're happy to go into a deeper dive and show you not only this great solution we come up to, develop to resolve your driver payroll issues, but we could perhaps arrange for a demo using the Oracle solution. So, again, thank you to my Argano team, and, I think we will conclude today's presentation. Thank you for attending and joining. We really appreciate it, and have a great rest of the day. Thank you, David. Thank you, everyone. Thank you.