[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-173162-105":53,"doc-detail-173162-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","configuration-change-management-ccm-description","Configuration Change Management (CCM) - Description","","Configuration Change Management (CCM) establishes disciplined control and documentation of changes to approved configuration baselines across hardware, software, firmware, and related documentation. The process identifies, records, evaluates, dispositions, and incorporates changes while maintaining consistency in performance, functional, physical attributes, requirements, design, and operational information through the life cycle. Changes are assessed for impacts to cybersecurity and airworthiness, managed with access restrictions and verification activities, and implemented through an approved Change Action (CA) supported by digital transformation approaches such as MBSE where applicable.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/configuration-change-management-ccm-description/173162/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/configuration-change-management-ccm-description/173162.png","ImageObject",442,249,{"name":88,"@type":89},"Lucas Vance","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-10-20","2026-09-01",true,{"@type":98,"interactionType":99,"userInteractionCount":15},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the primary purpose of the CCM process?","Question",{"text":108,"@type":109},"CCM controls and documents changes to approved configuration baselines, ensuring changes are properly identified, evaluated, dispositioned, and incorporated while maintaining consistency across the product life cycle.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"When do Cybersecurity assessments occur in the CCM workflow?",{"text":113,"@type":109},"A cybersecurity assessment is performed on all Change Requests (CRs) and Change Actions (CAs) to evaluate potential impacts to the program’s cybersecurity posture.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the process move from a Change Request to an approved Change Action?",{"text":117,"@type":109},"The requesting organization submits a Change Request to the Program Office, which validates the need and approval path; then a formal Change Action is developed, reviewed by the Configuration Control Board (CCB), and tracked through implementation to closure.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},173162,1790759104,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":15,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},549768064622,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","\u000f\nAir Force Life Cycle Management Center\nStandard Process\nFor\nConfiguration Change Management (CCM)\nProcess Owner:  AFLCMC/EZSC\nDate:  21 November 2024\nVersion:  5.0\nRecord of Changes. This page summarizes the changes from each revision of the process to the next. Revision numbering starts with 1.0. Minor changes are annotated by changing the second digit, i.e., the first minor change after the basic document would be recorded as “1.1.” Major changes are annotated by changing the first digit, i.e., the first major change after release of the basic document would be numbered as “2.0.”  Example:\n\u000fTABLE OF CONTENTS\n\u0003\n\u0013 TOC \\o \"1-3\" \\h \\z \\u \u0014\u0013 HYPERLINK \\l \"_Toc114225415\" \u00141.0 Description\t\u0013 PAGEREF _Toc114225415 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225416\" \u00142.0 Purpose\t\u0013 PAGEREF _Toc114225416 \\h \u00147\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225417\" \u00143.0 Entry/Exit Criteria and Inputs/Outputs\t\u0013 PAGEREF _Toc114225417 \\h \u00147\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225418\" \u00144.0 Process Workflow and Activities.\t\u0013 PAGEREF _Toc114225418 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225419\" \u00145.0 Process Measurement.\t\u0013 PAGEREF _Toc114225419 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225420\" \u00146.0 Roles and Responsibilities.\t\u0013 PAGEREF _Toc114225420 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225421\" \u00147.0 Tools\t\u0013 PAGEREF _Toc114225421 \\h \u001419\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225422\" \u00148.0 Training\t\u0013 PAGEREF _Toc114225422 \\h \u001420\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225423\" \u00149.0 Definitions, Guiding Principles and/or Ground Rules & Assumptions\t\u0013 PAGEREF _Toc114225423 \\h \u001421\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc114225424\" \u001410.0 References to Law, Policy, Instructions or Guidance\t\u0013 PAGEREF _Toc114225424 \\h \u001426\u0015\u0015\n\u0015\u0004\n\u000f\nDescription\nConfiguration change management (CCM) is a fundamental aspect of Configuration Management (CM) practices that emphasizes controlling and documenting changes to established weapon system configuration baselines, including hardware, software, firmware, and associated documentation. The goal is to maintain consistency in a product's performance, functional, physical attributes, requirements, design, and operational information throughout its life cycle. The CCM process ensures changes to and deviations from a configuration baseline are properly identified, recorded, evaluated, dispositioned, and incorporated as appropriate. Changes are analyzed for potential impacts to cybersecurity and airworthiness and addressed accordingly. Various access restrictions, such as access controls, process automation, abstract layers, change windows, and verification and audit activities, are used to prevent unauthorized and undocumented changes to programs. The primary objective is to establish a secure and cost-effective environment that supports mission and business processes while protecting against unauthorized changes and significant threats. This Standard Process describes the high-level actions to identify, record, evaluate, disposition, and implement an approved Change Action (CA). Digital transformation should be implemented, to include Model Based Systems Engineering (MBSE) when applicable to the program’s Acquisition Strategy (AS), Intellectual Property Strategy (IPS), Sustainment Strategies (SS), Systems Engineering Plan (SEP), and product support and logistics requirements.\nThis document describes the process of maintaining configuration information and its technical baselines by applying change management, also known as configuration or change control, as referenced in MIL-HDBK-61B, EIA-649C, GEIA-HB-649A, and NIST SP 800-128. Change management begins when the configuration information or technical baselines are established and approved. There are three distinct (functional, allocated, and product) technical baselines that are developed and placed under configuration control. See above references for additional information about configuration information, technical baselines, and change management.\nThe organization requesting a change to an approved configuration technical baseline will present a Change Request (CR) to the Program Office (P","cbCaiqkFy1V0DxZc","https://ap.wps.com/l/cbCaiqkFy1V0DxZc","docx",563055,28,"English","# Table of Contents\n## 1.0 Description\n## 2.0 Purpose\n## 3.0 Entry/Exit Criteria and Inputs/Outputs\n## 4.0 Process Workflow and Activities\n## 5.0 Process Measurement\n## 6.0 Roles and Responsibilities\n## 7.0 Tools\n## 8.0 Training\n## 9.0 Definitions, Guiding Principles and/or Ground Rules & Assumptions\n## 10.0 References to Law, Policy, Instructions or Guidance","[{\"question\":\"What is the primary purpose of the CCM process?\",\"answer\":\"CCM controls and documents changes to approved configuration baselines, ensuring changes are properly identified, evaluated, dispositioned, and incorporated while maintaining consistency across the product life cycle.\"},{\"question\":\"When do Cybersecurity assessments occur in the CCM workflow?\",\"answer\":\"A cybersecurity assessment is performed on all Change Requests (CRs) and Change Actions (CAs) to evaluate potential impacts to the program’s cybersecurity posture.\"},{\"question\":\"How does the process move from a Change Request to an approved Change Action?\",\"answer\":\"The requesting organization submits a Change Request to the Program Office, which validates the need and approval path; then a formal Change Action is developed, reviewed by the Configuration Control Board (CCB), and tracked through implementation to closure.\"}]","Configuration Change Management (CCM) - Description | DOCX",1788300631,10]