Home    ITIL  Index

Accurate Configurations -Technology Alone Isn't the Answer

Change management is really the heart of configuration management, writes ITSM Watch columnist George Spafford.
Feb 7, 2007
By

George Spafford





The idea behind ITIL’s configuration management process is to have a logical view of the world that IT supports. This means understanding the hardware, software, documentation, people, services, facilities and how they relate to one another.

The desire is for an IT person with appropriate authority to be able to access the data and understand, for example, what hardware and software make up a given server? What component configuration items (CIs) make up a service and how they relate to one another.

Having an accurate and timely understanding of what is in production is vital to everyone in IT. So much so that many groups are rushing to implement automatic tools that promise to discover new and changed systems on the network.

Like any tool, these automated systems have a time and a place but groups must understand the causality of their configuration management concerns before simply buying one of these tools and putting it into production.

In principle, these automated tools scan the network and/or monitor network traffic on a defined interval and can then load their findings directly into the configuration management database (CMDB). The premise behind these tools is configuration management takes a lot of work so why not implement systems to do the mundane data collection faster and more accurately.

The siren song is that by implementing these tools the vital configuration management data will finally be accurate and current for everyone to benefit from.

The issue to consider is why isn’t the configuration data accurate today? Is it due to data entry error or because people aren’t recording the changes to the infrastructure to begin with? In some cases there are errors with the recording but the bigger problem relates most likely to uncontrolled changes in the form of new systems and changes to existing systems not being recorded into the CMDB.

Change Matters

Fundamentally, what groups don’t realize is their challenge isn’t with configuration management. It is with change management. Change management is the process by which an organization implements the necessary procedures to control changes to production and thus manage risk.

It is very important to understand that change management governs configuration management — nothing should change in production, or the CMDB, without an approved Request for Change (RFC). If production is changing and nobody knows about it, then this is a change management failure — not a configuration management failure.

Systems don’t magically change overnight on their own. Somebody changed them for some reason. If a service is important for an organization to know the configuration at a moment’s notice, then it is important enough to be governed by change management so the question “What changed?” can always be answered.


    1 2 >> Last Page


Comments  (click to add your comment)

Comments

    Name or nickname

    Email address

    Website

    Write comment
    You have characters left. (Maximum characters: 1200).

     


    IT Management Daily Newsletter




    Most Popular