A unified modeling platform for industrial apps

Abstract

The present application discloses a unified modeling platform for industrial apps, including a system built-in plug-in module and a system kernel. The system built-in plug-in module is used to provide plug-in services according to the user's plug-in configuration request; the system kernel includes a metamodel bootstrap module, a model data operation protocol module, a model data publishing module and a model data processing plug-in module; the metamodel bootstrap module is used to realize the self-description of the model; the model data operation protocol module is used to provide data addition, modification or deletion services, and is also used to provide standard rest interface services; the model data publishing module is used to publish the data operation as a message after completing the data operation; the model data processing plug-in module is used to provide plug-in registration, deregistration and operation performance monitoring services. This solution allows industrial app developers to easily carry out relational data modeling and object model modeling, and by building the relationship between these data, all the factory data can be integrated.

Description

Technical Field

[0001] The present application relates to the field of industrial application technology, and more specifically, to a unified modeling platform for industrial applications. Background Art

[0002] Industrial APP is the carrier of industrial technology elements. In order to solve specific problems and meet specific needs, various knowledge in the industrial field is extracted through data modeling and analysis, structured organization, and systematic abstraction. Based on unified standards, these industrial technology elements are encapsulated and solidified to form an industrial application that can be efficiently reused and widely disseminated. Industrial APP encapsulates industrial technology elements such as processes, logic, data flows, experience, algorithms, knowledge, and laws that have specific functions and solve specific problems.

[0003] Since the industry involves a wide range of industries, each industry has accumulated a lot of knowledge. This feature makes industrial data modeling the key to industrial app development. Through the data modeling platform, industrial knowledge can be extracted, precipitated, and abstracted, laying the foundation for the development and evolution of upper-level apps. The versatility and flexibility of the data modeling platform greatly determine the efficiency and quality of industrial app development, especially the low-code-based development platform is more dependent on the underlying data modeling capabilities.

[0004] Currently, there is no data modeling solution that can well integrate relational data modeling and physical modeling. This has brought great obstacles to the modeling and development of industrial apps. Because app developers need to learn different modeling methods and tools to process data, in many scenarios, developers need to build different models for the same data based on different platforms, resulting in a lot of duplication of work. More importantly, the models built on different platforms cannot understand each other, and the data cannot be connected, resulting in users being unable to integrate all the factory data. Summary of the invention

[0005] In view of this, the present application provides a unified modeling platform for industrial apps, which is used to provide modeling services for the development of industrial apps, and is used to enable users to integrate all factory data by building relationships between data.

[0006] In order to achieve the above objectives, the proposed solution is as follows:

[0007] A unified modeling platform for industrial apps, the unified modeling platform comprising a system kernel and a system built-in plug-in module, wherein:

[0008] The system kernel includes a metamodel bootstrap module, a model data operation protocol module, a model data publishing module and a model data processing plug-in module;

[0009] The metamodel bootstrapping module is used to implement self-description of the metamodel;

[0010] The model data operation protocol module is used to provide data addition, modification or deletion services, and is also used to provide standard REST interface services;

[0011] The model data publishing module is used to publish the data operation as a message after completing the data operation;

[0012] The model data processing plug-in module is used to provide plug-in registration, deregistration and operation performance monitoring services;

[0013] The system built-in plug-in module is used to provide plug-in services according to the user's plug-in configuration request.

[0014] Optionally, the metamodel bootstrapping module includes a logical table metamodel and a logical field metamodel.

[0015] Optionally, the logical data types of the metamodel bootstrap module include part or all of integers, decimals, text, files, and Boolean data.

[0016] Optionally, the system built-in plug-in module includes a platform metadata plug-in, a data persistence plug-in, a physical model extension plug-in and a time series data modeling plug-in, wherein:

[0017] The platform metadata plug-in is used to define the metadata of the platform itself;

[0018] The data persistence plug-in is used to persist model data to various databases;

