• the concept of Configuration Change Management (CCM), emphasizing its importance in maintaining consistency between a product and its defining information throughout its lifecycle. It explains the systematic process for managing changes—identifying, classifying, documenting, approving, and implementing changes—to ensure product supportability, reliability, and traceability.
Created by Dr. YASSER MEKKY
EN/AR [Auto]
Join Now| # | Content |
|---|---|
| 1 | • Introduction to Configuration Change Management |
| 2 | • Principles of CCM (nine principles) |
| 3 | • Procedures When a Change is Required |
| 4 | • Identification of the Change (request, change number) |
| 5 | • Classification of the Change (minor, major) |
| 6 | • Documentation of Change (requests, records) |
| 7 | • Approval Process and Authorities (Program Manager, CAA, CCB) |
| 8 | • Post-Approval Implementation Processes |
| 9 | • Management of Variance Requests |
| 10 | • Summary of CCM processes, classifications, and key considerations. |
| # | Outcomes |
|---|---|
| • Understand the role and importance of CCM in product lifecycle management. | |
| • Recognize the nine principles that underpin effective change management. | |
| • Describe how to identify, classify, and document changes systematically. | |
| • Explain the approval process, including roles of authorities like the Program Manager and Change Control Boards. | |
| • Apply knowledge to manage change requests, variances, and ensure proper implementation. |
| # | Participants |
|---|---|
| 1 |
�
• military, defense contractors, logisticians, program managers, and stakeholders involved in configuration management and product sustainment.
|