A method for controlling the number of test prototype vehicles

By optimizing and integrating the number of test prototypes through a nine-layer elimination method, the problems of dispersed prototype numbers and resource waste were solved, thereby achieving cost control and shortening the project cycle.

CN123070530APending Publication Date: 2026-11-10YIBIN COWIN AUTO CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611118351.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-27
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

During the vehicle development process, the demand for prototype vehicles is scattered and lacks systematic integration, resulting in wasted resources and project delays. Existing methods rely on experience-based judgment, leading to large fluctuations in the number of prototype vehicles.

Method used

A nine-layer step-by-step elimination method was adopted, including steps such as verifying test requirements and development scope, verifying test cycle and standards, judging logical order, judging the feasibility of CAE virtual simulation replacement, judging the feasibility of configuration coverage, judging the feasibility of modifying and utilizing existing prototype vehicles, and confirming the vehicle commonality of replacing prototypes to meet different test items. The number of prototype vehicles was optimized by selecting each layer.

Benefits of technology

By systematically eliminating multiple testing requirements, we can reasonably control the number of prototype vehicles, reduce R&D costs, shorten project cycles, and avoid resource waste and announcement failures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070530A_ABST
    Figure CN123070530A_ABST
Patent Text Reader

Abstract

This invention discloses a method for controlling the number of test prototype vehicles, comprising the following steps: 1) verifying test requirements and development scope; 2) verifying test cycle and standards; 3) determining the logical order of test items; 4) determining the feasibility of CAE virtual simulation as a substitute; 5) determining the feasibility of configuration coverage; 6) determining the feasibility of modifying and utilizing existing prototype vehicles; 7) confirming the vehicle commonality of replacing prototypes to meet different test items; 8) comparing the integrated number of prototype vehicles with historical similar vehicles; 9) determining the final number of prototype vehicles, and through a systematic elimination method, selecting and optimizing layer by layer, integrating multi-dimensional test requirements to form a reasonable number of prototype vehicles, thereby reducing R&D costs and shortening the project cycle.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the field of automobile manufacturing technology, and in particular relates to a method for controlling the number of test prototype vehicles. Background Technology

[0002] In the process of realizing this invention, the inventors discovered that the prior art has at least the following problems:

[0003] In the process of vehicle development, prototype vehicles are crucial for verifying product performance and meeting regulatory requirements. The demand for the number of prototype vehicles is typically submitted by each department using the vehicle, based on the project's development scope. This demand covers various types of testing, including certification, seasonal calibration, durability and reliability, intelligent connectivity, crash safety, and high-altitude / high-temperature (HALT) testing. Furthermore, the investment in prototype vehicles is a significant component of the overall vehicle development cost—according to industry statistics, prototype production accounts for approximately 30% to 50% of the total development cost in new vehicle development. Optimizing and integrating the dispersed testing needs from various departments to form a reasonable number of prototype vehicles is a key challenge in cost management and project cycle management during project development. Currently, automotive companies mainly rely on project team experience or simple requirement aggregation methods for planning the number of prototype vehicles, which presents the following technical problems:

[0004] First, the testing needs of various vehicle-using departments are submitted in a decentralized manner, lacking a systematic integration method, which often leads to redundant or duplicate manufacturing of prototype vehicles, resulting in a waste of R&D resources.

[0005] Second, there are logical sequence constraints between different test items. For example, EMC (electromagnetic compatibility) testing can only be carried out after development is qualified; otherwise, failure of the certification test will cause delays and cost losses. Existing solutions lack a systematic verification and judgment of such logical sequences.

[0006] The main drawback of existing technologies is that they often rely on model predictions or empirical judgments. However, models are typically built for entirely new development projects, and the scope of each project varies. Therefore, model results are only for reference, and actual decisions still largely depend on the personal experience of engineers. Due to differences in the experience accumulated by different projects and personnel, judgments often differ, ultimately leading to significant fluctuations in the number of prototype vehicles.

[0007] CN118275129A discloses a method, equipment, device, and medium for calculating combined test conditions, relating to the field of automotive durability testing technology. The method includes collecting load spectrum data of various types of road surfaces under public roads, calculating relative pseudo-damage and frequency damage spectra, calculating the total target of relative pseudo-damage and the total target of frequency damage spectrum; statistically analyzing the relative pseudo-damage, frequency damage spectra, and the time required for each test condition to run; converting the relative pseudo-damage matrix of each test condition into a contribution matrix, and outputting the solution for the expected target of a set number of groups; however, it still cannot solve the aforementioned technical problems. Summary of the Invention

[0008] The technical problem to be solved by the present invention is to provide a method for controlling the number of test prototypes. By systematically eliminating and optimizing step by step, integrating multi-dimensional test requirements, a reasonable number of prototypes can be formed, thereby reducing R&D costs and shortening the project cycle.

[0009] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a method for controlling the number of test prototype vehicles, comprising the following steps:

[0010] 1) Verify test requirements and development scope; 2) Verify test cycle and standards; 3) Determine the logical order of test items; 4) Determine the feasibility of CAE virtual simulation as a substitute; 5) Determine the feasibility of configuration coverage; 6) Determine the feasibility of modifying and utilizing existing prototype vehicles; 7) Confirm the vehicle commonality of replacing prototypes to meet different test items; 8) Compare the number of integrated prototype vehicles with historical similar vehicles; 9) Determine the final number of prototype vehicles.

[0011] In step 1) above, the development scope information of the whole vehicle development project and the test requirements submitted by each vehicle user organization are obtained. Each test requirement is checked against the development scope, and unnecessary test requirements that exceed the development scope are eliminated to generate the first round of optimized test requirement quantity.

[0012] In step 2) above, the required test cycle and standard test cycle for each test project are obtained, including transportation time. Test cycles that do not meet the standards are identified and optimized. The optimization principle is that the cycle of one vehicle is less than 90 days. Test vehicles are required to be shared with other test projects. The number of test requirements after the second round of optimization is generated.

