Information management system, information management method, and information management program

Abstract

To provide an information management system and an information management method capable of managing information about a device.SOLUTION: The information management system for managing information about a device comprises: first generation means for generating a type data set composed of information common among devices belonging to the same type; and second generation means for generating an instance including information about an actually manufactured device and a type data set for the actually manufactured device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information management system, an information management method, and an information management program. [Background technology]

[0002] With the development of information and communication technology, it has become possible to collect, manage, and distribute huge amounts of information. Attempts are being made to realize production management at manufacturing sites with finer granularity. For example, Patent Document 1 (JP 2017-068816 A) discloses a configuration for achieving more detailed production management even at manufacturing sites where production management is performed on an order basis. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-068816 A Summary of the Invention [Problem to be solved by the invention]

[0004] A typical device is composed of multiple parts, and usually, these multiple parts are not manufactured by a single manufacturer but by multiple manufacturers. Furthermore, the device goes through various processes before being distributed to the market, and maintenance may be required after the device starts being used.

[0005] The present invention provides an information management system and method capable of managing information relating to a device. [Means for solving the problem]

[0006] According to an embodiment of the present invention, there is provided an information management system for managing information relating to devices, the information management system including a first generating means for generating a type data set consisting of information common to devices belonging to the same type, and a second generating means for generating an instance including information relating to actually manufactured devices and the type data set for the actually manufactured devices.

[0007] With this configuration, by using a type data set for information that is common among devices belonging to the same type, information can be managed without duplication among multiple devices, and by using instances that contain information specific to each device, information about each device can be collected and managed throughout its lifecycle.

[0008] The information management system may further include a determination unit for determining identification information for uniquely identifying an actually manufactured device. The instance may include instance identification information based on the identification information. With this configuration, an instance including information about each device can be easily identified based on the identification information that uniquely identifies the device.

[0009] The information management system may further include a registration unit that registers the history of the use of the actually manufactured device in the instance. With this configuration, in addition to the information on how each device was manufactured, information on how it is used can be included in one instance.

[0010] The instance may include sub-instances that include information related to the parts included in the actually manufactured device. With this configuration, it is easy to obtain unique information about each part that constitutes each device, such as how it was manufactured.

[0011] The information management system may further include an associating unit for associating sub-instances corresponding to parts included in the actually manufactured device with the instance. With this configuration, the configuration of the actually manufactured device can be reflected in the instance according to the individual parts determined when the device is actually manufactured.

[0012] The sub-instance may include information related to the transportation of parts included in the actually manufactured device. With this configuration, the process of assembling parts into a product after they are manufactured can be easily managed.

[0013] The sub-instance may include a subtype data set that includes information common to parts of the same type as the parts included in the actually manufactured device. This configuration eliminates the need to duplicate information between parts of the same type, thereby enabling efficient information management.

[0014] The sub-instance may further include an information providing unit for providing information included in the instance upon request. This configuration makes it possible to utilize or make use of instances that store various information.

[0015] According to another embodiment of the present invention, there is provided an information management method for managing device-related information by a computer, the information management method including the steps of generating a type data set consisting of information common to devices belonging to the same type, and generating an instance including information related to actually manufactured devices and the type data set for the actually manufactured devices.

[0016] According to yet another embodiment of the present invention, there is provided an information management program for causing a computer to execute an information management method for managing information relating to devices, the information management program causing the computer to execute the steps of generating a type data set consisting of information common to devices belonging to the same type, and generating an instance including information relating to actually manufactured devices and the type data set for the actually manufactured devices. Effect of the Invention

[0017] According to the present invention, it is possible to provide an information management system and an information management method capable of managing information relating to a device. [Brief description of the drawings]

[0018] [Figure 1] 1 is a schematic diagram showing an overview of an information management system according to an embodiment of the present invention; [Diagram 2] 2 is a block diagram showing an example of a hardware configuration of a server device constituting the information management system according to the present embodiment. FIG. [Diagram 3] FIG. 2 is a schematic diagram showing an example of processing in a design and development phase of an information management system according to the present embodiment. [Figure 4] 1 is a schematic diagram showing an example of processing in a manufacturing phase and a usage phase of an information management system according to an embodiment of the present invention; [Diagram 5] FIG. 2 is a schematic diagram showing an example of use of an instance of the information management system according to the present embodiment. [Figure 6] 2 is a diagram illustrating an example of a data structure of an instance of the information management system according to the present embodiment. FIG. [Figure 7] FIG. 7 illustrates an example data structure used to generate the instance shown in FIG. 6. [Figure 8] 5 is a flowchart showing a processing procedure of an information management method executed in the information management system according to the present embodiment. [Figure 9]It is a schematic diagram showing an example of a functional configuration for realizing an information management method executed in the information management system according to the present embodiment.

