1 SCOPE
1.1 Purpose
1.2 Application
1.2.1 Relationship to other requirements
1.2.2 Integration with other activities
2 REFERENCED DOCUMENTS
2.1 Issues of documents
3 DEFINITIONS
3.1 Terms
3.2 Acquiring activity
3.3 Closed loop failure reporting system
3.4 Contractor
3.5 Corrective action effectively
3.6 Failure
3.7 Failure analysis
3.8 Failure cause
3.9 Failure Review Board
3.10 Failure symptom
3.11 Fault
3.12 Laboratory analysis
4 GENERAL REQUIREMENTS
4.1 Contractor responsibility
4.2 FRACAS planning
4.3 Failure Review Board
4.4 Failure documentation
5 DETAILED REQUIREMENTS
5.1 Failure reporting
5.2 Failure analysis
5.3 Failure verification
5.4 Corrective action
5.5 Failure report close-out
5.6 Identification and control of failed items
APPENDIX A - APPLICATION AND TAILORING GUIDE
10 GENERAL
10.1 Scope
10.2 Tailoring requirements
10.3 Duplication of effort
10.4 Relationship of FRACAS to FMECA
20 REFERENCED DOCUMENTS
30 DEFINITIONS
40 GENERAL REQUIREMENTS
40.1 Importance of FRACAS
40.2 Data items
50 DETAILED REQUIREMENTS
50.1 FRACAS planning and documentation
50.1.1 Primary Objective
50.1.2 Request of FRACAS plan
50.1.3 Requirement addition
50.1.4 Failure data
50.2 FRACAS data collection
50.2.1 Effectiveness of FRACAS
50.2.2 Failures
50.2.3 Failure analysis
50.2.4 Results of failure analysis
60 DATA ITEM DESCRIPTIONS (DID)
60.1 Data