Method and apparatus for constructing information model of process control system, and storage medium

Abstract

A method and apparatus for constructing an information model of a process control system, and a storage medium. The method comprises: acquiring system structure data and system application data of a process control system, wherein the system structure data is used for representing structured data of the process control system, and the system application data is used for representing data generated by the process control system in an actual application scenario (S102); on the basis of an information model framework, creating an information model namespace of the process control system, wherein the information model framework is used for unifying data representations between different devices (S104); and on the basis of the namespace, performing conversion on the system structure data and the system application data, so as to obtain an information model of the process control system (S106).

Description

Method, device and storage medium for constructing information model of process control system

[0001] Cross-reference

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 28, 2023, with application number 202311848436.1, and entitled “Information model construction method, device and storage medium for process control system”, all contents of which are incorporated by reference into this application. Technical Field

[0003] The present invention relates to the field of industrial automation, and in particular to a method, device and storage medium for constructing an information model of a process control system. Background Art

[0004] Enabling data exchange and information sharing from the process control layer to the manufacturing execution system layer or business management layer is an important link in realizing the integration of industrial automation and informatization and meeting the needs of enterprise management for digital transformation. However, due to the many differences in protocols and standards between different devices and manufacturers, there are problems with the openness of control system data and semantics.

[0005] To solve the problem of open control system data and semantics, the OPCDA / AE (Ole for Process Control Data Access / Alarms and Events) protocol can be used to enable data exchange between automation equipment from different manufacturers. However, this protocol can only open real-time data or alarms and cannot open more process control system information. The MQTT (Message Queuing Telemetry Transport) protocol can also be used for data transmission between devices. Although it can transmit any type of data, it is only oriented towards a single type of process control system and does not have the universality of the process control system domain model and semantics. Therefore, how multiple types of process control systems from different manufacturers and different devices can exchange data with upper-level systems and achieve the universality of the process control system domain model and semantics remains a problem.

[0006] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0007] Embodiments of the present invention provide a method, device, and storage medium for constructing an information model of a process control system, so as to at least solve the technical problem that due to the differences in protocols and standards between different devices and manufacturers, multiple types of process control systems from different manufacturers and different devices have poor universality.

[0008] According to one aspect of an embodiment of the present invention, a method for constructing an information model of a process control system is provided, comprising: acquiring system structure data and system application data of the process control system, wherein the system structure data is used to represent structured data of the process control system, and the system application data is used to represent data generated by the process control system in actual application scenarios; creating an information model namespace of the process control system based on an information model framework, wherein the information model framework is used to unify data representation between different devices; and transforming the system structure data and the system application data based on the namespace to obtain an information model of the process control system.

[0009] In some embodiments of the present application, obtaining system structure data of a process control system includes: obtaining multiple system objects of the process control system and the control logic of the process control system; extracting attribute information and variable information of the multiple system objects and the association relationship between the multiple system objects; and generating system structure data based on the attribute information, variable information, association relationship and control logic.

[0010] In some embodiments of the present application, obtaining system application data of a process control system includes: obtaining application scenarios, application instances, and application processes of the process control system; and generating system application data based on the application scenarios, application instances, and application processes.

[0011] In some embodiments of the present application, an information model namespace of a process control system is created based on an information model framework, including: determining a control station type, a controller type, and a communication module type of the process control system based on the information model framework, wherein the control station type includes a control loop of the process control system; determining a control system hardware type of the process control system based on the control station type, the controller type, and the communication module type; determining a control component type of the process control system based on the control loop type of the control loop; and creating an information model namespace based on the control system hardware type and the control component type.

[0012] In some embodiments of the present application, the method also includes: compiling the information model based on the information model standard of the information model framework to obtain a model class library of the information model; instantiating the model class library according to multiple devices corresponding to the process control system to obtain instantiation objects of multiple devices, wherein the multiple devices are used to represent devices connected to the process control system; aggregating the instantiation objects of multiple devices to obtain device information models of multiple devices.

