hello and welcome to the latest in our DPM Academy Series this particular video is going to cover how DPM digital portfolio management and the common Services data model or csdm are very interrelated and how you can use the csdm to power your DPM experience we're going to get into a deep dive and talk about key relationships my name is Caitlyn Morse I am the product manager for digital portfolio management and I'm joined by Justin Harden Justin you want to introduce yourself hello yeah I'm Justin Harden I'm the development manager uh for digital portfolio Management Service Builder and service portfolio management awesome thank you so Justin and I will be tag teaming today and we hope you get a ton of value out of this video okay you are probably familiar with the common Services data model if you are not this is the overarching data model and best practice that service now puts forward on how you should map your cmdb for like best practices across service now we are going to highlight the key configuration items or CIS that we include in digital portfolio management we're going to talk about how those key relationships impact what you can see and how you see data in DPM and ultimately how you you can start to take advantage of DPM really no matter where you start in your csdm journey there are places that we will support and you can start to get immediate value and then continue to get more as you further adopt the full data model when looking at this screen I'm just going to highlight very quickly that we do surface CIS in this dark green sell consume box including the business service and the Business Service offering in the design box with the business applications and in the manage Technical Services box where we have the technical services with technical service offerings and the application services this is a better view or or I should say another view of those core cmtv tables that we surface and the ones that are very Central to managing or to like to that end to end solution management with than digital portfolio management I really like this diagram because it highlights from the conceptual model then how that fits into the physical model and this is really important because when we talk about surfacing business applications in digital portfolio management we are talking about surfacing the records that are listed in this table so this is a really good uh image to help you trace back when we say business app or when we say technical service what table we're referencing now the one caveat I want to highlight is that in the in the context of DPM when we say business service we are talking about the services that are listed in the cmdb CI service business table and so that's listed here on the left in the notes so you can see the the table name there we do surface services in seem to beci service those however are just given a label of service they're not designated as a quote unquote business service so I do want to make that distinction um just in case there's any confusion there but again just to highlight we surface the business applications Technical Services and Technical service offerings the note here is that service offerings regardless of type will all be included in a single table servicecore offering and their classification is based on the parent service or I should say the related service so the service offering if it has a relationship to the technical service then it is considered considered a technical service offering application Services we surface application services and dynamic CI groups when it comes to app Services we surface all records that are within this cbci service table and then down here at the bottom again the core Solutions include the business service and the Business Service offering and I did mention the note about the tables already we also surface other items that are in this model but that are considered that we consider more secondary and by secondary I mean they're not prominently managed in that end to end life cycle view as those other core solution solution types are so if we start at the top this business capability we surface business capabilities in a few different places one place place is in the relationship Maps so you'll be able to see when the business capability is related to business apps or uh Business Services the other place that we um will show business capabilities are on the detail pages of the business application or the business service and it's in more the context of the information tab the infot tab where it will list out you know where those relationships come into play We show the information objects that is surfaced on the business application detail page so you can access that as well as I believe in the relationship map we show applications and infrastructure CI as part of the relationship map as well and then the service portfolio so the service portfolio is listed here and that is not a CI but it's part of the Enterprise portfolio's view the key thing to to highlight here is there's also records called taxonomy noes those are fundamentally critical to building out service portfolios and those are also included in DPM as part of that like the service portfolio in the Enterprise portfolio module so even though it's not included here I like to call that out because that is important um that's an important factor when it comes to service portfolios and then finally request catalog items these are shown on the service offering detail page uh we track kpis related to the number of times a catalog item was requested you know for that service offering and then we also will show just what catalog items are requestable for each service offering as well so that's that's included on the detail page so when you're thinking about the csdm model what is shown and sort of how in the context of DPM the previous slide in this slide is intended to really illustrate that in detail for you the next piece that's really important when it comes to DPM are the references and so again I really like this diagram because it shows you the CSD and best practice of how each CI is related to other CIS what are those prescribed relationships per that core data model one thing I do want to highlight is we very much and intentionally so align to the csdm because there are so many different ways that that organizations can build out their cmdb build out their relationships the tables that they use and it becomes nearly impossible to be able to support every possible permutation so we really needed to put like a stake in the ground of what we were going to support and how we were going to support it in the context of DPM and so we we very closely follow again not only the the tables but the relationships and the relationships really impact they impact a couple of things so the first one is how we basically show relationships of business apps to app Services of services to offerings and of offerings to application services so those particular applica uh sorry references are very important when it comes to like the core like detail Pages a perfect example is and this actually just came up on a a a customer or maybe even it was an account uh rep that was we were connecting about an upcoming demo was they were saying hey I can't see the application services that are related to you know that are dependent on this particular service offering and So after talking a little bit we realized that he was looking at a technical service offering detail page and he was expecting to see the application services and you can see that that relationship is is supported here however he was mapping technical service offerings to application services with a dependson relationship and in DPM we actually follow the contains relationship guidance from cstm so it's not that the app service or that the technical offering depends on the app service but more the fact that it contains it so that's why he wasn't seeing the relationship he was following the business service offering to app service relationship types which was is that depends on so that's where you can kind of get or people kind of get caught up or confused and it is confusing um and so it's really important to to always reference this in doubt um so we we follow this very closely again a couple of the key ones to call out are business applications uh excuse me this one referencing other business apps so this will show up this is important in the context of the relationship map and also in a couple of our views on the info tab to understand how business are related to each other the other one is around the business app consuming the application service and then technical service referencing the technical service offering the relationship from offering to app service or dynamic CI group and then the same thing down here on the business services side again those are sort of those core key relationships and then just to sort of continue or build on the from an impact perspective we follow those relationships also in our Enterprise portfolios when it comes to things like needs attention so how data is rolled up from a service offering to a service to a taxonomy node to a portfolio or from an app service to a business application that impacts our kpi results same thing with like indicator breakdowns and then in previous releases our relationship map was focused specifically like we basically built out that map component following these prescribed relationships in our latest uh May 2024 release we actually took up the unified CI map so that includes the the dependency and then the service map as well so that issue will be fixed but if you are on a previous version you know to that version the relationship map will only show you these prescribed relationships so it it is a bit Limited in that sense okay so I'm going to pass it over to Justin to now get into those core tables and data model all right so again um this is Justin I'm the dev manager I'm going to kind of share a high level of different ways things can be wired in so they show up in DPM attached to Solutions so this slide illustrates sort of the two different what I'll call taxonomies so one is a taxon omy of service portfolios nodes and then Services they can be either business or Technical and then service offerings and this is the service portfolio management tables cbci service technical cbci service business we saw a lot of that in the slides that Caitlin just presented these are also in those slides she mentioned them the service portfolio and the taxonomy node and when you create these these two objects here are service portfolio and taxonomy node will end up with this tree that you see here in DPM so right here at the Top This is a service portfolio and then in user Services is a node PC management is another node new pc installations is the service and new pc installation onsite is the service offering and so this is a sort of very simplified illustration of the relationship we see right there on the other side of this diagram we have Enterprise portfolios which can contain taxonomy noes which can either directly contain application services or can contain business applications which then reference an application service you'll see that over here in digital portfolio management here we went here and we looked at business application portfolio and then you'll see the portfolio this is a node and then we have the actual business application and then down here you'll see the application service and of course you can also build out application service portfol folios which go straight to the application service so portfolio node and service like Caitlyn was saying this is sort of the shape of your data and how how we would present it to users in a taxonomy okay now it gets a little bit more interesting when we talk about wiring up specific things to specific like like for example Improvement initiatives or changes or incidents and I'll show you a few of those to specific Solutions and so that's where I'm going to go through some of those relationships I'll start over here let me go back here to Enterprise technology service portfolio so we're on the right side of that that um that diagram that I showed and I'm going to go to PC management new pc installations and I'm going to go all the way down here to New PC installation on site okay so here we see we have eight open incidents we have no incidents in the last 24 hours uh and one thing to note here this is par data which means it is calculated every 24 hours you can see this is data from July 22nd I'm actually taking this recording on July 23rd so it's important to note that this is data over time and then we should see more real-time data down here in the needs attention section I'm going to go to the incident creation form and I've already filled this out a little bit and I've wired it up here see this service and service offering that's how you wire up an incident to this solution the the main way to do it there's some other approaches you can take with related lists but this is the main thing impact as high and urgency high when I submit this guy here's the incident right here it's showing up as P1 critical so theoretically if I go in here into DPM and I hit refresh Enterprise technology and user Services PC management new pc installations onsite you'll see an incident down here and so this illustrates how you would wire an incident up to an offering and that is best practice to wire stuff up to the offering not to the service now once the nightly job runs this number will update to nine if there's no other if this incident is still open and there's no other incidents added intervening time so that's the first example we've wired up an incident and you can see the incident over here in critical major in how would you wire up an outage so I'll show how that's done it works a little bit different let's go over here to all outages and I'm going to create a new outage and here I'm going to actually choose a configuration item which is the service offering which is the recommended way to attach out outages not to the service I'm going to say onsite installations are un available I'm going to begin now so it shows up and needs attention they check right and then I'm going to submit um now when I go into DPN and I hit refresh PC management new pc installations on site we'll actually see a second outage here that shows up uh which I just created and so what I wanted to show you guys there is instead of using like the service and offering Fields like you saw an incident in this case we're using the configuration item field on the aage table and then finally this is the essent Align core demand and here I should be able to and then new pc installations on site and then new style APM demand record and I'm going to submit this guy or save it okay now if we go over here to DPM back here and refresh this we see new style APM demand record all right so I'm going to go back to the slides I'm not going to go through each value or how how to wire up each field in DPM that would take a week but I will kind of talk through some of the patterns and so we've gone over some of the objects you can attach to services and offerings and there's two different ways there's one is direct references which I showed you there's also some that use related lists and you'll see things like affected CIS on an outage or or an incident so you can basically if there's a like in this case an incident it can impact multiple application Services is what I'm showing here or it can impact multiple service offerings so now we're going to talk about business application references so some of these things are very similar to what I've shown before where the pattern is a direct reference so in this case if you wanted to look at backlog items there's a field on the backlog item which is called business application so it's just a direct reference and if you were to wire up that business application to this planning item it will show up on that business application now there are other approaches where for example for an idea right this is an older style table there's actually two Fields there's idea. bus applications and idea. bus application so one is a direct reference and one is a list reference and in this case the recommended way the way that works in DPM is you use the list reference so you can essentially add multiple business applications to an idea and then you'll see another example where we have the Glide list is a list reference here and this one handles both projects you can either do the direct reference which is cbci business app or you can use the cmci business applications Glide list which is a list reference and then there's more of that I'm not going to go through all of these but there's more references here and so what I was trying to and hopefully succeeded at illustrate is that there are multiple ways and patterns when you want to wire up your data your plan build run data to your solution types whether they're service offerings or business applications or application services and that's all I've got okay so thank you so much for joining us today I hope you found this content valuable we do have additional resources here and we will include these links in the video description so please feel free to check out additional resources for more information and have a great rest of your day or evening