MOM data processing device and method, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an MOM data processing device and method, electronic equipment and a storage medium. The MOM data processing device comprises a data integration module for acquiring multi-source heterogeneous data with different data formats and converting the multi-source heterogeneous data into standardized semantic data with a unified data format, the multi-source heterogeneous data comprising at least one of IT data and OT data; the service configuration module is used for acquiring an MOM service application demand, selecting a plurality of micro-service components associated with the MOM service application demand from a micro-service component library, and arranging the plurality of micro-service components to obtain an MOM service application, and each micro-service component is configured to execute micro-service based on the standardized semantic data; and the front-end configuration module is used for determining each visualization module corresponding to the MOM service application, and presenting each MOM service data processing result of the standardized semantic data processed by the MOM service application to each visualization module.

Description

MOM data processing device, method, electronic device and storage medium Technical Field

[0001] Embodiments of the present invention relate to the field of Internet technology, and in particular to a MOM data processing device, method, electronic device, and storage medium. Background Art

[0002] Manufacturing Operations Management (MOM) integrates most production processes to enhance quality management, advanced planning and scheduling, manufacturing execution systems, and R&D management. However, building MOM solutions for enterprises still presents many challenges and difficulties. For example, MOM requirements vary across industries, and even within the same industry, different business processes often require greater or lesser levels of customization.

[0003] Therefore, MOM solutions require high scalability and flexibility.

[0004] Summary of the Invention

[0005] In order to solve the above problems, embodiments of the present invention provide a MOM data processing device, method, electronic device and storage medium to at least partially solve the above problems.

[0006] According to a first aspect of an embodiment of the present invention, a MOM data processing device is provided, comprising: a data integration module for acquiring multi-source heterogeneous data having different data formats and converting the multi-source heterogeneous data into standardized semantic data having a unified data format, wherein the multi-source heterogeneous data includes at least one of IT data and OT data; a service configuration module for acquiring MOM service application requirements, selecting multiple microservice components associated with the MOM service application requirements from a microservice component library, and orchestrating the multiple microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on the standardized semantic data; and a front-end configuration module for determining respective visualization modules corresponding to the MOM service application and presenting the standardized semantic data to the respective visualization modules after the respective MOM service data processing results of the MOM service application.

[0007] In another implementation of the present invention, the data integration module includes a data connector framework configured with various connection interfaces, and the different connection interfaces are used to convert the formats of the multi-source heterogeneous data into the unified data format.

[0008] In another implementation of the present invention, the data integration module includes a metadata model for defining the unified data format, and the data integration module converts the multi-source heterogeneous data into the standardized semantic data through model parameters of the metadata model.

[0009] In another implementation of the present invention, the metadata model is further configured to: construct a knowledge graph of the standardized semantic data based on the data association relationship indicated by prior knowledge, and store the knowledge graph of the standardized semantic data in association with the standardized semantic data.

[0010] In another implementation of the present invention, the service configuration module analyzes the standardized semantic data through the MOM service application to obtain a data analysis result, and stores the data analysis result in association with the standardized semantic data.

[0011] In another implementation of the present invention, the service configuration module analyzes the standardized semantic data through a microservice component for cluster analysis to obtain a data analysis result, wherein the microservice component for cluster analysis is trained based on a neural network.

[0012] In another implementation of the present invention, the service configuration module is specifically used to: determine at least one of the component dependency, concurrency relationship, and priority relationship indicated by the MOM service application requirements, determine the microservice orchestration order, and orchestrate the multiple microservice components based on the microservice orchestration order.

[0013] In another implementation of the present invention, the front-end configuration module determines the orchestration order of each visualization module based on the microservice orchestration order, and orchestrates each visualization module based on the orchestration order of each visualization module, wherein each visualization module includes at least one of a user interface generation module and a user interface layout module.

[0014] A second aspect of an embodiment of the present invention provides a MOM data processing method, comprising: obtaining multi-source heterogeneous data having different data formats, and converting the multi-source heterogeneous data into standardized semantic data in a unified data format, wherein the multi-source heterogeneous data includes at least one of IT data and OT data; obtaining MOM service application requirements, selecting multiple microservice components associated with the MOM service application requirements from a microservice component library, and orchestrating the multiple microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on the standardized semantic data; determining each visualization module corresponding to the MOM service application, and presenting the standardized semantic data to each visualization module after the MOM service data processing results of the MOM service application.