Embodiment for Carrying Out the Invention

[0019] Embodiments of the present invention will be described in detail with reference to the drawings. For the same or corresponding parts in the drawings, the same reference numerals are given and their descriptions will not be repeated.

[0020] <A. Application Example> First, an example of the overall configuration of the information management system 1 according to the present embodiment will be described. FIG. 1 is a schematic diagram showing an overview of the information management system 1 according to the present embodiment.

[0021] Referring to FIG. 1, the information management system 1 manages information related to devices and provides a data sharing platform capable of collecting and managing information about any device over its life cycle. FIG. 1 shows an example of an instance 2 of a certain device (Device A) managed in the data sharing platform.

[0022] In this specification, an "instance" means a set of data related to a specific device. Alternatively, an "instance" may mean a specific type of component that can be specifically and clearly identified.

[0023] Also, in this specification, a "type" means a hardware element or a software element for specifying common features and characteristics of instances belonging to the same type, and includes a uniquely specified device number, a set of development documents, manufacturing and test instructions, technical materials, etc. That is, a "type" means information such as common characteristics and does not depend on individual devices.

[0024] Identification information (ID) for uniquely identifying the target device is assigned to instance 2 for device A. More specifically, an instance ID 200 generated from identification information for uniquely identifying the target device is assigned to instance 2. The instance ID corresponds to instance identification information for uniquely identifying instance 2.

[0025] The instance 2 may include manufacturing quality 202, usage history 204, and individual configuration information 206. These pieces of information are unique to the target device, and therefore are associated with the instance ID 200. More specifically, the manufacturing quality 202 includes information indicating the circumstances under which the target device was manufactured (e.g., traceability information, etc.). The usage history 204 includes a history of the target device being used by a user. The individual configuration information 206 includes information for identifying the target device and information on one or more parts that constitute the target device.

[0026] A type ID 210 for identifying the type of the target device is further assigned to the instance 2. The instance 2 may include type common information 220 in association with the type ID 210.

[0027] The type common information 220 includes design data 222, configuration information 224, a data sheet 226, and a manual 228. These pieces of information are specific to devices of the same type as the target device, and are therefore associated with the type ID 210. More specifically, the design data 222 includes information such as CAD data. The configuration information 224 includes information on the parts that make up the target device. The data sheet 226 includes information such as the specifications of the target device. The manual 228 includes an instruction manual for the target device. The entities of these pieces of information may be placed in any position, and only the URI (Uniform Resource Identifier) ​​of the placed entity may be stored.

[0028] Here, we will explain the instance ID 200 and the type ID 210. The devices from which the information management system 1 collects and manages information are typically assigned an SGTIN (Serialized Global Trade Item Number), which is an identification code defined by GS1, whose headquarters are in Brussels, Belgium, to each device and each part.

[0029] The SGTIN includes a Global Trade Item Number (GTIN) that identifies the type of product and a serial number that uniquely identifies each product. The instance ID 200 is identification information for uniquely identifying the target device. The instance ID 200 can be generated, for example, using the entire SGTIN or a portion of the serial number included in the SGTIN.

[0030] On the other hand, the type ID 210 is identification information for identifying devices of the same type. For example, the type ID 210 uses the Global Trade Item Number (GTIN) included in the SGTIN.

[0031] In this way, by using two types of IDs, instance ID 200 and type ID 210, for instance 2 for each device, it is possible to efficiently manage information specific to the target device and information specific to devices of the same type as the target device.

[0032] Any identification information that can uniquely identify the target device may be used for the instance ID 200. Similarly, any identification information that can uniquely identify the type (kind) of the target device may be used for the type ID 210.

[0033] The instance 2 for the device A may further be associated with one or more sub-instances 250 of one or more parts that constitute the device A. The one or more sub-instances 250 associated with the instance ID 200 correspond to one or more parts that constitute the actual device identified by the instance ID 200. In other words, each of the sub-instances 250 includes information related to a part included in the actually manufactured device.

[0034] In this way, information contained in instance 2 is added, etc., to correspond to the configuration of the actual device.

[0035] Each sub-instance 250 is assigned an identification (ID) for uniquely identifying the target part (e.g., device a). More specifically, an instance ID 260 generated based on identification information for uniquely identifying the target device a is assigned to the sub-instance 250. Also, a type ID 270 for identifying the type of the target part (e.g., device a) is assigned to each sub-instance 250.

[0036] Each of the sub-instances 250 may include a manufacturing quality 252 and a logistics quality 254. These pieces of information are unique to the target part, and therefore are associated with an instance ID 260. More specifically, the manufacturing quality 252 includes information (e.g., traceability information) indicating the circumstances under which the target part was manufactured. The logistics quality 254 includes information related to the transportation of parts included in equipment that has actually been manufactured. More specifically, the logistics quality 254 includes the history of the target part being transported from a parts manufacturer to an equipment manufacturer.

[0037] The sub-instance 250 may include type common information 280 in association with the type ID 270. The type common information 280 includes design data 282, a data sheet 286, and a manual 288. These pieces of information are specific to the same type of device as the target part, and are therefore associated with the type ID 270. More specifically, the design data 282 includes information such as CAD data. The data sheet 286 includes information such as the specifications of the target part. The manual 228 includes an instruction manual for the target part. The entities of these pieces of information may be placed in any position, and only the URIs of the entities may be stored.

[0038] Furthermore, the entities of one or more sub-instances 250 associated with instance 2 may also be arranged in any position, and only the URIs of the entities arranged may be stored.

[0039] Furthermore, if a part corresponding to one sub-instance 250 is further composed of one or more parts, one or more sub-instances 250 may be further associated with the sub-instance 250.

[0040] In this manner, one or more sub-instances 250 may be directly associated with the instance ID 200 of the target device, and one or more sub-instances 250 may be hierarchically associated with the instance ID 260 of a part contained in one sub-instance 250.

[0041] Instance 2 is added or updated by the phase and / or stakeholder involved in the target device. It is also assumed that Instance 2 is used and utilized by the stakeholders.

[0042] FIG. 1 shows two axes, an engineering chain 10 and a supply chain 20, as typical examples.

[0043] Engineering chain 10 includes, as an example of a phase, a planning phase 12, a development phase 14, and a manufacturing preparation phase 16. Further, the phases of the engineering chain 10 may include a procurement phase, a manufacturing phase, a shipping phase, and the like.

[0044] Supply chain 20 includes, as an example of a stakeholder, a component manufacturer 22, a logistics person 24, an equipment manufacturer 26, and an equipment user 28. The component manufacturer 22 is a manufacturer of components that make up the target equipment, and the equipment manufacturer 26 is a manufacturer of the target equipment. The logistics person 24 is the one who transports the components manufactured by the component manufacturer 22 to the equipment manufacturer 26. Note that the logistics person 24 may also be the one who transports the equipment manufactured by the equipment manufacturer 26 to the equipment user 28. The equipment user 28 is the one who uses the equipment manufactured by the equipment manufacturer 26. The equipment user 28 is the one who manufactures any item using the target equipment.

[0045] Details of the addition or update of instance 2 by a phase and / or a stakeholder, and the use of instance 2 by a stakeholder will be described later.

[0046] <B. Example of Hardware Configuration of Server Device> FIG. 2 is a block diagram showing an example of the hardware configuration of a server device 100 that constitutes the information management system 1 according to the present embodiment. Referring to FIG. 2, the server device 100 is an example of a computer and includes one or more processors 102, one or more main memories 104, a display unit 106, an input unit 108, one or more communication interfaces 110, and a storage 120. Each component is electrically connected via a bus 112.

[0047] The processor 102 is composed of a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), a GPU (Graphical Processing Unit), etc., reads out various programs stored in the storage 120, expands them in the main memory 104, and executes them to realize various processes as described later.

[0048] The display unit 106 is composed of a liquid crystal display or the like, and displays the processing result by the processor 102. The input unit 108 is composed of a keyboard, a mouse, etc., and receives operations from the user. The communication interface 110 exchanges data with an arbitrary device.

[0049] The storage 120 is composed of an HDD (Hard Disk Drive), an SSD (Solid State Drive), etc., and stores, for example, an OS 122, an information management program 124, and a data chain 126 including an instance 2 described later.

[0050] FIG. 2 shows a configuration example in which functions necessary for the processor 102 to execute a program are provided. However, some or all of these provided functions may be implemented using a dedicated hard-wired circuit (for example, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc.). That is, the processes executed and the functions provided by the server device 100 may be realized by a processing circuit including a processor, an ASIC, an FPGA, etc.

[0051] Furthermore, a plurality of server devices 100 may manage the instance 2 in a distributed manner, and any hardware resources may be adopted for the information management system 1.

[0052] <C. Usage Example of Instance> Next, a usage example of the instance 2 managed by the information management system 1 according to the present embodiment will be described.

[0053] (c1: Design and development phase) Fig. 3 is a schematic diagram showing a processing example in the design and development phase of the information management system 1 according to the present embodiment. Referring to Fig. 3, in the design and development phase, since the actual device has not yet been manufactured, there is no instance 2, and only a type data set 2A associated with a type ID 210 exists. In addition, there is no sub-instance 250, and only a sub-type data set 250A exists.

[0054] The type data set 2A is composed of information common to devices of the same type. A type ID 210 is assigned to the type data set 2A, and type common information 220 is associated with the type data set 2A. The subtype data set 250A is composed of information common to parts included in an actually manufactured device and parts belonging to the same type. A type ID 270 is assigned to the subtype data set 250A, and type common information 280 is associated with the type data set 250A.

[0055] In the design and development phase, basically, the parts manufacturer 22 designs and develops the parts, and the equipment manufacturer 26 designs and develops the equipment, each independently.

[0056] In the component development phase 14, the component manufacturer 22 registers type-common information 280 (design data 282, data sheet 286, manual 288, etc.) in the information management system 1 in association with the type ID 270 of the component (data addition process 50). Also, in the component manufacturing preparation phase 16, the component manufacturer 22 may register type-common information 280 (design data 282, data sheet 286, manual 288, etc.) in association with the type ID 270 of the component in the information management system 1 (data addition process 52). The type-common information 280 is static information common to the component at the stage prior to manufacturing the actual part.

[0057] Meanwhile, the equipment manufacturer 26 registers type common information 220 (design data 222, configuration information 224, data sheet 226, manual 228, etc.) in the information management system 1 in association with the type ID 210 of the equipment during the development phase and / or manufacturing preparation phase of the equipment (data addition process 54). The type common information 280 is static information common to the parts at the stage prior to the manufacture of the actual parts. At this time, the equipment manufacturer 26 specifies one or more parts to be used in the target equipment, and a subtype data set 250A corresponding to the parts to be used is associated with the type data set 2A (nesting process 56).

[0058] Such a type data set 2A is generated in advance, and then the instance 2 is generated.

[0059] (c2: Manufacturing phase / Use phase) Fig. 4 is a schematic diagram showing an example of processing in the manufacturing phase and the use phase of the information management system 1 according to the present embodiment. With reference to Fig. 4, in the manufacturing phase and / or the use phase, an actual device is manufactured and the manufactured device is used, so an instance 2 is generated. The instance 2 includes information related to the actually manufactured device and a type data set 2A for the actually manufactured device.

[0060] In the part manufacturing phase, the part manufacturer 22 generates a sub-instance 250 from a sub-type data set 250A (see FIG. 3) for each part during or after manufacturing, and assigns an instance ID 260, which is generated based on identification information that uniquely identifies the target part, to the generated sub-instance 250 (data addition process 60). In the data addition process 60, the part manufacturer 22 registers the manufacturing quality 252 of the target part in the information management system 1.

[0061] During the transportation process of a part manufactured by the part manufacturer 22, the logistics person 24 registers the logistics quality 254 of the part in the information management system 1 (data addition process 60). At this time, the target sub-instance 250 (instance ID 260) is identified based on the SGTIN assigned to the part manufacturer 22. The target sub-instance 250 may be identified by the logistics person 24 or may be identified by the server device 100 (not shown).

[0062] In the manufacturing phase of the equipment, the equipment manufacturer 26 determines identification information (SGTIN) for uniquely identifying the equipment during or after manufacturing. The equipment manufacturer 26 also generates an instance 2 from the type data set 2A (see FIG. 3), assigns an instance ID 200 generated based on the identification information that uniquely identifies the target equipment to the generated instance 2, and includes the identification information in the individual configuration information 206 (data addition process 64). The equipment manufacturer 26 also registers the manufacturing quality 202 of the target equipment in the information management system 1 (data addition process 66). In this way, the instance 2 includes instance identification information (instance ID 200) based on the identification information (SGTIN) of the target equipment.

[0063] Furthermore, the equipment manufacturer 26 identifies one or more parts used in the target equipment, and one or more sub-instances 250 corresponding to the one or more parts used are associated with the instance 2 (nesting process 68). In this way, the information management system 1 associates the sub-instances 250 corresponding to the parts included in the actually manufactured equipment with the instance 2.

[0064] When the equipment manufactured by the equipment manufacturer 26 is delivered to the equipment user 28 and the equipment user 28 starts using the equipment, the equipment user 28 registers the usage history 204 of the equipment in the information management system 1 (data addition process 70). In this way, the information management system 1 registers the history of the actual use of the manufactured equipment in the instance 2.

[0065] As described above, with the instance 2 of the device manufactured by the device manufacturer 26 at the center, the parts constituting the device and the usage history of the device can be managed in a total manner.

[0066] (c3: Use instance 2) In response to a request, the information management system 1 can provide the information contained in the instance 2. Fig. 5 is a schematic diagram showing an example of the use of the instance 2 of the information management system 1 according to this embodiment.

[0067] Referring to FIG. 5, for example, if there is some kind of defect in equipment incorporating a certain part, parts manufacturer 22 can verify the transportation process to equipment manufacturer 26 by referring to logistics quality 254 added by logistics specialist 24 (utilization process 72).

[0068] Similarly, if there is some kind of defect in equipment incorporating a certain part, the equipment manufacturer 26 can refer to the logistics quality 254 added by the logistics specialist 24 (use process 74) and verify the transportation process to the equipment manufacturer 26, etc.

[0069] Furthermore, equipment manufacturer 26 can easily obtain necessary information for the parts incorporated in the target equipment by referring to type common information 280 (use process 76). For example, by referring to design data 282 and data sheets 286 of the parts, the equipment manufacturer can evaluate the design validity of the target equipment. Furthermore, by referring to the parts manual 288, the equipment manufacturer can investigate the cause of any malfunctions that have occurred and create a manual for the target equipment.

[0070] Furthermore, the device user 28 can refer to the type-common information 220 of the target device to check how to use it and whether it complies with the specifications.

[0071] Note that there may be information that cannot be provided to others without limit. In such a case, the information may be set to private as necessary. For example, as shown in FIG. 5, the manufacturing quality 252 and logistics quality 254 of the sub-instance 250, as well as the design data 282, may be set to private. In this case, the information may be made accessible to others with the permission of the owner.

[0072] In addition, the manufacturing quality 202, the usage history 204, and the individual configuration information 206 of the instance 2, as well as the design data 222 and the configuration information 224, may be set to be private. Even in this case, it may be possible for others to access the information if the owner gives permission.

[0073] For example, in consideration of data utilization, the usage history 204 registered by the equipment user 28 may be provided to a third party for a fee based on a contract or the like with the equipment user 28. Fig. 5 shows an example of information provision to the parts manufacturer 22 (use process 80) and information provision to the equipment manufacturer 26 (use process 82).

[0074] As another embodiment, in a case where a plurality of equipment manufacturers 26 deliver their respective equipment to the same equipment user 28 and the plurality of equipment manufacturers 26 collect maintenance information of the equipment they delivered, the necessary maintenance information may be provided to a third party such as an equipment diagnosis service provider at the discretion or permission of the equipment user 28. For example, even in a case where a party to whom the equipment user 28 entrusts maintenance wants to refer to the information of the equipment, data can be distributed smoothly. In this case, a part of the compensation paid from the equipment diagnosis service provider to the equipment user 28 may be provided to the equipment manufacturer 26 that collected the provided maintenance information. By adopting such a scheme, a cycle of data utilization can be realized among the equipment user 28, one or more equipment manufacturers 26, and a third party.

[0075] In this way, by determining the owner of each piece of data through a contract or other arrangement, the use and distribution of collected data can be simplified and facilitated.

[0076] (c4: Data structure example) Fig. 6 is a diagram showing an example of a data structure of an instance 2 of the information management system 1 according to the present embodiment. Fig. 7 is a diagram showing an example of a data structure used to generate the instance 2 shown in Fig. 6.

[0077] A data structure in which each value is arranged hierarchically may be adopted as the instance 2, as shown in Fig. 6. The instance 2 shown in Fig. 6 may be generated by reflecting information on an instance generated as real parts and devices are manufactured in the type data set 2A shown in Fig. 3.

[0078] 6 and 7, an International Registration Data Identifier (IRDI), which is identification information for uniquely identifying data, may be added to the instance 2 and / or each data included in the instance 2. By using the IRDI, it is possible to facilitate the registration (uploading) of data to the information management system 1 and the use (downloading) of data managed by the information management system 1.

[0079] Furthermore, category information may be added to each piece of data included in the instance 2. Examples of categories include whether the data belongs to an instance or a type, and whether the data is set to public or private.

[0080] Furthermore, information for identifying the owner may be added to instance 2 and / or each data included in instance 2. Furthermore, if there is a hierarchical relationship (parent-child relationship) between data, index information of the parent data and index information of the child data may be added. Open Key information may be added to manage access authority.

[0081] Also, by adding time information between data having the same instance ID, data management in time series becomes possible.

[0082] (c5: Implementation example) The data collected and managed by the information management system 1 may be, for example, distributed and held in a plurality of server devices using a blockchain. By using a blockchain, it is possible to prevent unauthorized alteration of data.

[0083] When implemented using a blockchain, the public / non-public setting for each piece of information may be realized using, for example, Decentralized identity or Identity on Blockchain.

[0084] The collection and management of data by the information management system 1 may be implemented using AAS (Asset Administration Shell). By using AAS, the data collected and managed is standardized, so that information that meets arbitrary conditions can be searched efficiently and automatically. By using AAS, it is also possible for a bot to search for necessary information according to the state of a device, for example, and display it to the user without going through the user.

[0085] <D. Processing procedure> FIG. 8 is a flowchart showing the processing procedure of the information management method executed in the information management system 1 according to the present embodiment. Each step shown in FIG. 8 is typically realized by the processor 102 of the server device 100 executing the information management program 124.

[0086] Referring to FIG. 8, the server device 100 assigns a type ID 210 to the type common information 220 (design data 222, configuration information 224, data sheet 226, manual 228, etc.) registered by the device manufacturer 26 to generate a type data set 2A (step S2).

[0087] Furthermore, the server device 100 assigns the type ID 270 to the type common information 280 (design data 282, data sheet 286, manual 288, etc.) registered by the parts manufacturer 22 to generate the subtype data set 250A (step S4).

[0088] Furthermore, the server device 100 associates one or more subtype data sets 250A with the type data set 2A in accordance with the configuration information 224 registered by the device manufacturer 26 (step S6).

[0089] Through the above-described processing procedure, the type data set 2A and the subtype data set 250A are generated. In this manner, the server device 100 executes processing for generating a type data set made up of information common to devices belonging to the same type.

[0090] Subsequently, when the parts manufacturer 22 manufactures an arbitrary part, the server device 100 determines identification information that uniquely identifies the manufactured part (step S8), generates an instance ID 260 based on the determined identification information (step S10), and generates a sub-instance 250 of the part to which the generated instance ID 260 is assigned (step S12). Furthermore, the server device 100 associates the manufacturing quality 252 registered by the parts manufacturer 22 with the sub-instance 250 (step S14). Note that the process of determining identification information that uniquely identifies a part may be executed by the parts manufacturer 22, rather than by the server device 100.

[0091] Also, the logistics quality 254 registered by the logistics person 24 is associated with the sub-instance 250 (step S16).

