Home / IT Governance / ITSM: More Tips to Do Configuration Management

ITSM: More Tips to Do Configuration Management

Configuration management is the secret sauce for greater success in IT service management, and for the business in general. In a guest post for Joe the IT Guy, Rebecca Beach elaborates further on this discipline and explores identification, control, status accounting, and auditing.

After there is a plan for configuration management in place, step two is ready to commence: the identification and baselining phase. This phase takes a photograph of your infrastructure so that it is crystal clear what the organization has and where precisely it is. This baseline can be used as a tool for comparison. It is absolutely essential for there to be agreement about who can update the configuration management system (CMS)/configuration management database (CMDB) during baselining so that there is no overreaching of authority.

The next phase involves gaining control, which means administering change management. Configuration management and change management go hand-in-hand because at any moment the CMS/CMDB could go out of date. A proactive behavior could be to simply add a step to the change ticket that ensures the CMS/CMDB is updated before the file on the change is forever closed.

Status accounting is the step that involves analyzing the configuration management capabilities against the previous baseline. The phase could include stages such as: planning, order raised, delivered, test environment, retired, or disposal.

The final aspect is the verification and audit. This precautionary step ensures that what exists in the CMS/CMDB aligns with what exists in real life. No matter the size of the organization, there needs to be a solid plan established for auditing. Spot checks on critical services should be conducted monthly, and a full audit should be completed yearly. Additionally, there should be a log developed in order to keep track of actions. The log should include information regarding the date of the audit, service, task to remedy, due date, and status. Any configuration audit will ultimately ensure that all configuration items (CIs) match with the documented CMS/CMDB and that documentation supports the CIs.

You can read the original post here: http://www.joetheitguy.com/2015/12/15/configuration-management-part-2/

Check Also

Strategic Incident Management

What truly lies at the heart of incident management? And is it possible to still …

Leave a Reply

Your email address will not be published. Required fields are marked *