Common use of Configuration Management Plan Clause in Contracts

Configuration Management Plan. Contractor shall provide a Configuration Management Plan that will include the following topics and sections: i. How Contractor will maintain a Configuration Management Database (CMDB) on behalf of the State that contains Configuration Items, attributes, and relationships for the Service being provided. The CMDB shall be managed by a documented configuration management process and under the control of Change Management; ii. Processes for the identification, control, recording, reporting, auditing, and verifying service assets and configuration items managed on behalf of State. The intention of capturing CIs, attributes and relationships is for impact analysis during changes, troubleshooting for Incidents and Problems, and keeping computing environments in sync; iii. A policy/plan for working with State and other DDI providers for continuous improvement; iv. A Responsibility Matrix (RACI) that outlines the roles within the process; v. Documented plan for keeping computing environments (software and hardware) sufficiently synchronized to confirm testing and release integrity. These include Production, Non-Production, and DR environments; vi. Staffing required to build, manage, and maintain the CMDB; vii. Strategy and procedure for tracking and reporting on State owned software assets and licenses for the HSEP M&O Services that are within Contractor’s scope of responsibilities; and viii. Strategy for providing State reporting (and raw data upon request) based upon KPIs, metrics outlined within these NFRs.

Configuration Management Plan. Contractor shall provide a Configuration Management Plan that will include the following topics and sections: i. How Contractor will maintain a Configuration Management Database (CMDB) on behalf of the State that contains Configuration Items, attributes, attributes and relationships for the Service being provided. The CMDB shall be managed by a documented configuration management process and under the control of Change Management; ii. Processes for the identification, control, recording, reporting, auditing, auditing and verifying service assets and configuration items managed on behalf of State. The intention of capturing CIs, attributes and relationships is for impact analysis during changes, troubleshooting for Incidents and Problems, Problems and keeping computing environments in sync; iii. A policy/plan for working with State and other DDI providers for continuous improvement; iv. A Responsibility Matrix (RACI) that outlines the roles within the process; v. Documented plan for keeping computing environments (software and hardware) sufficiently synchronized to confirm testing and release integrity. These include Production, Non-Production, and DR environments; vi. Staffing required to build, manage, manage and maintain the Configuration Management Database (CMDB); vii. Strategy and procedure for tracking and reporting on State owned software assets and licenses for the HSEP M&O Services that are within Contractor’s scope of responsibilities; and; viii. Strategy for providing State reporting (and raw data upon request) based upon KPIs, metrics outlined within these NFRs.