[0013] In some embodiments of the present application, instantiated objects of multiple devices are aggregated to obtain device information models of the multiple devices, including: obtaining device namespaces of the multiple devices; encoding the instantiated objects based on the device namespaces and the running nodes of the multiple devices to obtain identification information of the instantiated objects; and aggregating the instantiated objects based on the identification information to obtain a device information model.

[0014] In some embodiments of the present application, an instantiated object is encoded based on a device namespace and running nodes of multiple devices to obtain identification information of the instantiated object, including: obtaining the node type of the running node; if the node type is used to indicate that the running node is in automatic allocation mode, the instantiated object is encoded based on the device namespace and the node name of the running node to obtain identification information, wherein the automatic allocation mode is used to indicate a mode of automatically allocating instantiated objects to the running node according to the running status of multiple devices; if the node type is used to indicate that the running node is in fixed mode, the instantiated object is encoded based on the node name of the running node to obtain identification information, wherein the fixed mode is used to indicate a mode in which the instantiated object of the running node is fixedly set.

[0015] According to another aspect of an embodiment of the present invention, an information model construction device for a process control system is also provided, including: an acquisition module, configured to acquire system structure data and system application data of the process control system, wherein the system structure data is configured to represent structured data of the process control system, and the system application data is configured to represent data generated by the process control system in an actual application scenario; a creation module, configured to create an information model namespace for the process control system based on an information model framework, wherein the information model framework is configured to unify data representations between different devices; and a conversion module, configured to convert the system structure data and system application data based on the namespace to obtain an information model of the process control system.

[0016] According to a third aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, the computer-readable storage medium including a stored program, wherein when the program is running, the information model construction method of the process control system is controlled in the processor of the device.

[0017] According to the fourth aspect of an embodiment of the present invention, an electronic device is also provided, comprising: one or more processors; a storage device configured to store one or more programs; when the one or more programs are executed by one or more processors, the one or more processors execute the above-mentioned information model construction method of the process control system.

[0018] In an embodiment of the present invention, a method is adopted in which system structure data and system application data of a process control system are acquired, wherein the system structure data is used to represent structured data of the process control system, and the system application data is used to represent data generated by the process control system in actual application scenarios; an information model namespace of the process control system is created based on an information model framework, wherein the information model framework is used to unify data representation between different devices; and the system structure data and system application data are converted based on the namespace to obtain an information model of the process control system. By acquiring the system structure data and system application data of the process control system, creating an information model namespace of the process control system based on the information model framework, and converting the system structure data and system application data based on the namespace, the purpose of constructing a universal information model of the process control system is achieved, thereby achieving the technical effect of shielding the differences in many protocols and standards between different devices and manufacturers, and improving the universality of multiple types of process control systems from different manufacturers and different devices, thereby solving the technical problem of poor universality of multiple types of process control systems from different manufacturers and different devices due to the differences in many protocols and standards between different devices and manufacturers. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0020] FIG1 is a flow chart of a method for constructing an information model of a process control system according to an embodiment of the present invention;

[0021] FIG2 is a schematic diagram of an example of an optional process control system information model according to an embodiment of the present invention;

[0022] 3 is an overall flow chart of establishing an optional process control system information model according to an embodiment of the present invention;

[0023] FIG4 is a flow chart of modeling an optional process control system information model according to an embodiment of the present invention;

[0024] FIG5 is a schematic diagram of the overall structure of an optional process control system information model according to an embodiment of the present invention;

[0025] FIG6 is a schematic diagram of an apparatus for constructing an information model of a process control system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] Example 1

[0029] According to an embodiment of the present invention, an embodiment of a method for constructing an information model of a process control system is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0030] FIG1 is a flow chart of a method for constructing an information model of a process control system according to an embodiment of the present invention. As shown in FIG1 , the method includes the following steps:

[0031] Step S102 : acquiring system structure data and system application data of the process control system, wherein the system structure data is used to represent structured data of the process control system, and the system application data is used to represent data generated by the process control system in actual application scenarios.

