Quick Navigation
Create HARA Document
Set up a new HAZID/HARA analysis document in your project.
Identify Hazards
Systematically discover hazards from operational situations and system functions.
Assess S/E/C
Evaluate Severity, Exposure, and Controllability for ASIL determination.
Determine ASIL
Calculate Automotive Safety Integrity Level from hazard classification.
Derive Safety Goals
Transform hazard analysis into safety goals that guide design and verification.
Review & Approve
Submit HARA documents for review and track approval workflows.
Generate Reports
Create ISO 26262 compliance reports and risk matrices from your HARA.
HARA Process Overview
The HARA workflow consists of seven key steps that transform system operational knowledge into safety requirements:
Key Concepts
What is HARA?
HARA is a structured hazard analysis required by ISO 26262 (Functional Safety for Road Vehicles) to:- Identify all hazards that could result from system malfunctions
- Classify hazards by severity, exposure, and controllability
- Assign automotive safety integrity levels (ASIL) to guide design and verification rigor
- Derive safety goals that specify what the system must do to prevent harm
ASIL Classification
The Automotive Safety Integrity Level (ASIL) ranges from QM (quality managed) to ASIL D (highest):| ASIL | Rigor Level | Typical Application |
|---|---|---|
| QM | Quality Managed | No functional safety requirement |
| A | Low | Minor hazards, easily controllable |
| B | Medium | Moderate hazards, normal controllability |
| C | High | Significant hazards, limited controllability |
| D | Highest | Severe hazards, difficult to control |
S/E/C Matrix
ASIL is determined by combining three factors:
Common Tasks
- Create a HARA Document — Set up a new HAZID risksheet with operational situations
- Identify Hazards — Discover and document hazards using hazard brainstorming techniques
- Assess Severity, Exposure, and Controllability — Classify each hazard using S/E/C scales
- Determine ASIL — Calculate safety integrity levels from S/E/C combinations
- Derive Safety Goals — Transform hazards into high-level safety requirements
- Review HARA Document — Submit for cross-functional review and approval
- Generate HARA Report — Export ISO 26262 compliance evidence and traceability
Next Steps
Once you’ve completed HARA and derived safety goals, proceed to:- FMEA Workflow — Analyze failure modes at system, design, and process levels
- Requirements Management — Trace safety goals to system requirements
- Traceability Management — Link hazards through the full V-model
Related Concepts
- ISO 26262 Functional Safety — Standards framework for HARA
- ASIL Classification System — In-depth ASIL determination rules
- Safety Goal Derivation — How to write effective safety goals
- V-Model Methodology — How HARA fits into the development lifecycle