Stand-alone version interactive automobile after-sales manual development method

Abstract

According to the standalone version interactive automobile after-sales manual development method, the deliverable catalog framework library and the deliverable database are constructed, the interactive relation of the deliverable data elements is created, the delivery database is searched to automatically generate the delivery data packet, and the standalone version automobile after-sales manual is quickly generated. Compared with the prior art, automatic generation can be realized without networking, required information can be quickly positioned, the development cost is low, the efficiency is high, and large-area popularization and application are facilitated.

Description

Technical Field

[0001] This invention relates to the field of automotive aftermarket manual development technology, and more specifically, to a standalone interactive automotive aftermarket manual development method. Background Technology

[0002] With the continuous advancement of automotive technology, modern cars are equipped with an increasing number of electronic control systems and complex mechanical structures. The complexity of these technologies means that traditional paper-based after-sales manuals and some electronic after-sales manuals are gradually becoming insufficient to meet the needs of users and repair personnel. The main shortcomings are as follows: 1) Most electronic after-sales manuals require real-time internet access to obtain the latest data and have high development costs, which limits their use in environments with poor network signals or no network (such as remote overseas areas); 2) Most existing manuals are static documents, and users cannot obtain personalized maintenance suggestions or fault diagnosis through interactive operations; 3) Traditional manuals have a complex information organization structure, making it difficult for users to quickly locate the information they need, especially in emergency situations, resulting in low efficiency.

[0003] Therefore, it is necessary to propose a standalone interactive automotive after-sales manual development method, which is of great significance for improving the development efficiency and reducing the development cost of standalone automotive after-sales manuals. Summary of the Invention

[0004] This invention provides a standalone interactive automotive after-sales manual development method to solve the problem that existing electronic after-sales manuals require an internet connection for development, resulting in high costs and low efficiency.

[0005] According to one aspect of the present invention, a method for developing a standalone interactive automotive after-sales manual is provided, comprising the following steps: Step 1: Create a corresponding delivery item catalog framework library based on the brand, vehicle model, and delivery item type information in the order; Step 2: Create a vehicle model labor hour database, a brand exploded view spare parts list database, a repair process database, and a fault diagnosis database; Step 3: Create a database that maps brand vehicle codes to sub-product system numbers, a database that maps brand diagnostic process codes to vehicle codes, a database that maps brand entry codes to vehicle codes, a database that maps brand entry codes to part numbers to sub-product system numbers to work hour codes to work hour names, and a database that maps brand entry codes to tool unit codes. Step 4: Based on Step 2, obtain various deliverable process data packages, find and output the corresponding work hour data packages according to brand and vehicle model information, and generate the associated data packages of repair item-parts-work hours, repair item-spare part exploded view, repair item tool unit, diagnostic unit, flowchart link-diagnostic unit, and fault diagnosis-repair item-spare part details-repair work hour. Step 5: Generate the vehicle after-sales manual based on the data package obtained in Step 4.

[0006] Based on the above scheme, in step 1, the deliverables catalog framework library includes the names of each level of the catalog in the manual, the catalog name codes, the hierarchical relationship between each level of the catalog, and the order in which files at the same level are stored; and when the deliverables type information is entered to form the catalog name code, it is verified.

[0007] Based on the above scheme, the preferred option is that the creation of the vehicle model time database in step 2 includes: according to the parts assembly list, measuring the time quota of the time name corresponding to each assembled part to form a vehicle model time list, and reviewing and uploading the developed vehicle model time list to the vehicle model time database.

[0008] Based on the above scheme, the preferred option is that step 2, creating the brand exploded view spare parts list library, includes: Based on the parts loading list, the assembly drawings of each part are processed according to the sub-product system to obtain the exploded view of the sub-product system in SVG format. Based on the parts assembly information of each sub-product system, obtain a table-style spare parts list for each sub-product system. Name the exploded view of the sub-product system and the spare parts list of the sub-product system according to the sub-product system number, and upload them to the brand exploded view and spare parts list library.

