Page 1 of 1

CMDB CI Status Tracking

Posted: Thu Mar 26, 2015 7:28 am
by cb122
I am pretty new to ITIL and COnfiguration Management, but am trying to learn the key concepts. I know with ITIL the 4th stage out of 5 relates to status tracking of CI's. I understand from asset management the general notion of the lifecycle of an asset. But I am struggling to see what issues / risks are caused if you dont have proper status tracking procedures in place for your CI's. what risks can you face with poor status tracking procedures of CI's? If any?

status is key field for other service management processes

Posted: Fri Apr 24, 2015 6:49 pm
by svinjam
This is how we use it:

We use status tracking to understand the actual state of a CI and when they are related to incidents, changes, problems etc - it helps do a better analysis on the CI.

Example: If a CI status is not in production, the approvals for that change might be different from a CI that has been deployed to production.

If an incident is reported on a CI - the status tells us if its active or decommissioned and users should or should not be using it.

For service catalogue - some of our services are automatically managed based on CI status - if something is decommissioned / not in production anymore - the service goes from published to inactive.

CI status is controlled by change management process to ensure right people are notified and right impact is assessed.

Hope that helps!

Posted: Sat Jun 06, 2015 2:38 pm
by Kranti
The biggest risk that you have in not maintaining this CMDB is you loose track of CIs and cannot analyze things in future