July 2016: Application of BC sets for the success logic is sensitive to the order of failure branches with multiple failure alternatives. 
This known problem affects success treatment in certain cases with multiple branch alternatives and with BC sets. Following the standard treatment of compact master fault tree, BC-sets are applied one by one (and not merged into a new BC set). This means that the BC set inherited from the success branch by following function events is sensitive to the order of the failure branches. The BC set from a higher branch (as presented in the graphical representation) overrides assignments from lower branches (should they be in conflict). This functionality will be modified to use the concept “True beats False” as when RSAT merges several nested BC sets.
Moreover, the success logic might differ from the (negation of the) failure logic. This might happen if a BC set from one input alternative assigns states to events that occur in other inputs. The problem is due to aggregation of BC-sets in the same way as was for compact master fault tree before. This is an inconsistency since for the failure branches only the specified BC set is applied. 
From RSAT version 3.3.0 the program builds one accumulated BC set from all BC sets in the branch point alternatives. The rule for conflict resolution is that True beat False. This means that if an event is set to True by one BC set and to False by another one then the accumulated BC set will set this event to True. This BC set is inherited to following function events. Also, the success logic always expresses that none of the failure branches is satisfied. See Theory Manual of RSAT 3.3.0 and higher for details. 
Fixed in 3.3.0 
RiskSpectrum Analysis Tools (RSAT)