[0009] Based on the above scheme, the preferred option is that the maintenance process database in step 2 includes a brand maintenance item library, a brand maintenance item tool unit library, a brand system overview unit library, a brand precautions unit library, a brand technical parameter unit library, a brand maintenance tool unit library, and a brand system component description unit library.

[0010] Based on the above scheme, the preferred option is that step 2, the creation of the maintenance process database, includes: Based on the development materials and deliverables catalog framework, establish development tasks for the overview content, precautions content, technical parameters content, maintenance tools content, and maintenance items content under each chapter of the catalog framework. According to the development task, the data of each manual is developed separately. The developed maintenance item files, tool unit files involved in the maintenance items, system overview files, precaution files, technical parameter files, maintenance tool files, and system component description files are coded and uploaded to the maintenance process database.

[0011] Based on the above scheme, the preferred option is that the fault diagnosis database creation in step 2 includes a brand diagnosis process library, a brand diagnosis tool unit library, a brand system function introduction unit library, a brand control unit terminal diagram unit library, a brand vehicle inspection unit library, a brand fault phenomenon table unit library, and a brand fault code table unit library.

[0012] Based on the above scheme, the preferred option is that step 2, creating the fault diagnosis database, includes: Based on the development materials and deliverables catalog framework, establish development tasks for diagnostic processes, diagnostic unit content involved in the diagnostic processes, system function introduction content, diagnostic parameter content, control unit terminal diagram, on-vehicle inspection content, fault phenomenon content, and fault code content under each chapter in the catalog framework library. According to the development task, the data of each manual are developed separately. The developed diagnostic process, diagnostic tools, system function introduction, diagnostic parameters, control unit terminal diagram, on-vehicle inspection, fault phenomenon table and fault code table are coded and uploaded to the fault diagnosis database.

[0013] Based on the above scheme, step 3 specifically includes the following optimization: Based on the brand and vehicle model, obtain the fault diagnosis path and assign it a code, create a correspondence between the vehicle model code and the diagnostic process code of the developed diagnostic process, and upload the correspondence to the brand diagnostic process code and vehicle model code mapping database. Based on the obtained vehicle model code and part number information, create a correspondence between the vehicle model code and the existing repair item code, and upload the correspondence to the brand item code and vehicle model code mapping database; Based on the parts loading list, the developed maintenance items, and the work hour list, create a correspondence between maintenance item code, part number, sub-product system number, work hour code, and work hour name, and upload this correspondence to the brand item code-part number-sub-product system number-work hour code-work hour name mapping database. Based on the developed maintenance items and maintenance tool units, create a correspondence between maintenance item codes and the maintenance tool unit codes involved in the maintenance items, and upload this correspondence to the brand item code and tool unit code mapping database.

[0014] Based on the above scheme, the preferred method is that the generation of the associated data package for maintenance items, parts, and working hours in step 4 includes: In step 1, the existing deliverable catalog is searched and retrieved from the deliverable catalog framework library; based on the deliverable catalog code and the same encoded field in the deliverable data package, the deliverable data is associated with the standard catalog framework of the corresponding deliverable type. Using the maintenance item codes in the maintenance manual catalog framework, one by one, go to the brand item code-part number-sub-product system number-work hour code-work hour name in step 3 and look up the associated sub-product system number, part number, and work hour code in the relational database to obtain the associated sub-product system number. Then, search for and generate an associated data package containing maintenance item codes, sub-product system spare parts exploded diagrams, and sub-product system spare parts details in the deliverable data package. Based on the associated work hour code, search in the work hour data package and generate an associated data package containing maintenance item-part-work hour, sub-product system number-part number-work hour code-work hour name-work hour quota data.

