ML FOR PROCESS MONITORING

20210224670 · 2021-07-22

Assignee

Inventors

Cpc classification

International classification

Abstract

A computer program product providing an environment in which control software controlling at least one physical process is executed, wherein the control software is comprised of modular blocks termed actions, wherein the control software is defined through graph connections between the actions, wherein the computer program product provides for a monitoring functionality, wherein physical sub-processes of the at least one physical process influenced by an action may be monitored. A method for choosing which physical sub-processes are to be monitored is provided, wherein a user places a debug point on an action.

Claims

1. A computer program product providing an environment in which control software is executed, the control software controlling at least one physical process via at least one external software solution, wherein each controlled physical process is decomposable into at least one physical sub-process, the physical sub-processes of the controlled physical processes combinable into a nonempty set of physical sub-processes, the computer program product receiving as input: sensor data recording observables of the at least one physical process, and monitoring information relating to which physical sub-processes from the set of physical sub-processes are to be monitored, wherein the control software comprises: at least one elementary building block, termed action, wherein the number and type of actions and the associations between actions determine the control software, wherein each of the at least one external software solutions provides interfaces through which actions may communicate with the external software solutions, wherein the monitoring information comprises at least one debug point, wherein each debug point is placed on an action to which is associated a nonempty subset of the set of physical sub-processes, wherein the sensor data recording observables which depend on the subset of the set of physical sub-processes associated to a debug point are stored in memory, the computer program product having access to the memory, that the stored data are relatable to the debug point, and to each debug point is associated a monitoring function having access to the parts of memory comprising sensor data related to the debug point, wherein the monitoring function provides an indication about a physical state of the subset of the set of physical sub-processes associated to the debug point, wherein a debug point and a monitoring function form a pair.

2. A computer program product according to claim 1, wherein a debug point on an action allows for monitoring the physical state of the subset of the set of physical sub-processes associated to the debug point, wherein the monitored sub-processes comprise sub-processes belonging to physically remote physical processes, wherein the monitoring provides information about the joint physical state of the monitored sub-processes.

3. A computer program product according to claim 1, wherein a monitoring function associated to at least one debug point is configured to provide anomaly detection on the stored data associated to the debug point, wherein anomalies in the stored data are identified by the monitoring function, the anomalies relating to physical changes in the subset of the set of physical sub-processes associated to the debug point.

4. A computer program product according to claim 3, wherein the monitoring function implements an online unsupervised anomaly detection algorithm, wherein the monitoring function operates on the stream of sensor data recording observables which depend on the subset of the set of physical sub-processes associated to the debug point to which the monitoring function is associated.

5. A computer program product according to claim 3, wherein the monitoring function implements a rule-based anomaly detection algorithm, wherein the monitoring function operates on the stream of sensor data recording observables which depend on the subset of the set of physical sub-processes associated to the debug point to which the monitoring function is associated, wherein the rules are adapted to the action on which the debug point is placed.

6. A computer program product according to claim 1, wherein a graphical user interface is provided, wherein actions are associated to each other via a graph, wherein a debug point is represented by a pin placed on an action.

7. A computer program product according to claim 7, wherein upon the detection of an anomaly associated to a debug point, a visual change in the pin representing the debug point is displayed in the graphical user interface.

8. A computer program product according to claims 6, wherein different graphical forms of the pin representing the debug point are associated to different monitoring functions.

9. A method for monitoring the behavior of at least one physical sub-process using the computer program product according to claim 1, wherein placing a debug point with a paired monitoring function on an action to which is associated the at least one physical sub-process, and providing information about the behavior of the at least one physical sub-process with the monitoring function by analyzing the sensor data recording observables which are related to the at least one physical sub-process associated to the debug point.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The inventive system is described below in more detail purely by way of example with the aid of concrete exemplary embodiments illustrated schematically in the drawings, further advantages of the invention also being examined Identical elements are labelled with the same reference numerals in the figures. In detail:

[0025] FIG. 1 shows a schematic and illustrative depiction of the invention.

DETAILED DESCRIPTION

[0026] FIG. 1 shows a schematic and illustrative depiction of the invention. The computer program product according to the invention provides an environment 1 in which control software 2 may be executed. The control software 2 is used for controlling at least one physical process 4a,4b, wherein the control proceeds indirectly through external software 7a,7b, wherein the control software 2 calls the external software 7a,7b to control the execution of the at least one physical process 4a,4b. The control software 2 itself is assembled from modular blocks termed actions 3a,3b,3c. In FIG. 1, an exemplary illustration with three actions 3a,3b,3c is given. A graphical connection between different actions 3a,3b,3c determines the control software 2. Actions 3a,3b,3c may be connected in a bidirectional manner, or information may only flow in one direction from one action to another. Actions may communicate with the external software 7a,7b via interfaces provided by the external software 7a,7b. An action 3b,3c may communicate with the external software 7a, or an action 3a may only provide internal functionality for the control software 2.