[0015] According to a third aspect of an embodiment of the present invention, an electronic device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus, and the communication interface is used to communicate with multiple servers and expansion switches; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to the method described in the second aspect.

[0016] According to a fifth aspect of an embodiment of the present invention, a storage medium is provided, wherein the storage medium includes a stored program, wherein when the program is running, a device including the storage medium is controlled to execute the method according to the second aspect.

[0017] In the solution of the embodiment of the present invention, the data integration module can convert multi-source heterogeneous data into standardized semantic data in a unified data format, improving the circulation and interconnection between different data assets and reducing data barriers. In addition, the front-end configuration module can achieve flexibility and scalability in the display configuration of MOM service data through various visualization modules. In addition, the service configuration module can orchestrate the multiple microservice components to obtain a MOM service application. Through the loose coupling association between the various microservice components, the development and configuration of MOM solutions such as MOM service applications can be scalable and flexible. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The following drawings are only intended to illustrate and explain the present invention, and do not limit the scope of the present invention.

[0019] FIG1 is an architecture diagram of a MOM data processing system according to an embodiment of the present invention.

[0020] FIG2 is a schematic block diagram of a MOM data processing device according to another embodiment of the present invention.

[0021] FIG3 is a software architecture diagram of the MOM data processing device according to the embodiment of FIG2 .

[0022] FIG4 is a diagram showing the arrangement principle of the service configuration module in FIG2 .

[0023] FIG5 is a schematic diagram of the steps of a MOM data processing method according to another embodiment of the present invention.

[0024] FIG6 is a schematic structural diagram of an electronic device according to another embodiment of the present invention.

[0025] List of reference numerals:

[0026] 100: MOM data processing system; 10: IT system; 11: Industrial monitoring equipment; 12: Industrial controller; 13: Actuator; 14: Sensor; 15: Robot; 16: Communication equipment; 20: OT system; 21: Enterprise resource management application; 22: Production lifecycle management application; 23: Digital rights management application; 24: Supplier relationship management application; 25: Transportation management application; 26: Network management application; 30: MOM data processing device; 31: Service component orchestration module; 32: Data integration module;

[0027] 210: Data integration module; 211: OT system connection interface; 212: IT system connection interface; 213: Data connector framework; 214: Knowledge graph; 215: Data model resource library; 216: Semantic data interface;

[0028] 220: Service configuration module; 221: General service components; 222: Core service components; 223: Personalized service components; 224: Microservice orchestration workflow; 225: Microservice orchestration process; 226: Microservice component library;

[0029] 230: front-end configuration module; 231: user interface generation module; 232: user interface layout module; 233: visualization module resource library;

[0030] 40: Visual orchestration module; 41-44: Node; 410-440: Functional block;

[0031] S510: Acquire multi-source heterogeneous data in different data formats, and convert the multi-source heterogeneous data into standardized semantic data in a unified data format, where the multi-source heterogeneous data includes at least one of IT data and OT data;

[0032] S520: Obtaining a MOM service application requirement, selecting multiple microservice components associated with the MOM service application requirement from a microservice component library, and orchestrating the multiple microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on standardized semantic data;

[0033] S530: Determine each visualization module corresponding to the MOM service application, and present the standardized semantic data to each visualization module after the MOM service data processing results of the MOM service application;

[0034] 600: electronic device; 602: processor; 604: communication interface; 606: memory; 608: communication bus; 610: program. DETAILED DESCRIPTION

[0035] In order to have a clearer understanding of the technical features, purposes and effects of the embodiments of the present invention, specific implementation methods of the embodiments of the present invention are now described with reference to the accompanying drawings.

[0036] Building MOM solutions for enterprises still presents many challenges and difficulties. For example, MOM requirements vary across industries, and even within the same industry, different business processes often require greater or lesser customization. Providing a highly maintainable MOM architecture with traditional technologies presents numerous challenges. Furthermore, standardized capabilities struggle to meet the specific requirements of factories, production lines, and processes. Domain expertise is only understood by business experts, making it difficult to develop reusable practices. Furthermore, the communication costs from MOM management requirements to implementation are high. Implementation consultants often lack a deep understanding of the business, and presenting requirements to the team can lead to misunderstandings.