[0015] Based on the above scheme, the preferred embodiment of step 4, which involves generating the maintenance item tool unit data package, includes: Based on the repair item codes in the tool unit library related to the brand repair item, the tool unit codes are searched in the brand item code and tool unit code mapping database. Then, the tool unit codes are searched in the brand repair item tool unit library based on the found tool unit codes, and a repair item tool unit data package is generated. Step 4, the flowchart section – diagnostic unit data package generation – includes: For each process step in the flowchart associated with the content elements of the "Fault Phenomenon Table" or "Fault Code Table" in the fault diagnosis directory, the corresponding diagnostic unit code is searched in the diagnostic unit data package one by one, and a flowchart step-diagnostic unit link relationship data package containing the flowchart step-diagnostic unit link relationship is generated and output.

[0016] Based on the above scheme, the preferred method is that the generation of the fault diagnosis-maintenance item-spare parts list-maintenance man-hour association data package in step 4 includes: Based on the preset correspondence between brand, vehicle model, main sales location, and language, the existing delivery catalog is searched and retrieved from the delivery catalog framework library. Associate the deliverable data with the deliverable catalog based on the same encoded field in the deliverable data package; The diagnostic process cause in the diagnostic process file of the deliverable data package is used to determine the associated work hour code, and then the corresponding maintenance item code, sub-product system number, part number, work hour name, and work hour quota are searched in the associated data package of maintenance item-part-work hour. By finding the sub-product system number and part number information, the corresponding part's installation quantity is found in the associated data package of maintenance item-spare part exploded view, and a fault diagnosis-maintenance item-spare part detail-maintenance time association data package is generated. This data package contains fault cause determination, maintenance item, part number, part name, part installation quantity, work hour code, work hour name, and work hour quota association relationship.

[0017] This invention discloses a method for developing a standalone interactive automotive after-sales manual. Various generated data packages are uploaded to a standalone PC application to generate the manual. This allows for interactive information retrieval, including: viewing repair time information for corresponding parts from repair item content; viewing exploded views and spare parts details for corresponding parts from repair item content; viewing corresponding repair tool information from repair item content; querying diagnostic units related to fault diagnosis flowcharts and causes; and querying repair processes, repair time, and spare parts diagrams related to fault diagnosis process causes. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1 This is a flowchart of the stand-alone interactive automotive after-sales manual development method of the present invention. Detailed Implementation

[0019] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.

[0020] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of a descriptive feature, integral, step, operation, element, and / or component, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or sets.

[0021] To keep the drawings concise, only the parts relevant to the invention are shown schematically in each figure, and they do not represent the actual structure of the product. Furthermore, for ease of understanding, in some figures, only one of components with the same structure or function is shown schematically, or only one is labeled. In this document, "one" can mean not only "only one" but also "more than one".

[0022] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] In the embodiments shown in the accompanying drawings, the directional indications (such as up, down, left, right, front, and back) used to explain the structure and movement of the various components of the invention are relative rather than absolute. These descriptions are appropriate when these components are in the positions shown in the drawings. If the descriptions of the positions of these components change, these directional indications also change accordingly.

[0024] Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings and other implementation methods can be obtained based on these drawings without any creative effort.

[0026] Please see Figure 1 As shown, a standalone interactive automotive after-sales manual development method of the present invention includes the following steps: Step 1: Create a corresponding delivery item catalog framework library based on the brand, vehicle model, and delivery item type information in the order; Specifically, a backend management system is built to create development tasks for after-sales manuals, store procedure development data, and generate standalone data packages based on the vehicle's sales location and the language type of the sales location.

[0027] Based on the brand, vehicle model, and delivery type information in the customer order, developers create a corresponding delivery item catalog framework table offline. This is then imported into the backend management system by delivery item type and language, and the system verifies the imported catalog encoding.

[0028] in: 1) The deliverables catalog framework table includes the names of each level of the catalog in the manual, the catalog name codes, the hierarchical relationship between each level of the catalog, and the order in which files at the same level are stored.

[0029] 2) The encoding of directory names at all levels shall be set according to the encoding rules of two Arabic numerals or letters.

