Method and System for Implementing Event Rules for Maintenance Relevant Events in a Plurality of Machines

Abstract

Method for implementing event rules for maintenance relevant events in a plurality of machines, wherein the method utilizes a computer system containing a common central configurator, and wherein the machines are connected to the common central configurator to transfer data, where the method includes defining a maintenance relevant event for a certain class of machines by using the common central configurator, sending the event rule to an edge device of at least one machine of this class, preferably to edge devices of all machines of this class, where the edge device forms part of the computer system, and storing the event rule in the edge device and the common central configurator such that it is possible to implement event rules in a plurality of similar machines without having to implement those event rules on every single machine independently.

Claims

1.-10. (canceled)

11. A method for implementing event rules for maintenance relevant events in a plurality of machines, the method utilizing a computer system containing a common central configurator, the plurality of machines being connected to the common central configurator to transfer data, the method comprising: defining a maintenance relevant event for a class of machines by utilizing the common central configurator; sending an event rule to an edge device of at least one machine of said class of machines and storing the event rule in the edge device, the edge device forming part of the computer system; and storing the event rule in the common central configurator.

12. The method according to claim 11, wherein the edge device is situated at or near the at least one machine and the common central configurator comprises a cloud service.

13. The method according to claim 11, wherein the edge device includes a complex event processing engine which, based on the event rule and based on input data from the at least one machine, creates an event message if the input data fulfills the event rule and sends the event message to a device which deploys a respective maintenance rule.

14. The method according to claim 12, wherein the edge device includes a complex event processing engine which, based on the event rule and based on input data from the at least one machine, creates an event message if the input data fulfills the event rule and sends the event message to a device which deploys a respective maintenance rule.

15. The method according to claim 13, wherein the edge device includes a message broker (MB) which receives signals from sensors of the at least one machine and processes the signals before sending said processed signals as input data to the complex event processing engine.

16. The method according to any claim 11, wherein the common central configurator includes a knowledge base which stores a model of each machine, data sources of each machine, events and corresponding event rules of each machine; and wherein new events are stored as new data sources.

17. The method according to claim 11, wherein the common central configurator includes a user interface for defining an event for a certain class of machines by utilizing semantic models.

18. The method according to claim 16, wherein the common central configurator includes a deployment module which deploys a new event rule for an edge device of at least one machine of this class, preferably for the edge devices of all machines of this class, and which subsequently updates the model in the knowledge base with the new event rule.

19. The method according to claim 16, wherein if a machine is reconfigured the event rule is automatically updated by amending the model of said machine in the knowledge base and by deploying the new event rule to respective machines.

20. The method according to claim 11, wherein the event rule is sent to edge devices of all machines of the class.

21. The method according to claim 18, wherein the new event rule is deployed for edge devices of all machines of said class.

22. Computer program code means adapted to perform the method of claim 11 when the computer program is executed on a computer system containing a common central configurator and a plurality of edge devices.

23. A computer system for implementing event rules for maintenance relevant events, the computer system comprising: a plurality of machines with edge devices; and a common central configurator, the plurality of machines being connected to the common central configurator via edge devices to transfer data; wherein the common central configurator is configured to allow definition of a maintenance relevant event for a class of machines; wherein the common central configurator is configured to send a respective event rule to an edge device of at least one machine of said class of machines and configured to store the event rule; wherein the edge device forms part of the computer system; and wherein the edge device is configured to store the event rule.

24. The computer system according to claim 23, wherein the respective event rule is sent to edge devices of all machines of said class.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The invention will be explained in closer detail by reference to a preferred embodiment, which is depicted schematically in the figures, in which:

[0050] FIG. 1 shows a schematic illustration of a computer system in accordance with the invention;

[0051] FIG. 2 shows a user interface for entering a first new event in accordance with the invention;

[0052] FIG. 3 shows a user interface for entering a second new event in accordance with the invention;

[0053] FIG. 4 shows an event rule model in accordance with the invention;

[0054] FIG. 5 shows a semantic model in accordance with the invention; and

[0055] FIG. 6 is a flowchart of the method in accordance with the invention.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

[0056] FIG. 1 shows a computer system containing a common central configurator CCC in its function as an event rule configuration framework. The common central configurator CCC contains a CEP rule configuration interface UI, a knowledge base KB, a message broker connector MBC, and a CEP rule deployment module DM.

[0057] A plurality of machines, here exemplarily represented by two edge devices E1,E2 (each edge device E1,E2 for one machine), are connected to the common central configurator CCC via the message broker MB of their edge device E1,E2. There is an additional message broker MB in front of the common central configurator CCC, where the message broker MB communicates with the message broker connector MBC of the common central configurator CCC. Every edge device E1,E2 has a CEP engine CEP_E connected to its own and to all other message brokers MB. Every machine or edge device E1,E2, respectively, has two sensors S1,S2 sending their data to the communication system of the message brokers MB, as well as to their own CEP engine CEP_E. The item CEP events (labelled CEP_EV) refers to events generated by the CEP engine CEP_E and published on the message broker MB.

