Configuration Management Work Activities

Configuration management is the set of activities that identifies, documents, and controls configuration items relevant to a particular investment program and the larger Enterprise Architecture of which it is a part. The Enterprise Architecture defines the allocation of agency requirements to appropriate systems and facilities, and defines connectivity among them. Service Teams and other designated organizations establish program-level configuration management to control product configurations, and to maintain interfaces and interoperability with other systems, facilities, and services comprising the Enterprise Architecture. Service Teams establish functional and product baselines, and control change to those baselines through configuration control boards. Typically, Configuration items include the most important elements of the product. The documents that define the investment program, including the Exhibit 300 Program Baseline, Program Requirements attachment to the Exhibit 300 Program Baseline, System Specification, and Product Baseline are artifacts of the configuration items that are managed as hardware and software items are changed.

Configuration Control Boards (CCBs) are decision-making bodies that examine and decide whether changes to requirements, system design, and so on, are cost-effective and to be pursued. CCBs are distributed, both at Headquarters (primarily for acquisition configuration items) and at Regions (predominately for in-service management needs, including facility site drawings).

Configuration management activities are two basic types: Baselining and Change Control. Baselining involves the managerial agreement on the content of an investment program or configuration item (e.g., the Exhibit 300 Program Baseline, System Specification, Product Specification by a CCB or a Specification Review Board). Change control is the process of developing, coordinating, approving, and documenting changes to configuration items throughout solution implementation and in-service management phases, again controlled by the same CCBs.

During final investment analysis, early configuration management is focused on baselining and change control of principal acquisition-related configuration item documents (e.g., Program Requirements attachment, Exhibit 300 Program Baseline, System Specification). During solution implementation, activities shift to baselining and change control of implementation-related configuration items such as equipment layout drawings for installation support.

During in-service management, configuration management shifts to in-service configuration items relating to operations and support of installed equipment. Such Configurations Items include technical and maintenance manuals, engineering drawings, and facility layout drawings. This configuration management resides within Regional Offices, although Service Teams remain responsible for in-service product improvements, technology refreshment, and product upgrades.