[0013] In step 3) above, the development dependencies and logical order constraints between each test project are obtained, and the logical order of each test project is judged to be correct. Specifically, if the successful development of test project A is a prerequisite for the implementation of test project B, then test project B shall not be implemented before test project A is successfully developed. If there is a combination of test requirements with incorrect logical order, an alarm signal is issued, and the test plan is adjusted according to the correct logical order before continuing execution. After the logical order is judged and adjusted, the number of test requirements after the third round of optimization is generated.

[0014] In step 4) above, a pre-built CAE simulation capability database is obtained, which records whether each test item can be completely or partially replaced by virtual simulation; each test item is judged one by one to see if it meets the CAE replacement conditions: if it meets the complete replacement conditions, the actual vehicle requirement for that test item is removed; if it meets the partial replacement conditions, the corresponding actual vehicle test times are reduced; if it does not meet the replacement conditions, the actual vehicle test requirements are retained; after the CAE replacement judgment, the number of test requirements after the fourth round of optimization is generated.

[0015] In step 5) above, the vehicle configuration information required for each test item is obtained, and the low-configuration test items and high-configuration test items of the same vehicle model are matched and judged to determine whether the test content of the low-configuration test item can be covered by the test of the high-configuration vehicle on the same platform. If the low-configuration test item can be covered by the high-configuration vehicle, the independent prototype vehicle requirement of the low-configuration test item is removed and integrated into the test plan of the corresponding high-configuration vehicle. After the configuration coverage judgment, the number of test requirements after the fifth round of optimization is generated.

[0016] In step 6) above, the inventory information of existing prototype vehicles in the current project is obtained. Existing prototype vehicles include prototype vehicles that have completed some tests and prototype vehicles in the project inventory. It is determined one by one whether the prototype vehicle requirements of each test project can be met by modifying existing prototype vehicles. If they can be met by modification, the test project is marked as no longer requiring new prototype vehicles, and the corresponding existing prototype vehicles are included in the modification plan. If they cannot be met by modification, the new prototype vehicle requirements are retained. After the determination of existing prototype vehicle modification and utilization, the number of test requirements after the sixth round of optimization is generated.

[0017] In step 7) above, feasibility information on the replacement of prototype vehicle parts for each test item is obtained. Component replacement includes, but is not limited to, powertrain replacement, suspension system replacement, electrical system replacement, and exterior part replacement. It is then determined whether the test requirements of two or more test items can be met by replacing different parts on the same base prototype vehicle. If sharing can be achieved by replacing parts, the multiple test items are integrated into the same base prototype vehicle, and the corresponding prototype vehicle quantity requirement is reduced. If sharing cannot be achieved by replacing parts, the individual prototype vehicle requirements are retained. After confirming vehicle commonality, the seventh round of optimized test requirement quantity is generated.

[0018] In step 8) above, obtain historical data on similar prototype vehicles and compare the number of prototype vehicles integrated after the seventh round of optimization with the number of similar prototype vehicles in the past. If the number of integrated prototype vehicles is not higher than the average number of similar projects in the past, the optimization effect is deemed to have met the standard and proceed to the next step. If the number of integrated prototype vehicles is higher than the number of similar projects in the past, backtrack to check whether there is any omission in steps 1) to 7) and make further optimization adjustments.

[0019] In step 9) above, the number of test vehicles after optimization and integration in steps 1 to 8 will be finally confirmed. The conditions for confirmation include, but are not limited to: the total budget corresponding to the total number of test vehicles finally confirmed does not exceed 50% of the total budget of the entire project; if it exceeds this proportion, at least one optimization step from step 1) to step 8) will be backtracked and executed until the budget constraints or requirements are met and the final confirmation is made.

[0020] One of the above technical solutions has the following advantages or beneficial effects: by systematically eliminating and optimizing layer by layer, integrating multi-dimensional test requirements, a reasonable number of prototype vehicles can be formed, thereby reducing R&D costs and shortening the project cycle. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the method for controlling the number of test vehicles provided in this embodiment of the invention; Detailed Implementation

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. 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.

[0023] Example 1

[0024] See Figure 1A method for controlling the number of prototype vehicles includes the following steps: 1) verifying test requirements and development scope; 2) verifying test cycles and standards; 3) determining the logical order of test items; 4) assessing the feasibility of CAE virtual simulation as a substitute; 5) assessing the feasibility of configuration coverage; 6) assessing the feasibility of modifying and utilizing existing prototype vehicles; 7) confirming the commonality of vehicles that can be replaced to meet different test items; 8) comparing the integrated number of prototype vehicles with historical similar vehicles; and 9) determining the final number of prototype vehicles. Through a systematic elimination method, layer-by-layer screening and optimization are performed to integrate multi-dimensional test requirements and form a reasonable number of prototype vehicles, thereby reducing R&D costs and shortening the project cycle.

[0025] Unlike existing technologies that rely on model predictions or experience-based judgments, this invention employs a nine-layer step-by-step elimination method. From the aggregation of requirements to the final decision, it filters out unnecessary requirements at each level, minimizing the number of unreasonable prototypes and avoiding waste or shortage of prototype resources. This enables precise planning and cost control of R&D resources.

[0026] In step 1) above, the development scope information of the whole vehicle development project and the test requirements submitted by each vehicle user organization are obtained. Each test requirement is checked against the development scope, and unnecessary test requirements that exceed the development scope are eliminated to generate the first round of optimized test requirement quantity.

[0027] The core purpose of this step is to establish the first line of defense for "demand access." This is achieved by mandating a comparison between the testing requirements submitted by each vehicle-using department and the official development scope of the vehicle development project, eliminating requirements that are irrelevant to the project's development goals or exceed its boundaries. In actual project development, due to a lack of comprehensive understanding of the overall project scope or for their own convenience, vehicle-using departments often submit testing requirements that exceed the project's scope. For example, a vehicle model project might only be developed for the Chinese domestic market, but the certification department might submit ECE (Economic Commission for Europe) certification testing requirements based on export models; similarly, a project might only develop a pure electric version, but the durability department might use the road load spectrum of the hybrid version to submit additional durability verification requirements. This step ensures that every retained testing requirement has its legitimacy and necessity by establishing a unique correspondence between the "development scope" and "testing requirements."