[0037] In summary, the development and configuration of MOM solutions have poor scalability and flexibility. Therefore, the embodiments of the present invention provide a series of solutions to solve the above problems.

[0038] 1 shows a MOM data processing system 100 according to an embodiment of the present invention. The MOM data processing system 100 includes an information technology (IT) system 10 , an operations technology (OT) system 20 , and a MOM data processing device 30 .

[0039] The IT system 10 and the MOM data processing device 30 may communicate with each other via a bus. The OT system 20 and the MOM data processing device 30 may communicate with each other via a messaging protocol such as HTTP or MQTT.

[0040] Furthermore, IT system 10 includes, but is not limited to, industrial monitoring equipment 11, industrial controllers 12, actuators 13, sensors 14, robots 15, and communication equipment 16. OT system 20 includes, but is not limited to, enterprise resource management applications 21, production lifecycle management applications 22, digital rights management applications 23, supplier relationship management applications 24, transportation management applications 25, and network management applications 26. MOM data processing device 30 includes, but is not limited to, a service component orchestration module 31 and a data integration module 32.

[0041] Through the data layer integration capabilities of the data integration module 32, external OT systems and IT systems can be integrated into the MOM data processing device 30. The service component orchestration module 31 orchestrates various business microservices to form business processes, truly integrating data and business. Furthermore, data models and business processes can be defined and managed using visual, low-code tools, providing a highly maintainable foundation for this modular MOM data processing device 30. Furthermore, the architecture of the MOM data processing device in this embodiment of the present invention addresses the poor scalability and flexibility of MOM solution development and configuration by designing different components.

[0042] FIG2 shows a MOM data processing device according to another embodiment of the present invention. The MOM data processing device of FIG2 includes:

[0043] Data integration module 210 acquires multi-source heterogeneous data in different data formats and converts this data into standardized semantic data in a unified data format. The multi-source heterogeneous data includes at least one of IT data and OT data. It should be understood that data integration module 210 is an example of data integration module 32 described above.

[0044] It should be understood that the data integration module 210 connects to various data sources, extracts data from them, and converts data formats. It can recognize and process different data formats, such as structured data, semi-structured data, and unstructured data. By using appropriate data conversion and mapping technologies, module 210 converts these data formats into unified, standardized semantic data. For example, the standardized semantic data can be stored in the form of reusable data templates, such as business data templates or industry data templates. These reusable data templates can be stored in a semantic template library for subsequent processing and analysis.

[0045] Multi-source heterogeneous data is derived in part from industrial data based on industry standards, such as ISA95, IEC61970, IEC61968, and IEC62264. It also stems from the accumulation of industry data models during project implementation. Industry standards are the foundation of data modeling. In the early stages of a solution, customer data models can be customized and configured according to these standards based on the data availability within the business domain. Once sufficient data models within the same industry have been accumulated, they can be formalized and stored in a resource library for reuse in other projects. Furthermore, each ontology model template can be versioned, allowing users to select the template version appropriate for their business domain.

[0046] Service configuration module 220 obtains MOM service application requirements, selects multiple microservice components associated with the MOM service application requirements from a microservice component library, and orchestrates the multiple microservice components to obtain a MOM service application. Each microservice component is configured to execute a microservice based on standardized semantic data. Service configuration module 220 is an example of the aforementioned service component orchestration module 31.

[0047] It should be understood that the service configuration module 220 selects appropriate microservice components from the microservice component library based on the requirements of the MOM service application. Various reusable microservice components can be stored as storage objects in the microservice component library. These microservice components can provide various functions, such as data processing, data analysis, and data storage. By orchestrating these microservice components, a complete MOM service application can be formed. Each microservice component is configured to execute microservices based on standardized semantic data to ensure data consistency and availability.

[0048] The front-end configuration module 230 determines each visualization module corresponding to the MOM service application, and presents the standardized semantic data to each visualization module after being processed by each MOM service data of the MOM service application.

[0049] It should be understood that the front-end configuration module 230 determines the required visualization modules, such as charts, reports, and dashboards, based on the requirements of the MOM service application. The visualization modules are combined into reusable forms, which can be formed into form templates. The visualization modules and form templates can be stored as storage objects in the front-end component repository for reuse by the front-end configuration module 230. The front-end configuration module 230 transmits the standardized semantic data processed by the MOM service application to these visualization modules, allowing users to intuitively understand the data processing results through visualization. These visualization modules can provide interactivity and real-time updates, enabling users to deeply analyze data and make appropriate decisions.

