[Music] hi this is mark podman in this session we're going to cover it4it version 3 mapping to cstm version 3. a little bit about the it4it standard this is an open group standard that is a reference architecture for how i t value streams and functional components uh 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 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 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 there's 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 customers started to use them together they identified there was no framework for that 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 so i wanted to talk about it 5g version 3 as a preliminary snapshot because version 3 has not been released yet we're looking at releasing it4it version 3 late 2021 and what you see here is the change in it4it from version 2.1 is really centered around digital product in version 3. so here we're dealing with a digital value network as the extended integration between all of these different value streams the value stream strategy portfolio required meant to deploy uh request of fill and detect to correct start to migrate over into a capability definition in this particular version so on the left hand side you're seeing the digital value network supported by capabilities in it basically and the center of everything is the digital product and that digital product definition we'll get to in a minute but it's the the thing you work on through the entire set of capabilities and and all of the value streams on the right on the right-hand side you can see a little bit of an expansion of what a digital product is and we really have it starting at that strategy portfolio the idea here is you have a portfolio of digital products that you're managing throughout their life cycles and the idea here is that you have the in white uh the different value streams that interact with those digital products as it goes through these different capability areas and so what you have here is the explore value stream for example that basically this is where you explore new product ideas you're able to test those ideas before you do your full investment um down in the product in the requirement deploy side you have product release where you do the continuous integration for example and now the output of those continuous integration processes and if you're not familiar with that that's something that comes from the ci cd or the devops movement where we've automated a lot of the the work required to merge code and then compile it and make sure that it runs some basic testing so that continuous integration process is now captured in this product release now if you choose to release or deploy a new digital product that's where the the next set of value streams comes in so these value streams are here to handle the release process uh if you choose to take one of your good builds uh if you're doing continuous integration you can choose to release into production periodically on the other hand you can choose to deploy a new version of those particular digital products through the deployment process which also integrates with the operations side so kind of goes through that whole process you could deploy without releasing um which is like a patch or an upgrade or you can release a new version of a digital product which comes with new um a service offer that you can fulfill so that leads us to the fulfillment value stream that fulfillment value stream is all about fulfilling interactions with your customers so how do customers obtain your digital products is that an internal catalog is it not ios app store so those are the different catalogs you can actually provide your offering your service offer part of your digital product as a fulfillment process and last but not least you have continuous operations and that's the idea of monitoring and proactively resolving issues whether it's a capacity issue a security issue or anything else that comes up in terms of uh continuing to make sure the operations of that digital product is good and there's a feedback loop also incorporated here which is the continuous evaluation of your digital products so to make good portfolio level decisions you need to have an understanding of how well your digital product is performing in the market are customers happy with your digital product um even on the internal consumption are people using what you're providing internally um and what is the show back or even chargeback from an external customer point of view so it doesn't make a distinction between internally consumed and externally consumed digital products but we do want to make sure that we look at these four capability areas and we have supporting capabilities like risk and compliance and security and asset management things that are basically applied to all value streams but not specific to just one so those kind of tie in from a supporting capability down at the bottom so that's it52 version three at a high level and what it's going to be containing is a lot more detail behind the scenes that describes these value streams and it describes the functional components that make up each of these capability areas so to map this to it4it at a high level we can start with that digital product concept when we're looking at csdm we've got these product and product models here up in the foundations domain and this is more future oriented as we start to look at different types of products and understanding their life cycle the life cycle of the internal activities the life cycles from your vendors that all matters okay so we want to make sure that that's synchronized there and it is foundational the next area that we see a mapping is around the um strategy portfolio domain and largely aligns to things happening in the design domain here in csdm so uh it's all those functional capabilities all those objects are usually managed there it's part of an enterprise architecture practice or engineering practice the next area to kind of mention is that digital product and strategy portfolio area also integrate with technical and business services and the portfolios of those business services the idea here being that you have to understand what those portfolios are and organize them appropriately and uh that evaluation a lot of the service mantra where service management came from is to understand how that customer to provide consumer to provider interaction happens and managing that to meet slas and understand price or showback the next area that overlaps is the service offer and the request of fulfill value stream so that really maps over to what we have as the request catalog and service offerings either technical or business and it's it4it doesn't make a distinction between that so we don't really care what kind of services as long as it has the supports these value these different value streams that are articulated and that you have an offering of some sort you formalize that offering in agreement with your consumers uh the next area that maps over is largely that detect to correct area where we have actual product instances these are the assets and the integrations between those axis and the configuration of those assets into an application service in our vernacular so this is uh where the actual instances are and application services and all the underlying ci types are what we discover and we make sure that we understand what that current state looks like when we're dealing with operational processes now the one thing that also to highlight here is the different types of offerings and in this case we have service offerings that are both uh for people internally or externally or machines digital products that consume your digital product and that would be typically integrations apis things that are connecting these digital products in some machine to machine interface and so the important thing that we've identified in it4itwork is that these digital products all work together in some way but there are they may be autonomous or part of a larger microservices architecture where they're integrated and loosely coupled so all that machine integrations are kind of another way to manage consumer provider relationships and we're proposing here as far as yt5t version 3 is like to be more formalized about that now when we started to create it4it version 3 we needed to define what a digital product was and so there's a white paper that's published that provides that definition and this is uh largely on the left-hand side where every digital product instance needs to understand the the contract basically how am i going to provide this digital product to my consumers so that way you see the different interaction methods that could be human or machine interfaces to other digital products down below however as part of your particular digital product instances you have systems and you have code and compute the various devices that might be actually involved information obviously that's stored and managed so all of those systems basically are part of that particular digital product portfolio and understanding how those products are are allocated to individual consumers they can be a device that you ship and you wear on your body like a smartwatch or those systems can be just a user uh record that you provide a human to be able to log in and interact with your systems and your backend systems and then down below that you have interactions with other digital products so the important thing here is that it is a dependency chain that digi one digital product has dependencies on on other digital products but also dependents that depend on those digital products so we this forms a long chain and a mesh if you will of interactions that's really hard to manage in a large it organization so it's important that we formalize this so we do instead institute contract language here where we define things like your slas price outcomes and and the other thing too as part of your digital product instance is you have shared resources and teams that are staffing these and the idea here is that uh if you go to a teams-based mode of delivery you have people staffing different positions on that team from development engineering support delivery staff and then we have some shared things in a large organization distribution catalogs might be one internal catalog everybody uses or it can be product catalog that is on your android so understanding all these shared resources and how these digital product instances are actually managed and mass you have to consider the shared resource implications and requirements as well so see how i t for it deal product definition maps over to csdm what we do is we have the main interaction here with the products and product models so we have different types of products in csdm supported software hardware applications and so that's kind of the main mapping but it also incorporates things that you would see typically in this technical or business service domain so we don't make a big distinction when we go to product orientation in these things and then one more thing gets absorbed here in the definition too it's the up business application so you see we don't necessarily have an application defined here in the digital product instance but we do have systems and systems corresponds to the application service and the interactions to your consumers corresponds to the technical and business service offerings so how do you provide those to your consumers what does that offer look like and what is the basic understanding of uh the systems that you have access to and in a management of the sla or olas now the systems will map best to the application service in this particular diagram as a matter of fact one of the things that i i commonly when i explain application services i have to explain it from a systems point of view because that's pretty much what it does when we do service mapping for example or you put create a diagram in the cmdb you're basically articulating the structure of a system a systems diagram and that's what app services basically does deals with and last but not least we have those systems that comprise of underlying resources now think of these are the resources that you own as a company and have to manage as part of that system it's not the interaction with other systems like an api or dependency of an app on a platform but it is the code that you have to manage or device that you have to manage whether it be on in your data center in the cloud or in the possession of your customer so all of that has to be understood so thank you very much for the it14 version 3 mapping to csdm version 3. hopefully this has been helpful