Information processing device, information processing system, and information processing program

Abstract

In parts searches, the system allows for multidimensional filtering by using type (part category) and condition (new, used, etc.) as independent criteria. [Solution] The information processing device comprises a storage unit that stores component IDs and attribute information in association, and a control unit that searches for components based on the attribute information. The attribute information includes component type information indicating the type of component and component condition information indicating the state of the component, each as separate data items. The condition information includes a value indicating whether the component is new, used, or refurbished, and the control unit identifies components that meet the conditions based on the combination of component type information and condition information.

Description

Technical Field

[0001] The present invention relates to an information processing device, information processing system and an information processing program.

Background Art

[0002] Techniques for managing vehicle parts have been proposed. In Patent Document 1, a technique for specifying parts that can be attached to a vehicle by associating and managing a vehicle ID indicating the vehicle, a part ID indicating the part, and information indicating whether the part can be attached has been proposed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As parts that can be attached to a vehicle, in addition to genuine parts by vehicle manufacturers, there are also alternative parts that are compatible with genuine parts, and different model numbers are assigned to each of the genuine parts and alternative parts. Also, in the case of parts supplied by an Original Equipment Manufacturer (OEM), even for the same part, the model number assigned to the part at the supplier and the model number assigned to the part at the customer may be different. Therefore, when replacing a part mounted on a vehicle, it is not easy to identify the part to be used for replacement. Such problems are common to the repair of products other than vehicles.

[0005] Furthermore, regarding data registration and management, building and maintaining a database for managing information on replacement parts required considerable effort in registering part information and the correspondence between parts. In particular, if an incorrect correspondence was registered, the wrong replacement part would be suggested, potentially leading to a decline in repair quality. Moreover, there were cases where a correspondence that had been deleted as an error was mistakenly registered again at a later date, highlighting the need for a mechanism to prevent the same error from being repeated.

[0006] Furthermore, regarding system configuration and processing efficiency, a challenge arose when numerous repair shops simultaneously requested replacement parts, potentially leading to a concentration of load on the system and a decrease in response performance. In particular, efficiently utilizing system resources was difficult when processing large volumes of inquiries that did not require real-time processing (e.g., bulk inquiries for inventory replenishment) immediately. Moreover, in an environment where multiple locations accessed the database in a distributed manner, a mechanism was needed to efficiently share centrally managed data.

[0007] Furthermore, when the target is software, the challenges related to component substitution, as described above, are not limited to the physical components of a product. Modules or libraries that make up computer programs may also require the identification of compatible alternative modules as versions are upgraded or dependencies change. In particular, with the proliferation of open-source software, the need to replace modules with security vulnerabilities with compatible and secure modules is increasing.

[0008] Furthermore, regarding visualization and usability challenges, the relationships between products, parts, and interchangeable parts can form complex hierarchical and network structures. It is difficult for users to intuitively grasp such complex relationships, and there was a need for a mechanism to visualize the relationship structure from various perspectives. In addition, part numbers and serial numbers obtained from external sources may undergo format changes or duplicates, and there was a need for a robust data management platform that does not rely on this external data.

[0009] One aspect of the technology disclosed is an information processing device that can easily identify the parts to be replaced during repairs. system and aims to provide information processing programs. 。 Another aspect of the disclosed technology is an information processing device that can streamline the registration process of part information and correspondence information between parts, and prevent erroneous registration. system and aims to provide information processing programs. 。 Another aspect of the disclosure technology aims to efficiently utilize system resources to handle a large volume of inquiry requests and to provide a parts management system that can be accessed in a distributed manner from multiple locations. 。 Another aspect of the disclosed technology is an information processing device that manages the compatibility of modules or libraries that make up a computer program and can easily identify alternative modules. system and aims to provide information processing programs. 。 Another aspect of the disclosure technology aims to provide a robust data management platform that is independent of external data formats, by visualizing products, components, and substitute relationships between components from diverse perspectives. [Means for solving the problem]

[0010] One aspect of the disclosed technology is exemplified by the following information processing device: The information processing device includes a storage unit that stores first correspondence information which associates a part ID that uniquely identifies each of a plurality of parts used to repair a product with part attribute information which indicates the attributes of the part, and second correspondence information which associates the part IDs of the parts that can be substituted for each other; and a control unit that, based on a request from an external device which includes the part attribute information for the first part used to repair the product, performs the following: a process which identifies the part ID corresponding to the first part based on the part attribute information by referring to the first correspondence information; a process which obtains the part ID of a substitute part that replaces the first part by referring to the second correspondence information based on the identified part ID; a process which obtains the part attribute information corresponding to the part ID of the substitute part by referring to the first correspondence information; and a process which transmits the obtained part attribute information corresponding to the part ID of the substitute part to the external device.

[0011] According to this information processing device, even if product manufacturers or compatible parts manufacturers assign unique part numbers to parts, a part ID that uniquely identifies each part is assigned to it. Then, the part IDs of mutually interchangeable parts are associated with the second correspondence information described above. In this information processing device, where the correspondence of part IDs is managed in this way, the part attribute information of the replacement part can be transmitted to the external device based on a request that includes the part attribute information of the first part used to repair the product, making it easy to identify interchangeable parts.

[0012] The information processing device may further have the following features: The control unit accesses a server managed by the manufacturer of each of the above-mentioned components to identify the components that can be substituted for each other. By obtaining information from the server managed by the manufacturer, the information processing device can make the information on the components that can be substituted for each other more reliable.

[0013] This information processing device may further have the following features: It acquires repair history information, including the above-mentioned part attribute information, from the above-mentioned external device, and identifies the above-mentioned parts that can be substituted for each other based on the acquired repair history information. By using the above-mentioned repair history information, which includes information on the parts actually used in the repair, this information processing device can make the information on the above-mentioned parts that can be substituted for each other more reliable.

[0014] The information processing device may further have the following features. The control unit outputs a hierarchical structure in which an image representing the product is the root, and images representing the multiple parts are placed as nodes under the root, and the images representing the parts associated in the second correspondence information are connected by line segments. By outputting such a hierarchical structure, the information processing device can output the relationships between interchangeable parts in a visually easy-to-understand manner.

[0015] The information processing device may further have the following features. When a node is moved in the hierarchical structure, the control unit performs an update process for the correspondence of the part ID in the second correspondence information, according to the connection relationship of the node in the hierarchical structure after the move. The information processing device can update the information associated in the second correspondence information through a simple operation of the visually displayed hierarchical structure.

[0016] The information processing device may further have the following features. In the update process, the control unit adds information indicating that the pre-update information is attached to the pre-update correspondence of the part IDs, and adds the record of the post-update correspondence of the part IDs to the second correspondence information. That is, since the pre-update information is left in the second correspondence information with an indication that it is pre-update information, the information processing device can later verify whether or not there was an error in the update process.

[0017] Furthermore, according to one aspect of the present invention, information processing system It can also be understood from the perspective of information processing programs. [Effects of the Invention]

[0018] Also, according to one aspect of the present invention, parts used for replacement during repair can be easily identified.

[0019] Also, according to one aspect of the present invention, in the inquiry of replacement parts, by narrowing down the replacement parts based on the state designation information that designates the state required for the replacement parts, replacement parts that match the intention of the user can be efficiently presented.

[0020] Also, according to one aspect of the present invention, the inquiry requests for replacement parts are not immediately processed but accumulated, and batch processing is performed at the timing when a predetermined execution condition is satisfied, thereby realizing efficient utilization of system resources and load distribution.

[0021] Also, according to one aspect of the present invention, the correspondence relationship determined as an error in the past is stored as error history information, and a warning or restriction is performed when re-registering the correspondence relationship, thereby preventing the same misregistration from occurring repeatedly.

[0022] Also, according to one aspect of the present invention, based on the product identification information, the attribute information of the parts mounted on the product is automatically identified and registered in the parts management database, thereby realizing efficient data input and improved data quality.

[0023] Also, according to one aspect of the present invention, in the hierarchical structure diagram with products and parts as nodes, it is possible to switch between a first display mode with a product as a root node and a second display mode with an arbitrary part as a root node, thereby facilitating the understanding of the part relationship from various viewpoints.

[0024] Also, according to one aspect of the present invention, by storing the type information and the state information as independent data items in the part attribute information, it is possible to narrow down the replacement parts according to multi-dimensional search conditions.

[0025] Also, according to one aspect of the present invention, the product ID and parts IDBy managing this as a surrogate key automatically assigned within the system, a robust data management infrastructure that does not depend on changes in the format of external data is realized.

[0026] Furthermore, according to one aspect of the present invention, a database can be constructed using collective intelligence by aggregating registration requests for component information transmitted in a distributed manner from multiple user terminals.

[0027] Furthermore, according to one aspect of the present invention, if a correspondence registered in the association table is determined to be inappropriate, the status information is updated to a value indicating an error or invalid without deleting the record, thereby enabling data history retention and analysis.

[0028] Furthermore, according to one aspect of the present invention, the completeness or accuracy of part attribute information is verified when part is registered, and supplementary information is obtained from an external source if there are deficiencies or inconsistencies, thereby achieving automatic improvement of data quality.

[0029] Furthermore, according to one aspect of the present invention, the search results for replacement parts are displayed in a format that allows users to identify whether each replacement part is new, used, or refurbished, thereby improving the efficiency of part selection by the user.

[0030] Furthermore, according to one aspect of the present invention, a parts management server and multiple user terminals are connected via a network, and a centrally managed database is made accessible in a distributed manner, thereby realizing the provision of a SaaS-type service. [Brief explanation of the drawing]

[0031] [Figure 1] Figure 1 shows an example of a parts management system according to the embodiment. [Figure 2] Figure 2 shows an example of the hardware configuration of a parts management server according to an embodiment. [Figure 3] Figure 3 shows an example of the hardware configuration of a repair factory terminal according to the embodiment. [Figure 4]Figure 4 shows an example of a processing block for a parts management server according to an embodiment. [Figure 5] Figure 5 shows an example of a vehicle management table stored in the management database. [Figure 6] Figure 6 shows an example of a parts management table stored in the management database. [Figure 7] Figure 7(A) shows an example of an association table stored in the management database. Figure 7(B) shows an example of an error history table stored in the management database. [Figure 8] Figure 8 shows an example of a vehicle registration screen output by the vehicle registration unit in the embodiment. [Figure 9] Figure 9 shows an example of a parts registration screen output by the parts registration unit in this embodiment. [Figure 10] Figure 10 shows an example of a component correspondence screen output by the association unit in the embodiment. [Figure 11] Figure 11 illustrates a state in the component matching screen where a compatible component node image has been specified. [Figure 12] Figure 12(A) is an example of the component correspondence screen after moving the specified compatible component node image. Figure 12(B) is an example of the confirmation screen output by the association unit. [Figure 13] Figure 13 illustrates a state in the component matching screen where one compatible component node image and another compatible component node image are specified. [Figure 14] Figure 14 illustrates a state in which the nodes selected in Figure 13 are connected by line segments. [Figure 15] Figure 15 shows an example of the processing flow related to vehicle registration in the parts management server according to the embodiment. [Figure 16] Figure 16 shows an example of the processing flow related to parts registration in the parts management server according to the embodiment. [Figure 17]Figure 17 shows an example of a processing flow related to the component association process of the component management server according to the embodiment. [Figure 18] Figure 18 shows an example of a processing flow related to the component association editing process of a component management server according to an embodiment. [Figure 19] Figure 19 shows an example of the processing flow related to the response processing of the parts management server according to the embodiment. [Figure 20] Figure 20 shows an example of a processing flow related to response processing using status specification information. [Modes for carrying out the invention]

