Configuration Management Plan Sample Clauses

Configuration Management Plan. Contractor shall produce a Configuration Management Plan within 60 days after NTP for Fleet 1. The Configuration Management Plan shall identify the methods and procedures that shall be used to achieve the requirements of the Configuration Management system. The Plan shall identify how the interfaces with design, production and management teams are controlled, and the associated procedures, systems and techniques employed.
AutoNDA by SimpleDocs
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. 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. Contractor shall provide a Configuration Management Plan that will include the following topics and sections:
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.
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. The Contractor shall:
AutoNDA by SimpleDocs
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 <Insert methods of engagement> For example: Recorded webinar <Identify stakeholder group> For example: Texas Bar Association <Insert purpose of the engagement> For example: Awareness of new State EFSP protocols <Estimate duration of involvement > For example: Recorded webinar available one month prior to go live
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:
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):
Time is Money Join Law Insider Premium to draft better contracts faster.