[0032] The process control system mentioned in the above steps is an automated system used to monitor, control, and optimize industrial processes. It is usually composed of sensors, actuators, controllers, and human-machine interfaces. Process control systems are widely used in various industries, including but not limited to chemical, petroleum, manufacturing, and energy, to improve production efficiency, quality, and safety. System structure data is data used to represent concepts, relationships, attributes, and events in process control systems. It is data from the provider's perspective. System application data is used to represent data related to business boundaries, use cases, and use case processes generated by users when using process control systems. It is data from the user's perspective. Structured data refers to data organized according to certain rules and formats to facilitate data storage, processing, and analysis.

[0033] In one optional embodiment, the concepts, relationships, attributes, and events in the process control system are first analyzed and abstracted from the provider's perspective, and the relevant data is structured to obtain system structure data. Then, from the user's perspective, the user's business boundaries, use cases, and use case flows when using the process control system are described, and this data is summarized and processed to obtain system application data. Taking the user's use cases and use processes into full consideration during the information modeling process can effectively improve the user experience and efficiency of the final model.

[0034] Step S104 : creating an information model namespace of the process control system based on an information model framework, wherein the information model framework is used to unify data representations between different devices.

[0035] The information model namespace described in the preceding steps is used to standardize the naming used in different process control systems and serves as the foundation for open data and semantics in process control systems. The information model framework is a standardized framework for defining and describing data models in industrial automation systems, providing a unified approach to representing, exchanging, and interpreting data across different vendors, devices, and systems. It provides a basic type system that allows users to define and customize their own data models to meet specific application scenarios.

[0036] In an optional embodiment, the information model framework is first determined. A suitable information model framework can be selected based on specific application scenarios and requirements. The information model framework can be a cross-platform communication architecture OPC UA (OLE for Process Control Unified Architecture) that enables seamless data exchange and integration between different devices, systems, and applications. Alternatively, the standardized communication protocol OPC XML-DA (OLE for Process Control XML-Data Access) based on XML (Extensible Markup Language) used to transmit data in industrial automation systems can be selected. Then, based on the information model framework, an information model namespace is constructed to uniformly represent data between different devices. The information model namespace can include hardware subtypes of the process control system, static attributes, and real-time dynamically changing variables, but is not limited thereto.

[0037] Step S106 : transforming the system structure data and the system application data based on the namespace to obtain an information model of the process control system.

[0038] In the above steps, the information model defines how to represent and exchange data in a given domain, as well as the structure and semantics between data. It is used to describe and organize the abstract representation of data, entities, attributes and the relationships between them in a specific domain, and can realize the openness of data and semantics in process control systems.

[0039] In an alternative embodiment, the data types, variable types, object types, object relationships, and alarm event types of the process control system are first defined based on the namespace and the acquired system structure data and system application data. These data are then stored in an information framework model node file. The information framework model node file is then converted into an information model for the process control system by combining the abstracted system structure data, system application data, and the selected information model framework.

[0040] In an embodiment of the present invention, a method is adopted in which system structure data and system application data of a process control system are acquired, wherein the system structure data is used to represent structured data of the process control system, and the system application data is used to represent data generated by the process control system in actual application scenarios; an information model namespace of the process control system is created based on an information model framework, wherein the information model framework is used to unify data representation between different devices; and the system structure data and system application data are transformed based on the namespace to obtain an information model of the process control system. By acquiring the system structure data and system application data of the process control system, creating an information model namespace of the process control system based on the information model framework, and transforming the system structure data and system application data based on the namespace, the purpose of constructing a universal information model of the process control system is achieved, thereby achieving the technical effect that multiple types of process control systems from different manufacturers and different devices can realize data openness and semantic openness to the upper-level system, thereby solving the technical problem that multiple types of process control systems from different manufacturers and different devices have poor universality due to many differences in protocols and standards between different devices and manufacturers.

