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
Results
—
—
—
—
Charts
- X: activates
- B: blocks
How it was calculated and standards
Effects, counterexamples and findings
| Effect | Type | Status | Does not activate | Activates when it should not |
|---|
| Effect | Active causes | Matrix | Logic |
|---|
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 samplen 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 effectEach 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,NOTandXOR, or in SpanishY,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
0and1give 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 as87L,21Z1or50BF_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,94or86. Close:CLOSE,CIERREorCERRAR. - Block:
BLK,BLOQorBLOCK. Alarm:ALMorALARM. Start:ARR,STARTorINI. - The equipment is the last part after
_:TRIP_QA1andCIERRE_QA1belong to the same breaker QA1.BLK_CIERRE_QA1is 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
Solar energy
PV system sizingPV production and energy costPV I-V curveAGPE classifier and connection proceduresCable voltage dropSolar plants and the grid codeP-Q capability testPPC control testsPlant model validationCND supervision indicatorsPMU tests and commissioningRenewable energy tax incentives (Colombia)
Protection
Function 50/51 overcurrentFunction 27/59 voltageFunction 81 frequencyFunction 67/67N directionalFunction 46 negative sequenceFunction 49 thermal overloadFunction 25 synchronism checkFunction 32 reverse powerFunction 51V voltage overcurrentFunction 64G stator groundFunction 27TN third harmonicFunction 64F rotor groundFunction 78 out-of-stepFunction 50/27 inadvertent energizationFunction 37 undercurrentFunction 38 bearingsFunction 48 incomplete sequenceFunction 66 starts per hourFunction 51LR locked rotorFunction 14 underspeedFunction 47 phase sequenceFunction 59N residual overvoltageFunction 60 fuse failureFunction 55 power factorFunction 46BC broken conductorFunction 68 power swing blockingFunction 87N restricted earth faultFunction 63 Buchholz and pressureFunction 26 oil temperatureFunction 71 oil levelFunction 87B bus differentialFunction 60C bank unbalanceFunction 51G neutral groundFunction 79 reclosingFunction 86 lockoutFunction 94 tripFunction 74 trip supervisionFunction 87L line differentialPhasor diagramRelay coordinationCurrent transformer: burden and saturationVector group compensation (87T)Frequency df/dt rampBreaker failure 50BF87 differential settingCT and VT selectorDistance setting 21MV feeder coordinationMotor protectionBoundary meteringGenerator protectionLoad shedding 81 and UVLSShunt reactorSynchronizing and closing 25/78Secondary arc and single-pole reclosing
Analysis and communications
COMTRADE records: viewer and generatorOscillography analysisIEC 61850 SCL viewerIEC 61850 SCL auditorIEC 61850 network: GOOSE/SV addresses and process busIEC 60870-5-104 APDU decoderIEC 61850 to IEC 60870-5-104 and 101 mappingICCP bilateral table checkerIP and VLAN planDNP3 and Modbus decoderTeleprotection channel timeOptical and radio link budgetTime synchronisationMMS control sequenceGOOSE simulatorIEC 61850 station networkInterlocking table and CILO equationsZones and conduits (IEC 62443-3-2)Zone firewall rule reviewerRoles and permissions (IEC 62351-8)IED X.509 certificate verifierDevice hardening baselineIncident response exercise (CNO 2188)Cybersecurity gap: CNO and IEC 62443
Equipment testing and diagnostics
Commissioning checklistCurrent transformer testsDisconnector and GIS switchgear testsGrounding system testsPower cable testsVoltage transformer testsInsulation diagnosis: dissolved gases (DGA) and temperature correctionTransformer TTR testTransformer winding resistanceTransformer insulation, PI and DARTransformer power factor and capacitanceTransformer excitation currentTransformer SFRATransformer leakage reactanceTap changer dynamic resistanceCalibration and uncertaintyPCB equipment: classification and deadlinesRETIE pre-inspectionTransformer test interpreterCircuit breaker testsTest budgetMaintenance plan and health indexSF6 inventory and leakage
Electrical studies
Lightning protectionShort circuit and per-unit systemGround fault and neutralShort-circuit checkerPower transformerTransformer noiseSafety clearancesArc flashGrounding resistancePower-frequency electric and magnetic fieldsCurrent split factor SfApproach boundariesSubstation configuration selectorBusbar stressesInsulation co-ordinationTRV and short-line faultGenerator circuit-breakerInductive load switchingSwitch-fuse combinationDisconnector and earthing switchMV switchgear and GIS specifierMV cable insulation levelInsulator strings: mechanical checkSeismic qualification of substation equipmentSurge protective device selectionElectric vehicle charging station
Yard equipment control
Circuit breaker controlDisconnector controlTransformer controlMV switchgear controlCapacitor bank controlAuxiliary services controlIEC 61850 bay controllerRecloser control
Industry and power quality
Motor startingHarmonic distortion THD and TDDEquipment harmonic emissionHarmonic emission allocationCapacitor bankBattery sizingRegulatory quality indicatorsCapacitor bank protectionSubstation DC systemsPower qualityGenerating sets to ISO 8528Lighting design to RETILAPControl valve Cv and Kv and affinity laws