[0032] <Embodiment> The embodiments will be described below with reference to the drawings. Figure 1 shows an example of a parts management system 1 according to an embodiment. The parts management system 1, also called an information processing system, manages parts used in the repair of a vehicle 4, and when it receives an inquiry from repair shops 3A, 3B, and 3C about parts that can be used in place of parts normally used (substitute parts), it provides information on substitute parts to repair shops 3A, 3B, and 3C. The vehicle 4 is an example of a "product". Furthermore, when referred to as an ID assigned within the system, it indicates that the ID was automatically assigned by the numbering function of this parts management system.

[0033] The parts management system 1 consists of a parts management server 100 and a repair factory terminal 200. A Repair factory terminal 200 B Repair factory terminal 200 C and network N1 It is equipped with: Repair factory terminal 200 A , 200 B , 200 C When not distinguishing between them, it is also called repair factory terminal 200. Repair factory 3 A , 3 B , 3 CWhen not distinguishing between them, it is also referred to as repair shop 3. The parts management system 1 has a system configuration that allows a database (management database 105) centrally managed on the parts management server 100 to be accessed in a distributed manner from multiple repair shop terminals 200. Such a system configuration is Saas We will implement a (Software as a Service) type business model.

[0034] <Network-based distributed parts management system configuration> The repair shop terminal 200 is a user terminal installed at a repair or maintenance base (repair shop 3) for the product (vehicle 4). The repair shop terminal 200 has a transmission unit and a display unit. The transmission unit sends inquiry information regarding replacement parts for the target part to the parts management server 100. The display unit displays the results received from the parts management server 100. The repair shop terminal 200 can be any information processing terminal capable of communicating with the parts management server 100 via the network 2, such as a desktop computer, notebook computer, tablet terminal, smartphone, or dedicated terminal device. The repair shop terminal 200 may be configured to access a web application provided by the parts management server 100 via a web browser, or it may be configured with a dedicated client application installed. Furthermore, the repair shop terminal 200 is not limited to a terminal fixedly installed in the repair shop 3, but may also be a portable terminal carried by a repair worker. This allows repair workers to inquire about replacement parts and register part information in the vicinity of the vehicle 4.

[0035] The parts management server 100 has a receiving unit, an identification unit, and a transmitting unit. The receiving unit aggregates and receives inquiry information transmitted from multiple repair shop terminals 200 (multiple information processing terminals). Based on the received inquiry information, the identification unit identifies replacement parts by referring to a centrally managed database (management database 105). The transmitting unit individually transmits information on the identified replacement parts to the requesting repair shop terminals 200.

[0036] The parts management system 1 can be implemented in a cloud computing environment. The parts management server 100 can be implemented, for example, as a server instance running on a cloud service. The management database 105 can be implemented, for example, as a managed database service. This cloud-native configuration improves the system's scalability, availability, and fault tolerance. The parts management system 1 can provide parts management services to multiple repair shops 3 as a SaaS (Software as a Service) model.

[0037] The parts management server 100 is an information processing device that manages parts used to repair vehicle 4, which is identified by vehicle identification information such as model, chassis number, and vehicle identification number (VIN). The parts management server 100 manages information related to parts used to repair the vehicle, exemplified by genuine parts provided by the vehicle manufacturer that manufactured vehicle 4 and compatible parts provided by compatible parts manufacturers. The parts management server 100 receives replacement parts inquiry information from the repair shop terminal 200. The replacement parts inquiry information includes, for example, vehicle identification information for vehicle 4 and information related to parts that were planned to be used at the repair shop 3. When the parts management server 100 receives replacement parts inquiry information, it sends response information to the repair shop terminal 200 that includes information related to replacement parts that can replace the parts identified by the information related to the parts that were planned to be used included in the replacement parts inquiry information.

[0038] Repair shop terminal 200 is an information processing device used in repair shop 3, where vehicle 4 is repaired. Repair shop terminal 200 sends alternative parts inquiry information to the parts management server 100 to inquire about alternative parts that can replace the parts to be used, and receives information about alternative parts from the parts management server 100 as a response to the alternative parts inquiry information. Repair shop terminal 200A is an information processing device used in repair shop 3A. Repair shop terminal 200B is an information processing device used in repair shop 3B. Repair shop terminal 200C is an information processing device used in repair shop 3C.

[0039] <Diverse display technologies for "part status" in the output of replacement part inquiry results> The repair factory terminal 200 has a display unit that displays information about replacement parts received from the parts management server 100. When outputting the results of the replacement parts inquiry, the display unit displays whether each replacement part is new, used, or refurbished in an identifiable format.

[0040] Network N1 is a computer network that connects information processing devices in a way that enables them to communicate with each other. Network N1 may be based on wired communication or wireless communication. Network N1 is, for example, the Internet.

[0041] <Parts used to repair Vehicle 4> Vehicle 4 is manufactured using many parts, including the steering wheel, brake calipers, oil filter, timing chain, spark plugs, mirrors, and wipers. As mentioned above, each of these parts has various types, such as genuine parts and compatible parts. Each of these parts is assigned a part number that identifies it within the manufacturer that produced it. That is, genuine parts are assigned a part number that identifies them within the vehicle manufacturer, and compatible parts are assigned a part number that identifies them within the compatible part manufacturer that produced them. Since these part numbers are assigned independently by each manufacturer, there is often no correlation between the part numbers assigned to genuine parts and those assigned to compatible parts. Furthermore, even for the same part, different part numbers may be assigned depending on the year and place of manufacture. Also, even for the same part, improvements may result in different part numbers being assigned to parts before and after improvements. In this way, because each parts manufacturer assigns part numbers independently, it can be difficult to identify compatible parts for a faulty part when repairing Vehicle 4 at repair shop terminal 200. In the parts management system 1, the following configuration is adopted to facilitate the identification of such parts.

[0042] <Hardware Configuration> Figure 2 shows an example of the hardware configuration of the parts management server 100 according to the embodiment. The parts management server 100 comprises a processor 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a connection bus B1. The processor 11, the main memory unit 12, the auxiliary memory unit 13, and the communication unit 14 are interconnected by the connection bus B1.

[0043] The processor 11 is also called a microprocessor unit (MPU) or central processing unit (CPU). The processor 11 is not limited to a single processor, but may be a multiprocessor configuration. Furthermore, a single processor 11 connected by a single socket may have a multicore configuration. The processor 11 is, for example, a Digital The processor 11 may include dedicated processors such as a Signal Processor (DSP), Graphics Processing Unit (GPU), numerical processor, vector processor, and image processing processor. The processor 11 may also include integrated circuits (ICs) and other digital circuits. Furthermore, at least a portion of the processor 11 may include analog circuits. The integrated circuit is a Large Scale Integrated Circuit. This includes LSIs (large-scale integrated circuits), Application Specific Integrated Circuits (ASICs), and Programmable Logic Devices (PLDs). PLDs include, for example, Field-Programmable Gate Arrays (FPGAs). The processor 11 may also be a combination of a processor and an integrated circuit. Such combinations are called, for example, a microcontroller unit (MCU), a System-on-a-chip (SoC), a system LSI, or a chipset. In the parts management server 100, the processor 11 deploys programs stored in the auxiliary storage unit 13 to the work area of ​​the main storage unit 12 and controls peripheral devices through program execution. This allows the parts management server 100 to perform processing that conforms to a predetermined purpose. The main storage unit 12 and the auxiliary storage unit 13 are recording media readable by the processor 11.

[0044] The main memory unit 12 is exemplified as a memory unit that is directly accessed by the processor 11. The main memory unit 12 includes Random Access Memory (RAM) and Read Only Memory (ROM).

[0045] The auxiliary storage unit 13 stores various programs and data on a recording medium in a read-write manner. The auxiliary storage unit 13 is also called an external storage device. The auxiliary storage unit 13 stores the operating system (OS), various programs, various tables, etc. The OS includes a communication interface program that exchanges data with external devices connected via the communication unit 14. External devices include, for example, other information processing devices and external storage devices connected by a computer network. The auxiliary storage unit 13 may also be, for example, part of a cloud system, which is a group of computers on a network.

[0046] The auxiliary storage unit 13 is, for example, an Erasable Programmable ROM (EPROM), a Solid State Drive (SSD), a Hard Disk Drive (HDD), etc. Alternatively, the auxiliary storage unit 13 may be a Compact Disc (CD) drive, a Digital Versatile Disc (DVD) drive, etc. Furthermore, the auxiliary storage unit 13 may be provided by a Network Attached Storage (NAS) or Storage Area Network (SAN). The auxiliary storage unit 13 is just one example of a "storage unit."

[0047] The communication unit 14 is, for example, an interface with the network N1. The communication unit 14 communicates with external devices via the network N1.

[0048] Figure 3 shows an example of the hardware configuration of the repair factory terminal 200 according to the embodiment. The repair factory terminal 200 includes a processor 21, a main memory unit 22, an auxiliary memory unit 23, a communication unit 24, an input unit 25, an output unit 26, and a connection bus B2. The processor 21, main memory unit 22, auxiliary memory unit 23, communication unit 24, and connection bus B2 are the same as the processor 11, main memory unit 12, auxiliary memory unit 13, communication unit 14, and connection bus B1 of the parts management server 100, so their explanation is omitted.

[0049] The input unit 25 receives operation instructions from the user. Examples of the input unit 25 include a keyboard, pointing device, touch panel, accelerometer, and voice input device.

[0050] The output unit 26 outputs data processed by the processor 21 and data stored in the main memory unit 22. Examples of the output unit 26 include a display, speaker, printer, etc.

[0051] <Processing block> Figure 4 shows an example of a processing block of a parts management server 100 according to an embodiment. The parts management server 100 includes a vehicle registration unit 101, a parts registration unit 102, an association unit 103, a response unit 104, and a management database 105. The parts management server 100 performs processing as each of its parts, such as the vehicle registration unit 101, parts registration unit 102, association unit 103, response unit 104, and management database 105, by having the processor 11 execute a computer program that has been expanded in executable form in the main memory unit 12. The processor 11 is an example of a "control unit". The computer program executed by the processor 11 is an example of an "information processing program".