[0058] The computer system here is used to monitor the machines and to generate maintenance relevant events based on system status. A maintenance use case is presented based on spindle condition monitoring of a CNC machine, i.e., to generate an event if the average clamping time deviates from a given value in a given period of time. In order to cover condition-based spindle maintenance, two CEP operation types (=event rules) are defined: “Aggregated Cycle Interval” and “Threshold”. The result from the first event rule “Aggregated Cycle Interval” will be used as input to the second event rule “Threshold”.

[0059] For the first event rule, i.e., “Aggregated Cycle Interval”, the input user interface UI appears as shown in FIG. 2. In a window “Add Operation”, a new event rule can be defined. The user has to define to which component the event rule refers to, here it is the spindle of the CNC machine tool (“Spindle”). The event rule has to be named (under “Operation Type”), here as “AggregatedCycleInterval”. Then the user has to give the name of the data source or signal for the input (under “Input Name”) for the event rule, in this case he chooses the sensor that gives a Boolean value (0 or 1) for the clamping status of the tool (“ToolClamped”). The user chooses how the signal or data shall be aggregated (under “Aggregate Funktion”), here “average”. Accordingly, the user has to define the period for aggregation (under “Over Period”), here “24” and the time unit, here “hours”. The user could also choose other aggregate functions, such as a sum, or minimal or maximal values. The user names the output event or signal (under “Output Event/Signal”), here the chosen name is “AverageClampingTime24h”. This first event rule generates an event that is used for further processing thus the box for “Use Output as Signal” is checked.

[0060] By clicking “Save”, the new event rule is saved, translated into CEP language and sent to the CEP engines CEP_E of the machines M1,M2 over the CEP rule deployment module DM and the message brokers MB (see FIG. 1). Then the new event rule “Aggregated Cycle Interval” is saved in the knowledge base KB. The event “Aggregated Cycle Interval” is generated every 24 hours, and it contains the value of the average time between spindle clamping cycles.

[0061] The first event rule, i.e., “Aggregated Cycle Interval”, is used to detect the average of the period between spindle cycles. This event rule will not generate final events.

[0062] For the second event rule “Threshold” the input user interface UI appears as shown in FIG. 3. As in FIG. 2, there is a window “Add Operation” where the new event rule can be defined. The user has to define to which component the event rule refers, here it is again the spindle of the CNC machine tool (“Spindle”). The event rule has to be named (under “Operation Type”), here as “Threshold”. Then the user has to give the name of the data source or signal for the input (under “Input Name”) for the event rule, in this case he chooses the output of the first event rule or operation type “AverageClampingTime24h”. The first event rule yields a number. Accordingly, the possible operation (under “Operation”) that are offered by the user interface UI and that can be chosen is for comparing values, here <, >, <=, >=. Here the user chooses “>=”. The user then has to choose a threshold value (under “Threshold”), here he chooses “80” seconds. The user names the output event or signal (under “Output Event/Signal”), here the chosen name is “SpindleLubricationDueEvent”. This second event rule generates an event that is not used for further processing thus the box for “Use Output as Signal” is not checked.

[0063] By clicking “Save”, the new event rule is saved, translated into CEP language and sent to the CEP engines CEP_E of the machines M1,M2 over the CEP rule deployment module DM and the message brokers MB (see FIG. 1).

[0064] The second event rule “Threshold” gives an event when the average spindle clamping time over 24 hours exceeds 80 seconds. The generated event message of the event “SpindleLubricationDueEvent” has the following format:

[0065] ID number

[0066] date and time

[0067] Event Type: SpindleLubricationDueEvent

[0068] Affected Component: 45AX-Spindle

[0069] Affected Component Label: Spindle

[0070] Measurement: SpindleLubricationSpindleLubricationDueEvent

[0071] Value: 9.00275

[0072] Unit: seconds

[0073] This event message can be forwarded to the suitable maintenance executing entities.

[0074] FIG. 4 depicts an event rule model for asset and data item classes. An asset can be a machine or a machine component that shall be monitored and for which event rules are created. Each asset item (“Iot:Asset”) has a unique identification, such as an ID number, for the computer system, a name (for display on the user interface UI) and a serial number (of the physical device). Thus, the asset here could be the spindle. This event rule model will be stored in the knowledge base KB of the common central configurator CCC.

[0075] As properties of the asset (“Iot:hasProperty”) different data can be assigned, here one data item “Iot:DataItem” is present, containing a unit and an address.