[0028] The implementation of this step brings benefits in three aspects: First, it reduces communication costs. By standardizing the requirements verification process, disputes that previously required multiple rounds of meetings are addressed proactively and systematically, reducing back-and-forth between the project team and various vehicle-using departments and significantly improving the efficiency of requirements confirmation. Second, it reduces ineffective investment. Eliminating out-of-scope testing requirements early in the project avoids unnecessary costs in subsequent prototype manufacturing, tooling development, and test site reservations. Third, it prevents requirement inflation. Clear requirements admission standards are established, effectively suppressing the tendency of departments to submit redundant requirements "for safety's sake," ensuring effective control over the total number of prototype vehicle requirements from the outset. Through the mandatory "requirements-scope" verification mechanism, testing requirements are shifted from "passive reception and aggregation" to "active review and filtering," forming the first line of defense for prototype vehicle quantity control. Compared to existing methods that directly aggregate departmental requirements and then calculate, this step eliminates unnecessary requirements at the source, avoiding the problem of "garbage in, garbage out," and significantly improving the input quality of all subsequent optimization steps. Meanwhile, this step provides a "purified" list of requirements for subsequent steps such as periodic verification and logical sequence judgment, reducing the workload of invalid judgments in subsequent steps. In addition, in project practice, the "requirements and scope comparison table" generated in this step can also serve as an important basis for project scope change management—when the project development scope is adjusted, the impact on the requirements for prototype vehicles can be quickly analyzed, enabling dynamic control of the number of prototype vehicles.

[0029] In step 2) above, the required test cycle and standard test cycle for each test item are obtained, including transportation time. Test cycles that do not meet the standards are identified and optimized. Except for destructive tests (collision or dissection, etc.), the optimization principle is that the cycle of one vehicle is less than 90 days. It is required to share test prototypes with other test items and generate the second round of optimized test requirements.

[0030] The core objective of this step is to identify test items that cannot be actually performed due to their test cycle (including transportation time) not meeting the window requirements. It then optimizes these substandard individual tests through a shared solution, ensuring that every retained test requirement is feasible in terms of time. In vehicle development projects, many tests have strong seasonal and time-sensitive requirements: high-temperature tests need to be conducted in July-August, low-temperature tests in January-February, and notification tests must align with the time windows of government certification bodies. In actual projects, the following situation frequently occurs: although a test item has a legitimate requirement and matching scope, its required test cycle (including the entire process time from prototype vehicle transportation, test preparation, formal testing, and prototype vehicle return to the factory) exceeds the available window, making it impossible to complete the test independently. This step sets a "90-day" cycle threshold as a mandatory sharing trigger condition. That is, when the cycle for a prototype vehicle to perform a certain test alone is less than 90 days, it is mandatory for that test to share a prototype vehicle with other test items, thereby achieving intensive utilization of cycle resources.

[0031] The implementation of this step brings three main benefits: First, it avoids plans becoming unfeasible due to infeasibility of the timeframe. By eliminating or adjusting test projects that cannot actually be completed within the specified window period through timeframe verification, the test plan becomes truly executable, avoiding the passive situation of discovering during project execution that tests cannot be completed on schedule. Second, it identifies potential sharing opportunities. Short-term test projects with a timeframe of less than 90 days are required to share prototype vehicles with other tests, effectively forcing project teams to discover matching opportunities between different test projects in the time dimension, thereby completing more test tasks without increasing the number of prototype vehicles. Third, it optimizes transportation and waiting time. By calculating the entire timeframe, including transportation time, project teams are prompted to optimize prototype vehicle scheduling plans, transportation routes, and test sequences, reducing wasted time on the road and waiting for prototype vehicles, and improving the time utilization rate of prototype vehicles. Introducing the time dimension into the prototype quantity control consideration system realizes the expansion of the dimension from "only looking at the required quantity" to "also looking at time feasibility". In particular, the design of the "90-day mandatory sharing" rule establishes a quantifiable and automatically triggered mechanism for the intensive utilization of prototype vehicles. This transforms the sharing decision, which originally required human coordination, into a process-oriented, automated judgment, reducing interference from human factors and negotiation costs. Simultaneously, this step synergizes with step 7) (replacing prototypes to achieve sharing): step 2) identifies sharing needs from a time perspective, while step 7) confirms sharing feasibility from a technical perspective. The combination of these two steps significantly improves the success rate and efficiency of vehicle sharing. Furthermore, the experimental cycle data accumulated in this step can be fed back into the formulation of the project's master schedule, providing data support for identifying the critical path and setting buffer times.

[0032] In step 3) above, the development dependencies and logical order constraints between each test project are obtained, and the logical order of each test project is judged to be correct. Specifically, if the successful development of test project A is a prerequisite for the commencement of test project B, then test project B cannot be carried out before test project A is successfully developed. If there is a logically incorrect combination in the test requirements, an alarm signal is issued, and the test plan is adjusted to the correct logical order before continuing execution. After the logical order judgment and adjustment, the number of test requirements after the third round of optimization is generated. By using the logical order constraints between test projects as an independent judgment dimension in the prototype quantity control method, significant resource waste problems such as announcement failures caused by improper timing arrangements are effectively avoided, and the engineering practicality of the method is improved.

[0033] In step 4) above, a pre-built CAE simulation capability database is obtained. This database records whether each test item can be completely or partially replaced by virtual simulation. Each test item is then assessed to determine if it meets the CAE replacement conditions: if it meets the complete replacement condition, the actual vehicle requirement for that test item is removed; if it meets the partial replacement condition, the corresponding actual vehicle test run requirement is reduced; if it does not meet the replacement condition, the actual vehicle test requirement is retained. After the CAE replacement assessment, the fourth round of optimized test requirement quantity is generated. This systematically integrates multiple optimization mechanisms, such as CAE virtual simulation replacement, high-configuration coverage of low-configuration, modification and utilization of existing prototype vehicles, and replacement of prototype parts to achieve vehicle sharing, forming a complete decision-making chain and significantly improving prototype integration efficiency.