[0052] The management database 105 stores information about vehicle 4 and genuine and compatible parts used to repair vehicle 4. The management database 105 is constructed, for example, in the auxiliary storage unit 13. Figure 5 shows an example of a vehicle management table 1051 stored in the management database 105. The vehicle management table 1051 is also called the vehicle management database and is a table that manages information related to vehicle 4. The vehicle management table 1051 has the following items: "Vehicle ID", "Vehicle Identification Information", "Manufacturer", and "Vehicle Type". The "Vehicle ID" stores an ID that uniquely identifies vehicle 4 in the parts management system 1. The "Vehicle Identification Information" stores information assigned to vehicle 4. For example, the vehicle identification number (VIN) is stored in the "Vehicle Identification Information". The "Manufacturer" stores information indicating the manufacturer that manufactured vehicle 4. The "Vehicle Type" stores information indicating the vehicle type of vehicle 4. Furthermore, the management database 105 may also store information such as options installed on vehicle 4 (sunroof, speakers, suspension, cold weather specifications, etc.) and transaction history (buyer, whether it is a new or used car, etc.). The information stored in the "Vehicle Identification Information," "Manufacturer," and "Vehicle Model" fields is an example of "Product Attribute Information." The information stored in "Vehicle ID" is an example of "Product ID." The vehicle management table 1051 described above is an example of a "product management table" that stores a product ID that uniquely identifies a product, in association with the product's manufacturing number and model information. In other words, in the vehicle management table 1051, the vehicle ID is an example of a product ID, the chassis number or VIN (Vehicle Identification Number) is an example of a manufacturing number, and the vehicle type information and year information are examples of model information. A product management table can be implemented with a similar configuration when managing products other than vehicles (for example, home appliances, industrial machinery, electronic equipment, computer programs, etc.).

[0053] <An ID management system that uniquely identifies both parts and vehicles> The "Vehicle ID" in the vehicle management table 1051 stores the system ID (surrogate key) that is automatically assigned within the parts management system 1. The surrogate key is an identifier that has persistent uniqueness within the system, independent of the manufacturer's defined serial number and model information (natural key). The surrogate key is generated, for example, in the form of a UUID (Universally Unique Identifier). A UUID is a 128-bit number that is generated by combining time, node ID, random values, etc. With this surrogate key method, even if the manufacturer changes the VIN or model information, the vehicle ID does not change, eliminating the need to update the association table 1053.

[0054] <Clear distinction and management techniques for "state" and "type" as component attributes> Figure 6 shows an example of a parts management table 1052 stored in the management database 105. The parts management table 1052, also known as the parts management database, has the following items: "Part ID," "Model Number," "Manufacturer," "Type," "Status," and "Vehicle Identification Information." The "Part ID" stores an ID that uniquely identifies the part used to repair vehicle 4 in the parts management system 1. The "Model Number" stores the model number assigned to the part by the manufacturer that produced the part. The "Manufacturer" stores information indicating the manufacturer that produced the part. The "Type" stores information indicating the type of part (e.g., brake caliper, oil filter, spark plug). The "Status" stores information indicating the status of the part. Examples of part statuses include new genuine parts, used genuine parts, new compatible parts, used compatible parts, etc. In the example in Figure 6, "Genuine New" is stored in the "Condition" field for new genuine parts, and "Compatible Used" is stored for used compatible parts. "Vehicle Identification Information" is the same as "Vehicle Identification Information" in the vehicle management table 1051, and stores vehicle identification information about the vehicle in which the part is used. The information stored in each of the "Model Number," "Manufacturer," "Type," "Condition," and "Vehicle Identification Information" fields is an example of "Part Attribute Information." The parts management table 1052 is information that shows the correspondence between "part ID" and "part attribute information," and is an example of "first correspondence information."

[0055] <Technology for narrowing down and providing replacement parts based on the condition of the parts> The "Status" column in the parts management table 1052 stores status information indicating the market distribution status or quality status of the parts. The status information is expressed as a combination of the type of supplier and the quality status of the parts. The type of supplier includes genuine parts and compatible parts. The quality status includes new, used, or refurbished parts. Specifically, the "Status" column stores values ​​such as "Genuine New," "Genuine Used," "Genuine Refurbished," "Compatible New," "Compatible Used," and "Compatible Refurbished." By classifying the condition information in this detailed manner, it becomes possible to extract replacement parts that match the user's intentions (for example, "I want a used part because I want to repair it cheaply," or "I want a new part because I prioritize quality") in the replacement part selection process described later.

[0056] In the parts management table 1052, "Type" and "Status" are stored as separate data items. "Type" is type information that indicates the functional classification of the part. For example, the type information can be set to a value that indicates the functional category of the part, such as "brake caliper," "oil filter," "spark plug," "wiper blade," "battery," or "timing belt." "Condition" refers to condition information indicating the market availability or quality status of the part. The condition information must be at least one of the following: a new genuine part, a used genuine part, a new compatible part, or a used compatible part. By managing type information and condition information as separate items in this way, it becomes possible to perform multidimensional filtering, such as using search conditions like "brake caliper" (type information) and "new" (part of condition information), or "oil filter" (type information) and "compatible part" (part of condition information). The response unit 104 narrows down the alternative parts based on the combination of type information and status information.

[0057] <An ID management system that uniquely identifies both parts and vehicles> The "Part ID" in the parts management table 1052 stores the system ID (surrogate key) that is automatically assigned within the parts management system 1, similar to the "Vehicle ID" in the vehicle management table 1051. This surrogate key scheme offers three advantages: Firstly, even if a parts manufacturer changes the part number, the part ID remains unchanged, eliminating the need to update the association table 1053. Secondly, even if different manufacturers use the same part number, the part ID is unique within the system, preventing duplication. Thirdly, it provides a robust data management infrastructure that is independent of changes in the format of external data (VIN, part number).

[0058] The parts management server 100 converts the manufacturing number, model information, or part number included in the external inquiry into a product ID (vehicle ID) or part ID, and uses the converted ID to identify the correspondence. Specifically, the parts management server 100 searches the vehicle management table 1051 using the manufacturing number (VIN, etc.) included in the inquiry as the key in the "vehicle identification information" and obtains the corresponding vehicle ID. Similarly, the parts management server 100 searches the parts management table 1052 using the "part number" as the key for the part part number included in the query and obtains the corresponding part ID. Then, the parts management server 100 uses the obtained vehicle ID or part ID to identify the correspondence managed by the association table 1053.

[0059] Figure 7(A) shows an example of an association table 1053 stored in the management database 105. The association table 1053 is a table that manages the correspondence between interchangeable parts. The association table 1053 has the following items: "First Part ID", "Second Part ID", and "Error". The information stored in "First Part ID" and "Second Part ID" is the same as the "Part ID" in the parts management table 1052. "First Part ID" and "Second Part ID" store the part IDs of parts that are interchangeable with each other. "Error" stores information indicating that the information is from before the update when the correspondence between "First Part ID" and "Second Part ID" has been updated (for example, "Incorrect Registration" or "Before Update"). The association table 1053 is an example of "Second Correspondence Information" that shows the correspondence between part IDs of interchangeable parts.

[0060] <Error management techniques for alternative relationships in association tables> The "Error" column in the association table 1053 stores information indicating that the information is from before the update (for example, "Incorrect Registration" or "Before Update") when the correspondence between "First Part ID" and "Second Part ID" is updated. In this embodiment, if a correspondence registered in the association table 1053 is determined to be inappropriate, a logical deletion method is employed in which information indicating an incorrect registration is registered in the "Error" column, rather than physically deleting the record related to that correspondence. This logical deletion method preserves a history of inappropriate correspondences, making verification and analysis possible at a later date.

[0061] <Proactive misregistration prevention technology based on operation prevention using historical information> The management database 105 may store an error history table 1054 in addition to the association table 1053. This error history table 1054 is a table that stores information indicating correspondences that have been deleted from the association table 1053 in the past, or correspondences that have been judged as errors, as error history information.

[0062] Figure 7(B) shows an example of the error history table 1054. The error history table 1054 has the following items: "Error ID", "First Part ID", "Second Part ID", "Error Reason", "Registration Date and Time", and "Deletion Date and Time". The "Error ID" stores an ID that uniquely identifies the error history. The "Error Reason" stores the reason why the correspondence was deemed an error (for example, "Incompatibility", "Incorrect Part Number", "Dimensional Mismatch", etc.). The "Registration Date and Time" stores the date and time when the correspondence was registered in the association table 1053. The "Deletion Date and Time" stores the date and time when the correspondence was determined to be an error.

[0063] Returning to Figure 4, the vehicle registration unit 101 accepts the registration of vehicle 4. The vehicle registration unit 101 may, for example, accept the registration of vehicle 4 by outputting a vehicle registration screen to a display. Figure 8 is a diagram showing an example of a vehicle registration screen 1011 output by the vehicle registration unit 101 in an embodiment. The vehicle registration screen 1011 has a vehicle identification information input field 1012, a manufacturer input field 1013, a vehicle type input field 1014, a registration button 1015, and a cancel button 1016. The vehicle identification information input field 1012 is an input field that accepts the input of vehicle identification information. The manufacturer input field 1013 is an input field that accepts the input of information indicating the manufacturer. The vehicle type input field 1014 is an input field that accepts the input of information indicating the vehicle type.

[0064] When the registration button 1015 is pressed with information relating to vehicle 4 entered in the respective input fields of vehicle identification information input field 1012, manufacturer input field 1013, and vehicle type input field 1014, the vehicle registration unit 101 generates a vehicle ID that uniquely identifies vehicle 4 in the parts management system 1, and registers the generated vehicle ID and the information entered in the vehicle identification information input field 1012, manufacturer input field 1013, and vehicle type input field 1014 in the vehicle management table 1051. Specifically, the vehicle registration unit 101 registers the generated vehicle ID in the "Vehicle ID" field of the vehicle management table 1051, the information entered in the vehicle identification information input field 1012 in the "Vehicle Identification Information" field of the vehicle management table 1051, the information entered in the manufacturer input field 1013 in the "Manufacturer" field of the vehicle management table 1051, and the information entered in the vehicle type input field 1014 in the "Vehicle Type" field of the vehicle management table 1051. Furthermore, when the cancel button 1016 is pressed, the vehicle registration unit 101 deletes the information entered in the vehicle identification information input field 1012, the manufacturer input field 1013, and the vehicle type input field 1014, and cancels the registration to the vehicle management table 1051.

[0065] <Automatic ID generation and database management technology during vehicle registration> The vehicle registration unit 101 has the functions of a receiving unit, an ID generation unit, and a registration processing unit. In its function as a receiving unit, the vehicle registration unit 101 receives vehicle registration requests from an external device (for example, a repair shop terminal 200) that include vehicle identification information that can uniquely identify an individual vehicle. The vehicle identification information is the chassis number or vehicle identification number (VIN).

