Name: Transforming Public Sector with Workday Extend
Uploaded: 2025-05-21T19:16:05.418Z
Duration: 1 h 2 min 4 s
Description: Transforming Public Sector with Workday Extend

Transcript for "Transforming Public Sector with Workday Extend": Welcome, everyone. Thanks for joining us today. We will dive right into our content and get started with our webinar today. So today's webinar is entitled Transforming Public Sector with Workday Extend. Pretty excited about the content we have to share with you all today, and we really appreciate everyone joining us. Couple of housekeeping notes before we dive in, our product statement here. We don't plan to show any future capabilities today, but if we do, we will certainly mention it. And, please obviously make any purchasing decisions based off of current functionality. With that said, a couple of notes for today. We are recording the webinar, and everyone who registered for this will be able to come back and watch it again. You'll also get an email with a link to the recording. We are muting all of the participants today, and please submit any and all questions through the q and a tab on your screen. We welcome your questions and your comments. Please feel free to send all the questions our way. We'll do our best to get all of them answered. And if we don't, we'll be sure to follow-up with you to get those answered. Quickly, I wanna introduce our presenters today. We've got a great cast of of folks. So my name is Joe Lamastra. I'm an enterprise I'm sorry. I'm an extend product specialist with Workday. With me today is my colleague, Griffin Anderson. Griffin is a principal enterprise architect, and then the crew from Accenture. Our friends at Accenture are joining us today. Bharath, Sid, and Saron are all here to talk about all the great and what I think is really cool stuff they're doing at Accenture with extend, and they're gonna show us a couple of really, really cool demos. So that's the team. I'm sure they'll introduce themselves as they begin speaking. But a quick agenda for today. So we're gonna start off the meeting today with a Extend overview. Griffin's gonna kinda explain Extend for those of you maybe you haven't seen it before or don't have a % confidence in it. And then he'll do a few demos to kinda get you up to speed on what extend looks like. I'll come back and do some, use cases, talk about how accounts in the public sector are utilizing work they extend, and then we'll turn it over to Accenture where they'll do both a public sector overview and talk about kind of what they're doing as well as show a couple of demos, including the the shift bidding app that they've developed. So, we may or may not have time at the end for q and a, but like I said, please enter all of your q and a into the q and a section, and we will do our best to get all of those questions answered for you. So, yeah, I think with that, we will turn it over to Griffin. Perfect. Thanks, Joe. And hi, everyone. My name is Griffin Anderson. And as Joe said, I'm an enterprise architect here at Workday. I've been here about eight years and excited to tell you a little bit about Workday Extend today. So from a high level, when we think about extend, extend is really about opening up the Workday platform to our customers so they can build their own apps, their own extensions using the same tools that we use to deliver the core Workday application. So when we think about what an extend app is, when I say we open up that platform, I think of the core building blocks of Workday as business objects, business processes, security domains. With Extend, we're enabling you to create your own business objects, your own business process, your business processes, your own security domain. So those core building blocks that we're using to deliver our functionality are now opened up to extend customers to create their own extensions and apps. Just like the rest of Workday, it has the same look and feel. It's exposed on desktop, on mobile. And these applications that our customers are building can interact with third party systems through, through open APIs as well, as well as interacting with the rest of Workday. So complementing things like Prism, Journeys, our Illuminate AI strategy, all interwoven into extend as well. Just a little bit of extend by the numbers. So this product's been around, started with early adopters back in 02/2018. I was fortunate enough to get to start poking around in the product back then, and, it's just amazing to see the growth between then and and how the product is today. Just tremendous growth and really exciting, maturity of the product as well as growth within customers. So it went generally available in 2020, which was interesting timing. We had customers building all sorts of apps to, pivot during the pandemic, whether that was vaccine management apps or PPE request apps. So being able to agilely respond to that, tremendous event really benefited our extend customers. And then you could just see some of the overall growth here. So we're to a point now where we have over a thousand extend customers, over 2,000 apps. So, even I can do that math and realize that customers are are building more than one app. They're getting value out of the extend platform. And then we have a developer community of over 9,000 developers. I think Joe's gonna, talk about our developer, event that's coming up, not too long. So really exciting growth on this platform. In addition to extend, there's a couple flavors of extend. And with extend professional, we are infusing AI and ML into that product in a number of ways. Wanna share a little bit about that, and then we'll jump into the demo. So there's code three main components of AI that are infused into that extend professional offering. The first is what we call our AI gateway. I'll talk about that in a moment. But that's a set of Workday APIs that you can tap into. Second, you can tap into a d AWS. So they have a number of AI services that extend from customers can leverage within their apps. And then our developer Copilot, just like it sounds, is a Copilot that's riding alongside developers and assisting them in that coding and development process. So, again, the AI gateway is tapping into Workday AI APIs. So these are, Workday delivered APIs that are exposed to extend pro customers, and we're gonna look at some of these in the demo. So things like document intelligence, being able to pull and extract information out of documents, tapping into the Workday skills cloud. We know Workday's been investing in skills for quite some time, and you can infuse that into your apps. Things like ML forecasting, sentiment analysis. And this is really just the first wave of these, capabilities that are exposed through AI gateway. There's a whole another set that is, coming very soon. On the AWS side, similar story, but we're tapping into AWS AI offerings. So now you can infuse your apps with AI through the offerings of AWS. So things like translate. They have a translate service. So if you need to translate, into different languages, AWS has an AI service for that, and you can infuse that into your apps. Recognition, so taking pictures and being able to kind of recognize what's happening in those different images, and we'll see how that could look in a in an app in just a moment. And then developer Copilot, I'm gonna do a demo of this. I won't spend a ton of time here, but did wanna kinda leave this slide as an artifact as we're gonna share this deck with everyone on the call. So let's get into it and show a a quick couple of demos here. So I'm gonna start out with that AI gateway that we talked about. So, again, that's exposing Workday APIs into extend apps. And I'm gonna open up a very simple app here, and this is what we call a app to help you explore this capability. When we turn it over to Accenture in a few minutes here, they're gonna talk about how they're leveraging these, this AI gateway to kind of, bolster the apps that they're creating. This is just, again, a really simple app showing the capabilities. So what we can do here, there's a number of parsers that are available within this document intelligence service within the AI gateway. So we can do things like, look at an image and extract the text. So if I upload an image here, I've got just a simple badge that we're gonna expose to this API, and I can run that. It's gonna scan that badge and pull out any text from that badge. So interesting, you know, good response there. That might be beneficial in an app that I'm building, but it's a pretty raw response. Right? It's just grabbing all that information right out of that badge. Let's do another one with a little bit more purpose behind it. So let's look at our resume parser. And here, we're gonna upload our resume, obviously. We'll grab that, and then we're gonna align this to a job profile. So let's look at our director of HR operations here. And what this is gonna do is not only parse that resume and extract information that we can use within our extend application, but it's also gonna infer skills and then leverage those inferred skills to compare to that job profile. So here we get a really nice skills gap analysis where we can see, okay, we've extracted skills from that resume. We've also extracted the core information. Right? Who is this applicant, some demographic information. But where do their skills align? So we've got, you know, skill, alignment to that job profile. We have some, extra skills, so skills where they have, talent beyond what's required in that profile, but also a deficiency, right, where we're missing some skills, so maybe not the best fit there. So, again, just a high level example of playing around with that document intelligent app and understanding how it can pull information out, whether that's raw text or things like inferring skills from a resume. There's a, expense, parser as well. So just giving you a feel for that kind of raw capability here. And then, again, Accenture is gonna talk in a moment about how they're leveraging this in their app road map. Let's look at another quick example here. So we talked about the AWS, services that we can tap into. So what might that look like? Well, here's an example of a badge, to do tasks that's presented to this user as part of onboarding. So one thing to call out here, the look and feel in these extend apps is just like the rest of Workday. It's very hard to see that line between core Workday and something like this that's created and extend, and that's obviously intentional. That's a value proposition for extend. So what we're seeing here is as part of that onboarding process, this user has been presented with a to do task to create their badge. Let me let this video run for a moment here, and they're gonna pop that open and get some instruction around what they need to do to to create this badge. So we basically have an auto approval if this photo meets all the requirements. You can see some of the requirements bulleted there, face visible, just one person in the photo, good quality and not blurry. So what we're gonna do here with this extend app is as this user uploads their photo, it's gonna call that AWS AI service behind the scenes and check on these different capabilities here. So let me advance this video just a little bit here. So we've got a a nice picture with the sunglasses. And when we call that AWS service, it recognizes that the user's wearing sunglasses in that picture. So maybe great for match.com, but less good for our badge photos. So they can either proceed and try and get a manual approval or have that rejected. Another example here, better, no sunglasses, but just calling out that that this, the user isn't smiling here. They can proceed, but we'd really love to have a picture of them smiling. And then the last picture here checks all the boxes, and we're okay to proceed with the badge. So just one kind of fun example of how we can, leverage those Amazon Web Services, AI services behind the scenes and infuse those into an extend application. So let's talk for a moment about how we get to that point, the app offering experience. So what we're looking at here is what we call the developer side or dev side. And I think about this as similar to Workday community, but just for our extend customers, our developer community. It's a new persona, of Workday customers, and and, really, they have different needs, so we've created this developer site to cater to them. And there's all sorts of things we can do or developers can do within this dev site. We've got API explorers. We've got a forum. All our documentation is here. We have reference apps. So these reference apps are really useful when you're thinking about, okay. I wanna build an app that does these things. You can use these reference apps to understand how you might build that, and we can see different capabilities here. So document intelligence. Right? That's the app that I was just looking at. So if you wanna play around with that service within the AI gateway, great. We have a reference app that you can download in your environment, see the code, play around with that, and understand how you might leverage that that document intelligence within your applications. And You can see you can filter these down. So if you're looking for an app that includes orchestrations, right, you can filter on that and see how those work within this reference app. Or if we wanna look at those pro features like the AI gateway or AWS integration, we can filter those reference apps. So really powerful way to kinda get started with extend. This dev site is also where we're actually offering our apps. So we're we're creating apps, for the Workday application. So I've got a simple app here that I'm gonna pop open. This is a employee nomination app. So think we're nominating an employee for something, an award, who knows, but some kind of employee nomination that we wanna capture within Workday. Very HR adjacent and a perfect use case for Xfend. So one thing to call out here in what we call the app builder, this is where we're actually building out our apps. And, you can see on the left side here, when I talked earlier about exposing those core building blocks, we have business objects. We've created an object for nomination. We don't have a business process associated with this yet, but as we capture that nomination, we might wanna have that flow through a business process. Right? And that's gonna be a totally stand alone business process, something that's never been, available in Workday until we release it then. And then we have our security domain. Right? So exposing these core building blocks of the Workday application to our customers here. So let's look at a few of these things. If I look at my nominations object here, this is we talked about the growth of Extend and really moving to a low code platform. It's been really fun to watch as I mentioned, but very much low code. Right? So if I wanna add a new field to this object, it's all done through UI. I can add a field here, grab a field or call it, a field of manager. Maybe we wanna capture that in this. And I've simply added that through clicking around in the app developer here. Now what's really cool is behind the scenes, Extend is creating the code. Right? So there's still JSON that's being generated behind the scenes. Here's all that that code that was created when I added that, but I did it all through UI. So it's doing that for me behind the scenes. So let's go look at the components of our app here. We've got a home page. Right? And we can see sort of the building blocks here. So, again, drag and drop components. But let's look at what this actually looks like. I can open up my app preview here. Let me connect to my tenant real quick. There we go. Bear with me one moment. Okay. So once I'm connected to a tenant, I get a nice preview. So I can actually see the components of this home page. So in this case, we have two cards, one to create a nomination, and then we can view nominations. If I want to create new, components within this page, I can do it all here in the the edit view. I can drag these things around. So maybe I want to view ahead of the create card. I can just drag that up here, refact refresh my page, and see that change. Right? So very much a low code environment. But, again, behind the scenes, all that code is being created for me. So really, really powerful, really easy to use this platform. And then we take that a step further. So we've got this home page, and we've started to get the building blocks of an application here to create these nominations. But I don't have anything that happens when when I press this button yet. I just sort of started, building the container for that. So let's use our developer Copilot to actually create a page to capture these nominations when we click that button. So I'm gonna invoke the Copilot up here. And just like many Copilots, I can just enter a prompt so I can tell this Copilot what I'm trying to do, or I can leverage the prompt library here. So this is, the Copilot being aware of what I've already done. So I've got a business object for nominations. Now I wanna create a page to capture those nominations. So I can go ahead and generate that. Copilot's gonna analyze that request, take a moment to generate those components. So now it's gonna come back with, exactly what I asked for here, leveraging that business object that I've created. So there we go. So I didn't have to create any of this code. I didn't have to know how to to operate that. And if we, again, toggle over to our app preview, we can see what that's gonna look like. So really, really valuable. Not even drag and drop. I'm just leveraging AI here to help me to ride along in this development process. And I can continue to iterate on this. So, maybe I wanna say, yes. I wanna create this page with the employee name at the top. Right? So I can continue to iterate with this Copilot, adjust that page, and, again, it's creating all that. Oops. Sorry about that. Little error there. But it's generating all the, the, code and everything that goes along with that application. And then I can add that to my app. So really, really powerful. Again, going beyond just drag and drop and taking that to an area where we can leverage AI to, to assist us in creating those types of pages. So, Joe Lamastra, let me pass it back over to you, and I think you're gonna take us through some use cases for the public sector here. Yeah. Real quick, I'd like to just talk a little bit about some of our customers and what we've seen them build, with the cope with I'm sorry, with the extend tool. So just some some use cases here from the public sector. The first one is a dependent scholarship program. So this company, this entity wanted to offer its employees dependence scholarships, and so they built this app, to sort of basically, you know, automate a manual paper process. So the approvals, the business process, all of that was done, in extend as opposed to Excel as you see there. So, the next one, another government entity was as just another screenshot for the dependent scholarship program. Happy to to share the slides with you on on these as well. The next one is, basically a leave donation. So we've heard this quite a bit in the public sector that, different entities, allow employees to pool excess leave or excess PTO that they're not using, donating that to a pool, and then that can actually be utilized by other employees who maybe are out of PTO or had an emergency and needed additional PTO. So that's one we've seen quite a few times. It's a pretty common design pattern. The last two are from a power company that we have as a customer. Oh, sorry. One I I skipped one. The part time study program, again, kind of tuition reimbursement related, that kind of thing. So, again, manual processes in the in the past, fill out this paper application, send it via interoffice or, you know, snail mail, and then we get that and we process it. Now we do obviously, it's all electronic and all built in within Workday. And then the power company I was talking about, they've built a couple of apps so far. They've got a time entry app that they built. The the existing time tracking screens within Workday were not something that met their needs, and so they decided they were gonna change up how they did this, and build new time tracking screens, still calling the same time tracking APIs and tracking all of the time through payroll just like Workday does in a standard way. But in this particular case, they, needed a different kind of screen to do that. And then the last one they built, was a grievance app. And this is another pretty common design pattern. Right? If an employee has a grievance that they'd like to submit, there's obviously lots of documentation and process that goes with that. And so they were able to automate all of that capability within this grievance app. So one thing I'll point out, there's four or five different use cases there for public sector. None of those are actually public sector specific. They really are more universal in nature. So just giving you a feel for what some of our customers have done. And with that, I'll I'll turn it over to you, Bharath, to talk about what Accenture's doing. Hey there. My name is Bharath Srinivas. I am the CTO for our Workday business, here at Accenture, and I'm super excited to be here. I'm gonna share a little bit about who we are before I hand it over to, our two team members to take us through some awesome demos. Let's go to the next slide. Just as a a a little bit of a recap to what Griffin was sharing, we have been, with Workday and Workday Extend from the beginning. From the announcement that happened in 2017 to working on some of the early projects with the Workday team, in 2018, we have been both a design partner and an implementation partner. Our focus in the in the development of our, people and working with our clients has been focused, across multiple industries. We have been working on building internal apps ourselves and also working with industries, from the public sector to many of the commercial, clients as well, including nonprofit, organizations. We were one of the first organizations to prime and extend project, and that goes back to why we believe, in the extend as a product and the evolution of what the product has been since the beginning to where it is headed in the future as well. And throughout this journey, for each of the client projects that we have done, we've also created a robust catalog of these extend apps that we often use in conversations with clients and also use as templates to help our clients get to the, go live much faster and much, quicker. But also think about all of the different ways that clients are using extend, working alongside with us. We presented at many of these conferences as well, but the key thing that I'll just, kind of, like, you know, end with is, a lot of our solutions are at least the ones that we believe are good, multi ones. We've highlighted through the work in marketplace and so are part of the AI marketplace, you know, to see how we can take the innovation that we do as a team and working alongside with our internal Accenture teams that are using extend, because we use Workday internally for all of Accenture's meetings from an HCM perspective and take the combination of all of those, to be made available through marketplace to all of our clients. Let's go to the next slide. So here's a snapshot of, some of those apps that I was referencing. And, while these apps look both generic, but also are specific in certain cases for industries, I can, I can kinda be gonna say from my own memory, the labor cost distribution is one that we built out with the state organization? Same thing, with the fellowship as well that we built out with another government organization. We also have a security request app that we built out with a university and a handful of those that we've, tested and also used in multiple public sector organizations. And this catalog continues to grow and I'm super proud of that one. So with all of this said, I'm gonna now hand it over to Sid, to take us through one of these kind of marquee solutions that we wanted to demonstrate, for all of you today. Sid? Thanks, Bharath. So let me just skip to the next slide. So one of the extend applications that we have recently built is, around the shift bidding, by preference. You know? So where we are giving the employees the flexibility to choose their workshops for the upcoming schedule. And this was primarily needed for, like, Department of Public Safety's at, several of our customers, whether it's state or the locals. You know, there there was just a heavy demand around, the shift billing process, which is kind of a cycle twice a year, once a year, depending upon the type of organization, that that you are. Just before we dive into the application, I just wanna take a brief moment here to do the use case analysis on why we built this application. So Workday does deliver a shift bidding process, in their latest release. So what is a true difference between, what Workday is delivering versus what we have? So this kind of chart kind of represents, you know, what is in Workday. Like, the OpenShift board is out there in Workday where you can see what the OpenShift are that are available for employees to bid. There's OpenShift bidding out there. However, there's a a a manual selection process. There isn't, like, an automation, that will kind of evaluate, employees, their preferences. It does not allow you to enter the preferences as an employee either. So there's just a lot of differences between, what Workday's standard, shift bidding processes versus, why we why this extended application kind of evolved. Just to walk you through the life cycle of the shift bidding by preference, is where, what we are doing is we are giving some administrators of the departments, or even, some locations. You know, they they can just set up a bidding period, and they can just say that from January 1 through January 15, you know, I'm gonna open up the bidding period for the employees of my department where the employees would then get be notified of when that period is kind of closed or open. Then the employees will just go in and then they will enter their preferences in in the order that they would like to work in that upcoming time period, you know, like next six months or one year, like I said earlier. Then once the preferences are locked in, you could be changing your preferences throughout the, bidding period until it is closed. So once it is closed, the the preferences are all, are kind of locked in. And then there is a rule based evaluation, you know, that that the system is gonna evaluate based upon, you know, your seniority dates, you know, your prior shifts, your certifications, your credentials. So there's just a lot of rules that will govern on who will actually win win the bid for that particular schedule. And then the the system is gonna review or present a dashboard to the administrators, to that the way they can review and adjust any of the suggestions that were made by the engine, before finally publishing the schedule to the employees. So that is kind of the overall flow of the application. Again, another slide about that, but we just talked about with, you know, again, we're creating the billing periods, letting the employees put their preferences in, evaluating it through the engines, and then assigning the shifts. So kind of a four step process, but very transparent to employees that and the administrators on what is really happening in those ship bidding processes. So with that, let me just, go right into the tenant, and we shall take a look. So here I am in, one of the Accenture's, extended tenants, that Griffin has been talking about. I did have multiple different tenants that are available for workday extend. This is one dashboard for Logan right here where she has all these custom tasks that are available to her. So one of the first tasks that she does is, you know, she picks up a a bidding period, for an organization. And then these organizations down here, these these are configurable. These could be anything of your choice. You wanna do department, but you wanna do a location or a supervisory organization or a call center or a department. There is just so much of flexibility in the excellent application that that this is this will allow you to, get get the, define the ship bidding periods based upon the organizations. So for our purpose today, we are just gonna go department of, state police, and then, we will define a period that the employees can use these candidates to bid their preferences on the shifts. Let's just pick those. And then as an administrator, I can also define what is the meaning that I will need, on on those shifts. So I can just define, this one, seems to be a 4PM to 12PM. I know my, my needs are not too too many at that location where I'm defining it. 8AM to 4PM, that's where I need the peak, so I'll just define ten. And then I have a 12AM to 8AM. I do not really have a a a greater need in there. So, five, ten, and four, and I will just click on okay down here. So at this time, because it was 05:21, so we kind of opened up the bit. What the system is doing is it's sending out a notification to the employees of that department or that location where, the the, the employees can see their, choices. So for example, like, right here, now I'm kind of locked in as, mister Coke. And then there's a ship bidding open up for them that and then, again, this notification is also gonna go into their email boxes. The text is all configurable, you know, whatever you would like to show in there. But, primarily, what we are saying is that there's a bidding period that is open for you. It ends on 05:30, so you really have these ten days to put in your preferences. And if you didn't do that, you know, system's gonna just take the, consider you as last in the queue and then, you know, apply, the the the rules on on you as if you were the last. And then we also kind of, you know, show that when does the next work schedule within begin. That's July 7. And some of the key dates where we're saying, 05:30 is the close of the bidding cycle. 06:13 is when we communicate the published schedules to the workers. And then seven seven would be the new schedule, when it takes effect. So then let's take a look at, how the employees view looks like. And here are the three schedules that we had put in for mister Colt, change department. So now depending upon what, he wants to do, he could just put in the preferences. And mind you that you have to put in, the preferences for everything. That's a required field. So you can just say, oh, you know what? I just wanna work, twelve to eight, at night. I like working at nights. So, you know, like, 01:00 would be totally oh, I'm sorry. That that would be number one choice that I wanna put in the system. And then if I somehow did not get it, then, number two choice would be 8AM to 4PM. So I would go with that notion, and then I will submit my preferences. And, again, remember that we, these preferences are editable throughout that window of two weeks that that we opened up, and then employees are, are allowed to go in into their the screen and then make their preference updates. So let's just go back into, so that was the employee experience. Let's just go back into, the the administrator. So now, what the next task is that the everything is kind of done. The period is, let's say, locked. There's a job that will run behind the scene. It will calculate all the scores for the employees depending upon what their preferences were and apply all the rules, like like I said earlier. So it could be based upon your seniority. It could be based upon your prior bids. It could be based upon the location. It could be based upon the demand. So there's just a lot of calculation that the engine is doing, and then it's it's, awarding these, scores behind the scene to each employee. And this is kind of a dashboard that is shown to the administrator, where it will it will suggest that, Janice, for example, in this case, wins the the ship b. Bettina, who happens to be another person who had paid for, similar shifts, but she lost the bill and she only gets shift a. So that that's the the kind of, dashboard that the system is producing. Once this is all done, then another ship job runs behind the scene where all the adjustments are done. And then finally, the work schedule assignments are then finally pushed back into what they're using the APIs. And then that's where you can see that mister Johannes, this person is now because he won the the bid for for to work a shift. Mhmm. And that's July 7. And that's where, you know, we are giving you that that particular bid. So with that, this was the shift bidding demo. There's just a lot to it. You know, there are a lot of moving pieces and a lot of connections, but this is what you'll see based upon the administrator, and as as employees, from experience standpoint. Hey, Sid. There's a couple of questions, from the the audience about the shift bidding. The first one, is can you show a schedule of everyone assigned working in a single location on a single view, I assume that would I don't know if you have that in there or not, but I know it could be a custom report. Right? %. Yep. That is gonna have to be a custom report, that will that'll list everything on a location, all the employees, and their associated shifts. Gotcha. And the, yeah, I think Bharath answered the other one. The ship bidding is can be based on seniority. Great. 1100%. And that's that's the that's the major demand of of majority of our customers. Some of our customers are are they have complex rules than just based on seniority. So we we have both options. Okay. Yeah. Because there's another chat or another question that came up that says, you know, what else could the score be based on? Yep. I just answered that. Yeah. So really a a variety of things, and and a a lot of public entities all kinda have different, you know, categories and and scores to to calculate that. Right? Absolutely. Okay. Great. Alright. Great. So Yeah. I think, I think, Saron, if you wanna come on stage, I think you're up next. Well, Saron coming on stage. Sid, there's another question there. How long did it take to develop the app? How many hours did it take? Kinda getting a feel for scope on that. Use case to use case. So for one of the customers, it was, like, around four hours because there was a simple app, but then some of the customer, it it it's more than, a thousand plus hours. So, answer really varies upon the use case, but this is the basic, you know, that that is, like, less than, four hundred. So it's close or close to four hundred hours ish. Gotcha. Okay. Another question was, once the schedules are assigned, will they be reflected in Workday scheduling? Oh, 100%. Because like I said, so, the once the schedules are final finalized, they're all published back to Workday schedule assignments. And from there, the standard will just take over. Got it. One other question. I know we have a little bit of time, so I'll just kinda read these off. They're asking about the report. So it says, does everything have to be driven from a report? Is there no roster style view? That is a great question. We are working on a roster style view as well because extend has recently come up with new features where they they give a roster style view of widgets as well. But that is something that's work in progress. It's technically a research in progress just to see if we can give you a roster view. But, again, we have the like I said, so this extend application kind of pushes all the data back into standard Workday. So delivered Workday has the roster views, and that will be what that is what we are trying to or will be, utilizing, to display the rosters. That's awesome. Great. Yeah. Great. Thanks, Sid. Yeah. I think Saron is with us. So, Saron, you're gonna take over, please? And, Saron, you're on mute, just so you know. There we go. Can you all hear me? Yes. We can. Perfect. Thank you, Sid. Let me share my screen. Alright. Hi, everyone. My name is Saron. I am the extend practice leader at Accenture. Today, I'll show you one of our latest apps that leverages generative AI and Accenture Pro to offer a centralized and integrated place to tailors, talent cards or resumes. Now this is already released to Accenture CIO internally. The first release of the app, went right about a month ago, and it is being used by hundreds of thousands of people globally to simplify the talent review process and the project staffing efforts. So I'll tell you a little bit about what we were doing before this solution. The legacy process, was a fragmented experience, with countless formats and styles and layouts all managed offline. So for the workers, this was cumbersome and a time consuming process mostly managed manually. And for our managers and HR teams, it was inconsistent, and it was an an inefficient experience without a go to place to to review and identify their team's talent. And when they do have the data, it wasn't really tailored to the need, and then they didn't really have, quality content, in their talent cards. So, that's the that's the background of the legacy process. We have all of our HR data and talent data based in Workday. So we thought, why don't we bring everything into Workday? So a centralized and integrated place, to have this experience for employees itself as well as for managers and and HR teams. So our solution, does just that. It streamlines and and simplifies the process using generative AI to customize the data and XtendPro to reuse and edit the contents of existing talent cards or or as you need. So this provides a go to place for all things talents for for everyone. So let's go into next slide. One second. So I'm having technical technical difficulties. So this is what we had heard from our people. Just a quick summary of what I had just mentioned. People were finding the process frustrating and very manual. It was very hard to have, an exact match of their requirements for supply demand. There was a lot of offline work, and managers were not really going to to, to Workday to see this data because it wasn't really a centralized centralized place to find all of the data that they that they needed. There wasn't a lot of customizable options without touching the master data, in Workday. So we are using AI and, generative AI and a central power tool to help alleviate all of these pinpoints and these gaps. This will be editable and shareable. It's being stored in Workday Drive. So the link can be shared with anyone who has access to Workday. And also for external systems, say, if you have an agent, for, for those of you who already have, who are using agent agentic AI, if you have your HR team working and work your, your work scheduling tools, your staffing tools, and other systems, you can have deep links coming back into Workday, your one stop shop to get all of your your talent data, and you can have predefined templates, that can be uploaded into the system so that when you do generate those documents, it's not just going to be a static format. Right? So based on, what the needs are for different teams, you can have different templates that can be, implemented to this tool. So let's take a look at our application data flow. So as a user in Workday, first, the foundation for all of this is quality talents data. So on a worker, worker profile, you'd want to have your skills updated, experience, language, if it is a talent card that has all the data like professional, professional affiliation, all of those things updated and look as a foundation to everything, that we're able to to pull into this tool. Once we have all of that, there's two things that we can do. We can either generate a new talent card or we can edit an existing one. If we're, if we're generating a new one, we can leverage our our generative AI assistant. We select input for the AI. Now this could be a specific project role that a worker might be applying to, maybe a manager is looking for, a specific match, and they have a job description they would like to compare this data to. But this, this input to to, the Gen AI gives a direction how to tailor this this content and the suggestions. There's also some supplementary data, not prompts necessarily, but some supplementary guidance data that could be provided, as user input as well. The GenAI process in the background takes the user input and, also looks at the worker profile holistically, looks at the talent data from the worker profile, and then recommends content to tailor it to to the desired needs. The user can look at the con can look at those suggestions, review that, update what, what's needed, and uptake, what they would like to confirm from from the junior suggestions. At this point, you can you can either, start over and, and give new inputs to that to the AI tool, or we can export our, our CD or our talent cards. When we click export, it's going to launch an integration, that uses predefined templates. Now earlier, I mentioned you could have different templates. Right? So this is where we predefined the templates. Integration use is using BERT to generate the PDF. So those predefined templates could be loaded into BERT, And based on the need, those those templates will be used to produce a document and that will be stored in a Workday Drive. Once that's generated, if there is a need to edit that talent card or any previously generated talent card, we can also do that using document intelligence from the extend pro package, to parse this resume file or this talent card file and present it to the user to make further edits. Once the edits are are done, we can, again, come back to the same process here. We launched integration, where we select a predefined template to generate that PDF file and store it in Workday Drive. Once the file is in Workday Drive, it's accessible like any other file in Workday Drive, for download, for sharing links, and anything else that the user wants to do with it. So I'll pause here in case we have any questions before we go into the demo. Yes, sir. And there was just one question. I think Sid answered it, but the question was, is there a fill by rules function for trying to hire overtime based on the available pool of personnel who sign up? Sorry. That was a that was a bit fast. A fill by a fill by what? Fill by roles function. Was that a Sid, was that a question for, the shift bidding, or was that a a question for this app? There was a question for shift getting it. Okay. Sorry, sir. Keep going. Okay. Sounds great. So I will go into the tool to demo this. Give me a moment. Alright. So live demos are fun, so we're being brave here. One second. So here we are on the worker profile. Of course, this can be a deep link from one of your staffing tools or scheduling, scheduling tools, or from teams a team's channel. Like, wherever it is, you can definitely deep link into here. But we're starting here on the, on the worker profile, and we clicked a button to get here. So we can either customize with AI or if there is any legal concerns or maybe the person just doesn't wanna use AI, there's also an option to, to do it without generative AI. So we'll continue with AI here. Okay. Give me one moment. I don't know why. Hopefully, it's still visible just so we can see the full screen. Right. Okay. So this is where we provide input for the AI. So at the top, you'll see that, you can play a project role in here if you'd like to customize or tailor this specific talent card to a given project or job description. This can be tied to any tool for us, for specifically for Accenture. It's tied to, our scheduling tool where different project rules are posted. This is an optional field, but I'm just going to put in here, given role ID. So this happens to be an application designer ID. What happens here is, once we select this, then the background, the the system pulls details, the description for this role, if there's any requirement, skills, and so on so that it can feed it into into the AI, to to find that that bridge between the person's, existing talent and and the the requirements of the given role. In addition to that, we could put some supplementary guy, guidance here for for the AI. I'm just going to say focus on extend my extend experience. Right. So then we have work experience here. I have about seven experiences, but I can select up to three because, of course, there's limited space on the page. So, I'd like to do technology architects, integration architects, and let's do integration architect again. Now on the right hand side, there are some sections for for the talent cards. You'll see some of these are grayed out. These are the required, the required sections, and there are some optional sections. Of course, we can add more we can add more here. Say, if you want language or professional affiliations or education, anything like that included on here, that's optional fields you can do that. So I'll choose to include certifications on here. You kinda see a a quick example of what that final document will look like. You go to the next page. This is where we'll see the recommendation from the Gini service. Alright. So we'll see here, for each experience that I've chosen, it's giving me some suggestions as to what I can have here. Now I will say, that some of these experiences which are stored in job history, within this tenant might not have a lot of information on there. So some of these, the service is just completely, you know, building up from scratch and suggesting some content. Others, it is suggesting based on the data that I have. So this has some data in here, so it's just letting me know, how to present this. So select a few of these these options. And you'll see as I add here, I'm getting content. Looks like it's loading, but I'm getting content here on the right hand side. So I can edit this as I go, if I would like to customize it further. So I'll pick a few of these for my other two experiences. And we have a character count down here to to ensure that we're not overflowing that one page. The next page, we will see all of the data collectively, all of the skills, the certifications, and the summary data that, that have been provided by the AI service. So we'll see here some non editable data, contact info, organization, and demographic data. We'll see summary where I'm able to edit the summary. We see work experience. This is what I just, what I just did on the previous page. There were some skills based on, based on the role that I selected and based on the experiences that I selected. It suggests these skills, might be best to have on this on this specific resume. And then I see here, certifications. So these can be edited. So maybe I want to have extend instead of orchestrate for integration. We will just do one more edit here for the summary. This is my grade demo summary. We'll export this. Alright. So we'll give that a name. That's the org. And you can get feedback, quick suggestions, export. So I do have Workday drive already open here. So just add it here so we see I already have three files in here. So I got my, my my talent card here, testing for a great demo. Let's take a look. And here we have it based on the predefined template and the template that we saw on the first page. We have our skills, certification, the work experience, and and summary. Now I see we're running a long time. So let me just very, very quickly show the edit part. So we're going to choose an existing file from our drive. So I'm going to choose this last one, which I previously generated. Click okay. Now you'll see this is a different tenants. This portion is still under, under construction at the at the moment. It's under development. It's not fully integrated into the main app. Try this one more time. So this part uses document intelligence to parse the data and allow the user to do further editing. Okay. Here we go. So it's very big. I don't know how to, reduce the sizing, but we'll just scroll here. So we have our demographic data that's not editable. We have our summary previously generated that we can edit here. Work experience that can be edited or removed. We can add anything else that we that we see missing here. Certifications are editable as as well as skills we can add or remove. And we can either create a new talent card, but this is not if we're not really, satisfied that we have here, or we can export this and it does the same thing, use the same integration, to to generate the pre, the predefined template the data in the predefined template and store it in working drive. So let's go get back to the PowerPoint here in the interest of time. Right. So what does what does the future hold? What could where could we go from here? So we can expand on this. We can, one, identify talent gaps between where the worker is right now based on the talent card versus where they should be, maybe qualifications for a given project role they're applying to, maybe some, some targets that were defined by the manager. But we can use document intelligence, skill extraction from from a given document, and gap analysis between two different documents to identify any talent gaps, and identify areas of growth for for our teams. So all of these all three of these APIs are offered through the, AI gateway for extend pro. And then another thing we could probably, possibly do is from here, we can infer skills based on a given, talent card, and we can find related skills to recommend training for workers and possibly have, a road map of where a worker wants to be or where our team needs to be for a given performance cycle. So there's a lot of things that we could do with this. We would love to hear from you. So at the bottom here, I have a QR code. If you will be at DEFCON, we do have a brain date there to do a deep dive on this. So I'd love to walk you through, through this process and answer any and all of the questions that you have. So this QR code is the the specific brain date. If you will not be at DEFCON, please still reach out, and we would love to talk to you about this and part of the possible what all we can do, with this tool. Thank you so much. So let me open up to questions here. Any questions or thoughts? No other questions in the chat. So, if you have any questions, feel free to to submit. I know this is gonna be ending here in about a minute and a half. Bharath, if you wanna come on stage and and do a wrap, I also just wanted to mention DevCon as well, but we'll let Bharath kinda finish up, and then I'll I'll just do a quick commercial for DevCon. Absolutely. Thank you, Joe. And, thank you, all for for listening into this. And my special thanks to the Workday team, for creating this as an opportunity and for Sid and Saron for, for representing their respective solutions. Our contact information is, here with us. We'd love to talk to you and understand more about your requirements and work alongside with you on, how you would like to use extend and especially these two solutions. If you have questions, feel free to reach out. You can use this QR code, which will direct us, directly to our LinkedIn pages. And then from there, we can continue the conversation. Joe? Yeah. I just wanted to, to quickly mention DevCon. Saron mentioned it. Just a quick commercial. DevCon is coming up here in a couple of weeks. There are a a couple of options for you to attend. You obviously can attend in person, But if you can't do that, you can attend, virtually, and the virtual attendance is free. So, yeah, we'll we'll make sure to get that, code out to you. You can obviously Google Workday Workday DevCon to find information on that, but we'll get a link to everyone who attended today. And, that way you can sign up virtually. And even if you're watching this after, after DevCon, you can still sign up for the virtual DevCon and register and log in to watch some of the sessions from DevCon. So thanks everyone for joining us today. We we appreciate your time and, look forward to it. Please reach out with any additional questions that you have.