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 26, 2004 Posts: 3 Location: Powys, Wales
Posted: Tue Feb 01, 2005 12:20 am Post subject: HELP! Config Plan example
members... is there anyone who can share with me a completed Configuration Management plan please...
I am looking for an example to show to management and while there is good advice on creating one, the managers in question want to see an example of some else using one.... they want ot see one today and I cannot possibly get one written for their programme by 16:00 hours... any documents welcomed..
Joined: Oct 06, 2004 Posts: 77 Location: Bloomington, IL
Posted: Tue Feb 01, 2005 1:13 am Post subject:
tz746q
I posted this earlier:
Quote:
Begin by identifying critical systems (your continuity plans, annual report, business departments should be able to tell you what they are). You will then need to pull together two views or perspectives on the infrastructure. The first will be the "accountability" view. This will be a logical picture of who owns or is responsible for the various pieces of the infrastructure. Who owns the servers? Who owns the mainframe? By "owning" I mean whose head will roll if something goes wrong with that component. Identify who provides services to whom. Once you know the owners, start creating a logical diagram that shows who is accountable to whom. This will result in something that looks like a value chain. This will become the basis for your service chains.
customer----user interface-----business applications-----operating systems/mid-tier------back end hardware/network
Now you can create the second view. You may already have this in terms of topologies, physical infrastructure diagrams, etc. The second view shows the physical and functional relationships between pieces of the infrastructure. This will become the basis for your CMDB and and CI structure.
Now comes the hard part. You must overlay or map the first view on top of the second view. This will show you gaps in your ability to deliver services and to monitor your infrastructure. Anything that does not directly support your service chain should not initially be in your CMDB. In other words, your services provide the requirements for what goes into your CMDB and how your Config process works. Once you have an initial CMDB, just keep repeating the process, building on what you already have.
As time goes on, you will be ready for other processes.
Not sure this is what you are looking for but thought it might help
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
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