[0019] The object model extension plug-in is used to describe entities and the relationships between the entities;

[0020] The time series data modeling plug-in is used to add multivariate data information to time series data.

[0021] Optionally, the unified modeling platform also includes industry standard models.

[0022] Optionally, the unified modeling platform also includes factory customized models and plug-ins.

[0023] It can be seen from the above technical solutions that the present application discloses a unified modeling platform for industrial apps, including a system kernel and a system built-in plug-in module. The system kernel includes a metamodel bootstrap module, a model data operation protocol module, a model data publishing module and a model data processing plug-in module; the metamodel bootstrap module is used to realize the self-description of the model; the model data operation protocol module is used to provide data addition, modification or deletion services, and is also used to provide standard rest interface services; the model data publishing module is used to publish the data operation as a message after completing the data operation; the model data processing plug-in module is used to provide plug-in registration, deregistration and operation performance monitoring services; the system built-in plug-in module is used to provide plug-in services according to the user's plug-in configuration request;. This solution allows industrial app developers to easily carry out relational data modeling and object model modeling, and by building the relationship between these data, all factory data can be integrated.

[0024] By integrating all data, developers' development efficiency can be improved, duplication of work can be avoided, and learning costs can be reduced. Developers can more easily model the data of the entire factory, and efficiently extract, precipitate, and abstract industrial knowledge. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0026] Figure 1 A block diagram of a unified modeling platform for industrial apps according to an embodiment of the present application;

[0027] Figure 2 A block diagram of a unified modeling platform for another industrial app according to an embodiment of the present application;

[0028] Figure 3 A block diagram of a unified modeling platform for another industrial app according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0030] Example

[0031] Figure 1 A block diagram of a unified modeling platform for an industrial app according to an embodiment of the present application.

[0032] like Figure 1 As shown, the unified modeling platform provided in this embodiment is applied to an electronic device, which can be understood as a computer or server with data calculation and information processing. The unified modeling platform includes a system built-in plug-in module 10 and a system kernel 20. Among them, the system kernel of the present application includes a metamodel bootstrap module 21, a model data operation protocol module 22, a model data publishing module 23 and a model data processing plug-in module 24.

[0033] The metamodel bootstrap module is the foundation of the entire platform. This module is used to complete the self-description of the metamodel, so it does not need to rely on any other modules. The metamodel is a model about the model. For example, in the field of data modeling, the metamodel is a model that describes the data table. A set of modeling elements and rules for using these elements can be provided, and these elements and rules can be applied recursively to describe business models and metamodels in a unified way.

[0034] The metamodel provides two concepts, the logical table metamodel and the logical field metamodel. The logical table metamodel is used to describe the model body; the logical field metamodel is used to describe the model structure, and the model bootstrapping is completed through the following three logical tables.

[0035] a. Logical table metamodel:

[0036] name description logic_table Logical table metamodel logic_column Logical Field Metamodel logic_data_type Logical Data Type Metamodel

[0037] b. Logical field metamodel:

[0038] logic_table name logic_data_type description logic_table name string Logical table name logic_table description string Logical table description logic_column name string Logical field name logic_column description string Logical Field Description logic_column data_type string Logical Type logic_data_type name string Logical type name logic_data_type description string Logical type description physical_data_type name string Physical Type Name physical_data_type description string Physical Type Description

[0039] c. Logical data types of the metamodel:

[0040]

[0041]

[0042] The model data operation protocol module is used to define the standard REST interface for data addition, modification and deletion, and batch mixed operations. The data is transmitted in JSON format. The logical table in the interface routing is used as a resource. The platform implements the data operation protocol, and all data operations must be completed through this protocol. No other methods are provided.

[0043] The model data publishing module is used to publish the entire operation as a message after the platform has processed the data operation. It provides both asynchronous and synchronous methods for external monitoring of messages. The synchronous method requires waiting for the other party to process the message and confirm it before completing the operation. The asynchronous method does not block the current data operation. In order to ensure the stability of the platform, all external modules that require synchronous processing must meet performance requirements.

