An automobile after-sales document development route automatic generation method and system

Abstract

The application discloses an automobile after-sales document development route automatic generation method and system, relates to the automobile after-sales market technical document development field, and the method comprises the following steps: constructing a development route element library, a development route element relationship library, an auxiliary information library and a delivery product development standard element library; after receiving new project information, the system automatically matches historical data based on the delivery product standard elements of the new project information through intelligent recommendation rules, selects optimal element characteristics for each element factor, and automatically generates a complete development route containing associated information such as operation steps, division of labor, preconditions and risk points. The application realizes the automatic and standardized generation of the development route, overcomes the defects of large manual preparation workload, difficult risk identification and non-optimal path selection, and significantly improves the development efficiency and project management level.

Description

Technical Field

[0001] This invention relates to the field of automotive aftermarket technical document development, and in particular to a method and system for automatically generating automotive aftermarket document development roadmaps. Background Technology

[0002] In the development of technical documentation for the automotive aftermarket, a development roadmap is a crucial management tool. It defines the specific workflows, methods, steps, and standards that must be followed from project initiation to the completion of the final deliverable, guiding the project team to conduct development work efficiently and compliantly.

[0003] Currently, traditional development roadmap development methods in the industry primarily rely on the personal experience and subjective judgment of individual developers. The specific process involves senior technical personnel manually creating a project development roadmap that includes various development stages such as development preparation, content development, translation, and integration, along with their corresponding tasks. This traditional manual method has several significant drawbacks and limitations:

[0004] 1. The compilation process is arduous and highly dependent on personnel: Because the development roadmap needs to cover the entire chain from data collection, content creation, review to delivery, involving numerous stages and complex details, the workload for manual compilation is enormous. At the same time, this method places extremely high demands on the professional skills of the compilers, requiring them to have a comprehensive and in-depth understanding of the entire document development process, the specific requirements of various brand clients, and potential risks. Once key personnel leave, historical development knowledge is difficult to pass on and preserve.

[0005] 2. Difficulty in accurately identifying and controlling development risks: Under manual compilation, the identification of potential risks during development, such as delayed data delivery, misunderstandings of technical standards, and changes in customer requirements, relies mainly on individual experience and lacks systematic analysis based on massive amounts of historical data. This identification method is often incomplete and inaccurate, easily overlooking key risks and leading to rework, project delays, and unnecessary cost waste in the later stages of the project.

[0006] 3. It is difficult to accurately adopt the optimal path with the lowest cost and lowest development risk based on the actual needs of project development.

[0007] In conclusion, existing development roadmap development methods, which rely on human experience, are no longer sufficient to meet the increasingly sophisticated, standardized, and efficient management needs of the modern automotive aftermarket in terms of efficiency, accuracy, risk control, and optimization capabilities. Therefore, the industry urgently requires a solution that can automate and intelligently generate development roadmaps to overcome these shortcomings. Summary of the Invention

[0008] The purpose of this invention is to overcome the shortcomings of the prior art and provide a method and system for automatically generating automotive aftermarket document development routes. Through systematic knowledge base construction and intelligent recommendation algorithms, the development routes are standardized and automatically generated, effectively reducing reliance on manpower, improving the accuracy and scientific nature of route planning, and enabling proactive control of development risks.

[0009] To achieve the above objectives, the present invention provides the following technical solution:

[0010] In a first aspect, the present invention provides a method for automatically generating automotive aftermarket documentation development roadmaps, comprising the following steps:

[0011] Construct a development route element library, which is used to store structured data of deliverable development routes and development route element information;

[0012] Construct a development route element relationship library to store the association and mutual exclusion relationships between the development route element factors and between the element features;

[0013] Construct an auxiliary information database and establish a connection with the development route element database. The auxiliary information database includes at least one of the following: a task allocation database for storing task allocation information, a prerequisite database for storing task prerequisites, a customer management taboo information database for storing customer management taboos, and a task risk point database for storing task risk points.

[0014] Construct a deliverable development standard element library to store development standard element information for each deliverable category. The development standard element information includes development standard element factors and corresponding element features.

[0015] Receive project information for a new project, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information for the new project, retrieve the corresponding development stage, work category, and development route element factors from the development route element library;

[0016] Based on the development standard elements of the deliverables of the new project and in conjunction with the pre-set recommendation rules, matching element features are automatically recommended from the development route element library for each development route element factor.

