Whole vehicle part weight management method and system, electronic equipment and storage medium

Abstract

The invention provides a whole vehicle part weight management method and system, electronic equipment and a storage medium, and relates to the technical field of automobile manufacturing, and the method comprises the steps: estimating a first version BOM table through historical project BOM data, carrying out the comparison at a pre-designed development stage BOM, generating a difference report, and carrying out the calculation of the difference report. Updating the first version BOM table according to the difference report to obtain an optimized second version BOM table; afterwards, the actual weight is further compared in the real object weighing stage, and finally a target BOM version is formed, so that the whole process control of the whole vehicle part weight management is realized, and the consistency, traceability and high accuracy of the whole vehicle part weight data in the whole research and development period are ensured.

Description

Technical Field

[0001] The present application relates to the field of automobile manufacturing technology, and in particular to a method, system, electronic device, and storage medium for weight management of vehicle parts. Background Art

[0002] In recent years, demand for BOM (Bill of Materials) weight management in the lightweighting business of new energy vehicles has grown. Precisely controlling the weight of vehicles and components is crucial for improving range, optimizing energy efficiency, and reducing manufacturing costs. Existing BOM weight management methods primarily rely on manual record-keeping and decentralized data processing. During vehicle and component development, projects have numerous BOM versions and lack a unified management mechanism. Under traditional management models, collaborative processes are complex and data exchange is poor during BOM creation, verification, and updates, leading to error-prone and untimely information transfer, impacting the efficiency and accuracy of vehicle lightweighting development.

[0003] Therefore, in view of the limitations of the existing BOM weight management methods, it is urgent to propose an integrated and standardized BOM weight management method. Summary of the Invention

[0004] In view of the above problems, embodiments of the present application provide a vehicle component weight management method, system, electronic device, and storage medium to overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect of an embodiment of the present application, a method for weight management of vehicle parts is provided, which is applied to a weight management platform. The method includes: Based on the received BOM table of the historical project, estimate the first version of the BOM table of the current project, where the first version of the BOM table includes the first version weight of each component; receiving a development-stage BOM for the current project design, and comparing the first-version BOM with the development-stage BOM to generate a difference report, wherein the difference report is used to indicate weight change information of components that differ between the development-stage BOM and the first-version BOM; updating the first version of the BOM according to the difference report to obtain a second version of the BOM, wherein the second version of the BOM includes a second version of the weight of each component; The third version weight obtained by weighing the components is received, the third version weight of the components is compared with the second version weight, and the second version BOM table is updated based on the comparison result to obtain the target version BOM table.

[0006] Optionally, estimating the first version of the BOM of the current project based on the received BOM of the historical project includes: Obtaining project information of the current project; estimating the weight of each component of the current project based on the BOM table of the historical project and the project information of the current project to obtain the estimated weight of each component; Performing weight simulation tests on each of the components to ensure that each component obtains at least one simulated design weight; The first version of the BOM table is determined based on the simulated design weight and estimated weight corresponding to each of the components.

[0007] Optionally, determining the first version of the BOM table according to the simulated design weight and the estimated weight corresponding to each of the components includes: Obtaining design requirements corresponding to each of the components from the project information; Determining a first version weight corresponding to each component based on the design requirements corresponding to each component, where the first version weight is the weight of the component that has the smallest error from the design requirements among at least one simulated design weight and an estimated weight of the component; The first version BOM table is obtained according to the first version weight of each component.

[0008] Optionally, comparing the first version BOM with the development stage BOM to generate a difference report includes: Comparing the first version weight of each component in the first version BOM with the design weight of the corresponding component in the development stage BOM to obtain weight change information for components with weight differences; The difference report is generated based on the weight change information of the parts with weight differences.

[0009] Optionally, updating the first version BOM table according to the difference report to obtain the second version BOM table includes: Determining weight change information of each component having weight differences based on the difference report; Obtaining the preset weight requirement of the current project; According to the weight requirement and the weight change information of each component with weight difference, the first version weight of each component with weight difference in the first version BOM table is updated to obtain the second version BOM table.

[0010] Optionally, comparing the third version weight of each component with the second version weight, and updating the second version BOM table based on the comparison result to obtain the target version BOM table includes: Comparing the weight of the third version of each component with the weight of the second version, and determining the components in the second version of the BOM that have weight differences; The second version weight of the parts with weight differences is replaced with the corresponding third version weight to obtain the target version BOM table.

[0011] Optionally, the method further includes: Receiving the actual weight of the vehicle obtained by weighing the vehicle; Sum up the weights of the various components in the target version BOM to obtain the vehicle design weight; Comparing the actual weight of the vehicle with the designed weight of the vehicle to obtain a comparison result; If the comparison result satisfies a preset error range, the weight of each component in the target version BOM is determined as the target production weight; If the comparison result does not meet the error range, the third version weight obtained by weighing the various components is re-received, and based on the third version weight of the various components after re-weighing, the weight of each component in the second version BOM table is updated so that the comparison result meets the preset error range.

