Skip to main content
Source file: modules/RiskTemplates/PFMEATemplate/attachments/risksheet.json

Hierarchy Structure

LevelNameControl ColumnWork Item Link
L1Process StepitemprocessStep via assesses link role
L2Failure ModefailureModeBound to description field
L3Causecausescause work items via cause link role

Comparison with DFMEA

The PFMEA risksheet shares the same SxOxD=RPN scoring pattern as the DFMEA risksheet but differs in several key areas:
FeatureDFMEAPFMEA
L1 entityFunction (function)Process Step (processStep)
L2 bindingCustom failureMode fieldBuilt-in description field
L3 causesFree-text (causeOfFailure)Linked work items (multiItemLink)
Component resolutionParent systemElementParent heading work item
Function scopingqueryFactory filters by subsystemNo queryFactory (unscoped)
HARA cross-referenceYes (riskRecord column)No
Auto-descriptionYes (formula column)No

Column Reference

Identification Columns

Column IDTypeBinding / LinkLevelDescription
componentserverRenderVelocityResolves parent heading work item of the process step
itemitemLinkassesses -> processStep1Links to Process Step work items
failureModetextdescription field2Failure mode description (uses built-in description)
(effect)texteffectOfFailure field2Downstream effects of the failure
causesmultiItemLinkcause -> cause items3Linked cause work items (structured)

Pre-Mitigation RPN Columns

Column IDTypeBindingDescription
sevenumfmSeverity (failureModeSeverity)Severity rating (shared pre/post)
occenumpremitigationFMOccurrencePre-mitigation occurrence
detenumpremitigationDetectionPre-mitigation detection
(RPN)formulacommonRpn = S x O x DPre-mitigation Risk Priority Number

Mitigation Task Columns

Column IDTypeBindingDescription
tasktaskLinkmitigates -> taskMitigation action link
taskTitletexttask.titleAction name
taskStatusenumtask.statusAction status
requirementsserverRenderVelocityLinked sys_req/des_req
verificationserverRenderVelocityTwo-hop: task -> requirements -> verif_test_case

Post-Mitigation RPN Columns

Column IDTypeBindingDescription
occNewenumpostmitigationFMOccurrencePost-mitigation occurrence
detNewenumpostmitigationDetectionPost-mitigation detection
rpnNewformulacommonRpnNew = S x Onew x DnewPost-mitigation RPN

RPN Formula and Color Coding

The RPN calculation and color coding are identical to DFMEA: RPN = Severity x Occurrence x Detection
RPN RangeColorCSS Class
1 — 10Greenrpn1
11 — 30Amberrpn2
> 30Redrpn3

Key Differences from DFMEA

Structured Causes

Unlike DFMEA where causes are free-text (causeOfFailure binding), PFMEA uses multiItemLink with the cause link role. This makes causes first-class traceable work items that can be independently tracked, linked, and reported on.

Component Resolution via Headings

PFMEA resolves the component column by finding the parent heading work item type (not systemElement as in DFMEA). This means PFMEA uses document headings as process area grouping rather than the product decomposition hierarchy.

No Subsystem Scoping

PFMEA does not define a queryFactory, so process steps are not filtered by subsystem or component. All process steps in the project are available for selection.

No HARA Cross-Reference

PFMEA does not include a riskRecord cross-reference column. Process failure modes are not directly linked to HARA risk records.

Data Types

Data TypeWork Item TypeLink Role
riskfailureMode
tasktaskmitigates