Marines, The Few, the Proud - link to the Official Marine Corps website.
Configuration Control Board

Configuration Control Board (CCB)


Configuration Control is the systematic process of proposing, justifying, evaluating, validating, disposing of proposed changes, and implementing approved changes, as well as tracking the many changes affecting a configuration item's state.  Configuration control essentially ensures the documentation and coordination of recommended engineering changes to configuration items.  Until a standard process is established, internal procedures will dictate how the recommended change will be processed.

In addition, the process ensures the Configuration Control Board's (CCB) involvement to formally authorizes all changes from the baseline.  The level of Configuration Control should be tailored based on the configuration item's life cycle phase.  The process is dependent on various types of analysis to include engineering, cost/benefit, interface, and schedule.

Configuration control focuses on ensuring baselines changes are properly authorized, coordinated, and documented. Control of proposed changes are performed under the auspices of a Configuration Control Board (CCB), which consists of technically competent members from various functional areas who review, analyze, and consider the impact of incorporating the recommended change. The organization, jurisdiction, and operating procedures for the CCB should be described in the Configuration Management Plan.



The CCB will be established as specified in the CM Plan and will remain active until the system has reached the end of its operational life.



The responsibility for change control resides in the Program Office.  The authority to approve or disapprove any proposed changes resides with the Program Manager. The System Engineer or Logistics Management Specialist assigned to the program may be delegated the responsibility for properly executing the configuration control process.



Terms and Definitions

General References

Specific References:

  • MIl-HDBK-61A[1], Section (NOTE: MIL-HDBK-61A has not yet been updated in accordance with the new DoDI 5000.2, May 2003)


1.3.4 Change Review/Evaluation Criteria: The applicable parameters/elements delineated should be considered during the evaluation of proposed changes before a recommended disposition or decision is made to change a configuration item or its configuration identification:

1. Affordability. 15. Configuration audits.
2. Financially executable. 16. Schedules
3. Military characteristics changes. 17. Retrofit requirements.
4. Functional and physical characteristics. 18. Impact on total life cycle costs.
5. All integrated logistic support elements. 19. Change justification.
6. Quality assurance. 20. Support equipment.
7. Reliability. 21. Security.
8. Maintainability. 22.  Interfaces.
9. Availability. 23. FMS requirements.
10. Operational readiness. 24. Environmental impact.
11. Test and evaluation. 25.  Ship and/or shore suitability.
12. Systems engineering (e.g., design integrity, interfaces, simulation, interchangeability, interoperability, nuclear hardening, survivability, human factors, etc.).  
13. System safety -- Nuclear safety. 26. Warranties/guaranties.
14. Technical reviews. 27. Requirements for GFE
15. Configuration audits. 28. MCCR Requirements


Extract From Systems Engineering Fundamentals (Supplemental Text)
Configuration Control Board (CCB)

A CCB is formed to review Class I ECPs for approval, and make a recommendation to approve or not approve the proposed change. The CCB chair, usually the program manager, makes the final decision. Members advise and recommend, but the authority for the decision rests with the chair. CCB membership should represent the eight primary functions with the addition of representation of the procurement office, program control (budget), and Configuration Control manager, who serves as the CCB secretariat.

The CCB process is shown in Figure 10-2. The process starts with the contractor. A request to the contractor for an ECP or Preliminary ECP is necessary to initiate a government identified configuration change. The secretariat's review process includes assuring appropriate government contractual and engineering review is done prior to receipt by the CCB.


CCB Management Philosophy

The CCB process is a configuration control process, but it is also a contractual control process. Decisions made by the CCB chair affect the contractual agreement and program baseline as well as the configuration baseline. Concerns over contractual policy, program schedule, and budget can easily come into conflict with concerns relating to configuration management, technical issues, and technical activity scheduling. The CCB technical membership and CCB secretariat is responsible to provide a clear view of the technical need and the impact of alternate solutions to these conflicts. The CCB secretariat is further responsible to see that the CCB is fully informed and prepared, including ensuring that:

  • A Government/contractor engineering working group has analyzed the ECP and supporting data, prepared comments for CCB consideration, and is available to support the CCB;
  • All pertinent information is available for review;
  • The ECP has been reviewed by appropriate functional activities; and
  • Issues have been identified and addressed.


CCB Documentation

Once the CCB chair makes a decision concerning an ECP, the CCB issues a Configuration Control Board Directive that distributes the decision and identifies key information relating to the implementation of the change:

  • Implementation plan (who does what when);
  • Contracts affected (prime and secondary);
  • Dates of incorporation into contracts;
  • Documentation affected (drawings, specifications, technical manuals, etc.), associated cost, and schedule completion date; and
  • Identification of any orders or directives needed to be drafted and issued.


[1] Go to Defense Standardization Program Office, ASSIST Database for the most up-to-date and ONLY official version of MIL-HDBK-61A. (


(Last Updated December 08, 2011)    Web Publisher | Privacy Policy | USMC Home Page