[0012] In a second aspect of an embodiment of the present application, a vehicle parts weight management system is provided, which is applied to a weight management platform. The weight management system is configured to execute the method according to the first aspect of the present application. The weight management system includes: An estimation module is configured to estimate a first version of the BOM for the current project based on the received BOM for the historical project, where the first version of the BOM includes a first version weight of each component. a report generation module, configured to receive a development-stage BOM table designed for the current project, compare the first-version BOM table with the development-stage BOM table, and generate a difference report, wherein the difference report is used to indicate weight change information of components that differ between the development-stage BOM table and the first-version BOM table; A first updating module is configured to update the first version of the BOM table according to the difference report to obtain a second version of the BOM table, where the second version of the BOM table includes a second version weight of each component; The second update module is used to receive the third version weight obtained by weighing the various components, compare the third version weight of the various components with the second version weight, and update the second version BOM table based on the comparison result to obtain the target version BOM table.

[0013] Optionally, the first version of the BOM table of the current project is estimated based on the received BOM table of the historical project, and the estimation module includes: A first acquisition submodule is used to acquire project information of the current project; A first estimation submodule is configured to estimate the weight of each component of the current project based on the BOM table of the historical project and the project information of the current project to obtain the estimated weight of each component; A test submodule is used to perform weight simulation tests on each of the components, so that each component obtains at least one simulated design weight; The first determining submodule is used to determine the first version of the BOM table according to the simulated design weight and the estimated weight corresponding to each of the components.

[0014] Optionally, the first version of the BOM table is determined according to the simulated design weight and the estimated weight corresponding to each of the components, and the first determining submodule includes: An acquisition subunit, configured to acquire design requirements corresponding to each component from the project information; a first determining subunit, configured to determine a first version weight corresponding to each component according to the design requirements corresponding to each component, wherein the first version weight is the weight of the component that has the smallest error with the design requirements among at least one simulated design weight and an estimated weight of the component; The second determining subunit is configured to obtain the first version BOM table according to the first version weight of each of the components.

[0015] Optionally, the first version BOM table is compared with the development stage BOM table to generate a difference report, and the report generation module includes: A first comparison submodule is configured to compare the first version weight of each component in the first version BOM with the design weight of the corresponding component in the development stage BOM to obtain weight change information of components with weight differences; The generating submodule is used to generate the difference report according to the weight change information of the parts with weight differences.

[0016] Optionally, the updating of the first version BOM table according to the difference report to obtain the second version BOM table, the first updating module includes: A second determining submodule is configured to determine weight change information of each component having a weight difference based on the difference report; A second acquisition submodule is used to obtain the weight requirement preset in the current project; The third determining submodule is used to update the first version weight of each component with weight difference in the first version BOM table according to the weight requirement and the weight change information of each component with weight difference, and obtain the second version BOM table.

[0017] Optionally, the third version weight of each component is compared with the second version weight, and the second version BOM is updated based on the comparison result to obtain the target version BOM, and the second updating module includes: a fourth determining submodule, configured to compare the weight of the third version of each component with the weight of the second version, and determine components in the second version BOM table that have weight differences; The replacement submodule is used to replace the second version weight of the parts with weight differences with the corresponding third version weight to obtain the target version BOM table.

[0018] Optionally, the system further comprises: The receiving submodule is used to receive the actual weight of the vehicle obtained by weighing the vehicle; A summing submodule, configured to sum the weights of the various components in the target version BOM table to obtain the vehicle design weight; A third comparison submodule is used to compare the actual weight of the vehicle with the designed weight of the vehicle to obtain a comparison result; A fifth determining submodule, configured to determine the weight of each component in the target version BOM as the target production weight if the comparison result satisfies a preset error range; an updating submodule, configured to, if the comparison result does not satisfy the error range, re-receive the third version weight obtained by weighing the components, and update the weight of the components in the second version BOM table based on the third version weight of the components after re-weighing, so that the comparison result satisfies the preset error range.

[0019] In a third aspect of an embodiment of the present application, an electronic device is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the vehicle component weight management method as described in the first aspect of the present application are implemented.

[0020] In a fourth aspect of an embodiment of the present application, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the vehicle component weight management method as described in the first aspect of the present application are implemented.

[0021] Beneficial effects of this application: The present application proposes a method for managing the weight of complete vehicle parts. First, based on the BOM table of a received historical project, a first version of the BOM table of the current project is estimated, and the first version of the BOM table includes the first version weight of each component; then, a development stage BOM table designed for the current project is received, and the first version of the BOM table is compared with the development stage BOM table to generate a difference report, and the difference report is used to characterize the weight change information of the components that differ from the development stage BOM table and the first version of the BOM table; then, according to the difference report, the first version of the BOM table is updated to obtain a second version of the BOM table, and the second version of the BOM table includes the second version weight of each component; finally, a third version weight obtained by weighing each component is received, the third version weight of each component is compared with the second version weight, and the second version of the BOM table is updated based on the comparison result to obtain a target version of the BOM table.