[0041] In some embodiments of the present application, obtaining system structure data of a process control system includes: obtaining multiple system objects of the process control system and the control logic of the process control system; extracting attribute information and variable information of the multiple system objects and the association relationship between the multiple system objects; and generating system structure data based on the attribute information, variable information, association relationship and control logic.

[0042] The system objects in the above steps refer to the various entities managed and controlled in the process control system. They can be specific entities or abstract concepts, including but not limited to hardware and software structures, operating status, diagnostic status, and system alarms. Control logic is used to characterize the control strategy in the process control system and can be applied to a series of control components in the process control system. The control components include but are not limited to function blocks, control loops, and process variables. Attribute information is used to characterize the characteristics of system objects. Variable information is related information used to describe the variables of system objects. Association relationships are used to characterize the connections between different system objects. System structure data is data organized according to certain rules and formats to describe the process control system.

[0043] In an optional embodiment, multiple system objects of a process control system are first acquired. These system objects are then analyzed, their attribute information and variable information extracted, and organized and summarized. The relationships between the system objects are then analyzed and abstracted to obtain the associations between them. The control logic of the process control system is then summarized based on the control relationships between the control components. Based on the attribute information, variable information, associations, and control logic, the data and relationships are structured to obtain system structured data.

[0044] In some embodiments of the present application, obtaining system application data of a process control system includes: obtaining application scenarios, application instances, and application processes of the process control system; and generating system application data based on the application scenarios, application instances, and application processes.

[0045] The application scenarios in the above steps refer to the application and usage of process control systems in specific environments, situations, or fields. In different scenarios, process application systems may have different requirements and performance. Application examples refer to specific use cases of process control systems within application scenarios. Application procedures refer to the steps required to complete specific operations when using a process control system.

[0046] In one optional embodiment, an analysis is first conducted from the perspective of the process control system user to obtain the application scenarios of the process control system. Based on the actual application process of the process control system, application examples are summarized and the application process is abstracted. Then, based on the application scenarios, the business boundaries of the process control system application are determined. System application data is generated by combining the descriptions of the application examples and application processes.

[0047] In some embodiments of the present application, an information model namespace of a process control system is created based on an information model framework, including: determining a control station type, a controller type, and a communication module type of the process control system based on the information model framework, wherein the control station type includes a control loop of the process control system; determining a control system hardware type of the process control system based on the control station type, the controller type, and the communication module type; determining a control component type of the process control system based on the control loop type of the control loop; and creating an information model namespace based on the control system hardware type and the control component type.

[0048] The control station type in the above steps is used to characterize the type of control station. The control station is the center of the control system and can monitor and control the status of the process control system. The controller type is used to characterize the type of controller. The controller can be a separate device or an electronic control unit integrated inside the equipment, which responds to control actions under the instructions of the control station. The communication module type is used to characterize the type of communication module. The communication module is used to realize the communication of the process control system. The control station type, controller type and communication module type are determined according to the information model framework. The main hardware of the control system includes the control station, controller and communication module. The control system hardware type can be characterized by the control station type, controller type and communication module type. The control loop type is used to characterize the type of control loop. The type of control loop can determine the type of control component. The control component type is used to characterize the type of control component. The control component is a component used to realize a specific control function. Its type is determined by the control loop type.

[0049] In an optional embodiment, the control station type, controller type, and communication module type of the process control system are first determined based on the information model framework. The control station type includes, but is not limited to, hardware address, number, manufacturer, device model, device type, device health status, controller, communication module, and control loop. The controller corresponds to the controller type, the communication module corresponds to the communication module type, and the control loop corresponds to the control loop type. The control component type can then be determined based on the control loop type, and the control system hardware type can be determined based on the control station type, controller type, and communication module type. Finally, an information model namespace is created based on the control system hardware type and control component type.

