CMDB Classes and Relationship Info

[Geeky]

Hello Pals,

Can anybody share the detailed meaning of each class and the attribute details? I am also looking for relationship types in CMDB with their meanings. I have searched wiki page but couldn't find any specific details.

What I am looking is; Let say there is a calss Server

Server : Stores the information about the server

Attributes of sever class

1) Name

2) Host Name

3) Serial Number etc

Kind of data dictionary for CMDB with detailed information.

Regards,

Srini

[postwick]

ERM4SN - Table - cmdb_ci_server «Server »

You can just use their demo, which refreshes against the ServiceNow demo system every night, or pay for your own subscription and have it show you the schema of your system.

[Geeky]

The link is providing the list of classes, their attributes but I am looking for the meaning of each attribute and the class, types of relationships. Which CI should go to which class and what relationship is should have?

I know that classification has to be based on my company's policy but Service Now CMDB should also enlist or provide a data dictionary for reference to categorize the CIs. I make sure must be something which I am not able to find.

Regards,

Srini

[Ed Laar1]

What we do to put ci's in the correct ci-class is the following way of working:

• Every CI (at least most of them) are categorised by the ci manufacturer so the ci manufacturer has put the CI into a certain class (like server, netgear, software and so on). We follow this guideline. Why: Because this prevents us from a lot of discussions with users.
• We do not use all the ci-classes as they are avialable out of the box: We use a CI class (example Computer) and we put all the CI's referring to a computer in this class. But we added an extra attribute to every CI: Category. Example: In the class=Computer, Categories like Desktop, Laptop, Notebook and so on are there. This prvents us form a lot of 'almost equal' ci-classes and the categorisation is for almost every user a logical categorisation.
• How do we put a CI in the correct CI class and in the correct Category within the Class? We added again an attribute to every CI called 'Product Model'. In the Product Model table, we register (how logical) the Product Model number, Product Model name, Manufacturer and so on an also the Class and Category within the class. As soon as a cmdb administrator or our ci discovery toolset wants to add a ci into the cmdb, a check is done on the product model of the involved ci. Without a Product Model is is impossible to create a CI. A check in the Product Model table determines a) the class and b) the category of the ci to be loaded into the cmdb.

One remark: This way of working is almost (!!) perfect but is not out of the box anymore. As we are trying to move from our tailored discovery to ServiceNOW discovery, perhaps we have to move backwards to the ootb ci-classes. The mechnism which used product model to determine the correct class will remain as foreseen now.

Im hope this helps,

Ed