SYSTEM AND METHOD FOR UPDATING A REPAIR PROCESS OF VEHICLE COMPONENTS

Abstract

The present invention provides a system (100) and a method (300) for updating one or more repair processes of one or more vehicle components. The system (100) extracts bill of materials (BOM) data assigned to a plurality of vehicle components from a BOM database (110) assigned to the system (100). The system (100) retrieves sub-module information (130) correlated with one or more repair document identifiers from a mapping database (120) assigned to the system (100). Furthermore, the system (100) compares the BOM data assigned to the vehicle components with the sub-module information (130) correlated with the repair document identifiers (140).Based on the comparison, the system (100) generates a report (150) containing a variety of parameters that indicate updates required for one or more repair operations of one or more vehicle components from the multitude of vehicle components.

Description

TECHNICAL AREA

[0001] The present invention relates to systems for the maintenance and repair of motor vehicles. In particular, the present invention relates to a system and a method for updating repair procedures of vehicle components. BACKGROUND

[0002] Currently, identifying changes to vehicle assemblies, subassemblies, and components is a complex and time-consuming task, often requiring extensive research into transfer parts and the identification of relevant repair documentation. This process is further complicated by the reliance on three-dimensional (3D) data and information from designers, which is not always fully developed or up-to-date. Using immature 3D layouts, also known as snapshots, can increase the likelihood of inaccuracies, potentially leading to rework and delays in production and repair documentation.

[0003] These challenges can impact several key areas, including the accurate identification of part changes, the time spent locating previously used components, and the effort required to update repair documentation. Furthermore, difficulties in accessing and verifying information from engineers further complicate the process, making it harder to ensure that all parts and arrangements are correctly documented and that changes are effectively communicated throughout the production and after-sales pipeline. As a result, the overall efficiency and accuracy of the vehicle manufacturing and repair process can be compromised.

[0004] Many techniques have been developed to avoid the aforementioned problems. For example, patent US2004138792A1 discloses a system and method for efficiently capturing, storing, and reporting maintenance, repair, and overhaul (MRO) data for the aerospace industry, providing a consistent set and type of data captured and stored across various systems, parts, and components. The system includes a first server computer implementing a web-based data capture application used to capture and store aerospace product-related MRO data in a MRO database accessible to a company's workforce. A portion of the captured data is extracted from the MRO database and stored in a customer MRO database.In addition, the system includes a second server computer that implements a web application for the customer interface, which is used to retrieve the data stored in the customer repair and overhaul database.

[0005] Although the cited document reveals various techniques for collecting and reporting on various aviation product-related repair and overhaul data in connection with the maintenance, repair and overhaul of aircraft components, they do not focus on updating repair operations of vehicle components.

[0006] Therefore, there is still room for a solution to update the repair processes of the vehicle components. ITEMS OF THE PRESENT INVENTION

[0007] A general object of the present invention is to provide a system and a method for effectively updating one or more repair processes of one or more vehicle components.

[0008] Another object of the present invention is to provide a system and a method for extracting bill of materials (BOM) data associated with a large number of vehicle components from a database.

[0009] Another object of the present invention is to provide a system and a method for retrieving sub-module information correlated with one or more repair document identifiers from a mapping module associated with the system.

[0010] Another object of the present invention is to provide a system and a method to compare the BOM data assigned to a plurality of vehicle components with the sub-module information correlated with one or more repair document identifiers.

[0011] Another object of the present invention is to provide a system and a method for generating a report containing a plurality of parameters to update one or more repair operations of one or more vehicle components from the plurality of vehicle components. SUMMARY

[0012] The present invention relates to systems for the maintenance and repair of motor vehicles. In particular, the present invention relates to a system and a method for updating repair procedures of vehicle components.

