Mr. Niermann, what is behind the plug-in concept?

Niermann: In purely practical terms, the plug-ins are self-sufficient mini-projects that contain specific visualization modules for the various real machine modules. These have to be created once and can also contain functions and information - from the user interface to process data, alarm messages, trend recordings and logic. Cross-variant functions are then also combined in a framework project. This gives machine builders a library from which they can draw when they want to create the visualization for a new machine. The required plug-ins then only need to be loaded into the framework and the customized visualization is ready.

Another challenge for many machine builders that we can solve with the Inosoft plug-in concept is good version management. Plug-ins and frameworks can be updated individually and centrally, so any improvements and maintenance measures are automatically available for all future projects.

Which showcase do you use to demonstrate the concept?

Niermann: Using the example of a printing press, we demonstrate schematically how the individual modules, such as paper unwinding, printing units, rewinding or drying, can be created and visualized. The printing units in particular can also be instantiated, as they are always the same in principle, but are supposed to work with different colors in several work steps.

What is the project creation functionality integrated in Visiwin all about?

Niermann: With this functionality, the Visiwin software can handle the project creation process in part or completely automatically - including all variables, links, descriptions and definitions that previously had to be drawn manually from the control concepts and integrated into the visualization. With the help of a small program that machine builders can develop themselves or commission from us, a PLC project, for example, can be scanned through and the elements of various functionalities identified using specific programming instructions.

Using an object-oriented programming interface, these elements are set up as an object with all relevant information, such as the PLC address, and saved in the configuration. The Visiwin software has open interfaces that can be used to implement and utilize precisely these objects extracted from the PLC project. The visualization can now access these functions, display them and make them operable. In this way, we offer the machine manufacturer the option of automatically assembling all the required modules dynamically from the configuration file to create an interface based on the machine configuration individually ordered by the end customer.

How does the graphical editor for the WebUI support automation engineers?

Niermann: With the help of the graphical editor, programming work is normally no longer necessary. It follows the simple but good "what you see is what you get" principle that we already use in our Modern UI. This means that there is a toolbox with various intuitive tools and elements. The automation engineer selects the appropriate modules, places them on the interface using drag and drop and links them to the right process variables without having to write a single line of code. This allows additional interfaces to be quickly created for mobile devices, for example, or adapted for specific users. For us, the graphical editor rounds off the WebUI engineering, especially for mobile but also IPC.