Session 2.5: Hazard Analysis

Note: This training deck is primarily composed of instructional screenshots (numbered dialog boxes, toolbar callouts, field highlights). The text below preserves all extractable slide text — titles, bullet points, discussion/exercise headings, and table content. Where a slide is dominated by an unlabeled screenshot, only the caption and step-list text could be extracted; screenshot visual detail itself is not represented.

Session 2.5: Hazard Analysis

SESSION 2.5 OUTLINE

2.5.1: Hazard Diagrams 2.5.2: Software Hazards 2.5.3: Hazard Path Analysis 2.5.4: Hazard Analysis Report

---

Session 2.5: Hazard Analysis

DISCUSSION 2.5 HAZARD ANALYSIS

This session will cover all aspects of how hazards are defined in MADE We will cover the difference between hardware and software hazards We will use hazard diagrams to define more detail of a hazard We will generate hazard path analysis to look at all of the generated hazards by the software

---

Session 2.5: Hazard Analysis

DISCUSSION 2.5.1 HAZARD DIAGRAMS

Hazard diagrams look at the sources & progression of hazards Hazard diagrams use a peer-reviewed taxonomy to assist in definition Taxonomy for hazard concepts are shown below

Hazard Concept Symbol Definition Hazard Source This is the basic hazardous resource creating the impetus for the hazard, typically a hazardous energy source such as Initiating explosives being used in the system. This can be thought as the basic hazardous component that produces a source of Mechanism danger.

Target / Threat This is the trigger or initiating event(s) causing the hazard to occur. The IMs cause actualization or transformation of the Outcome hazard from a dormant state to an active mishap state. This can be thought as the hazard trigger or trigger events that transform the hazard to a mishap.

                         This is the person or thing that is vulnerable (target), the threat to the target (threat), and the resulting severity outcome
                         (outcome) when the mishap event occurs. The outcome is the expected consequential damage and loss. This can be though
                         as the basic hazard threat.

---

Session 2.5: Hazard Analysis

EXERCISE 2.5.1 HAZARD DIAGRAMS

To construct a component hazard diagram:

Open the system model for the `Power Generation' subsystem

Right-click the `Control Unit' component

Select from right-click menu

The Hazard Diagram automatically incorporates failure concepts from the Failure Diagram, as they represent potential sources that can escalate into Hazards

---

Session 2.5: Hazard Analysis

EXERCISE 2.5.1 HAZARD DIAGRAMS (CONTINUED)

To construct a component hazard diagram:

Select Hazard Sources in the Hazard Concepts viewer

Search-and-drag Non-ionizing Radiation, Electromagnetic Interference sources onto the hazard diagram editor

Search-and-drag Extreme Heat, High Temperature initiating mechanisms

Search-and-drag Major loss of Operational Capability, Loss of Life, Severe Financial Impact TTOs

Connect the Hazard Concepts as show in the diagram

---

Session 2.5: Hazard Analysis

EXERCISE 2.5.1 HAZARD DIAGRAMS (CONTINUED)

Hazard diagrams have an underlying taxonomy; however, users may choose to edit the display name to better represent or provide additional information to the hazard concept.

To change the display name of the Electromagnetic Interference:

Select the Electromagnetic Interference source Using the Properties viewer, edit the Name field to: Radiofrequency Disturbance Add the narrative: Disruptions from unintended electromagnetic signals that interfere with electronic system

performance

---

Session 2.5: Hazard Analysis

DISCUSSION 2.5.2 SOFTWARE HAZARDS

Software hazards are potential mishaps or risks introduced by software systems that can impact system functionality, safety, or performance

Relevance to MIL-STD-882E

   Software is often a critical component in complex systems, capable of
     controlling or influencing hardware operations

   MIL-STD-882E mandates hazard analysis and mitigation strategies for
     software components to prevent or minimize risks

Examples:

   Incorrect data processing leading to unintended system commands
   Failure to initiate or terminate critical functions on time
   Software allowing unsafe operations due to logic errors

The Software Control parameter can be managed from the Properties viewer

---

Session 2.5: Hazard Analysis

EXERCISE 2.5.2 SOFTWARE HAZARDS

To edit a Software Hazard:

   Open the hazard diagram of the `Control Unit'
   Select the fault `Property Mismatch'
   Navigate to the Properties Viewer and select MIL-STD-882E tab
   Set the Software Control parameter to 5.0

---

Session 2.5: Hazard Analysis

DISCUSSION 2.5.3 HAZARD PATH ANALYSIS

Generate a comprehensive list of all model hazards on-demand Hazards are represented as discrete paths through the system Hazard Diagrams split paths into multiple branches for detailed

analysis Verify and refine hazard paths in real-time during modeling Use the Hazard Path Analysis feature to trace, validate, and

manage hazard paths

---

Session 2.5: Hazard Analysis

EXERCISE 2.5.3 HAZARD PATH ANALYSIS

To generate hazard path analysis in the model:

Right-click `Power Generation' sub-system in the Project Explorer Select: Hazard Path Analysis In the Hazard Path Analysis tab, expand item tree to view all the hazard paths

Note 1: The Hazard Cause shows the start' of each path Note 2: Verify that the path starting with Property Mismatch' has an assigned software control level

---

Session 2.5: Hazard Analysis

DISCUSSION 2.5.4 HAZARD ANALYSIS REPORT

Hazard Analysis Report can be automatically generated from the Report Wizard

   Report can be generated in PDF format
   Allows System or Sub-system level analysis report generation

---

Session 2.5: Hazard Analysis

EXAMPLE 2.5.4 GENERATE A HAZARD ANALYSIS REPORT

To generate a Hazard Analysis Report:

Select Reports Report Wizard from the main menu

Select PDF

Select Hazard Analysis Report

Select

Select Vehicle System in the System Hierarchy

Select to generate the report

---

Session 2.5: Hazard Analysis

SESSION 2.5 SUMMARY

2.5.1: Hazard Diagrams 2.5.2: Software Hazards 2.5.3: Hazard Path Analysis 2.5.4: Hazard Analysis Report