Skip to main content

Overview

The Aerospace Safety Solution implements a 5-point severity scale for FMEA analysis, aligned with ARP 4761 aerospace safety standards. This scale is used in System FMEA (SFMEA) and Design FMEA (DFMEA) to assess the impact of failure modes on system functions and design characteristics. The severity rating reflects the worst-case consequence of a failure mode without considering any risk controls or mitigation actions. This ensures objectivity in the initial hazard assessment phase.

Severity Scale Values

The Failure Mode Severity enumeration defines five severity levels, each with a numeric value (1–5), descriptive label, and color coding for visual identification in risksheet analysis.
ValueLabelDescriptionColor CodeHex Value
1No EffectFailure has no detectable impact on system operation or safetyGreen#58FF59
2MinorFailure results in minor degradation; crew workload slightly increased, minimal passenger discomfortYellow-Green#ADFF59
3MajorFailure results in significant degradation of system function; major reduction in safety margins, crew workload substantially increasedYellow#FFFF59
4HazardousFailure results in hazardous condition; large reduction in safety margins, inability to operate critical systemOrange#FFB359
5CatastrophicFailure results in loss of critical function; potential aircraft loss or fatality; unrecoverable by crew actionRed#FF5959

Aerospace-Specific Criteria

Each severity level incorporates aerospace-specific evaluation criteria:
  • No Effect (1): System continues normal operation; no impact on crew or passengers
  • Minor (2): Reduced comfort or convenience; crew can manage with normal procedures; no safety impact
  • Major (3): Significant system degradation; crew workload increases; requires non-normal procedures; safety margins reduced but recoverable
  • Hazardous (4): Large safety margin reduction; crew cannot recover without difficulty; potential for accident if additional failures occur
  • Catastrophic (5): Loss of critical safety function; potential hull loss, fatalities, or inability to recover through any crew action

Severity in RPN Calculation

Failure Mode Severity is the first component of the Risk Priority Number (RPN) calculation:
RPN = Severity × Occurrence × Detection
Where:
  • Severity (S): Impact of the failure (1–5 scale)
  • Occurrence (O): Probability the failure will occur (1–5 scale)
  • Detection (D): Likelihood the failure will be detected before reaching the user (1–5 scale)

RPN Interpretation and Action Priority

The resulting RPN guides risk control prioritization:
RPN RangeClassificationRecommended Action
1–10Low RiskMonitor; no immediate risk control required
11–30Medium RiskRisk control recommended; plan mitigation actions
> 30High RiskRisk control required; address before release
RPN values are relative rankings within your FMEA analysis. A high RPN in one failure mode does not necessarily mean it is unacceptable—it must be evaluated against organizational risk acceptance criteria and regulatory requirements (e.g., DO-178C, ARP 4754A objectives).

Severity Assessment Considerations

Pre-Mitigation vs. Post-Mitigation

The Aerospace Safety Solution tracks severity assessment across the analysis lifecycle:
  • Pre-Mitigation: Initial severity rating before any risk controls are implemented
  • Post-Mitigation: Severity rating after risk controls are in place (if applicable)
In strict FMEA methodology, severity reflects the inherent consequence of a failure and typically does not change after mitigation. Mitigation usually reduces occurrence and/or detection, not the severity of the failure if it occurs. If severity is reduced post-mitigation, document the rationale clearly (e.g., design modification that eliminates the worst-case consequence).
The Aerospace Safety Solution uses multiple severity/classification scales depending on the analysis type:
ScaleContextLevelsPurpose
FMEA SeveritySFMEA, DFMEA1–5 (No Effect to Catastrophic)Assess failure mode consequences in FMEA
ARP 4761 ClassificationFHA, PSSA, SSA5-level (Catastrophic to No Safety Effect)Classify functional failures in hazard analysis
MIL-STD-882E SeverityHazard Tracking4-level (Cat I to Cat IV)Classify hazards by injury/cost impact
Polarion Issue SeverityDefects, Changes6-level (Blocker to Trivial)Track non-safety work items
Each scale is appropriate for its specific analysis type and should not be confused or interchanged.

Severity Enumeration Schema

