Schematex
faulttree·NUREG-0492 / MOCUS (Fussell-Vesely 1972)·engineering, manufacturing·complexity 2/3·since v0.6.5

Repeated event with cut-set absorption

A shared basic event feeds two gates — the case naive fault-tree tools get wrong. MOCUS applies absorption so the supersets collapse, leaving two single points of failure that a shape stencil would miss.

For the safety analyst who needs the math right

Open in Playground →
faulttree·§
↘ preview
100%
Product not removed Fault tree for "Failure to remove product": 1 top, 3 intermediate, 4 basic. 2 minimal cut sets: {CDM}, {MSF}. Single points of failure: CDM, MSF. P(top) = 0.0044 (rare). Product not removed Failure to removeproduct Arm jams or collides MSF Manipulator system … p=0.0035 Loss of positionfeedback ESF Encoder sensor fail… p=0.0021 RCF Resolver cable fault p=0.0012 Wrong slot commanded CDM Controller command … p=9.00e-4 MSF Manipulator system … p=0.0035 P(top) = 0.0044 (rare)
UTF-8 · LF · 10 lines · 477 chars✓ parsed·5.7 ms·8.0 KB SVG

What this shows

MSF feeds both G1 and G2 — a repeated event, the DAG case that separates a real engine from a shape stencil. It is drawn once per reference with the shared-event mark, but the cut-set engine treats every instance as the same Boolean variable.

Absorption is the point. MOCUS first expands the tree to {MSF, ESF}, {MSF, RCF}, {MSF}, {CDM}. Because {MSF} is itself a cut set (via G2), the larger sets {MSF, ESF} and {MSF, RCF} are absorbed — a superset of a cut set is not minimal. The two minimal cut sets are {MSF} and {CDM}, both order-1 single points of failure (boxed in the strongest red). A naive expander that forgets absorption would wrongly report four. P(top) ≈ P(MSF) + P(CDM) = 0.0044.

Fault tree syntax