Whole vehicle file design method and device, electronic equipment, storage medium and BOM system

Abstract

The invention discloses a whole vehicle file design method and device, electronic equipment, a storage medium and a BOM system, and relates to the field of vehicle production. According to the vehicle demand information, a deliverable is generated and added into a whole vehicle document package; driving a vehicle production process according to the whole vehicle document package so as to meet vehicle requirements; wherein the Coze platform is used for central scheduling and automatic verification; the central scheduling of the Coze platform comprises the steps of performing task decomposition, bill of material triggering, risk analysis triggering and document generation triggering on the vehicle demand information based on a Coze central scheduling Agent; the central scheduling of the Coze platform further comprises the steps of calling a knowledge base based on the automatic verification Agent, carrying out BOM verification, risk verification and drawing compliance detection, and feeding back a verification conclusion to the Coze central scheduling Agent; wherein according to a conclusion that the BOM verification, the risk verification and the drawing compliance detection pass, a deliverable document package is correspondingly generated and added into the whole vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle production, and in particular to vehicle design methods, vehicle design devices, electronic equipment, storage media, and BOM systems. Background Technology

[0002] In the current state of vehicle design management, in order to quickly respond to market demands, engineers face the heavy task of assembling vehicle documents. The existing EBOM system is inefficient, which adds a lot of burden to vehicle designers, and these tasks are also routine processes.

[0003] Therefore, a solution for whole vehicle document design is needed to improve work efficiency. For example, it is possible to improve efficiency by using intelligent agents, or to use web crawling technology to accurately conduct market insights and quickly build whole vehicle BOM and design documents based on market demand. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle design method, a vehicle design device, an electronic device, a storage medium, and a BOM system, at least to solve the technical problem of how to accurately conduct market insights and how to quickly build a vehicle BOM and design documents based on market demand.

[0005] This invention provides the following solution:

[0006] According to a first aspect of the present invention, a vehicle document design method is provided, the vehicle document design method comprising:

[0007] Obtain vehicle demand information;

[0008] Based on vehicle requirement information, generate deliverables and add them to the vehicle documentation package;

[0009] Based on the complete vehicle documentation package, drive the vehicle production process to meet vehicle requirements;

[0010] in,

[0011] The Coze platform is used for central scheduling and automated verification;

[0012] The Coze platform's central dispatching includes, based on the Coze Central Dispatch Agent, performing task decomposition, bill of materials triggering, risk analysis triggering, and document generation triggering based on vehicle demand information;

[0013] The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent.

[0014] Based on the conclusion that the BOM verification, risk verification, and drawing compliance inspection have all passed, the corresponding deliverables are added to the vehicle documentation package.

[0015] Furthermore, obtaining vehicle demand information includes:

[0016] Obtain original requirement statements from multiple information sources;

[0017] Based on the corresponding information sources and original requirement statements, multiple requirement analysis results are generated;

[0018] This includes building a requirements analysis agent;

[0019] The corresponding information sources and original requirement statements are imported into the requirement parsing agent for analysis, generating vehicle requirement information.

[0020] Furthermore, the construction of the requirement parsing agent includes the following steps: constructing multi-format parsing, constructing conflict detection, and constructing output;

[0021] in,

[0022] The construction of the multi-format parser includes extracting text information based on web crawlers;

[0023] Based on the text information, NLP extracts key parameter information;

[0024] Key parameter information includes key parameters related to battery life and voltage platform;

[0025] in,

[0026] The construction of conflict detection includes acquiring a knowledge base;

[0027] The knowledge base includes records that are validated by calling the knowledge base based on the rule engine;

[0028] The verification includes verifying that the battery capacity matches the curb weight;

[0029] in,

[0030] The output of the construction includes a matrix of structured requirement information;

[0031] Get Formula ;

[0032] Priority calculation is performed based on the formula;

[0033] in,

[0034] This indicates the charm attribute;

[0035] This indicates the expected attribute;

