Skip to main content

FMEA Workflow Overview

Saphira’s FMEA Workflow provides a guided, four-phase process for conducting comprehensive Failure Mode and Effects Analysis with AI-assisted failure mode generation, automatic risk priority calculations, and architecture-aware context. Access the FMEA Workflow from the Dashboard by clicking Run Safety AnalysisFMEA, or directly navigate to the FMEA tab.

Workflow Phases

The FMEA Workflow consists of four sequential phases: FMEA Workflow Overview
1

Reference Documents

Upload existing FMEA spreadsheets, specifications, or reference material
2

Item Selection

Select or create systems, subsystems, and components for analysis
3

FMEA Configuration

Choose template type and configure columns for generation
4

FMEA Generation

Generate failure modes with AI assistance and review results

Phase 1: Reference Documents

Upload existing documentation to enrich the FMEA generation with context.
Purpose: Provide context and extract existing data to inform failure mode generation.Supported Uploads:
  • Existing FMEA Spreadsheets: Import past FMEA data to build upon
  • Technical Specifications: System specs for architecture context
  • Item Definitions: System/component definitions
  • Architecture Diagrams: Visual system structure
Upload Types:
  • Item Definitions: Documents describing system structure
  • Past FMEA: Existing FMEA spreadsheets to extract and continue
Documents auto-populate systems and components, providing architecture context for AI-assisted generation.

Extraction Options

Extract Item Definitions

Upload system specifications to extract:
  • System hierarchy
  • Component lists
  • Interfaces and connections
  • Operating modes

Extract Past FMEA

Upload existing FMEA to extract:
  • Previous failure modes
  • Historical S/O/D ratings
  • Existing controls
  • Action items

Phase 2: Item Selection

Select or create the items to analyze. Items are organized hierarchically.
Hierarchy Levels:
  • System: Top-level system (e.g., “Brake Control System”)
  • Subsystem: Major subsystems (e.g., “Hydraulic Unit”, “ECU”)
  • Sub-subsystem: Lower-level groupings
  • Component: Individual components (e.g., “Pressure Sensor”, “Valve”)
Item Selector Features:
  • View all items from project data
  • Filter by hierarchy level
  • Search by name
  • Create new items inline
  • Items extracted from documents appear here automatically

Item Context

When you select an item, Saphira loads its context:
  • Function: What the item does
  • Interfaces: Connections to other items
  • Operating Modes: Normal, maintenance, degraded states
  • System Boundary: Scope of analysis
This context informs AI-generated failure modes with architecture-aware suggestions.

Phase 3: FMEA Configuration

Configure the FMEA template and columns for your analysis.

FMEA Templates

Standard FMEA with RPN calculation.Columns:
ColumnTypeDescription
ComponentTextComponent being analyzed
FunctionTextFunction of the component
Failure ModeTextHow the component can fail
Failure EffectTextImpact of the failure
Failure CauseTextRoot cause of failure
Severity (S)1-10Impact rating
Occurrence (O)1-10Likelihood rating
Detection (D)1-10Detection capability
RPNCalculatedS × O × D (1-1000)
ActionsTextRecommended actions
Modern FMEA approach per AIAG-VDA Handbook.Columns: Same as FMEA-RPN but with:
ColumnTypeDescription
APNCalculatedAction Priority Number
APN provides improved action prioritization over traditional RPN.
Extended FMEA with criticality analysis per MIL-STD-1629A.Additional Columns:
ColumnTypeDescription
Criticality IndexNumberQuantitative criticality measure
RPNCalculatedRisk Priority Number
Hardware-focused FMEA for functional safety (IEC 61508 / ISO 26262).Columns:
ColumnTypeDescription
ComponentTextHardware component
Failure ModeTextFailure mode description
Failure RateNumberλ (failure rate)
Failure Mode DistributionNumberDistribution percentage
System Level EffectTextEffect at system level
Safety EffectTextSafety impact
Diagnostic CoverageNumberDC percentage
Safe Failure FractionNumberSFF calculation
SIL LevelTextAchieved SIL
Used for PFH/PFD calculations and architectural constraints verification.
Extended templates with insurance/loss assessment fields.Additional Columns:
ColumnTypeDescription
Estimated Loss (USD)NumberFinancial loss estimate
Is Catastrophic LossBooleanCatastrophic flag
Loss TypeDropdownOperational, Safety, Reputation, Regulatory, Financial, Environmental
Uniqueness Score1-5Uniqueness rating
LP ScoreNumberLoss Probability score
Is Insurer FlaggedBooleanInsurer attention flag
Available for: Insurer FMEA-RPN, Insurer FMEA-APN, Insurer FMECA