[0022] This application estimates the first version of the BOM table through historical project BOM data, compares it with the BOM in the pre-design development stage, generates a difference report, and then updates the first version of the BOM table based on the difference report to obtain an optimized second version of the BOM table; subsequently, during the physical weighing stage, the actual weight is further compared to finally form the target BOM version, which not only realizes the full process control of the vehicle parts weight management, but also ensures the consistency, traceability and high accuracy of the vehicle parts weight data throughout the entire R&D cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1This is a schematic flow chart of the steps of a vehicle parts weight management method provided in an embodiment of the present application; Figure 2 This is a flowchart of a vehicle parts weight management method provided in an embodiment of the present application; Figure 3 This is a timing diagram of a vehicle parts weight management method provided in an embodiment of the present application; Figure 4 This is a schematic diagram of a vehicle parts weight management system provided by an embodiment of the present application; Figure 5 This is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The exemplary embodiments of the present application will be described in more detail below in conjunction with the accompanying drawings in the embodiments of the present application. Although the accompanying drawings show exemplary embodiments of the present application, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0026] In this application, the vehicle development process is divided into three key stages: concept stage, development stage and physical weighing stage.

[0027] Among them, the concept stage is used to represent the stage when the product architecture is initially formed but the details are not yet clear; the development stage is used to represent the stage when the vehicle design team produces basic BOM information as the project progresses, but its completeness and accuracy need to be further improved; the physical weighing stage is used to represent the stage after the physical formation of the vehicle and parts. The first version of the BOM table mentioned in this application is the BOM table generated in the concept stage, the second version of the BOM table is the BOM table generated in the development stage, and the target version of the BOM table is the BOM table generated in the physical weighing stage.

[0028] The vehicle parts weight management method provided in this application is applied to a weight management platform, wherein the weight management platform has built-in multiple functional modules for executing the weight management method described in this application. In addition, in this application, the weight management platform provides a data calculation and processing platform for receiving various weight data and parts information sent by engineers. Among them, in view of the different professional capabilities of engineers and their respective familiar fields, engineers are divided into lightweight groups and professional groups. The lightweight groups and professional groups are used to obtain various data required for this application and upload the data to the weight management platform.

[0029] The lightweight group described in this application is a team specifically responsible for the lightweight design planning of new energy vehicles and the management of weight-related data in the BOM version. Its main responsibilities include creating and updating the weight estimate data in the BOM version at various stages of the project, optimizing the weight design based on the feedback from the professional group, and performing the final freezing operation on the BOM during the physical weighing stage. The professional group is composed of engineers from multiple different professional fields, such as structural engineers, electrical engineers, etc. Among them, the professional group is responsible for verifying the BOM version created by the lightweight group in multiple professional dimensions, evaluating the rationality of the weight data from their respective professional perspectives, and proposing modification opinions and feedback. At the same time, the physical weighing operation and relevant data statistics are carried out during the physical weighing stage.

[0030] In a first aspect of an embodiment of the present application, a method for weight management of vehicle parts is provided, which is applied to a weight management platform. The method includes: Step S101 : For the received BOM table of the historical project, a first version BOM table of the current project is estimated, where the first version BOM table includes the first version weight of each component.

[0031] In this step, the first version of the current project's BOM is estimated through data analysis and empirical modeling based on the received historical project BOMs. The first version weight of each component is also determined. The core goal of this step is to establish a preliminary weight management framework for the current project during the project concept phase, based on historical data and industry standards. This framework provides a reference and optimization foundation for subsequent development phases. In this application, the historical project BOMs were obtained by the lightweighting team and uploaded to the weight management platform.

[0032] In some cases, to ensure the accuracy of the first version of the BOM estimate, you can select a historical vehicle BOM similar to the current project, filter out parts information with a high degree of match, and use it as the basis for weight estimation. In addition, you can also remove inapplicable or obsolete parts information through data cleaning and filtering.

[0033] Step S102: Receive a development stage BOM table designed for the current project, compare the first version BOM table with the development stage BOM table, and generate a difference report, wherein the difference report is used to characterize the weight change information of the parts that differ between the development stage BOM table and the first version BOM table.

[0034] In step S102, the development phase BOM for the current project design is received and compared with the first version BOM, generating a difference report. In this application, the development phase BOM may be designed by a designer and uploaded to the weight management platform. This difference report identifies the differences between the development phase BOM and the first version BOM, specifically including weight difference information for components with weight changes. In some cases, the difference report may also include information on newly added, deleted, or modified components.

[0035] To improve comparison accuracy and efficiency, in some embodiments, intelligent data matching algorithms can be used to automatically identify identical or similar parts based on key attributes such as part ID, material type, and configuration options, and calculate the corresponding weight changes. Multi-dimensional comparisons are also supported, such as categorized analysis by subsystem, material type, and weight change range, allowing lightweighting and specialized teams to quickly identify key changes.

[0036] This step generates a difference report to discover the weight changes of components in the first version of the BOM, thereby providing a decision-making basis for optimizing the first version of the BOM.

[0037] Step S103: updating the first version of the BOM table according to the difference report to obtain a second version of the BOM table, wherein the second version of the BOM table includes the second version weight of each component.

[0038] In step S103, based on the difference report generated in step S102, the first version of the BOM is updated to generate a second version of the BOM, ensuring that the BOM data remains consistent with the current project design status. The updated second version of the BOM contains the latest weight data for all components, namely the second version weight, reflecting the weight adjustments made during the current design phase.

[0039] In some examples, the above steps are repeated over multiple iterations during the development phase until the preset weight accuracy and data stability requirements are met. At this point, the lightweighting team uses the system's permission management function to freeze the final BOM data, generating a final development-stage BOM data version that is archived and backed up as the baseline data for the physical weighing phase.