[0066] In its function as an ID generation unit, the vehicle registration unit 101 automatically generates a vehicle ID, which is an identifier for uniquely managing the vehicle within this system, upon receiving a vehicle registration request. The vehicle registration unit 101 generates, for example, a UUID. The UUID is a 128-bit number generated by combining the time, node ID (MAC address, etc.), random values, etc. Since the UUID is practically unique worldwide, no ID duplication occurs even in a distributed environment. The vehicle registration unit 101 may also generate sequential numbers (e.g., "V00000001", "V00000002", etc.).

[0067] In its function as a registration processing unit, the vehicle registration unit 101 creates a record associating the received vehicle identification information with the generated vehicle ID and stores it in the vehicle management table 1051. In addition to the vehicle identification information and vehicle ID, the vehicle registration unit 101 also associates the vehicle's manufacturer name and model name and stores them in the vehicle management table 1051. This automatic ID generation method realizes a robust data management infrastructure that does not depend on changes in the format of external data (VIN).

[0068] Returning to Figure 4, the parts registration unit 102 accepts the registration of parts. The parts registration unit 102 may, for example, accept the registration of parts by outputting a parts registration screen to a display. Figure 9 is a diagram showing an example of a parts registration screen 1021 output by the parts registration unit 102 in an embodiment. The parts registration screen 1021 has a model number input field 1022, a manufacturer input field 1023, a type input field 1024, a status input field 1025, a vehicle identification information input field 1026, a registration button 1027, and a cancel button 1028. The model number input field 1022 is an input field that accepts the input of the model number of the part to be registered. The manufacturer input field 1023 is an input field that accepts the input of information indicating the manufacturer of the part to be registered. The type input field 1024 is an input field that accepts the input of information indicating the type of the part to be registered. The status input field 1025 is an input field that accepts the input of information indicating the status of the part to be registered via a pull-down menu 10251. The vehicle identification information input field 1026 is an input field that accepts vehicle identification information for vehicles in which the registered parts are used.

[0069] <Part attribute information registration function via repair factory terminal (distributed input)> The parts registration unit 102 has the function of aggregating registration requests for parts information transmitted in a distributed manner from multiple repair shop terminals 200 and constructing a parts management table 1052. This function realizes database construction using collective intelligence.

[0070] When the registration button 1027 is pressed after information relating to the part to be registered has been entered in the respective input fields of the part number input field 1022, manufacturer input field 1023, type input field 1024, status input field 1025, and vehicle identification information input field 1026, the parts registration unit 102 generates an ID that uniquely identifies the part to be registered in the parts management system 1, and registers the generated ID and the information entered in the part number input field 1022, manufacturer input field 1023, type input field 1024, status input field 1025, and vehicle identification information input field 1026 in the parts management table 1052. In other words, the parts registration unit 102 registers the generated ID in the "Part ID" field of the parts management table 1052, the information entered in the model number input field 1022 in the "Model Number" field of the parts management table 1052, the information entered in the manufacturer input field 1023 in the "Manufacturer" field of the parts management table 1052, the information entered in the type input field 1024 in the "Type" field of the parts management table 1052, the information entered in the status input field 1025 in the "Status" field of the parts management table 1052, and the information entered in the vehicle identification information input field 1026 in the "Vehicle Identification Information" field of the parts management table 1052. Furthermore, when the cancel button 1028 is pressed, the parts registration unit 102 deletes the information entered in the respective input fields of model number input field 1022, manufacturer input field 1023, type input field 1024, status input field 1025, and vehicle identification information input field 1026, and cancels the registration to the parts management table 1052.

[0071] <Technology for automatically registering parts based on specific vehicle information> The parts registration unit 102 may have the function of automatically identifying the attribute information of parts based on vehicle identification information and registering it in the parts management table 1052. In this case, the parts registration unit 102 has the functions of an acquisition unit 120, a parts identification unit 121, and a registration processing unit 122.

[0072] In its function as an acquisition unit 120, the parts registration unit 102 acquires product identification information from an external device that uniquely identifies an individual product (vehicle 4). In the case of vehicle 4, the product identification information includes the chassis number or vehicle identification number (VIN). The VIN includes information such as the country of manufacture, manufacturer, vehicle type, engine type, year of manufacture, manufacturing plant, and serial number.

[0073] In its function as a parts identification unit 121, the parts registration unit 102 identifies the attribute information of the parts installed in the product (vehicle 4) identified by the acquired product identification information. The parts registration unit 102 identifies the attribute information of the parts by, for example, the following method. As a first method, the parts registration unit 102 accesses the parts configuration database (BOM: Bill of Materials) managed by the vehicle manufacturer and obtains a parts list corresponding to the VIN. As a second method, the parts registration unit 102 refers to the correspondence table (parts configuration master) between vehicle model and parts configuration stored in the management database 105 and obtains a parts list corresponding to the vehicle model identified from the VIN. As a third method, the parts registration unit 102 accesses an external parts information provision service (API) and obtains a parts list corresponding to the VIN.

[0074] In its function as a registration processing unit 122, the parts registration unit 102 automatically registers product identification information and attribute information of the identified parts in the parts management table 1052. Specifically, the parts registration unit 102 associates product identification information with at least one of the attribute information of the part, such as the part number, manufacturer, type, or status, and stores it in the parts management table 1052. The parts registration unit 102 also automatically generates a parts ID that uniquely identifies the part in the parts management system 1 and stores the parts ID in the "Parts ID" field of the parts management table 1052. This automatic registration function reduces the effort required for users to manually input parts information, resulting in improved data input efficiency and data quality.

[0075] <Part attribute information registration function via repair factory terminal (distributed input)> The parts registration unit 102 functions as a communication unit capable of communicating with multiple repair shop terminals 200. The parts registration unit 102 receives registration requests from the repair shop terminals 200 for information regarding parts used for the repair or maintenance of a product (vehicle 4). The registration request is information entered via the parts registration screen 1021 (Figure 9) displayed on the repair shop terminal 200. The registration request includes attribute information such as the manufacturer, type, and condition of the part, part number information to identify the part, and product identification information (vehicle identification information) to identify the product in which the part is used.

[0076] Based on the registration request, the parts registration unit 102 associates part number information that identifies the part, part attribute information, and product identification information that identifies the product in which the part is used, and stores them in the parts management table 1052. The parts registration unit 102 aggregates registration requests sent in a distributed manner from multiple repair shop terminals 200, and builds or updates the correspondence between parts and products, or the substitutability relationships between parts, in the parts management table 1052.

[0077] The parts registration unit 102 can increase the reliability of the registration information for a part if it receives registration requests for the same part from multiple repair shop terminals 200. For example, if the parts registration unit 102 receives registration requests from multiple repair shop terminals 200 that include the same part number and the same vehicle identification information, it may increase the score indicating the reliability of the correspondence between the part and the vehicle. This distributed input method allows master data to be collected and stored in a distributed manner, triggered by actual work (repair input) at the edge (repair factory 3), rather than having a central administrator input all the parts information.

[0078] <Technology for multiple registration and association of part attribute information and vehicle identification information during part registration> The parts registration unit 102 registers both the attribute information of the parts and the vehicle identification information in the parts management table 1052 when parts are registered. This function efficiently manages the many-to-many (N-to-N) relationship between "parts" and "vehicles (products)".

[0079] The parts registration unit 102 has the functions of an acquisition unit, an ID generation unit, and a registration unit. In its function as an acquisition unit, the parts registration unit 102 acquires a parts registration request from an external device (repair factory terminal 200, etc.) which includes parts attribute information indicating the attributes of the parts and vehicle identification information that identifies the target vehicle on which the parts will be installed. The parts attribute information includes the part number, manufacturer, type, and status of the parts. The vehicle identification information includes VIN, model information, etc. In its function as an ID generation unit, the parts registration unit 102 generates a parts ID that uniquely identifies the parts within this system based on the parts registration request. In its function as a registration unit, the parts registration unit 102 registers both the parts attribute information and the vehicle identification information in the parts management table 1052, associating them with the parts ID.

[0080] The parts registration unit 102 stores all of the following information associated with a single parts ID: part number, manufacturer, type, status, and vehicle identification information. The parts management table 1052 may also have a "Vehicle ID" field. The "Vehicle ID" field stores the vehicle ID from the vehicle management table 1051 that corresponds to the "Vehicle Identification Information" in the parts management table 1052. This allows for both parts referencing vehicles and vehicles referencing parts, enabling efficient management of many-to-many relationships between parts and products.

[0081] <Verification and supplementation technologies for attribute information during parts registration> The parts registration unit 102 may have a function to verify the completeness or accuracy of parts attribute information during parts registration and to acquire supplementary information from external sources if there are deficiencies or inconsistencies. This function realizes a self-correcting registration process that incorporates data cleansing and data enrichment into the registration flow.

[0082] The parts registration unit 102 has the functions of a verification unit and an information acquisition unit. In its function as a verification unit, the parts registration unit 102 verifies the completeness or accuracy of the parts attribute information included in the registration request. For example, the parts registration unit 102 performs the following verifications: First, the parts registration unit 102 determines whether the parts attribute information includes information indicating the type or state of the part. Second, the parts registration unit 102 determines whether the format of the part number information is correct. Third, the parts registration unit 102 determines whether the manufacturer name is included in the known manufacturer list. Fourth, the parts registration unit 102 determines whether the combination of type and state is logically consistent.

[0083] In its function as an information acquisition unit, the parts registration unit 102, if it determines as a result of verification that there is a shortage or inconsistency in the parts attribute information, accesses an external information source and acquires supplementary information corresponding to the part number information. External information sources include, for example, a server managed by a parts manufacturer (manufacturer management server), a parts catalog database, and an industry-standard parts information provision service (API). If information indicating the type or status of the part is missing, the parts registration unit 102 acquires information indicating the type or status of the part from an external information source to supplement it.

[0084] The parts registration unit 102 reflects supplementary information in the received parts attribute information and registers the information of the part in the parts management table 1052. The parts registration unit 102 can also support supplementation using image data. For example, if image data of a part is included in the registration request, the parts registration unit 102 may use image recognition technology to estimate the type of part. Alternatively, the parts registration unit 102 may identify similar parts already registered in the parts management table 1052 through similar image search and use the attribute information of those similar parts as supplementary information. Through such verification and supplementation functions, incomplete user input is compensated for, and the data quality of the parts management table 1052 is improved.

[0085] Returning to Figure 4, the association unit 103 associates mutually interchangeable parts with the registered parts. The association unit 103, for example, accesses a server managed by the compatible parts manufacturer to obtain correspondence information indicating which compatible parts are interchangeable with which genuine parts. The correspondence information includes, for example, information indicating the manufacturer that produced the compatible parts, the part number assigned to the compatible parts, information indicating the manufacturer that produced the genuine parts, and the part number assigned to the genuine parts. Based on the correspondence information, the association unit 103 obtains the part IDs of the mutually interchangeable genuine parts and compatible parts, stores one part ID in the "first part ID" of the association table 1053, and stores the other part ID in the "second part ID" of the association table 1053. Here, there may be multiple compatible parts that can substitute for one genuine part. Also, there may be other genuine parts that can substitute for one genuine part. Also, there may be other compatible parts that can substitute for a certain compatible part.

