
Who this is for
If you need to be certain your fire system will perform, and prove it to an authority, start with the cause-and-effect matrix.
You probably need this if…
- A fire-safety audit or authority inspection is coming up.
- Your current panel is conventional and can't pinpoint which device triggered.
- There's no documented cause-and-effect matrix for your building.
- You're expanding the building and need new zones designed in, not bolted on.
- Insurance requires a tested, code-compliant system.
- Fire needs to trigger BMS or access-control actions during evacuation and currently doesn't.
Where it applies
Probably not the right fit when…
- A small single tenancy already covered by the landlord's base-building fire system.
- Routine annual servicing of an existing, already-compliant panel.
Technical overview
Fire systems have one job and no tolerance for false confidence. We design addressable detection and notification to code, interface it with BMS and security, and hand over a documented cause-and-effect matrix, not just a working panel.
Technologies we work with
Reference architecture
Design principles
- Design detection, alarm zoning, audibility, visibility and evacuation functions against applicable codes and the approved fire strategy.
- Use approved compatible devices and control equipment within their permitted circuit and loading limits.
- Document cause-and-effect logic for fire doors, lifts, HVAC, access control and other interfaced systems, with the fire strategy taking precedence.
- Commission every device, fault condition, notification circuit, standby supply and approved interface with witnessed acceptance tests.
Specification baseline
| Aspect | Specification | Why it matters |
|---|---|---|
| Code basis | Apply NBC India Part 4, current applicable IS standards and local fire-service requirements | The authority having jurisdiction and building use determine applicable obligations. |
| Detection selection | Choose detector type and placement from hazard, ceiling geometry, airflow and environmental conditions | Incorrect placement or detector type can delay detection or increase nuisance alarms. |
| Alarm zoning | Align addressable device locations and alarm zones with the approved evacuation strategy | Clear zone identification supports rapid incident response. |
| Standby power | Calculate battery capacity against required standby and alarm durations, circuit loads and applicable standard | Battery capacity must support prescribed operation under design conditions. |
| Integration | Use approved supervised or isolated interfaces with documented normal, alarm and fault states | Interfaces must not compromise the primary life-safety function. |
| Acceptance | Test detection, notification, fault reporting, standby power and every approved cause-and-effect action | End-to-end testing verifies the system rather than only individual components. |
Key design decisions
Detection architecture
Device-level identification, flexible zoning and larger or more complex building layouts are required.
A smaller, simpler installation is permitted by the applicable code and approved design.
System integration
Safety-critical status or control requires a specifically approved, monitored connection.
An approved interface provides supplementary status or reporting without replacing required life-safety control paths.
Sizing & calculations
Loop loading must satisfy approved device limits, current demand, wiring constraints, cable limits and fault-isolation requirements.
If an approved loop design permits 100 compatible devices and the planned count is 80, device-count utilisation is 80%; electrical loading and topology still require validation.
Battery capacity must account for standby load, alarm load, required durations, battery characteristics and design allowances.
A hypothetical 2 A standby load for 24 hours consumes 48 Ah before alarm-period demand, derating and reserve are added.
Notification quantity and placement must come from the approved audibility, visibility and coverage design.
A hypothetical 1 A notification circuit with sounders drawing 25 mA each supports at most 40 devices, before cable voltage drop and design margin are applied.
Standards, protocols & references
Handover documentation
- Approved fire alarm design and zoning drawings
- Device address and loop schedule
- Cause-and-effect matrix
- Battery and circuit calculations
- Commissioning and witnessed acceptance report
- Operation, maintenance and emergency response documentation

What you get
- A system built to a documented cause-and-effect matrix, not assumptions
- Documentation ready for authority sign-off
- Fire, BMS and access control that respond together, not separately
What we deliver
Detection & notification
- Addressable fire alarm systems
- Smoke, heat, aspirating and gas detection
- Visual and audible notification
Compliance & documentation
- Cause-and-effect matrix
- Documentation prepared for authority sign-off
- Zoning and as-built drawings
Integration
- Interface with BMS and access control
- Public address and evacuation coordination
- Gas suppression interlocks where required


