Vehicle cost scenario determination method, device, processor and electronic device

Abstract

This application discloses a method, apparatus, processor, and electronic device for determining the cost scenario of a vehicle. The method includes: determining a primary cost scenario for the vehicle, wherein the primary cost scenario represents the cost dimensions involved in the vehicle's process from design to recycling; classifying the primary cost scenario to obtain at least one secondary cost scenario, and classifying the secondary cost scenarios to obtain at least one tertiary cost scenario, wherein each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario, and the secondary cost scenario includes different system dimension scenarios and cost management activity dimension scenarios within the vehicle; encoding the primary, secondary, and tertiary cost scenarios to obtain encoding results; and determining the target cost scenario for the vehicle based on the encoding results. This application solves the technical problem of low accuracy in determining the cost scenario of a vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle management technology, and more specifically, to a method, apparatus, processor, and electronic device for determining the cost scenario of a vehicle. Background Technology

[0002] Currently, vehicle cost management generally relies on experience-based judgment and single-dimensional classification methods, such as cost aggregation and analysis based solely on product lifecycle stages (e.g., R&D, procurement, manufacturing, sales, and disposal) or organizational functions (e.g., human resources, equipment, and logistics). Such methods lack a systematic framework, leading to overlaps or omissions in cost scenarios and making it difficult to accurately identify and trace cost elements. Therefore, the technical problem of low accuracy in determining vehicle cost scenarios persists.

[0003] There is currently no effective solution to the aforementioned technical problems. Summary of the Invention

[0004] This application provides a method, apparatus, processor, and electronic device for determining the cost scenario of a vehicle, in order to at least solve the technical problem of low accuracy in determining the cost scenario of a vehicle.

[0005] According to one aspect of the embodiments of this application, a method for determining the cost scenario of a vehicle is provided. The method may include: determining a primary cost scenario for the vehicle, wherein the primary cost scenario represents the cost dimension involved in the process from vehicle design to recycling; classifying the primary cost scenario to obtain at least one secondary cost scenario, and classifying the secondary cost scenario to obtain at least one tertiary cost scenario, wherein each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario, the secondary cost scenario includes different system dimension scenarios and cost management activity dimension scenarios in the vehicle, and the tertiary cost scenario is used to identify triggering factors that cause cost changes; encoding the primary, secondary, and tertiary cost scenarios to obtain encoding results, wherein the encoding results represent standardized identifiers for the primary, secondary, and tertiary cost scenarios; and based on the encoding results, determining the target cost scenario for the vehicle, wherein the target cost scenario represents a cost event unit triggered by a target cost-driven event in the cost analysis dimension.

[0006] Optionally, based on the coding results, the target cost scenario for the vehicle is determined, including: based on the coding results, assigning target weight coefficients to the first-level cost scenario, the second-level cost scenario, or the third-level cost scenario to obtain the target cost scenario.

[0007] Optionally, the method further includes: adjusting the target weight coefficient based on historical cost proportion, scoring results, and risk level, wherein the historical cost proportion is used to represent the proportion of the cost of different cost scenarios within a historical period to the total cost of the upper-level cost scenarios in which the different cost scenarios are located; the scoring results are used to represent the degree of influence of different cost resource allocations under different cost scenarios; and the risk level is used to represent the level of cost fluctuation caused by the external environment in different cost scenarios; and assigning the adjusted target weight coefficient to the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the target cost scenario.

[0008] Optionally, the primary cost scenario includes a cycle dimension scenario and a cost information dimension scenario. The cycle in the cycle dimension scenario is used to represent the process from vehicle design to recycling, and the cost information in the cost information dimension scenario is used to represent the cost consumed during the process from design to recycling. Determining the primary cost scenario of a vehicle includes: determining the cycle dimension scenario and the cost information dimension scenario based on a structured classification strategy, wherein the structured classification strategy is used to represent a strategy that makes the cycle dimension scenario and the cost information dimension scenario independent of each other and covers each other.

[0009] Optionally, the different systems corresponding to different system dimension scenarios include at least one of the following: body system, chassis system, power system, electronic system, trim system, and in-vehicle system. The cost management activities corresponding to the cost management activity dimension scenarios include at least one of the following: input cost management activities, equipment depreciation management activities, energy consumption management activities, logistics and warehousing management activities, quality loss management activities, and expense management activities. Classifying the primary cost scenarios yields at least one secondary cost scenario, including: classifying the primary cost scenarios based on different systems and cost management activities to obtain at least one secondary cost scenario.

[0010] Optionally, the cost-driven event types include at least one of the following: technology change events, market fluctuation events, supply chain events, production and operation events, and external environment events. The secondary cost scenarios are classified to obtain at least one tertiary cost scenario, including: according to the cost-driven event types, the secondary cost scenarios are classified to obtain at least one of the following tertiary cost scenarios: technology change event scenario, market fluctuation event scenario, supply chain event scenario, production and operation event scenario, and external environment event scenario.

[0011] Optionally, the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain the encoding result, including: encoding the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario according to the hierarchical concatenation rule to obtain the encoding result, wherein the hierarchical concatenation rule is used to represent the rule of using hyphens to separate the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to form a structured cost scenario encoding sequence.

[0012] According to another aspect of the embodiments of this application, a vehicle cost scenario determination device is also provided. The device may include: a first determining unit, configured to determine a primary cost scenario for the vehicle, wherein the primary cost scenario represents the cost dimension involved in the vehicle's process from design to recycling; a classification unit, configured to classify the primary cost scenario to obtain at least one secondary cost scenario, and classify the secondary cost scenario to obtain at least one tertiary cost scenario, wherein each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario, the secondary cost scenario includes different system dimension scenarios and cost management activity dimension scenarios within the vehicle, and the tertiary cost scenario is used to identify triggering factors that cause cost changes; an encoding unit, configured to encode the primary, secondary, and tertiary cost scenarios to obtain encoding results, wherein the encoding results represent standardized identifiers for different cost scenarios; and a second determining unit, configured to determine a target cost scenario for the vehicle based on the encoding results, wherein the target cost scenario represents a cost event unit triggered by a target cost-driven event in the cost analysis dimension.

[0013] According to another aspect of the embodiments of this application, a processor is also provided. The processor is used to run a program, wherein the program executes the methods of the embodiments of this application during runtime.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the method of the embodiments of this application when it runs.

[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the method of the embodiments of this application.

[0016] According to another aspect of the embodiments of this application, a vehicle is also provided. The vehicle includes a memory and a processor. The memory stores an executable program; the processor is used to run the program, which, when running, implements the methods described in the embodiments of this application.

[0017] In this embodiment, if it is necessary to determine the target cost scenario of a vehicle, a first-level cost scenario can be determined, wherein the first-level cost scenario represents the cost dimension involved in the process from vehicle design to recycling; the first-level cost scenario is classified to obtain at least one second-level cost scenario, and the second-level cost scenario is classified to obtain at least one third-level cost scenario, wherein each second-level cost scenario belongs to one first-level cost scenario, and each third-level cost scenario belongs to one second-level cost scenario. The second-level cost scenario includes different system dimension scenarios and cost management activity dimension scenarios in the vehicle, and the third-level cost scenario is used to identify the triggering factors that cause cost changes; the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain the encoding result, wherein the encoding result represents the standardized identifier of the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario; based on the encoding result, the target cost scenario of the vehicle is determined, wherein the target cost scenario represents the cost event unit of the vehicle in the cost analysis dimension caused by the target cost-driven event. In other words, this application embodiment uses a three-tiered progressive classification mechanism of first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, combined with coding rules, to encode the first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, thereby determining the target cost scenario of the vehicle. This achieves full coverage, non-overlapping, and quantifiable precise positioning of the vehicle's cost from macroscopic dimensions to microscopic drivers, thus solving the technical problem of low accuracy in determining the cost scenario of the vehicle and realizing the technical effect of improving the accuracy of determining the cost scenario of the vehicle. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0019] Figure 1 This is a flowchart of a method for determining the cost of a vehicle according to an embodiment of this application;

[0020] Figure 2 This is a schematic diagram of the overall architecture of a three-level cost scenario classification system according to an embodiment of this application;

[0021] Figure 3 This is a schematic diagram of a primary scene classification according to an embodiment of this application;

[0022] Figure 4 This is a schematic diagram of a secondary scene classification according to an embodiment of this application;

[0023] Figure 5 This is a schematic diagram of a three-level scene classification according to an embodiment of this application;

[0024] Figure 6 This is a schematic diagram of a scene coding system according to an embodiment of this application;

[0025] Figure 7 This is a flowchart of a scene weight calculation method according to an embodiment of this application;

[0026] Figure 8 This is a flowchart of a scenario classification application method according to an embodiment of this application;

[0027] Figure 9 This is a schematic diagram of a vehicle cost scenario determination device according to an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] According to an embodiment of this application, an embodiment of a method for determining the cost scenario of a vehicle is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0031] Figure 1 This is a flowchart of a method for determining the cost of a vehicle according to an embodiment of this application, such as... Figure 1 As shown, the method may include the following steps.

[0032] Step S102: Determine the primary cost scenario for the vehicle.

[0033] In the technical solution provided in step S102 of this application, the primary cost scenario can be used to represent the dimension of costs involved in the process from vehicle design to recycling.

[0034] In this embodiment, the primary cost scenarios can include Category A – the product lifecycle dimension and Category B – the value chain distribution dimension. Category A – the product lifecycle dimension can include five stages: A1 R&D and design, A2 procurement and supply, A3 manufacturing, A4 sales and service, and A5 end-of-life recycling, covering the complete product lifecycle from concept to end-of-life. Category B – the value chain distribution dimension can include three categories: B1 direct costs, B2 indirect costs, and B3 quality costs, covering the cost elements of the enterprise value chain.

[0035] Optionally, the aforementioned Category A scenario – product lifecycle dimension – is not simply divided into stages according to chronological order. Instead, it uses the complete existence cycle of the vehicle as a physical object as a benchmark, systematically covering five irreversible and logically closed stages from initial R&D and design, parts procurement, production line manufacturing, market sales to final scrapping and recycling. Based on the objective laws governing the physical existence and value stream transformation of vehicle products, it ensures that every cost can be located at the lifecycle node where it occurs.

[0036] Optionally, the aforementioned Category B scenario—value chain distribution dimension—takes a different approach from the perspective of internal resource allocation and cost generation mechanisms, categorizing costs into three main types: direct costs, indirect costs, and quality costs. Direct costs correspond to materials and labor that can be clearly attributed to specific products. Indirect costs cover supporting functions, such as management and R&D support, which are not directly related to production line expenditures. Quality costs are used to identify losses due to defects in prevention, identification, rework, and failure.

[0037] In this embodiment, a first-level cost scenario is constructed by paralleling two dimensions, overcoming the single-axis thinking of classification based solely on function or stage in related technologies. This transforms cost management from planar observation to three-dimensional modeling, achieving comprehensive coverage and providing complete information for subsequent classification.

[0038] Step S104: Classify the first-level cost scenarios to obtain at least one second-level cost scenario, and classify the second-level cost scenarios to obtain at least one third-level cost scenario.

[0039] In the technical solution provided in step S104 of this application, each secondary cost scenario belongs to a primary cost scenario, and each tertiary cost scenario belongs to a secondary cost scenario. The secondary cost scenario may include different system dimension scenarios and cost management activity dimension scenarios in the vehicle. The tertiary cost scenario is used to identify the triggering factors that cause cost changes.

[0040] In this embodiment, based on the established primary cost scenarios, further refinement can be achieved layer by layer to construct a nested classification system of secondary and tertiary cost scenarios. Classifying primary cost scenarios yields at least one secondary cost scenario, and classifying secondary cost scenarios yields at least one tertiary cost scenario. This process can be based on a structurally in-depth analysis using the Mutually Exclusive, Collectively Exhaustive (MECE) principle, enabling a shift from a classification framework to event-driven cost management. Here, primary cost scenarios can be simply referred to as primary scenarios, secondary cost scenarios as secondary scenarios, and tertiary cost scenarios as tertiary scenarios.

[0041] Optionally, the construction of secondary cost scenarios involves parallel segmentation from two complementary but mutually exclusive perspectives within each primary cost scenario. One is the product system dimension (corresponding to the system dimension scenario), and the other is the management activity dimension (corresponding to the cost management activity dimension scenario).

[0042] Optionally, the product system dimension focuses on the physical and functional composition of the vehicle itself, dividing it into seven core systems. These include the body system, chassis system, powertrain system, electronic and electrical system, interior and exterior trim system, intelligent connectivity system, and new energy system. These systems are the physical units that carry the value of the vehicle, and each system can correspond to independent R&D, manufacturing, and maintenance costs. For example, under "Level 1 Scenario A1 R&D and Design," a secondary scenario "2A4 Electronic and Electrical System" can be derived, precisely targeting the R&D investment in electronic components such as the intelligent cockpit and radar modules, rather than being broadly categorized as R&D expenses. Meanwhile, the management activity dimension starts from the company's operational behavior, identifying the organizational activities that support cost occurrence, such as labor costs, equipment depreciation, energy consumption, logistics and warehousing, quality losses, and management expenses. Under the same Level 1 scenario "B1 Direct Costs," secondary scenarios such as "2B1 Labor Costs" or "2B3 Energy Consumption" can be corresponding. The product system dimension and the management activity dimension have no overlap or intersection, together forming a complete description of the cost incurrence carriers.

