what i would be covering is how the cmdb works in the platform because if we take all the item modules the cmdb forms as a basic part for everything because the data comes in and we utilize that data so first thing is we have something called identification reconciliation api that is coming along with the platform and that is part of cmdb and all the other modules in item makes use of this module to keep the cmdb consistent so that is the first thing that we will be looking first and then uh next we go in a flow so once we understand how cmdb works uh probably we'll look into couple of scenarios uh something like the cmdb health and how the data comes into cmtp and how do we keep it consistent so that is the first thing we need to understand before starting the item modules so i'll be focusing on that for the first three days or first three sessions uh let me put it in a harley basis so i i will need three house to cover that and to start with discovery again what we will be doing as part of discovery is uh as of now we will be discovering our own laptops so when i mean that uh let's say abdul wants to discover prague's laptop he can do that we will discuss about how we do that and when we discover that how is the data coming into servicenow and can i get additional data apart from what discovery is switching so we'll be using pattern for that so that we can do it with props and sensors but protein synthesis has become legacy but it's not like it's not in use probe senses that are still in use but we'll be focusing more on the patterns part even if you guys want we can achieve the similar functionality using probes and sensors we'll discuss about that but in case if there is a specific need for any one of you to learn more in depth about processing stuff we can do that also so as part of discovery once we understood how the cmdb works uh basically taking it around two to three hours we will be starting our discovery we'll try to discover the other participants laptop or whatever device that is and then we'll work on the pattern to fetch additional details so that is where you will get a basic understanding about how pattern works and then we move so to do this again we need anywhere around 8 to 10 hours so accumulating cmdb and discovery it may take anywhere from 10 to 12 hours and then we switch into service mapping as part of service mapping what we'll be doing is we'll install some dummy applications so when i mean dummy uh what we'll be doing as part of service marketing we are planning to map an application so what is service mapping first step so basically every organization will want to reduce the number of incidents that is happening for their particular application let's take an example so there is an internet service provider abc and i am using that internet service so when the internet services go down when let's say the model is on but i'm not getting internet what i will do i'll first i will just open the abc app to see what has happened or to register complaint what will happen is as soon as i open the app i'll get a pop-up message saying that we understand that your internet is not working and there is a ticket already raised we are working on it so this is the level of automation we will be able to perform if we have service mapping and how do we do that again that's a custom application that will send some data to servicenow and that is called events so that is where even management will come into picture so when that event is received by servicenow servicenow will understand that okay uh i have received an event from a third party application saying that this internet service is down so that is handled by the third party application it is inclusive enough to understand as soon as i open the app it tries a ping and if internet is down it says okay your internet is down i'll write away raise a ticket for you you don't have to race for me and that is where the event is sent to servicenow and that's where even management comes in picture so we filter the event and we create a alert using an alert we can create an incident so that's internal number will be sent to the third party application saying this is the ticket number for you so uh again when will the service mapping come into pictures let's say this server uh so the internet services has gone down in colony one uh so i need to know exactly what is the dependency now where is this call mean colony one located what are all the other uh so i i have to go uh in a upstream now i have to find out uh where is this colony one connected sum which is the server providing this internet to me so all those i can build it as a map if i have it as a map right away whenever an alert whenever an event is coming into service now it will directly pop up showing that this is a service that has been impacted we can calculate the impacted services what are the other services impacted and what are the underlying operations that will be impacted because of this so this is the uh major end solution that a customer will look forward when he is working on uh discovery service mapping and even management so this is the flow we will be going in uh first cmdb discovery uh from 10 to 12 hours then we will pitch into service mapping service mapping we will focus on uh building a map for authentic application application and then we'll go how we can create a specific class for it and initially we'll do a manual mapping and then we'll do a dynamic map by which if i just give the url the map will automatically change it and to do that we'll work on the advanced customizations of the patterns so all these things will be doing in your personal laptops or in your personal machines so again once uh we are done once we are in that level uh again that will take around 10 hours uh 5 to 10 hours anywhere between 5 to 10 now it depends upon what level of uh customizations we are doing on that so basically uh we would be uh just building a generic or a dummy application we'll be downloading a dummy application and we'll be trying to map that so again let's let's uh assume that it's a eight hour session so again 20 has almost done till service mapping and then we'll move into even management again in even management we will see how an event is coming into servicenow how we can process it how we can automatically allow an event to create a incident for us so again that would take around three to five hours so to cover all these things it will take me anywhere between 20 to 25 hours and these are the topics that i would be covering as part of our sessions so the ask from my end would be uh to have uh i hope we have paris available right now so probably we can take a paris and then make sure that you have activated discovery service mapping and even management plugins so to start with again we will be focusing in the initial sessions with the cmdp that is uh that will be available as part of as part of the platform but going further we may need an instance your personal instance with these plugins activated so this is the ask from my end and this is the agenda i have and for this session uh whatever topics that you guys want me to do a demo uh feel free to ask me we can discuss about that but before that whatever that i have said so far if anyone of you have any questions do let me know we'll discuss that and then we'll jump on to a quick demo a quick question from my side so in the same tv part you mentioned you we're going to talk about the bare outer box cmd tables that are there the ira engine right so are we also going to talk about out of box dashboards which are there the health dashboard yes yes yeah i i will definitely give up a basic idea about how that works we will also see how we can remediate a duplicated ci so again that i will take help from the dashboard to find out which via is a duplicate so just just a straight uh forward overview on the dashboard and how it works and how we can remediate all those things great thanks uh balaji like uh what amount of networking knowledge and as well as javascript is needed for uh item okay uh networking knowledge whatever that i would be discussing as of uh our training that would be sufficient but if you ask me uh the terminologies that we would be using uh is mostly credentials and then we'll talk about tcp endpoints what is endpoint and then ip address subnets these are just some common terminologies you don't need to have a mastery of networking if you just know what is a subnet what is what is the end point that is fine okay and uh of javascript yes uh mostly uh the discovery service mapping and event management works out of the box then i mean out of the box you don't need to customize anything until or unless there is a need and there will definitely be a need because customers are always like that they want magic to happen so you will definitely be in a phase where you need to work on it so comparing to the basic development activities that we do in servicenow that basic level of understanding is needed here so mostly uh from my point of view again uh we'll be doing uh some customizations in the pattern level and those are if you see it's a low code no code environment pattern is a local noken environment you don't have to script there all you need to do is at a higher level you need to know how a regular expression works that your expression is a passing strategy because we will need to pass whatever information that the pattern has brought up for us and to do that we can do there are various methods again if you're not comfortable with regular expression you can do a different way we'll discuss both of them but it all depends uh the platform level of basic scripting knowledge is what will be required in order to work on this and that too in case if you are at a place where you need to perform customizations okay we'll discuss about one or two use cases on that and probably that will give you some idea about it okay by any chance will you be touching the orchestration piece or is it completely it is as of now autoscope as part of this package we initially wanted to cover up cmdb discovery service mapping and then even management so of course it is part of uh adam but as part of our training modules we want to test facebook and then go further with the different uh specific module based training sure yeah on a higher end uh it would take anywhere between 20 to 25 hours to cover up all these topics and again uh we'll discuss about all this before during our first session i'll share my agenda about what or all in specific we will be discussing again i don't have a device agenda this is going to be a computing agenda uh so we'll be uh discussing all those but on a higher level this is what we will be doing and for today uh whichever topic that uh you guys want me to demo uh i'm happy to show you uh if you ask me we can discuss about cmtp i see a couple of people here that are at a beginner level so i would recommend anything from cntp that we can discuss yeah okay great um i see another participant here prashanth hi prashant okay can you hear us no worries the session is recorded i'll make sure this is shared and yeah to start with uh about cmdb uh again uh we all know uh at least the cmdb is part of a base platform it is closely integrated with each one of the module so that's why we call it cmdb as a base table apart from task so one thing biology like by your voice is some uh sometimes audible and sometimes not like uh can you please uh um make sure like your voice is very clear yeah yeah sure please stop me if that's the case is it the same for everyone no it's fine by me okay no problem if if it repeats again uh ravi uh i would recommend to uh reconnect i would ask you to rick but yeah if if it's fine for everyone i think the problem should be from your end see i'm not i'm able to listen your voice but uh sometimes it is the words are not audible okay no problem please stop me if that repeats again uh maybe i'll try to connect again otherwise we can do straight away okay wait um that's it uh to start with yeah i was talking about cmdb uh cmdb again is part of the platform uh and when i mean platform again we have to base table i'm on a stash and the other one is cmdb and when i say that cmdb being a base table it is closely related with each and every module and we talked about an example about uh internet services and to quickly talk about that uh let's say when i create an incident again whenever i am about to create i can see that there is a configuration at a minute again it is pointing at the cmtp and it can be directly related with the cmdp tables again it is not just incident we can see it being available in all the other tables also wherever that it is related to let's say if it is going to be a problem if it's going to be a change and all these things and whenever we talk about cmdb and other things there is another table that is closely related to this that is nothing but a set so cmdb and asset are closely related to each other and even though it is not related to this again it is a part of a specific complete training available for that is asset management but it is always better to understand what happens when you create a ci so there is a specific condition set out of the box whenever you create a ci an ss gets created whenever you create an asset a ci gets created so what is the difference between them so to understand this you should know the life cycle of them what is the asset life cycle and what is the cmdd lifecycle so let's take one example so i have an organization called xyz and i am about to hire 10 employees and i need to provision them with 10 laptops so what i do before i hire these employees i procure those laptops so when i procure those laptops again where where can i do that service request so let's let's all uh consider that everything is happening inside the system so as a owner of the company i go and raise a request i create a service request because i want everything to be in the system so i raise a service request for 10 laptops and that service request what will happen it check if the laptops are available in the inventory if it is not available in the inventory a purchase order that is a procurement order uh will be placed and a specific team has to go and purchase them so when the purchase if it is integrated with a third party procurement uh system something like uh just for an example an amazon or a flipkart it will get the purchase order ids also so this flow happens here and when it is purchased it is kept in the inventory at this point of time these 10 laptops are called as an asset so what happens to this asset so i have procured it and right now it is in stock in the inventory and i have hired these 10 employees so when i provision these laptops to them at that point of time those employees start using those laptops for my company related works so at that point of time the asset life cycle takes a pass and the cmdp life cycle it enters into the cmd lifecycle because only operational items we can call it as a ci and things that are non-operational they can uh consider them as a asset and when i mean non-operational let's say i procure a chair if i'm not using it that chair is non-operational only when i use it that becomes operational so this is the basic difference and only when it is operational i'll be able to create an incident for it let's say i don't have i uh let's say i have my keyboard not working my keyboard is not working what little i'll go and create an incident and i can create an incident for only operational things so this is the difference between assets here textbook definition asset is something that has financial values and configuration item is something that has technical attributes to it attached to it so this is the textbook definition but to understand clearly the difference between an asset and a ci assets are not something that is purchased and kept but it is not operational and cas are something that are being operational and what happens then let's say the employee is leaving the organization then what happens that's it sorry the laptop which is a configuration item it is either disposed or it goes back into the inventory so that it can be provisioned to another employee so this is the basic relation between the asset lifecycle and the cmdb lifecycle and the difference between a certain ca so asset lifecycle just takes a pass when it becomes operational and when it is not operational the cmdb life cycle is entered there and it goes into the asset lifecycle so again out of the box there are many uh there are a couple of scripting clues and business rules that keeps an asset and a ci in sync so to talk about that we have asset ci field mapping these are responsible for field mappings between asset and ci and there are script includes that keeps an asset under ci in sync so a certain c a synchronizer so it takes the value from all these tables accidents a field mappings and it maps between an asset and a ci but yeah it's all uh the script it will take at least a couple of days to understand but on a higher level this is a script that will be called every time whenever there is an update or insert happening in either asset or ci so yeah this is about that and that is a specific condition again we can look into either one of the tables to check that let's go to the cmdb's business rules and we have a business tool here create asset on insert so whenever there is an insert in the cmdb table an asset will be created but not every time there's a specific condition for it similarly vice versa that will be a business rule in the effective so this is the condition all about it just checks if the specific model model categories and the type ci type all those if there is no if there is already an effect and a specific facilities for them and then it calls a specific business rule so this business rule is not accessible for us but yeah it's part of the platform only those specific conditions and those specific tables only for those it will create an answer so this is about uh how an asset and ci is kept in sync and how this works in a higher level there is again a specific training agenda uh to understand how the effort works what all the type of integrations and other things that is involved but whenever we are talking about cmdp and whenever we are talking about discovery we should also be concerned about the asset creation because as part of cmpv and discovery we will be populating data into cmdb and we should know what else is happening apart from the scope of what we are doing so we should be aware that this whenever there is a creation of a new ci an effort a relevant asset will also be created so yeah that's pretty much it i wanted to discuss so yeah uh regarding to this if you guys have any questions you can uh we can discuss about it but this is how we'll be taking further uh from our trainings so we'll start with any queries and then we'll start with a recap of our previous day session and then we'll go into the session and at the end of the day uh we will again once we are done with the session we'll do the labs and queries if time permits will talk about the queries or else the next day we'll discuss about that so this is how we'll be going and yeah i'm open to questions now uh and probably uh yeah my understanding is we are starting this by monday but yeah you guys have any questions or anything else to discuss you can talk about that but this is all i have for today the practicals which means the wrap which we do is through our laptops or else you we will be given uh when it comes to discovery we will be given any other uh servers uh as of now i will be doing uh within our own laptops as well as the participants recently like a couple of months back there are a lot of policy changes and uh currently we don't do it with servers okay will it be also be setting up and installing the mid servers yes yes we'll be okay and uh how many hours are we um sorry go ahead yeah so that's what like let's say uh what we'll be doing is we'll definitely be setting up the mid server but let's say if ravi is installing mid server in his laptop but he will give instead of his personal developer instance id he'll give your develop uh your instance id so you will be able to discover ravi's laptop so this is what i have it planned for the labs so that we'll be able to discover a remote machine sure does that make sense uh so how many hours are we talking about every day is it like two hour session or is it a one hour session as of now i have it uh planned for nhar and 25 has 20 to 25 hours at max is the completion time i'm looking for here but again we do it in a very flexible way the timings and agendas everything can be discussed with the organizers so my understanding is we are going to do this monday 8 00 a.m to 9 00 a.m one hour for now but it depends upon the participants here depending upon your available timings your comfortable timings we can make it two hours per day let's say 7 a.m to 9 a.m i'm fine with that but yeah it depends upon everyone's opinion how you feel comfortable and how the organizations fit to it sure and is it a pretty straight week days or are we talking about weekends as well um we can do weekends again if depending upon everyone's availability if everyone is available we can do it over weekend and we can continue it over the weekends also but if the participants let's say are not available or not comfortable over weekends then we'll be forced to do it over a week basically got it thanks okay so any more questions or are we good here no i don't have any questions about it okay so that sounds great guys uh i will discuss again with the organizers and they'll inform you about when we are starting this and what is the comfortable timing for everyone to get this session started so thank you thank you all thank you very much uh thanks milima please take it forward from here yeah sure thank you yeah thank you