[0092] Next, when the equipment manufacturer 26 manufactures an arbitrary equipment using one or more parts, the server device 100 determines identification information that uniquely identifies the manufactured equipment (step S18), generates an instance ID 200 based on the determined identification information (step S20), and generates an instance 2 of the equipment to which the generated instance ID 200 is assigned (step S22). Next, the server device 100 associates the individual configuration information 206 and the manufacturing quality 202 registered by the equipment manufacturer 26 with the instance 2 (step S24). Note that the process of determining the identification information that uniquely identifies the equipment may be executed by the equipment manufacturer 26, not by the server device 100. Furthermore, the server device 100 refers to the individual configuration information 206 to identify a sub-instance 250 of one or more parts that configure the target equipment, and associates it with the instance 2 (step S26).

[0093] Thereafter, when the usage history 204 generated by the device user 28 using the target device is registered, the server device 100 associates the usage history 204 with the instance 2 (step S28).

[0094] Through the above-described process, the instance 2 is generated. In this manner, the server device 100 executes the process of generating the instance 2 including information related to the actually manufactured device and the type data set for the actually manufactured device.

[0095] Furthermore, when a request is made to use any data included in instance 2 (YES in step S30), the server device 100 determines whether the access source has a predetermined access authority (step S32).

[0096] If the access source has the predetermined access authority (YES in step S32), the server device 100 provides the requested data to the access source (step S34). On the other hand, if the access source does not have the predetermined access authority (NO in step S32), the server device 100 rejects the requested access (step S36).

[0097] The above processing is repeated.

[0098] <E. Functional Configuration> FIG. 9 is a schematic diagram showing an example of a functional configuration for realizing an information management method executed in the information management system 1 according to the present embodiment. Referring to FIG. 9, the server device 100 includes, as functional components, an interface unit 150, a type data generation unit 152, an instance generation unit 154, an identification information generation unit 156, an association unit 158, a registration unit 160, an information providing unit 162, a type data storage unit 170, and an instance storage unit 172. The type data storage unit 170 and the instance storage unit 172 may be realized by using at least a part of the storage 120 of the server device 100. Regarding other functional configurations, they may be realized by the processor 102 of the server device 100 executing the information management program 124.

[0099] The interface unit 150 exchanges information with, for example, the component manufacturer 22, the logistics person in charge 24, the device manufacturer 26, and the device user 28, which are examples of stakeholders.

[0100] The type data generation unit 152 generates a type data set 2A consisting of common information among devices belonging to the same type and / or a sub-type data set 250A consisting of common information among parts belonging to the same type as the parts included in the actually manufactured device in response to a request from a stakeholder.

[0101] The instance generation unit 154 generates an instance 2 including information related to the actually manufactured device and the type data set 2A for the actually manufactured device.

[0102] The identification information generation unit 156 determines identification information (for example, SGTIN) for uniquely identifying the actually manufactured device. Further, the identification information generation unit 156 may determine identification information (for example, SGTIN) for uniquely identifying the parts included in the device.

[0103] The association unit 158 associates the sub-instance 250 corresponding to the components included in the actually manufactured device with the instance 2.

[0104] The registration unit 160 registers in the instance 2 the history of use of the actually manufactured device in response to a request from a stakeholder.

[0105] The information providing unit 162 provides the information included in the instance 2 in response to a request.

[0106] The type data storage unit 170 stores the type data set 2A and / or the sub-type data set 250A.

[0107] The instance storage unit 172 stores the instance 2.

[0108] <Appendix F> The present embodiment as described above includes the following technical ideas.

[0109] [Configuration 1] An information management system (1) for managing information related to a device, a first generation means (152) for generating a type data set (2A) consisting of information common among devices belonging to the same type, and a second generation means (154) for generating an instance (2) including information related to the actually manufactured device and the type data set for the actually manufactured device. An information management system.

[0110] [Configuration 2] further comprising a determination means (156) for determining identification information for uniquely identifying the actually manufactured device, wherein the instance includes instance identification information (200) based on the identification information. The information management system according to Configuration 1.

[0111] [Configuration 3] 3. The information management system according to configuration 1 or 2, further comprising a registration means (160) for registering a history (204) of the use of the actually manufactured device in the instance.

[0112] [Configuration 4] 4. The information management system according to any one of configurations 1 to 3, wherein the instance includes a sub-instance (250) including information related to a part included in the actually manufactured device.

[0113] [Configuration 5] 5. The information management system according to configuration 4, further comprising an associating means (158) for associating the sub-instance corresponding to a part included in the actually manufactured device with the instance.

