KR20230168882A - Data Interoperating Method of Enterprise and Control Applications via Asset Administration Shell - Google Patents

Abstract

In cyber-physical systems, enterprise applications, controls, and physical manufacturing assets are interconnected and exchange information seamlessly. However, software and hardware often differ in terms of data interfaces, data formats, and semantics. Existing enterprise applications typically use file-based interfaces (e.g. Excel). Control applications always support Ethernet-based protocols (e.g. OPC UA). Therefore, there is currently a lack of data interoperability. Asset Management Shell (AAS) is a new approach to achieve data interoperability across the automation pyramid as the AASX data format represents AAS information and supports data communication over OPC UA. The present invention first provides insight into the AASX format and provides example applications for AASX, and then presents an AASX-based solution for bidirectional data exchange between enterprise and control applications. In the solution according to the invention, conversion between AASX and Excel spreadsheets is completed, enabling interoperable data exchange. Finally, a data exchange scenario for motor control is constructed to verify the effectiveness of the solution. The results show that no data is lost during the two-way conversion.

Description

Data Interoperating Method of Enterprise and Control Applications via Asset Administration Shell}

The present invention relates to data interoperability technology, and more specifically, to an AASX-based solution capable of two-way lossless information exchange between an enterprise (enterprise) and a control application.

The Internet of Things (IoT) and Cyber Physical Systems (CPS) have emerged as core technologies that meet the needs of many users and applications in the era of the Fourth Industrial Revolution. Manufacturing operations will be digitized and distributed from the shop floor to the office and across the entire enterprise network. Traditional manufacturing systems must change.

Modeling, simulation, and integration of products, processes, and resources (PPR) throughout the production life cycle are promising approaches to increase manufacturing efficiency. Manufacturing assets such as sensors, machines, and control systems (applications or software) from various manufacturers and suppliers generate large amounts of data during production. System integrators or power plant operators must expend significant effort to integrate data into higher-level enterprise systems that support decision making.

Manufacturing data can be represented and stored in a variety of formats, which hinders efficient and transparent data transfer between control systems and enterprise applications. In particular, industrial control systems often have Ethernet-based interfaces such as Open Platform Communications Unified Architecture (OPC UA) to support runtime data communication. Traditional enterprise applications, such as enterprise resource planning systems (ERP), typically use file-based methods such as comma-separated values (CSV) files and Microsoft Excel spreadsheets to communicate data. Files are exchanged between two different applications either directly (end-to-end) or indirectly through an intermediate data hub. Data exchange often takes place offline, which is time-consuming and error-prone.

Moreover, the final application must have the same file-based interface, which requires significant system development. Data homogeneity (consistent semantically produced data that can be understood by all users) is essential to meet the needs of all engineering chain participants. Data collection should be simple and allow rapid and selective access to information. Therefore, the industry needs data interoperability solutions that ensure easy data integration, comprehensive semantic data homogenization, contextual information delivery, and full access and control of data flows.

Recently, the use of digital twins (DTs) to model field manufacturing resources has improved data interoperability. Industry 4.0 Asset Management Shell (AAS), a practical example of DT, can promote interoperability between a manufacturing company's applications by making data searchable, identifiable, and accessible. AASX is a package file format that stands for AAS. The AASX interface for field hardware assets was previously developed.

Many researchers have studied data exchange between industrial applications or engineering tools. For example, Automation Markup Language (AutomationML) is a neutral data format that connects heterogeneous modern engineering tools from various fields. AutomationML describes real plant components at various levels of detail. However, data semantics has not received much attention. AutomationML primarily focuses on the engineering phase of the plant life cycle. The MTConnect data exchange standard uses a domain-specific vocabulary to devise data models for factory floor equipment. However, MTConnect is a read-only protocol primarily used to monitor data from machine tool components. Therefore, neither AutomationML nor MTConnect can prove data interoperability between different applications.

