Skip to main content

Visual Diagrams

NirmIQ provides five visual diagram types to support the AIAG-VDA 7-step FMEA methodology. Each diagram uses data from your existing analysis — no separate data entry required.

Process Flow Diagram

Available for: PFMEA analyses

A vertical flowchart showing your manufacturing or assembly process steps in sequence.

What It Shows

  • Process steps as rectangular nodes, connected top-to-bottom
  • Parent-child relationships from the Structure Tree
  • Step sequence matching the order of structure elements

How to Access

  1. Open a PFMEA analysis
  2. Click the "Process Flow" sub-tab

Data Source

The diagram is generated from the Structure Tree elements of your PFMEA. Each structure element becomes a process step in the flow. The parent-child hierarchy defines the flow sequence.

Keep Your Structure Tree Updated

The Process Flow Diagram reflects your Structure Tree. Add or reorder structure elements to update the flow.

Use Cases

  • Visualize the manufacturing sequence before identifying failure modes
  • Present the process overview in team reviews
  • Include in PPAP (Production Part Approval Process) documentation

Function Net

Available for: DFMEA and PFMEA analyses

A three-column diagram showing how functions map across system hierarchy levels.

What It Shows

Three columns representing hierarchy levels:

ColumnLevelContent
LeftSystemTop-level functions
CenterSubsystemMid-level functions
RightComponentDetailed functions

Lines connect functions across levels to show relationships. This visualization corresponds to Step 3: Function Analysis of the AIAG-VDA 7-step process.

How to Access

  1. Open any DFMEA or PFMEA analysis
  2. Click the "Function Net" sub-tab

Data Source

Functions are pulled from the functions array defined on each Structure Tree element. The hierarchy level of the element determines which column it appears in.

Use Cases

  • Verify complete function coverage across all levels
  • Identify missing functions (elements without defined functions)
  • Communicate system architecture to cross-functional teams
  • Support AIAG-VDA Step 3 documentation requirements

Failure Net

Available for: DFMEA and PFMEA analyses

A three-column cause-effect visualization showing how failures propagate across system levels.

What It Shows

ColumnContentColor
LeftEffects (impact at higher level)Colored by AP
CenterFailure Modes (how the function fails)Colored by AP
RightCauses (root cause at lower level)Colored by AP

Lines connect causes → failure modes → effects to show the Failure Chain — a key concept in AIAG-VDA Step 4: Failure Analysis.

How to Access

  1. Open any DFMEA or PFMEA analysis
  2. Click the "Failure Net" sub-tab

Color Coding

Nodes are colored by Action Priority:

  • Red — High priority failure modes
  • Amber — Medium priority
  • Green — Low priority

This makes it easy to spot the most critical failure chains at a glance.

Data Source

Uses the parent_effect_id and linked_mode_id fields on failure modes to build chain relationships. If you've linked failure modes across hierarchy levels, the net shows the complete propagation path.

Use Cases

  • Trace how a component-level cause leads to a system-level effect
  • Identify common causes that affect multiple failure modes
  • Present failure analysis results to auditors and reviewers
  • Support AIAG-VDA Step 4 documentation requirements

Block/Boundary Diagram

Available for: DFMEA analyses only

An interactive diagram showing system components and their scope boundaries.

What It Shows

  • Blocks representing structure elements (components, subsystems)
  • Boundary rectangle (dashed line) showing the scope of the analysis
  • In-scope elements inside the boundary, out-of-scope outside
  • Connections between blocks showing interfaces

How to Access

  1. Open a DFMEA analysis
  2. Click the "Block/Boundary" sub-tab

Interactive Features

  • Drag blocks to rearrange the layout
  • Toggle scope — Click an element to mark it as in-scope or out-of-scope
  • Positions are saved automatically

Data Source

Blocks are created from Structure Tree elements. Position data (x, y coordinates) and scope status are stored on each element and persist between sessions.

Use Cases

  • Define what is and isn't included in the DFMEA scope
  • Identify interfaces between in-scope and out-of-scope components
  • Communicate analysis boundaries to stakeholders
  • Support AIAG-VDA Step 2: Structure Analysis

P-Diagram

Available for: DFMEA analyses only

A Parameter Diagram (P-Diagram) showing the relationship between inputs, outputs, control factors, noise factors, and error states.

What It Shows

The P-Diagram has five zones arranged around a central system block:

ZonePositionContent
Signal InputLeftWhat triggers the system (e.g., driver presses brake pedal)
Ideal ResponseRight-topDesired output when working correctly
Error StatesRight-bottomUndesired outputs (failure modes)
Control FactorsTopParameters the engineer can control
Noise FactorsBottomEnvironmental/usage factors outside control

How to Access

  1. Open a DFMEA analysis
  2. Click the "P-Diagram" sub-tab

Editing

The P-Diagram editor lets you:

  • Add items to each zone by clicking and typing
  • Remove items with the delete button
  • Rearrange items within zones
  • Data is stored as JSON on the analysis and auto-saves

Data Source

P-Diagram data is stored as a JSONB field on the FMEA analysis record. It is independent of the Structure Tree — you define the diagram content directly.

Use Cases

  • Identify noise factors that may cause failures (feeds into Failure Analysis)
  • Document the ideal response vs. error states for each function
  • Brainstorm control factors during team FMEA sessions
  • Support AIAG-VDA Step 2: Structure Analysis

Diagram Availability by FMEA Type

DiagramDFMEAPFMEAFMEA-MSR
Process FlowYes
Function NetYesYes
Failure NetYesYes
Block/BoundaryYes
P-DiagramYes

Best Practices

  1. Build the Structure Tree first — Most diagrams are generated from structure elements and functions
  2. Define functions on every element — The Function Net only shows elements that have functions defined
  3. Link failure modes across levels — The Failure Net is most valuable when cause-effect chains are connected
  4. Use diagrams in reviews — Visual representations help cross-functional teams understand the analysis
  5. Export for documentation — Use the refresh/export controls to capture diagrams for reports

What's Next?