[0043] Optionally, building upon the secondary scenario, the tertiary cost scenario further focuses on the triggering events that cause cost changes, i.e., the cost drivers. These events are not static structures, but rather dynamic, identifiable, and managerially valuable disturbances, which can include: 3T technology change events (e.g., chip upgrades, software architecture restructuring), 3M market fluctuation events (e.g., rising lithium prices, exchange rate fluctuations), 3S supply chain events (e.g., supplier switching, logistics route adjustments), 3P production and operation events (e.g., yield improvement, production line automation upgrades), and 3E external environment events (e.g., stricter environmental regulations, tariff policy adjustments). Each tertiary scenario uniquely belongs to a secondary scenario. For example, the 3T event of "intelligent cockpit chip technology upgrade" belongs to the product system "2A4 electronic and electrical systems," and cannot be mistakenly classified as "2B1 labor costs." Similarly, the 3S event of "increased logistics and warehousing costs" belongs to the management activity "2B4 logistics and warehousing," not a specific product system. This "secondary carrier-tertiary driver" binding makes costs no longer just numbers on paper, but specific events that are traceable, analyzable, and operable.

[0044] In this embodiment, at least one secondary cost scenario is obtained by classifying the primary cost scenario, and at least one tertiary cost scenario is obtained by classifying the secondary cost scenario. Since each scenario strictly follows the MECE principle, the entire system has strong logical self-consistency and scalability. When adding new energy systems or intelligent event types, there is no need to reconstruct the overall framework; only new nodes need to be added under the established dimensions, ensuring long-term applicability.

[0045] Step S106: Encode the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the encoding results.

[0046] In the technical solution of step S106 of this application, the encoding result can be used to represent the standardized identifiers of the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario.

[0047] In this embodiment, by establishing a hierarchical, structured, and semantically clear coding system, the abstract cost scenario classification results are transformed into standardized identifiers that are calculable, searchable, and systematically processed, thereby realizing the transformation of cost scenarios from conceptual descriptions to digital assets. The coding of first-level, second-level, and third-level cost scenarios can be based on MECE classification logic and employ coding rules with inherent hierarchical relationships and semantic penetration.

[0048] Optionally, the coding can be constructed according to a nested coding hierarchy of "first-level coding - second-level coding - third-level coding", using a serial structure of parent-level coding + child-level coding to form a unique identifier such as "A1-2A4-3T". The first-level coding can be used to represent a category in the lifecycle or value chain dimension (e.g., A1 represents R&D design, B2 represents indirect costs), the second-level coding can be used to represent the product system or management activity to which it belongs in that first-level scenario (e.g., 2A4 represents electrical and electronic systems, 2B1 represents human resource costs), and the third-level coding can precisely point to the type of event change that triggers cost changes (e.g., 3T represents technological change).

[0049] Optionally, each level of coding can use a unified prefix (A / B, 2A / 2B, 3T / 3M, etc.) to clearly identify the dimension and avoid semantic ambiguity. The combination of coded characters can follow the standardized format of "dimension identifier + sequence number" to ensure machine readability, human discernibility, and system traceability. For example, "A2-2A7-3M" fully expresses "cost changes in the new energy system due to market fluctuations (e.g., rising battery raw material prices) during the procurement and supply phase," and can be automatically identified and processed by the information system without further explanation.

[0050] In the embodiments of this application, the encoding realizes a precise and unique identifier for cost scenarios, enabling cost data across departments, systems, and time periods to be aligned under a unified semantic framework, thus solving the data silo problem in traditional manual reports where the same cost has multiple names and the same name refers to different contents.

[0051] Step S108: Based on the coding results, determine the target cost scenario for the vehicle.

[0052] In the technical solution of step S108 of this application, the target cost scenario can be used to represent the cost event unit triggered by the target cost driving event in the cost analysis dimension of the vehicle.

[0053] In this embodiment, based on the encoding results, abstract cost scenarios can be categorized and transformed into actionable, locatable, and analyzable target cost scenarios. That is, in a specific cost analysis task, it is the smallest cost event unit with a unique coded identifier, triggered by a specific cost-driven event.

[0054] Optionally, the target cost scenario is determined by the coding result. For example, "A1-2A4-3T" not only represents a combination of the three dimensions of "R&D design stage, electronic and electrical systems, and technology changes," but also directly points to a specific and measurable event unit. For example, the increased software development and testing costs caused by the upgrade of the smart cockpit chip architecture.

[0055] Optionally, the structured expression based on the coding system can determine the target cost scenario. For example, analysts or the system can freely combine and filter from three core dimensions according to actual needs: target cycle stage (e.g., A2 procurement and supply), target system dimension (e.g., 2A4 electrical and electronic systems), and target cost management activity dimension (e.g., 2B4 logistics and warehousing). Based on the hierarchical nesting relationship of the codes, the system automatically matches the three-level scenarios that meet the conditions. For example, if a company wants to assess the additional procurement costs of an intelligent connected system caused by chip shortages during the procurement phase, it can retrieve events that match the "A2-2A6-3S" coding path and output all relevant cost event units without the need for manual screening of original vouchers or cross-system comparisons. This matching method is based on the logical structure of the coding and features automation, high efficiency, and zero ambiguity.

[0056] In this embodiment, the target cost scenario becomes the smallest executable unit connecting the cost classification system and enterprise operational decisions. It is the core carrier for realizing cost management from descriptive statistics to predictive intervention, thereby improving the accuracy of determining the cost scenario of the vehicle.

[0057] In steps S102 to S108 of this application, if it is necessary to determine the target cost scenario of the vehicle, a first-level cost scenario of the vehicle can be determined, wherein the first-level cost scenario is used to represent the cost dimension involved in the process of vehicle design to recycling; the first-level cost scenario is classified to obtain at least one second-level cost scenario, and the second-level cost scenario is classified to obtain at least one third-level cost scenario, wherein each second-level cost scenario belongs to one first-level cost scenario, and each third-level cost scenario belongs to one second-level cost scenario. The second-level cost scenario includes different system dimension scenarios and cost management activity dimension scenarios in the vehicle, and the third-level cost scenario is used to identify the triggering factors that cause cost changes; the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain the encoding result, wherein the encoding result is used to represent the standardized identifier of the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario; based on the encoding result, the target cost scenario of the vehicle is determined, wherein the target cost scenario is used to represent the cost event unit of the vehicle in the cost analysis dimension caused by the target cost driving event. In other words, this application embodiment uses a three-tiered progressive classification mechanism of first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, combined with coding rules, to encode the first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, thereby determining the target cost scenario of the vehicle. This achieves full coverage, non-overlapping, and quantifiable precise positioning of the vehicle's cost from macroscopic dimensions to microscopic drivers, thus solving the technical problem of low accuracy in determining the cost scenario of the vehicle and realizing the technical effect of improving the accuracy of determining the cost scenario of the vehicle.

[0058] The method described in this embodiment will be further described below.

[0059] As an optional embodiment, step S108, based on the coding results, determines the target cost scenario for the vehicle, including: based on the coding results, assigning target weight coefficients to the first-level cost scenario, the second-level cost scenario, or the third-level cost scenario to obtain the target cost scenario.

[0060] In this embodiment, based on the identification of target cost scenarios, a target weight coefficient mechanism can be introduced to assign weighted values ​​to first-level cost scenarios, second-level cost scenarios, or third-level cost scenarios, so that the originally static scenario identifiers are transformed into dynamic cost influence units with priority and influence assessment capabilities.