In academic research, AASX is widely used as the data representation and exchange format for AAS. It is likely that AASX will become the official data format of AAS. IEC project 63278-1 aims to develop an international standard for AAS, while other studies have described a lightweight software framework for AAS implementation (based on the AAS specification). AASX was used to demonstrate such an implementation. Finally, we comprehensively analyzed open source solutions for AAS implementation and presented a method for implementing AASX-based AAS in embedded devices, significantly reducing computing requirements. However, the above study only focused on AASX itself rather than data exchange scenarios between applications using AASX.

There are only a few studies that focus on proposing AASX-enabled data exchange solutions. For example, one study developed AAS models for two different software tools. AASX was used for integration and another study used AASX to map the proprietary ABB capability information model to the standard AAS information model.

Additionally, in another study, AASX was used to develop a data AAS for managing cross-enterprise engineering data sets. This research promotes the adoption of AASX to solve various data interoperability problems. However, it is very important to design a generic AASX-enabled data interoperability solution that not only enables consistent data exchange between enterprise and control applications, but can also extend to control of field devices.

The present invention was created in consideration of the above-mentioned situation, and the purpose of the present invention is to provide an AASX-based solution capable of two-way lossless information exchange between an enterprise and a control application.

To this end, the method according to the present invention is a data interoperability method between an enterprise application and a control application performed in an industrial manufacturing system, comprising the steps of the control application of the control system collecting data of field assets, and the collected data of field assets. Converting the AASX file to an AASX file using an AASX package explorer, converting the AASX file to enterprise file data using a web conversion tool, and transmitting the enterprise file data to an enterprise application of an enterprise system. Includes.

The method according to the present invention is a data interoperability method between an enterprise application and a control application performed in an industrial manufacturing system, comprising the steps of an enterprise application of an enterprise system outputting enterprise file data, and converting the enterprise file data to a web conversion tool. It includes converting the JSON file to a JSON file using an AASX package explorer.

The method according to the present invention is a data interoperability method between an enterprise application and a control application performed in an industrial manufacturing system, comprising the steps of generating field asset data collected by the control application as an AASX file using an AASX package explorer; Converting the AASX file to a JSON file using the AASX package explorer and uploading it to a web conversion tool, parsing all elements of the AASX model in the JSON file using the web conversion tool, and then converting the Excel template to an Excel template. It includes the step of generating an Excel file based on the data and outputting it to the enterprise application.

The method according to the present invention is a data interoperability method between an enterprise application and a control application performed in an industrial manufacturing system, comprising the steps of uploading an Excel file output from the enterprise application to a web conversion tool, and converting the Excel file using the web conversion tool. It includes steps of parsing the file and performing serialization to output the JSON file to the AASX package explorer, and converting the JSON file to an AASX file using the AASX package explorer.

As described above, the present invention can ensure two-way lossless data conversion between AASX and Excel by providing an AASX-based data exchange solution that connects enterprise and control level applications.

Additionally, because AASX acts as an intermediary for data exchange, it can effectively eliminate data silos that separate enterprise and control applications.

Figure 1: AAS transforming manufacturing assets into Industry 4.0 components
Figure 2: AAS metamodel and serialization in AASX format
Figure 3: Intermediate AASX interface connecting hardware and software
Figure 4: AASX Package Explorer and AASX information accessed via OPC UA and REST
Figure 5: AASX solution for data exchange between enterprise and control applications
Figure 6: Converting data from AASX to Excel and vice versa
Figure 7: Data exchange for motor control scenarios
Figure 8: AASX model and its properties displayed in AASX Package Explorer
Figure 9: Data exchange results for motor control scenario
Figure 10: Flow chart of data interoperability method according to the present invention

Hereinafter, embodiments according to the present invention will be described in detail with reference to the attached drawings. The configuration of the present invention and its operational effects will be clearly understood through the detailed description below.

Embodiments of the invention focus on data interconnection between high-level and mid-level control applications. Traditional enterprise applications typically use file-based methods (e.g. Excel spreadsheets) to exchange information, while control applications always support Ethernet-based protocols (e.g. OPC UA). AASX can support data communication via OPC UA. Information semantics are implemented in AASX to ensure data interoperability.