[0030] 3) When the backend management terminal verifies the directory codes in the imported deliverables manual directory framework table, if duplicates are found, it will prompt "Duplicate directory code", refuse the import, and output a list of issues; if there are no duplicates, the import will be successful.

[0031] 4) When the deliverables catalog framework is modified and needs to be re-imported, each import operation is an overwrite import, which facilitates version management; the deliverables catalog framework library is also synchronously set with permission policies after successful import, which supports online modification of the deliveredables catalog after successful import.

[0032] Step 2: Create a vehicle model labor hour database, a brand exploded view spare parts list database, a repair process database, and a fault diagnosis database; In the backend management system, create the following databases respectively. Developers select the language type and upload the developed deliverable process data to the corresponding databases according to brand and deliverable type.

[0033] The creation of the vehicle model time database includes: based on the parts assembly list, measuring the time quota corresponding to the time name of each assembled part, forming a vehicle model time list, and reviewing and uploading the developed vehicle model time list to the vehicle model time database. The vehicle model labor hour list includes: sub-product system number, part number, part name, labor hour code, labor hour name, and labor hour quota.

[0034] Step 2, the creation of the brand exploded view spare parts list library includes, Based on the parts loading list, the assembly drawings of each part are processed according to the sub-product system to obtain the exploded view of the sub-product system in SVG format. Based on the parts assembly information of each sub-product system, obtain a table of spare parts details for each sub-product system. Name the exploded view and spare parts details of each sub-product system according to the sub-product system number and upload them to the brand exploded view and spare parts details database.

[0035] Specifically, the spare parts list for the sub-product system includes: sub-product system number, sub-product system name, sequence number of each assembly part in the sub-product system, part number, part name, and quantity of part used on the vehicle.

[0036] In step 2, the maintenance process database includes a brand maintenance item library, a brand maintenance item tool unit library, a brand system overview unit library, a brand precautions unit library, a brand technical parameter unit library, a brand maintenance tool unit library, and a brand system component description unit library.

[0037] Specifically, the process of creating a maintenance process database includes, First, based on the development materials and deliverables catalog framework, establish development tasks for the overview content, precautions content, technical parameters content, maintenance tools content, and maintenance items content under each chapter of the catalog framework. Secondly, according to the development task, the data of each manual is developed separately. The developed HTML format maintenance entry files, tool unit files involved in the maintenance entries, system overview files, precaution files, technical parameter files, maintenance tool files, and system component description files are coded and uploaded to the maintenance process database. The coding adopts the directory coding # five Arabic numerals or letters coding rule.

[0038] In step 2, the fault diagnosis database creation includes a brand diagnosis process library, a brand diagnosis tool unit library, a brand system function introduction unit library, a brand control unit terminal diagram unit library, a brand vehicle inspection unit library, a brand fault phenomenon table unit library, and a brand fault code table unit library.

[0039] The specific steps for creating a fault diagnosis database according to this invention include: Based on the development materials and deliverables catalog framework, establish development tasks for diagnostic processes, diagnostic unit content involved in the diagnostic processes, system function introduction content, diagnostic parameter content, control unit terminal diagram, on-vehicle inspection content, fault phenomenon content, and fault code content under each chapter in the catalog framework library. According to the development task, the data of each manual were developed separately. The developed HTML format diagnostic process, diagnostic tools, system function introduction, diagnostic parameters, control unit terminal diagram, vehicle inspection, fault phenomenon table and fault code table were coded and uploaded to the fault diagnosis database. The coding adopts the directory coding # five Arabic numerals or letters coding rule.

[0040] The diagnostic units involved in the XML format diagnostic process are encoded according to the encoding rule of diagnostic process code + diagnostic unit sequence number, and then uploaded to the brand diagnostic unit library.

[0041] in: 1) The diagnostic process includes: system schematic diagram, flowchart, and diagnostic process elements; 2) The fault phenomenon table includes: fault phenomenon, possible cause, troubleshooting, and operation elements; the fault code table includes: DTC code, code description, and operation elements, and the corresponding diagnostic process document code must be filled in the operation elements of the fault phenomenon table and the fault code table.