[0017] Based on the recommended combination of feature elements, the development roadmap for the new project is automatically generated, and auxiliary information associated with the development roadmap is output simultaneously; the approved development roadmap is stored in the development roadmap feature library.

[0018] As a further aspect of the present invention, constructing a development roadmap element library includes the following steps:

[0019] Organize the required task categories for each development stage according to the deliverables and development phases;

[0020] Based on the aforementioned task categories, identify the development path factors that influence the development path and development costs, and construct the corresponding element characteristics for each of the aforementioned development path factors based on historical project development models.

[0021] Define corresponding work steps for each work category based on the aforementioned feature characteristics;

[0022] The deliverables, development stages, job categories, development route element factors, element characteristics, and job steps are associated, stored, and uploaded to the development route element library.

[0023] As a further aspect of the present invention, according to the deliverable category and development stage, the required task categories for each development stage are sorted out, and the development order dependency coding is set for the task categories to determine the development order or parallel development order between different task categories.

[0024] As a further aspect of the present invention, constructing a development route element relationship library also includes:

[0025] The system automatically verifies the compliance of the element factors and element features uploaded or configured in the development route element relationship library by using the pre-set association and mutual exclusion relationships of the development route element factors and element features. When a specific element feature is selected for a certain element factor, the system automatically selects the associated element features according to the association relationship, or hides the mutually exclusive element features according to the mutual exclusion relationship.

[0026] As a further aspect of the present invention, the information in the auxiliary information database is associated with the feature characteristics of the work category items in the development route element database.

[0027] As a further aspect of the present invention, a standard element library for deliverable development is constructed, including:

[0028] Based on the category of deliverables, the information of each development standard element in the deliverable development standards of historical partner brands is extracted manually.

[0029] Based on the extracted development standard element information, create development route element factor names, development standard element factor element characteristics, element characteristic descriptions, and applicable brands, and store them in the deliverable development standard element library.

[0030] As a further aspect of the present invention, the recommendation rules include:

[0031] If a new project and a previous project share the same brand, deliverable category, and deliverable development standards, then the features of the most recent previous project should be prioritized.

[0032] If a new project and a historical project share the same brand and deliverable category but have different deliverable development standards, then the historical project with the most identical deliverable development standard elements to the new project should be given priority in recommendation.

[0033] If a new project and a previous project are from different brands but have the same deliverable category, the features of the most recent previous project should be recommended first.

[0034] As a further aspect of the present invention, a development roadmap for the new project is automatically generated based on a recommended combination of element features, and auxiliary information associated with the development roadmap is output synchronously. The synchronously output auxiliary information includes at least one of the following:

[0035] The information on the division of labor between Party A and Party B, retrieved from the task assignment database, the information on prerequisites retrieved from the prerequisite database, the information on customer management prohibitions retrieved from the customer management prohibition information database, and the information on task risk points retrieved from the task risk point database; wherein, the automatically generated development route and associated auxiliary information are displayed on the front end in tabular form.

[0036] Secondly, the present invention also provides an automatic generation system for automotive aftermarket document development roadmaps, comprising:

[0037] The development route element library is used to store structured data of deliverable development routes and development route element information;

[0038] A development route element relationship library, connected to the development route element library, is used to store the association and mutual exclusion relationships between the development route element factors and between the element features;

[0039] An auxiliary information database, connected to the development route element database, is used to store auxiliary management information associated with work category items. The auxiliary information database includes at least one of the following: a work assignment database, a prerequisite database, a customer management taboo information database, and a work risk point database.

[0040] The deliverable development standard element library is used to store development standard element information for each deliverable category;

[0041] The route recommendation engine is configured to: receive project information for new projects, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information, match relevant work category items and development route element factors from the development route element library; and automatically select element features for each development route element factor based on preset recommendation rules, according to the deliverable development standard elements and by invoking the association and mutual exclusion relationships in the development route element relationship library.

[0042] The route generation module, connected to the route recommendation engine and the auxiliary information database, is configured to: generate a development route for the new project based on the combination of feature elements selected by the route recommendation engine, and synchronously acquire and output auxiliary management information associated with the development route from the auxiliary information database.

[0043] As a further aspect of the present invention, the development route element library also stores development order dependency codes set for the task categories, which are used to define the development sequence or parallel development sequence between different task categories.