[0050] In the solution of the embodiment of the present invention, the data integration module can convert multi-source heterogeneous data into standardized semantic data in a unified data format, improving the circulation and interconnection between different data assets and reducing data barriers. In addition, the front-end configuration module can achieve flexibility and scalability in the display configuration of MOM service data through various visualization modules. In addition, the service configuration module can orchestrate the multiple microservice components to obtain a MOM service application. Through the loose coupling association between the various microservice components, the development and configuration of MOM solutions such as MOM service applications can be scalable and flexible.

[0051] Overall, the design and functionality of the aforementioned modules aim to provide a comprehensive solution for processing multi-source heterogeneous data, configuring service components, and displaying data processing results. Through an integrated process of data integration, service configuration, and front-end presentation, efficient, accurate, and visual data processing and analysis can be achieved, meeting the requirements of MOM service applications. The innovation of these modules lies in their integration of data integration, service configuration, and front-end presentation capabilities, providing a unified approach to processing multi-source heterogeneous data and configuring service components. The specific implementation of these modules can include various algorithms, data structures, data transformations, low-code visual configuration, and corresponding software and hardware implementations.

[0052] Furthermore, as shown in FIG3 , the data integration module 210 includes but is not limited to: an OT system connection interface 211 , an IT system connection interface 212 , a data connector framework 213 , a knowledge graph 214 , a data model resource library 215 , and a semantic data interface 216 .

[0053] Without loss of generality, the data integration module includes a data connector framework configured with various connection interfaces. Different connection interfaces are used to convert the formats of multi-source heterogeneous data into a unified data format, thereby using indirect software configuration to improve the circulation and interconnection between different data assets and reduce data barriers.

[0054] In other words, the Data Connector Framework provides a unified data integration framework that can integrate various systems, such as IT and OT systems, in a configurable manner, supporting different drivers and protocols within each system. Furthermore, custom plug-ins can be created to support new connection drivers. As a component, the Data Connector Framework provides capabilities such as data connection, hot and cold data differentiation, disconnection and reconnection, transaction compensation, and connection pool optimization to ensure data reliability and stability.

[0055] Furthermore, the data integration module includes a metadata model for defining a unified data format. Using the model parameters of the metadata model, the module converts multi-source heterogeneous data into standardized semantic data, thereby enhancing the value of standardized semantic data through the cloud data model. The model parameters of the metadata model enable the establishment of a mapping connection between multi-source heterogeneous data and standardized semantic data through a low-code paradigm.

[0056] Furthermore, the metadata model is configured to construct a knowledge graph of standardized semantic data based on data associations indicated by prior knowledge, and to associate and store the knowledge graph with the standardized semantic data. This allows the knowledge graph of standardized semantic data to provide higher data value for MOM service applications. In other words, standard models for various industries can be established based on prior knowledge, such as industry standards, and knowledge graphs can be customized based on these models to provide access interfaces to semantic and virtual data for application development and configuration.

[0057] 3 , service configuration module 220 includes, but is not limited to, a shared service component 221, a core service component 222, a personalized service component 223, a microservice orchestration workflow 224, a microservice orchestration process 225, and a microservice component library 226. It should be understood that the aforementioned service components are examples of microservice components according to embodiments of the present invention.

[0058] Specifically, the common service component 221 refers to many service applications that can call some common business functions. Therefore, these functions are abstracted and defined as common business services, such as tag management services, code management services, document management services, etc.

[0059] Furthermore, based on the MOM's business scope, core businesses are divided into several business areas, such as scheduling management, production execution management, materials management, quality management, equipment management, production resource management, and process management. Core service components 222 refer to core business microservices defined in each area to manage corresponding sub-businesses. To improve reusability and reduce custom development costs, these business service components assume small business responsibilities and are scheduled and coordinated by visual business process orchestration.

[0060] In summary, the service configuration module 220 can use a microservices governance framework to address service governance and communication issues within a microservices architecture. The microservices governance framework provides multiple microservices components, including service registration and discovery, load balancing, a configuration center, service monitoring, log management, and an API gateway, to meet service governance requirements. The microservices governance framework is designed to be highly extensible, allowing users to easily implement various custom logic for functions such as traffic interception and location selection.