[0013] One aspect of the present invention relates to a system for updating one or more repair processes of one or more vehicle components. The system comprises a processor and a memory coupled to the processor. The memory contains one or more processor-executable instructions which, when executed, cause the processor to extract bill of materials (BOM) data associated with a plurality of vehicle components from a database. After extracting the BOM data, the processor retrieves sub-module information correlated with one or more repair document identifiers from a mapping module associated with the system. The processor compares the BOM data associated with the vehicle components with the sub-module information correlated with one or more repair document identifiers.Based on the comparison, the processor generates a report containing a variety of parameters that necessitate an update of one or more repair operations for one or more vehicle components from the multitude of vehicle components.

[0014] In some embodiments, each of the one or more repair receipt identifiers can specify a repair operation for each of the multiple vehicle components.

[0015] In some embodiments, the processor can generate the report by being configured to detect one or more changes during the comparison of the BOM data and the submodule information that correlate with one or more repair document identifiers.

[0016] In some embodiments, the multitude of parameters may include at least one of the changes in one or more submodules, changes in a component number, a change in the position of one or more vehicle components, changes in a configuration rule assigned to one or more vehicle components, and changes in the change notice for technical data of one or more vehicle components.

[0017] In some embodiments, the memory may contain one or more processor-executable instructions which, when executed, cause the processor to create one or more submodules containing one or more associated components from the multitude of vehicle components based on the BOM data.

[0018] In some embodiments, the processor can be configured to assign one or more repair receipt identifiers to each of the one or more submodules, indicating a repair operation for each of the one or more assigned components.

[0019] One aspect of the present invention relates to a method for updating one or more repair processes of one or more vehicle components. The method comprises extracting BOM data associated with a plurality of vehicle components from a database by a processor associated with a system. After extracting the BOM data, the method comprises retrieving sub-module information correlated with one or more repair document identifiers from a mapping module associated with the system by the processor. The method comprises comparing the BOM data associated with the vehicle components with the sub-module information correlated with one or more repair document identifiers by the processor.Based on the comparison, the procedure involves the processor generating a report containing a variety of parameters that necessitate an update of one or more repair operations for one or more vehicle components from the multitude of vehicle components.

[0020] In some embodiments, the generation of the report by the processor may include detecting one or more changes during the comparison of the BOM data and the information about the submodule that correlates with one or more repair document identifiers.

[0021] In some implementations, the process may involve the processor generating one or more submodules containing one or more associated components from the multitude of vehicle components based on the BOM data.

[0022] In some implementations, the procedure may involve the processor assigning each of the one or more submodules to the one or more repair document identifiers that specify a repair operation for each of the one or more assigned components.

[0023] Various objects, features, aspects and advantages of the subject matter according to the invention will become clearer from the following detailed description of preferred embodiments together with the accompanying drawing figures, in which the same numbers represent the same components. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings serve to further understand the present invention and are an integral part of this description. The drawings illustrate exemplary embodiments of the present invention and, together with the description, serve to explain the principles of the present invention. Fig. Figure 1 shows a system architecture for identifying changes that require an update of one or more repair operations of one or more vehicle components, according to embodiments of the present invention. Fig. Figure 2 shows a block diagram of a system for detecting changes that require an update of one or more repair operations of one or more vehicle components, according to embodiments of the present invention. Fig. Figure 3 shows a flowchart of an example method for determining changes that require an update of one or more repair operations for one or more vehicle components, according to embodiments of the present invention. Fig. Figure 4 shows an example of a computer system in which or with which embodiments of the system according to the embodiments of the present invention can be implemented. DETAILED DESCRIPTION

[0025] A detailed description of the embodiments of the invention illustrated in the accompanying drawings follows. The embodiments are described in sufficient detail to ensure the invention is clearly understandable. However, the intention is not to limit foreseeable embodiments with the necessary level of detail; rather, the aim is to cover all modifications, equivalents, and alternatives that fall within the scope of the present invention as defined by the accompanying claims.

[0026] The present invention relates to systems for the maintenance and repair of motor vehicles. In particular, the present invention relates to a system and a method for updating repair procedures of vehicle components.