[0034] In step 5) above, the vehicle configuration information required for each test item is obtained. A matching judgment is performed between low-configuration and high-configuration test items for the same vehicle model to determine whether the test content of the low-configuration test item can be covered by the test of the high-configuration model on the same platform. If the low-configuration test item can be covered by the high-configuration model, the independent prototype vehicle requirement for the low-configuration test item is removed and integrated into the test plan of the corresponding high-configuration model. After the configuration coverage judgment, the number of test requirements after the fifth round of optimization is generated. By comparing the integrated prototype vehicle number with historical similar projects, the solution is self-checked and further optimized to ensure that the optimization results meet industry practice standards.

[0035] In step 6) above, the inventory information of existing prototype vehicles in the current project is obtained. Existing prototype vehicles include prototype vehicles that have completed some tests and prototype vehicles in the project inventory. It is determined one by one whether the prototype vehicle requirements of each test project can be met by modifying existing prototype vehicles. If they can be met by modification, the test project is marked as no longer requiring new prototype vehicles, and the corresponding existing prototype vehicles are included in the modification plan. If they cannot be met by modification, the new prototype vehicle requirements are retained. After the determination of existing prototype vehicle modification and utilization, the number of test requirements after the sixth round of optimization is generated.

[0036] The core objective of this step is to maximize the utilization of existing prototype vehicle resources within the project. By modifying these vehicles, new testing uses are assigned to them, thus avoiding the need for new prototype manufacturing and achieving resource recycling through "replacing the old with the new." At different stages of a vehicle development project, various types of existing prototype vehicles are generated: prototypes that have completed specific testing tasks in the early stages (such as body-in-whites that have completed crash tests, or complete vehicles that have completed performance tests), spare prototypes in the project inventory, and prototypes that have become idle due to plan adjustments. Although these existing prototypes have fulfilled their original testing missions, their basic structure and main components remain intact. Through appropriate modifications (such as replacing the engine / motor, adjusting the suspension, adding testing equipment, or changing the body paint), they can fully meet new testing requirements. This step, through systematic inventory checks and feasibility assessments of modifications, activates existing prototype vehicle resources from "dormant assets" into "effective production capacity."

[0037] The implementation of this step brings benefits in three aspects: First, it directly reduces the manufacturing cost of prototype vehicles. Reducing the manufacturing of even one new prototype vehicle saves costs on raw material procurement, tooling development, assembly labor, testing, and debugging, resulting in significant savings per vehicle. For example, the manufacturing cost of a single prototype vehicle for a mid-sized passenger car is typically between 300,000 and 500,000 yuan; replacing one through existing stock achieves the same amount of cost savings. Second, it shortens the prototype preparation cycle. Existing prototype vehicles are already in stock, and the conversion cycle is typically 2-4 weeks, while manufacturing new prototypes usually takes 8-12 weeks from order placement to delivery. Converting existing stock significantly reduces prototype preparation time, allowing the test project to start earlier and shortening the overall project development cycle. Third, it reduces inventory management pressure. After a project ends, remaining prototype vehicles often face difficulties in disposal. By utilizing existing prototype vehicles as much as possible in this project, it reduces the need for new prototypes and consumes existing inventory, thus optimizing the inventory structure.

[0038] The beneficial effect of this step lies in establishing a transformation channel from "passively idle" to "actively reused" existing prototype vehicles, achieving optimized allocation of prototype vehicle resources throughout the entire project lifecycle. This step, together with step 7) (replacing shared prototype components), forms a complete "hardware reuse" solution—step 6) focuses on the direct modification and utilization of the entire vehicle, while step 7) focuses on switching between different tests by replacing key prototype components. The combination of the two minimizes the need for new prototype vehicles. Furthermore, the effective implementation of this step relies on the support of an existing prototype vehicle information management system. In practice, this step compels companies to establish a comprehensive database of in-stock prototype vehicle status (including key information such as prototype vehicle model, completed test projects, remaining lifespan, current status, and scope of modification), providing systematic support for the refined management of prototype vehicle resources. Its derivative benefits far exceed the control of the number of prototype vehicles in a single project.

[0039] In step 7) above, feasibility information on the replacement of prototype vehicle parts for each test item is obtained. Component replacement includes, but is not limited to, powertrain replacement, suspension system replacement, electrical system replacement, and exterior part replacement. It is then determined whether the test requirements of two or more test items can be met by replacing different parts on the same base prototype vehicle. If sharing can be achieved by replacing parts, the multiple test items are integrated into the same base prototype vehicle, and the corresponding prototype vehicle quantity requirement is reduced. If sharing cannot be achieved by replacing parts, the individual prototype vehicle requirements are retained. After confirming vehicle commonality, the seventh round of optimized test requirement quantity is generated.

[0040] The core objective of this step is to use technical means—replacing different key components on the same base prototype (i.e., "one vehicle, multiple configurations")—to enable a single prototype to sequentially meet the needs of multiple test projects, thereby further reducing the number of prototypes required. In actual testing, different test projects often have different requirements for prototype configurations: for example, powertrain durability testing requires engine A, while high-temperature calibration testing requires engine B; similarly, suspension system evaluation testing requires a sport suspension, while comfort evaluation testing requires a comfort suspension. Previously, a separate prototype with the corresponding configuration was manufactured for each test project, resulting in an inflated number of prototypes. In reality, many test projects only differentiate prototypes at the level of individual systems / components, while the rest of the main structure remains identical. This step, through a systematic evaluation of the feasibility of replacing specific components on the same base prototype, integrates test tasks that originally required multiple prototypes into a single prototype for sequential completion.

[0041] The implementation of this step brings benefits in three aspects: First, it significantly reduces the total number of prototype vehicles. By using a "one vehicle, multiple states" approach, one prototype vehicle can cover the test tasks that originally required 2-3 or even more prototype vehicles, resulting in a very significant reduction in the number of prototype vehicles. This reduction is even more pronounced when component replacement is simple and inexpensive (such as wheel / tire replacement, ECU software remapping, sensor replacement, etc.). Second, it reduces prototype vehicle storage requirements. The reduction in the number of prototype vehicles directly reduces the demand for prototype vehicle storage space, charging / refueling facilities, and daily maintenance manpower, which has additional practical value for projects with limited space resources. Third, it focuses on truly differentiated needs. By identifying which test items can be met simply by replacing components, the project team is forced to examine and clarify the differentiated requirements of each test item for the prototype vehicle's state, making the test items that truly require independent prototype vehicles clearer.

