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.
Posted: Mon May 30, 2011 7:32 am Post subject: Tips for CI Control?
We already have the tools (System with Auto Discovery tool as well), naming convention, etc. Im currently in the need to create CI Control / Status processes and would love some tips from the pros. Anything will do, just enough to get ideas on how its usually handled.
Im worried about maintaining CI Status (in use by, stored, disposed etc) up to date with the way the CIs are being handled right now. Autodiscovery tool helps with everything except the CI status and the Asset Tag (label) which have to be entered manually. Basically, all workstations are received, deployed, handled, repaired and released to users by Service Desk. So I depend a lot on their work.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Mon May 30, 2011 6:18 pm Post subject: Re: Tips for CI Control?
kevo wrote:
Autodiscovery tool helps with everything except the CI status and the Asset Tag (label) which have to be entered manually.
Just for clarity, kevo, what is the scope of "everything" in your statement. For example, I doubt if auto-discovery helps much with relationships in the CMDB, but perhaps that is outside the scope of your question. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
I meant CI attributes. Software installed, Last logged in user, Hostname, Serial Number, RAM, HDD Space. Things like that.
Theres not many relationships configured in our CMDB as of yet, on a Workstation CI theres the relationships with software (some) and the relationship with the user assigned /owner. The latter being one of my worries.
Yeah, Its proven useful to some extent but like you said there has to be human involvement for the attributes the ADTool doesnt catch.
Ill have to work on a process for SD to help me with that. Im thinking since theyre the ones who have direct contact with most of the assets (mainly workstations) they should check that the CI information is accurate on our CMDB. In other words, every time they have to handle (repair, redeploy etc) a workstation, for example, they'd have to check the accuracy of the information on our CMDB for that specific CI.
Thanks and please excuse my English, its not my first language.
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