[0114] [Configuration 6] 6. The information management system of configuration 4 or 5, wherein the sub-instance includes information (254) related to transportation of parts included in the actually manufactured device.

[0115] [Configuration 7] The information management system according to any one of configurations 4 to 6, wherein the sub-instance includes a subtype data set (250A) consisting of information common to parts belonging to the same type as the parts included in the actually manufactured device.

[0116] [Configuration 8] 8. The information management system according to any one of configurations 1 to 7, further comprising an information providing means (162) for providing information included in the instance in response to a request.

[0117] [Configuration 9] An information management method for managing information related to a device by a computer (100), comprising the steps of: generating a type data set consisting of information common to devices belonging to the same type (S2, S4); An information management method comprising: a step (S20) of generating an instance including information related to a device that has actually been manufactured and a type data set for the device that has actually been manufactured.

[0118] [Configuration 10] An information management program (124) for causing a computer (100) to execute an information management method for managing information related to a device, the information management program (124) being generating a type data set consisting of information common to devices belonging to the same type (S2, S4); and generating (S20) an instance including information related to an actually manufactured device and a type data set for the actually manufactured device.

[0119] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not the above description, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0120] 1 Information management system, 2 Instance, 2A type data set, 10 Engineering chain, 12 Planning phase, 14 Development phase, 16 Manufacturing preparation phase, 20 Supply chain, 22 Parts manufacturer, 24 Logistics manager, 26 Equipment manufacturer, 28 Equipment user, 50, 52, 54, 60, 64, 66, 70 Data addition processing, 56, 68 Nest processing, 72, 74, 76, 80, 82 Usage processing, 100 Server device, 102 Processor, 104 Main memory, 106 Display unit, 108 Input unit, 110 Communication interface, 112 Bus, 120 Storage, 122 OS, 124 Information management program, 150 Interface unit, 152 Type data generation unit, 154 Instance generation unit, 156 Identification information generation unit, 158 Association unit, 160 Registration unit, 162 Information provision unit, 170 Type data storage section, 172 Instance storage section, 200,260 Instance ID, 202,252 Manufacturing quality, 204 Usage history, 206 Individual configuration information, 210,270 Type ID, 220,280 Type common information, 222,282 Design data, 224 Configuration information, 226,286 Data sheet, 228,288 Manual, 250 Sub-instance, 250A Sub-type data set, 254 Logistics quality.

Claims

1. An information management system for managing information related to a device, a first generating means for generating a type data set including information common to devices of the same type; a storage means for storing said type data set; a second generating means for generating an instance including information related to a real manufactured device and a type data set for said real manufactured device; a determination means for determining identification information for uniquely identifying the actually manufactured device; a registration means for registering a history of the use of the actually manufactured device in the instance based on information from a person related to the actually manufactured device, The instance includes an instance identification based on the identification information.

2. The information management system of claim 1 , wherein the instance includes a sub-instance that includes information related to a part included in the actually manufactured device.

3. 3. The information management system according to claim 2, further comprising an associating means for associating the sub-instances corresponding to parts included in the actually manufactured device with the instances.

4. The information management system according to claim 2 or 3, wherein the sub-instance includes information related to transportation of parts included in the actually manufactured device.

5. 5. An information management system according to claim 2, wherein the sub-instance includes a subtype data set consisting of information common to parts belonging to the same type as the parts included in the actually manufactured equipment.

6. 6. The information management system according to claim 1, further comprising an information providing unit that provides the information included in the instance in response to a request.

7. A computer-implemented information management method for managing information relating to a device, comprising: generating a type data set consisting of information common to devices of the same type; storing the type data set; generating an instance including information related to a real manufactured device and a type data set for said real manufactured device; determining identification information for uniquely identifying the actually manufactured device; and registering a history of the use of the actually manufactured device in the instance based on information from a person related to the actually manufactured device, The instance includes instance identification information based on the identification information.

8. An information management program for causing a computer to execute an information management method for managing information related to a device, the information management program comprising: generating a type data set consisting of information common to devices of the same type; storing the type data set; generating an instance including information related to a real manufactured device and a type data set for said real manufactured device; determining identification information for uniquely identifying the actually manufactured device; and registering a history of the use of the actually manufactured device in the instance based on information from a person related to the actually manufactured device; The instance includes instance identification information based on the identification information.

Images