Skip to main content

​
What you will achieve

After completing this checklist, you will have:
  • Verified all TestAuto2 components are installed and accessible
  • Created your first system structure with hierarchical elements
  • Established a functioning HARA workflow with sample hazards
  • Set up an FMEA document with failure mode tracking
  • Confirmed dashboard reporting and traceability links work
  • Identified your primary navigation paths for daily work

​
Prerequisites

Before starting this checklist:
  • TestAuto2 solution is installed on Polarion 23.x or higher
  • You have project member access or higher permissions
  • Nextedy Risksheet and PowerSheet licenses are active
  • You have reviewed the Solution Overview
This checklist assumes the installation is complete. If dashboards or risksheets fail to load, contact your Polarion administrator to verify solution deployment.

​
The 60-Minute Quick Start Path

diagram

​
Step 1: Verify Component Access (5 minutes)

Navigate through each critical component to confirm your environment is ready. Actions:
  1. Open the Home Dashboard from the Polarion project home page
  2. Verify you see six space tiles: Requirements, Design, Risks, Testing, Process, Documentation
  3. Click Risks Space → confirm the dashboard loads with document inventory sections
  4. Click ** Safety Engineer Dashboard** from the role dashboards menu
  5. Verify the Whole RTM PowerSheet link opens a tabular view
What you should see:
  • Statistics cards showing counts (likely all zeros in new projects)
  • Navigation cards with report icons and sheet icons
  • Nextedy branding footer with copyright notice
Add your primary role dashboard to browser favorites. For safety engineers, the Safety Engineer Dashboard becomes your daily entry point.
Checkpoint: All dashboards load without errors. If you see “Widget failed to load” messages, verify Nextedy Solutions macros are installed in .polarion/pages/_default/.

​
Step 2: Create System Structure (10 minutes)

Build a minimal three-level system hierarchy to support hazard analysis. Actions:
  1. Navigate to Design Space → Create Work Item → Select System Element
  2. Create root element:
    • Title: “Autonomous Emergency Braking System”
    • Element Type: System
    • Status: Active
  3. Create two subsystem children (use Create Child action):
    • “Radar Sensor Subsystem” (Element Type: Subsystem)
    • “Brake Actuator Subsystem” (Element Type: Subsystem)
  4. Open System Structure Navigator report from Design Engineer Dashboard
  5. Verify the hierarchy displays correctly
Visual verification:
Every FMEA document will link to a specific system element. This hierarchy becomes the structural backbone of your risk analysis.
Checkpoint: System Structure Navigator shows your three-level hierarchy with correct parent-child relationships.

​
Step 3: Create HARA Document and First Hazard (15 minutes)

Establish ISO 26262 hazard analysis workflow. Actions:
  1. Navigate to Risks Space → Documents section
  2. Create new module:
    • Title: “AEB HARA Analysis”
    • Document Type: HAZID (Risk Specification)
    • Space: Risks
  3. Open the new document → verify Risksheet loads (grid interface appears)
  4. Click Add Hazard (+ button in grid toolbar)
  5. Fill first hazard row:
    • Title: “Unintended braking activation”
    • System Element: (link to “Autonomous Emergency Braking System”)
    • Severity: S2 (Moderate injuries)
    • Exposure: E3 (Medium probability)
    • Controllability: C2 (Normally controllable)
    • ASIL: (auto-calculated → should show ASIL B)
  6. Create linked Safety Goal (use Derive Safety Goal action from context menu)
  7. Verify traffic light appears green in “Pre-Mitigation Status” column
What you should see:
  • Risksheet grid with editable cells (Excel-like behavior)
  • ASIL auto-calculation formula working (S2+E3+C2 → ASIL B)
  • Traffic light indicators in status columns
  • ▶ Intro Tour button in page footer (click to see guided tour)
If this is your first time using Risksheet, click the ▶ Intro Tour button. The 8-step guided tour explains grid editing, view switching, traffic lights, and high-risk tracking in under 2 minutes.
Checkpoint: HARA document shows one hazard with valid ASIL classification and linked safety goal. Traffic light is green.

​
Step 4: Create FMEA Document and Failure Mode (15 minutes)