[0050] In some embodiments of the present application, the method also includes: compiling the information model based on the information model standard of the information model framework to obtain a model class library of the information model; instantiating the model class library according to multiple devices corresponding to the process control system to obtain instantiation objects of multiple devices, wherein the multiple devices are used to represent devices connected to the process control system; aggregating the instantiation objects of multiple devices to obtain device information models of multiple devices.

[0051] The model library described in the previous steps is compiled from the information model. When the process control system is connected to other systems, it can be directly accessed and called to enable communication between different types of systems. An instantiated object is a specific instance of the model library generated for a specific device. A device information model is a model that aggregates multiple instantiated objects and contains information about multiple device instances.

[0052] In an optional embodiment, first, according to the information model standard of the information model framework, the information model is compiled to obtain a model class library, and then the information of multiple devices corresponding to the process control system is collected, and the model class library is instantiated. Since the specific device models of the equipment are different, there are often some differences from the standard information model. Usually, the differences conform to the 28 principle, that is, 20% are the differences and 80% are the common parts. During the instantiation process, the differences can be processed using the OPC UA Server (Open Platform Communications Unified Architecture Server) deployed on the device. The OPC UA Server can create a runtime device namespace for storing instance objects. After inheriting the common types in the process control system information model, it defines the device-specific types and stores them in the device namespace, and uses the namespace to isolate types to avoid type conflicts. The device-specific types defined by the OPC UA Server and the common types in the information model together constitute the instance of the device. Then, the instantiation objects of multiple devices are aggregated to obtain the device information models of multiple devices.

[0053] In some embodiments of the present application, instantiated objects of multiple devices are aggregated to obtain device information models of the multiple devices, including: obtaining device namespaces of the multiple devices; encoding the instantiated objects based on the device namespaces and the running nodes of the multiple devices to obtain identification information of the instantiated objects; and aggregating the instantiated objects based on the identification information to obtain a device information model.

[0054] The device namespace described in the previous steps is created by the OPCUA Server and is used to store all types of instantiated objects. Identification information is used to identify the instantiated object corresponding to a device, uniquely identifying the device within the plant-wide object topology. The device information model is a model that aggregates multiple instantiated objects based on representation information.

[0055] In an optional embodiment, the device namespaces of multiple devices are first obtained, followed by the path codes of the multiple device operating nodes. The path code consists of the code of each node from the current node to its root node. Then, instantiated objects are encoded based on the device namespaces and the multiple device operating nodes. The device namespaces and the path codes of the device nodes are combined and hashed to obtain the identifier of the instantiated object, thereby uniquely identifying the device and preventing confusion caused by the same device operating node number. Finally, the instantiated objects are aggregated based on the identification information, covering the factory topology, to obtain a device information model.

[0056] In some embodiments of the present application, an instantiated object is encoded based on a device namespace and running nodes of multiple devices to obtain identification information of the instantiated object, including: obtaining the node type of the running node; if the node type is used to indicate that the running node is in automatic allocation mode, the instantiated object is encoded based on the device namespace and the node name of the running node to obtain identification information, wherein the automatic allocation mode is used to indicate a mode of automatically allocating instantiated objects to the running node according to the running status of multiple devices; if the node type is used to indicate that the running node is in fixed mode, the instantiated object is encoded based on the node name of the running node to obtain identification information, wherein the fixed mode is used to indicate a mode in which the instantiated object of the running node is fixedly set.

[0057] In an optional embodiment, the node type of the running node is first obtained. If the node type is a numeric value, indicating that the running node is in automatic allocation mode, the running node is re-encoded based on the device namespace and the node name of the running node, and the identification information of the instantiated object is generated. This avoids the mismatch of the running node name caused by the automatic allocation mode of the running node and ensures the uniqueness of the instantiated object in the entire plant topology. If the node type is not a numeric value, indicating that the running node is in fixed mode and the node name will not change, the instantiated object is encoded based on the node name of the running node to obtain identification information.

