DI-SAFT-82502
Functional Hazard Analysis (FHA)
Specifies requirements for a Functional Hazard Analysis (FHA) used to identify and evaluate system functions and associated hazards, mapping Safety Significant Functions (SSF) and Safety Significant Items (SSI) to the system design architecture.
Approval DateSeptember 30, 2025
AMSC NumberF10603
Preparing Activity40 (AFMC/SE)
Project NumberSAFT-2025-014
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Related
DI-SAFT-80101DI-SAFT-80102DI-SAFT-80105DI-SAFT-82085
Application & Interrelationship
—
Use & Relationship
The Functional Hazard Analysis (FHA) is used for identification and evaluation of functions within the system and associated hazards. The FHA is a mapping of the Safety Significant functions (SSF) and Safety Significant Items (SSI) to the system design architecture.
a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.
b. This DID is related to DI-SAFT-80101, System Safety Hazard Analysis Report, DI-SAFT-80102, Safety Assessment Report (SAR); and DI-SAFT-80105 System Safety Program Progress Report (SSPPR); and DI-SAFT-82085, Hazard Tracking System (HTS) Data.
(Copies of these DIDs are available online at https://quicksearch.dla.mil.)
Preparation Instructions
1Reference documentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2FormatThe FHA shall be in the contractor's format.
3ContentThe FHA shall include the following information:
3.1IntroductionThe FHA shall state, in narrative form, the purpose of the FHA.
3.2System DescriptionThis section shall include the following:
3.2.1The physical (e.g. hardware) and functional (e.g. hardware and software) characteristics of the system and its subsystems at a major component level.
3.2.2A functional description of each subsystem shall include:
3.2.2.1A functional description of each component of the interfaces between the identified subsystems and components.
3.2.2.2Interface descriptions addressing the connectivity, functional inputs and outputs.
3.3Function AssessmentDocumentation of the assessment shall address the implementation of the identified functions.
3.3.1Function mapping shall be included identifying SSI components for each SSF.
3.3.2The functional map documentation shall be decomposed to the lowest level of the design.
3.3.3SSIs shall be designated either SCI (e.g. Catastrophic or Critical severity potential) or SRI (e.g. Marginal or Negligible severity potential) as appropriate.
3.3.3.1NOTEAn SSI may be SCI for one SSF but SRI for a different SSF.
3.3.3.2NOTEAn SCF may possess both SCIs and SRIs thereby reflecting functional redundancies or the lack thereof.
3.3.4Interfaces between subsystems, hardware components, and units of software shall be documented within the assessment.
3.3.4.1Unit of SoftwareInformation needed to properly characterize software being cited. The program's definition of what a Unit of Software is (e.g. CSCI, CSC, CSU); this definition is to be used in all documentation required by this DID.
3.3.5Interfaces with human and environmental design aspects shall be annotated.
3.4Documentation of the summary of HTS hazards related to each SSF shall be included.
3.5Documentation of the summary for each unit of software shall include which SSFs are supported, the SCC and the SwCI.
3.6References and RemarksAny additional technical information associated with the FHA.
Schema v3.0Community-maintained · Verify against ASSIST 