Codesys Group
Device management in the cloud
The Codesys Group is presenting the upcoming 'Codesys Automation Server' for the first time at SPS IPC Drives 2018. We spoke about this with Dieter Hess, one of the two managing directors.
Mr. Hess, what exactly is behind the 'Codesys Automation Server'?
Dieter Hess: The Codesys Automation Server is the Codesys Group's Industry 4.0 platform, which enables server-based device management, collaborative engineering and process data acquisition - either in the cloud or as an installation on your own servers. The associated interfaces are seamlessly integrated into the Codesys development and runtime system.
Here at the trade fair, you are launching it - with which features exactly and what does the future roadmap look like?
Dieter Hess:Device management is the first function that we are providing and that can be seen here at the trade fair. The Automation Server manages a list of all active controllers of an operator, the so-called digital twins. Based on this list, it supports functions such as mass commissioning and updates. It is also possible to parameterize or replace controllers using just a smartphone or tablet. The development environment is not required for this. In 2019, we will add further functions such as user and certificate management centrally for all connected controllers. We will then focus on collaborative engineering - i.e. functions such as central source code management, test automation and continuous integration. Last but not least, we will also cover the area of process data recording.
Many OEMs or control system manufacturers that use Codesys are now building their own cloud-based service platforms. Where do you think you can offer added value here?
Dieter Hess : As a device-independent provider, we can already offer machine manufacturers and, above all, operators a cross-system software platform. The Automation Server further expands this added value. Visitors will be able to see this for themselves at the trade fair: Many devices from different manufacturers on our stand can be conveniently managed in the server via a browser. And in 2019, we want to integrate all compatible devices at the trade fair wherever possible.
Machine builders or operators usually also use control systems from different manufacturers? How do you take this into account?
Dieter Hess: The Automation Server is designed to be able to communicate with Codesys V2.3 controllers - i.e. existing products from the latest generation - and even with third-party products. This is implemented in the edge gateway, which connects several controllers with the Automation Server. The range of functions with third-party devices will at least include the application update and parameterization of the controller.
Do you want to or will you be able to develop all conceivable functions yourself in future?
Dieter Hess: Our solution is designed for expansion with customer-specific modules and third-party modules. We have been pursuing this business policy for some time now with the Codesys Automation Platform and our Codesys Store. Similarly, there will be a third-party provider program that enables companies to offer expansion modules for the Automation Server.
Up to now, customers have paid for the Codesys Runtime according to the per-unit license model. What exactly does the payment model for the Automation Server look like?
Dieter Hess: We are planning a fee per controller and per month as well as a basic fee per customer and month. We are still looking at a few use cases and specific customer experiences before we set the final price.