[0036] This indicates a required attribute;

[0037] I indicates an indifferent attribute;

[0038] This indicates priority.

[0039] Furthermore, building the BOM generation agent includes the following steps: establishing a data pipeline, establishing a rule engine, a parts recommendation engine, and real-time change management.

[0040] in,

[0041] The establishment of the data pipeline includes connecting the Coze platform with EBOM and JFBOM to ensure real-time acquisition of existing file data and cost information;

[0042] The cost calculation formula is as follows:

[0043] ;

[0044] in,

[0045] BasePrice indicates the supplier's quote;

[0046] LeadTime indicates the delivery date;

[0047] MOQ stands for Minimum Order Quantity.

[0048] OrderQty represents the order quantity;

[0049] Indicates cost;

[0050] in,

[0051] Establish a rules engine to prevent BOM errors;

[0052] The rules engine includes matching rules related to the engine, motor, transmission, axle, and cab.

[0053] in,

[0054] A parts recommendation engine is used to support and drive vehicle production.

[0055] The parts recommendation engine involves scoring parts based on parameters such as matching degree, reliability, and supplier stability to drive parts recommendations.

[0056] in,

[0057] Real-time change management, used for document changes and document design;

[0058] Change management involves requirements analysis, including:

[0059] Based on the analysis of requirements information, changes are made to the documents and new documents are designed.

[0060] Furthermore, the process of building a BOM to generate an agent includes the following steps: building a DFMEA analysis agent;

[0061] Building a DFMEA analysis agent includes constructing a failure mode knowledge base;

[0062] The failure mode knowledge base includes knowledge cases of failure scenarios for automotive parts;

[0063] This also includes industry standard integration information;

[0064] Industry standard integration information includes clauses of ISO 26262 / SAE J1739 standard;

[0065] Based on the loaded ISO 26262 / SAE J1739 standard clauses, key requirements are extracted using Coze's preset document parsing plugin;

[0066] This also includes building an expert database;

[0067] Preventive measures are generated based on an expert database;

[0068] Based on preventative measures, the testing and verification system is integrated to evaluate and predict these measures.

[0069] Furthermore, technical documentation is used to generate an agent;

[0070] Building a technical documentation-generated agent includes data integration;

[0071] Data integration includes data integration with the CREO, Catia, and AutoCAD systems;

[0072] Based on the data integration to meet vehicle requirements, 3D and 2D drawings are generated;

[0073] This also includes constructing constraint rules;

[0074] The constraint rules include dimensional constraints, material constraints, motion constraints, and weight constraints.

[0075] This also includes building a data association system;

[0076] Building a data association system includes generating two-dimensional data based on three-dimensional drawings and annotating them, and then associating them with the already generated BOM.

[0077] According to a second aspect of the present invention, a vehicle document design apparatus is provided, the vehicle document design apparatus comprising:

[0078] The vehicle demand information module is used to obtain vehicle demand information;

[0079] The vehicle documentation package module is used to generate deliverables and add them to the vehicle documentation package based on vehicle requirement information;

[0080] Based on the complete vehicle documentation package, drive the vehicle production process to meet vehicle requirements;

[0081] in,

[0082] The Coze platform module is used for central scheduling and automated verification.

[0083] The Coze platform's central scheduling includes task decomposition, bill of materials triggering, risk analysis triggering, and document generation triggering based on the Coze Central Scheduling Agent;

[0084] The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent.

[0085] The deliverable generation module is used to generate corresponding deliverables and add them to the vehicle documentation package based on the conclusions that the BOM verification, risk verification, and drawing compliance inspection have all passed.

[0086] According to a third aspect of the present invention, an electronic device is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0087] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the vehicle document design method.

[0088] According to a fourth aspect of the present invention, a computer-readable storage medium is provided storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the vehicle document design method.

[0089] According to a fifth aspect of the present invention, a BOM system is provided, comprising:

[0090] Electronic equipment for implementing the steps of the vehicle file design method;

[0091] The processor runs a program, and when the program runs, it executes the steps of the vehicle file design method based on data output from the electronic device.

[0092] A storage medium for storing a program that, when running, executes the steps of the vehicle file design method on data output from an electronic device.

[0093] The above solution achieves the following beneficial technical effects:

[0094] This application makes full use of the design of intelligent agents to improve the efficiency of the whole vehicle business process.

[0095] This application utilizes web crawling technology to accurately understand the market and quickly build the complete vehicle BOM and design documents based on market demand. Attached Figure Description

[0096] Figure 1 This is a flowchart of a vehicle document design method provided by one or more embodiments of the present invention.

[0097] Figure 2 This is a structural diagram of a vehicle document design device provided by one or more embodiments of the present invention.

[0098] Figure 3 This is a schematic diagram of a vehicle business intelligent agent architecture provided in a specific embodiment of the present invention.

[0099] Figure 4 This is a structural block diagram of an electronic device provided by one or more embodiments of the present invention for a vehicle document design method. Detailed Implementation

[0100] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0101] Figure 1 This is a flowchart of a vehicle document design method provided by one or more embodiments of the present invention.

[0102] like Figure 1 The complete vehicle document design method shown includes:

[0103] Step S1: Obtain vehicle demand information;

[0104] Step S2: Based on the vehicle requirement information, generate deliverables and add them to the vehicle documentation package;

[0105] Step S3: Drive the vehicle production process based on the complete vehicle documentation package to meet vehicle requirements;

[0106] Step S31: The Coze platform is used for central scheduling and automated verification;

[0107] The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent.

[0108] Step S32: Based on the conclusion that the BOM verification, risk verification, and drawing compliance inspection have all passed, the corresponding deliverables are generated and added to the vehicle documentation package.

[0109] Specifically, the Coze platform (a one-stop AI development platform) performs central scheduling by decomposing vehicle demand information into tasks (decomposing R&D and production tasks to meet customer needs), triggering bill of materials (a list of vehicle parts), triggering risk analysis (analyzing the risks in vehicle R&D and failure modes), and triggering document generation (generating project process documents such as design schemes).

[0110] In this embodiment, obtaining vehicle demand information includes:

[0111] Obtain original requirement statements from multiple information sources;

[0112] Based on the corresponding information sources and original requirement statements, multiple requirement analysis results are generated;

[0113] This includes building a requirements analysis agent;

[0114] The corresponding information sources and original requirement statements are imported into the requirement parsing agent for analysis, generating vehicle requirement information.

[0115] In this embodiment, building the demand parsing agent includes the following steps: building a multi-format parser, building a conflict detection mechanism, and building the output.

[0116] in,

[0117] The construction of multi-format parsing includes extracting text information based on web crawlers;

[0118] Based on the text information, NLP extracts key parameter information;

[0119] Key parameter information includes key parameters related to battery life and voltage platform;

[0120] in,

[0121] Building a conflict detection system includes acquiring a knowledge base;

[0122] The knowledge base includes records that are validated by calling the knowledge base based on the rule engine;

[0123] The verification includes verifying that the battery capacity matches the curb weight;

[0124] in,

[0125] The output includes a matrix of structured requirement information;

[0126] Get Formula ;

[0127] Priority calculation is performed based on the formula;

[0128] in,

[0129] This indicates the charm attribute;

[0130] This indicates the expected attribute;

[0131] This indicates a required attribute;

[0132] I indicates an indifferent attribute;

[0133] This indicates priority.

[0134] In this embodiment, building the BOM generation agent includes the following steps: establishing a data pipeline, establishing a rule engine, a parts recommendation engine, and real-time change management.

[0135] in,

[0136] Establishing a data pipeline includes connecting the Coze platform with EBOM and JFBOM to ensure real-time access to existing file data and cost information;

[0137] The cost calculation formula is as follows:

[0138] ;

[0139] in,

[0140] BasePrice: Supplier's quote;

[0141] LeadTime: Delivery date;

[0142] MOQ stands for Minimum Order Quantity.

[0143] OrderQty represents the order quantity;

[0144] EBOM: Design Document Management System;

[0145] JFBOM: Production Document Management System;

[0146] in,

[0147] Establish a rules engine to prevent BOM errors;

[0148] The rules engine includes matching rules related to the engine, motor, transmission, axle, and cab.

[0149] in,

[0150] A parts recommendation engine is used to support and drive vehicle production.

[0151] The parts recommendation engine involves scoring parts based on parameters such as matching degree, reliability, and supplier stability to drive parts recommendations.

[0152] in,

[0153] Real-time change management, used for document changes and document design;

[0154] Change management involves requirements analysis, including:

[0155] Based on the analysis of requirements information, changes are made to the documents and new documents are designed.

[0156] Specifically, EBOM is a design document management system; JFBOM is a production document management system.

[0157] In this embodiment, constructing the BOM to generate the agent includes the step of constructing a DFMEA analysis agent;

[0158] Building a DFMEA analysis agent includes constructing a failure mode knowledge base;

[0159] The failure mode knowledge base includes knowledge cases of failure scenarios for automotive parts;

[0160] This also includes industry standard integration information;

[0161] Industry standard integration information includes clauses of ISO 26262 / SAE J1739 standard;

[0162] Based on the loaded ISO 26262 / SAE J1739 standard clauses, key requirements are extracted using Coze's preset document parsing plugin;

[0163] This also includes building an expert database;

[0164] Preventive measures are generated based on an expert database;

[0165] Based on preventative measures, the testing and verification system is integrated to evaluate and predict these measures.

[0166] In this embodiment, a technical document is constructed to generate an Agent;

[0167] Building a technical documentation-generated agent includes data integration;

[0168] Data integration includes data integration with the CREO, Catia, and AutoCAD systems;

[0169] Based on the data integration to meet vehicle requirements, 3D and 2D drawings are generated;

[0170] This also includes constructing constraint rules;

[0171] The constraint rules include dimensional constraints, material constraints, motion constraints, and weight constraints.

[0172] This also includes building a data association system;

[0173] Building a data association system includes generating two-dimensional data based on three-dimensional drawings and annotating them, and then associating them with the already generated BOM.

[0174] Specifically, in this application, the requirement analysis agent plays the role of an intelligent requirement hub in the automated design of vehicle documents. Its core value lies in transforming fragmented and vague human language into precise and executable engineering parameters, as shown in the embodiments in Table 1, breaking down departmental barriers and unifying the requirement language.

[0175] Table 1

[0176] department Original requirements statement Agent parsing results Marketing Department "Charging is as fast as refueling." Fast charging 10%-80% in ≤15 minutes Management "Costs to be kept under 250,000" BOM cost ≤ 185,000 (including tax)

[0177] In this application, the agile way to respond to market changes is to use web crawlers to crawl commercial vehicle industry websites and quickly output market demand and market competitor benchmarking reports.

[0178] This application also involves a BOM generation agent, such as calling the JFBOM system via a REST API to build the complete vehicle BOM. This allows for rapid changes based on market demand while supporting real-time material pricing. (Test data: response time <200ms)

[0179] In one specific embodiment, such as Figure 3 Under the intelligent agent architecture of the whole vehicle business shown, a strategy is formed to complete the whole vehicle documents and drive the vehicle production process.

[0180] 1. Construct a requirement analysis agent:

[0181] Multi-format parsing: Web crawler / uploaded PDF / Word document / → NLP extraction of key parameters (battery life, voltage platform, etc.).

[0182] Conflict detection: Call the rule engine for verification; (e.g., "battery capacity" vs. "curb weight")

[0183] Output: A structured requirements matrix, with priorities calculated according to the following formula:

[0184] ;

[0185] Parameter description:

[0186] A: Charm attribute;

[0187] O: Expected attribute;

[0188] M: Required attribute;

[0189] I: Indifferent attribute;

[0190] Priority;

[0191] 2. Construct BOM to generate Agent:

[0192] Establish data pipelines: Connect COZE with EBOM and JFBOM to ensure real-time access to existing file data and costs;

[0193] The cost calculation formula is as follows:

[0194]

[0195] Parameter description:

[0196] BasePrice: Supplier's quote;

[0197] LeadTime: Delivery date;

[0198] MOQ: Minimum Order Quantity;

[0199] OrderQty: Number of orders;

[0200] :cost;

[0201] Establish a rule engine (core error prevention): such as matching rules related to the engine, motor, transmission, axle, and cab.

[0202] Parts recommendation engine: This engine scores parts based on various dimensions such as parameter matching, reliability, and supplier stability to achieve parts recommendation.

[0203] Real-time change management: Through automated requirements analysis upstream, changes are made to documents and new documents are designed.

[0204] 3. Construct a DFMEA analysis agent:

[0205] Build a failure mode knowledge base: pre-set 2000+ failure scenarios for automotive parts (such as motor overheating code FMEA-2023-MOT).

[0206] Industry standard integration: Automatically loads standard clauses such as ISO 26262 / SAE J1739 and extracts key requirements through Coze (a one-stop artificial intelligence development platform).

[0207] Build an expert database: Automatically generate preventive measures through the expert database, connect with the testing and verification system, and evaluate and predict the preventive measures.

[0208] 4. Build a technical documentation generation agent:

[0209] Data integration: Integrates with CREO, Catia, and AutoCAD systems to generate existing 3D and 2D drawings according to requirements;

[0210] Construct constraint rules: Construct size constraints, material constraints, motion constraints, and weight constraints;

[0211] Build a data association system: automatically generate 2D data from 3D data and label it, and associate it with the already generated BOM.

[0212] In the above embodiments, the demand analysis agent uses web crawling technology to quickly obtain real-time market information and generate a functional demand matrix, ensuring agile market response.

[0213] The BOM generation agent uses different dimensions such as parameter matching degree, reliability, and supplier stability to construct an intelligent parts recommendation algorithm for components, and accurately generates BOMs.

[0214] The DFMEA analysis agent uses a BERT+BiLSTM hybrid model to predict failure modes and constructs automatic part generation constraints in accordance with existing failure modes.

[0215] Figure 2 This is a structural diagram of a vehicle document design device provided by one or more embodiments of the present invention.

[0216] like Figure 2 The vehicle design document unit shown includes: a vehicle requirements information module, a vehicle document package module, and a Coze platform module;

[0217] The vehicle demand information module is used to obtain vehicle demand information;

[0218] The vehicle documentation package module is used to generate deliverables and add them to the vehicle documentation package based on vehicle requirement information;

[0219] Based on the complete vehicle documentation package, drive the vehicle production process to meet vehicle requirements;

[0220] in,

[0221] The Coze platform module is used for central scheduling and automated verification.

[0222] The Coze platform's central scheduling includes task decomposition, bill of materials triggering, risk analysis triggering, and document generation triggering based on the Coze Central Scheduling Agent;

[0223] The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent.

[0224] The deliverable generation module is used to generate corresponding deliverables and add them to the vehicle documentation package based on the conclusions that the BOM verification, risk verification, and drawing compliance inspection have all passed.

[0225] It is worth noting that although this system / device only discloses the vehicle demand information module, the whole vehicle documentation package module, and the Coze platform module, it does not mean that this device is limited to the above-mentioned basic functional modules. On the contrary, what this invention intends to express is that, based on the above-mentioned basic functional modules, those skilled in the art can add one or more functional modules in combination with existing technology to form an infinite number of embodiments or technical solutions. That is to say, this system / device is open rather than closed. It should not be assumed that the scope of protection of the claims of this invention is limited to the above-disclosed basic functional modules just because this embodiment only discloses a few basic functional modules.