[0058] The following describes a preferred embodiment of the present invention in detail. FIG2 is a schematic diagram of an example of an optional process control system information model according to an embodiment of the present invention. As shown in FIG2 , the first namespace represents the default imported information model framework, which includes basic object types, topology element types, and component types. The URL for the first namespace can be http: / / xxa.org / UA / * (a specific URL). The second namespace represents the newly established process control system information module, where the control system hardware type and control component type inherit from the component type in the information model framework. The second namespace can be http: / / xxb.com / PCS / UA (a specific URL). The control system hardware type also includes a series of control system hardware subtypes, namely, control station type, controller type, and communication module type. The control station type includes static attributes such as hardware address, serial number, manufacturer, device model, and device type, as well as real-time, dynamically changing variables such as device health status. It also includes a series of subobject instances: controller, communication module, and control loop. The controller type in the control system hardware subtype corresponds to the controller in the subobject instance, the communication module type in the control system hardware subtype corresponds to the communication module in the subobject instance, and the control loop type in the control system hardware subtype corresponds to the control loop in the subobject instance.

[0059] FIG3 is an overall flow chart of an optional process control system information model establishment according to an embodiment of the present invention. As shown in FIG3 , information modeling, model compilation, and instantiation operations of the information model need to be performed at the process control layer. At the manufacturing execution layer, aggregation operations of the instantiated information model can be performed to implement specific applications of the information model. First, the process control layer performs information modeling to obtain the information model, and then performs model compilation to compile the model into a model class library. Afterwards, instantiation is performed, the model class library is loaded, and model instances of different devices are created. Subsequently, model instances are aggregated at the manufacturing execution layer, and the model instance of a single device is expanded to the entire factory to form a model instance of the factory topology. Applications can then be performed to participate in read, write, subscription, and event notification operations.

[0060] Figure 4 is a modeling flowchart for an optional process control system information model according to an embodiment of the present invention. As shown in Figure 4, in the analysis phase, the system application is first analyzed from the user's perspective, first determining the business boundaries, then describing use cases and processes, thereby obtaining system structure data. The system structure is then analyzed from the provider's perspective, first analyzing system objects, then analyzing and abstracting the relationships between system objects, then extracting system object variables and attributes, and finally analyzing system alarms and events, thereby obtaining system application data. After analysis, the modeling phase begins, introducing an information model framework to create a namespace, then defining data types, variable types, object types and relationships, and finally defining alarm and event types to generate the process control system information model.

[0061] FIG5 is a schematic diagram of the overall structure of an optional process control system information model according to an embodiment of the present invention. As shown in FIG5 , the objects of the process control system information model include domains, system software, system hardware, operation stations, control stations, controllers, communication modules, and input / output modules. The operation stations can operate the system software and system hardware, and the control stations can control the system hardware, controllers, and communication modules. The control stations, controllers, and communication modules together constitute the control system, controlling the objects in the entire information model. The communication module enables communication between the input / output modules and the information model, and the system hardware can issue system alarm events. The control strategy includes control components, which include function blocks, control loops, and process variables. The function blocks, control loops, and process variables work together to implement control functions, and the control components can issue process alarm events. The external system includes field instruments and devices. The control components can control the devices of the external system. The input / output modules can exchange information with the field instruments, and the field instruments can issue instrument alarm events.

[0062] Example 2

[0063] According to another aspect of an embodiment of the present invention, a device for constructing an information model of a process control system is also provided. The device can execute the information model construction method of the process control system provided in the above-mentioned embodiment 1. The specific implementation method and preferred application scenario are the same as those of the above-mentioned embodiment 1 and will not be repeated here.

[0064] FIG6 is a schematic diagram of an information model building device for a process control system according to an embodiment of the present invention. As shown in FIG6 , the device includes:

[0065] The acquisition module 60 is configured to acquire system structure data and system application data of the process control system, wherein the system structure data is configured to represent structured data of the process control system, and the system application data is configured to represent data generated by the process control system in actual application scenarios.

[0066] The creation module 62 is configured to create an information model namespace of the process control system based on an information model framework, wherein the information model framework is configured to unify data representations between different devices.

