From Frustration to Automation: Winning with JDE Orchestrator

Transcript:
[...0.1s]You really just have to automate like 80 to 90% of things, cause there's really smart people who could help you deal with the other next 10%, right? Are your JD Edwards users still bogged down by repetitive manual processes?What if there was a way to automate those clicks, eliminate tickets, and start making AI power decisions inside JD?Today [...0.8s] in this episode of not your Grandpa's JD Edwards, I sit down with most shoes out to explore how to identify the best automation opportunities, qualify them for ROI [...0.6s] and unlock serious value using orchestrator. Stick around, this one's going to change how you think about process automation. [...4.7s]Hello everyone, and welcome to not your Grandpa's JD Edwards, the podcast where we explore real practical ways to bring JD Edwards into the future.I'm your host Nate Bushfield, and today I'm excited to be joined by Mo Shoe Shot, VP of advisory and Consulting Services at ERP Suites. How are you doing today, Ma? [...1.3s] You know, Nate, I am doing really well. This is the thing I've been looking the most forward to today.So I'm really excited to talk to, [...0.7s] talk to JDM Works and orchestration and automations and really cool stuff with you. Yeah, of course, I mean, obviously you've been in this space for a long time.Do you mind telling us a little bit about your background, where you came from and what you're doing now?Yeah, yes, I, um, I [...0.8s] grew up here in Cincinnati [...0.4s] in a small suburb, went to Miami University of Ohio, [...0.5s] and right out of college, I got, I got started working at [...0.8s] a local company that does JD Edwards services and got introduced to the JD Edwards world, and found myself absolutely [...0.5s] in love with JD Edwards, the community, the software, and everything. Um, I implemented JD Edwards for about 10 years.Um, I got really blessed with the ability to, with the opportunity to do some new implementations, do some upgrades, [...0.4s] um, got got, got exposed to a lot of different projects across a lot of different industries, and just in a short span was able to get [...0.5s] a, a deep breath of knowledge on JD Edwards.I then actually left the JD Edwards world for a little bit and went to the tech startup world. We're working for a company called stored, where we were creating our own WMS and order management system.Um, I eventually found myself missing and [...0.6s] realizing how amazing JD Edwards is, and decided to make a boomerang back into JD Edwards.That's when I, uh, came back to an old friend of mine, uh you know like, more than the owner of V R V Swedson, [...0.5s] and, uh you know um, he was looking for somebody to help run their consulting practice. And I love Judy Edwards and I love consulting.So here I am. Yeah I mean, I'm sure I speak for everyone when I say we missed you in this space. Obviously, you're a leader in so many different ways when it comes to JD Edwards, so it's great to have you here.Um, but today we're gonna be walking through your automation framework, and today we're gonna be talking about your automation framework, can be talking from identifying great use cases to qualifying them for Ry and finally building orchestrations that drive real results.So let's get into it a little bit. Let's start with what people are feeling right now. Why do you so many JD Edwards users feel stuck doing manual repetitive tasks in 2025? [...1.2s] Um, that's good. Well, it's because, because they're doing manual repetitive tasks in 2025, right?I mean, it's it's, it's wild. You, we live in this world where we have, [...0.7s] you know, these this this, [...1.0s] these users, right, who are used to this world of this new technology coming right from our phones, right into our pockets, right into our faces, where information is essentially being thrown at us, right? And then, um, and, and it's all very, very automated.It's all built because, you know, because of social media, because of the new app ecosystem is all built in a way where it's instantaneous and it's meant to take the burden off the user so we can get content to the user faster. Right?And that's the way the rest of the technological ecosystem is kind of working these days, right?And then you have the same people and then they go to work, you know, so then, you know, they browse their reels at night and they get all this information, they become an expert on, on some things through reels and TikTok, uh, at night and then they go home to work and they're like, man, it takes me a lot of clicks to figure out important information about my business and this really matters.This is how I pay my bills, this is how I pay my mortgage, this is how I feed my family, right? And [...0.4s] the frustration is, is so [...0.5s] common place for users cause you're just like, hey, there's this other world I live in where information is literally thrown at me and I actually have to filter it out.And then I come to work and then there's world where information isn't thrown at me. I have to go through all these extra steps and all this extra pain point pain and all this extra work to get the information that I need to be able to do my job correctly.This dichotomy we live in is really, really frustrating to users. And I understand. I get it, right? I get it. Um. And I think that hope is on the horizon because we have some really great tools now that make it so users don't have to live like that anymore.Yeah, exactly. But like [...0.7s] a little bit more specific about businesses, about people. What type of signals can organizations look for that might indicate there's an [...0.9s] automation opportunity in front of them? [...1.9s]You know, what I always tell people is, [...1.4s] um, look for pain, [...0.6s] honestly, look for pain inside your organization. Look for frustration.Look for areas where you're [...1.0s] feeling like you're lagging behind, even though, [...1.4s] you know, all the sort, all the signs kind of point to the fact that you shouldn't. So I'll give you an example.Right, um you know, right now I'm, I'm going through this really interesting upgrade with a customer, [...0.5s] and [...0.4s] they're on a much older release of JD Edwards, right? Um, [...0.5s] much, much older. They're gonna get to the new 9. 2, [...0.7s] and [...0.4s] they walked me through this really, [...0.6s] uh, interesting example today.And one of the frustrations the user point out, he said, he said it takes so many clicks for me to enter an item, [...0.4s] enter an item information in the Item master.And he's walking through this process, and I'm just sitting here thinking [...0.4s] like, man, I cannot wait to get this guy into 9 dot 2, cause I'm just gonna orchestrate that for them.Like we're literally gonna create a spreadsheet and we're gonna give a button [...0.6s] and he's gonna press some, but he's gonna type it all in, into one scrunchie line.He's gonna press a button and it's gonna automatically go in and enter all the data into JD afterwards, and it's gonna make his life so much easier. And when I walked him through that, he was just like so excited, you know.And I think that's really what the important thing is that like we have to a go seek out the pain where it is users, where we're finding bottlenecks in our processes, where we're finding, [...0.5s] you know, things that are taking too long.And those are opportunity [...0.9s] automation opportunities, right? There's no [...0.7s] substitute for, like you know, some things just take time, right? You know, coming from a a a, [...1.5s] a NSI, right, working as a provider or partner, we know that some things just take time.I cannot [...0.5s] put 20 consultants on a project and make an implementation go by in three months. It's just not possible, right? It just, it will just take the time that it sometimes takes and will take some times a year.Um, and so what users need to do and what it practitioners, a leader need to do is look through those areas in their business where [...0.8s] is the opposite of that, where it's not just taking the time because it has to take the time.It's taking the time because your users are forced to take the time, right? These are date manual data entry processes like entering an item masters, entering in bills and materials entering in branches. What is your turnaround time for when somebody requests an item master record and it gets created in the system?What is your turnaround time for when, [...0.7s] um you know, somebody requested build material change for engineering change order and it gets added into the system? Is it 24, is it 24 hours? Is it 48 hours?What is the acceptable standard for your business? And if that acceptable standard, if, if your gut feeling is telling you that, hey, 48 hours just seems like it's way too long, right? Go dig in, Lean In, find out why that is, [...0.5s] and I can guarantee you will find some optimization opportunities there.Um, and if you need help, Onyx is here to help you find those optimization opportunities if you need them, [...1.0s] yeah, that actually leads in perfectly to this next question. Um, how can it leaders engage with users [...0.6s] to service these inefficiencies in bottlenecks in day to day processes? [...1.1s]Um you know, [...0.8s] it's it's it's, [...0.5s] it's funny, we, we don't live in this world of everyone's and [...0.8s] offices anymore, right? Some people are still hybrid, some people are still fully returned to office.Um, [...0.6s] but in this ever growing remote world that feels [...0.5s] more connected yet disconnected at the same time, I think it's really important to form coalitions.I think it leaders have to form deep coalitions and deep relationships with their business counterparts, form committees, form an excellence committee, form a center of excellence within your, your users, right.Um, make the case to see if you can get everybody in and and, and a committee meeting once a month, and [...0.6s] bring in lunch for everybody and sit down and, and do a brainstorming opportunity on where you're gonna do these things, right?Run a kaisen event, [...0.7s] you know, it's, it's these kinds of things that will, I think, set the it leader of tomorrow apart from the it leader yesterday. Because, [...1.2s] you know, you have to form those, those coalitions with business leaders.Right, um, right, there's always the two flip sides of ID Coin. One is the keep the lights on, and, um you know, the compliance side of things where, hey, we're making sure that all the things are running well, and, um, we're not incorporating too much risk.And then there's the other side of it where they just do cool stuff, you know, and that side is the, it is the consultative side of it.And I think, [...0.4s] um, it leaders really need to embrace that side of ideas, like, hey, how do we go out and find what kind of cool stuff we need to do for our businesses?Well, you go out and find that by, by really [...0.6s] having and inspire your business leaders to have the trust and faith in you and and, and sharing those opportunities with you.You know yeah, of course, I mean, that's, I feel like that's the basis of any businesses building trust, building those relationships that way, you don't have these type of issues coming up as, as much as they typically do.Um, but let's switch gears a little bit, [...0.4s] um, so once we've collected potential [...0.5s] automation use cases, [...0.6s] how do we know which ones are actually worth pursuing? [...5.9s]There's no substitute for good old ry financial model, right, so sometimes you gotta just put pen to paper, and you gotta build out a bit of a financial model, but there are some things that are just, you know, [...0.9s] when it comes to automation, I, I think things tend to fall into a couple different buckets. One is, this is a no brainer, right?I'll give you my favorite no brainer example. I challenge my team with this all the time and I feel like one day I'll get sick of saying it, but I probably never gonna say why are users still running ubes? Like, oh my God, give me a button, [...0.6s] why am I still going to data selection?Just give me a button, let me highlight a row, give me a button, [...0.5s] email me the PDF, right?Better yet, [...0.4s] email me the PDF and attach it [...1.4s] to the order or the P O or whatever it is, and I'm running it on, right? So like, I think there's things like that, that's like a no brainer. Just, just do it. Like if you have users running P O, print like R43, 500, just put a button on the screen, right?Just like as this is a shout out challenge to all Bas who may be listening to this, like [...0.6s] I guarantee you can probably go find 5 areas in your business where you can probably replace the data selection screen with a button, right?Um, and if you can't, you know, we'll, you know, let us know, we'll help you find them, right?Um, there's there's, there's that bucket, which it's like a no brainer, [...0.8s] then there's this bucket, we're like, hey, I know my gut, this is worth it, but I, this is a pretty big automation, so I have to really build out the financial model in the business case to do it.Um, [...0.8s] my go to with that is use your vendors, if your vendors can't build you an ROI, you know, you gotta go go to your partners and use your partners, have your partners build out the ROI with you, right.Get ideas, ask ideas for them, and how they've seen other customers justify and do ROI, right. Um, you don't have to tell us all the information we don't need to know, but I bet you, [...0.6s] your partner can help you do that, right.Um, also on those use cases, it's best if you can form a coalition strong enough where it's not it [...0.4s] that's asking for automation. It's actually the business asking for automation because [...0.6s] it has shown them [...0.5s] how much automation is gonna make their lives better, right? [...1.2s]So that middle bucket and then there's the other bucket where he sometimes the juice is not worth the squeeze.And on those buckets, be [...0.9s] ruthless, right? Like, if you find automation opportunities where, hey, we just think that this juice is not worth the squeeze, [...0.6s] you know um, be be don't, don't waste time pursuing that option or spend a little time finding creatively how you can chip away at that and get the ROI out of some automation, not even if you don't have to automate the whole thing, right?So there's another fallacy there where sometimes people just think that, hey, I have to automate everything. No, you really just have to automate like 80 to 90% of things, cause there's really smart people who could help you deal with the other next 10%.Right, [...0.7s] yeah, [...0.5s] completely right. I mean, [...0.7s] there's so many people out there that can really change your business, and even make a small little change that you'll see a butterfly effect throughout your entire company.So completely agree with that. But what are some of the biggest pitfalls companies run into when they maybe try to automate a little bit too much? [...2.7s] Um, [...1.5s] this is a great question, [...1.5s] uh, [...0.7s] sometimes with, with pitfalls with automation. [...1.5s]So this takes me to this conversation I had today, um, with a really bright [...0.6s] young integration developer, um, an orchestration developer.And this is not somebody who came after the JD Edwards road. You know, he he he, he's learning JD Edwards. Um, now, um, he's really smart guy, [...1.0s] had Learned a ton about orchestrations, um, has gotten really good at them, but isn't familiar with traditional JD Emperor's development frameworks like ube [...0.6s] and business functions, and, and overall, kind of, the architecture of how it all works.Right, [...1.1s] so, um you know, one of the things he said to me was, like, uh you know, I, I know I can do this, but I'm not sure if I should be doing this, right, so not to point his example, he did the right thing, is he he, he found somebody who he trusts, and he asked us questions on if he should be doing things, right.Um, so, so first of all, one of the biggest ways to avoid the pitfall that I'm talking about is, um, talk to someone, find a buddy user, use the Learn J E resources, um, J E tips is a great form. I talk to people on there on all the time, um, post on LinkedIn.There's a community there, right, post on the quest boards, um, [...0.6s] tend to sig, find a buddy, find a buddy you can talk to by JDN where you can bounce ideas off. Because a lot of the pitfalls that I see people get into is, is [...1.7s] incomplete or sometimes not thoroughly thought out design and architecture. [...1.8s]Orchestrations and automations are amazing, but if you design an orchestration incorrectly, or if you design it without the most, without the best thought out architecture, [...1.3s] that automation can [...1.5s] quickly become a major pain in your body, right, because it's crashing all the time.Things are getting stuck, [...0.5s] you know, orders are getting stuck in in in the in the, in the system that they're coming from. And now people are complaining, right, so now can start to become a really big pain, uh, pain in your butt.So [...1.5s] having the right design and architecture of an animation that takes into account [...0.4s] all the factors, your workflow, your users, the quality of your data, [...0.6s] um you know, all that context [...0.6s] and starts to put together.Okay you know, how does it need to be architected to be performance, how does it need to be architected to be redundant, how does it need to be architected to be communicated?Right, [...0.6s] um, I, I had this really great in focus presentation I did for my learnings called characteristics of a, of an integration, you know, get an integration.Yeah, I'm gonna saucing myself out. Um you know um, so, you know, the point of is that, you know, integrations, great integrations, um, need to be communicative, they need to be scalable, they need to be timely, they need to be responsive, right, [...0.6s] um, and, and you need to make sure that automations are the same way they're, they're doing all these things.A lot of times people are just like, oh, let me just automate, let me build something out there. And next thing, you know, you didn't consider all those things in a design, and you've got a bigger problem on your hands. And that's, I think one of the pitfalls that people need to watch out for.And then going back to my point of [...1.0s] having a buddy, having someone you talk to, someone you trust, right? A friend, a mentor, [...0.4s] a partner, someone you can just pick up the phone and say, hey, I'm thinking about doing an orchestration that does this.Have you ever tried that before? Can I show you on my screen? And can you give me some thoughts on how that works or what you think about it? And and, and that will help because sometimes just, just balancing your ideas of how you design your orchestration against somebody makes a huge difference.Yeah, of course, I mean that kind of, [...0.6s] that kind of thinking is more of a long term strategic thought, more than, oh, this is something that I need quick.Maybe this is a quick win, but once you start to build out a certain framework or certain automations that can really just mess up your business and maybe even set you back instead of [...0.6s] propelling you forward, which is what you're trying to do with all these automations. So completely understand that. But [...0.6s] let's shift [...0.4s] again.I know I'm sorry, I keep making you shift after we, I feel like we're having a great conversations about these stuff, but let's shift a little bit more to something really hands on [...0.5s] from your session.It's clear that JD Edwards Orchestrator is way more than a nice to have, you know, it's an automation engine that can modernize entire business processes.Can you, I know you have, but can you walk through maybe a few real examples of high impact orchestrations that companies are using today? [...1.4s] Oh, yeah, yeah, yeah um, [...0.7s] orchestrator honestly has been, um, a game changer, you know.And I was recently talking to somebody at Oracle and talking about the orchestrator.And, and, you know, even they said something mean, like, I don't think anybody really realized [...0.4s] just what exactly this thing had the potential of being. And I think many of us feel that way, right? Like I remember when [...0.7s] IoT Orchestrator came out in 9.1 and the tail end of 9. 1, you're like, what is this IoT Orchestrator thing? You know, I'm like, oh, just for IoT devices, that's what it's gonna be used for. Then [...0.4s] it started becoming like in 9.2. 3, it started becoming way more prominent. You're like, okay, I can do some really cool stuff with this. And, you know, when you hit like 9. 2, 4, 9. 2, 5, you're like, we are flying. You know.So I've listened, I'm, you know, over the history of building this, I've got some customers that have built some really cool orchestration ones that we've built for them, ones we built with them, [...0.4s] um, [...0.9s] and ones that they've built themselves.Once you've taught them the framework and, and the landscape of how you build orchestrations, right.So [...1.0s] I think some of my favorite ones [...3.2s] trying to think back to, like, one of, some of my favorite ones, [...0.4s] this one orchestration I built, um, where [...0.5s] it was, it was really simple, but I love the concept of it, cause you just think about this back in like 2,020, maybe.Right, the concept of the connected, [...0.9s] the intelligent enterprise was always there, [...0.7s] but, you know, I don't think it has been realized, right, not, not the way that we're starting to see it be realized now [...0.8s] by this customer. And we did this integration with this with the orchestrations, with them.And, um, and it wasn't what the orchestration did when it worked, that was cool. That was pretty simple and just picked up a file and process the file and there's some data inside of JD Edwards and made, you know, users lives very easy.What was I think really cool about it is when the integration broke [...0.9s] and what it did.So what we did was we had [...0.5s] essentially [...0.4s] an exception path where if the integration broke and didn't work, instead it created a service desk ticket [...0.7s] and it let it know and they could reprocess the integration transactions in the morning before the accounting people got in. And it was as if the error never happened, right?And, you know, I think that then we probably didn't realize how, [...0.6s] you know, [...0.6s] well that was [...0.6s] because really that is the intelligent enterprise.If you think about it is like, you know, I've got processes that run and problems that happen, and it's not that you are, you need to avoid problems cause you always have problems, right?Is that when the problems happen, you have systems and automations in place [...0.6s] that course correct without human involvement. You know. And I think that's what was really cool for me. It was kind of like a mind, it's kind of like a, uh uh like a shift in mentality for me, right?Um, I think another cool orchestration we have, um, [...0.6s] we've done is, [...0.5s] you know, a customer [...0.5s] kind of came to us and was like, hey, [...0.5s] I'm being told you can't really enter a configured sales order through an orchestration.And for those of you who don't know me or or or, or do or haven't had the chance to, there's very few things in this world and get me just sort of jazzed up, like hearing you can't do this [...0.5s] and orchestrator at the same time ever.Let's go find out, let's go prove it, let's go prove it, [...0.9s] you know, let's go ram our heads against this problem, the brick wall and see how we can either get through it, jump above it and figure it out.So, [...0.5s] um, so long behold, this customer says it's us. And we're like, alright, cool, let's go figure this out.And within I think a week and a half, we had a forklift, you know, the standard JD Edwards forklift configurator [...0.6s] sandbox data. We had a forklift order going into JD Edwards. After about two weeks, we figured out how to change out the, sorry, two weeks from the beginning.So another about half week we figured out how to change the options. Um, and then after about a month of plugging away at this, we actually started learning and building how do you actually make the, the whole thing dynamics, the configuration changes, like new segments and stuff get added.How do you actually make the, the whole thing [...0.4s] adapt to changing configuration in segments? So it took a while, um, but like I said, it was something that was interesting or customers like, hey, I don't think this is possible.And we were like, let's go figure out, let's go prove it if it's not possible or not. So, [...0.6s] um, again, just another one where it was like a shift in mentality for me, where I was like, yeah yeah, there's, there's a lot of things that are possible with this, with the soul.Yeah, and honestly, [...0.7s] knowing you, [...0.4s] you took that as a challenge, and I'm sure that you worked your butt off to really get across the finish line.So [...0.5s] honestly, I'm not surprised that, not surprised at all that you were able to accomplish it at all. And, and, like, the coolest thing, like the little moment of victory for me, so like, we're banging our head against the wall, right?I had, I had a functional consultant who was very technical, and I had a developer, and those two were just like banging their heads against. They were like, figure out it's not working though, it's not working.I'm just like pushing, like yeah, you guys go, come on, guys, we can figure it out. We can do it. Let's go. I know it's gonna be possible, right?Like, let's go, let's try this. I'm in the sessions of working with them [...0.6s] and then all of a sudden, you know, I, I do what I normally do when, when resources and technical people are frustrated, right? I say, hey, let's everyone just take a break.Let's all walk away. So like, right [...0.8s] 30 minutes an hour, walk away. Let's go hang out with our kids or play with our cats or go take a walk, go lift, go, go to your gym, go around, just walk away from them. [...1.2s] And that's what we did. We walked away, and of course, I say that to people, but I never walk away.So now I'm hanging at this and then, you know, I take over and I'm, I'm developing it. And while my developer, my functional consultant, you're actually taking a bit of a break, I managed to figure it out. And then they came back and I'm just like, guys, I got it.I showed and I showed to them and they're just like, I think they were annoyed, first of all by me because they're like, of course it had to be him. Um, but I think more than that, they were just like, hell, yeah, let's do this right. Cause they were so close, they were so close, like, 99% of the way there.Yeah, and honestly, I'm sure that they love taking that break held. There's a lot of data that suggest that if people walk away from a problem, like, that will actually come up with new ideas and new ways to fix it, and new ways to come about it. And you didn't even give them time to do that here, like, no, I got it, guys.Don't you worry. It's a your your, your boss will just figure out the 1% that you were missing, and then come in and take all the glory from you. No, no, those two are absolutely amazing. They did all, they did literally all the work and, and we could not have done it without them.Yeah, that's awesome. Uh, but to bring up your session again, this, I read this phrase and I honestly, I started cracking up [...1.0s] the read my lips, no more data selection.That's so you number one, haha. So you, [...0.5s] but how exactly does orchestration replace traditional ube selection screens and what does that do for end users? You know um, [...0.5s] I've used that slide [...0.5s] in at least more conferences [...0.6s] and I'm gonna say my George H W.Bush impression is getting way better every time I deliver this, you know um, [...1.0s] no, so, so, you know, I think, [...0.5s] I think there's like you know, go back to what I was saying, like these, these automations, they follow these different buckets, right?And one of those buckets is this no brainer bucket where it's just worth it. And so I like to call these, like these quality of life [...1.0s] improvements and [...0.6s] I think they're so pervasive throughout the JDM world.These are things that are so [...0.6s] simple we actually don't see them when they're right in front of our eyes, right? Um. I'll give you an example, you know, I had a [...0.6s] consultant who, [...0.7s] um, who created a row exit using a form extension for a customer, right?And, you know, just for the first time, this consultant created a form extension and they wanted to show me and they were kind of like proud of their work.And, [...0.5s] you know um, and, [...0.5s] you know, they, they did this whole thing and they did, did then it's a row exit, save the, [...0.5s] the user a click already, right?It's already saved them a click because now we're adding a new row exit rather than the user having to go back out to the E1 page and click something else, [...0.7s] you know.So [...0.8s] the controller shows this to me and, you know, first, like, I'm looking at it and then they're not, they're not seeing the excitement on my face, right, cause that's what, that's what [...0.6s] she's looking for.And, and I'm just like, well, you know, I was like, why didn't you just open that up in a pop up form rather than [...0.4s] a new form so the user doesn't have to exit the current application? [...1.3s]And, you know, immediately you can tell, again, you know, the recurring theme here. My consultant is probably don't like working for me or working with me, right? Um.But I think the recurring theme was just like, [...0.5s] I hate that you thought of that, but that is [...0.5s] an amazing idea because it just saves the user one additional click, right?Anytime you move from one screen to the next screen, even if the data you're seeing is related, [...0.9s] it's, there's a focus switching cop that we don't respect enough. And [...1.4s] I think if you can use things like the pop up form and it doesn't work in every case, right? It works in some cases, but it doesn't work in every case.But when it does, it's a really elegant solution [...0.6s] to just doing a small pop up, [...0.9s] having the user see the information they need, do the actions they need to close the pop up and remain where they are.So to them, it doesn't feel like I went to a whole different screen, I went to a whole different application. I did all this stuff, right?So there, I think there's, he's very, [...0.5s] you know, [...1.1s] small elegant quality of life improvement that [...0.5s] have the potential for us to just really drastically improve the user experience in JD Edwards.And I think that's really where the whole read my lips, [...0.6s] um, no data, no more data selection comes from, and I won't, I'll save [...0.9s] my, my H W impression. Come see me in blueprint if you wanna see the impression. Um, [...1.1s] is, is that [...0.8s] it was always meant to be a challenge to my team, right?It was always meant to be a challenge to say, [...0.8s] if you're, if you're upgrading or implementing Danny Edwards for a customer, right?And it's meant to be challenged to everyone, honestly, [...0.6s] where can you remove those things that are unnecessary, you know, [...0.5s] and I think orchestrator and the Udo framework gives us tools to make it so elegant, [...0.8s] right?They take the system that users have described as [...0.7s] to me, you know, people said, oh, it's so clunky and I take so many clicks and do all these screens and I really don't like it, you know, to, when you design something that's so elegant and the information is right there in front of the users, right? But really just changes the way they think about it, right?And, and we're trying to build this new generation of people who love JD Edwards as much as, you know, a lot of us did. And the only way I think we're gonna do that is by showing them [...0.6s] how we get to make this a very modern, very user experienced focus system, right?And that's the whole premise by that that that, [...0.7s] that bit, [...1.7s] it's still one of my favorite bits. I know, [...0.5s] I know you use it a lot, well, not a lot, but throughout, throughout time, I know you have used it.I'm sure we might even bring this up during the AI week that I know we're putting on here soon at the [...0.5s] end of April, so [...0.9s] very excited about it. Can't wait. But if you're hearing this [...0.8s] and you're thinking we've got processes that need this yesterday, don't wait. Visit ERP.Suites. Com or connect with Mo in the team. Get started with us, whether it's a quick orchestration win or roadmap towards AI readiness, they'll help you prioritize and deliver real value. But that's a wrap.Thank you again, Mo. Huge shout out to you. I know you have a busy schedule. I know it was a little bit hard for us to get onto this, but [...0.4s] this is a great episode of not your Grandpa's JD Edwards.If you liked what you heard, subscribe, leave a review, share with colleague who's tired of clicking through data selection screens until next time, keep automating, keep modernizing, and keep pushing JDE [...0.5s] forward. Catch you later. [...17.1s]