Aug 2015: Handling of missing event trees in ET linking with Inherit BC Sets 
Using consequences as initiating events, i.e. linking event trees, you must make sure to include all event trees in the chain of events trees leading to the a consequence used as input to an initiating event. If you, by mistake, do not include one of the parent event trees, RSAT will issue an error message if you use the setting “Compact Master Fault Tree” in the Analysis Settings, but not for the settings “Inherit BC Sets” and “No inherit BC Sets” Consider a model with linked event trees connected by consequences used as inputs to initiating events. CONS is defined as a consequence in sequences of event tree ET-PARENT and is used as an initiating event in event tree ET-CHILD. A consequence analysis case for analyzing consequences in ET-CHILD includes event tree ET-CHILD but not ET-PARENT. The chain of sequences going through the event tree ET-CHILD will, in this case, start with a consequence for which there is no sequences leading to, in the event trees included in the analysis. Moreover, there has to be at least one complete sequence included in the analysis case, i.e., a sequence which ultimately leads to an initiating event with either a basic event or a gate as input. In the scenario outlined above RSAT will issue an error message if you use the setting “Compact Master Fault Tree” (SeqBCMethod=1 in the INI file) in the Analysis Settings, but not for the settings “Inherit BC Sets” and “No inherit BC Sets” (SeqBCMethod=2 or 3).Besides this, RSAT crashes if there is a consequence used as an initiating event in an event tree and this consequence is never used in a sequence of another event tree. 
To test that all sequences connect correctly in a consequence analysis case, you can set the value for "Inherit BC Sets through event trees" to Compact Master Fault Tree (SeqBCMethod=1 in the INI file), run the analysis, and if RSAT starts generating minimal cutsets then the whole analysis case is built up correctly. Otherwise, there is an error message. 
 
Fixed in 3.3.0 
2883 
High 
RiskSpectrum Analysis Tools (RSAT) 
3.2.5