[0042] The beneficial effect of this step lies in transforming the rigid "one-to-one" binding relationship between "prototype vehicles" and "test projects" into a flexible "one-to-many" matching relationship, breaking the traditional mindset of configuring prototype vehicles independently on a project-by-project basis. This step complements step 5) (configuration coverage)—step 5) solves the horizontal integration problem of "high-configuration covering low-configuration," while this step solves the vertical integration problem of "achieving multi-purpose functionality through component replacement on the same base vehicle." Both work together from different dimensions to reduce the number of prototype vehicles. Furthermore, the engineering practice of this step has promoted the formation of the "prototype-level" test planning concept, that is, shifting from test planning on a vehicle-by-vehicle basis to planning on a "base vehicle + replaceable prototype combination" basis, improving the level of precision in test planning. The promotion of this concept can also be extended to aspects such as advance stockpiling of test prototypes and standardization of prototype replacement operations, possessing methodological value beyond the control of the number of prototype vehicles itself.

[0043] In step 8) above, obtain historical data on similar prototype vehicles and compare the number of prototype vehicles integrated after the seventh round of optimization with the number of similar prototype vehicles in the past. If the number of integrated prototype vehicles is not higher than the average number of similar projects in the past, the optimization effect is deemed to have met the standard and proceed to the next step. If the number of integrated prototype vehicles is higher than the number of similar projects in the past, backtrack to check whether there is any omission in steps 1) to 7) and make further optimization adjustments.

[0044] The core purpose of this step is to conduct external benchmarking verification of the prototype quantity plan after the first seven optimization steps by comparing it with historical data. This determines whether the optimization result is within a reasonable range and provides an objective basis for whether further optimization is needed. The optimization in the first seven steps is mainly based on logical judgment and screening of internal information of the current project. Although it can eliminate unreasonable requirements, it cannot answer a key question—"Is this quantity reasonable in the industry / in similar historical projects?" Prototype usage data from similar historical projects is an important reference for verifying the rationality of the current solution. Through horizontal comparison, we can verify that the optimization result does not deviate from industry practice, and we can also discover potential overlooked optimization opportunities in the current solution—if the integrated quantity is significantly higher than that of similar historical projects, it indicates that there may be insufficiently identified optimization space in the first seven steps.

[0045] The implementation of this step brings benefits in three aspects: First, it establishes a quantitative evaluation benchmark. It transforms the previously expert-driven judgment of "whether a solution is good or bad" into a quantifiable benchmarking analysis, making the evaluation results more objective and transparent, and reducing disputes arising from subjective judgment. Second, it uncovers hidden optimization opportunities. Prototype usage data from similar historical projects contains proven and effective integration patterns. When the current solution exceeds historical benchmarks, retrospectively reviewing the first seven steps is essentially learning from and reusing successful optimization experiences from past projects. Third, it enhances the persuasiveness of the solution. A solution with a number of prototypes validated by historical data has stronger data support and persuasiveness when submitted to project decision-makers for review, facilitating rapid approval and subsequent implementation.

[0046] The beneficial effect of this step lies in introducing a "historical data closed-loop verification" mechanism, upgrading the method of this invention from a "one-way optimization process" to a "closed-loop control system with feedback loops." Steps 1) to 7) constitute the forward optimization path, and step 8) constitutes the reverse verification and correction path, together forming a complete learning-based optimization closed loop. This two-way mechanism of "forward optimization + reverse verification" ensures that the prototype quantity control results consider both the actual situation of the current project and the practical level of historical projects, avoiding the extremes of over-optimization or under-optimization. Furthermore, the long-term implementation of this step has significant knowledge accumulation value. As the number of projects increases, the database of similar historical projects becomes richer, and the benchmark values ​​for comparison become increasingly statistically significant and valuable. The optimization effect of subsequent projects will continue to improve with data accumulation, forming a positive accumulation of corporate knowledge assets. Meanwhile, this step, together with step 2) (periodic verification) and step 9) (budget decision-making), forms a three-tiered verification system: step 2) verifies from the perspective of time feasibility, step 8) verifies from the perspective of historical experience, and step 9) verifies from the perspective of cost controllability—the three from different angles form a comprehensive verification of the prototype quantity plan, ensuring the overall rationality of the final plan.

[0047] In step 9) above, the number of prototype vehicles optimized and integrated through steps 1 to 8 is finally confirmed. Confirmation conditions include, but are not limited to: the total budget corresponding to the final confirmed number of prototype vehicles does not exceed 50% of the total project budget; if this proportion is exceeded, at least one optimization step from steps 1) to 8) is re-executed until the budget constraint or requirement is met, at which point final confirmation is made. Using "prototype vehicle budget not exceeding 50% of the total project budget" as a quantitative red line for project control forms a rigid cost safety net mechanism, effectively ensuring that R&D costs are controllable.

[0048] Compared with the prior art, the present invention has the following beneficial effects:

[0049] 1. Systematic elimination method thinking: Unlike existing technologies that rely on model prediction or experience judgment, this invention adopts a nine-level step-by-step elimination method, from demand aggregation to final decision, filtering out unnecessary demands at each level, minimizing the number of unreasonable prototypes, avoiding waste or shortage of prototype resources, and achieving precise planning and cost control of R&D resources.

[0050] 2. Introduction of test logic sequence constraint verification: This invention is the first to use the logical sequence constraint between test items as an independent judgment dimension in the prototype vehicle quantity control method, which effectively avoids major resource waste problems such as announcement failure caused by improper timing arrangement and improves the engineering practicality of the method.

[0051] 3. Multi-dimensional optimization mechanism synergistic integration: This invention systematically integrates multiple optimization mechanisms such as CAE virtual simulation replacement, high configuration covering low configuration, modification and utilization of existing prototype vehicles, and replacement of prototype parts to achieve vehicle sharing, forming a complete decision-making link and significantly improving the efficiency of prototype vehicle integration.

