The core of the change manager’s job in ITIL-based systems is to create protocols to handle changes in system configuration directly and in use. Changes can be subject to external manifestations as problems in the system. In that case, change management is a reactive process. Changes can also be implemented in an effort to improve system performance. In that case, change management is considered a proactive process.
In each event, this type of change can involve a new system strategy, an increase in a specific area in the system, a change in technology or a change in service perspective.
The New Strategy Seeks To Reset The System’s Focus
A typical example is the globalization of information systems where local area networks must be equipped with internet connectivity, a feature that will require more control to be incorporated into the system. Another example of this is enabling online bill payments. In both examples, the change manager must authorize and control the rate and manner in which remodeling of the system must occur so as not to push it out of balance. In other words, change management sets the standard process that must be taken if the need for change is felt so as not to interfere with the normal operation of the system.
Need To Be Upgraded Or Adjusted
Sometimes, one or more modules in a system need to be upgraded or adjusted to produce better output. After this need is identified by the configuration manager, it channels requests for changes to the change manager who then studies the implications of the revision to the current system stability. On the basis of his findings, he can recommend procedures for implementing those changes, can modify the changes or reject them altogether.
Moving To Technology That Is Faster And More Efficient
Often too, central management of the system wants to move to technology that is faster and more efficient. In such cases, the plan is left to the change manager to study. He then submitted his recommendations on how to make changes and the time frame in which these modifications had to be completed. He can also determine which areas in the system must be improved first. This is usually the management side of the system. New technology was introduced there before the effect flowed into modules that could be accessed by ratings and files.
Sometimes, the desired change must be made by performing services rather than anything directly related to the system itself. In that case, change management is asked to plan a phase in which improvements in employee behavior towards clients must be implemented.
Clearly, a change manager is a person who is aware of the interdependence of the various entities that make up the system. He considered all of these ties when spreading innovation in the system. Usually, everything is planned in a subtle stage that will not have far side effects on the system.