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

script to import excel FMEA

medini_1057179964

Dear all

I want to create a script to import existing FMEA (not only an excel import) but with an interface with components/functions, feared event, preventive action, detection action..

In the library (finder.js and factory.js) I don’t find control to create a component in a FMEA

We have this script to create failure entry in factory

// helper

function __createFailureEntry(scope) {

if (!scope) {

console.error("Scope is undefined in create method!");

}

var entry = FMEAFactory.eINSTANCE.create(Metamodel.FMEA.FailureEntry);

// XXX changing containment is not supported in 3.1.0 API

var feature = Metamodel.FMEA.ComponentEntry.failureModes;

MediniModelModificationUtil.addValueOfFeature(scope, feature, entry);

return entry;

}

If i use in script like this

var created = Factory.createElement(scope, Metamodel.FMEA.FailureEntry);

it don’t run

We don’t have this command in this list in factory.js

// FMEA

if (type == Metamodel.FMEA.TakenAction) {

return __createTakenAction(scope);

}

if (type == Metamodel.FMEA.RecommendedAction) {

return __createRecommendedAction(scope);

}

if (type == Metamodel.FMEA.CurrentDesignControl) {

return __createCurrentDesignControl(scope);

}

if (type == Metamodel.FMEA.FMEAWorksheet) {

return __createFMEAWorksheet(scope);

}

And it return me this message

// not supported

throw"type is not supported";

same even if I add this in the previous list

if (type == Metamodel.FMEA.FailureEntry) {

return __createFailureEntry(scope);

}

Do you have an idea ?

Thank you in advance

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023909254

Hi Philippe,

there are a few steps which have to be done for this:

All measures are managed and created in one or multiple measure collections (e.g. one collection for all detection measures and one for all prevention measures). You need to create these collections with
coll = Factory.createElement(scope, Metamodel.safetyModel.MeasureCatalog)
In these collections you now can create your measures using
findOrCreateMeasure(coll, measure_name) and then set further properties of the measure
Now you come to the slightly more tricky part - the connection between the failure causes and the measures. Following the concepts of VDA and AIAG-VDA medini uses the concept of a measure group. One or multiple measure groups can be related to a failure cause (e.g. reflecting the state at different gates in the development process). Each measure group again references one or multiple detection& prevention measures. Therefor you first have to create the measureGroup for the failure cause using mg =Factory.createElement(failure_cause, Metamodel.safetyModel.MeasureGroup) and afterwards add the references to the detection/prevention measures (from the measure collection) to the appropriate lists mg.detetctionMeasures resp mg.preventionMeasures

I hope this helps a little

Eckhardt

All comments

medini_1023909254

Hello Phillipe,

do you plan to have a detached FMEA (i.e. without an underlying architecture model) - or an attached FMEA (which is based/synchronized with an architecture model)?

In fact for the latter one you would add all the components/functions (including hierachical structure and even failure modes and cause-effect relations) during the import from Excel to an architecture model (SysML model) and have the FMEA worksheet just synchronized with it. In the worksheet you would just add the additional things like actions and measures.

Eckhardt

medini_1057179964

Dear ALL

I have solved this issue with the creation of a folder with empty model and a derived FMEA in my Template

Best regards

medini_1057179964

Dear All

I continue to do my script to import FMEA. I am capable to import and create my elements, ports, functions, malfunctions, feared events, measures and safety mechanisms

Now i want to map these informations in my FMEA. I use the control ".add" hereafter but it doesn't work to add Feared events or causes

Do you have an idea ?

if (FE) {

FMEA.components[sg1].failureModes[ii].failureEffects.add(FE);

}

if (mf1){

FMEA.components[sg1].failureModes[ii].failureCauses.add(mf1);

}

Thanks in advance

Best regards

medini_1057179964

Hello Eckhardt

Sorry for my late answer but i don't see your answer

And thank you for this

Yes my idea is to have an attached FMEA. I have found the same solution than you. But you can see in my other message, now i have other issues.

Best regards

Philippe

medini_1023909254

Hello Philippe,

concerning the failure modes/malfunctions and the cause-effect relations you sould do it as follows:

For failures which belong to a component/function you would create them at the architecture model using findOrCreateMalfunction(function, malfunction-name) resp findOrCreateFailureMode(component, failuremode-name) (these two functions are defined in the library finderEx.js)
For failures which have no owners (that would be the top-level effects like hazards and the root-causes) you would first need to create collections where you store them. Afterward you can also use the findOrCreateMalfunction/findOrCreateFailureMode to create the entries in the collections.
The cause-effect relations can afterwards be created again at the architecture model using Factory.createRelation(source-failure, target_failure, Metamodel.safetyModel.CausalityRelation) - this will automatically make it appear in the FMEA sheet.
You may also inbetween force a synch of the worksheet with the architecture using synchronizeWorksheet(worksheet) from factoryEx.js ( this may be needed if the worksheet is open while you are executing the FMEA import script.

I hope this helps you to proceed with your scripting work.

Best regards,

Eckhardt

medini_1057179964

Hello Eckhardt

thanks, you help me a lot of

Best regards

Philippe

medini_1023909254

Hi Philippe,

thank you - could you complete the imports script - or are there still any open points where you need support?

Best regards,

Eckhardt

medini_1057179964

Hello Eckhardt

Now it is ok for the relation between FM and Effects, and causes with FM. However I continue to have issue to create my script.

I need to create the relation between measure and prevention action or detection action. But I don't find the control to do. I am in contact with Abdoul Niazi to search this one .

Best regards

Philippe

medini_1023909254

Hi Philippe,

there are a few steps which have to be done for this:

All measures are managed and created in one or multiple measure collections (e.g. one collection for all detection measures and one for all prevention measures). You need to create these collections with
coll = Factory.createElement(scope, Metamodel.safetyModel.MeasureCatalog)
In these collections you now can create your measures using
findOrCreateMeasure(coll, measure_name) and then set further properties of the measure
Now you come to the slightly more tricky part - the connection between the failure causes and the measures. Following the concepts of VDA and AIAG-VDA medini uses the concept of a measure group. One or multiple measure groups can be related to a failure cause (e.g. reflecting the state at different gates in the development process). Each measure group again references one or multiple detection& prevention measures. Therefor you first have to create the measureGroup for the failure cause using mg =Factory.createElement(failure_cause, Metamodel.safetyModel.MeasureGroup) and afterwards add the references to the detection/prevention measures (from the measure collection) to the appropriate lists mg.detetctionMeasures resp mg.preventionMeasures

I hope this helps a little

Eckhardt

medini_1057179964

Hello Eckhardt

Thank you

It works and i have found how to precise it is a MSR measure

mg =Factory.createElement(mf1, Metamodel.safetyModel.MeasureGroup);

mg.kind= Metamodel.safetyModel.MeasureGroupKind.FMEAMSR;

mg.preventionMeasures.add(f5);

To put the occurrence value it is necessary to do like this

if (occurrence ==10){

mg.occurrence= new java.lang.Integer(10);

}

if (occurrence ==9){

mg.occurrence= new java.lang.Integer(9);

}

if (occurrence ==8){

mg.occurrence= new java.lang.Integer(8);

}

if (occurrence ==7){

mg.occurrence= new java.lang.Integer(7);

}

if (occurrence ==6){

mg.occurrence= new java.lang.Integer(6);

}

if (occurrence ==5){

mg.occurrence= new java.lang.Integer(5);

}

if (occurrence ==4){

mg.occurrence= new java.lang.Integer(4);

}

if (occurrence ==3){

mg.occurrence= new java.lang.Integer(3);

}

if (occurrence ==2){

mg.occurrence= new java.lang.Integer(2);

}

if (occurrence ==1){

mg.occurrence= new java.lang.Integer(1);

}

same for frequency, detection and monitoring

Now my need is to create a recommended Actions

Best regards

Philippe

medini_1023909254

Hi Philippe,

great work - the FMEA table looks already very good. I just have one remark - the measuregroup kind should probably be set as follows:

mg.kind= Metamodel.safetyModel.MeasureGroupKind.DFMEA;

except you really want to create the Supplementary MSR-FMEA as defined in the AIAG-VDA Handbook and not a DFMEA.

The addition of the recommended and taken actions should now be rather straight-forward:

Use the factory function createElement(ra_scope,Metamodel.FMEA.RecommendedAction) where ra_scope is the measure group for the recommended action and afterwards add to the recommended action the taken action again using the factory function createElement(ta_scope, Metamodel.FMEA.TakenAction) where ta_scope is the recommended action to which it is associated. ( I may need to try it out but this way it should work).

For the recommended/taken action just fill in the additional data which are all just plain text (and if you have further profile-properties also fill in those).

Best regards,

Eckhardt

PS: You may try mg.occurrence= new java.lang.Integer(""+ occurence); ... or a litlle more tricky mg.occurrence= new java.lang.Integer(""+ occurence); ... It would avoid the long list of if-statements ... and you may need just check for values above 10 and below 1