[0052] 4. Historical data closed-loop verification: By comparing the integrated number of prototype vehicles with similar historical projects, the solution can be self-checked and further optimized to ensure that the optimization results meet industry practice standards.

[0053] 5. Hard budget constraint: For the first time, the "prototype budget shall not exceed 50% of the total project budget" is set as a quantitative red line for project control, forming a rigid cost guarantee mechanism to effectively ensure that R&D costs are controllable.

[0054] After adopting the above scheme, a systematic elimination method is used to screen and optimize layer by layer, integrate multi-dimensional test requirements, and form a reasonable number of prototype vehicles, thereby reducing R&D costs and shortening the project cycle.

[0055] Example 2

[0056] A method for controlling the number of test prototype vehicles includes the following steps:

[0057] Step 1: Verify the test requirements against the development scope;

[0058] Obtain the development scope information of the whole vehicle development project and the test requirements submitted by each vehicle-using department. Check each test requirement against the development scope, eliminate unnecessary test requirements that exceed the development scope, and generate the first round of optimized test requirement list.

[0059] Step 2: Verify the test cycle against the standards;

[0060] Obtain the required test cycle and standard test cycle (including transportation time) for each test item, identify test cycles that do not meet the standards and optimize them (in principle, a cycle of less than 90 days for a vehicle must be shared with other test items), and generate a second round of optimized test requirement list.

[0061] Step 3: Determining the logical order of the test items;

[0062] The development dependencies and logical order constraints between each test project are obtained, and the logical order of each test project is checked sequentially. Specifically, if the successful development of test project A is a prerequisite for the commencement of test project B, then test project B cannot be carried out before test project A is successfully developed. If there are combinations of test requirements with incorrect logical order (such as an announcement that an EMC test is planned to be carried out before the EMC test is successfully developed), an alarm signal is issued, requiring the test plan to be adjusted to the correct logical order before execution can continue. After the logical order is checked and adjusted, a third-round optimized list of test requirements is generated.

[0063] Step 4: Feasibility assessment of CAE virtual simulation as an alternative;

[0064] A pre-built CAE simulation capability database is obtained, which records whether each test item can be completely or partially replaced by virtual simulation. Each test item is assessed to determine if it meets the CAE replacement criteria: if it meets the complete replacement criteria, the actual vehicle requirement for that test item is removed; if it meets the partial replacement criteria, the corresponding actual vehicle test times are reduced; if it does not meet the replacement criteria, the actual vehicle test requirement is retained. After the CAE replacement assessment, a fourth-round optimized test requirement list is generated.

[0065] Step 5: Assess the feasibility of configuration coverage;

[0066] Obtain the vehicle configuration information required for each test item, and match low-configuration test items with high-configuration test items for the same vehicle model to determine whether the test content of the low-configuration test item can be covered by the test of the high-configuration model on the same platform. If the low-configuration test item can be covered by the high-configuration model, then the independent prototype requirement of the low-configuration test item is removed and integrated into the test plan of the corresponding high-configuration model. After the configuration coverage determination, a fifth round of optimized test requirement list is generated.

[0067] Step 6: Feasibility assessment of modifying and utilizing existing prototype vehicles;

[0068] Obtain the inventory information of existing prototype vehicles in the current project. Existing prototype vehicles include those that have completed partial testing and those currently in the project inventory. Determine whether the prototype vehicle requirements for each testing project can be met by modifying existing prototype vehicles. If they can be met through modification, mark the testing project as not requiring new prototype vehicles and include the corresponding existing prototype vehicle in the modification plan; if they cannot be met through modification, retain the requirement for new prototype vehicles. After determining the modification and utilization of existing prototype vehicles, generate the sixth round of optimized testing requirement list.

[0069] Step 7: Replace the sample parts to confirm vehicle commonality for different test items;

[0070] Obtain feasibility information for replacing prototype parts on the vehicle for each test item. Component replacement includes, but is not limited to, powertrain replacement, suspension system replacement, electrical system replacement, and exterior component replacement. Determine sequentially whether the test requirements of two or more test items can be met by replacing different parts on the same base prototype vehicle: if sharing can be achieved by replacing prototype parts, then the multiple test items are integrated into the same base prototype vehicle, and the corresponding prototype vehicle quantity requirement is reduced; if sharing cannot be achieved by replacing prototype parts, then the individual prototype vehicle requirements are retained. After confirming vehicle commonality, a seventh-round optimized test requirement list is generated.

[0071] Step 8: Compare the number of integrated prototype vehicles with similar historical projects;

[0072] Obtain prototype usage data from similar historical projects, including those with similar platform levels and technical complexity to the current project. Compare the number of prototypes integrated after the seventh round of optimization with the number of prototypes from similar historical projects: if the number of integrated prototypes is not higher than the average of similar historical projects, the optimization is considered successful, and proceed to the next step; if the number of integrated prototypes is significantly higher than that of similar historical projects, backtrack to check for any missed optimization opportunities from steps one to seven, and perform further optimization and adjustments.

[0073] Step 9: Final review and decision;

[0074] The proposed number of test vehicles after optimization and integration through steps one through eight will be submitted to the project decision-making level for final review and approval. The conditions for review and approval include, but are not limited to: the total budget corresponding to the final confirmed number of test vehicles shall not exceed 50% of the total budget of the entire project; if it exceeds this proportion, at least one optimization step from step one through eight will be re-executed until the budget constraint is met or the project decision-making level approves it before final confirmation.

[0075] Compared with the prior art, the present invention has the following beneficial effects:

[0076] 1. Systematic elimination method thinking: Unlike existing technologies that rely on model prediction or experience judgment, this invention adopts a nine-level step-by-step elimination method, from demand aggregation to final decision, filtering out unnecessary demands at each level, minimizing the number of unreasonable prototypes, avoiding waste or shortage of prototype resources, and achieving precise planning and cost control of R&D resources.

[0077] 2. Introduction of test logic sequence constraint verification: This invention is the first to use the logical sequence constraint between test items as an independent judgment dimension in the prototype vehicle quantity control method, which effectively avoids major resource waste problems such as announcement failure caused by improper timing arrangement and improves the engineering practicality of the method.