[0067] The conversion module 64 is configured to convert the system structure data and the system application data based on the namespace to obtain an information model of the process control system.

[0068] In some embodiments of the present application, the acquisition module includes: a first acquisition unit, configured to acquire multiple system objects of a process control system and the control logic of the process control system; an extraction unit, configured to extract attribute information and variable information of multiple system objects and the association relationship between multiple system objects; a first generation unit, configured to generate system structure data based on attribute information, variable information, association relationship and control logic.

[0069] In some embodiments of the present application, the acquisition module also includes: a second acquisition unit, configured to acquire application scenarios, application instances and application processes of the process control system; and a second generation unit, configured to generate system application data based on the application scenarios, application instances and application processes.

[0070] In some embodiments of the present application, a creation module includes: a first determination unit, configured to determine the control station type, controller type, and communication module type of a process control system based on an information model framework, wherein the control station type includes a control loop of the process control system; a second determination unit, configured to determine the control system hardware type of the process control system based on the control station type, controller type, and communication module type; a third determination unit, configured to determine the control component type of the process control system based on the control loop type of the control loop; and a creation unit, configured to create an information model namespace based on the control system hardware type and the control component type.

[0071] In some embodiments of the present application, the conversion module also includes: a compilation unit, which is configured to compile the information model based on the information model standard of the information model framework to obtain a model class library of the information model; an instantiation unit, which is configured to instantiate the model class library according to multiple devices corresponding to the process control system to obtain instantiation objects of multiple devices, wherein the multiple devices are configured to represent devices connected to the process control system; an aggregation unit, which is configured to aggregate the instantiation objects of multiple devices to obtain device information models of multiple devices.

[0072] In some embodiments of the present application, the aggregation unit is further configured to obtain a device namespace of multiple devices; encode the instantiated object based on the device namespace and the running nodes of the multiple devices to obtain identification information of the instantiated object; aggregate the instantiated object based on the identification information to obtain a device information model.

[0073] In some embodiments of the present application, the aggregation unit is further configured to obtain the node type of the running node; if the node type is set to indicate that the running node is in automatic allocation mode, the instantiated object is encoded based on the device namespace and the node name of the running node to obtain identification information, wherein the automatic allocation mode is set to indicate a mode in which instantiated objects are automatically allocated to the running node according to the operating status of multiple devices; if the node type is set to indicate that the running node is in fixed mode, the instantiated object is encoded based on the node name of the running node to obtain identification information, wherein the fixed mode is set to indicate a mode in which the instantiated object of the running node is fixedly set.

[0074] Example 3

[0075] According to an embodiment of the present invention, a computer-readable storage medium is also provided, which includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute the information model construction method of the process control system in the above-mentioned embodiment 1.

[0076] Example 4

[0077] According to an embodiment of the present invention, an electronic device is also provided, comprising one or more processors and a storage device, wherein the storage device is used to store one or more programs. When the one or more programs are executed by one or more processors, the one or more processors execute the information model construction method of the process control system in the above-mentioned embodiment 1.

[0078] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0079] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0080] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0081] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0082] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0084] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention. Industrial Applicability

[0085] The technical solution provided by the embodiment of the present application is applicable to the technical field of industrial automation. In the embodiment of the present application, system structure data and system application data of a process control system are obtained, wherein the system structure data is used to represent the structured data of the process control system, and the system application data is used to represent the data generated by the process control system in an actual application scenario; an information model namespace of the process control system is created based on an information model framework, wherein the information model framework is used to unify the data representation between different devices; the system structure data and the system application data are converted based on the namespace to obtain an information model of the process control system. By obtaining the system structure data and the system application data of the process control system, creating an information model namespace of the process control system based on the information model framework, and converting the system structure data and the system application data based on the namespace, the purpose of building a universal information model of the process control system is achieved, thereby shielding the differences in many protocols and standards between different devices and manufacturers, and improving the universality of multiple types of process control systems from different manufacturers and different devices, thereby solving the technical problem that the universality of multiple types of process control systems from different manufacturers and different devices is poor due to the differences in many protocols and standards between different devices and manufacturers.

