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

Adding attribute to derived FMEA Profile (Failure derived)

medini_1039539557

I am trying to add an attribute in the FMEA worksheet, that will show the "SM preventing Single point faults" and "SM preventing the failure mode from being latent" for every failure mode.

How can I do that? Tried to do that by adding a new profile under "Failure (dereived)"

self.element.oclAsType(safetyModel::Failure).getProfilePropertyValue('single') \

self.element.oclAsType(safetyModel::Failure).getProfilePropertyValue('latent')

but of course it is not the right way to do that..failed to find the right name for that properties...

can you please advice?

Thanks in advance,

Alon

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Alon,

I am not fully sure what you want to achieve in the end, but it seems that many things you did were absolutely correct. So you took the right type and

self.element.oclAsType(safetyModel::Failure)

is already navigating from FMEA to the failure mode. After that it gets a bit "blurry".

getProfilePropertyValue('latent')

accesses a property that you have defined for "Failure Mode" yourself, not sure you have that, do you?

If it is a default property, just access it using ".property". If you are not sure about which property you can access, maybe check this article: https://medini.freshdesk.com/support/discussions/topics/1000087956

Maybe you can explain a bit more what you want to achieve so I can support you better.

Happy Scripting

Jan

medini_1039539557

Thank you for that article, I believe that it was really helpful if I could find it two months ago :P

But still, I am unable to add this "spfSafetyMachinisms" attribute to derived FMEA.

This is what I did :

Profiling -> FMEA Worksheets -> Failure(derived FMEA only) -> add new derived "SM prevents FM from violating safety goal" -> OCL "self.element.oclAsType(safetyModel::Failure).getProfilePropertyValue('spfSafetyMechanisms[]')"

but "Can not evaluate script"

and by the way - is there any scripting manual / webinar that I can find?

medini_1039539557

Just to clarify what I'm trying to reach here: Add the FM SafetyMechanisms as a column in the FMEA

Thanks!

medini_1024169437

Alon, there is a scripting guide inside of the tool.

I think I got the point now, stay tuned, I may post some help before.

Happy Scripting

Jan

medini_1024169437

Alon, I think just the variable access is wrong, its not a profile property. Please try:

self.element.oclAsType(safetyModel::FailureMode).spfSafetyMechanisms

Note that I had to type it FailureMode, not just Failure. You may try:

self.element.oclAsType(safetyModel::FailureMode).mpfSafetyMechanisms

or even

self.element.oclAsType(safetyModel::FailureMode).allSafetyMechanisms

Happy Scripting

Jan

medini_1039539557

Thanks a lot

I will start working with that scripting guide... hope to be smarter with the scripting

Best regards, Alon

medini_1036016653

The hint regarding ".getProfilePropertyValue('propertyName')" helped me to display a custom property of my hardware parts in the diagnostic coverage worksheet (FMEDA):

self.element.oclAsType(sysml::SysMLPart).getProfilePropertyValue('assembly')

The crucial step was to derive the linked hardware part, which is done by "oclAsType(sysml:SysMLPart)".

Thanks again!

Peter

medini_1024169437

Nice! Thanks Peter for posting this.

Just to mention that this is required for OCL but its not required if you use Java Script:

-- OCL
self.element.oclAsType(sysml::SysMLPart).getProfilePropertyValue('assembly')

// same in Java Script
self.element.assembly

Way shorter if you ask me :-)

Happy Scripting

Jan

medini_1036016653

Now that is good to know! I'm new to the meta model and scripting in medini, though haven't come across a document stating the differences/(dis)advantages between scripting with OCL vs. JavaScript. Possibly you have a link for me?

Thank you!

Peter

medini_1024169437

Hi Peter,

there is no such comparison document, only a few comparison articles in certain situations and articles about dedicated scenarios where OCL makes sense like this one and this one. There is also the series "A Journey into Java Script" with a few articles "praising JS" :-)

Generally I think that OCL is nice and neat when it comes to (1) traversal, (2) handling large sets of data and (3) expressing queries. Its rather bad when it comes to (1) computation, (2) if/then/else cases and other more imperative scripts as well as (and especially as) profile access.

Maybe we start another article that compares OCL and JS? Or a "Journey into OCL?

What do you think?

Jan