[0061] Without loss of generality, the service configuration module analyzes the standardized semantic data through the MOM service application to obtain data analysis results, and stores the data analysis results in association with the standardized semantic data. For example, the data analysis results are stored in association with the standardized semantic data in the data model resource library 215. Therefore, the storage of the data analysis results in association with the standardized semantic data increases the value of the standardized semantic data, and can provide higher data value for MOM service applications developed and configured based on the standardized semantic data.

[0062] Furthermore, the service configuration module analyzes the standardized semantic data using a microservice component for cluster analysis, generating data analysis results. This microservice component is trained using a neural network. Because cluster analysis effectively analyzes and mines the potential value of data, the use of neural networks as a microservice component for cluster analysis further enhances data analysis and mining capabilities, offering easy iterative updates and flexible deployment.

[0063] In other examples, the service configuration module is specifically configured to determine at least one of component dependencies, concurrency relationships, and priority relationships indicated by MOM service application requirements, determine a microservice orchestration order, and orchestrate multiple microservice components based on the microservice orchestration order. For example, the component dependencies, concurrency relationships, and priority relationships can be stored as objects in microservice orchestration workflow 224, and a matching process can be selected in microservice orchestration process 225 to execute the objects in microservice orchestration workflow 224.

[0064] In the service configuration module, a series of tools are provided through visual modeling tools to manage warehouses, ontology models, knowledge graph models, and database schema mapping. These tools include, but are not limited to: ontology model management tools, data modeling tools, database schema management tools, and data model authorization tools.

[0065] Specifically, the ontology model management tool is used to manage the industrial data model repository and can create a knowledge graph based on one of the ontology models. This is achieved by providing a data modeling tool with a graphical user interface. The database schema management tool creates the database schema based on the entities defined in the knowledge graph and provides version management for the data model to support model expansion. The data model authorization tool establishes the permission attributes of the data model and assigns ownership of the data model to specific microservices. For example, other microservices can only read the data in the data model but cannot modify it. In addition, the data model can be versioned, and each microservice can specify a specific data model version.

[0066] Figure 4 is a schematic diagram of the orchestration principle of the service configuration module of Figure 2. Exemplarily, a function block (FB) is the basic unit of business orchestration and can be composed of one or more microservice components. For example, a visual orchestration module 40 is an example of a service configuration module. Taking function blocks 410-440 as an example, the visual orchestration module 40 includes nodes 41, 42, 43, and 44, and the order between each node 41-44 reflects the microservice orchestration workflow. The nodes correspond to function blocks. Users can create customized business processes and form process templates by visually arranging these function blocks 410-440. Each function block contains custom code and interface calls to microservices. Both function blocks and process templates can be persisted in the function block repository to achieve reusability and scalability.

[0067] Furthermore, the front-end configuration module determines the arrangement order of each visualization module based on the microservices arrangement order, and arranges each visualization module based on the arrangement order of each visualization module. Determining the arrangement order of each visualization module based on the microservices arrangement order reflects the corresponding relationship between the client and the server, thereby improving the development and configuration efficiency of the front-end of the MOM service application. In addition, each visualization module includes at least one of a user interface generation module 231 and a user interface layout module 232. Further, as shown in Figure 3, the front-end configuration module 230 includes but is not limited to: a user interface generation module 231, a user interface layout module 232, and a visualization module resource library 233.

[0068] The user interface generation module 231 includes UI templates and form templates. UI templates can constitute the visual elements or modules of the user interface of a website or application. These components are designed to be reusable and modular, allowing developers to build complex user interfaces by assembling them together. Form templates are UI tools used to create form templates in web applications. This tool typically provides a user interface for defining the structure and layout of the form and generates corresponding code that can be easily integrated into the application. The generated code may also include JavaScript code to handle form validation and submission. This can save developers time and effort by eliminating the need to write complex form validation and submission logic from scratch.

[0069] The user interface layout module 232 can be a front-end UI component HTML generation tool used to create the HTML and CSS code for UI components in a web application. The generated code can not only allow UI components to be published based on NPM, but can also include JavaScript code to handle UI component interactions and behaviors. This can save developers time and effort by eliminating the need to write complex UI component code from scratch. Using a UI component HTML generation tool can also ensure the consistency and maintainability of UI components across different pages and sections of the application, as the generated code will follow a consistent structure and style.

