System Integration

Two products standing in the same building does not mean either knows the other's state. The lift controller, the fire panel, the KNX line and the VMS each speak their own language. One is polled over RS-485, another publishes events over ONVIF or MQTT, a third opens nothing but its own interface. The gateway between them translates those languages and sets the direction and frequency of the traffic.

The mapping table is the real deliverable of this work. Every value in a device's point list is bound to the object above it by name, by unit and by scale. A temperature carrying no decimal place is converted here, a meter rolling over is caught here, and the text an alarm code corresponds to is written here. Where a naming scheme is not set at the outset, the same space appears in three lists under three names, and every report produced afterwards carries that difference.

When the gateway breaks

The real engineering becomes visible when the connection drops. A polled line holds its last value when no answer comes. Unless the time of that reading reaches the screen, a state that no longer exists still looks current, and the operator decides by looking at it. Reading back that the device really changed after a write, a retry rule, preserved command order and a shared clock source keep sources running at different speeds inside one sequence of events. The polling cycle and event reporting are sized separately, so a slow field line does not hold up the layer above.

Because a manufacturer's software update can break the mapping silently, version tracking extends into the operating period. The life-safety chain stays outside this discussion: the fire panel's decision is not taken over, and the layer above only watches and records.