Background on AAS and AASX

As seen in Figure 1, AAS is a standardized digital representation of assets with industrial applications that facilitates interoperability between applications in manufacturing companies by allowing uniform access to information and functionality. AAS provides an interoperable way to capture key information about an asset, including its unique attributes, operating parameters, and technical capabilities. It enables direct interaction through standardized and secure communication links with other Industry 4.0 components.

The structure of AAS is defined in Part 1 of the AAS specification. As shown in Figure 2(a), the AAS meta model has a 'Submodel' that defines specific aspects of 'AssetInformation'. 'Submodel' contains 'SubmodelElement' which organizes asset information into 'Property' for example. The definition of 'Property' is linked to the definition of 'ConceptDescription', which references a semantic 'DataSpecification' such as the Common Data Dictionary (CDD) or ECLASS. AAS model elements accept several types of identifiers (IDs), including Internationalized Resource Identifier (IRI), International Registration Data Identifier (IRDI), and custom IDs. Depending on their purpose, they identify elements within a single AAS or across an AAS network that extends within the company (or outside the company).

Currently, AAS is considered a promising concept within Industry 4.0 initiatives. Information and communication technologies facilitate the practical use of AAS. Current research on AAS in academia and industry generally focuses on specific cases, with different AAS implementation methods. Web ontology languages such as AutomationML, OPC UA, and RDF (Resource Description Framework) were used. Standardized guidelines (or agreed upon technical approaches) are urgently needed to implement AAS.

As shown in Figure 2(b), the AASX file encapsulates the AAS information, including the AAS itself, sub-model elements, properties, concept descriptions, and additional files, in a structurally sound manner according to the AAS metamodel. Compared to traditional engineering approaches to data interoperability (e.g. AutomationML), AASX not only connects to field-level hardware assets (e.g. motors), but also enables data integration into enterprise-level applications (e.g. ERP) and enables these software applications. Facilitates data transfer between programs. Clear data semantics are guaranteed. All hardware and software in the entire automation pyramid can be interconnected in a networked, non-hierarchical system and thus exchange information through a uniform AASX interface. As shown in Figure 3, field hardware, control software, enterprise and management applications can connect to the intermediate AASX interface, although the data interfaces vary.

The Industrial Digital Twin Association (IDTA) has developed a series of AASX-based open source applications for creating, editing, and viewing AAS information. These applications allow users to intuitively understand how AAS is organized and information is accessed and exchanged. Applications have different ways to access AAS data, all of which follow Parts 1 and 2 of the AAS specification.

Below we summarize the two main applications, the first of which is the AASX Package Explorer. This C#-based AAS editor manipulates AASX information and implements several application programming interfaces (APIs), including representational state transfer (REST), Message Queuing Telemetry Transport (MQTT), and OPC UA. These APIs allow other applications to access AASX information. Security mechanisms (e.g. token-based authentication) are also built-in. As shown in the AASX package explorer in Figure 4(a), assets and their AAS information can be accessed and explored by an OPC UA client (e.g. UaExpert) [Figure 4(b)]. Information can also be optionally accessed through a REST interface in a web browser. Results (e.g. submodel data) are displayed in the JSON file in Figure 4(c).

The second application, AASX Server, is derived from AASX Package Explorer. AASX Server is a C#-based program that implements a server hosting AAS information (AASX models). AASX servers can be accessed via REST, MQTT and OPC UA protocols. Secure access is guaranteed.

However, these two programs only work on high-end devices such as personal computers. Before integrating into user-specific applications and deploying to devices with limited resources, AASX models must first be converted to a machine-interpretable data format, such as Extensible Markup Language (XML) or JavaScript Object Notation (JSON). This feature is included in the AASX Package Explorer. In previous research, the applicant applied AASX to a robot-based manufacturing system. Runtime data from field-level robots were mapped to an AASX model and the model was integrated into OPC UA for data communication with a web application in the cloud.