[0044] As a further embodiment of the present invention, the development route element relationship library is further configured to: automatically perform compliance checks on the element factors and element features in the development route element library; when a specific element feature is selected for a certain element factor, automatically enable the associated element feature according to the association relationship, or disable the mutually exclusive element feature according to the mutual exclusion relationship.

[0045] As a further aspect of the present invention, the pre-defined recommendation rules in the route recommendation engine include:

[0046] If a new project and a previous project share the same brand, deliverable category, and deliverable development standards, then the features of the most recent previous project should be prioritized.

[0047] If a new project and a historical project share the same brand and deliverable category but have different deliverable development standards, then the historical project with the most identical deliverable development standard elements to the new project should be given priority in recommendation.

[0048] If a new project and a previous project are from different brands but have the same deliverable category, the features of the most recent previous project should be recommended first.

[0049] As a further embodiment of the present invention, the route generation module is also configured to display the generated development route and associated auxiliary management information in a table format on the front-end interface, and to save the approved development route back to the development route element library.

[0050] Compared with existing technologies, the present invention provides a method and system for automatically generating automotive aftermarket documentation development roadmaps, which has the following advantages:

[0051] The present invention relates to an automatic method and system for generating automotive aftermarket documentation development routes. By automatically retrieving knowledge base data and using intelligent recommendation rules to generate development routes, it completely changes the traditional model that relies on manual compilation by senior technical personnel. This liberates developers from the heavy and repetitive work of route compilation, resulting in an order-of-magnitude improvement in compilation efficiency. By constructing a development route element library and a deliverable development standard element library, it transforms the implicit project development experience scattered in individuals' minds into reusable and iterative structured digital assets for the enterprise.

[0052] This invention also establishes a database of operational risk points and associates it with the characteristics of specific operational categories. The system can automatically output various operational risk points that may exist under the project path when generating a development route, achieving systematic and comprehensive risk identification. Binding risk warnings to specific operational steps allows project teams to clearly understand potential problems during the planning phase. Intelligent recommendations based on historical project data and pre-set optimization rules make the generated development route more closely aligned with actual project needs, and more scientific and feasible. Through a development route element relationship database, the system automatically handles the associations and mutual exclusions between element factors, avoiding logical errors and technical conflicts that may occur with manual selection, ensuring the inherent rationality and feasibility of the recommended path, thereby assisting in selecting the development path with the optimal cost and lowest risk.

[0053] This invention, while generating a development roadmap, can automatically associate and output key management information such as the division of labor between the client and contractor, prerequisites, and customer management taboos. It not only solves the core pain points of traditional manual compilation methods, such as low efficiency, uncontrollable risks, and difficulty in optimization, but also transforms the compilation of development roadmaps from a method that relies on personal experience into a replicable, optimizable, and controllable scientific process through systematic and intelligent means. This significantly improves the management level, quality assurance, and overall efficiency of automotive aftermarket technical document development projects.

[0054] These or other aspects of the invention will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0055] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. In the drawings:

[0056] Figure 1 This is a flowchart illustrating an automatic generation method for automotive aftermarket documentation development roadmap according to the present invention.

[0057] Figure 2 This is a flowchart illustrating the construction of a development route element library in an automatic generation method for automotive aftermarket documentation development routes according to the present invention.

[0058] Figure 3 This is a flowchart illustrating the construction of a standard element library for deliverable development in an automatic generation method for automotive aftermarket documentation development roadmap according to the present invention.

[0059] Figure 4 This is a structural block diagram of an automatic generation system for automotive aftermarket documentation development roadmap, as described in this invention. Detailed Implementation

[0060] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings, but it should be understood that the scope of protection of the present invention is not limited to the specific embodiments.

[0061] Unless otherwise expressly stated, throughout the specification and claims, the term "comprising" or its variations such as "including" or "comprises" shall be understood to include the stated elements or components without excluding other elements or other components.

[0062] like Figure 1 As shown, one embodiment of the present invention provides a method for automatically generating automotive aftermarket documentation development roadmaps, comprising the following steps:

[0063] Step S10: Construct a development route element library, which is used to store structured data of deliverable development routes and development route element information.

[0064] In this embodiment, as Figure 2 As shown, building a development roadmap element library includes the following steps:

[0065] Step S101: According to the deliverables and development stages, sort out the work categories required for each development stage.