Configuration Options

  • Select which columns to include in generation
  • Add custom columns with name and type
  • Reorder columns as needed
  • Toggle columns on/off
  • Max Failure Modes: Number to generate per component (default: 5)
  • Additional Instructions: Custom guidance for AI generation
  • Standards Context: Select applicable standards (ISO 26262, IEC 61508, etc.)

Phase 4: FMEA Generation

Generate failure modes with AI assistance using your configuration.

Generation Process

1

Click Generate

Start generation with the “Generate Failure Modes” button
2

AI Analyzes Context

Saphira analyzes:
  • Selected component/system
  • Architecture relationships
  • Reference documents
  • Standards context
3

Failure Modes Stream In

Results appear in real-time as they’re generated
4

Review and Edit

  • Edit any cell inline
  • Adjust S/O/D ratings
  • RPN/APN auto-recalculates
  • Add recommended actions

Generated Failure Mode Fields

For each failure mode, Saphira generates:
Format: “Provide [function description] ([Component Path])”Example: “Provide stable power to ECU electronics (Power Supply → Protection & Filtering → DC-DC)”Identifies the function and its location in the system architecture.
Technical description of how the component/system fails.Example: “Loss of ECU supply voltage during operation”Specific and technical—avoids generic descriptions.
Cascading effects traced through the system.Format: “[Local effect] → [Component effect] → [System effect] → [Vehicle effect]”Example: “ECU resets or shuts down → loss of actuator control → possible unexpected torque/braking behavior”
Root cause or failure mechanism with multiple potential causes.Example: “Over-current or short on load side, over-temperature of DC-DC, connector looseness, wiring fault”
Existing controls, diagnostics, and safeguards.Example: “Input fuse, reverse polarity & over-voltage protection, DC-DC thermal shutdown, vehicle power rail monitoring, diagnostic trouble code (DTC) on undervoltage”
Severity (S): 1-10 based on consequences
  • 1 = No effect
  • 10 = Catastrophic / life-threatening
Occurrence (O): 1-10 based on likelihood
  • 1 = Extremely unlikely
  • 10 = Almost certain
Detection (D): 1-10 based on detection capability
  • 1 = Almost certain detection
  • 10 = No detection method
Each rating includes justification.
RPN = S × O × D (Range: 1-1000)Higher RPN indicates higher risk priority.Saphira highlights high-priority items (RPN > 100) for action.

Review Features

Inline Editing

Click any cell to edit. Changes auto-save and RPN recalculates.

Diff Highlighting

New and changed items are highlighted for easy review.

Component Grouping

Failure modes grouped by component with expandable sections.

FMEA Assistant

AI chat assistant for guidance on ratings and actions.

FMEA Metrics Dashboard

Track your FMEA progress with real-time metrics:
MetricDescription
Total Failure ModesCount of all failure modes
Components with FMEAComponents analyzed
Components without FMEAGap identification
Avg Failure Modes/ComponentCoverage depth
Failure Modes by SystemDistribution view

Completeness Analysis

Click Analyze Completeness to get AI-powered assessment:
  • Missing failure mode categories
  • Coverage gaps by component
  • Recommended additional analyses
  • Standards compliance check

Export Options

Export your FMEA in multiple formats:

Excel (XLSX)

Full FMEA worksheet with all columns and formatting

CSV

Data export for integration with other tools

PDF Report

Formatted report for documentation

Integration with Safety Workflows

FMEA failure modes trace to other Saphira artifacts:
  • Requirements: Link failure modes to requirements they inform
  • HARA: Connect failure modes to hazards they could cause
  • Test Cases: Generate verification tests for detection controls
  • Safety Functions: Link to safety mechanisms that mitigate failures
  • GSN Safety Case: Failure mode coverage as evidence

Best Practices

Upload architecture diagrams and item definitions first. This provides context for more accurate failure mode generation.
Start at system level, then drill down to subsystems and components. System-level failure modes inform component-level analysis.
The AI assistant can help with:
  • Severity rating calibration
  • Detection control suggestions
  • Action recommendation refinement
Review generated failure modes and provide feedback. The AI learns from your edits to improve future generations.