Several open source projects focusing on AASX implementation are listed in the GitHub repository. For example, the 'java-serializer' project serializes/deserializes JAVA classes to/from AASX instances, while the 'aas-transformation-library' project converts AutomationML models to AASX models. Results are displayed in JSON format.

AASX data exchange method for enterprise and control applications

We first present the data exchange challenges faced by enterprise and control applications, then propose a data conversion solution between AASX and Excel, and finally detail the data conversion steps.

A. Problem

Consider the following manufacturing scenario: Field devices perform specific tasks and generate large amounts of production data. The control system transmits the collected data to enterprise applications for analysis. The enterprise program then creates a manufacturing schedule and instructs the control system to process new production tasks for field devices to perform. For this two-way information exchange, enterprise-level applications typically use file-based interfaces such as Excel, while control-level systems use industrial communication interfaces such as OPC UA, ensuring consistent data between enterprise applications and control systems. There is not enough exchange. AASX can support data communication via OPC UA. The AASX data format can act as an intermediary between enterprise applications and control systems. The only remaining task is data conversion between AASX and Excel.

B.Solution

The entire two-way information exchange in the above scenario is shown in Figure 5. The present invention has designed an AASX solution that allows two-way information exchange. The AASX solution is implemented as follows: All field asset information and data collected from the control system through top-down operations are first converted to AASX files using the AASX Package Explorer. Then convert the data from the AASX file to Excel using a web conversion tool. Finally, import the Excel file into your enterprise application. From top to bottom, the conversion tool converts Excel data to AASX format. The present invention focuses on data conversion because AASX data communication has been achieved through OPC UA in the prior art. Additionally, Excel file import/export is within the scope of certain industry enterprise level applications and is therefore not considered here.

C. Data conversion step

Figure 6 shows the data conversion process between AASX and Excel and the design process of the web conversion tool. The requirement for solution design is to realize bidirectional and lossless data transformation between source and destination. The tool has two independent parsing programs written in Python. One tool parses the AASX model (JSON file) to produce a properly formatted Excel file, and the other tool performs the opposite function. The two Python programs are stored in a GitHub repository.

1) Convert AASX to Excel

As shown at the top of FIG. 6, first prepare the AASX file (number 1 in FIG. 6) using the AASX package explorer. This file must be validated using the AASX Package Explorer's modeling rules. Otherwise, a warning or error message appears. Second, export the AASX file as a JSON file (number 2) supported by the AASX Package Explorer. Third, the JSON file is uploaded to a web conversion tool that deserializes the JSON data into Python objects. Finally, the Python program outputs an Excel file (No. 3) based on a pre-specified Excel template (No. 4) with a hierarchical structure for storing the parsed AASX information. In the third step, the tool parses all elements of the AASX model in the JSON file. Table 1 shows the items output as an Excel file. Specifically, Table 1(a) lists the main elements of the AASX file, Table 1(b) lists identifying information for the AASX elements, and Table 1(c) lists the semantic content of 'ConceptDescription' in the AASX file. List.

2) Convert Excel to AASX

The reverse procedure can be briefly described as follows. As shown at the bottom of Figure 6, the Excel template is populated with data from the enterprise application. The Excel file (number 5) is then uploaded to the web tool for conversion. Python parses the Excel file, performs serialization, and outputs the results as a JSON file (number 6). Finally, the AASX package explorer loads the JSON file and saves the AASX information as an AASX file (No. 7). This tool can only process files that meet the requirements of predefined Excel templates.

Test Case: Motor Control

Given a manufacturing scenario, we provide an example of real-world data exchange between a motor control system and an enterprise application. Reviews the AASX solution and demonstrates lossless data conversion between AASX and Excel. No enterprise or motor control applications are being developed here.

A. Data Exchange Scenario

The data exchange scenario for motor control is shown in Figure 7. After operating a specific motor, the control system must send the motor's operating data (e.g. rotational speed) to the enterprise application. Companies collect data, analyze it, and send new commands (e.g. control modes) to the motor control system. The motor can then perform new tasks. Detailed AASX model information is introduced below.

