Priority level change facility, priority level change system and priority level change procedure

Abstract

The processing of high-priority data is managed while reducing the load resulting from data processing. A priority level change device comprises: a priority level change unit that modifies the priority level of the data; and a data selection unit that selects data for which processing should be reduced from a plurality of data elements based on the priority level.In the priority level change facility, the priority level change unit changes the priority level of priority-related data, which are data relating to priority-changed data, based on the relevance level of the priority-changed data, which are data whose priority level has been changed, and the data selection unit selects data for which processing is to be reduced from a plurality of data elements, including the priority-changed data and the priority-related data, based on the priority level.

Description

Technical field

[0001] The invention disclosed in the present description relates to a technology for changing priority levels in data processing. State of the art

[0002] In a maintenance management system or similar system that manages multiple administrative targets periodically distributing data using telemetry technology, data with a large number of data points or a large volume of data received from a facility is frequently handled. Therefore, there are instances where the management system becomes overloaded due to an enormous amount of received data. State-of-the-art document Patent document

[0003] Patent Document 1: Japanese Patent Application Publication JP 2020 - 28 005 A Summary Problem to be solved with the invention

[0004] Patent document 1 specifies the priority level of data processing based on the change tendency in the data, thus avoiding an overloaded state.

[0005] However, there are cases where specifying a priority level becomes inappropriate due to the relationships between the data elements, which cannot be considered solely based on the data's change tendency. In such cases, the problem arises that processing data with a high priority level is not guaranteed.

[0006] The invention disclosed in the present description was conceived in view of the above problem, and it is an invention for ensuring the processing of data with a high priority level while reducing the load resulting from data processing. Ways to solve the problem

[0007] A priority level changing device, which is a first aspect of the invention disclosed in the present description, is a priority level changing device that modifies a priority level associated with the processing of a plurality of data elements, wherein the priority level of the data and a relevance level, indicating the relevance of the data to another element of the data, are predetermined for each element of the data, wherein the priority level changing device comprises: a priority level changing unit that modifies the priority level of the data; and a data selection unit that selects the data for which processing is to be reduced from a plurality of elements of the data based on the priority level. The priority level changing unit modifies the priority level of the priority-related data, respectively.Priority-related data, which are the data belonging to or relating to the priority-changed data, are selected based on the relevance level of the priority-changed data, i.e., the data whose priority level has been changed. The data selection unit chooses the data for which processing is to be reduced from a plurality of elements of the data containing the priority-changed data and the priority-related data, based on the priority level. Effects of the invention

[0008] According to at least the first aspect of the invention disclosed in the present description, the priority levels of the priority-modified data and the priority-related data are changed so that the processing of data with a high priority level can be ensured, while the processing of data with a low priority level is reduced.

[0009] Further objectives, features, aspects and advantages related to the invention disclosed in the present description will become even more apparent from the following detailed description and the accompanying drawings. Brief description of the drawings Fig. Figure 1 is a diagram that conceptually shows an example configuration of a monitoring control system according to a priority level change system according to an embodiment. Fig. Figure 2 is a flowchart showing an exemplary operation to be carried out by a priority level change unit according to the embodiment. Fig. Table 3 shows an example of data in a priority-level model management database. Fig. Figure 4 is a flowchart showing an exemplary operation to be carried out by a load level adjustment unit according to the embodiment. Fig. Table 5 shows an example of data in the priority level model management database. Fig. Figure 6 is a flowchart showing another exemplary operation to be carried out by the load level adjustment unit according to the embodiment. Fig. Figure 7 is a diagram showing an example of how image data is displayed on a display device. Fig. Figure 8 is a diagram showing another example of displaying image data on the display device. Fig. Figure 9 is a diagram showing a model management system in the priority level model management database. Fig. Figure 10 is a diagram showing another example of model management in the priority level model management database. Fig. Figure 11 is a diagram that schematically shows an example of hardware components assumed in a case where the priority level change system, which serves as an example in Fig. 1 is shown, is actually in operation. Fig. Figure 12 is a diagram that schematically shows an example of hardware components assumed in a case where the priority level change system, which serves as an example in Fig. 1 is shown, is actually in operation. Description of embodiments

[0010] The following is a description of one embodiment with reference to the accompanying drawings. In the embodiment described below, detailed features and the like are also described to illustrate the invention, but they are merely examples, and not all of them are necessarily essential features for the embodiment to be carried out.

[0011] It should be noted that the drawings are schematic, and for the sake of clarity, components may be omitted, configurations simplified, or the like may be appropriately altered. Furthermore, the relationships in size and position among the components shown in various drawings are not necessarily accurate and may be modified as necessary. There are also instances where a drawing is hatched, such as a top view that is not a cross-sectional view, to facilitate understanding of the embodiment.

[0012] Furthermore, in the following description, identical components are designated with the same reference symbols, and their names and functions are also identical. Therefore, their detailed explanation is occasionally omitted to avoid repetition.