[0040] In this application, the lightweighting team can create a BOM verification task in the weight management platform and assign it to the professional team. Based on the task requirements and actual development progress, and in conjunction with the difference report, the professional team updates the first version of the BOM to obtain the second version of the BOM. For example, based on the task requirements and actual development progress, and in conjunction with the difference report, the professional team conducts on-site verification of the components in the first version of the BOM and enters the verification results into the weight management platform in real time.

[0041] The lightweighting team regularly reviews the verification progress and feedback from the specialized teams through the weight management platform. Once all specialized teams have completed verification, they conduct a comprehensive review using the platform's built-in audit tools. Upon successful review, the platform automatically generates a second version of the bill of materials (BOM) and synchronizes this update information with the relevant departments. The platform also maintains a version update log, including information such as the update time, content, and updater, for easy traceability and query.

[0042] In some cases, to improve the accuracy and efficiency of the second version BOM update, you can use an automatic data synchronization and version management mechanism and make corresponding adjustments for the following situations: New parts: Add the new parts information in the BOM during the development phase to the second version of the BOM, and enter their material, size, and weight data.

[0043] Delete components: Remove components that have been eliminated or replaced during the development phase to ensure the simplicity and accuracy of the second version of the BOM data.

[0044] Modify component weight: Compare the weight changes identified in the difference report and update the weight data of the corresponding components while retaining the original weight records to support subsequent weight traceability and change management.

[0045] In addition, the weight management platform provided by this application also supports version control and log recording. While updating the BOM data, it stores the weight change information before and after the update to ensure that the specific content of each adjustment can be traced later.

[0046] Step S104: receiving the third version weight obtained by weighing the components, comparing the third version weight of the components with the second version weight, and updating the second version BOM table based on the comparison result to obtain the target version BOM table.

[0047] In step S104, the third version weight of each component is received. The third version weight of each component is the actual weighed weight of each component. This weight is compared with the second version weight in the second version BOM to identify and correct the deviation between the design weight and the actual weight. Finally, the second version BOM is updated based on the comparison results to generate the final target version BOM. In this application, a professional team can weigh each component and upload the third version weight obtained from the weighing of each component to the weight management platform in sequence.

[0048] Through this step, the final weight data of each component is accurately corrected, reducing production and cost risks caused by weight deviations.

[0049] This application estimates the first version of the BOM table through historical project BOM data, compares it with the BOM in the pre-design development stage, generates a difference report, and then updates the first version of the BOM table based on the difference report to obtain an optimized second version of the BOM table; subsequently, during the physical weighing stage, the actual weight is further compared to finally form the target BOM version, which not only realizes the full process control of the vehicle parts weight management, but also ensures the consistency, traceability and high accuracy of the vehicle parts weight data throughout the entire R&D cycle.

[0050] In one embodiment, estimating the first version of the BOM of the current project based on the received BOM of the historical project includes: Obtaining project information of the current project; estimating the weight of each component of the current project based on the BOM table of the historical project and the project information of the current project to obtain the estimated weight of each component; Performing weight simulation tests on each of the components to ensure that each component obtains at least one simulated design weight; The first version of the BOM table is determined based on the simulated design weight and estimated weight corresponding to each of the components.

[0051] In this embodiment, project information of the current project is first obtained, wherein the project information may be design requirements corresponding to the design of each component.

[0052] Then, based on the BOM table of historical projects and combined with the design requirements of the current project, the weight of each component is intelligently estimated.

[0053] In some instances, the following methods can be used to estimate the weight of each component. For example, component data for similar models can be filtered out from historical project BOM tables, such as previous-generation models on the same platform. Components that may be replaced due to design changes or material upgrades can be eliminated to ensure data applicability. In combination with industry standard libraries, missing component data can be supplemented, such as weight information related to new materials or new processes.

[0054] In order to further optimize the estimation accuracy, weight simulation tests are carried out on each component to obtain a simulated design weight that is more in line with the actual situation.

[0055] Ultimately, each component will receive at least one simulated design weight as a reference for weight optimization. After obtaining the simulated design weight of each component, the final first-version BOM table will be determined based on the simulated design weight and estimated weight of all components.

[0056] This embodiment uses the received historical project BOM table, combined with the project information of the current project, to estimate the weight of the components of the current project through data analysis and simulation tests, and finally determines the first version of the BOM table to ensure that the weight management of components in subsequent development stages is accurate and controllable.

[0057] In one embodiment, determining the first version of the BOM table according to the simulated design weight and the estimated weight corresponding to each of the components includes: Obtaining design requirements corresponding to each of the components from the project information; Determining a first version weight corresponding to each component based on the design requirements corresponding to each component, where the first version weight is the weight of the component that has the smallest error from the design requirements among at least one simulated design weight and an estimated weight of the component; The first version BOM table is obtained according to the first version weight of each component.

[0058] In this embodiment, in the process of determining the first version of the BOM table, it is necessary to comprehensively consider the design requirements preset for each component in the current project information, the simulated design weight and the estimated weight of each component to ensure that the selected first version weight meets the design requirements, thereby generating a high-quality first version of the BOM table.

