Comprehensive Data and Traceability Model for AIAG–VDA FMEA in Polarion ALM with Nextedy Risksheet

Structure

System Elements & Characteristics

systemelement, characteristic

Hierarchical product structure

Function

Functional intent of each element

function

What the element does or shall do

Risk

Analysis records per failure

riskrecord

Captures failure modes, effects, causes, and ratings

Optimization

Actions and Verification loop

task, requirement, testcase

Defines mitigations and evidence of effectiveness

Step 2 – Structure Analysis

Define hierarchy of system elements and characteristics

System Element, Characteristic

System Element → contains → System Element ; System Element → has_feature → Characteristic

Step 3 – Function Analysis

Define functions and interdependencies

Function

System Element → defines → Function

Step 4 – Failure Analysis

Identify effects, modes, and causes

Risk Record

links to System Element, Function, Characteristic

Step 5 – Risk Analysis

Evaluate S/O/D and Action Priority (AP)

Risk Record fields (cf_ …)

Internal fields compute AP

Step 6 – Optimization

Define Actions and verify effectiveness

Task, Requirement, Test Case

Task → mitigates → Risk Record; Requirement → relates_to → Task; Test Case → relates_to → Requirement

1. Next Higher Level

Parent element containing the Focus Element

❌ Read-only (via link role parent)

Shows hierarchical context of analysis (§6.2.1)

2. Focus Element

Element currently analyzed

✅ (Risk Record → context → System Element)

Central anchor for the row; defines scope of failure analysis

3. Next Lower Level / Characteristic Type

Direct or indirect child element or feature affecting the Focus Element

✅ (Risk Record → characteristic → System Element/Characteristic)

AIAG–VDA permits “dependent structures” — not only immediate children (§6.2.2); represents dependencies one or two levels below.

1. Next Higher Level Function and Requirement

Function(s) of parent element

❌ Read-only (derived via parent’s defines)

Supports top-down traceability between levels (§6.3.1)

2. Focus Element Function and Requirement

Function performed by the Focus Element

✅ (Risk Record → function → Function)

Core function evaluated for failure modes (§6.3.2)

3. Next Lower Level Function and Requirement or Characteristic

Function or requirement of linked lower element / characteristic

❌ Read-only (derived from characteristic target’s backlinks)

Connects functional dependence to lower-level features (§6.3.3). Empty if target is Characteristic.

Failure Effect (FE)

Consequence to higher level or end user

✅

cf_failure_effect

AIAG–VDA Step 4 requires link to “next higher function” (§6.4.1).

Severity (S)

Rating of effect seriousness (1–10)

✅

cf_severity

Standard severity scale.

Failure Mode (FM)

How the Focus Element fails

✅

cf_failure_mode

Central to Risk Record definition (§6.4.2).

Failure Cause (FC)

Root cause at next lower level or feature

✅

cf_failure_cause

Enables bottom-up cause analysis (§6.4.3).

Prevention Control (PC)

Existing measure to prevent cause

✅

cf_prevention_control

Prevention is assessed first (§6.5.2).

Occurrence (O)

Likelihood of cause occurring

✅

cf_occurrence

Rated 1–10 per handbook table.

Detection Control (DC)

Existing control to detect cause or failure mode

✅

cf_detection_control

Distinguishes between PC and DC (§6.5.3).

Detection (D)

Detection rating (1–10)

✅

cf_detection

Numeric assessment for DC effectiveness.

Action Priority (AP)

Calculated priority (Low/Middle/High)

⚙️ Auto-computed via formula

Required output of AIAG–VDA Step 5 (AP replaces RPN).

Task ID / Title

Mitigation Action defined to reduce risk

✅

Task → Risk Record (mitigates)

Step 6 defines Actions that address causes and reduce risk (§6.6.1). Action owns the mitigation.

Action Type / Responsible / Dates / Status

Execution fields of the Action

✅

Task fields

Support planning and tracking of mitigation execution.

Requirements

Requirements resulting from completed Actions

❌

Requirement → Task (relates_to)

Step 6 demands “implementation and verification of actions” — the result becomes a new requirement (§6.6.2).

Req Verification

Verification evidence (Test Cases) confirming those Requirements

❌

Test Case → Requirement (relates_to)

Step 6 and 7 require proof of effectiveness (§6.6.3). Test Cases own the verification link.

New S/O/D & New AP

Re-evaluation after Action closure

✅ (fields + formula)

—

Represents the “residual risk” per AIAG–VDA Table 6-8.

Task → Risk Record

Action mitigates risk

The Action is the active entity executing mitigation; Risk is the object of mitigation.

Requirement → Task

Requirement relates_to the Action that produced it

Requirement is the result of Action execution, not its sub-task. Keeps Requirement independent and reusable.

Test Case → Requirement

Test Case relates_to Requirement

Verification objects always point to the specification they verify. Consistent with ISO 15288 and AIAG–VDA verification principles.

Top-Down Structure → Bottom-Up Failure

Parent/child links between System Elements and Functions mirror hierarchical decomposition (§6.2–6.3).

Linkage of Function and Failure

Each Risk Record connects Focus Element Function with its Failure Mode (§6.4).

Action Planning and Tracking

Step 6 columns map to Action responsibility, status, and timing (§6.6).

Verification of Effectiveness

Requirements and Test Cases close the loop of evidence (§6.7).

Residual Risk Evaluation

New S/O/D and AP fields support final assessment (§6.8).

Full Traceability

Every failure mode is connected upstream to its structure and function and downstream to its verified mitigation.

AIAG–VDA Compliance

All mandatory steps and relationships are covered in logical sequence.

Audit Readiness

Inspectors can trace from risk to verification evidence without manual cross-reference.

Reuse and Scalability

Functions, Requirements, and Tests are independent work items usable in other contexts.

Automation Potential

Computed Action Priority and visual color coding support automatic risk ranking and dashboards.