[0013] Furthermore, in the present description, where a certain component is described as "possessing", "containing", "having" or the like, the expression is not an exclusive expression that excludes the presence of other components, unless otherwise specified.

[0014] Furthermore, in the present description - even where ordinal numbers such as "first" and "second" are used - these terms are used to facilitate understanding of the contents of the embodiment, and the contents of the embodiment are not limited to the sequence or the like that can be expressed by these ordinal numbers. embodiment

[0015] The following describes a priority level change device, a priority level change system, and a priority level change procedure according to the present embodiment. Configuration of the priority level change system

[0016] Fig. Figure 1 is a diagram that conceptually shows an example configuration of a monitoring control system according to a priority level change system according to the present embodiment.

[0017] As in Fig. As shown in Figure 1, a monitoring control system 1 comprises: a priority level change unit 10 that receives a priority level change command 100; a priority level model management database 12 that records priority levels and relevance grades with respect to the processing of monitoring data; a load level setting unit 14 that sets a load level derived from the processing of data based on the priority levels (or, more precisely, that selects the data to be the processing target); a monitoring data management database 18 that records the monitoring data; a display data generation unit 16 that captures the data selected by the load level setting unit 14 from the monitoring data management database 18 and generates the display data; and a display device 20 that displays the generated display data.The priority level model management database 12, the priority level change unit 10, the load level setting unit 14, or similar components can be contained in and operated in a cloud. This allows the processing load to be distributed.

[0018] A functional unit group containing the priority level change unit 10, the priority level model management database 12, and the load level setting unit 14 is also called monitoring control unit 2 (corresponding to the priority level change unit). The priority level model management database 12 can be located outside of the monitoring control unit 2 and access the priority level change unit 10 and the load level setting unit 14 appropriately.

[0019] Using the monitoring control system 1, the load level setting unit 14 selects the data to be processed based on the priority levels, thus reducing the load on the system resulting from data processing. Here, the priority levels that serve as a reference for the load level setting unit 14 to select the data are dynamically changed by the priority level change unit 10 according to the priority level change command 100, and they are recorded in the priority level model management database 12.

[0020] In the priority level model management database 12, predefined priority levels for processing each data element and predefined relevance levels, which represent the relevance of each data element to other data, are associated with and recorded. A data priority level is predefined for a data element and is indicated, for example, by a numerical value from 1 to 10, with a higher numerical value indicating that the processing of the corresponding data is assigned a higher priority level.

[0021] One or more relevance levels are also predefined for a data element, and these are indicated, for example, by a numerical value (including a decimal) from 0 to 1. A higher numerical value indicates a greater degree of relevance to other data (or to each data element in cases where relevance to multiple data elements is expected). The relevance levels can be predefined by a user and can be modified appropriately based on the degree of similarity in the change tendency within the data or similar criteria (i.e., the priority level between data elements with similar change tendencies is set to a high value).

[0022] Examples of relevance levels between data elements include: a value calculated from a relation between components in a piece of equipment, facility, or the like (including a relation between installation locations); a relation in an energy system distribution flow; a relation between upper and lower levels in a processing flow (including a relation between processes of things, such as a processing flow in a water treatment plant); a relation between trains or the like on the same line in operations management; a relation between parts on a display screen to which data is assigned; a relation derived from an input tendency of users (workers) on a display screen; and a relation on a system between components provided by the same data source.

[0023] The relationship between data elements managed by the priority-level model management database 12 can be maintained as a tree structure, or it can be maintained as a graph database, where the relationship between the data elements is written as node connections. In the case where the tree structure is maintained, it is possible to search for data (priority-related data) that belongs to or is related to data whose priority level has been changed (priority-changed data) at high speed.

[0024] Priority Level Change Command 100 is information generated from an alarm triggered when an anomaly occurs in another facility within Monitoring Control System 1 or a related facility outside Monitoring Control System 1, an alarm triggered when a data processing volume exceeds a threshold, feedback sent by a worker from Display Device 20, or similar sources. Priority Level Change Command 100 includes: information identifying the data whose priority level is to be changed, information regarding the change value in the priority level, and information regarding the reason for the priority level change (such as the facility where an anomaly occurred).

[0025] The priority level change unit 10 dynamically changes the priority level of each element of the data recorded in the priority level model management database 12, based on the priority level change command 100. For example, the priority level of data related to a facility where an anomaly has occurred is changed to a higher level according to the reason why the priority level needs to be changed.However, in a case where the processing load in priority level change unit 10 increases, the priority level change operation to be performed by priority level change unit 10 may only involve adding a change flag or the like to the priority levels of the priority-changed data and the priority-related data recorded in priority level model management database 12, and load level setting unit 14 may calculate the changed priority level based on the change flag (including performing an operation to rewrite an actual numeric value).

[0026] In this way, the need to change the priority level of priority-related data every time the priority level of priority-changed data is changed is eliminated; the load level setting unit 14 can change the priority level of another data element later by tracking the relation of some data elements that have high priority levels, and the processing load of the priority level change unit 10 can be reduced.