[0044] The model data processing plug-in module provides a plug-in system, which is built on the model data publishing module and provides a series of functions such as plug-in registration, deregistration, and operation performance monitoring. At the same time, this module also uses unified modeling capabilities to manage plug-in models.

[0045] The system kernel provides capabilities that are independent of the specific platform, but as an industrial app development platform, a set of platform standards needs to be defined. However, all capabilities related to the platform are completed through plug-ins, which greatly improves the universality and extensibility of the platform. Accordingly, the system built-in plug-in module in this application is used to provide plug-in services according to the user's plug-in configuration request, which specifically includes but is not limited to platform metadata plug-ins, data persistence plug-ins, physical model extension plug-ins, and time series data modeling plug-ins.

[0046] The platform metadata plugin is used to define the metadata of the platform itself, such as the platform version, the modules it contains, all the APIs provided by the system, and all the apps installed on the platform.

[0047] The data persistence plug-in is used to persist model data to various databases, so that the entire platform is decoupled from the specific database. The same data can even be persisted to different databases, such as relational databases and graph databases. This plug-in mechanism greatly improves the flexibility and universality of the system.

[0048] The object model extension plug-in is used to provide a richer description of entities and the relationships between entities during the object modeling process. For example, the platform can provide metamodels such as events and services by extending the metamodel, and provide the ability to define metadata such as attributes on instance data. This is a typical example of increasing platform capabilities by extending the metamodel.

[0049] Time series data has many unique features. For example, each time series data is a data stream. By extending the attribute metamodel, the time series data modeling plug-in can add more metadata information to the time series attributes, such as the unit of the attribute, the underlying sensor information, etc. By extending the metamodel instead of solidifying this capability into the system kernel, time series data modeling and relational data modeling can be integrated to provide a set of standard concepts and tools. At the same time, time series data and relational data can be connected to each other, establish relationships, and perceive each other, providing apps with richer data processing capabilities.

[0050] It can be seen from the above technical scheme that this embodiment provides a unified modeling platform for industrial apps, including a system kernel and a system built-in plug-in module. The system kernel includes a metamodel bootstrap module, a model data operation protocol module, a model data publishing module and a model data processing plug-in module; the metamodel bootstrap module is used to realize the self-description of the model; the model data operation protocol module is used to provide data addition, modification or deletion services, and is also used to provide standard rest interface services; the model data publishing module is used to publish the data operation as a message after completing the data operation; the model data processing plug-in module is used to provide plug-in registration, deregistration and operation performance monitoring services; the system built-in plug-in module is used to provide plug-in services according to the user's plug-in configuration request. This solution allows industrial app developers to easily carry out relational data modeling and object model modeling, and by building the relationship between these data, all factory data can be integrated.

[0051] By integrating all data, developers' development efficiency can be improved, duplication of work can be avoided, and learning costs can be reduced. Developers can more easily model the data of the entire factory, and efficiently extract, precipitate, and abstract industrial knowledge.

[0052] The following describes the use of the unified modeling platform through the process of app development and implementation:

[0053] Assume that a general app developer who develops apps based on the unified modeling platform of this application is refining the standard model of the cement industry. First, all models are created through the data operation protocol in the unified modeling platform. Taking the creation of a simple warehousing model as an example, the operation described in json is as follows:

[0054]

[0055]

[0056] Since this platform unifies data and metadata, app developers no longer need to call various metadata creation interfaces to create models, but only need to care about data operation protocols. This reduces the complexity of app development and improves the scalability of the model.

[0057] This platform packages the cement industry standard model into the app, and the creation of the cement industry standard model can be completed by installing the app during the implementation phase.

