Selection option of transfer gate or MOE

Question

I am using a lot of identical but independent basic events, which has exactly same parameters (except name and E-ID). I would expect the transfer gate or MOE can provide a pop up option to choose if the user wants

a duplicated event (same E-ID), which is the existing feature, or an independent event (new E-ID but still keep the referencing relationship). No matter which option being chosen, any changes in the original basic event, it will apply to other referencing events (both duplicated and independent)

medini_1059007410 · Answer

Hi Bob,

I couldn't find any "reference" feature in Isograph RWB FT+, but they have "Failure models", which can be applied to multiple Events. For that we have an similar feature in medini. Thinking of that, I may have thought of a too complicated solution first, so let's try again:

If you need independent events with same failure rate information, you can benefit from the fact that events, which represent a certain failure mode (best created via drag&drop of the failure mode into the fault tree diagram), directly take the failure rate from the failure mode. If you then duplicate the event (as an independent event), the ID will be different, but the failure rate will be identical and will be updated for all these events if it is updated for the represented failure mode.

The only exception are the cycle kind information, e.g. a monitoring time for latency. That's individual per event (some use cases need the flexibility) and the different copies do not reference a common latency time (that's a planned feature for the future, via central variables being used for that time input).

That would cover your use case, right? (Anyway medini fault trees shouldn't be used with pure base events not representing SysML model elements - that'd be wasting many integration features...)

Regards,

Nils

medini_1072628395 · Answer

Hi Nils,

I think this feature will be very helpful as a native feature, I can see similar use cases in electrification using many identical but independent components (basic events). so that "one place change apply to all" can be achieved.

I remember Isograph can support that (called reference)?

Thanks!

medini_1059007410 · Answer

Hi Bob,

You are in the right forum category, as the use case seems to be a bit too special for a native implementation (at least to me), and solvable via scripting.

As you can execute scripts via context menu of an event (Execute > ...(script file name)...), you could:

* For the MOE use the built-in native functionality (via "Alt + Drag and Drop" in case of few elements to duplicate), or actually via an import script if many instances are required with an e.g. Excel list of names and event IDs), and
* For the independent copies a script, which* creates copies of the current event (look for "create events" in the scripting forum, e.g.  Programatically derving FTA models from the SysML models (Functional/Software/Hardware) : Ansys medini analyze Support (freshdesk.com) )
* gives them IDs with unused numbers (look for "autocounter", e.g. Complete empty function IDs, e.g. after an import : Ansys medini analyze Support (freshdesk.com) )
* creates a reference to the original event, stored in a reference profile property
* asks the user to use "restore subtree" at the parent gate to see all added events (could also be done via scripting, but manual step is so easy with an existing FT that it might not be worth doing the scripting: New utility function in ui.js to add elements to a diagram : Ansys medini analyze Support (freshdesk.com) )

The second approach would need a 2nd script, which updates the properties of the independent events after any changes to the linked event. That script could run over the whole project to do that all together, once manually executed.

Does that help you?

Happy Scripting,

Nils

PS: See here for updated libraries:  Scripting Libraries : Ansys medini analyze Support (freshdesk.com)