Cause & Effect / Logic
PROGRAMMING KNOWLEDGE
Cause & Effect / Logic
A practical guide to fire-alarm logic, staged operation, coincidence, delays, inhibits, network scope and commissioning proof.
Before changing a live system: agree the test/disablement with the responsible person, identify any ARC/fire-routing connection and plant interfaces, decide what must remain operational, record every temporary change, and restore/verify everything before leaving.
OR
Any cause
Any selected input can drive the effect. Typical example: any detector or MCP in a fire zone starts local warning.
AND
Confirmed / double knock
Two independent conditions must be true before the effect operates. Use only where the design/fire strategy requires confirmed operation.
DELAY
Timed action
An effect operates after an investigation or staged-alarm delay. Confirm how MCPs, evacuation and manual controls override the delay.
INHIBIT
Conditional suppression
A keyswitch, time clock, test mode or other condition prevents an effect. Make the inhibited state visible and easy to restore.
CAUSE & EFFECT WORKFLOW
Commission logic from the fire strategy, not from memory
- Define causes: device, zone, group, sprinkler, suppression, BMS or other input.
- Define effects: sounders/VADs, routing, doors, lifts, fans, dampers, smoke control, suppression interfaces and shutdowns.
- Define logic: OR, AND, coincidence, delays, time clocks, dependencies, overrides and reset behaviour.
- Define scope: local panel, sector, network node, building area or system-wide.
- Test every path: prove the expected effect and also prove that unwanted effects do not occur.
- Document: retain an approved cause-and-effect matrix and note software/configuration revision.
MANUFACTURER TERMINOLOGY
Common names for similar concepts
| Manufacturer | Common terminology | Engineer note |
|---|---|---|
| Advanced | Standard mapping, flexible logic, time clocks, sectors, disablement groups | PC configuration tools provide detailed network-wide cause/effect. |
| Kentec | Cause & effect, actions, test mode, Loop Explorer | Logical operators can combine zones/inputs to drive outputs. |
| C-TEC | Input Groups, Output Groups, Action Sequences | ZTOOLS is central to ZFP configuration. |
| Gent | Sectors, groups, command builds | Site-specific Gent configuration terminology is important. |
| Notifier | Control matrix / logic / virtual points depending family | Pearl, ID3000 and INSPIRE differ; follow family documentation. |
| Protec | Output groups, panel logic | Some output groups may be logic/keyswitch controlled rather than manually available. |
| Eaton xDetect | Matrix cause & effect, groups, type IDs | xDetectWorks is the configuration environment for trained engineers. |
| Nittan | Cause & effect matrix / groups | Evolution 1 supports on-panel or PC-tool configuration. |
Return to service:Exit test modeClear temporary disablementsRestore sounders / outputsRestore fire routing / ARCRestore delays / time controlsProve a normal event pathCheck panel = normalRecord work