[0076] An event rule item (“rule:EventRule”) with a certain ID and name points (“rule:hasRuleType”) to a rule type item (“rule:EventRuleType”) with a certain ID and name. The rule type item is linked to the asset item, if it is suitable for this type of asset (“rule:suitableForAssetFamily”), i.e., for this class of machine or this class of machine component. The rule type item is also linked (“rule:hasOperation”) to a rule item relating to the operation type (“rule:OperationType”), the operation type containing an ID, a name, an output name and an output event. The rule item relating to the operation type points (“rule:haslnputSignal”) to the data item “Iot:DataItem”.

[0077] The event rule item (“rule:EventRule”) also points (“rule:generatesDataItem”) to the data item and points (“rule:appliedForAset”) to the asset item.

[0078] The data item receives (“Iot:observedProperty”) observation data from the observation item (“Iot:Observation”), where each observation contains a timestamp and a value and is triggered by an event item (“Iot:Event”).

[0079] Here, three different rules point to the operation type item (“rule:OperationType”): the threshold rule item (“rule:Threshold”) containing an ID, a name, an operation and a treshold value, see FIG. 3; the counting cycle item (“rule:CountingCycle”) containing an ID, a name and a cycle number; the item for aggregated cycle interval (“Rule:AggregatedCycleInterval”) containing an ID, a name, a period and a threshold value, see FIG. 2.

[0080] FIG. 5 depicts a semantic model of the spindle class and its data items. The spindle class (for spindles all having the same mechanical and technical properties) are defined in the asset item (“Iot:Asset”) by an ID and a serial number. This item points (“Iot:hasProperty”) to the data item (“Iot:DataItem”) that contains information about the unit, the address in the system and the data type of this data.

[0081] The data of a certain spindle SN1 is defined in a respective item (“data:spindle-SN1”) and contains an ID “GMN-SN1” for identification within the computer system and a serial number SN1. This data item points to the general spindle item (“mt:Spindle”), which again points to the asset item. The general spindle item (“mt:Spindle”) at the beginning additionally points (“Iot:has Property”) only to one property item for the clamped tool (“mt:ToolClamped”), where the general spindle item contains information about the unit and the Boolean data type according to which the tool is clamped or not. The item for the clamped tool points to the data item (“Iot:DataItem”). Accordingly, the spindle data item (“data:spindle-SN1”) also points (“Iot:has Property”) to its tool clamped item (“data:SN1-ToolClamped”) that contains a unit, a concrete data type (Booelan) and a concrete address: DB13.DBX32.4. The tool clamped item of the concrete spindle SN1 points to the general item for the clamped tool (“mt:ToolClamped”).

[0082] Now, when the user defines a new event rule “Aggregated Cycle Interval” with the output event or signal “AverageClampingTime24h”, see FIG. 2, then this output event is added both as a new general item “mt:AverageClampingTime24h” to the properties of the general spindle item (“mt:Spindle”), parallel to the existing clamped tool item (“mt:ToolClamped”), and as a new item “data:SN1-AverageClampingTime24h” to the concrete spindle item (“data:spindle-SN1”), parallel to the existing data item. The concrete spindle item “data:spindle-SN1-AverageClampingTime24h” contains the unit of the data, here seconds, the data type, here double, and the concrete address DB13.DBX32.6, and points to the general item “mt:AverageClampingTime24h”.

[0083] When the user defines the new event rule “Threshold” with the output event or signal “SpindleLubricationDueEvent”, see FIG. 3, then this output event is added both as a new general item “mt:SpindleLubricationDue” to the properties of the general spindle item (“mt:Spindle”), parallel to the two existing property items, and as a new item “data:SN1-SpindleLubricationDue” to the concrete spindle item (“data:spindle-SN1”), parallel to the existing data item. The concrete spindle item “data:SN1-SpindleLubricationDue” contains the unit of the data, here no units, the data type, here Boolean, and the concrete address DB13.DBX32.8, and points to the general item “mt:SpindleLubricationDue”.

[0084] FIG. 6 is a flowchart of the method FIG. 6 is a flowchart of a method for implementing event rules for maintenance relevant events in a plurality of machines, where the method utilizes a computer system containing a common central configurator CCC, and the plurality of machines are connected to the common central configurator to transfer data. The method comprises defining a maintenance relevant event for a class of machines by utilizing the common central configurator CCC, as indicated in step 610.

[0085] Next, an event rule is sent to an edge device E1,E2 of at least one machine of the class of machines and storing the event rule is stored in the edge device E1,E2, as indicated in step 620. In accordance with the invention, the edge device E1,E2 forms part of the computer system.

[0086] Next, the event rule is stored in the common central configurator CCC, as indicated in step 630.

[0087] Thus, while there have been shown, described and pointed out fundamental novel features of the invention as applied to a preferred embodiment thereof, it will be understood that various omissions and substitutions and changes in the form and details of the methods described and the devices illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.