[0059] Specifically, the design requirement described in this embodiment may be a design accuracy requirement for weight error. For each component, the weight that best meets the design accuracy requirement is selected from the simulated design weight and the estimated weight as the first version weight. That is, for each component, the weight error between the simulated design weight and the design accuracy requirement, as well as the weight error between the estimated weight and the design accuracy requirement, are calculated. The simulated design weight or estimated weight with the smallest weight error is selected as the first version weight for that component.

[0060] Finally, after the first version weights of all components are determined, a complete first version BOM is constructed.

[0061] In one embodiment, comparing the first version BOM with the development stage BOM to generate a difference report includes: Comparing the first version weight of each component in the first version BOM with the design weight of the corresponding component in the development stage BOM to obtain weight change information for components with weight differences; The difference report is generated based on the weight change information of the parts with weight differences.

[0062] In this embodiment, the first version weight of each component in the first version BOM is compared with the design weight of the corresponding component in the development stage BOM to identify weight change information, specifically including: If the weight of the component in the development stage BOM is greater than the first version weight in the first version BOM, record the increased weight value and possible reasons.

[0063] For example, if an additional cooling structure is added to the battery pack, resulting in a 5kg weight increase, the change and its impact must be noted in the variance report.

[0064] If the weight of the component in the BOM table during the development phase is less than the weight of the first version in the BOM table of the first version, the reduced weight value and lightweight optimization measures shall be recorded.

[0065] For example, if the chassis suspension uses a new alloy material, which reduces the overall weight by 2.3kg, this optimization item needs to be recorded in the difference report to assess its impact on the overall vehicle quality.

[0066] Finally, based on the above comparison differences, a difference report is generated.

[0067] In some embodiments, each component type in the first version of the BOM may be compared with each component type in the development stage BOM to obtain multiple component types that differ between the development stage BOM and the first version of the BOM, and the difference report may be further optimized and updated based on this. Specifically, each component type in the first version of the BOM is compared with each component type in the development phase BOM to analyze the addition, deletion, or modification of components, including: If there are parts in the BOM during the development phase that are not in the BOM of the first version, they will be marked as newly added and their basic information (such as name, material, design weight, etc.) will be recorded.

[0068] For example, a new car model may add a smart cockpit module, which does not exist in the first version of the BOM table and needs to be marked separately and included in the management.

[0069] If a component in the first version of the BOM disappears in the development stage BOM, it is marked as deleted and the reason for its removal is recorded (such as structural adjustment, component merger, etc.).

[0070] For example, if the new design combines two separate control units into one, the original separate components will be deleted.

[0071] If the material, size or configuration of a component changes, mark it as a modification and record the specific changes.

[0072] For example, if the door outer panel is changed from steel to aluminum alloy, the component type needs to be adjusted and its weight information needs to be updated in subsequent versions.

[0073] This embodiment of the application generates a difference report by comparing the BOM during the development phase with the first version of the BOM. This report provides a basis for decision-making regarding subsequent BOM updates and weight optimization. This report clearly records changes in component type and weight, ensuring traceability of version updates. It also identifies key components with increased weight, allowing for proactive design optimization to prevent vehicle overweight.

[0074] In one embodiment, updating the first version BOM table according to the difference report to obtain the second version BOM table includes: Determining weight change information of each component having weight differences based on the difference report; Obtaining the preset weight requirement of the current project; According to the weight requirement and the weight change information of each component with weight difference, the first version weight of each component with weight difference in the first version BOM table is updated to obtain the second version BOM table.

[0075] In this embodiment, the difference report is first parsed to determine the main differences between the BOM in the development phase and the BOM in the first version, mainly including: weight change information of components with weight differences.

[0076] Before updating the first version of the BOM data, you need to obtain the current project's weight requirements. Based on the current project's weight requirements and the weight change information of the components with weight differences, you can update the first version weight of each component with weight differences in the first version of the BOM to obtain the second version of the BOM.

[0077] In this embodiment, the second version of the BOM is updated based on the first version of the BOM generated in the conceptual stage to obtain the second version of the BOM. The second version of the BOM will serve as the weight management benchmark for the next stage and will be used for subsequent physical weighing comparisons to ensure the management and collaboration of weight data throughout the entire process of lightweight development of new energy vehicles.

[0078] In this embodiment, Table 1 shows a visual display of the aggregate weight of each configuration of the vehicle model according to the statistical project:

[0079] Table 1 In this embodiment, Table 2 shows a visualization of the latest weight of the main control configuration of the current project vehicle model:

[0080] Table 2 In one embodiment, comparing the third version weight of each component with the second version weight, and updating the second version BOM table based on the comparison result to obtain the target version BOM table, includes: Comparing the weight of the third version of each component with the weight of the second version to determine the components in the second version of the BOM that have weight differences; The second version weight of the parts with weight differences is replaced with the corresponding third version weight to obtain the target version BOM table.

[0081] In this embodiment, by comparing the second version weight in the second version BOM table with the third version weight obtained in the physical weighing stage, the components with weight deviations are accurately identified, and the second BOM table is updated accordingly, and finally the target version BOM table is formed to ensure that the final weight data is consistent with the actual manufacturing status.