[0086] Furthermore, the association unit 103 may output a parts correspondence screen to the display, for example, which visually shows the correspondence between the associated parts. Figure 10 is a diagram showing an example of a parts correspondence screen 1031 output by the association unit 103 in an embodiment. The parts correspondence screen 1031 may, for example, as shown in (A) in the upper part of Figure 10, use a vehicle node image 1032 representing vehicle 4 as the root, and arrange genuine parts node images 1033 representing genuine parts applicable to repairing vehicle 4 shown in vehicle node image 1032 and compatible parts node images 1034 representing compatible parts applicable to repairing vehicle 4 shown in vehicle node image 1032 as nodes to show the correspondence between parts. Furthermore, the parts correspondence screen 1031 may also show the correspondence of parts used to repair vehicle 4 by a hierarchical structure in which one of the compatible parts node images 1034, compatible parts node image 10341, is used as the root, and the vehicle node image 1032, genuine parts node image 1033, and compatible parts node image 1034 are arranged as nodes, for example, as shown in (B) in the lower part of Figure 10. The parts correspondence screen 1031 may use any of the vehicle node image 1032, genuine parts node image 1033, and compatible parts node image 1034 as the root. In the hierarchical structure diagrams of the hierarchical structure exemplified in (A) in the upper part of Figure 10 and (B) in the lower part of Figure 10, each node is connected by line segments starting from the root, according to the correspondence stored in the association table 1053. The root is located at the top of the hierarchical structure. The root serves as the starting point for searching (exploring) nodes in the hierarchical structure and is the basis for showing the correspondence between the root and each node. In this embodiment, the parts correspondence screen 1031 has a hierarchical structure with the vehicle node image 1032 as the root, as shown in (A) of the upper part of Figure 10. In the hierarchical structure of the parts correspondence screen 1031, for example, an image representing a part stored in the "first part ID" of the association table 1053 is placed as a parent node, and an image representing a part stored in the "second part ID" is placed as a child node. In such a hierarchical structure, the genuine part node image 1033 may be placed as a child node of the compatible part node image 1034, or the compatible part node image 1034 may be placed as a child node of the genuine part node image 1033.On the parts correspondence screen 1031, interchangeable parts are visually represented by the connection relationships between the genuine part node image 1033 and the compatible part node image 1034.

[0087] The association unit 103 functions as a display control unit 124 and can switch between a first display mode and a second display mode. In the first display mode, the association unit 103 places the node corresponding to the product (vehicle node image 1032) as the highest-level root node. The first display mode is the display form exemplified in the upper part (A) of Figure 10. In the second display mode, the association unit 103 places the node corresponding to any part selected by the user as the highest-level root node. The association unit 103 places other parts related to that part as lower-level nodes. The association unit 103 also places the product (vehicle 4) on which the part is mounted as a lower-level node. The second display mode is the display form exemplified in the lower part (B) of Figure 10.

[0088] The parts display screen 1031 may have a display mode switching button 1035. By pressing the display mode switching button 1035, the user can switch between the first display mode and the second display mode. In the first display mode, the user can switch to the second display mode, with the part node as the root node, by double-clicking any part node (genuine part node image 1033 or compatible part node image 1034). By switching display modes in this way, the user can see at a glance which genuine part a compatible part replaces and which vehicle it is compatible with. The second display mode is useful for sales activities by compatible parts manufacturers (suggesting which vehicle models are compatible) and for parts selection at repair shops 3 (comparing alternative candidates for a particular part).

[0089] In the parts correspondence screen 1031, the vehicle node image 1032 is represented as a rhombus, the genuine parts node image 1033 as a circle, and the compatible parts node image 1034 as a rectangle. However, the vehicle node image 1032, genuine parts node image 1033, and compatible parts node image 1034 may, for example, be photographs of the corresponding vehicles or parts. In addition, the names of the vehicle node image 1032, genuine parts node image 1033, and compatible parts node image 1034 may be attached to their vicinity. By performing such processing, users of the parts management system 1 can easily understand which node corresponds to which part or vehicle.

[0090] Here, the association unit 103 may accept modifications to the association of parts by moving nodes on the part correspondence screen 1031. Figure 11 is an example of a state in which a compatible part node image 1034 is specified on the part correspondence screen 1031. Such a specification can be made, for example, by moving the mouse cursor 800 with a pointing device such as a mouse over the desired compatible part node image 1034 (for example, compatible part node image 1034A, which is one of the child nodes of compatible part node image 1034C). Then, the specified compatible part node image 1034A is moved to the position of a child node of compatible part node image 1034B.

[0091] Figure 12(A) is an example of the component correspondence screen 1031 after moving the specified compatible component node image 1034A. It can be seen that, due to the node movement, compatible component node image 1034A has become a child node of compatible component node image 1034B.

[0092] When the compatible part node image 1034A is moved in this manner, the association unit 103 updates the association table 1053. Specifically, the association unit 103 registers information indicating an incorrect registration in the "Error" field of the record in the association table 1053 where the part ID of compatible part node image 1034C is stored as the "First Part ID" and the part ID of compatible part node image 1034A is stored as the "Second Part ID". Then, the association unit 103 adds a record to the association table 1053 where the part ID of compatible part node image 1034B is stored as the "First Part ID" and the part ID of compatible part node image 1034A is stored as the "Second Part ID". Furthermore, when the association unit 103 outputs the part correspondence screen 1031, it excludes the records in the association table 1053 where an incorrect registration has been registered in the "Error" field, visually showing the correspondence between parts.

[0093] <Error management techniques for alternative relationships in association tables> The association unit 103 has a management function. In its management function, if the association unit 103 determines that a particular correspondence registered in the association table 1053 is inappropriate, it updates or sets the "Error" of the record related to the correspondence to a value indicating error or invalid, without deleting the record. The triggers for determining that a correspondence is inappropriate include, for example, the following cases: Firstly, when a user moves a node on the parts correspondence screen 1031. Secondly, when the repair shop 3 reports that a certain combination of parts is actually irreplaceable. Thirdly, when the parts manufacturer notifies the user that the compatibility information for a certain part is incorrect.

[0094] When registering a new alternative relationship, the association unit 103 refers to the association table 1053 and issues a warning or restriction to the registration if the "error" of the relationship to be registered is recorded as a value indicating an error or invalidity. This logical deletion method offers the following advantages: Firstly, it is easy to restore relationships that have been mistakenly deleted. Secondly, it allows the use of structured data, including not only "what was correct" but also "what was wrong," as training data when adding an AI-based automatic matching accuracy improvement function in the future.

[0095] Furthermore, the association unit 103 may accept modifications to the association of substitute parts by adding or deleting line segments between nodes in the part matching screen 1031. Figure 13 illustrates a state in the part matching screen 1031 where a genuine part node image 1033 and another compatible part node image 1034 are specified. In Figure 13, the compatible part node image 1034D and the genuine part node image 1033A are selected, and the selected nodes are represented by dotted lines.

[0096] Figure 14 illustrates a state in which the nodes selected in Figure 13 are connected by line segments. In Figure 14, a line segment L1 is set connecting the compatible part node image 1034D and the genuine part node image 1033A. When the line segment L1 is set in this way, the association unit 103 adds a record to the association table 1053 that stores the part ID of the genuine part node image 1033A as the "first part ID" and the part ID of the compatible part node image 1034D as the "second part ID". Note that, as with the compatible part node image 1034D in Figure 14, there may be nodes with multiple parent nodes in the part correspondence screen 1031.

[0097] Returning to Figure 4, when the response unit 104 receives replacement part inquiry information from the repair shop terminal 200, it sends response information including information about the replacement part to the repair shop terminal 200. The response unit 104, for example, refers to the parts management table 1052 based on the vehicle identification information and information about the parts to be used included in the replacement part inquiry information, and obtains the part ID of the parts to be used. Then, the response unit 104 refers to the association table 1053 and extracts the record in which the obtained part ID is stored as "first part ID" or "second part ID". The response unit 104 obtains the part ID (also called the replacement part ID) associated with the part ID of the parts to be used in the extracted record. The response unit 104 obtains the information associated with the replacement part ID in the parts management table 1052 (for example, model number, manufacturer, type, vehicle identification information), and sends the obtained information to the repair shop terminal 200 as information about the replacement part.

[0098] <Technology for narrowing down and providing replacement parts based on the condition of the parts> The response unit 104, if the replacement part inquiry information includes status specification information, executes a process to narrow down the candidate replacement parts based on the status specification information. Status specification information is information that specifies the required state of the replacement part. For example, the status specification information can be set to values ​​such as "new only," "used only," "refurbished only," "new or refurbished," or "all, including used."

[0099] The response unit 104 has the functions of a specification unit, an extraction unit, and an output unit. In its function as a specification unit, the response unit 104 refers to the association table 1053 based on the part ID corresponding to the target part to identify candidate replacement parts that can replace the part. In its function as an extraction unit, the response unit 104 refers to the part management table 1052 from among the identified candidate replacement parts to extract replacement parts that match the status indicated in the status specification information. Specifically, when "used" is specified as the status information, the response unit 104 extracts replacement parts from the parts management table 1052 whose "status" is "genuine used," "compatible used," "genuine refurbished," or "compatible refurbished." In its function as an output unit, the response unit 104 outputs information about the extracted replacement parts to the repair factory terminal 200.

[0100] <Multi-stage logic technology for specific processing when searching for alternative parts> The answer unit 104 performs a multi-hop lookup based on a normalized database structure. A multi-hop lookup is a process that sequentially searches multiple tables, including converting foreign keys (part numbers) to internal keys (part IDs), identifying correspondences between part IDs in a linked table (association table 1053), and converting internal keys (part IDs) to external attributes (part numbers, etc.).

[0101] Specifically, the response unit 104 performs the following processes. As a first identification process, the response unit 104 searches the parts management table 1052 (first table) using the attribute information of the target part (model number, manufacturer, etc.) as a key to identify the first part ID corresponding to the target part. As a second identification process, the response unit 104 searches the association table 1053 (second table) using the identified first part ID as a key to obtain the second part ID corresponding to a substitute part that can replace the target part. As an output process, the response unit 104 searches the parts management table 1052 using the obtained second part ID as a key to obtain the attribute information of the substitute part and output it to the repair factory terminal 200.

[0102] For example, the part number "X-12345" included in the query request is used as a search key in the parts management table 1052, and part ID "P001" is retrieved. Part ID "P001" is used as a search key in the association table 1053, and alternative part IDs "P002" and "P003" are retrieved. Alternative part IDs "P002" and "P003" are again used as search keys in the parts management table 1052, and the part numbers of the alternative parts "Y-67890" and "Z-11111" are retrieved. In this way, in a normalized database structure, alternative parts can be identified by sequentially searching multiple tables.