[0027] One aspect of the present invention relates to a system for updating one or more repair processes of one or more vehicle components. The system comprises a processor and a memory coupled to the processor. The memory contains one or more processor-executable instructions which, when executed, cause the processor to extract bill of materials (BOM) data associated with a plurality of vehicle components from a database. After extracting the BOM data, the processor retrieves sub-module information correlated with one or more repair document identifiers from a mapping module associated with the system. The processor compares the BOM data associated with the vehicle components with the sub-module information correlated with one or more repair document identifiers.Based on the comparison, the processor generates a report containing a variety of parameters that necessitate an update of one or more repair operations for one or more vehicle components from the multitude of vehicle components.

[0028] Various embodiments of the present invention are described with reference to the Fig. 1-4 explained in more detail. 1-4.

[0029] Fig. Figure 1 shows a system architecture for identifying changes that require an update of one or more repair operations of one or more vehicle components, according to embodiments of the present invention.

[0030] With reference to Fig. System 100 can contain a BOM database 110 and a mapping database 120. The BOM database 110 can contain BOM data associated with a wide variety of vehicle components. These components can include, but are not limited to, engine components, transmission components, electrical components, brake system components, suspension and steering components, exhaust system components, cooling system components, fuel system components, interior components, and body and chassis components.

[0031] Engine components can include pistons, crankshafts, camshafts, fuel injectors, and turbochargers. Transmission components include the gearbox, clutch, driveshaft, and torque converter. Electrical components include the battery, alternator, starter, wiring harness, and sensors (e.g., oxygen sensors, temperature sensors, etc.). Braking system components include brake pads, brake discs, calipers, master cylinder, and anti-lock braking system (ABS). Suspension and steering components include shock absorbers, struts, coil springs, rack and pinion, and steering gears. Exhaust system components include the exhaust manifold, catalytic converter, and muffler.

[0032] Components of the cooling system can include a radiator, water pump, thermostat, and cooling fan. Components of the fuel system can include a fuel tank, fuel pump, and fuel filter. Interior components can include a dashboard, seat belts, airbags, steering wheel, and infotainment system. Body and chassis components can include a frame / chassis, doors, fenders, bumpers, and hood.

[0033] In some embodiments, the mapping database 120 can store sub-module information 130 obtained from 3D arrangements, also called snapshots. The mapping database 120 can also store one or more repair document identifiers 140, which specify a repair operation for each of the multiple vehicle components in a mapping module. In some embodiments, the sub-module information 130 can be correlated with the one or more repair document identifiers 140.

[0034] In some embodiments, System 100 can extract the BOM data associated with the multitude of vehicle components from the BOM database 110, for example, from a Product Lifecycle Management (PLM) database. In some embodiments, System 100 can retrieve the sub-module information correlated with one or more repair document identifiers from the mapping module of the mapping database 120. In some embodiments, System 100 can compare the BOM data associated with the multitude of vehicle components with the sub-module information correlated with one or more repair receipt identifiers.

[0035] Based on the comparison, system 100 can generate a report 150 containing a variety of parameters if one or more changes are detected during the comparison of the BOM data and the information about the submodule correlated with the one or more repair document identifiers. These parameters can include, but are not limited to, changes in the one or more submodules, changes in a component number, a change in the position of one or more vehicle components, changes in a configuration rule assigned to the one or more vehicle components, and changes in the change notification for technical data of the one or more vehicle components.

[0036] Changes to one or more submodules that categorize repairable components within a larger assembly can be carefully reviewed. If submodule information changes, System 100 may indicate a potential impact on the repair process. Changes in component numbers can be significant, as they may indicate the introduction of new components or modifications to existing ones. A thorough review of component numbers may be necessary to identify and categorize such changes.

[0037] The position of components within a vehicle configuration can be a critical factor. Any change in position data during the comparison process can signal a potential change in the component's physical location, requiring an update to the repair procedures. System 100 can evaluate changes in the configuration rules associated with the repair procedures. A change in the configuration rule can indicate a potential impact on the repair procedure, leading to the inclusion of the corresponding repair identifier in Report 150. Furthermore, changes in the technical data change notification can also be considered during the comparison process to determine which adjustments are required in the post-sale repair document.