[0082] For example: Based on the unique identification of the parts (such as part ID, type, etc.), the second version weight is matched with the third version weight one by one, and the weight difference is calculated. If the weight error exceeds the set allowable preset error range, the part is marked as having a weight deviation, and the specific change information is recorded, including the original design weight, the measured weight and the error value. Subsequently, for these parts, the second version weight is directly replaced with the third version weight to ensure that the BOM data can truly reflect the final manufacturing status. At the same time, an update log is generated to record the specific reasons for the change for subsequent optimization and traceability. Ultimately, the target version BOM table serves as the ultimate benchmark for vehicle weight management, ensuring that the lightweight development goals of new energy vehicles are accurately achieved, while improving manufacturing consistency and reducing performance deviations or production adjustment costs caused by weight errors.

[0083] In one embodiment, receiving the actual weight of the entire vehicle obtained by weighing the entire vehicle; Sum up the weights of the various components in the target version BOM to obtain the vehicle design weight; Comparing the actual weight of the vehicle with the designed weight of the vehicle to obtain a comparison result; If the comparison result satisfies a preset error range, the weight of each component in the target version BOM is determined as the target production weight; If the comparison result does not meet the error range, the third version weight obtained by weighing the various components is re-received, and based on the third version weight of the various components after re-weighing, the weight of each component in the second version BOM table is updated so that the comparison result meets the preset error range.

[0084] In this embodiment, a vehicle weighing comparison mechanism ensures that the weight data in the target version BOM of the vehicle is highly consistent with the actual manufacturing status. First, the vehicle weighing data is received, the actual vehicle weight is obtained, and this weight is compared with the vehicle design weight calculated by summing the weights of all components in the target version BOM to assess any deviations in vehicle weight. If the comparison result falls within a preset tolerance (e.g., within ±1%), the component weight data in the target version BOM is confirmed to be accurate and set as the target production weight, serving as the final manufacturing benchmark. In some cases, the target version BOM can be frozen to prevent unauthorized modifications. However, if the comparison result falls outside the tolerance range, it indicates a data deviation, which may be caused by measurement error, material changes, or assembly process issues. In this case, a reweighing process is triggered, requiring all components to be weighed again. The second version BOM is then updated based on the latest third version weight until the comparison result falls within the tolerance range. This method effectively improves the accuracy of vehicle weight management, ensures that lightweighting goals are achieved during mass production, and avoids manufacturing errors and quality risks caused by data inconsistencies.

[0085] In one embodiment, in order to ensure that the target version BOM always maintains data accuracy and consistency during the application process, this application also introduces a change management and intelligent correction mechanism. When the weight of a component changes due to factors such as design changes, process adjustments or supplier changes, the professional group change weight management platform records detailed change information, including component number, change content, change time, change initiator and approver, etc., and synchronizes the weight change value to the target version BOM table. Based on the built-in intelligent correction model, the platform combines mathematical models such as material density and structural size adjustment to automatically correct the design weight of the corresponding components and update historical data records and BOM version information. This mechanism not only ensures that the data referenced by new projects is always accurate, but also effectively reduces development risks and cost overruns caused by weight data deviations, improves the quality stability and cost control capabilities of the entire vehicle, and provides reliable data support for the continuous optimization and precise manufacturing of new energy vehicles.

[0086] In one embodiment, a Figure 2 The flow chart of the vehicle parts weight management method is shown in Figure 2 As shown: Process start: Enter the vehicle parts weight management process to ensure that subsequent development meets lightweighting goals.

[0087] Conceptualization phase: The lightweighting team develops an initial version of the bill of materials (BOM), also known as the first version, and enters the initial weight data for each component type. The professional team reviews the first version of the BOM and provides feedback. If there is room for improvement, adjustments are made and the results are re-verified until confirmation.

[0088] Development Phase: During product development, the Lightweighting Team continuously adjusts and optimizes the first version of the BOM. The Professional Team re-reviews the updated BOM and provides feedback. If further improvements are needed, further revisions and re-verification are conducted to ensure accurate weight control. During the development phase, the Lightweighting Team and the Professional Team, based on the generated difference reports, update the first version of the BOM through the weight management platform to obtain the second version of the BOM. If no update is required, the Lightweighting Team freezes the second version of the BOM to prepare data for weight comparison during the physical weighing phase.

[0089] Physical weighing stage: The professional team conducts physical weighing and enters the actual weighed weight of each component, that is, the third version weight of each component. Combined with the second version BOM table in the development stage, the third version weight of each component is compared with the second version weight of the corresponding component in the second version BOM table to determine whether there is any weight change. If so, the lightweighting team will continue to register the change information until the change information of all components is registered, generate the target version BOM table, traceability chain and related reports, and end the process.

[0090] In one embodiment, a Figure 3 The timing diagram of the vehicle parts weight management method is shown in Figure 3 The vehicle component weight management method shown is divided into three stages: the concept stage, the development stage, and the final physical weighing stage. At each stage, the lightweighting team and the professional team, respectively, use the weight management platform to process component weight data. Specifically: Time sequence 1. Concept stage: Lightweighting Group: Create the first version of the BOM table and enter the first version weight of each component to lay the foundation for subsequent weight management.

[0091] Professional team: Verify the rationality of the first version of the BOM table and provide feedback to ensure data accuracy.

[0092] Weight management platform: provides models or algorithms for data processing, receives feedback and performs data integration.

