A Functional Configuration Audit shall be conducted for each configuration item for which a separate development or requirements specification has been baselined, except as otherwise required by the contract, and for the overall system, if required by the contract. The objective of the FCA shall be to verify the configuration item's and system's performance against its approved configuration documentation. Test data for the FCA shall be that collected from the test of the configuration of the item that is to be formally accepted or released for production (prototype or preproduction article). If a prototype or preproduction article is not produced, the test data shall be that collected from test of the first production article. Subject to prior Government approval, the FCA for complex items may be conducted in increments. In such cases, a final FCA may be conducted to ensure that all requirements of the FCA have been satisfied. In cases where item verification can only be completely determined after system integration and testing, the (final) FCA shall be conducted using the results of these tests.
220.127.116.11 Contract requirements. The schedule dates, and actual accomplishment dates for the FCAs shall be recorded in the CSA information system. The CI, or system, shall not be audited separately without prior Government approval of the FBL and ABL for the CI, or system, involved. In addition, the contractor shall make the final draft copy of the CI product specification available to the Government for review prior to the FCA, as specified in the contract.
18.104.22.168 Contractor responsibility.
a. Prior to the audit date, the contractor shall provide the following information to the Government:
(1) Contractor representation.
(2) Identification of items to be audited:
(b) Specification identification number.
(C) CI identification.
(3) Current listing of all deviations/waivers against the CI, either requested of or approved by the Government.
(4) Status of test programs to test configuration items with automatic test equipment (when applicable).
b. The contractor shall provide a matrix for each CI at the FCA that identifies the requirements of sections three and four of the specifications; includes a cross reference to the test plan, test procedures, and test report, results of demonstrations, inspections, and analyses for each requirement; and identifies each deficiency by deficiency report number. The matrix shall be made a part of the FCA minutes.
c. The contractor shall prepare an FCA check sheet
which identifies documents to be audited and tasks to be accomplished at the
FCA for the CI. A sample FCA Checklist is shown in Figure 4
22.214.171.124 Verification Procedures and requirements. The contractor shall provide the FCA team with a briefing for each CI being audited and shall delineate the test results and findings for each CI. As a minimum, the discussion shall include CI requirements that were not met, including a proposed solution to each item, an account of the ECPs incorporated and tested as well as proposed, and a general presentation of the entire CI test effort delineating problem areas as well as accomplishments. The audit should also include:
a. The contractor's test procedures and results shall be reviewed for compliance with specification requirements.
b. The following testing information shall be available for the FCA team.
(1) Test plans, specifications, descriptions, procedures, and reports for the CI.
(2) A complete list of successfully accomplished tests during which pre-acceptance data was recorded.
(3) A complete list of successful tests if detailed test data are not recorded.
(4) A complete list of tests required by the test requirements but not yet performed. (To be . performed as a system or subsystem test.)
(5) Preproduction test results.
c. An audit of formal test plans, specifications, and procedures shall be made and compared against the official test data. The results shall be checked for completeness and accuracy. Deficiencies shall be documented and made a part of the FCA minutes. Interface requirements and the testing of these requirements shall be reviewed. Completion dates for all discrepancies shall be clearly established and documented.
d. For those requirements which cannot be completely verified through the use of testing, the FCA shall determine whether adequate analyses or simulations have been accomplished and whether the results of the analyses or simulations are sufficient to insure that the CI meets the requirements in the specification. All ECPs that have been approved shall be reviewed to ensure that they have been technically incorporated and verified.
e. An audit of the test reports shall be performed to validate that the reports are accurate and completely describe the CI tests. Test reports, procedures, and data used by the FCA team shall be made a matter of record in the FCA minutes.
f. A list of the contractor's internal configuration documentation of the HWCI shall be reviewed to insure that the contractor has documented the physical configuration of the HWCI for which the test data are verified.
g. Drawings of the CI parts which are to be provisioned shall be selectively sampled to assure that test data essential to manufacturing are included on, or furnished with, the drawings.
h. CIs which fail to pass quality requirements are to be analyzed as to the cause of failure to pass. Appropriate corrections shall be made before a CI is subjected to a reverification.
i. Acknowledge accomplishment of partial completion of the FCA for those CIs whose verification is contingent upon completion of integrated system testing.
j. For CSCIs the following additional requirements shall apply:
(1) Review data base characteristics, storage allocation data and timing, and sequencing characteristics for compliance with specified requirements.
(2) Review all documents which comprise or describe the contents or the use of the software product for format and completeness. (e.g., SPS, User's Manual, VDD)
(3) Review the records that reflect the changes made to the developmental configuration for the CSCI.
(4) Review the listing of all versions of the developmental and non-developmental software for the CSCIs that are in the software library.
(5) Review the findings of all internal CM and software QA audits of the CSCI.
k. Preliminary and Critical Design Review (CDR) minutes shall be examined to ensure that all findings have been incorporated and completed.
126.96.36.199 Post-audit actions. After the FCA is completed, the contractor shall:
a. Publish copies of the FCA minutes.
b. Record the accomplishment and results of the FCA in the CSA Record for each CI audited.
c. Accomplish residual tasks for which they were identified as the responsible activity.
188.8.131.52 FCA Certification Package. A sample FCA
certification package is shown in Figures
5a - 5g