[Music] hi to this lesson we're going to cover the tbm council or atom version 3.02 and how it maps to csdm version 3.0 a little bit about tbm council or anthem the tbm council is a vendor agnostic organization uh yet it does have some background in aptio so it's something to keep in mind apptio donated a lot of their thinking and establishing this tbm council but it is largely driven by the financial modeling and things that you want to do from a financial management of it so some of the differences and similarities between csdm and atom if you think about csdm as a common model across our platform to understand digital products and services and how they're managed throughout their lifecycle tbm atom was really focused on that service model to understand finances in i.t how is that attributed to the business use of it so that was really the key coverage and driver the use of course of csdm is to establish what those digital products and services are and how they actually work across the platform and tbm core council and the atom model what we have is the primary use for its financial service management understanding where the finances are and how to attach your general ledger to the things you do in it and how to bubble it up to business the origins of csdm are relatively new in that they we came about in the 2018 time frame as a collaboration between servicenow product units and eventually was used by customers directly the tbm atom was largely a apto framework that became probably bigger than aptio and was uh donated or created as an agnostic framework uh because the the caveat there is that a lot of other vendors don't play within the tm tbm council but we see given the adoption a hard drive from customers to adopt the framework and we'll talk a little bit about that as well so we wanted to talk a little about what tbm council taxonomy looks like what you see on the left and the right these are the models that they provide the standard way of looking at these models now these are industry and vendor agnostic of course but the idea here is that the bottom part where you have cost pools you you identify those cost pools from where you spend your money and how you uh basically get get billed by your vendors and how things how money basically flows to your vendors and to different pockets like external external labor and then you you basically move that money up the ladder and you identify which it towers that money goes to and what products and services and then it kind of bifurcates into both a business unit and a capability perspective on the right hand side you'll see a bit more detail in how that money basically flows from that external general ledger all the way through the cost pools up to the various paths up to business units and capabilities now now the thing to keep in mind is that a lot of organizations when they do spend money and on things it goes into a general larger bucket and this is a bit of a reverse engineering of how money is spent back into um from from a from a financial peer financial point of view to it and back into the business point of view so it is a bit of a challenge to do this in practice but there is a framework for it and uh the thing that i think got a lot of executives excited about this is finally being able to have some visibility on where money is spent within it now how this maps to what we do and i and csdm is as follows and so the first thing that's really obvious from the top down is looking at the business unit and how that maps to the foundation's domain and cstm so that's almost a one-for-one mapping there we also have a very good strong mapping on the business capability viewpoint too so as a common point of view this is a good starting point for the mapping when you look at the shared services at this level uh the next level down which is business view you have a mapping to the business service over on the consumer sell side of cstm so that pretty much pretty much maps pretty well and they don't of course get into the offerings uh or a hierarchy of services so to speak but they do have uh support for those services the next area is the service delivery and now this is interesting because we have the delivery which is an ongoing consumption of technology if you think about it that way these are standard services and those mapped largely to those technical services down below that underpin many of those business services now there's another path we don't really account for in csdm which is projects and investments and this is labor that's changing things and that's something we don't have a direct mapping for now the interesting thing is the it towers largely map to the cis and ci classes that we have for infrastructure down below there's some i.t towers that we don't necessarily cover down here obviously like labor but this is something to keep in mind especially for cost of support uh aligning to those towers and how we basically set up those technical services and how those align to the various infrastructure that is being managed as well so that's where we make the connection between sort of the um the delivery services as well as the i.t towers down below the cost pools those cost pools generally come from the general ledger as it's shown in the tbm forum diagram where what what's interesting for us is that we have the product models and the contracts that cover those products that you use from vendors again it's not every cost pool like labor but it is a good start and i think there's a more pragmatic approach to how we rolled cost up using this information on a very mature csdm rollout versus trying to use the cost information from a general ledger so just something to keep in mind uh a mature csdm you won't need to take information from a deal and apply it in this way but the good thing is we do have a lot of the entities that map we just don't have everything on csdm such as projects and investments which would come from a ppm or agile type solution where you understand how many people are working on things thank you very much for your time on the tvm model mapping to csm hopefully hopefully this was a value