Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Tue Aug 29, 2006 3:18 am Post subject: Re: CMDB: What is? Who Make and What contain?
Please see my responses, embedded below...
1. What is CMDB?
A Configuration Management Database is a data warehouse that allows you to see the details associated with the entities you track and the relationships between them. It is the tool you use to manage your configurations.
2. How do I make a CMDB?
The building of a CMDB is a very complicated and expensive undertaking. Many of the requirements for a CMDB have been posted in other threads in this topic.
3. Which tools (Software) I can use to create a CMDB?
This is a vague question. Since an adequate CMDB requires so much, the answer to this can be very large.
4. What should CMDB contain?
All entities your enterprise needs to track as well as all the relationships between them.
I hope this helps to answer your questions.
Regards, _________________ [Edited by Admin to remove link]
Joined: Aug 11, 2006 Posts: 262 Location: Netherlands
Posted: Tue Aug 29, 2006 11:17 pm Post subject:
Regarding 4 (what should it contain), you should take the following steps:
1. Who are the users of the information in the cmdb?
2. Why do they want this information (how important is it)?
3. Define the scope: what kind of infrastructure do you want to register. If cmdb-users like the service desk from your department only support mainframe, than you don't have to register pc's. If they support the automated coffee machine, you also might want to register these machines.
4. Define the depth (and therefor: define the separate configuration items): if you have decided on the scope, and (as an example) you know you want to register pc's, do you want to register the monitor, the keyboard and the pc itself as separate entities in your database, or do you want to register them as one. The same question goes for software (every patch a separate entry in the db?), coffee machines etc. For an organisation with heavy graphical/video use, it might be usefull to even make a separate registration for a pc video card.
5. Define the atributes: What kind of info do you want to register for your configuration items (room, wall outlet, supplier, owner, user, price, mac adress, memory etc). Be aware: the more atributes, the costlier it will be to maintain the cmdb.
6. Define relations between configuration items. Which software configuration item is installed on which server? Which switch connects to which router? Which monitor belongs to which pc?
Especially with a succesfull #6 (relations between c.i.'s), you will be able to prove the importance and contribution of configuration management to most users of the cmdb.
Always remember that you should continue to ask yourself and other people involved what the costs and benefits are of defining and maintaining a cmdb.
Joined: May 09, 2007 Posts: 22 Location: Bangalore
Posted: Tue May 15, 2007 4:48 pm Post subject:
I suggest you go through the ITIL foundation materials once again.
Because the questions you have asked are basics and are very much there in the materials.
Start with Configuration Items, definition, attributes, relationship with other CIs etc.
Then go through Configuration Management team objectives, goals, functions.
Go through Configuration Management database thereby and then come back to Problem Management, Change Management and go through the CMDB dependence of these teams.
This will give answers to all your questions.
After the above, I suggest get back to this topic under this forum and go through all the postings under Configuration Management and you will be at par with the basics and a little more. _________________ Ranjith Raghunathan
ITIL Foundation Certified
P.S - Most of my posts are to understand the ITIL fundamentals clearly. So please excuse if not genuine answers to questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum