Skip to main content

​
Steps

​
1. Navigate to Risks Space

From the sidebar, click Risks to open the Risks space dashboard. This is where all FMEA documents are stored.

​
2. Create New Document

Click the ➕ Create Document button in the top toolbar. Fill in the document properties:
  • Title: [System Element Name] - System SFMEA (e.g., “AEB System - System SFMEA”)
  • Space: Risks
  • Type: System FMEA
  • Template: Select System-FMEATemplate from RiskTemplates space
Click Create.

​
3. Configure Risksheet Attachment

The template automatically includes a preconfigured risksheet.json attachment. Verify it contains: 
{
  "levels": {
    "1": {"type": "customerRequirement", "controlColumn": "title"},
    "2": {"type": "failureMode", "controlColumn": "fmFailureMode"},
    "3": {"type": "failureMode", "controlColumn": "fmCause"}
  },
  "views": [
    {"name": "1. Identify Failure Modes"},
    {"name": "2. Initial Risk Ranking"},
    {"name": "4. Define Mitigations"},
    {"name": "7. Risk Summary"}
  ]
}
This three-level hierarchy organizes:
  • Level 1: Customer requirement or item being analyzed
  • Level 2: Failure mode associated with that item
  • Level 3: Cause of each failure mode

​
4. Open in Risksheet

From the document page, click Open in Risksheet in the toolbar. The SFMEA risksheet opens with the progressive workflow view “1. Identify Failure Modes”. In the first row, set the System Element column to the system-level component you’re analyzing (e.g., “AEB System”). This creates traceability from FMEA to system architecture.
System FMEA analyzes top-level systems and major subsystems. For component-level analysis, use Design FMEA (DFMEA) instead. The hierarchy flows: System SFMEA → Subsystem SFMEA → Component DFMEA.

​
6. Add Customer Requirements

In Level 1 rows, select the customer requirements this system must satisfy. These drive the failure mode analysis — what can go wrong when trying to meet each requirement? diagram

​
7. Define Failure Modes

For each customer requirement, add child rows (Level 2) describing how that requirement could fail:
  • Click ➕ on the parent row to add a child
  • Enter Failure Mode description (functional failure, not root cause)
  • Set SC/CC Classification if this failure affects safety or critical characteristics
Level 2 is the what (functional failure), Level 3 is the why (root cause). Example: Failure Mode = “No obstacle detection”, Cause = “Camera module power loss”.

​
8. Define Causes

For each failure mode, add child rows (Level 3) describing potential causes:
  • Click ➕ on the Level 2 row
  • Enter Cause description (root mechanism)
  • Assess Severity, Occurrence, Detection ratings (1-10 scale)
The Action Priority (AP) formula calculates automatically:
  • High (H): Severity ≥9 OR (Severity ≥5 AND Occurrence ≥4) OR (Severity ≥6 AND Occurrence ≥4 AND Detection ≥5)
  • Medium (M): Any rating exceeds medium thresholds but doesn’t meet High criteria
  • Low (L): All ratings below medium thresholds

​
Verification

You should now see:
  • A three-level hierarchical SFMEA document in the Risks space
  • Customer requirements linked at Level 1
  • Failure modes with AP ratings color-coded (red = High, orange = Medium, green = Low)
  • Row headers color-coded by post-mitigation AP
  • The document appears in the Risks space dashboard document inventory

​
Next Steps

  1. Switch to view “2. Initial Risk Ranking” to review AP distribution
  2. Switch to view “3. Link Downstream DFMEA” to cascade risks to subsystem/component level
  3. Switch to view “4. Define Mitigations” to link risk controls
  4. Complete the Assess Severity, Occurrence, Detection workflow
  5. See Link to Upstream SFMEA to create hierarchical FMEA chains

​
See Also