[0066] In this step, according to the deliverables such as user manuals, maintenance manuals, circuit diagrams, and fault diagnosis, and the development stages such as development preparation, content development, manual translation, manual integration, and first draft delivery, the tasks required for each development stage are manually sorted out. For example, the tasks in the development preparation stage include product maturity assessment, maintenance of the data requirements list, preprocessing of development data, and creation of the manual catalog framework.

[0067] Step S102: According to the work category, sort out the development route element factors that affect the development route and development cost, and construct the element characteristics corresponding to each development route element factor based on the historical project development model.

[0068] In this step, when identifying development path factors that affect the development path and development costs, factors such as product validation location and whether development is outsourced should be identified.

[0069] When constructing the feature characteristics corresponding to each of the development route element factors, for the element factor being a product verification location, feature characteristics such as "on-site verification, third-party verification on business trip, and local verification" can be constructed; for the element factor being outsourced development, feature characteristics such as "customer-designated outsourcing, self-outsourcing, and no outsourcing" can be constructed.

[0070] Step S103: Define the corresponding work steps for each work category based on the element characteristics.

[0071] Step S104: Associate the deliverables, development stages, work categories, development route element factors, element characteristics, and work steps, and store and upload them to the development route element library.

[0072] In this step, according to the deliverable category and development stage, the required task categories for each development stage are sorted out, and the development order dependency coding for the task categories is also included to determine the development order or parallel development order between different task categories.

[0073] Step S20: Construct a development route element relationship library to store the association and mutual exclusion relationships between the development route element factors and between the element features.

[0074] In this step, by setting development sequence dependency codes, the order of development or parallel development of different job categories is determined for job category items uploaded to the development route element library according to brand and deliverable category.

[0075] In this embodiment, constructing the development route element relationship library also includes:

[0076] The system automatically verifies the compliance of the element factors and element features uploaded or configured in the development route element relationship library by using the pre-set association and mutual exclusion relationships of the development route element factors and element features. When a specific element feature is selected for a certain element factor, the system automatically selects the associated element features according to the association relationship, or hides the mutually exclusive element features according to the mutual exclusion relationship.

[0077] In this step, the conformity verification of the development route element factors and feature uploaded to the development route element library is automatically performed by calling the pre-set association and mutual exclusion relationship tables in the development route element relationship library. The association and mutual exclusion relationship tables are created separately according to association or mutual exclusion relationships, and the tables contain one or more pairs of element factors or feature that have association or mutual exclusion relationships.

[0078] For example, development roadmap elements include deliverable source file format requirements and operating software, which are mutually exclusive and related.

[0079] When the feature selection in the deliverable source file format requirement is set to FM format, the database will automatically select the feature selection in the job software as FrameMaker, indicating that there is a relationship.

[0080] When the feature selection in the deliverable source file format requirement is set to Word format, the feature selections FrameMaker and Arbortext in the database automation software are masked, meaning they are mutually exclusive.

[0081] Step S30: Construct an auxiliary information database and establish an association with the development route element database. The auxiliary information database includes at least one of the following: a job assignment database for storing job assignment information, a prerequisite database for storing job prerequisites, a customer management taboo information database for storing customer management taboos, and a job risk point database for storing job risk points.

[0082] In this embodiment, the information in the auxiliary information database is associated with the feature characteristics of the work category items in the development route element database.

[0083] The system includes a task assignment database to store the division of labor between Party A and Party B for corresponding tasks during the development of historical projects. It also establishes a relationship between the brand's division of labor between Party A and Party B and the characteristics of task categories within the development route element database. Specifically, the system manually creates the corresponding division of labor between Party A and Party B for task categories within the development route element database.

[0084] A prerequisite database is created to store the prerequisites for corresponding brand-specific tasks during the development of historical projects, i.e., the preparatory work required for each task. The relationship between brand prerequisites and task category element characteristics is established in the development roadmap element database. Specifically, prerequisites for task category element characteristics are manually created in the development roadmap element database; however, it is not required that all task category element characteristics have prerequisites.

[0085] A customer management taboo information database is created to store management taboos for corresponding brand customers during the historical project development process. In the development roadmap element database, a relationship is established between brand customer management taboos and task category element characteristics. For example, during data collection, a customer management taboo might be "Unauthorized forwarding is prohibited." In the development roadmap element database, customer management taboos corresponding to task category element characteristics are manually created. Note that not all task category element characteristics have customer management taboos.

