DI-SESS-82381
System-of-Systems Hazard Analysis (SOSHA)
Documents an analysis of the System-of-Systems (SoS) to identify unique SoS hazards from integrating a Sense and Avoid (SAA) system with the Triton Unmanned Aircraft System (UAS) and to produce requirements to eliminate or mitigate them.
Approval DateMarch 31, 2022
AMSC NumberN10311
Preparing ActivityAS
Project NumberSESS-2022-018
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.
Application & Interrelationship
—
Use & Relationship
The purpose of the SOSHA is to perform and document an analysis of the System-of-Systems (SoS) to identify unique SoS hazards associated with the integration and use of a Sense and Avoid (SAA) system with the Triton Unmanned Aircraft System (UAS). This task will produce special requirements to eliminate or mitigate identified unique SoS hazards which otherwise would not exist, and to ultimately incorporate them into appropriate system documentation.
This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described in the contract SOW.
Preparation Instructions
1Reference documentsMIL-STD-882E Task 209, 11 May 2012.
2FormatThe SOSHA shall be submitted using Microsoft Word (and embedded Microsoft Excel files if logistically beneficial) in the Contractor's format.
3ContentThe Contractor is responsible for conducting an SOSHA on items under their cognizance, including any safety-relevant systems/software the Contractor may have subcontracted.
3.1Preparation Instructions
3.1.1General Instructions
3.1.1.1The SOSHA is meant for unclassified datause only. The Contractor shall ensure that only unclassified data is reported in the SOSHA. If classified data needs to be reported, then the Contractor shall contact the Requiring Office for special processing instruction.
3.1.2Specific Instruction
3.1.2.1Task descriptionAs applicable to this phase of the program, the contractor shall perform and document an analysis of the SoS to identify unique SoS hazards and mitigation requirements. The human shall be considered an element of the SoS, receiving both inputs and initiating outputs within the analysis:
3.1.2.1.1The contractor will provide traceabilityof all identified unique SoS hazards to architecture locations, interfaces, data, and the stakeholder(s) associated with each hazard.
3.1.2.1.2The contractor will assess the riskof identified unique SoS hazard(s) and recommend mitigation measures to eliminate the hazards or reduce the associated risks when the hazards cannot be eliminated. The hazard severity, hazard frequency of occurrence, and Risk Assessment Codes (RACs) defined in the Triton IFC-4 contract shall be used.
3.1.2.1.3The contractor will verify and validatethe effectiveness of recommended mitigation measures.
3.1.2.1.4The contractor shall document results ofthe analysis to include the following:
3.1.2.1.4.1SoS descriptionThis summary describes the physical and functional characteristics of the SoS. Reference to more detailed individual system descriptions, including specifications and detailed review documentation, shall be supplied when such documentation is available.
3.1.2.1.4.2Hazard analysis methods and techniquesProvide a description of each method and technique used in conduct of the analysis. Include a description of assumptions made for each analysis and the qualitative or quantitative data used.
3.1.2.1.4.3Hazard analysis resultsContents and formats may vary according to the individual requirements of the program and methods and techniques used. As applicable, analysis results should be captured in the Hazard Tracking System (HTS).
Schema v3.0Community-maintained · Verify against ASSIST 