Configuration Management (CM) - Revision history

User at 13:18, 31 August 2023

2023-08-31T13:18:59Z

User at 23:02, 7 December 2022

2022-12-07T23:02:24Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T14:48:19Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 14:25, 19 May 2020

2020-05-19T14:25:51Z

User at 13:19, 7 September 2019

2019-09-07T13:19:05Z

User at 02:27, 7 September 2019

2019-09-07T02:27:17Z

User at 22:14, 6 September 2019

2019-09-06T22:14:36Z

User at 22:13, 6 September 2019

2019-09-06T22:13:27Z

User at 22:04, 6 September 2019

2019-09-06T22:04:23Z

User at 22:00, 6 September 2019

2019-09-06T22:00:21Z

@@ Line 92: / Line 92: @@
 == See Also ==
-[[Configuration Lifecycle Management (CLM)]]<br />
+*[[Configuration Lifecycle Management (CLM)]]
-[[Configuration Management Database (CMDB)]]<br />
+*[[Configuration Management Database (CMDB)]]
-[[Configuration Item (CI)]]<br />
+*[[Configuration Item (CI)]]
-[[Product Lifecycle Management]]<br />
+*[[Product Lifecycle Management]]
-[[Enterprise Resource Planning (ERP)]]<br />
+*[[Enterprise Resource Planning (ERP)]]
-[[Software Development Life Cycle (SDLC)]]<br />
+*[[Software Development Life Cycle (SDLC)]]
+*[[IT Maturity Model]]
 == References ==

@@ Line 97: / Line 97: @@
 [[Product Lifecycle Management]]<br />
 [[Enterprise Resource Planning (ERP)]]<br />
 [[Software Development Life Cycle (SDLC)]]<br />

