[Music] in this session we're going to cover the it4it version 2.1 mapping to csdn version 3.0 a little about the it4it standard this is an open group standard that is a reference architecture for how i t value streams and functional components which are are the functions in it and how they work together there's a data model there there's a flow model you can find out more at the open group slash it4it as the url the main differences and similarities between cstm and it4it is that the csdm framework was function largely here to facilitate a common model across our different products and services and we focus on the digital products and services that you provide customers obviously we not to be able to map those in a common way across our products it4it however it focuses on standardizing the vendor landscape for tooling and arc and understanding what those tools need to do and how they need to integrate so this was uh done as a collective from a number of different organizations that came together and helped to find what that might look like the cstm use on the platform specific products and integrations that we sell leverage csm so as new products come aboard or we change products we reflect that change in cstm it4it is used by large it organizations to understand what they have what the gaps and tooling and integrations that they have and to rationalize those tools from various vendors as they start integrating them or they identify where there's redundancies other uses in it4it also for like setting up a operating model for it and also to understand what functional areas do you outsource or in source for example the origins of csdm were back in 2018 is a collaboration between servicenow product teams and uh getting together on the same standard way of modeling services and the cmdb so that's that was the background and it's become a very common framework for customers to use to help implement our servicenow platform as well uh itifrit origins were really created by hewlett-packard now part of microfocus the software division and going back in the 2013 time frame it was there as a guided setup for how products are supposed to work one of the challenges that hp had is they acquired many different products over time and as they customers started to use them together they identified there was no framework for that and so um across the different hp customers they got together and they they formed it4it and eventually they decided to donate that ip to the open group as a new standard it4it version 2.1 has something called the value chain which is made up of four value streams so you'll see plan build deliver and run and those are the specific things that you do and those are underpinned by supporting activities on the bottom things that go across multiple value streams in the middle you have something called the service model backbone which is what is the service from a planning point of view all the way through run detect to correct so the the focus on that whole life cycle approach and when you look at the mapping to csdm the the activities over in the planning stage align pretty well with what happens in the design stage which is mostly a conceptual level planning these are the things we want to do these are the business capabilities not the exact processes or organization structure when you look at the delivery request to fulfill value stream the entities in there largely align to the technical services domain but they also align to the business services domain one distinction in it4it is they we don't make a distinction between technical versus business services where they're all services and there's a common way of looking at engaging your customers through requesting and fulfilling those service engagements so those are key to both sides of the csdm model on the run side that largely impacts the area of the infrastructure so these are what we call as is services uh for detect to correct and that kind of maps to the application services and the underlying infrastructure and software and all those interconnections uh typically seen from a managing technical services domain in cstm uh this is just a higher level granularity of the cs of the it5t framework and what you're seeing here are the four different value streams along the top and underneath in the in the blue tiles those are the functional components and then you have the data model in black and uh components that are there there so you can see within each component there's a an object or two that are managed that are the system records if you will and along the bottom are in the purple dots these purple dots represent that service model background the conceptual service from planning point of view all the way through actual service that is being managed from a detect to correct an operational point of view now how this maps a little bit more detail i'll kind of take you through that largely the same sort of mapping but we're getting to some specifics in terms of the service model backbone and i would say for the most part the csdm model maps to what you would find in that service model backbone so when you model the conceptual service what is it from a conceptual point of view right so at a high level when we're doing our planning that also maps to what the service portfolio might look like at a high level so conceptually we see a lot of synergy between service portfolio and business capability for example this this is kind of how we would manage that as a whole we also see from a logical point of view the business service and the technical service being defined here so conceptual is higher level logical gets down into a little bit more specificity when we look at the desired service this is what the offering basically maps to so this is what you put in your catalog eventually service catalog entry and this is what you describe as something you will eventually deploy when somebody orders it so there's a on the it5t side you have the service catalog entry uh which we don't have we do have actually in csdm as well for the request catalog and then of course the underlying service offerings the actual services are are actually part of that operational point of view within cm csdm and down in the managed technical services area so that that classic cis or the physical cis map to actual service the one thing that's interesting also about desired service it does cover everything in that whole offer management request subscription area so that aligns pretty well with what we do in spm service portfolio management service on our workspace understanding those offerings understanding the catalog entry and how people order their services through a self-service request to fill fulfill value stream now this has been the it4it version 2.1 mapping to cscm thank you very much for your time