MADE Knowledge Base > FAQ
Understanding and Performing Hazard Analysis in MADE 3.8.9
This KBA provides a step by step guide to create and use Hazard Diagrams.
Overview
Hazard Analysis in MADE is a systematic process used to identify and evaluate potential hazards within a system. The analysis helps in assessing risks and implementing appropriate control measures to ensure system safety.
Prerequisites
- Access to MADE 3.8.9 software
- Appropriate system model in the project explorer
- Access to SRA Module
- Valid criticality profile
Step-by-Step Process
Creating a Hazard Diagram
- Navigate to the project explorer.
- Select the desired model item.
- Right-click and select "Hazard Diagram."
Setting Up Risk Profile
- Access Preferences > Criticality profile editor.
- Select the appropriate risk profile for your analysis.
- Ensure the OSD-supported criticality profile is selected.
Assigning Criticality Parameters
- In the hazard diagram, select a hazard concept.
- Navigate to the 'MIL-STD-882E' tab in the Properties viewer.
- Assign appropriate criticality parameters.
- For software-related hazards: set the software control parameter value ≥ 1 in the 'MIL-STD-882E' section.
Managing Control Measures
If control measures exist:
- Right-click the concept.
- Select "Control Measure."
- Choose from predefined control measures or create custom ones.
- Review and adjust criticality parameters through the Barrier matrix in the control measures window.
Performing Hazard Path Analysis
- In the project explorer, select the system level item.
- Right-click and select "Hazard Path Analysis."
- Review initial risk values for each hazard path.
- Evaluate if risk meets safety requirements.
Risk Assessment and Mitigation
If risk exceeds the acceptable threshold:
- Assign hazard control measures to appropriate concepts.
- Right-click the concept and select control measures.
- Choose existing or create new control provisions.
- Revise criticality parameters using the Barrier matrix.
Key Components of Hazard Analysis
- Hazard Sources
- Initiating Mechanisms
- Target/Threat Outcomes
- Initial Risk Assessment
- Compensating Provisions
- Detection Methods
- Prevention Controls
- Substantiation Actions
Best Practices
- Always ensure the correct criticality profile is selected before beginning analysis.
- Document all control measures and their justifications.
- Regularly review and update hazard analyses as system changes occur.
- Pay special attention to software-related hazards and their control parameters.
Note: this process is iterative and may require multiple revisions to achieve acceptable risk levels for all identified hazards.
Source: https://support.sw.siemens.com/en-US/product/238942692/knowledge-base/KB000156622_EN_US · retrieved 2026-07-08