FMEA software separates which failure information is owned by the analysis and which is owned by an underlying engineering model. Relyence documentation positions FMEA as a continual, living process that starts with selecting an analysis type and standard, then building an optional Analysis Tree before worksheet entry [3][1]. Ansys medini analyze documentation describes a stricter coupling: failure modes defined on a SysML element appear automatically in the FMEA worksheet, and editing the worksheet can write through to the model [6][2]. For healthcare device teams, that difference affects how a change to a design structure propagates into risk documentation.

A useful evaluation is therefore not about counting built-in templates. It is about asking which device-category artifacts already exist, whether analysis must stay synchronized with a system model or remain an independent controlled record, and what happens when legacy spreadsheets enter the tool. The supplied documentation answers parts of that question directly and leaves other parts unknown.

The Analysis Type Precedes the Tool Choice

Relyence help documentation lists the first FMEA step as deciding what type of analysis is best suited to the work [3]. The product supports DFMEAs, PFMEAs, Software FMEAs, piece-part FMECAs, FMEA-MSRs, and related documents such as Process Flow Diagrams and Control Plans [1]. FMEA-MSR describes monitoring and system response analysis for failures while a product is in use by a customer [3]. That distinction matters in healthcare settings where a device may need both a design analysis and a separate monitoring-response analysis rather than one merged worksheet.

SAE1025 documentation gives a parallel category breakdown and states that SwFMEA addresses risks specific to software during the design phase, while SupFMEA evaluates factors affecting product support and maintenance during design [8]. The standard also lists PFMEA as concentrating on manufacturing and operational processes [8]. A team that cannot first state whether a suspected failure belongs to software logic, supportability, or a manufacturing step may produce an unstructured worksheet regardless of which vendor is selected. The documented template coverage does not by itself establish that any organization's classification is correct.

Worksheet Ownership and Model Synchronization

Ansys medini analyze supports FMEA directly on SysML system and design models, with any structural or behavioral element available for analysis [2]. When failures are defined at an underlying element, they appear automatically in the FMEA table; adding or removing failures writes through to the model itself [6]. That behavior reduces duplication but assumes a SysML model is already the authoritative source for the device design. The documentation also provides a detached worksheet option with the system design model reference left empty, described as useful for legacy data import [2].

Relyence uses a different synchronization concept, described as always-in-sync across PFMEA documents and Knowledge Bank data reuse [1]. The documentation emphasizes an optional Analysis Tree for defining a product hierarchy or process list [3]. It is not stated in the provided anchors whether Relyence writes worksheet edits back into an external engineering model or treats the FMEA as the controlled record with internal synchronization only. For a healthcare evaluator, the practical question is whether the existing design artifact is a SysML model, a controlled spreadsheet, or a series of paper-based process maps.

What to Test in a Vendor Demonstration

For healthcare device teams, a practical demonstration should begin with the failure net concept documented by Ansys: causes and effects of a potential failure of an element [2]. Ask the vendor to create a failure mode for a single component, then verify whether the cause and effect relationship remains intact when the component is duplicated or copied. medini analyze documentation describes copy and duplicate operations that preserve FMEA-related data such as RPN, design controls, and actions while reusing model components [2]. EnCo SOX documentation separately describes building structured failure relationships across system levels [4].

A second test should cover import error handling for a legacy PFMEA spreadsheet with incomplete detection values. The medini wizard selects an input file and line range, but the supplied anchors do not specify what the importer does when required fields are empty [2]. Healthcare evaluators should also inspect the risk matrix behavior, since medini documentation describes matrices of at most 10x10 cells that tally FMEA entries according to severity and occurrence values [6]. That matrix summary is a documented output feature, not a substitute for documented risk acceptance criteria.

Import Paths Define What Legacy Data Can Become

medini analyze accepts Excel or CSV import. The import action requires that a detached FMEA worksheet be selected first; if no such model exists, it must be created [2]. The import wizard controls file selection and the range of lines to be imported [2]. The supplied Relyence documentation does not state an Excel or CSV import path, though it describes template selection and custom worksheet configuration [3]. Whether Relyence supports spreadsheet import is therefore unknown from the provided anchors, not established as absent.

A healthcare quality team migrating from spreadsheet-based PFMEAs should test whether column headers map to severity, occurrence, and detection fields without manual reassignment. The medini documentation describes import into a detached FMEA worksheet, which is not synchronized with any model [2]. It does not state that imported rows automatically receive failure cause and effect relationships or that a detached worksheet can later be attached to a design model. Healthcare evaluators should therefore ask the vendor directly about validation rules for missing fields, duplicate failure modes, and version-controlled reimport.

Risk Classification and Criticality Are Configured, Not Universal

medini analyze describes the FMEA component as configurable for severity, occurrence, and detection, as well as frequency and monitoring for VDA-AIAG settings [2]. The documentation states that ranges can be reduced to arbitrary subsets, with an example limiting occurrence values to [1,3,7,10] [2]. That means the same underlying analysis can produce different prioritization outputs depending on how a project administrator configures scales. Healthcare teams should not assume that RPN values from another site or supplier are directly comparable to their own.

Isograph documentation says the FMEA module highlights high-risk items via RPN or criticality analysis and supports standards including MIL-STD-1629A and AIAG & VDA [7]. Sphera advertises templates for ISO 13485 and FDA 21 CFR Part 820 among other standards [5]. The supplied anchors list these as supported framework labels, not as independently verified compliance outcomes. The high_impact flag is not triggered here because no source anchor establishes that any product's use causes regulatory acceptance or clinical safety improvement. The available evidence is limited to vendor statements about template and standard coverage.

A Hypothetical Comparison for a Dual FMEA Setting

Consider a healthcare manufacturer that already maintains a SysML model for a connected infusion pump and separately runs PFMEA workshops for its assembly line. In a medini analyze configuration, the design-focused DFMEA could attach to the pump model so failure modes defined on model elements flow into the worksheet and edits write through [6]. The PFMEA would more likely use a detached worksheet because the assembly line may not be represented in SysML [2]. This suggested split is an editorial hypothesis about a plausible workflow, not a tested implementation or a vendor recommendation.

Under Relyence, the same organization might create separate analyses for the design and the process, using an Analysis Tree to organize the process steps for PFMEA [3]. Relyence claims easier collaboration and data reuse compared with Excel [1], while Sphera claims its system eliminates time-consuming spreadsheets for some customers [5]. Neither anchor establishes which tool completes that dual scenario faster or with fewer errors. The unknown variables are how much SysML integration is actually needed, how many users edit concurrently, and whether existing quality system software already stores process maps.