Another area that people find it difficult to differentiate is a configuration item and an asset. Some of us feel that both are same. I will focus this post on key differences between the two.
Asset has a financial value along with a depreciation rate attached to it. IT assets are just a sub-set of it. Anything and everything that has a cost and the organization uses it for its asset value calculation and related benefits in tax calculation falls under Asset Management, and such item is called an asset. Asset's life is for duration till its financial value becomes 'Zero', which depends on the associated depreciation rate. There is no relationship between assets.
Configuration Item or CI on the other hand may or may not have financial values assigned to it. It will not have any depreciation linked to it. Thus, its life would not be dependent on its financial value but will depend on the time till that item becomes obsolete for the organization. CI has a relationship. So from a CI all information on subsequent parent and child CIs can easily be obtained. Also, CI is restricted to items specific for use in live IT environment.
Let’s take an example that can easily signify the similarity and differences:
1) Similarity:
Server - It is both an asset as well as a CI.
2) Difference:
Building - It is an asset but not a CI.
Document - It is a CI but not an asset.
nicely explained. thanks a lot.
ReplyDeleteGreat simple explanation
ReplyDeleteThanks, been looking fr ths simple explanation.
ReplyDeleteNice and Simple Explaination. Thanks for Posting
ReplyDeleteGreat explanation. Thanks
ReplyDeleteVery nice explanatoin
ReplyDeletequestion, is business apps an asset or a CI?
ReplyDeleteBusiness Application can be a CI. It would definitely be a CI in case you are creating a service model starting from a business service to an IT service to IT components used to deliver these service(s).
DeleteIt may or may not be an asset depending on whether it has a financial value.
Hi, when you mention "CI is restricted to items specific for use in live IT environment", are you talking about production environment? or testing environments, development environments should be included in CMDB. And what should we do with DRP environments? Can we consider DRP infrastructure as CIs?
ReplyDeleteThank You.
It would depend on the scope of your Configuration Management implementation which has to be agreed during Planning phase.
ReplyDeleteIs there a broader way of classifying : When i am populating my CMDB what CI's should it contain. What is the linking between a CI and a Assest do they depend on each other.
ReplyDeleteHi Sumit,
ReplyDeleteWoud appreciate if you could clarify that why we wont consider "building" as a CI as stated in the example above. We normally do record location information in the CMDB.
Thanks.
Please refer to my post
Deletehttp://process-consultant.blogspot.in/2014/04/understanding-configuration-item-ci.html
I believe that this post would clarify all the doubts.
Happy Reading!!!
Regards,
Sumit
What a CMDB should contain is defined by the scope which further depends on planning and organization's business.
ReplyDeleteFor relationship between Asset and CI, please refer to my post:
http://process-consultant.blogspot.in/2014/04/asset-and-ci-relationship.html
Regards,
Sumit
Nice Explanation
ReplyDeleteKrishna
Hi Sumit, could you please share best practices document, a soft of road map, asset life cycle if you have
ReplyDeleteVery simple explanation with full clarity over this topic.
ReplyDeleteGreat Job Done !!!