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 custom columns with cell division to the FMEA table

medini_1064611722

Hello,

Working with FMEA tables and using profiling, it is possible to
add a new column to the table. I have a column that takes requirements. I like that
for each requirement that I put in this column, the rest of the table gets
divided and has one row per requirement. So, if I have ten requirements in my
first cell, I want to have ten rows for all the columns after. Is there a way
to do that?

Thank you,

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1059007410

Hi Ali,

Additional levels (row divisions in your wording) cannot be introduced by a requirements property - but you can create a requirements reference property on an e.g. failure level and then have multiple failures per Component. See the different categories in the different profiling types. The structure is also explained in the metamodel documentation, which shows the hierarchy/structure: 7.1. Generic FME(D)A structure (ansys.com)

As you haven't mentioned any typical FMEA levels (component/failure/effect/cause) - what's actually your use case, what do you want to achieve in the end (lines in an FMEA sheet is already on solution level, but what's your overall goal)?

Happy Scripting,

Nils

medini_1064611722

Thank you, for your reply! I have division based on failure modes. I like to add secondary division based on requirements and their associated mechanism. Can this be done through scripting?

Thank you

medini_1059007410

As described, below failure modes there can be multiple Causes, which can have multiple Measures assigned, So if you want to have requirements reference property at the same level as Measures, then you can do this by adding the property to the "Current Design Control" section in Profiling.

But be aware that you will have to add both Causes as well as Measures to see the requirements column editable.

medini_1064611722

Thank you! I was able to adjust the table using
failure causes.

I have another question. I want to have a separate column for
functions. I want this column to look at the component in the component/function
column and populate the function based on the function associated with the
"type" of the component. If component type has more than
one function, I like that it populates all of those functions. I have been
doing this manually. Is there a way to automate this?

medini_1059007410

Of course, that's possible with a derived property for the "Component/Function" category. For this kind of task I would recommend OCL (probably you'll only need a single line with OCL).

You'll reach the type with this:

this.element.oclAsType(sysml::SysMLPart).theType.oclAsType(sysml::SysMLBlock)...

The rest (...) is dependent on how you define "associated with the type" - how is the function linked to the type? If you know that, you can check the metamodel (and maybe other forum entries) and finish the OCL statement.

medini_1064611722

Thank you! the function is added under the type part:

When I run Medini in debug mode here is the information about the function object:

The element is contained in an EMF resource. The element is of type 'SysMLActivity' defined in

package 'sysml' (copy). The element is contained via the 'the_owned_elements' feature.

medini_1059007410

Hi,

Then you should be able to use this:
self.element.oclAsType(sysml::SysMLPart).theType.oclAsType(sysml::SysMLBlock).the_owned_elements->select(e | e.oclIsTypeOf(sysml::SysMLActivity)).oclAsType(sysml::SysMLActivity)

Happy Scripting,

Nils

medini_1064611722

Thank you! It worked.