Tiza Group

Home / Tools / Cause-and-effect matrix

Cause-and-effect matrix and logic checker

Enter the bay's cause-and-effect matrix and the logic left in the relay, one equation per effect: the tool compares them in every combination of causes, shows you the simplest counterexample of each difference, draws the gates and builds the test protocol.

Boolean algebratruth tablesIEC 60617-12gate symbols

Example cases
Cause-and-effect matrix and logic checker
ALearn

E1Cause-and-effect matrix

First row: Cause;Description;EFFECT1;EFFECT2… Cells X (activates), B (blocks) or empty. Separator ; , or tab: you can paste it from a spreadsheet.

E2Programmed logic

EFFECT = expression, with AND, OR, NOT, XOR and parentheses. Lines starting with # are comments.

E3Gate view

Click an input of the drawing to change its value.

Effects that differ from the matrix

—

Fault-level findings

—

Combinations checked

—

Protocol tests

—

Cause-and-effect matrix
  • X: activates
  • B: blocks
Each row is a cause and each column an effect. Above each column, ✓ if the logic does what the matrix asks in every combination checked and ≠ if not; a column that differs is framed.
Logic of the effect in gates
The equation of the chosen effect with IEC 60617-12 symbols. If the effect differs from the matrix, the drawing starts at its first counterexample. Click an input to change it: the output is compared above with what the matrix asks for.

Effects, counterexamples and findings

EffectTypeStatusDoes not activateActivates when it should not
EffectActive causesMatrixLogic

    Test protocol

    What it is for

    The cause-and-effect matrix says what the bay must do: which protections trip the breaker, which start breaker failure and reclosing, what blocks each command and which alarm is raised. The logic of the relay or bay controller is something else: what was actually programmed. Between the two, small mistakes with big consequences appear, such as a 50BF start without the test-mode block.

    This tool compares the two in every combination of causes, shows you for each difference the simplest combination that produces it, draws the equation with gates and builds the factory and site test protocol with the expected result of each effect.

    How it is calculated

    Boolean algebraTiza Group matrix convention

    What the matrix asks for

    Expected effect = (CX1 OR CX2 OR …) AND NOT (CB1 OR CB2 OR …)

    CX are the causes marked X in the effect's column and CB those marked B. The effect is active when any X cause is active and no B cause is. B as a block is a convention of this tool: if your project writes blocks another way, turn them into B before checking.

    Boolean algebratruth table

    Combinations checked

    n ≤ 16: 2n combinations · n > 16: each cause alone, each pair and a fixed sample

    n is the number of signals: the causes of the matrix plus the signals the logic uses and the matrix does not have, which are tested at 0 and at 1. In each combination the effect's equation is compared with what the matrix asks for. Differences are sorted by the number of active causes: the first one is the one you would test first in the bay.

    Test protocol

    one test per cause + one for each B cause with each X cause of the same effect

    Each test carries the expected value (1 or 0) of every effect according to the matrix, and the table marks where the written logic would give another value. The matrix is also checked on its own: causes with no effect, effects with no cause that activates them, and a cause that orders the same equipment to trip and close at the same time.

    How to write the logic

    • One line per effect, in the form EFFECT = expression (also :=). Empty lines and lines starting with # or // are ignored.
    • Operators: AND, OR, NOT and XOR, or in Spanish Y, O, NO. The symbols & and · or * for AND, | and + for OR, and ! and ~ for NOT also work. Precedence: NOT, then AND, then XOR, then OR; use parentheses when in doubt.
    • The constants 0 and 1 give an effect that is always inactive or always active.
    • An equation may use another effect, for example ALM_DISPARO = TRIP_QA1: it is replaced by its equation. A circular reference is an error.
    • Names use letters, digits, _ and ., with no spaces, such as 87L, 21Z1 or 50BF_EXT. The same names as in the matrix.

    Effect names

    To find a cause that orders the same equipment to trip and close at the same time, the tool reads the type and the equipment from the effect name. It is a convention of this tool:

    • Trip: starts with TRIP, DISP, 94 or 86. Close: CLOSE, CIERRE or CERRAR.
    • Block: BLK, BLOQ or BLOCK. Alarm: ALM or ALARM. Start: ARR, START or INI.
    • The equipment is the last part after _: TRIP_QA1 and CIERRE_QA1 belong to the same breaker QA1. BLK_CIERRE_QA1 is a block, not a close.

    Limits of the calculation

    • It is a Boolean check: it does not see timers, pulses, edges or seal-ins (latches) of the real logic. Logic with those elements is written here without them, and its behavior over time is tested separately.
    • It does not read signal quality or the manufacturer's files: you transcribe the logic as it was left in the relay.
    • With more than 16 signals the check is not complete: each cause alone, each pair and a fixed sample. A mistake that only shows with three or more causes at once may go unnoticed.
    • The reading X activates, B blocks and the naming convention belong to this tool. The example cases are illustrative, written by Tiza Group: they are not real projects.

    Frequently asked questions

    What is a cause-and-effect matrix in a substation?

    It is the table that says what the bay must do on each event: each row is a cause (a protection that operates, a position, a mode) and each column an effect (trip the breaker, start breaker failure, block reclosing, raise an alarm). It is the specification against which the logic of the relay or bay controller is programmed and tested.

    How is the cause-and-effect matrix tested in FAT and SAT?

    One cause is activated at a time and the effects that appear are recorded; then each blocking cause is activated together with each cause it blocks. This tool builds that list with the expected result of each effect and downloads it as CSV to be signed at the factory or on site.

    Why check every combination and not just each cause?

    Because some mistakes only show with two causes at once: a block missing from the 50BF start, or an alarm that copied the trip's block. With up to 16 signals the tool checks the complete truth table; with more, each cause alone, each pair and a fixed sample of combinations.

    Related guides

    Other tools

    All tools
    WhatsApp