Cause and Effect Matrix.
A cause and effect matrix is a tabular document that lays out the safety-instrumented and interlock logic of a plant in a row-by-column format. Rows are causes, initiating conditions like high pressure, low level, gas detection, manual trip. Columns are effects, actions like close inlet valve, depressurize unit, stop pump, alarm. A cell at the intersection means that cause triggers that effect.
Three drawings included on a new account.
What Cause and Effect Matrix means.
A cause and effect matrix is how the interlock and shutdown logic of a plant is made legible to everyone who has to use it. Written as paragraphs of trip narrative or scattered across logic-block diagrams, that logic is almost impossible to review. Laid out as a grid with initiating conditions down the rows and protective actions across the columns, a single filled cell carries one complete statement, this cause produces this effect, and the same document answers three different questions at once. The operator reads across a row to see everything a given trip will do. The safety engineer reads down a column to see every condition that drives a given action. The auditor reads the whole grid against the safety requirement specification to confirm nothing is missing or contradictory. The matrix is built from the HAZOP and LOPA workshops, where each cell traces back to an initiating event and the protection layer credited against it, and time delays and bypass permissives are annotated in or beside the cell. It is normally issued as a controlled document alongside the IFC P&ID set and referenced from the drawing rather than drawn in full on it, and the logic in the safety controller is configured directly from it. The part the drawing does carry, the SIS-classified tags and their trip annotations, is what an I/O list pairs with the matrix so the safety scope can be reconciled end to end.
Why the matrix format works
Reading interlock logic as paragraphs of text or as scattered logic-block diagrams is hard for humans. The matrix is dense, scannable, and lets the operator, the safety engineer, and the auditor each find what they need. The operator finds. What does this trip do. The safety engineer finds. What causes this action. The auditor finds. Is the matrix consistent with the SRS. Most modern SIS projects deliver the cause-and-effect matrix as a separate document referenced from the P&ID, sometimes embedded in the PLC code as configuration.
How the matrix gets built
The matrix derives from the HAZOP and LOPA workshops where each safety hazard scenario is enumerated. Each cause is the LOPA initiating event. Each effect is the protective-action layer. The matrix consolidates the per-scenario logic into one register and the SIS configuration is built from it. Bypass and override logic is annotated alongside the trip cells. Time delays, initial alarm at Tplus 0, trip at Tplus 30 seconds are noted in the cell. Cause-and-effect matrix software, Tridel, exSILentia, GE Mark VIe Safety Builder, Honeywell Safety Builder generates SIS code directly from the matrix.
A worked cause and effect matrix extract
Illustrative rows and columns for a generic separator, using invented tag numbers. Causes read down the left, effects read across the top, and a mark in a cell says that cause drives that effect.
| Cause | Close inlet ESDV-1201 | Close outlet XV-1210 | Stop pump P-1201 | Open blowdown BDV-1205 | Annunciate in the control room |
|---|---|---|---|---|---|
| PAHH-1201, vessel pressure high high, 2oo3 | X | X | X | X | X |
| LAHH-1202, vessel level high high, 2oo3 | X | X | X | X | |
| LALL-1203, vessel level low low, 2oo3 | X | X | X | ||
| Confirmed gas detection in the module, 2oo3 | X | X | X | X | X |
| Confirmed fire detection in the module, 2oo2 | X | X | X | X | X |
| Manual shutdown pushbutton, module | X | X | X | X | X |
| Loss of instrument air, low low header pressure | X | X | X | X |
How to read the conventions on a cause and effect matrix
Conventions vary by project and are defined in the matrix legend. These are the ones in common use.
| Convention | What it means |
|---|---|
| A cross or a filled cell | This cause initiates this effect |
| A number in the cell | The effect is initiated as part of a sequence, in the numbered order |
| A letter code in the cell | The effect is delayed or conditional; the legend and the notes column give the rule |
| An empty cell | No relationship, and that is a decision rather than an omission |
| A shaded row or column band | A grouping, for example one shutdown level or one vendor package |
| A row grouped under a heading | Causes belonging to one initiating system, for example fire and gas |
| The notes column | Time delays, voting, bypass permissions, reset requirements and any manual step |
| A reset column or row | Whether the effect resets automatically or needs a deliberate operator reset |
Common questions
Is the cause-and-effect matrix the same as the SRS.
Can the cause-and-effect matrix be extracted from a P&ID.
Who reviews the cause-and-effect matrix before it is issued for construction.
Turn a C and E matrix into a sheet you can query.
Every cause-to-effect pair off the printed matrix, as rows, exported to Excel or CSV.