Activity: Include CM Requirements in Program Requirements Attachment CM-1
Responsible Agent	Product	Approval Authority	Tools and Aids
CM specialist of the Investment Analysis Team	CM requirements in the Program Requirements attachment to the Exhibit 300 Program Baseline		Template and instruction for the Program Requirements attachment to the Exhibit 300 Program Baseline
Description: The Program Requirements attachment to the Exhibit 300 Program Baseline establishes functional and performance requirements for the investment program, as well as the operational framework required by the operating service organization. The Program Requirements attachment must contain the final set of configuration management requirements for the alternative selected for implementation at the final investment decision. These requirements may be very different for different solutions. For example, a commercial / NDI solution may require the prime contractor to maintain product configuration, whereas the configuration of a developmental program may be managed organically within the FAA.
Activity: Include CM Cost / Schedule in the Exhibit 300 Program Baseline CM-2
Responsible Agent	Product	Approval Authority	Tools and Aids
CM specialist of the Investment Analysis Team	CM cost and schedule in the Exhibit 300 Program Baseline
Description: The Investment Analysis Team develops an Exhibit 300 Program Baseline that sets out the performance, cost, schedule, and benefit baselines to be achieved. The configuration management specialist must ensure the cost and schedule of configuration management is included in the Exhibit 300 Program Baseline. This includes provision for such activities as conducting functional and physical configuration audits, establishing and maintaining the program support library, performing lifecycle configuration status accounting, and supporting contractor tasks to develop and maintain the various CM baselines.
Activity: Develop CM Strategy for Part 1 of the Implementation Strategy and Planning Attachment CM-3
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team configuration management specialist	CM strategy for Part 1 of the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline		Template and instruction for Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline
Description: The Service Team decides how best to manage the configuration of the investment program, and summarizes this approach in Part 1 of the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline. This involves identifying and documenting practices applicable this product. The CM strategy must satisfy all CM requirements in the Program Requirements attachment, and must comply with agency CM policy. It fleshes out all aspects of product configuration management including resources, roles and responsibilities, schedules, vendor CM requirements and products, technical CM products (e.g., System Specification, Interface Requirements Documents), training, and reporting. The CM strategy covers planned product upgrades, when applicable, as well as both contractor and government roles and responsibilities.
Activity: Define CM Activities for Part 2 of the Implementation Strategy and Planning Attachment CM-4
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team configuration management specialist	Tasks in Part 2 of the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline		Template and instruction for the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline
Description: The Service Team defines the work activities and tasks necessary to implement the CM strategy and records them in Part 2 of the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline. Part 2 describes each work activity, assigns the responsible agent, identifies any products or outputs (e.g., functional baseline, product baseline, facility baseline, program support library, physical configuration audit), the approval authority (if applicable), and establishes when the activity must be completed.
Activity: Establish Program CM Support Library CM-5
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team configuration management specialist	Program Support Library
Description: The CM specialist establishes and maintains a Program Support Library for CM containing technical baseline documents, change vehicles, and any other information needed for configuration management of the product(s) of the investment program. This may include establishing a stand-alone library, establishing electronic links to an FAA or vendor library, or establishing access to an established library. The CM specialist specifies the information to be included in the library and the metrics applicable to the library. The use of electronic data for the Product Support Library is highly recommended.
Activity: Define Interface Requirements CM-6
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist	Interface Requirements Documents Interface Control Documents	Appropriate Configuration Control Board (NAS CCB, ST CCBs, Facility CCBs)
Description: The Service Team prepares and gains approval of Interface Requirements Documents (IRDs) and Interface Control Documents (ICDs) for each interface of the system or equipment with other NAS systems, equipment, or facilities. IRDs and ICDs are approved by the appropriate CCB, and included in the appropriate Screening Information Request, Request for Offer, or other procurement or tasking vehicle.
Activity: Establish and Maintain the Functional Baseline CM-7
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Functional Baseline	Service Team Configuration Control Authority
Description: The Service Team establishes and maintains a Functional Baseline for the product(s) to be developed and deployed. This baseline may include the Program Requirements attachment to the Exhibit 300 Program Baseline, one or more Interface Requirements Documents, Functional / Performance Specifications, and System / Segment Specifications. Once established, the Functional Baseline is maintained under strict configuration control throughout the lifecycle of the product or service. While the Service Team typically manages the configuration of these core configuration items, in some cases (e.g., facility modification drawings) a Regional CCB may be the appropriate approval and change authority.
Activity: Incorporate CM Input to the Screening Information Request CM-8
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team configuration management specialist	CM-related information for the SIR	Service Team leader
Description: The Service Team prepares a Screening Information Request that solicits proposals from potential vendors. The CM specialist provides CM-related input to the SIR, including: Vendor CM tasking in the Statement of Work, including the level of configuration identification, the method for changing baselines, the requirement for audits and establishing baselines, and status accounting; CM section of the System Specification (A-Spec); CM data to be provided by the vendor in the Contract Data Requirements List, including frequency of submittal, distribution, and approvals; Format and content of CM data submittals using appropriate Data Item Descriptions, including specific fields and data elements of reports; CM-related Instructions, Conditions and Notices to Offerors; CM evaluation criteria to be used in source selection. The Service Team should solicit field input to these documents to ensure implementation and transition CM requirements are addressed adequately in the Screening Information Request.
Activity: Provide CM Support During Source Selection CM-9
Responsible Agent	Product	Approval Authority	Tools and Aids
ServiceTeam configuration management specialist	Evaluation of the CM sections of vendor proposals
Description: The Service Team CM specialist evaluates and scores the configuration procedures and processes of potential vendors, and determines whether vendor proposals are in compliance with CM requirements in the System Specification.
Activity: Monitor Contractor CM Activities CM-10
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team configuration management specialist	Approved CM contract deliverables	Official stipulated in the CDRL
Description: The Service Team CM specialist monitors, reviews, and comments on vendor CM activity and contract deliverables, as stipulated in the Statement of Work, System Specification, Contract Data Requirements List, and Data Item Descriptions. The intent is to ensure strict configuration control of all configuration items developed and managed by the contractor. This activity includes the flow down of CM requirements to subcontractors if the prime contractor subcontracts substantial portions of the overall program solution to mission need.
Activity: Establish the Allocated Baseline CM-11
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Allocated Baseline	Appropriate configuration control board
Description: The Service Team establishes and places under configuration control the Allocated Baseline. The allocated baseline consists of documentation describing the allocation of an item�s functional, interoperability, and interface characteristics to lower-level configuration items. For developmental software, the Allocated Baseline assigns program requirements to specific, lower-level software configuration items and defines the interfaces between them. This Allocated Baseline governs all developmental activity by the contractor. After approval, changes to the Allocated Baseline are formally controlled and managed by the Service Team CCB or contractor configuration control processes (or both), as specified in the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline and prime contract.
Activity: Establish Test Configuration Baselines CM-12
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team test director Service Team configuration management specialist Test organization configuration manager	Baselined Test Configurations	Service Team test director
Description: The purpose of testing is to establish that performance and functional requirements defined in the Allocated Baseline have been achieved. Testing also establishes that the design is accurately and sufficiently documented. The Service Team CM specialist (or CM unit within the testing organization, as specified in the Part 1 of the Implementation Strategy and Planning attachment to the Exhibit 300 Program Baseline) establishes and manages change to test configurations. This applies to both developmental and operational test and evaluation.
Activity: Establish / Maintain Facility / Site Configuration Baselines CM-13
Responsible Agent	Product	Approval Authority	Tools and Aids
Appropriate Regional office Service Team facility specialist Service Team configuration management specialist	Facility / Site Configuration Baselines	Appropriate Regional Configuration Control Boards
Description: Working in conjunction with the Service Team, appropriate Regional offices establish and maintain facility / site configuration baselines. The Facility Configuration Baseline consists of such items as facility drawings, technical documentation, and change control information. The Facility Configuration Baseline is established by means of a Facility Document Review to determine whether the baseline documentation is complete and whether it reflects accurately the current facility configuration. This activity involves establishing and managing facility / site configuration drawings, as well as validating site configuration processes and procedures.
Activity: Conduct Functional Configuration Audit CM-14
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Final Software Requirements Specification Final Interface Requirements Specification Final Software Design Document(s) Final Software Development Folder(s) Final Software Test Procedures Final STD(s) SPS including source code listings Software Test Report(s) PTR(s) Software Version Document Final Computer Operation Manual Final Software User Manual	Appropriate Service Team specialist
Description: The Service Team conducts a Functional Configuration Audit (FCA) supported by appropriate FAA and contractor personnel. The FCA examines the functional characteristics of a configuration item, prior to acceptance, to verify it achieves the requirements specified in its functional and configuration documentation. Functional documentation describes the product�s functional performance, interoperability, and interface requirements, as well as the verifications necessary to demonstrate achievement of those requirements. Allocated documentation describes the distribution of a configuration item�s functional, performance, interoperability, and interface requirements to loser-level system segments. Specifically, the Functional Configuration Audit verifies that: � Performance of individual configuration items complies with requirements of the Allocated Baseline; and � Product design and the "as-built" product configuration are documented accurately. The FCA is conducted on test data from a unit representative of the configuration to be released to production, typically the OT&E Product Configuration and associated data. The Service Team certifies satisfactory completion of the audit. The FCA for a complex system (multiple Computer Software Configuration Items CSCIs and Hardware Configuration Items HWCIs) may be conducted progressively throughout system development. The process ends with completion of the Design Qualification Test and a review of all CSCI / HWCI discrepancies at the final system-level FCA.
Activity: Conduct Physical Configuration Audit CM-15
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team conducts the PCA	Product Baseline	Service Team systems engineering specialist
Description: The Service Team conducts a Physical Configuration Audit (PCA) after all test programs are completed, as close to production of the first unit as possible. The PCA examines the "as-built" product against its design documentation to establish the Product Baseline. The PCA includes a detailed audit of engineering drawings, specifications, technical data, and tests used in the production of HWCIs, and design documentation, code listings, and manuals for CSCIs. The review includes an audit of released engineering documentation and quality control records to ensure the "as-built" and "as-coded" configuration is reflected by this documentation. For software, the Software Product Specification and Software Version Document must be part of the PCA review. The PCA also determines whether acceptance test requirements are adequate for acceptance of production unit configuration items by quality assurance. After successful completion of the PCA, changes to the system or its documentation are processed by formal engineering change action. The Service Team certifies satisfactory completion of the audit.
Activity: Establish Product Baseline CM-16
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Product Baseline	NAS Configuration Control Board
Description: The Product Baseline include Product Specifications (hardware and software), Technical Instruction Manuals, Version Design Documents, Interface Control Documents, drawings, and any site-specific directives / instructions, adaptation data, and updates to the baselines. The official Product Baseline is established after a successful FCA / PCA, and approval of the NAS Change Proposal introducing Product Baseline components into the NAS.
Activity: Perform Configuration Status Accounting CM-17
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Configuration Status Accounting Reports
Description: The Service Team establishes and manages the activities required for configuration status accounting of the Product Baseline. Status accounting encompasses vendor change vehicles and baseline data; configuration items, NCPs, configuration-controlled documents and associated baselines; and HDRs, EEM Chapters and associated baselines. Status accounting involves recording, storing, and accessing information needed to manage configuration items effectively, including: A record of the approved configuration documentation and identification numbers; The status of proposed changes and deviations to the configuration; The implementation status of approved changes; The configuration of all units of the configuration items in the inventory.
Activity: Perform Configuration Change Management CM-18
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Controlled Product Baseline	Service Team Configuration Control Board
Description: The Service Team manages change control of the Product Baseline. This involves the systematic proposal, justification, evaluation, review, and disposition of proposed changes, as well as the implementation of all approved changes into: (a) the applicable configurations of the product, (b) associated product information, and (c) supporting and interfacing products and their associated product information. Documentation includes case files, NCPs, ECPs, PTRs, and deviations and waivers. Change management frequently involves such activities as engineering studies, cost / benefit analysis, interface analysis, and schedule analysis to determine and quantify the impact of proposed changes.
Activity: Manage Configuration Items for P³I, Technology Refresh, and Product Upgrades CM-19
Responsible Agent	Product	Approval Authority	Tools and Aids
Service Team systems engineering specialist Service Team configuration management specialist	Managed Configuration Item Baselines of product upgrades	Service Team Configuration Control Board
Description: The Service Team, working in concert with operating and support service organizations, develops, approves, and manages configuration items for all new products entering into operational use. Many of the configuration management activities conducted during Solution Implementation for the currently fielded capability are replicated to assure smooth transition and continuity of operational service as installed equipment is modified and upgraded.