[0042] Step 3: Create a database that maps brand vehicle codes to sub-product system numbers, a database that maps brand diagnostic process codes to vehicle codes, a database that maps brand entry codes to vehicle codes, a database that maps brand entry codes to part numbers to sub-product system numbers to work hour codes to work hour names, and a database that maps brand entry codes to tool unit codes. This involves creating a vehicle loading list information processing module in the backend management system, which is used to extract vehicle model code, vehicle part name, part number, sub-product system number, and sub-product system name information from the parts loading list of the target vehicle model.

[0043] Create the following mapping relationship databases in the backend management terminal to store the mapping relationships between process data elements of each deliverable, so as to facilitate data interaction.

[0044] First, create a database that maps brand vehicle codes to sub-product system numbers; Based on the extracted vehicle model code and sub-product system number information, the system automatically creates a correspondence between vehicle model code, sub-product system number, and sub-product system name, and uploads the created correspondence table to the brand vehicle model code and sub-product system number mapping database. Then create a database that maps brand diagnostic process codes to vehicle model codes;

[0045] Based on the brand and vehicle model, according to the patented automotive DTC fault diagnosis process development method (ZL202411779910.4), the output fault diagnosis path (i.e., diagnosis process) is assigned a code, the fault diagnosis path is obtained and assigned a code, a correspondence between the vehicle model code and the diagnosis process code of the developed diagnosis process is created, and the correspondence is uploaded to the brand diagnosis process code and vehicle model code mapping database. Then create a database that maps brand entry codes to vehicle model codes;

[0046] Based on the obtained vehicle model code and part number information, a correspondence is created between the vehicle model code and the existing repair item code, and this correspondence is uploaded to the brand item code and vehicle model code mapping database. The repair item code is set according to the repair attribute (e.g., replacement, disassembly, etc.) code + part number rule of the installed parts.

[0047] Create a database mapping brand entry code - part number - sub-product system number - work hour code - work hour name;

[0048] Based on the parts loading list, the developed maintenance items, and the work hour list, create a correspondence between maintenance item codes, part numbers, sub-product system numbers, work hour codes, and work hour names, and upload this correspondence to the brand item code-part number-sub-product system number-work hour code-work hour name mapping database.

[0049] Create a database mapping brand entry codes to tool unit codes;

[0050] Based on the developed maintenance items and maintenance tool units, create a correspondence between maintenance item codes and the maintenance tool unit codes involved in the maintenance items, and upload the created correspondence to the brand item code and tool unit code mapping database.

[0051] Step 4: Based on Step 2, obtain various deliverable process data packages, find and output the corresponding time data packages, and generate the associated data packages of maintenance item-part-time, maintenance item-spare part exploded view, maintenance item tool unit, diagnostic unit, flowchart link-diagnostic unit, and fault diagnosis-maintenance item-spare part list-maintenance time data packages. Step 4, the generation of the associated data package for maintenance items, parts, and work hours, includes: Export the data from the brand exploded diagram and spare parts list, maintenance process data (excluding the tool unit library involved in the brand maintenance items), and fault diagnosis data (excluding the brand diagnosis unit library) in step 2 that have been developed and uploaded to the database according to the deliverable file code, and generate various deliverable process data packages; Work time data package generation method: Based on brand and vehicle model information, find and output the corresponding work time data package.