[0078] 3. Multi-dimensional optimization mechanism synergistic integration: This invention systematically integrates multiple optimization mechanisms such as CAE virtual simulation replacement, high configuration covering low configuration, modification and utilization of existing prototype vehicles, and replacement of prototype parts to achieve vehicle sharing, forming a complete decision-making link and significantly improving the efficiency of prototype vehicle integration.

[0079] 4. Historical data closed-loop verification: By comparing the integrated number of prototype vehicles with similar historical projects, the solution can be self-checked and further optimized to ensure that the optimization results meet industry practice standards.

[0080] 5. Hard budget constraint: For the first time, the "prototype budget shall not exceed 50% of the total project budget" is set as a quantitative red line for project control, forming a rigid cost guarantee mechanism to effectively ensure that R&D costs are controllable.

[0081] After adopting the above scheme, a systematic elimination method is used to screen and optimize layer by layer, integrate multi-dimensional test requirements, and form a reasonable number of prototype vehicles, thereby reducing R&D costs and shortening the project cycle.

[0082] Example 3

[0083] A method for controlling the number of test prototype vehicles, taking the control of the number of test prototype vehicles in a new vehicle development project as an example:

[0084] This embodiment takes a mid-sized new energy passenger vehicle development project as an example to illustrate the specific implementation process of controlling the number of test prototypes using the method of the present invention.

[0085] Step 1: Obtain information on the overall vehicle development scope of the project and the test requirements list submitted by each vehicle-using department. This requirement list includes: 3 certification tests, 4 seasonal calibration tests (2 for summer and 2 for winter), 2 durability and reliability tests (300,000 km road test), 3 intelligent connectivity tests, 2 collision safety tests (frontal collision + side collision), and 6 high-altitude, high-temperature, and high-cold-weather tests (2 each for high temperature, high cold, and high altitude), totaling approximately 20 test requirements, corresponding to an initial sample vehicle requirement of 32 units from each department.

[0086] Step 2: Verify the actual test cycle of each test item against the standard test cycle. Upon verification, it was found that the actual cycle of one seasonal test could not meet the requirements of the winter window period, therefore it was decided to postpone execution, and the corresponding prototype vehicle requirement of 2 units was eliminated. The prototype vehicle requirement was reduced from 32 units to 30 units.

[0087] Step 3: Identify the logical sequence of the various test items. Upon verification, it was found that the submitted EMC test announcement was scheduled before EMC development was approved, indicating a logical error in the sequence. After issuing an alarm signal, the project team adjusted the test plan, moving the EMC test announcement to after EMC development was approved. The prototype requirements remained unchanged after the adjustment.

[0088] Step 4: Query the CAE simulation capability database. It was determined that two items in the crash safety test have reached the engineering replacement standard in CAE simulation accuracy and can be completely replaced by virtual simulation, thus eliminating the need for two corresponding prototype vehicles. Some conditions in the durability test can be partially replaced by virtual proving ground (VPG) simulation, reducing the prototype vehicle requirement by one. After this optimization step, the prototype vehicle requirement was reduced from 30 to 27 vehicles.

[0089] Step 5: Perform configuration coverage assessment. The test content of the two high-altitude, high-temperature, and high-humidity tests in the low-configuration version can be covered by the test plan in the high-configuration version, thus eliminating the requirement for two independent prototype vehicles in the low-configuration version. The prototype vehicle requirement is reduced from 27 to 25 vehicles.

[0090] Step 6: Check existing prototype vehicle inventory information. There are already 4 existing prototype vehicles that have completed some testing and are available for modification. After evaluation, it was confirmed that 3 of these can be modified to meet 3 testing requirements. Based on this, the requirement for new prototype vehicles is reduced by 3. The prototype vehicle requirement is reduced from 25 to 22.

[0091] Step 7: Confirm vehicle commonality. Through the sample replacement solution, it was confirmed that the same base prototype vehicle, by replacing the powertrain and suspension system, can simultaneously meet the preliminary operating conditions requirements of two seasonal calibration tests and one durability test. These three tests are integrated into the same base prototype vehicle, reducing the prototype vehicle requirement by two units. The prototype vehicle requirement is reduced from 22 units to 20 units.

[0092] Step 8: Compare the usage data of the 20 integrated prototype vehicles with those of similar historical projects (same platform level, similar technical complexity). Statistics show that the median number of prototype vehicles in similar historical projects was 21, and the average was 22. This solution's 20 prototype vehicles are below the historical average, thus the optimization is deemed successful.

[0093] Step 9: Submit the final plan to the project decision-making level for review and approval. Calculations showed that the total budget for 20 prototype vehicles was approximately 8.6 million yuan, while the total project budget was 20 million yuan, representing 43% of the total budget, which is below the 50% hard budget constraint. The project decision-making level approved the plan, ultimately confirming the number of test prototype vehicles at 20, a reduction of 12 from the initial requirement, representing a reduction rate of 37.5%.

[0094] As can be seen from this embodiment, the method of the present invention can systematically and effectively integrate multi-dimensional test requirements, significantly reduce the number of unreasonable prototype vehicles, and effectively reduce R&D costs.

[0095] Compared with the prior art, the present invention has the following beneficial effects:

[0096] 1. Systematic elimination method thinking: Unlike existing technologies that rely on model prediction or experience judgment, this invention adopts a nine-level step-by-step elimination method, from demand aggregation to final decision, filtering out unnecessary demands at each level, minimizing the number of unreasonable prototypes, avoiding waste or shortage of prototype resources, and achieving precise planning and cost control of R&D resources.

[0097] 2. Introduction of test logic sequence constraint verification: This invention is the first to use the logical sequence constraint between test items as an independent judgment dimension in the prototype vehicle quantity control method, which effectively avoids major resource waste problems such as announcement failure caused by improper timing arrangement and improves the engineering practicality of the method.

[0098] 3. Multi-dimensional optimization mechanism synergistic integration: This invention systematically integrates multiple optimization mechanisms such as CAE virtual simulation replacement, high configuration covering low configuration, modification and utilization of existing prototype vehicles, and replacement of prototype parts to achieve vehicle sharing, forming a complete decision-making link and significantly improving the efficiency of prototype vehicle integration.

