Correlation analysis system, integrated system, correlation analysis method, correlation analysis program

Abstract

This system automates the generation of information showing the interrelationships between objects and other elements present at a given site, using relatively simple processing. [Solution] The correlation event detection unit 1900 detects correlation events based on each of the device data 182. The correlation event processing unit 120 updates correlation information 112 for managing the correlation strength, which is the strength of the correlation 162 between devices 172, based on the correlation event, and also determines the occurrence or disappearance of a derivative from the correlation 162 to a device group relationship 164 or a group interrelationship 165 based on the correlation strength. The derivative occurrence / deletion event processing unit 121 updates device group relationship information 114 for managing the presence or absence of a device group relationship 164, and updates group interrelationship information 115 for managing the presence or absence of a group interrelationship 165, based on the occurrence or disappearance of the derivative.

Description

Technical Field

[0001] The present disclosure relates to a technology for grasping the situation at the site where a plurality of devices such as sensors are present, using the plurality of devices.

Background Art

[0002] Conventionally, "digitalization of the site" has been studied. For example, after installing a plurality of devices such as sensors at various sites such as a site for manufacturing products or a site for inspecting products, it has been studied to grasp the situation at the site based on the information obtained from the devices. In addition, based on the situation at the site, it has also been studied to give instructions for controlling the site to the devices and equipment present at the site.

[0003] As a prior art document regarding grasping the situation at the site, for example, there is Patent Document 1. Patent Document 1 discloses a technique for detecting changes in a manufacturing site system where a plurality of manufacturing machines and a plurality of programmable logic controllers (PLCs) are present. In Patent Document 1, a behavior monitor acquires behavior data from the manufacturing site system. The behavior monitor stores the processed result in a repository. The rearrangement detection unit compares the data acquired from the repository with the data acquired from the arrangement pattern repository to detect the rearrangement of manufacturing machines in the consistent site system. When the rearrangement detection unit detects a rearrangement or the like, it transmits a rearrangement notification to the asset manager. When the asset manager receives the rearrangement notification, it updates the information held in the asset repository. The information held in the asset repository indicates the hierarchical relationship between the plurality of manufacturing machines and the plurality of PLCs present in the manufacturing site system.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

[0005] Factors that shape the site conditions include the equipment present at the site, the processes carried out there, the workers engaged in the work, and devices (such as sensors) that collect information about the equipment, processes, and workers. In a work site, there may be cases where the number of equipment, processes, workers, and devices is large, or where equipment, processes, workers, and devices are added or removed, or where the relationships between equipment, processes, workers, and devices change. For example, if the work site is large in scale, or if there are many processes handled on site, or if the content of the processes is complex, the number of equipment, processes, workers, and devices on site will increase. If the work site is designed to flexibly respond to changes in the external environment from the perspective of the work site, or changes in the internal environment of the work site, then equipment, processes, workers, and devices may be added or removed, or the relationships between equipment, processes, workers, and devices may change. In cases like those described above, manually understanding the interrelationships between equipment, processes, workers, and devices on-site, and preparing information to illustrate those relationships, can be extremely time-consuming in order to achieve "digitalization of the workplace."

[0006] For example, if we consider a scenario where the work site needs to be adapted to flexibly respond to changes in the external environment as seen from the site, or changes in the internal environment of the site, the following problems may arise if preparing information that shows the interrelationships between equipment, processes, workers, and devices at the site remains extremely time-consuming. Firstly, if prioritizing the implementation of changes on-site leads to delays in preparing information that shows the interrelationships between equipment, processes, workers, and devices on-site, then there will be a period during which the workplace cannot adapt to the "digitalization of the workplace" after the changes. Secondly, if changes to the workplace are only implemented after information showing the interrelationships between equipment, processes, workers, and devices in the changed workplace is prepared, then changes to the workplace that respond to changes in the external environment from the perspective of the workplace, as well as changes in the internal environment of the workplace, will not be implemented quickly.

[0007] As already mentioned, the prior art disclosed in Patent Document 1 detects changes in a manufacturing site system and keeps the information held in an asset repository, which represents the hierarchical structure of multiple manufacturing machines and multiple PLCs present in the manufacturing site system, up to date. However, it is presumed that the prior art disclosed in Patent Document 1 involves organizing information about the relationships between multiple manufacturing machines and multiple PLCs within the manufacturing site system in order to prepare behavioral data. In other words, it is presumed that there is complexity in the processing on the manufacturing site system side. Furthermore, the prior art disclosed in Patent Document 1 does not clearly explain how to handle the addition or removal of manufacturing machinery and other components in a manufacturing site system. Furthermore, the prior art disclosed in Patent Document 1 is essentially about managing the interrelationships between manufacturing machines and PLCs present in a manufacturing site system, and it is difficult to say that it is intended to manage various devices or workers. In addition, the prior art disclosed in Patent Document 1 compares data obtained from the repository with data obtained from the deployment pattern repository, and updates the information held in the asset repository if the comparison results do not match. Therefore, the processing load required to keep the information held in the asset repository up-to-date is large.

[0008] Based on the above, one of the purposes of this disclosure may be to automate the generation of information showing the interrelationships between objects and other things present at a site in order to understand the situation at the site where multiple devices are present, using a relatively simple process, and to enable the generation of such information in a flexible manner in response to changes at the site. [Means for solving the problem]

[0009] To achieve at least one of the above objectives, the features that this disclosure may have include, for example, the following: One of the disclosed features is a correlation analysis system. The correlation analysis system includes a correlation event detection unit, a correlation event processing unit, and a derivative occurrence / disappearance event processing unit. The correlation event detection unit detects strong correlation events, which are events that suggest the existence of a correlation between devices, or weak correlation events, which are events that suggest the absence of a correlation between devices, based on the device data obtained from each device. The correlation event processing unit updates correlation information for managing the correlation strength, which is the strength of the correlation between devices, based on the detected strong correlation event or weak correlation event. Based on the correlation strength between devices, the correlation event processing unit determines whether a derivative has occurred or disappeared from the correlation between devices. Here, the derivative is a device group derivative between a group and a device, or a group mutual derivative between groups. The derivative occurrence / disappearance event processing unit updates device group derivative information for managing the presence or absence of a device group derivative, based on the determined occurrence or disappearance of the derivative. The derivative occurrence / destruction event processing unit updates group interrelationship information to manage the presence or absence of group interrelationships based on the determined occurrence or destruction of derivatives. [Effects of the Invention]

[0010] As described above, this disclosure manages correlation strength, which is the strength of the correlation between devices, based on each of the device data obtained from each device. Based on the correlation strength between devices, this disclosure determines the occurrence or disappearance of device group relationships, which are relationships between groups and devices, or group relationships between groups. In other words, this disclosure enables the generation of information indicating correlations, device group relationships, and group interrelationships, which are included in the relationships between objects and other things present in the field, through relatively simple processing based on device data. Furthermore, even when devices are installed or removed at the site, this disclosure can update information indicating correlations, device group relationships, and group interrelationships at any time based on device data output from the devices being installed or removed. Furthermore, if the relationships between objects and other elements present at the site change, this disclosure can track the relationships between objects and other elements at the site after the change by updating information indicating correlation, device group relationships, and group interrelationships based on device data at the site after the change.

[0011] Based on the above, this disclosure enables the automation of information generation through relatively simple processing when preparing information that shows the interrelationships between objects and other things present at a site in order to grasp the situation at the site where multiple devices are present, and enables the generation of such information in a flexible manner in response to changes at the site.

[0012] Correlation analysis methods and programs that achieve the same results as the correlation analysis system described above can also achieve the same effects and benefits. Furthermore, integrated systems that encompass the correlation analysis system can also achieve the same effects and benefits. In the case of a program, costs are often reduced. Design changes related to processing are also easier to implement in a program. Any other features that this disclosure may possess, and the effects corresponding to such features, are disclosed in this specification, claims, or drawings. [Brief explanation of the drawing]

[0013] [Figure 1] The basic functional configuration of the embodiments disclosed herein is shown. [Figure 2]Examples of correlation and relevance are shown. [Figure 3] The overall configuration is shown. [Figure 4] The functional configuration involved in device installation is shown. [Figure 5] The functional configuration involved in the detection or management of correlation and relevance is shown. [Figure 6] The functional configuration involved in the construction and modification of an application is shown. [Figure 7] The functional configuration related to application execution is shown. [Figure 8] The device management information table is shown. [Figure 9] The group management information table is shown. [Figure 10] The motion detection information table is shown. [Figure 11] The motion time information table is shown. [Figure 12] The correlation information table is shown. [Figure 13] The correlation information table is shown. [Figure 14] The device group relevance information table is shown. [Figure 15] The group mutual relevance information table is shown. [Figure 16] The derived prohibition information table is shown. [Figure 17] The device group relevance prohibition information table is shown. [Figure 18] The group mutual relevance prohibition information table is shown. [Figure 19] The processing of the correlation event detection unit is shown. [Figure 20] The processing of the strong correlation event processing unit is shown. [Figure 21] The processing of the derived occurrence event processing unit is shown. [Figure 22] The processing of the device group relevance information derived occurrence time update unit is shown. [Figure 23] The processing of the group mutual relevance information derived occurrence time update unit is shown. [Figure 24] The processing of the weak correlation event processing unit is shown. [Figure 25] This shows the processing performed by the derived event termination processing unit. [Figure 26] This shows the processing of the device group relationship information derivation and deletion update section. [Figure 27] This shows the processing of the update section when group interrelationship information is derived and then deleted. [Figure 28] This shows the fixed settings screen. [Figure 29] This shows the parameter settings screen. [Figure 30] This shows the low-code development environment screen. [Figure 31] This shows the device search screen. [Figure 32] This shows the processing of the device group relationship information derivation and update section. [Figure 33] This shows the processing of the update unit when group interrelationship information is derived. [Figure 34] This shows a simplified processing method for the derived disappearance event handling section. [Figure 35] This shows variations of the functional configuration involved in building and modifying applications. [Figure 36] This shows the computer architecture. [Modes for carrying out the invention]

[0014] Embodiments of this disclosure will be described in detail below with reference to the drawings. The embodiments described below are not intended to limit the scope of the claims, and not all elements and combinations thereof described in the embodiments are necessarily essential to the solutions of this disclosure. This disclosure can also be implemented in various other forms. Each of the systems (e.g., correlation analysis systems or integration systems), devices, or functional units of this disclosure may be a single hardware unit, or it may be divided into multiple parts that work together to perform their respective functions. Several systems, devices, or functional units may be integrated in hardware. Each of the systems, devices, or functional units may be implemented by having a computer execute software (a program, e.g., a correlation analysis program) (as shown in Figure 36). Some of the functions of the systems, devices, or functional units may be implemented in hardware (e.g., hardwired logic or field-programmable gate arrays (FPGAs)), and the remaining functions may be implemented by executing software (programs). All of the functions of each of the systems, devices, or functional units may be implemented in hardware. Some or all of the steps shown in the flowcharts, etc., described in this disclosure may be implemented in hardware. One or more systems, devices, or functional units of the Disclosure may be implemented from one or more hardware resources. For this purpose, each of the systems, devices, or functional units of the Disclosure may be implemented virtually. For example, virtual computer or virtual container techniques may be used. The program is not limited to any particular type or form. Furthermore, the program may initially be recorded in a compressed format. When a system, device, functional unit, or part of the functionality of a functional unit is implemented by having a computer execute software (program), the implemented system, device, functional unit, or part of the functionality of the functional unit does not need to be implemented at all times. In other words, it is sufficient for the system, device, functional unit, or part of the functionality of the functional unit to be implemented only when the processing provided by that system, device, functional unit, or part of the functionality of the functional unit is needed. Reference numerals used in multiple drawings indicate that they are equivalent. In flowcharts, rectangular boxes indicate processing steps, and hexagonal boxes indicate conditional branching steps. In flowcharts, "step" is abbreviated as "S". The displays or outputs shown in the drawings are merely examples. The manner of display or output may be arbitrary, as long as it is sufficient to achieve the purpose of this disclosure.

[0015] 1. Basic Functional Configuration (Figures 1 and 2) Figure 1 shows the basic functional configuration 100 (and the information handled) of the correlation analysis system 101 according to an embodiment of this disclosure. Not all functional configurations shown in Figure 1 are mandatory. Furthermore, it is not prohibited for functional configurations other than those shown in Figure 1 to exist. In Figure 1 (and Figures 4, 5, 6, 7, and 35), solid rectangles with "part" in their name indicate functional parts, and dotted rectangles indicate the information (data) handled.

[0016] 1.1. Correlation analysis system handles devices, groups, correlations, and relationships. The correlation analysis system 101 of the embodiment of this disclosure seeks information indicating relationships between devices 172 and groups 175, which are objects present at the site. The device 172 at the bottom of Figure 1 may collect information indicating the situation on site and output it as device data 182. For example, each of the devices 172 shown in Figure 1 may be a camera, accelerometer, speed sensor, wearable terminal, router, or programmable logic controller (PLC), as shown in the device management information table 800 in Figure 8. The group 175 at the bottom of Figure 1 may be objects or other things present on-site whose situations are observed by device 172, or there may be some kind of hierarchical relationship between the groups 175. For example, the factory, process, or workers shown in the group management information table 900 in Figure 9 may each be a group 175 shown in Figure 1.

[0017] The correlation 162, indicated by the thick, bidirectional arrows at the bottom of Figure 1, may have different strengths (correlation strengths) for each combination of devices 172. For example, two devices 172 may be acquiring information about the same object at the site, objects that are close to each other at the site, or objects that are related to each other at the site. In such cases, it can be expected that the correlation will be high (correlation strength will be high) between the device data 182 output by each of the two devices 172.

[0018] In the lower part of Figure 1, the relationships indicated by the white, one-way arrows may include the device group relationship 164 between device 172 and group 175, and the group interrelationship 165 between groups 175 themselves. For example, if a device 172 is a camera and a group 175 is a group of workers, there may be a situation where the camera takes images of the workers and collects information about them. In such a situation, a device group association 164 may exist between the device 172, which is the camera, and the group 175, which is the group of workers. Furthermore, for example, if one group 175 is workers and another group 175 is a process (for example, one of the production processes (or production lines) or inspection processes (or inspection lines) of a product on the factory floor), there may be a situation where the workers are engaged in the work of that process. In such a situation, a group relationship 165 may exist between the group 175 that is the workers and the other group 175 that is the process. In this case, a hierarchical relationship (parent-child relationship, inclusion relationship) may be established between the two groups 175 linked by one group relationship 165. For example, if multiple workers can be engaged in one process, the process may be set as the relative higher position in the group relationship 165 (parent in a parent-child relationship, or the inclusive side in an inclusion relationship).

[0019] Figure 2 provides more specific examples of the devices 172, groups 175, correlations between devices 162 (and their derivations), device group relationships 164, and group relationships 165 shown at the bottom of Figure 1. The top of Figure 2 shows a situation where worker 1 is engaged in process 1 (proc1) and worker 2 is engaged in process 2 (proc2). The bottom of Figure 2 shows a situation where, after worker 1 has moved, both worker 1 and worker 2 are engaged in process 2 (proc2).

[0020] Figure 2 shows examples of device 172, including camera 1 (cam1), camera 3 (cam3), accelerometer 1 (acc1), wearable device 1 (wear1), camera 2 (cam2), accelerometer 2 (acc2), and wearable device 2 (wear2). Also in Figure 2, examples of group 17 are shown, including factory 1 (factory1), process 1 (proc1), worker 1 (worker1), process 2 (proc2), and worker 2 (worker2).

[0021] In Figure 2, among the correlations 162 between devices 172, only those correlations 162 that have derived into device group relationships 164 or group interrelationships 165 (due to reasons such as a relatively high correlation strength) are shown with dotted lines. For example, in the upper part of Figure 2, the correlation 162 between camera 3 (cam3) and accelerometer 1 (acc1), the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1), and the correlation 162 between accelerometer 2 (acc2) and wearable device 2 (wear2) are shown by dotted lines. From these correlations 162, the device group correlation 164 or group inter-correlation 165 are derived. Furthermore, in the lower part of Figure 2, which shows the movement of worker 1, the correlations 162 between camera 3 (cam3) and accelerometer 1 (acc1), the correlations 162 between accelerometer 2 (acc2) and wearable device 2 (wear2), and the correlations 162 between camera 2 (cam2) and wearable device 1 (wear1) are shown by dotted lines. From these correlations 162, derivations of device group relationships 164 or group interrelationships 165 occur.

[0022] In Figure 2, among the existing device group relationships 164, those that are fixedly set regardless of the correlation 162 (or fixedly set by the fixed setting units 378 and 388 described later; hereinafter referred to as "fixed type device group relationships") are shown as undirected solid line segments. For example, in Figure 2, fixed-type device group relationships are set between process 1 (proc1) and camera 1 (cam1), between process 1 (proc1) and acceleration sensor 1 (acc1), between worker 1 (worker1) and wearable device 1 (wear1), between process 2 (proc2) and camera 2 (cam2), between process 2 (proc2) and acceleration sensor 2 (acc2), and between worker 2 (worker2) and wearable device 2 (wear2). Note that it is arbitrary to set which of the existing device group relationships 164 will be designated as fixed-type device group relationships.

[0023] In Figure 2, among the existing device group relationships 164, those that are established by a derivation from any of the correlations 162 (hereinafter sometimes referred to as "derived-type device group relationships") are shown as undirected dashed-dotted line segments. For example, in the upper part of Figure 2, derived type device group relationships exist between process 1 (proc1) and camera 3 (cam3), between process 1 (proc1) and wearable device (wear1), between worker 1 (worker1) and accelerometer 1 (acc1), between worker 1 (worker1) and camera 3 (cam3), between process 2 (proc2) and wearable device 2 (wear2), and between worker 2 (worker2) and accelerometer 2 (acc2). Furthermore, in the lower part of Figure 2, which shows the movement of worker 1, derived type device group relationships exist between process 1 (proc1) and camera 3 (cam3), between process 2 (proc2) and wearable device 2 (wear2), between worker 2 (worker2) and acceleration sensor 2 (acc2), between process 2 (proc2) and wearable device 1 (wear1), and between worker 1 (worker1) and camera 2 (cam2).

[0024] In Figure 2, among the existing group interrelationships 165, those that are fixedly set regardless of their correlation 162 (or fixedly set by the fixed setting units 378 and 388 described later; hereinafter referred to as "fixed-type group interrelationships") are shown as solid line segments in one direction. For example, in Figure 2, there are fixed-type group relationships between factory 1 (relatively higher) and process 1 (relatively lower), and between factory 1 (relatively higher) and process 2 (relatively lower). Note that the designation of any of the 165 existing group relationships as fixed-type relationships can be arbitrarily determined.

[0025] In Figure 2, among the existing group interrelationships 165, those that are established by a derivation from any of the correlations 162 (hereinafter sometimes referred to as "derivative type group interrelationships") are shown by a one-way dashed line segment. For example, in the upper part of Figure 2, there are derived group relationships 165 between process 1 (proc1), which is relatively higher in rank, and worker 1, which is relatively lower in rank, and between process 2 (proc2), which is relatively higher in rank, and worker 2, which is relatively lower in rank. Furthermore, in the lower part of Figure 2, which shows the movement of worker 1, there are derived group relationships 165 between process 2 (proc1), which is relatively higher in rank, and worker 2, which is relatively lower in rank, and between process 2 (proc2), which is relatively higher in rank, and worker 1, which is relatively lower in rank.

[0026] 1.2. Basic Functional Configuration of the Correlation Analysis System and the Basic Content of the Information It Handles To control the occurrence or disappearance of derivatives from correlation 162, as illustrated in Figure 2, and the existence or non-existence of device group relationships 164 and group interrelationships 165 associated with the occurrence or disappearance of derivatives, the correlation analysis system 101 has the functional configuration shown at the top of Figure 1 and handles the information shown at the top of Figure 1. As shown in Figure 1, the correlation analysis system 101 may include a correlation event detection unit 1900, a correlation event processing unit 120, and a derivative occurrence / disappearance event processing unit 121.

[0027] 1.2.1. Correlation Event Detection Unit, Strong Correlation Events, and Weak Correlation Events The correlation event detection unit 1900 detects strong correlation events or weak correlation events based on the device data 182 obtained from each of the devices 172. A strong correlation event is an event that suggests the existence of a correlation 162 between the devices 172. A weak correlation event is an event that suggests the absence of a correlation 162 between the devices 172. For example, consider a case where one device 172 and another device 172 acquire information about the same object present in the field, objects present in close proximity to each other in the field, and objects present in the field that are related to each other, and output the acquired information as device data 182. In such a case, events often occur that suggest the existence of some kind of correlation 162 between the device data 182 output from the first device 172 and the device data 182 output from the other device 172. For example, if both the first device 172 and the other device 172 detect the movement of an object, it can be assumed that the device data 182 output from the first device 172 and the device data 182 output from the other device 172 will have similar timings and time periods for detecting movement. For example, consider a case where one device 172 and another device 172 acquire information about unrelated objects present in the field and output the acquired information as device data 182. In such a case, events often occur that suggest the absence of correlation 162 between the device data 182 output from the first device 172 and the device data 182 output from the other device 172. For example, if both the first device 172 and the other device 172 detect the movement of objects, it can be assumed that the device data 182 output from the first device 172 and the device data 182 output from the other device 172 will have very little similarity in terms of the time or period in which they detect movement. The correlation event detection unit 1900 notifies the correlation event processing unit 120 when it detects a strong correlation event or a weak correlation event for each combination of devices 172.

[0028] 1-2-2. Correlation Event Processing, Correlation Strength, Derivative Occurrence, and Derivative Disappearance The correlation event processing unit 120 updates the correlation information 112, which is the strength of the correlation 162 between devices 172, based on the strong or weak correlation events detected by the correlation event detection unit 1900. For example, as shown in Figures 12 and 13, the correlation information 112 may manage a correlation strength value 1202 for each combination of devices 172. The correlation event processing unit 120 may update the correlation strength value 1202 for that particular combination of devices 172 in a direction that indicates a strong correlation 162 when a strong correlation event is detected for a particular combination of devices 172. On the other hand, the correlation event processing unit 120 may update the correlation strength value 1202 for that particular combination of devices 172 in a direction that indicates a weak correlation 162 when a weak correlation event is detected for a particular combination of devices 172. Furthermore, as shown in Figures 12 and 13, for example, the correlation information 112 may be managed by a correlation information table 1200 (or 1300). In each correlation information record, which is a record in the correlation information table 1200 (or 1300), the correlation strength (correlation strength value 1202) for combinations of devices 172 may be managed.

[0029] The correlation event processing unit 120 determines whether a correlation 162 between devices 172 has evolved into an association based on the correlation strength (correlation strength value 1202) between the devices 172. Here, the association may be a device group association 164 between group 175 and device 172, or a group inter-association 165 between groups 175. For example, as shown in Figures 12 and 13, the correlation information 112 may manage a derivation flag 1203 for each combination of devices 172, which is information indicating the occurrence or disappearance of a derivation from the correlation 162 to a relationship (device group relationship 164, or group interrelationship 165). (Alternatively, the correlation information 112 may not include a derivation flag 1203, and the correlation event processing unit 120 may simply transmit the occurrence or disappearance of a derivation to the derivation occurrence / disappearance event processing unit 121.) For example, the correlation event processing unit 120 may determine that a correlation 162 has been derived from the correlation 162 to a relationship (device group relationship 164, or group interrelationship 165) when the correlation strength between devices 172 (correlation strength value 1202) satisfies certain conditions (for example, the condition that it is equal to or greater than the derivation occurrence threshold (t1) shown in Figure 29), indicating that the correlation 162 is strong to a certain extent. On the other hand, the correlation event processing unit 120 may determine that the derivation from the correlation 162 to the relationship (device group relationship 164, or group interrelationship 165) disappears when the correlation strength between devices 172 (correlation strength value 1202) satisfies another certain condition (for example, the condition that it is less than or equal to the derivation extinction threshold (t2) shown in Figure 29, or the condition that it is less than or equal to the derivation extinction threshold (t2)), indicating that the correlation 162 is somewhat weak. When the correlation event processing unit 120 determines that a derivative has occurred or has disappeared, it notifies the derivative occurrence / disappearance event processing unit 121 of this fact. Alternatively, the derivative occurrence / disappearance event processing unit 121 may detect that the correlation event processing unit 120 has determined that a derivative has occurred or has disappeared by detecting a change in the value of the derivative flag 1203 included in the correlation information 112. Furthermore, the correlation event processing unit 120 in Figure 1 corresponds to the strongly correlation event processing unit 2000 and the weakly correlation event processing unit 2400 in the detailed functional configuration shown in Figure 5.

[0030] 1.2.3. Changes in the existence or non-existence of the relationship between the derived occurrence / disappearance event processing unit and the event processing unit. The derivative occurrence / disappearance event processing unit 121 updates the device group relationship information 114 for managing the presence or absence of device group relationships 164 based on the occurrence or disappearance of derivatives determined by the correlation event processing unit 120. The derivative occurrence / disappearance event processing unit 121 also updates the group interrelationship information 115 for managing the presence or absence of group interrelationships 165 based on the occurrence or disappearance of derivatives determined by the correlation event processing unit 120.

[0031] If a correlation 162 leads to an association (device group association 164, or group inter-association 165) for a specific combination of devices 172, then a new device group association 164 or group inter-association 165 may come into existence that did not exist before. For example, when the situation changes from the one shown in the upper part of Figure 2 to the one shown in the lower part of Figure 2, the correlation strength value of the correlation 162 between camera 2 (cam2) and wearable device 1 (wear1) increases to 1202, causing a derivation of the correlation 162 into a relationship (device group relationship 164, or group interrelationship 165). As a result of this derivation, in the lower part of Figure 2, a new device group relationship 164 is established between process 2 (proc2) and wearable device (wear1), and between worker 1 (worker1) and camera 2 (cam2). Also, as a result of this derivation, in the lower part of Figure 2, a group interrelationship 165 is established between process 2 (proc2) and worker 1 (worker1).

[0032] Furthermore, if the derivation from correlation 162 to association (device group association 164, or group inter-association 165) disappears for a particular combination of devices 172, then the device group association 164 or group inter-association 165 that previously existed may cease to exist. For example, when the situation changes from the one shown in the upper part of Figure 2 to the one shown in the lower part of Figure 2, the correlation strength value 1202 of the correlation 162 between camera 3 (cam3) and wearable terminal 1 (wear1) decreases, causing the derivation of the relationship (device group relationship 164, or group interrelationship 165) from the correlation 162 to disappear. With the disappearance of this derivation, the device group relationships 164 that existed between process 1 (proc1) and wearable terminal (wear1), between worker 1 (worker1) and acceleration sensor 1 (acc1), and between worker 1 (worker1) and camera 3 (cam3) disappear in the lower part of Figure 2. Also, with the disappearance of this derivation, the group interrelationship 165 that existed between process 1 (proc1) and worker 1 (worker1) disappears in the lower part of Figure 2.

[0033] The derived occurrence / disappearance event processing unit 121 determines the existence or non-existence of the device group relationship 164 and the existence or non-existence of the group inter-relationship 165 as described above, and reflects the result of that determination in the device group relationship information 114 and the group inter-relationship information 115. As shown in Figure 14, device group relationship information 114 may be managed by a device group relationship information table 1400. In each device group relationship information record, which is a record in the device group relationship information table 1400, information identifying the correlation 162 that formed the basis for the existence of the device group relationship 164 and other device group relationships 164 (or information identifying the original correlation 162 that led to the existence of the device group relationship 164) may be managed for each combination of device 172 and group 175. Furthermore, as shown in Figure 15, the group interrelationship information 115 may be managed by the group interrelationship information table 1500. In each group interrelationship information record, which is a record in the group interrelationship information table 1500, information identifying the correlation 162, device group relationship 164, and other group interrelationships 165 that formed the basis for the existence of the group interrelationship 165 (or information identifying the original correlation 162 that led to the existence of the group interrelationship 165) may be managed for each combination of groups 175. Furthermore, the derivative occurrence / destruction event processing unit 121 in Figure 1 corresponds to the derivative occurrence event processing unit 2100, the device group relationship information derivative occurrence update unit 2200, the group mutual relationship information derivative occurrence update unit 2300, the derivative occurrence / destruction event processing unit 2500, the device group relationship information derivative occurrence / destruction update unit 2600, and the group mutual relationship information derivative occurrence / destruction update unit 2700 in the detailed functional configuration in Figure 5.

[0034] Since the correlation analysis system 101 in the embodiment of this disclosure has the functional configuration described above, it can provide the effects shown in the [Effects of the Invention] section above (the effects shown in paragraphs

[0010] to

[0012] ).

[0035] 2. Overall configuration including the correlation analysis system 101 (Figure 3) Figure 3 shows the overall configuration 300 including the correlation analysis system 101 of the embodiment of this disclosure. Note that not all of the functional configurations shown in Figure 3 are mandatory. Furthermore, the existence of functional configurations other than those shown in Figure 3 is not prohibited.

[0036] 2.1. Site where the device is installed and the group is configured. As already explained with Figures 1 and 2, the correlation analysis system 101 handles multiple devices 172 and multiple groups 175. These multiple devices 172 and multiple groups 175 may be related to a field, as shown at the bottom of Figure 3. The bottom of Figure 3 shows a field example that generally follows the correlation and association example 200 shown in Figure 2. In the lower part of Figure 3, the workspace for process 1 (proc1) is shown in the lower left, and the workspace for process 2 (proc2) is shown in the lower right, both within a site (for example, factory 1). Robots, equipment, and devices may be present in either workspace. In either workspace, communication between robots, equipment, and devices may be conducted via a wired network, via a wireless network using base stations, or using both wireless and wired networks.

[0037] In the workspace for process 1 (proc1) shown in the lower left of Figure 3, a robot and worker 1 are located near a conveyor belt used to move the products produced or inspected in process 1 (proc1). Process 1 (proc1) may be a production line or an inspection line. Here, process 1 (proc1) and worker 1 (worker1) are treated as group 175. As shown in the group management information table 900 in Figure 9, each of the group 175 is assigned a relationship change degree 903 (or inclusion degree 904). The smaller the relationship change degree 903 (or inclusion degree 904) value, the higher the group is positioned in the hierarchical relationship among the group 175.

[0038] In the workspace for process 1 (proc1), there is a programmable logic controller 1 (PLC1) for controlling the motor that operates the belt conveyor used in process 1 (proc1). As shown in the device management information table 800 in Figure 8, the programmable logic controller 1 (PLC1) controls the operating mode of the motor that operates the belt conveyor used in process 1 (proc1), and may output an operation flag indicating the operating mode as device data 182. For example, there may be a mode in which the belt conveyor is transporting products, etc., and a mode in which the belt conveyor is stopped. Alternatively, the operating mode may be determined by the magnitude of the transport speed by the belt conveyor. Worker 1 may carry a wearable device 1. As shown in the device management information table 800 in Figure 8, the wearable device 1 may be capable of measuring its own acceleration. The wearable device 1 may output the component values ​​for each three-dimensional coordinate (X, Y, Z) of the measured acceleration as device data 182. Alternatively, the wearable device 1 may only be able to determine whether the magnitude of its own acceleration is above or above a predetermined threshold, or greater than a predetermined threshold. In that case, the wearable device 1 may output information of a flag indicating the relationship between the magnitude of its own acceleration and the predetermined threshold as device data 182. An acceleration sensor (acc1) or (although not shown in the lower left of Figure 3) a velocity sensor 1 (velo1) may be installed in the workspace of process 1 (proc1). As shown in the device management information table 800 in Figure 8, the acceleration sensor (acc1) or velocity sensor 1 (velo1) may measure the acceleration or velocity of belt conveyors, robots, equipment, and devices present in the workspace of process 1 (proc1). The acceleration sensor (acc1) or velocity sensor 1 (velo1) may output the component values ​​for each three-dimensional coordinate (X, Y, Z) of the measured acceleration or velocity as device data 182. In addition, for the acceleration or velocity of a belt conveyor, the acceleration sensor (acc1) or velocity sensor 1 (velo1) may measure the acceleration or velocity in the one-dimensional direction, which is the direction in which the belt conveyor transports products, etc., and output it as device data 182. Router 1 or switch 1 (snmp1) may be configured in the workspace of process 1 (proc1). As shown in the device management information table 800 in Figure 8, Router 1 or switch 1 (snmp1) may count the number of communication packets transmitted and received via a wired or wireless network between various robots, various equipment and various devices 172 in process 1 (proc1) based on the Simple Network Management Protocol (SNMP). Router 1 or switch 1 (snmp1) may output the measured number of packets (or communication volume) as device data 182. Cameras 1 (cam1) and 3 (cam3) may be installed in the workspace of process 1 (proc1). As shown in the device management information table 800 in Figure 8, cameras 1 (cam1) and 3 (cam3) may acquire image data. In the example in the lower left of Figure 3, cameras 1 (cam1) and 3 (cam3) will photograph the workspace of process 1 (proc1). Cameras 1 (cam1) and 3 (cam3) may output the acquired image data as device data 182.

[0039] The lower right of Figure 3 shows that the workspace for process 2 (proc2) contains a conveyor belt for moving products produced or inspected in process 2 (proc2), a robot, a worker 2 (worker2), a programmable logic controller 2 (PLC2), a wearable terminal 2 (wear2), an accelerometer 2 (acc2), a router 2 or switch 2 (snmp2), and a camera 2 (cam2). Process 2 (proc2) may be a production line or an inspection line. Process 2 (proc2) and worker 2 (worker2) are treated as group 175, just like process 1 (proc1) and worker 1 (worker1). Furthermore, the functions of the robots, equipment, and devices present in the workspace of process 2 (proc2) may be the same as those of the robots, equipment, and devices already described for the workspace of process 1 (proc1).

[0040] Figure 3 also shows worker 1 moving from the work area of ​​process 1 (proc1) to the work area of ​​process 2 (proc2). Figure 3 also shows that worker 1 moves while carrying the wearable device 1 (wear1). As already shown, the lower part of Figure 3 may represent a site including a production line or inspection line for products, etc. In such cases, embodiments of the present disclosure are useful for understanding the situation at the site including the production line or inspection line, and for understanding changes in said situation. Furthermore, embodiments of the present disclosure are also useful for controlling the site including the production line or inspection line.

[0041] 2-2. Various systems that utilize device data obtained from the field As shown at the top of Figure 3, in addition to the correlation analysis system 101 outlined using Figures 1 and 2, various other systems may exist. For the transmission and reception of information between the correlation analysis system 101, various systems, and the sites shown at the bottom of Figure 3, any type of network may be used, such as wired networks, wireless networks, local area networks (LANs), or wide area networks (WANs), and any network topology may be used. The various systems shown at the top of Figure 3, along with the correlation analysis system 101, may be collectively referred to as the integrated system 301, or the site shown at the bottom of Figure 3 may also be included in the term "integrated system 301."

[0042] At the top of Figure 3, the metadata management system 302 is shown as one of the various systems. The metadata management system 302 manages metadata about devices 172 present in the field and groups 175 set up in the field. Metadata is information that indicates the characteristics and attributes of devices 172 or groups 175. Metadata may also include information that indicates the relationships between devices 172 and groups 175, such as correlation information 112, device group relationship information 114, and group interrelationship information 115, as explained in Figure 1, and related information. The information held by the metadata management system 302 may include, for example, the device management information table 800 in Figure 8, the group management information table 900 in Figure 9, the correlation information table 1200 (or correlation information table 1300) in Figure 12 or Figure 13, the device group relationship information table 1400 in Figure 14, the group interrelationship information table 1500 in Figure 15, the derivation prohibition information table 1600 in Figure 16, the device group relationship prohibition information table 1700 in Figure 17, and the group interrelationship prohibition information table 1800 in Figure 18. The device data 182 output by device 172, and the information obtained by processing the device data 182, are mainly handled by the correlation analysis system 101, the data utilization system 304 (described later), and the data collection system 305 (described later).

[0043] The correlation information 112 (correlation information table 1200 or correlation information table 1300), device group relationship information 114 (device group relationship information table 1400), and group interrelationship information 115 (group interrelationship information table 1500), which are generated by the correlation analysis system 101 and stored in the metadata management system 302, can be used in a variety of ways. One such application is to utilize the various types of information described above in the process of building or modifying applications using device data 182 obtained from the field, as shown at the bottom of Figure 3. At the top of Figure 3, the development environment system 303 is shown as one of the various systems. When a developer 393 uses the development environment system 303 to build or modify an application, the development environment system 303 obtains information from the metadata management system 302 to identify the device 172, which is the source of information to be obtained when the application is executed. The development environment system 303 can then present the information identifying the device 172 to the developer 393. Applications built or modified by developer 393 using development environment system 303 are executed by data utilization system 304, shown at the top of Figure 3. The execution results of the applications are provided to data users 394. Depending on the input information from data users 394 to data utilization system 304, the data utilization system 304, which executes the applications, may control robots, equipment, and devices present at the site, as shown at the bottom of Figure 3. Furthermore, if the various types of information stored in the metadata management system 302 are used for purposes other than application storage and development, the development environment system 303 and data utilization system 304 shown at the top of Figure 3 may be omitted.

[0044] The correlation analysis system 101 may directly acquire device data 182 from device 172. In that case, the data acquisition system 305 shown at the top of Figure 3 may be omitted. Alternatively, a data collection system 305, shown at the top of Figure 3, may be provided, and the data collection system 305 may directly collect device data 182 from device 172. In this case, the data collection system 305 may store the device data 182 in the collection information database 355 (collection information DB) shown in Figure 4. The correlation analysis system 101 may then acquire the device data 182 from the data collection system 305.

[0045] In the upper part of Figure 3, the correlation analysis system 101, the metadata management system 302, the development environment system 303, the data utilization system 304, and the data collection system 305 are each shown as separate systems. Some or all of the systems described above may be combined into a single system. For example, the functions and information of the correlation analysis system 101 and the functions and information of the metadata management system 302 may be combined into a single system. Also, for example, the functions and information of the development environment system 303 and the functions and information of the data utilization system 304 may be combined into a single system.

[0046] 3. Computer architecture for realizing embodiments of the present disclosure (Figure 36) Figure 36 shows a computer architecture 3600 for realizing the correlation analysis system 101 of the embodiment of this disclosure. The computer architecture 3600 shown in Figure 36 may also be called an information processing device or information processing system. (Furthermore, the computer architecture 3600, which is an information processing device or information processing system, may be understood to be one that performs a correlation analysis method.) In addition, the various systems included in the integrated system 301 shown in Figure 3 may also be realized using the same computer architecture 3600 as shown in Figure 36. To realize the correlation analysis system 101, some or all of the following components may be interconnected at the interconnection unit 3611: the arithmetic processing unit 3601, the storage device 3602, the non-volatile recording medium (recording device) 3603, the external recording medium drive 3604, the input device 3606, the display or output device 3607, the communication device 3608, the external input / output port 3609, and the reading device 3610. (Note that some or all of the interconnection unit 3611 may be a network. In that case, the correlation analysis system 101 will be realized by multiple devices connected via the network.) The arithmetic processing unit 3601 may be, for example, a processor. Examples of such processors include a CPU, MPU, or GPU. Alternatively, the processor referred to herein may be any other semiconductor device that performs a predetermined process. Furthermore, the arithmetic processing unit 3601 may be one or more (micro)processors. The storage device 3602 may be, for example, memory. The non-volatile recording medium (recording device) 3603 may be, for example, non-volatile memory (e.g., flash memory) or a non-volatile disk device. The external recording medium drive 3604 may be, for example, a disk drive. The input device 3606 may be, for example, a mouse, keyboard, imaging device, sensor, touch panel, or pointing device. The display or output device 3607 may be, for example, a display, printer, or speaker. The communication device 3608 may be, for example, a communication device for wired communication or a communication device for wireless communication. The communication device 3608 may be a network interface device (NIC) that controls communication with other systems, devices, terminals, or servers according to a predetermined protocol. The interconnection unit 3611 may be, for example, a bus or a crossbar switch. (As mentioned above, part or all of the interconnection unit 3611 may be a network.)

[0047] The non-volatile recording medium (recording device) 3603 may record various programs included in the program group 3631 (for example, programs for realizing the functional configuration related to this disclosure; for example, various programs for implementing each of the functional units realized in the correlation analysis system 101; collectively, these may be called correlation analysis programs), various data groups included in the data group 3632, or information included in the various information 3633. The program group 3631 may include various programs for realizing each of the functional units designated as "units" in the functional configuration diagrams of Figures 1, 4, and 5. (The functional units in Figures 6, 7, and 35 may also be realized by program execution in a similar manner.) Some of the above programs may be integrated into a single program. Alternatively, any of the above programs may be split into multiple programs. The data group 3632 may include information (data, etc.) handled by the above-mentioned functional unit. For example, the data group 3632 may include information that constitutes each of the information groups or data groups indicated by the dotted lines in the functional configuration diagrams of Figures 1, 4, and 5. (Note that some or all of the information included in the information group or data group may be stored in the storage device 3602 (memory).) (The information groups or data groups in Figures 6, 7, and 35 may be held in a similar manner.) Alternatively, some or all of the various programs included in the program group 3631, the various information groups or data groups included in the data group 3632, or the information included in the various information 3633 may be obtained from outside the configuration shown in Figure 36.

[0048] The external storage media drive 3604 can connect to an external storage media 3605. The external storage media 3605 may be, for example, a portable recording disc (DVD, etc.), an IC card, an SD card, non-volatile memory (e.g., flash memory), or a portable hard disk. Alternatively, information similar to the various programs included in the program group 3631, the various information groups or data groups included in the data group 3632, or the information included in the various information 3633 may be transferred and stored from the external storage media 3605 to the non-volatile storage media (recording device) 3603 or the storage device 3602. The external storage media 3605 may be used to record programs and data handled in the correlation analysis system 101. The external storage media drive 3604 and the external storage media 3605 may be connected to the correlation analysis system 101 shown in Figure 36 via a network. Various programs included in program group 3631, various information groups or data groups included in data group 3632, or information included in various information 3633 may be provided via communication device 3608, external input / output port 3609, input device 3606, and read device 3610, and recorded or stored in non-volatile recording medium (recording device) 3603 or storage device 3602.

[0049] In order for the architecture of Figure 36 to function as the correlation analysis system 101, each functional unit within the correlation analysis system 101, or a part of each functional unit (performing one or a series of processes (steps)), the various programs included in the program group 3631 may be loaded into the storage device 3602 (for example, from the non-volatile recording medium (recording device) 3603). The loaded program is shown as 3621 in Figure 36. The arithmetic processing unit 3601 may then execute program 3621 (using, if necessary, various information groups or data groups included in the data group 3632 present in the non-volatile recording medium (recording device) 3603, etc., or information included in various information 3633). The execution of program 3621 realizes the function of the correlation analysis system 101, each functional unit within the correlation analysis system 101, or a part of each functional unit (performing one or a series of processes (steps)). Various buffers 3623 temporarily formed in the storage device 3602 may also be used as appropriate.

[0050] 4. Functional configuration, processing, and information of the embodiment The following describes the functional configuration, processing, and information of the integrated system 301, which includes the correlation analysis system 101, with the correlation analysis system 101 as the central focus. The following sections will broadly describe the process of installing device 172 on-site and the process of detecting or managing correlations and relationships. In addition, examples of how correlation and relationship information regarding device 172 and group 175 can be used will be described, such as when building or modifying applications.

[0051] 4.1. Functional configuration, processing, and information involved during device installation (Figure 4) This section describes the functional configuration, processes, and information involved when device 172 is installed in the integrated system 301. The functional configuration, processing, and information described below enable the device 172 to be recognized by the metadata management system 302 and the correlation analysis system 101 when it is installed on-site. The correlation analysis system 101 then acquires device data 182 output from the device 172 and can perform correlation and relationship detection using the device data 182. The metadata management system 302 can also manage information regarding the correlation and relationship detected based on the device data 182 output from the recognized device 172.

[0052] Figure 4 shows the functional configurations and information handled when device 172 is installed in the integrated system 301. Note that not all functional configurations and information shown in Figure 4 are mandatory. Furthermore, the existence of functional configurations and information other than those shown in Figure 4 is not prohibited.

[0053] 4-1-1. Functional configurations, processes, and information involved when a device is installed. In Figure 4, the device 172 newly installed at the site is labeled as device 172-NEW. Note that the device 172 already installed at the site is not shown in Figure 4. When device 172-NEW is installed at the site, information for device registration (device registration request) is input to the device registration reception unit 321, which is a functional unit of the metadata management system 302. This input of information for device registration may be performed by device 172-NEW itself to the device registration reception unit 321. Alternatively, the administrator 401 of the metadata management system 302 may input the information for device registration (device registration request) to the device registration reception unit 321 via the user interface provided by the metadata management system 302. The information for device registration (device registration request) entered into the device registration reception unit 321 may be, for example, part or all of the information that should be held in a device management information record, which is a single record (for the newly installed device 172-NEW) in the device management information table 800 shown in Figure 8.

[0054] Figure 8 shows the device management information table 800 of the metadata management system 302. The device management information table 800 has a device management information record for each of the 172 devices installed on site, which is a record in the device management information table 800. The device management information record may have some or all of the following items: device ID 801, device name 802, device data content 803, and URL 804 for obtaining device data. The example in Figure 8 assumes that when the correlation analysis system 101 and the data utilization system 304 acquire device data 182, they access a URL set for each device 172. When the correlation analysis system 101 and the data utilization system 304 acquire device data 182 and directly access device 172, accessing the URL indicated in the device data acquisition URL 804 is direct access to device 172. On the other hand, when the correlation analysis system 101 and the data utilization system 304 acquire device data 182 and access the collection information database 355 (collection information DB) within the data collection system 305, accessing the URL indicated in the device data acquisition URL 804 is access to the data collection system 305. If a method other than URL-based access is used to obtain device data 182, the device management information record may have an access setting information field that conforms to the chosen method for obtaining device data 182, instead of the field for the URL 804 where the device data is obtained.

[0055] In Figure 8, device 172, whose device name 802 is "camera 1", is assigned the device ID 801 "cam1". Furthermore, the content of device data 182 output from device 172, whose device name 802 is "camera 1", is "image data from camera 1". In Figure 8, device 172, whose device name 802 is "Accelerometer 1 (or Velocity Sensor 1)", is assigned the device ID 801 "acc1 (or velo1)". The content of the device data 182 output from device 172, whose device name 802 is "Accelerometer 1 (or Velocity Sensor 1)", is "Accelerometer or velocity of each XYZ coordinate in the belt conveyor, robot, equipment, or device for process 1. Units are G, etc. Updated every 0.1 seconds." In Figure 8, device 172, whose device name 802 is "Wearable Terminal 1," is assigned the device ID 801 "wear1." Furthermore, the content of the device data 182 output from device 172, whose device name 802 is "Wearable Terminal 1," is "the acceleration of each XYZ coordinate of Wearable Terminal 1. The unit is G. Updated every 0.1 seconds." Alternatively, the content of the device data 182 output from device 172, whose device name 802 is "Wearable Terminal 1," may be "information indicating whether the magnitude of the acceleration of Wearable Terminal 1 is above or above a predetermined threshold, or greater than a predetermined threshold." In Figure 8, device 172, whose device name 802 is "Router 1 (or Switch 1)", is assigned the device ID 801 "snmp1". Furthermore, the content of device data 182 output from device 172, whose device name 802 is "Router 1 (or Switch 1)", is "The number of packets sent and received between robots, equipment, and devices for process 1. Updated every second." In Figure 8, device 172, whose device name 802 is "Programmable Logic Controller 1", is assigned the device ID 801 "PLC1". Furthermore, the content of device data 182 output from device 172, whose device name 802 is "Programmable Logic Controller 1", is "Operation flag for the motor that operates the belt conveyor for process 1". Figure 8 also shows device management information records where device name 802 is "Camera 3", "Camera 2", "Accelerometer 2", "Wearable Terminal 2", "Router 2", and "Programmable Logic Controller 2 (PLC2)", but these are the same as the device management information records already described. Furthermore, devices other than the type of device 172 shown in Figure 8 may also be used. For example, an infrared sensor for detecting the presence or movement of a person may be used as device 172.

[0056] Furthermore, if administrators 401, developers 393, and data users 394 do not directly refer to "device name 802" or "device data content 803," then "device name 802" and "device data content 803" do not need to be included in the device management information record.

[0057] Returning to the explanation of Figure 4, when the device registration receiving unit 321 receives a device registration request to register device 172-NEW, it registers the information contained in the device registration request in the device management information table 800 held by the metadata management system 302. More specifically, the device registration receiving unit 321 creates a device management information record for device 172-NEW and registers the device management information record in the device management information table 800. The device registration receiving unit 321 issues a registration notification (device registration notification) to the correlation analysis system 101 to inform it that device 172-NEW has been newly registered. This registration notification may include some or all of the information contained in the device management information record for device 172-NEW. This registration notification is received by the registration notification receiving unit 311, which is a functional unit of the correlation analysis system 101. Furthermore, if a data collection system 305 exists, the device registration reception unit 321 may also issue a registration notification to the data collection system 305 to inform it that device 172-NEW has been registered. In this case, the registration notification is received by the registration notification reception unit 351, which is a functional unit of the data collection system 305.

[0058] The registration notification receiving unit 311 may register the information contained in the received registration notification in the device management information buffer 318 held by the correlation analysis system 101. The device management information buffer 318 may hold at least the information from the device management information table 800 that the data request unit 313, which is a functional unit of the correlation analysis system 101, uses when it performs the process of acquiring device data 182. For example, the device management information buffer 318 may hold the "device ID 801" and the "URL 804 (or other type of access setting information)" in Figure 8, which are from the information contained in the device management information record for the device 172 that was the subject of the registration notification. As described above, if a data collection system 305 exists, the registration notification receiving unit 351 may register the information contained in the received registration notification in the device management information buffer 358 held by the data collection system 305. The device management information buffer 358 may hold at least the information from the device management information table 800 that the data collection unit 354, a functional unit of the data collection system 305, uses when it collects device data 182 from device 172 and stores it in the collection information database 355 (collection information DB). In addition, the device management information buffer 358 may hold at least the information from the device management information table 800 that the data response unit 353, a functional unit of the data collection system 305, uses when it retrieves device data 182 from the collection information database 355 (collection information DB) in response to a data request from the data request unit 313 and returns the device data 182 to the data request unit 313.

[0059] 4-1-2. Acquisition of device data using a correlation analysis system after device installation. After device 172 is installed, the correlation analysis system 101 continuously acquires device data 182 output by device 172. As already explained, there are two methods for acquiring device data 182 by the correlation analysis system 101: one using the data acquisition system 305 and one not using the data acquisition system 305. Each method will be described below. Note that for each device 172, it may be possible to select which of the two methods is used. (If device data 182 is acquired for all devices 172 using the method not involving the data acquisition system 305, then the data acquisition system 305 may no longer be necessary.)

[0060] 4-1-2-1. Acquisition of device data via a data acquisition system When device data 182 is acquired using the data acquisition system 305, device 172 and the data acquisition unit 354, which is a functional part of the data acquisition system 305, cooperate with each other to store the device data 182 output from device 172 in the data acquisition information database 355 (data acquisition information DB) held by the data acquisition system 305. At this time, the data acquisition unit 354 may perform control using the information held in the device management information buffer 358. The method for collecting device data 182 into the collection information database 355 (collection information DB) can be any method. For example, the data collection unit 354 may receive device data 182 output from device 172 in a push manner, and the data collection unit 354 may store the device data 182 in the collection information database 355 (collection information DB). Alternatively, the data collection unit 354 may request device data 182 from device 172, receive the device data 182 output from device 172 in a pull manner, and the data collection unit 354 may store the device data 182 in the collection information database 355 (collection information DB).

[0061] The data request unit 313, which is a functional part of the correlation analysis system 101, requests device data 182 from the data acquisition system 305 as needed. At this time, the data request unit 313 may perform control using information held in the device management information buffer 318. The data response unit 353, a functional unit of the data acquisition system 305, receives a request for device data 182 from the data request unit 313. The data response unit 353 retrieves the requested device data 182 from the acquisition information database 355 (acquisition information DB) and returns the device data 182 to the correlation analysis system 101 (data request unit 313). At this time, the data response unit 353 may perform control using the information held in the device management information buffer 358.

[0062] When the method for acquiring device data 182 via the data acquisition system 305 described above is used, the device data 182 output from device 172 is first stored in the collection information database 355 (collection information DB) and then provided to the correlation analysis system 101 (or data utilization system 304). Therefore, it is expected that the instability of acquiring device data 182 depending on the type of device 172 will be reduced, and stable acquisition of device data 182 will be achieved.

[0063] 4-1-2-2. Direct acquisition of device data without using a data collection system. If device data 182 is acquired without using the data acquisition system 305, device 172 and the data request unit 313, which is a functional unit of the correlation analysis system 101, cooperate with each other to directly transfer the device data 182 output from device 172 to the correlation analysis system 101 as needed. At this time, the data request unit 313 may perform control using information held in the device management information buffer 318. The method for acquiring (transferring) the device data 182 may be any method. For example, the data request unit 313 may receive the device data 182 output from device 172 using a push method. Alternatively, the data request unit 313 may request the device data 182 from device 172, and the data request unit 313 may receive the device data 182 output from device 172 using a pull method.

[0064] If a method for acquiring device data 182 without using the data acquisition system 305 is employed, the correlation analysis system 101 (or data utilization system 304) will not go through the data acquisition system 305 when acquiring the device data 182, so the entire process of acquiring the device data 182 is expected to be simplified. Furthermore, if the data acquisition system 305 is not provided, a reduction in hardware and other costs can also be expected.

[0065] 4-2. Functional configurations, processes, and information involved in the detection or management of correlation and association (Figure 5) This section describes the functional configuration, processing, and information involved when the correlation analysis system 101 detects and manages correlations 162, device group relationships 164, and group interrelationships 165. The functional configuration, processing, and information described below enable the detection or management of correlations 162, device group relationships 164, and group interrelationships 165 using the device data 182 output from each of the devices 172. Furthermore, it becomes possible to grasp correlations 162, device group relationships 164, and group interrelationships 165 that appropriately reflect the installation, activation, removal, and deactivation of devices 172 at the site, as well as changes in the site conditions (for example, workers moving from one work area to another), thereby providing information that allows for an appropriate understanding of changes in the site conditions.

[0066] Figure 5 shows the functional configurations involved and the information handled when detecting and managing correlations 162, device group associations 164, and group inter-associations 165. Not all functional configurations and information shown in Figure 5 are mandatory. Furthermore, the existence of functional configurations and information other than those shown in Figure 5 is not prohibited. In the representation of the information flow in Figure 5, the parts marked with (c), (r), (cn), (rn), (gn), (q), (p), and (#) are connected to each other.

[0067] 4-2-1. Overview of Functional Configurations Involved in the Detection or Management of Correlation and Relationships Before the details of the processing of each functional unit of the correlation analysis system 101 are described in "4.2.3. Processing involved in the detection or management of correlations and associations," an overview of the individual functional units of the correlation analysis system 101 is provided here.

[0068] 4-2-1-1. Overview of the Data Request Section The correlation analysis system 101 has a data request unit 313 as a functional unit. Most of the functions of the data request unit 313 have already been explained with reference to Figure 4. The data request unit 313 stores device data 182 acquired from device 172 or data acquisition system 305 in the acquisition information buffer 315 held by the correlation analysis system 101.

[0069] 4-2-1-2. Overview of the Data Processing Department The correlation analysis system 101 may have a data processing unit 316 as a functional unit. The data processing unit 316 may generate information (data) in a format that is easy for the correlation event detection unit 1900 to handle by processing the device data 182 held in the collected information buffer 315.

[0070] For example, among the device data 182 held in the collected information buffer 315, the device data 182 acquired by cameras such as camera 1 (cam1), camera 2 (cam2), and camera (cam3) shown in Figure 8 is the image data (or video data) itself. However, the correlation event detection unit 1900 may find it difficult to handle the image data (or video data) as is. In such cases, the data processing unit 316 may detect the time (or time period) when movement of a certain magnitude or greater than a certain threshold is detected on the screen, and the time (or time period) when movement of a certain magnitude or greater than a certain threshold is not detected, and generate a movement presence / absence flag 1003 for each time (or time period). The movement presence / absence flag 1003 may be stored in the movement detection information table 1000 in Figure 10.

[0071] The data processing unit 316 may also process the device data 182 output from devices 172 other than the camera to generate information (data) in a format that is easy for the correlation event detection unit 1900 to handle. For example, if the device data 182 output from devices 172 such as acceleration sensor 1 (acc1), velocity sensor 1 (velo1), wearable terminal 1 (wear1), acceleration sensor 2 (acc2), and wearable terminal 2 (wear2) shown in Figure 8 is time-series information of the values ​​of the three-dimensional coordinate (X, Y, Z) components of acceleration and velocity, the data processing unit 316 may generate a motion presence / absence flag 1003 for each time (or time period) indicating whether the magnitude of acceleration or velocity is above (or greater than) a certain threshold. The motion presence / absence flag 1003 may be stored in a table similar to the motion detection information table 1000. For example, if the device data 182 output from devices 172 such as the programmable logic controller 1 (PLC1) and programmable logic controller 2 (PLC2) shown in Figure 8 is time-series information indicating the operating mode of a belt conveyor, the data processing unit 316 may generate a motion presence / absence flag 1003 for each time (or time period) based on the operating mode, indicating whether or not the belt conveyor is moving. The motion presence / absence flag 1003 may be stored in a table similar to the motion detection information table 1000. For example, if the device data 182 output from router 1 (or switch 1) (snmp1) and router 2 (snmp2) shown in Figure 8 is time-series information indicating the number of packets and the amount of communication transmitted and received between robots, equipment, and devices for a corresponding process, the data processing unit 316 may generate a motion presence / absence flag 1003 for each time (or time period) indicating whether the number of packets or the amount of communication is above (or greater than) a certain threshold. The motion presence / absence flag 1003 may be stored in a table similar to the motion detection information table 1000.

[0072] The data processing unit 316 may further identify the start time (most recent motion detection start time 1111) and end time (most recent motion detection end time 1112) of the most recent time period in which motion was detected, based on the motion presence / absence flag 1003 (time-series information of the motion presence / absence flag 1003) for each device 172. The data processing unit 316 may then store the identified most recent motion detection start time 1111 and most recent motion detection end time 1112 in the motion time information table 1100 shown in Figure 11.

[0073] The data processing method used by the data processing unit 316 described above is merely an example. The data processing unit 316 may use any processing method other than those described above.

[0074] By including a data processing unit 316 in the correlation analysis system 101, it becomes possible to handle the data format of the device data 182 output from the device 172, even if there is a certain degree of variation in the data format.

[0075] 4-2-1-3. Overview of the Correlation Event Detection Unit The overview of the correlation event detection unit 1900, which is a functional part of the correlation analysis system 101, has already been explained with reference to Figure 1. The information that the correlation event detection unit 1900 refers to in order to detect strong or weak correlation events between devices 172 may be some or all of the following: the device data 182 itself stored in the collected information buffer 315, the information obtained by processing the device data 182 by the data processing unit 316, the information stored in the motion detection information table 1000, and the information stored in the motion time information table 1100. As will be explained in more detail later, the correlation event detection unit 1900 may be controlled by the "correlation event detection period (k)" shown in Figure 29, which is one of the parameters 399. When the correlation event detection unit 1900 detects a strong correlation event for a specific combination of devices 172, this fact is recognized by the strong correlation event processing unit 2000. As already shown, a strong correlation event is an event that suggests the existence of a correlation 162 between devices 172. The method for transmitting the detection of a strong correlation event from the correlation event detection unit 1900 to the strong correlation event processing unit 2000 may be arbitrary (e.g., interrupt, memory mediation, etc.). When the correlation event detection unit 1900 detects a weak correlation event for a specific combination of devices 172, this fact is recognized by the weak correlation event processing unit 2400. As already shown, a weak correlation event is an event that suggests the absence of a correlation 162 between devices 172. The method for transmitting the detection of a weak correlation event from the correlation event detection unit 1900 to the weak correlation event processing unit 2400 may be arbitrary (e.g., interrupt, memory mediation, etc.). The details of the processing performed by the correlation event detection unit 1900 will be explained later with reference to Figure 19.

[0076] 4-2-1-4. Overview of the Strong Correlation Event Processing Unit The strongly correlated event processing unit 2000, which is a functional part of the correlation analysis system 101, implements some of the functions of the correlated event processing unit 120 shown in Figure 1. When the strong correlation event processing unit 1900 detects a strong correlation event between two devices 172, the strong correlation event processing unit 2000 adjusts the correlation strength value 1202, which is the strength of the correlation 162 between those devices 172. In this adjustment, the correlation strength value 1202 is often adjusted in a direction that strengthens the correlation 162. The strong correlation event processing unit 2000 then reflects the adjusted correlation strength value 1202 in the correlation information record for the combination of devices 172 for which a strong correlation event was detected, which is a record in the correlation information table 1200. Furthermore, the strong correlation event processing unit 2000 determines whether a new derivation (device group relationship 164 or group mutual relationship 165) arises from the correlation 162 between the devices 172 as a result of adjusting the correlation strength value 1202 between the devices 172. When the strong correlation event processing unit 2000 determines that a new derivation has occurred, it may reflect information indicating that a derivation has occurred (for example, a derivation flag 1203 that is turned ON) in the correlation information record for the combination of devices 172 for which a strong correlation event was detected, which is a record in the correlation information table 1200. When the strong correlation event processing unit 2000 determines that a new derivation has occurred, it may directly communicate that a derivation has occurred to the derivation occurrence event processing unit 2100. As will be explained in more detail later, the strongly correlated event processing unit 2000 may be controlled by the "correlation strength increase / decrease amount (t3)" and the "derivation occurrence threshold (t1)" shown in Figure 29, among the 399 parameters. Also, as will be explained in more detail later, the strongly correlated event processing unit 2000 may perform processing while referring to the derivation prohibition information table 1600. The details of the processing performed by the strongly correlated event processing unit 2000 will be explained later, along with Figure 20.

[0077] 4-2-1-5. Overview of the Derived Event Processing Unit The derivative occurrence event processing unit 2100, which is a functional part of the correlation analysis system 101, implements some of the functions of the derivative occurrence / disappearance event processing unit 121 shown in Figure 1. When the strongly correlated event processing unit 2000 determines that a new derivative has occurred, the derivative event processing unit 2100 identifies a device group relationship 164 (relationship setting candidate) and a group mutual relationship 165 (relationship setting candidate) that may newly exist as a result of the newly occurred derivative. The derivative event processing unit 2100 identifies combinations of devices 172 and groups 175 that correspond to the device group relationship 164 that may newly exist, and combinations of groups 175 that correspond to the group mutual relationships 165 that may newly exist. The derived event processing unit 2100 may, as appropriate, refer to the correlation information table 1200 and the device group relationship information table 1400 in order to perform the above identification. The derived event processing unit 2100 may transmit information identifying combinations of devices 172 and groups 175 (candidates for relationship setting) corresponding to newly existing device group relationships 164 to the device group relationship information derived event update unit 2200, and then request that it update information regarding the existence or non-existence of the device group relationships 164. The derived event processing unit 2100 may also transmit information identifying combinations of groups 175 corresponding to newly existing group mutual relationships 165 (candidates for relationship setting) to the group mutual relationship information derived event update unit 2300, and then request that it update information regarding the existence or non-existence of the group mutual relationships 165. The details of the processing performed by the derived event processing unit 2100 will be explained later with reference to Figure 21.

[0078] 4-2-1-6. Overview of the Device Group Relationship Information Derivation and Update Unit The device group relationship information derivation occurrence update unit 2200, which is a functional part of the correlation analysis system 101, implements some of the functions of the derivation occurrence / destruction event processing unit 121 shown in Figure 1. The device group relationship information derivative occurrence update unit 2200, in response to a request from the derivative occurrence event processing unit 2100, determines the changes related to the device group relationship 164 that occur due to the new occurrence of a derivative. The device group relationship information derivative occurrence update unit 2200 reflects the determined changes related to the device group relationship 164 in the device group relationship information table 1400. In this case, if a new device group relationship 164 comes into existence due to the new occurrence of a derivative, the device group relationship information derivative occurrence update unit 2200 registers a new device group relationship information record for the newly existing device group relationship 164 in the device group relationship information table 1400. The device group relationship information generation update unit 2200 may perform the above determination by referring to the device group relationship information table 1400 and the device group relationship prohibition information table 1700. The details of the processing of the device group relationship information generation update unit 2200 will be explained later with reference to Figure 22.

[0079] 4-2-1-7. Overview of the group interrelationship information generation and update unit. The group interrelationship information generation and update unit 2300, which is a functional part of the correlation analysis system 101, implements some of the functions of the generation and disappearance event processing unit 121 shown in Figure 1. The group interrelationship information derivative occurrence update unit 2300, in response to a request from the derivative occurrence event processing unit 2100, determines the changes related to the group interrelationship 165 that occur due to the new occurrence of a derivative. The group interrelationship information derivative occurrence update unit 2300 reflects the determined changes related to the group interrelationship 165 in the group interrelationship information table 1500. In this case, if a new group interrelationship 165 comes into existence due to the new occurrence of a derivative, the group interrelationship information derivative occurrence update unit 2300 registers a new group interrelationship information record for the newly existing group interrelationship 165 in the group interrelationship information table 1500. The group interrelationship information generation occurrence update unit 2300 may perform the above determination by referring to the group interrelationship information table 1500, the group interrelationship prohibition information table 1800, and the group management information table 900. The details of the processing of the group interrelationship information generation update unit 2300 will be explained later with reference to Figure 23.

[0080] 4-2-1-8. Overview of the Weak Correlation Event Processing Unit The weak correlation event processing unit 2400, which is a functional part of the correlation analysis system 101, implements some of the functions of the correlation event processing unit 120 shown in Figure 1. When the weak correlation event processing unit 1900 detects a weak correlation event between two devices 172, the weak correlation event processing unit 2400 adjusts the correlation strength value 1202, which is the strength of the correlation 162 between those devices 172. In this adjustment, the correlation strength value 1202 is often adjusted in a direction that weakens the strength of the correlation 162. The weak correlation event processing unit 2400 then reflects the adjusted correlation strength value 1202 in the correlation information record for the combination of devices 172 for which a weak correlation event was detected, which is a record in the correlation information table 1200. Furthermore, the weak correlation event processing unit 2400 determines whether the derivation (which previously existed) from the correlation 162 between the devices 172 to the relationship (device group relationship 164 or group interrelationship 165) disappears as a result of adjusting the correlation strength value 1202 between the devices 172. When the weak correlation event processing unit 2400 determines that the derivation (which previously existed) has disappeared, it may reflect information indicating that the derivation (which previously existed) has disappeared (for example, a derivation flag 1203 that is OFF) in the correlation information record for the combination of devices 172 where the weak correlation event was detected, which is a record in the correlation information table 1200. When the weak correlation event processing unit 2400 determines that the derivation (which previously existed) has disappeared, it may directly communicate the fact that the derivation has disappeared to the derivation disappearance event processing unit 2500. As will be explained in more detail later, the weak correlation event processing unit 2400 may be controlled by the "correlation strength increase / decrease amount (t3)" and the "derived extinction threshold (t2)" shown in Figure 29, which are among the 399 parameters. The details of the processing performed by the weak correlation event processing unit 2400 will be explained later with reference to Figure 24.

[0081] 4-2-1-9. Overview of the Derived Annihilation Event Processing Unit The derivative event processing unit 2500, which is a functional part of the correlation analysis system 101, implements some of the functions of the derivative event occurrence and disappearance processing unit 121 shown in Figure 1. When the weak correlation event processing unit 2400 determines that a derivative (which previously existed) has disappeared, the derivative disappearance event processing unit 2500 identifies device group relationships 164 (candidates for relationship setting cancellation) and group mutual relationships 165 (candidates for relationship setting cancellation) that may cease to exist as a result of the disappearance of the derivative. The derivative disappearance event processing unit 2500 identifies combinations of devices 172 and groups 175 that correspond to the device group relationships 164 that may cease to exist, and combinations of groups 175 that correspond to the group mutual relationships 165 that may cease to exist. The derived disappearance event processing unit 2500 may, as appropriate, refer to the correlation information table 1200 and the device group relationship information table 1400 in order to perform the above identification. The derivative disappearance event processing unit 2500 may transmit information identifying combinations of devices 172 and groups 175 corresponding to device group relationships 164 that may cease to exist (candidates for relationship setting cancellation) to the device group relationship information derivative disappearance update unit 2600, and then request that the device group relationship information derivative disappearance update unit 2600 perform an update on the existence or non-existence of the device group relationship 164. In addition, the derivative disappearance event processing unit 2500 may transmit information identifying combinations of groups 175 corresponding to group mutual relationships 165 that may cease to exist (candidates for relationship setting cancellation) to the group mutual relationship information derivative disappearance update unit 2700, and then request that the group mutual relationship information derivative disappearance update unit 2700 perform an update on the existence or non-existence of the group mutual relationships 165. The details of the processing of the derived event termination processing unit 2500 will be explained later with reference to Figure 25.

[0082] 4-2-1-10. Overview of the Device Group Relationship Information Derivation and Deletion Update Unit The device group relationship information derivation and disappearance update unit 2600, which is a functional part of the correlation analysis system 101, implements some of the functions of the derivation occurrence and disappearance event processing unit 121 shown in Figure 1. The device group relationship information derivative deletion update unit 2600, in response to a request from the derivative deletion event processing unit 2500, determines the changes related to the device group relationship 164 due to the deletion of a derivative (which previously existed). The device group relationship information derivative deletion update unit 2600 reflects the determined changes related to the device group relationship 164 in the device group relationship information table 1400. If, in this case, the device group relationship 164 ceases to exist due to the deletion of a derivative (which previously existed), the device group relationship information derivative deletion update unit 2600 deletes the device group relationship information record for the device group relationship 164 that ceases to exist from the device group relationship information table 1400. The device group relationship information derivation and deletion update unit 2600 may perform the above determination while referring to the device group relationship information table 1400. The details of the processing of the device group relationship information derivation and deletion update unit 2600 will be explained later with reference to Figure 26.

[0083] 4-2-1-11. Overview of the group interrelationship information derivation and deletion update unit. The group interrelationship information derivation and disappearance update unit 2700, which is a functional part of the correlation analysis system 101, implements some of the functions of the derivation occurrence and disappearance event processing unit 121 shown in Figure 1. The group interrelationship information derivative deletion update unit 2700, in response to a request from the derivative deletion event processing unit 2500, determines the changes related to the group interrelationship 165 that occur due to the deletion of a derivative (which previously existed). The group interrelationship information derivative deletion update unit 2700 reflects the determined changes related to the group interrelationship 165 in the group interrelationship information table 1500. In this case, if the group interrelationship 165 ceases to exist due to the deletion of a derivative (which previously existed), the group interrelationship information derivative deletion update unit 2700 deletes the group interrelationship information record for the group interrelationship 165 that ceases to exist from the group interrelationship information table 1500. The group interrelationship information derivation and deletion update unit 2700 may perform the above determination while referring to the group interrelationship information table 1500. The details of the processing of the group interrelationship information derivation and deletion update unit 2700 will be explained later with reference to Figure 27.

[0084] 4-2-1-12. Overview of the Fixed Settings Section The fixed setting unit 378, which is a functional part of the correlation analysis system 101, controls whether or not to fix information about some state that is handled by the correlation analysis system 101 and held by the metadata management system 302. Here, "some state" may be one or more of the following: the occurrence of a derivation from correlation 162 between devices 172 to a relationship (device group relationship 163 or group interrelationship 165); the existence of a device group relationship 164 between device 172 and group 175; or the existence of a group interrelationship 165 between groups 175. Furthermore, a fixed setting unit 388 having the same function as the fixed setting unit 378 may be provided in the metadata management system 302. In addition, a fixed setting unit having the same function as the fixed setting unit 378 may be provided in the development environment system 303 and the data utilization system 304 shown in Figure 3. The details of the processing in the fixed setting unit 378 will be explained later with reference to Figure 28.

[0085] 4-2-1-13. Overview of the Parameter Setting Section The parameter setting unit 319, which is a functional part of the correlation analysis system 101, sets the parameters 399 based on the input information to the correlation analysis system 101. The parameters 399 may include the "derivative occurrence threshold (t1)", "derivative disappearance threshold (t2)", "correlation strength increase / decrease amount (t3)", and "correlation event detection period (k)" shown in Figure 29. The parameters 399 may also include other parameters. Furthermore, a parameter setting unit 329 having the same function as the parameter setting unit 319 may be provided in the metadata management system 302. In addition, a parameter setting unit having the same function as the parameter setting unit 319 may be provided in the development environment system 303 or the data utilization system 304. The details of the processing in the parameter setting unit 319 will be explained later with reference to Figure 29.

[0086] 4-2-2. Overview of information involved in detecting or managing correlations and associations When the details of the processing of each functional unit of the correlation analysis system 101 are explained in "4-2-3. Processing involved in the detection or management of correlations and associations," the actual use of the information used in the processing will also be explained. Before that, an overview of the information used by the correlation analysis system 101 (mostly information held by the metadata management system 302) will be given here. Furthermore, the device management information table 800 shown in Figure 8, which is part of the information held by the metadata management system 302, has already been explained. The information held by the metadata management system 302 may be considered, in whole or in part, to form a knowledge database, a device catalog, or a data catalog.

[0087] 4-2-2-1. Overview of the Group Management Information Table Figure 9 shows the group management information table 900 held by the metadata management system 302. The group management information table 900 may be accessible from the correlation analysis system 101. A group management information record, which is a record in the group management information table 900, may have the following fields: group ID 901, group name 902, and relationship change degree 903 (or inclusion degree 904). Group ID 901 is the identification information of the group associated with the group management information record. Group ID 901 in Figure 9 is the same as that in Figures 2 and 3. Group name 902 is the name of the group associated with the group management information record. The Relationship Change Degree 903 (or Inclusion Degree 904) indicates whether group 175, associated with the group management information record, is likely to be relatively higher or lower in the hierarchical relationship among groups 175. In the example in Figure 9, the lower the Relationship Change Degree 903 (or Inclusion Degree 904) value associated with group 175, the more likely that group 175 is to be relatively higher in the hierarchical relationship among groups 175. In the example in Figure 9, the Relationship Change Degree 903 (or Inclusion Degree 904) value for factory 1 is "0", the Relationship Change Degree 903 (or Inclusion Degree 904) values ​​for process 1 (proc1) and process 2 (proc2) are "20", and the Relationship Change Degree 903 (or Inclusion Degree 904) values ​​for worker 1 (worker1) and worker 2 (worker2) are "70". Therefore, in terms of the hierarchical relationships among the 175 groups, factory 1 tends to be relatively higher, process 1 and process 2 tend to be relatively higher after factory 1, and worker 1 and worker 2 tend to be relatively lower. The term "degree of relationship change" indicates the likelihood that the corresponding group 175 will become a trigger for a change in correlation or relationship. For example, worker 1 and worker 2 are likely to become a trigger for a change in correlation or relationship by moving on their own. On the other hand, factory 1, process 1, and process 2 themselves are less likely to become a trigger for a change in correlation or relationship (compared to worker 1 and worker 2). The presence of a relationship change degree 903 (or inclusion degree 904) item associated with the group in the group management information record makes it easy to determine which of the two groups 175 should be considered relatively higher when establishing group interrelationships 165. As a result, hierarchical relationships between groups 175 are quickly and accurately constructed. Furthermore, instead of the relationship change index 903 (or inclusion index 904), other indicators that show the trend of positioning in the hierarchical relationships among the 175 groups may be used.

[0088] 4-2-2-2. Overview of the Motion Detection Information Table Figure 10 shows the motion detection information table 1000 held by the correlation analysis system 101. In Figure 10, only tables for camera 1 (cam1) and camera 2 (cam2) are shown, but similar tables may be provided for other devices 172 as well. A motion detection information record, which is a record in the motion detection information table 1000, may contain information for each of the following items: record number 1001, device ID 801, timestamp 1002, and motion presence / absence flag 1003. Device ID 801 is the identification information of the device associated with the motion detection information record. This device ID 801 may be the same as the one in Figure 8. Furthermore, if a separate motion detection information table 1000 is provided for each device ID 801, the device ID 801 item does not need to exist in each individual motion detection information record. The timestamp 1002 indicates the time (or time zone) associated with the motion detection information record. In Figure 10, the timestamp 1002 is shown with the year, month, day, and time in 24-hour format, but the timestamp 1002 may be in other formats. The motion presence / absence flag 1003 is a flag that indicates whether or not there was motion of a magnitude greater than a certain threshold (or greater than a certain threshold) at the time (or time period) indicated by the timestamp 1002 in the motion detection information record for device 172, which is pointed to by device ID 801 in the motion detection information record.

[0089] 4-2-2-3. Overview of the motion time information table Figure 11 shows the motion time information table 1100 held by the correlation analysis system 101. A motion time information record, which is a record in the motion time information table 1100, may contain information for each of the following items: device ID 801, device name 802, most recent motion detection start time 1111, and most recent motion detection end time 1112. Device ID 801 is the identification information of the device associated with the motion time information record. This device ID 801 may be the same as the one in Figure 8. Device name 802 is the name of the device associated with the motion time information record. This device name 802 may be the same as the one in Figure 8. Note that the item for device name 802 does not necessarily have to exist in the motion time information record. The most recent motion detection start time 1111 indicates the start time of the most recent time period in which there was motion of a magnitude greater than (or above) a certain threshold in device 172, which is pointed to by device ID 801 in the motion time information record. The most recent motion detection end time 1112 indicates the end time of the most recent time period in which there was movement of a certain magnitude or greater than a certain threshold at device 172, which is pointed to by device ID 801 in the motion time information record. However, if there is currently movement of a certain magnitude or greater than a certain threshold at device 172, which is pointed to by device ID 801 in the motion time information record, at the most recent time, the most recent motion detection end time 1112 may be blank. In Figure 11, the most recent motion detection start time 1111 and the most recent motion detection end time 1112 are shown as absolute values ​​of the elapsed time from a predetermined standard time. However, other notation methods may be used for the most recent motion detection start time 1111 and the most recent motion detection end time 1112. For example, the notation of the year, month, day, and time in 24-hour format, as shown in Figure 10, may also be used.

[0090] 4-2-2-4. Overview of the Correlation Information Table Figure 12 shows the correlation information table 1200 held by the metadata management system 302. The correlation information table 1200 may be accessible from the correlation analysis system 101. The correlation information table 1200 in Figure 12 shows the correlation information before worker 1 moved in the examples in Figures 2 and 3. A correlation information record, which is a record in the correlation information table 1200, may contain information for each of the following items: record number 1201, first device ID 801-1, second device ID 801-2, correlation strength value 1202, derivation flag 1203, and derivation fixed flag 1204.

[0091] Record number 1201 may be stored in the derived source record number group 1403 within the device group relationship information record, which is a record in the device group relationship information table 1400 in Figure 14, or in the derived source record number group 1403 within the group interrelationship information record, which is a record in the group interrelationship information table 1500 in Figure 15. The correlation 162 shown by the correlation information record to which record number 1201 belongs and the device group relationship 164 shown by the device group relationship information record that stores record number 1201 in the derived source record number group 1403 are in a derived source-destination relationship. Similarly, the correlation 162 shown by the correlation information record to which record number 1201 belongs and the group interrelationship 165 shown by the group interrelationship information record that stores record number 1201 in the derived source record number group 1403 are in a derived source-destination relationship.

[0092] The first device ID 801-1 and the second device ID 801-2 identify the combination of devices 172 that are targeted by correlation 162 indicated by the corresponding correlation information record. The correlation strength value 1202 indicates the strength of the correlation 162 shown by the correlation information record to which the correlation strength value 1202 belongs. For example, the stronger the correlation 162, the greater the correlation strength value 1202 may be, but is not limited to this. The correlation strength value 1202 may increase or decrease depending on the status of the device data 182 output from each of the devices 172 targeted by the correlation 162. The derivative flag 1203 indicates whether a derivative has occurred from the correlation 162 indicated by the correlation information record to which the derivative flag 1203 belongs, to a related relationship (device group related relationship 164 or group mutual related relationship 165). For example, if a derivative has occurred, the derivative flag 1203 may be ON, and if a derivative has not occurred (the derivative has disappeared), the derivative flag 1203 may be OFF. In this disclosure, ON and OFF may be represented by any form of notation, such as binary representation or character representation.

[0093] The derivative fixing flag 1204 indicates whether the derivative flag 1203 in the correlation information record to which the derivative fixing flag 1204 belongs will remain ON (whether the occurrence of derivatives will be fixed). If the occurrence of derivatives is fixed, the derivative fixing flag 1204 will be ON; if the occurrence of derivatives is not fixed (derivatives may occur or disappear), the derivative fixing flag 1204 will be OFF. Furthermore, if the derivative fixing flag 1204 is ON, the derivative flag 1203 will also be ON. Even if the correlation strength value 1202, which is the strength of the correlation 162 shown by the correlation information record in which the derivative fixing flag 1204 is ON, decreases, the derivative flag 1203 will not be turned OFF (derivatives will disappear). The presence of the derivation fixing flag 1204 prevents the unintentional disappearance of derivations, for example, when it is known that it is appropriate to generate derivations from the correlation 162 for a specific combination of devices 172, but there are circumstances such as low measurement accuracy of the device data 182.

[0094] Figure 13 shows the correlation information table 1300 after worker 1 moves from the work area of ​​process 1 (proc1) to the work area of ​​process 2 (proc2), resulting in the situation shown at the bottom of Figure 2. (Figure 12 shows the correlation information table before worker 1 moves.) In Figure 13, the changes compared to Figure 12 are enclosed in dotted lines.

[0095] As the situation changes from the upper part of Figure 2 to the lower part of Figure 2, a derivative of correlation 162 between camera 2 (cam2) and wearable device 1 (wear1) is generated, as indicated by "c4" at the bottom of Figure 2. On the other hand, as the situation changes from the upper part of Figure 2 to the lower part of Figure 2, the derivative of correlation 162 between camera 3 (cam3) and wearable device 1 (wear1), which was indicated by "c2" at the top of Figure 2, disappears. The emergence and disappearance of the above derivatives are shown in Figure 13 as follows. First, in the correlation information table 1300 in Figure 13, in the correlation information record where record number 1201 is "c4", the pair of first record ID 801-1 and second record ID 801-2 is "cam2" and "wear1", the correlation strength value 1202 becomes sufficiently high (to "60" in Figure 13), and the derivation flag 1203 is turned ON. This indicates that a derivation has occurred from the correlation 162 between camera 2 (cam2) and wearable device 1 (wear1). On the other hand, in the correlation information table 1300 in Figure 13, in the correlation information record where record number 1201 is "c2", the pair of first record ID 801-1 and second record ID 801-2 is "cam3" and "wear1", the correlation strength value 1202 becomes sufficiently low (from "70" in Figure 12 to "10" in Figure 13), and the derivation flag 1203 becomes off (from ON in Figure 12). This indicates that the derivation from the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1) has disappeared. In Figure 13, there is still a correlation information record with record number 1201 that is "c2". However, if the correlation strength value 1202 becomes even lower (for example, to zero), the correlation information record with record number 1201 that is "c2" may be deleted.

[0096] 4-2-2-5. Overview of the Device Group Relationship Information Table Figure 14 shows the device group relationship information table 1400 held by the metadata management system 302. The device group relationship information table 1400 may be accessible from the correlation analysis system 101. A device group relationship information record, which is a record in the device group relationship information table 1400, may contain information for each of the following items: record number 1401, device ID 801, group ID 901, relationship fixed flag 1402, and derived source record number group 1403.

[0097] Record number 1401 may be stored in the derived source record number group 1403 within other device group relationship information records other than the device group relationship information record to which record number 1401 belongs, or in the derived source record number group 1403 within a group relationship information record that is a record in the group relationship information table 1500 in Figure 15. The device group relationship 164 indicated by the device group relationship information record to which record number 1401 belongs and the device group relationship 164 indicated by other device group relationship information records that store record number 1401 in the derived source record number group 1403 have a "cause in causal relationship" (similar to the source) and an "effect in causal relationship" (similar to the destination) relationship between the device group relationships 164. Similarly, the device group relationship 164 indicated by the device group relationship information record to which record number 1401 belongs, and the group interrelationship 165 indicated by the group interrelationship information record that stores record number 1401 in the item of the derived record number group 1403, are in a "causal relationship" (similar to the source) and "effect relationship" (similar to the destination) relationship from device group relationship 164 to group interrelationship 165.

[0098] Device ID 801 and group ID 901 identify the combination of device 172 and group 175 that the device group relationship 164, indicated by the corresponding device group relationship information record, targets.

[0099] The relationship lock flag 1402 indicates whether it is permissible to delete the device group relationship information record to which the relationship lock flag 1402 belongs from the device group relationship information table 1400 (i.e., whether the device group relationship 164 is locked). If the device group relationship 164 is locked, the relationship lock flag 1402 is ON, and if the device group relationship 164 is not locked (i.e., it is permissible to delete the device group relationship information record), the relationship lock flag 1402 is OFF. Even if the derived source record number group 1403 within a device group relationship information record for which the relationship lock flag 1402 is ON is empty, the deletion of the device group relationship information record (i.e., the device group relationship 164 ceasing to exist) is prevented. The presence of the relationship-fixing flag 1402 prevents situations where, for example, it is known that a device group relationship 164 should exist for a particular combination of device 172 and group 175, but there is a risk that the device group relationship 164 may be mistakenly omitted due to circumstances such as low measurement accuracy of device data 182. In the examples shown in Figures 2 and 3, if it is known in advance that worker 1 will always carry wearable device 1, it is useful to turn on the relationship fixing flag 1402 for the device group relationship 164 between wearable device 1 and worker 1. Furthermore, device group relationships 164 indicated by device group relationship records where the relationship-fixing flag 1402 is ON may be called "fixed-type device group relationships." Also, device group relationships 164 indicated by device group relationship records where the relationship-fixing flag 1402 is OFF and the relationship exists based on the existence of any of the derivatives of correlation 162 or other device group relationships may be called "derived-type device group relationships."

[0100] The derived record number group 1403 stores information identifying the correlation 162 from which the device group relationship 164 indicated by the device group relationship record to which the derived record number group 1403 belongs is derived. The derived record number group 1403 also stores information identifying other device group relationships 164 that are the "causes in the causal relationship" (similar to the source) of the device group relationship 164 indicated by the device group relationship record to which the derived record number group 1403 belongs. The information identifying the correlation 162 stored in the derived record number group 1403 may be record number 1201 in the correlation information record that indicates the correlation 162. The information identifying the other device group association 164 stored in the derived record number group 1403 may be record number 1401 in the other device group association record that indicates the other device group association 164. In the case shown at the top of Figure 2, the device group association 164 between camera (cam3) and worker 1 (worker1), which is appended with "r7", is derived from the correlation 162 between camera (cam3) and wearable device 1 (wear1), which is appended with "c2", and the existence of a fixed-type device group association 164 between wearable device 1 (wear1) and worker 1 (worker1), which is appended with "r5", is one of the reasons for its existence. To reflect this, in the device group association information table 1400, the group of derived source record numbers 1403 within the device group association information record where record number 1401 is "r7" includes "c2-r5". Of "c2-r5", "c2" is record number 1201 in the correlation information record that shows the correlation 162 between camera (cam3) and wearable device 1 (wear1). In "c2-r5", "r5" is record number 1401 in the device group relationship information record, which indicates a fixed type device group relationship 164 between wearable device 1 (wear1) and worker 1 (worker1). Furthermore, within the device group relationship information record where record number 1401 is "r7", the derived source record number group 1403 includes "c1-r9" in addition to "c2-r5". "c1-r9" indicates a combination of the occurrence of a derivative from the correlation 162 between camera 3 (cam3) and acceleration sensor 1 (acc1), and the existence of a derived type device group relationship 164 between acceleration sensor 1 (acc1) and worker 1 (worker1). Thus, multiple sources may be set to support the existence of a single device group relationship 164.

[0101] In Figure 14, a white arrow is shown pointing from the device group relationship information records where record number 1401 is "r7", "r9", and "r10" to the device group relationship information records where record number 1401 is "r13" and "r14". This indicates that when the situation changes from the upper part of Figure 2 to the lower part of Figure 2, the device group relationship information records where record number 1401 is "r7", "r9", and "r10" are deleted, while new device group relationship records where record number 1401 is "r13" and "r14" are registered.

[0102] 4-2-2-6. Overview of the Group Interrelationship Information Table Figure 15 shows the group interrelationship information table 1500 held by the metadata management system 302. The group interrelationship information table 1500 may be accessible from the correlation analysis system 101. A group interrelationship information record, which is a record in the group interrelationship information table 1500, may contain information for each of the following items: record number 1501, starting group ID 901-1 (child group ID), ending group ID 901-2 (parent group ID), relationship fixed flag 1402, and derived source record number group 1403.

[0103] The starting group ID 901-1 (child group ID) and ending group ID 901-2 (parent group ID) are the identification information of group 175 included in the combination of group 175s targeted by group interrelationship 165 indicated in the corresponding group interrelationship information record. Here, the starting group ID 901-1 (child group ID) indicates a group 175 that is relatively lower in the hierarchical relationship of group 175. On the other hand, the ending group ID 901-2 (parent group ID) indicates a group 175 that is relatively higher in the hierarchical relationship of group 175.

[0104] The role of the relationship-fixing flag 1402 in the group relationship information record is the same as the role of the relationship-fixing flag 1402 in the device group relationship information record. The relationship lock flag 1402 in a group relationship information record indicates whether it is forbidden to delete the group relationship information record to which the relationship lock flag 1402 belongs from the group relationship information table 1500 (i.e., whether the group relationship 165 is locked). If the group relationship 165 is locked, the relationship lock flag 1402 is ON, and if the group relationship 165 is not locked (i.e., it is permissible to delete the group relationship information record), the relationship lock flag 1402 is OFF. Even if the group source record number group 1403 in a group relationship information record with the relationship lock flag 1402 ON is empty, the deletion of the group relationship information record (the cessation of the group relationship 165) is prevented. The presence of a relationship-fixing flag 1402 within the group relationship information record prevents situations where, for example, it is known that a group relationship 165 should exist for a specific combination of groups 175, but there is a risk that the group relationship 165 may be mistakenly omitted due to circumstances such as low measurement accuracy of the device data 182. In the examples shown in Figures 2 and 3, if it is known in advance that process 1 (proc1) and process 2 (proc2) are always under the control of factory 1 (factory1), then it is useful to turn on the relationship fixing flag 1402 for the group relationship 165 between process 1 (proc1) and factory 1 (factory1), and for the group relationship 165 between process 2 (proc2) and factory 1 (factory1). Furthermore, group interrelationship 165 indicated by a group interrelationship record where the relationship-fixing flag 1402 is ON may be called a "fixed type group interrelationship." Conversely, group interrelationship 165 indicated by a group interrelationship record where the relationship-fixing flag 1402 is OFF may be called a "derived type group interrelationship."

[0105] The role of the derived source record number group 1403 within the group interrelationship information record is the same as the role of the derived source record number group 1403 within the device group relevance information record. The group of source record numbers 1403 within the group relationship information record stores information identifying the correlation 162 from which the group relationship 165 indicated by the group relationship record to which the group relationship number group 1403 belongs is derived. The group of source record numbers 1403 also stores information identifying the device group relationship 164 that is the "causal cause" (similar to the source) of the group relationship 165 indicated by the group relationship record to which the group relationship number group 1403 belongs. Similar to the case of the source record number group 1403 in the device group relationship information record, in the source record number group 1403 in the group relationship information record, there may be multiple sources that serve as the basis for the existence of a single group relationship 165.

[0106] In Figure 15, a white arrow is shown pointing from the group relationship information record with record number 1501 being "g3" to the group relationship information record with record number 1501 being "g5". This indicates that when the situation changes from the upper part of Figure 2 to the lower part of Figure 2, the group relationship information record with record number 1501 being "g3" is deleted, while a new group relationship information record with record number 1501 being "g5" is created.

[0107] 4-2-2-7. Overview of the Derivative Prohibition Information Table Figure 16 shows the derivative prohibition information table 1600 held by the metadata management system 302. The derivative prohibition information table 1600 may be accessible from the correlation analysis system 101. A record in the Derivation Prohibition Information Table 1600, a Derivation Prohibition Information Record, may contain information for the following fields: Record Number 1601, First Device ID 801-1, and Second Device ID 801-2.

[0108] The first device ID 801-1 and the second device ID 801-2 in the derivation prohibition information record indicate the respective device ID 801 of the device 172 included in the device 172 when the occurrence of derivation from correlation 162 between the devices 172 is prohibited. For example, in Figure 16, the derivation prohibition information record with record number 1601 being "cn2" indicates the prohibition of the occurrence of derivation from the correlation 162 between camera 1 (cam1) and camera 2 (cam2). As shown in Figures 2 and 3, camera 1 (cam1) photographs the workspace of process 1 (proc1), and camera 2 (cam2) photographs the workspace of process 2 (proc2). If it is known in advance that these two workspaces are separated by a wall or the like, then a derivation prohibition information record with record number 1601 "cn2" as described above may be registered.

[0109] In this way, by registering a derivation prohibition information record in the derivation prohibition information table 1600, it is possible to prevent unintentional derivation in cases where, for example, it is known that it is not appropriate to generate a derivation from the correlation 162 for a specific combination of devices 172, but there is a risk of such a derivation occurring erroneously due to circumstances such as low measurement accuracy of device data 182.

[0110] 4-2-2-8. Overview of the Device Group Relationship Prohibition Information Table Figure 17 shows the device group association prohibition information table 1700 held by the metadata management system 302. The device group association prohibition information table 1700 may be accessible from the correlation analysis system 101. A device group relationship prohibition information record, which is a record in the device group relationship prohibition information table 1700, may contain information for each of the following fields: record number 1701, device ID 801, and group ID 901.

[0111] In the device group relationship prohibition information record, device ID 801 and group ID 901 represent the device ID 801 of device 172 and the group ID 901 of group 175 when the existence of a device group relationship 164 between device 172 and group 175 is prohibited. For example, in Figure 17, the device group association prohibition information record with record number 1701 being "rn3" indicates the prohibition of the existence of device group association 164 between camera 2 (cam2) and process 1 (proc1). As shown in Figures 2 and 3, camera 2 (cam2) photographs the workspace of process 2 (proc2), and camera 2 (cam2) does not photograph the workspace of process 1 (proc1). If it is known in advance that these two workspaces are separated by a wall or the like, then a derivation prohibition information record with record number 1701 "rn3" as described above may be registered.

[0112] In this way, by registering a device group relationship prohibition information record in the device group relationship prohibition information table 1700, for example, in cases where it is known that it is not appropriate for a device group relationship 164 to exist for a particular combination of device 172 and group 175, but there is a risk that the device group relationship 164 may exist erroneously due to circumstances such as low measurement accuracy of device data 182, it is possible to prevent the device group relationship 164 from unintentionally existing.

[0113] 4-2-2-9. Overview of the Group Interrelationship Prohibition Information Table Figure 18 shows the group interrelationship prohibition information table 1800 held by the metadata management system 302. The group interrelationship prohibition information table 1800 may be accessible from the correlation analysis system 101. A group inter-relationship prohibition information record, which is a record in the group inter-relationship prohibition information table 1800, may contain information for the following fields: record number 1801, first group ID 901-1, and second group ID 901-2.

[0114] The first group ID 901-1 and the second group ID 901-2 in the group interrelationship prohibition information record indicate the respective group IDs 901 of the group 175 included in the group 175 when the existence of group interrelationship 165 between the group 175 is prohibited. For example, in Figure 18, the group interrelationship prohibition information record with record number 1801 being "gn2" indicates the prohibition of the existence of group interrelationship 165 between worker1 and worker2.

[0115] In this way, by registering a group interrelationship prohibition information record in the group interrelationship prohibition information table 1800, for example, if it is known that it is not appropriate for a group interrelationship 165 to exist for a particular combination of groups 175, but there is a risk that the group interrelationship 165 may exist erroneously due to circumstances such as low measurement accuracy of device data 182, it is possible to prevent the unintentional existence of the group interrelationship 165.

[0116] 4.2.3. Processes involved in detecting or managing correlations and associations. This section describes the details of each process of the functional components of the correlation analysis system 101.

[0117] 4-2-3-1. Processing of the Correlation Event Detection Unit Figure 19 shows a flowchart of the processing of the correlation event detection unit 1900. The following explanation will follow the order of processing shown in Figure 19. Each processing step in the flowchart of Figure 19 can be understood as forming a "correlation event detection step". The following functions and processes are implemented, so that information can be obtained to estimate the existence or non-existence of correlations 162 between devices 172, based on the device data 182 output from each of the devices 172. Furthermore, even if the existence or non-existence of correlations 162 between devices 172 changes over time, information can be obtained to estimate that change.

[0118] In step 1901 of Figure 19, the correlation event detection unit 1900 determines whether a change in the value of the motion presence / absence flag 1003 has been detected in any of the devices 172 (here, device A). The motion presence / absence flag 1003 here may be the one in the motion detection information table 1000 of Figure 10. If the determination result in step 1901 is positive, the control proceeds to step 1902. If the determination result in step 1901 is negative, step 1901 is repeated. In step 1902 of Figure 19, the correlation event detection unit 1900 waits for k seconds. Here, k is the correlation event detection period in Figure 29. This k is included in the parameter 399 shown in Figure 5.

[0119] In step 1903 of Figure 19, the correlation event detection unit 1900 identifies each of the devices 172 (here referred to as device B) whose motion presence flag 1003 value has changed in a similar way to the change in the motion presence flag 1003 value for device A in step 1901, from 2k seconds ago (after waiting for k seconds in step 1902) to the present. In other words, when the motion presence flag 1003 value changes for device A, the correlation event detection unit 1900 identifies device B, which has had a similar change in the motion presence flag 1003 within a time period of plus or minus k seconds from the time the motion presence flag 1003 value changed for device A. The correlation event detection unit 1900 then determines that a "strong correlation event" has been detected between device A and device B. In other words, the correlation event detection unit 1900 determines that there is a certain degree of similarity between the change in the motion presence / absence flag 1003 of device A and the change in the motion presence / absence flag 1003 of device B, and therefore determines that an event has been detected that suggests the existence of a correlation between device A and device B.

[0120] In step 1904 of Figure 19, the correlation event detection unit 1900 identifies each of the devices 172 (referred to as device K) corresponding to the value of the motion presence flag 1003 that has not undergone a similar change to the change in the value of the motion presence flag 1003 for device A in step 1901, from 2k seconds ago (after waiting for k seconds in step 1902) to the present. In other words, when the value of the motion presence flag 1003 changes for device A, the correlation event detection unit 1900 identifies device K, which has not undergone a similar change in the motion presence flag 1003 within a time period of plus or minus k seconds from the time when the change in the motion presence flag 1003 occurred for device A. The correlation event detection unit 1900 then determines that a "weak correlation event" has been detected between device A and device K. In other words, the correlation event detection unit 1900 determines that there is little to no similarity between the change in the motion presence / absence flag 1003 of device A and the change in the motion presence / absence flag 1003 of device K, and therefore determines that an event has been detected in which the absence of correlation between device A and device K is presumed. After step 1904 in Figure 19, control is returned to step 1901.

[0121] The processing of the correlation event detection unit 1900 shown in Figure 19 is an example of detecting "strongly correlated events" and "weakly correlated events" between devices 172. The correlation event detection unit 1900 may use any method as long as it can detect "strongly correlated events" and "weakly correlated events" between devices 172. For example, a method for determining the similarity between the time-series information of the device data 182 output from each of the devices 172 (e.g., Dynamic Time Warping (DTW) or a cross-correlation function) may be used to detect "strongly correlated events" and "weakly correlated events" between devices 172.

[0122] 4-2-3-2. Processing of strongly correlated events. Figure 20 shows a flowchart of the processing of the strongly correlated event processing unit 2000. The following explanation follows the order of processing shown in Figure 20. Each processing step in the flowchart of Figure 20 may be understood to form a "strongly correlated event processing step". Furthermore, steps 2003, 2004, and 2008 in the flowchart of Figure 20 and steps 2403, 2404, 2408, and 2409 in the flowchart of Figure 24 described later may be understood to form a "correlation strength management step". In addition, steps 2005, 2006, and 2007 in the flowchart of Figure 20 and steps 2405, 2406, and 2407 in the flowchart of Figure 24 described later may be understood to form a "derivative occurrence and extinction judgment step". As the functions and processes described below are implemented, the correlation strength value 1202, which indicates the strength of the correlation 162 between devices 172, can be appropriately adjusted in response to the detection of an event that suggests the existence of a correlation 162 between devices 172. Furthermore, based on the correlation strength value 1202, the occurrence of a derivative from the correlation 162 to a relationship (device group relationship 164 or group inter-relationship 165) can be appropriately determined.

[0123] In step 2001 of Figure 20, the strong correlation event processing unit 2000 determines whether a "strong correlation event" has been detected for any combination of devices 172. For example, when the correlation event detection unit 1900 detects a "strong correlation event" in step 1903 of Figure 19, the correlation event detection unit 1900 may notify the strong correlation event processing unit 2000 that a "strong correlation event" has been detected. Any method may be used for this notification. For example, an interrupt method or a notification transmission method via a mailbox-type memory intermediary may be used. If the determination result in step 2001 is positive, control proceeds to step 2002. If the determination result in step 2001 is negative, step 2001 is repeated. As shown in step 2002 of Figure 20, the combination of devices 172 in which a "strongly correlated event" was detected will be referred to as device A and device B below.

[0124] In step 2003 of Figure 20, the strong correlation event processing unit 2000 determines whether a correlation information record already exists in the correlation information table 1200 shown in Figure 12 for the combination of device A and device B corresponding to the "strong correlation event". If the result of the determination in step 2003 is positive, control proceeds to step 2004. If the result of the determination in step 2003 is negative, control proceeds to step 2007.

[0125] In step 2004 of Figure 20, the strong correlation event processing unit 2000 increases the correlation strength value 1202 in the correlation information record for the combination of device A and device B corresponding to the "strong correlation event" that already existed in the correlation information table 1200 by t3. Here, t3 may be the correlation strength increase / decrease amount shown in Figure 29. Figure 29 shows an example where the correlation strength increase / decrease amount t3 is 10, but the value of the correlation strength increase / decrease amount t3 may be arbitrary. The correlation strength increase / decrease amount t3 is included in parameter 399 shown in Figure 5. Note that when increasing the correlation strength value 1202 in step 2004, an upper limit for the correlation strength value 1202 may be set. If increasing the correlation strength value 1202 in the correlation information record for the combination of device A and device B by t3 exceeds the upper limit, the correlation strength value 1202 may be set to the upper limit. The upper limit could be, for example, 100, but setting the upper limit is arbitrary.

[0126] In step 2005 of Figure 20, the strong correlation event processing unit 2000 determines whether the correlation intensity value 1202 in the correlation information record for the combination of device A and device B corresponding to the "strong correlation event" has changed from less than t1 to t1 or greater, before and after the process of increasing the correlation intensity value 1202 in step 2004. Here, t1 may be the derivation occurrence threshold shown in Figure 29. Figure 29 shows an example where the value of the derivation occurrence threshold t1 is 60, but the value of the derivation occurrence threshold t1 may be arbitrary. However, considering the stability of the control of derivation occurrence and extinction, it is desirable that the value of the derivation occurrence threshold t1 is greater than the derivation extinction threshold t2 shown in Figure 29. If the determination result in step 2005 is positive, control transitions to step 2006. If the determination result in step 2005 is negative, control returns to step 2001, and the strong correlation event processing unit 2000 waits until the next "strong correlation event" is detected.

[0127] In step 2006 of Figure 20, the strong correlation event processing unit 2000 sets the derivation flag 1203 in the correlation information record for the combination of device A and device B to ON. In other words, since the correlation strength value 1202 corresponding to the combination of device A and device B has become greater than or equal to the derivation occurrence threshold t1, it is assumed that a derivation has occurred from the correlation 162 between device A and device B to a relationship (device group relationship 164 and group mutual relationship 165). As a result of this derivation flag 1203 being turned ON, the judgment result in step 2101 of Figure 21 becomes positive. After step 2006, control is returned to step 2001, and the strongly correlated event processing unit 2000 waits until the next "strongly correlated event" is detected.

[0128] In the situation where control transitions to step 2007 in Figure 20, the correlation information table 1200 will not yet contain any correlation information records for the combination of device A and device B that corresponds to a "strongly correlated event". In step 2007 of Figure 20, the strong correlation event processing unit 2000 determines whether a derived prohibition information record exists in the derived prohibition information table 1600 of Figure 16 for the combination of device A and device B corresponding to the "strong correlation event". In other words, the strong correlation event processing unit 2000 checks whether there is a combination of first device ID 801-1 and second device ID 801-2 in the records included in the derived prohibition information table 1600 that matches the combination of device A and device B. If the result of the determination in step 2007 is positive, the registration of a new correlation information record for the combination of device A and device B in the correlation information table 1200 is prohibited, so control returns to step 2001, and the strong correlation event processing unit 2000 waits until the next "strong correlation event" is detected. If the result of the determination in step 2007 is negative, control transitions to step 2008.

[0129] In step 2008 of Figure 20, the strong correlation event processing unit 2000 registers a new correlation information record in the correlation information table 1200 for the combination of device A and device B corresponding to the "strong correlation event". The initial value of the correlation strength value 1202 in the newly registered correlation information record can be arbitrary, but it may be a value equal to the correlation strength increase / decrease amount t3, for example. The strong correlation event processing unit 2000 also sets both the derivative flag 1203 and the derivative fixed flag 1204 in the newly registered correlation information record to off (OFF). After step 2008, control is returned to step 2001, and the strong correlation event processing unit 2000 waits until the next "strong correlation event" is detected.

[0130] 4-2-3-3. Processing of Derived Events Processing Unit Figure 21 shows a flowchart of the processing of the derived event processing unit 2100. The following explanation will follow the order of processing shown in Figure 21. Note that each processing step in the flowchart of Figure 21 may be understood to form a "derived event processing step". Also, each processing step in the flowcharts of Figure 21, Figure 22, Figure 23, Figure 25, Figure 26, and Figure 27 may be understood to form a "derived event termination processing step". Furthermore, steps 2103, 2104, 2105, 2106, and 2107 in the flowchart of Figure 21, each processing step in the flowchart of Figure 22, steps 2503, 2504, 2505, 2506, and 2507 in the flowchart of Figure 25, and each processing step in the flowchart of Figure 26 may be understood to form a "device group relationship update step". In addition, steps 2103, 2104, 2105, and 2108 in the flowchart of Figure 21, each of the processing steps in the flowchart of Figure 23, each of the steps 2503, 2504, 2505, and 2508 in the flowchart of Figure 25, and each of the processing steps in the flowchart of Figure 76 can be understood to form a "group interrelationship update step". As the functions and processes described below are implemented, it is possible to identify combinations of devices 172 and groups 175 that may have a device group relationship 164 as a result of the emergence of new derivatives. Furthermore, it is possible to identify combinations of groups 175 that may have a group mutual relationship 165 as a result of the emergence of new derivatives.

[0131] In step 2101 of Figure 21, the Derivation Event Processing Unit 2100 determines whether a new derivation has occurred from any correlation 162 of the device 172 combination to a relationship (device group relationship 164 or group mutual relationship 165). For example, when the strong correlation event processing unit 2000 performs the processing in step 2006 of Figure 20, the strong correlation event processing unit 2000 may notify the Derivation Event Processing Unit 2100 of the occurrence of a new derivation from the correlation 162 between device A and device B. This notification may take any form (e.g., in the form of an interrupt, or in the form of notification transmission via memory). Alternatively, in response to the strong correlation event processing unit 2000 turning on the derivation flag 1203 in the correlation information record for the device A and device B combination in step 2006 of Figure 20, the Derivation Event Processing Unit 2100 may detect the newly turned-on derivation flag 1203. As shown in step 2102 of Figure 21, the combination of devices 172 corresponding to the newly derived correlation 162 will be referred to as device A and device B below.

[0132] In step 2203 of Figure 21, the derived event processing unit 2100 identifies the combinations of devices 172 that correspond to correlations 162 that have already generated a derivative, and the combinations of devices 172 and groups 175 that correspond to existing device group relationships 164, immediately before a new derivative occurs from the correlation 162 between device A and device B. For example, the derivative event processing unit 2100 identifies combinations of devices 172 indicated by correlation information records where the derivative flag 1203 is already turned on, other than the correlation information record for the combination of device A and device B for which the derivative event was newly detected in step 2101. Specifically, the derivative event processing unit 2100 refers to the first device ID 801-1 and the second device ID 801-2 in the correlation information record where the derivative flag 1203 is already turned on. For example, the derived event processing unit 2100 identifies the combination of device 172 and group 175 indicated by an existing device group relationship information record. Specifically, the derived event processing unit 2100 refers to device ID 801 and group ID 901 in an existing device group relationship information record. Here, the graph showing the combinations of devices 172 together and the combinations of devices 172 and group 175, as identified above, is denoted as G(A,B). Graph G(A,B) shows the "relationships" or "interconnectivity" between devices 172 and group 175, formed from the correlation 162 that has already generated a derivative and the existing device group association 164, immediately before a new derivative arises from the correlation 162 between device A and device B.

[0133] In step 2104 of Figure 21, the derived event processing unit 2100 finds the set of devices 172 that can be traced from device A based on graph G(A,B), and sets this set as set_of_d(A). Here, devices 172 that can be traced from device A mean devices 172 that can be reached starting from device A by correlations 162 in graph G(A,B) where derivation has already occurred. The derived event processing unit 2100 also finds the set of groups 175 that can be traced from device A based on graph G(A,B), and sets this set as set_of_g(A). Here, groups 175 that can be traced from device A mean groups 175 that can be reached starting from device A by correlations 162 in graph G(A,B) where derivation has already occurred and existing device group associations 164. In step 2105 of Figure 21, the derived event processing unit 2100 finds the set of devices 172 that can be traced from device B based on graph G(A,B), and sets this set as set_of_d(B). The derived event processing unit 2100 also finds the set of groups 175 that can be traced from device B based on graph G(A,B), and sets this set as set_of_g(B). Here, due to the emergence of new derivatives from the correlation 162 between device A and device B, a new device group association 164 may exist for each combination of device 172 included in set_of_d(A) and group 175 included in set_of_g(B). Similarly, due to the emergence of new derivatives from the correlation 162 between device A and device B, a new device group association 164 may exist for each combination of device 172 included in set_of_d(B) and group 175 included in set_of_g(A). Furthermore, similarly, due to the emergence of new derivatives from the correlation 162 between device A and device B, a new group inter-association 165 may exist for each combination of group 175 included in set_of_g(A) and group 175 included in set_of_g(B). Furthermore, as a result of processing in steps 2104 and 2105, it is possible that the sets of devices 172 belonging to set_of_d(A) and set_of_d(B) will be exactly the same, and the sets of groups 175 belonging to set_of_g(A) and set_of_d(B) will be exactly the same. In this case, there will be no new device group associations 164 and group interrelationships 165 that would arise from the new generation of the correlation 162 between device A and device B. In this case, in Figures 22 and 23, only the derived source record numbers within the existing device group association information records and group interrelationship records will be updated.

[0134] In step 2106 of Figure 21, the derived event processing unit 2100 registers or updates a device group relationship information record for each combination of device 172 included in set_of_d(A) and group 175 included in set_of_g(B), provided that set_of_g(B) is not an empty set. Specifically, the derived event processing unit 2100 causes the device group relationship information derived event update unit 2200 to execute the process shown in Figure 22. If a new device group relationship 164 is created as a result of the process in Figure 22, a device group relationship information record for that device group relationship 164 is registered in the device group relationship information table 1400. In step 2107 of Figure 21, the derived event processing unit 2100 registers or updates device group relationship information records for each combination of devices 172 included in set_of_d(B) and groups 175 included in set_of_g(A), provided that set_of_g(A) is not an empty set. Specifically, the derived event processing unit 2100 causes the device group relationship information derived event update unit 2200 to execute the process shown in Figure 22. If a new device group relationship 164 is created as a result of the process in Figure 22, a device group relationship information record for that device group relationship 164 is registered in the device group relationship information table 1400. In step 2108 of Figure 21, the derived event processing unit 2100 registers or updates group interrelationship information records for each combination of group 175 included in set_of_g(A) and group 175 included in set_of_g(B), provided that neither set_of_g(A) nor set_of_g(B) is empty for group 175. Specifically, the derived event processing unit 2100 causes the group interrelationship information derived event update unit 2300 to execute the process shown in Figure 23. If the process in Figure 23 results in the existence of a newly existing group interrelationship 165, a group interrelationship information record for that group interrelationship 165 is registered in the group interrelationship information table 1500. After step 2108, control is returned to 2101, and the derivative event processing unit 2100 waits until it detects the occurrence of a new derivative.

[0135] 4-2-3-4. Processing of the device group relationship information when it is generated. Figure 22 shows a flowchart of the processing of the device group relationship information generation update unit 2200. The following explanation will follow the order of processing shown in Figure 22. Note that each processing step in the flowchart of Figure 22 can be understood as forming a "device group relationship generation update step". The functions and processes described below are implemented so that changes in information related to device group relationships 164 due to the occurrence of derivation can be appropriately determined, and the determined changes can be reflected in the device group relationship information table 1400. In addition, if a new device group relationship 164 comes into existence due to the occurrence of derivation, this fact can be reflected in the device group relationship information table 1400.

[0136] In step 2201 of Figure 22, the device group relationship information derivation occurrence update unit 2200 determines whether to register or update a device group relationship information record in response to the occurrence of a new derivation from correlation 162. For example, if the derivation occurrence event processing unit 2100 decides in step 2106 of Figure 21 to register or update a device group relationship information record for the combination of device 172 included in set_of_d(A) and group 175 included in set_of_g(B), the derivation occurrence event processing unit 2100 notifies the device group relationship information derivation occurrence update unit 2200 of this. Alternatively, if the derivation occurrence event processing unit 2100 decides in step 2107 of Figure 21 to register or update a device group relationship information record for the combination of device 172 included in set_of_d(B) and group 175 included in set_of_g(A), the derivation occurrence event processing unit 2100 notifies the device group relationship information derivation occurrence update unit 2200 of this. In the following explanation of Figure 22, the set of devices 172 mentioned above will be denoted as set_of_d, and the set of groups 175 mentioned above will be denoted as set_of_g.

[0137] In step 2202 of Figure 22, the device group relationship information generation update unit 2200 selects one of the devices 172 included in set_of_d and designates it as device C. The device group relationship information generation update unit 2200 also selects one of the groups 175 included in set_of_g and designates it as group D. In other words, the combination of device C and group D is selected as a candidate (relationship setting candidate) for the newly existing device group relationship 164.

[0138] In step 2203 of Figure 22, the device group relationship information generation update unit 2200 determines whether a device group relationship prohibition information record exists in the device group relationship prohibition information table 1700 of Figure 17 for the combination of device C and group D selected in the most recent step 2202. If the determination result in step 2203 is positive, a device group relationship 164 is not permitted between device C and group D, so steps 2204, 2205, and 2206 are skipped and control proceeds to step 2207. If the determination result in step 2203 is negative, control proceeds to step 2204.

[0139] In step 2204 of Figure 22, the device group relationship information generation update unit 2200 determines whether a device group relationship information record exists in the device group relationship information table 1400 of Figure 14 for the combination of device C and group D selected in the most recent step 2202. If the determination result of step 2204 is positive, step 2205 is skipped and control proceeds to step 2206. If the determination result of step 2204 is negative, control proceeds to step 2205.

[0140] In step 2205 of Figure 22, the device group relationship information generation update unit 2200 registers a new device group relationship information record in the device group relationship information table 1400 of Figure 14 for the combination of device C and group D selected in the most recent step 2202. In the newly registered device group relationship information record, device ID 801 is set to the device ID of device C, and group ID 901 is set to the group ID of group D. In the newly registered device group relationship information record, the relationship fixing flag 1402 is set to off (OFF). After step 2205, control transitions to step 2206.

[0141] In step 2206 of Figure 22, the device group relationship information derivation update unit 2200 registers or updates the source record number group 1403 in the device group relationship information record for the combination of device C and group D selected in the most recent step 2202. Specifically, the device group relationship information derivation update unit 2200 includes information in the source record number group 1403 that identifies the correlation 162 from which the newly derived correlation 162, which is the source of the newly existing device group relationship 164, originated. In other words, the device group relationship information derivation update unit 2200 includes information indicating the combination of device A and device B in the source record number group 1403. As shown in Figures 12 and 13, if each correlation information record in the correlation information table 1200 has a record number 1201, then in step 2206, the device group relationship information derivation occurrence update unit 2200 may include the record number 1201 in the correlation information record for the combination of device A and device B in the derived source record number group 1403. This section describes a case where a derivation occurs from the correlation 162 between camera 2 (cam2) and wearable device 1 (wear1) as the situation changes from the upper part of Figure 2 to the lower part of Figure 2. In this case, as shown by the change from correlation information table 1200 in Figure 12 to correlation information table 1300 in Figure 13, the derivation flag 1203 of the correlation information record for the combination of camera 2 (cam2) and wearable device 1 (wear1) is turned ON. Consequently, a device group association 164 is established between camera 2 (cam2) and worker 1 (worker1). At this time, the device group relationship information generation update unit 2200 registers a device group relationship information record for the combination of camera 2 (cam2) and worker 1 (worker1), as shown in Figure 14, and then includes "c4", which is record number 1201 in the correlation information record for the combination of camera 2 (cam2) and wearable terminal 1 (wear1), in the group of source record numbers 1403 within the record. As is clear from the bottom of Figure 2, the basis for the existence of the device group association 164 between camera 2 (cam2) and worker 1 (worker1) is the occurrence of a derivative from the correlation 162 between camera 2 (cam2) and wearable terminal 1 (wear1), and the fixed-type device group association 164 between wearable terminal 1 (wear1) and worker 1 (worker1). Therefore, as shown in the device group association information record of record number 1401 "r13" in Figure 14, the derived source record number group 1403 in the device group association information record for the combination of camera 2 (cam2) and worker 1 (worker1) will register "c4", which is record number 1201 in the correlation information record for the combination of camera 2 (cam2) and wearable terminal 1 (wear1), and "r5", which is record number 1401 in the device group association information record for the combination of wearable terminal 1 (wear1) and worker 1 (worker1), as being mutually associated. After step 2206, control transitions to step 2207.

[0142] In step 2207 of Figure 22, the device group relationship information generation update unit 2200 determines whether all possible combinations of device 172 (device C) included in set_of_d and group 175 (group D) included in set_of_g have been selected in step 2202. If the result of the determination in step 2207 is positive, control is returned to step 2201, and the device group relationship information generation update unit 2200 waits until the next opportunity to register or update the device group relationship information record. If the result of the determination in step 2207 is negative, control is returned to 2202, and a combination of device C and group D that has not yet been selected is newly selected.

[0143] 4-2-3-5. Processing of the update unit when group interrelationship information is derived. Figure 23 shows a flowchart of the processing of the group interrelationship information generation update unit 2300. The following explanation will follow the order of processing shown in Figure 23. Note that each processing step in the flowchart of Figure 23 can be understood as forming a "group interrelationship information generation update step". The functions and processes described below are implemented so that changes in information regarding group interrelationships 165 due to the occurrence of derivation can be appropriately judged, and the judged changes can be reflected in the group interrelationship information table 1500. In addition, if a new group interrelationship 165 comes into existence due to the occurrence of derivation, this fact can be reflected in the group interrelationship information table 1500.

[0144] In step 2301 of Figure 23, the group interrelationship information derivation occurrence update unit 2300 determines whether to register or update a group interrelationship information record in response to the occurrence of a new derivation from correlation 162. For example, if the derivation occurrence event processing unit 2100 decides in step 2108 of Figure 21 to register or update a group interrelationship information record for the combination of group 175 included in set_of_g(A) and group 175 included in set_of_g(B), the derivation occurrence event processing unit 2100 notifies the group interrelationship information derivation occurrence update unit 2300 of this. In the following explanation of Figure 23, one of the two sets of group 175 mentioned above (the first set) is denoted as set_of_g(1), and the other set (the second set) is denoted as set_of_g(2).

[0145] In step 2302 of Figure 23, the group interrelationship information generation update unit 2300 selects one of the groups 175 included in set_of_g(1) and designates it as group E. The group interrelationship information generation update unit 2300 also selects one of the groups 175 included in set_of_g(2) and designates it as group F. In other words, the combination of group E and group F is selected as a candidate (relationship setting candidate) for the newly existing group interrelationship 165.

[0146] In step 2303 of Figure 23, the group interrelationship information generation occurrence update unit 2300 determines whether a group interrelationship prohibition information record exists in the group interrelationship prohibition information table 1800 of Figure 18 for the combination of group E and group F selected in the most recent step 2302. If the determination result in step 2303 is positive, a group interrelationship 165 is not permitted between group E and group F, so steps 2304, 2305, 2306, 2307, and 2308 are skipped, and control transitions to step 2309. If the determination result in step 2303 is negative, control transitions to step 2304.

[0147] In step 2304 of Figure 23, the group interrelationship information generation and update unit 2300 determines whether a group interrelationship information record exists in the group interrelationship information table 1500 of Figure 15 for the combination of group E and group F selected in the most recent step 2302. If the determination result in step 2304 is positive, steps 2305, 2306, and 2307 are skipped, and control proceeds to step 2308. If the determination result in step 2304 is negative, control proceeds to step 2305.

[0148] In step 2305 of Figure 23, the group interrelationship information generation update unit 2300 determines which of the groups E and F selected in the most recent step 2302 is relatively higher in the hierarchical relationship of group 175. Specifically, the group interrelationship information generation update unit 2300 refers to the group management information table 900 in Figure 9 and compares the relationship change degree 903 (or inclusion degree 904) in the group management information record for group E with the relationship change degree 903 (or inclusion degree 904) in the group management information record for group F. The group interrelationship information generation update unit 2300 determines whether the relationship change degree 903 (or inclusion degree 904) of group E is greater than or equal to the relationship change degree 903 (or inclusion degree 904) of group F. If the result of the determination in step 2305 is positive (group F is treated as relatively higher), the control proceeds to step 2306. If the result of the decision in step 2305 is negative (group E is treated as the relative superior group), control proceeds to step 2307.

[0149] In step 2306 of Figure 23, the group interrelationship information generation and update unit 2300 newly registers a group interrelationship record in the group interrelationship information table 1500 of Figure 15 for the combination of group E, which is relatively lower in the hierarchical relationship of group 175, and group F, which is relatively higher. The starting group ID 901-1 (child group ID) in the record is set to the group ID that represents group E, and the ending group ID (parent group ID) in the record is set to the group ID that represents group F. In addition, the relationship fixing flag 1402 in the record is turned off (OFF). After step 2306, control transitions to step 2308.

[0150] In step 2307 of Figure 23, the group interrelationship information generation and update unit 2300 newly registers a group interrelationship record in the group interrelationship information table 1500 of Figure 15 for the combination of group F, which is relatively lower in the hierarchical relationship of group 175, and group E, which is relatively higher. The starting group ID 901-1 (child group ID) in the record is set to the group ID that represents group F, and the ending group ID (parent group ID) in the record is set to the group ID that represents group E. In addition, the relationship fixing flag 1402 in the record is turned off (OFF). After step 2307, control transitions to step 2308.

[0151] In step 2308 of Figure 23, the group interrelationship information derivation update unit 2300 registers or updates the group interrelationship information record number group 1403 within the group interrelationship information record for the combination of group E and group F selected in the most recent step 2302. Specifically, the group interrelationship information derivation update unit 2300 includes information in the group interrelationship record number group 1403 that identifies the correlation 162 from which the newly derived correlation 162, which will become a newly existing group interrelationship 165, originated. In other words, the group interrelationship information derivation update unit 2300 includes information indicating the combination of device A and device B in the group interrelationship record number group 1403. As shown in Figures 12 and 13, if each correlation information record in the correlation information table 1200 has a record number 1201, then in step 2308, the group interrelationship information derivation generation update unit 2300 may include the record number 1201 in the correlation information record for the combination of device A and device B in the derived source record number group 1403. For example, let's explain a case where a derivation occurs from the correlation 162 between camera 2 (cam2) and wearable device 1 (wear1) as the situation changes from the upper part of Figure 2 to the lower part of Figure 2. In this case, as shown by the change from correlation information table 1200 in Figure 12 to correlation information table 1300 in Figure 13, the derivation flag 1203 of the correlation information record for the combination of camera 2 (cam2) and wearable device 1 (wear1) is turned ON. Consequently, for example, a group interrelationship 165 comes into existence between worker 1 (worker1), which is relatively lower in rank, and process 2 (proc2), which is relatively higher in rank. At this time, the group interrelationship information generation update unit 2300 registers a group interrelationship information record for the combination of worker 1 (worker1), which is relatively lower in rank, and process 2 (proc2), which is relatively higher in rank, as shown in Figure 15, and then includes "c4", which is record number 1201 in the correlation information record for the combination of camera 2 (cam2) and wearable terminal 1 (wear1), in the group of source record numbers 1403 within the record. As is clear from the bottom of Figure 2, one of the reasons for the existence of group correlations 165 between the relatively lower worker 1 and the relatively higher process 2 is the emergence of a derivative from the correlation 162 between camera 2 (cam2) and wearable device 1 (wear1), and the combination of the fixed-type device group correlation 164 between wearable device 1 (wear1) and worker 1 (worker1) and the fixed-type device group correlation 164 between camera 2 (cam2) and process 2 (proc2). Therefore, as shown in the group interrelationship information record for record number 1501 "g5" in Figure 15, the derived source record number group 1403 within the group interrelationship information record for the combination of worker 1 (worker1), which is relatively lower in rank, and process 2 (proc2), which is relatively higher in rank, will be registered as being mutually related to "r5", which is record number 1401 in the device group relevance information record for the combination of wearable terminal 1 (wear1) and worker 1 (worker1), "c4", which is record number 1201 in the correlation information record for the combination of camera 2 (cam2) and wearable terminal 1 (wear1), and "r3", which is record number 1401 in the device group relevance information record for the combination of camera 2 (cam2) and process 2 (proc2). Furthermore, as is clear from the bottom of Figure 2, there are other factors besides those mentioned above that provide the basis for the existence of the group interrelationship 165 between the relatively lower worker 1 and the relatively higher process 2. Specifically, the combination of the (derived type) device group relationship 164 between camera 2 (cam2) and worker 1 (worker1) and the fixed type device group relationship 164 between camera 2 (cam2) and process 2 (proc2) also provides the basis for the existence of the group interrelationship 165 between the relatively lower worker 1 (worker1) and the relatively higher process 2 (proc2). In addition, the combination of the fixed type device group relationship 164 between wearable device 1 (wear1) and worker 1 (worker1) and the (derived type) device group relationship 164 between wearable device 1 (wear1) and process 2 (proc2) also provides the basis for the existence of the group interrelationship 165 between the relatively lower worker 1 (worker1) and the relatively higher process 2 (proc2). Therefore, record numbers 1201 and 1401, which provide this evidence, may also be included in the group of derived record numbers 1403 within the group interrelationship information record for the combination of worker 1 (relatively lower) and process 2 (relatively higher). After step 2308, control transitions to step 2309.

[0152] In step 2309 of Figure 23, the group interrelationship information generation update unit 2300 determines whether all possible combinations of group 175 (group E) included in set_of_g(1) and group 175 (group F) included in set_of_g(2) have been selected in step 2302. If the result of the determination in step 2309 is positive, control returns to step 2309, and the group interrelationship information generation update unit 2300 waits until the next opportunity to register or update the group interrelationship information record. If the result of the determination in step 2309 is negative, control returns to 2302, and a new combination of group E and group F that has not yet been selected is selected.

[0153] 4-2-3-6. Processing of Weakly Correlated Events Figure 24 shows a flowchart of the processing of the weak correlation event processing unit 2400. The following explanation will follow the order of processing shown in Figure 24. Each processing step in the flowchart of Figure 24 can be understood as forming a "weak correlation event processing step". The following functions and processes are implemented so that, in response to the detection of an event that suggests the absence of a correlation 162 between devices 172, the correlation strength value 1202, which indicates the strength of the correlation 162 between the devices 172, can be appropriately adjusted. Furthermore, based on the correlation strength value 1202, the disappearance of the derivation (which previously existed) from the correlation 162 to the association (device group association 164 or group inter-association 165) can be appropriately determined.

[0154] In step 2401 of Figure 24, the weak correlation event processing unit 2400 determines whether a "weak correlation event" has been detected for any combination of devices 172. For example, when the correlation event detection unit 1900 detects a "weak correlation event" in step 1904 of Figure 19, the correlation event detection unit 1900 may notify the weak correlation event processing unit 2400 that a "weak correlation event" has been detected. Any method may be used for this notification. For example, an interrupt method or a notification transmission method via a mailbox-type memory intermediary may be used. If the determination result in step 2401 is positive, control proceeds to step 2402. If the determination result in step 2401 is negative, step 2401 is repeated. As shown in step 2402 of Figure 24, the combination of devices 172 in which a "weakly correlated event" was detected will be referred to as device A and device K below.

[0155] In step 2403 of Figure 24, the weak correlation event processing unit 2400 determines whether a correlation information record already exists in the correlation information table 1200 shown in Figure 12 (or the correlation information table 1300 shown in Figure 13) for the combination of device A and device K corresponding to the "weak correlation event". If the determination result in step 2403 is positive, control proceeds to step 2404. If the determination result in step 2403 is negative, control returns to step 2401, and the weak correlation event processing unit 2400 waits until the next "weak correlation event" is detected.

[0156] In step 2404 of Figure 24, the weak correlation event processing unit 2400 reduces the correlation strength value 1202 in the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" that already existed in the correlation information table 1200 (or correlation information table 1300) by t3. Here, t3 may be the correlation strength increase / decrease amount shown in Figure 29. Figure 29 shows an example where the value of the correlation strength increase / decrease amount t3 is 10, but the value of the correlation strength increase / decrease amount t3 may be arbitrary. The correlation strength increase / decrease amount t3 is included in parameter 399 shown in Figure 5. (In the example in Figure 29, the amount of increase when increasing the correlation strength value 1202 in the flowchart of Figure 20 and the amount of decrease when decreasing the correlation strength value 1202 in the flowchart of Figure 24 are both set to the same t3, but the amount of increase and the amount of decrease may be different values.) In step 2404, when decreasing the correlation strength value 1202, a lower limit may be set for the correlation strength value 1202. For example, if decreasing the correlation strength value 1202 in the correlation information record for the combination of device A and device K by t3 would cause it to fall below the lower limit, then the correlation strength value 1202 may be set to the lower limit. The lower limit may be, for example, zero, but setting the lower limit is arbitrary.

[0157] In step 2405 of Figure 24, the weak correlation event processing unit 2400 determines whether the derivation fixed flag 1204 in the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" is on. If the result of the determination in step 2405 is positive, the derivation from the correlation 162 between device A and device K to the relationships (device group relationships 164 and group mutual relationships 165) is of the fixed type, and the disappearance of such derivation is not permitted, so control returns to step 2401, and the weak correlation event processing unit 2400 waits until the next "weak correlation event" is detected. If the result of the determination in step 2405 is negative, control transitions to step 2406.

[0158] In step 2406 of Figure 24, the weak correlation event processing unit 2400 determines whether the correlation intensity value 1202 in the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" has changed from t2 or greater to less than t2, before and after the reduction process of the correlation intensity value 1202 in step 2404. Here, t2 may be the derived extinction threshold shown in Figure 29. Figure 29 shows an example where the derived extinction threshold t2 is 40, but the value of the derived extinction threshold t2 may be arbitrary. If the determination result in step 2406 is positive (i.e., the correlation intensity value 1202 has changed from t2 or greater to less than t2), control proceeds to step 2407. If the determination result in step 2406 is negative, step 2407 is skipped, and control proceeds to step 2408.

[0159] In step 2407 of Figure 24, the weak correlation event processing unit 2400 sets the derivation flag 1203 in the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" to OFF. In other words, since the correlation strength value 1202 corresponding to the combination of device A and device K has fallen below the derivation extinction threshold t2, the derivation from the correlation 162 between device A and device K to the relationship (device group relationship 164 and group mutual relationship 165) is considered to have disappeared. As a result of this derivation flag 1203 being turned OFF, the judgment result in step 2501 of Figure 25 becomes positive. After step 2407, control transitions to step 2408.

[0160] In step 2408 of Figure 24, the weak correlation event processing unit 2400 determines whether the correlation strength value 1202 in the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" has reached a predetermined minimum value. The predetermined minimum value can be arbitrary, but for example, the predetermined minimum value may be zero. If the determination result in step 2408 is positive, control proceeds to step 2409. If the determination result in step 2408 is negative, the correlation information record for the combination of device A and device K is not yet deleted, so control returns to step 2401, and the weak correlation event processing unit 2400 waits until the next "weak correlation event" is detected.

[0161] In step 2409 of Figure 24, the weak correlation event processing unit 2400 deletes the correlation information record for the combination of device A and device K corresponding to the "weak correlation event" from the correlation information table 1200 (or correlation information table 1300). By performing such deletions, it is expected that the number of combinations of devices 172 managed by the correlation information table 1200 will be optimized. After step 2409, control is returned to step 2401, and the weak correlation event processing unit 2400 waits until the next "weak correlation event" is detected.

[0162] 4-2-3-7. Processing of Derived Annihilation Events Processing Unit Figure 25 shows a flowchart of the processing of the derived event processing unit 2500. The following explanation will follow the order of processing shown in Figure 25. Each processing step in the flowchart of Figure 25 can be understood as forming a "derived event processing step". The following functions and processes are implemented, making it possible to identify combinations of device 172 and group 175 where, due to the disappearance of a derivative (that previously existed), the device group association 164 may cease to exist. Furthermore, it is possible to identify combinations of groups 175 where, due to the disappearance of a derivative (that previously existed), the group mutual association 165 may cease to exist.

[0163] In step 2501 of Figure 25, the Derivation Deletion Event Processing Unit 2500 determines whether a derivation (which previously existed) from any correlation 162 of the device 172 combination to an association (device group association 164 or group mutual association 165) has been deleted. For example, when the weak correlation event processing unit 2400 performs the processing in step 2407 of Figure 24, the weak correlation event processing unit 2400 may notify the Derivation Deletion Event Processing Unit 2500 of the deletion of a derivation (which previously existed) from the correlation 162 between device A and device K. This notification may be in any form (e.g., in the form of an interrupt, or in the form of notification transmission via memory). Alternatively, in response to the weak correlation event processing unit 2400 turning off the derivation flag 1203 in the correlation information record for the device A and device K combination in step 2407 of Figure 24, the Derivation Deletion Event Processing Unit 2500 may detect the newly turned-off derivation flag 1203. As shown in step 2502 of Figure 25, below, the combination of devices 172 corresponding to correlation 162 (from which the previously existing derivative has disappeared) will be referred to as device A and device K.

[0164] In step 2503 of Figure 25, the derivative disappearance event processing unit 2500 identifies the combinations of devices 172 that correspond to correlations 162 that have already generated derivatives, and the combinations of devices 172 and groups 175 that correspond to existing device group associations 164, immediately after the disappearance of derivatives (that previously existed) from correlation 162 between device A and device K. For example, the derivative disappearance event processing unit 2500 identifies combinations of devices 172 indicated by correlation information records in which the derivative flag 1203 is already turned on, other than the correlation information record for the combination of device A and device K in step 2501 in which the disappearance of the derivative (which had existed until then) was detected. Specifically, the derivative disappearance event processing unit 2500 refers to the first device ID 801-1 and the second device ID 801-2 in the correlation information record in which the derivative flag 1203 is already turned on. For example, the derived event processing unit 2500 identifies the combination of device 172 and group 175 indicated by an existing device group relationship information record. Specifically, the derived event processing unit 2500 refers to device ID 801 and group ID 901 in an existing device group relationship information record. The graph showing the combinations of devices 172 together and the combinations of device 172 and group 175, as identified above, is denoted as G(A,K). Graph G(A,K) shows the "relationships" or "interconnectivity" between devices 172 and group 175, formed from the correlation 162 that has already generated a derivative and the existing device group association 164, immediately after the disappearance of the derivative from the correlation 162 between device A and device K (which previously existed).

[0165] In step 2504 of Figure 25, the Derived Annihilation Event Processing Unit 2500 finds the set of devices 172 that can be traced from device A based on graph G(A,K), and sets this set as set_of_d(A). Here, devices 172 that can be traced from device A mean devices 172 that can be reached starting from device A by correlations 162 in graph G(A,K) where derivation has already occurred. The Derived Annihilation Event Processing Unit 2500 also finds the set of groups 175 that can be traced from device A based on graph G(A,K), and sets this set as set_of_g(A). Here, groups 175 that can be traced from device A mean groups 175 that can be reached starting from device A by correlations 162 in graph G(A,K) where derivation has already occurred and existing device group associations 164. In step 2505 of Figure 25, the derived event processing unit 2500 finds the set of devices 172 that can be traced from device K based on graph G(A,K), and sets this set as set_of_d(K). The derived event processing unit 2500 also finds the set of groups 175 that can be traced from device K based on graph G(A,K), and sets this set as set_of_g(K). Here, due to the disappearance of the (previously existing) derivation from the correlation 162 between device A and device K, it is possible that there will be no device group association 164 for each combination of device 172 in set_of_d(A) and group 175 in set_of_g(K). Similarly, due to the disappearance of the (previously existing) derivation from the correlation 162 between device A and device K, it is possible that there will be no device group association 164 for each combination of device 172 in set_of_d(K) and group 175 in set_of_g(A). Furthermore, similarly, due to the disappearance of the (previously existing) derivation from the correlation 162 between device A and device K, it is possible that there will be no group inter-association 165 for each combination of group 175 in set_of_g(A) and group 175 in set_of_g(K). Furthermore, as a result of processing in steps 2504 and 2505, it is possible that the sets of devices 172 belonging to set_of_d(A) and set_of_d(K) become exactly the same, and the sets of groups 175 belonging to set_of_g(A) and set_of_d(K) become exactly the same. In this case, due to the disappearance of the derivation (which previously existed) from the correlation 162 between device A and device K, there are no device group associations 164 and group interrelationships 165 that cease to exist. In this case, in Figures 26 and 27, only the derived source record numbers within the already existing device group association information records and group interrelationship records are updated.

[0166] In step 2506 of Figure 25, the derived extinction event processing unit 2500 updates or deletes the device group relationship information record for each combination of device 172 included in set_of_d(A) and group 175 included in set_of_g(K), provided that set_of_g(K) is not an empty set. Specifically, the derived extinction event processing unit 2500 causes the device group relationship information derived extinction update unit 2600 to execute the process shown in Figure 26. If there is a device group relationship 164 that will cease to exist as a result of the process in Figure 26, the device group relationship information record for that device group relationship 164 is deleted from the device group relationship information table 1400. In step 2507 of Figure 25, the derived extinction event processing unit 2500 updates or deletes the device group relationship information record for each combination of device 172 included in set_of_d(K) and group 175 included in set_of_g(A), provided that set_of_g(A) is not an empty set. Specifically, the derived extinction event processing unit 2500 causes the device group relationship information derived extinction update unit 2600 to execute the process shown in Figure 26. If there is a device group relationship 164 that will cease to exist as a result of the process in Figure 26, the device group relationship information record for that device group relationship 164 is deleted from the device group relationship information table 1400. In step 2508 of Figure 25, the derived extinction event processing unit 2500 updates or deletes the group interrelationship information record for each combination of group 175 included in set_of_g(A) and group 175 included in set_of_g(K), provided that neither set_of_g(A) nor set_of_g(K) is empty for group 175. Specifically, the derived extinction event processing unit 2500 causes the group interrelationship information derived extinction update unit 2700 to execute the process shown in Figure 27. If there is a group interrelationship 165 that will cease to exist as a result of the process in Figure 27, the group interrelationship information record for that group interrelationship 165 is deleted from the group interrelationship information table 1500. After step 2508, control is returned to 2501, and the derived event processing unit 2500 then waits until it detects the disappearance of a derived event.

[0167] 4-2-3-8. Processing of the Device Group Relationship Information Derivation Deletion Update Unit Figure 26 shows a flowchart of the processing of the device group relationship information derivation and deletion update unit 2600. The following explanation will follow the order of processing shown in Figure 26. Note that each processing step in the flowchart of Figure 26 may be understood to form a "device group relationship derivation and deletion update step". The functions and processes described below are implemented so that changes in information related to device group relationships 164 due to the disappearance of a derivative (which previously existed) can be appropriately determined, and the determined changes can be reflected in the device group relationship information table 1400. Furthermore, if device group relationships 164 cease to exist due to the disappearance of a derivative (which previously existed), this fact can be reflected in the device group relationship information table 1400.

[0168] In step 2601 of Figure 26, the device group relationship information derivation and deletion update unit 2600 determines whether to update or delete the device group relationship information record due to the deletion of a derivation from correlation 162 (which previously existed). For example, if the derivation and deletion event processing unit 2500 decides in step 2506 of Figure 25 to update or delete the device group relationship information record for the combination of device 172 included in set_of_d(A) and group 175 included in set_of_g(K), the derivation and deletion event processing unit 2500 notifies the device group relationship information derivation and deletion update unit 2600 of this. Alternatively, if the derivation and deletion event processing unit 2500 decides in step 2507 of Figure 25 to update or delete the device group relationship information record for the combination of device 172 included in set_of_d(K) and group 175 included in set_of_g(A), the derivation and deletion event processing unit 2500 notifies the device group relationship information derivation and deletion update unit 2600 of this. In the following explanation of Figure 26, the set of devices 172 mentioned above is denoted as set_of_d, and the set of groups 175 mentioned above is denoted as set_of_g.

[0169] In step 2602 of Figure 26, the device group relationship information derivation and deletion update unit 2600 selects one of the devices 172 included in set_of_d and designates it as device L. The device group relationship information derivation and deletion update unit 2600 also selects one of the groups 175 included in set_of_g and designates it as group M. In other words, the combination of device L and group M is selected as a candidate for a device group relationship 164 that does not exist (a candidate for relationship setting cancellation).

[0170] In step 2603 of Figure 26, the device group relationship information derivation and deletion update unit 2600 determines whether a device group relationship information record exists in the device group relationship information table 1400 of Figure 14 for the combination of device L and group M selected in the most recent step 2602. If the determination result in step 2603 is positive, control proceeds to step 2604. If the determination result in step 2603 is negative, since the device group relationship 164 between device L and group M never existed in the first place, steps 2604, 2605, 2606, and 2607 are skipped, and control proceeds to step 2608.

[0171] In step 2604 of Figure 26, the device group relationship information derivation and deletion update unit 2600 refers to the device group relationship information table 1400 in Figure 14 to determine whether the relationship fixing flag 1402 in the device group relationship information record for the combination of device L and group M is ON. If the result of the determination in step 2604 is positive (the relationship fixing flag 1402 is ON), it is not permitted to make the device group relationship 164 between device L and group M nonexistent, so steps 2605, 2606, and 2607 are skipped and control transitions to step 2608. If the result of the determination in step 2604 is negative (the relationship fixing flag 1402 is OFF), control transitions to step 2605.

[0172] In step 2605 of Figure 26, the device group relationship information derivation and deletion update unit 2600 updates the source record number group 1403 in the device group relationship information record for the combination of device L and group M selected in the most recent step 2602. Specifically, the device group relationship information derivation and deletion update unit 2600 deletes from the source record number group 1403 the information that identifies the correlation 162 (which previously existed) whose derivation has disappeared. In other words, the device group relationship information derivation and deletion update unit 2600 deletes from the source record number group 1403 the information that indicates the combination of device A and device K. As shown in Figures 12 and 13, if each correlation information record in the correlation information table 1200 has a record number 1201, then in step 2605, the device group relationship information derivation deletion update unit 2600 may delete record number 1201 (and the record numbers associated with that record number) in the correlation information record for the combination of device A and device K from the derived source record number group 1403. For example, let's explain a case where the derivation from the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1) disappears as the situation changes from the upper part of Figure 2 to the lower part of Figure 2. In this case, as shown by the change from correlation information table 1200 in Figure 12 to correlation information table 1300 in Figure 13, the derivation flag 1203 of the correlation information record for the combination of camera 3 (cam3) and wearable device 1 (wear1) is turned off (OFF). The record number 1201 in that record is "c2". The device group relationship information derivation disappearance update unit 2600 deletes the record number "c2" (and the record numbers associated with the record number "c2") if the group of source record numbers 1403 in each device group relationship information record included in the device group relationship information table in Figure 14 contains the record number "c2". In the example in Figure 14, the "c2-c5" portion is deleted from the derived record number group 1403 within the device group relationship information record where record number 1401 is "r7". The "c1-c2-r5" portion is deleted from the derived record number group 1403 within the device group relationship information record where record number 1401 is "r9". The "c2-c1-r2" and "c2-r8" portions are deleted from the derived record number group 1403 within the device group relationship information record where record number 1401 is "r10". After step 2605, control transitions to step 2606.

[0173] In step 2606 of Figure 26, the device group relationship information derivation and deletion update unit 2600 determines whether the group of source record numbers 1403 in the device group relationship information record for the combination of device L and group M selected in the most recent step 2602 has become empty. In other words, the device group relationship information derivation and deletion update unit 2600 determines whether the basis for the existence of the device group relationship 164 between device L and group M has been completely lost. For example, let's explain the case where the derivation from the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1) disappears as the situation changes from the upper part of Figure 2 to the lower part of Figure 2. In this case, as shown by the change from correlation information table 1200 in Figure 12 to correlation information table 1300 in Figure 13, the derivation flag 1203 of the correlation information record for the combination of camera 3 (cam3) and wearable device 1 (wear1) is turned off (OFF). The record number 1201 in that record is "c2". Therefore, according to step 2605 above, the group of source record numbers 1403 in the device group relationship information record where record number 1401 is "r10" becomes empty. Therefore, for the device group relationship information record where record number 1401 is "r10", the judgment result in step 2606 is positive. Furthermore, after step 2605 described above, the derived source record number group 1403 in the device group relationship information record where record number 1401 is "r7" contains "c1-r9", and the derived source record number group 1403 in the device group relationship information record where record number 1401 is "r9" contains "c1-r7". However, the relationship fixing flag 1402 in the device group relationship information records where record number 1401 is "r7" and "r9" is both off (OFF), meaning that these are derived type device group relationships 164, not fixed type device group relationships 164. In other words, the derived type device group relationships 164 are each other's basis for existence (derived source). The device group relationship information derived disappearance update unit 2600 also affirms the judgment result of step 2606 in such cases. If the result of the decision in step 2606 is positive, control proceeds to step 2607. If the result of the decision in step 2608 is negative, there remains a valid basis (derived source) for the existence of the device group association 164 between device L and group M, so step 2607 is skipped and control proceeds to step 2608.

[0174] In step 2607 of FIG. 26, when the device group related information derived disappearance time update unit 2600 deletes the device group related record for the combination of device L and group M selected in the most recent step 2602 from the device group related information table 1400 of FIG. 14. By this deletion, the device group relatedness 164 between device L and group M is treated as if it no longer exists. After step 2607, the control transfers to step 2608.

[0175] In step 2608 of FIG. 26, the device group related information derived disappearance time update unit 2600 determines whether all possible combinations as the combination of the device 172 (device L) included in set_of_d and the group 175 (group M) included in set_of_g have been selected in step 2602. If the determination result in step 2608 is affirmative, the control returns to step 2601, and the device group related information derived disappearance time update unit 2600 waits until the next opportunity to update or delete the device group related record. If the determination result in step 2608 is negative, the control returns to 2602, and a combination of device L and group M that has not yet been selected is newly selected.

[0176] 4. Processing of the group mutual related information derived disappearance time update unit FIG. 27 shows a flowchart of the processing of the group mutual related information derived disappearance time update unit 2700. Hereinafter, the description will be made in accordance with the order of the processing shown in FIG. 27. Each processing step in the flowchart of FIG. 27 may be understood to form a "group mutual relatedness derived disappearance time update step". Since functions and processes as described below are realized, changes in information regarding group interrelatedness 165 associated with the disappearance of (previously existing) derivatives can be appropriately determined, and the determined changes can be reflected in the group interrelatedness information table 1500. Also, when group interrelatedness 165 ceases to exist due to the disappearance of (previously existing) derivatives, that fact can be reflected in the group interrelatedness information table 1500.

[0177] The content of the process in FIG. 27 executed by the group interrelatedness information derivative disappearance update unit 2700 and the content of the process in FIG. 26 executed by the device group relatedness information derivative disappearance update unit 2600 are the same except for the object to be processed. Therefore, the detailed description of FIG. 27 is omitted. Below, it is shown how the description regarding FIG. 26 should be read differently to become the description regarding FIG. 27. In FIG. 26, the functional unit that is the processing subject is the "device group relatedness information derivative disappearance update unit 2600", while in FIG. 27, it is the "group interrelatedness information derivative disappearance update unit 2700". In FIG. 26, the step names are respectively "step 2601", "step 2602", "step 2603", "step 2604", "step 2605", "step 2606", "step 2607", "step 2608", while in FIG. 27, they are respectively "step 2701", "step 2702", "step 2703", "step 2704", "step 2705", "step 2706", "step 2707", "step 2708". In FIG. 26, the sets being handled are the "set of devices set_of_d" and the "set of groups set_of_g", while in FIG. 27, they are the "first set of groups set_of_g(1)" and the "second set of groups set_of_g(2)". In Figure 26, the tables and records targeted for updating or deletion were the "Device Group Relationship Information Table 1400" and the "Device Group Relationship Information Records," whereas in Figure 27, they become the "Group Interrelationship Information Table 1500" and the "Group Interrelationship Information Records." In Figure 26, the selected items were "device L included in set_of_d" and "group M included in set_of_g," whereas in Figure 27, they become "group P included in set_of_g(1)" and "group Q included in set_of_g(2)."

[0178] This explains the case where the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1) disappears as the situation changes from the upper part of Figure 2 to the lower part of Figure 2. According to the group interrelationship information table 1500 in Figure 15, in the situation shown at the top of Figure 2, the group interrelationship record with record number 1501 being "g3" records five groups consisting of "r5-r10", "r5-c2-c1-r2", "r5-c2-r8", "r7-c1-r2", and "r7-r8" in the derived source record number group 1403. As already shown in the explanation for Figure 26, when the derivation (which previously existed) from the correlation 162 between camera 3 (cam3) and wearable device 1 (wear1) disappears, the derivation flag 1203 in the correlation information record with record number 1201 "c2" is turned off (OFF), and the device group relationship information records with record numbers 1401 "r7", "r9", and "r10" are deleted from the device group relationship information table 1400. Therefore, all five groups included in the derived source record number group 1403 within the group interrelationship record where record number 1501 is "g3" are subject to deletion in step 2705. Specifically, because the derivative flag 1203 of the correlation management record with record number 1201, "c2", has been turned off, "r5-c2-c1-r2" and "r5-c2-r8" will be subject to deletion in step 2705. Following the deletion of the device group relationship information record with record number 1401, "r7", "r7-c1-r2" and "r7-r8" will be subject to deletion in step 2705. As a result of deleting the device group relationship information record with record number 1401, "r10", "r5-r10" will be subject to deletion in step 2705. Combining the above, all five groups consisting of "r5-r10", "r5-c2-c1-r2", "r5-c2-r8", "r7-c1-r2", and "r7-r8" within the group relationship record 1403 derived from record number 1501, which is "g3", are subject to deletion by step 2705. Therefore, the group relationship record with record number 1501 being "g3" is subject to deletion in step 2707. In other words, in the situation shown at the bottom of Figure 2, the group relationship 165 between the relatively lower worker 1 and the relatively higher process 1 is treated as if it no longer exists.

[0179] 4-2-3-10. Processing of the fixed setting section The fixed setting unit 378, which is a functional unit of the correlation analysis system 101, may control the display included in the display or output device 3607 of the correlation analysis system 101, or the display of another system, to display a screen like that shown in Figure 28. Alternatively, the fixed setting unit 388, which is a functional unit of the metadata management system 302, the fixed setting unit, which is a functional unit of the development environment system 303, or the fixed setting unit, which is a functional unit of the data utilization system 304, may control the display of any of these systems to display a screen like that shown in Figure 28.

[0180] Figure 28 shows the fixed settings screen 2800. The example in Figure 28 corresponds to the situation at the top of Figure 2. The fixed settings unit 378 displays the information as shown in Figure 28 based on the information obtained from the correlation information table 1200, the device group relationship information table 1400, the group interrelationship information table 1500 (and, if necessary, the device management information table 800 and the group management information table 900).

[0181] A person who accesses the fixed settings screen 2800 shown in Figure 28 uses a mouse or the like included in the input device 3606 to input which of the following items they want to fix: the occurrence of derivation from correlation 162, the existence of device group association 164, and the existence of group inter-association 165. In the example in Figure 28, the group relationship 165 of the derived type, where the relatively lower-level group 175 is worker 2 and the relatively higher-level group 175 is process 2, is specified by a cursor operated by a mouse or the like (a white arrow in Figure 28). In the example in Figure 28, the group relationship 165 is shown as a fixed relationship, but what is fixed may also be the generation of a derivative from correlation 162 or device group relationship 164. In Figure 28, when a cursor is selected, a pop-up window appears with the message "The relationship between worker2 and proc2 will be fixed. Cancel / Execute," confirming the final decision to proceed with the fixation. Then, when the "Execute" icon is pressed with a cursor operated by a mouse or the like, input information specifying the relationships whose derivation / existence to be fixed (the occurrence of derivation from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165) is transmitted to the fixation setting unit 378. When input information is transmitted, the fixed setting unit 378 performs fixing for the specified relationships (the occurrence of derivation from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165). In the example in Figure 28, the group interrelationship 165 of the derived type, in which the relatively lower group 175 is worker 2 and the relatively higher group 175 is process 2, is the target of fixing. Therefore, the fixed setting unit 378 turns on the relationship fixing flag 1402 in the group interrelationship information record with record number 1501, "g4", in the group interrelationship information table 1500 in Figure 15. The fixed setting unit 378 may further control the display of the group interrelationship 165 of the derived type, in which the relatively lower group 175 is worker 2 and the relatively higher group 175 is process 2, in the fixed setting screen 2800 in Figure 28, to change it to the display of the group interrelationship 165 of the fixed type. The above was an example of fixing group interrelationships 165, but the fixing setting unit 378 may turn on the derivation fixing flag 1204 in a predetermined record in the correlation information table 1200 in Figure 12 or Figure 13 when fixing the occurrence of derivations from correlations 162. Similarly, the fixing setting unit 378 may turn on the relationship fixing flag 1402 in a predetermined record in the device group relationship information table 1400 in Figure 14 when fixing the existence of device group relationships 164.

[0182] A user who accesses the fixed settings screen 2800 shown in Figure 28 may use the mouse or other input device included in the input device 3606 to specify which of the following items they wish to unfix: the occurrence of a derivative from correlation 162, the existence of a device group relationship 164, or the existence of a group interrelationship 165. The operation of the mouse or other device to unfix the fixation, and the processing of the fixed settings unit 378, may be the same as those described above. However, in order to unfix the fixation, the relationship fixing flag 1402 and the derivative fixing flag 1204 described above are turned off.

[0183] As the functions and processes described above are realized, users of the correlation analysis system 101, users of the metadata management system 302 (e.g., administrator 401), users of the development environment system 303 (e.g., developer 393), and users of the data utilization system 304 (e.g., data user 394) can set which of the following to be fixed or unfixed among the occurrence of derivatives from correlation 162, the existence of device group relationships 164, and the existence of group interrelationships 165, as intended. Furthermore, the fixed settings described above can be utilized when a new device 172 is installed. For example, after a new device 172 is installed, a derivative may arise from some correlation 162 involving the installed device 172, based on the device data 182 output from the installed device 172 and the device data 182 output from other devices 172 that were already installed. Then, some derivative type of device group relationship 164 involving the installed device 172 may come into existence. In this way, a person who comes into contact with the derivative type of device group relationship 164 that has come into existence as a result of the new installation of device 172 (for example, an administrator 401, a developer 393) can use the fixed settings screen 2800 to change the derivative type of device group relationship 164 to a fixed type of device group relationship 164.

[0184] 4-2-3-11. Processing of the parameter setting section The parameter setting unit 319, which is a functional unit of the correlation analysis system 101, may control the display included in the display or output device 3607 of the correlation analysis system 101, or the display of another system, to display a screen like that shown in Figure 29. Alternatively, the parameter setting unit 329, which is a functional unit of the metadata management system 302, the parameter setting unit, which is a functional unit of the development environment system 303, or the parameter setting unit, which is a functional unit of the data utilization system 304, may control the display of any of these systems to display a screen like that shown in Figure 29.

[0185] Figure 29 shows the parameter setting screen 2900. In the example in Figure 29, the parameter setting screen 2900 allows you to set the values ​​of each parameter used in the strong correlation event processing unit 2000, the "derivative occurrence threshold (t1)", the "derivative disappearance threshold (t2)", the "correlation strength increase / decrease amount (t3)", the "correlation event detection period (k)", and the "correlation event detection period (k)", the "correlation event detection unit 1900". Note that parameters other than those shown in Figure 29 may also be settable, and some or all of the parameters shown in Figure 29 may not be settable. On the parameter setting screen 2900, a horizontal seek bar image is displayed for each parameter. The parameter value can be set by manipulating the position of the slider on this seek bar with a mouse or other means. Note that parameter values ​​may also be entered using methods other than the horizontal seek bar method shown in Figure 29. For example, the parameter value may be entered numerically into a text box. When information about the parameter settings is entered via the parameter setting screen 2900 or the like, that information is transmitted to the parameter setting unit 319. Based on the entered information, the parameter setting unit 319 updates the contents of the parameter 399 shown in Figure 5.

[0186] As the functions and processes described above are realized, users of the correlation analysis system 101, users of the metadata management system 302 (e.g., administrator 401), users of the development environment system 303 (e.g., developer 393), and users of the data utilization system 304 (e.g., data user 394) can adjust the sensitivity in detecting strongly correlated and weakly correlated events, as well as the sensitivity in determining the occurrence and disappearance of derivatives. For example, by actually acquiring device data 182 from the field, information can be collected to understand the situation at the site, and sensitivity adjustments can be made at the same time.

[0187] 3. Functions, processes, and information involved in building and modifying the application of 4 (Figure 6) The correlations 162, device group correlations 164, and group correlations 165 detected and managed by the correlation analysis system 101 can be used for various purposes related to the handling of devices 172 and groups 175. Below, as an example of such a use, the utilization of the correlations 162, device group correlations 164, and group correlations 165 to build or modify an application related to the handling of devices 172 and groups 175 is taken up. That is, in this section, the functional components, processes, and information involved when the development environment system 303 builds or modifies an application are described. With the functional components, processes, and information described below, in the construction and development of an application that uses the device data 182 acquired from the field, the developer 393 can quickly and accurately identify the device 172 that serves as the information source for obtaining the desired information, and can also quickly and accurately generate the application code (or functional block) that includes the process for obtaining the desired information.

[0188] Figure 6 shows the functional components 600 (and the information handled) when building or modifying an application that uses the device data 182 output from each of the devices 172 at the site in the development environment system 303.

[0189] First, the correlation-related information providing unit 323, which is a functional part of the meta information management system 302, transmits correlation-related information to the development environment system 303. The correlation-related information here refers to information regarding the occurrence of derivations from the correlations 162 between devices 172, the existence of device group correlations 164 between devices 172 and groups 175, and the existence of group correlations 165 between groups 175. The correlation and relationship information providing unit 323 acquires information from the correlation information table 1200, the device group relationship information table 1400, and the group interrelationship information table 1500 in order to form the correlation and relationship information to be transmitted. In addition, depending on the extent to which users of the development environment system 303 (e.g., developers 393) refer to information regarding device 172 and group 175, the correlation and relationship information providing unit 323 may acquire information from the device management information table 800 and the group management information table 900 in order to form the correlation and relationship information to be transmitted. The timing at which the correlation and relationship information provision unit 323 transmits the correlation and relationship information to the development environment system 303 after forming the correlation and relationship information is arbitrary. For example, this could be the timing when a person using the development environment system 303 to build or modify an application (e.g., a developer 393) starts working on building or modifying an application on the development environment system 303. In this case, the development environment unit 330, which is a functional unit of the development environment system 303, starts operating according to this timing, and the development environment unit 330 may instruct the correlation and relationship information acquisition unit 333, which is a functional unit of the development environment system 303, to acquire correlation and relationship information. Upon receiving the instruction, the correlation and relationship information acquisition unit 333 instructs the metadata management system 302 to provide the correlation and relationship information. The correlation and relationship information acquisition unit 333 then acquires the correlation and relationship information transmitted from the correlation and relationship information provision unit 323. The correlation and relationship information acquisition unit 333 may store the acquired correlation and relationship information in the correlation and relationship information buffer 338 held by the development environment system 303. Alternatively, the correlation and relationship information provision unit 323 may periodically, or whenever there is a change in any of the information in the correlation information table 1200, the device group relationship information table 1400, or the group interrelationship information table 1500, form correlation and relationship information and transmit it to the development environment system 303. In this case, the correlation and relationship information acquisition unit 333 may store the correlation and relationship information in the correlation and relationship information buffer 338 each time it acquires the transmitted correlation and relationship information.

[0190] The development environment unit 330 may use the correlation and relationship information stored in the correlation and relationship information buffer 338 to determine if there has been any change in any of the following: the occurrence of a derivation from a correlation 162 between devices 172, the existence of a device group relationship 164 between device 172 and group 175, or the existence of a group interrelationship 165 between groups 175. Based on the changes in the correlation and relationship information, the development environment unit 330 may identify information acquired when the application being modified is executed that may require a change in the device 172 that serves as the source of that information. The development environment unit 330 may display information on the development environment screen presented to users of the development environment system 303 (e.g., developers 393) regarding information that may require a change in the device 172 that serves as the source of information acquired when the application being modified is executed.

[0191] Figure 30 shows the low-code development environment screen 3000. The development environment unit 330 controls the display of the low-code development environment screen 3000 shown in Figure 30 on the display of the development environment system 303 (or on the display of some system located remotely from the perspective of the development environment system 303) when an application is built or modified. The development environment unit 330 may first control the display to show a rounded rectangle in the upper left of Figure 30. In the upper left of Figure 30, the functions of the application to be built or modified, namely "Function α," "Function β," "Function γ," and "Function δ," are shown as small rounded rectangular icons. Also in the upper left of Figure 30, the exchange of information between "Function α" and "Function γ," between "Function β" and "Function γ," and between "Function γ" and "Function δ" are shown as curves between the respective icons for "Function α," "Function β," "Function γ," and "Function δ."

[0192] When an application is modified, a notification may be displayed on a screen like the one in the upper left of Figure 30 indicating that it may be necessary to change the device 172 that serves as the source of information acquired when the application is executed. For example, if it becomes necessary to change the device 172 that serves as the source of information used in the processing of "Function α", a pop-up display with an exclamation mark (correlation / association change warning) may be added to the "Function α" icon, as shown in the upper left of Figure 30.

[0193] When building or modifying an application, users of the development environment system 303 (e.g., developers 393) may use an input device such as a mouse to click on icons such as "Function α," "Function β," "Function γ," and "Function δ" in the screen shown in the upper left of Figure 30. (Note that each icon is clickable regardless of whether the aforementioned correlation relationship change warning is displayed or not.) In response to a click, the development environment unit 330 may control the display to show a rounded rectangle in the upper right of Figure 30. The upper right of Figure 30 shows what is displayed on the screen after the "Function α" icon is clicked. The upper right of Figure 30 has an editable display of the details of the function performed by the clicked function (in this case, "Function α"). The upper right of Figure 30 shows, in particular, the display of the icon "cam3: worker1 information acquisition function," which is a function block that acquires image data (video data) of worker 1, which is information used in the processing of "Function α," from camera 3 (cam3). When modifying the application, a correlation / relevance change warning may be displayed, as mentioned above. In the upper left of Figure 30, there is a speech bubble with an exclamation mark (correlation / relevance change warning) for "Function α," so that users of the development environment system 303 (e.g., developer 393) can quickly and accurately identify the parts of the application that have been modified. Also, when the icon for "Function α" is clicked, the display in the upper right of Figure 30 is shown, and in this display in the upper right of Figure 30, a speech bubble with an exclamation mark (correlation / relevance change warning) may be displayed on the icon labeled "cam3: worker1 information acquisition function." Users of the development environment system 303 (e.g., developer 393) who see this display can understand that camera 3 (cam3) is no longer appropriate as a source of image data (video data) of worker 1, which is the information used in the processing of "Function α."

[0194] As shown in the upper right of Figure 30, users of the development environment system 303 (e.g., developer 393) modify the code of the function block corresponding to the icon labeled "cam3: worker1 information acquisition function". More specifically, users of the development environment system 303 (e.g., developer 393) rewrite the function block to acquire image data (video data) of worker 1, which is the information used in the processing of "function α", from an appropriate camera. To do this, it becomes necessary to identify the camera among the devices 172 that will be the source of the image data (video data) of worker 1, which is the information used in the processing of "function α". Therefore, a user of the development environment system 303 (for example, a developer 393) who is touching the display in the upper right of Figure 30 clicks the "Device Search Call" icon included in the display in the upper right of Figure 30 using an input device such as a mouse. In response to the click, the development environment unit 330 calls the device search unit 331, which is a functional unit of the development environment system 303. The device search unit 331 may be controlled to display the device search screen 3100 shown in Figure 31 on the display of the development environment system 303 (or on the display of some system that is remotely located from the perspective of the development environment system 303).

[0195] Figure 31 shows the device search screen 3100. In the display shown in the upper right of Figure 30, when the "Device Search Call" icon is clicked, the screen shown as a rounded rectangle at the top of Figure 31 may be displayed first. In order for the display shown at the top of Figure 31 to be displayed, the device search unit 331 reads the correlation and relationship information stored in the correlation and relationship information buffer 338 and grasps information regarding the occurrence of derivation from correlation 162 between devices 172, the existence of device group relationship 164 between device 172 and group 175, and the existence of group interrelationship 165 between groups 175. The device search unit 331 then controls the system to display the grasped information as a graph or the like, thereby realizing a display like the one at the top of Figure 31. The example shown at the top of Figure 31 shows a case where, from the situation at the top of Figure 2, worker 1 moves from the workspace of process 1 to the workspace of process 2, resulting in the situation at the bottom of Figure 2.

[0196] In the display shown at the top of Figure 31, in addition to graphs showing the occurrence of derivations from correlations 162 between devices 172, the existence of device group relationships 164 between device 172 and group 175, and the existence of group relationships 165 between groups 175, there may be a search window for device searching, as shown in the upper left of the display at the top of Figure 31. Users of the development environment system 303 (e.g., developers 393) may enter the group ID 901 and group name 902 of group 175 into the text input field of the search window and then click the "Search" icon with a mouse or the like. In the example at the top of Figure 31, "worker1," which is the group ID 901 of worker 1, has been entered as text and then clicked with a mouse or the like (in Figure 31, the cursor operated by the mouse or the like is shown as a white arrow). Alternatively, instead of the method shown at the top of Figure 31, a method may be used in which the user clicks an icon representing group 175 (for example, the "worker1" icon) with a mouse or the like in a graph display that shows the occurrence of derivations from correlations 162 between devices 172, the existence of device group relationships 164 between devices 172 and group 175, and the existence of group relationships 165 between groups 175. In any case, as shown at the top of Figure 31, by specifying "worker1" to indicate worker 1, devices 172 that have a relationship (device group relationship 164) with worker 1 (worker1) will be searched for.

[0197] The device search unit 331 uses the correlation and relationship information stored in the correlation and relationship information buffer 338 to search for devices 172 that have a device group relationship 164 with the designated group 175, as shown at the top of Figure 31. The case shown at the top of Figure 31 corresponds to the situation at the bottom of Figure 2. Therefore, in this case, the device search unit 331 identifies wearable terminal 1 (wear1) and camera 2 (cam2) as devices 172 that have a device group relationship 164 with worker 1 (worker1). The device search unit 331 may be controlled to display a rounded rectangle, as shown at the bottom left of Figure 31, to clearly indicate the relationship between the identified device 172 and the designated group 175, as shown at the top of Figure 31.

[0198] In the case of Figure 30, in order to recreate the function block that acquires image data (video data) of worker 1, which is information used in the processing of "function α", from an appropriate camera, a user of the development environment system 303 (e.g., a developer 393) who is touching the display in the lower left of Figure 31 may click the "cam2" icon (the icon indicating camera 2) in Figure 31. In other words, in the display shown in the lower left of Figure 31, wearable terminal 1 (wear1) and camera 2 (cam2) are shown as devices 172 with which worker 1 (worker1) has a device group relationship 164, so a user of the development environment system 303 (e.g., a developer 393) may click the "cam2" icon, which indicates camera 2, using a mouse or the like (in Figure 31, the cursor operated by the mouse or the like is shown as a white arrow). In response to a click in the display shown in the lower left of Figure 31, the functional block generation unit 332, which is a functional part of the development environment system 303, may generate code for a functional block to acquire device data 182 output from device 172 corresponding to the clicked icon. In the example in the lower left of Figure 31, the functional block generation unit 332 may generate a functional block to acquire image data (video data), which is device data 182 output by camera 2 (cam2), and to treat it as image data (video data) of worker 1. The functional block generated here corresponds to the icon named "cam2: worker1 information acquisition function" in the lower right of Figure 31 (and in Figure 30).

[0199] When the functional block generation unit 332 creates a functional block for acquiring device data 182 output from a specified device 172, it may require access setting information for acquiring the device data 182. This access setting information may be, for example, the URL 804 for acquiring device data, which is included in the device management information table 800 in Figure 8. Alternatively, the access setting information may be of other types. If the access setting information required for generating a functional block (e.g., the URL 804 for obtaining device data) is already provided as part of the correlation and relationship information and is stored in the correlation and relationship information buffer 338, the functional block generation unit 332 may generate the functional block using the access setting information (e.g., the URL 804 for obtaining device data) stored in the correlation and relationship information buffer 338.

[0200] If the access setting information required for generating the functional block (e.g., the URL 804 for obtaining device data) has not yet been provided to the development environment system 303, the functional block generation unit 332 transmits a request for the said access setting information (e.g., the URL 804 for obtaining device data) to the metadata management system 302. In response to a request for access setting information, the access setting information provision unit 322, which is a functional unit of the metadata management system 302, extracts the requested access setting information (e.g., the URL 804 for obtaining device data) from, for example, the device management information table 800, and transmits the extracted access setting information (e.g., the URL 804 for obtaining device data) to the development environment system 303.

[0201] The functional block generation unit 332 obtains access setting information (e.g., the URL 804 for obtaining device data) either by reading it from the correlation relationship buffer or by receiving it from the access setting information provision unit 322. The functional block generation unit 332 may generate a functional block using the obtained access setting information (e.g., the URL 804 for obtaining device data). The functional block generation unit 332 may store the code of the generated functional block in the functional block code buffer 337 held by the development environment system 303.

[0202] Users of the development environment system 303 (e.g., developers 393) may use the functional blocks generated by the functional block generation unit 332 to build or modify applications. To this end, the development environment unit 330 may read the functional block code stored in the functional block code buffer 337 and apply it to the application under development 334 handled by the development environment system 303. In the lower part of Figure 30, the displays shown in the center and on the right indicate that when the application is modified, the function block "cam2:worker1 information acquisition function," which is generated as shown in Figure 31, will be used for "function α" instead of the function block "cam3:worker1 information acquisition function."

[0203] As shown in Figures 30 and 31, the constructed or modified application may be ported (installed) to the data utilization system 304. Figure 6 shows that after the construction or modification of the development application 334 in the development environment system 303 is completed, the constructed or modified application is ported (installed) to the data utilization system 304 as application 344.

[0204] Furthermore, the development environment system 303 may have functions other than those performed by the device search unit 331, such as searching for devices 172 with which a device group relationship 164 exists with a specified group 175, searching for other devices 172 associated with the specified device 172 by a correlation 162 that has been derived from it, searching for groups 175 with which a device group relationship 164 exists with the specified device 172, and searching for groups 175 with which a group relationship 165 exists with the specified group 175.

[0205] 4.4. Functional configuration, processing, and information involved in application execution (Figure 7) Figure 7 shows the functional configuration 700 (and the information handled) when an application using device data 182 output from each of the devices 172 located on-site is executed on the data utilization system 304. The application execution unit 342, which is a functional part of the data utilization system 304, executes the object code of the application 344, for example, in response to input information indicating execution instructions from the data user 394. The application execution unit 342 then controls the application 344 to display or output information for use by the data user 394 while the application 344 is running. If the application execution unit 342 contains code or other information within the functional blocks of the application 344 that indicates the acquisition of desired information, it requests the data request unit 343 to acquire the desired information. The data request unit 343, which is a functional unit of the data utilization system 304, extracts access setting information for obtaining the desired information from a functional block containing a code indicating that the desired information should be obtained. The access setting information here may be, for example, the URL 804 for obtaining device data managed for each device ID 801 (device name 802) in the device management information table 800 in Figure 8. Alternatively, the access setting information may take any form as long as it is setting information for obtaining the desired information. The data request unit 343 obtains the desired information (device data 182) using access setting information (for example, the URL 804 for obtaining device data) to obtain device data 182 output from the device 172 that serves as the information source when acquiring the desired information. The desired information (device data 182) may be obtained directly from the information source device 172. Alternatively, the desired information (device data 182) may be obtained indirectly by being transferred from the information source device 172 to the collection information database 355 (collection information DB) in the data collection system 305. The data request unit 343 may store the acquired desired information (device data 182) in the device data buffer 345 within the data utilization system 304. The application execution unit 342 may then continue executing the application using the desired information (device data 182) stored in the device data buffer 345.

[0206] As the functions and processes described above are realized, when executing an application that uses device data 182 acquired from the field, the desired information from the information source device 172 can be accurately acquired.

[0207] 5. Other (Variations) This disclosure is not limited to the embodiments described above and includes various modifications. Some of the configurations and processes of the embodiments may be replaced with configurations and processes of other conceivable embodiments. Configurations and processes of other conceivable embodiments may be added to the configurations and processes of the embodiments. For example, the following modifications of the embodiments may be made in this disclosure.

[0208] (Variation A) Simplification of relevance information In the embodiment shown above, the group of derived record numbers 1403 held by the device group relationship information records, which are records in the device group relationship information table 1400 in Figure 14, and the group interrelationship information records, which are records in the group interrelationship information table 1500 in Figure 15, contained relatively detailed information. Specifically, the group of derived record numbers 1403 held, as comprehensively as possible, information that identifies the correlation 162 from which the derivation occurred (record number 1201 of the correlation information record), which is the basis for the existence of the device group relationship 164 or group interrelationship 165 indicated by the record to which the group of derived record numbers 1403 belongs, and information that identifies other device group relationships 164 (record number 1401 of other device group relationship records). For example, in the case where the situation changes from the upper part of Figure 2 to the lower part of Figure 2, a derivation occurs from the correlation 162 between camera 2 (cam2) and wearable device (wear1) after the situation becomes the lower part of Figure 2, and a device group relationship 164 between camera 2 (cam2) and worker 1 (worker1) comes into existence with the occurrence of this derivation. In this case, in the above embodiment, as indicated by the record with record number 1401 "r13" (device group relationship record) in the device group relationship information table 1400 of Figure 14, the group of derived record numbers 1403 may include "c4-r5". Here, "c4" indicates record number 1201 of the correlation information record that shows the correlation 162 between camera 2 (cam2) and wearable device (wear1) that occurred after the situation became the lower part of Figure 2. On the other hand, "r5" indicates record number 1401 of the device group relationship record, which shows a fixed type device group relationship 164 between wearable device 1 (wear1) and worker 1 (worker1). The embodiments described above use the derived record number group 1403 to relatively accurately show the basis for the existence of device group relationships 164 or group relationships 165, thus allowing for relatively accurate tracking of changes in the existence or non-existence of device group relationships 164 and group relationships 165 in response to changes in the field situation. On the other hand, the processing shown in Figures 21, 22, 23, 25, 26, and 27 can be relatively complex.

[0209] Therefore, while Modification A may be somewhat inaccurate in terms of tracking changes in the existence or non-existence of device group relationships 164 and group interrelationships 165 in response to changes in the field situation, it simplifies the information stored in the derived source record number group 1403 in the records within the device group relationship information table 1400 (device group relationship information records) and the records within the group interrelationship information table 1500 (group interrelationship information records). Specifically, in Modification A, the derived source record number group 1403 may only hold information that identifies the correlation 162 from which the derivation occurred, which was the direct trigger for the existence of the device group relationship 164 or group interrelationship 165 indicated by the record to which the derived source record number group 1403 belongs (record number 1201 of the correlation information record). (In Modification A, since the derived source record number group 1403 can hold at most one record number in each device group relationship information record or group interrelationship information record, the derived source record number group 1403 may also be called the "derived source record number.") For example, in the case where the situation changes from the upper part of Figure 2 to the lower part of Figure 2, a derivation occurs from the correlation 162 between camera 2 (cam2) and wearable device (wear1) after the situation in the lower part of Figure 2 is reached, and along with the occurrence of this derivation, a device group relationship 164 between camera 2 (cam2) and worker 1 (worker1) is established. In this case, in modified example A, the group of derived record numbers 1403 (which may also be called the "derived record number" in modified example A) within the record (device group relationship record) with record number 1401 "r13" in the device group relationship information table 1400 of Figure 14 may contain only "c4". Here, "c4" represents record number 1201 of the correlation information record that shows the correlation 162 between camera 2 (cam2) and wearable device (wear1) that occurred after the situation in the lower part of Figure 2 was reached. On the other hand, in modified example A, the group of derived record numbers 1403 does not contain "r5". By simplifying the group of source record numbers 1403 (which may also be called "source record numbers" in modified example A) as described above, the processing content shown in Figures 21, 22, 23, 25, 26, and 27 in the embodiment described above can also be simplified.

[0210] In the embodiments shown above, of the processes shown in Figures 21, 22, and 23 when a derivation occurs from any of the correlations 162, the process in Figure 21 may be the same in Modification A. On the other hand, in Modification A, the process in Figure 32, described later, may be performed instead of the process in Figure 22. Also, in Modification A, the process in Figure 33, described later, may be performed instead of the process in Figure 23.

[0211] Figure 32 shows the processing of the device group relationship information generation update unit (also referred to as the simplified device group relationship information generation update unit 3200) in modified example A. The processing shown in the flowchart of Figure 32 is a replacement for the processing shown in the flowchart of Figure 22.

[0212] The processing steps 2201, 2202, 2203, 2204, and 2207 shown in Figure 32 are the same as the processing steps 2201, 2202, 2203, 2204, and 2207 shown in Figure 22. However, in Figure 32, if the judgment result in step 2204 is positive, the control transition destination is step 2207.

[0213] If the result of the determination in step 2204 shown in Figure 32 is negative (i.e., no device group association record exists for the combination of device C and group D, and its existence is not prohibited), then step 3206 is executed. In step 3206 of Figure 32, the simplified device group relationship information generation update unit 3200 newly registers a device group relationship information record for the combination of device C and group D in the device group relationship information table 1400. During registration, the simplified device group relationship information generation update unit 3200 registers the device ID that identifies device C in the device ID 801 field, the group ID that identifies group D in the group ID 901 field, and sets the relationship fixed flag 1402 field to off (OFF). The simplified device group relationship information derivation update unit 3200 registers the record number 1201 of the correlation information record that indicates the correlation 162 that triggered the existence of the device group relationship 164, that is, the correlation 162 from which the derivation newly occurred, in the item of the source record number group 1403 (which may also be called the "source record number" in modified example A) within the newly registered device group relationship information record. Here, the simplified device group relationship information derivation update unit 3200 registers the record number 1201 of the correlation information record for the combination of device A and device B, as shown in Figure 21. After step 3206, the control transitions to step 2207 in Figure 32.

[0214] Figure 33 shows the processing of the group interrelationship information generation update unit (also referred to as the simplified group interrelationship information generation update unit 3300) in modified example A. The processing shown in the flowchart of Figure 33 is a replacement for the processing shown in the flowchart of Figure 23.

[0215] The processing steps 2301, 2302, 2303, 2304, 2305, 2306, 2307, and 2309 shown in Figure 33 are the same as the processing steps 2301, 2302, 2303, 2304, 2305, 2306, 2307, and 2309 shown in Figure 23. However, in Figure 33, if the judgment result in step 2304 is positive, the control transition destination is step 2309.

[0216] If the result of the determination in step 2304 shown in Figure 33 is negative (i.e., no group interrelationship record exists for the combination of group E and group F, and its existence is not prohibited), then step 2305 is performed, followed by either step 2306 or step 2307, and then step 3206 is performed. In step 3308 of Figure 33, the simplified group interrelationship information derivation update unit 3300 registers the record number 1201 of the correlation information record that indicates the correlation 162 that triggered the existence of the group interrelationship 165, that is, the correlation 162 from which the derivation newly occurred, in the item of the source record number group 1403 (which may be called the "source record number" in modified example A) within the group interrelationship information record newly registered in step 2306 or step 2307. Here, the simplified group interrelationship information derivation update unit 3300 registers the record number 1201 of the correlation information record for the combination of device A and device B, as shown in Figure 21. After step 3308, the control transitions to step 2309 in Figure 33.

[0217] In the embodiments shown above, instead of the processes shown in Figures 25, 26, and 27, which are the processes when a derivation from any of the correlations 162 disappears, Modification A may perform the process shown in Figure 34.

[0218] Figure 34 shows the processing of the derived disappearance event processing unit (referred to as the simplified derived disappearance event processing unit 3400) in modified example A. The processing in Figure 34 replaces the processing shown in the flowcharts of Figures 25, 26, and 27. In modified example A, instead of the derived disappearance event processing unit 2500, the device group relationship information derived disappearance update unit 2600, and the group mutual relationship information derived disappearance update unit 2700 in the embodiments shown above, the simplified derived disappearance event processing unit 3400 is used as a functional unit.

[0219] The processing steps 2501 and 2502 shown in Figure 34 are the same as the processing steps 2501 and 2502 shown in Figure 25. After step 2502 in Figure 34, control transitions to step 3403.

[0220] In step 3403 of Figure 34, the simplified derived disappearance event processing unit 3400 selects one of the existing device group relationship information records or group interrelationship information records from the device group relationship information table 1400 or the group interrelationship information table 1500. In step 3404 of Figure 34, the simplified derivative disappearance event processing unit 3400 examines the information registered in the item of the derivative source record number group 1403 (which may be called the "derivation source record number" in modified example A) within the record (device group relationship information record or group interrelationship information record) most recently selected in step 3403. The simplified derivative disappearance event processing unit 3400 determines whether the record number 1201 in the correlation information record showing correlation 162, which was deemed to have disappeared in step 2407 of Figure 24, is registered in the item of the derivative source record number group 1403 that was examined. Here, the simplified derivative disappearance event processing unit 3400 determines whether the record number 1201 in the correlation information record for the combination of device A and device K in Figure 24 is registered in the item of the derivative source record number group 1403 that was examined. If the result of the determination in step 3404 is positive, control proceeds to step 3405. If the result of the judgment in step 3404 is negative, steps 3405 and 3406 are skipped, and control proceeds to step 3407.

[0221] In step 3405 of Figure 34, the simplified derived disappearance event processing unit 3400 determines whether the relationship fixing flag 1402 in the record (device group relationship information record or group mutual relationship information record) most recently selected in step 3403 is turned ON. If the result of the determination in step 3405 is positive, the deletion of the record most recently selected in step 3403 is not permitted (it is not permitted for the device group relationship 164 or group mutual relationship 165 indicated by that record to cease to exist), so step 3406 is skipped and control transitions to step 3407. If the result of the determination in step 3405 is negative, control transitions to step 3406.

[0222] In step 3406 of Figure 34, the simplified derived event processing unit 3400 deletes the record (device group relationship information record or group interrelationship information record) that was most recently selected in step 3403 from the table (device group relationship information table 1400 or group interrelationship information table 1500). After step 3406, control transitions to step 3407.

[0223] In step 3407 of Figure 34, the simplified derivative elimination event processing unit 3400 determines in step 3403 whether all records (device group relationship information records or group interrelationship information records) have been selected. If the result of the determination in step 3407 is positive, control returns to step 2501 of Figure 34, and the simplified derivative elimination event processing unit 3400 waits until the next opportunity for the derivative to disappear. If the result of the determination in step 3407 is negative, control returns to step 3403, and one of the records that has not yet been selected (device group relationship information records or group interrelationship information records) is newly selected.

[0224] (Variation B) Remote device discovery in application development and modification In the embodiment described above, as shown in the upper part of Figures 6 and 31, correlation relationship information indicating the occurrence of a derivative from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165 was transmitted from the metadata management system 302 to the development environment system 303. Then, within the development environment system 303, a search for the information source device 172 was performed locally using the correlation relationship information. With the method of the embodiment described above, as shown at the top of Figure 31, it is possible to present the overall situation of the occurrence of derivations from correlation 162, the existence of device group relationships 164, and the existence of group interrelationships 165 to users of the development environment system 303 (e.g., developers 393). Furthermore, the process of searching for the information source device 172 can be executed locally in the development environment system 303, which is expected to increase processing speed.

[0225] Modification B does not transmit the correlation and relationship information itself, which indicates the occurrence of a derivative from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165, from the metadata management system 302 to the development environment system 303. Instead, it transmits information indicating the changes in the said correlation and relationship information, as well as related information, as change information.

[0226] Figure 35 shows the functional configuration and information involved in building and modifying the application in Modified Example B. The functional configuration shown in Figure 35 replaces the functional configuration and information shown in Figure 6. Specifically, in Modified Example B, the functional unit of the development environment system 303 has the change information acquisition unit 3533 in Figure 35 instead of the correlation relationship information acquisition unit 333 in Figure 6, and the device search unit 3531 in Figure 35 instead of the device search unit 331 in Figure 6. In the functional unit of the metadata management system 302, the change information provision unit 3523 in Figure 35 replaces the correlation relationship information provision unit 323 in Figure 6. Furthermore, in Modified Example B, the device search result provision unit 3521 in Figure 35 exists as a functional unit of the metadata management system 302. Moreover, in Modified Example B, the correlation relationship information buffer 338 in Figure 6 does not need to exist as information handled by the development environment system 303. In addition, in Modified Example B, the device search result buffer 3538 in Figure 35 may exist as information handled by the development environment system 303.

[0227] In Modified Example B, the change information providing unit 3523 refers to the correlation information table 1200, the device group relationship information table 1400, and the group interrelationship information table 1500 to identify the changes in the correlation relationship information shown in these tables. In other words, in Modified Example B, the change information providing unit 3523 identifies the changes associated with the emergence of a derivative from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165, specifically those resulting from the emergence of a new derivative or the disappearance of a derivative (that previously existed). The change information providing unit 3523 combines the information indicating the changes with related information (for example, information about devices 172 and groups 175 related to the changes, which is held in the device management information table 800 and the group management information table 900) to form change information. The change information providing unit 3523 transmits the change information to the development environment system 303. In modified example B, the change information acquisition unit 3533 may acquire change information transmitted from the change information provision unit 3523 and provide the acquired change information to the development environment unit 330.

[0228] In Modification B, the development environment unit 330 uses the provided change information to determine whether it is necessary to change the device 172, which is the source of information obtained when the application to be modified is executed. If it is necessary to change the information source device 172, the result of the display control performed by the development environment unit 330 in Modification B may be the same as the display in the upper left of Figure 30 in the embodiment shown above. Furthermore, the development environment unit 330 in modified example B may be controlled to display a similar display to the upper right portion of Figure 30 in the embodiment shown above. In a display similar to the upper right display in Figure 30, when the "Device Search Display" icon is clicked with a mouse or the like, the development environment unit 330 in modified example B calls the device search unit 3531.

[0229] In Modified Example B, the device search unit 3531 may be controlled to display only the search window for device search (text input field and "search" icon) from the upper display of Figure 31 in the embodiment shown above. Alternatively, in Modified Example B, the device search unit 3531 may be controlled to display, along with the search window for device search (text input field and "search" icon) from the upper display of Figure 31 in the embodiment shown above, a graph display, etc., corresponding only to the changes in each of the changes indicated by the change information, such as the occurrence of derivation from correlation 162, the existence of device group relationship 164, and the existence of group interrelationship 165. When a group ID such as 901 is entered into the text input field of the search window for device search and the "Search" icon is clicked with a mouse, or when the icon representing group 175 in the graph display is clicked with a mouse, the device search unit 3531 in modified example B has received a search request for device 172, which will be the source of information when obtaining information about group 175.

[0230] In modified example B, the device search unit 3531 outputs a device search request to the metadata management system 302. This device search request may include information identifying group 175, which is identified either by entering information in the aforementioned search window or by clicking the icon indicating group 175 (for example, group ID 901).

[0231] In Modified Example B, the device search result providing unit 3521 refers to the device group relationship information table 1400 and identifies device 172 with which a device group relationship 164 exists between it and group 175, indicated by group ID 901 included in the device search request received from the device search unit 3531. In Modified Example B, the device search result providing unit 3521 transmits the identification information (e.g., device ID 801) of the identified device 172 to the development environment system 303 as a device search result.

[0232] In Modified Example B, the device search unit 3531 may acquire the device search result (including, for example, device ID 801) transmitted from the device search result provision unit 3521 and store the acquired device search result in the device search result buffer 3538. Furthermore, the device search unit 3531 in Modified Example B may be controlled to display the same information as the display in the lower left of Figure 31 in the embodiment shown above, based on the acquired device search result (including, for example, device ID 801).

[0233] The function of the function block generation unit 332 in modified example B may be the same as that of the function block generation unit 332 in the embodiment shown above. Furthermore, the function of the development environment unit 330 in modified example B when building or modifying an application using the function block code generated by the function block generation unit 332 may be the same as that of the development environment unit 330 in the embodiment shown above.

[0234] In modification B, the device search results transmitted from the metadata management system 302 to the development environment system 303 may include, in addition to the device ID 801, access setting information (for example, the URL 804 for obtaining device data) for obtaining the device data 182 output by the device 172 indicated by the device ID 801. In this case, it is not necessary to transmit the access setting information (for example, the URL 804 for obtaining device data) from the access setting information provision unit 322 to the functional block generation unit 332.

[0235] Furthermore, in modified form B, in addition to the functions performed by the device search unit 3531 and the device search result provision unit 3521 to search for devices 172 with which a device group relationship 164 exists with a specified group 175, there may also be functions to search for other devices 172 associated with the specified device 172 by a correlation 162 that has been derived from it, a function to search for a group 175 with which a device group relationship 164 exists with the specified device 172, and a function to search for a group 175 with which a group relationship 165 exists with the specified group 175.

[0236] The above describes the process when the application is modified in Modification B, but the process when the application is built in Modification B may be generally similar. For example, if there is no change information at all, Modification B will not transmit change information from the metadata management system 302 to the development environment system 303, and a search window for device searching (a text input field and a "search" icon) may be displayed on the device search screen, which is controlled by the device search unit 3531.

[0237] According to Modification B, the metadata management system 302 can search for the device 172, which is the source of information to be acquired for the execution of the application. Therefore, compared to the embodiment shown above, the processing load on the development environment system 303 can be reduced, and it is expected that the amount of information transmitted and received between the metadata management system 302 and the development environment system 303 will also decrease.

[0238] (Variation C) Use of object detection in camera image data (video data) In the embodiment shown above, the data processing unit 316, which is a functional part of the correlation analysis system 101, determined whether motion was detected for each time (or time period) based on the image data (video data), which is device data 182 output from the cameras (camera 1 (cam1), camera 2 (cam2), camera (cam3)). The data processing unit 316 then recorded a motion presence / absence flag 1003 indicating whether motion was detected or not for each time (or time period).

[0239] In modified example C, the data processing unit 316 may, instead of simply determining the presence or absence of movement on the screen based on the image data (video data) which is device data 182 output from the camera, detect individual objects shown on the screen. For example, the data processing unit 316 may determine the presence or absence of worker 1 and worker 2, as shown in Figures 2 and 3, and whether or not worker 1 and worker 2 are moving. For example, the data processing unit 316 may also determine the presence or absence of robots, equipment, and devices, as well as whether or not they are moving, in addition to workers. The data processing unit 316 may achieve the above determinations by inputting the image data (video data) into a trained object detection model.

[0240] According to modified example C, the correlation analysis system 101 is expected to be able to more appropriately determine the level of the correlation strength value 1202, the presence or absence of derivatives from each of the correlations 162, the presence or absence of each of the device group relationships 164, and the presence or absence of group interrelationships 165.

[0241] (Modification D) Interpretation of motion presence / absence flag in correlation event detection In the embodiment described above, as shown in steps 1903 and 1904 of Figure 19, a "strong correlation event" was detected between a device 172 and another device 172 when a "similar change" occurred within k seconds between the value of the motion presence / absence flag 1003 based on device data 182 output from one device 172 and the value of the motion presence / absence flag 1003 based on device data 182 output from another device 172.

[0242] However, regarding the movement of a conveyor belt for a certain process and the movement of workers engaged in that process, for example, when the conveyor belt is moving, the workers may remain stationary and wait, while when the conveyor belt is stationary, the workers may move and perform tasks for the process.

[0243] Therefore, in modified example D, the condition for detecting a "strongly correlated event" in step 1903 of Figure 19 may be changed from the "similar change" described above to a "change in the opposite direction," depending on the type of device 172 included in the combination of devices 172. For example, if within k seconds the movement status flag 1003 for the conveyor belt changes from "no movement" to "movement," and the movement status flag 1003 for the wearable device held by the worker changes from "movement" to "no movement," then a "strong correlation event" may be detected between the conveyor belt and the wearable device. Similarly, if within k seconds the movement status flag 1003 for the conveyor belt changes from "movement" to "no movement," and the movement status flag 1003 for the wearable device held by the worker changes from "no movement" to "movement," then a "strong correlation event" may be detected between the conveyor belt and the wearable device.

[0244] Alternatively, in modified example D, the condition for detecting a "strongly correlated event" in step 1903 of Figure 19 may be changed from the "similar change" described above to a "direction-independent change," depending on the type of device 172 included in the combination of devices 172.

[0245] According to modified example D, the detection of "strongly correlated events" and "weakly correlated events" between devices 172 can be conditioned in a way that is appropriate to the actual types and usage of each device 172.

[0246] (Variation E) Division of correlation analysis systems and metadata management systems In the embodiments described above, the correlation analysis system 101, the metadata management system 302, and the data acquisition system 305 are each shown as a single system.

[0247] In modified example E, one or more of the correlation analysis system 101, the metadata management system 302, and the data acquisition system 305 may consist of multiple partitioned systems. For example, if there are many devices 172 installed on site, these devices 172 may be divided into several groups, and each group of devices may be assigned a separate partitioned system.

[0248] According to modified example E, even if there are many devices 172 installed on site, processing can be distributed to each of the divided systems. Therefore, regardless of the number of devices 172 installed on site, it is possible to obtain information to understand the situation on site.

[0249] The technical matters shown in each of the embodiments and modifications of the embodiments described above can be combined as appropriate, as long as no technical inconsistencies arise.

Claims

1. A correlation analysis system, The correlation analysis system includes a correlation event detection unit, a correlation event processing unit, and a derivative occurrence / disappearance event processing unit. The correlation event detection unit detects strong correlation events, which are events that suggest the existence of a correlation between the devices, or weak correlation events, which are events that suggest the absence of a correlation between the devices, based on the device data obtained from each of the devices. The correlation event processing unit updates correlation information for managing the correlation strength, which is the strength of the correlation between the devices, based on the detected strong correlation event or weak correlation event. The correlation event processing unit determines, based on the correlation strength between the devices, whether the correlation between the devices leads to a relationship between them, whether such a derivation occurs or disappears. The aforementioned relationship is a device group relationship between a group and the device, or a group relationship between the groups themselves. The aforementioned derivative occurrence / destruction event processing unit updates device group relationship information for managing the presence or absence of the device group relationship based on the determined occurrence or destruction of the derivative, The aforementioned derivative occurrence / extinction event processing unit updates group interrelationship information for managing the presence or absence of group interrelationships based on the determined occurrence or extinction of the derivative, and is a correlation analysis system.

2. A correlation analysis system according to claim 1, Correlation analysis system wherein the correlation event detection unit detects the strongly correlated event or the weakly correlated event using information about the time or date when there is movement of an object detected by the device, or information about the time or date when there is no movement of the object, based on each of the device data.

3. A correlation analysis system according to claim 1, The aforementioned correlation event processing unit has a strong correlation event processing unit and a weak correlation event processing unit. The strong correlation event processing unit increases the correlation strength between the devices corresponding to the strong correlation event, and when the correlation strength becomes equal to or greater than the derivation threshold, or when the correlation strength becomes greater than the derivation threshold, it determines that a derivation to the relationship has occurred from the correlation between the devices corresponding to that correlation strength. Correlation analysis system wherein the weak correlation event processing unit reduces the correlation strength between the devices corresponding to the weak correlation event, and when the correlation strength falls below a derivation extinction threshold, or when the correlation strength becomes smaller than the derivation extinction threshold, it determines that the derivation to the relationship has disappeared from the correlation between the devices corresponding to that correlation strength.

4. A correlation analysis system according to claim 3, The correlation analysis system has a parameter setting unit, Correlation analysis system, wherein the parameter setting unit sets at least one of the following based on the input information to the correlation analysis system: the derivative occurrence threshold, the derivative extinction threshold, the amount of increase in correlation strength when a strong correlation event is detected, and the amount of decrease in correlation strength when a weak correlation event is detected.

5. A correlation analysis system according to claim 1, The aforementioned derivative occurrence / destruction event processing unit comprises a derivative occurrence event processing unit, a device group relationship information derivative occurrence update unit, a group mutual relationship information derivative occurrence update unit, a derivative / destruction event processing unit, a device group relationship information derivative / destruction update unit, and a group mutual relationship information derivative / destruction update unit. The derived event processing unit identifies candidate relationship settings, which are candidates for the device group relationship or the inter-group relationship that will come into existence as a result of the occurrence of the derived event. The device group relationship information generation and update unit determines, for each of the candidate relationship settings related to the device group relationship, whether or not the device group relationship exists, and if it is determined that the relationship exists, it updates the device group relationship information so that the device group relationship exists. The group interrelationship information generation and update unit determines, for each of the candidate relationship settings related to the group interrelationship, whether or not the group interrelationship exists, and if it is determined that it does, updates the device group relationship information so that the group interrelationship exists. The derivative disappearance event processing unit identifies candidates for the device group relationship or the group inter-relationship that will cease to exist as a result of the disappearance of the derivative, and The device group relationship information derivation and deletion update unit determines, for each of the candidate devices for deactivating the relationship setting, whether or not the device group relationship exists, and if it is determined that the relationship does not exist, it updates the device group relationship information so that the device group relationship does not exist. The group interrelationship information derivation and deletion update unit determines, for each of the candidate groups for deactivation of the relationship setting, whether or not the group interrelationship exists, and if it is determined that it does, updates the group interrelationship information so that the group interrelationship does not exist, in a correlation analysis system.

6. A correlation analysis system according to claim 1, The aforementioned derivative occurrence / destruction event processing unit comprises a derivative occurrence event processing unit, a device group relationship information derivative occurrence update unit, a group mutual relationship information derivative occurrence update unit, and a derivative / destruction event processing unit. The derived event processing unit identifies candidate relationship settings, which are candidates for the device group relationship or the inter-group relationship that will come into existence as a result of the occurrence of the derived event. The device group relationship information generation update unit includes in the device group relationship information information information that identifies the combination of devices corresponding to the correlation from which the device group relationship was derived, corresponding to the combination of the device and the group for which the existence of the device group relationship was set among the candidate relationship setting for the device group relationship. The group interrelationship information generation update unit includes in the group interrelationship information information information that identifies the combination of devices corresponding to the correlation from which the group interrelationship was derived, in association with the combination of groups that were selected as targets for setting the existence of the group interrelationship among the candidate relationships for setting the existence of the group interrelationship. The derived extinction event processing unit updates the device group relationship information so that the device group relationship does not exist when the device group relationship information is associated with information that identifies combinations of devices corresponding to the correlation for which the extinction of the derived event was determined, and when the absence of the device group relationship is permitted. The derivative extinction event processing unit is associated with information that identifies combinations of devices corresponding to the correlation in which the derivation has been determined to have been extinct, among the group relationships in which the group relationships in which the existence of the group relationships is indicated, and updates the group relationship information so that the group relationship does not exist when the absence of the group relationship is deemed acceptable.

7. A correlation analysis system according to claim 1, The correlation event processing unit, if the derivation prohibition information includes information indicating that the derivation from the correlation to the relationship of a specific combination of the devices is prohibited, suppresses the occurrence of the derivation from the correlation to the relationship of that combination. The derived occurrence and termination event processing unit suppresses the setting of the existence of the device group association for a specific combination of device and group if the device group association prohibition information includes information indicating that the existence of the device group association for that combination is prohibited. The derivative occurrence and disappearance event processing unit suppresses the setting of the existence of the group interrelationship when the group interrelationship prohibition information includes information indicating that the existence of the group interrelationship for a specific combination of the groups is prohibited.

8. A correlation analysis system according to claim 1, The correlation analysis system has a fixed setting unit, The fixed setting unit, based on the input information to the correlation analysis system, For a specific combination of the aforementioned devices, the determination of the derivation is made to the correlation information in such a way that the derivation of the relationship from the correlation between the aforementioned devices is forced to occur. For a specific combination of the device and the group, the device group relationship information can be fixed in such a way that the existence of the device group relationship between the device and the group is enforced. A correlation analysis system that applies a fixed setting to the group correlation information so as to enforce the existence of the group correlation between specific combinations of the groups.

9. A correlation analysis system according to claim 1, The group relationship information includes information that shows the hierarchical relationship between the two groups that the group relationship is based on. Each of the aforementioned groups has a set degree of relationship change, The aforementioned derivative occurrence and disappearance event processing unit, when newly establishing the existence of the interrelationship between the groups, sets the hierarchical relationship between the groups based on the degree of relationship change set for each of the groups that are the subject of the interrelationship, and is a correlation analysis system.

10. It is an integrated system, The integrated system comprises the correlation analysis system described in claim 1 and a metadata management system, The metadata management system includes a device registration acceptance unit, a device management information table, a correlation information table for holding the correlation information, a device group relationship information table for holding the device group relationship information, and a group relationship information table for holding the group interrelationship information. The correlation analysis system comprises a registration notification receiving unit and a data request unit. The device registration receiving unit receives a device registration request to request that the device be registered in the device management information table. The device registration request includes access setting information for obtaining the device data output by the device targeted by the device registration request, The device management information table holds the access setting information for each of the devices. The device registration receiving unit transmits a device registration notification to the correlation analysis system. The device registration notification includes the access settings information for the device to which the device registration notification applies. The aforementioned registration notification receiving unit receives the aforementioned device registration notification, The data request unit is an integrated system that uses the access setting information included in the device registration notification received by the device registration acceptance unit to obtain the device data for the device targeted by the access setting information.

11. It is an integrated system, The integrated system comprises the correlation analysis system described in claim 1, a metadata management system, and a development environment system. The metadata management system includes a device management information table, a correlation relationship information provision unit, an access setting information provision unit, a correlation information table for holding the correlation information, a device group relationship information table for holding the device group relationship information, and a group interrelationship information table for holding the group interrelationship information. The aforementioned development environment system comprises a development environment unit, a correlation and relationship information acquisition unit, a device search unit, and a functional block generation unit. The device management information table holds access setting information for each of the devices to obtain the device data output by that device. The correlation and relationship information provision unit provides the development environment system with information contained in one or more of the correlation information table, the device group relationship information table, or the group interrelationship information table as correlation and relationship information. The correlation and relationship information acquisition unit acquires the correlation and relationship information, The aforementioned development environment unit, based on the correlation and relationship information acquired by the correlation and relationship information acquisition unit, identifies change information, which is information regarding changes in the correlation and relationship information, and controls the system to display the change information. The device search unit is a display for searching for the device that serves as a source of device data used when the application that the development environment system is developing or modifying is executed, and controls the display to accept input information related to the search. The device search unit identifies the device that serves as the source of the device data used when the application is executed, based on the correlation and relationship information acquired by the correlation and relationship information acquisition unit and the input information. The functional block generation unit requests the metadata management system to provide the access setting information for the device identified by the device search unit. The access setting information provision unit obtains the access setting information from the device management information table and provides the access setting information to the development environment system. The functional block generation unit includes the provided access setting information in the application that the development environment system is developing or modifying, in an integrated system.

12. It is an integrated system, The integrated system comprises the correlation analysis system described in claim 1, a metadata management system, and a development environment system. The metadata management system includes a device management information table, a change information provision unit, a device search result provision unit, an access setting information provision unit, a correlation information table for holding the correlation information, a device group relationship information table for holding the device group relationship information, and a group interrelationship information table for holding the group interrelationship information. The aforementioned development environment system includes a development environment unit, a change information acquisition unit, a device search unit, and a function block generation unit. The device management information table holds access setting information for each of the devices to obtain the device data output by that device. The aforementioned change information provision unit provides the development environment system with information regarding changes in the information contained in one or more of the correlation information table, the device group relationship information table, or the group interrelationship information table, as change information. The aforementioned change information acquisition unit acquires the provided change information. The aforementioned development environment unit controls the display of the change information acquired by the change information acquisition unit, The device search unit is a display for searching for the device that serves as a source of device data used when the application that the development environment system is developing or modifying is executed, and controls the display to accept input information related to the search. The device search unit issues a device search request to the metadata management system, which is a request to identify the device that will be used as a source of device data when the application is executed, based on the input information to the development environment system. The device search result providing unit uses the information contained in one or more of the correlation information table, the device group relationship information table, or the group interrelationship information table to identify the device to be identified by the device search request, and provides the information regarding the identified device as a device search result to the development environment system. The device search unit acquires the provided device search results. The functional block generation unit requests the metadata management system to provide the access setting information for the device corresponding to the information about the device included in the device search results obtained by the device search unit. The access setting information provision unit obtains the access setting information from the device management information table and provides the access setting information to the development environment system. The functional block generation unit includes the provided access setting information in the application that the development environment system is developing or modifying, in an integrated system.

13. A correlation analysis system according to claim 1, Each of the aforementioned groups may be either a process in the product production line or inspection line, or a person engaged in the production line or inspection line. A correlation analysis system in which each of the aforementioned devices may be a sensor for detecting any of the states of the aforementioned process.

14. A correlation analysis method performed by an information processing system, The correlation analysis method comprises a correlation event detection step, a correlation event processing step, and a derived occurrence / disappearance event processing step. The correlation event detection step involves detecting strong correlation events, which are events that suggest the existence of a correlation between the devices, or weak correlation events, which are events that suggest the absence of a correlation between the devices, based on the device data obtained from each of the devices. The correlation event processing step includes a correlation strength management step and a derivative occurrence / disappearance determination step. The correlation strength management step involves updating correlation information for managing the correlation strength, which is the strength of the correlation between the devices, based on the detected strong correlation event or weak correlation event. The aforementioned derivative occurrence / extinction determination step determines, based on the correlation strength between the devices, whether the derivative from the correlation to the relationship between the devices has occurred or disappeared. The aforementioned relationship is a device group relationship between a group and the device, or a group relationship between the groups themselves. The aforementioned derived occurrence and disappearance event processing step includes a device group relationship update step and a group interrelationship update step, The device group relationship update step updates device group relationship information for managing the presence or absence of the device group relationship based on the determined occurrence or disappearance of the derivative, A correlation analysis method wherein the group correlation update step updates group correlation information for managing the presence or absence of the group correlation based on the determined occurrence or disappearance of the derivative.

15. This is a correlation analysis program, The correlation analysis program is designed to cause the information processing system to execute a correlation event detection step, a correlation event processing step, and a derived occurrence / disappearance event processing step. The correlation event detection step involves detecting, based on the device data obtained from each device, a strong correlation event, which is an event that can be used to estimate the existence of a correlation between the devices, or a weak correlation event, which is an event that can be used to estimate the absence of a correlation between the devices. The correlation event processing step includes a correlation strength management step and a derivative occurrence / disappearance determination step. The correlation strength management step involves updating correlation information for managing the correlation strength, which is the strength of the correlation between the devices, based on the detected strong correlation event or weak correlation event. The aforementioned derivative occurrence / extinction determination step determines, based on the correlation strength between the devices, whether the derivative from the correlation to the relationship between the devices has occurred or disappeared. The aforementioned relationship is a device group relationship between a group and the device, or a group relationship between the groups themselves. The aforementioned derived occurrence and disappearance event processing step includes a device group relationship update step and a group interrelationship update step, The device group relationship update step updates device group relationship information for managing the presence or absence of the device group relationship based on the determined occurrence or disappearance of the derivative, The group correlation update step updates group correlation information for managing the presence or absence of the group correlation based on the determined occurrence or disappearance of the derivative, in a correlation analysis program.

Images