[0103] <Diverse display technologies for "part status" in the output of replacement part inquiry results> The response unit 104 has the function of an output unit. In its function as an output unit, the response unit 104 obtains status information corresponding to the part ID of the identified replacement part from the parts management table 1052. The response unit 104 generates display data that identifies whether the replacement part is new, used, or refurbished, along with the name or ID of the replacement part, and outputs it to the repair factory terminal 200.

[0104] The output unit 26 of the repair factory terminal 200 displays a list of replacement parts screen based on the display data received from the response unit 104. The list of replacement parts screen has a list of replacement parts that displays the part name, model number, manufacturer, condition, and reference price of multiple replacement parts in parallel. In the "Condition" column, values ​​such as "New," "Used," and "Refurbished" are displayed as icons or labels. For example, "New" may be displayed as a green icon, "Used" as a yellow icon, and "Refurbished" as a blue icon. By displaying the condition information in a visually identifiable format in this way, users can efficiently select replacement parts.

[0105] When multiple alternative parts are identified, the response unit 104 displays the status information for each alternative part in a parallel list, generating screen data to support the user in selecting a part. In addition to the status information, the response unit 104 may also display information such as reference price, inventory status, and delivery date. By referring to the alternative parts list screen, users can select parts according to their purpose, such as choosing used parts if cost is a priority, new parts if quality is a priority, or refurbished parts if reducing environmental impact is a priority.

[0106] <Processing Flow> Figure 15 shows an example of the processing flow related to vehicle registration in the parts management server 100 according to this embodiment. The following description will refer to Figure 15 to explain an example of the processing flow related to vehicle registration in the parts management server 100.

[0107] In step S1, the vehicle registration unit 101 outputs a vehicle registration screen 1011. In step S2, the vehicle registration unit 101 accepts input of information related to the vehicle to be registered for each input field (vehicle identification information input field 1012, manufacturer input field 1013, and vehicle type input field 1014) of the vehicle registration screen 1011 output in step S1.

[0108] In step S3, the vehicle registration unit 101 determines whether or not the registration button 1015 has been pressed. If the registration button 1015 has been pressed (YES in step S3), the process proceeds to step S4. If the registration button 1015 has not been pressed (NO in step S3), the process in step S2 is repeated.

[0109] In step S4, the vehicle registration unit 101 generates a vehicle ID that uniquely identifies the vehicle to be registered, based on the information received in step S2, within the parts management system 1. In step S5, the vehicle registration unit 101 associates the information entered in each input field of the vehicle registration screen 1011 in step S2 with the vehicle ID generated in step S4 and registers it in the vehicle management table 1051.

[0110] Figure 16 is a diagram showing an example of the processing flow related to parts registration in the parts management server 100 according to the embodiment. Hereinafter, an example of the processing flow related to parts registration in the parts management server 100 will be described with reference to Figure 16.

[0111] In step S11, the parts registration unit 102 outputs the parts registration screen 1021. In step S12, the parts registration unit 102 accepts input of information related to the parts to be registered for each input field (model number input field 1022, manufacturer input field 1023, type input field 1024, status input field 1025, and vehicle identification information input field 1026) of the parts registration screen 1021 output in step S11.

[0112] In step S13, the parts registration unit 102 determines whether or not the registration button 1027 has been pressed. If the registration button 1027 has been pressed (YES in step S13), the process proceeds to step S14. If the registration button 1027 has not been pressed (NO in step S13), the process in step S12 is repeated.

[0113] In step S14, the parts registration unit 102 generates a parts ID that uniquely identifies the information of the parts to be registered, which was received as input in step S12, in the parts management system 1. In step S15, the parts registration unit 102 associates the information entered in each input field of the parts registration screen 1021 in step S12 with the parts ID generated in step S14 and registers it in the parts management table 1052.

[0114] Figure 17 is a diagram showing an example of the processing flow related to the component association process of the component management server 100 according to the embodiment. Hereinafter, an example of the processing flow related to the component association process of the component management server 100 will be described with reference to Figure 17.

[0115] In step S31, the association unit 103 accesses a server managed by the compatible parts manufacturer to obtain correspondence information indicating which compatible parts can substitute for which genuine parts. In step S32, based on the correspondence information obtained in step S31, the association unit 103 obtains the part IDs of the mutually interchangeable genuine parts and compatible parts, stores one part ID in the "first part ID" column of the association table 1053, and stores the other part ID in the "second part ID" column of the association table 1053.

[0116] Figure 18 is a diagram showing an example of the processing flow related to the component association editing process of the component management server 100 according to the embodiment. Hereinafter, an example of the processing flow related to the component association editing process of the component management server 100 will be described with reference to Figure 18.

[0117] In step S41, the association unit 103 outputs the component correspondence screen 1031. In step S42, the association unit 103 accepts modification operations (moving nodes, adding / deleting line segments connecting nodes) for step S1031. In step S43, the association unit 103 updates the association table 1053 according to the modification operations accepted in step S42.

[0118] Figure 19 is a diagram showing an example of the processing flow related to the response processing of the parts management server 100 according to the embodiment. Hereinafter, an example of the processing flow related to the response processing of the parts management server 100 will be described with reference to Figure 19.

[0119] In step S51, the response unit 104 receives replacement parts inquiry information from the repair factory terminal 200. In step S52, the response unit 104 refers to the parts management table 1052 based on the replacement parts inquiry information received in step S51 and obtains the part ID of the part to be used.

[0120] In step S53, the response unit 104 refers to the association table 1053 based on the part ID of the part to be used obtained in step S52 to identify the alternative part ID. In step S54, the response unit 104 obtains information related to the alternative part associated with the alternative part ID identified in step S53 from the parts management table 1052.

[0121] In step S55, the response unit 104 transmits the information regarding the replacement part obtained in step S54 to the repair factory terminal 200.

[0122] <Technology for narrowing down and providing replacement parts based on the condition of the parts> Figure 20 shows an example of a processing flow related to response processing using status specification information. In Figure 20, the response unit 104 receives alternative part inquiry information (S2001). This alternative part inquiry information includes information about the part to be used and status specification information. Next, the response unit 104 refers to the parts management table 1052 based on the alternative part inquiry information to obtain the part ID of the part to be used (S2002). The response unit 104 also refers to the association table 1053 based on the obtained part ID to identify candidate alternative part IDs (S2003).

[0123] Then, the response unit 104 refers to the "status" of the parts management table 1052 for each of the identified candidate alternative parts IDs (S2004). It extracts alternative parts IDs whose "status" matches the status specification information (S2005). Next, the response unit 104 obtains the parts attribute information corresponding to the extracted alternative parts IDs (S2006). The response unit 104 then transmits the acquired information regarding the replacement part to the repair factory terminal 200 (S2007).

[0124] <Effects of the Embodiment> According to this embodiment, a unique part ID is assigned to parts that have been assigned part numbers independently by the vehicle manufacturer or compatible parts manufacturer in the parts management system 1. Then, the part IDs of mutually interchangeable parts are associated with each other in the association table 1053. Therefore, according to this embodiment, interchangeable parts can be easily identified.

[0125] Here, the registration of mutually interchangeable parts in the association table 1053 is performed, for example, by obtaining correspondence information from a server managed by the compatible parts manufacturer that indicates which compatible parts can be substituted for which genuine parts, and based on the obtained correspondence information. According to this embodiment, by registering information in the association table 1053 based on information provided by the compatible parts manufacturer, the reliability of the information registered in the association table 1053 can be increased.

[0126] According to this embodiment, the hierarchical structure of the component correspondence screen 1031 visually represents the relationships between interchangeable components. Therefore, according to this embodiment, it is possible to easily identify which component can be substituted for a given component.

[0127] In this embodiment, the association of replaceable parts is updated in the association table 1053 by accepting modifications to the association of replaceable parts through the movement of nodes and the addition or deletion of line segments connecting nodes in the hierarchical structure of the parts correspondence screen 1031. Therefore, according to this embodiment, the association of replaceable parts can be updated with simple operations.

[0128] In this embodiment, when the association table 1053 is updated, information indicating an incorrect registration is registered in the "Error" field of the record in the association table 1053 before the update, and the updated correspondence is added to the association table 1053 as a new record. According to this embodiment, since the record before the update is not deleted from the association table 1053, it is possible to verify later whether there are any errors in updating the correspondence.

[0129] According to the hierarchical structure of the parts correspondence screen 1031 of this embodiment, for example, compatible parts that can replace various vehicle types and various genuine parts can be visually displayed. Therefore, this embodiment can also be used for sales activities of compatible parts.

[0130] (Effect of filtering based on status information) In the above embodiment, the following effects can be obtained by configuring the response unit 104 to narrow down alternative parts based on the status specification information. First, if the user intends to "want a used part because they want to repair it cheaply," specifying "used" as the status specification information will extract only used parts, and alternative parts that match the user's intention will be efficiently presented. Second, if the user intends to "want a new part because they prioritize quality," specifying "new" as the status specification information will extract only new parts. Third, by narrowing down the results based on the status specification information, the number of inquiry results is reduced, and the burden on the user in the selection process is lessened.

[0131] (Effects of asynchronous processing) In the above embodiment, the following effects can be obtained by configuring the response unit 104 to accumulate inquiry requests and process them all at once when predetermined execution conditions are met. First, system resources can be used efficiently for large volumes of inquiries where real-time processing is not essential (for example, ordering inventory replenishment at night). Second, by concentrating processing during times when the system load is low (for example, late at night), system responsiveness during the day is improved. Third, the system has high compatibility with serverless architectures in cloud computing environments, improving system scalability and availability.

[0132] (Effect of suppressing incorrect registrations based on error history information) In the above embodiment, the following effects can be obtained by configuring the association unit 103 to issue warnings or restrictions by referring to error history information. Firstly, the re-registration of correspondences that have been previously flagged as errors for reasons such as "incompatibility," "incorrect model number," or "mismatched dimensions" is suppressed, preventing a deterioration in data quality. Secondly, the confirmation screen 1036 presents the user with the reason for the error and the date and time of past registration, allowing the user to decide whether or not to register based on sufficient information. Thirdly, the accumulation of error history information provides basic data for analyzing error trends and data cleansing.

[0133] (Effects of automatic registration based on product identification information) In the above embodiment, the configuration in which the parts registration unit 102 automatically identifies and registers parts attribute information based on product identification information (VIN, etc.) provides the following benefits: Firstly, the effort required for users to manually input parts information is significantly reduced. Secondly, since registration is performed based on accurate parts configuration information (BOM) managed by the manufacturer, input errors are prevented and data quality is improved. Thirdly, when a new vehicle is registered, the standard parts configuration of that vehicle is automatically registered in the database, thus improving the efficiency of initial data construction.