[0052] The methods for generating the associated data packages for maintenance items, parts, and work hours, and the associated data packages for maintenance items and spare parts exploded views in step 4 include: In step 1, the existing deliverable catalog is searched and retrieved from the deliverable catalog framework library; based on the deliverable catalog code and the same encoded field in the deliverable data package, the deliverable data is associated with the standard catalog framework of the corresponding deliverable type. Using the maintenance item codes in the maintenance manual catalog framework, each item is compared with the brand item code-part number-sub-product system number-work hour code-work hour name in step 3 to find its associated sub-product system number, part number, and work hour code in the relational database. The associated sub-product system number is obtained. The associated data package containing maintenance item codes, sub-product system spare parts exploded views, and sub-product system spare parts details is searched and generated in the deliverable data package. This allows the view of the exploded views and spare parts details of the corresponding parts from the parts in the maintenance item content. Based on the associated work hour code, the system searches and generates an associated data package containing maintenance item-sub-product system number-part number-work hour-work hour code-work hour name-work hour quota data in the work hour data package. This allows users to view the maintenance work hour information of the corresponding part from the part associated with the maintenance item content.

[0053] The method for generating a maintenance item tool unit data package includes: the system searches for the tool unit code in the tool unit library related to the brand maintenance item in step 3, and then searches for the tool unit code in the tool unit library of the brand maintenance item in step 3 based on the found tool unit code, and generates a maintenance item tool unit data package, so as to realize the viewing of the corresponding maintenance tool information associated with the parts in the maintenance item content.

[0054] The diagnostic unit data packet generation method includes: the system searches for and generates a diagnostic unit data packet in the brand diagnostic unit library in step 3 based on the diagnostic unit code associated with the diagnostic process file in the deliverable data packet in step 3.

[0055] The method for generating a flowchart-diagnostic unit data package includes: taking the diagnostic unit codes associated with each flowchart step in the diagnostic process related to the content elements of the "Fault Phenomenon Table" or "Fault Code Table" in the fault diagnosis directory, searching for the corresponding diagnostic unit files in the diagnostic unit data package of step 3 one by one, generating and outputting a flowchart-diagnostic unit link relationship data package containing the flowchart step-diagnostic unit link relationship, and realizing the fault diagnosis flowchart cause determination associated query diagnostic unit.

[0056] The method for generating a data package associated with fault diagnosis, repair items, spare parts details, and repair man-hours includes: based on the preset correspondence between brand, vehicle model, main sales location, and language, searching and retrieving existing deliverable catalogs from the deliverable catalog framework library in step 3. The deliverable data is then associated with the deliverable catalog based on the same coded field as the deliverable catalog code in the deliverable data package from step 3.

[0057] By determining the associated work hour code through the diagnostic process cause in the diagnostic process file of the deliverable data package, the corresponding maintenance item code, sub-product system number, part number, work hour name, and work hour quota are found in the associated data package of maintenance item-part-work hour in step 3.

[0058] By using the sub-product system number + part number information found above, the corresponding part's loading quantity is searched in the associated data package of maintenance item - spare parts exploded view in step 3. A fault diagnosis - maintenance item - spare parts details - maintenance time association data package is generated, which contains the relationship between fault cause determination, maintenance item, part number, part name, part loading quantity, work hour code, work hour name, and work hour quota. This enables the fault diagnosis process to be associated with the query of maintenance process, maintenance time, and spare parts drawing information.

[0059] Step 5: Generate the vehicle after-sales manual based on the data package obtained in Step 4.

[0060] The standalone PC application uploads the various data packages generated in step 3 to the standalone PC application and generates a standalone interactive automotive after-sales manual. This enables interactive queries of information such as viewing repair time information for corresponding parts from the repair item content, viewing exploded views and spare parts details for corresponding parts from the repair item content, viewing corresponding repair tool information from the repair item content, querying diagnostic units related to fault diagnosis flowcharts and causes, and querying repair processes, repair time, and spare parts diagrams related to fault diagnosis process causes.

[0061] This invention discloses a standalone interactive automotive after-sales manual development method. It constructs a deliverable catalog framework library, a vehicle model labor hour database, a brand exploded view spare parts detail library, a repair process database, and a fault diagnosis database. It creates interactive relationships between deliverable data elements, automatically generates delivery data packages by searching the delivery database, and quickly generates a standalone automotive after-sales manual. This allows for interactive information queries, including viewing repair hour information for corresponding parts from repair item content, viewing exploded views and spare parts details for corresponding parts from repair item content, viewing corresponding repair tool information from repair item content, querying diagnostic units related to fault diagnosis flowcharts and cause determination, and querying repair processes, repair hours, and spare parts diagram information related to fault diagnosis process cause determination.