[0099] 4. Historical data closed-loop verification: By comparing the integrated number of prototype vehicles with similar historical projects, the solution can be self-checked and further optimized to ensure that the optimization results meet industry practice standards.

[0100] 5. Hard budget constraint: For the first time, the "prototype budget shall not exceed 50% of the total project budget" is set as a quantitative red line for project control, forming a rigid cost guarantee mechanism to effectively ensure that R&D costs are controllable.

[0101] After adopting the above scheme, a systematic elimination method is used to screen and optimize layer by layer, integrate multi-dimensional test requirements, and form a reasonable number of prototype vehicles, thereby reducing R&D costs and shortening the project cycle.

Claims

1. A method for controlling the number of test prototype vehicles, characterized in that, Includes the following steps: 1) Verify test requirements and development scope; 2) Verify test cycle and standards; 3) Determine the logical order of test items; 4) Determine the feasibility of CAE virtual simulation as a substitute; 5) Determine the feasibility of configuration coverage; 6) Determine the feasibility of modifying and utilizing existing prototype vehicles; 7) Confirm the vehicle commonality of replacing prototypes to meet different test items; 8) Compare the number of integrated prototype vehicles with historical similar vehicles; 9) Determine the final number of prototype vehicles.

2. The method for controlling the number of test prototype vehicles as described in claim 1, characterized in that, In step 1) above, the development scope information of the whole vehicle development project and the test requirements submitted by each vehicle user organization are obtained. Each test requirement is checked against the development scope, and unnecessary test requirements that exceed the development scope are eliminated to generate the first round of optimized test requirement quantity.

3. The method for controlling the number of test prototype vehicles as described in claim 2, characterized in that, In step 2) above, the required test cycle and standard test cycle for each test project are obtained, including transportation time. Test cycles that do not meet the standards are identified and optimized. The optimization principle is that the cycle of one vehicle is less than 90 days. Test vehicles are required to be shared with other test projects. The number of test requirements after the second round of optimization is generated.

4. The method for controlling the number of test prototype vehicles as described in claim 3, characterized in that, In step 3) above, the development dependencies and logical order constraints between each test project are obtained, and the logical order of each test project is judged to be correct. Specifically, if the successful development of test project A is a prerequisite for the implementation of test project B, then test project B shall not be implemented before test project A is successfully developed. If there is a combination of test requirements with incorrect logical order, an alarm signal is issued, and the test plan is adjusted according to the correct logical order before continuing execution. After the logical order is judged and adjusted, the number of test requirements after the third round of optimization is generated.

5. The method for controlling the number of test prototype vehicles as described in claim 4, characterized in that, In step 4) above, a pre-built CAE simulation capability database is obtained, which records whether each test item can be completely or partially replaced by virtual simulation; each test item is judged one by one to see if it meets the CAE replacement conditions: if it meets the complete replacement conditions, the actual vehicle requirement for that test item is removed; if it meets the partial replacement conditions, the corresponding actual vehicle test times are reduced; if it does not meet the replacement conditions, the actual vehicle test requirements are retained; after the CAE replacement judgment, the number of test requirements after the fourth round of optimization is generated.

6. The method for controlling the number of test prototype vehicles as described in claim 5, characterized in that, In step 5) above, obtain the vehicle configuration information required for each test item, match and judge the low configuration test items and high configuration test items of the same vehicle, and determine whether the test content of the low configuration test items can be covered by the test of the high configuration vehicle on the same platform; if the low configuration test items can be covered by the high configuration vehicle, then remove the independent prototype vehicle requirement of the low configuration test items and integrate them into the test plan of the corresponding high configuration vehicle for execution. After configuration coverage assessment, the number of test requirements for the fifth round of optimization is generated.

7. The method for controlling the number of test prototype vehicles as described in claim 6, characterized in that, In step 6) above, obtain the inventory information of the existing prototype vehicles in the current project. The existing prototype vehicles include prototype vehicles that have completed some tests and prototype vehicles in the project inventory. Determine whether the prototype vehicle requirements of each test project can be met by modifying the existing prototype vehicles. If they can be met by modification, mark that the test project will not add new prototype vehicle requirements and include the corresponding existing prototype vehicles in the modification plan. If the requirements cannot be met through restructuring, the new prototype vehicle requirements will be retained; after assessing the utilization of existing prototype vehicles through restructuring, the sixth round of optimized test requirements will be generated.

8. The method for controlling the number of test prototype vehicles as described in claim 7, characterized in that, In step 7) above, feasibility information on the replacement of prototype vehicle parts for each test item is obtained. Component replacement includes, but is not limited to, powertrain replacement, suspension system replacement, electrical system replacement, and exterior part replacement. It is then determined whether the test requirements of two or more test items can be met by replacing different parts on the same base prototype vehicle. If sharing can be achieved by replacing parts, the multiple test items are integrated into the same base prototype vehicle, and the corresponding prototype vehicle quantity requirement is reduced. If sharing cannot be achieved by replacing parts, the individual prototype vehicle requirements are retained. After confirming vehicle commonality, the seventh round of optimized test requirement quantity is generated.

9. The method for controlling the number of test prototype vehicles as described in claim 8, characterized in that, In step 8) above, obtain historical data on similar prototype vehicles and compare the number of prototype vehicles integrated after the seventh round of optimization with the number of similar prototype vehicles in the past. If the number of integrated prototype vehicles is not higher than the average number of similar projects in the past, the optimization effect is deemed to have met the standard and proceed to the next step. If the number of integrated prototype vehicles is higher than the number of similar projects in the past, backtrack to check whether there is any omission in steps 1) to 7) and make further optimization adjustments.

10. The method for controlling the number of test prototype vehicles as described in claim 9, characterized in that, In step 9) above, the number of test prototypes after optimization and integration in steps one through eight will be finalized. The conditions for confirmation include, but are not limited to, the total budget corresponding to the final confirmed total number of test prototypes not exceeding 50% of the total budget of the entire project. If the ratio is exceeded, at least one optimization step from step 1) to step 8) is backtracked and executed until the budget constraint or requirement is met and finally confirmed.