[0134] (Effects of changing the route in the hierarchical structure) In the above embodiment, the following effects can be obtained if the association unit 103 is configured to switch between a first display mode and a second display mode. Firstly, the first display mode (product as the root node) makes it easy to understand relationships from the perspective of "all parts that fit a particular vehicle." Secondly, the second display mode (part as the root node) makes it easy to understand relationships from the perspective of "which genuine part a particular compatible part replaces and which vehicle it fits." Thirdly, it is useful for sales activities by compatible parts manufacturers (proposing which vehicle models a part fits) and for parts selection at repair shops (comparing potential replacements for a particular part).

[0135] (Effects of separating management of type information and condition information) In the above embodiment, the configuration in which type information and condition information are managed as independent data items as part attribute information provides the following effects. First, it becomes possible to narrow down the search using multidimensional search conditions such as "brake caliper" (type) and "new" (part of the condition). Second, because type information and condition information are independent, changes to the database structure can be minimized even if a type of condition (e.g., "certified refurbished product") is added in the future. Third, statistical analysis (e.g., understanding the volume of used goods in circulation for each type) becomes easier.

[0136] (The effectiveness of ID management using surrogate keys) In the above embodiment, product ID and parts ID A configuration that manages this as a surrogate key (UUID, etc.) automatically generated within the system yields the following benefits. 。 Firstly, even if a parts manufacturer changes the part number, the part ID remains unchanged, so there is no need to update the association table 1053. 。 Secondly, even if different manufacturers use the same part number, ID Since it is unique within the system, no duplication occurs. 。 Thirdly, external data ( VIN This enables a robust data management platform that is independent of changes in the format of part numbers.

[0137] (Effects of database construction using distributed input) In the above embodiment, the configuration that receives registration requests for parts information in a distributed manner from multiple repair shop terminals 200 provides the following advantages. First, instead of a central administrator inputting all parts information, master data is collected in a distributed manner triggered by actual work (repair input) at the edge (repair shop 3). Second, when the same part-to-vehicle correspondence is registered from multiple repair shops, the reliability of that correspondence increases. Third, practical parts compatibility data based on the actual work of the repair shops is accumulated.

[0138] (Effects of error management through logical deletion) In the above embodiment, if a correspondence registered in the association table 1053 is determined to be inappropriate, the configuration that updates the status information without physically deleting the record provides the following effects: Firstly, it is easy to restore a correspondence that has been mistakenly deleted. Secondly, a history of inappropriate correspondences is maintained, enabling verification and analysis at a later date. Thirdly, when adding an AI-based automatic matching accuracy improvement function in the future, not only "what was correct" but also "what was wrong" can be used as structured data for learning.

[0139] (Effects of verifying and supplementing attribute information) In the above embodiment, the following effects can be obtained by configuring the part registration unit 102 to verify the completeness or accuracy of the part attribute information and to acquire supplementary information from an external information source. First, incomplete part attribute information entered by the user is automatically supplemented, improving data quality. Second, even if only part number information is entered, information such as type, status, and manufacturer is acquired from an external information source and registered as a complete record. Third, input errors (for example, non-existent manufacturer names) are detected, and corrections are prompted before registration.

[0140] (Effect of visual display of status information) In the above embodiment, the configuration in which the response unit 104 displays the status information of replacement parts in an identifiable format provides the following advantages. First, on the replacement parts list screen, it is immediately clear whether each part is new, used, or refurbished. Second, users can efficiently select parts according to their purpose, such as selecting used parts when cost is a priority, new parts when quality is a priority, or refurbished parts when reducing environmental impact. Third, since the status information is visually displayed with icons or labels, the cognitive burden of the information is reduced.

[0141] (Effects of a distributed system configuration) In the above embodiment, the following effects can be obtained by a configuration in which the parts management server 100 and multiple repair shop terminals 200 are connected via network N1. First, the database (management database 105) centrally managed in the parts management server 100 can be accessed in a distributed manner from multiple repair shops 3. Second, by implementing it in a cloud computing environment, the system's scalability, availability, and fault tolerance are improved. Third, the parts management service can be provided as a SaaS (Software as a Service).

[0142] <Variation> In the embodiments described above, correspondence information indicating which genuine parts a compatible part can substitute for is obtained from a server managed by the compatible parts manufacturer. However, the correspondence information indicating which genuine parts a compatible part can substitute for is not limited to being obtained from a server managed by the compatible parts manufacturer. For example, repair history information of repairs performed on vehicle 4 at repair shop 3 may be stored at repair shop terminal 200. Repair history information includes, for example, the correspondence between information on parts removed from vehicle 4 for replacement and information on parts that were replaced and incorporated into vehicle 4. The parts management system 1 may obtain repair history information from repair shop terminal 200 and obtain correspondence information indicating which genuine parts a compatible part can substitute for from the correspondence relationships included in the obtained repair history information. Since such repair history information is information with actual replacement records, the reliability of registration in association table 1053 can be increased.

[0143] Furthermore, the replacement parts inquiry information may include information indicating the condition of the parts, such as a new genuine part or a used compatible part. In such cases, the response unit 104 only needs to send information related to replacement parts that matches the condition included in the replacement parts inquiry information to the repair shop terminal 200. In this embodiment, the response unit 104 sent information related to replacement parts in response to the receipt of the replacement parts inquiry information. However, the response unit 104 does not necessarily need to be triggered by the receipt of the replacement parts inquiry information. The response unit 104 may send information related to replacement parts in batch processing, for example, to replacement parts inquiry information stored in the auxiliary storage unit 13. For example, replacement parts inquiry information sent from the repair shop terminal 200 may be stored in the auxiliary storage unit 13, and the process of identifying replacement part IDs based on the replacement parts inquiry information stored in the auxiliary storage unit 13 may be performed at a predetermined time, such as at night.

[0144] <Asynchronous processing (batch processing) technology for providing alternative parts information> Furthermore, the provision of information regarding alternative parts by the response unit 104 may be performed by asynchronous processing (batch processing). This asynchronous processing is a method in which, instead of immediately executing processing upon receiving alternative part inquiry information, inquiry requests are temporarily stored and processed all at once at a predetermined timing.

[0145] When asynchronous processing is performed, the parts management server 100 includes a storage control unit 111, an inquiry queue 112, a batch processing unit 113, and a result provision unit 114. The storage control unit 111 does not process inquiry requests received from the repair factory terminal 200 immediately, but stores them in the inquiry queue. The inquiry queue is a message queue constructed in the auxiliary storage unit 13, and manages inquiry requests using, for example, a first-in, first-out (FIFO) method. The batch processing unit, upon meeting predetermined execution conditions, reads multiple query requests accumulated in the query queue and, based on the information of the target component contained in each of the query requests, collectively executes a process to identify a substitute component by referring to the management database 105. The results provision unit provides the results identified by the batch processing unit to the corresponding repair factory terminal 200 or a predetermined output destination.

[0146] The predetermined execution conditions are at least one of the following: the arrival of a pre-set time, or the number of accumulated query requests reaching a predetermined threshold. The pre-set time is preferably a time when the system load is low, such as 2:00 AM every day or 12:00 AM every Sunday. The predetermined threshold is, for example, a value such as 100, 500, or 1000 requests.

[0147] Asynchronous processing can be implemented in cloud computing environments. By properly constructing a serverless architecture, system scalability and availability are improved. Asynchronous processing allows for efficient handling of high-volume inquiry needs where real-time processing is not essential (e.g., nighttime inventory replenishment orders).

[0148] <Universalization of Applicability and Management Techniques for Non-Mechanical Components (Software Modules)> In this embodiment, the repair of vehicle 4 was given as an example, but the products to which the parts management system 1 can be applied are not limited to the repair of vehicle 4. Products to which the parts management system 1 can be applied include a variety of products such as home appliances, audio equipment, mobile devices such as robots and drones, smartphones, feature phones, power tools, personal computers, furniture, buildings, and software programs. Furthermore, the parts to which the parts management system 1 can be applied are not limited to tangible items such as mechanical parts, but may also include, for example, program modules.

[0149] When the parts management system 1 is applied to the management of software programs, "products" correspond to computer programs, and "parts" correspond to modules or libraries. In this case, the parts management server 100 functions as a module management server. The module management server stores module IDs, compatibility information, and module attribute information. A module ID is an identifier that uniquely identifies a module or library. Compatibility information is information that shows the correspondence between module IDs of modules or libraries that are functionally compatible and interchangeable with each other, and corresponds to association table 1053. Module attribute information is information that indicates the attributes of a module or library (name, version, provider, function description, dependencies, etc.), and corresponds to the parts management table 1052.

[0150] The module management server receives a query that includes the module ID of the target first module, and by referring to compatibility information, identifies the module ID of a second module that can replace the first module. The compatibility information may also include module or library version information. In this case, the module management server identifies a second module that is a different version from the first module and has the same or superior functionality as the first module. Superior functionality means, for example, that the second module provides all the APIs (Application Programming Interfaces) provided by the first module, and also provides additional APIs.

[0151] Such software module compatibility management can be applied as a backend system for dependency management tools in software development. It can also be used for corporate software asset management, open-source software (OSS) license management, and security vulnerability response (suggesting alternative modules for vulnerable ones).

[0152] <Proactive misregistration prevention technology based on operation prevention using historical information> Also, in association table 1053, a certain part A and other parts B Regarding the correspondence with "Error", if information indicating that it is pre-update information is stored in the part A and parts BIf a modification operation is detected that attempts to associate parts on the parts matching screen 1031, the association unit 103 may output a confirmation screen to confirm the execution of the modification operation, or it may prohibit the modification operation. Outputting a confirmation screen or prohibiting the modification operation can prevent incorrect parts from being registered in the association table 1053.

[0153] The association unit 103 may also function as a reception unit, a determination unit, and a control unit. In its function as a reception unit, the association unit 103 receives an operation from a user to register or update the association table 1053 as interchangeable between the first and second parts. In its function as a determination unit, when the association unit 103 receives such an operation, it refers to the error history table 1054 and determines whether the combination of the first and second parts is included in the error history information. In its function as a control unit, if the association unit 103 determines that the combination is included in the error history information, it performs at least one of the following: outputting warning information for the operation, or restricting the execution of the operation.

[0154] Figure 12(B) shows an example of a confirmation screen 1036 output by the association unit 103. The confirmation screen 1036 includes a warning message, an error reason display field, a past registration date and time display field, a confirmation button, and a cancel button. The warning message is, for example, "This combination of parts has been registered as an error in the past. Do you want to continue registration?". The error reason display field displays the value stored in "Error Reason" of the error history table 1054. The past registration date and time display field displays the values ​​stored in "Registration Date and Time" and "Deletion Date and Time" of the error history table 1054. This confirmation screen 1036 allows the user to see the reason why the combination was previously flagged as an error and the date and time of past registration related to that combination, thereby preventing the same incorrect registration from being repeated.

[0155] This error history-based error prevention feature is applicable not only to parts management but also to customer relationship management (CRM), product information management (PIM), and other database management systems. In other words, by generalizing "parts" to "data items," it can be used to maintain data integrity in various fields.

[0156] The embodiments and variations disclosed above can be combined in any way.

[0157] <Computer-readable recording medium> An information processing program that enables a computer or other machine or device (hereinafter referred to as "computer, etc.") to perform any of the above functions can be recorded on a recording medium that the computer, etc. can read. By having the computer, etc. read and execute the program on this recording medium, it can be made to provide that function.

[0158] Here, a recording medium that can be read by a computer refers to a recording medium that stores information such as data and programs through electrical, magnetic, optical, mechanical, or chemical means and can be read by a computer. Examples of such recording media that can be removed from a computer include flexible disks, magneto-optical disks, Compact Disc Read Only Memory (CD-ROM), Compact Disc-Recordable (CD-R), Compact Disc-ReWriterable (CD-RW), Digital Versatile Disc (DVD), Blu-ray Disc (BD), Digital Audio Tape (DAT), 8mm tape, flash memory, external hard disk drives, and Solid State Drives (SSDs). In addition, recording media that are fixed to a computer include internal hard disk drives, SSDs, and ROMs.

[0159] As used in the embodiments and claims described above, the terms “part,” “means,” “apparatus,” and “system” do not merely mean physical means, but also include cases where the functions of these are realized by software or software services. Furthermore, the functions of a single “part,” “means,” “apparatus,” or “system” may not only be realized by a single physical means, software, software module, or apparatus, but may also be realized by multiple physical means, software, software modules, apparatus, or combinations thereof.

[0160] The terms used in the embodiments and claims described above should be interpreted as non-limiting terms. For example, the term "includes" should be interpreted as "not limited to those described as including." The term "contains" should be interpreted as "not limited to those described as containing." The term "equips" should be interpreted as "not limited to those described as equipped." The term "possesses" should be interpreted as "not limited to those described as possessing." The term "complements" should be interpreted as "not limited to those described as possessing."

[0161] <Universalization of Applicability and Management Techniques for Non-Mechanical Components (Software Modules)> In this invention, "object" means an object or program composed of multiple components. The object includes, for example, products (vehicles, home appliances, industrial machinery, electronic equipment, etc.) or computer programs (application software, system software, firmware, etc.). "Component" refers to the individual elements that make up an object. Components include, for example, parts used for repairing or maintaining a product, or modules or libraries that constitute a computer program. "Component ID" refers to an identifier that uniquely identifies a component; if the component is a part, it corresponds to a part ID; if the component is a module or library, it corresponds to a module ID. "Component attribute information" refers to information indicating the attributes of a component; if the component is a part, it corresponds to part attribute information; if the component is a module or library, it corresponds to module attribute information.

[0162] In this invention, "configuration, repair, or updating of an object" means the assembly, repair, or maintenance of a product if the object is a product, and the construction, version upgrade, or updating of dependencies of a computer program if the object is a computer program. "Alternative component" means a second component that is interchangeable with the first component, corresponding to an alternative part if the component is a part, and corresponding to an alternative module or library if the component is a module or library. Thus, this invention is not limited to mechanical parts management but provides a general technical concept that can also be applied to software asset management.

[0163] (Note 1) A storage unit that stores: first correspondence relationship information that associates a part ID that uniquely identifies each of several parts used in the repair of a product with part attribute information that indicates the attributes of the part, and second correspondence relationship information that associates the part IDs of parts that can be substituted for each other. A process that, based on a request from an external device including part attribute information for a first part used to repair the product, identifies the part ID corresponding to the first part by referring to the first correspondence information based on the part attribute information, A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence information based on the identified part ID, A process to obtain the part attribute information corresponding to the part ID of the substitute part by referring to the first correspondence information, The system includes a control unit that performs a process of transmitting the part attribute information corresponding to the part ID of the acquired replacement part to the external device, Information processing device. (Note 2) The control unit accesses a server managed by the manufacturer of each of the plurality of components to identify the components that can be substituted for one another. The information processing device described in Appendix 1. (Note 3) The system acquires repair history information, including the aforementioned part attribute information, from the external device, and identifies the parts that can be substituted for each other based on the acquired repair history information. The information processing device described in Appendix 1 or 2. (Note 4) The control unit arranges a first image representing the product and a second image representing the parts as nodes, connects the first image and the second image with line segments based on the first correspondence information, and connects the second images representing parts that can be substituted for each other with line segments based on the second correspondence information, and outputs a hierarchical structure with either the first image or the second image as the root. An information processing device as described in any one of the appendices 1 to 3. (Note 5) When the node is moved in the hierarchical structure, the control unit performs the second correspondence information update process according to the connection relationship of the node in the hierarchical structure after the move. The information processing device described in Appendix 4. (Note 6) In the update process, the control unit adds information indicating that the record of the correspondence relationship of the part ID before the update is pre-update, and adds the record of the correspondence relationship of the part ID after the update to the second correspondence relationship information. The information processing device described in Appendix 5. (Note 7) A computer comprising a storage unit that stores: first correspondence relationship information that associates a part ID that uniquely identifies each of several parts used in the repair of a product with part attribute information that indicates the attributes of the part, and second correspondence relationship information that associates the part IDs of parts that can be substituted for each other, A process that, based on a request from an external device including part attribute information for a first part used to repair the product, identifies the part ID corresponding to the first part by referring to the first correspondence relationship based on the part attribute information, A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence relationship based on the identified part ID, A process to obtain the part attribute information corresponding to the part ID of the substitute part by referring to the first correspondence relationship, The process of transmitting the part attribute information corresponding to the part ID of the acquired replacement part to the external device is performed. Information processing methods. (Note 8) A computer having a storage unit that stores: first correspondence relationship information that associates a part ID that uniquely identifies each of several parts used in the repair of a product with part attribute information that indicates the attributes of the part, and second correspondence relationship information that associates the part IDs of parts that can be substituted for each other, A process that, based on a request from an external device including part attribute information for a first part used to repair the product, identifies the part ID corresponding to the first part by referring to the first correspondence information based on the part attribute information, A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence relationship based on the identified part ID, A process to obtain the part attribute information corresponding to the part ID of the substitute part by referring to the first correspondence relationship, The process of transmitting the part attribute information corresponding to the part ID of the acquired replacement part to the external device is performed. Information processing program. [Explanation of Symbols]

[0164] 1. Parts Management System 3. Repair shop 4 vehicles 11 processors 12 Main memory 13 Auxiliary storage 14 Communications Department 21 processors 22 Main memory 23 Auxiliary storage 24 Communications Department 25 Input section 26 Output section 100 Parts Management Server 101 Vehicle Registration Department 102 Parts Registration Department 103 Association section 104 Answer section 105 Management Database 111 Storage Control Unit 112 Inquiry Queue 113 Batch Processing Unit 114 Results Provision Department 120 Acquisition section (VIN compatible) 121 Part Identification Section 122 Registration Processing Unit (Automatic Registration) 200 Repair shop terminals 300 Module Management Server 301 Memory Unit (Module Management) 302 Specific Section (Module Management) 303 Output section (module management) 800 mouse cursors 1011 Vehicle Registration Screen 1012 Vehicle Identification Information Input Field 1013 Manufacturer input field 1014 Vehicle type input field 1015 Register button 1016 Cancel button 1021 Parts Registration Screen 1022 Model number input field 1023 Manufacturer input field 1024 Type input field 1025 Status input field 1026 Vehicle Identification Information Input Field 1027 Register button 1028 Cancel button 1031 Parts compatibility screen 1032 Vehicle node image 1033 Genuine Parts Node Image 1034 Compatible Part Node Image 1035 Display Mode Switching Button 1036 Confirmation screen 1051 Vehicle Management Table 1052 Parts Management Table 1053 Association Table 1054 Error History Table 10251 Pull-down menu 3011 Module Management Table 3012 Compatibility Table B1 connecting bus B2 connecting bus N1 Network

Claims

1. An information processing device that processes information about multiple parts, A communication unit that can connect to a management database that stores attribute information of the parts, with each of the aforementioned parts associated with a unique part ID, A control unit that identifies a replacement part by referring to the attribute information in response to a request from an external device, Equipped with, The attribute information includes type information indicating the functional classification of the part, and status information indicating the market distribution status or quality status of the part. The aforementioned management database is The system stores a first correspondence relationship information that associates the part ID with the attribute information, and a second correspondence relationship information that associates the part IDs of parts that can be substituted for each other. The control unit, Based on a request from the external device including the attribute information for the first component, the process involves identifying the component ID corresponding to the first component by referring to the first correspondence information. A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence information based on the identified part ID, A process to obtain the attribute information corresponding to the part ID of the substitute part by referring to the first correspondence information, A process of transmitting the attribute information corresponding to the part ID of the acquired replacement part to the external device, Execute, The control unit is an information processing device that narrows down the alternative parts based on a combination of the type information and the state information.

2. The aforementioned status information includes a value indicating that it is at least one of the following: a new genuine part, a used genuine part, a new compatible part, or a used compatible part. The information processing apparatus according to claim 1.

3. An information processing system for processing information about multiple parts, Information processing equipment and An external device that is connected to the aforementioned information processing device via a network in a manner that enables communication, A management database that stores attribute information of each of the aforementioned parts, with each of the aforementioned parts associated with a unique part ID, Equipped with, The attribute information includes type information indicating the functional classification of the part, and status information indicating the market distribution status or quality status of the part. The aforementioned management database is The system stores a first correspondence relationship information that associates the part ID with the attribute information, and a second correspondence relationship information that associates the part IDs of parts that can be substituted for each other. The external device is, A request including the attribute information for the first component is transmitted to the information processing device. The aforementioned information processing device is Based on the request received from the external device, the process involves identifying the part ID corresponding to the first part by referring to the first correspondence information, A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence information based on the identified part ID, A process to obtain the attribute information corresponding to the part ID of the substitute part by referring to the first correspondence information, A process of transmitting the attribute information corresponding to the part ID of the acquired replacement part to the external device, Execute, The information processing device is an information processing system that narrows down the alternative parts based on a combination of the type information and the state information.

4. A computer that processes information about multiple parts, A communication unit that can connect to a management database that stores attribute information of the parts, with each of the aforementioned parts associated with a unique part ID. A control unit that identifies a replacement part by referring to the attribute information in response to a request from an external device. An information processing program that functions as such, The attribute information includes type information indicating the functional classification of the part, and status information indicating the market distribution status or quality status of the part. The aforementioned management database is The system stores a first correspondence relationship information that associates the part ID with the attribute information, and a second correspondence relationship information that associates the part IDs of parts that can be substituted for each other. The control unit, Based on a request from the external device including the attribute information for the first component, the process involves identifying the component ID corresponding to the first component by referring to the first correspondence information. A process to obtain the part ID of a replacement part that replaces the first part by referring to the second correspondence information based on the identified part ID, A process to obtain the attribute information corresponding to the part ID of the substitute part by referring to the first correspondence information, A process of transmitting the attribute information corresponding to the part ID of the acquired replacement part to the external device, Execute, The control unit is an information processing program that narrows down the alternative parts based on the combination of the type information and the state information.

Images