all right uh today's today what we're going to do is we're going to go through some architecture services as part of csdn potentially i'm going to propose something i've been asked a lot of questions about governance around how to get started with csdm and uh where do you introduce it into the process so i'm gonna start talking about that a little bit and kind of open it up and see what other people are doing and then we're gonna go a little bit more into exactly like a specific use case and i got a demo set up on our demo instance that we can use and hopefully have a good discussion around that and around the architecture's role in defining the certain parts of the csdn so i want to go through those things today and then we'll open it up and talk about future topics at the end so that's going to be it chime in whenever you can we want to keep this really conversational and get get to something that everybody can use before i start i always like to go through this because there's a lot of new people joining us all the time and then some people who haven't been here in a while that might just like this particular topic so the reason we created this whole group is we want to be a leader in digital transformation so really get that thought leadership out there and show how you use the platform to do this digital transformation a lot of what we've been focusing time on is defining the services so that we can we can transform those services forwards to wrap a model around them and what i really like this model end up being eventually is is a place where you know you have this really good modeled service now we can start applying concepts to it like different ai concepts your different bi models i think that's what a lot of people are really thinking when they're talking about digital transformation is applying those modern technologies like some of the ai platforms offer so our mission is to enable all the members to be able to really participate in their own digital transformation using the servicenow platform and we share work a few weeks ago i shared this workshop that you can do yourselves locally or you can bring in somebody from servicenow to do it there's also papers that are out there and we used to put them on a google drive but now we're putting them all on the forum and i'll show you i'll share a link to that forum that we created it's it's newly created if you aren't registered for that it'd be a good place to go to get these videos and papers and stuff that we're producing this is hosted by the enterprise architecture group so in the beginning it was me getting it started now there's a basically a committee of us that are helping with all the content and people helping us stand the forum up and keep our youtube channel up so it's great that we're able to grow and get some some more help and people driving content into it as well we try to hold these every other week christmas it gets a little we might be three weeks in between or there might be some times but we do try to hold it every other week um since we started all right now this is uh these are the new places to go for all the content i've been getting a lot of emails saying okay is there a recording of the last meeting all our recordings now are on this youtube playlist so if you go here you'll see all those listed and everything since 2022 is on here if you want something older you might have to go back to the google drive which is still available there's also this community forum and we have a dedicated forum called the digital services forum and that's where you'll get a lot of the this is the next meeting here's the recordings from the prior meetings or else something else that somebody's working on you could actually spin up a little forum chat on there or a little forums thread right to make sure that everything you're doing is captured a lot of times we'd go between meetings and it would only be emails to communicate now we can jump on this forum and if there's something we're working on together or some some kind of thoughts you had around you know meeting or something that's coming up you can you can just list them on the forum and we're watching i'm sorry i i i should have raised my hand i'm still getting used to zoom i'm a i'm a microsoft teams user uh don't worry i'll just jump in where are all these links that we can actually click on them will you be sending us an email with these links in it after the meeting is done or it's on the bottom of the invite if you go all the way to the bottom of the invite i'm putting them on there and then i i should send that an email just letting everybody know i'm not sending out the newsletters anymore all the content that i do is going to be posted inside of the the forum okay great thank you i appreciate that you're welcome if somebody could paste it in the chat that'd be great i'm sure somebody has it handy but just pasted this youtube link and then i'm on it john all right thank you mitch sure appreciate it uh also the events are gonna be posted on there and then um we have a shared instance as well and it's still informal i've been meaning to make a catalog item a public catalog item so you can go on there and ask for permission to the instance but it's still informal there where you have to email me and i'll create an admin login for you on that instance but when i create you an admin login you're an admin so if you want to go ahead and create a login for somebody else you're able to do that as well so there's i have about 100 admins on this instance right now and uh that's the instance i'm going to demo from today so if there's something you like that you see in the demo today you can go jump back there and get that content to get started all right any first timers on today if you could post who you are and where you're from and what you're here for i just posted in the chat that'd be great i go go back and look at that chat and make sure if you have any questions or about the group or the communities that you can you can get to me so if you just post your name and uh like it's a name company and and what you're here for that'd be great we'd love to get new members and uh we seem to be getting every two weeks about 20 new members so right now we're about 630 members that are non-serviced now and then about 350 now people that join our call as well hey john i i hate to interrupt uh i think todd porter's waiting to be let in i don't see where we can let him in yeah i have somebody else's wedding be let in as well okay i just hit admit all if there's anybody from service now that can watch that participant button and just hit the admit all that'd be great yeah thank you touch yeah you should be in now i just hit the button okay john i'm from servicenow but i don't have the option to admit people all right you might need to make as a co-host yeah let me see if i can uh make co-hosts how about now heather can you let people in did that work heather yep looks like it did all right thank you okay so let's jump into the content i think and uh today we're going to talk about introducing csdm into your innovation pipeline and this deck will be on the forum as well so i'm going to post the deck up there and then um and then the video for this will be on the youtube channel by the end of the week so we look at the innovation pipeline i work with a couple customers and we're starting to get to these what are the the architectural requirements because when you think about a demand coming through the demand when a demand comes in for something some new service or even a service improvement if it's considered a strategic demand what we usually see is the architect gets involved so either solution architects or application architects and they're going to be able to see they're going to pick the application that we're going to use make a suggestion to the development team to say hey we're going to use this apps based on this selection matrix that we maybe have and and then we're gonna what we want to talk about here is the part about defining the business portfolio so how do we define the new service offerings or even the portfolios that come out of that and the data models around it right so this as we go through the pipeline before we get to the work tasks where we're actually assigning that work we want to make sure that the architect gets eyes on that demand and is able to introduce the the the different pieces of of a new service model that they might need we take a look look at this in a little more detail i'm going to kind of drill down to progressive detail when the when the demand comes in right the architect based on certain parameters of a demand rate a demand could turn into a change you're not going to have architects necessarily reviewing all the change but an architectural service when we're looking and assessing new demand coming in is to say what application or applications should we use to satisfy this demand they start to envision in their mind right how does this we don't want somebody coming in which a lot of times they still do saying hey i want to buy this app so that i can do x right and instead of having the the architect look at it and say we should really use this because that's the way our portfolio is set up but also there's the business portfolio piece right and this is really where the the csdm comes in for those business services that we've been talking a lot about so we want to talk about is this part of an architectural service where the the architect team uh solution architects app architects enterprise architects are participating in that demand evaluation so i want to introduce a process here today and i'm going to kind of bounce it off everybody and see what everybody else is doing because this is just conceptual for now all right now if we look at uh it4it this is it4it that's coming this is more the architects participation in this evaluation stage right you're you're evaluating a new digital service or digital product right a new idea that's coming in so before it hits the portfolio you're in that stage where it's just something proposed now it's a new idea that they decided should turn into a demand it warranted some some additional uh evaluation so it turns into a demand so they're evaluating it right so that's kind of the stage we're looking at now one of the one of the states i really like is um i stole this from one of the documents the architectural documents from the state of maryland they have this published publicly and a lot of people they publish their architectural methods but this is what they use so they're gonna identify the uh technology requirements right so this is what the architect does the solution architect and then they're gonna submit a solution request so that this is actually a little backwards right so what they're saying here is that the demand manager right should be able to submit somebody should be able to submit a new a requirements uh document like i need a new app or i need a new service and then submit it to the architectural team what i'm proposing is that as the demand starts everything and then we automate right that piece where we're sending a request to the architecture team to submit something or you know to suggest an application and so then the solution architect is assigned and they become part of that demand evaluation process and then it goes down right to where they they actually go ahead and promote it into development right it's up for consideration like everything else does in the demand pipeline it's not just done because they say oh we got an app and you know we we have a good idea right now it has to go and go through the financial gateway and all the approvers for the stakeholders so this is what the piece i want to talk about today or i showed you just two references to where it's described better than what i'm going to describe it today because i'm going to introduce like a lightweight entry to into this instead of all the it4it pieces which is pretty elaborate because they go from it4it and then they show you in togaf what the architecture role is so i'm loosely connecting to these these different methods that they have defined all right so let's jump into the demo and show you a little bit more about what i'm talking about now like i said i'm going to give you this this powerpoint because part of a deliverable could be a powerpoint and if you need this powerpoint and you can use it to describe it to your organization i want you to be able to do that whether you're going on to the environment and you're comfortable enough to do the demo i'm going to do for you or if you just need a click-through demo so this part is actually talking about the records in that process so new demand comes in you can click on it and this is what a demand looks like so here we're saying issue uniforms to new employees and then there's certain things that need to be done in order to assess this demand better right so at this point we just have a draft of the demand that came in and the um at this point the brm decides it's a strategic investment so they actually label it to be strategic and then they could pick the type of strategic investment it is whether they think it's going to be an epic or a project in this case we're going to say we usually flow into epics for these new types of new types of ideas that are coming in john can we ask a question about that category strategic sure the question is i put in the chat if you open up that drop down what is servicenow have as the other options for the categories as where they see strategic first operational standard work meaning strategic being a project it's capex or if it's not that it's upper opex and it's more like you're like you said earlier make a change or make an enhancement or something like that show you that in the demo so i'll pull it down for you in the demo and we can talk about that real quick cool thanks you're welcome all right so after it's submitted uh this is the part where i introduce process now because we don't want the the brm that's been assigned we don't want that brm to now say hey i'm going to create it i'm going to go to a pdf document like they're saying the state of maryland and i'm going to submit a request to the architecture team to evaluate this and say what application do i use or how does it affect my my portfolio so what we want to do here is we want to introduce a little bit of workflow we want to see we want to say when the demand is submitted and i'll show you this workflow in the demo but when it's submitted we want to create tasks for the architect an example of one of the tasks might be that we want to do a an application assessment or assess the application portfolio and determine what recommendation you're making to the development team or assess the business portfolio and then determine how this this new demand is going to affect that business portfolio okay so that's the workflow and i'm going to show you like i said in the demo we'll talk about a little more but when that kicks off and it creates those tasks an architect whoever's assigned to evaluate the tasks can come in and either look at the group tasks because i assigned this to the architect group so there might be these assessed demands against app portfolio or the business portfolio right these are the types of demands that might come in and i just did it for proof of concept but there could be checklists on these there could be all kinds of things you do to make these tasks more elaborate inside the workflow i could add different things to it but for now it's just it's just a test that says go ahead and and do this work and here's the demand at the brm here's the detail the brm filled out on the demand so far so they can pull that out of their out of their queue whatever you're using in this case the timesheet portal and start working on it okay and then from there once they get that demand they might say oh i need to make changes so now do they go in as the architect into production right away and do they add the get uniforms for employee do they add that as a pipeline right into production or maybe they there's a little more governance around it and they say okay we have to put in a user story to let the development team know that they should they should install this but there's a problem with that right because you don't want to make the first time a user sees a new like a solution owner or a stakeholder you don't want to make it so the first time they see a new offering is when it goes live you want them to see the offering when it's in the planning stage because in dpm you can give solution owners and stakeholders visibility all the way in that plan phase so we want to give them visibility like i said before it hits production usually you think of csdm is when it hits production i'm bringing the model with me uh but you can have these in different phases right and pipeline because that's where it is right now right it's just a demand and it's in the pipeline to be evaluated because we're actually doing work on this even even though it's just a demand that may never get done it's still a pipeline offering hey john another verification yeah there's a little bit of constraints with regards to the phases this is as you're showing pipeline catalog and retired and that's it and the business service has to be in the operational status and in the catalog phase before any of the so-called offerings under it could be moved to the catalog in operational phase isn't that correct the one dpm you can still see it you'd see it but you can't move it to catalog you can't move the child to catalog unless the parent is in catalog right and that's that that's another part i'm going to talk about here in a minute is when we get in the demo what we should do is we could we could put that in pipeline so there's visibility to the solution owners and to the other stakeholders in the business uh but there should also be user stories submitted to the development team to say look when you move this to production you have to move this to catalog right so we could actually document those stories as part of the demand process because we're an architect giving instructions to the development team or we're an architect saying during the development phase call me for this user story or assign this user story to me so i can make these changes right because the architect is participating in the model we're not going to give these requirements to a bunch of developers to define all these pieces because they might not know the business portfolio very well yeah and for a discussion related what i found happened was a lot of our in development apps are interactive poll in other words they are developing them that they need to submit tickets or report issues during the development so they're in the pipeline but really in order for them to be interactive you consider problem change we have to move into the catalog even though their their status is in development yeah very cool yeah those phases are a little tricky sometimes yes you filled me in a few times but all right so the next part the architect is working on those tasks but as part of the demand process uh this is kind of what you were getting into the the the architect may also want to pass some stories down to the epic that hasn't been defined yet like we know this is going to be a strategic investment and we determine it's going to be an epic it could be a project like you mentioned before but we may want to attach some stories to the demand so that we're sure that we're kicking off that project or that epic with some stories underneath it so the epic hasn't been created yet so we can't add up to the epic because we're still in the demand evaluation process but we want this is kind of like a predetermined story for that epic and i'll show you what i created here another workflow to actually move these stories over to the epic uh once it goes live so that this way you have visibility to the [Music] to the demand and then when the demand goes to approve then it creates the epic there's the stories are created and visibility goes all the way back to that business stakeholder so they could actually see the epics and stories and get updates on those like i said i'll show you what that looks like now in the end what we want to do right even though this is all just the demand we are putting an offering in the table and what i'm suggesting is we're putting an offering in the table during the demand phase and then we should be able to go back in dpm and actually give visibility even though there's not going to be much here right there might be a team defined there's a demand in the queue we know that so we create the new service and then actually label that demand with the service okay so there all those things can happen during this phase so if we look at the overall piece right you have a brm or a business analyst a lot of people call them and then they're working with the architect to do the demand evaluation and we introduced a new piece in that demand evaluation which is adding the data model parts the common service data model pieces in there right so they're adding the pieces in there the architect's doing this work the architect may give some instructions to the development team and then we're going back to the solution owner usually somebody that's on the demand record that is actually suggesting this change and we're giving them visibility to what's going on right now any questions on that we're going to do a demo of this live but i wanted to walk you through this and then a lot of people like i said aren't going to want to go do the whole demo so you might just click through the deck and explain that hey this is this is a getting started on governance hey john this is one question when you made the comment uh in the third screen uh that you know when the architect and the brm uh they will work together to put in the csdm components what does that mean what it's doing here is so the application selection is pretty typical i'm not going to go into that that's usually what an architect does right is it says how are you going to build this thing but what i'm suggesting here is that we're going to add another task that's assessing the business portfolio and that's where we want to introduce a new offering into the business portfolio that's the csdm component the service offering that somebody could see on the business side and they will see it as a part of a capability means are in here i'm just trying to understand what would it attach to in csdm this request this demand will it attach because they usually see the business applications and capabilities well it somehow associate that this new change is related to this business application or this capability so what they would see at this point and and that's a good that's a good question because that's where i'm going to go next with this the um the part that we're defining now just to give visibility in this use case is just going to be the stuff in the green right so we're not connecting anything yet to an application service because we're not sure the apps we're going to use so there's no traceability back to a capability that we're defining yet we're just defining maybe the service maybe the offering just this part we're defining the consume side okay during the demand phase so in this use case that i'm going to demo today it's just the business service offering but it could be the business service as well because these are the part these are the part that you're going to give visibility to the business you're not going to let them really see this stuff right agreed okay all right so let's jump in and i'm sorry i have a question um back when you were talking about either it's a project or it's uh agile do you have a way to do a hybrid um i've done this before we had we kind of made our own little hybrid so we could run projects and then create epics within the projects i didn't know if that was part of the uh the type could you have epic or project yeah yeah you could do it uh you could do a hybrid so the way that our hybrid works is that you have a project phase and a waterfall project and you can determine that as an agile phase and then what you're doing is you're submitting sprints into that phase okay yeah that's i've seen that before i've used it like that before i didn't know if that was still a capability of this yeah when you're actually managing the project that is in there all right so let's go back here to all my demands first because i thought i was going to be able to change that one and i'm not i'm going to use that one for the demo but in the new demand process just to cover that what lou asked there's strategic and then there's operational so in the operational phase the defaults are change defect i don't know what that it's no conversion i think that's one i put in so you could probably ignore that one but those are the operational ones and then on the strategic side these are the ones that we have out of the box is anybody using safe i know a couple of the states were talking about using safe but i don't know if anybody's using it today i used it at state farm a lot they they were a safe house but not an musd okay i think montana was using it i don't know if they're using these actual safe objects but the safe epic is a little bit different than the um the regular agile 2.0 epic that i'm going to use today john there's a question about that the drop down again it's interesting that enhancement is under strategic of course every organization is going to handle things differently regardless of what servicenow suggests but sony servicenow has vetted this with a lot of feedback from all their different customers uh however operationally the enhancement is that is that there because it's really tied more specifically to a project that may have a story and then you're enhancing that story yeah so usually that's something in flight it's yeah that's kind of like something that you're or a product you have a digital product that is being worked on and you're not going to create a new one so you're just going to enhance that thing that's already there so that's another type of record that you can submit got it thanks you're welcome all right so let's go back to the um i thought i was gonna be able to change the one there let's go back to the demand that i'm gonna talk about today and it's going to be the uh this somebody said i want to digitize the process for getting new uniforms basically it's a paper today and they want to say i want to i want to make sure that i can electronically submit the requests like i do to get parking or like i do to get somebody's w-2 or like i do to get active directory as part of the onboarding process i want to be able to get this person uniforms so that you know they don't have to come in their first day and i hand them a sheet and say here's how you go get your uniforms that's the scenario that i'm painting here now the first part that we talked about is this is in draft i'm a brm that's evaluating this and then at some point after i go ahead and i do all my business case i do my financials right there's different assessments you can do on here whatever your process is the part of the process we want to talk about specifically is once all that's done from the brm side that initial piece they want to go ahead and say it is going to be strategic it's going to be an epic we're going to submit the demand so it's going to move the submitted phase and then the submitted phase is where we kick off our workflow okay so i didn't and what the workflow should do in the submitted phase is it should create those tasks automatically for the architect right so i don't want to go out anymore and fill out things so what i should do is i should create demand tasks down here for the architect to provide that service on the innovation pipeline right and the service again is to assess the application portfolio and the business portfolio so i didn't kick those off here so our workflow didn't kick off and the reason it didn't kick off is because i didn't enable it in our environment yet so what i'm going to do is i'm going to use this and we're going to test it instead uh because i'll show you a couple of the features of the workflow so that you guys as you're messing around with it you can try it too so it's digitized the process for getting uniforms and here this is where we create the tasks so what i'm doing in this task is i'm saying when the demand is updated and it moves to a state of submitted like we just moved ours to submitted go ahead and create a task and we want to when we create this task we want to say assess the demand against our app portfolio and then we want to give it to the architect group i'm not going to assign it to a specific architect i just want to get it into their queue right now and then i'm going to have another task and that other task and it might be the same architect it might not be right assess the demand against the business portfolio so basically what we're doing is going back to that piece that we had in the uh in the powerpoint right where we're going up to those services that we define here so these are the two tasks the demand comes in it goes to submitted bang we shoot these two requests off to the architect group but that presumes you in that demand record there were the requirements related lists that presumes you already have that as you said earlier so that the architect can review those requirements and understand you know from a portfolio perspective before they do that further examination what really okay yeah that's the assumption is that brm has defined it enough because what's going to happen here they're going to push it to the architect but also they're going to push it to the stakeholders and we want the architect's assessment be visible to the stakeholders that are saying are we putting the money up for this thing right so when it's submitted now they're saying i have enough information in here in my business case for an architect to look at it and make a good enough assessment or likely they're going to have some conversations right based on the task hey john another question now this sufian while you showed us the technical uh you know due diligence that we care for does it also balance the other due diligence like the finance and business justification and all it could in this demo now in this demo we're just talking about those specific pieces okay thank you but the next piece of that is is exactly that the next piece of this after we do this would be to go ahead and drop it in to a demand pipeline so that it's evaluated for investment so that's where usually it's coming in to where the architect might do a rom sometimes in the process the architect has to do that how much it's going to cost to build right yeah and then it gets down here and then the stakeholders can say wow it's going to be huge or it's going to be really quick and they can make their decision to push it through to the developers and you're saying those capabilities exist right now is it right yeah yeah if you have spm that's part of the product okay investment funding is the specific capability that does that i'm not going to talk about that today but i think i might have done that in a prior meeting okay so we're going to do now is uh we're going to run the flow that we that we proposed in in that part where we're defining these tasks so i'm going to run this little test against that record that we've created that demand record and then what happens with flow designer as you build these things out i'll take the opportunity to show a little bit about the capability here is you can run it and then it's going to give you that that trace file so what you can see in the trace file was was the actual task uh run because sometimes it had that demand that i piped in it has to meet the criteria first so what it's doing is it's saying yes it did meet the criteria because it is in the submitted state and then it went ahead and created tasks uh for the architect right so it created and it gives you the task number so that's the trace file when you're doing your testing or if you want to change your process around you know you want to add another task in here to say go ahead and do a rom for me right so i can put a cost on to the into the demand so they can consider that cost whether it's small medium or large maybe you use t-shirt size is usually what people use in the demand phase but if you wanted to do that right you can do that and then test it in here so if we go back to our demand record after that workflow ran which should be automated right i just i just left it i left the demand right now i didn't activate it and that's that's so once i activate it that would automatically happen but for the demo today i wanted to leave it not activated so that i can run it manually uh so now what we'll see is there is demand tasks assess the demand against the app portfolio and make a recommendation and assess the demand against the business portfolio make a recommendation and these demand tasks that we created like you saw in the workflow we created those to go to the architect assignment group and that may be different for you guys too i understand that hey if you're going to this one business unit or this one agency or this one department there might be different architect groups so there may be some logic in front of that where there's there's different cues depending on who's doing the evaluation the assumption here too is that all these things are running through an architect group which a lot of times isn't the case but assuming all that stuff right we want to give those tests to the architect now what the architect does so now the brm's done they submitted it uh the architect now has to come in and do some work so they can go into their timesheet portal and if the architect team said hey this is uh this is likely going to be a workday request so i'm going to give it to this person that knows workday really well a solution architect that knows workday or it's servicenow what they'll be able to do is go in and get the test themselves if it was assigned to them just like any other tasks um or on the timesheet portal uh they'd be able to come down and they'd be able to see their their demand tests so right now there's two demand tasks that we just submitted and now i can come in and i could say assess this against my business portfolio and make a recommendation right so at this point the architect now has to have some conceptual idea of what's going on in the portfolio itself right so they have to know where this fits so if i'm i'm an architect i'm looking at this thing and i'm saying okay i'm able to go back to the demand and i'm looking at the demand and i might be saying okay this is probably going to be an onboarding activity let's go back to the demand on this one this is going to be an onboarding activity and um might have to go back here but because they're saying they want they want to be able to get these uniforms as part of the onboarding process so i know as an architect i already have an idea so i'm going to go look at what what we're doing for onboarding and see if we have something there right so the what they're going to have to do is come in and go to the service builder right because this is this is one of the ways you might go in like lou i know you guys are using um inspite a lot but if you're coming in and you're looking at your business portfolio you can look at service builder right service builder is is the new interface that we're using i can say okay i want that to land in onboard new employee and then an onboard new employee that's published right now so i'm going to take it out for draft and i'm going to do some work on it and so one of the things i might want to do is go ahead and say manage the offering and this is where i would come in and i would say i want to submit a pipeline offering underneath onboarding that's that's saying you know get new uniforms right so that's uh this is where they can come in and say uh let me create a new offering here and then i want to get my uniforms and then we're actually putting this in the portfolio so that the business can see it right this is my holder so get new uniforms or all right i'm going to save and close that so here this is where you start defining your team right all the stuff who's going to be the ones that's getting the requests for new portfolios uh the financials if there's things around that right all those can come in here if we're charging back that's where your financials would come in but right now just for this because we're focusing in the architect i'm just going to put that get new uniforms in there and then we're going to go ahead and now that we can do a couple things because the offering is created now and i'll show you what we can do so i'm going to go back now and take this out of draft mode and i'm going to say let's go ahead and save our our business service right so now what we did is we added a new offering to our service so that we can do a few things now one of the things i could do because i have that is i can now say um right i could add this get new uniforms for employee i can add this to my demand because that's i know that's the new service that i'm working on creating and then what i could also do is i might say okay i just did that as a demand task and i added it in and i associate it to the demand now what i want to do is i might want to say that on a story i might want to define a new story and the story might be that hey i just created this thing that's hanging there i didn't take and i didn't do any of the common service data model to work to attach this to an epic or to attach it to an application service or application services maybe you need workday and maybe you need some some kind of uniform app you need an api you know like a micro service maybe that's an application service you need to attach to to make this to make this story happen so here what we want to do we might want to say you know create uh csdm parts for uh the new uniform service right so this is basically a story that's getting passed back to the epic that we're going to create providing the demand goes through and so now they're attaching a story and adding that story to the um to the demand i want to show you sorry i had a question real quick um whenever you do a service offering does that attach to a maintained catalog item no not by default you have to you have to attach it okay so there is a way to link those two pieces together so that way i know my service offering goes to a specific catalog item yeah as part of defining it here we could have defined the catalog item as well but that's probably going to be you know make sure you define a catalog item i don't know if i'd have to say that in the demand because that's kind of an assumption because we need a ui to digitize the thing yeah i was just wondering trying to keep the service offering in the catalog item uh one for one because that's going to be well tricky might not be one to one like lou i know you have one service offering that has about 30 catalog items on it right that's right if you look at for example if your business services computing services for example and then within that you have laptop service you have laptop services and desktop services and things like that well the specific laptops might be the particular model of that laptop so that's your catalog item and all you have to do is go to whatever service offering that it goes with and in the related list of the bottom at the bottom of the service offering there's a available for subscribers related lists and you just link it there in the san diego release they made it a lot easier to do that in the service builder you can actually hook it where i defined the service there's a place to hook the catalog in okay thank you you're welcome and that's that's the part here where you got to get like a lot of the mechanics i'll show you a little bit of that right here but when we're using uh creating the demand and then we go so let's go to the epic let's go ahead and say now we're going to go ahead think i already have the epic defined for this but let's jump into the epic a little bit so one of the things i want to do when i create the epic is i want to be able to attach these stories i want to roll them over to the epic and that's not out of the box so what i did in flow designer is i created another one and it's really simple it says when an epic is submitted if there is there's a on the epic there's a demand field so you can see where the epic came from so i can go back to the demand so this is all this is saying is if the epic when it's created if there's a demand attached to it automatically go down and then get all the stories right that were all the stories that were attached to that demand and we're going to go ahead and we're going to update those by by now putting an epic on the story right so we're taking the newly created epic which is which triggered this workflow and now we're attaching it to all those user stories that were on the demand so basically what happens is when i go ahead and create the epic which will be right because this is epic up here there'll be a create epic link on here and then what the epic would do is and i already created on this one so i can't go back that's the part of my demo i messed up i should have waited to submit this one um to create the epic but let me just jump over to the epic and show you that part uh so when we go to the epic that was created and again there's agile development ethics and there's scaled agile epics so in this one i'm using the agile development epics okay so this record that comes through here it's going to be you know it's creating this off the demand and it's and my workflows are pushing those those user story records over here so when the epic gets created it's going to push those that story that we created into the epic child so now the the last step of the demo um and i want to get here is when we now that we've done this work right the the user evaluated it and um the architect did the evaluation the last step that i wanted to show here is as this work is done the evaluations done now when i this this demand is able to be assessed with all that architectural assessment attached to it but also you can go back to the business and you could show them that hey there's a get new uniforms in the pipeline in the portfolio and and you can see the demand right you give visibility to the business to that demand so they're not emailing and calling you anymore you can actually show them where that demand is and then if they get to the demand they can see the architectural work that was done against the demand so the idea here is that we don't want these people who have to go into some custom dashboard but they come back and they go to where they're used to to see all their services and they're able to see that demand so if we go back into uh the demo here and go to workspaces we go to digital portfolio management it'll bring up our our portfolio now the one thing you could do is you can define a personal portfolio and you could put that one you know get new uniforms in there if there's somebody in charge of that process but you can also show them in the enterprise portfolio where this landed now we attach this one to um to onboarding right so so here just in the demand phase uh we'll be able to go in and it's in this portfolio we'll be able to go in and look at human resources and see onboard new employee this is the get new uniforms for employee that we just created and so in there now because we attach that to the demand they're able to go ahead and see this record and see that we're in the planning phase and that that demand we just created forget new uniforms is attached and then our epic right would be in the build phase you'd be able to see your epic because now we're building that we're doing build work instead of just planning work and then when it hits production right they'll get all the additional information in production because you already defined that so that's kind of a little bit about your your design phase and then we fast forwarded it all the way down uh so the last part i showed you here is we we skipped a couple places right so we went from here let's jump back up real quick so we went from the top part right we went from here where we're assessing all the way down to here we're showing them that digital portfolio or the digital product or service we're showing them that in the portfolio that was that last screen but there's work to be done in the middle right and that's the last piece i'll just bring it up i don't have time to go through all that but there's work to be done in the middle that we want to consider as well and what i mean by that is we've done this evaluate part we introduced some new parts and we brought the cstm in very early on right which is really important because that's where you want it you want it considered in your strategy phase what is this how is this thing affecting my overall portfolio so we don't end up with a bunch of you know like a shiny town for these apps but we're actually building an enterprise right and uh that's where you actually have to address it i think it's way up front or if a new service is coming in for improvement you might say look this we want to reevaluate that portfolio make sure it's in the right spot can we add it to other areas of the catalog maybe right so all those things should come in during that evaluate phase during all strategic investments and that's basically what i'm proposing here all right i've got a few minutes left so i want to push through this and um continuing this discussion this is where a lot of people are getting hung up and um i had a couple conversations about this over the last two weeks is what does everybody do differently now that we're adopting the csdm we can't just have one person going in there saying what's all this stuff we got out there and then let's move it into a model and get everybody to start using the model right we have to actually introduce it into our governance so i think the next part we need to consider is what happens when when that thing gets approved it makes it through the investment phase and now it lands in a queue for for a product team to work on it's their epic it lands in their queue so now we have to say okay how did what what is their role the developers and the release managers what is their role in defining those csdm components so a lot of times it should be communication back or assignment in in within that scrum on that's running the epic it should be communication back to the architect to say hey dude we need we need to connect this thing or like lu said we need we need to move it into from pipeline into catalog and like you mentioned earlier we need to connect it to the catalog item right like all those things should be defined as part of that those user stories or a story task uh so this is a big section i didn't cover this today but that's kind of the next thing in the evolution of where the csdm comes in is there anybody else who's working on this governance piece because i i haven't found anybody yet but with all the people in the group i figured i'd ask is there anybody else there yet hey john this is todd from bjc we're we're kicking the tires trying to figure it out so we've got a we've got a black belt working on the team trying to define the processes and how do we capture it as early as possible what's the stage gate before you release something into production or operations to make sure that all the checks and balances have been sold for and so that's where we're at good deal sharing some point would be great if you could john i think it's important to note that the the business services the service offerings the catalog items they're all stemming from the underlying items in the cmdb where the model is there the asset is on the model the ci is on the asset the model has the life cycle information and then the catalog item is published from the model which then connects to your offering all the way up the stack to your portfolio so governance is in layers meaning if when you have the cmdb and you have all these uh objects the models and the assets and the cis all of those have fields on the form which then also going to have to have data owners and data stewards we know that in csdm the product owner is vital right every single model that's associated with a with an application service right that is that this that business app is consuming and that the service offering is depending on must have a product owner right for accountability and that's all part of your governance too and then the product would probably be like in this case it would be on-boarding right would be the product and then the um get new uniforms would be like a new feature of that product right if you were to use a service model and service now and it doesn't come out of the box but customize it so you can publish the uh product right if you were selling that customer's consuming it you can publish it from that service model and then yeah that would all be uh in place and connected yeah so that's actually that's what mark was on a few meetings ago talking about is where does that digital product come in and i think like this type of governance is setting us all up for that so we should yeah we should definitely bring the product in at some point i don't think a lot of people are there yet with products but like you said we might not be able to get around it for that catalog item piece we need the that product model in there and that product model should also be the what you're building right so it should be that epic lands in that that group that's running the scrums on that product and if we could have multiple epics with that product or is it now phases because i know there's phases epics stories enhancements how it rolls down if you're doing the hybrid it would be a mixture if you're doing you know straight agile it probably would just be the epic attached to the product right right or multiple epics sure yeah yeah based on what you're doing right because the the enhancement the story the epic they all link or associate with the product models table which would include whether you're doing a software model hardware model service model application model right you decide homegrown apps may use an application model because you're dictating the life cycle of that because you built it first a software model which is cots out of the box and comes with the life cycle if you're using things like sam pro and servicenow's content management library system same thing with ham pro for the hardware life cycles yep yeah so i'm going to put this uh like i said the video i'll put everything in the forum and um if if you have any more things on this or you have anything to share with the group you want to bounce your governance off how we're doing it to other people let's drop it in there and keep the conversation going on that if there's any guidance around it and you know what i provided today was nowhere near you know being able to be written up into a white paper run on governance for the csdm during an innovation pipeline but i just want to get the conversation started so that things like the product definitely would be a great piece to talk about but more of the roles too the like what does an architect do to start participating in this and how do we get the architect team ready to receive it and provide the service of the you know business portfolio evaluation during the demand phase all right so the demo mostly worked i just screwed up my epic piece but uh hopefully you guys can use the click through and that'll that'll assist you some in having this conversation in your own organization um and uh i'll go back on the chat and see if i i missed anything as well but i wanted to spend the last five minutes on on agenda planning for those of you that weren't on the call this week we do have a steering committee now so charles rod rachel jason and i are all part of that and we're going to take different we're going to take turns uh leading the the different sessions so you have a mix of people with a mix of experiences like charles rachel and jason are focused on enterprise very large accounts so there may be some that are more mature and and then i work mostly on state and local government accounts is really my focus but this way we can get a mix of industry uh experience so hopefully we get some stuff from financials and manufacturing those are a couple of the big ones then next in the next few meetings uh what jason's gonna do is he's going to kind of continue we're a little bit on a theme about the csdm delivery like how do we introduce it into that so what jason's going to come and talk about is something that he presented to a lot of his customers on how you set up the platform operating model so what are the who are the people you need to add to the team or what are the roles definitions that you need to have to actually make all this stuff work what charles is going to talk about is a multi multi-tier one so i have this service desk in the united states that's using servicenow to provide service to all the people in the united states now i have one in japan that pops up i have another tier one service desk over here and they want to share the platform we talked about this a little while ago like incident management i brought it up a while ago but i didn't follow through on it so it's kind of the same thing we keep running into those scenarios is like what's the best way to divide up that the people in japan get serviced in a japan help desk and the people from u.s get the service from the us help desk but if the person from the u.s goes to japan we might want to you know put their service center over in japan right and this common service data model accommodates those things so charles is going to talk a little bit about that and then rachel a couple weeks from now she has a few ideas that she's still kicking around so next meeting we'll talk about what rachel's going to do so any of these things are things you want to participate in we can really use a voice like lou you know you guys jumping in today is super valuable but if you want to coordinate with jason or charles or or rachel please just reach out to them and let them know and it's really good to have you guys chiming in and make sure we're we're doing something relevant here and then also sharing time it'd be great if we had half of where i was speaking and then half of where somebody else like todd i wish i had your name before i did this presentation i would have you know it would have been great for you to take half of it and come in and say what we're actually doing versus this concept john's presenting it might have been a little underwhelming that's all right we don't care on this we don't want everything polished here right that's the beauty of this group is a lot of times we come in and the demos break right we want to take stuff that's rough here and get ideas from everybody that's the goal of the forum so if if you're just kicking stuff around or you're stuck somewhere those are even more fun than hey there's this beautiful polished thing that works like right so so don't feel bad if it's if it's just something like that because you know typically it's going to hit a bunch of people in the right spot right they're going through the same stuff thanks for doing this john it's always helpful appreciate it oh you're welcome anybody else have anything are we right at time we got a minute left if anybody else has any questions or want to bring up any topics that we want to introduce all right it looks like not this time around thanks everybody for uh for those of you that chimed in and gave me the feedback i really appreciate that and we'll we'll talk to you in a few weeks and uh hear what jason has to say hey john one last thing sorry uh it looks like several folks are trying to figure out how to reach out to you and team is there is there best way to do that the forum is going to be the best way okay so if you go into communities and look up digital services forum or go into the invite and at the bottom of that there's a digital services forum link on there you could subscribe to that forum and you'll get all the messages from it or you can just go in there and see the threads without logging in or anything but it'd be great if you could subscribe we want to try to get more subscribers on there so we can have these conversations without waiting two weeks in between and if you don't see that you can just send chris uh have him send me an email but you should see that forum link in there it was also in the chat okay perfect thank you you're welcome all right everybody's in a few weeks thank you