In an industrial context, digital nameplates are accessed in the same way as information is accessed using digital product labels on consumer goods. However, in order to clarify how the access process works, a distinction must first be made as to who would like to access the corresponding product data – a human or a machine.
A: Access by a human
When a human accesses data, a mechanism is used that many of us are already familiar with from our private lives. Scanning a 2D data matrix code or QR code opens a manufacturer platform on a smartphone, tablet or PC, which displays the product data for the relevant product matching the serial numbers. The details of this mechanism are described in detail in DIN SPEC/91406 or IEC 61406.
The digital code on the printed type plate contains the link to a globally unique product ID (the asset). The content on the manufacturer platform is generally based on asset administration shells (abbreviated to AAS) and has been standardised across manufacturers, particularly in relation to the data structure. In addition to the content of the printed type plate, manufacturers can record all available information, data and documents for the product here. The use of sub-models in the asset administration shells ensures that the data is clearly structured and organised. The content can be read by humans as well as machines – and can also be transferred to other software systems. In this way, for example, a product can be incorporated into a local asset management system.
B: Access by a machine
If a machine initiates the call-up, this generally occurs via an API (application programming interface). Using this, machines can access individual features in a targeted manner or can retrieve the entire information content of an asset administration shell, if required. The situation is different if machines and products are directly connected to each other. In this case, smart assets (products with an interface, processor and their own memory) are used. This configuration does not necessarily require a connection to an external cloud. In the same way, in addition to the provision of asset administration shells on a server, the asset administration shells can be saved directly in the product. Via communication by Ethernet IP, MQTT or OPC UA, all participants can communicate the content of the asset administration shells directly to one another in the product network.
Further Reading:
These articles might also interest you
Ethernet-APL: Time for action!
Use case: Provision of all documents and certificates
![[Translate to Englisch:]](/fileadmin/_processed_/b/f/blog-explosionsschutz-rstahl-startseite-279x205_fd835544b0.jpg "[Translate to Englisch:]")
![[Translate to Englisch:]](/fileadmin/_processed_/3/9/blog-explosionsschutz-rstahl-ueber-den-blog-279x205_ba20676840.jpg "[Translate to Englisch:]")
![[Translate to Englisch:]](/fileadmin/_processed_/0/d/blog-explosionsschutz-rstahl-autoren-279x205_0fc02e6150.jpg "[Translate to Englisch:]")
![[Translate to Englisch:]](/fileadmin/_processed_/f/5/blog-explosionsschutz-rstahl-newsletter-expert-mail-279x205_1126e74698.jpg "[Translate to Englisch:]")
Write new comment