configuration information held in the Configuration Management Database (CMDB). This may include approved configuration documents, software, data, and their current version numbers; build reports; status of any submitted changes; or any discrepancies and status identified through configuration audits. It is important that for the NexGen Project, the Project Sponsor and Vice President of Technology have the ability to review configuration status at any given time. The Project Manager will also submit weekly reports, to include configuration status, every Friday. These reports will consist of the following information as part of the configuration status section: Change requests Aging - How long change requests have been open Distribution number of change requests submitted by owner/group – Trending what area(s) are approved changes occurring in – Version Control Software Hardware Data Documentation Build Reporting Files CI relationships Incorporated Changes Audits Physical Configuration Functional Configuration Prior to any new software releases, the CM will work with each Lead Engineer to ensure all CIs are updated with latest release versions. Configuration Audits Audits are an important part of project and configuration management. The purpose of an audit is to ensure that established processes are being followed as intended and to provide an opportunity to correct any deviations from these processes. Many people hold a negative view of audits; however, when used appropriately, audits are an effective management and quality assurance tool.
configuration information held in the Configuration Management Database (CMDB). This may include approved configuration documents, software, data, and their current version numbers; build reports; status of any submitted changes; or any discrepancies and status identified through configuration audits. It is important that for the NexGen Project, the Project Sponsor and Vice President of Technology have the ability to review configuration status at any given time. The Project Manager will also submit weekly reports, to include configuration status, every Friday. These reports will consist of the following information as part of the configuration status section: Change requests Aging - How long change requests have been open Distribution – number of change requests submitted by owner/group Trending – what area(s) are approved changes occurring in Version Control Software Hardware Data Documentation Build Reporting Files CI relationships Incorporated Changes Audits Physical Configuration Functional Configuration Prior to any new software releases, the CM will work with each Lead Engineer to ensure all CIs are updated with latest release versions. Configuration Audits Audits are an important part of project and configuration management. The purpose of an audit is to ensure that established processes are being followed as intended and to provide an opportunity to correct any deviations from these processes. Many people hold a negative view of audits; however, when used appropriately, audits are an effective management and quality assurance tool.
Configuration-Management-Plan.docx