December 18th, 2009 by Bracken
When people find out a configuration management database (CMDB) is being created, many people will have data they feel should be included. The list of potential sources for data is as varied as the organizations that can benefit from a CMDB. Although specific types of data and sources will vary for every industry and company. You need to create a plan how to identify what data is need to be a part of the new CMDB.
Your plan will include a set of steps to collecting each type of data you identify. Start with a series of meetings with the all managers to understand what they have, and more importantly, what they don’t have that you need. If the data is managed by a part of the organization different from that sponsoring your configuration management team, you will need more detailed meetings to work out what format the data can be sent, how the data will actually be transferred, the owner of the data, and what processing must happen after the data is received. Finally, your project plan should include some set of tasks for confirming that the data was correctly received.
December 15th, 2009 by Bracken
Configuration management (CM) is a field of management that focuses on establishing and maintaining consistency of a system’s or product’s performance and its functional and physical attributes with its requirements, design, and operational information throughout its life. For information assurance, CM can be defined as the management of security features and assurances through control of changes made to hardware, software, firmware, documentation, test, test fixtures, and test documentation throughout the life cycle of an information system.
History
Configuration management was created by the federal government and is currently required for all military contractors. This was in response to the problem the military was having with contactors not being able to duplicate their prototypes exactly.
The concepts have been widely adopted by numerous technical management models, including systems engineering, integrated logistics support, Capability Maturity Model Integration (CMMI), ISO 9000, Prince2 project management methodology, COBIT, Information Technology Infrastructure Library (ITIL), product lifecycle management, and application lifecycle management. Many of these models have redefined configuration management from its traditional holistic approach to technical management. Some treat configuration management as being similar to a librarian activity, and break out change control and change management as separate areas of discipline.