← Older revision		Revision as of 14:25, 19 May 2020
Line 1:		Line 1:
		+	== Definition of Configuration Management (CM) ==
		+	'''Configuration Management (CM)''' is a continuous process of recording and maintaining consistent and reliable records pertaining to an organization's hardware and software composition, including software version control and hardware updates.<ref>Defining Configuration Management (CM) [https://study.com/academy/lesson/what-is-configuration-management-definition-process-tools.html Study.com]</ref>
		+
		+	Configuration Management is typically identified with managing the software configurations of network devices. It addresses the following kinds of practical questions: What features are to be enabled? What addressing and routing configurations will be supplied? How will the configuration be maintained? How will a configuration be restored? However, configuration management also covers several other topics. These include:
		+	*Inventory Management: Inventory Management consists of tracking network devices and their attributes (e.g. chassis, cards, interface types, serial numbers, hardware revisions, etc.).
		+	*Change Management: Change Management encompasses the tracking of changes to the network, its devices and services, from request through planning, engineering, approval, implementation and operational hand-off.
		+	*Provisioning Management: Provisioning management is the configuration of network devices to enable or disable network services. Provisioning can be as simple as network operators logging into network devices to modify configurations. Provisioning might also consist of implementing vendor, third-party, or homegrown applications capable of taking higher-level input.<ref>What is Configuration Management (CM) [https://www.tobiassystems.com/fcaps/ Tobias International]</ref>
		+
		+
		+	__TOC__

−	~~== Definition of Configuration Management (CM) ==~~
−	Configuration Management (CM) is a continuous process of recording and maintaining consistent and reliable records pertaining to an organization's hardware and software composition, including software version control and hardware updates.<ref>Defining Configuration Management (CM) [https://study.com/academy/lesson/what-is-configuration-management-definition-process-tools.html Study.com]</ref>

	Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies. Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the IT Infrastructure Library (ITIL) service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the configuration management database (CMDB); ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding Configuration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>		Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies. Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the IT Infrastructure Library (ITIL) service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the configuration management database (CMDB); ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding Configuration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>

@@ Line 86: / Line 86: @@
 [[Configuration Lifecycle Management (CLM)]]<br />
 [[Configuration Management Database (CMDB)]]<br />
 [[Product Lifecycle Management]]<br />
 [[Enterprise Resource Planning (ERP)]]<br />

@@ Line 17: / Line 17: @@
 *Configuration Audits – process of analyzing Configuration Items and their respective documentation to ensure that it reflects the current situation.
-[[File:Configuration_Management_Process.gif|300px|Configuration Management Process]]<br />
+[[File:Configuration_Management_Process.gif|400px|Configuration Management Process]]<br />
 source: DOT

@@ Line 81: / Line 81: @@
 *When your business has to comply with a configuration audit request, or pass a technology risk assessment.
 The benefits of configuration management flow into all these activities. These activities take time, and time is money.
 == See Also ==

← Older revision		Revision as of 22:13, 6 September 2019
Line 8:		Line 8:
	== History of Configuration Management (CM)<ref>History of Configuration Management (CM) [https://en.wikipedia.org/wiki/Configuration_management Wikipedia]</ref> ==		== History of Configuration Management (CM)<ref>History of Configuration Management (CM) [https://en.wikipedia.org/wiki/Configuration_management Wikipedia]</ref> ==
	Configuration Management originated in the United States Department of Defense in the 1950s as a technical management discipline for hardware material items—and it is now a standard practice in virtually every industry. The CM process became its own technical discipline sometime in the late 1960s when the DoD developed a series of military standards called the "480 series" (i.e., MIL-STD-480, MIL-STD-481 and MIL-STD-483) that were subsequently issued in the 1970s. In 1991, the "480 series" was consolidated into a single standard known as the MIL–STD–973 that was then replaced by MIL–HDBK–61 pursuant to a general DoD goal that reduced the number of military standards in favor of industry technical standards supported by standards developing organizations (SDO). This marked the beginning of what has now evolved into the most widely distributed and accepted standard on CM, ANSI–EIA–649–1998. Now widely adopted by numerous organizations and agencies, the CM discipline's concepts include systems engineering (SE), Integrated Logistics Support (ILS), Capability Maturity Model Integration (CMMI), ISO 9000, Prince2 project management method, COBIT, Information Technology Infrastructure Library (ITIL), product lifecycle management, and Application Lifecycle Management. Many of these functions and models have redefined CM from its traditional holistic approach to technical management. Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline.		Configuration Management originated in the United States Department of Defense in the 1950s as a technical management discipline for hardware material items—and it is now a standard practice in virtually every industry. The CM process became its own technical discipline sometime in the late 1960s when the DoD developed a series of military standards called the "480 series" (i.e., MIL-STD-480, MIL-STD-481 and MIL-STD-483) that were subsequently issued in the 1970s. In 1991, the "480 series" was consolidated into a single standard known as the MIL–STD–973 that was then replaced by MIL–HDBK–61 pursuant to a general DoD goal that reduced the number of military standards in favor of industry technical standards supported by standards developing organizations (SDO). This marked the beginning of what has now evolved into the most widely distributed and accepted standard on CM, ANSI–EIA–649–1998. Now widely adopted by numerous organizations and agencies, the CM discipline's concepts include systems engineering (SE), Integrated Logistics Support (ILS), Capability Maturity Model Integration (CMMI), ISO 9000, Prince2 project management method, COBIT, Information Technology Infrastructure Library (ITIL), product lifecycle management, and Application Lifecycle Management. Many of these functions and models have redefined CM from its traditional holistic approach to technical management. Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline.
		+
		+
		+	== Configuration Management Process<ref>Configuration Management Process [https://ops.fhwa.dot.gov/freewaymgmt/publications/cm/brochure/index.htm FHWA]</ref> ==
		+	The general CM process, graphically demonstrated below, is made up of the following elements:
		+	*Configuration Identification – process of documenting and labeling the items in the system, by providing a unique identifier to track changes and identify item location.
		+	*Change Management – process of assessing impacts of a possible change to a system, determining the fate of the proposed change, executing the approved changes, and ensuring that the change is properly documented.
		+	*Configuration Status Accounting – process of ensuring that all of the relevant information about an item is up to date and as detailed as necessary.
		+	*Configuration Audits – process of analyzing Configuration Items and their respective documentation to ensure that it reflects the current situation.
		+
		+	[[File:Configuration_Management_Process.gif\|300px\|Configuration Management Process]]<br />
		+	source: DOT

← Older revision		Revision as of 22:04, 6 September 2019
Line 1:		Line 1:
		+
		+	== Definition of Configuration Management (CM) ==
	Configuration Management (CM) is a continuous process of recording and maintaining consistent and reliable records pertaining to an organization's hardware and software composition, including software version control and hardware updates.<ref>Defining Configuration Management (CM) [https://study.com/academy/lesson/what-is-configuration-management-definition-process-tools.html Study.com]</ref>		Configuration Management (CM) is a continuous process of recording and maintaining consistent and reliable records pertaining to an organization's hardware and software composition, including software version control and hardware updates.<ref>Defining Configuration Management (CM) [https://study.com/academy/lesson/what-is-configuration-management-definition-process-tools.html Study.com]</ref>

	Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies. Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the IT Infrastructure Library (ITIL) service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the configuration management database (CMDB); ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding Configuration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>		Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies. Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the IT Infrastructure Library (ITIL) service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the configuration management database (CMDB); ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding Configuration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>
		+
		+
		+	== History of Configuration Management (CM)<ref>History of Configuration Management (CM) [https://en.wikipedia.org/wiki/Configuration_management Wikipedia]</ref> ==
		+	Configuration Management originated in the United States Department of Defense in the 1950s as a technical management discipline for hardware material items—and it is now a standard practice in virtually every industry. The CM process became its own technical discipline sometime in the late 1960s when the DoD developed a series of military standards called the "480 series" (i.e., MIL-STD-480, MIL-STD-481 and MIL-STD-483) that were subsequently issued in the 1970s. In 1991, the "480 series" was consolidated into a single standard known as the MIL–STD–973 that was then replaced by MIL–HDBK–61 pursuant to a general DoD goal that reduced the number of military standards in favor of industry technical standards supported by standards developing organizations (SDO). This marked the beginning of what has now evolved into the most widely distributed and accepted standard on CM, ANSI–EIA–649–1998. Now widely adopted by numerous organizations and agencies, the CM discipline's concepts include systems engineering (SE), Integrated Logistics Support (ILS), Capability Maturity Model Integration (CMMI), ISO 9000, Prince2 project management method, COBIT, Information Technology Infrastructure Library (ITIL), product lifecycle management, and Application Lifecycle Management. Many of these functions and models have redefined CM from its traditional holistic approach to technical management. Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline.

@@ Line 1: / Line 1: @@
 Configuration Management (CM) is a continuous process of recording and maintaining consistent and reliable records pertaining to an organization's hardware and software composition, including software version control and hardware updates.<ref>Defining Configuration Management (CM) [https://study.com/academy/lesson/what-is-configuration-management-definition-process-tools.html Study.com]</ref>
-Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies.  Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the [[ITIL (Information Technology Infrastructure Library)|IT Infrastructure Library (ITIL)]] service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the [[Configuration Management Database (CMDB)|configuration management database (CMDB)]]; ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding onfiguration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>
+Configuration management (CM) is a governance and systems engineering process for ensuring consistency among physical and logical assets in an operational environment. The configuration management process seeks to identify and track individual configuration items (CIs), documenting functional capabilities and interdependencies.  Administrators, technicians and software developers can use configuration management tools to verify the effect a change to one configuration item has on other systems. Configuration management is one of the operational processes identified in the IT Infrastructure Library (ITIL) service management framework, although an enterprise need not adopt the ITIL framework to perform configuration management. Configuration management is referred to as Service Asset and Configuration Management in ITIL V3. For a configuration management system to operate, it needs some form of mechanism in which to store the information it governs. Originally, this was called the configuration management database (CMDB); ITIL V3 introduced the concept of a configuration management system (CMS) to replace the CMDB. The CMDB promotes a concept of a singular monolithic repository, while the CMS provides a conceptualized system of CMDBs that act together to support the needs of this governance process. Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices. Every service management tool is deployed with a supporting data repository. Without the governance process of configuration management validating its contents, the repository is simply an operational database with unverified data, not a CMDB or CMS. Automated configuration audit and verification components entitle a repository to be leveraged as an authorized gold source of assets. A manual audit is also possible. A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise. The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.<ref>Understanding Configuration Management [https://searchitoperations.techtarget.com/definition/configuration-management-CM Techtarget]</ref>
@@ Line 27: / Line 25: @@
 The table below should give you a quick overview of the main differences between three of the most popular configuration management tools available in the market today: Ansible, Puppet, and Chef.
-[[File:Configuration_Management_Tools.png|500px|Comparison of Configuration Management Tools]]<br />
+[[File:Configuration_Management_Tools.png|400px|Comparison of Configuration Management Tools]]<br />
 source: Digital Ocean