Mr. Jamal, what are the main objectives of the testbed that has now been initiated?
Jamal: The primary goal is to evaluate the new Ethernet standard TSN live in the production environment and to test the practical suitability of TSN. We are very pleased that National Instruments has been assigned the task of host for the physical project setup. Especially as this is the world's first testbed to put TSN through its paces in an industrial environment.

Which aspects are in focus?
Roughly speaking, there are five main topics. Firstly, we are investigating the combination of different communication protocols and their execution on a single, resilient network based on IEEE 802.1 TSN standards. Secondly, we want to provide proof of real-time capability and cross-vendor interoperability with a convergent Ethernet standard. Thirdly, we will evaluate the security aspect of TSN and provide feedback on the security capability of the first TSN functions. Fourth, we will demonstrate the integration capability of high performance applications and those where latency is critical. And fifthly, we want to explore the possibility of integrating a smart edge cloud into IIoT infrastructures and applications.

It is noticeable that the participants in the testbed - NI, Bosch Rexroth, Cisco, Intel, Kuka, Schneider Electric and TTTech - do not include a traditional specialist in fieldbus technology. By mistake or on purpose?
I don't think this is a deliberate strategy. It is more likely due to the fact that the companies involved have a strong interest in TSN and are understandably not burdened by the development of their own fieldbus. In the testbed, the focus is on cooperation with regard to an overarching standard. Individual interests of the respective companies, such as the enforcement of a specific fieldbus variant, should not be the focus.

TSN has not yet been adopted as a standard. So what can already be tested and what timeframe have you set for the implementation of the testbed?
The IEEE's work on TSN has reached a relatively solid foundation. We can therefore already start with the investigations. The idea is that this testbed will first and foremost be permanently set up physically at NI headquarters in Austin, Texas. The first phase will focus on integrating three to four automation, control and regulation applications that require real-time network capability within a single network infrastructure. We anticipate an implementation time of six to nine months. The resulting findings will also serve to fertilize further IIC testbeds. It is also conceivable that the testbed could be extended to new areas such as data management and data analysis.

You say that different communication protocols will be combined. What will these be?
We are starting with OPC UA. However, the overarching goal is actually to combine different communication protocols, depending on the automation, control and regulation applications to be used.

Which production applications are you targeting with the testbed?
First of all, there are two main areas. Firstly, the conveying and sorting of packaged goods elements. Here we are looking at the integration of several motor control systems and image processing elements for the identification, tracking and sorting of packaged goods; flexible process lines with several integrated regulation and control systems as well as peer-to-peer communication and merging with IT systems for accessing data for subsequent system analysis.

Secondly, we look at flexible production. In other words: mixed reconfigurable production applications including robotics, multi-axis motor control, image processing, inputs and outputs, as well as diagnostic and machine status applications. We also want to take a closer look at integration at M2M and IIoT level.

The testbed is now being created on behalf of the IIC. Will it also have an impact on the activities of the German Industry 4.0 platform?
On March 2, 2016, both initiatives announced a close collaboration. In my opinion, our work will certainly also be reflected in the platform.