Method for configuring a monitoring system for monitoring industrial processes and industrial assets
By adopting a monitoring system framework in industrial automation systems and utilizing the OPC UA protocol and common data models, the flexibility issues of data integration and view creation are resolved, enabling efficient information sharing and fault detection across factories.
Patent Information
- Application Number
- CN202080030349.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-05-31
- Filing Date
- 2020-05-27
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-05-27
AI Technical Summary
Existing industrial automation systems struggle to achieve flexible data integration and dynamic view creation when monitoring industrial processes and assets associated with multiple industrial plants, leading to difficulties in information sharing and fault detection.
It adopts a monitoring system framework, configures the gateway to receive data through the OPC UA protocol, organizes and transforms data using a common predefined data model, generates graphical views, and performs analysis and control based on data processing requests. It supports the integration of multiple application functions and dynamic view updates.
It enables efficient data integration and dynamic view creation across multiple industrial plants, simplifies fault detection and analysis, and improves system flexibility and information sharing capabilities.
Smart Images

Figure CN113728342B_ABST
Abstract
Description
Technical Field
[0001] The present invention generally relates to the field of industrial automation systems, and more particularly to a method for monitoring industrial processes and industrial assets associated with an industrial plant and an industrial plant operated by an industrial automation system. Background Art
[0002] Modern industrial plants, such as process plants or manufacturing plants, operate using industrial automation systems (process control systems, factory automation systems) that provide automated control, production planning and several other features, and whose monitoring systems are used to optimize and plan processes / industrial equipment. Such industrial processes and systems (such as manufacturing units or enterprises) can be modeled as a functional hierarchy of five levels or layers 0-4. The five levels represent the various technical and business processes that make up the enterprise. Level 4 can constitute business planning and logistics decisions supported by enterprise resource planning (ERP) and supply chain management systems. Functions that are part of level 4 include a framework for organizing, defining and standardizing business processes required for effective planning and control of the enterprise. ERP is designed to integrate business functions and can constitute functions such as accounting, distribution, marketing, sales, manufacturing, etc. The scope of these functions also covers policies related to continuous improvement of its product range and manufacturing capabilities; expansion of production facilities; policy decisions on environmental and product compliance, and design decisions on, for example, modular controllable transformers for achieving various power ratings.
[0003] Level 3 constitutes traditional Manufacturing Operations Management (MOM) and Manufacturing Execution Systems (MES). Software systems associated with MOM and MES provide tracking and trending information to support decision making in areas such as workflow, process control, and maintenance. MOM is a method used to manage and optimize the processes that occur on the shop floor of an enterprise. MOM and MES systems are designed to: manage work in process, manage work orders, shop floor materials, report material consumption data, etc.
[0004] Levels 0, 1, and 2 constitute decisions related to real-time production events such as process sensing, supervisory control, and process automation technologies. Monitoring systems are provided to facilitate real-time control of shop floor equipment, manage machine processing, provide logic for various functionalities, execute manufacturing sequences (such as batch, continuous, large-scale, etc.), buffer for communication with higher-level systems, and deliver basic logic for operating the factory. These levels also host servers and databases that store any detailed historical data. Storage can be based on local servers or / and cloud services.
[0005] Integration and linkage of all these different enterprise levels is critical to a unified, plant-wide view of manufacturing. The integrated process will facilitate the effective sharing of information between units of the enterprise to effectively utilize equipment and data at all levels.
[0006] MOM usually bridges information between the factory floor and enterprise applications (levels 2 and 4, respectively). There may be integration for ERP solutions, which manage materials, costs, resources and their quality parts from the enterprise and control systems. Historical data is also associated with MOM to understand the historical trends of process behavior over a period of time and in different batches. The workflow of processes, materials and quality is fed into the MOM system through enterprise applications. The MES system processes the workflow and executes the program through the control system. This bridging of information or the integration of data can help make actionable decisions in the production process. For example, the analysis of work orders and the total throughput time from ordering to shipment can be used to decide whether to adopt a centralized factory approach or to produce multiple product lines based on different technology platforms. There may be other information sources, such as SQL servers or from other applications, where data needs to be collected to be associated and work together to effectively implement various business needs.
[0007] Generally speaking, there are specialized applications (apps) / application functions / microservices developed for MOM. These applications can include independent modules for various enterprise functions, such as logistics management, quality control management, maintenance management, etc. For example, in the manufacture of transformers, many power and distribution transformers are often customized to meet specific customer requirements. In most cases, each customized manufacturing requires the implementation of customized logic. For example, depending on whether the transformer manufacturing is dry or oil-type or the customer's requirements for specific mechanical design constraints, the manufacturing process will require customized logic. This customized implementation takes a considerable amount of time and the independent modules may not be fully integrated, resulting in disconnection between hierarchical levels. Disconnection may correspond to a lack of data or analysis availability or / and visibility across enterprise systems, or further efforts are needed to achieve shared data and analysis across enterprise systems. Most MOM and MES implementations will be highly specific and may require further configuration and customization to better integrate with pre-installed applications. This will generally require a separate view implementation of the module and also require an authorization module for each implementation. The view implementation gives a graphical representation of various software modules across the enterprise layer, while identifying any dependencies between them. For example, dependencies can be "assigned to", "contained", "used", etc. For example, if a module is assigned to another module, the dependency is one of "assigned to".
[0008] As the size and functionality of manufacturing cells become increasingly complex, the number of modules can become very large. Modules can correspond to all hardware and software components and their subcomponents, as well as the communication modules involved and the protocols adopted, etc. The system can be divided into different network areas at different levels. The current system can consist of the following: Thin clients for process control, engineering workstations, business / ERP systems, information management servers, factory networks, process portals / OPC servers, operator workstations / portals, client-server networks, basic system servers, dual history logs for parallel recording in two history servers, programmable automation controllers, third-party PLCs and DCS, motor controllers. Typically, this layer follows the field network connected to various field devices, such as sensors (for temperature, pressure, flow, etc.), actuators, positioners, etc.
[0009] The thin client for process control can be used as a process portal. It provides a portal with features and functions designed to facilitate and optimize any process of the enterprise. The process portal is a user interface for participating in the process. Engineering workstations can be used to develop control strategy designs or configure systems. The information management server hosts information such as production information management. The information management server also supports data access for third-party applications. The provided plant network facilitates data transfer to and from other parts of the plant (including the process portal server). The process portal server can be accessed through a graphical user interface on the process control portal. It hosts process data collection, storage and analysis tools; advanced alarm management systems; comprehensive historical libraries; and advanced reporting packages. Server information can also be accessed by operator workstations / portals, which provide an interface to perform various operational tasks and workflow integration and access to multiple applications. Operator workstations can be connected to other servers through a client-server network to enable the transfer of information related to various operations between workstations and servers. These other servers can be basic system servers, dual historical logs for parallel recording in two historical servers. They can host information including control configurations of the control system (industrial automation system), build data for various applications, data for graphic configurations, and so on. They can receive information through the control network for storage and archiving. The control network can also be used to control various process instruments such as programmable automation controllers, third-party PLCs and DCSs, motor controllers, etc.
[0010] Such a system view as described above does not provide optimal system flexibility and does not enable efficient data integration and dynamic view creation of process and processing assets to perform analysis and fault detection, etc. In particular, a system view is required when information is integrated from multiple industrial plants to be able to holistically process information related to processes / equipment of these multiple plants. Various applications across multiple services face integration challenges, which makes it difficult to customize applications for different customers or experts within the enterprise. In addition, in-depth methods for analyzing and identifying faults in a process or its processing require more engineering work and it is difficult to correlate information available from multiple sources.
[0011] Therefore, there is a need to develop a framework for a monitoring system that allows flexible integration of various devices / equipment / assets and their process data as well as result data from various data sources (such as various servers, historical repositories, assets, etc.). Summary of the invention
[0012] The above-mentioned shortcomings, defects and problems may be understood by reading and understanding the following specification.
[0013] The present invention provides a method for configuring a monitoring system, the monitoring system being used to monitor industrial processes and industrial assets associated with a plurality of industrial plants, wherein each industrial plant is operated using one or more industrial automation systems. The method comprises: the monitoring system: receiving data associated with the industrial process, the operation of the industrial plant, and the industrial assets in the industrial plant from the one or more industrial automation systems in one or more local data models through one or more gateways according to a preconfigured protocol configuration in one or more gateways. The monitoring system adopts a common predefined data model to organize data associated with industrial processes, operations of industrial plants and industrial assets received from one or more industrial automation systems in one or more local data models, and converts the data into a common structured data format for use by multiple application functions configured in the monitoring system, the multiple application functions involving data processing and generation of graphical views associated with industrial processes and industrial assets, wherein the common predefined data model provides identifiers to associate industrial processes with corresponding industrial assets; receives a request for data processing and uses one or more application functions from multiple application functions to generate graphical views of industrial processes and corresponding assets; identifies specific industrial processes and industrial assets associated with the request for data processing and generates graphical views; extracts specific data and identifiers associated with the industrial processes and industrial assets; processes specific data according to the data processing request, and generates a first graphical view associated with the industrial processes and corresponding assets for the processed specific data and associated identifiers according to a preconfigured first view configuration, wherein the processing of the specific data includes at least one of the following: analysis of process data for diagnosis, predictions related to processes and assets, identification of fault locations, control of processes and assets, and information access control for users. Finally, the monitoring system generates a second graphical view from the first graphical view by merging at least one new view configuration onto the preconfigured first view configuration based on the result of at least one data processing performed on the specific data according to the data processing request.
[0014] In one embodiment, the method includes controlling at least one process parameter associated with the industrial process and / or the industrial asset based on a result of at least one data processing performed.
[0015] In one embodiment, the graphical view is generated based on role authorizations used to control user access rights.
[0016] In one embodiment, a common predefined data model is defined for variables and relational database entities for representing and storing data.
[0017] In one embodiment, the preconfigured protocol configuration is an Open Platform Communications Unified Architecture (OPC UA), application programming interface (API).
[0018] In one embodiment, the identifier that associates the industrial process and the corresponding industrial asset is an XML tag for data associated with the industrial process, the operation of the industrial plant, and the industrial asset. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings illustrate exemplary embodiments as disclosed herein and should not be considered to limit the scope. In the drawings:
[0020] Figure 1 A schematic diagram of a monitoring system for monitoring industrial processes and industrial assets associated with a plurality of industrial plants is shown;
[0021] Figure 2 shows schematic data collected from industrial processes, operations of industrial plants, and industrial assets in industrial plants;
[0022] Figure 3 shows the implementation of authentication in a microservices architecture through a gateway;
[0023] Figure 4 shows a block diagram representation of an application configurator;
[0024] Figure 5 shows a graphical view of implementing a role map built on a plug-in architecture;
[0025] Figure 6 a process diagram illustrating a method for configuring a monitoring system; and
[0026] Figure 7 A graphical view of a manufacturing system is shown as an exemplary embodiment of the present invention. DETAILED DESCRIPTION
[0027] The present invention provides a method for configuring a monitoring system for monitoring industrial processes and industrial assets associated with multiple industrial plants. The industrial plants are operating using industrial automation systems. In one embodiment, the present invention can be implemented as a plug-in framework (flexible and dynamic monitoring system) for manufacturing operations management (MOM), which supports dynamic integration and addition of multiple applications / application functions / microservices and data sources. This provides a way to combine manufacturing execution system (MES) and MOM data. Combining data from these services facilitates the implementation of customized and meaningful views based on multiple data sources. Dynamic views are provided by the framework, so there is minimal development on the client side. Multiple applications, including analytical applications, can be included to access various data sources registered in the framework. Microservices / application functions / applications (Apps) communicate with each other through a message bus, thereby providing microservices integrated by the technology and business functions of the enterprise. The present invention simplifies the method for dynamic view creation.
[0028] In the following detailed description, reference is made to the accompanying drawings which form a part thereof, and the accompanying drawings are shown by way of illustration of specific embodiments that can be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice them, and it is understood that other embodiments may be utilized. Therefore, the following detailed description should not be construed in a limiting sense.
[0029] Figure 1 1 is an exemplary schematic diagram showing a monitoring system 130 for monitoring industrial processes and industrial assets associated with multiple industrial plants. The present invention provides flexible and dynamic integration of various data sources to update views that may be task-specific. Figure 1 As shown in , an enterprise includes multiple manufacturing or process industrial control system units (industrial automation systems) 100a, 100b, etc., which may even be separated by different networks and geographically. Components and functions of enterprise devices and processes can communicate with a monitoring system (130) through a preconfigured protocol configuration such as the Open Platform Communications Unified Architecture (OPC UA). Here, OPC UA, as an open platform communication model, is viewed as a common data model for data communication between an industrial plant and a monitoring system 130. However, the industrial plant may provide / receive information from the monitoring system using a data model that is local to the industrial automation system used in the industrial plant. In this scenario, the monitoring system will have a method for converting the local data model into a common data model (e.g., the public predefined data model of OPC UA) to allow easy integration of data from multiple data sources. In reference Figure 1 In an embodiment of the present invention, the monitoring system 130 can receive data from the industrial automation system 100a in a local data model 140 and from the industrial automation system 100b in a public data model 150 (public structured data format). Multiple data sources can have data in different local data models / formats specific to industrial assets. Data from all sources can be integrated and imported by the monitoring system through a gateway interface (120). OPC UA (110) implemented on the server provides a communication link between the factory floor and manufacturing enterprise applications (ERP, MOM, MES, etc.). The control system configured as an OPC UA client is provided with a dashboard that provides a view layout of various applications and modules. The applications and modules correspond to a large number of different devices / equipment / assets and various data across data sources. The applications and modules can also involve analysis of the collected data, graphical representation of such data, etc.
[0030] The complexity in a view increases as the number of modules that need to be represented in the view increases, and the view may require a lot of customization. For example, a view may span different time windows or specific process flows in manufacturing. This requires adding additional views while leveraging data from various sources and still working as a single system. This view creation is facilitated by providing a framework for new back-end and front-end components for plug-ins. The back-end components can consist of plug-ins for analysis, plug-ins for data pre-processing (such as filtering, etc.). The back-end components are implemented on back-end servers and computing resources (which may also include cloud servers). The front-end components can consist of plug-ins for generating local views on the system, which can limit the amount of information to reduce view complexity. The front-end components are implemented on a front-end system such as a monitoring system (130). For example, the framework can provide public methods for audit processing and authorization through plug-in components.
[0031] The developed framework provides the necessary libraries and wizards to create modules, applications (or apps), and plug-ins. Applications can be modularized by combining multiple modules. Plug-ins can be added to existing modules and applications to extend various features. Plug-ins can also be used to encapsulate functionalities such as library implementation, integration with various data sources, etc. In addition, the framework also provides many plug-ins, which allow users to easily develop complex applications and modules using these plug-ins. A collection of these independently deployable modules and applications constitutes a microservice architecture. These microservices can work together by sharing data and information between them, thereby integrating different levels of the enterprise.
[0032] Figure 2 A representation of the present invention is shown where data is collected from various data sources related to industrial processes, operations of industrial plants, and industrial assets in industrial plants. The data sources may be historians (230a), SQL servers (230b), various enterprise related reports / documents (230c), MES systems, and Enterprise Connectivity Solutions (ECS) systems (230d). The historian (230a) may consist of archived data and the MES / ECS system (230d) may also contain information or data from ERP (210) and other system components (220) such as motors, controllers, etc.
[0033] The data collected from these different data sources can be in formats such as csv, tag constraints, image formats, structured text or tagged files, audio and video data, etc. The data sources can be integrated through the interface of the data provider (270). The data provider is a software function implemented on the server that hosts the received data. The server that hosts the above data and the software functions that enable the service are collectively referred to as data providers in this article. Data providers can also be constructed in modular accessories with appropriate customization and configuration. Customization and configuration allow various data sources and formats to be continuously added. The data provider also provides a data access layer, which is a collection of software functions that extract data from various data sources. The data access layer extracts data from the data source and passes them to the data provider, and then the data provider integrates, builds and organizes the data in a standardized format, and the standardized format is also marked or annotated to identify the data source from which the data is extracted. These integrated data form a common data model, which can be used by application functions (or microservices or applications) to perform various data processing, such as data reduction, plot generation, statistical process analysis, etc., as well as subsequent graphical view generation as requested by the user. The data processing and graphical viewing requests may correspond to specific industrial processes and industrial assets, where the specific industrial processes and industrial assets are identified by tags or indicia associated therewith.
[0034] These modules can communicate with each other and with data providers through commonly accessible application programming interfaces (APIs). Implementations of these microservices can be hosted locally on control systems and local servers or distributed across cloud services and data centers. Applications and modules (240, 250, 260) access data sources through a gateway (280), which can also host firewalls and other authorization protocols. Applications can be hosted on a network (250) or accessed through a specific device (260) such as a handheld device. Applications can be pre-constructed or custom created (240) and hosted on a network or any other device.
[0035] Thus, the framework allows plugging in multiple data sources, which can have their own authorization policies, for example, implemented through an API gateway. The layout of applications and modules (microservices) can exist on a web page and be accessed through a control system or through a collection of applications. The framework also allows hosting of custom applications developed through or independently of the framework. In one embodiment, communication is supported by Hypertext Transfer Protocol Secure (HTTPS) or WebSocket Secure (WSS) protocols.
[0036] Figure 3The implementation of security and authentication in a microservice architecture through a gateway 350 is shown. For example, the gateway 350 can be an API gateway. All communications from the client can be routed to specific applications 310, 320, and 330 and data providers 300 of microservices through the gateway. All applications and data providers are registered in the gateway. Registration is performed using an Internet Protocol (IP) address and a root address, both of which are registered with the gateway. Registration can be implemented using a service registry database such as an identity server 340, which is used to host IP addresses, port numbers, or paths to application root directories. The API gateway can use this service registry to locate microservices and route any client requests thereto.
[0037] In one embodiment of the present invention, client calls are routed by the gateway to the corresponding API of the endpoint service or data provider. Routing is based on query requests from the client, where the API gateway uses a service registry database to identify the endpoint. Initially, when the client connects, user authentication is done locally against an identity server or a cloud-based server such as Azure Active Directory. The API gateway can initiate authentication and authorization by collecting client credentials. The client credentials can be a client certificate with structured data, which can also be shared with an authorization server hosted in the cloud or on-site. The data in the client certificate can consist of information such as the client name, digital signature, and so on.
[0038] After successful authentication, the gateway or authentication server then generates a token corresponding to the client with the username. The token thus provided to the client is stored by the client and is used for every request made for any microservice request. The token is passed to the corresponding controller along with the API call.
[0039] Each API is equipped with roles and access rights, or it can be mapped to a common role. For example, a role can be an administrator, super administrator, manager, operator, service engineer, customer, supplier, guest user, etc. Roles can be set and changed dynamically as needed. More roles can be added and customized to suit enterprise operations. Each role is associated with its host access rights, such as read and write access to data and reports, planning maintenance permissions,
[0040] Role mapping is done through a public view that provides a graphical layout where roles are mapped to several APIs representing data sources. Data sources can also be logically grouped together in various ways so that multiple data sources can be accessed through a single API. The role map connects to several APIs and lists the available roles. Access policies are defined for each role. For each API, roles may have different scopes and responsibilities. The data exposed by each API is based on the policies defined in each API. For example, for the customer role, the access policy can be defined to limit access to the data source corresponding to the catalog to products and services; the supervisor role can be authorized to access product flow, machine and operator efficiency; equipment operators will have access to equipment data, past performance history and ideal performance data on their production lines, etc.
[0041] Figure 4 A block diagram representation of an application configurator 430 is shown that is used to configure all applications on the dashboard 420, enterprise reporting 410, production management application 400, etc., with a gateway for authentication and access policies for various roles. The application configurator configures the applications to facilitate each application having its own profiles and configurations required for its operation. All information is contained in the service. The application registration provides routing to the gateway. This defines the routing of incoming queries and decisions to the services to be processed.
[0042] Figure 5A graphical view is shown that implements role mapping built on a plug-in architecture that enables new widgets or components to be added to the view. Available applications and widgets are pre-configured for specific roles of users or operators. Only those applications for which the operator has role-based authentication in advance can be configured on the dashboard. All applications are linked to the dashboard, and they can also be configured in the same view. Multiple applications can be hosted in the same view and configured to obtain a comprehensive view or a partial view of a specific industrial process and industrial asset. Customization can be made for each application, such as the amount of detailed information to be viewed, and each application can be configured to be visualized in the same framework. This provides a method for extending functionality and integrating specific views according to customer requirements. For example, if a customer has a graphical view configured for visualization of a specific process and corresponding industrial asset (such as a motor) (referred to as a pre-configured first view configuration), where the graphical view is used for specific data associated with the motor. Specific data and its analysis may include at least one of the following: process data for diagnosis, predictions related to processes and assets, identification of fault locations, control of processes and assets, and information access control for users. The user may want to add another view (new view configuration) that may correspond to a motor calibration, where the first graphical view previously had no calibration information, the new view configuration associated with the calibration can be imported into the existing first graphical view and flexibly arranged with the help of the plugin framework. As the new view configuration (with the calibration data) is imported into the pre-configured first view configuration, a second graphical view is generated from the first graphical view.
[0043] Applications can be plugged into the same framework. New applications can be added dynamically and routing can be configured in a visual way.
[0044] Application widgets can be associated with a role or a specific application or / and data source. For all widgets or components, an endpoint reference needs to be defined. The endpoint uniquely identifies the application or data source to which the service request is sent. Views are very generic and widgets can be placed anywhere in a dashboard or view. Direct endpoints can also be used to obtain data.
[0045] Data from various data sources can be organized by data providers in a standardized, modular and extensible set of data formats. This allows various applications and widgets to access the data for use and analysis. Multiple parts of the factory can be integrated with different views on the hosted dashboard. Therefore, while monitoring the view on the control system, the production management application can be integrated to have a more comprehensive view. This provides enterprise service partners and system integrators with the ability to create separate views and extend application functionality by adding services. It can be connectivity with an ERP system or with a specific control system.
[0046] Figure 6 A process diagram of a method 600 for configuring a monitoring system 130 for monitoring an industrial process and industrial assets associated with a plant is shown. The industrial plant is operated with an industrial automation system. As shown in step 610, the monitoring system receives data associated with the industrial process, the operation of the industrial plant, and the industrial assets in the industrial plant. The data is received from the industrial automation system in a native data model or format via a gateway having a preconfigured protocol configuration. The preconfigured protocol configuration can be OPC UA as mentioned above.
[0047] As shown in step 620, the monitoring system uses a public predefined data model to organize data associated with industrial processes, industrial plant operations, and industrial assets, and converts the data into a public structured data format for use by application functions. Application functions or applications are configured in the monitoring system and involve data processing and generation of graphical views associated with industrial processes and industrial assets. The public predefined data model is defined for variables and relational database entities for representing and storing data. Any data provider that conforms to the public predefined data model provides data to be visualized in a standard widget that can be used for a view. Therefore, the defined public data model is a public data structure that facilitates data management and application development by unifying all data sources in the data provider.
[0048] This data unification and structuring supports the use or transfer of data across multiple microservices in all hierarchies of the enterprise. The common predefined data model provides identifiers to associate industrial processes and corresponding industrial assets. For example, data can be annotated (e.g., using XML tags) to simplify the flow of data across microservices while reducing errors and enabling easier search and retrieval of data. The addition of tags further facilitates the classification of data collections without further modification. Data can be maintained on the front end, and therefore the same data can be represented in multiple widgets, such as pie charts or bar charts.
[0049] As shown in step 630, a request for data processing is received and a graphical view of an industrial process and corresponding assets is generated using one or more application functions from a plurality of application functions. At step 640, associated specific industrial processes and industrial assets related to the request for data processing are identified for use in generating the graphical view. As shown in step 650, specific data and identifiers associated with the industrial process and industrial assets are extracted.
[0050] At step 660 , specific data is processed according to the data processing request, and a first graphical view associated with the industrial process and the corresponding asset is generated for the processed specific data and the associated identifier according to a preconfigured first view configuration.
[0051] The processing of specific data includes: analysis of process data for diagnostics, predictions related to processes and assets, identification of fault locations, control of processes and assets, and information access control for users.
[0052] Finally, at step 670 , a second graphic view is generated from the first graphic view by merging the new view configuration onto the first view configuration based on the result of the data processing performed on the specific data according to the data processing request.
[0053] In one embodiment, a link is created to connect directly to a specific database or data source. The link is associated with a tag, for example "DS":" / Hist / Tags / {Variablename}" The historical data source has its corresponding link defined. Therefore MES and control system data can be associated with the historical database using the corresponding link in the variable. The variable will have a link to the historical data. This enables the user to represent the data value in a trend or obtain the value for other applications (such as analysis).
[0054] Such analysis from data source integration at different levels across the enterprise allows for the creation of dynamic views of enterprise capabilities. The dynamic views are provided by the framework. The framework facilitates the addition of multiple applications and provides application-specific authorizations for various services and data access. The framework also permits the hosting of multiple web-based factory automation applications in the same framework. The communication between applications provides microservices that integrate across the technical and business capabilities of the enterprise. Analysis from such views allows everyone within the enterprise who is authorized to see all data and analysis customized to their specific needs to make actionable decisions. For example, a view that permits customized analysis of parameters, such as processes involving the reduction of transformer bad quality scrap, the reduction of total production time from order to shipment, and the reduction of total production time, can recommend actions in favor of a centralized factory approach in transformer manufacturing, rather than producing multiple product lines based on different technology platforms.
[0055] Figure 7 A graphical view of a manufacturing system as an exemplary embodiment of the present invention is shown. In this example, a request for data processing for fault diagnosis and subsequent fault processing of an industrial system is performed to isolate any faults of the manufacturing system or / and a sensing system associated with the manufacturing system. A manufacturing system may have a collection of equipment and sub-equipment, such as motors, valves, heaters, dryers, tanks, etc. All components and sub-components are assets and may be purchased from multiple vendors and supported through different communication protocols. Each of them may further operate with different data and file formats, such as plain text, audio, images, JavaScript Object Notation (JSON), etc.
[0056] Data models can be used to define assets or objects. The definition of object models with input and output signals provides the generation of visual objects without manual engineering. Various pre-built microservices can also be deployed for such visual representations. Since microservices can be implemented in different programming languages, they are built through application programming interface (API) layers that support the use of their services using standard protocols (such as HTTP). The framework provided by the present invention provides a wide range of microservices to facilitate the creation of asset models with all input / output functions and their network environment, data integration from various data sources using data providers, data pre-processing and validation to meet any specific rules, data storage, etc.
[0057] Thus, the definition of the object model makes it control system and application agnostic. The application agnostic feature is generated by the flexibility provided by the framework in selecting the nature of the signals and the communication module for each device and tailoring it to any given application. For example, a motor can be used in a pump or a compressor, and the object model of the motor can be flexibly represented by selecting the appropriate configuration or template from the microservice. The object model once created can be reused throughout the manufacturing plant or even in multiple manufacturing plants using similar objects or assets.
[0058] Different parts of the plant and associated objects as well as relationships and cross-reference information from different aspects of the process can be identified. Earlier it was not actually possible to dynamically provide visualization for all aspects of a process involving multiple objects, and therefore there might be various aspects for any fault or malfunction. Without integrating each device data model, they would have to be analyzed as independent entities, and the visualization would not contain the flexible and dynamic aspects of the data flow between devices. The microservice architecture within the framework provides flexibility by placing different visualization components (object models) at any desired location on the screen, depending on user needs. For example, a user may be an operator or technician, an automation engineer or a data analysis engineer, etc. Each of them may need a different view to analyze the process and its processing. The view needs to be configured with the required visual objects, and the corresponding view is saved so that it can be recalled dynamically on demand. Users can navigate to different views that have been pre-configured and previously archived. In addition, views can flexibly have any type of visual object, which can even be added to the system later. Dynamic views are generated based on the information required by a specific role, where the view can be customized to focus on the part of the system that is relevant to the decision of a specific role.
[0059] Views that did not exist before can be created on the fly. Process views can show the entire process view or a selected portion of a view. It can also generate views based on location (by area) or assets (assets of similar kind or assets required for a specific process), views based on fault conditions, etc. Each user can create any desired dynamic views and archive them for on-demand recall.
[0060] Any analysis or visualization requires a specific data set associated with the recipe or process and all the equipment associated with it. This data is usually distributed throughout the process and various equipment and must be manually constructed and configured to obtain all necessary information and visualizations. That is, there are multiple data sources with various data formats that may come from different manufacturers. Integrating all data formats from different data sources or equipment to generate flexible and dynamic visualizations is a huge engineering challenge.
[0061] Examples of objects in a factory are tanks, motors, valves, heaters, dryers, etc. Each object is configured to be part of a workflow. On the control system, using a microservices architecture, each object and its associations and input / output signals are defined through a data model. The data model is used to display objects or assets as interlinked visual elements to show the complete workflow. Various views can be generated, for example, a field engineer needs an asset view, a software engineer needs another view (application / module; software and firmware versions; authorization and access information), a data analyst may need another view of the data source; data structure, etc.
[0062] The provided framework enables building and utilizing various microservices associated with processing, analysis and monitoring to achieve fault diagnosis, fault isolation and perform corrective actions or recommend them. Such frameworks have the flexibility and dynamic aspects of the provided views without the need to create separate visualizations for the process. The model also defines reference parameters that represent the normal operation of the process and the status of the processing equipment. References to objects are defined in the model and thus any deviation or change from the normal behavior can be classified as a fault. Microservice applications for predictive analysis can be attached to the framework to monitor fault conditions and equipment efficiency.
[0063] In one example, a microservice function that performs analytics to monitor equipment efficiency can be attached to the framework. The attached model can be used to predict improvements in workflow or set point changes. Set points can be adjusted or workflows can be modified based on the predictive algorithm. Corrective actions are then deployed in place, and since the visualization is dynamic, those are updated based on the changes. This will facilitate a dynamic view from a location, function or asset perspective as well as raw material and efficiency information perspective.
[0064] This written description uses examples to describe the subject matter herein, including the best mode, and to enable any person skilled in the art to make and use the subject matter. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.
Claims
1. A method for configuring a monitoring system for monitoring a plurality of industrial processes and a plurality of industrial assets associated with a plurality of industrial plants, wherein each industrial plant is operated using one or more industrial automation systems, the method comprising: a) receiving, through the one or more gateways, data associated with the plurality of industrial processes, operations of the industrial plants of the plurality of industrial plants, and the plurality of industrial assets in the industrial plants from the one or more industrial automation systems in one or more local data models according to a preconfigured protocol configuration in the one or more gateways; b) employing a common predefined data model to organize data associated with the plurality of industrial processes, the operation of the industrial plant, and the plurality of industrial assets received in one or more local data models from the one or more industrial automation systems, and converting the data into a common structured data format for use by a plurality of application functions configured in the monitoring system, the plurality of application functions involving data processing and generation of graphical views associated with the plurality of industrial processes and the plurality of industrial assets, wherein the common predefined data model provides identifiers to associate an industrial process from the plurality of industrial processes with a corresponding industrial asset from the plurality of industrial assets; c) receiving a request for data processing and generating, using one or more application functions from the plurality of application functions, a graphical view of one or more industrial processes from the plurality of industrial processes and one or more corresponding industrial assets from the plurality of industrial assets; d) identifying an associated specific industrial process from the one or more industrial processes and a specific industrial asset from the one or more corresponding industrial assets associated with the request for data processing and generating the graphical view, wherein the specific industrial process corresponds to the specific industrial asset; e) extracting specific data and identifiers associated with the specific industrial process and the specific industrial asset; f) processing the specific data according to the data processing request, and generating a first graphical view associated with the specific industrial process and the corresponding specific industrial asset for the processed specific data and the associated identifier according to a preconfigured first view configuration; g) generating a second graphical view from the first graphical view by merging at least one new view configuration into a preconfigured first view configuration based on a result of at least one data processing performed on specific data according to a data processing request, wherein the processing of the specific data includes at least one of the following: analysis of process data for diagnosis, prediction related to processes and assets, identification of fault locations, control of processes and assets, and information access control for users.
2. The method of claim 1, further comprising: At least one process parameter associated with the plurality of industrial processes and / or the plurality of industrial assets is controlled based on a result of the at least one data processing performed. The method of claim 1 , wherein the graphical view is generated based on role authorization for controlling user access rights.
4. The method of claim 1, wherein the common predefined data model is defined for variables and relational database entities for representing and storing data.
5. The method of claim 1, wherein the preconfigured protocol configuration is an Open Platform Communications Unified Architecture (OPC UA), an Application Programming Interface (API).
6. The method of claim 1, wherein the identifier associating the industrial process and the corresponding industrial asset is an XML tag for data associated with a plurality of industrial processes, operations of an industrial plant, and a plurality of industrial assets.
