The service team decides how best to manage the configuration of the investment program. This approach is recorded in section 9 of the implementation strategy and planning attachment to the Exhibit 300 program baseline. The CM strategy must satisfy all CM requirements in the program requirements attachment, and must comply with agency CM policy. The strategy specifies all key elements of product definition and configuration management including configuration items, 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.

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.

The investment analysis team develops an Exhibit 300 program baseline that sets out the performance, cost, schedule, and benefit baselines of the investment program. The configuration management specialist must ensure the cost and schedule of configuration management is included. This includes provision for such activities as functional and physical configuration audits, establishing and maintaining the program support library, lifecycle configuration status accounting, and contractor tasks to develop and maintain the various CM products and baselines.

System Engineering Manual

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 or Non-NAS IT 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.

The service team prepares a screening information request (SIR) that solicits proposals from potential vendors. The CM specialist provides CM-related input to the SIR, including:

The service team CM specialist evaluates and scores configuration plans, processes and procedures of potential vendors, and determines whether vendor proposals are in compliance with CM requirements in the system specification.

The CM specialist establishes and maintains a program support library containing technical baseline documents, change vehicles, and any other information needed for configuration management 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 recommended.

The service team ensures establishment and maintenance of 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 as-built drawings) a service-area CCB may be the appropriate approval and change authority.

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.

The service team establishes and places under configuration control the allocated baseline. The allocated baseline consists of documentation describing the allocation of 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. The allocated baseline governs all development activity by the contractor. After approval, changes to the allocated baseline are controlled and managed by the service organization CCB or contractor configuration control processes (or both), as specified in the implementation strategy and planning attachment and prime contract.

Service team configuration management specialist

Testing confirms 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 implementation strategy and planning attachment) establishes and manages change to test configurations. This applies to both developmental and operational testing.

Working in conjunction with the service team, the designated service organization CM board establishes and maintains the facility/site configuration baseline (end-state and as-built). 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 facility configuration for both end-state and as-built. This activity involves establishing and managing facility/site configuration drawings, as well as validating site configuration processes and procedures.

Service-area CCBs control changes to facility equipment layout drawings, critical power panel designation, and unique regional equipment. They also regularly validate the accuracy of baselined facility space and power panel documentation.

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) STR(s)

Software version document

Computer operation manual

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 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 lower-level system segments.

Specifically, the functional configuration audit verifies that:

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.

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 leader certifies satisfactory completion of the audit.

The product baseline includes 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 appropriate NAS or non-NAS IT change proposal.

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, NAS change proposals, configuration-controlled documents and associated baselines, PTRs and HDRs, and system support directives and associated baselines. Status accounting involves recording, storing, and accessing information needed to manage configuration items effectively, including:

The service team manages change control of the product baseline. This involves the 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.