Posted: Wed Jun 14, 2006 2:28 am Post subject: Why is ConfM a process?
In reviewing all IT processes that we need to develop, I find that ConfM is a rather minute area that hardly calls for the identification of a process.
ConfM assures documenting the configuration, so good administration is necessary and maybe some way of retrieving the info (for IM or for reporting on the architecture). I would only create a work instruction for a CMDB administrator how to add CIs or administer the categories, no more.
So why do we call it a process?
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