[0086] A task risk point database is created to store task risks that existed during the historical project development process. The association between task risk points and task category element characteristics is established in the development route element library. Specifically, task risk points corresponding to task category element characteristics are manually created in the development route element library; not all task category element characteristics have task risk points.

[0087] Step S40: Construct a deliverable development standard element library to store development standard element information for each deliverable category. The development standard element information includes development standard element factors and corresponding element features.

[0088] In this embodiment, as Figure 3 As shown, a standard element library for deliverable development is constructed, including:

[0089] Step S401: According to the deliverable category, manually extract the information of each development standard element from the deliverable development standards of historical cooperative brands.

[0090] In this step, the deliverable standard is composed of multiple development standard element factors in the information of each development standard element in the deliverable standard.

[0091] Step S402: Based on the extracted development standard element information, create the development route element factor name, development standard element factor element characteristics, element characteristic description, and applicable brand, and store them in the deliverable development standard element library.

[0092] In this step, the names of development route element factors include cover style, development layout, directory structure, image format, etc., and the element characteristics of standard element factors include development layout: horizontal 164mm×106mm, vertical 154mm×210mm, etc.

[0093] Step S50: Receive project information for a new project, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information for the new project, retrieve the corresponding development stage, work category, and development route element factors from the development route element library.

[0094] Step S60: Based on the development standard elements of the deliverables of the new project and in conjunction with the preset recommendation rules, automatically recommend matching element features for each development route element factor from the development route element library.

[0095] In this step, based on the new project's brand information and deliverable category information, the system automatically retrieves development stage information, task category information, development route element factors, and development sequence dependency coding information from the development route element library. Based on the new project's deliverable development standard element information, and the association and mutual exclusion relationships between element factors and element features, the system automatically recommends element features under each element factor. The recommendation rules include:

[0096] If a new project and a previous project share the same brand, deliverable category, and deliverable development standards, then the features of the most recent previous project should be prioritized.

[0097] If a new project and a historical project share the same brand and deliverable category but have different deliverable development standards, then the historical project with the most identical deliverable development standard elements to the new project should be given priority in recommendation.

[0098] If a new project and a previous project are from different brands but have the same deliverable category, the features of the most recent previous project should be recommended first.

[0099] The system automatically outputs the development roadmap for new projects based on recommended combinations of features, along with information on the division of labor between the client and vendors, prerequisites, client management restrictions, and operational risks. The approved development roadmap is then stored in a table format in the development roadmap element library and can be displayed on the front end, thus completing the full recommendation and activation of development roadmaps for each deliverable category under the new project.

[0100] Step S70: Based on the recommended combination of element features, automatically generate the development route of the new project and simultaneously output auxiliary information associated with the development route; store the approved development route in the development route element library.

[0101] In this step, a development roadmap for the new project is automatically generated based on the recommended combination of feature elements, and auxiliary information associated with the development roadmap is output synchronously. This synchronously output auxiliary information includes at least one of the following:

[0102] The information on the division of labor between Party A and Party B, retrieved from the task assignment database, the information on prerequisites retrieved from the prerequisite database, the information on customer management prohibitions retrieved from the customer management prohibition information database, and the information on task risk points retrieved from the task risk point database; wherein, the automatically generated development route and associated auxiliary information are displayed on the front end in tabular form.

[0103] The present invention relates to an automatic method and system for generating automotive aftermarket documentation development routes. By automatically retrieving knowledge base data and using intelligent recommendation rules to generate development routes, it completely changes the traditional model that relies on manual compilation by senior technical personnel. This liberates developers from the heavy and repetitive work of route compilation, resulting in an order-of-magnitude improvement in compilation efficiency. By constructing a development route element library and a deliverable development standard element library, it transforms the implicit project development experience scattered in individuals' minds into reusable and iterative structured digital assets for the enterprise.

[0104] See Figure 4 As shown, another embodiment of the present invention also provides an automatic generation system for automotive aftermarket document development roadmaps, which includes:

[0105] The development route element library is used to store structured data of deliverable development routes and development route element information;

[0106] A development route element relationship library, connected to the development route element library, is used to store the association and mutual exclusion relationships between the development route element factors and between the element features;

[0107] An auxiliary information database, connected to the development route element database, is used to store auxiliary management information associated with work category items. The auxiliary information database includes at least one of the following: a work assignment database, a prerequisite database, a customer management taboo information database, and a work risk point database.