Claims

1. A method for constructing an information model of a process control system, comprising: Obtaining system structure data and system application data of the process control system, wherein the system structure data is used to represent the structured data of the process control system, and the system application data is used to represent the data generated by the process control system in an actual application scenario; Creating an information model namespace of the process control system based on an information model framework, wherein the information model framework is used to unify data representation between different devices; Converting the system structure data and the system application data based on the namespace to obtain the information model of the process control system.

2. The method according to claim 1, wherein Obtaining system structure data of the process control system includes: Obtaining a plurality of system objects of the process control system and the control logic of the process control system; Extracting attribute information, variable information of the plurality of system objects, and the association relationship between the plurality of system objects; Generating the system structure data based on the attribute information, the variable information, the association relationship, and the control logic.

3. The method according to claim 1, wherein, Obtaining system application data of the process control system includes: Obtaining the application scenario, application instances, and application processes of the process control system; Generating the system application data based on the application scenario, the application instances, and the application processes.

4. The method according to claim 1, wherein, Creating an information model namespace of the process control system based on an information model framework includes: Determining the control station type, controller type, and communication module type of the process control system based on the information model framework, wherein the control station type includes the control loops of the process control system; Determining the control system hardware type of the process control system based on the control station type, the controller type, and the communication module type; Determining the control component type of the process control system based on the control loop type of the control loop; Creating the information model namespace based on the control system hardware type and the control component type.

5. The method according to claim 1, wherein The method further includes: Compiling the information model according to the information model standard of the information model framework to obtain a model class library of the information model; Instantiating the model class library according to a plurality of devices corresponding to the process control system to obtain instantiated objects of the plurality of devices, wherein the plurality of devices are used to represent the devices connected to the process control system; Aggregating the instantiated objects of the plurality of devices to obtain a device information model of the plurality of devices.

6. The method according to claim 5, wherein, Aggregating the instantiated objects of the plurality of devices to obtain a device information model of the plurality of devices, including: Obtaining the device namespace of the plurality of devices; Encoding the instantiated objects based on the device namespace and the running nodes of the plurality of devices to obtain identification information of the instantiated objects; Aggregating the instantiated objects based on the identification information to obtain the device information model.

7. The method according to claim 6, wherein, Encoding the instantiated objects based on the device namespace and the running nodes of the plurality of devices to obtain identification information of the instantiated objects, including: Obtaining the node type of the running node; If the node type is used to indicate that the running node is in the automatic allocation mode, encode the instantiated object based on the device namespace and the node name of the running node to obtain the identification information, where the automatic allocation mode is used to indicate the mode of automatically allocating the instantiated object to the running node according to the running states of the multiple devices; If the node type is used to indicate that the running node is in the fixed mode, encode the instantiated object based on the node name of the running node to obtain the identification information, where the fixed mode is used to indicate the mode in which the instantiated object of the running node is fixedly set.

8. An information model construction device for a process control system, comprising: An acquisition module, configured to acquire the system structure data and the system application data of the process control system, where the system structure data is configured to represent the structured data of the process control system, and the system application data is configured to represent the data generated by the process control system in an actual application scenario; A creation module, configured to create the information model namespace of the process control system based on the information model framework, where the information model framework is configured to unify the data representation between different devices; A conversion module, configured to convert the system structure data and the system application data based on the namespace to obtain the information model of the process control system.

9. A computer-readable storage medium, the computer-readable storage medium including a stored program, wherein, Execute the information model construction method of the process control system according to any one of claims 1 to 7 in the processor of the device where the program runs.

10. An electronic device, comprising: One or more processors; A storage device, configured to store one or more programs; When the one or more programs are executed by the one or more processors, enable the one or more processors to execute the information model construction method of the process control system according to any one of claims 1 to 7.

Images