[0070] The Visual Module Repository 233 is used to store reusable code components that can be used to build front-end web applications. These components may include UI widgets, form elements, navigation menus, and other visual or interactive elements. Similar to NPM (Node Package Manager) component repositories, it allows developers to publish and share their own components, while also discovering and using components created by others.

[0071] The MOM data processing method according to another embodiment of the present invention will be described in detail below with reference to FIG5 . The MOM data processing method of FIG5 includes:

[0072] S510: Acquire multi-source heterogeneous data in different data formats, and convert the multi-source heterogeneous data into standardized semantic data in a unified data format, where the multi-source heterogeneous data includes at least one of IT data and OT data.

[0073] S520: Obtaining a MOM service application requirement, selecting multiple microservice components associated with the MOM service application requirement from a microservice component library, and orchestrating the multiple microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on standardized semantic data;

[0074] S530: Determine each visualization module corresponding to the MOM service application, and present the standardized semantic data to each visualization module after the MOM service data processing results of the MOM service application.

[0075] In the solution of the embodiment of the present invention, the data integration module can convert multi-source heterogeneous data into standardized semantic data in a unified data format, improving the circulation and interconnection between different data assets and reducing data barriers. In addition, the front-end configuration module can achieve flexibility and scalability in the display configuration of MOM service data through various visualization modules. In addition, the service configuration module can orchestrate the multiple microservice components to obtain a MOM service application. Through the loose coupling association between the various microservice components, the development and configuration of MOM solutions such as MOM service applications can be scalable and flexible.

[0076] In other examples, converting multi-source heterogeneous data into standardized semantic data in a unified data format includes: converting the formats of the multi-source heterogeneous data into the unified data format through various connection interfaces configured by a data connector framework.

[0077] In other examples, the formats of the multi-source heterogeneous data are converted into the unified data format through the various connection interfaces configured by the data connector framework, including: converting the multi-source heterogeneous data into the standardized semantic data through model parameters of the metadata model used to define the unified data format, and the various connection interfaces configured by the data connector framework are used to convert data in different data formats into the unified data format.

[0078] In other examples, the MOM data processing method further includes: constructing a knowledge graph of the standardized semantic data based on the data association relationship indicated by prior knowledge, and storing the knowledge graph of the standardized semantic data in association with the standardized semantic data.

[0079] In other examples, the MOM data processing method further includes: analyzing the standardized semantic data through the MOM service application to obtain a data analysis result, and storing the data analysis result in association with the standardized semantic data.

[0080] In other examples, the standardized semantic data is analyzed through the MOM service application, including: analyzing the standardized semantic data through a microservice component for cluster analysis to obtain data analysis results, wherein the microservice component for cluster analysis is trained based on a neural network and deployed in the MOM service application.

[0081] In other examples, orchestrating multiple microservice components to obtain a MOM service application includes: determining at least one of component dependencies, concurrency relationships, and priority relationships indicated by MOM service application requirements, determining a microservice orchestration order, and orchestrating the multiple microservice components based on the microservice orchestration order to obtain the MOM service application.

[0082] In other examples, presenting the standardized semantic data after the results of MOM service data processing by the MOM service application to the respective visualization modules includes: determining the orchestration order of the respective visualization modules based on the microservice orchestration order, and presenting the standardized semantic data after the results of MOM service data processing by the MOM service application to the respective visualization modules based on the orchestration order of the respective visualization modules, wherein each visualization module includes at least one of a user interface generation module and a user interface layout module.

[0083] Another embodiment of the present invention provides an electronic device. FIG6 is a schematic diagram of the structure of an electronic device 600 provided by an embodiment of the present invention. The electronic device 600 may include: a processor 602 for executing a program 610, a communications interface 604, a memory 606, and a communication bus 608.

[0084] The processor, the communication interface, and the memory communicate with each other via a communication bus.

[0085] The communication interface is used to communicate with the server via a communication bus.

[0086] The processor is used to execute the program, and specifically can execute the relevant steps in the above method embodiment.

[0087] Specifically, the program may include program codes including computer operation instructions.

[0088] The processor may be a CPU, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs, or different types of processors, such as one or more CPUs and one or more ASICs.

[0089] Memory is used to store programs. The memory may include high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk storage.