[0093] Timeline 2, Development Phase: Lightweighting team: First adjust the first version of the BOM table according to the needs to make it more suitable for actual applications, and then generate the second version of the BOM table.

[0094] Professional team: Verify the accuracy of weight data again and update to the second version of BOM table.

[0095] Lightweight Group: After the second version of the BOM is fully updated, freeze the second version of the BOM as the benchmark for subsequent weight management.

[0096] Weight management platform: provides data processing models or algorithms, synchronizes and records weight data changes in real time, and ensures data integrity and traceability.

[0097] Time series 3: Physical weighing stage Professional team: perform physical weighing of the entire vehicle and enter the measured data into the system.

[0098] Weight management platform: provides a data processing model or algorithm, compares the designed weight with the measured weight, analyzes data differences, and evaluates whether the error range is within acceptable limits. It also records information related to weight changes and generates traceability chains and related reports.

[0099] Based on the same inventive concept, the second aspect of the embodiment of the present application provides a vehicle parts weight management system, which is applied to a weight management platform. The weight management system is used to execute the method described in the first aspect of the present application. The weight management system, such as Figure 4 Shown, including: An estimation module 201 is configured to estimate a first version of a BOM for a current project based on a received BOM for a historical project, where the first version of the BOM includes a first version weight of each component. A report generation module 202 is configured to receive a development-stage BOM for the current project design, compare the first-version BOM with the development-stage BOM, and generate a difference report, wherein the difference report is configured to indicate weight change information of components that differ between the development-stage BOM and the first-version BOM; A first updating module 203 is configured to update the first version of the BOM table according to the difference report to obtain a second version of the BOM table, where the second version of the BOM table includes a second version weight of each component; The second update module 204 is used to receive the third version weight obtained by weighing the various components, compare the third version weight of the various components with the second version weight, and update the second version BOM table based on the comparison result to obtain the target version BOM table.

[0100] Optionally, the first version of the BOM table of the current project is estimated based on the received BOM table of the historical project. The estimation module 201 includes: A first acquisition submodule is used to acquire project information of the current project; A first estimation submodule is configured to estimate the weight of each component of the current project based on the BOM table of the historical project and the project information of the current project to obtain the estimated weight of each component; A test submodule is used to perform weight simulation tests on each of the components, so that each component obtains at least one simulated design weight; The first determining submodule is used to determine the first version of the BOM table according to the simulated design weight and the estimated weight corresponding to each of the components.

[0101] Optionally, the first version of the BOM table is determined according to the simulated design weight and the estimated weight corresponding to each of the components, and the first determining submodule includes: An acquisition subunit, configured to acquire design requirements corresponding to each component from the project information; a first determining subunit, configured to determine a first version weight corresponding to each component according to the design requirements corresponding to each component, wherein the first version weight is the weight of the component that has the smallest error with the design requirements among at least one simulated design weight and an estimated weight of the component; The second determining subunit is configured to obtain the first version BOM table according to the first version weight of each of the components.

[0102] Optionally, the first version BOM is compared with the development stage BOM to generate a difference report, and the report generation module 202 includes: A first comparison submodule is configured to compare the first version weight of each component in the first version BOM with the design weight of the corresponding component in the development stage BOM to obtain weight change information of components with weight differences; The generating submodule is used to generate the difference report according to the weight change information of the parts with weight differences.

[0103] Optionally, the updating of the first version BOM table according to the difference report to obtain the second version BOM table, the first updating module 203 includes: A second determining submodule is configured to determine weight change information of each component having a weight difference based on the difference report; A second acquisition submodule is used to obtain the weight requirement preset in the current project; The third determining submodule is used to update the first version weight of each component with weight difference in the first version BOM table according to the weight requirement and the weight change information of each component with weight difference, and obtain the second version BOM table.

[0104] Optionally, the third version weight of each component is compared with the second version weight, and the second version BOM is updated based on the comparison result to obtain the target version BOM. The second updating module 204 includes: a fourth determining submodule, configured to compare the weight of the third version of each component with the weight of the second version, and determine components in the second version BOM table that have weight differences; The replacement submodule is used to replace the second version weight of the parts with weight differences with the corresponding third version weight to obtain the target version BOM table.

[0105] Optionally, the system further comprises: The receiving submodule is used to receive the actual weight of the vehicle obtained by weighing the vehicle; A summing submodule, configured to sum the weights of the various components in the target version BOM table to obtain the vehicle design weight; A third comparison submodule is used to compare the actual weight of the vehicle with the designed weight of the vehicle to obtain a comparison result; A fifth determining submodule, configured to determine the weight of each component in the target version BOM as the target production weight if the comparison result satisfies a preset error range; an updating submodule, configured to, if the comparison result does not satisfy the error range, re-receive the third version weight obtained by weighing the components, and update the weight of the components in the second version BOM table based on the third version weight of the components after re-weighing, so that the comparison result satisfies the preset error range.

[0106] Based on the same inventive concept, the third aspect of the embodiment of the present application provides a Figure 5 The electronic device 100 shown includes a processor 120, a memory 110, and a program or instruction stored in the memory 110 and executable on the processor 120. When the program or instruction is executed by the processor 120, the steps of the vehicle component weight management method as described in the first aspect of the present application are implemented.