[0061] Optionally, based on historical data and expert experience, a target weight coefficient can be assigned to each scenario. The formula for calculating the target weight coefficient W_scenario can be expressed as follows:

[0062] W_Scenario = (Historical cost percentage × 0.6) + (Strategic importance score × 0.3) + (Risk level coefficient × 0.1).

[0063] Among them, the proportion of historical costs can be obtained through statistical analysis, the strategic importance score can be scored by experts (1-10 points), and the risk level coefficient can be determined based on risk assessment (0.5-1.5).

[0064] In this embodiment of the application, based on the encoding results, target weight coefficients are assigned to the first-level cost scenario, the second-level cost scenario, or the third-level cost scenario, which can yield a more accurate target cost scenario.

[0065] As an optional embodiment, the method further includes: adjusting the target weight coefficient based on historical cost proportion, scoring results, and risk level, wherein the historical cost proportion represents the proportion of the cost of different cost scenarios within a historical period to the total cost of the upper-level cost scenarios in which the different cost scenarios are located; the scoring results represent the degree of influence of different cost resource allocations under different cost scenarios; and the risk level represents the level of cost fluctuation caused by the external environment in different cost scenarios; and assigning the adjusted target weight coefficient to the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the target cost scenario.

[0066] In this embodiment, by continuously introducing real-time feedback information on historical cost ratios, scoring results (e.g., strategic importance scores) and risk levels (e.g., risk level coefficients), iterative optimization of the weights of cost scenarios at all levels is achieved. This makes the priority assessment of cost scenarios no longer a one-time static configuration, but an intelligent feedback system that continuously evolves with the enterprise's operating environment, technological evolution, and market changes.

[0067] Optionally, the aforementioned historical cost percentages reflect the relative contribution of a specific sub-scenario to actual costs over a past period within a particular upper-level scenario (e.g., a product system or a lifecycle stage). For example, in the cost of the secondary scenario of electrical and electronic systems (2A4), the actual expenditure proportion of the "intelligent cockpit development" event is 62%. This data can be directly obtained from the aggregation results of the enterprise resource planning and cost accounting system and is an objective and quantifiable factual basis.

[0068] Alternatively, the above scoring results can be derived from the subjective assessment of the impact of different cost scenarios by experts from multiple departments such as corporate strategy, product, and finance. This reflects the strategic value of the scenario in promoting product competitiveness, supporting technological routes, and ensuring delivery quality. For example, although a certain process optimization may not account for a high percentage of current costs, it may be rated by experts as affecting the universality of the entire vehicle platform, scoring as high as 9 points, indicating that its long-term value far exceeds its short-term cost performance.

[0069] Optionally, the aforementioned risk levels can be assessed using quantitative models to evaluate the potential impact of external environmental disturbances on costs. For example, chip supply disruptions, the implementation of carbon tariffs, or upgrades to battery recycling regulations are given high risk coefficients of 1.2 to 1.5 to measure the uncertainty of significant cost fluctuations in the future.

[0070] Optionally, at each budget cycle or major strategic milestone, historical cost data can be automatically extracted to calculate the proportion, the latest score can be obtained by calling the expert scoring platform simultaneously, the risk level can be updated by accessing the external risk database, and then a new target weight coefficient can be automatically calculated by using the preset weighting formula W_scenario = (historical cost proportion × 0.6) + (strategic importance score × 0.3) + (risk level coefficient × 0.1).

[0071] In this embodiment, by continuously adjusting the target weight coefficient, the weight result constantly approaches the real influence, greatly improving the scientific nature and fairness of resource allocation, and providing technical support for vehicle companies to achieve agile, accurate and forward-looking cost management in a highly uncertain market environment.

[0072] As an optional implementation, the primary cost scenario includes a cycle dimension scenario and a cost information dimension scenario. The cycle in the cycle dimension scenario is used to represent the process from vehicle design to recycling, and the cost information in the cost information dimension scenario is used to represent the cost consumed during the process from design to recycling. Step S102, determining the primary cost scenario of the vehicle includes: determining the cycle dimension scenario and the cost information dimension scenario based on a structured classification strategy, wherein the structured classification strategy is used to represent a strategy that makes the cycle dimension scenario and the cost information dimension scenario independent of each other and overlapping.

[0073] In this embodiment, the cycle dimension scenario (corresponding to the product life cycle dimension) is a standardized division of the timeline and process stages of the entire life cycle of a vehicle product. It can cover five continuous, irreversible, and non-overlapping stages from A1 R&D and design, A2 procurement and supply, A3 production and manufacturing, A4 sales and service, and A5 scrapping and recycling, fully covering the entire process of a vehicle from conception, parts procurement, vehicle assembly, market launch to final recycling and disposal.

[0074] Optionally, the cost information dimension scenario (corresponding to the value chain distribution dimension) involves functionally classifying the essential attributes of costs from the perspective of the enterprise value chain. This can include three categories: B1 direct costs, B2 indirect costs, and B3 quality costs.

[0075] Optionally, direct costs reflect resource consumption directly tied to the product entity, indirect costs reflect the input of supporting functions, and quality costs reveal hidden waste and rework costs. These three categories are independent of each other. For example, depreciation of testing equipment during the R&D phase is an indirect cost, not a direct cost. And although repair costs for after-sales recalls occur during the sales phase, they are still classified as quality costs, not sales expenses.

[0076] Optionally, based on a structured classification strategy (such as the MECE principle), the cycle dimension scenario and the cost information dimension scenario can be determined, thereby overcoming the problem of duplicate collection of R&D expenses in traditional classification, which include both R&D stage and management expenses, and also avoiding the omission of the collection of production costs of new energy batteries as quality costs.

[0077] In this embodiment, based on a structured classification strategy, the cycle dimension scenario and the cost information dimension scenario are determined, laying the logical foundation for the accurate nesting of subsequent secondary cost scenarios and tertiary cost scenarios and the determination of dynamic target weight coefficients.

[0078] As an optional implementation method, the different systems corresponding to different system dimension scenarios include at least one of the following: body system, chassis system, power system, electronic system, trim system, and vehicle system. The cost management activities corresponding to the cost management activity dimension scenarios include at least one of the following: input cost management activities, equipment depreciation management activities, energy consumption management activities, logistics and warehousing management activities, quality loss management activities, and expense management activities. Step S104: Classify the primary cost scenarios to obtain at least one secondary cost scenario, including: classifying the primary cost scenarios based on different systems and cost management activities to obtain at least one secondary cost scenario.

[0079] In this embodiment, the system dimension scenario can be a Class A secondary scenario - product system dimension. The cost management activity dimension scenario can be a Class B secondary scenario - management activity dimension. That is, the secondary cost scenario can include both Class A secondary scenario - product system dimension and Class B secondary scenario - management activity dimension.

[0080] Optionally, the Category A Level 2 scenario - product system dimension may include 2A1 body system, 2A2 chassis system, 2A3 power system, 2A4 electronic and electrical system (corresponding to electronic system), 2A5 interior and exterior trim system (corresponding to trim system), 2A6 intelligent connected system (corresponding to vehicle system), and may also include 2A7 new energy system.