[0038] If any of these parameters show changes between the current data and previously stored data, the associated repair identifier can be entered in Report 150. This ensures a comprehensive and systematic identification of the identifiers of post-sale repair documents affected by changes in vehicle assembly data. Careful consideration of these specific data points can improve the accuracy and relevance of the generated Report 150 and enable effective updates to post-sale repair records.

[0039] Report 150 can highlight the impact repair document identifiers, which can be used to update one or more repair operations for one or more vehicle components that correspond to the impact repair document identifiers. This can significantly reduce the effort required to manually search for each individual repair identifier, thereby streamlining the process and improving efficiency in identifying changes to a vehicle's assemblies, subassemblies, and components.

[0040] In some implementations, the identified changes can be categorized into corresponding vehicle component groups during report generation. These vehicle component groups can serve as categories to help organize and prioritize the detected changes. In this context, the vehicle component groups can effectively classify the changes into various categories, such as the introduction of new parts, the modification of parts, or the adjustment of positions. Therefore, Report 150 can be a comprehensive document highlighting the specific repair document identifiers associated with the identified changes. Only the identifiers included in Report 150 need to be considered, indicating that these elements may require further analysis and a potential modification of the repair procedure.This systematic approach can ensure that Report 150 serves as a targeted guide for addressing and implementing necessary arrangements in the assembly and repair of vehicles.

[0041] Fig. Figure 2 shows a block diagram of system 100 for identifying changes that require an update of one or more repair operations of the vehicle components, according to embodiments of the present invention.

[0042] As in Fig. As shown in Figure 2, the system 100 can contain one or more processors 102. The processor(s) 102 can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any devices that process data based on operating instructions. Among other capabilities, the one or more processors 102 can be configured to retrieve and execute computer-readable instructions stored in a memory 104. The memory 104 can store the computer-readable instructions or routines that can be retrieved and executed to create the data units or passed to other elements of the system 100. The memory 104 can include any non-volatile storage device, such as...volatile memory such as Random-Access Memory (RAM) or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), Flash memory, and the like.

[0043] In some embodiments, the system 100 may also include one or more interfaces 106. The interface(s) 106 may include a variety of interfaces, such as interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) 106 may enable communication between the system 100 and the external storage device by using peripheral devices that enable wired and / or wireless communication. The interface(s) 106 may also provide a communication path for one or more components within the system 100. Examples of such components include, but are not limited to, the processing machine(s) 108 and the databases 110, 120.

[0044] Databases 110 and 120 could refer to the BOM database 110 and the mapping database 120, as described in Fig. Figure 1 shows that databases 110 and 120 can contain data that is either stored or generated as a result of functionalities implemented by one of the components of the processing machine(s) 108. In some embodiments, the BOM database 110 can store BOM data associated with a plurality of vehicle components. In some embodiments, the mapping database 120 can store sub-module information correlated with the one or more repair document identifiers that specify the repair operation of each of the plurality of vehicle components in the mapping module.

[0045] In one embodiment, the processing machine(s) 108 can be implemented as a combination of hardware and software (e.g., programmable instructions) to implement one or more functions of the processing machine(s) 108. In the examples described here, such combinations of hardware and software can be implemented in various ways. For example, the software for the processing machine(s) 108 can consist of processor-executable instructions stored on a non-volatile, machine-readable storage medium, and the hardware for the processing machine(s) 108 can include a processing resource (e.g., one or more processors) to execute such instructions. In other embodiments, the processing machine(s) 108 can be implemented by an electronic circuit.

[0046] In some embodiments, the processing machine(s) 108 may include an extraction machine 112, a comparison machine 114, a report generation machine 116, and other machine(s) 118. The other machine(s) 118 may implement functions that complement the applications / functions performed by the system 100.

[0047] In some embodiments, one or more processors 102 can extract the BOM data associated with the multitude of vehicle components from the BOM database 110 via the extraction machine 112. To extract the BOM data from the BOM database 110, users can utilize a predefined, integrated functionality within the BOM database 110. The BOM database 110 can store comprehensive BOM data curated by various teams. The BOM data in the BOM database 110 can be accessed via a download function within the BOM database 110, whereby the download can be performed in a specific version for optimal results.

