configuration control board CCB Glossary

Configuration Management originated in the United States Department of Defense in the 1950s as a technical management discipline for hardware material items—and it is now a standard practice in virtually every industry. The CM process became its own technical discipline sometime in the late 1960s when the DoD developed a series of military standards called the „480 series” (i.e., MIL-STD-480, MIL-STD-481 and MIL-STD-483) that were subsequently issued in the 1970s. Many of these functions and models have redefined CM from its traditional holistic approach to technical management. Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline. Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications.

The functional architecture should be placed under technical configuration control to establish a functional design baseline for software design synthesis. The functional architecture must be complete and traceable to software specifications. The software engineering team representatives from software implementation and test and evaluation organizations must endorse the functional architecture and revise their technical plans and schedules to align organizational resources with anticipated task assignments.

h International Symposium on Process Systems Engineering

The change may be approved by the LCCB or sent via
unclassified e-mail to their voting sponsor and IT CCB management for final
review, evaluation, and decision, per IT CCB standard operating procedure (SOP)
guidelines. See 5
FAM 862 for more information regarding
LCCB processes and responsibilities. The CM plan must be developed during the study
period and must be augmented throughout the system life cycle. See 5 FAH-5 Exhibit
H-515, Model Configuration Management Plan (Sample). A change request may be submitted by any Department
of State organization that has a requirement to add a product to or change a
product on the baseline.

Complex assets such as aircraft, ships, industrial machinery etc. depend on many different components being serviceable. This serviceability is often defined in terms of the amount of usage the component has had since it was new, since fitted, since repaired, the amount of use it has had over its life and several other limiting factors. Understanding how near the end of their life each of these components is has been a major undertaking involving labor-intensive record keeping until recent developments in software.

MIL-HDBK-61A: Configuration Control

P can be described by the difference equations (1) and is used as the internal model of the MPC. The block △ and Kfv represent the norm bounded perturbation matrix and the favourite controller respectively. If you checked off more than a few of the above items, your organization may be underperforming in its CM functional capability, workflow capacity, or skills maturity. Or if there are problems you have seen over your career that we have missed please share them by leaving a comment below. One of the most important items covered in the primer has to do with the importance of CM Plans.

The CDCA may be a Government activity or a contractor,
and the authority may be transferred. However there is only one
CDCA for a document at a time. Appropriate evaluation criteria should be developed in the CM Plan and applied according to the scope and tier of the Architectural Description effort. The evaluation criteria must include factors that test compliance with the Net-Centric Reference Architectures and the DoD IE as outlined in Section 3.0 of the DoDAF and the Net-Centric Guidance contained in Volume 2. The results of architecture evaluations should be used to guide decisions for approving proposed changes, as well as in planning future extensions or updates to the Architectural Description. Another topic that often confuses managers is the difference between change control and configuration management.

Program Scope and Objectives

Approvers work closely with managers to approve and direct change in the organization and/or project. In smaller organizations, however, the approver and the change manager are the same people. Once the change control board has approved a change, the change must be managed. ProjectManager is work and project management software with multiple project views that allow you to work how you want.

ProjectManager is cloud-based software that gives the project team and the change control board real-time data to allow them to make more insightful decisions. It’s a given that there will be changes to the project plan during the project execution phase. It’s impossible to factor in everything—from weather to supply chains to change requests—something is going to conspire against your schedule and budget. Configuration control is perhaps the most visible configuration control board element of
configuration management. The CCB may, from time to time, establish technical working groups (TWG), as required, to oversee, review, and make recommendations to the board on specific technical aspects of the CM Program, or configuration items. TWGs provide the subject-matter expertise necessary to ensure that documents, the DM2, and other products under configuration control of the CCB are maintained in a responsible manner.

RE Definition: Configuration Control Board

A configuration control board (CCB) is a group of stakeholders that reviews and approves proposed changes to the CIs, ensuring that they are aligned with the project objectives, requirements, and standards. CCB meetings and reviews are essential for effective CM, but they can also be challenging, time-consuming, and prone to conflicts. A change control board is sometimes referred to as a change review board. It’s a group of people from the project team that meets regularly to consider changes to the project.

• (2)  ISP connections and their networks that are funded
  by Public Affairs or other grants, that are not located on US Government
  property.
• Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline.
• While the change control board usually has the authority, its decision is not always final and binding.
• The software must be legally procured and fully licensed,
  according to Department acquisition policies and vendor End User License
  Agreements.
• Comments about the glossary’s presentation and functionality should be sent to
• However there is only one
  CDCA for a document at a time.

Larger projects that include many teams working together typically have a central change control board in addition to various change boards specific to their project area. These teams report to the central change board that has the final say on the matter. There might also be a site change board for smaller changes that only impact remote sites. If changes are requested, the change control board shows how those changes are managed with the least amount of disruption to the project’s plan.

Resources for Configuration Management Assessments

The span of Configuration control begins for the Government once
the first configuration document is approved and baselined. This
normally occurs when the functional configuration baseline (referred
to as the requirements baseline in EIA/IS-649) is established for
a system or configuration item. Configuration control is an essential discipline
throughout the program life cycle.

Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes. Through the configuration control process, the full impact of proposed
engineering changes and deviations is identified and accounted for
in their implementation.

Speak with the team in the same language

The IT CCB is the enterprise central point for
evaluating change. When a change of any nature affects the Department of State
infrastructure or has potential for affecting the infrastructure then that
change must be presented to the IT CCB. The IT CCB is not intended to police
development activity, rather it is intended to be an assessor and advisor to
change and how it affects Department of State’ infrastructure. Many types of component use electronic sensors to capture data which provides live condition monitoring.