[0081] Optionally, the Class B secondary scenario - management activity dimension may include six management activity categories: 2B1 Human resource costs (corresponding to input cost management activities), 2B2 Equipment depreciation (corresponding to equipment depreciation management activities), 2B3 Energy consumption (corresponding to energy consumption management activities), 2B4 Logistics and warehousing (corresponding to logistics and warehousing management activities), 2B5 Quality loss (corresponding to quality loss management activities), and 2B6 Management expenses (corresponding to expense management activities).

[0082] In this embodiment of the application, based on different systems and cost management activities, the primary cost scenarios are classified to obtain at least one secondary cost scenario, providing a stable and accurate framework for the subsequent classification of tertiary cost scenarios.

[0083] As an optional implementation method, the cost-driven event type includes at least one of the following: technology change event, market fluctuation event, supply chain event, production and operation event, and external environment event. Step S104: Classify the secondary cost scenarios to obtain at least one tertiary cost scenario, including: classify the secondary cost scenarios according to the cost-driven event type to obtain at least one of the following tertiary cost scenarios: technology change event scenario, market fluctuation event scenario, supply chain event scenario, production and operation event scenario, and external environment event scenario.

[0084] In this embodiment, based on the secondary cost scenario, cost-driven event types can be further introduced to classify the secondary cost scenario and obtain the tertiary cost scenario.

[0085] Optionally, cost-driven event types are standardized abstractions of the business drivers that trigger cost changes. Cost-driven event types can include 3T - technology change events, 3M - market fluctuation events, 3S - supply chain events, 3P - production and operation events, and 3E - external environment events.

[0086] Optionally, the aforementioned 3T-technology change events can be design changes, process optimizations, technology upgrades, etc.

[0087] Optionally, the aforementioned 3M-market fluctuation events can be fluctuations in raw material prices, changes in exchange rates, changes in market demand, etc.

[0088] Optionally, the aforementioned 3S-supply chain events can include supplier changes, logistics adjustments, inventory optimization, etc.

[0089] Optionally, the aforementioned 3P-production operation events can be capacity adjustments, yield improvements, equipment upgrades, etc.

[0090] Optionally, the aforementioned 3E-external environmental events can include policy and regulatory changes, stricter environmental protection requirements, and emergencies.

[0091] In this embodiment of the application, secondary cost scenarios are classified according to the type of cost-driven events to obtain at least one of the following tertiary cost scenarios: technology change event scenario, market fluctuation event scenario, supply chain event scenario, production and operation event scenario, and external environment event scenario, thereby obtaining a more accurate and comprehensive tertiary cost scenario.

[0092] As an optional embodiment, step S106 encodes the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the encoding result, including: encoding the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario according to the hierarchical concatenation rule to obtain the encoding result, wherein the hierarchical concatenation rule is used to represent the rule of using hyphens to separate the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to form a structured cost scenario encoding sequence.

[0093] In this embodiment, by hierarchically serializing and encoding the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario, the originally abstract classification logic can be transformed into a standardized coding sequence that can be accurately located, automatically processed, and interacted across systems, providing underlying data anchors for subsequent cost collection, analysis, early warning, and decision support.

[0094] Optionally, hierarchical concatenation coding can follow the rule of "top-down, step-by-step, and symbol-separated". For example, using the hyphen "-" as the hierarchical separator, the first-level scenario code, the second-level scenario code, and the third-level scenario code are concatenated in a logical order from macro to specific, forming an irreversible string sequence that fully expresses the overall picture of cost occurrence. For example, the code "A1-2A4-3T" represents "Research and Design Phase" (A1) → "Electronic and Electrical Systems" (2A4) → "Technical Change Event" (3T) from left to right. Each sub-segment corresponds to a subset of the previous level scenario, forming a strict tree-like hierarchical relationship.

[0095] Optionally, Level 1 cost scenarios can use a single uppercase letter followed by a number, for example, A1 to A5 represent lifecycle stages, and B1 to B3 represent value chain dimensions. Level 2 cost scenarios add a "2" prefix to the Level 1 code to distinguish levels; for example, 2A1 to 2A7 represent product systems, and 2B1 to 2B6 represent management activities, ensuring a natural structural distinction from Level 1 codes. Level 3 scenarios use "3" followed by the first letter of the event type, such as 3T, 3M, 3S, 3P, and 3E, corresponding to five types of events: technology change, market fluctuations, supply chain, production operations, and external environment, respectively—concise and with industry-wide recognizability. The hyphen "-" is used as a separator.

[0096] In this embodiment, if it is necessary to determine the target cost scenario of a vehicle, a first-level cost scenario can be determined, wherein the first-level cost scenario represents the cost dimension involved in the process from vehicle design to recycling; the first-level cost scenario is classified to obtain at least one second-level cost scenario, and the second-level cost scenario is classified to obtain at least one third-level cost scenario, wherein each second-level cost scenario belongs to one first-level cost scenario, and each third-level cost scenario belongs to one second-level cost scenario. The second-level cost scenario includes different system dimension scenarios and cost management activity dimension scenarios in the vehicle, and the third-level cost scenario is used to identify the triggering factors that cause cost changes; the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain the encoding result, wherein the encoding result represents the standardized identifier of the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario; based on the encoding result, the target cost scenario of the vehicle is determined, wherein the target cost scenario represents the cost event unit of the vehicle in the cost analysis dimension caused by the target cost-driven event. In other words, this application embodiment uses a three-tiered progressive classification mechanism of first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, combined with coding rules, to encode the first-level cost scenarios, second-level cost scenarios, and third-level cost scenarios, thereby determining the target cost scenario of the vehicle. This achieves full coverage, non-overlapping, and quantifiable precise positioning of the vehicle's cost from macroscopic dimensions to microscopic drivers, thus solving the technical problem of low accuracy in determining the cost scenario of the vehicle and realizing the technical effect of improving the accuracy of determining the cost scenario of the vehicle.

[0097] The technical solutions of the embodiments of this application will be illustrated below with reference to preferred embodiments.

[0098] Currently, the automotive industry is facing multiple challenges, including new energy transformation, intelligent upgrading, and supply chain restructuring, significantly increasing the complexity and difficulty of cost control. Traditional cost management methods rely heavily on experience-based judgment, lacking a systematic analytical framework and dynamic response mechanism, leading to the following problems: Low cost forecasting accuracy, failing to accurately predict the impact of macroeconomic factors, market competition, and technological changes on costs; Delayed decision-making response, making it difficult to achieve pre-emptive control through post-event analysis, resulting in missed optimal decision-making opportunities; Incomplete scenario coverage, lacking a comprehensive cost control system covering all scenarios from strategy to execution, and from routine to emergency situations; Insufficient systemicity, making it difficult to achieve systemic cost optimization throughout the entire product lifecycle through localized optimization.

