Every element of the structural configuration should be uniquely identified per approved software configuration control procedures. From this point forward, only change requests or proposals that have been approved by the software change control board (CCB) should be integrated into the structural configuration. The discipline required with complex products such as defense systems provides an excellent basis for considering rules related to configuration changes.
Changes to contractor baselined documentation must
all be reviewed by the contractor to determine if they also impact
government performance requirements and support activities. The main difference between the change management and configuration management systems is that change management deals with process, plans, and baselines, while configuration management deals with product specifications. The Configuration Control Board (CCB) is a team responsible for overseeing the configuration management process. This includes the design, implementation, and ongoing maintenance of your CMDB.
The DMC controlled variables are the ammonia concentration in Z5 and the nitrate concentration in Z2. Both permanent members of the CCB and members of all technical working groups are notified about all CCB meetings and all scheduled TWG sessions, as are the Combatant Commands and Defense Agencies. During the middle of the project, your contractor for steel work walks off the job and you have to find a replacement. You find an alternative, but the new contractor will not start working on your project for a week.
Consistent with the federated architecture approach described in Section 3, essential architectural information must be registered with DARS so that discovery of reusable architectural data can be accomplished throughout the Department. Individual data entities and other artifacts are similarly registered in the DMR. These CM activities are complementary with existing DoD CM processes for the DARS, the DoD Information Technology Standards Registry (DISR), and the Metadata Registry (MDR). A more comprehensive description of the overall CM Process is found online in the DoDAF Journal. You are constructing a school building and the client requests that you increase the number of rooms from ten to fifteen. Suppose you are working on a project to construct a school building with ten classrooms.
4.1 Change control
Configuration management (CM) is a process of identifying, tracking, and controlling changes to the configuration items (CIs) that make up a system or product. 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. Figure 6-4 models the third segment of Figure 6-1,
covering the portion of the process concerned with Government review
and disposition of contractor submitted ECPs and RFDs. It illustrates
local Government representative review and concurrence with class
II changes and minor deviations (where such action is contractually
required) and its endorsement (or non-endorsement) of class I changes
and major/critical deviations. The CCB then
reviews the proposal and the implementation commitments and either
approves or disapproves them in accordance with the procuring activity’s
A higher-level CCB could tackle major change requests that have significant impact on costs or customer. The Change Control Board and the Change Advisory Board are similar organizational structures play vital roles in decision configuration control boards making. Both are comprised of teams whose role is to collectively help the organization make the right decisions of balancing need and risk of changes to technology that supports business processes, but they’re not the same.
The CCB is comprised of representatives who oversee, propose and review proposed software releases and property requirements. Create a configuration management practice that will provide ongoing value to the organization. Since the order bill of material will be used to maintain information on temporary changes in configuration, it should also maintain information on the authorization for this temporary change if applicable. In a complex product with a high volume of changes, changes should be grouped together and implemented in blocks to improve control over these changes and minimize the overall effect of changing part numbers and revision levels.
To effect change to a product, the first step is the revision
of the documents defining the product. The concepts discussed below
facilitate accomplishing this step, using automated tools such as
a CM AIS. This handbook views these concepts from both program management
(macro) point of view and the document control (micro) point of
Program Scope and Objectives
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. Figure 6-1 illustrates
a top-level activity model of the configuration control process.
Another concept that will affect the implementation of changes is interchangeability. Interchangeability is defined as when two parts possess such functional and physical characteristics as to be equivalent in performance, reliability, maintainability, etc. These parts should be able to be exchanged one for another without selection for fit or performance and without alteration of the item itself or of adjoining items. Where a partial design release is necessary to support long lead procurement or fabrication, partial engineering and manufacturing bills can be established, reconciled and controlled.
configuration control board (CCB)
More frequently and there wouldn’t be enough changes in the queue to make the meeting worthwhile. If they meet less frequently, then changes might need to be implemented in the gap between meetings and would need to be handled in an emergency mode. Once the FPGA design has been captured and compiled and initially downloaded to the HW target, configuration tracking needs to be maintained at the board level in the lab. Efficient real-world debugging is much easier when as many variables as possible are removed when trying to determine the source of a problem.
- The CM Authority for the contents of the DoDAF document is the DoD CIO, Office of the Assistant Secretary of Defense (OASD) Enterprise Architecture & Standards Directorate.
- For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards.
- Configuration control is an essential discipline
throughout the program life cycle.
- High-impact, high-risk and changes requiring multi-stakeholder approval should trigger a review.
- As the rest of the bill of material items are released, the remaining structure can be added and linked to the previous partial structure.
It also enables collaboration between CCB members and other stakeholders, as well as providing audit trails and security features. Online platforms are another beneficial tool which allow CCB members to conduct meetings and reviews remotely with video conferencing, screen sharing, chat, and file sharing features. Additionally, decision-making techniques can help analyze, compare, and choose among different options for change requests. These techniques include criteria-based evaluation, multi-voting, and consensus – each requiring active participation from CCB members. In conclusion, using the right tools and techniques can significantly improve the quality, speed, and accuracy of CCB decisions.
Section 2. Change Management Process
They could be submitted to a representative of the Change Control Board via e-mail. If the organization has a formal Change Control application, then tickets that have been entered into it can be extracted via a weekly report. An e-mail listing all proposed changes gets sent out to all board members a day or two prior to each scheduled meeting. With the freedom to change, recompile and reload the FPGA design to a board comes the responsibility to keep track of changes and keep FPGA design versions under configuration control.