[0226] Figure 4 This is a structural block diagram of an electronic device provided by one or more embodiments of the present invention for a vehicle document design method.

[0227] like Figure 4 As shown, this application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0228] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the vehicle design method.

[0229] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the vehicle design method.

[0230] This application also provides a BOM system, including:

[0231] Electronic devices used to implement the steps of the vehicle design methodology;

[0232] The processor runs programs, and when the program runs, it executes the steps of the vehicle design method based on data output from electronic devices.

[0233] Storage medium used to store programs that, when running, execute the steps of the vehicle file design method on data output from electronic devices.

[0234] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0235] The electronic device comprises a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory. The operating system can be any one or more computer operating systems that control the electronic device through processes, such as Linux, Unix, Android, iOS, or Windows. Furthermore, in this embodiment of the invention, the electronic device can be a smartphone, tablet computer, or other handheld device, or a desktop computer, portable computer, or other electronic device; there is no particular limitation in this embodiment.

[0236] In this embodiment of the invention, the executing entity for electronic device control can be an electronic device itself, or a functional module within an electronic device capable of calling and executing a program. The electronic device can obtain the firmware corresponding to the storage medium. This firmware is provided by the supplier, and different storage media may have the same or different firmware; no limitation is made here. After obtaining the firmware corresponding to the storage medium, the electronic device can write this firmware into the storage medium; specifically, it burns the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented using existing technology, and will not be elaborated upon in this embodiment of the invention.

[0237] Electronic devices can also obtain reset commands corresponding to the storage media. The reset commands corresponding to the storage media are provided by the supplier. The reset commands corresponding to different storage media can be the same or different, and no restrictions are imposed here.

[0238] At this time, the storage medium of the electronic device is a storage medium on which the corresponding firmware has been written. The electronic device can respond to the reset command corresponding to the storage medium on which the corresponding firmware has been written, thereby resetting the storage medium on which the corresponding firmware has been written according to the reset command. The process of resetting the storage medium according to the reset command can be implemented by existing technology and will not be described in detail in this embodiment of the invention.

[0239] For ease of description, the above devices are described separately by function as various units and modules. Of course, in implementing this application, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0240] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined.

[0241] For the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0242] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0243] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for designing complete vehicle documentation, characterized in that, The vehicle document design method includes: Obtain vehicle demand information; Based on vehicle requirement information, generate deliverables and add them to the vehicle documentation package; Based on the complete vehicle documentation package, drive the vehicle production process to meet vehicle requirements; in, The Coze platform is used for central scheduling and automated verification; The Coze platform's central dispatching includes, based on the Coze Central Dispatch Agent, performing task decomposition, bill of materials triggering, risk analysis triggering, and document generation triggering based on vehicle demand information; The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent. Based on the conclusion that the BOM verification, risk verification, and drawing compliance inspection have all passed, the corresponding deliverables are added to the vehicle documentation package.

2. The vehicle document design method according to claim 1, characterized in that, The acquisition of vehicle demand information includes: Obtain original requirement statements from multiple information sources; Based on the corresponding information sources and original requirement statements, multiple requirement analysis results are generated; This includes building a requirements analysis agent; The corresponding information sources and original requirement statements are imported into the requirement parsing agent for analysis, generating vehicle requirement information.

3. The vehicle design method according to claim 1, characterized in that, The construction requirement parsing agent includes the following steps: construction multi-format parsing, construction conflict detection, and construction output; in, The construction of the multi-format parser includes extracting text information based on web crawlers; Based on the text information, NLP extracts key parameter information; Key parameter information includes key parameters related to battery life and voltage platform; in, The construction of conflict detection includes acquiring a knowledge base; The knowledge base includes records that are validated by calling the knowledge base based on the rule engine; The verification includes verifying that the battery capacity matches the curb weight; in, The output of the construction includes a matrix of structured requirement information; Get Formula ; Priority calculation is performed based on the formula; in, This indicates the charm attribute; This indicates the expected attribute; This indicates a required attribute; I indicates an indifferent attribute; This indicates priority.