[0099] In related technologies, existing cost management methods typically employ a single-dimensional classification approach, such as classifying only by product lifecycle stage or organizational function. This lack of a multi-dimensional, multi-level systematic classification system leads to blind spots and overlaps in cost management. Traditional classification methods do not adhere to the MECE principle, resulting in overlapping or omissions between scenarios, hindering accurate cost aggregation and traceability. Existing methods often only have one or two levels of classification, failing to delve into specific cost-driving events and thus struggling to support refined cost control and decision analysis. Furthermore, traditional classification methods lack dynamic scalability, making them ill-suited to the rapidly changing technological and market environment of the automotive industry, such as the emergence of new energy and intelligent technologies.

[0100] To address the aforementioned issues, this application proposes a vehicle lifecycle cost scenario classification method based on the MECE principle. By constructing a three-level cost scenario classification system, it covers the entire product lifecycle and value chain, achieving comprehensive cost management. Strictly adhering to the MECE principle, it ensures that each level of scenario is independent and completely exhaustive, avoiding duplication and omissions in cost aggregation. The three-level classification delves into specific cost-driving events, supporting precise cost attribution analysis and the formulation of control measures. The classification system has good scalability, allowing new scenario categories to be added based on industry developments. In practical applications, this method improves cost aggregation accuracy by 40% and cost analysis efficiency by 60%.

[0101] The embodiments of this application will be further described below.

[0102] Figure 2 This is a schematic diagram of the overall architecture of a three-level cost scenario classification system according to an embodiment of this application, as shown below. Figure 2 As shown, the three-level cost scenario classification system 200 includes first-level scenario 201, second-level scenario - product system dimension 2021, second-level scenario - management activity dimension 2022, and third-level scenario 203.

[0103] Level 1 Scenario 201 includes Category A Scenario - Product Lifecycle Dimension 2011 and Category B Scenario - Value Chain Distribution Dimension 2012. Category A Scenario - Product Lifecycle Dimension 2011 includes A1 R&D and Design, A2 Procurement and Supply, A3 Manufacturing, A4 Sales and Service, and A5 End-of-Life and Recycling. Category B Scenario - Value Chain Distribution Dimension 2012 includes B1 Direct Costs, B2 Indirect Costs, and B3 Quality Costs.

[0104] The second-level scenario consists of the Product System Dimension 2021 and the Management Activity Dimension 2022. The Product System Dimension 2021 includes 2A1 Body System, 2A2 Chassis System, 2A3 Powertrain System, 2A4 Electronic and Electrical System, 2A5 Interior and Exterior System, 2A6 Intelligent Connectivity System, and 2A7 New Energy System. The Management Activity Dimension 2022 includes 2B1 Labor Costs, 2B2 Equipment Depreciation, 2B3 Energy Consumption, 2B4 Logistics and Warehousing, 2B5 Quality Losses, and 2B6 Management Expenses.

[0105] Level 3 scenario 203 includes 3T - technology change events, 3M - market fluctuation events, 3S - supply chain events, 3P - production and operation events, and 3E - external environment events.

[0106] Figure 3 This is a schematic diagram of a primary scene classification according to an embodiment of this application, such as... Figure 3 As shown, the primary scenario classification includes Category A scenarios - product lifecycle dimension 301 and Category B scenarios - value chain distribution dimension 302.

[0107] Category A scenario - Product lifecycle dimension 301 includes A1 R&D and design, A2 Procurement and supply, A3 Manufacturing, A4 Sales and service, and A5 End-of-life recycling.

[0108] Category B scenario - Value chain distribution dimension 302 includes B1 direct costs, B2 indirect costs, and B3 quality costs.

[0109] Figure 4 This is a schematic diagram of a secondary scene classification according to an embodiment of this application, such as... Figure 4 As shown, the secondary scenario classification includes Category A secondary scenario - product system dimension 401 and Category B secondary scenario - management activity dimension 402.

[0110] Figure 5 This is a schematic diagram of a three-level scene classification according to an embodiment of this application, such as... Figure 5 As shown, the three-level scenarios include 3T - Technology Change Event 501, 3M - Market Fluctuation Event 502, 3S - Supply Chain Event 503, 3P - Production and Operation Event 504, and 3E - External Environment Event 505.

[0111] 3T-Technical Change Event 501 includes design changes, process optimizations, and technology upgrades.

[0112] 3M-Market Volatility Event 502 includes fluctuations in raw material prices, exchange rate changes, and changes in market demand.

[0113] 3S - Supply Chain Event 503 includes supplier changes, logistics adjustments, and inventory optimization.

[0114] 3P - Production Operations Event 504, including capacity adjustment, yield improvement, and equipment upgrade.

[0115] 3E - External Environmental Events 505, including policy and regulatory changes, increased environmental requirements, and emergencies.

[0116] Figure 6 This is a schematic diagram of a scene coding system according to an embodiment of this application, such as... Figure 6 As shown, the scene encoding system 600 includes: encoding rule 601 and encoding example 602.

[0117] Each scenario is assigned a unique code, with coding rule 601 being: Level 1 Code - Level 2 Code - Level 3 Code. Level 1 codes include Category A: Product Lifecycle Dimensions (A1-A5) and Category B: Value Chain Distribution Dimensions (B1-B3). Level 2 codes include Product System Dimensions (2A1-2A7) and Management Activity Dimensions (2B1-2B6). Level 3 codes include 3T (Technology Change), 3M (Market Fluctuations), 3S (Supply Chain), 3P (Production and Operations), and 3E (External Environment).

[0118] Encoding example 602, for example, A1-2A4-3T represents the upgrade of smart cockpit chip technology (technology change event); A2-2A4-3M represents the fluctuation of chip supply price (market fluctuation event); A2-2A4-3S represents the switch of supplier from A to B (supply chain event); A3-2A4-3P represents the automation transformation of electronic and electrical assembly line (production operation event).

[0119] Figure 7 This is a flowchart of a scene weight calculation method according to an embodiment of this application, such as... Figure 7 As shown, the method may include the following steps.

[0120] Step S701: Input data.

[0121] In this embodiment, data can be entered first.

[0122] Step S702: The risk level coefficient is determined based on the risk assessment (0.5-1.5).

[0123] In this embodiment, the risk level coefficient can be determined based on a risk assessment. The risk level coefficient can be between 0.5 and 1.5.

[0124] Step S703: The strategic importance score is given by experts (1-10 points).

[0125] In this embodiment, strategic importance can be scored by experts (1-10 points).

[0126] Step S704: The historical cost percentage is obtained through statistical analysis.

[0127] In this embodiment, the historical cost percentage can be obtained through statistical analysis.

[0128] Step S705: Is the data integrity complete?

[0129] In this embodiment, it can be determined whether the data is complete. If it is complete, step S706 is executed. Otherwise, step S707 is executed.

[0130] Step S706: Calculate scene weights.

[0131] In this embodiment, if the data integrity is complete, the scene weight can be calculated.

[0132] Step S707: Add data.

[0133] In this embodiment, if the data integrity is incomplete, data can be added.

