TSN Hardware Ships Widely While Configuration Stays Vendor-Specific

Time-Sensitive Networking has reached the point where the hardware is no longer the obstacle. TSN-capable switches ship from Cisco, Belden, Moxa and Siemens among others, and OPC UA PubSub running over TSN has moved from conference demonstrations into production pilots. What has not kept pace is configuration.

As of early 2026, most deployments are configured through vendor-specific engineering tools: PROFINET over TSN through Siemens TIA Portal, EtherNet/IP over TSN through Rockwell Studio 5000. Each tool computes gate schedules, assigns streams and pushes configuration to bridges within its own ecosystem, and each does so competently. The difficulty appears when a network spans two ecosystems, because the schedule is a global property of the path and there is no widely adopted neutral way to hand one tool's stream reservations to another vendor's bridge.

The consequence is that TSN's promise of a converged network is easiest to realise inside a single vendor's estate, which is a familiar shape in industrial networking and slightly at odds with the standards-based framing. Centralised configuration models exist in the standards and are the intended answer, but adoption in shipping products remains partial.

For anyone scoping a project this year the practical guidance follows directly. A single-vendor cell is a reasonable first deployment and can be running within a normal project cycle. A mixed-vendor backbone is a longer engagement that should be scoped as an integration project, with the configuration path proven in a lab before any panel is opened.

The technology works. The tooling has not yet caught up to the interoperability the standards describe, and pretending otherwise is how a network schedule ends up owned by nobody.