Discussions
Categories
Groups
Documentation
Knowledge base
Developer portal
App catalog
The Hub
GitHub
Home
Newly Imported
User Forums
How it Works
FTA Models best practice
medini_1050701002
Hello everyone, With the team we argued about what was the best practice when doing FTAs. Our situation is the following: - We have several system level fault trees - Each leaf in the system fault trees is detailed in a subsystem fault tree - We also have copies of the system fault trees in which each leaf is replaced with a transfer gate to the corresponding subsytem fault tree top event. Until now we had one Medini "FTA model" per tree (that would equate, in our projet, to 100+ FTA models in the system medini project). Is this considered a valid approach our should we have, for example, one FTA model for the system containing all the system FT and one FTA model for each subsystem? It doesn't seem to matter in terms of functionality (we're able to do everything we want this way) but could it change something performance-wise? Adrien Gérard
Find more posts tagged with
medini
medini legacy
Accepted answers
All comments
medini_1023909254
Hi Gerard, there are pro's and cons between both approaches: In case you have one FTA-Model containing multiple fault trees (and diagrams) you can make efficient use of MOE's derived from architecture elements/failure modes. The Outline view would always give you a quick view on all the MOEs and also on how often they occur in your FTA model (which may be indicators for common causes). If you would use instead individual FTA models for all the trees, than you would get a lot of transfer gates modeling explictly the multiple occurring events. In that case you would have to investigate manually, how many transfer gates would point to the same target. (Note: The detection of MOEs and the information on how many times they do occurr is always scoped by an FTA model) On the other side, if you want to share sub-trees between many different higher level trees, it would usually be better to have that tree as a separate model in order to avoid copying sub-trees between different models (which especially in case of changes always has the risk of inconsistencies). For the calculation of course it does not make any difference whether you directly use MOEs or model them with transfer gates. Best regards, Eckhardt
medini_1050701002
Thank you for your answer. I have another related question regarding your last sentence "For the calculation of course it does not make any difference whether you directly use MOEs or model them with transfer gates.". Is there a way to make it that two transfer gates pointing at the same place are considered two separate independant events? We have, for example, two instances of a subsystem in our project - do we have to have two instances of their trees or is there a way to make it work with only one? Adrien Gérard
medini_1023909254
Hello, you mean e.g. having two redundant subsystems? In that case you have to have to separate sub-trees (i.e. make a copy of the tree for each subsystem). It is not possible to somehow "instantiate" a tree multiple times using transfer gates as it would involve a lot of uncertainties - e.g. what should happen if there are in the subsystem fault trees again transfer gates to other (sub)-systems etc. Best regards, Eckhardt
medini_1040753747
When I import XML from Reliability Workbench (RWb), formerly known as FaultTree+... There is a huge list of tables and columns to choose from when exporting to XML from RWb. Based on what medini analyze is looking for when importing, what is the best practice (or minimum) selection needed when I export from RWb to XML?
medini_1040753747
I ended up setting up my export template to include all the tables and columns. It imports with no issues into medini analyze with all the events and gates included. Is there a way to display the quantitative values as Probability/Mission time?
medini_1023909254
Hi Johan, you can modify the display of the of the quantitative labels of the events in the project settings - the available options are shown below: Best regards, Eckhardt
medini_1040753747
Is there a way to hide the probability (P) value in the FTA Diagram?
medini_1023909254
Hi Johan, there is a switch in the diagram toolbar to enable/disable the display ofth probability data: Eckhardt
medini_1053447504
Hi All, I have a FTA in RWB which doesn't include any FailureModels. When exporting to XML from RWb, I am choosing the following three tables and all columns corresponding to each of these 3 tables. However on importing this XML file into Medini, I get the following error: Has anyone of you faced such an issue? Let me know if you have some guidance on how to resolve this. Thank you so much. Kind Regards, Avni
medini_1024169437
Avni, which version of medini are you using? Do you have any error in your error log? Jan
medini_1059007410
Avni, Have you tried to still include the FailureModels table in the export, even if you don't actually use it in RWB (e.g. for qualitative fault trees)? I know that the medini FT+ XML importer does look for the failure models even for events with no model attached in RWB (as it logs a warning), so it depends on that table and leaving it out of the XML may cause issues. The recommended settings for the export are included in the Technical Documentation for Fault Tree Plus (Help > Online Support Page... > Technical Documents (under FAQ)). The FT+ importer did further improve in version 2021 R2, but your import should also work in previous versions. Regards, Nils
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of