Prerequisites
Before importing hazards, ensure you have:
- Excel file with hazard analysis data (HAZOP, HAZID, or HARA format)
- Column headers mapped to TestAuto2 work item fields
- ASIL ratings calculated (if importing HARA data)
- Write permissions to the Risks space in Polarion
Prepare the Excel File
Structure your Excel file to match the TestAuto2 hazard data model:
| Column Type | Columns | Example |
|---|
| Required | Hazard Title, Description, Severity (S), Exposure (E) | Power supply failure, Loss of 12V rail to ECU, S2, E3 |
| Optional | Controllability (C), ASIL, Safety Goal, System Element | C2, B, Ensure power redundancy, ECU Power Subsystem |
Excel column headers must exactly match TestAuto2 custom field IDs or standard Polarion field names. Use hazardSeverity not “Severity Level”, hazardExposure not “Exposure Rating”. Check the HARA Custom Fields reference for exact field IDs.
-
Open the HAZID Risksheet template in Polarion:
- Navigate to Risks space
- Open RiskTemplates/HAZIDTemplate document
- Click Open in Risksheet button
-
Map Excel columns to Risksheet levels:
- Hazards map to Level 0 (parent items)
- Harms/Consequences map to Level 1 (child items linked via
hasHarm role)
- Safety Goals map via
hasSafetyGoal link role
-
Create a staging Risksheet document:
- Click + New Document in Risks space
- Set document type to
riskSpecification
- Title: “HARA Import - [Source Name]”
- Attach
document.risksheet configuration from HAZIDTemplate
-
Prepare the import CSV:
- Export your Excel file as CSV (UTF-8 encoding)
- Verify delimiter is comma (
,) not semicolon
- Check that ASIL values use format
QM, A, B, C, D (not ASIL-A)
Import Via Polarion Work Item Import
-
Navigate to project Administration → Work Items → Import
-
Select import mode:
- Choose Create new work items
- Set work item type to
hazard
- Set space to
Risks
-
Map CSV columns to fields:
| CSV Column | Polarion Field | Notes |
|---|
| Hazard Title | title | Required, max 255 chars |
| Description | description | Supports HTML formatting |
| Severity (S) | hazardSeverity | Enum: s0, s1, s2, s3 |
| Exposure (E) | hazardExposure | Enum: e0, e1, e2, e3, e4 |
| Controllability (C) | hazardControllability | Enum: c0, c1, c2, c3 |
| ASIL | hazardASIL | Auto-calculated via formula if blank |
| System Element | systemElement | Link role to existing systemElement work items |
-
Preview the import:
- Review mapped fields for data type mismatches
- Check that enumerations are valid values
- Verify system element references exist in Polarion
If you omit the ASIL column, TestAuto2 will automatically calculate ASIL ratings using the formula IF(S=S0 OR E=E0 OR C=C0, "QM", LOOKUP(S,E,C)) based on ISO 26262-3 Table 4. Import Severity, Exposure, and Controllability values first, then let the formula populate ASIL.
- Execute the import:
- Click Import Now
- Monitor progress in the import log
- Check for validation errors (invalid enum values, missing required fields)
Add Imported Hazards to HAZID Risksheet
After work items are created, populate the HAZID Risksheet document:
-
Open HAZID - AEB System in Risksheet editor
-
Add imported hazards to the grid:
- Click ➕ Add Level 0 button (top toolbar)
- In the item picker dialog, search for your imported hazards
- Multi-select hazards (Ctrl+Click) and click Add
-
Verify ASIL calculations:
- Check that ASIL column shows correct values
- If ASIL is blank, verify S/E/C columns are populated
- Save the document to trigger formula recalculation
-
Link to existing safety goals (if applicable):
- In the Safety Goal column, click the cell
- Use the picker to link to existing
safetyGoal work items
- Or create new safety goals via Add Level 2 → Safety Goal
Post-Import Verification
You should now see:
- ✅ Hazard work items visible in Risks space work item table
- ✅ Hazards displayed in HAZID Risksheet grid with S/E/C/ASIL columns populated
- ✅ ASIL values match ISO 26262-3 classification matrix
- ✅ Safety goals linked via
hasSafetyGoal role (if configured)
- ✅ Traceability coverage metrics updated in Risks Space Dashboard
Polarion’s import does not automatically detect duplicate hazards by title. If you re-run the import, you will create duplicate work items. Always preview first and use Lucene queries (title:"Power supply failure") to check for existing hazards before importing.
See Also