The failureModeSeverity enumeration is defined in the Aerospace Safety Solution configuration:
<!-- Source: .polarion/tracker/fields/failureMode-failureModeSeverity-enum.xml -->
<enum id="failureModeSeverity">
  <enumValue id="1">
    <name>No Effect</name>
    <description>Failure has no detectable impact on system operation</description>
    <color>#58FF59</color>
  </enumValue>
  <enumValue id="2">
    <name>Minor</name>
    <description>Failure results in minor degradation; crew workload slightly increased</description>
    <color>#ADFF59</color>
  </enumValue>
  <enumValue id="3">
    <name>Major</name>
    <description>Failure results in significant degradation of system function</description>
    <color>#FFFF59</color>
  </enumValue>
  <enumValue id="4">
    <name>Hazardous</name>
    <description>Failure results in hazardous condition; large reduction in safety margins</description>
    <color>#FFB359</color>
  </enumValue>
  <enumValue id="5">
    <name>Catastrophic</name>
    <description>Failure results in loss of critical function; potential aircraft loss or fatality</description>
    <color>#FF5959</color>
  </enumValue>
</enum>

Using Severity in Risksheet Analysis

In the Aerospace Safety Solution risksheet templates (System SFMEA, Component DFMEA), the severity rating appears in the “Sev.” column:
| Failure Mode | Effect(s) | Cause(s) | Sev. | Occ. | Det. | RPN |
|---|---|---|---|---|---|---|
| System takes too long to activate | Delayed system ready | Slow startup sequence | 3 | 4 | 1 | 12 |
| Sensor output incorrect | Loss of critical data | Sensor IC failure | 5 | 2 | 2 | 20 |
The color coding (green → red gradient) provides instant visual feedback on risk magnitude:
Severity 1 (Green)      ██ No Effect
Severity 2 (Yellow-Green) ██ Minor
Severity 3 (Yellow)      ██ Major
Severity 4 (Orange)      ██ Hazardous
Severity 5 (Red)        ██ Catastrophic

Assigning Severity Ratings

When completing FMEA analysis, assign severity based on:
  1. Worst-case consequence of the failure (ignoring likelihood or detectability)
  2. Aircraft operation context (normal cruise, takeoff, landing, emergency descent)
  3. Crew response capability (can crew recover? how quickly? what procedures apply?)
  4. Passenger impact (comfort, safety, potential injury or fatality)
  5. Regulatory criteria (ARP 4761 and DO-178C/DO-254 definitions)
  • Confusing severity with occurrence: A very likely failure of minor consequence ≠ high severity
  • Including risk controls in severity: Severity should reflect the failure itself, not the likelihood it will occur with existing mitigations
  • Over-rating non-critical failures: Severity 5 (Catastrophic) is reserved for failures with potential aircraft loss or fatalities—not inconvenience

Traceability to Failure Conditions and DAL

In the Aerospace Safety Solution, severity ratings in FMEA analysis connect to Functional Hazard Assessment (FHA) through the failure condition classification:
  • A Severity 5 (Catastrophic) failure mode may contribute to a Catastrophic failure condition in FHA
  • A Severity 4 (Hazardous) failure mode may contribute to a Hazardous failure condition in FHA
  • Each failure condition classification in FHA drives DAL (Design Assurance Level) allocation for safety requirements
This creates a traceable link from component-level FMEA failures → system-level FHA classifications → safety requirement DAL levels.
This page documents the Failure Mode Severity enumeration based on source code configuration. For aerospace-specific guidance on severity assessment in your organization’s FMEA process, consult your approved FHA/FMEA procedures and ARP 4761 / DO-178C standards documentation.

See Also

Code: .polarion/nextedy/models/rtm.yaml (0.64) · .polarion/tracker/fields/failureMode-custom-fields.xml (0.63) · .polarion/tracker/fields/failureCondition-classification-enum.xml (0.59) · .polarion/tracker/fields/failureMode-failureModeSeverity-enum.xml (0.57) · .polarion/nextedy/sheet-configurations/MIL-STD-882E Hazard Tracking Log.yaml (0.56) · modules/RiskTemplates/SubSystem-FMEATemplate/attachments/risksheet.json (0.56) · .polarion/tracker/fields/hazard-milSeverity-enum.xml (0.55) · .polarion/tracker/fields/failureCondition-custom-fields.xml (0.55) · .polarion/tracker/fields/severity-enum.xml, status-enum.xml, priority-enum.xml, implementationStatus-enum.xml, riskSpecification-document-status-enum.xml (0.53) · .polarion/pages/spaces/_default/Requirements Traceability Summary/page.xml, Verification Validation Summary/page.xml, Risk Control Effectiveness Report/page.xml, System Decomposition Report/page.xml, FMEA Coverage Report/page.xml, Classification Consistency Report/page.xml, System FMEA Report/page.xml, System Structure Navigator/page.xml (0.53)