[0108] The deliverable development standard element library is used to store development standard element information for each deliverable category;

[0109] The route recommendation engine is configured to: receive project information for new projects, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information, match relevant work category items and development route element factors from the development route element library; and automatically select element features for each development route element factor based on preset recommendation rules, according to the deliverable development standard elements and by invoking the association and mutual exclusion relationships in the development route element relationship library.

[0110] The route generation module, connected to the route recommendation engine and the auxiliary information database, is configured to: generate a development route for the new project based on the combination of feature elements selected by the route recommendation engine, and synchronously acquire and output auxiliary management information associated with the development route from the auxiliary information database.

[0111] In this embodiment, the development route element library also stores development order dependency codes set for the task category items, which are used to define the development sequence or parallel development sequence between different task categories items.

[0112] The development route element relationship library is also configured to: automatically perform compliance checks on the element factors and element features in the development route element library; when a specific element feature is selected for a certain element factor, automatically enable the associated element feature according to the association relationship, or disable the mutually exclusive element feature according to the mutual exclusion relationship.

[0113] In this embodiment, the preset recommendation rules in the route recommendation engine include:

[0114] If a new project and a previous project share the same brand, deliverable category, and deliverable development standards, then the features of the most recent previous project should be prioritized.

[0115] If a new project and a historical project share the same brand and deliverable category but have different deliverable development standards, then the historical project with the most identical deliverable development standard elements to the new project should be given priority in recommendation.

[0116] If a new project and a previous project are from different brands but have the same deliverable category, the features of the most recent previous project should be recommended first.

[0117] The route generation module is also configured to display the generated development route and associated auxiliary management information in a table format on the front-end interface, and to save the approved development route back to the development route element library.

[0118] This invention establishes a database of operational risk points and associates it with the characteristics of specific operational categories. The system can automatically output various potential operational risk points along the project path when generating a development route, achieving systematic and comprehensive risk identification. By linking risk warnings to specific operational steps, the project team can clearly understand potential problems during the planning phase. Intelligent recommendations based on historical project data and pre-defined optimization rules ensure that the generated development route is closer to the actual project needs, making it more scientific and feasible. Through a development route element relationship database, the system automatically handles the associations and mutual exclusions between element factors, avoiding logical errors and technical conflicts that may occur with manual selection, ensuring the inherent rationality and feasibility of the recommended path, and thus assisting in selecting the development path with the optimal cost and lowest risk.

[0119] This invention, while generating a development roadmap, can automatically associate and output key management information such as the division of labor between the client and contractor, prerequisites, and customer management taboos. It not only solves the core pain points of traditional manual compilation methods, such as low efficiency, uncontrollable risks, and difficulty in optimization, but also transforms the compilation of development roadmaps from a method that relies on personal experience into a replicable, optimizable, and controllable scientific process through systematic and intelligent means. This significantly improves the management level, quality assurance, and overall efficiency of automotive aftermarket technical document development projects.

[0120] The foregoing description of specific exemplary embodiments of the invention is for illustrative and explanatory purposes. These descriptions are not intended to limit the invention to the precise forms disclosed, and it will be apparent that many changes and variations can be made in accordance with the foregoing teachings. The exemplary embodiments were chosen and described in order to explain the specific principles of the invention and its practical application, thereby enabling those skilled in the art to implement and utilize various different exemplary embodiments of the invention, as well as various different choices and variations. The scope of the invention is intended to be defined by the claims and their equivalents.

Claims

1. A method for automatically generating automotive aftermarket documentation development roadmaps, characterized in that, Includes the following steps: Construct a development route element library, a development route element relationship library, an auxiliary information library, and a deliverable development standard element library. The auxiliary information library is associated with the development route element library. The auxiliary information library includes at least one of the following: a task allocation library for storing task allocation information, a prerequisite library for storing task prerequisites, a customer management prohibitions information library for storing customer management prohibitions, and a task risk point database for storing task risk points. Receive project information for a new project, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information for the new project, retrieve the corresponding development stage, work category, and development route element factors from the development route element library; Based on the development standard elements of the deliverables of the new project and in conjunction with the pre-set recommendation rules, matching element features are automatically recommended from the development route element library for each development route element factor. Based on the recommended combination of feature elements, the development roadmap for the new project is automatically generated, and auxiliary information associated with the development roadmap is output simultaneously; the approved development roadmap is stored in the development roadmap feature library.

2. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 1, characterized in that, Building a development roadmap element library includes the following steps: Organize the required task categories for each development stage according to the deliverables and development phases; Based on the aforementioned task categories, identify the development path factors that influence the development path and development costs, and construct the corresponding element characteristics for each of the aforementioned development path factors based on historical project development models. Define corresponding work steps for each work category based on the aforementioned feature characteristics; The deliverables, development stages, job categories, development route element factors, element characteristics, and job steps are associated, stored, and uploaded to the development route element library.

3. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 2, characterized in that, Based on the deliverable category and development stage, the task categories required for each development stage are sorted out, and the development order dependency coding for the task categories is also included to determine the development order or parallel development order between different task categories.

4. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 1, characterized in that, Construct a development roadmap element relationship library, including: The system automatically verifies the compliance of the element factors and element features uploaded or configured in the development route element relationship library by using the pre-set association and mutual exclusion relationships of the development route element factors and element features. When a specific element feature is selected for a certain element factor, the system automatically selects the associated element features according to the association relationship, or hides the mutually exclusive element features according to the mutual exclusion relationship.

5. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 1, characterized in that, Construct a standard element library for deliverable development, including: Based on the category of deliverables, the information of each development standard element in the deliverable development standards of historical partner brands is extracted manually. Based on the extracted development standard element information, create development route element factor names, development standard element factor element characteristics, element characteristic descriptions, and applicable brands, and store them in the deliverable development standard element library.

6. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 1, characterized in that, The recommendation rules include: If a new project and a previous project share the same brand, deliverable category, and deliverable development standards, then the features of the most recent previous project should be prioritized. If a new project and a historical project share the same brand and deliverable category but have different deliverable development standards, then the historical project with the most identical deliverable development standard elements to the new project should be given priority in recommendation. If a new project and a previous project are from different brands but have the same deliverable category, the features of the most recent previous project should be recommended first.

7. The method for automatically generating automotive aftermarket documentation development roadmap as described in claim 1, characterized in that, Based on the recommended combination of feature elements, a development roadmap for the new project is automatically generated, and auxiliary information associated with the development roadmap is output synchronously. This synchronously output auxiliary information includes at least one of the following: The information on the division of labor between Party A and Party B, retrieved from the task assignment database, the information on prerequisites retrieved from the prerequisite database, the information on customer management prohibitions retrieved from the customer management prohibition information database, and the information on task risk points retrieved from the task risk point database; wherein, the automatically generated development route and associated auxiliary information are displayed on the front end in tabular form.

8. An automatic generation system for automotive aftermarket documentation development roadmap, characterized in that, The system for automatically generating automotive aftermarket documentation development roadmaps as described in any one of claims 1-7 is configured to perform the steps of such method. The development route element library is used to store structured data of deliverable development routes and development route element information; A development route element relationship library, connected to the development route element library, is used to store the association and mutual exclusion relationships between the development route element factors and between the element features; An auxiliary information database, connected to the development route element database, is used to store auxiliary management information associated with work category items. The auxiliary information database includes at least one of the following: a work assignment database, a prerequisite database, a customer management taboo information database, and a work risk point database. The deliverable development standard element library is used to store development standard element information for each deliverable category; The route recommendation engine is configured to: receive project information for new projects, which includes at least brand, deliverable category, and deliverable development standard elements; based on the project information, match relevant work category items and development route element factors from the development route element library; and automatically select element features for each development route element factor based on preset recommendation rules, according to the deliverable development standard elements and by invoking the association and mutual exclusion relationships in the development route element relationship library. The route generation module, connected to the route recommendation engine and the auxiliary information database, is configured to: generate a development route for the new project based on the combination of feature elements selected by the route recommendation engine, and synchronously acquire and output auxiliary management information associated with the development route from the auxiliary information database.

9. The automatic generation system for automotive aftermarket documentation development roadmap as described in claim 8, characterized in that, The development route element library also stores development sequence dependency codes set for the task categories, which are used to define the development sequence or parallel development sequence between different task categories.

10. The automatic generation system for automotive aftermarket documentation development roadmap as described in claim 9, characterized in that, The development route element relationship library is also configured to: automatically perform compliance checks on the element factors and element features in the development route element library; when a specific element feature is selected for a certain element factor, automatically enable the associated element feature according to the association relationship, or disable the mutually exclusive element feature according to the mutual exclusion relationship.

Images