nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatic Trace generation between Safety Requirements and Malfunctions

medini_1080812477

Hello,

I'm very new the Medini scripting and I want to automatically create the traces between the requirements listed in the "Safety Requirements" column and my Malfunctions (MF) in the "Potential Failure Effects" as shown in the image

Are there ways to configure an existing column or have a script to automatically create a formal Trace between a Malfunction and a Requirement without changing our existing FMEA structure?

My safety requirements are imported from PTC Windchill.
Medini: 2025 R2

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1079543555

Hi Srikanth,

The attached script should do what you have described above. There are some development assumptions based on your problem statement:

Only failure effects that are Malfunctions will be considered
There is no direct relationship between the failure cause and effect on a row-by-row basis - so essentially it will check and map on a 1:1 basis as the cause/effects appear visually (using their position in the set). If there is a mismatch in number between cause/effect then the extras don't get any traces.
The column for the safety reqs is assumed as "user_safety_requirements" - if this is different, needs to be updated in script.

Best,

Abilash

All comments

medini_1063548292

Hi,

It is not clear where do you configure the Safety Requirements profile attribute column. is it FMEA Failure, Failure Effect or Failure Cause?

What I got is that the entry point for requirements is the FMEA (but not clear whether Failure,Effect,Cause?)

The automatic tracing is possible but a bit too complex and over-complicated, I would consider to do entry of requirements a bit opposite instead.

1) for Effect setup Traces.Optionally you can specify a specific keyword as kind to make distinction on the Trace purpose. (e.g. "fmea")
To configure traces just use the Traces dialog (from Properties View) or Trace Matrix whatever method suits you the most

2) create a derived profile property at the same level as you now have your "Safety Requirements" column.

code snippets for derived profile property (OCL) may look like (FMEA Failure or FMEA Cause):

--Example snippet derived profile property at FMEA Failure (OCL), any trace of all effects to Req. with 'fmea' kind
self.element.effects
>selectByKind(safetyModel::CauseEffect).mediniGetTracedElements(safetygoals::SafetyRequirement,'fmea')

-Example snippet derived profile property at FMEA Effect (OCL),any trace of effect to Req. with 'fmea' kind
self.element->selectByKind(safetyModel::CauseEffect).mediniGetTracedElements(safetygoals::SafetyRequirement,'fmea')

The FMEA worksheet could look like

Regards,
Marian

medini_1080812477

Hi Marian,

In my project Safety Requirements profile attribute column is configured in Failure cause.

I agree it is more easy to have your proposed solution implemented and have the Safety requirement column populate the requirements already traced to Malfunctions. I was trying to find is there a simpler option to use existing requirements in the safety requirement column and created traces to avoid manual configure of traces.

Thanks for code snippets, it helps.

Best,
Srikanth

medini_1079543555

Hi Srikanth,

The attached script should do what you have described above. There are some development assumptions based on your problem statement:

Only failure effects that are Malfunctions will be considered
There is no direct relationship between the failure cause and effect on a row-by-row basis - so essentially it will check and map on a 1:1 basis as the cause/effects appear visually (using their position in the set). If there is a mismatch in number between cause/effect then the extras don't get any traces.
The column for the safety reqs is assumed as "user_safety_requirements" - if this is different, needs to be updated in script.

Best,

Abilash

medini_1080812477

Thanks Abilash for looking into this.