[0134] Step S708, W_Scenario = (Historical cost percentage × 0.6) + (Strategic importance score × 0.3) + (Risk level coefficient × 0.1).

[0135] In this embodiment, a weight coefficient can be assigned to each scenario based on historical data and expert experience. The weight calculation formula is W_scenario = (historical cost ratio × 0.6) + (strategic importance score × 0.3) + (risk level coefficient × 0.1).

[0136] Step S709: Output scene weight values.

[0137] In this embodiment, scene weight values ​​can be output.

[0138] Step S710: Verify the reasonableness of the weights.

[0139] In this embodiment, it can be determined whether the weight rationality verification is reasonable. If it is reasonable, the execution ends. Otherwise, step S711 is executed.

[0140] Step S711: Adjust the input parameters.

[0141] In this embodiment, if the weight rationality verification is not reasonable, the input parameters are adjusted.

[0142] The following section will further illustrate this using the example of cost-based application scenarios in electronic and electrical systems.

[0143] Figure 8 This is a flowchart of a scene classification application method according to an embodiment of this application, such as... Figure 8 As shown, the method includes the following steps.

[0144] Step S801, Level 1 scene recognition.

[0145] In this embodiment, the first-level scenario identification yields three lifecycle stages: A1 R&D and design, A2 procurement and supply, and A3 production and manufacturing, as well as two value chain categories: B1 direct costs and B2 indirect costs.

[0146] Step S802, secondary scene subdivision.

[0147] In this embodiment, at the product system level, it can be identified as 2A4 electronic and electrical system; at the management activity level, it involves 2B1 human resource costs, 2B3 energy consumption, and 2B4 logistics and warehousing.

[0148] Step S803, Level 3 scene recognition.

[0149] In this embodiment, specific cost-driving events are identified as follows: A1-2A4-3T: Smart cockpit chip technology upgrade (technology change event); A2-2A4-3M: Chip supply price fluctuation (market fluctuation event); A2-2A4-3S: Supplier switch from A to B (supply chain event); A3-2A4-3P: Automation transformation of electronic and electrical assembly lines (production operation event).

[0150] Step S804: Calculate scene weights.

[0151] In this embodiment, the intelligent cockpit accounts for 62% of the cost of the electronic and electrical systems, has a strategic importance score of 9, and a risk level of 1.2.

[0152] W_Smart Cockpit = 0.62 × 0.6 + 0.9 × 0.3 + 1.2 × 0.1 = 0.372 + 0.27 + 0.12 = 0.762

[0153] Step S805, application effect.

[0154] In this embodiment, the company successfully identified 18 specific cost-driving events using this classification method, formulated targeted cost reduction measures, and ultimately achieved a 12.3% reduction in the cost of electronic and electrical systems.

[0155] The following section will further illustrate this using the full lifecycle cost scenario classification application as an example.

[0156] Primary scenario coverage includes five lifecycle stages (A1-A5) and three value chain categories (B1-B3), totaling eight primary scenarios.

[0157] Secondary scenario coverage: 7 scenarios (2A1-2A7) in the product system dimension and 6 scenarios (2B1-2B6) in the management activity dimension, for a total of 13 secondary scenarios.

[0158] Level 3 scene recognition: A total of 127 specific cost-driven events were identified in 13 Level 2 scenes, distributed across 5 event types (3T, 3M, 3S, 3P, 3E).

[0159] Cost aggregation verification: Through this classification system, enterprises have achieved accurate aggregation of all costs, increasing the cost aggregation accuracy rate from 73% to 98% and improving cost analysis efficiency by 60%.

[0160] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0161] According to an embodiment of this application, a vehicle cost scenario determination device is also provided. It should be noted that this vehicle cost scenario determination device can be used to execute the vehicle cost scenario determination method in the embodiments.

[0162] Figure 9 This is a schematic diagram of a vehicle cost scenario determination device according to an embodiment of this application, such as... Figure 9 As shown, the cost scenario determination device 900 for the vehicle may include: a first determination unit 902, a classification unit 904, an encoding unit 906, and a second determination unit 908.

[0163] The first determining unit 902 is used to determine the first-level cost scenario of the vehicle, wherein the first-level cost scenario is used to represent the dimension of costs involved in the process of vehicle design to recycling.

[0164] Classification unit 904 is used to classify primary cost scenarios to obtain at least one secondary cost scenario, and to classify secondary cost scenarios to obtain at least one tertiary cost scenario. Each secondary cost scenario belongs to a primary cost scenario, and each tertiary cost scenario belongs to a secondary cost scenario. The secondary cost scenarios include different system dimension scenarios and cost management activity dimension scenarios in the vehicle. The tertiary cost scenarios are used to identify the triggering factors that cause cost changes.

[0165] Encoding unit 906 is used to encode the first-level cost scenario, the second-level cost scenario and the third-level cost scenario to obtain the encoding result, wherein the encoding result is used to represent the standardized identifier of different cost scenarios.

[0166] The second determining unit 908 is used to determine the target cost scenario of the vehicle based on the coding results, wherein the target cost scenario is used to represent the cost event unit of the vehicle in the cost analysis dimension caused by the target cost driving event.

[0167] Optionally, the second determining unit 908 includes: an allocation subunit, used to allocate target weight coefficients to a first-level cost scenario, a second-level cost scenario, or a third-level cost scenario based on the coding results, so as to obtain a target cost scenario.

[0168] Optionally, the cost scenario determination device 900 for the vehicle further includes: an adjustment unit, used to adjust the target weight coefficient based on historical cost proportion, scoring results, and risk level, wherein the historical cost proportion represents the proportion of the cost of different cost scenarios within a historical period to the total cost of the upper-level cost scenario in which the different cost scenarios are located, the scoring results represent the degree of influence of different cost resource allocations under different cost scenarios, and the risk level represents the level of cost fluctuation caused by the external environment in different cost scenarios; and an allocation unit, used to allocate the adjusted target weight coefficient to the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the target cost scenario.

[0169] Optionally, the first-level cost scenario includes a cycle dimension scenario and a cost information dimension scenario. The cycle in the cycle dimension scenario is used to represent the process from vehicle design to recycling, and the cost information in the cost information dimension scenario is used to represent the cost consumed during the process from design to recycling. The first determining unit 902 includes: a determining subunit, used to determine the cycle dimension scenario and the cost information dimension scenario based on a structured classification strategy, wherein the structured classification strategy is used to represent a strategy that makes the cycle dimension scenario and the cost information dimension scenario independent of each other and overlapping.

[0170] Optionally, the different systems corresponding to different system dimension scenarios include at least one of the following: body system, chassis system, power system, electronic system, trim system, and in-vehicle system. The cost management activities corresponding to the cost management activity dimension scenarios include at least one of the following: input cost management activities, equipment depreciation management activities, energy consumption management activities, logistics and warehousing management activities, quality loss management activities, and expense management activities. The classification unit 904 includes: a first classification subunit, used to classify the first-level cost scenarios based on different systems and cost management activities to obtain at least one second-level cost scenario.

