Joined: Oct 06, 2004 Posts: 77 Location: Bloomington, IL
Posted: Tue Nov 30, 2004 12:56 am Post subject:
Bottom up approach: Start from infrastructure architecture documents. Use topologies, diagrams, etc or an existing architecture strategy/plan and convert that to a Config plan (internally/technical focus)
Top down approach: Identify/define services, negotiate SLAs, identify CIs needed to deliver those services and build your Config plan based on your service delivery (externally/customer focused)
I have similar requirements in that I'm a Problem Manager moving over to a Configuration Manager role in an organisation that has NO Config Management or planning whatsoever. I realise the need for a plan however I've never seen the format or content of one. Any direction or pointers to a site would be appreciated.
Joined: Sep 22, 2006 Posts: 9 Location: Plymouth, UK
Posted: Tue Jan 16, 2007 12:37 am Post subject:
I was in a similar boat to your guys, but an now loading information into our CMDB.
I started with what I knew already eg Details of mobile phones, laptop users, software etc and then built up from there. Remember that you can do everything, its better to take a small chunk and get it finished before moving on.
I am now completing server information so we have gone from a bottom up approach, but in retrospect I think its easier to start at the top and work down.
Its also a good idea to write down what you want CM to do for your company or department and go from there.
I think if I`m honest there is still a lot to do, but once you sort it in your head and get it on paper its a whole lot easier.
Joined: Aug 11, 2006 Posts: 262 Location: Netherlands
Posted: Tue Jan 16, 2007 6:42 pm Post subject: Re: Configuration Management Plan sample
I am trying to pull together a joined up Configuration Management solution for a very diverse area that covers ITIL related services and old fashion software teams.
I am looking for a sample of an ITIL Config Plan so I can see what, if anything differs.
1. Start with "why"
> Who benefits from a good cmdb (who is your sponsor)
> What are the costs of maintaining it (and who pays for it)
> How do costs and benefits compare?
2. Design your cmdb
> Define scope: will you include mainframes? copiers? software? vending machines? PC's? Printers? etc. (you might call these cmdb-categories)
> Define depth: what will you register as CI's within each category? (for instance: the PC as a whole, or seperate entries for monitor, pc, keyboard etc.
> Define atributes: what info will you register on CI's? (type, manufacturer, owner, price, tech. info etc.). (especially here, it is important to look back at the "why", as the level of detail influences the cost of maintaining your cmdb)
> Define relations between CI's (this is what makes your cmdb a cmdb, it gives added value on info output to other processes). Example: software x on server y.
3. Design your process
> Some important questions/issues to consider: centralized versus decentralized maintenance of your cmdb? use of asset inventory tooling? Communication to workfloor! Management support!
Posted: Fri Jul 06, 2007 6:35 am Post subject: Re: Configuration Management Plan sample
I am also curious about seeing a sample Configuration Management plan.
While I understand and appreciate that each plan will be different for each organization, it is often helpful to see a doc or pdf that has already been constructed with the appropriate material content. This is especially true when that content is organized in a manner that would be considered consistent with the best practice expectations.
Such a document does not need to be exactly as described by the ITIL chapter on Configuration Management, but something closely resembling what has been outlined there could prove to be helpful.
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