For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Joined: Aug 11, 2006 Posts: 262 Location: Netherlands
Posted: Wed Dec 06, 2006 8:42 pm Post subject:
Hi Matt,
Have you already gone through the first steps of config:
1. determine scope of cmdb
2. determine depth of cmdb (config. items)
3. determine atributes of items
4. determine relationships between items.
While doing this, you should "somehow" run into the question of who will benefit from your cmdb, and what it costs to maintain it. Also, decide whether you want cmdb updates to be done centrally or decentralized, as this will influence the design of your process. Your management will most likely have a standpoint on this matter that you have to take into account.
Joined: Sep 16, 2006 Posts: 3110 Location: London, UK
Posted: Wed Dec 06, 2006 9:32 pm Post subject:
Matt
Remember that Configuration Management is related to Change and Release
In my opinion, the 3 go together like a Full English Breakfast . As such, if you do all 3, the combined objective of the three is
1 - to know what IT assets you have and control them (Config)
2 - manage any work done to the IT assets so the impact of any work is minimized (Change)
3 - when there is to be work on the IT assets, it is done in a planned well thoughtout manner. (release) _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
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