B. AASX Model

Figure 8 shows the motor control system model in the AASX package explorer. The AASX model serves as a benchmarking file in the example of data exchange. The file contains all AAS information to be exchanged between the enterprise application and the motor control system. The AASX model according to the present invention was created based on the official AASX example provided by IDTA, which shows all the disciplines/rules that users must follow to create their own AASX model. We adopt this AASX example because it is sophisticated, comprehensive, and allows us to verify the effectiveness of the data transformation solution.

As can be seen at the top of Figure 8, the AASX model describes AAS 'ExampleMotor' for asset 'ServoDCMotor'. AAS includes five well-defined sub-models that describe the characteristics and capacities of motors used in various fields. ‘Identification’ includes supplier information (e.g. manufacturer name). 'TechnicalData' defines the technical parameters of the motor (e.g. maximum torque). 'OperationalData' contains the runtime parameters of the motor (e.g. rotational speed). ‘Document’ stores and classifies asset documents (e.g. operation manuals). The above four sub-models are essential for describing assets. The last submodel, 'EnterpriseData', is customized for the motor control scenario, containing a 'SubmodelEelement' or 'Property' called 'ControlMode'. Enterprise users use it to control motor operation.

The bottom of Figure 8 shows detailed properties (e.g. semantic ID and content) of 'ControlMode'. The semantic ID links 'SubmodelElement' to its definition (e.g. 'ConceptDescription'). Additionally, 'ConceptDescription' includes the semantic description of 'SubmodelElement'. You may refer to semantic 'DataSpecifications' (i.e. data standards such as ECLASS and IEC 61360 that allow formal, common and unambiguous definitions of properties). If a suitable definition cannot be found in the standard, users can extend IEC 61360 to create and reference a public 'DataSpecification'. An attribute must have a data value and a value type. Supplementary files attached to the AASX model do not need to be converted and will not work with the conversion tool.

C. Data exchange results

The data exchange results of the motor control scenario are shown in Figure 9. AASX to Excel First export the example AASX model as a JSON file. Figure 9(a) shows the extraction of an Excel file converted from a JSON file. The extraction includes the motor's AAS, submodels, and properties. This Excel file can be further imported into enterprise applications. Meanwhile, when converting from Excel to AASX, the Excel file created in the first round is used as input. Figure 9(b) is an extracted JSON file converted from an Excel file. This JSON data block contains information about the motor's AAS submodel 'EnterpriseData'. You can import a JSON file and display it in the AASX Package Explorer.

Comparing the generated JSON file with the original JSON file exported from the AASX model, no data loss was found after two-way conversion. Therefore, both AASX models (before and after conversion) are identical. This proves the effectiveness of the conversion tool and the viability of the AASX solution for lossless data exchange between enterprise and control applications. All files have been uploaded to the GitHub repository and are free to use.

To successfully convert using an online conversion tool, you must follow certain rules when preparing your AASX file. For example, you must assign both a property's value type and an initial value. The properties of the submodel must be mapped to the corresponding 'ConceptDescription', and the definition of 'ConceptDescription' must not be empty.

Figure 10 shows a flowchart of a data interoperability method between an enterprise application and a control application according to the present invention.

Each step shown in Figure 10 is performed in an integrated industrial manufacturing system including an enterprise system and a control system. At this time, each step may be performed by hardware or software of the industrial manufacturing system.

Here, the enterprise system and the control system may be composed of hardware and software, respectively. For convenience of explanation, they will be divided into the enterprise system and its applications, and the control system and its applications.

In an embodiment of the present invention, the enterprise system constituting the industrial manufacturing system may be an enterprise resource planning (ERP) system, and the control system may be a PLC (power link communication) system.

Referring to FIG. 10, the data interoperability method between an enterprise application and a control application according to the present invention can be largely divided into data flow from the enterprise system to the control system and vice versa.

