Configuration Management Plan. Contractor shall produce a Configuration Management Plan within 60 days after NTP for Fleet 2.
Configuration Management Plan. The Contractor shall:
a) Provide a Configuration Management Plan that describes specific procedures and the extent of their application during the life cycle; and identifies roles and responsibilities for carrying out configuration management;
b) Support effective, predictable and repeatable configuration management processes.
Configuration Management Plan. The Prime Contractor shall submit a CTS Configuration Management Plan to the CDCR Operations Manager for approval at least 30 calendar days prior to any planned implementation. The CTS Configuration Management Plan shall focus on establishing and maintaining consistency of a system's performance and the functional and physical attributes with the requirements, design, and operational information throughout the term of the Contract. The Prime Contractor shall describe the plan to keep the CTS hardware and software, along with the documentation, consistent and current. The CTS Configuration Management Plan shall be updated and provided to CDCR Operations Manager when CTS components are modified, installed, or upgraded. The components shall include all CTS equipment, hardware, software, and firmware.
Configuration Management Plan. The Contractor shall, during SVP and as further required, provide a full-time configuration manager in order to develop a configuration management plan. The configuration manager shall ensure that all project artifacts are maintained with appropriate version control and undergo review and approval before moving into various environments (e.g., code has completed user acceptance testing before going into a staging envi- ronment). The Contractor shall employ a variety of tools to maintain configuration control, such as Microsoft SharePoint for document version control and SourceSafe for code control.
3.1. Quality Assurance (“QA”): Project Performance Evaluation.
A. QAP. The Contractor shall prepare, during SVP and as further required, a Project-specific quality assurance plan (“QAP”) that is used to ensure the quality of deliverables. The QAP shall:
(1) Establish the approach, plans, quality standards and quality procedures for QA on the Project;
(2) Describe the organization, support, schedule, management, and performance of all QA activities and the procedures, tools, and methodologies used in the management and evaluation of the project’s work products;
(3) Support the overall role of quality on this Project, which ensures that the project meets contract requirements of the State, verifies that the Contractor is following defined processes, begins the process of resolving any deficiencies that arise, continues the maturing of the defined processes, and develops and maintains a cooperative, positive relationship with team members.
Configuration Management Plan. The Contractor shall prepare a Configuration Management Plan and submit to the Government for review and approval (CDRL A010).
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. 9.1.1 The Contractor shall implement a configuration management regime using processes that are appropriate to the Project and approved by the Defence Project Manager.
Configuration Management Plan. Describes the following (at a minimum): a) Approach for managing programming changes, third-party software, and configuration settings made in the system, including testing, final approval of deployment, and deployment b) How Contractor will create (and maintain) a Configuration Items Log that captures configuration items in a register, including identified baselines under control that complies with the requirements of the Texas Project Delivery Framework • Develop Stakeholder Outreach and Communication Plan 5) Stakeholder Outreach and Communication Plan – Outreach to stakeholder groups to ensure a successful transition to the Solution and after cutover is complete. The plan applies specifically to stakeholder groups that are outside of OCA but are impacted by UCMS. The plan must include the following elements (at a minimum): a) Summary of Plan: Description of the methodology or approach that the Contractor will use to engage with the identified stakeholder groups b) Communication Channels: Information related to the type of communication channels that the Contractor intends to use c) Tools or measures to assess progress: Information on how the Contractor intends to measure progress and any tools required d) Established timeline: Timeline for outreach activities e) Stakeholder Engagement Table: submit the following table of proposed methods of outreach and involvement for various stakeholders: Methods of Engagement Stakeholder Purpose Level of Involvement
Configuration Management Plan. Describes the following (at a minimum): a) Approach for managing programming changes, third-party software, and configuration settings made in the system, including testing, final approval of deployment, and deployment.
Configuration Management Plan. The contractor shall deliver a CM Plan in contractor format and IAW DI-CMAN-80858B (CDRL A006). The plan shall be consistent with the approach used in the performance of CM activities for this effort as defined in section 3.3.1.2.3 of this SOW.
