Functional Configuration Audit (FCA)
FCA is the formal examination of the "as-tested" characteristics of a configuration item where the focus is on design and performance suitability. FCA provides a systematic comparison of requirements with the results of tests, analyses, or inspections. Normally, test/analysis data is collected from a prototype or pre-production article. When a prototype of pre-production article is not produced, test/analysis data from the first article can be used. The FCA demonstrates System Development and Demonstration is sufficiently mature for entrance into Low Rate Initial Production.
The objective is to verify that the configuration item has achieved the performance specified in its functional, or allocated, configuration identification documents, and that it's operational and support documents are complete and satisfactory. An FCA is essentially a review of the configuration item's test/analysis data including software unit test results to validate the intended function or performance is met.
The Functional Configuration Audit is used to verify that the actual performance of a configuration item meets the requirements contained in its performance specification and to certify that the configuration item has met those requirements.
The FCA determines if the system produced (including production representative prototypes or LRIP units) is capable of meeting the technical performance requirements established in the specifications, test plans, etc. Among the issues addressed are:
The FCA is normally performed prior to Low Rate Initial Production and prior to or in conjunction with a Physical Configuration Audit (PCA). Although an FCA is only required once for each CI or system, a number of FCA-like activities may be accomplished at other times during the life cycle of the CI or system.
The time frame for audits will vary depending on the particular program. The configuration item's complexity may dictate an incremental audit approach throughout development until the completion of qualification testing. The FCA schedule should be delineated in the Configuration Management Plan but may be delineated in the system engineering management plan. The FCA should be executed after the functional baseline and allocated baseline have been established and submittal of the draft item detail specification (following Critical Design Review and/or Test Readiness Review) for the configuration item to be audited.
Software FCA should be performed prior to the hardware/software integration phase.
If performed incrementally throughout the system development, the process should end with completion of the design qualification test and review of configurations items discrepancies at the final system-level FCA.
The Program Management Office is ultimately responsible for the performance of audits. The Program Manager (PM) has overall disposition authority on audit results and reports. The PM's designee, who may be the system engineer (SE) or Logistics Management Specialist (LMS), will ensure audits requirements are properly delineated in the contract and the FCA is properly executed.
The FCA is conducted by Government and contractor personnel. Government personnel include representatives of:
The contractor participates in the FCA as provided in the contract. The contractor is responsible for the participation of subcontractors, vendors, and suppliers as appropriate.
The FCA is normally conducted at the Contractor's facility because of the availability of technical information and equipment.
Terms and Definitions
The PM's designee will serve as FCA team chairman and perform the following:
The audit team will perform the following functions:
 Go to Defense Standardization Program Office, ASSIST Database for the most up-to-date and ONLY official version of MIL-HDBK-61A. (http://assist2.daps.dla.mil/quicksearch/)