As shown in (a) of FIG. 10, when data is moved from the enterprise system to the control system, the control application of the control system in the industrial manufacturing system collects data of field assets (S10), and Convert to an AASX file using the AASX package explorer (S20), convert the AASX file to Excel data using a web conversion tool (S30), and then transfer the Excel data to the enterprise application of the enterprise system (S40). .

As shown in (b) of FIG. 10, when data is moved from the control system to the enterprise system, the enterprise application of the enterprise system in the industrial manufacturing system outputs Excel data (S100) and converts the Excel data using a web conversion tool. After converting to a JSON file (S110), converting the JSON file to an AASX file using the AASX package explorer (S120), and transmitting the AASX file to the application of the control system (S130), the control application enters the AASX file. Based on this, the operation of field assets is controlled.

In terms of the data interoperability required by Industry 4.0, AAS is emerging as a digitalized approach that enables closer interaction between cyber applications and physical devices. Given a uniform AAS interface, all manufacturing components (hardware devices and software applications) can be interconnected. In a fully integrated system, enterprise applications and manufacturing functions are aligned for efficient data flow.

However, existing research has paid little attention to the semantic aspects of information exchange. The present invention describes data conversion between AASX and Excel to ensure robust data exchange between enterprise and control applications. Excel is commonly used to manage business-related data in enterprise applications. AASX is an Industry 4.0 AAS-compliant data representation format that supports data communication with field-level manufacturing assets, for example via OPC UA. Additionally, an appropriate semantic description of the information is provided by the AASX model, which can refer to data standards such as IEC 61360. Data interoperability between enterprise and control applications is therefore ensured when two-way lossless conversion between AASX and Excel is possible.

The data conversion solution was validated using a motor control scenario. An AASX model for motor control was developed based on the AASX file provided by IDTA. No data was lost during the two-way conversion. The invention focuses on data conversion and is not currently aimed at developing enterprise or control applications.

Our case study is simple but demonstrates the effectiveness of the AASX-based data conversion method. One limitation of current solutions is that data conversion is completed by workers. In the future, we plan to develop an automatic conversion solution that can support runtime data conversion. The present invention will be applied to companies to control applications in actual industries. Conversion between AASX and other data formats, such as IEC 62264 Business to Manufacturing Markup Language (B2MML), will also be explored for the exchange of business information between the two organizations.

The above description is merely an exemplary explanation of the present invention, and various modifications may be made by those skilled in the art without departing from the technical spirit of the present invention.

Accordingly, the embodiments disclosed in the specification of the present invention do not limit the present invention. The scope of the present invention should be interpreted in accordance with the scope of the patent claims below, and all technologies within the equivalent scope thereof should be interpreted as being included in the scope of the present invention.

Claims (4)

In a method of data interoperability between an enterprise application and a control application performed in an industrial manufacturing system,
a control application of the control system collecting data from field assets;
Converting the collected field asset data into an AASX file using the AASX package explorer;
Converting the AASX file into enterprise file data using a web conversion tool;
A data interoperability method comprising transmitting the enterprise file data to an enterprise application of an enterprise system. In a method of data interoperability between an enterprise application and a control application performed in an industrial manufacturing system,
A step where the enterprise application of the enterprise system outputs enterprise file data,
Converting the enterprise file data into a JSON file using a web conversion tool,
A data interoperability method comprising converting the JSON file to an AASX file using an AASX package explorer. In a method of data interoperability between an enterprise application and a control application performed in an industrial manufacturing system,
Creating field asset data collected by the control application as an AASX file using the AASX package explorer;
Converting the AASX file into a JSON file using the AASX package explorer and uploading it to a web conversion tool;
A data interoperability method comprising parsing all elements of the AASX model in the JSON file using the web conversion tool, then generating an Excel file based on an Excel template and outputting it to the enterprise application. In a method of data interoperability between an enterprise application and a control application performed in an industrial manufacturing system,
Steps in which the Excel file output from the enterprise application is uploaded to the web conversion tool,
Parsing the Excel file using the web conversion tool, performing serialization, and outputting the JSON file to the AASX package explorer;
Data interoperability method comprising converting the JSON file to an AASX file using the AASX package explorer.