[0171] Optionally, the cost-driven event types include at least one of the following: technology change events, market fluctuation events, supply chain events, production and operation events, and external environment events. The classification unit 904 includes a second classification subunit, used to classify the secondary cost scenarios according to the cost-driven event types, to obtain at least one of the following tertiary cost scenarios: technology change event scenario, market fluctuation event scenario, supply chain event scenario, production and operation event scenario, and external environment event scenario.

[0172] Optionally, the encoding unit 906 includes an encoding subunit, used to encode the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario according to the hierarchical concatenation rules to obtain the encoding result, wherein the hierarchical concatenation rules are used to represent the rules for separating the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario using hyphens to form a structured cost scenario encoding sequence.

[0173] In this embodiment, a first determining unit 902 determines a primary cost scenario for the vehicle, where the primary cost scenario represents the cost dimension involved in the vehicle's process from design to recycling. A classification unit 904 classifies the primary cost scenario to obtain at least one secondary cost scenario, and classifies the secondary cost scenario to obtain at least one tertiary cost scenario. Each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario. The secondary cost scenario includes different system dimension scenarios and cost management activity dimension scenarios within the vehicle. The tertiary cost scenario is used to identify triggering factors that cause cost changes. An encoding unit 906 encodes the primary, secondary, and tertiary cost scenarios to obtain encoding results, where the encoding results represent standardized identifiers for different cost scenarios. A second determining unit 908 determines the target cost scenario for the vehicle based on the encoding results, where the target cost scenario represents the cost event unit triggered by a target cost-driven event in the cost analysis dimension. This solves the technical problem of low accuracy in determining the vehicle's cost scenario and achieves the technical effect of improving the accuracy of determining the vehicle's cost scenario.

[0174] According to another aspect of the embodiments of this application, a processor is also provided. The processor is used to run a program, wherein the program executes the methods of the embodiments of this application during runtime.

[0175] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the method of the embodiments of this application when it runs.

[0176] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the method of the embodiments of this application.

[0177] According to another aspect of the embodiments of this application, a vehicle is also provided. The vehicle includes a memory and a processor. The memory stores an executable program; the processor is used to run the program, which, when running, implements the methods described in the embodiments of this application.

[0178] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0179] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0180] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0181] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0182] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0183] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for determining the cost scenario of a vehicle, characterized in that, include: Determine the primary cost scenario for the vehicle, wherein the primary cost scenario represents the dimension of costs involved in the process from design to recycling of the vehicle; The primary cost scenarios are classified to obtain at least one secondary cost scenario, and the secondary cost scenarios are classified to obtain at least one tertiary cost scenario. Each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario. The secondary cost scenarios include different system dimension scenarios and cost management activity dimension scenarios in the vehicle. The tertiary cost scenarios are used to identify triggering factors that cause cost changes. The first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain an encoding result, wherein the encoding result is used to represent the standardized identifier of the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario; Based on the encoding results, the target cost scenario of the vehicle is determined, wherein the target cost scenario is used to represent the cost event unit of the vehicle in the cost analysis dimension caused by the target cost driving event.

2. The method according to claim 1, characterized in that, Based on the encoding results, the target cost scenario for the vehicle is determined, including: Based on the encoding results, target weight coefficients are assigned to the first-level cost scenario, the second-level cost scenario, or the third-level cost scenario to obtain the target cost scenario.

3. The method according to claim 2, characterized in that, The method further includes: Based on historical cost proportions, scoring results, and risk levels, the target weight coefficients are adjusted. The historical cost proportions represent the proportion of the costs of different cost scenarios within a historical period to the total costs of the upper-level cost scenarios in which the different cost scenarios are located. The scoring results represent the degree of influence of different cost resource allocations under different cost scenarios. The risk level represents the level of cost fluctuations caused by the external environment in different cost scenarios. The adjusted target weight coefficients are assigned to the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain the target cost scenario.

4. The method according to claim 1, characterized in that, The primary cost scenario includes a cycle-dimensional scenario and a cost information-dimensional scenario. The cycle in the cycle-dimensional scenario represents the process from vehicle design to recycling, and the cost information in the cost information-dimensional scenario represents the costs incurred during the process from design to recycling. Determining the primary cost scenario for the vehicle includes: Based on a structured classification strategy, the cycle dimension scenario and the cost information dimension scenario are determined, wherein the structured classification strategy is used to represent a strategy that makes the cycle dimension scenario and the cost information dimension scenario independent of each other and overlapping.

5. The method according to claim 1, characterized in that, The different systems corresponding to the different system dimension scenarios include at least one of the following: body system, chassis system, powertrain system, electronic system, trim system, and in-vehicle system. The cost management activities corresponding to the cost management activity dimension scenarios include at least one of the following: input cost management activities, equipment depreciation management activities, energy consumption management activities, logistics and warehousing management activities, quality loss management activities, and expense management activities. Classifying the primary cost scenarios yields at least one secondary cost scenario, including: Based on the different systems and the cost management activities, the primary cost scenarios are classified to obtain at least one secondary cost scenario.

6. The method according to claim 5, characterized in that, The cost-driving event types include at least one of the following: technology change events, market fluctuation events, supply chain events, production and operation events, and external environment events. Classifying the secondary cost scenarios yields at least one tertiary cost scenario, including: Based on the cost-driven event types, the secondary cost scenarios are classified to obtain at least one of the following tertiary cost scenarios: technology change event scenarios, market fluctuation event scenarios, supply chain event scenarios, production and operation event scenarios, and external environment event scenarios.

7. The method according to any one of claims 1 to 6, characterized in that, The first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded to obtain the encoding results, including: The first-level cost scenario, the second-level cost scenario, and the third-level cost scenario are encoded according to the hierarchical concatenation rule to obtain the encoding result. The hierarchical concatenation rule is used to represent the rule of using hyphens to separate the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to form a structured cost scenario encoding sequence.

8. A device for determining the cost scenario of a vehicle, characterized in that, include: The first determining unit is used to determine the primary cost scenario of the vehicle, wherein the primary cost scenario is used to represent the dimension of costs involved in the process of the vehicle from design to recycling; A classification unit is used to classify the primary cost scenario to obtain at least one secondary cost scenario, and to classify the secondary cost scenario to obtain at least one tertiary cost scenario. Each secondary cost scenario belongs to one primary cost scenario, and each tertiary cost scenario belongs to one secondary cost scenario. The secondary cost scenario includes different system dimension scenarios and cost management activity dimension scenarios in the vehicle. The tertiary cost scenario is used to identify triggering factors that cause cost changes. The encoding unit is used to encode the first-level cost scenario, the second-level cost scenario, and the third-level cost scenario to obtain an encoding result, wherein the encoding result is used to represent a standardized identifier for different cost scenarios; The second determining unit is used to determine the target cost scenario of the vehicle based on the encoding result, wherein the target cost scenario is used to represent the cost event unit of the vehicle in the cost analysis dimension caused by the target cost driving event.

9. A processor, characterized in that, The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 7 when it runs.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 7.

12. A vehicle, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

Images