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; } } }

[FMEDA] Import failure model description from excel

medini_1062733402

Hello,

I'd like to import the failure description written down in an excel file into the medini FMEDA sheet.

What is necessary?

- Unique property for identifying the component

- Check if failure modes are equally in medini and excel

- Import the failure description according to component/ failure mode

As it is used in my project:

- Unique property in medini: Name

- I'd like to have a input mask to enter the used failure modes

* The names will be equal in medini and excel

- I'd like to have a input mask to enter which column contains the unique property (reference designator) which the failure modes and which the failure description

Excel structure is attached.

Optionally if this is working the selection of SPF and MPF can be added.

Best Regards

Benedikt

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Benedikt,

find attached a change version of your script. You will find (1) column to read the pinName, (2) some code to change the "failable" to the pin if a name is given (lines 37-44).

Note comment in lines 38 and 46: we search explicitly only in the next level of contained elements to avoid issues when for example the Component has an OPEN FM but the pin has an OPEn as well.

Happy Scripting

Jan

All comments

medini_1024169437

Hi Benedikt,

there are some scripts in this forum that import data from Excel,

I have provided libraries to write simple "callback" style importers.

However, importing an FEMDA is one of the more tricky things. Tricky part is that

the FEMDA is partially derived from a sysml model, so the importer has to import

structure and failure modes into sysml, other things as coverage into FMEDA sheet.

I have started to write an importer for SOX2 FMEDA Excel exports.

I could post it here to give you a start, would that help?

Jan

medini_1062733402

Hello Jan,

so the FMEDA is already derived from Hardware Architecture in medini.

And I want to add the failure comments into this already derived FMEDA.

Just to be clear.

Does your script work like that?

Best Regards

Benedikt

medini_1024169437

Ah, complete misunderstanding. the script I mentioned imports the complete FMEDA from scratch.

And now I remember what you were seeking for. Your case would be just a fraction of it.

Pseudo code would be

1. find target sysml model (selection or finder)

2. find derived FMEDA worksheet (selection or finder)

3. import excel, handle each row

3.1 for each row get part (via name?), find failure mode (via name)

3.2 read description from column K and write it to (the failure mode?) or find appropriate row in DC and write it there

Do you have anything of that already? What about 1. and 2.?

Jan

medini_1062733402

Yes, that's the way.

So for 1. and 2. selection would be fine.

Then import the excel and select the column which contains the unique identifier (via name),

Then select the column that contains the failure mode,

then select the column that contains the failure description.

The structure of the excel you see in the picture I have attached initially.

What I have already?

So the FMEDA is already derived and the failure description and SPF/ MPF slection is already done for some of the modules.

But for other modules I want to import the failure comments and if this is working maybe also the SPF and MPF selection.

Regards

medini_1026021779

Hello Jan,

Could you please share the script for the steps 1,2,3.x you described above?

Regards,

Tony

medini_1024169437

Hi Tony,

well, that script was never really done, just pseudo code, as mentioned above.

However, should be fairly straight to set the skeleton up. Maybe I can post an initial draft and you continue the scripting part and re-post it here?

Happy Scripting

Jan

medini_1026021779

Hello Jan,

Sure. please share the draft. I will try my best from there.

medini_1024169437

Hi Tony,

here is a simple skeleton that assumes an Excel with 3 columns as Benedikt has described, though it does not ask the user for the column indexes but has them hard coded in the script, you can improve if you like.

The script does also not ask for any selection, it simply searches the complete project for the component.

Script and sample Excel are included in the attached project. Please extend and re-post.

Note that this is a 20.1 project.

Happy Scripting

Jan

medini_1062733402

Hello Jan,

thank you for your Skeleton script.

I already tried it in one of my Projects and it works for me.

But some of the components have ports.

Is it necessary to use a further column in the Excel sheet with Port Name?

Could you add the Code to further look if a port is used (Port Name cell empty or filled)?

One Question:

How can I make this Failure description visible in the DC worksheet?

If you could help me in those 2 Points, I have everything I need.

Best Regards

Benedikt

medini_1024169437

Hi Benedikt,

the later should be straight: just create a new *derived* property at "DC Failure Entry":

Use JavaScript to avoid overhead:

And you will get:

For the first I am not sure. The script looks for any element, so ports should be included.

That would work if the port name is unique as the component name.

If its not unique, you need to introduce something else, maybe you name the cell "C::p" where C is the component name and p is the port name.

Then search for C and if ::p is present search a second time for p in C?

This way you do not need another column.

Jan

medini_1026021779

Hello Jan,

I have attached my customized script here. My objective is to create 'cause->effect' relation between two failure modes (both the failure modes are nested in a sysml), as per the input in excel sheet. for this i am using 'createFailureRelation' function and its not working for me. please help in this.

medini_1024169437

Hi Tony,

you have to use the factory.js library here. Simply do:

Factory.createRelation(cause, effect, Metamodel.safetyModel.FailureRelation);

// or in your case:

Factory.createRelation(fm, fmeffect, Metamodel.safetyModel.FailureRelation);

Happy Scripting

Jan

medini_1062733402

Hello Jan,

as discussed could you please add further code to the script for searching if the component owns ports?

The Excel Looks like showed in the Picture "Excel_Example".

And if a component has no ports, the cell for ports will be empty.

Best Regards

Benedikt

medini_1024169437

Hi Benedikt,

find attached a change version of your script. You will find (1) column to read the pinName, (2) some code to change the "failable" to the pin if a name is given (lines 37-44).

Note comment in lines 38 and 46: we search explicitly only in the next level of contained elements to avoid issues when for example the Component has an OPEN FM but the pin has an OPEn as well.

Happy Scripting

Jan

medini_1062733402

I adapted the script a Little bit, so that it dont Shows a message when component not available and if not available, continue with the next component.

So I have a script that fulfills what I Need.

Thank you for your great support!

Attached my last Version.

medini_1024169437

Good! Please mark as answered.

Jan

medini_1076359557

Hi,
When I use the function:

Factory.createRelation(fm, fmeffect, Metamodel.safetyModel.FailureRelation);

where the cause is the failure mode of a SysMLPart and the effect is the failure mode of a port.

I get the following error.

Do you know how to fix it?

Thanks in advance.

medini_1024169437

Hello Sandra, which version of the tool (Help -> About) and which version of the factory.js (look insid ethe file and there the history) are you using?

Seems you need an updated version. The latets version can be always found here: Scripting Libraries : Ansys medini analyze Support

Jan