[0090] The program may include multiple computer instructions, and the program may specifically enable the processor to execute the following through the multiple computer instructions: obtaining multi-source heterogeneous data with different data formats, and converting the multi-source heterogeneous data into standardized semantic data in a unified data format, wherein the multi-source heterogeneous data includes at least one of IT data and OT data; obtaining MOM service application requirements, selecting multiple microservice components associated with the MOM service application requirements from a microservice component library, and orchestrating the multiple microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on the standardized semantic data; determining each visualization module corresponding to the MOM service application, and presenting the standardized semantic data to each visualization module after the MOM service data processing results of the MOM service application.

[0091] Another embodiment of the present invention provides a storage medium, wherein the storage medium includes a stored program, wherein when the program is run, a device including the storage medium is controlled to execute the method described in any embodiment of the present invention.

[0092] It should be noted that the computer storage medium of the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. Computer-readable media may, for example, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage medium, a magnetic storage medium, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present invention, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. This propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program configured for use by or in conjunction with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, or any suitable combination thereof.

[0093] It should be understood that although the present invention is described according to various embodiments, not every embodiment contains only one independent technical solution. This narrative method of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation methods that can be understood by those skilled in the art.

[0094] The above is only an illustrative embodiment of the present invention and is not intended to limit the scope of the present invention. Any equivalent changes, modifications, and combinations made by any person skilled in the art without departing from the concept and principle of the present invention should fall within the scope of protection of the present invention.

Claims

1. A MOM data processing system, comprising: A data integration module (210) acquires multi-source heterogeneous data in different data formats and converts the multi-source heterogeneous data into standardized semantic data in a unified data format, wherein the multi-source heterogeneous data includes at least one of IT data and OT data; A service configuration module (220) obtains a MOM service application requirement, selects a plurality of microservice components associated with the MOM service application requirement from a microservice component library, and arranges the plurality of microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on the standardized semantic data; The front-end configuration module (230) determines each visualization module corresponding to the MOM service application, and presents the standardized semantic data to each visualization module after being processed by each MOM service data of the MOM service application.

2. The system according to claim 1, wherein: The data integration module includes a data connector framework configured with various connection interfaces, and the different connection interfaces are used to convert the formats of the multi-source heterogeneous data into the unified data format.

3. The system according to claim 2, wherein: The data integration module includes a metadata model for defining the unified data format, and the data integration module converts the multi-source heterogeneous data into the standardized semantic data through model parameters of the metadata model.

4. The system according to claim 3, wherein: The metadata model is also configured to: construct a knowledge graph of the standardized semantic data based on the data association relationship indicated by prior knowledge, and store the knowledge graph of the standardized semantic data in association with the standardized semantic data.

5. The system according to claim 1, wherein: The service configuration module analyzes the standardized semantic data through the MOM service application to obtain a data analysis result, and stores the data analysis result in association with the standardized semantic data.

6. The system according to claim 1, wherein: The service configuration module is specifically used to: determine at least one of the component dependency, concurrency relationship, and priority relationship indicated by the MOM service application requirement, determine the microservice orchestration order, and orchestrate the multiple microservice components based on the microservice orchestration order.

7. The system according to claim 6, wherein: The front-end configuration module determines an orchestration order of each visualization module based on the microservice orchestration order, and orchestrates each visualization module based on the orchestration order of each visualization module, wherein each visualization module includes at least one of a user interface generation module and a user interface layout module.

8. A MOM data processing method, characterized in that: include: Acquire multi-source heterogeneous data having different data formats, and convert the multi-source heterogeneous data into standardized semantic data in a unified data format, wherein the multi-source heterogeneous data includes at least one of IT data and OT data (S510); Obtaining a MOM service application requirement, selecting a plurality of microservice components associated with the MOM service application requirement from a microservice component library, and arranging the plurality of microservice components to obtain a MOM service application, wherein each microservice component is configured to execute a microservice based on the standardized semantic data (S520); Determine each visualization module corresponding to the MOM service application, and present the standardized semantic data to each visualization module after being processed by each MOM service data of the MOM service application (S530).

9. An electronic device, comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus, and the communication interface is used to communicate with multiple servers and expansion switches; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the method according to claim 8.

10. A computer storage medium having a computer program stored thereon, which implements the method according to claim 8 when the program is executed by a processor.

Images