{"id":7187,"date":"2020-12-15T09:36:39","date_gmt":"2020-12-15T07:36:39","guid":{"rendered":"https:\/\/www.iese.fraunhofer.de\/blog\/?p=7187"},"modified":"2024-01-08T09:20:15","modified_gmt":"2024-01-08T08:20:15","slug":"industrie-4-0-it-infrastructure-for-digital-twins-part2","status":"publish","type":"post","link":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/","title":{"rendered":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins"},"content":{"rendered":"<p class=\"lead\">In our <a href=\"https:\/\/www.iese.fraunhofer.de\/blog\/industry-4-0-it-infrastructure-for-digital-twins\/\">previous blog post<\/a>, we outlined a solution architecture to show what an Industrie 4.0 IT infrastructure for Digital Twins can look like. However, an architecture on its own is not sufficient for realizing <a href=\"https:\/\/www.iese.fraunhofer.de\/en\/customers_industries\/digitalisierung-produktion\/industrie40.html\">Industrie 4.0<\/a>. To bring the architecture to life and reap its benefits, an implementation of the concepts is needed. In the following, we will present our implementation using the open-source middleware Eclipse BaSyx and elaborate the IT infrastructure for Digital Twins based on a demonstration scenario using code examples.<\/p>\n<p><a href=\"https:\/\/www.iese.fraunhofer.de\/blog\/industry-4-0-it-infrastructure-for-digital-twins\/\" target=\"_blank\" rel=\"noopener noreferrer\">Previously<\/a>, we elaborated requirements on an Industrie 4.0 IT infrastructure for Digital Twins. Additionally, we showcased the Asset Administration Shell (AAS) as a specific implementation of the Digital Twin. Based on these requirements and the concept of the AAS, we identified the following key elements of such an infrastructure:<\/p>\n<ul>\n<li><strong>AAS Registry:<\/strong> Keeps track of the AAS in the system, can be browsed based on certain criteria, and provides the endpoint information for AAS access.<\/li>\n<li><strong>AAS Server<\/strong>: Provides the AAS and allows dynamic upload of AAS. Can be located in the cloud.<\/li>\n<li><strong>Edge Node<\/strong>: Provided by the device. Hosts highly dynamic data, e.g., sensor values.<\/li>\n<\/ul>\n<figure id=\"attachment_7188\" aria-describedby=\"caption-attachment-7188\" style=\"width: 698px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-7188\" src=\"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure-698x552.png\" alt=\"Fraunhofer IESE - Architecture Overview of the IT infrastructure for Digital Twins\" width=\"698\" height=\"552\" srcset=\"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure-698x552.png 698w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure-400x316.png 400w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure-768x608.png 768w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure-1320x1044.png 1320w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/Digital-Twin-Infrastructure.png 1360w\" sizes=\"auto, (max-width: 698px) 100vw, 698px\" \/><figcaption id=\"caption-attachment-7188\" class=\"wp-caption-text\">Figure 1 &#8211; The IT infrastructure for Digital Twins, composed of AAS Registry, AAS Server, and Edge Node<\/figcaption><\/figure>\n<p>Yet, identifying key components is not enough to enable easy instantiation of the Digital Twin infrastructure. These concepts need to be implemented and instantiated. However, companies may either lack the IT know-how and IT experts to implement these components, or they might not want to invest the effort for developing their own solutions. This is where open-source software comes into play.<\/p>\n<p>Today, companies are resorting more and more to open-source software [1]. As already described ten years ago, open source can be a key driver of innovation [2].<\/p>\n<p>In <a href=\"https:\/\/blog.iese.fraunhofer.de\/open-source-software\/\" target=\"_blank\" rel=\"noopener noreferrer\">another blog post<\/a>, researchers of Fraunhofer IESE have already detailed various benefits of open-source software. These include:<\/p>\n<ul>\n<li>Free access to existing source code &amp; easy tailoring<\/li>\n<li>A community supporting the solution<\/li>\n<li>No dependency on commercial suppliers<\/li>\n<li>No development efforts of one&#8217;s own needed to create the solution<\/li>\n<li>Broad support with open-source tools<\/li>\n<\/ul>\n<p>In the following, we will showcase a demonstration scenario using <a href=\"https:\/\/www.eclipse.org\/basyx\/\" target=\"_blank\" rel=\"noopener noreferrer\">Eclipse BaSyx<\/a>, which is an open-source Industrie 4.0 middleware developed by Fraunhofer IESE and its partners.<\/p>\n<p>First, we will present an overview of BaSyx and related open-source tools. Then we will detail the off-the-shelf components provided by BaSyx that allow easy instantiation of a Digital Twin system. Using BaSyx and its off-the-shelf components, we will present a demonstration scenario where we set up the AAS infrastructure and provide code examples. Finally, we will provide next steps as to how interested parties can dive deeper into the world of BaSyx and develop their own solutions and components.<\/p>\n<h2><strong>Enabling Industrie 4.0 with open source and Eclipse BaSyx<\/strong><\/h2>\n<p>Fraunhofer IESE is leading the <a href=\"http:\/\/www.basys40.de\/\" target=\"_blank\" rel=\"noopener noreferrer\">BaSys 4.2 project,<\/a> which is sponsored by the German Federal Ministry of Education and Research (BMBF) and focuses on enabling interoperability based on the concept of the Asset Administration Shell. While the results of the project are being <a href=\"http:\/\/www.basys40.de\/publikationen\/\" target=\"_blank\" rel=\"noopener noreferrer\">published<\/a> at appropriate scientific venues, they are also implemented as open source in <a href=\"https:\/\/www.eclipse.org\/basyx\/\" target=\"_blank\" rel=\"noopener noreferrer\">Eclipse BaSyx<\/a>.<\/p>\n<p>BaSyx is published on the platform of the Eclipse Foundation and utilizes the Eclipse Public License 2.0, which enables its usage in commercial applications and products.<\/p>\n<p>The middleware provides SDKs in Java, C++, and C#, enabling developers to implement Industrie 4.0 solutions in the programming language they are most comfortable with. In the context of this blog post, we will focus on the Java SDK, which is driven by Fraunhofer IESE.<\/p>\n<p>SDKs provide the means to work with Asset Administration Shells, their submodels, and the AAS infrastructure in accordance with the <a href=\"https:\/\/www.plattform-i40.de\/PI40\/Redaktion\/EN\/Downloads\/Publikation\/Details_of_the_Asset_Administration_Shell_Part1_V2.html\" target=\"_blank\" rel=\"noopener noreferrer\">Details of the Asset Administration Shell 2.0.1<\/a> document.<\/p>\n<p>For example, there are methods for retrieving AAS and submodels based on their ID, as well as\u00a0 for handling SubmodelElements.<\/p>\n<p>In addition to several SDKs and off-the-shelf components, an <a href=\"https:\/\/wiki.eclipse.org\/BaSyx\" target=\"_blank\" rel=\"noopener noreferrer\">open-source wiki<\/a> is also provided. Here, a plethora of documentation on components and concepts, example snippets, and scenarios is available, such as the prerequisites and <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Download\" target=\"_blank\" rel=\"noopener noreferrer\">installation instructions<\/a> of the Java SDK.<\/p>\n<p>Additionally, an API documentation for each key component is provided. The API is described by an OpenAPI 3.0 specification and hosted on <a href=\"https:\/\/app.swaggerhub.com\/organizations\/BaSyx\" target=\"_blank\" rel=\"noopener noreferrer\">SwaggerHub<\/a>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-7191\" src=\"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/AAS-Registry-API-698x334.png\" alt=\"Fraunhofer IESE - AAS Registry API\" width=\"698\" height=\"334\" srcset=\"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/AAS-Registry-API-698x334.png 698w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/AAS-Registry-API-400x192.png 400w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/AAS-Registry-API-768x368.png 768w, https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/AAS-Registry-API.png 1132w\" sizes=\"auto, (max-width: 698px) 100vw, 698px\" \/><\/p>\n<p>Figure 2 &#8211; Excerpt of the AAS Registry API<\/p>\n<p>Furthermore, there exist other open-source tools that facilitate working with AAS and their submodels. For example, the <a href=\"https:\/\/github.com\/admin-shell-io\/aasx-package-explorer\" target=\"_blank\" rel=\"noopener noreferrer\">AASX Package Explorer<\/a> enables quick creation of AAS and submodels via a graphical user interface. This configured data is then stored as an AASX package, which can be understood, for example, as a zip file containing Asset Administration Shells, submodels, and accompanying data (e.g., data sheets). However, this AASX file only contains the serialized data \u2013 it is not able to provide a runtime interface on its own. Using the off-the-shelf components provided by BaSyx, these AASX components can be hosted with little effort. Further details are described in the <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Documentation_\/_Components_\/_AAS_Server\" target=\"_blank\" rel=\"noopener noreferrer\">wiki<\/a>.<\/p>\n<h2><strong>Off-the-shelf components enable a quick instantiation<\/strong><\/h2>\n<p>While the SDKs allow quick creation of programs working with AAS and their infrastructure, they require knowledge of the respective programming language. However, not every user of BaSyx and the AAS environment needs to have programming know-how. Off-the-shelf components enable stakeholders to quickly instantiate the AAS infrastructure with no programming effort. Instead, with little changes in configuration files, they can be tailored to the specific contexts and the stakeholders\u2019 needs.<\/p>\n<p>Currently, we have the following off-the-shelf components with their respective backends at our disposal:<\/p>\n<ul>\n<li><strong>AAS Registry<\/strong>\n<ul>\n<li>In-memory<\/li>\n<li>MongoDB<\/li>\n<li>SQL database<\/li>\n<\/ul>\n<\/li>\n<li><strong>AAS Server<\/strong>\n<ul>\n<li>In-memory<\/li>\n<li>MongoDB<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>These components are distributed using Docker images. For example, images for these key components are available on <a href=\"https:\/\/hub.docker.com\/u\/eclipsebasyx\" target=\"_blank\" rel=\"noopener noreferrer\">DockerHub<\/a> and can thus be easily downloaded and instantiated.<\/p>\n<p>Additionally, the components are documented on their <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Documentation_\/_Components_\/_AAS_Server\" target=\"_blank\" rel=\"noopener noreferrer\">own page<\/a> in the BaSyx Wiki.<\/p>\n<h2><strong>Demonstrating the Industrie 4.0 IT infrastructure for Digital Twins with Eclipse BaSyx<\/strong><\/h2>\n<p>To showcase the principles of the Industrie 4.0 IT infrastructure for Digital Twins and Eclipse BaSyx, we will next provide and describe an example scenario. This scenario utilizes the previously mentioned off-the-shelf components. The code for this scenario is also available <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Scenarios_\/_Cloud_Edge_Deployment\" target=\"_blank\" rel=\"noopener noreferrer\">online<\/a>. In this scenario, an oven will be added to the system and will integrate itself with the AAS infrastructure.<\/p>\n<p>However, first we have to set up the infrastructure itself. Note that you need to set up Docker on your machine. Since the AAS Server and the AAS Registry images are made available via Docker Hub, they can be pulled directly and started using the following commands:<\/p>\n<pre><span lang=\"EN-US\">docker run --name=aasServer -p 8081:4001 eclipsebasyx\/aas-server:0.1.0-PREVIEW<\/span><\/pre>\n<pre><span lang=\"EN-US\">docker run --name=aasRegistry \u2013d -p 8082:4000 eclipsebasyx\/aas-registry:1.0.0<\/span><\/pre>\n<p>The first time this is executed, the required images are automatically downloaded from Docker Hub. Now the local endpoints for accessing the AAS Server and the AAS Registry are:<\/p>\n<pre><span lang=\"EN-US\">http:\/\/localhost:8081\/aasServer\/shells\/\r\nhttp:\/\/localhost:8082\/registry\/api\/v1\/registry\u00a0<\/span><\/pre>\n<p>The AAS Registry and the respective containers can be started, stopped, and removed using their names \u201caasServer\u201d and \u201cregistry\u201d. For example, the following commands can be used to control the registry:<\/p>\n<pre><span lang=\"EN-US\">docker stop aasRegistrydocker start aasRegistrydocker rm aasRegistry<\/span><\/pre>\n<p>By default, these components are completely empty and based on the non-persistent in-memory &#8222;backend&#8220;. This and other settings can be changed by providing a configuration file when starting the container. For example, the AAS Server can be configured to load an existing AASX file (i.e., a packaged AAS, its submodels, as well as accompanying files). All configuration possibilities are documented on a <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Documentation_\/_Components_\/_AAS_Server\" target=\"_blank\" rel=\"noopener noreferrer\">page<\/a> in the Eclipse Wiki.<\/p>\n<p>After the infrastructure is set up, we can focus on the device commissioning.<\/p>\n<p>First, the Asset Administration Shell and the two submodels (one for the Edge Node and one containing the documentation) are created.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Create the oven asset\r\nAsset ovenAsset = new Asset(\"OvenAsset\", new Custom-Id(\"basyx.examples.OvenAsset\"), AssetKind.INSTANCE);\r\n\r\n\/\/ Create the AAS representing the oven\r\nAssetAdministrationShell ovenAAS = new AssetAdministrationShell(\"oven\", new CustomId(\"basyx.examples.oven\"), ovenAsset);\r\n\r\n\/\/ Create the documentation Submodel\r\nSubModel docuSm = new SubModel(\"oven_doc\", new Custom-Id(\"basyx.examples.oven.oven_documentation_sm\"));\r\n\r\n\/\/ Create the maximum temperature property and include it in the sub-model\r\nProperty maxTemp = new Property(\"max_temp\", 1000);\r\ndocuSm.addSubModelElement(maxTemp);\r\n\r\n\/\/ Create the edge submodel\r\nSubModel edgeSm = new SubModel(\"curr_temp\", new Custom-Id(\"basyx.examples.oven.current_oven_temperature\"));\r\n\t\t\r\n\/\/ The property in this submodel contains the currently measured temperature of the oven\r\n\/\/ It is represented by a static value in this example\r\nProperty property = new Property(\"temp\", 31);\r\nedgeSm.addSubModelElement(property);\r\n\r\n<\/span><\/pre>\n<p>Now the Edge Node can be created and populated with the edgeSM. For this, an HTTP server is configured using the BaSyxContextConfiguration and a SubmodelServlet containing the Edge Submodel. After the configuration, the server is started.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Create a BaSyxContext for port 8083 with an empty endpoint\r\nBaSyxContextConfiguration config = <strong>new<\/strong> BaSyxContextConfiguration(8083, \"\");\r\nBaSyxContext context = config.createBaSyxContext();\r\n\r\n\/\/ Create a new SubmodelServlet containing the edgeSubmodel\r\nSubmodelServlet smServlet = <strong>new<\/strong> SubmodelServlet(edgeSM);\r\n\u00a0\r\n\/\/ Add the SubmodelServlet mapping to the context at the path \"\/oven\/curr_temp\"\r\ncontext.addServletMapping(\"\/oven\/curr_temp\/*\", smServlet);\r\n\r\n\/\/ Create and start a HTTP server with the context created above\r\nAASHTTPServer edgeServer = <strong>new<\/strong> AASHTTPServer(context);\r\nedgeServer.start();\r\n\r\n<\/span><\/pre>\n<p>In the next step, the AAS and the Documentation Submodel that were created are uploaded to the cloud. The ConnectedAASManager is used for this task.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Create a proxy to the registry server\r\nAASRegistryProxy registry = new AASRegistryProxy(\"http:\/\/localhost:8082\/registry\/\");\r\n\r\n\/\/ Create a ConnectedAASManager with the registry created above\r\naasManager = <strong>new<\/strong> ConnectedAssetAdministrationShellManager(registry);\r\n\r\n\/\/ Push the AAS to the cloud server\r\n\/\/ The manager automatically registers it in the registry\r\naasManager.createAAS(ovenAAS, \"http:\/\/localhost:8081\/aasServer\/\");\r\n\r\n\u00a0\/\/ Push the docuSubmodel to the cloud\r\n\/\/ The manager automatically registers it in the registry\r\naasManager.createSubModel(ovenAAS.getIdentification(), docuSm);\r\n\r\n<\/span><\/pre>\n<p>The last step is to register the submodel provided by the Edge Node now running in the registry. For this, a descriptor for the submodel has to be created first .<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Build the SubmodelDescriptor for the Edge-SM\r\nSubmodelDescriptor edgeSMDescriptor = SubmodelDescriptor(edgeSM, \"http:\/\/localhost:8083\/oven\/curr_temp\/\");\r\n\r\n\/\/ Add the already existing edgeSM to the descriptor of the AAS\r\nregistry.register(ovenAAS.getIdentification(), edgeSMDescriptor);\r\n<\/span><\/pre>\n<p>Now that the device has been commissioned and integrated with the system, we can use the Java SDK to retrieve the information about the AAS and the submodels, e.g., in an application.<br \/>\nThe following code shows how to retrieve an AAS from the server using the ConnectedAssetAdministrationShellManager.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Create a proxy to the registry server\r\nAASRegistryProxy registry = AASRegistryProxy(\"http:\/\/localhost:8082\/registry\");\r\n\r\n\/\/ Create a ConnectedAASManager using the registry proxy\r\nConnectedAssetAdministrationShellManager manager = new ConnectedAssetAdministrationShellManager(registry);\r\n\r\n\/\/ Retrieve the AAS from the server\r\nIAssetAdministrationShell aas = manager.retrieveAAS(ovenAAS.getIdentification());\r\n<\/span><\/pre>\n<p>Next, the submodels are retrieved from the server using the AAS obtained above.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Get the Submodels from the AAS\r\n\/\/ The returned Map maps idShort to Submodel\r\nMap&lt;String, ISubModel&gt; submodels = aas.getSubModels();\r\n<\/span><\/pre>\n<p>Finally, the <em>max_temp <\/em>property is retrieved from the Documentation Submodel and printed to the console.<\/p>\n<pre><span lang=\"EN-US\">\r\n\/\/ Get the required Submodel from the Map using its idShort\r\nISubModel docuSubmodel = submodels.get(\"oven_doc\");\r\n\r\n\/\/ Retrieve it using its idShort\r\nISubmodelElement smElement = docuSubmodel.getSubmodelElement(\"max_temp\");\r\n\r\n\/\/ Print its value to the console\r\nSystem.out.println(smElement.getValue());\r\n\r\n<\/span><\/pre>\n<h2><strong>Taking a deep dive into Eclipse BaSyx<\/strong><\/h2>\n<p>Of course, the previous example showcases only a small portion of the features of Eclipse BaSyx. In the following, a small excerpt of other features is given:<\/p>\n<ul>\n<li><strong>Events:<\/strong> Pulling information is not always the most appropriate interaction pattern. Instead, events can be triggered when an element changes. Currently, BaSyx supports events for changes on Submodels and their respective SubmodelElements. In the future, events will also be supported for changes on the AAS and Registry level.<\/li>\n<li><strong>Virtual Automation Bus: <\/strong>The integration of heterogeneous communication systems can impose great challenges. The Virtual Automation Bus provides quick integration of arbitrary protocols through the definition of an intermediate language [3].<\/li>\n<li><strong>Control Components: <\/strong>In a service-based production, interaction with service providers has to be addressed. Control Components provide the necessary abstraction and API for handling different types of service providers.<\/li>\n<\/ul>\n<p>For further reading, the Eclipse BaSyx <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Developer_\/_Contributing\">Project Wiki<\/a> is a good starting point. As previously mentioned, we provide a multitude of <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Examples\">code snippets<\/a> and <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Scenarios_\/_Cloud_Edge_Deployment\">scenarios<\/a> illustrating further use cases of BaSyx. Additionally, there are papers that describe Digital Twins for specific use cases. For example, the data models to be contained in Digital Twins for a service-based production are detailed [4].<\/p>\n<p>Additionally, Eclipse BaSyx enables easy implementation of custom components. It provides interfaces for each core component that can be overwritten. The rest is handled by the BaSyx system. Furthermore, it provides <a href=\"https:\/\/wiki.eclipse.org\/BaSyx_\/_Developer_\/_Contributing#Developing_new_Components\">Technology Compatibility Kits<\/a> (TCK)]. These TCKs exist for each core component of BaSyx and enable third-party developers to easily validate whether their components behave as expected by the BaSyx system.<\/p>\n<p>To summarize, Eclipse BaSyx and its off-the-shelf components make it easy to set up an Industrie 4.0 IT infrastructure for Asset Administration Shells. Its distribution as open-source software enables developers and users to quickly realize their own use cases and build commercial products.<\/p>\n<p>&nbsp;<\/p>\n<div class=\"info-box\">\n<p>Fraunhofer IESE is engaged in research on the Asset Administration Shell and the Industrie 4.0 IT Infrastructure in <a href=\"http:\/\/basys40.de\">BaSys 4.2.<\/a> In this project, <a href=\"https:\/\/www.eclipse.org\/basyx\/\">Eclipse BaSyx<\/a> is being developed as an open-source middleware that allows quick entry into the world of Industrie 4.0. With its asset administration shell, it supports future standardized Digital Twins. In addition, it offers many components that enable easy implementation of Industrie 4.0.<\/p>\n<p>&nbsp;<\/p>\n<p>In cooperation with NetApp and objective partner, <a href=\"https:\/\/www.objective-partner.de\/shopfloor-40-flexibilitaet-in-der-fertigung\/\">ShopFloor 4.0<\/a> is the commercial version of the solution, which offers comprehensive support packages and ready-to-use solutions.<\/p>\n<p>&nbsp;<\/p>\n<p>Additionally, the <em>German Federal Ministry of Education and Research (BMBF) <\/em>is <a href=\"https:\/\/blog.iese.fraunhofer.de\/basys-satelliten\/\">sponsoring<\/a> projects that want to explore the capabilities of BaSyx.<\/p>\n<\/div>\n<p><strong>SOURCES:<\/strong><\/p>\n<p>[1] <a href=\"https:\/\/www.immagic.com\/eLibrary\/ARCHIVES\/GENERAL\/OPTAR_US\/O051219W.pdf\">https:\/\/www.immagic.com\/eLibrary\/ARCHIVES\/GENERAL\/OPTAR_US\/O051219W.pdf<\/a><\/p>\n<p>[2] Ebert, Christof. &#8222;Open source drives innovation.&#8220; IEEE Software 24.3 (2007): 105-109.<\/p>\n<p>[3] Kuhn, Thomas, Pablo Oliveira Antonino, and Frank Schnicke. &#8222;Industrie 4.0 Virtual Automation Bus Architecture.&#8220; <em>European Conference on Software Architecture<\/em>. Springer, Cham, 2020.<\/p>\n<p>[4] Schnicke, Frank, Thomas Kuhn, and Pablo Oliveira Antonino. &#8222;Enabling Industry 4.0 Service-Oriented Architecture Through Digital Twins.&#8220; <em>European Conference on Software Architecture<\/em>. Springer, Cham, 2020.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In our previous blog post, we outlined a solution architecture to show what an Industrie 4.0 IT infrastructure for Digital Twins can look like. However, an architecture on its own is not sufficient for realizing Industrie 4.0. To bring the&#8230;<\/p>\n","protected":false},"author":76,"featured_media":7217,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[94],"tags":[120,202],"coauthors":[317,377,378],"class_list":["post-7187","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industrie-4-0","tag-digitaler-zwilling","tag-softwarearchitektur"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE<\/title>\n<meta name=\"description\" content=\"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE\" \/>\n<meta property=\"og:description\" content=\"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/\" \/>\n<meta property=\"og:site_name\" content=\"Fraunhofer IESE\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/FraunhoferIESE\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-12-15T07:36:39+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-01-08T08:20:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"748\" \/>\n\t<meta property=\"og:image:height\" content=\"375\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Frank Schnicke, Daniel Espen, Maximilian Conradi\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@FraunhoferIESE\" \/>\n<meta name=\"twitter:site\" content=\"@FraunhoferIESE\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Frank Schnicke\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"11\u00a0Minuten\" \/>\n\t<meta name=\"twitter:label3\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data3\" content=\"Frank Schnicke, Daniel Espen, Maximilian Conradi\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/\"},\"author\":{\"name\":\"Frank Schnicke\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#\\\/schema\\\/person\\\/6508db45546b3cce421931dc38d4a8f1\"},\"headline\":\"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins\",\"datePublished\":\"2020-12-15T07:36:39+00:00\",\"dateModified\":\"2024-01-08T08:20:15+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/\"},\"wordCount\":1887,\"publisher\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg\",\"keywords\":[\"Digitaler Zwilling\",\"Softwarearchitektur\"],\"articleSection\":[\"Industrie 4.0\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/\",\"name\":\"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg\",\"datePublished\":\"2020-12-15T07:36:39+00:00\",\"dateModified\":\"2024-01-08T08:20:15+00:00\",\"description\":\"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg\",\"width\":748,\"height\":375,\"caption\":\"Industrie 4.0 IT Infrastructure\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/industrie-4-0-it-infrastructure-for-digital-twins-part2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/\",\"name\":\"Fraunhofer IESE\",\"description\":\"Blog des Fraunhofer-Institut f\u00fcr Experimentelles Software Engineering\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#organization\",\"name\":\"Fraunhofer IESE\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/fhg_iese_logo.png\",\"contentUrl\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/fhg_iese_logo.png\",\"width\":183,\"height\":50,\"caption\":\"Fraunhofer IESE\"},\"image\":{\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/FraunhoferIESE\\\/\",\"https:\\\/\\\/x.com\\\/FraunhoferIESE\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/fraunhoferiese\\\/\",\"https:\\\/\\\/www.youtube.com\\\/c\\\/FraunhoferIESE\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/#\\\/schema\\\/person\\\/6508db45546b3cce421931dc38d4a8f1\",\"name\":\"Frank Schnicke\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/04\\\/schnicke-frank_320-250_5D3_9948-96x96.jpg22964df4fa0931b3ee0c148d30b634ee\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/04\\\/schnicke-frank_320-250_5D3_9948-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/04\\\/schnicke-frank_320-250_5D3_9948-96x96.jpg\",\"caption\":\"Frank Schnicke\"},\"description\":\"Frank Schnicke ist Leiter der Abteilung Digital Twin Engineering am Fraunhofer-Institut f\u00fcr Experimentelles Software Engineering. Die von ihm geleitete Abteilung konzentriert sich auf die Bereitstellung skalierbarer L\u00f6sungen f\u00fcr die Arbeit mit der Asset Administration Shell, die sowohl in missionskritischen Bereichen als auch in AAS-Datenr\u00e4umen eingesetzt werden k\u00f6nnen. Au\u00dferdem ist er Projektleiter f\u00fcr Eclipse BaSyx und Eclipse AAS4J, die eine einfache und nachhaltige Implementierung von AAS-basierten Anwendungsf\u00e4llen erm\u00f6glichen.\",\"url\":\"https:\\\/\\\/www.iese.fraunhofer.de\\\/blog\\\/author\\\/frank-schnicke\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE","description":"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/","og_locale":"de_DE","og_type":"article","og_title":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE","og_description":"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?","og_url":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/","og_site_name":"Fraunhofer IESE","article_publisher":"https:\/\/www.facebook.com\/FraunhoferIESE\/","article_published_time":"2020-12-15T07:36:39+00:00","article_modified_time":"2024-01-08T08:20:15+00:00","og_image":[{"width":748,"height":375,"url":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","type":"image\/jpeg"}],"author":"Frank Schnicke, Daniel Espen, Maximilian Conradi","twitter_card":"summary_large_image","twitter_creator":"@FraunhoferIESE","twitter_site":"@FraunhoferIESE","twitter_misc":{"Verfasst von":"Frank Schnicke","Gesch\u00e4tzte Lesezeit":"11\u00a0Minuten","Written by":"Frank Schnicke, Daniel Espen, Maximilian Conradi"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#article","isPartOf":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/"},"author":{"name":"Frank Schnicke","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#\/schema\/person\/6508db45546b3cce421931dc38d4a8f1"},"headline":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins","datePublished":"2020-12-15T07:36:39+00:00","dateModified":"2024-01-08T08:20:15+00:00","mainEntityOfPage":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/"},"wordCount":1887,"publisher":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#organization"},"image":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","keywords":["Digitaler Zwilling","Softwarearchitektur"],"articleSection":["Industrie 4.0"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/","url":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/","name":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins - Blog des Fraunhofer IESE","isPartOf":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#primaryimage"},"image":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","datePublished":"2020-12-15T07:36:39+00:00","dateModified":"2024-01-08T08:20:15+00:00","description":"Digital Twins enable core Industry 4.0 use cases. However, they require an IT infrastructure for Digital Twins. How can this be realized?","breadcrumb":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#primaryimage","url":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","contentUrl":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","width":748,"height":375,"caption":"Industrie 4.0 IT Infrastructure"},{"@type":"BreadcrumbList","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/industrie-4-0-it-infrastructure-for-digital-twins-part2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.iese.fraunhofer.de\/blog\/"},{"@type":"ListItem","position":2,"name":"Implementing the Industrie 4.0 IT Infrastructure for Digital Twins"}]},{"@type":"WebSite","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#website","url":"https:\/\/www.iese.fraunhofer.de\/blog\/","name":"Fraunhofer IESE","description":"Blog des Fraunhofer-Institut f\u00fcr Experimentelles Software Engineering","publisher":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.iese.fraunhofer.de\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#organization","name":"Fraunhofer IESE","url":"https:\/\/www.iese.fraunhofer.de\/blog\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2016\/08\/fhg_iese_logo.png","contentUrl":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2016\/08\/fhg_iese_logo.png","width":183,"height":50,"caption":"Fraunhofer IESE"},"image":{"@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/FraunhoferIESE\/","https:\/\/x.com\/FraunhoferIESE","https:\/\/www.linkedin.com\/company\/fraunhoferiese\/","https:\/\/www.youtube.com\/c\/FraunhoferIESE"]},{"@type":"Person","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/#\/schema\/person\/6508db45546b3cce421931dc38d4a8f1","name":"Frank Schnicke","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/04\/schnicke-frank_320-250_5D3_9948-96x96.jpg22964df4fa0931b3ee0c148d30b634ee","url":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/04\/schnicke-frank_320-250_5D3_9948-96x96.jpg","contentUrl":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/04\/schnicke-frank_320-250_5D3_9948-96x96.jpg","caption":"Frank Schnicke"},"description":"Frank Schnicke ist Leiter der Abteilung Digital Twin Engineering am Fraunhofer-Institut f\u00fcr Experimentelles Software Engineering. Die von ihm geleitete Abteilung konzentriert sich auf die Bereitstellung skalierbarer L\u00f6sungen f\u00fcr die Arbeit mit der Asset Administration Shell, die sowohl in missionskritischen Bereichen als auch in AAS-Datenr\u00e4umen eingesetzt werden k\u00f6nnen. Au\u00dferdem ist er Projektleiter f\u00fcr Eclipse BaSyx und Eclipse AAS4J, die eine einfache und nachhaltige Implementierung von AAS-basierten Anwendungsf\u00e4llen erm\u00f6glichen.","url":"https:\/\/www.iese.fraunhofer.de\/blog\/author\/frank-schnicke\/"}]}},"jetpack_featured_media_url":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-content\/uploads\/2020\/12\/header-blog-industry_4.0_infrastructure-istock_com_ipopba-fraunhofer_iese-1.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/posts\/7187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/users\/76"}],"replies":[{"embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/comments?post=7187"}],"version-history":[{"count":25,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/posts\/7187\/revisions"}],"predecessor-version":[{"id":10149,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/posts\/7187\/revisions\/10149"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/media\/7217"}],"wp:attachment":[{"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/media?parent=7187"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/categories?post=7187"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/tags?post=7187"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.iese.fraunhofer.de\/blog\/wp-json\/wp\/v2\/coauthors?post=7187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}