4. The vehicle document design method according to claim 1, characterized in that, Building a BOM generation agent includes the following steps: establishing a data pipeline, establishing a rules engine, a parts recommendation engine, and real-time change management. in, The establishment of the data pipeline includes connecting the Coze platform with EBOM and JFBOM to ensure real-time acquisition of existing file data and cost information; The cost calculation formula is as follows: ； in, BasePrice indicates the supplier's quote; LeadTime indicates the delivery date; MOQ stands for Minimum Order Quantity. OrderQty represents the order quantity; Indicates cost; in, Establish a rules engine to prevent BOM errors; The rules engine includes matching rules related to the engine, motor, transmission, axle, and cab. in, A parts recommendation engine is used to support and drive vehicle production. The parts recommendation engine involves scoring parts based on parameters such as matching degree, reliability, and supplier stability to drive parts recommendations. in, Real-time change management, used for document changes and document design; Change management involves requirements analysis, including: Based on the analysis of requirements information, changes are made to the documents and new documents are designed.

5. The vehicle document design method according to claim 1, characterized in that, Building a BOM to generate an agent includes the following steps: building a DFMEA analysis agent; Building a DFMEA analysis agent includes constructing a failure mode knowledge base; The failure mode knowledge base includes knowledge cases of failure scenarios for automotive parts; This also includes industry standard integration information; Industry standard integration information includes clauses of ISO 26262 / SAE J1739 standard; Based on the loaded ISO 26262 / SAE J1739 standard clauses, key requirements are extracted using Coze's preset document parsing plugin; This also includes building an expert database; Preventive measures are generated based on an expert database; Based on preventative measures, the testing and verification system is integrated to evaluate and predict these measures.

6. The vehicle document design method according to claim 1, characterized in that, Build technical documentation to generate an agent; Building a technical documentation-generated agent includes data integration; Data integration includes data integration with the CREO, Catia, and AutoCAD systems; Based on the data integration to meet vehicle requirements, 3D and 2D drawings are generated; This also includes constructing constraint rules; The constraint rules include dimensional constraints, material constraints, motion constraints, and weight constraints. This also includes building a data association system; Building a data association system includes generating two-dimensional data based on three-dimensional drawings and annotating them, and then associating them with the already generated BOM.

7. A vehicle document design device, characterized in that, The vehicle document design device includes: The vehicle demand information module is used to obtain vehicle demand information; The vehicle documentation package module is used to generate deliverables and add them to the vehicle documentation package based on vehicle requirement information; Based on the complete vehicle documentation package, drive the vehicle production process to meet vehicle requirements; in, The Coze platform module is used for central scheduling and automated verification. The Coze platform's central scheduling includes task decomposition, bill of materials triggering, risk analysis triggering, and document generation triggering based on the Coze Central Scheduling Agent; The Coze platform's central dispatch also includes, based on the automated verification agent, retrieving the knowledge base to perform BOM verification, risk verification, drawing compliance checks, and feeding back the verification results to the Coze central dispatch agent. The deliverable generation module is used to generate corresponding deliverables and add them to the vehicle documentation package based on the conclusions that the BOM verification, risk verification, and drawing compliance inspection have all passed.

8. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus are connected, with the processor, communication interface, and memory communicating with each other via the communication bus. The memory stores a computer program that, when executed by a processor, causes the processor to perform the steps of the vehicle document design method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The device stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the vehicle document design method as described in any one of claims 1 to 6.

10. A BOM system, characterized in that, include: An electronic device for implementing the steps of the vehicle document design method as described in any one of claims 1 to 6; A processor that runs a program, and when the program runs, it executes the steps of the vehicle document design method as described in any one of claims 1 to 6 from data output by the electronic device. A storage medium for storing a program that, when run, performs the steps of the vehicle document design method as described in any one of claims 1 to 6 on data output from an electronic device.

Images