Skip to main content

Quick Navigation

Overview of Risksheet Types

Each risksheet configuration in TestAuto2 serves a specific phase of the safety lifecycle and maps to ISO 26262, AIAG-VDA FMEA, or IATF standards:
Risksheet TypePurposeStandardKey Metrics
HARASystem-level hazard identification and ASIL allocationISO 26262-3Severity (S), Exposure (E), Controllability (C), ASIL (A-D)
HAZIDPreliminary hazard screening and safety goal derivationISO 26262-3Risk level, preliminary ASIL, mitigation options
System FMEA (SFMEA)System element failure analysis across hierarchyISO 26262-4, AIAG-VDAFailure mode, effects, current controls, Action Priority
Design FMEA (DFMEA)Component-level design failure analysisISO 26262-5, AIAG-VDADesign weaknesses, protective measures, detection controls
Process FMEA (PFMEA)Manufacturing and assembly process failure analysisAIAG-VDA, IATF 16949Process failures, control plan items, reaction plans
Control PlanProduction control strategy and sampling planIATF 16949 / APQPMeasurement methods, sample frequency, reaction plans
Risk Control PlanMitigation actions and effectiveness trackingISO 26262-4Control effectiveness, risk reduction, residual risk

Risksheet Configuration Structure

Each risksheet is defined by a JSON configuration file (.json) stored in the Polarion project’s .polarion/nextedy/sheet-configurations/ directory. The configuration specifies:
  • Column groups — Logical sections (e.g., Identification, Assessment, Controls, Mitigation)
  • Column definitions — Field mappings to work item properties, formulas, and rendering
  • Views — Filtered and sorted table representations (e.g., “High-Risk Items Only”)
  • Cell styling — Color coding, traffic lights, conditional formatting
  • Levels — Multi-level hierarchy rendering (e.g., System → Subsystem → Component)

Typical Column Group Hierarchy

diagram

Key Configuration Patterns

1. Multi-level Hierarchy

System FMEA risksheets often display multiple system element levels:
System: AEB System
├─ Subsystem: Sensor Housing
│  ├─ Component: Camera Module (3 failure modes)
│  ├─ Component: Radar Module (4 failure modes)
│  └─ Component: Sensor Housing Assembly (2 failure modes)
├─ Subsystem: ECU Processing
│  ├─ Component: SoC (5 failure modes)
│  ├─ Component: Safety Co-Processor (3 failure modes)
│  └─ Component: Memory (2 failure modes)
└─ Subsystem: Vehicle Interface
   └─ Component: CAN Transceivers (1 failure mode)
This requires the nxFmeaElementBlock Velocity macro to render hierarchical element data alongside failure modes.

2. Risk Rating Formulas

  • FMEA (AIAG-VDA): RPN = Severity × Occurrence × Detection (0–1000)
  • Design FMEA: Action Priority (H/M/L) based on Severity and Occurrence thresholds
  • HARA (ISO 26262): ASIL = f(Severity, Exposure, Controllability) → A, B, C, D, or QM

3. Pre/Post-Mitigation Tracking

Most risksheets include dual columns for risk metrics:
  • Pre-Mitigation: Original assessment before controls are implemented
  • Post-Mitigation: Updated assessment after risk controls are in place
This tracks effectiveness and verifies risk reduction to acceptable levels.

4. Dynamic Views

Each risksheet supports filtered views:
ViewFilter Criteria
High-Risk ItemsAP = H (Design FMEA) or RPN > 100 (Process FMEA)
Open ActionsStatus = “Open” for mitigation actions
Verification GapsNo linked test cases or incomplete verification
Not StartedCurrent control effectiveness = None
CompleteAll assessment fields populated, post-mitigation verified

Integration with Work Item Types

Each risksheet configuration links to specific work item types in the RTM domain model:
  • Failure Mode — Core entity in FMEA risksheets (System/Design/Process)
  • Risk Record — Hazard assessment work item in HARA/HAZID
  • Risk Control — Mitigation action linked to failure modes
  • Process Step — Manufacturing step in PFMEA documents
  • Control Plan Item — Quality control activity (IATF 16949)
  • Test Case — Verification evidence for controls
Columns in risksheets are bound to custom fields on these work items (e.g., customFields.actionPriority, customFields.postMitigationRPN).

Customization and Best Practices

Risksheet JSON files are version-controlled in SVN. Always back up the configuration before making changes, and test in a sandbox project first.
Changing column field bindings or formula expressions can cause data loss or calculation errors. Document all changes and notify the project team.
When adding new rows to a risksheet, verify that existing views still render correctly. Some views may need filter criteria updates.

Section Index: