JP2020194391A - Information management method, information management system, and information management program - Google Patents

Abstract

To enable appropriate information sharing.SOLUTION: An information management system 2A holds relevance data model connection information indicating relevance between a relevance data model which defines a data structure of information managed by itself and distributed relevance data models, relevance data which defines relevance between the information managed by itself and the relevance data model, and relevance data connection information indicating relevance between pieces of information on distributed relevance data. When a class of a relevance data model acquired from information management systems 2B, 2C is associated with target information, information on the relevance data related to the class selected on the basis of the relevance data model is acquired from the information management systems 2B, 2C and displayed on a user interface 7C.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information management method, an information management system and an information management program.

Traditionally, there have been many different tasks in various jobs. For example, in the transportation industry, there is a business that constitutes a transportation process from receipt of a load to delivery to a destination. In factories and offices in the manufacturing industry, there are operations that constitute the manufacturing process when manufacturing finished products.

In each business that composes each process, business information is generated and collected when the business is completed or a predetermined event occurs, and by analyzing this business information, the work efficiency in each business is optimized. There is.

However, if the department that manages each business is different, it becomes difficult to share information between departments because the management system is not unified or it is not realistic to provide all the information. Regarding information sharing between departments, there are techniques shown in Patent Documents 1 and 2.

Patent Document 1 relates to a technique relating to a method of "centrally managing distributed databases" by "apparently considering databases distributed on a network as one normalized database" and "network". In a method of managing a plurality of databases connected above, a database for information management including business use information, a database search program, and data item management information is provided, and the business use information includes the above-mentioned related to the information. Information for identifying a database search program is included, the database search program includes information for identifying data item management information related to the information, and the data item management information is on the network. A centralized management method for a plurality of databases, which includes information for identifying a database of the above-mentioned database, and accesses a database on the network by tracing business use information, a database search program, and data item management information. Is disclosed.

Patent Document 2 states that "it is managed in different systems" in order to "improve the convenience of information integration by reducing the development / operation burden, reducing costs, improving the efficiency of information integration, and expanding the applications of information integration." Correspondence between the physical model which is a data model of a plurality of information sources, the logical model which is a data model defined in advance for the user who uses the integrated information, and the physical model and the logical model. An instruction by the first integration process that stores the mapping definition indicating the relationship and returns the integration result of the logical model based on the information to be integrated of the information source defined in the physical model to the user side. Or, an instruction by the second integration process that returns the integration result of the logical model based on the information from each information source in response to the inquiry from the user side input in the physical model to the user side. Detected, referred to the mapping definition, converted the information input from each of the information sources from the physical model to the logical model, integrated the converted information, referred to the mapping definition, and converted the above. The inquiry on the user side expressed by the logical model is decomposed into a physical model corresponding to each information source, and the information searched by each information source is collected by the decomposed physical model, and the first When the instruction by the integrated process is detected, the first integrated process is executed, and when the instruction by the second integrated process is detected, the data model of the collected information is obtained from the physical model and the logical. The second integration process of converting to a model and integrating the converted information is executed, the integrated integration result is output to the user side, and the integration controlled integration result is output to the user side. The technology that "requires output to the output source of the inquiry" is disclosed.

Japanese Unexamined Patent Publication No. 8-227369 Japanese Unexamined Patent Publication No. 2011-13989

In recent years, in various jobs, there is a tendency that individual responses to detailed requests that differ for each user are required. In particular, in the manufacturing industry, cooperation between departments is indispensable in order to advance from a mass production method to a high-mix low-volume production method and to improve the overall production efficiency across a plurality of processes.

However, in the technique described in Patent Document 1, the user who retrieves the information for the first time needs to understand the structure of the database and the content of the information, but considered the optimization of the whole including other facilities in the process. In this case, when the management scale becomes large, it becomes difficult to centrally manage and grasp the contents of information.

In the technology described in Patent Document 2, information is centrally managed by an integrated engine, but when the management scale becomes large, it is difficult to create a large-scale database for aggregating and centrally managing information. There remains a problem with confidentiality, which is that it is difficult for the information provider to disclose all the information.

Therefore, when there are a plurality of systems having one or more processes, a system capable of acquiring information regardless of whether or not the systems have different management methods and the processes are grasped and / or a technology for ensuring the confidentiality of the information. Is required.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an information management method, an information management system, and an information management program capable of optimizing information sharing.

In order to achieve the above object, the information management method according to the first aspect is an information management method including a storage unit that can be read by a computer, and the storage unit is a relevance data model that defines a data structure of information. And the relevance data model connection information indicating the relevance between the relevance data that defines the relevance between the relevance data model and the information and the distributed relevance data model.

According to the present invention, information sharing can be optimized.

It is a block diagram which shows an example of the system configuration to which the information management method which concerns on 1st Embodiment is applied. It is a figure which shows the relevance data model used for the information management method which concerns on 1st Embodiment, and the structure of the relevance data. It is a block diagram which shows an example of the hardware configuration of the information management system of FIG. It is a figure which shows an example of the relevance data model held by the information management system of FIG. It is a figure which shows an example of the relevance data model connection information held by the information management system of FIG. It is a figure which shows an example of the relevance data connection information held by the information management system of FIG. It is a figure which shows an example of the destination held by the information management system of FIG. It is a sequence diagram which shows the flow of the output method of the relevance data model of the information management system of FIG. It is a sequence diagram which shows the flow of the acquisition method of the information related to the relevance data model of the information management system of FIG. It is a figure which shows the display example of the user interface corresponding to the model output K13 of FIG. It is a figure which shows the display example of the user interface corresponding to the model output K19 of FIG. It is a figure which shows the display example of the user interface corresponding to the model output K25 of FIG. It is a figure which shows the display example of the user interface corresponding to the analysis data output K41 of FIG. It is a figure which shows an example of the content of the information provision request of K32 of FIG. It is a figure which shows an example of the route information table which contains the route information of K35 of FIG. It is a figure which shows an example of the objective information table which contains the objective information of K39 of FIG. It is a flowchart which shows the model output processing K12, K15, K21 of FIG. It is a flowchart which shows the shared model provision processing K17, K23 of FIG. It is a flowchart which shows the information provision request processing K32 of FIG. It is a flowchart which shows the information provision process K34, K38 of FIG. It is a flowchart which shows the information processing K36, K40 of FIG. It is a sequence diagram which shows the flow of the output and sharing method of the relevance data model of the information management system which concerns on 2nd Embodiment. It is a sequence diagram which shows the flow of the acquisition method of the information related to the relevance data model of the information management system which concerns on 2nd Embodiment.

Hereinafter, embodiments will be described with reference to the drawings. It should be noted that the embodiments described below do not limit the invention according to the claims, and all of the elements and combinations thereof described in the embodiments are essential for the means for solving the invention. Not necessarily. Further, in the following embodiments, when it is necessary for convenience of explanation, the description will be divided into a plurality of sections or embodiments, but unless otherwise specified, they are not unrelated to each other, and one of them is not related to each other. It is related to some or all of the other modifications, details or supplementary explanations. Furthermore, it goes without saying that, in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless otherwise specified or clearly considered to be essential in principle. No.

FIG. 1 is a block diagram showing an example of a system configuration to which the information management method according to the first embodiment is applied.
In FIG. 1, each factory 5A to 5C divides labor to produce a product. For example, if factory 5A produces a vehicle, which is a product, factory 5B produces a door, which is a vehicle component, and factory 5C produces glass, which is a door component.

The factory 5A includes an information management system 2A, a data lake 3A, a client 4A, and a communication network 6A. The factory 5B includes an information management system 2B, a data lake 3B, a client 4B, and a communication network 6B. The factory 5C includes an information management system 2C, a data lake 3C, a client 4C, and a communication network 6C. Each client 4A-4C includes user interfaces 7A-7C.

The information management system 2A, the data lake 3A and the client 4A are connected via the communication network 6A. The information management system 2B, the data lake 3B, and the client 4B are connected via the communication network 6B. The information management system 2C, the data lake 3C and the client 4C are connected via the communication network 6C. The communication networks 6A to 6C are connected via the communication network 1.

The communication networks 6A to 6C are, for example, a LAN (Local Area Network) such as WiFi or Ethernet (registered trademark). The communication network 1 may be a WAN (Wide Area Network) such as the Internet, a LAN such as WiFi or Ethernet, or a mixture of WAN and LAN.

Each data lake 3A to 3C holds manufacturing process information of each factory 5A to 5C. For example, assuming that factory 5A produces vehicles, factory 5B produces doors, and factory 5C produces glass, data lake 3A holds manufacturing process information about the vehicle, and data lake 3B , Holds manufacturing process information about doors, and Data Lake 3C holds manufacturing process information about glass. The manufacturing process information can be stored in an arbitrary format in, for example, a table, a database, or a file. Further, the manufacturing process information may be, for example, in addition to the inspection data in each process, IoT (Internet of Things) data or form data at the site.

Each client 4A to 4C operates each information management system 2A to 2C in each factory 5A to C. Each of the clients 4A to 4C is a terminal such as a personal computer. The number of each client 4A to 4C is not limited, and may also be used as a terminal of each information management system 2A to 2C.

Each information management system 2A to 2C manages manufacturing process information of each factory 5A to 5C, and provides and requests the manufacturing process information. Further, each information management system 2A to 2C acquires the manufacturing process information of the other factories 5A to 5C from the other information management systems 2A to 2C, and provides the manufacturing process information. Each information management system 2A to 2C is a terminal such as a server or a personal computer, for example.

Each information management system 2A to 2C holds the relevance data model connection information showing the relevance between the relevance data model that defines the data structure of the information managed by itself and the distributed relevance data model. To do. For example, this data structure can define relationships between nodes that symbolize a bunch of information with the same or similar attributes. As this node, a class in which information is conceptualized can be used. At this time, the relevance data model includes inter-class relationship information indicating the relationships between the classes in which the information is conceptualized.

In addition, each information management system 2A to 2C shows the relationship between the relevance data that defines the relevance between the information managed by itself and the relevance data model and the information of the distributed relevance data. Holds data connection information. Relevance data includes relevance data elements associated with a class in a relevance data model and inter-element relationship information that indicates the relationships between the relevance data elements.

The information management system 2A displays its own relevance data model on the user interface 7A, the information management system 2B displays its own relevance data model on the user interface 7B, and the information management system 2C displays its own relevance. The data model is displayed on the user interface 7C.

Further, the information management system 2A acquires the relevance data model and the relevance data model connection information of the information management systems 2B and 2C based on the shared model provision request. The relevance data model acquired at this time refers to the shared relevance data model 13 that the information management systems 2B and 2C can provide to the information management system 2A. The shared relevance data model 13 processes a relevance data model that can be disclosed to the requester or the relay source, or a relevance data model that can be disclosed, among the relevance data models held by the provider or the relay source. It is a model. The share relevance data model 13 is provided from the provider or the relay source to the requester via the communication network 1. The shared model is an abbreviation for the shared relevance data model.

At this time, the information management system 2A is an information management system that is the target of the shared model provision request based on the relevance data model connection information indicating the relevance between the relevance data models held by the information management systems 2A to C. The shared relevance data model 13 of 2B and 2C can be specified.

Then, the information management system 2A transfers the target information associated with the relevance data element associated with the class selected based on the relevance data model acquired from the information management systems 2B and 2C to the information management systems 2B and 2C. And display it on the user interface 7A. At this time, the information management system 2A is the information management system 2B that is the target of the information provision request based on the relevance data connection information indicating the relevance between the relevance data element information held by the information management systems 2A to C. 2. The target information held by 2C can be specified.

The information management system 2B acquires the relevance data model and the relevance data model connection information of the information management systems 2A and 2C based on the shared model provision request. At this time, the information management system 2B is an information management system that is the target of the shared model provision request based on the relevance data model connection information indicating the relevance between the relevance data models held by the information management systems 2A to C. 2A and 2C relevance data models can be identified.

Then, the information management system 2B transfers the target information associated with the relevance data element associated with the class selected based on the relevance data model acquired from the information management systems 2A and 2C to the information management systems 2A and 2C. It is obtained from and displayed on the user interface 7B. At this time, the information management system 2B is the information management system 2A that is the target of the information provision request based on the relevance data connection information indicating the relevance between the relevance data element information held by the information management systems 2A to C. 2. The target information held by 2C can be specified.

The information management system 2C acquires the relevance data model and the relevance data model connection information of the information management systems 2A and 2B based on the shared model provision request. At this time, the information management system 2C is an information management system that is the target of the shared model provision request based on the relevance data model connection information indicating the relevance between the relevance data models held by the information management systems 2A to C. The relevance data model of 2A and 2B can be identified.

Then, the information management system 2C attaches the target information to the information management systems 2A and 2B by associating the relevance data elements associated with the class selected based on the relevance data model acquired from the information management systems 2A and 2B. It is obtained from and displayed on the user interface 7C. At this time, the information management system 2C is the information management system 2A, which is the target of the information provision request, based on the relevance data connection information indicating the relevance between the relevance data elements held by the information management systems 2A to C. The purpose information held by 2B can be specified.

The target information is information managed by each information management system 2A to 2C in which each information management system 2A to 2C requests information provision to another information management system 2A to 2C. The purpose information is, for example, information on manufacturing process information or manufacturing process information of each factory 5A to 5C.

Here, each information management system 2A to 2C can access the distributed relevance data model by holding the relevance data model connection information, and is managed by each information management system 2A to 2C. It is possible to request the acquisition of information.

Further, by collecting the information in a class in which the information is conceptualized, even if the name of the information used for management is different between the request source and the provider, each information management system 2A to 2C requires the information required by the request source. Can be requested from the provider.

Furthermore, the provider who receives the information provision request from the requester can select the information managed by the provider and send it to the requester, and the provider manages it in order to obtain the necessary information. Since it is not necessary to disclose all the information to be requested to the requester, the confidentiality of the information managed by the provider can be improved.

In addition, although FIG. 1 shows an example in which the information management systems 2A to 2C are constructed by independent servers, the information management systems 2A to 2C may be tenants in the cloud, respectively, or a mixed system of the server and the cloud. It may be.

FIG. 2 is a diagram showing a relevance data model and a configuration of relevance data used in the information management method according to the first embodiment.
In FIG. 2, the relevance data model M1 includes a class C1 in which information is conceptualized and an interclass relationship information CE1 showing a relationship between classes C1 in the relevance data model M1. Class C1 has a role of collecting information having the same or similar attributes. Class C1 and inter-class relationship information CE1 can be represented by, for example, nodes and edges used in a graph database.

The relevance data model connection information CF1 indicating the relevance between the relevance data model M1 and other distributed relevance data models is associated with the class C1 of the relevance data model M1. At this time, the relevance data model connection information CF1 indicates the relevance with the class of the relevance data model outside the relevance data model M1.

Here, the interclass relationship information CE1 does not have the information of the system that holds the relevance data model M1, but the relevance data model connection information CF1 has the information of the system that holds the relevance data model M1. The information of the system that holds the relevance data model M1 is, for example, the system name associated with the destination of the system that holds the relevance data model M1.

The relevance data D1 is an inter-element relationship indicating the relationship between the relevance data elements E1 to E3 ... Associated with the class C1 in the relevance data model M1 and the relevance data elements E1 to E3 ... Includes information EE1 to EE3 ... Each relevance data element E1 to E3 includes a class identifier P1 to P3 that identifies the class C1 to which each relevance data element E1 to E3 ... Is associated.

Each relevance data element E1 to E3 ... indicates the relevance between each relevance data element E1 to E3 ... and the distributed relevance data element. Relevance data connection information EF1 to EF3 ... Is tied.

Further, each relevance data element E1 to E3 ... Can have a property. Each relevance data element E1 to E3 ... May have a plurality of properties. At this time, the class C1 has the name of the property of each of the relevance data elements E1 to E3 ... Associated with the class C1 as an item. The items of the class C1 are associated with the properties of the relevance data elements E1 to E3.

Further, the relevance data elements E1 to E3 ... Have a property value or a pointer to the actual data. The property value or actual data is, for example, on-site data generated and collected at each factory 5A to 5C in FIG. The site data can be classified into any information such as business information, workers, machines, work procedures or materials (parts). This field data may be numerical data such as measured values, or pass / fail data in the inspection process. At this time, the property values or actual data generated and collected in the factory 5A are held in the data lake 3A of FIG. Property values or actual data generated and collected in factory 5B are retained in data lake 3B. Property values or actual data generated and collected in the factory 5C are held in the data lake 3C.

For example, the factory 5A produces the products T11, T21, T31 ..., And the factory 5B produces the doors T12, T22, T32 ..., which are the parts of the vehicles T11, T21, T31 ... Factory 5C shall produce glass T13, T23, T33 ..., which are parts of each door T12, T22, T32 ...

Here, the concept G1 of the vehicle is commonly set for the entities T11, T21, T31 ... Of the individual vehicles, and the concept G2 of the door is commonly set for the entities T12, T22, T32 ... The concept G3 of glass is commonly set for each entity of glass T13, T23, T33 ...

At this time, assuming that the class C1 is assigned to the concept G1 of the vehicle, each of the relevance data elements E1 to E3 ... Is an entity corresponding to the concept G1 of the individual vehicles T11, T21, T31 ... Information can be linked to class C1. For example, assuming that 100 vehicles are produced in the factory 5A, each relevance data element E1 to E3 ... Associates the information of 100 vehicles with the class C1 to which the concept G1 of the vehicle is assigned. Can be done.

Assuming that the class C1 is assigned to the concept G2 of the door, each relevance data element E1 to E3 ... Classes the information of the individual doors T12, T22, T32 ... Which are the entities corresponding to the concept G2. It can be linked to C1. For example, assuming that the doors of 100 vehicles are produced in the factory 5B, each relevance data element E1 to E3 ... is the information of the doors of 100 vehicles to the class C1 to which the concept G2 of the door is assigned. Can be linked.

Assuming that class C1 is assigned to the concept G3 of glass, each relevance data element E1 to E3 ... Classes the information of each glass T13, T23, T33 ... Which is an entity corresponding to the concept G3. It can be linked to C1. For example, assuming that the glass used for the doors of 100 vehicles is produced in the factory 5C, each relevance data element E1 to E3 ... 100 vehicles in class C1 to which the concept G3 of glass is assigned. Information on the glass used for the door can be linked. This glass information is real data such as, for example, glass thickness, glass size or glass weight.

Here, the information management system 2A is associated with the relevance data model M1 including the class C1 to which the concept G1 of the vehicle is assigned, and the relevance data element E1 associated with the information of the individual vehicles T11, T21, T31 ... Holds the relevance data D1 having ~ E3 ...

The information management system 2B includes the relevance data model M1 including the class C1 to which the concept G2 of the door is assigned, and the relevance data elements E1 to E3 ... Associated with the information of the individual doors T12, T22, T32 ... -Holds the relevance data D1 with.

The information management system 2C is composed of a relevance data model M1 including a class C1 to which the concept G3 of glass is assigned, and relevance data elements E1 to E3, which are associated with information of individual glasses T13, T23, T33, and so on. -Holds the relevance data D1 with.

At this time, when the requester acquires the actual data managed by the provider, the requester can specify the actual data required by the requester based on the class C1 of the relevance data model M1. Therefore, even when the actual data required by the requester is managed by the provider, if the relevance data model M1 held by the provider is acquired in order to specify the actual data required by the requester. Often, it is not necessary to acquire all the actual data held by the provider, so it is possible to reduce the communication load and storage capacity for the requester to acquire the required actual data from the provider, and also to provide the data. It is possible to improve the confidentiality of the information managed originally.

Hereinafter, specific configurations and operations of the information management systems 2A to 2C will be described. In the following explanation, the factory 5C performs "manufacturing of glass" and provides the finished product "glass" to the factory 5B, and the factory 5B receives the material "glass" from the factory 5C and "manufactures the door". For example, the finished product "door" is provided to the factory 5A, and the factory 5A receives the material "door" from the factory 5B and "assembles the vehicle using the door".

Further, in the following description, the case where the information management system 2A acquires information from the information management systems 2B and 2C will be taken as an example. Specifically, an example is a case where the factory 5A acquires the information "glass thickness" of the material "glass" used for the material "door" received from the factory 5B used for assembling the vehicle from the factory 5C. Take it to.

At this time, the factory 5A is a request source that is a main body for performing information retrieval. Factory 5C is a provider that provides the purpose information required by the requester. The factory 5B is a provider that does not hold the purpose information required by the requester, but provides route data to the provider that holds the purpose information required by the requester. In the following description, a provider that does not hold the purpose information required by the requester but provides route data to the provider that holds the purpose information required by the requester is referred to as a relay source.

Further, in the following description, an example is taken in which the requester, the provider, and the relay source do not concurrently serve as roles, but if there is one requester and one provider, the requester, the provider, and the relay source are described. The relay sources can serve any role, and the number in the communication network is not limited. For example, the requester may be the provider, or the provider may be the relay source.

Further, in the following description, the case where the factory 5A and the factory 5C are not related and only the factory 5B is directly related to the manufacturing process of each of the factory 5A and the factory 5C is taken as an example, but the request source is via the relay source. And the provider are connected, the requester and the provider may or may not have a direct relationship.

FIG. 3 is a block diagram showing an example of the hardware configuration of the information management system of FIG. Although FIG. 3 shows the configuration of the information management system 2A of FIG. 1, the information management systems 2B and 2C can be configured in the same manner as the information management system 2A.

In FIG. 3, the information management system 2A includes a memory 21, a processor 22, an input / output device 23, an auxiliary storage device 24, and a network interface 25. The memory 21, the processor 22, the input / output device 23, the auxiliary storage device 24, and the network interface 25 are connected to each other via the internal bus 26. The memory 21 and the auxiliary storage device 24 are accessible from the processor 21.

The processor 22 is hardware that controls the operation of the entire information management system 2A. The processor 22 may be a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The processor 22 may be a single-core processor or a multi-core processor. The processor 22 may include a hardware circuit (for example, an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs a part or all of the processing. The processor 22 may include a neural network.

The memory 21 can be composed of, for example, a semiconductor memory such as SRAM or DRAM. The memory 21 can store a program being executed by the processor 22 or provide a work area for the processor 22 to execute the program.

The auxiliary storage device 24 is a storage device having a large storage capacity, and is, for example, a ROM (ReadOnly Memory), a hard disk device, or an SSD (Solid State Drive). The auxiliary storage device 24 can hold the executable files of various programs and the data used for executing the programs non-temporarily or temporarily.

The input / output device 23 is an input device and an output device. The input device is, for example, a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a card reader, a voice input device, or the like. The output device is, for example, a display, a printer or an audio output device.

The network interface 25 is hardware having a function of controlling communication with the outside. The network interface 25 is connected to the communication network 1 via the communication network 6A.

The memory 21 includes a model output program P1, a shared model providing program P2, an information providing request program P3, an information providing program P4, an information processing program P5, a user interface program P6, a relevance data search program P7, a stored data acquisition program P8, and related. Sex data model 11, relevance data 12, shared relevance data model 13, relevance data model connection information 14, relevance data connection information 15, instruction information 16, information provision request query 17, destination 18, and analysis data 19. Hold.

The model output program P1 causes the processor 22 to execute a process of outputting the relevance data model 11 held by the requester.

The shared model providing program P2 causes the processor 22 to execute a process in which the requester shares the relevance data model held by the provider and the relay source.

The information provision request program P3 causes the processor 22 to execute a process in which the requester requests the provider and the relay source to provide information.

The information providing program P4 causes the processor 22 to execute a process in which the provider and the relay source provide information to the requester.

The information processing program P5 causes the processor 22 to execute a process of processing the information received by the requester from the provider and the relay source.

The user interface program P6 is called from the client 4A or the like based on the operation of the requesting user, and causes the processor 22 to execute a process related to viewing and operation of the user interface 7A.

When a predetermined relevance data element is selected, the relevance data search program P7 has other relevance related to the relevance data element based on the relevance data element identifier given to the relevance data element. The data element is searched, and all or a part of the relevance data element obtained as a result of the search is displayed on the user interface 7A by hatching or color coding, and the processor 22 is made to execute a process of presenting the user. Further, the relevance data search program P7 causes the processor 22 to execute a process of transmitting the selected relevance data element and the connection relationship of the relevance data element obtained as a result of the search as analysis data 19.

The stored data acquisition program P8 causes the processor 22 to execute a process of acquiring information from the data lakes 3A to 3C based on the relevance data 12 held in the memory 21.

The relevance data model 11 defines a data structure of information managed by the information management system 2A. The relevance data model 11 has classes and inter-class relationship information. A class is defined as conceptualized information in a manufacturing process such as business or material, and has a class identifier. The inter-class relationship information indicates the relationship between two classes in the relevance data model 11.

The relevance data 12 defines the relevance between the relevance data model 11 and the information managed by the information management system 2A. The relevance data 12 has relevance data elements and inter-element relationship information. Relevance data elements are information associated with materials or operations that actually exist as actual results in the manufacturing process. Relevance data elements have properties. The property may have any number of values and may be associated with the property value or actual data. The objective property is one of the properties of the relevance data element. The relevance data element includes a relevance data element identifier and a class identifier associated with the actual data. The inter-element relationship information indicates the relationship between two relevance data elements whose relevance to the relevance data model 11 is defined.

The relevance data model connection information 14 is mapping information indicating the connection between the relevance data model held by the requester and the relevance data model held by the provider or the relay source. At this time, the relevance data model connection information 14 includes information on the system that holds the relevance data model and the class identifier of the class in the relevance data model.

The relevance data connection information 15 is mapping information indicating the connection between the relevance data held by the requester and the relevance data held by the provider or the relay source.

The instruction information 16 includes target data and route data thereof, which are information related to the target information required by the requester instructed by the user interface program P6 or other programs. The objective data includes at least the class identifier, the objective property, and the provider or relay source information that holds them. The route data includes at least the identifier of the class to be the route and the information of the provider or the relay source that holds the route data. The target data given at one time may be plural or one.

The information provision request query 17 is an information provision request query sent from the request source to the provider or the relay source.

The destination 18 is a destination of a provider or a relay source that exchanges data with the request source. The destination 18 is, for example, an IP (Internet Protocol) address of a provider or a relay source.

The analysis data 19 is a work area for merging the data of the data or the identifier provided by the provider or the relay source in order to create the data for which the request source has requested the information provision.

The auxiliary storage device 24 includes a model output program P1, a shared model providing program P2, an information providing request program P3, an information providing program P4, an information processing program P5, a user interface program P6, a relevance data search program P7, and accumulated data acquisition. Program P8, relevance data model 11, relevance data 12, relevance data model connection information 14 and relevance data connection information 15 may be retained.

Then, the processor 22 may read the program or data stored in the auxiliary storage device 24 into the memory 21 as needed. The model output program P1, the shared model providing program P2, the information providing request program P3, the information providing program P4, the information processing program P5, the user interface program P6, the relevance data search program P7, and the accumulated data acquisition program P8 are information management system 2A. It may be software that can be installed in the information management system 2A, or it may be incorporated as firmware in the information management system 2A.

The model output program P1, the shared model providing program P2, the information providing request program P3, the information providing program P4, the information processing program P5, the user interface program P6, the relevance data search program P7, and the accumulated data acquisition program P8 are executed. It may be shared by multiple processors and computers. Alternatively, the processor 22 sends a model output program P1, a shared model providing program P2, an information providing request program P3, an information providing program P4, an information processing program P5, a user interface program P6, and relevance to a cloud computer or the like via the communication network 1. The execution of all or a part of the data search program P7 and the stored data acquisition program P8 may be instructed, and the execution result may be received.

FIG. 4 is a diagram showing an example of a relevance data model held by the information management system of FIG.
In FIG. 4, the relevance data models MA to MC are distributed to each other.

At this time, the information management system 2A of FIG. 1 holds, for example, the relevance data model MA. The relevance data model MA can conceptually represent the manufacturing process of the factory 5A.

The relevance data model MA includes, for example, classes A11-A18. Each class A11 to A18 is assigned the concept of information of the relevance data element associated with each class A11 to A18. In addition, the relevance data model MA includes interclass relationship information indicating the relationship between each class A11 to A18 in the relevance data model MA.

For example, class A11 is assigned the concept of a door, which is a vehicle component produced in factory 5A. Further, the inter-class relationship information EA indicating the relationship between the class A11 and the class A13 is set.

For example, in the relevance data model MA, the finished vehicle assigned to class A18 indicates the product assembled by the requester, and the class identifier of class A18 is "product". The door, which is a part assigned to the class A11, corresponds to the "door" which is a finished product received from the relay source by the requester, and the class identifier is "door".

Here, the information management system 2A holds, for example, the relevance data model connection information EAB indicating the relevance between the class A11 of the relevance data model MA and the class B18 of the relevance data model MB.

The information management system 2B of FIG. 1 holds, for example, the relevance data model MB. The relevance data model MB can conceptually represent the manufacturing process of the factory 5B.

The relevance data model MB includes, for example, classes B11-B18. Each class B11 to B18 is assigned the concept of information of the relevance data element associated with each class B11 to B18. Further, the relevance data model MB includes interclass relationship information indicating the relationship between each class B11 to B18 of the relevance data model MB.

For example, class B11 is assigned the concept of glass, which is a part of a door produced in factory 5B. Further, the inter-class relationship information EB indicating the relationship between the class B11 and the class B12 is set.

For example, in the relevance data model MB, the finished door assigned to class B18 corresponds to the pre-shipment "door" created by the relay source, and the class identifier is "door P". The glass, which is the material assigned to the class A11, corresponds to the "glass" received from the provider by the relay source, and the class identifier is "glass".

Here, the information management system 2B holds, for example, the relevance data model connection information EBC indicating the relevance between the class B11 of the relevance data model MB and the class C26 of the relevance data model MC.

The information management system 2C of FIG. 1 holds, for example, the relevance data model MC. The relevance data model MC can conceptually represent the manufacturing process of the factory 5C.

The relevance data model MC includes, for example, classes C11-C26. Each class C11 to C26 is assigned the concept of information of the relevance data element associated with each class C11 to C26. Further, the relevance data model MC includes interclass relationship information indicating the relationship between each class C11 to C26 of the relevance data model MC.

For example, class C26 is assigned the concept of finished glass produced in factory 5C. Further, the inter-class relationship information EC indicating the relationship between the class C25 and the class C26 is set.

For example, in the relevance data model MC, the finished glass assigned to class C26 corresponds to the pre-shipment "glass" created by the provider, and the class identifier is "glass P". The inspection assigned to class C25 corresponds to the "glass thickness inspection" in the manufacturing process of the provider, the class identifier is "glass thickness inspection", and the property has "glass thickness".

FIG. 5 is a diagram showing an example of the relevance data model connection information held by the information management system of FIG.
In FIG. 5, for example, the information management system 2A of FIG. 1 holds the relevance data model connection information 10A. The relevance data model connection information 10A is the identification number 11A, the requesting system name 12A, the class identifier 13A used by the requesting source, the system name 14B of the relay source or provider having a direct contract, and the provider or relay source. It has the class identifier 15A used.

By using the relevance data model connection information 10A, it is possible to convert the class identifier 13A and the class identifier 15A, which are the same by delivery and acceptance, but have different names by the information management system, so that they can be identified as the same object. Become.

For example, if this relevance data model connection information 10A is used, the information management system 2A of the request source has delivered the part called "door" that was inspected by the request source from the administrator of the information management system 2B, and the delivery source. Then, it can be seen that it is managed as a finished product called "Door P". Therefore, the user of the information management system 2A is related to the part called "door" without being aware that the part called "door" is managed as a finished product called "door P" in the information management system 2B. Information can be acquired from the information management system 2B.

The relevance data model connection information 10A is held by the requester, but the timing of receiving the information from the relay source or the provider is arbitrary. The relevance data model connection information 10A may be created by aggregating the relevance data connection information, or may be created manually. For example, the requester and the provider can create relevance data connection information including a pair of relevance data element identifiers of the requester and the provider based on the exchange of data between the requester and the provider. In addition, the requester and the provider identify the class identifier that identifies the class based on the relevance data element identifier held by the relevance data connection information, and the relevance data model connection is based on the identified class identifier. Information can be created.

FIG. 6 is a diagram showing an example of relevance data connection information held by the information management system of FIG.
In FIG. 6, for example, the information management system 2A of FIG. 1 holds the relevance data connection information 30A. The relevance data connection information 30A includes an identification number 31A, a requesting system name 32A, a relevance data element identifier 33A used by the requesting source, a relay source or provider system name 34A with a direct contract, and a provider or relay. It has the relevance data element identifier 35A originally used.

By using the relevance data connection information 30A, it is possible to convert the identifiers 33A and the identifiers 35A, which are the same by delivery and acceptance but have different names by the information management system, so that they can be identified as the same object.

For example, if this relevance data connection information 30A is used, the information management system 2A of the requesting source has delivered the "door 001" accepted by the requesting source from the administrator of the information management system 2B, and the delivery source has " It can be seen that it is managed by the identifier "door P001". Therefore, the user of the information management system 2A manages the identifier "door 001" with the identifier "door 001" without being aware that the identifier "door 001" is managed by the identifier "door P001" in the information management system 2B. Information related to the door to be used can be obtained from the information management system 2B.

The relevance data connection information 30A may be held by the requester, may be owned by the relay source or the provider, or may be held by both parties. The relevance data model connection information 10A and the relevance data connection information 30A may be in other forms, for example, the relevance data model connection information 10A and the relevance data connection information 30A may be held as the same list. Good. The relevance data connection information 30A can be created, for example, from the form data possessed by each factory 5A to 5C, ERP (Enterprise Resource Planning), or the like.

FIG. 7 is a diagram showing an example of a destination held by the information management system of FIG.
In FIG. 7, the information management system 2A of FIG. 1 holds, for example, the destination list 40. The destination list 40 has a destination 42 and a system name 41 which is an identifier of an information management system corresponding to the destination 42.

The destination 42 is information on the communication destination, and may be held in a format such as an IP address (Internet Protocol Address). The information management system 2A may prepare the destination list 40 at the time of constructing the information management system 2A, or may provide information on the destination 42 in the exchange with other information management systems 2B and 2C or the exchange with other factories 5B and 5C. May be collected as appropriate.

FIG. 8 is a sequence diagram showing a flow of an output method of the relevance data model of the information management system of FIG.
In FIG. 8, the client 4A of FIG. 1 requests the information management system 2A to output the relevance data model held by the information management system 2A via the user interface 7A (K11). At this time, the processor 22 of FIG. 3 executes the user interface program P6.

Next, when the information management system 2A receives the model output request, it executes the model output process (K12) and outputs its own relevance data model to the client 4A (K13). At this time, the processor 22 executes the model output program P1.

Here, the information management system 2A can display its own relevance data model on the user interface 7A and present it to the user. At this time, the processor 22 executes the user interface program P6.

Next, the client 4A requests the information management system 2A to output the relevance data model held by the information management system 2B via the user interface 7A (K14). At this time, the processor 22 executes the user interface program P6.

Next, when the information management system 2A receives the model output request, it executes the model output process (K15) and outputs the shared model provision request to the information management system 2B (K16). At this time, the processor 22 executes the shared model providing program P2.

Next, when the information management system 2B receives the shared model provision request, it executes the shared model providing process (K17) and outputs its own relevance data model and relevance data model connection information to the information management system 2A. (K18). At this time, the information management system 2B can output only the portion of the relevance data model that it has that can be provided to the information management system 2A as the shared relevance data model. Further, the information management system 2B may encrypt the class information included in the sharing relevance data model output to the information management system 2A.

Next, when the information management system 2A receives the response to the shared model provision request, the information management system 2A outputs the sharing relevance data model acquired from the information management system 2B to the client 4A (K19). Here, the information management system 2A can display the sharing relevance data model acquired from the information management system 2B on the user interface 7A and present it to the user. At this time, the processor 22 executes the user interface program P6.

Next, the client 4A requests the information management system 2A to output the relevance data model held by the information management system 2C via the user interface 7A (K20). At this time, the processor 22 executes the user interface program P6.

Next, when the information management system 2A receives the model output request, it executes the model output process (K21) and outputs the shared model provision request to the information management system 2C (K22). At this time, the processor 22 executes the shared model providing program P2.

Next, when the information management system 2C receives the shared model provision request, it executes the shared model providing process (K23) and outputs its own relevance data model and relevance data model connection information to the information management system 2A. (K24). At this time, the information management system 2C can output only the portion of the relevance data model that it has that can be provided to the information management system 2A as the shared relevance data model. Further, the information management system 2C may encrypt the class information included in the sharing relevance data model output to the information management system 2A.

Next, when the information management system 2A receives the response to the shared model provision request, the information management system 2A outputs the sharing relevance data model acquired from the information management system 2C to the client 4A (K25). Here, the information management system 2A can display the sharing relevance data model acquired from the information management system 2C on the user interface 7A and present it to the user. At this time, the processor 22 executes the user interface program P6.

The model sharing process may be triggered by a shared model provision request from the information management system 2A, or may be triggered by a shared model provision process of the information management system 2B, regardless of such an opportunity. Model sharing may be performed on a regular basis. Alternatively, the information management system 2A may be acquired when the information management system 2B creates or updates the relevance data model.

FIG. 9 is a sequence diagram showing a flow of a method of acquiring information related to the relevance data model of the information management system of FIG.
In FIG. 9, the client 4A inputs the target data and the search range into the information management system 2A via the user interface 7A (K31). At this time, the processor 22 executes the user interface program P6.

Next, when the information management system 2A receives the target data and the search range, it executes the information provision request process (K32) and outputs the information provision request to the information management system 2B (K33). At this time, the processor 22 executes the information provision request program P3. In this embodiment, information on the inspection item "glass thickness" of the material "glass" used for the material "door" received from the relay source used by the requester for assembling the product is input as the target data. .. This target data is temporarily held as instruction information 16 in FIG.

Next, when the information management system 2B receives the information provision request, it executes the information provision process (K34) and outputs the route information for accessing the information held by the information management system 2C to the information management system 2A (). K35). The information management system 2B may encrypt the route information output to the information management system 2A.

The route information includes at least a start point identifier and a converted identifier. The start point identifier is a relevance data element identifier specified in the query of the information provision request from the request source to the relay source. The converted identifier is a relevance data element identifier specified in the query of the request for information from the requester to the provider. This converted identifier is, for example, an identifier obtained by converting the relevance data element identifier of the relevance data held by the information management system 2B into the relevance data element identifier of the relevance data held by the information management system 2C. ..

Next, when the information management system 2A receives the route information, it executes information processing (K36) and outputs an information provision request to the information management system 2C (K37). At this time, the processor 22 executes the information processing program P5 and the information provision request program P3.

Next, when the information management system 2C receives the information provision request, it executes the information provision process (K38) and outputs the target information held by the information management system 2C to the information management system 2A (K39). At this time, the information management system 2C acquires the value of the property which is the target information or the actual data from the data lake 3C based on the target data included in the information provision request. The information management system 2C may encrypt the target information output to the information management system 2A.

Next, when the information management system 2A receives the target information, it executes information processing (K40) and outputs analysis data to the client 4A (K41). At this time, the processor 22 executes the information processing program P5.

Here, the information management system 2A can display the analysis data on the user interface 7A and present it to the user. At this time, the processor 22 executes the user interface program P6.

FIG. 10 is a diagram showing a display example of a user interface corresponding to the model output K13 of FIG.
In FIG. 10, the user interface 7A of FIG. 1 includes a model display unit 7MA. When the model output K13 of FIG. 8 is executed, the information management system 2A causes the model display unit 7MA to display the display model HA corresponding to the relevance data model MA of FIG. Then, if the user requests information on the inspection item "glass thickness" of the material "glass" used for the material "door", the class NA11 of the display model HA is selected. At this time, the information management system 2A requests the information management system 2B to provide the relevance data model MB of FIG. 4 based on the relevance data model connection information EAB of FIG.

FIG. 11 is a diagram showing a display example of the user interface corresponding to the model output K19 of FIG.
In FIG. 11, when the information management system 2B is requested to provide the relevance data model MB of FIG. 4, only the portion of the relevance data model MB of FIG. 4 that can be provided is managed as a shared relevance data model. Output to system 2A. At this time, the information management system 2B also outputs the relevance data model connection information EBC necessary for the information management system 2A to acquire the relevance data model MC of FIG. 4 from the information management system 2C to the information management system 2A. To do.

Then, the information management system 2A causes the model display unit 7MA to display the display model HB corresponding only to the portion of the relevance data model MB that can be provided. Then, it is assumed that the user has selected the class NB11 of the display model HB. At this time, the information management system 2A requests the information management system 2C to provide the relevance data model MC of FIG. 4 based on the relevance data model connection information EBC.

FIG. 12 is a diagram showing a display example of the user interface corresponding to the model output K25 of FIG.
In FIG. 12, when the information management system 2C is requested to provide the relevance data model MC of FIG. 4, only the portion of the relevance data model MC of FIG. 4 that can be provided is managed as a shared relevance data model. Output to system 2A.

Then, the information management system 2A causes the model display unit 7MA to display the display model HC corresponding only to the portion of the relevance data model MC that can be provided. Then, assuming that the user selects the class NC25 of the display model HC, the referenceable property name associated with the class NC25 is displayed. For example, when the user selects class NC25, a list 81 of items 1 to 5 possessed by the inspection work of class NC25 is displayed.

Then, when the user selects item 4, the property name 82 "glass thickness" is displayed, and "glass thickness" can be set as the target property of the target data. Further, when the user selects the output button 83, the information management system 2A executes the process of FIG. 9 with the "glass thickness" as the target property of the target data, and obtains the target information corresponding to the target data in the information management system. Obtained from 2C.

FIG. 13 is a diagram showing a display example of a user interface corresponding to the analysis data output K41 of FIG.
In FIG. 13, the information management system 2A outputs the analysis data 84 by executing a process such as merging the target information acquired from the information management system 2C, and displays the analysis data 84 on the user interface 7A.

For example, the requester shall search for the relevance data "product 001, product 002, product 003" having the class identifier "product" of class A18. At this time, the requester uses the relevance data element identifier “door 001, door” of the relevance data associated with the class A11 related to the product to be searched based on the inter-element relationship information held by the requester. 002, door 003 "is detected. Further, the requester relays the relevance data element identifiers “door P001, door P002, door P003” of the relevance data associated with the class B18 based on the relevance data connection information 30A held by the requester. Get from.

Next, the requester uses the relevance data element identifier "door P001, door P002, door P003" of the relevance data associated with the class B18 as the starting point identifier, and the relevance of the relevance data associated with the class B11. The sex data element identifier is detected, and the relevance data element identifier of the relevance data associated with the class C26 is acquired from the provider based on the relevance data connection information acquired from the relay source.

Next, the requester detects the relevance data element identifier of the relevance data associated with the class C25, using the relevance data element identifier of the relevance data associated with the class C26 as the starting point identifier, and detects the relevance data element identifier of the relevance data associated with the class C25. The value "2.01mm, 2.00mm, 2.05mm" of the property "glass thickness" of the relevance data element of the relevance data associated with is acquired as the target information, and the user interface is used as the analysis data 84. Display on 7A.

It is also possible to set the development record by selection as the route information in the instruction information 16 of FIG. The association of the expansion records by these selections can refer to the relevance data model connection information.

FIG. 14 is a diagram showing an example of the content of the information provision request of K32 of FIG.
In FIG. 14, the query for the request for information 50 is created by the requester. This query includes at least the request destination start point identifier 53, the objective class identifier 64 of the objective data, and the objective property 55. However, the start point identifier 53 of the request destination may be an identifier under the control of the provider, the relay source, or the provider.

For example, the information provision request 50 includes a request number 51, a request destination name 52, a request destination start point identifier 53, a target class identifier 54 managed by the request destination, a target property name 55, a presence / absence of a certificate provision request 56, and the like. Has certificate 57.

The information management system 2A can refer to the information provided by the information management system 2B based on the information provision request whose request number 51 is No. 1, and can request the information management system 2C to make a query whose request number 51 is No2. At this time, the start point identifier 53 and the certificate 57 whose request number 51 is No. 2 are provided from the information management system 2B to the information management system 2A.

For example, the query in which the request number 51 is No. 1 searches for the target class identifier "glass" related to the start point identifier "door P001, door P002, door P003", and searches for the target property "conversion used in the next system". Request the information management system 2B to provide the "completed identifier". Further, this query requests the information management system 2B to issue a valid certificate between the information management systems 2A and 2C because there is no direct communication between the requester and the provider in the certificate provision request 56.

Here, the converted identifier provided from the information management system 2B to the information management system 2A is the start point identifier "glass P001, glass P002, glass P003" of the information management system 2C. Therefore, the information management system 2A can request the information management system 2C to make a query with the request number 51 No. 2 even when the request source and the provider do not have a direct contractual relationship.

The query with request number 51 No. 2 searches for the target class identifier "glass thickness inspection" related to the start point identifiers "glass P001, glass P002, glass P003" and provides information on the target property "glass thickness". Ask the information management system 2C. Further, this query proves the validity of the information provision request from the requester to the requester by granting the certificate provided by the information management system 2B in the certificate 57.

FIG. 15 is a diagram showing an example of a route information table including the route information of K35 of FIG.
In FIG. 15, the route information table 60 has, for example, a request number 61, a start point identifier 62, a converted identifier 63, and a certificate 64. The relay source acquires the request number 61 of the route information table 60 from the request number 51 of FIG. The relay source acquires the start point identifier 62 from the start point identifier 53 in FIG.

The relay source provides the start point identifier 62 and the converted identifier 63 to the request source based on the query of the information provision request from the request source. The converted identifier 63 is a start point identifier of the information management system 2C converted from the start point identifier 62 of the information management system 2B. By acquiring the converted identifier 63 from the relay source, the requester can request the provider to provide information even if the requester and the provider do not have a direct contractual relationship. The converted identifier 63 is not limited to the identifier of the provider, and may be the identifier of the next relay source.

The information management system 2A holds the route information table 60 of FIG. 15 as the analysis data 19 of FIG. 3 and uses it for processing.

FIG. 16 is a diagram showing an example of a purpose information table including the purpose information of K39 of FIG.
In FIG. 16, the provider provides the target information to the requester based on the query for the information provision request from the requester. The purpose information table 70 has, for example, the request number 71, the start point identifier 72 of the provider, and the information 73 of the target property among the target data of the request source.

The provider acquires the request number 71 of the purpose information table 70 from the request number 51 of FIG. The provider acquires the start point identifier 72 from the start point identifier 53 in FIG. The information management system 2A holds the purpose information table 70 of FIG. 16 as the analysis data 19 of FIG. 3 and uses it for processing.

FIG. 17 is a flowchart showing the model output processes K12, K15, and K21 of FIG.
In FIG. 17, when the information management system 2A of FIG. 1 receives the model output request, it determines whether the model output request is due to the activation of the user interface or the expansion of the model (S11).

When the user interface is activated (initiation of S11), the information management system 2A creates a display model from the relevance data model held by itself (S16) and displays it on the user interface 7A (S17).

On the other hand, when the model is expanded (model expansion in S11), the information management system 2A holds the class identifier of the relevance data for which the model expansion is specified, and temporarily stores it in the instruction information 16 as route data. (S12).

Next, in the information management system 2A, whether the shared relevance data model to be deployed exists in the shared relevance data model 13 of FIG. 3, or the relevance data model connection information associated with the shared relevance data model to be deployed is related. It is determined whether or not it exists in the sex data model connection information 15 (S13).

When the shared relevance data model to be deployed and the relevance data model connection information exist (with S13), the information management system 2A creates a display model from the shared relevance data model (S16) and provides the user interface 7A. Display (S17).

On the other hand, when the shared relevance data model to be deployed and the relevance data model connection information do not exist (without S13), the information management system 2A creates a shared model provision request (S14), and each information management system 2B, The shared relevance data model and the relevance data model connection information are acquired from 2C (S15).

The information management system 2A accumulates the shared relevance data model acquired from each information management system 2B and 2C in the shared relevance data model 13, creates a display model from the shared relevance data model (S16), and creates a user interface. It is displayed on 7A (S17).

FIG. 18 is a flowchart showing the shared model providing processes K17 and K23 of FIG.
In FIG. 18, when each information management system 2B and 2C receives a shared model provision request from the information management system 2A, it determines whether or not to disclose the relevance data model held by itself and the provision range at an arbitrary timing (S21). .. At this time, each information management system 2B and 2C performs a process of selecting a part or all of the disclosure of the relevance data model, a process of selecting a part of the relevance data model to be disclosed to the requester, and a relevance data model. At least one of the processes of encrypting the information of the contained class can be executed.

At this time, each information management system 2B and 2C deletes the class of the relevance data model for which non-disclosure is selected, the model for which the inter-class relationship information contact is deleted, and the class of the relevance data model for which non-disclosure is selected. It is possible to generate one of a model that includes a model that contains interclass relationship information and a model that includes classes in the relevance data model for which disclosure is selected and has the interclass relationship information removed.

In addition, each information management system 2B and 2C is not limited to when the information management system 2A issues a shared model provision request, but also when it updates the relevance data model or performs batch processing at a fixed time every day. It is possible to disclose the relevance data model at various timings as needed.

When there is no relevance data element to be disclosed (disclosure 0 in S21), each information management system 2B and 2C creates mapping information between relevance data connected to another information management system (S22), and relevance. It is sent to the information management system 2A as data model connection information (S24).

When there is one or more relevance data elements to be disclosed (one or more disclosures in S21), each information management system 2B and 2C can be disclosed to the requester from the relevance data model owned by the information management system 2B and 2C. Create the shared relevance data model defined in (S23). The information of the class identifier associated with the relevance data model of the request source is sent to the request source together with the shared relevance data model as the relevance data model connection information (S24).

As a method of rounding the relevance data model, for example, the relevance data model is created by creating the relevance data model classes and inter-class relationship information only for the relevance data elements that can be provided, and removing all non-sharing parts. There is a method of using a shared relevance data model. Alternatively, leave all classes and inter-class relationship information, make the relevance data model associated only with the relevance data elements that can be provided as the shared relevance data model, and gray out the classes that do not have the relevance data elements that can be provided. It may be a method. Alternatively, one class may be newly created, the relevance data elements that can be provided are registered, and the relevance data model including only one class without inter-class relationship information may be used as the shared relevance data model.

FIG. 19 is a flowchart showing the information provision request process K32 of FIG.
In FIG. 19, the information management system 2A confirms the remaining number of instruction information (S31). The instruction information includes target data, search range and route data. The objective data includes the objective class identifier 54 and the objective property 55 of FIG. The target information is actual data associated with the target property 55.

Multiple target data may be specified in one search. The search range has an identifier that satisfies the search condition specified at the time of inputting the target data. The route data has at least a class identifier acquired during the model output process of FIG.

In this embodiment, the objective class identifier 54 is a "glass thickness inspection". The object property 55 is "glass thickness". The search range is an identifier of the relevance data element of "product using door". The search range can be specified in detail by the date and time or property conditions. The route data are the class identifier "door" held by the information management system 2A acquired during the model output process of FIG. 3 and the class identifier "glass" held by the information management system 2B. The purpose information is the actual data associated with the "glass thickness" of the "glass" used for the "door" used for the "product using the door".

When there is one or more target data 301 in the instruction information 16 (there is a remaining number in S31), the information management system 2A has a class identifier (that is, information) of the first route data connected by the identifier of the search range and the interclass relationship information. The search is performed up to the terminal class identifier of the management system 2A, and all the relevant data element identifiers (that is, the end point identifier of the information management system 2A) of the terminal class identifier are acquired (S32).

The information management system 2A acquires the first identifier of the next information management system (that is, the start point identifier of the information management system 2B) based on the identifier acquired in the search (S32) of the own system and the relevance data connection information. (S33). This process may be performed by the information management system 2A, the information management system 2B, or both if necessary.

The information management system 2A creates an information provision request to the information management system 2B using the start point identifier of the information management system 2B as the next search base identifier, stores it in the information provision request query 17 (S34), and processes S31. Return to. The information management system 2A performs this processing for all route information.

On the other hand, when the target data 301 is not in the instruction information 16 (there is no remaining number in S31), the information provision request to the information management system 2B existing in the information provision request query 17 is collected and transmitted to the information management system 2B (S35). ..

In the present embodiment, the information management system 2A searches from the "product using the door" to the class identifier "door", and the relevance data element identifier "door 001, door 002," of the "door used in the product". "Door 003" is acquired. The information management system 2A uses the relevance data element identifiers "door 001, door 002, door 003" based on the relevance data connection information, and relevance data element identifiers "door P001," which are managed by the information management system 2B. Converted to "door P002, door P003".

In the information management system 2A, the relevance data element identifiers "door P001, door P002, door P003" are set as the start point identifier 53 of the system B in FIG. 14, and the class identifier "glass" obtained from the route data is set as the target class identifier 54. An information provision request 50 to the information management system 2B is created with the "converted identifier of the information management system 2C" as the target property 55, and is stored in the information provision request query 17.

At this time, the information management system 2A may create an information provision request 50 to the information management system 2C having the target information based on the information currently held by the information management system 2A. The information management system 2A creates a query for all the instruction information, and then transmits an information provision request 50 to the information management system 2B.

FIG. 20 is a flowchart showing the information providing processes K34 and K38 of FIG.
In FIG. 20, when each information management system 2B and 2C receives each information provision request, the remaining number of unprocessed information provision requests is confirmed (S41). When there is no unprocessed search query remaining (there is no remaining number in S41), each information management system 2B and 2C transmits the data requested by each query to the information management system 2A (S47).

When an unprocessed search query remains (there is a remaining number in S41), each information management system 2B and 2C performs a search based on the start point identifier 53 and the target class identifier 54 of each information provision request 50, and the purpose is Acquire the relevance data element identifier (that is, the end point identifier) of the relevance data having the class identifier 54 (S42).

Next, each of the information management systems 2B and 2C acquires the value of the target property 55 having the end point identifier, the identifier obtained by converting the end point identifier, or the actual data associated with the accumulated data acquisition program P8 (S43). ..

Next, the information management systems 2B and 2C determine whether or not there is a certificate provision request 56 to the next information management system (S44). When there is a certificate provision request 56 (necessary for S44), each information management system 2B and 2C issues a certificate (S45) and creates provision data (S46). When there is no certificate provision request 56 (S44 is unnecessary), each information management system 2B and 2C creates the provision data without issuing the certificate (S46).

Regarding the issuance of the certificate (S45), any mechanism may be used as long as it can be proved between the information management systems 2B and 2C, and for example, an SSL (Secure Socket Layer) certificate or the like may be used.

In the present embodiment, the information management system 2B receives the information provision request 50 to the system B, and acquires the end point identifier based on the start point identifier "door P001, door P002, door P003" and the target class identifier "glass". ..

Next, the information management system 2B acquires the converted identifiers "glass P001, glass P002, glass P003" which are the target property 55 based on the relevance data connection information with the information management system 2C, and the information management system 2A Issue a certificate to request the information management system 2C for permission to acquire information from.

Next, the information management system 2B transmits the provided data to the information management system 2A together with the converted identifiers "glass P001, glass P002, glass P003" and the certificate.

FIG. 21 is a flowchart showing information processing K36 and K40 of FIG.
In FIG. 21, the information management system 2A determines whether the data provided by the information management systems 2B and 2C includes target information or route information (S51).

In the case of data including route information, the information management system 2A collates the request number obtained from the information provision request query 17 with the request number of the provided data, and based on the provided converted identifier, the following information Create a provision request and send it to the next information management system (S52). At this time, the information management system 2A stores the provided route information in the analysis data 19.

When the data provided by the information management systems 2B and 2C is data including the target information, the information management system 2A includes the target data included in the instruction information 16, the route information data, and the provided target information. The data are collated and the data for analysis is created (S53).

The analysis data includes at least the search range when the target data is input (that is, the start point identifier of the information management system 2A) and the value of the target property of the target data included in the instruction information 16 (that is, the target information).

Next, the information management system 2A determines whether or not the processing of all the target data included in the instruction information 16 is completed (S54). When there is unprocessed target data (unfinished in S54), the information management system 2A accumulates the analysis data created in S53 in the analysis data 19 and waits for the provision of other route information or target information.

When the analysis data is completed for all the target data (completion of S54), the information management system 2A merges and outputs the analysis data (S55). At this time, the output destination of the analysis data does not matter. For example, it may be another application or user interface.

In the present embodiment, since the data provided by the information management system 2B includes the route information, the information management system 2A is issued by the provided converted identifiers "glass P001, glass P002, glass P003" and the information management system 2B. Based on the certificate, an information provision request to the information management system 2C is created and transmitted to the information management system 2C.

Since the data provided by the information management system 2C includes the purpose information, the information management system 2A includes the provided start point identifiers "glass P001, glass P002, glass P003", the purpose information, and the route information provided by the information management system 2B. Data for analysis 84 including the values "2.01 mm, 2.00 mm, 2.05 mm" of the "glass thickness" used for the start point identifiers "door 001, door 002, door 003" of the information management system 2A. Is created and displayed on the user interface 7A.

As described above, according to the first embodiment described above, the information management system 2A sends a shared model provision request and an information provision request to the information management systems 2B and 2C, and data acquired from the information management systems 2B and 2C. Can be processed. Therefore, the information management system 2A acquires the necessary information from the information management systems 2B and 2C without causing the information management systems 2B and 2C to execute the processes such as the shared model provision request and the information provision request. It becomes possible to do.

Further, according to the first embodiment described above, even when the scale of the entire manufacturing process including a plurality of processes is large, it is possible to optimize the entire system while suppressing the increase in the scale per system.

In the first embodiment described above, the information management system 2A acquires the route data to the information management system 2C from the information management system 2B, and transmits an information provision request to the information management system 2C based on the route data. Therefore, the method of acquiring the target information from the information management system 2C has been explained.

In the second embodiment below, the information management system 2A describes a method of acquiring the target information held by the information management system 2C without transmitting an information provision request to the information management system 2C. In this second embodiment, the information management system 2A requests the information management system 2B to acquire the target information held by the information management system 2C, and the information management system 2B manages the target information acquired from the information management system 2C. Obtained from system 2B.

FIG. 22 is a sequence diagram showing a flow of an output and sharing method of the relevance data model of the information management system according to the second embodiment.
In FIG. 22, the client 4A of FIG. 1 requests the information management system 2A to output the relevance data model held by the information management system 2A via the user interface 7A (K51).

Next, when the information management system 2A receives the model output request, it executes the model output process (K52) and outputs its own relevance data model to the client 4A (K53). At this time, the information management system 2A can display its own relevance data model on the user interface 7A and present it to the user.

Next, the client 4A requests the information management system 2A to output the relevance data model held by the information management system 2B via the user interface 7A (K54).

Next, when the information management system 2A receives the model output request, it executes the model output process (K55) and outputs the shared model provision request to the information management system 2B (K56).

Next, when the information management system 2B receives the shared model provision request, it executes the shared model providing process (K57) and outputs its own relevance data model and relevance data model connection information to the information management system 2A. (K58). At this time, the information management system 2B can output only the portion of the relevance data model that it has that can be provided to the information management system 2A as the shared relevance data model.

Next, when the information management system 2A receives the response to the shared model provision request, the information management system 2A outputs the sharing relevance data model acquired from the information management system 2B to the client 4A (K59). At this time, the information management system 2A can display the sharing relevance data model acquired from the information management system 2B on the user interface 7A and present it to the user.

Next, the client 4A requests the information management system 2A to request the information management system 2B to output the relevance data model held by the information management system 2C via the user interface 7A (K60).

Next, when the information management system 2A receives the model output request, it executes the model output process (K61) and outputs the shared model provision request to the information management system 2B (K62). This shared model provision request requests the information management system 2B to acquire the relevance data model held by the information management system 2C by the information management system 2B and transmit the information management system 2B to the information management system 2A.

Next, when the information management system 2B receives the shared model provision request from the information management system 2A, the information management system 2B outputs the shared model provision request to the information management system 2C (K63).

Next, when the information management system 2C receives the shared model provision request from the information management system 2B, it executes the shared model providing process (K64) and informs itself of the relevance data model and the relevance data model connection information. Output to management system 2B (K65). At this time, the information management system 2C can output only the portion of the relevance data model that it has that can be provided to the information management system 2B as the shared relevance data model.

Next, when the information management system 2B receives the relevance data model and the relevance data model connection information from the information management system 2C, the information management system 2B outputs the relevance data model and the relevance data model connection information to the information management system 2A (K66). ).

Next, when the information management system 2A receives the response to the shared model provision request, it outputs the shared relevance data model of the information management system 2C acquired from the information management system 2B to the client 4A (K67). At this time, the information management system 2A can display the shared relevance data model of the information management system 2C acquired from the information management system 2B on the user interface 7A and present it to the user.

FIG. 23 is a sequence diagram showing a flow of a method of acquiring information related to the relevance data model of the information management system according to the second embodiment.
In FIG. 23, the client 4A inputs the target data and the search range into the information management system 2A via the user interface 7A (K71).

Next, when the information management system 2A receives the target data and the search range, it executes the information provision request process (K72) and outputs the information provision request to the information management system 2B (K73). In this information provision request, the information management system 2B is requested to acquire the target information held by the information management system 2C and to transmit the information management system 2B to the information management system 2A. In this information provision request, the information management system 2B is inquired about the relevance data related to the target information held by the information management system 2C together with a part of the relevance data model connection information. For example, the information management system 2A can create an information provision request to the information management system 2B by merging the information provision request to the system B and the information provision request to the system C in FIG.

Here, the information provision request to the information management system 2B of K33 in FIG. 9 does not include the objective class identifier “glass thickness inspection” and the objective property “glass thickness”, but the information management system of K73 in FIG. The information provision request to 2B includes the target class identifier "glass thickness inspection" and the target property "glass thickness". Further, in the information provision request of K73 in FIG. 23, the presence / absence 56 and the certificate 57 of the certificate provision request in FIG. 14 are unnecessary.

Next, when the information management system 2B receives the information provision request, it executes the information provision process (K74) and outputs the route information including the information provision request and the converted identifier to the information management system 2C (K75).

Next, when the information management system 2C receives the information provision request and the route information including the converted identifier, it executes the information providing process (K76) and outputs the target information held by the information management system 2C to the information management system 2B. (K77).

Next, when the information management system 2B receives the target information held by the information management system 2C, the information management system 2B outputs the route information including the target information and the converted identifier to the information management system 2A (K78).

Next, when the information management system 2A receives the target information, it executes information processing (K79) and outputs analysis data to the client 4A (K80). At this time, the information management system 2A can display the analysis data on the user interface 7A and present it to the user.

As described above, according to the second embodiment described above, the information management system 2A sends the shared model provision request and the information provision request to the information management system 2B, so that the purpose information held by the information management system 2C can be obtained. It can be obtained from the information management system 2B. Therefore, the information management system 2A does not need to send a shared model provision request and an information provision request to the information management system 2C which has no direct contractual relationship in order to acquire the target information held by the information management system 2C, and also information. It is no longer necessary to hold the destination of the management system 2C.

The present invention is not limited to the above-described embodiment, and includes various modifications. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, it is possible to add / delete / replace a part of the configuration of each embodiment with another configuration. Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit.

Further, in the above-described embodiment, a part of the vehicle manufacturing process has been described as an example, but the present invention is not limited to the manufacturing process of the manufacturing industry such as the vehicle, but various industries such as the transportation industry, the sales industry, and the financial industry. It can be adapted to the process of the industry. It may also be applied to a supply chain that shows the entire flow from manufacturing, inventory management, delivery, sales and consumption.

1, 6A-6C communication network, 2A-2C information management system, 3A-3C data lake, 4A-4B client, 5A-5B factory

Claims (20)

An information management method equipped with a computer-readable storage unit.
The storage unit
Relevance data models that define the data structure of information,
Relevance data that defines the relevance of the relevance data model to the information,
Distributed relevance An information management method that holds relevance data model connection information that shows relevance to a data model. The relevance data model includes inter-class relationship information that indicates the relationships between the classes in which the information is conceptualized.
The relevance data includes inter-element relationship information indicating the relationship between the information associated with the class in the relevance data model.
The information management method according to claim 1, wherein the storage unit holds relevance data connection information indicating relevance between the relevance data information associated with the distributed relevance data model class. Further equipped with a processor accessible to the storage unit
The processor requests the acquisition of the distributed relevance data model and the relevance data model connection information associated with the class of the relevance data model based on the relevance data model connection information. Information management method described in. The information according to claim 3, wherein the processor requests acquisition of information on the relevance data associated with the decentralized relevance data model based on the acquisition result of the decentralized relevance data model. Management method. The storage unit
A first relevance data model that includes inter-class relationship information that indicates the inter-class relationships for which the information is conceptualized, and
Relevance data model connection information indicating the relevance between the first relevance data model and the distributed second relevance data model, and
The first relevance data including the inter-element relationship information indicating the relationship between the information associated with the class of the first relevance data model, and the first relevance data.
An association showing the relevance between the information of the first relevance data associated with the class of the first relevance data model and the information of the second relevance data associated with the class of the second relevance data model. Holds sex data connection information and
The processor
Based on the relevance data model connection information, at least a part of the first relevance data model and the second relevance data model distributed are acquired.
The information management method according to claim 4, wherein the information of the second relevance data associated with the class of the second relevance data model is acquired based on at least a part of the second relevance data model. The relevance data information includes a plurality of relevance data elements.
The relevance data element contains at least one property.
The relevance data element includes a relevance data element identifier associated with the value of the property or the actual data.
The requester and the provider of the information hold the relevance data model, the relevance data model connection information, the relevance data, and the relevance data connection information regarding the information managed by themselves.
The request source is relevance data connection information indicating the relevance of the first information which is the relevance data element of the relevance data of the request source and the second information which is the relevance data element of the relevance data of the provider. The information management method according to claim 4, wherein the second information is acquired from the provider based on the relevance data element identifier of the second information specified based on the first information. The class and the relevance data element include a class identifier that identifies the class.
The request for information regarding the acquisition of the purpose information from the request source is a purpose class that identifies a start point identifier that is a relevance data element identifier of the provider that can be specified from the request source and a class associated with the purpose information. Including identifier
The provider
Based on the start point identifier and the target class identifier, the end point identifier which is the relevance data element identifier of the relevance data element of the relevance data having the target class identifier is acquired.
The information according to claim 6, which obtains a converted identifier which is a relevance data element identifier of another provider that can be specified from the target information or the requester based on the end point identifier and transmits the converted identifier to the requester. Management method. The relay source between the request source and the provider holds the relevance data model, the relevance data model connection information, the relevance data, and the relevance data connection information regarding the information managed by itself. ,
The information management method according to claim 6, wherein the requester inquires of a relay source between the requester and the provider about the relevance data held by the provider. In response to the inquiry, the relay source creates proof information that can be confirmed by the provider and sends it to the requester.
The information management method according to claim 8, wherein the requester transmits an information provision request to the provider together with the proof information. The provider includes a process of selecting a part or all of the disclosure of the relevance data model, a process of selecting a part of the relevance data model to be disclosed to the requester, and the relevance data model. The information management method according to claim 6, wherein at least one of the processes of encrypting the class information is executed. A part of the relevance data model is a model in which the class of the relevance data model and the interclass relationship information contact are deleted, a model in which the class of the relevance data model is deleted and the interclass relationship information is included, and the above. The information management method according to claim 10, which is one of the models including the class of the relevance data model and deleting the interclass relationship information. The requester and the provider create relevance data connection information including a pair of relevance data element identifiers of the requester and the provider based on the exchange of data between the requester and the provider. The information management method according to claim 6. The relevance data connection information holds the relevance data element identifier of the requester and the relevance data element identifier of the provider.
The requester and the provider identify a class identifier that identifies the class based on the relevance data element identifier held by the relevance data connection information.
The information management method according to claim 6, wherein the relevance data model connection information is created based on the specified class identifier. The requester is a process of acquiring the relevance data model when the provider creates or updates the relevance data model, a process of periodically acquiring the relevance data model, and a provision from the requester. The information management method according to claim 6, wherein at least one of the processes for acquiring the relevance data model based on the request is executed. The information management method according to claim 6, wherein an arbitrary relevance data model of the requester and the provider is displayed by operating the user interface of the relevance data model. The requester is
The class identifier that identifies the class and the properties set in the class are sent to the provider.
The information management method according to claim 6, wherein the actual data associated with the property is acquired from the provider. The information management method according to claim 8, wherein the requester makes an inquiry to the relay source for route information to the provider that holds the target information. The information management method according to claim 8, wherein the requester makes an inquiry to the relay source with a part of the relevance data model connection information for the relevance data related to the target information held by the provider. An information management system including a storage unit and a processor that can access the storage unit.
The storage unit
Relevance data models that define the data structure of information,
Relevance data that defines the relevance of the information to the relevance data model,
Holds relevance data model connection information that shows relevance to the distributed relevance data model
The processor is an information management system that requests acquisition of a distributed relevance data model and relevance data model connection information associated with the relevance data model based on the relevance data model connection information. Based on the relevance data model connection information that shows the relevance between the first relevance data model that defines the data structure of the first information and the second relevance data model that defines the data structure of the second information. The process of requesting the acquisition of the first relevance data model and the distributed second relevance data model, and
An information management program that causes a computer to execute a process of requesting acquisition of the second information associated with the second relevance data model based on the acquisition result of the second relevance data model.

Images