[0062] Compared with existing technologies, the stand-alone interactive automotive after-sales manual development method of the present invention can automatically generate the manual without the need for internet access, and can quickly locate the required information. It has low development cost and high efficiency, and is easy to promote and use on a large scale.

[0063] Finally, the method described in this application is merely a preferred embodiment and is not intended to limit the scope of protection of this invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for developing a standalone interactive automotive after-sales manual, characterized in that, Includes the following steps: Step 1: Create a corresponding delivery item catalog framework library based on the brand, vehicle model, and delivery item type information in the order; Step 2: Create a vehicle model labor hour database, a brand exploded view spare parts list database, a repair process database, and a fault diagnosis database; Step 3: Create a database that maps brand vehicle codes to sub-product system numbers, a database that maps brand diagnostic process codes to vehicle codes, a database that maps brand entry codes to vehicle codes, a database that maps brand entry codes to part numbers to sub-product system numbers to work hour codes to work hour names, and a database that maps brand entry codes to tool unit codes. Step 4: Based on Step 2, obtain various deliverable process data packages, find and output the corresponding work hour data packages according to brand and vehicle model information, and generate the associated data packages of repair item-parts-work hours, repair item-spare part exploded view, repair item tool unit, diagnostic unit, flowchart link-diagnostic unit, and fault diagnosis-repair item-spare part details-repair work hour. Step 5: Generate the vehicle after-sales manual based on the data package obtained in Step 4.

2. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, In step 1, the deliverables catalog framework library includes the names of each level of the catalog in the manual, the catalog name codes, the hierarchical relationship between each level of the catalog, and the order in which files at the same level are stored. Furthermore, the catalog name code is validated when the deliverable type information is entered.

3. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 2, the creation of the vehicle model time database, includes: based on the parts assembly list, measuring the time quotas for the time names corresponding to each assembled part to form a vehicle model time list, and then reviewing and uploading the developed vehicle model time list to the vehicle model time database.

4. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 2, creating the brand exploded view spare parts list library, includes: Based on the parts loading list, the assembly drawings of each part are processed according to the sub-product system to obtain the exploded view of the sub-product system in SVG format. Based on the parts assembly information of each sub-product system, obtain a table-style spare parts list for each sub-product system. Name the exploded view of the sub-product system and the spare parts list of the sub-product system according to the sub-product system number, and upload them to the brand exploded view and spare parts list library.

5. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, The maintenance process database mentioned in step 2 includes a brand maintenance item library, a brand maintenance item tool unit library, a brand system overview unit library, a brand precautions unit library, a brand technical parameter unit library, a brand maintenance tool unit library, and a brand system component description unit library; Furthermore, the creation of the maintenance process database in step 2 includes, Based on the development materials and deliverables catalog framework, establish development tasks for the overview content, precautions content, technical parameters content, maintenance tools content, and maintenance items content under each chapter of the catalog framework. According to the development task, the data of each manual is developed separately. The developed maintenance item files, tool unit files involved in the maintenance items, system overview files, precaution files, technical parameter files, maintenance tool files, and system component description files are coded and uploaded to the maintenance process database.

6. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 2, the creation of the fault diagnosis database, includes a brand diagnostic process library, a brand diagnostic tool unit library, a brand system function introduction unit library, a brand control unit terminal diagram unit library, a brand used vehicle inspection unit library, a brand fault phenomenon table unit library, and a brand fault code table unit library. Step 2, the creation of the fault diagnosis database, includes: Based on the development materials and deliverables catalog framework, establish development tasks for diagnostic processes, diagnostic unit content involved in the diagnostic processes, system function introduction content, diagnostic parameter content, control unit terminal diagram, on-vehicle inspection content, fault phenomenon content, and fault code content under each chapter in the catalog framework library. According to the development task, the data of each manual are developed separately. The developed diagnostic process, diagnostic tools, system function introduction, diagnostic parameters, control unit terminal diagram, on-vehicle inspection, fault phenomenon table and fault code table are coded and uploaded to the fault diagnosis database.

7. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 3 specifically includes: Based on the brand and vehicle model, obtain the fault diagnosis path and assign it a code, create a correspondence between the vehicle model code and the diagnostic process code of the developed diagnostic process, and upload the correspondence to the brand diagnostic process code and vehicle model code mapping database. Based on the obtained vehicle model code and part number information, create a correspondence between the vehicle model code and the existing repair item code, and upload the correspondence to the brand item code and vehicle model code mapping database; Based on the parts loading list, the developed maintenance items, and the work hour list, create a correspondence between maintenance item code, part number, sub-product system number, work hour code, and work hour name, and upload this correspondence to the brand item code-part number-sub-product system number-work hour code-work hour name mapping database. Based on the developed maintenance items and maintenance tool units, create a correspondence between maintenance item codes and the maintenance tool unit codes involved in the maintenance items, and upload this correspondence to the brand item code and tool unit code mapping database.

8. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 4, the generation of the associated data package for maintenance items, parts, and work hours, includes: In step 1, the existing deliverable catalog is searched and retrieved from the deliverable catalog framework library; based on the deliverable catalog code and the same encoded field in the deliverable data package, the deliverable data is associated with the standard catalog framework of the corresponding deliverable type. Using the maintenance item codes in the maintenance manual catalog framework, one by one, go to the brand item code-part number-sub-product system number-work hour code-work hour name in step 3 and look up the associated sub-product system number, part number, and work hour code in the relational database to obtain the associated sub-product system number. Then, search for and generate an associated data package containing maintenance item codes, sub-product system spare parts exploded diagrams, and sub-product system spare parts details in the deliverable data package. Based on the associated work hour code, search in the work hour data package and generate an associated data package containing maintenance item-part-work hour, sub-product system number-part number-work hour code-work hour name-work hour quota data.

9. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 4, the generation of the maintenance entry tool unit data package, includes: Based on the repair item codes in the tool unit library related to the brand repair item, the tool unit codes are searched in the brand item code and tool unit code mapping database. Then, the tool unit codes are searched in the brand repair item tool unit library based on the found tool unit codes, and a repair item tool unit data package is generated. Step 4, the flowchart section – diagnostic unit data package generation – includes: For each step in the flowchart of the diagnostic process associated with the content elements of the "Fault Phenomenon Table" or "Fault Code Table" in the fault diagnosis directory, the corresponding diagnostic unit code is searched in the diagnostic unit data package one by one, and the corresponding diagnostic unit file is generated and output as a flowchart step-diagnostic unit link relationship data package containing the flowchart step-diagnostic unit link relationship.

10. The method for developing a standalone interactive automotive after-sales manual as described in claim 1, characterized in that, Step 4, the generation of the Fault Diagnosis - Repair Items - Spare Parts List - Repair Time Association Data Package, includes: Based on the preset correspondence between brand, vehicle model, main sales location, and language, the existing delivery catalog is searched and retrieved from the delivery catalog framework library. Associate the deliverable data with the deliverable catalog based on the same encoded field in the deliverable data package; The diagnostic process cause in the diagnostic process file of the deliverable data package is used to determine the associated work hour code, and then the corresponding maintenance item code, sub-product system number, part number, work hour name, and work hour quota are searched in the associated data package of maintenance item-part-work hour. By finding the sub-product system number and part number information, the corresponding part's installation quantity is found in the associated data package of maintenance item-spare part exploded view, and a fault diagnosis-maintenance item-spare part detail-maintenance time association data package is generated. This data package contains fault cause determination, maintenance item, part number, part name, part installation quantity, work hour code, work hour name, and work hour quota association relationship.

Images