Set up AIAG-VDA FMEA workflow linked to your system structure. Actions:
  1. Return to Risks Space → create new module:
    • Title: “Radar Sensor DFMEA”
    • Document Type: Design FMEA
    • Space: Risks
  2. Open document → Risksheet loads with FMEA column layout
  3. Click Add Failure Mode
  4. Fill failure mode row:
    • Title: “Radar sensor provides erroneous distance data”
    • System Element: (link to “Radar Sensor Subsystem”)
    • Severity (S): 8 (Severe impact on braking decision)
    • Occurrence (O): 5 (Moderate failure rate)
    • Detection (D): 6 (Low detection capability)
    • Action Priority: (auto-calculated → should show High)
  5. Verify RPN calculation appears (S×O×D = 240)
  6. Switch to Post-Mitigation view using view dropdown
  7. Observe “Pre-Mitigation Status” traffic light shows red (high-risk)
Progressive workflow views:
ViewPurposeWhen to Use
Initial AssessmentS, O, D rating entryFirst-pass failure mode identification
Mitigation PlanningRisk control linkageAfter initial ratings complete
Post-MitigationPost-control S, O, DAfter mitigations implemented
High: RPN ≥ 200 or S ≥ 8 or (S ≥ 7 AND O ≥ 6)
Medium: RPN ≥ 100
Low: RPN < 100
These thresholds are configurable in risksheet formula settings.
Checkpoint: DFMEA document contains one failure mode with calculated RPN and Action Priority. High-risk traffic light indicator is visible.

​
Step 5: Create Verification Test Case (10 minutes)

Establish V&V workflow and traceability linkage. Actions:
  1. Navigate to Testing Space → Create Work Item → Verification Test Case
  2. Create test case:
    • Title: “Verify radar sensor distance accuracy”
    • Verifies: (link to your failure mode from Step 4)
    • Test Method: Inspection
    • Acceptance Criteria: “Distance error < 5% at 10-50m range”
  3. Open System Verification Sheet PowerSheet from V&V Engineer Dashboard
  4. Verify your test case appears with linked failure mode reference
  5. Check Verification Coverage KPI on V&V Engineer Dashboard (should show partial coverage)
Traceability chain established:
Verification tests design outputs against design inputs (are we building it right?).
Validation tests product against user needs (are we building the right thing?).
Use Verification Test Cases for technical compliance, Validation Test Cases for customer acceptance.
Checkpoint: PowerSheet shows test case with failure mode linkage. Coverage KPI is non-zero on dashboard.

​
Step 6: Dashboard Review and Navigation (5 minutes)

Confirm all workflow outputs appear in reporting dashboards. Actions:
  1. Open Safety Readiness Scorecard from Program Manager Dashboard
  2. Verify you see counts for:
    • 1 Hazard (from Step 3)
    • 1 Safety Goal (from Step 3)
    • 1 Failure Mode (from Step 4)
    • 1 Test Case (from Step 5)
  3. Open Standards Compliance Overview
  4. Check ISO 26262 compliance section → confirm HARA workflow shows “In Progress”
  5. Return to Home Dashboard → verify statistics on space tiles reflect new work items
Dashboard data flow:
Dashboards use Lucene queries that index asynchronously. If counts don’t update immediately after creating work items, wait 30-60 seconds and refresh the page.
Checkpoint: Dashboards show your newly created work items. Statistics match expected counts (1 hazard, 1 failure mode, 1 test case).

​
Validation Summary

After completing all six steps, you should have:
ComponentExpected State
System Structure3 elements (1 system, 2 subsystems)
HARA Document1 hazard, 1 safety goal, ASIL calculated
FMEA Document1 failure mode, RPN calculated, Action Priority assigned
Test Cases1 verification test case linked to failure mode
DashboardsAll statistics non-zero, KPIs showing partial coverage
RisksheetTraffic lights working, formulas auto-calculating
Total work items created: 7 (3 system elements + 1 hazard + 1 safety goal + 1 failure mode + 1 test case)

​
Next steps

​
Immediate next actions

  1. Expand your system structure: Create System Hierarchy
  2. Complete HARA workflow: Identify Hazards and Derive Safety Goals
  3. Build FMEA coverage: Define Failure Modes and Link to Risk Controls

​
Workflow-specific guides

​
Understanding the foundation

​
Troubleshooting

If any step failed:
Completion time: This checklist takes 45-60 minutes for first-time users. Experienced users can complete it in 30 minutes. You now have a functioning safety workflow baseline ready for production use.