I often find myself talking to customers, peers, and suppliers who use the terms assets and configuration items interchangeably. They say that ignorance is bliss, but when it comes to management terminologies, it is better to understand the differences between terminologies than to look over it. In this article, I am
Incident logging is a somewhat straightforward activity. However, it is important to note that no matter how simple it may sound, organizations tend to go wrong in its implementation. In the third set of the incident management lifecycle series, I will talk briefly about the incident logging activity. To fully touch base
Most ITSM consultants prefer to start off the blocks with the design and implementation of the incident management process. Also, by hanging onto the low hanging fruits in the form of incident management process development and implementation, you can certainly prove your authority in the ITIL area to the customer. I
Process development and implementation is a skill that is best learnt through experience and maturity. Organizations implementing ITIL processes normally develop workflows, define activities, identify roles and embed all of it in a process document. This is good, but there is a major chunk that is still missing. The design.
I got a proposition from one of my customers. They wanted to have a single database containing asset and configuration details. In other words, they wanted to merge the asset database (ADB) and the configuration management database (CMDB). It is said that databases must be the single source of truth. So,
In a market research commissioned by HP to feel the pulse of IT professionals regarding the challenges faced with using and implementing CMDB and the level of implementation has thrown some interesting numbers. Around 100 IT executives were interviewed with specific survey questions. The respondents were primarily chosen from the middle