Prerequisites
- Project administrator or safety engineer role
- Access to the Risks space
- System elements or functions already defined in the project
Steps
1. Navigate to Document Creation
- From the sidebar, click Risks to open the Risks space dashboard
- In the document inventory section, click ➕ Create Document
- Select HAZID/HARA from the document type dropdown
Fill in the document creation form:
| Field | Value | Notes |
|---|
| Document Name | HAZID - [System Element Name] | Example: HAZID - AEB System |
| Document ID | Auto-generated or custom | Must be unique within project |
| Space | Risks | Pre-selected |
| Module Folder | Risks | Pre-selected |
| Status | draft | Will progress through workflow |
Use consistent naming: HAZID - [System] for top-level analysis, HARA - [Subsystem] for detailed assessments. This helps distinguish between preliminary hazard identification and full ASIL determination.
3. Select HARA Template
- In the Template dropdown, select HARATemplate from RiskTemplates space
- This loads the pre-configured risksheet with:
- Four-level hierarchy (System Element → Category → Phase → Hazard)
- ASIL auto-calculation formula
- Progressive workflow views
- Safety Goal link columns
4. Initialize Document Structure
After creation, the document opens in risksheet view:
- Click ** Add Row** to create your first hazard grouping
- In the System Element column (Level 1), click to select the system being assessed
- Type to search for existing
systemElement or function work items
- Select from dropdown or create new if needed
- Set Category (Level 2): Choose hazard classification (e.g., Functional Safety, Performance, Environmental)
- Set Operational Phase (Level 3): Select driving scenario (e.g., Highway, Urban, Parking, Emergency)
Always populate the System Element column before adding hazard details. The four-level hierarchy collapses rows under this top-level grouping for organized analysis.
5. Add Hazard Entries
For each identified hazard:
- Click the ➕ icon next to the operational phase row
- Fill in the Situation Analysis column group:
- Operational Situation: Describe the specific driving context (free text, 250px wide)
- Complete Hazard Identification columns:
- Hazard Name: Short title (e.g., “Delayed braking activation”)
- Description: Detailed hazard description (300px wide)
- Cause(s): What could trigger this hazard
- Consequence(s): Potential harms to occupants/road users
Switch to the HARA Classification view using the view selector at top-right, then rate each hazard:
| Parameter | Scale | Definition |
|---|
| Severity (S) | S0–S3 | Injury severity (S0=none, S3=life-threatening/fatal) |
| Exposure (E) | E0–E4 | Operational situation probability (E0=incredible, E4=>50% of time) |
| Controllability (C) | C0–C3 | Driver’s ability to prevent harm (C0=>99%, C3=<90%) |
| Condition | Result |
|---|
| S=0 OR E=0 OR C=0 | QM (no ASIL requirement) |
| S3 + E4 + C3 | ASIL D (highest) |
| S2 + E3 + C2 | ASIL C |
| S1 + E2 + C1 | ASIL A (lowest) |
ASIL cells display color backgrounds: QM (gray), A (green), B (orange), C (red), D (purple). High-integrity requirements (ASIL C/D) trigger dashboard alerts requiring safety mechanisms and verification rigor.
7. Derive Safety Goals
For hazards with ASIL A–D:
- Switch to Safety Goals view
- In the Safety Goal column, click ** Create Link**
- This creates a new
safetyGoal work item with:
- Inherited ASIL from parent hazard
- Bidirectional
derivedFrom link
- Auto-populated SG ID reference
- Fill in Safety Goal Title describing the required safe state
Example: For hazard “Failure to detect obstacle - no braking” (ASIL D), create safety goal “SG-02: Ensure obstacle detection reliability”.
8. Document Rationale
In the HARA Rationale column (300px text field):
- Justify each S/E/C rating with analysis data, standards references, or expert judgment
- Document assumptions (e.g., “E3 assumes 30% highway driving per usage profile”)
- Note any uncertainties or conservative estimates
ISO 26262 compliance requires documented rationale for all ASIL classifications. Missing rationale will trigger warnings in the HARA Report and compliance scorecard.
9. Save and Validate
- Click Save in the risksheet toolbar
- From the document actions menu, select ** Validate**
- Check for warnings:
- Incomplete assessments (missing S/E/C ratings)
- Unlinked high-ASIL hazards (C/D without safety goals)
- Empty rationale fields
10. Verification
You should now see:
- ✅ Document listed in Risks space dashboard under HAZID/HARA type
- ✅ ASIL distribution statistics on Home dashboard (QM/A/B/C/D counts)
- ✅ Safety goals appearing in Safety Readiness Scorecard
- ✅ High-ASIL alert (if any ASIL C/D hazards exist) on Home page
- ✅ Traceability links between hazards and safety goals in RTM reports
Progressive Workflow Views
The HARA template provides four stage-specific views:
| View | Focus | Columns Visible |
|---|
| Situation Analysis | Operational context | System Element, Category, Phase, Operational Situation |
| Hazard Identification | Causes and consequences | Hazard name, Description, Cause(s), Consequence(s) |
| HARA Classification | S/E/C/ASIL rating | Severity, Exposure, Controllability, ASIL, Rationale |
| Safety Goals | Mitigation linkage | SG ID, Safety Goal Title, SG ASIL (inherited) |
Common Pitfalls
Setting any parameter to zero (S0, E0, or C0) forces ASIL = QM regardless of other values. Verify that truly non-hazardous situations warrant zero ratings per ISO 26262-3 definitions.
Safety Goals automatically inherit ASIL from parent hazard via inheritASIL formula. Do not manually override SG ASIL—correct the hazard S/E/C rating instead.
See Also