[0027] A physical process 4a,4b may comprise physical sub-processes 5a,5b. Each physical process 4a,4b may comprise a different number of physical sub-processes 5a,5b. The physical sub-processes 5a,5b are typically influencing each other, wherein influencing is depicted in FIG. 1 via bidirectional graph connections between physical sub-processes 5a,5b.

[0028] An individual action 3c may at least partially control a plurality of physical processes 4a,4b. An action 3b,3c may control a subset 6a,6b,6c of physical sub-processes 5a,5b, wherein the controlled subset may comprise physical sub-processes corresponding to different physical processes. The “action” abstraction provided by the computer program product according to the invention therefore allows for distinct physical processes to be controlled at once using an individual action 3c.

[0029] Sensors record physical observables related to physical sub-processes 5a,5b. A control software 2 defined by an action graph controls at least one physical process 4a,4b. If a set of pre-defined actions are available to a user, the association of which physical sub-processes 5a,5b are influenced by which action may be pre-stored on the computing unit on which the control software is executed. A user graphically assembling a control software 2 therefore may not need to know about the associations of physical sub-processes 5a,5b to actions 3a,3b,3c. Such knowledge is encoded in the actions themselves. Having abstracted away the close connection between physical sub-processes 5a,5b and actions 3a,3b,3c, the user of the control software 2 may decide to monitor the behavior of the (parts of) physical processes 4a,4b influenced by an action. The user, however, does not need to know which physical sub-processes 5a,5b are specifically influenced by the action he chooses to monitor. Monitoring proceeds then by analyzing the sensor data provided by sensors associated to the physical sub-processes 5a,5b associated to the monitored action.

[0030] Monitoring may proceed in different forms. One way is unsupervised monitoring, wherein monitoring may be provided by a model which attempts to detect changes or outliers in the sensor data on which it operates. Such an unsupervised monitoring may operate directly on the stream of sensor data in an online fashion, or it may use stored sensor data for detecting anomalies that might have occurred in the past. In the latter case, monitoring an action requires allocating memory on a computing unit, wherein the memory may be typically allocated in a dynamic way, wherein the required amount of memory may depend on the length of the execution time of the monitored action. The monitoring method may, for example, be embodied as the incremental local outlier detection algorithm.

[0031] Monitoring may also be provided as supervised monitoring. For supervised monitoring, examples of typical failures and normal behavior of the physical sub-processes 5a,5b associated to a monitored action may have been gathered, and a supervised model might have been trained to detect normal or abnormal behavior of the monitored physical sub-processes 5a,5b.

[0032] Monitoring functionality is provided by the computer program product 1 according to the invention by enabling debug points 8a,8b which can be placed on individual actions 3a,3b,3c. A debug point 8a,8b may be represented by a pin, wherein different shapes or colors of pins may be provided by the computer program product 1 according to the invention. Different types of pins representing debug points 8a,8b may be associated to different monitoring functions. A debug point 8a,8b according to the invention placed on an action by a user does not stop the execution of the at least one physical process 4a,4b controlled by the control software 2. Instead, the monitoring function associated to the placed debug point 8a,8b monitors the sensor data provided by the sensors recording observables of the physical sub-processes 5a,5b associated to the action 3b,3c on which the debug point 8a,8b is placed. The computer program product according to the invention may restrict the actions on which debug points 8a,8b can be placed by a user, for example by requiring that actions on which debug points can be placed influence at least one physical process 4a,4b.

[0033] The pairing between debug points 8a,8b and monitoring functions according to the invention may enable a user to monitor (parts of) physical processes 4a,4b without knowing the detailed structure of processes. The graphical environment 1 provided by the computer program product according to the invention may allow for rapid and intuitive development of control software 2, wherein complicated interactions between different physical processes 4a,4b may be simply monitored by placing debug points 8a,8b according to the invention on actions 3a,3b,3c considered to be important by a user of the control software 2.

[0034] It goes without saying that the illustrated figure is merely a schematic of possible exemplary embodiments.

[0035] Although the invention is illustrated above, partly with reference to some preferred embodiments, it must be understood that numerous modifications and combinations of different features of the embodiments can be made. All of these modifications lie within the scope of the appended claims.