/ Engineering · Decisioning
The engineering choice,
explained in plain language.
Each journey walks through the conditions, the recommendation and the engineering reasoning — best suited for, avoid when, operationally safer, future-ready.
- Decision journeys
- 6
- Decision steps
- 14
- Journey kinds
- 5
- Updated
- 2026-05-17
/ technology selection
KNX or Rako for the residential lighting bus?
Choosing the residential lighting bus is the first lock-in decision of a smart home. KNX gives breadth and a deep ecosystem; Rako gives integration polish and a faster handover.
Both KNX and Rako can run the lighting bus of a premium residence. KNX is the open standard with the broadest ecosystem and the most flexible long-term posture. Rako is a tighter, more polished experience with a faster commissioning curve. The correct choice is not the better technology; it is the better fit for the operating reality of the household.
Step 1
If The residence has more than ~80 lighting circuits and integrates with a building-wide automation logic (curtains, BMS, HVAC).
Then Specify KNX as the lighting bus.
KNX's open standard and supervisory tree scale better when the lighting load is sharing the same bus as curtains, HVAC, BMS and energy management.
Step 2
If The residence has fewer than ~60 lighting circuits and the priority is a polished cinematic scene experience with mobile-first control.
Then Specify Rako as the lighting bus.
Rako's tighter ecosystem and built-in scene polish reduce commissioning time and produce a clean handover when lighting is the dominant subsystem.
Step 3
If The residence is mid-scale (60–80 circuits) and integration with non-Rako subsystems is required (BMS, fire, supervisory views).
Then Specify KNX with a Rako overlay for scene polish.
A KNX backbone with a Rako wireless overlay gives the open-bus posture for integration and the scene polish for the cinematic experience.
- Best suited for
- Premium residences · Villas · Owner-operated estates
- Avoid when
- Apartments under 6 circuits per zone — single-room DALI is cleaner
- Maintenance-friendly
- Both are AMC-friendly; KNX requires a documented bus map, Rako requires a documented zone map.
- Future-ready
- KNX leaves more headroom for future BMS or supervisory integration; Rako leaves more headroom for OTA-style upgrade cadence.
/ technology selection
BACnet/IP or Modbus/TCP for the BMS supervisory layer?
BACnet/IP is the de-facto BMS supervisory standard; Modbus/TCP is the legacy plant tail. Choosing between them rarely needs to be a single-protocol decision.
BACnet/IP is what every modern BMS supervisory layer speaks; Modbus/TCP is what every legacy plant device speaks. The decision is not 'which protocol' but 'which protocol at which layer'. The default we deploy is BACnet/IP at the supervisory layer with a documented Modbus/TCP tail at the plant.
Step 1
If The building has a new-build BMS scope with chillers, AHUs and plant directly specifiable.
Then Specify BACnet/IP end-to-end where the manufacturer offers it natively.
Native BACnet/IP removes the gateway layer and simplifies cause-and-effect across the BMS tree.
Step 2
If The building has an existing Modbus/TCP plant that the BMS must integrate with.
Then Specify BACnet/IP supervisory with a Modbus/TCP tail via a documented gateway.
The gateway is a documented seam — the gateway map becomes a versioned artefact in the AMC pack.
- Best suited for
- Corporate fit-outs · Healthcare campuses · Hospitality properties
- Avoid when
- Single-tenant warehouses where the plant is too small to justify a supervisory layer
- Maintenance-friendly
- Gateway map is the highest-value AMC artefact; ensure it is versioned and signed.
- Future-ready
- BACnet/SC adoption is a software upgrade away once the BMS supports it.
/ engineering tradeoff
Single-vendor or multi-vendor for the residential AV / cinema stack?
A single-vendor stack ships fast and demos beautifully; a multi-vendor stack survives the second product-line refresh. The correct choice depends on the household's appetite for handover discipline.
A single-vendor residential AV stack ships fast, demos beautifully and integrates cleanly because the manufacturer has done the integration work. A multi-vendor stack — Trinnov processor, JBL Synthesis amplification, Sonos / Symetrix multi-room — is more flexible and survives the second product-line refresh, but requires a tighter commissioning discipline. The trade-off is between speed-to-handover and 10-year resilience.
Step 1
If The household plans to live in the residence beyond 7–10 years and the AV stack is a permanent investment.
Then Specify a multi-vendor stack with explicit interoperability documented at the processor.
The processor (Trinnov, Storm, JBL Synthesis SDP) becomes the long-term anchor. Amplification and sources can refresh around it.
Step 2
If The household prioritises a polished demo-day experience and is comfortable refreshing the whole stack at year 5.
Then Specify a single-vendor reference stack (e.g. JBL Synthesis end-to-end).
The single-vendor stack ships faster and demos cleaner; refresh cost is absorbed at year 5.
- Best suited for
- Premium residences · Villas with dedicated cinema rooms
- Avoid when
- Apartments under 800 sq ft — a soundbar is the right answer
- Maintenance-friendly
- Single-vendor stack has the simpler AMC; multi-vendor stack has the cleaner long-term documentation.
- Future-ready
- Multi-vendor stack is more future-ready by construction; single-vendor stack requires a refresh discipline.
/ deployment selection
Addressable or conventional fire alarm system?
Addressable is the modern default; conventional survives only on very small loads. Most retrofits should be planned as migrations to addressable.
Addressable fire alarm systems report at the device level and support explicit cause-and-effect logic across panels. Conventional systems report at the zone level. Modern Indian codes (IS 2189) increasingly assume addressable detection for anything beyond a single-storey low-occupancy building. The decision is rarely between the two; it is between addressable now and addressable later.
Step 1
If The building has a planned occupancy beyond a single-storey, low-density use.
Then Specify an addressable, peer-to-peer fire alarm panel.
IS 2189 cause-and-effect logic and AHJ review are far cleaner against an addressable system.
Step 2
If The building already has a conventional system and a major refurbishment is on the horizon.
Then Plan the migration to addressable as part of the refurbishment.
Migration bundled with a refurbishment shares the commissioning window and the AHJ walk-through.
- Best suited for
- Corporate fit-outs · Hospitality properties · Healthcare campuses · Education campuses
- Avoid when
- Very small single-zone buildings where the AHJ accepts a conventional panel
- Maintenance-friendly
- Per-device serviceability extends visits but reduces frequency.
- Future-ready
- Addressable panels integrate cleanly into BMS supervisory views.
/ deployment selection
Online UPS or LFP BESS for mission-critical ride-through?
An online UPS is the fast-cycle ride-through; an LFP BESS is the energy-envelope ride-through. Mission-critical buildings now run both, tiered.
An online UPS gives seconds-to-minutes of ride-through for the IT load — clean, fast, well-understood. An LFP BESS gives minutes-to-hours of ride-through against the energy envelope. The mission-critical posture is no longer 'UPS only' — it is 'UPS at the rack tier, BESS at the building tier'. The decision is about tiering, not selecting.
Step 1
If The building has a small (≤ 50 kVA) IT-only critical load.
Then Specify an online UPS, no BESS.
An online UPS covers the entire mission-critical window at this load size.
Step 2
If The building has a 100–500 kVA mixed critical load with multi-hour ride-through expectations.
Then Specify a tier: online UPS at the rack, LFP BESS at the building.
BESS handles the energy envelope; UPS handles the clean ride-through.
Step 3
If The building has an aged single-source diesel genset and an EOL lead-acid UPS.
Then Migrate to LFP BESS + downsized genset.
The migration resets the lifecycle and reduces total cost across the next decade.
- Best suited for
- Corporate offices with on-prem compute · Healthcare campuses · Industrial estates
- Avoid when
- Small residential loads — domestic battery storage is a different product class
- Maintenance-friendly
- LFP BESS reduces lead-acid replacement cycles; tier-1 UPS still needs battery monitoring.
- Future-ready
- BESS is grid-services-ready; solar coupling is software-defined.
/ engineering tradeoff
AV-over-IP or hardware matrix switcher?
AV-over-IP scales further and integrates cleaner with networking; hardware matrices give better latency on a fixed footprint. The decision is rarely binary.
AV-over-IP runs the AV signal through a Layer-2 switch fabric — it scales further, integrates with the building network and supports remote management. A hardware matrix switcher gives deterministic latency on a fixed input × output footprint. Most premium installations now run AV-over-IP for the breadth and a small hardware matrix for the cinema room.
Step 1
If The installation has more than ~8 sources and more than ~8 displays in a building-wide configuration.
Then Specify AV-over-IP (SDVoE or proprietary equivalent).
AV-over-IP scales further and integrates with the same Cat6A backbone the building already runs.
Step 2
If The installation is a dedicated cinema or boardroom with tight latency expectations and a fixed source count.
Then Specify a hardware matrix switcher (HDBaseT or HDMI 2.1).
Hardware matrix has deterministic latency for a cinema-grade experience.
- Best suited for
- Corporate fit-outs · Hospitality properties · Auditoriums
- Avoid when
- Single-display residential setups — direct HDMI is the right answer
- Maintenance-friendly
- AV-over-IP requires PoE++ budget management; matrix requires firmware cadence.
- Future-ready
- AV-over-IP is the more future-ready posture by construction.
· Decisioning · The choice, in the open