[0107] In a fourth aspect of an embodiment of the present application, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the vehicle component weight management method as described in the first aspect of the present application are implemented. Each embodiment in this specification focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referenced to each other.

[0108] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the embodiments of the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0109] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0112] Although preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic inventive concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0113] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0114] The above is a detailed introduction to the provided vehicle component weight management method, system, electronic device and storage medium. Specific examples are used in this article to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method of this application and its core idea; at the same time, for general technical personnel in this field, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on this application.

Claims

1. A method for managing the weight of vehicle parts, characterized in that: Applied to a weight management platform, the method comprises: Based on the received BOM table of the historical project, estimate the first version of the BOM table of the current project, where the first version of the BOM table includes the first version weight of each component; receiving a development-stage BOM for the current project design, and comparing the first-version BOM with the development-stage BOM to generate a difference report, wherein the difference report is used to indicate weight change information of components that differ between the development-stage BOM and the first-version BOM; updating the first version of the BOM according to the difference report to obtain a second version of the BOM, wherein the second version of the BOM includes a second version of the weight of each component; The third version weight obtained by weighing the components is received, the third version weight of the components is compared with the second version weight, and the second version BOM table is updated based on the comparison result to obtain the target version BOM table.

2. The vehicle parts weight management method according to claim 1, characterized in that: The method of estimating the first version of the BOM of the current project based on the received BOM of the historical project includes: Obtaining project information of the current project; estimating the weight of each component of the current project based on the BOM table of the historical project and the project information of the current project to obtain the estimated weight of each component; Performing weight simulation tests on each of the components to ensure that each component obtains at least one simulated design weight; The first version of the BOM table is determined based on the simulated design weight and estimated weight corresponding to each of the components.

3. The vehicle parts weight management method according to claim 2, characterized in that: Determining the first version of the BOM table according to the simulated design weight and the estimated weight corresponding to each of the components includes: Obtaining design requirements corresponding to each of the components from the project information; Determining a first version weight corresponding to each component based on the design requirements corresponding to each component, where the first version weight is the weight of the component that has the smallest error from the design requirements among at least one simulated design weight and an estimated weight of the component; The first version BOM table is obtained according to the first version weight of each component.

4. The vehicle parts weight management method according to claim 1, characterized in that: The step of comparing the first version BOM with the development stage BOM to generate a difference report includes: Comparing the first version weight of each component in the first version BOM with the design weight of the corresponding component in the development stage BOM to obtain weight change information for components with weight differences; The difference report is generated based on the weight change information of the parts with weight differences.

5. The vehicle parts weight management method according to claim 1, characterized in that: The updating of the first version BOM table according to the difference report to obtain the second version BOM table includes: Determining weight change information of each component having weight differences based on the difference report; Obtaining the preset weight requirement of the current project; According to the weight requirement and the weight change information of each component with weight difference, the first version weight of each component with weight difference in the first version BOM table is updated to obtain the second version BOM table.

6. The vehicle parts weight management method according to any one of claims 1 to 5, characterized in that: The step of comparing the third version weight of each component with the second version weight, and updating the second version BOM table based on the comparison result to obtain the target version BOM table includes: Comparing the weight of the third version of each component with the weight of the second version, and determining the components in the second version of the BOM that have weight differences; The second version weight of the parts with weight differences is replaced with the corresponding third version weight to obtain the target version BOM table.

7. The vehicle parts weight management method according to claim 6, characterized in that: The method further comprises: Receiving the actual weight of the vehicle obtained by weighing the vehicle; Sum up the weights of the various components in the target version BOM to obtain the vehicle design weight; Comparing the actual weight of the vehicle with the designed weight of the vehicle to obtain a comparison result; If the comparison result satisfies a preset error range, the weight of each component in the target version BOM is determined as the target production weight; If the comparison result does not meet the error range, the third version weight obtained by weighing the various components is re-received, and based on the third version weight of the various components after re-weighing, the weight of each component in the second version BOM table is updated so that the comparison result meets the preset error range.

8. A vehicle parts weight management system, characterized in that: Applied to a weight management platform, the weight management system is used to execute the method according to any one of claims 1 to 7, the weight management system comprising: An estimation module is configured to estimate a first version of the BOM for the current project based on the received BOM for the historical project, where the first version of the BOM includes a first version weight of each component. a report generation module, configured to receive a development-stage BOM table designed for the current project, compare the first-version BOM table with the development-stage BOM table, and generate a difference report, wherein the difference report is used to indicate weight change information of components that differ between the development-stage BOM table and the first-version BOM table; A first updating module is configured to update the first version of the BOM table according to the difference report to obtain a second version of the BOM table, where the second version of the BOM table includes a second version weight of each component; The second update module is used to receive the third version weight obtained by weighing the various components, compare the third version weight of the various components with the second version weight, and update the second version BOM table based on the comparison result to obtain the target version BOM table.

9. An electronic device, characterized in that: The invention comprises a processor, a memory and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the vehicle parts weight management method as described in any one of claims 1 to 7.

10. A readable storage medium storing a program or instruction, characterized in that: When the program or instruction is executed by a processor, the steps of the vehicle component weight management method according to any one of claims 1 to 7 are implemented.

Images