Components and systems in industry are becoming increasingly interlinked. This is hardly surprising when you consider the ideas and basic principles behind the industrial Internet of Things and would like to implement them. This trend will grow even more over the next few years, while the degree of networking is also set to increase. This presents many new challenges for users and service organisations. One of these relates to the firmware of the affected components, machines and systems.
What is firmware?
To put it in very basic terms, firmware is the operating software for the hardware used. In many cases, firmware is based on a specific Windows or Linux program and is only written by hardware manufacturers in very rare cases. This is beneficial for hardware manufacturers in that a very time-consuming and complex part of product development (software development) can be greatly simplified and sped up. However, using Windows- or Linux-based firmware also has its drawbacks. For instance, the program code may contain errors or security vulnerabilities that are also transferred.
What are firmware updates?
If a manufacturer discovers errors or security vulnerabilities, they can rectify these with a firmware update. In addition to correcting errors, firmware updates can also be used to introduce new functionalities or improvements to the hardware's operation or performance.
Regardless of the reason why a manufacturer developers a new or updated firmware version, there is the question of how to load this version on devices already being used in the field. With a very large number of devices, the user or trained service technicians can load a firmware update on installed devices.
Especially in the case of security vulnerabilities, there is the question of how is the hardware user notified that a new firmware version is available? There are currently two main ways of doing this:
- The manufacturer publishes the information on their website.
- The manufacturer uses information services like Cert@VDE to share this information in the market.
What kind of problems are there with the current solutions for users?
Existing mechanisms have so far not been satisfactory for users. If the information is published on manufacturers' websites, this means that users have to actively look for it. What's more, they have to check whether each update is relevant to the hardware installed in their factories, and what specific hardware programs are concerned. If a number of identical products are being used, there is no other option than to manually check all firmware versions on the devices and compare them with the new firmware update. In general, no company is able to go to this effort. This task is time-consuming and laborious, even when services like Cert@VDE are used. These services only do away with the need to search for updates on manufacturers' websites.
How can the digital nameplate and digital twins help?
The digital nameplate, in combination with asset administration shells, can offer a solution to these problems. Users or service organisations can use the digital nameplate to directly display all of the details about the product from the digital twin. This information also contains all of the details about the installed firmware. And that's not all – there is the option to register for updates relating to this serial number. After registering, serial numbers are used to let users or service organisations know when a new firmware update is available for this exact product. If the user also links the serial number with an installation site, they will have access to all the information they need for planning a possible update (for example during the next maintenance operation). This eliminates the need for tiresome manual searches.
Write new comment