/ Engineering · Interoperability
The engineering
at the seams.
Where two systems meet, the integration is engineered, not assumed. Each matrix documents the fit, the caveats, the failure scenarios and the maintenance implications of an integration we do repeatedly.
- Published matrices
- 9
- Topic tags
- 24
- Average pairings per matrix
- 2.1
- Last batch reviewed
- 2026-05-17
Interoperability · lighting
KNX + DALI
KNX provides the building-wide control bus; DALI provides per-luminaire addressing and dimming. The two are paired with a KNX/DALI gateway per DALI segment.
3 pairings · Reviewed 2026-05-17
Interoperability · bms
BACnet + Modbus
BACnet is the modern BMS protocol; Modbus is what the plant already speaks. The two coexist via a BACnet-Modbus router per plant cluster.
3 pairings · Reviewed 2026-05-17
Interoperability · cctv
CCTV + PoE switching + storage
IP cameras need PoE switches sized for both power and bandwidth, and storage sized for retention × bitrate × camera-count.
2 pairings · Reviewed 2026-05-17
Interoperability · av
AV-over-IP + network design
AV-over-IP places real-time video traffic on the building's IP layer. Network design must accommodate latency, jitter and multicast.
2 pairings · Reviewed 2026-05-17
Interoperability · wifi
Wi-Fi density engineering
Premium Wi-Fi is sized for concurrent client density, not square-metre coverage. AP placement, channel plan and PoE budget are interlocked.
3 pairings · Reviewed 2026-05-17
Interoperability · ups
UPS + BESS + DG
UPS bridges short outages; BESS bridges medium ones with quiet headroom; DG handles long outages with switchover discipline.
3 pairings · Reviewed 2026-05-17
Interoperability · fire
Fire alarm + PA voice evacuation
Fire-alarm panels trigger zoned PA voice messages via a cause-and-effect matrix; both are governed by NBC 2016 + IS 2189/14735.
3 pairings · Reviewed 2026-05-17
Interoperability · access
Access control + CCTV + VMS
Card reads trigger camera tags in the VMS; the operator sees the face that swiped the badge.
0 pairings · Reviewed 2026-05-17
Interoperability · acoustics
Acoustics + architecture
RT60 is set by surface area, absorption coefficients and room volume — not by adding more speakers later.
0 pairings · Reviewed 2026-05-17
Key engineering takeaways
- Interoperability is engineered at the seam, not assumed at the catalogue. Two vendors' published compatibility is the starting point for an engineering exercise, not the conclusion.
- Every multi-vendor integration carries a documented interface specification — protocol, telegram format, fallback behaviour, supervision strategy — that survives a vendor's product roadmap change.
- Failure-domain isolation is a first-class design output, not an after-thought. A fault on one vendor's bus must not have the authority to crash another vendor's controller; the protocol bridge is the failure boundary.
- Vendor product lifecycles do not synchronise. The interoperability matrix is dated against each vendor's published release and is re-validated at each major release, not assumed to hold for the duration of the deployment.
- Multi-vendor commissioning takes longer than single-vendor commissioning by a margin that compounds against the number of seams — not the number of devices. Every additional vendor in the stack adds a seam, not just a device.
When this architecture fails
Failure modes worth knowing in advance
Multi-vendor seams fail in patterns the matrix can predict if the integration is engineered, not assumed. Each scenario below is preventable at the design stage and expensive to fix once the seam is live.
A vendor firmware release silently changes telegram format on a shared bus.
The published interoperability matrix is suddenly wrong; the integration is intermittently silent until the affected vendor's release is rolled back or the bridge spec is rewritten — a multi-day outage on what was previously a stable seam.
BACnet/IP shared between BMS and lighting controller without VLAN isolation.
A lighting-controller broadcast storm overwhelms the BMS supervisor's UDP queue; the supervisor stops accepting trend data; the operator sees stale data with no alert until the daily reconciliation runs.
Modbus master timeout shared across multiple sub-systems.
A single slow slave on one sub-system drives a Modbus master timeout across all sub-systems on the same bus; the operator console reports a wide-area fault that traces back to a single slave's response delay.
Two vendors' alarm priorities collide in a shared destination queue.
A low-priority alarm from one vendor floods the operator's queue and the high-priority alarm from another vendor sits below it — the operator works the queue front-to-back and the critical event waits behind the routine event.
· Where to go next
The interoperability authority graph.
Engineering discipline
· The engineering pack covers each seam