[0048] In some embodiments, the one or more processor(s) 102 can retrieve the submodule information correlated with the one or more repair document identifiers from the mapping module assigned to the mapping database 120 via the extraction machine 112. The correlation between the one or more repair document identifiers and specific submodules within vehicle assemblies can be a sophisticated internal process. Each of the one or more repair document identifiers can represent a specific repair operation (e.g., AR82.10-P-4731* for removing / installing taillights) and can be carefully assigned for each vehicle line, resulting in approximately 1000-1500 different identifiers per line.In a comprehensive three-dimensional (3D) arrangement, also known as a snapshot, one or more repairable components can be consistently assigned to specific submodules to ensure uniformity across all vehicle lines.

[0049] This correlation process can include a manual review of the repair document identifiers, comparing them with the associated sub-module data in the snapshot. Mapping database 120 can be carefully created through this manual review. The sub-module information can serve as a constant reference point for comparing the BOM data associated with the multitude of vehicle components and the sub-module information correlated with one or more repair document identifiers.

[0050] In some implementations, the one or more processor(s) 102 can use the comparison engine 114 to compare the BOM data assigned to the multitude of vehicle components with the sub-module information correlated with the one or more repair document identifiers. For example, a Python-based data execution script can be used to seamlessly compare or integrate the BOM data assigned to the vehicle components with the sub-module information correlated with the one or more repair document identifiers.

[0051] The Python-based script, or any script based on programmable software code, can orchestrate a range of computational techniques to ensure a smooth integration process. The script can employ efficient data query and manipulation techniques to extract the BOM data from BOM database 110 and retrieve the submodule information associated with each repair identifier from the mapping module associated with mapping database 120. Seamless integration can then be achieved by comparing the BOM data retrieved from BOM database 110 with the corresponding submodule information stored in the mapping module. Data analysis and manipulation libraries, such as Python pandas, can be used to efficiently process and compare large datasets, thus ensuring the accuracy and speed of the integration process.If discrepancies or changes are detected between the BOM data and the information about the submodules, a report can be generated that provides information about the specific repair document identifiers and the corresponding modified parts. Therefore, the script can function as a versatile computational tool that employs algorithms enabling the extraction, processing, and integration of the BOM data with carefully curated map data from the submodules, thus ensuring a seamless and accurate correlation process.

[0052] In some embodiments, the one or more processor(s) 102 can, via the report generation engine 116, generate the report containing the plurality of parameters to update or revise the one or more repair operations of the one or more vehicle components from the plurality of vehicle components. In some embodiments, the one or more processor(s) 102 can, via the report generation engine 116, generate the report when one or more changes are detected during the comparison of the BOM data and the submodule information correlated with the one or more repair document identifiers.

[0053] In some embodiments, the one or more processor(s) 102 can create one or more submodules with one or more associated components from the multitude of vehicle components based on the BOM data. For example, components such as, but not limited to, the pistons, crankshafts, camshafts, fuel injectors, and turbochargers that are associated with each other can be grouped together in a first vehicle component group, and components such as, but not limited to, the frame / chassis, doors, fenders, bumpers, and hood that are associated with each other can be grouped together in a second vehicle component group, and so on.

[0054] In some embodiments, the one or more processors 102 can map each of the one or more submodules to the one or more repair document identifiers that specify the repair operation of each of the one or more associated components. Thus, when comparing the BOM data and the information about the submodules correlated with the one or more repair document identifiers, if a discrepancy or change is detected, the one or more processors 102 can generate a report highlighting the affected repair document identifiers associated with the one or more submodules. This can be used to update the one or more repair operations of the one or more associated components in the one or more submodules based on the affected repair document identifiers.

[0055] Fig. Figure 3 shows a flowchart of an example method 300 for updating one or more repair processes for one or more vehicle components according to embodiments of the present invention.

[0056] With reference to Fig. 3. Procedure 300 at 302 can include extracting the BOM data assigned to the multitude of vehicle components from the BOM database 110.