[0027] When the priority level of a data element is changed, the priority level change unit 10 can also (simultaneously or sequentially over time) change the priority level of data (priority-related data) that is related to the data (priority-changed data), according to the degree of relevance. That is, the priority level of data (priority-related data) related to a data element (priority-changed data) is also changed, which is derived from the priority level change process for the data.

[0028] The load level setting unit 14 selects the data to be transferred to the display device 20, referring to the priority level model management database 12 and taking into account the priority levels of data elements. More precisely, the load level setting unit 14 selects data to reduce the data processing load (data to reduce processing by excluding data from normal processing targets). When selecting the data to be transferred to the display device 20, the load level setting unit 14 also considers the relationship (the degree of relevance) between data elements.

[0029] For example, consider a case where data A and data α each have a priority level of five (on a scale of one to ten). In this case, the priority levels of data B, which is related to data A, and data C, which is related to data A, are eight and ten, respectively, and the priority levels of data β, which is related to data α, and data γ, which is related to data α, are eight and two, respectively. In this case, the load level setting unit 14 determines that, among data A and data α, which have the same priority level, the data A, whose related data have a higher priority level (in this case, the sum of the priority levels of the related data is greater), has a higher priority level, and then performs the selection.

[0030] In this example, the sum of the priority levels of the related data is used as the criterion for determination. However, in a case where the number of related data elements varies, an average priority level can be used, or the priority levels of the related data can be weighted and calculated based on their relevance levels. Operation of Priority Level Change Unit 10

[0031] Next, a process to be carried out by the priority level change unit 10 in the monitoring control system 1 according to the present embodiment when the priority level change command 100 is received is described with reference to Fig. 2 described here Fig. 2 a flowchart illustrating an exemplary operation to be carried out by the priority level change unit 10 according to the present embodiment.

[0032] First, priority level change unit 10 determines whether priority level change command 100 has been issued (step ST01 in Fig. 2) If the priority level change command 100 has been issued, the process continues with step ST02. If, on the other hand, the priority level change command 100 has not been issued, step ST01 is repeated.

[0033] In a case where priority level change command 100 is issued due to an anomaly in a certain device, priority level change unit 10 raises the priority level of the data collected by the device. Alternatively, priority level change unit 10 modifies the priority level of the target data depending on a specified value or quantity entered by the user along with priority level change command 100. Such data, whose priority level is changed according to priority level change command 100, is designated as priority-modified data.

[0034] The priority level change unit 10 next retrieves from the priority level model management database 12 the degree of relevance between the priority-changed data, which is data whose priority level is to be changed according to the priority level change command 100, and the priority-related data, which is data that is related to or refers to the priority-changed data (step ST02 in Fig. 2).

[0035] The priority level change unit 10 then changes the priority level of the priority-changed data and the priority level of the priority-related data (step ST03 in Fig. 2) At this point, the change value in the priority level of the priority-related data is determined according to the degree of relevance to the priority-changed data.

[0036] For example, the following applies: Since the priority level change command 100 for the priority-changed data has the change value in the priority level of the priority-changed data (the difference from the previous value), the priority level change unit 10 can be the value obtained by multiplying the difference by the relevance level of the priority-related data to the priority-changed data, as specified as the difference produced by the priority level change in the priority-related data (at this point, the relevance level is in the range of 0 to 1.0).

[0037] In this way, priority level change unit 10 modifies the respective priority levels of the priority-changed data and their priority-related data. Priority level change unit 10 then remains ready until the next priority level change command 100 is issued (step ST04 in...). Fig. 2).

[0038] The priority level change command 100 can be issued again, for example, once the anomaly in the device has been resolved. When it is no longer necessary to maintain high priority levels for data belonging to the device in which the anomaly occurred, the priority level change command 100 can be issued to assign each data element a priority level appropriate for the next state (which is the system's normal state). As a result, the priority level of each data element can be reset upon any event (such as an anomaly in a device).

[0039] Fig. Table 3 shows an example of data in the priority level model management database 12. As in the example in Fig. As shown in Figure 3, a priority level is specified for each data element (Data A to Data Z), and data related to the respective data elements and their relevance levels are shown sequentially. The number of data elements belonging to or related to each data element is not all the same, and some data may have only one related data element, or they may have no related data at all.

[0040] For example, if data F is modified based on priority level change command 100, then priority level change unit 10 changes the priority levels of data B, data C, and data E according to their relevance to data F, with reference to Fig. 3.

[0041] In a case where the change value in the priority level of data F, designated by priority level change command 100, is, for example, +3, the priority level of data B as priority-related data can be changed by +3 × 0.4 = +1.2, the priority level of data C as priority-related data can be changed by +3 × 0.3 = +0.9, and the priority level of data E as priority-related data can be changed by +3 × 0.6 = +1.8.

[0042] It should be noted that in the example above, priority levels are defined in the range of 1 to 10, relevance levels are defined in the range of 0 to 1.0, and a larger number indicates a higher priority level or a higher relevance level. Operation of the load level adjustment unit 14

[0043] Next, a process is described that is to be carried out by the load level setting unit 14 in the monitoring control system 1 according to the present embodiment, in a case where the system load level has increased, with reference to Fig. 4. Here is Fig. 4 a flowchart showing an exemplary operation to be carried out by the load level adjustment unit 14 according to the present embodiment.

[0044] The system load level mentioned above refers to the load on the system (including the monitoring control system 1) associated with data processing, and it can be, for example, the CPU load on the monitoring control system 1 or the character load on the display device. The system load does not cause a problem when all data undergoes normal processing at the usual time, but the load can increase if the amount of data requiring processing increases at an anomaly or similar event.

[0045] First, the load level setting unit 14 determines whether the system load level is high (step ST11). For this determination, it is conceivable to specify a method for defining a threshold value for the CPU load, the character load, or the like, and, for example, to determine whether the threshold is exceeded. If the system load is not high, the operation is terminated.

[0046] When the system load is high (or in a case where priority level change command 100 is issued for this reason), the load level setting unit 14 selects from the priority level model management database 12 the data for which processing is to be reduced (reduced-processing data) because its priority level is lowest (step ST12). It should be noted that the reduced-processing data selected by the load level setting unit 14 at this time also includes the priority-changed data and the priority-related data whose priority levels were changed according to priority level change command 100.

[0047] Here, the load level setting unit 14 determines whether there are multiple data elements that have the lowest priority level (reduced processing data) (step ST13).

[0048] If there are multiple data elements with the lowest priority level (reduced-processing data), then the load level setting unit 14 further searches the priority level model management database 12 for the data (reduced-processing related data, which are data that have relevance levels to the reduced-processing data) that are related to those data elements. Among the multiple elements of reduced-processing data, the one whose reduced-processing related data has a high priority level is excluded from the selection targets (step ST14). If, on the other hand, there are no multiple data elements with the lowest priority (reduced-processing data), the process continues with step ST15.

[0049] It should be noted that the above processing is repeated until it is determined that a single element of the reduced-processing data should be selected at the load level setting unit 14. However, depending on the system's data processing capability, multiple elements of reduced-processing data may be selected, or there may be no reduced-processing data to select (there may be no data selection operation by the load level setting unit 14).

[0050] The load level setting unit 14 next reduces the load on the processing of the selected reduced-processing data (step ST15). More precisely, it is possible to extend the processing interval of the reduced-processing data or to exclude the reduced-processing data from the data processing targets. That is, reduced-processing data refers to data that is excluded from the regular processing targets without any reduction and for which processing is reduced; it does not only refer to data that is completely excluded from the data processing targets. For example, in a screen drawing process, it is possible to reduce the resolution, exclude the data from screen refresh targets, or similar measures. The process then returns to step ST11.

[0051] Fig. Table 5 shows an example of data in the priority level model management database 12. In the example in Fig. Figure 5 shows the respective data elements arranged in descending order of priority levels, and data C and data Z (both of which have priority level 1), where the same priority level is specified (priority level 1), and data B and data E (both of which have priority level 2) are shown.

[0052] In this case, the load level setting unit 14 can select an element of the reduced-processing data from data C and data Z, as described above with reference to step ST14.

[0053] With reference to Fig. 3. The load level setting unit 14 first recognizes that the reduced-processing contiguous data of data C are data A, data F, and data Y, and that the reduced-processing contiguous data of data Z are data X and data Y. The load level setting unit 14 then checks that the average priority level of data A, data F, and data Y is greater than the average priority level of data X and data Y. The load level setting unit 14 is then able to select data Z as the reduced-processing data.

[0054] As described above with reference to step ST14, the load level setting unit 14 can also select an element of the reduced-processing data from data B and data E.

[0055] With reference to Fig. 3. The load level setting unit 14 first recognizes that the reduced-processing contiguous data of data B are data A, data D, and data F, and that the reduced-processing contiguous data of data E are data A, data D, and data F. The load level setting unit 14 then checks that the priority levels of the reduced-processing contiguous data of data B and data E are the same. In such a case, the load level setting unit 14 can further consider the relevance levels of the reduced-processing contiguous data and select data E, which has a lower relevance level compared to the reduced-processing contiguous data (data A), which has the highest priority level.

[0056] Fig. Figure 6 is a flowchart showing another exemplary operation to be carried out by the load level adjustment unit 14 according to the present embodiment.

[0057] First, the load level setting unit 14 determines whether the system load level is high (step ST21). For this determination, it is conceivable to specify a method for defining a threshold value for the CPU load, the character load, or the like, and, for example, to determine whether the threshold is exceeded. If the system load is not high, the operation is terminated.

[0058] When the system load is high (or in a case where priority level change command 100 is issued for this reason), the load level setting unit 14 selects from the priority level model management database 12 the data (reduced-processing data) that have a lower priority level than a predetermined threshold (step ST22). It should be noted that the reduced-processing data selected by the load level setting unit 14 at this time also includes the priority-changed data and the priority-related data whose priority levels were changed according to priority level change command 100.

[0059] The load level setting unit 14 then reduces the load on the processing of the one element or the plurality of elements of reduced-processing data (step ST23).

[0060] Next, the load level setting unit 14 determines whether the system load level is below a threshold (step ST24). If the system load level is below the threshold, the process continues with step ST25. Conversely, if the system load level is above the threshold, the process returns to step ST21.

[0061] In step ST25, the load level setting unit 14 cancels the action to reduce the processing load from the data with high priority levels to the data with reduced processing load (i.e., it performs normal data processing) until the system load level reaches the threshold. When the system load level reaches the threshold, the process then returns to step ST21.

[0062] The above operation allows the load on processing data with lower priority levels than the threshold to be reduced all at once. Consequently, the time required to reduce the load can be shortened, and the load reduction operation itself can also be simplified. Example of the display on the display device 20

[0063] Fig. Figure 7 is a diagram showing an example of how image data is displayed on the display device 20. Fig. 7 are data B, data C, data E and data Z in Fig. 3 shown on the display device 20.

[0064] Fig. Figure 8 is a diagram showing another example of the display of image data on the display device 20. Fig. Figure 8 illustrates an example of a display in a case where the display processing of data with lower priority levels than the threshold is reduced, specifically in the operation that is in Fig. 6 is shown. Fig. 8 is any element of data B, data C, data E, and data Z in Fig. 3 not shown on the display device 20. Example of the priority level model management database 12

[0065] Fig. Figure 9 is a diagram showing a model management system for priority level model management database 12. Fig. Figure 9 shows a directed graph in which each node specifies data and its priority level, and an edge between nodes indicates the degree of relevance between data elements.

[0066] Fig. Figure 10 is a diagram showing another example of model management in the priority level model management database 12. Fig. Figure 10 shows a directed graph in which each node specifies data and its priority level, and an edge between nodes indicates the relevance level between data elements. Fig. 10 priority level nodes are arranged in descending order of priority levels. Learning priority levels of data

[0067] To change a data priority level, there are cases where a temporary change is made, such as generating an alarm, and there are cases where a permanent change is made by learning the tendency of inputs from a user through the display device 20.

[0068] In accordance with the above, machine learning of the tendency of inputs or the like from a user is carried out by the display device 20 to permanently change priority levels so that a frequently occurring alarm can be dealt with at high speed.

[0069] Artificial intelligence (AI) can be used to learn the tendency of user input and to determine whether a priority level change should be made permanent. By using AI to learn from large datasets, a more accurate determination can be made quickly. AI can be used in the cloud for this purpose.

[0070] Examples of events that trigger a priority level change include feedback from user input, and changing the priority level based on the feedback includes changing the display method, such as changing the magnification on the screen display, the size of the display area, or the display direction. Hardware components of the priority level change system

[0071] Fig. 11 and Fig. 12 are diagrams, each schematically showing an example of hardware components assumed in a case where the priority level change system, which serves as an example in Fig. 1 is shown, is actually in operation.

[0072] It should be noted that there are cases in which the hardware components used as examples in Fig. 11 and Fig. The components shown in 12 do not match the components shown as an example in Fig. 1 are shown, specifically regarding the numbers and the like, since the components, which serve as an example in Fig. Figure 1 shows conceptual units.

[0073] Therefore, it is possible to at least devise the following: a case in which a single component, which is in Fig. Figure 1 shows a plurality of hardware components that are located in Fig. 11 and Fig. Figures 12 show a case in which a single component, which is in Fig. Figure 1 shows some of the hardware components that are in Fig. 11 and Fig. 12 are shown, and a case in which a plurality of components that are in Fig. 1 are shown, contained in a single hardware component which is in Fig. 11 and Fig. 12 is shown.

[0074] In Fig. Figure 11 shows a processing circuit 1102A, which performs arithmetic operations, a storage device 1103, which is capable of storing information, and an output device 1105A, which is capable of outputting information, such as a display, a liquid crystal display device, or a lamp, as hardware components for forming the priority level change unit 10, the priority level model management database 12, the load level setting unit 14, the display data generation unit 16, the monitoring data management database 18, and the like, which are shown in Figure 11. Fig. 1 are shown.

[0075] In Fig. Figure 12 shows a processing circuit 1102B, which performs arithmetic operations, and an output device 1105B, which is capable of outputting information, such as a display, a liquid crystal display device, or a lamp, as hardware components for forming the priority level change unit 10, the priority level model management database 12, the load level setting unit 14, the display data generation unit 16, the monitoring data management database 18, and the like, which are shown in Figure 12. Fig. 1 are shown.

[0076] The priority level model management database 12 and the monitoring data management database 18 are configured with the storage device 1103 or any other storage device (not shown herein).

[0077] The storage device 1103 can, for example, be a volatile or non-volatile semiconductor memory, such as a hard disk drive (HDD), a selective access memory (RAM), a read-only memory (ROM), a flash memory, an erasable programmable read-only memory (EPROM) or an electrically erasable programmable read-only memory (EEPROM), a memory (recording medium) including a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a DVD or the like, or any type of recording medium that may be used in the future.

[0078] The processing circuit 1102A can execute a program stored in the storage device 1103, an external CD-ROM, an external DVD-ROM, an external flash memory, or the like. That is to say, it can be, for example, a central processing unit (CPU), a microprocessor, a microcomputer, or a digital signal processor (DSP).

[0079] In a case where the processing circuit 1102A executes a program stored in the storage device 1103, an external CD-ROM, an external DVD-ROM, an external flash memory, or the like, the priority level change unit 10, the load level setting unit 14, and the display data generation unit 16 are formed by software, firmware, or a combination of software and firmware, wherein the program stored in the storage device 1103 is executed by the processing circuit 1102A. It should be noted that the functions of the priority level change unit 10, the load level setting unit 14, and the display data generation unit 16 can, for example, be implemented through the cooperation of a plurality of processing circuits.

[0080] Software and firmware can be written as a single program and stored in memory device 1103. In this case, processing circuit 1102A implements the above functions by reading and executing the program stored in memory device 1103. That is, memory device 1103 can store a program that is executed by processing circuit 1102A to achieve the functions described above.

[0081] Alternatively, the 1102B processing circuit can be dedicated hardware. That is, it can be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an integrated circuit (an application-specific integrated circuit that is an ASIC), a field-programmable gate array (FPGA), or a circuit formed from a combination of these.

[0082] In a case where the processing circuit 1102B is dedicated hardware, the priority level change unit 10, the load level setting unit 14, and the display data generation unit 16 are formed by the operation of the processing circuit 1102B. It should be noted that the functions of the priority level change unit 10, the load level setting unit 14, and the display data generation unit 16 can be implemented by separate circuits, or they can be implemented by a single circuit.

[0083] It should be noted that the functions of the priority level change unit 10, the load level setting unit 14 and the display data generation unit 16 may be partially implemented in the processing circuit 1102A, which executes a program stored in the memory device 1103, and partially implemented in the processing circuit 1102B, which is dedicated hardware.

[0084] Meanwhile, the display device 20 is equipped with the output device 1105A or the output device 1105B. Effects produced by the embodiment described above

[0085] Next, examples of the effects produced by the embodiment described above are described. It should be noted that the following description is based on the specific components shown in the embodiment described above, but these specific components can be replaced by any other specific components described as examples in this description, as long as the same effects as above are achieved. That is, in the description above, only one of the associated specific components may be described as a substitute, but the specific component described as a substitute can be replaced by any other specific component that belongs to the same category.

[0086] According to the embodiment described above, the priority level change device comprises the priority level change unit 10 and a data selection unit. Here, the data selection unit corresponds, for example, to the load level setting unit 14. A priority level and a relevance level, which indicates the relevance of the data to other data, are predefined for each data element. The priority level change unit 10 modifies the priority levels of the data. The load level setting unit 14 selects the data for which processing is to be reduced from a plurality of data elements based on the priority levels.

[0087] Based on the relevance of the priority-changed data (data whose priority level has been changed), the priority level change unit 10 also modifies the priority level of the priority-related data (data that is related to or refers to the priority-changed data). The load level setting unit 14 then selects the data for which processing is to be reduced from a plurality of elements of the data containing the priority-changed and priority-related data, again based on the priority level.

[0088] According to the embodiment described above, the priority level change device also includes the processing circuit 1102A, which executes a program, and the storage device 1103, which stores the program to be executed. When the processing circuit 1102A executes the program, the following operation is carried out.

[0089] More precisely: A priority level and a relevance level, which indicates the relevance to other data, are assigned to each data element. The priority level of the data is then changed. The data for which processing is to be reduced is then selected from a plurality of data elements based on the priority level. Here, changing the priority level means changing the priority level of the priority-related data—that is, the data that is related to or pertains to the changed priority data—based on the relevance level of the changed priority data. Similarly, selecting the data means selecting the data for which processing is to be reduced from a plurality of data elements, including the changed priority data and the priority-related data, based on the priority level.

[0090] Furthermore, according to the embodiment described above, the priority level change device includes the processing circuit 1102B, which is dedicated hardware. The processing circuit 1102B, which is dedicated hardware, then performs the following operation.

[0091] More precisely: The 1102B processing circuit, which is dedicated hardware, assigns a priority level and a relevance level, indicating its relevance to other data, to each data element. The priority level of the data is then changed. The data for which processing is to be reduced is then selected from a plurality of data elements based on the priority level. Here, changing the priority level means changing the priority level of the priority-related data—that is, the data that is related to or pertains to the changed priority level—based on the relevance level of the changed priority level of the data whose priority level has been altered.Selecting the data also involves selecting the data for which processing is to be reduced from a plurality of data elements, including priority-changed data and priority-related data, based on the priority level.

[0092] With such a configuration, the priority levels of the priority-changed data and the priority-related data are changed so that the processing of data with a high priority level can be ensured, while the processing of data with a low priority level is reduced.

[0093] More precisely: Since the priority level of the priority-related data is also changed based on the degree of relevance to the priority-changed data, it is possible to effectively change the priority level of data that may be necessary in determining the true cause of an anomaly or predicting the next malfunction by considering the degree of relevance between data elements from different perspectives and ensuring the processing of data with a high priority level among the data including the priority-changed data and the priority-related data.

[0094] Even in a case where some other component, described as an example in the present description, is appropriately added to the above components, or in a case where some other component, not one of the above components in the present description, is appropriately added, the same effects as above can be produced.

[0095] According to the embodiment described above, the priority level change unit also includes a database for recording the priority level and relevance level of each data element. Here, the database corresponds, for example, to the priority level model management database 12. The priority level change unit 10 then modifies the priority levels of the data recorded in the priority level model management database 12. With such a configuration, the priority levels of the priority-modified data and the priority-related data are changed, ensuring the processing of data with a high priority level while reducing the processing of data with a low priority level.

[0096] Furthermore, according to the embodiment described above, the priority level model management database 12 is configured with the following: a table that stores priority levels and relevance levels that are mapped to each other; a directed graph in which each node specifies data and its priority level, and an edge between nodes specifies the relevance level; or a tree structure in which each node specifies data and its priority level, and the edge specifies the relevance level. With such a configuration, a graph database is managed so that the relationship between related data elements can be traced by nodes, and related data can be searched for more quickly. Consequently, the process of changing the priority level of priority-related data associated with priority-changed data can be performed more quickly.

[0097] According to the embodiment described above, the priority level change unit 10 also increases the change value in the priority level of priority-related data when the relevance level to the priority-changed data is higher. With such a configuration, priority-related data with a higher relevance level to the priority-changed data have a similar change value in the priority level as that of the priority-changed data, and consequently, the processing of related important data can be carried out without malfunction.

[0098] According to the embodiment described above, the load-level setting unit 14 further selects the data for which processing is to be reduced based on the priority levels of the data associated with the respective data elements. With such a configuration, the following applies: Even among elements of reduced-processing data that have the same priority level, related reduced-processing data with the higher priority level are added to the processing targets, so that the data excluded from the normal processing targets and for which processing is to be reduced can be selected with high accuracy.

[0099] Relevance levels can also be modified according to the embodiment described above, based on external input or the degree of similarity of the change trend in the corresponding data. Such a configuration can improve the accuracy of the relevance levels.

[0100] Furthermore, according to the embodiment described above, the priority level change system comprises a first database, the priority level change unit 10, the load level setting unit 14, a second database, and a display unit. Here, the first database corresponds, for example, to the priority level model management database 12. Similarly, the second database corresponds, for example, to the monitoring data management database 18. Furthermore, the display unit corresponds, for example, to the display device 20. Here, a priority level and a relevance level, which indicates the relevance of the data to other data, are predefined for each data element.

[0101] The priority level model management database 12 records the priority levels and relevance grades of the respective data elements. The priority level change unit 10 modifies the priority levels of the data recorded in the priority level model management database 12. The load level setting unit 14 selects the data for which processing is to be reduced from a plurality of data elements based on the priority levels. The monitoring data management database 18 records each data element. The display device 20 captures the data, excluding the selected data, from the monitoring data management database 18 and displays the captured data.

[0102] Here, based on the relevance level of the priority-changed data (data whose priority level has been changed), the priority level change unit 10 modifies the priority level of the priority-related data (data that is related to or pertains to the priority-changed data). The load level setting unit 14 also selects the data for which processing is to be reduced from a plurality of elements of the data containing the priority-changed and priority-related data, again based on the priority level.

[0103] With such a configuration, the priority levels of priority-changed data and priority-related data are modified, ensuring the processing of high-priority data while reducing the processing of low-priority data. Artificial intelligence (AI) can be used to learn the tendency of user inputs and to determine whether a priority level change should be made permanent, thus automating dynamic priority level changes. As a result of using AI to learn from large datasets when determining priority level changes, the accuracy of these changes can be improved. Furthermore, AI can be deployed in a cloud environment.

[0104] According to the embodiment described above, a priority level and a relevance level, which indicates the relevance to other data, are specified for each data element by a priority level change procedure. The priority level of the data is then changed. The data for which processing is to be reduced is then selected from a plurality of data elements based on the priority level. Here, changing the priority level means changing the priority level of the priority-related data, which are the data that are related to or refer to the priority-changed data, based on the relevance level of the priority-changed data, which are the data whose priority level has been changed.Selecting the data also involves selecting the data for which processing is to be reduced from a plurality of data elements, including priority-changed data and priority-related data, based on the priority level.

[0105] With such a configuration, the priority levels of the priority-changed data and the priority-related data are changed so that the processing of data with a high priority level can be ensured, while the processing of data with a low priority level is reduced.

[0106] It should be noted that in a case where there are no special restrictions, the order in which the respective processes are carried out can be changed.

[0107] Even in a case where some other component, described as an example in the present description, is appropriately added to the above components, or in a case where some other component, not one of the above components in the present description, is appropriately added, the same effects as above can be produced. Modifications of the embodiment described above

[0108] In the embodiment described above, the dimensions, shapes, relative positional relationships, implementation conditions, and the like of the respective components are also described in some cases. However, these are in all aspects only an example and are not limiting.

[0109] Therefore, it is assumed that numerous modifications and equivalents, examples of which are not shown, are within the scope of the invention described in the present description. For example, a case in which at least one component is deformed and a case in which at least one component is added or omitted are included.

[0110] Furthermore, in a case where the above embodiment teaches that “one” component is included, “one or more” components may also be added, as long as no contradiction arises.

[0111] Furthermore, the descriptions in the present invention refer to the present invention for all purposes, and none of them are considered to be conventional technology.

[0112] Each of the components described above in the embodiment is also assumed to be software, firmware, or corresponding hardware. In the case of software, each component is referred to as a "unit" or the like. In the case of hardware, each component is referred to as a "processing circuit" or the like. Reference symbol list 1 Monitoring and control system 2 Monitoring and control device 5 priority level 10 Priority Level Change Unit 12 Priority Level Model Management Database 14 Load level adjustment unit 16 Display data generation unit 18 Monitoring Data Management Database 20 Display device 100 Priority Level Change Command 1102A Processing circuit 1102B Processing circuit 1103 Storage device 1105A Output device 1105B Output device QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2020 - 28 005 A

[0003]

Claims

[1] Priority level change device that changes a priority level related to the processing of a plurality of data elements, where the priority level of the data and a relevance level, which indicates the relevance of the data to another element of the data, are specified for each element of the data, the priority level change device has the following features: a priority level change unit that changes the priority level of the data; and a data selection unit that selects the data for which processing is to be reduced from a plurality of data elements based on the priority level, where the priority level change unit changes the priority level of the priority-related data, which are the data that belong to or relate to the priority-changed data, based on the relevance level of the priority-changed data, which are the data whose priority level has been changed, and The data selection unit selects the data for which processing is to be reduced from a plurality of elements of the data, which contain the priority-modified data and the priority-related data, based on the priority level. [2] Priority level change device according to claim 1, further comprising: a database that records the priority level and relevance degree of each element of the data, where the priority level change unit changes the priority level of the data stored in the database. [3] Priority level change device according to claim 2, wherein the database is formed with one of the following: a table that stores the priority level and the relevance level associated with each other; a directed graph in which each node specifies the data and the priority level and an edge between the nodes specifies the relevance level; or a tree structure in which each of the nodes specifies the data and the priority level and the edge specifies the relevance level. [4] Priority level change device according to any one of claims 1 to 3, wherein the priority level change unit increases the change value in the priority level of the priority-related data when the relevance level to the priority-changed data is higher. [5] Priority level changing device according to any one of claims 1 to 4, wherein the data selection unit changes the data for which processing is to be reduced on the basis of the priority level of the data associated with each element of the data. [6] Priority level change device according to any one of claims 1 to 5, wherein the relevance level can be changed on the basis of an external input or a degree of similarity of a change tendency in a corresponding element of the data. [7] Priority level change system that changes a priority level related to the processing of a plurality of data elements, where the priority level and a relevance level, which indicates the relevance of the data to another element of the data, are specified for each element of the data, the priority level change system includes the following: a first database that records the priority level and relevance degree of each element of the data; a priority level change unit that changes the priority level of the data stored in the first database; a data selection unit that selects the data for which processing is to be reduced from a plurality of elements of the data based on the priority level; a second database that records each element of the data; and a display unit that captures the data excluding the selected data from the second database and displays the captured data, where the priority level change unit changes the priority level of the priority-related data, which are the data that belong to or relate to the priority-changed data, based on the relevance level of the priority-changed data, which are the data whose priority level has been changed, and The data selection unit selects the data for which processing is to be reduced from a plurality of elements of the data, which contain the priority-modified data and the priority-related data, based on the priority level. [8] Priority level change procedure for changing a priority level associated with the processing of a plurality of data elements, where the priority level and a relevance level, which indicates the relevance to another element of the data, are specified for each element of the data, the priority level change procedure includes the following: Changing the priority level of the data; and Selecting the data for which processing should be reduced from a plurality of data elements, based on the priority level, where Changing the priority level is a change in the priority level of priority-related data, which are the data that relate to the priority-changed data, based on the relevance level of the priority-changed data, which are the data whose priority level has been changed, and Selecting the data is the selection of the data for which processing is to be reduced, from a plurality of elements of the data including priority-changed data and priority-related data based on the priority level.

Images