[0058] The app developers of a cement group conduct customized development based on the general cement industry standard model to adapt to the special needs of the group. For example, the group has a unified warehouse order number generation standard. The app developers can extend the model data type and add a warehouse order number data type. On the unified modeling platform, you can develop a plug-in that first adds a row of data to the data type metamodel: name: repo_number, description: warehouse order number type. Then process the published data operation message and fill the corresponding field of the data type repo_number with the generated warehouse code. Through this extension plug-in, all app developers do not need to care about the warehouse order number generation logic and can directly use this extended data type to improve the efficiency of app development. If combined with the visual app configuration platform, integrating this data type directly into the configuration can make low-code development more efficient.

[0059] In a specific cement plant under the cement group, on-site engineering implementation personnel can continue customized development based on the group's customized model to handle the special needs of the cement plant. For example, they can add some fields to the warehouse model. In the unified modeling platform, they can directly add fields to the logical field model through the data operation protocol.

[0060] Through the unified modeling platform, app developers can accumulate common industry models and knowledge at each stage, which can greatly improve the development efficiency of the entire app.

[0061] In addition, in a specific embodiment of the present application, the unified modeling platform also includes industry standard models and plug-ins 30, such as Figure 2 shown.

[0062] Based on the industry standard model, in the app development platform, each company can accumulate models in its own field, and the platform can also accumulate standard models of various industries, which can greatly improve the efficiency of modeling of the entire platform. Users only need to customize the standard model to quickly complete the modeling. The modeling flexibility provided by the present invention can make the accumulation of standard models more efficient.

[0063] In addition, in another specific embodiment of the present application, the unified modeling platform also includes a factory customization model and plug-in 40, such as Figure 3 shown.

[0064] After the app is developed, the corresponding model is implemented in a specific factory and customized according to the special conditions of the factory. The model scalability provided by the present invention can efficiently meet the needs of customized models.

[0065] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0066] It will be appreciated by those skilled in the art that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0067] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0068] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0069] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0070] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0071] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0072] The technical solution provided by the present invention is introduced in detail above. Specific examples are used in this article to illustrate the principle and implementation mode of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation mode and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A unified modeling platform for industrial apps, characterized in that: The unified modeling platform includes a system kernel and a system built-in plug-in module, wherein: The system kernel includes a metamodel bootstrap module, a model data operation protocol module, a model data publishing module and a model data processing plug-in module; The metamodel bootstrapping module is used to provide modeling elements and rules for using the modeling elements, and recursively apply the modeling elements and the rules to describe the metamodel using a unified method to achieve self-description of the metamodel; The model data operation protocol module is used to provide data addition, modification or deletion services, and is also used to provide standard REST interface services; The model data publishing module is used to publish the data operation as a message after completing the data operation; The model data processing plug-in module is used to provide plug-in registration, deregistration and operation performance monitoring services; The system built-in plug-in module is used to provide plug-in services according to the user's plug-in configuration request.

2. The unified modeling platform according to claim 1, characterized in that: The metamodel bootstrapping module includes a logic table metamodel and a logic field metamodel.

3. The unified modeling platform according to claim 2, characterized in that: The logical data types of the metamodel bootstrap module include some or all of integer, decimal, text, file and Boolean data.

4. The unified modeling platform according to claim 1, characterized in that: The system built-in plug-in modules include platform metadata plug-in, data persistence plug-in, physical model extension plug-in and time series data modeling plug-in, among which: The platform metadata plug-in is used to define the metadata of the platform itself; The data persistence plug-in is used to persist model data to various databases; The object model extension plug-in is used to describe entities and the relationships between the entities, and the entity includes at least one of an event metamodel, a service metamodel and attribute metadata; The time series data modeling plug-in is used to add multivariate data information to time series data.

5. The unified modeling platform according to any one of claims 1 to 4, characterized in that: The unified modeling platform also includes industry standard models.

6. The unified modeling platform according to claim 5, characterized in that: The unified modeling platform also includes factory customization models and plug-ins.

Images