[0057] At 304, after extraction of the BOM data, procedure 300 may include retrieving submodule information correlated with one or more repair document identifiers from the mapping module assigned to system 100.

[0058] In 306, the procedure 300 can include comparing the BOM data assigned to the multitude of vehicle components with the submodule information correlated with one or more repair document identifiers.

[0059] In the case of 308, the procedure 300, based on the comparison, may include generating a report with a variety of parameters to update one or more repair operations of one or more vehicle components from the multitude of vehicle components.

[0060] Fig. Figure 4 shows an example of a computer system 400 in which or with which embodiments of the system 100 according to the embodiments of the present invention can be implemented.

[0061] System 100 and Procedure 300 can be implemented in a computer system 400. As in Fig.As shown in Figure 4, the system 400 can comprise an external device 410, a bus 420, main memory 430, read-only memory 440, a mass storage device 450, a communication port 460, and a processor 470. A person skilled in the art will understand that the system 400 can comprise more than one processor 470 and communication ports 460. The processor 470 can contain various modules associated with the embodiments of the present invention. The communication port 460 can be a recommended standard 232 port for use with a modem-based dial-up connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port over copper or fiber optic cable, a serial port, a parallel port, or other existing or future ports. The port 460 can be selected depending on the network, e.g.,a Local Area Network (LAN), a Wide Area Network (WAN) or any other network to which the System 400 is connected.

[0062] In one embodiment, the memory 430 can be random-access memory (RAM) or any other dynamic storage device generally known in the art. The read-only memory (ROM) 440 can be any static device, such as a programmable read-only memory (PROM) for storing static information, without being limited thereto. The device 450 can be any current or future mass storage solution that can be used to store information and / or instructions. Examples of mass storage solutions include, but are not limited to, PATA (Parallel Advanced Technology Attachment) or SATA (Serial Advanced Technology Attachment) hard disks (internal or external, such as with Universal Serial Bus (USB) and / or FireWire interfaces), one or more optical disks, RAID (Redundant Array of Independent Disks) storage, such as an array of hard disks (e.g., SATA arrays).

[0063] In one embodiment, bus 420 provides communication between the processor(s) 470 and the other storage, repository, and communication blocks. Bus 420 may be, for example, a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, a Small Computer System Interface (SCSI), USB, or similar, for connecting expansion cards, drives, and other subsystems, as well as other buses, such as a front-end bus (FSB) that connects the processor 470 to the computer system 400.

[0064] In another embodiment, operator and management interfaces, such as a display device, a keyboard, and a cursor control unit, can also be connected to bus 420 to support direct operator interaction with the computer system 400. Other operator and management interfaces can be provided via network connections connected through the communication port 460. In some embodiments, the external storage device 410 can be any type of external hard disk drive, floppy disk drive, Compact Disc - Read Only Memory (CD-ROM), Compact Disc - Re-Writable (CD-RW), or Digital Video Disc - Read Only Memory (DVD-ROM). The components described above serve only to illustrate various possibilities. The computer system 400 described above is not intended to limit the scope of the present invention in any way.

[0065] While the foregoing describes various embodiments of the present invention, other and further embodiments of the present invention can be developed without departing from the fundamental scope of the invention. The scope of the present invention is defined by the following claims. The present invention is not limited to the described embodiments, variants, or examples, which are included to enable a person with ordinary technical knowledge to manufacture and use the present invention when combined with information and knowledge available to such a person. ADVANTAGES OF THE PRESENT INVENTION

[0066] The present invention effectively identifies changes that require an update of one or more repair procedures for one or more vehicle components.

[0067] The present invention reduces the effort required for manually searching for each individual repair identifier, streamlines an update process, and improves the efficiency of updating one or more repair operations of one or more vehicle components.

[0068] The present invention generates a comprehensive report that enables engineers to selectively update the repair processes of impacting repair receipt identifiers.

[0069] The present invention evaluates the impact of repair documents without access to three-dimensional (3D) computer-aided design (CAD) data models. QUOTES INCLUDED IN THE DESCRIPTION

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

[0000] US 2004138792A1

[0004]

Images