fair warning good morning good afternoon or good evening depending on where you're calling from this is our sixth session of the digital portfolio management launch and learn today we are joined by Mark bodman a local celebrity it seems uh he will be talking to us today about the common service data model and its relationship with DPM um as always feel free to throw your questions in the chat we'll do our best to answer them or if Mark opens up the space for um questions or comments during his presentation or walk through um feel free to unmute yourself if you can't or you run into any issues please um say something in the chat I'll make sure to be monitoring and with that I will po pass it off to you mark all right uh well thanks for having me everybody uh we've been uh I do apologize for not making the call the last time I think we had a conflict or something and uh but I'm able to make today uh Sue nice to see you how you doing uh yeah there so uh yeah there's a number of names out there I recognize so hi to everybody that uh that knows me have met me before it's great to see you again um yeah so this is going to be a session on uh common service data model this is a a topic that I've been working with oh gosh since uh 2017 uh probably before that even um so I'm here to kind of just take you through a brief overview of what csdm is how it's relevant and why it's so relevant to DPM and DPM is sort of the outcome of some of the work we were doing early on and trying to figure out what the data model is here at service now that everybody should be following so umh and Caitlyn was in the room when some of these ideas were were coming to fruit so to speak we were just documenting them for the first time on the Whiteboard board and they turned into a a full product that we're we're talking about here today so um so there's a lot of background there and of course there's there's a little bit about where we're going with all this too that we're still uh kind of figuring out sorting out but I think it's going to really help everybody here that's using DPM that see that as a value right now uh I certainly did and uh and still do so um that might be interesting for you guys to to know more about um and don't be afraid to ask questions we only have an hour so I may not be able to answer everything I I do record a lot of videos and they get a lot of they they answer a lot of specific things and that's what we U Kaitlyn and I did a couple videos actually there's one on digital portfolio management and on service Builder so if you haven't seen those we'll put links in there for you all uh as a maybe a follow-up or something you can watch those all right U so I'm going to just jump in with a presentation that I have prepared so as the the folks here kind of um talked about we I'm currently on a tour in Asia and I completed one a couple weeks ago in in uh Amia to talk about csdm it FR digital products and this this uh has a lot to do with DPM as well so it may not be obvious today but we have a we're on a trajectory to to bring what I call the the application world and the and the service worlds together more completely and DPM is sort of the one of the first real Investments that we have to make that make that real for the users of our platform um I will probably mention some Futures during this conversation so don't make any buying decisions my uh my get out of jail card so to speak um and you know I'd like to start with just a a view of our platform because one of the reasons I'm here at service now uh if you're if I haven't explained this to you before I used to be a strategist uh at HP software and we used to sell a lot of software to a lot of customers as you can imagine but we had a grown through acquisition and we didn't really integrate the software very well that we had acquired over the years and and the challenge with that of course is that making the software work with other software that we had um was ult I came aboard service now to manage the portfolio management product here so that was my first uh product that came in in uh 2016 um and I brought APM into the market into into into service now got that going with our uh customer base and it's done pretty well since then um so uh so so the value here and the reason I came to service now is because we have a common platform and we can interoperate more readily on the platform the the challenge I found however when I arrived is that didn't always happen it was it was it wasn't really it was more a circumstance where we integrated our with each other on the platform uh the cmdb was sort of central but not everybody used the cmdb data in the same way the so uh the data models every customer had were a little bit different and um we had a philosophy back then every customer could do whatever they want and they did they did whatever they want on the platform there was not a lot a lot of guidance from us on what that data model needed to look like so we um got together in a room um back in 2016 actually 2017 it was knowledge I represented itbm at the time with APM product and there was itm in the room and itom in the room and you know we were we were saying well how do we how do we report on data across the platform what is the consistent model that everybody uses and out of that came this idea of csdm and it wasn't the first idea the first the first name this had was called dos definition of service because nobody had it we were just s trying to solve for the name of of what a service is uh we had identified over 45 different types of service in our platform uh some would argue 145 different types of service and we didn't necessarily Define them all so what what what kind of service do I use when and what do I actually look at and and so out of that was born this whole whole cstm effort so that's kind of the backstory this is why cstm is is there and and to be real Frank it was not a framework we were intending to give to customers right away it was just something the product managers were trying to sort out so that we can interoperate more right we we had our our act together we had our framework that explains or and shows our product managers how to how to integrate with our products so that was the original intent but now it turned into a full-time career pretty much for myself and and many folks here and it become much more relevant to every product on a platform so fast forward to today and just talking a little bit about the the shared data foundation and and maybe the history of our our team the team I'm on now is called Data foundations and it's run under uh gentleman Michael Ludwick I think some of the folks here might have met him over the years and we used to be part of itom but we were split out because the data foundations uh in the platform is useful for everybody all these product areas and what we found was we were unique in that regards um having a shared data makes it easier to add add on more products over time because you can basically leverage the data you already have and you don't have to reinvent the wheel or come up with an integration to bring data into a product that you might buy off the shell from another vendor to me that's that that accelerates uh the value on our platform it's a reason to be on a platform versus buy lots of tools and try to integrate them and make them work together so this is just a slide that I like to use to explain some of that you know the value you get from many products on the platform and how they work together uh using and sharing that same data so um so so so this is just an overview of course just to give you an idea and one of the things I like to present to customers is some of the features and new products that we now have that leverage csdm and you know since csdm is relatively new in our life you know service now has been around for more than 10 years and we've only had csdm for for a short time now so some of the older products that we now have or new features um have started to leverage cstm in a very specific way um one of the things I like to point out is that like business applications now per can show up per incident when you put when you turn out a few flags on the incident setup in on the form on the form expose that information and we use CS M to populate the list of business applications that an incident may be impacting um other things that we of course are here to talk about a little bit more is um service Builder and digital portfolio management and uh digital portfolio management uh product uh leverages the the cstm structures to pull data into the the portal so you're able to see now in DPM is is are the main Services the main applicate business applications and all the things related to that including app services and all the other context that you'd want to see now now the backstory the interesting backstory on DPM and the reason that you know we kind of created Created that product is um because when you look at the our our devops world right and you think about the two ends of the spectrum I call it you you got developers that know how to develop code code and and deploy applications right everything is you know the prerequisite is you know you're buying a product that has code in it when it runs it delivers a service um the service is really the interaction between a user and have that that code execute to do something the users want to do and so um I like this devop servic slide to explain this because from an end to end perspective um developers know about deploying and creating applications but on the service management side we know how to provide services for those applications now there there is a notion of services that won't have applications behind it uh some might call that manual Services um some might call it um uh you know labor but uh that is something that you can do that uh it has nothing to do with uh code running basically you're just doing work but in our platform when we we run code in a data center into an operations context and the cmdb is used for that but when we go Bey a traditional cmdb when we're starting to put data in our repository that exist before um operations exist you know you you've actually thing have things done in an earlier stage in life cycle um you can then you know document that and then understand what what's coming uh also we since we U have the ability to look at planning on our platform so my old product APM is used for Enterprise architecture we're able to uh plan conceptually and understand where the business is in regards to uh how how we're constructing and how we're servicing our business so so these this is the context that allows us to kind of have data in our in our repository that goes beyond just the CNB and bring in data that's contextually uh more relevant broader than your typical seem Tob so uh I do want to pause there uh there's is there any question it looks like we do have somebody that stated something in the in the chat there yeah um Mark there's one from Mike and he's asking about business applications per incident and trying to use mapping to deliver that and then he's asking if there's an outof boox solution or or if there's somebody who should he should reach reach out to yeah so how that works is that if you have an incident against a specific CI for example there's a there's a feature in Incident Management it's also change management that does uh run run a process to try to find the impacts of all of the services right so it kind of works by default historically to identify Services impacted by that particular CI the same process now includes business applications if you turn that on so I'll draw that out on the cstm diagram in a minute but the neat thing about that is we're we're using the cstm path we're using the app services to figure that out because the app services are the ones that map all of the underlying infrastructure to an app service which is logical and the app service is then connected to all these other key areas uh the business application the business service and Technical Services so but I'll I'll draw that out and you'll you'll see kind of how that works um okay yeah thanks I mean that that's what we're trying to figure out right now do we need to do an organizational change to have everyone choose application service or does it pull does it pull that from the impacted services or from the additional C guys um so we're right in the middle of that right now and see Great Value if we can if we can map that up and and bring out the business applications that are impacted from that since we're we have everything already mapped because we use service Builder so we're in a good space for it now we're just trying to figure out how to get that data out using those types of things like refresh impacted services so thanks yeah yeah it it's basically in that same process where we where they now show um uh the business applications exactly so um and if I if I can have an instance up and running I could probably show you I Caitlyn I think we went through that in one of the videos too I can't remember which one service Builder maybe um yes I think we we did I I also can't remember which one it was um and I I wanted to to say that I think in one of our sessions we did I did also do a demo of that uh in one of our previous topics so um we can maybe figure out which one that was and for um business applications we will show uh the incidence for a business application based on the related application services so we do provide that out of box in DPM um and if there are questions specific to how to get that working we can talk that see Caitlyn and Mark and Mike I work with Mike uh closely on the product and I'm from a process standpoint uh I I managed a team that managed the process or the practice is it possible that we can have a 30 minutes one hour one day to follow up just on what we are trying to do with SPM DPM and utilizing csdm really changing the culture at US bank and then getting on board with what we're trying to do we're looking for you know confirming what we have put together and and the directions that we're going toward and we recently had a service now readout just yesterday uh as they deep dived into what we're trying to do uh the question is maybe for Mike too as well is do you think it would be beneficial uh one off for us to work with Caitlyn and in in the team to show them what we've got as a user case um scenario and and then maybe continue to guide us in the right path yeah we can work that up through our engineering team and then allow this this meeting right here to get through the whole csdm but yeah we have a pth for that I hear you I hear you I hear you thank you yep all right thank you yeah yeah no problem this that's why I'm here I'm here to answer answer questions and hopefully you guys can also collaborate which is great um but yeah it's it's the two ends of the spectrum that are very interesting and and so csdm kind of fills in for the guidance on how that model needs to look in order to be consistently connecting these two worlds um just back in the day just for for some context I used to be the developer manager here and I would basically throw things over the wall and I wouldn't worry about it I didn't really understand what a service was I wasn't trained in itel I was a developer uh than an Enterprise architect again even in in the EA space we don't really do a good job about planning and understanding the operational context so I'm trying to fix that too that's a whole another story but um I'm trying to I'm trying to evolve the EA world to to into sort of that that uh uh it for IT world which we'll get to in a minute the um the service graph you might have heard this term before as well that the term really comes from the fact that we want to Rebrand the cmdb and what do we call this more complete model which covers so many things that the cmdb never had in you know traditionally so um cmdb is traditionally just operations um even operations in service management were well well connected historically so we're doing we're doing that already that's kind of one of our our cornerstones key of the the company but what we uh um as we extend you know further to the left and all the planning activities deployment activities um build activities those are all kind of out connected as well which is really for me compelling um but I I think one of the challenges and one of the challenges that we had of course is that we were still operating in silos in terms of the user experience the the folks that are creating applications have had a completely set of user experiences than those that are managing services or even operations and DPM the cool thing is if you if you notice here uh looks at that full life cycle detail as you start plugging in different areas of the model and and contextual information like you know uh once you have that app Service uh and it's connected to operations what are the tickets right how can you bubble that up to the folks in the planning side that have applications equally to the services and um to bridge these worlds traditionally it's always difficult uh so so you know in the platform provides us this opportunity but we didn't we just didn't have the data model until csdm that consistently connected those worlds so this this to me is is really compelling about the platform and and the reason I'm here the um cstm itself as you start looking at the different domains are pretty much aligned to that devop service point of view and and so we have these two uh Chevrons here kind of the world is develop is split in the middle but we have Dev on this side and Ops on the right side and we have four key domains in cstm if you're not aware uh the first domain is design and this is where APM kind of started and when you're planning uh a new app you have to hire developers and whatnot and or buy code and deploy it so that leads to the second domain and which is build uh now build didn't exist in previous versions of cstm if you've been tracking this the the reason build is there is because we purchased um different companies that start to operate in this area we also have a few products like devops agile save that operate in this area to track deliverables uh project portfolio management to a degree you know PPM so uh as we as we design and we build things we have context now connects to what we already have out there uh operations we have this manage domain the manage domain is where we uh the itom and itam products kind of sit to manage the what's what's going on in the data centers this also works for what's in your cloud data center so it's not just on premise but also in the cloud and then we have itsm and CSM on the very cons uh end here for consumption and so um the the interesting that's happening is itm is kind of um now kind of baked in you know pretty much to the platform it's kind of B default but we've uh extended our capabilities and a lot of our customers are managing how how they sell and manage services to their customers so um these are going to be external to your organization CSM folks and U those are going to be the folks that buy your services and your products so consume means more than just internal use right it's it's external use too and we're investing a lot more in this space so this is going to be uh an area of growth for us and we've also started to stratify and and bifurcate CSM into different industry verticals because different uh folks have different companies have different types of products they have different types of customers and um so we need to be able to articulate those products in CSM to be able to capture them so when they call you you we we have that uh product aware you know we understand the products and the kind of customers that that you're selling to your [Music] customers um looks like do we have uh a question here oh no just some folks talking in the background that's fine um and then all of this sits on what we call the foundations domain and csdm and the foundations d domain is used across a lot of these different areas by default so things like locations uh business unit higher Keys things like that which are referenced and used by uh like like I like to use locations locations of your developers locations of your consumers locations of the servers and the data center so we try to use the same location hierarchy in all those cases and part of what my team here uh does is we work with different business units to extend those hierarchies or to to modify things or bring stuff into the common data where it doesn't exist today so uh there's sometimes things get out from under us there's there's a we can't kind of control everything but you csdm kind of represents that that effort and what we're trying to do um one of the things that I I also noticed a lot of our customers have have struggled with this too is uh kind of making decisions on what they're going to how they're going to use the data model and um when we when we first came together to start discussing this these different worlds and we had different definitions for the same thing so service you know was the big one that brought us together we had to agree on definitions now even if we disagreed we still had to agree to move forward and so there are certain elements of the model that I'm not too happy with um especially app services that to me is a very confusing name um but we'll get to that in a moment but we had to agree to disagree and and just um move on the other thing that we also put a lot more emphasis on in cstm is data governance and so part of my team over the last couple of years we've been um introducing some data governance Tooling in order to better manage uh the data life cycle and the data uh Integrity basically so dashboards there's something called Data foundations dashboards that's now in the in the platform you can download that in the store gives you a whole bunch of metrics to work on and also there's a something called CM Tob data manager that deals with end of life which we never had in the platform before so we can get rid of data that's no longer relevant so um so just looking at things more end to end that full life cycle again um and data governance happens to be sort of the Achilles heel for um success ESS on the platform when you're sharing data if you don't have a governance process it's impossible to trust the data or to deal with issues where data coming in isn't isn't correct and it has to be corrected or even identifying an owner of that data so this is a big part of what we're focusing on uh now okay um so as we get into csdm itself one of the things that uh you know my background is Enterprise architecture and one of the one of the the things that uh I learned early on in my career as an EA is if you can't put it on a single page and talk about it it's too complex you haven't done your job you have to simplify things to the point where you can explain everything on one page um and as an architect then you can you can discuss it and get feedback and do something about it the um yeah I appreciate that Caitlin yes three people what a services and you'll get five different answers so um the output the outcome of our particular work is that we put these definitions out there and there's a white paper associated with cstm that's on our community site that is slowly becoming documentation by the way so the documentation site that we have is very good I I just met with some customers yesterday and they made a comment that uh uh you know the the docks that we have here at service now are pretty extraordinary compared to other uh vendor experien they've had and I would agree with that so um so this is this is all of csdm and every object here has its definition um and these do change a little bit over time um you what you're seeing here is in the design domain up in the upper right hand side these are the objects and the personas that interact with this area uh now this isn't everything in our data model we have over 10,000 tables in the service now platform um this is meant to be that minimum viable model that connects these worlds okay and the consistent way we use them up until now people maybe not have used certain elements in the same way or connected them in the way that we're prescribing and that leads to issues um you know of course as a product manager if I have consistent data um we can then leverage that consistent structure and data for reporting our analysis purposes uh I think we just talked about Incident Management um the way Incident Management works on the form now is if these are the CIS down here that you would pick and then we can analyze all of the potential app services that use that CI then all of the services U that are impacted but uh with the going in there and turning on the flags and the related list you can also see the the related business applications as well so as as these things are um are related obviously we can use that relationship and to our advantage and the incident form now takes this path to bring that information in um now a lot of times it starts with a a user and you might pick the service and off offering and then CI so um you can kind of come into this from two different directions the way I like to think about it uh you know event management can can you know trip on an event on a specific server or network device uh and that could create your incident or you can deal with a person calling so there's two two directions in which that typically occurs um but yeah the what you're what you're seeing here is uh all the different domains and all of the key objects that are part of those domains that make up those um uh those those areas of the model uh the top part of this model is really your Dev uh area and then down below is OPS in service management so best way to think about it uh the build domain is here on the left and this is very pretty much optional the uh reason for that being optional is that we do have a lot of customers that are uh not tracking those uh Deb deliverables yet we bought a company a couple years ago called sgle and they manage config files and that's what this stlc component represents today we will expand that in the future by adding additional capabilities in this area additional I would say uh detail such as artifacts source code repositories things like that and be able to trace what's being worked on by the dev team and how that relates to the operational picture and entities that we would find down here so that's the that's the goal of our build domain is that we're tracking what's uh what's related and how that's uh connected to everything else um down here the service is sort of the central you'll note note that this is the Lynch pin that connects all these worlds if you don't have application Services uh this this all they can't really hang together so to speak so without this Lynch pin right we we're unable to connect the the the Devon Ops worlds and of course Services worlds we have yeah really quick so a question from Cassandra uh so she mentioned that it looks like the business app to app service arct line is is kind of newer Edition from the first release um and I sort of mentioned I I think it was added just to be clear that that relationship from business app to app service can be direct in stlc is truly more optional that's that's right um I what happened was when that when we first published that white paper um we did document that the sdlc component was not required but we didn't have a line on the map that that showed it so so we ended up just saying you know you you can still bypass it you don't need to use an sdlc component uh you only need it when you have um that level of detail and it and it's kind of like both those relationships will be respected you know um it's like this is the super highway and this is your local bypass route you know coming through the sdl component so those will will continue to coexist for as long as we uh uh foresee anyway so and then one more question from her she's asking if you could speak to the products model in Agile development and the tie into s uh csdm yeah that leads us into some of where we're going in terms of product centricity um and before I move on is there a uh can you want to you want to do a show of hands on people that are trying to migrate to a product based operating model is there is there anybody out there that's that's doing this product Centric yes I see a yes A couple yeses a couple of familiar names with yeses all right so a few of you anyway are moving to a product Centric operating model there's four that's good still trying to figure out okay um so so all right so so this is good because you're in the right place you're using the right product here because uh that's that's one of the the Visions for DPM Now product models is currently down here and those product models have traditionally been used uh for the infrastructure that we sell and software that we sell the idea here is that um if you have Asset Management we need to know the products you purchased um the agile products however that we have started using product models here as well for a very similar purpose the as a product owner you deliver a product but it's not the same thing today it's not the same thing they use something called application models the reason for application models is because they needed a way of tracking their backlog and they chose the application model in order to um say all all this backlog pertains to one product that I'm delivering um so historically we've had a couple of uses of product models and they haven't been well coordinated here in terms of what is that holistic picture look like how how are these product models used should be used and where are we going with all of that this this is becoming um more Central in our in our model going forward and in what we're doing now this is still more than a year away until you start really seeing this as becoming more Central but we're getting ready for it and we've been making some changes under the covers to prepare the world to be product Centric using these product models so um let me just so so I don't want to put all my time today and just explaining cstm because there's a lot of videos there's training and I'll have links for that at the end so you we can learn more about this and kind of go through it I just wanted to show at least the the bare minimum uh connections through this model and the fact that we have the worlds connecting through app services and of course those Connect into the technical service world and the Business Service world and by the way the major differentiation that I like to explain here is that Technical Services um are are basically consumed by technology consumers and there is no necessarily there's no um subscriber there you're you're alloc an environment for a production deployment for example or you know you're using this infrastructure storage array because you're building a new application that needs that storage so you you bought this is where your piece Parts your building blocks are purchased and implemented the difference is over here you have a business consumer and you know who they are you know the locations and you know the groups you know the users and maybe business units that are those subscribers and so offering connects you to those subscribers and so you understand exactly who is impacted by an outage for example or a change that's coming so you can do that work and and Caitlyn you you explained to me in one of our last calls that we we can do some really cool things we could say who give me all the users in a location even if you have that as a subscriber so uh that can be used for um proactive communication but that's the main difference between uh this world over here and this world over here just to just to set the record there and down below all of this other information is used like I said contextually um product models is sort of the center here and that's kind of where we're going and um the way I like to explain that one uh and kind of how we're we're planning on going with that is that um all right hold on a minute I'm gonna fast forward a little bit um there's a little bit of a mess today that we're we're trying to reconcile and it leads us into where we're going with all of this um so when we say product we have products use in Asset Management I just kind of explained that one um we have it done used in a agile devops for managing backlog like I just explained but we have one more thing to think about the products you sell to your customers and so today when we say product it's not necessarily consistent and um they're not the same thing and they're not managed in relationship to one another now the other thing that's interesting here is that they're not related usually to the portfolios that most organizations do manage and that's sort of the the this is sort of the the scope for what what's built in DPM um the applications and the services the two ends of the spectrum the things that you know you're investing in from a code perspective and in you know obviously infrastructure Cloud resources versus the you know managing the consumption experience to uh internal or and customers so so the magic here is like well how do we redefine this universe in order to bring these worlds together and uh before I move on I I see there's some chat there is there some questions here do I need to address Caitlyn there is one question around um agile and Ops um and I don't know dianae if you want to come off of mute this was a in sort of previous when you were on the the screen discussing yes um we're struggling here because um if a customer logs an incident and then it becomes a story and then it becomes a defect and all of that and our customers are really getting confused so what we're trying to do is to make sure that they have that one reference which is their incident to track it end to end but there doesn't seem to be any clear lines between the agile and the itsm products as to operationally what goes where so we end up with duplications or we end up with missing items uh it gets closed here so it appears that operationally this is fixed but it isn't so I'm just trying to wrap my head around that as we're discussing product and we just don't want to lose the perspective of the customer we're really big on what the customer sees and what they have to deal with and if you say well okay it's no longer an incident now it's a story no it's no longer a story it's now become like we're just confusing them right now we're just making this overly complicated I think maybe it is you're you're absolutely right this is the issue and and this slide is sort of the reason for that because you know think about sold to customers this could be and you know internal customers too right internal consumers but we don't necessarily have a connection back you know uh between these two worlds service management world and back into applications uh we we live in completely different data models completely different tools and the connection between his worlds is is Loosely managed at best right that that's really what you're you're alluding to I think um I think our customers don't to be quite honest don't care about any of that they got a patient they got an application not working they want it fixed exactly but the problem today yeah the historical problem just backing up a little bit I'll me go back to another to the diagram again um is that the when the customer reports an incident you know you're looking at what's running and you know um all they know is this instance of my application is is not working and the the dev team has their own repository for backlog and there's a different thing over here to manage the business application list so what you're what you're describing is sort of the today's disconnect and what is the consistent thing that's really binding all these worlds together and uh that's that's kind of where that product model is is going to start um solving for us in the future but today it's it's it is disconnected out absolutely there's no doubt about it the other challenge I have I also manage our CSI and I tend to look at reports and to me it's important that we have an endtoend Vision that there's no you know how long did it take how many test how many teams did we need how many so there's got to be a means to get that I'm going to use the word story but in the context context of data when I look at the data I need to see the whole story to understand how can I improve or what the real issue is and I'm not do we lose you no it's just what I said is I'm I'm not seeing how we're heading towards that where's my bridges yeah yeah so so so the first you know this this is the world is transforming and the world doesn't change overnight right so the best way to really think about this is that we're tackling part of the problem with with cstm which is a consistent way to join the worlds you know that we we now have a world in which design is connected to Bild is connected to operations is connect Ed to who uses what right so so on one map we have a consistent way of connecting the dots okay which was stage one honestly stage one is just understanding how do we really relate to each other consistently through the data model the second stage that we're we're talking about is DPM DPM what DPM effectively does is say I manage the services okay and the offerings and I manage the ampli and I can see both of them in the same in the same space and again I can connect the details from using csdm so that I can pick up all the details I need to from either perspective from the business app perspective or the service perspective but it's still sort of loosely coupled if you don't follow csdm the world's you cannot see the connected tissue right from the business app point of view or the buiness service point of view just you just still can't see how it's connected unless you follow cstm appropriately now the third wave the third wave we're going to talk about briefly here is digital products and and these product models somebody was asking me you know about the uh our Dev products our Dev products do use the product models today but the the issue today is that it's still sort of disconnected um is if you are an APM customer if you're using our APM product one of the things that's happening in our um our our next release our uh Vancouver release is that when um you create a business application it will automatically create an application product model APM I'll just say APM and so that means we're going to proactively have a product model for every business application and the devops tools the agile tools will have a connection directly to this business app um this some of you might know Colin Colin O'Brien I worked with him well since I came to service now and we we talked about this back you know six years ago and a the the application product model is a product model type okay that uh they've been using ever since then but there was no connection to the business application that is now explicitly connected and it will start to tie in that backlog from a business app point of view so that's going to be um useful for those folks that do use the aall products Dev products and want to connect it to at least the business app which which better connects the you know the top the the the dev worlds together together right planning and execution from a Dev point of view so that's happening in in Vancouver Mark just want to give you a quick time check we have about 10 minutes left and we'll need a minute or two at the very end to do a couple closing remarks okay so I will um speed through the you know rest of us but the the cool thing this is really the the message I want you guys to to to hear today those worlds are connect Ed because cstm exists period right there's going to be incremental changes to the year world in the products we sell in order to further tighten those connections right through the way that we create the model and use the model daytoday you know version to version and DPM represents that user interface that brings that service product owner and you can even say app owner right into the into the picture so you don't have to go to many different user experiences in order to see what you're managing and the world from that perspective but um and that came out of um an a meeting that that Caitlin was in and I just want to pull up just a couple more slides and then we'll we'll get back to your your uh items but but basically DPM came out of um a meeting where're saying you know the application and the service worlds are are starting to converge in a lot of ways right csdm was helping to to bridge that Gap bring those together um and we have that app service like I said that's in the middle so that's kind of why we chose that as the middle object in cstm but at the same time we said well how do we now bind those worlds together even F even better and so we we came up with a definition of what we're calling digital product and uh so this is a quick quick overview um to give you some context this this definition didn't exist in 2018 okay it didn't exist we um I worked for about two years on a white paper Sue was on this uh call Sue desiderio she was on that effort to to define a digital product we did this and we published this at the open group now the reason we needed to do this is because U there was no definition Gartner published a paper in 2018 saying customers were agonizing over the product definition because uh uh nobody's done it before so so now what we imagined or we envision in this definition is a convergence of these two entities when you're when you own an app and a service all right it is what we would consider a digital product uh going forward that that's really the the new what I would say top down entity that can be consistent throughout the whole model now um we went we've so this is just an outline of that particular um that particular white paper and you can see Sue here uh helped with that paper and so thank you very much Sue and and just to net the definition it's managing running code and the outcome delivered uh everything that goes into that running code and all the outcomes that that might might be delivered so those that's that's essentially what we're managing and that's what we mean by by digital product um the it for it standard I'm just so one slide was refactored around that and it came out in December uh this new version of it FR it and um it it's all centered around this digital product that we're managing and you have different releases of it you have different offers that you you consume and then you have instances that you operate on so again bringing all the different worlds using it FR because it's a comprehensive framework and now being product entric and just service is part of that app is part of it Hardware is part of it if it's if we're considering our digital product like a smart car or an airplane or smartphone so digital product now works for all of those things it can be an app service um Hardware or combination of all those things and we can plan on it through you know build it deliver it and run it so uh it's a simpler definition that is more flexible for um making sure that we're doing all these things we're we're evaluating the market we're exploring backlog we're integrating building and releasing uh we're consuming it and we're operating it um these are all value streams by the way these zeros so if you want to learn more I would suggest going to the open group and looking at uh it for it version 3 there's training available and certification available so you can learn more about it so that's that this is DPM kind of came from is is really that that that vend diagram bringing those worlds together from both ends from user experience but now there's a framework that does this for us going forward so that's really the the exciting thing for us um and just one more small yeah wait just one more thing um when you think about the portfolio structure in DPM we talked about the the Enterprise portfolios we think about that in four different areas um so Caitlyn and I have been talking about this a little bit lately and making this more um I would say deliverable or consistent as well but when you think about what you deliver to your customers you need to plan your strategy investment there uh what your employees use what's foundational like shared IT services right and then tool change is the the other thing you have to think about optimizing so your EAS your pling has to has to look at the at the World in at least these four buckets and then there's of course dependencies between these buckets because everybody depends on shared services right everything depends on your infrastructure running somewhere in cloud or on premise Network Services data data services so all these things are dependent on one another and we would argue that they're all digital products you want to see the development and the services and who those consumers are otherwise uh these guys will might be infected if you're not investing in something foundational that's used so this is the world we're trying to make more formal more consistent and um yeah look at it for it to see where this is coming but that digital product is a way to to to simplify the model but also accommodate planning through execution delivery and use of um apps hardware and services going forward so that's what's coming so I want to stop there I know we're we're pretty much right at the end of our our session um any questions at this point there's been a lot of good conversation in the chat Mark um and I think we'll try to capture some things that might be outstanding that we can cover in an email followup um thank you so much for taking the time to walk through all this information one thing that was requested as a copy of this of these slides is that is that something that you um are willing to share oh yeah yeah um there's I didn't get to a lot of the Futures here so that's fine um and there's a lot more you can learn about csdm and um this is just a quick overview of the the material available out there for you U we're updating the lab by the way there's an older lab there we we did a newer version of the lab in knowledge that will be made available on now learning awesome so that um that will we'll share these these uh links as well we'll try to extract that from the PowerPoint and make them available in our email followup so it's really easy for you guys to get access to these and one of the updates in the lab of course is service Builder is there and also DPM awesome wonderful well thank you so much I have one thing that I want to share with the group very briefly in two minutes two minutes or less so um okay I want to quickly share this I'm sorry that this is just visualized in not the presentation mode um but this is our road map so I wanted to just do a couple of quick call outs coming in August uh which will be here before we know it we've we're Dev complete and so we're we're just tying up things with a bow um what you can expect is we are delivering uh an update to our Enterprise portfolios module so you'll now be able to create Enterprise portfolios for business applications and for application Services um in the business application portfolio you will be able to see the related app services so um so that they are included there um and then we've also introduced kpi groups for business applications so you'll be able to create the groups um and have a lot more flexibility in what kind of data metrics that you want to report without having to make any um customization in uib um and then we also did update our their technology portfolio management data model um that's not listed here because this kind of came in a little bit last minute but we we um are uptaking the the work that was made in uh APM with the Enterprise architect workspace and so now we'll have parody with u the data that they're showing in November we're looking at releasing an improved and personalized home homepage experience and so um that's something that we're really excited uh for you guys to to get and for your users to have it'll be a lot more tailored to their specific things that they own and care about and they can then personalize that um so in February we're looking at making updates to our personal portfolios to make those more of an entity in it of itself so we can have data points and things that really represent the personal portfolio and make it a little bit more action actionable and then we also want to introduce condition-based personal portfolios so that you can set a series of conditions and that will maintain we'll create and maintain the portfolio now we are looking for for customers to help us with some research um we're looking at some early Discovery to understand what would be useful um what kind of features that you would be interested in for the personal portfolio and how your users um would get the most out of it and similarly with the condition-based portfolio um it's painless I promise if you are interested um please do send me your information you can just send your name or your email as a direct message to me in the chat Chris will send a follow-up email as well um if you if you want to participate you don't have to do anything to prepare it's just taking a little time to meet with us um myself and our our designers so thank you I know we're a minute over uh but I did want to just get that in there for you guys thank you Kaitlyn thank you Mark what a great session we had today very much appreciate you both for uh participating and giving these presentations um as always everyone you will see a recap in your emails within the next 48 hours if you have any questions or comments in the meantime please don't hesitate to reach out otherwise I will see you all in two weeks have a good one bye thanks have a good day everybody than