through service now and I think the concept this for someone is new to this you know this application the common service and is standard shared service we do had definition across of product and platform that will support us from service level reporting purpose and dat model and seal you know recom data model is Crow Sur products platform yes Ena support multiple config configuration strates this pretty high level but you know we always start look at from this blue plint diagram to understand um is dat entries mve to a subst powerform if look at the diagram this is a 4.0 uh de model pop serves now the 5 uh uh Z version is coming in next few months if you look this diagram you can see uh is in the data modeling basically defined by multiple domains and you the design build and manage Technical Services either know sell consumer at final stage then we do have foundational uh you know data Foundation of domain support of all data models but it you know for man portfolio domain is covered and each portion of each domain and you can see we have different Rule and use a persona for each domain list here they play pretty important role and to support and uses data modeling and this data modeling PR high level we call conception data mod models and uh each box we right now we I can we either call you know entity in object and because it's a conception models and uh uh the connection between each entity is relationship basically this model will help you to use relationship connect in all the and the object together in final business can consume you know your services but but how Serv now to map this concept model into the phys model in that case become part of same DB then we can be used next slides please yeah yeah I think that's a question a lot of people have is why do I need csdm and cmdb yeah you know the the one I show you first slide it's just like conception data model it's not part Serv now platform application yet and but Serv now basically use a con conception data model and you can see list here all the object then mapped over physical model of s platform and that basically it is one most in object one to one relationship is mapped to same same DB table and uh by accept application servers you can map to multiple tables you know after you maap csdm object into physical cdb table then we call you know you know csdm it no longer is object is is part CB of now we call logic CI is like a logical configuration item and but in addition you can see we do have uh some application like application in trct CIS that's basic part of CB application in service now and you know as instruct CIS U you know you map to multiple taes and when we start to in know SD project I think if you P you worked project same DB project before the first step is you basically use Discovery is Agent CL connector is a service graph connector try to put the data from is a A promise is a coud envir environment to PO data is is we call instructed data into same DB but but most conceptions you know um concept object can be ma one to one relationship at same DB but but not all them in same DB for example you know service portfolio is mapped to service portfolio table but it's not same dcis and uh request item color is mapped to you know you know S car table but not same de as well but this is important information we need to know um second one you know in we do see this Ty you know we have physical table for uh csdm will be able to populate SDM data and uh become part of same Deb but in in addition way you know how data can be relate to each other you know reference cross platform is important to connect user relationship this how service now H present csdm relationship predefined for us that's that's pretty easy you know for current samdb project you how you migrate to csdn you can see uh business application capability can map to business servers use certain uh you know relation type of data uh also you can use reference to uh from business application to P be applications basically can see two step um you convert from concept data model in from object to physical table then you define relationship between each csdm object on same DB tables that make the csdm application right in service now you can use but this now after we have the structureal mapping and how we pop the data you know we basically um in a traditional same DB we pop information for you know from Network and different environment different data source you we can use Discovery other tools and for example that's for instruct C applications you can automat get information popped in in SB goes through R engine but not for logic CI C csdm you know cdb information all this csdm uh you know logic CI need manually Define and populate in service now and basically the two step you know you can follow when we talk about you know how we Implement csdm usually we follow same process you define the diagram in conceptional model services and start to use this in basic information po all information we need but I want to notice something here is um is sdlc components and IC component using this table uh Rees data for for example product software part and for applications and instructions infrastructures uh and uh like a config files so you can see on this table and lot information relate to uh development details it all can be saved here but I like to mention here this is not operational CI what that means oper CI oper CI is means you can reference from instance change and F and use as service component CI and uh but but sdlc is not and uh in because every business application we is will not have you know some has SDC components but some not that's why uh the data U is not mandatory to be populated yeah this information uh I'd like to point here um as from this slides overall we just let's have two concept to remember we we move to next slides is uh instructure data CI uh we call you know we call instruct CI for C DB sayd MCI map to cdb table we call logic CI and because this information most them is logical layer of Thea the model next slid please okay y cool um we just mention in a pretty basic concept you know how you know conception model and service not be mapped physically into service not platform and the basically have relationship you can set up when you start use zdm application to build digital product and service for your organizations in the sub platform and but here is pretty example I call large digital product and service and basically make up from collection of CI there two type you know CI we just mentioned one is infrastructure data and the logic CI data from csdm then in addition from both the you know this application product as servers you reference to foundational data but I like to mention to here Foundation data is basic fun you know like a user group a CNB group uh a and uh all this basic location information be referenced from from infra C all services then the common service data is is all this you know SMD SDM logic C and they be cross be used in AC cross platform to support individual applications um this a pretty mature stage you know after you use csdm to define your own product and become service now product and become service you can be subscribed by either it consumers and business customers and how we GA is very important to know the termination in a a relationship between the logic CI and how they construct from um infrastruct thei through application service to support you know service and service offerings um that's we need to important need to know what is a business application all application service how they depend to each other and what is service service offering and how we connect them become one service through csdm relationship and after you understand their terminal definition the relationships na is a build Foundation you start to build your own and service model use CSD csdm csdm application then you then we can move to stage and how we you know what kind of approach to imp SDM um let's let's see the B application let's talk from start from bu application bu application is design view of application service and basically which is like application you can personal externally external or you can develop your own internal support your own business capabilities is line up with a business object to support your business need in organizations and application service is operational view of business application of a unique deployed inent remember it's instance of the business application you know which is logic view of the point application and system or recently you know we we also use because application may have Micro services for application in the hierarchies and when you start to build application service and sometimes ask you oh how many tier you have that's part how you build your micro services and let's give you example service now is application you know work day SCP and Oracle and Max all teams but come to application serves you have dependency serves now death upli service Serv not test Serv not QA and s of production you you can see we call different version instance on different environment that's how you can connect um you know from business application consume application service um come to technical service and Technical service all three um technical service is really like high level technical functionalities is focus on SE is more is it components infrastructure have be used to support application service and business service and example give to you here is like a database hosting service and basically provide infrastructure and management information necessary to for hosting in a maintenance Port database is used by you know different applications in your organizations but but that technal service may have dependency CIS like database servers storage networking and database measurement like software or also you can like a backup recovery or such such but sometimes the technical service tech service only have technical customer focus mean not for the business for example like L app um we Ms and this type of techn service can only be have service offering as you know can concerned by it customers but Technic service offering is details different package of technical service it basically associate with service commitment you know this this very important is when you have service you know technical service offering when is fysal customer basically you try to have you know contract like OA SLA you know like a commitment how we can support you know this service availability high avability for your customers all this information will be uh when you start build techn uh technal service offering that be part information we need to collect uh particular example I like to give to you uh like a you know Technic service offering uh like a virtual machine hosting service offering uh this offering can provide utilized you know computer resource you can run uh VAR you different applications and servers and which include different configuration you can convert to you know what you need as different environment for example you know development testing production environment such such another example I can give to you like you know um as Tech servers we can have like a Windows service but offering we can have window Administration and uh as techn service we can have like a network service then we do have S offering Network Administration you can that's how you know they connect others but important thing you need to know is techn service can have multiple Technic service offerings this one to many relationship um let's come to the business you know after we have of technical it functionality line up with technical service tech service offering uh you know constructed through instruct data through application service and then we start support business that is that case uh we need to start to Define business applications then offer different business offering to the business the the business service you definition is you know basically is a service we published to the business users and uh this typically can under the pay is the one and more business capabilities and the Business Service can be either used ordered by business users you can select deserved offering all service commitment level you know that's how we mention you know when you offer offering to the business is the techn you know customers and commitment of service a service availability is part information it's like a contract between you uh services and your you know consumer and then you can you know order and this type information through service C loog and uh Business Service offering you know particular example I like give to you like service application you know human resource you know we do have uh onboarding that's business service but we can have multiple uh uh offering for this service like Enterprise on boarding mobile onboarding you can see this whole Business Service mapped Business Service offering but also from Human Resource you know business application you can have another you know example I can give to you like a business business case that's is business casy support service as business servers it can offer different um you know hrk support like uh like a ER like a employee uh relationship and then we have seven b different you know uh HR Keys offering can provide through HR Keys um basically uh understand all this definition then next we say okay we understand this all informations how we link to each other to their based on their relationship connect each other build of connection from either from B application connect to the physical CIS then reference to foundational data next slid please yeah I just we basically go through all csdm logic CI how they relate to connect to individuals in trci and ref to foundational data how make that happened is we need to build a relationship use csdm relationship basically just predescribed by service now and you can this basically have information relationship form complete follow the data modeling in first slide we present you can see they connect all logic CI table and each other until end server hostings for example when we startop from business application you can consume application servers application service can be consumed by business application and from business bus up in a service perspect you can see service business service offering is Def is depends on application service then application service can be used by Business Service application then from application server we can depends on application connect to each other and runs on the server it's very important we has a Connect data through relationship from Top service to physical CI then when outage happen in server and uh then Ser outage will be in you know happen right away you can detect automate detect and impact to business service service offering can be automated triggered monitored and you can take action but another point I like to mention here is csdm is not only for cdb also is for Asset Management as well basically you know you use in taxonomy approach you know basically a product model you connect between asset and cdb you can see we M you know software model you can map to application servers is a one many to many relationship and the overall CI from C DB csdn and asset they connect by their life cycle status and for current version Washington we all already have automate connection try to in sync the life cycle between cmdb and asset csdm and but in next coming version all this information can automate in syn if you build your data modeling and you know we basically talked and the you know how we start you know CDM applications it's always start from conceptional data model that's is the blueprint you can use to map your service and then how do we use you know from conceptional your own mapping into s now you know csdm logic table that's is you can see that entries you know basically how concept entry to to the table we guide you to publ data then after you public data in you know each table relationship and we you know for example in application service is automatic you can connect relationship with is business applications you know you know technical service you know Business Service offering techn service offering this is will be become automate in know approach in service now uh yeah I think on this one at four slides I basically get Concept in know how assumtion works from conceptional to physical and then next slides we talk about you know uh the poll two next slides please well first we got a poll here we're going to take a little let you catch your breath there a little bit um we've talked a lot about csdm and you know obviously there's some challenges to getting it set up it's not the necessarily the easiest thing for everybody to understand so I have a poll here if you want to chime in on what are your biggest obstacles that you're finding as you are um trying to implement CSD and and there we go okay so poor data quality a lack of resources um yeah it looks like all of these look like they're challenges and um I also have a second question there if you have any other obstacles that I haven't listed that you would want to draw attention to and I sincerely apologize I forgot to get out of teams before I started the webinar here so I apologize for all of the notifications coming up um not sure what is um so exciting this morning um all right managing understanding uh weak governance they're all kind of chiming here while people are filling in the poll um we did have one question John about when csdm 5.0 will be released and I think you said it in a couple of months uh yeah I think the Ser some Mark already scheduled uh event to talk about version 5.0 I I think in next month I don't know exact date I did register myself if we found that link we can post here yeah we can add that to their the resources so I'm G to go ahead and end the poll here and let you carry on with your next topic okay which is obstacles yeah I I have you know just give some background my C DB experience uh why I had my first NDB project 10 years ago is all manual we don't have csdm application I still remember we manually map everything including relationship and the map is a physical table we call you know physical model and relation to the service um but but right now Sur not really matured basically you can see lot of information in csdm application already and if you really understand how their you know logic CI relationship how they support each other uh would be really good start but before we start yes like a you know always you got to start from C DB the basic data when you start same DB I think everyone you know you work same DB project the first how we poped CP data from different data source and uh uh Discovery is to most be used and you can use on prise and a cloud configure schedule and use your pattern to Discovery you you know uh as a device as possible to pop in know each cdb table and same table do have R and they from outbox identification rule is fully defined you can use however it because you have multiple data source and then for reconation rule how we you know eliminate duplication eer entries that always challenges and uh in addition uh you know we can you have connection issues you know how we pop the you know uh correct and you know attribute um then how we defined of you know some required field and how we scan some um the attribute is not part you can find from Network or is required you use can use you know data certification on schedule job to f information to keep data qu you know quality always challenge um that's why before you start you know just csdn and the first step is always in do cdb remediation that's how my project per in perform you few project I did I did you know I work for multiple comp in few companies uh not yeah not multiple companies few companies um you know we always facing you know data issues how we keep clean data uh if you don't do as I mentioned here because csdm is the map to ex your data to csdm standard table we call logic CI cdb tables and when you go through there then I when you connect to you know all the instructor CI data you will face a lot of challenges next SL next um okay I'm sorry there we go yeah yeah this is one I'm going to use um CB Health dashboard and this is you know we Ser now Prov us to monitor healthy of CNB basically they have the three kpis to monitor your health CB like a completeness compliance correctness and and each kpi has a matrix is a calculation to find you know the error for example duplication they basically we show you you know how many duplication record in your same DB it basic can click and go to record and fix the issues it's so convening for you know current service applications and the first step we need to keep this you know data kpi high enough have clean data you know you I said you know 77 97% will be a consider is healthy same DB uh you can move to csdm but rest 3% you can fix through your Operational Support and after you have this you know ready to go then you can start your you know csdm data modeling let's go to next um I just mention you know another big chall I did list here is the first step when you start csdm project you need map your service use conceptual data models and that one is always a challenge because especially when you come to application service and uh you may have some CH to see how we connect you know from technical service offering and uh then connect to application service and to support business service that that relationship is really is the key when you come to be you know before you even start collect data it yeah before we jump to you know that challenge I have some in latest slide to show you what kind of approach we should take to implement csdm but other challenge uh after you you know basically challenge I put here is you know basically is challenge how when you implement C SDM you can see governance and standard process I think I heard some feedback said we don't have enough resource and that because when you keep governance and we have like C owner you know supporting group approval Group Change group all this need be defined need a resource to support and the policy government policy ensure the data Integrity you know accountability transparency and that's why governance process after you pop the data and to support this you know this application and for csdm data or manage your product and services is very important but another big challenge is let's see you you pretty pretty in good shape you already built your C DB and uh basically all the governance then link to csdm you pop you know pop the csdm you have mapping together and ready to subscribe from business but another thing is this all required change in organization because you already defend right you defend all this sumon group assigned to CI it's huge it's like it's not like you know it's just like one people you can support everything that's clearly defined all the rule and we call use Pana in the in the first slides you know conception model you can see they play really important role for in each section domain of csdm that really the same DB that's why uh organization change always challenge especially for big organization you have you have different unit you have different location based on if you are international company right that will have big change as well next slide please yeah um we've got a quick poll here um because the next thing that John's going to talk about is um what value um you are looking for to get out of the csdm and while you're answering that um question um John we are starting to get a little tight on time we got about 15 minutes left here I do want W to get through the the value but I also want to leave some time for questions um so once we get done with um yeah let's TR try to um keep it moving here I'm sorry um this this is a very dense topic and it's very hard to cover even an overview in just 30 minutes um we definitely understand that um so uh looks like the the biggest value that people are looking for is improved the service um visibility and the mapping and then operational efficiency um but it looks like the poll has slowed down so let's move right along here to getting to the um the benefits yeah but I will spent a little time here and move to how to implementation csdm some approach I like to mention uh to the audience yeah basically you know after we have you service mapping ready for the service just use one use case like outage you know if outage happened and uh then on the server side like for example M server then serf out haveen application service that be triggered right away and automated create instance now instance will be aate map to you know server the D as well as business you know service offering and service and after instant create it that will be automaten notification to supporting team you can see this process maybe just like a one or two minutes and after you know we connect uh use you know this uh data modeling you know creat services but what's the benefit you B is the benefit PR like structional and uh uh if we OPP this cons you know a consistent model organization will really reduce redundancy void duplication effort really streamline your process and then you you can have more efficient Service delivery and ACC could identifi the instance and change on the service um then all this benefit list here uh I'm not going detail I want to move to next because I really want how to implement csdm and I think you know a lot of people may to that part um csdm s not have been recommend um you know stage approach basically SE now is divide into foundational uh craw walk run and fly and in the foundational stage basically we try to populate all the foundation data in a table this here after you have this data you know basically we can reference from service to all this data and start to uh build overall technical service and Business Service second Crown stage is we focus application table to build minimum data we need that's the entry of service might in basically you start build business application then how this in application rate application service and applications is that case uh even you're not mature stage in organizations it can basically understand uh which application has impact you know from you can reference from instant problem change then after this Foundation you can start get mure is connect from in a technical perspect it function function nties and then you define technical service you know through Dynamic CI group this very important I don't have time to explain for this one this basically Dynamic field category use the MDB group to allocate your CIS this is important feature we need to know in in know later from this state basically you are ready from technical functionality ities you can support it customers and up to this stage okay you become a wrong stage that means you're available to provide your it functionality support to the business and that case you need to Define your business how relate to technical uh service through service you application service and you have complete on this stage basically from Foundation CW walk and wrong are you ready basically you have all the services defined and uh you just need to create request card item to pop your serve to the business users uh I just highlight go through this process but if you want to go to detail step look at this one C MDB Service uh migration Playbook and use case example the you know the ticle block I just published three weeks ago in service of community and you can get detail information from there basically tell you each stage what do you need to do how do you build your data model as use case and uh it's then is you know you have all information need you can you know uh start inform says there uh next slid please next SL please can you click next one bri can you hear me oh yeah sorry I lost okay um AUD while so I hope is helpful to folks because most people are usually asking for a crawl walk run approach so um I'm hoping that'll be a helpful tool for everybody yeah we got about eight minutes left yeah just high level I'm not go through everything and just need to point on Dat model stage you know basically you know two step one is diagram data that's basically you like concepted you model Services the second one is dat map workbook that is basically connect all information together you collect for csdm next slide please oh can you move up yeah yeah basically you can see this yeah this is the workbook uh is oh yeah this workbook you can download from no learnings is Serv and published and from here this template I use to collect data to reflect the data model you your diagram then you can from here you follow the blog I published you can start imp your csdm I think uh let's end my talk sorry spent too much time yeah there too many information to talk there is just so much information to share about this so as you can see we do have some references that we'll share with you but I'd like to get through some of the questions here so we have about nine open questions so first up we have what is the difference between a service and a capability okay um this the service and the the capability if you go to you know basically we call business capabilities um then uh the capability information if you go back to diagram I can show you you can go back to slides the relationship that be clear to show you the echo up I get there sorry yeah yeah this one yeah this one uh I you know basically you can see um business capability us is last stage uh you input csdm basically you have the services ready to go you mapped through csdm model and uh then you can based on service you provided to you can Define the business capability say okay for HR service right we do have onboarding offboarding we do have HR case and you look at all this you know servic be defined then you can provide you know defin what is capabilities that belong to um I hope this answer your question okay um next up um if any relationships are not predefined in the csdm suggested relationship and we don't have the relationship which we want can we add a new one and how do we know we're adding the correct one yeah um that's a good question is that usually um you know on current data modeling in csdm level and you know we tried for Lo the prescript you know like you know relationship we defined here um if you have any is not defined here you can basically uh go to you know relationship table we call relation type that's is a table called uh says cdbc R in R table that's have all relationship can select and to map some unknown you know table is not predefined all right um Robert has a question here they um what are the strategies to aligning to the cstm through craw Ra Run Fly that can be done in parallel to where they already are today that is you know how do they continue working on their data as it is while they try to undo and realign the data and Mist they already made yeah yeah that thank you this is really good question is you know basically is this csdm is so big uh you know we don't recommend it just start all business unit Department all services we always start from one Department Bas unit and try to map to exceeding one application but but sometime it you know as we mention is some challenge is uh some CI data is not clean you always have challenge that's your question to go back to change but that impact is Big that's why we said before you start csdm make sure you have clean healthy cdb dashboard that's is a uh Foundation make sure you have and let you know limitate impact in the future csdm Pro implementation but so start from small and go direct then increase to you know to business unit and multiple department and after multi years this is not just one year project it should be ongoing effort yeah yeah um so another one was is the on slide nine we showed the relationships that must be mapped does completing all the mappings mean the completion of the csdm implementation um all the relationships that are mapped uh yeah basically you know the map you have two sections you can consider um one is you can show map here is instructed table uh in the device is discoverable from is you know different data source all this relationship is all the map themselves when you pop the CIS but and for for CS DM we call logic C and uh when you pop data for example application service you go to record there and you need to select you know the what is the B application what's the you know service offering when you select them relationship will be automate mapped by service now you don't need to Define which application type we should do and service not already done for you and another good question I think that came up here is what is the granularity that you have compon that you recommend going to you know I I recommend basically when you start csdm project you know um as I mentioned you know start small which is one business service and uh build your data model for the DAT you know data model I just put the first slid then the important things is you need really need to understand and what is application service all this SSM object you know how they support each other and you know we have two type of services right you know technical and business and you can see um you know you always start from technical perspect because the support by infrastructure eyes and um but you know start one from technical service and uh then gradually extend to business service that's my recommendation but start from small one then gradually go to more services all and we're just going to take one last question here because we are at time um can you just quickly uh explain how csdm aligns with DPM the D or is that something take offline DP uh DPN yeah fro do you want to elaborate on oh digital product management uh digital Prof management okay um yeah basically and uh uh csdm you know uh is is ifu is leverage uh from uh you know uh application portfolio management uh service portfolio management and digital uh profio management they all are line together after you and Define your services you have service portfolio you can manage then the final result is basically you create digital product let's come to digital uh portfol management you can manage I'm not going through detail in that but the Align up this is why csdm is very important it's line up to you know from application perspect your portfolio in the service portfolio perspect and the final stage you can line up uh dig product perspect and uh eventually all you need to use SDM to create your digital product that's how that I can but not detail yeah okay all right I'm I'm really sorry everybody um that we need to wrap this up um there's obviously a lot of great information that needs to be shared here and a lot of questions we'll try to get to all these questions in a Q&A document that we'll publish later as well as a link to the recording and a copy of the deck I want to thank you all so much for joining and being such a great audience um there will be a post event survey that'll come out when you uh when we uh close the webinar here if you'd be so kind as to fill that out because we obviously want to try to keep making these sessions better and better for you and also um hit the topics that you're looking for us to cover so again thank you for joining and we'll see you next time yes thank you everyone thank you bre yep