Talk:Network configuration and change management

Article title
Should this page be renamed "Network Change and Configuration Management?" This version and the current title are used interchangeably in most media about the subject, but "Network Change and Configuration Management" seems to be the most used version.Jeffreyahaines (talk) 20:08, 19 March 2009 (UTC)

Yes, it should.

Definition of Change Management:

Change Management: Coordinate and control all changes to IT services to minimize adverse impacts of those changes to Event business operations and the users of IT services

The goal of the Change Management process is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of change-related incidents upon service quality, and consequently improve the day-to-day operations of the organization.

So by definition, if I get a new laptop, would the NCCM be aware of that?

What if we replace our Fault manager with a new tool? Should we manage that change?

An NCCM certainly wouldn't track these things - remember, Change Mgmt is coordination and control of ALL changes to IT, not just hardware.

I've never heard of NCCM standing for anything other than "Network Configuration and Compliance Management", but it seems to be out there, perhaps by mistake?

However, I still wholeheartedly disagree with this definition.

"Change Management" is a process - the process includes things such as planning, continual service improvement, change advisory boards, etc.

"Configuration and Compliance Management" is a function that manages configurations (and compliance) to support an overall process such as change management Claytondukes (talk) 19:52, 26 October 2010 (UTC)