Vehicle part data processing method and related equipment

Abstract

The invention discloses a vehicle part data processing method and related equipment, and relates to the technical field of data processing.The method comprises the steps that assembly parts and sub-parts are coded, and assembly codes and sub-part codes are obtained; establishing a mapping relation between the assembly codes and the sub-part codes according to the assembly requirements of the assembly parts on the sub-parts; and in response to an order request for the assembly part, generating order data for the sub-parts according to the mapping relationship. According to the invention, through establishment of the coding and mapping relation, automation, precision and high efficiency of part management are realized, and material management and production scheduling in the production process are optimized.

Description

Technical Field

[0001] The present application relates to the technical field of data processing, and more specifically, to a vehicle component data processing method and related equipment. Background Art

[0002] With the continuous development of the automobile manufacturing industry, modern automobiles need to process a large amount of parts data during the production process, including various assembly parts and their sub-parts. In the entire production chain, how to efficiently manage and track the orders and assembly requirements of these parts has become a key issue; especially in the complex automobile production process, there is a close assembly relationship between assembly parts and sub-parts. Accurate part coding and order data generation are crucial to ensuring production efficiency, reducing management costs, and ensuring the accuracy of production plans.

[0003] In the prior art, parts management usually relies on managing assembly parts and sub-parts separately. However, this management method has certain limitations, because the assembly requirements between assembly parts and sub-parts are not fully considered, resulting in the fact that in actual operation, the ordering and inventory management of parts are often disconnected; in addition, when dealing with complex assembly relationships, the prior art usually only manages based on the basic information of parts, and fails to fully utilize the mapping relationship between parts to achieve automatic data generation and order management; this makes it impossible for the system to accurately and timely generate order data for sub-parts when responding to order requests, thereby affecting the overall production efficiency and timely supply of materials. That is, the prior art has technical problems such as insufficient accuracy, efficiency and automation level of vehicle parts management. Summary of the invention

[0004] A series of simplified concepts are introduced in the summary of the invention, which will be further described in detail in the detailed description. The summary of the invention of this application does not mean to attempt to define the key features and essential technical features of the technical solution claimed for protection, nor does it mean to attempt to determine the scope of protection of the technical solution claimed for protection.

[0005] The vehicle component data processing method and related devices provided in the present application can realize the automation, precision and efficiency of component management through the establishment of coding and mapping relationships, and optimize the material management and production scheduling in the production process.

[0006] In a first aspect, the present application provides a vehicle component data processing method, comprising: encoding an assembly component and a sub-component to obtain an assembly code and a sub-component code; establishing a mapping relationship between the assembly code and the sub-component code according to the assembly requirements of the assembly component for the sub-component; and in response to an order request for the assembly component, generating order data for the sub-component according to the mapping relationship.

[0007] In some embodiments, the mapping relationship includes a type mapping and a quantity mapping; the generating of order data for the sub-components according to the mapping relationship in response to an order request for the assembly component includes: in response to an order request for the assembly component, determining a target sub-component among the sub-components according to the type mapping; determining quantity information of the target sub-component according to the quantity mapping; and determining the target sub-component and the quantity information as the order data.

[0008] In some embodiments, encoding the assembly components and sub-components to obtain the assembly code and the sub-component code includes: encoding the assembly components according to the type, version and assembly requirements of the assembly components to obtain the assembly code, wherein the assembly code includes assembly type information, assembly version information and assembly sub-component information; encoding the sub-components according to the type and version of the sub-components to obtain the sub-component code, wherein the sub-component code includes sub-component type information and sub-component version information.

[0009] In some embodiments, after establishing a mapping relationship between the assembly code and the sub-component code based on the assembly requirements of the assembly component for the sub-component, the method further includes: updating the sub-component version information in the sub-component code in response to a design change request for the sub-component; and updating the assembly version information of the assembly code corresponding to the sub-component code based on the mapping relationship.

[0010] In some embodiments, the assembly components are encoded according to the type, version and assembly requirements of the assembly components to obtain the assembly code, including: generating an assembly type text, an assembly version text, a sub-component type text and a sub-component quantity text according to the type, version and assembly requirements of the assembly components; generating the assembly code according to the assembly type text, the assembly version text, the sub-component type text and the sub-component quantity text.

[0011] In some embodiments, the assembly code is generated based on the assembly type text, the assembly version text, the sub-component type text and the sub-component quantity text, including: concatenating the sub-component type text and the sub-component quantity text to obtain a sub-component information text; performing hash function calculation on the sub-component information text to obtain a sub-component summary text; and concatenating the assembly type text, the assembly version text and the sub-component summary text to obtain the assembly code.

[0012] In some embodiments, encoding the sub-component according to the type and version of the sub-component to obtain the sub-component code includes: generating a sub-component type text and a sub-component version text according to the type and version of the sub-component; and concatenating the generated sub-component type text and the sub-component version text based on a preset delimiter to obtain the sub-component code.

[0013] In a second aspect, the present application also provides a vehicle component data processing device, comprising: a coding generation unit, used to encode assembly components and sub-components to obtain assembly codes and sub-component codes; a mapping generation unit, used to establish a mapping relationship between the assembly code and the sub-component code according to the assembly requirements of the assembly component for the sub-component; and an order generation unit, used to respond to an order request for the assembly component and generate order data for the sub-component according to the mapping relationship.

[0014] In a third aspect, the present application further provides an electronic device, comprising: a memory and a processor, wherein the processor is configured to implement the steps of the vehicle component data processing method described in the first aspect when executing a computer program stored in the memory.

[0015] In a fourth aspect, the present application further provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the vehicle component data processing method described in the first aspect.

[0016] In a fifth aspect, the present application also provides a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implements the vehicle component data processing method provided in an embodiment of the present application.

[0017] In summary, the present application ensures that the assembly requirements between the assembly components and their sub-components can be accurately recorded by encoding the assembly components and sub-components respectively and establishing a mapping relationship between them. This accurate mapping relationship enables the corresponding sub-component order data to be automatically generated when responding to the order request of the assembly components, avoiding manual calculations and data processing errors, significantly improving work efficiency, reducing manual intervention and operational errors, and improving management accuracy and efficiency; and enables the order data of the assembly components and sub-components to be synchronized in real time, ensuring that the supply of parts in the production plan is connected with the actual assembly requirements, avoiding production delays and material waste caused by untimely or missing orders, optimizing the production process, and enhancing the coordination and predictability of the production plan. In summary, the vehicle component data processing method provided by the present application realizes the automation, precision and efficiency of component management through the establishment of encoding and mapping relationships, and optimizes material management and production scheduling in the production process. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present specification. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0019] Figure 1 A schematic flow chart of a vehicle component data processing method provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of a vehicle component data processing device provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] Terms in the specification, claims and drawings of this application, such as "first", "second", "third", "fourth", etc. (if any), are used to distinguish similar objects rather than to describe a specific order or sequence. Therefore, it is understood that these terms can be used interchangeably where appropriate, so that the described embodiments can be implemented in a different order unless otherwise specified in the diagram or description. In addition, the terms "is" and "has" and any variations thereof in this application are intended to cover all possible constituent elements on a non-exclusive basis. For example, a process, method, system, product or device comprising a number of steps or units is not necessarily limited to the steps or units that are explicitly listed, but may also include other steps or units that are not explicitly listed, or steps or units that are inherent to the process, method, product or device.

[0023] In this application, a "module" or "unit" refers to a computer program or a part of a computer program that has a specific function and works in conjunction with other related parts to achieve a predetermined goal. These modules or units can be implemented by software, hardware (such as processing circuits or memories), or a combination of the two. One or more processors or memories can implement one or more modules or units. At the same time, each module or unit can also be a part of a larger module or unit.

[0024] The technical solutions in the present application will be described in detail below in conjunction with the drawings in the embodiments. It should be noted that the described embodiments are only a part of the present application, not all embodiments. In the following description, the "some embodiments" mentioned are only subsets of all possible embodiments, which may be the same or different subsets, and different embodiments may be combined with each other without conflict.

[0025] Figure 1 is a flow chart of a vehicle component data processing method provided by an embodiment of the present application. Figure 1 The vehicle component data processing method provided in the embodiment of the present application may include the following steps 101 to 103:

[0026] Step 101, encode the assembly components and sub-components to obtain assembly codes and sub-component codes;

[0027] In some examples, an assembly part refers to a final component composed of multiple sub-components. In a car, multiple sub-components are assembled to form a fully functional component; an assembly part can be a vehicle's engine, door, chassis, etc. A sub-component refers to a single part or smaller component that constitutes an assembly part, and is a component of an assembly part; for example, the piston, crankshaft, cylinder head, etc. in a car engine (assembly part) are all sub-components. The assembly code is a unique identifier assigned to each assembly part to distinguish between different types and versions of assembly parts; for example, the code of an engine assembly part may be "ENG-V1", where "ENG" represents the engine and "V1" represents the version number. The sub-component code is a unique identifier assigned to each sub-component to distinguish between different types and versions of sub-components; for example, the sub-component code of a piston may be "PISTON-V1", where "PISTON" represents the piston and "V1" represents the version number.

[0028] By implementing step 101, unique codes are assigned to assembly components and sub-components respectively, which can ensure that each component has a clear identification, help avoid confusion of component information, and ensure that in various links such as production, orders, and inventory, relevant personnel can clearly and accurately identify each component, thereby improving the standardization and consistency of data management.

[0029] Step 102, establishing a mapping relationship between the assembly code and the sub-component code according to the assembly requirements of the assembly component for the sub-components;

[0030] In some examples, assembly requirements refer to the number, type, and specifications of the required sub-components of the assembly component during the manufacturing process, which clearly defines the number of sub-components and their corresponding quantities that a certain assembly component relies on during the production or assembly process; assembly requirements can be obtained through assembly drawings, bill of materials (BOM) and other documents in the product design stage; for example, in the assembly requirements of a car engine, the engine assembly may require 6 pistons, 1 crankshaft, 1 cylinder head and other sub-components, and the quantity and version of each sub-component have clear requirements. The mapping relationship refers to the association established between the assembly component and its sub-components to ensure that the assembly requirements of the assembly component can be accurately converted into the specifications, quantity and other information of the required sub-components; for example, the engine assembly code is "ENG-V1", and the mapping relationship of the assembly component may point to 6 pistons (coded "PISTON-V1"), 1 crankshaft (coded "CRANK-V1"), 1 cylinder head (coded "CYLINDER-V1"), etc.

[0031] For example, based on the product design and assembly drawings, the assembly requirements of the assembly components and sub-components can be clearly defined, including the types, quantities and specifications of sub-components required for each assembly component; then, based on these assembly requirements, a mapping relationship can be established for each assembly component and its sub-components, such as mapping the "ENG-V1" assembly component to 6 "PISTON-V1", 1 "CRANK-V1" and other sub-components.

[0032] By implementing step 102, a mapping relationship between assembly components and sub-components is established, ensuring that the production demand for each assembly component can be correctly mapped to the required sub-components, which helps to avoid incorrect distribution or shortage of parts due to inaccurate assembly requirements during the production process; so that when planning production and scheduling materials, the demand for each component can be accurately predicted based on the mapping relationship, thereby improving the accuracy of production and the timeliness of material supply.

[0033] Step 103, in response to an order request for an assembly component, generating order data for sub-components according to the mapping relationship;

[0034] In some examples, an order request refers to a demand initiated by an enterprise or system, usually a material or component ordering request for a certain assembly component proposed by the procurement, production and other departments based on production plans or inventory requirements; the order request can come from the enterprise's enterprise resource planning (ERP) system, production scheduling system or through manually submitted demand orders. Order data refers to the specific material ordering information generated based on the order request, which can include the type, quantity, specifications and other content of the sub-components, as the basis for actual procurement or production scheduling.

[0035] For example, when the production line initiates an order request for the engine assembly component "ENG-V1", the request can be converted into sub-component order data of "PISTON-V1", "CRANK-V1" and "CYLINDER-V1" according to the mapping relationship of the assembly component.

[0036] Through the implementation of step 103, corresponding sub-component orders can be quickly generated according to the order request of the assembly component, reducing the time for manual intervention and order processing; and the order data generated through the mapping relationship can accurately reflect the number of sub-components required for each assembly component, ensuring the accuracy and timeliness of the order, reducing delays or mismatches in material supply, and improving the response speed and efficiency of the supply chain.

[0037] In summary, the embodiment of the present application ensures that the assembly requirements between the assembly component and its sub-components can be accurately recorded by encoding the assembly component and the sub-components respectively and establishing a mapping relationship between them. This accurate mapping relationship enables the corresponding sub-component order data to be automatically generated when responding to the order request of the assembly component, avoiding manual calculation and data processing errors, significantly improving work efficiency, reducing manual intervention and operational errors, and improving management accuracy and efficiency; and it enables the order data of the assembly component and the sub-components to be synchronized in real time, ensuring that the supply of parts in the production plan is connected with the actual assembly requirements, avoiding production delays and material waste caused by untimely or missing orders, optimizing the production process, and enhancing the coordination and predictability of the production plan. In summary, the vehicle component data processing method provided in the embodiment of the present application realizes the automation, precision and efficiency of component management through encoding and the establishment of mapping relationships, and optimizes material management and production scheduling in the production process.

[0038] In some embodiments, the aforementioned mapping relationship may include type mapping and quantity mapping; the aforementioned step 103 may include: in response to an order request for an assembly component, determining a target sub-component among the sub-components according to the type mapping; determining quantity information of the target sub-component according to the quantity mapping; and determining the target sub-component and quantity information as order data.

[0039] In some examples, category mapping refers to the correspondence established between an assembly component and its subcomponents, ensuring that each assembly component can be correctly mapped to the subcomponent category it requires; for example, the engine assembly component "ENG-V1" is mapped to the piston "PISTON-V1", crankshaft "CRANK-V1" and other subcomponent categories through category mapping. Quantity mapping refers to the relationship between the quantity requirements of each target subcomponent and the assembly component during the assembly process; for example, the engine assembly "ENG-V1" may require 6 pistons "PISTON-V1", 1 crankshaft "CRANK-V1" and other subcomponents, so the quantity mapping is 6 and 1.

[0040] For example, when an order request for an engine assembly component "ENG-V1" is received, the required sub-components are first determined through category mapping, such as the piston "PISTON-V1" and the crankshaft "CRANK-V1"; then, the quantity requirement for each sub-component is determined based on quantity mapping, such as 6 pistons and 1 crankshaft; finally, these sub-components and their quantity information are summarized as order data to ensure that material procurement and production scheduling can be carried out as required.

[0041] Through the implementation of the above embodiment, the mapping relationship is divided into type mapping and quantity mapping, which can more finely manage the demand relationship between assembly components and sub-components; type mapping ensures the accurate identification of target sub-components, while quantity mapping ensures the precise calculation of the quantity of target sub-components; it can ensure that when processing an order, not only the correct sub-components can be found, but also the accuracy of the order quantity can be ensured, thereby improving the accuracy of inventory management and material supply.

[0042] In some embodiments, the aforementioned step 101 may include: encoding the assembly component according to the type, version and assembly requirements of the aforementioned assembly component to obtain an assembly code, wherein the assembly code may include assembly type information, assembly version information and assembly sub-component information; encoding the sub-component according to the type and version of the aforementioned sub-component to obtain a sub-component code, wherein the sub-component code may include sub-component type information and sub-component version information.

[0043] In some examples, assembly type information refers to the category or type of assembly components, which is used to describe the basic characteristics and functional properties of assembly components; for example, engines, wheels, doors, etc. all belong to different assembly types. Assembly version information refers to the specific version of the assembly component, which is used to distinguish the design or configuration of different versions in the same assembly type; for example, the engine assembly may have multiple versions "ENG-V1" (first version) and "ENG-V2" (second version), and the version differences are usually due to design improvements or configuration changes. Assembly sub-component information refers to the information of the sub-components contained in the assembly component, which describes the specific requirements of each sub-component required for the assembly of the assembly component; for example, the engine assembly "ENG-V1" may contain sub-components such as 6 pistons, 1 crankshaft and 1 cylinder head. Sub-component type information refers to the category or type of each sub-component, which describes the function and type of the sub-component; for example, pistons, cylinder heads, crankshafts, etc. are different sub-component types. Subcomponent version information refers to the specific version of a subcomponent, which is used to distinguish different versions of subcomponents, which may differ due to design updates or functional improvements; for example, a piston may have multiple versions "PISTON-V1" and "PISTON-V2", corresponding to different designs or manufacturing processes.

[0044] Exemplarily, the engine assembly components are first encoded according to their type (such as "ENG"), version (such as "V1") and assembly requirements (such as 6 pistons, 1 crankshaft, etc.) to obtain a unique assembly code "ENG-V1-6PISTON-1CRANK"; then, each sub-component is encoded according to its type (such as "piston" or "PISTON") and version (such as "V1") to obtain a unique sub-component code.

[0045] Through the implementation of the above-mentioned embodiments, the coding of assembly parts and sub-parts is refined, not only considering the type and version, but also including the assembly requirements, so that each assembly code can accurately reflect the characteristics and assembly requirements of its assembly parts, which helps to improve the accuracy of parts management and ensure that suitable parts can be quickly located in complex production processes; and the detailed information in the code (such as type, version, assembly requirements, etc.) provides greater flexibility for subsequent management, tracking and maintenance.

[0046] In some embodiments, after step 102, the method may further include: updating the subcomponent version information in the subcomponent code in response to a design change request for a subcomponent; and updating the assembly version information of the assembly code corresponding to the subcomponent code according to a mapping relationship.

[0047] In some examples, a design change request refers to a request to modify or update an existing design during product development or production; a design change request can be submitted through a product lifecycle management (PLM) system, an engineering change order (ECR), or a design change notification (ECN); for example, the engineering team found that the piston was unstable under certain conditions, so they filed a design change request to modify the material or size of the piston and update the version to "PISTON-V2". Sub-component version information update refers to adjusting the versions of related sub-components after a design change occurs to ensure that the sub-components are consistent with the new design version; for example, when the design change request for the piston is approved, the sub-component code "PISTON-V1" may be updated to "PISTON-V2" to reflect the new design. Assembly version information update means that after the sub-component version is changed, the version information of the related assembly components also needs to be updated to ensure that the version of the assembly component is consistent with the sub-component version it contains; for example, if the piston "PISTON-V1" is updated from version "V1" to "V2", the related engine assembly "ENG-V1" also needs to be updated to "ENG-V2" to match the new version of the piston.

[0048] Through the implementation of the above-mentioned embodiments, when the design of a sub-component is changed, the version information in the sub-component code can be updated in time, and the version information of the assembly code can be updated according to the mapping relationship, ensuring that the design change can be reflected in the order and production process in real time, avoiding the delay and errors caused by the design change, improving production adaptability, reducing manual operations and manual tracking, reducing the probability of errors in the change process, and improving the efficiency of change processing.

[0049] In some embodiments, the aforementioned encoding of assembly components according to the type, version and assembly requirements of the assembly components to obtain the assembly code may include: generating assembly type text, assembly version text, sub-component type text and sub-component quantity text according to the type, version and assembly requirements of the assembly components; generating the assembly code according to the assembly type text, assembly version text, sub-component type text and sub-component quantity text.

[0050] In some examples, assembly type text refers to the type or category of assembly parts expressed in text form, describing the basic functions and uses of assembly parts, and is an important part of assembly coding; for example, a car engine can correspond to an assembly type text "ENG" (for engine), and other assembly parts such as wheels, doors, etc. will have their own corresponding type text. Assembly version text refers to the specific version information used to describe the assembly part, indicating whether the assembly part is the first version or a version after design update; for example, the version text of the engine may be "V1" or "V2", indicating the first version and the second version respectively. If the design update causes the parts to be different, the version information will change accordingly. Sub-component type text refers to the text that describes the category of each sub-component in the assembly part, defining the function and use of the sub-component; for example, an engine assembly may contain sub-components such as "piston" (PISTON), "crankshaft" (CRANKSHAFT), etc., and each sub-component has a corresponding type text. The sub-component quantity text is used to express the quantity of each sub-component required in the assembly to ensure correct procurement and production; for example, the engine assembly may require 6 pistons (PISTON) and 1 crankshaft (CRANKSHAFT), and the corresponding quantity texts are "6" and "1".

[0051] For example, the engine assembly code may be “ENG-V1-PISTON6-CRANK1”, indicating an engine assembly with version V1 including 6 pistons and 1 crankshaft.

[0052] Through the implementation of the above-mentioned embodiments, texts of the types, versions, sub-component types and quantities of assembly components are generated, and assembly codes are generated based on these texts. This allows for a more flexible construction of assembly codes, making the generation process of assembly codes more transparent and controllable, which not only enhances the readability of the codes, but also enables the components of each code to be clearly understood, making it easier to understand and manage.

[0053] In some embodiments, the aforementioned generation of the assembly code based on the assembly type text, assembly version text, sub-component type text and sub-component quantity text may include: concatenating the sub-component type text and the sub-component quantity text to obtain a sub-component information text; performing hash function calculation on the sub-component information text to obtain a sub-component summary text; and concatenating the assembly type text, the assembly version text and the sub-component summary text to obtain the assembly code.

[0054] In some examples, the sub-component information text refers to a character string describing the sub-component information formed by concatenating the sub-component type text and quantity text, which combines the sub-component type and quantity as part of the subsequent generation of the assembly code; assuming that an engine assembly contains 6 pistons and 1 crankshaft, the sub-component information text can be concatenated as "PISTON6-CRANK1". A hash function is an algorithm that converts input data (such as text) into an output value of a fixed length. The hash function is used to generate a "summary" of the data and is unique and irreversible; hash algorithms such as SHA-256 and MD5 can be used to calculate the sub-component information text to generate a unique hash value; for example, a hash operation is performed on the sub-component information text "PISTON6-CRANK1" to obtain a fixed-length summary value (such as "f5d5fbbf7a233a6f315bcbfa3b7dbd3e"). The sub-component summary text refers to the unique identifier of the sub-component information obtained through the hash function calculation. It is a compressed representation of the sub-component information text. The summary value can effectively avoid lengthy sub-component information text and facilitate storage and management.

[0055] For example, first, by concatenating the type and quantity texts of the sub-components, "PISTON6-CRANK1" can be obtained as the sub-component information text; then, the text is processed using a hash function to generate a unique sub-component summary text (for example, "f5d5fbbf7a233a6f315bcbfa3b7dbd3e"); next, the type text "ENG", version text "V1" and sub-component summary text of the assembly component are concatenated to finally form a unique assembly code "ENG-V1-f5d5fbbf7a233a6f315bcbfa3b7dbd3e".

[0056] Through the implementation of the above-mentioned embodiment, the sub-component information text is hashed to generate a sub-component summary text, thereby ensuring the uniqueness of the overall code. The hash algorithm makes the generated code highly secure and avoids the risk of information tampering or duplication. Multiple text fields are concatenated to generate the overall code, which not only simplifies the coding rules, but also makes the code generation more efficient, which is conducive to improving data processing speed.

[0057] In some embodiments, the aforementioned encoding of sub-components according to the types and versions of the sub-components to obtain the sub-component codes may include: generating sub-component type text and sub-component version text according to the types and versions of the sub-components; and concatenating the generated sub-component type text and sub-component version text based on preset delimiters to obtain the sub-component codes.

[0058] In some examples, subcomponent type text refers to a text string generated based on the type or category of a subcomponent, which is used to describe the function, type or category of the subcomponent; for example, if the subcomponent is a "piston", the generated subcomponent type text is "PISTON"; if it is a "crankshaft", the generated subcomponent type text is "CRANKSHAFT". Subcomponent version text refers to text generated based on the version number or revision status of the subcomponent, which describes the version information of the subcomponent and is used to distinguish different design versions; for example, the version of a certain piston may be the first edition, and the generated subcomponent version text is "V1"; another version may be the second edition, and the generated subcomponent version text is "V2". Preset delimiters refer to specific symbols used to separate the contents of each part when splicing the type text and version text of the subcomponent, which helps to keep the structure of the code clear and ensure that each part can be correctly parsed in the system; preset delimiters can be "-", "_", etc.

[0059] For example, first, the sub-component type text "PISTON" and the sub-component version text "V1" can be generated according to the type (such as "piston") and version (such as "V1") of the sub-component; then, these two texts are concatenated together based on the preset separator "_" to obtain the sub-component code "PISTON_V1".

[0060] Through the implementation of the above-mentioned embodiment, the type and version text of the sub-components are spliced ​​based on the preset separators, thereby simplifying the generation process of the sub-component codes, making the coding rules simpler and clearer, avoiding confusion or errors in the coding process, facilitating the maintenance and upgrading of the sub-component codes, and improving the overall reliability of the parts management process.

[0061] Furthermore, as an implementation of the aforementioned method embodiment, the present application also provides a vehicle component data processing device for implementing the aforementioned method embodiment. The device embodiment corresponds to the aforementioned method embodiment. For ease of reading, the vehicle component data processing device embodiment will no longer repeat the details of the aforementioned method embodiment one by one, but it should be clear that the device in the embodiment of the present application can correspond to and implement all the contents of the aforementioned method embodiment. Figure 2 As shown, the vehicle component data processing device 20 includes: a code generation unit 201, a mapping generation unit 202 and an order generation unit 203, wherein the code generation unit 201 is used to encode the assembly component and the sub-components to obtain the assembly code and the sub-component code; the mapping generation unit 202 is used to establish a mapping relationship between the assembly code and the sub-component code according to the assembly requirements of the assembly component for the sub-component; the order generation unit 203 is used to respond to the order request for the assembly component and generate order data for the sub-component according to the mapping relationship.

[0062] In some embodiments, the mapping relationship includes type mapping and quantity mapping; the order generation unit 203 is also used to respond to an order request for an assembly component, determine a target sub-component in the sub-components according to the type mapping; determine the quantity information of the target sub-component according to the quantity mapping; and determine the target sub-component and quantity information as order data.

[0063] In some embodiments, the code generation unit 201 is also used to encode the assembly components according to the type, version and assembly requirements of the assembly components to obtain an assembly code, wherein the assembly code includes assembly type information, assembly version information and assembly sub-component information; and to encode the sub-components according to the type and version of the sub-components to obtain a sub-component code, wherein the sub-component code includes sub-component type information and sub-component version information.

[0064] In some embodiments, the code generation unit 201 is also used to update the subcomponent version information in the subcomponent code in response to a design change request for a subcomponent; and update the assembly version information of the assembly code corresponding to the subcomponent code according to the mapping relationship.

[0065] In some embodiments, assembly components are encoded according to the type, version and assembly requirements of the assembly components to obtain assembly codes, including: generating assembly type text, assembly version text, sub-component type text and sub-component quantity text according to the type, version and assembly requirements of the assembly components; generating assembly codes according to the assembly type text, assembly version text, sub-component type text and sub-component quantity text.

[0066] In some embodiments, the encoding generation unit 201 is also used to concatenate the sub-component type text and the sub-component quantity text to obtain the sub-component information text; perform hash function calculation on the sub-component information text to obtain the sub-component summary text; and concatenate the assembly type text, the assembly version text and the sub-component summary text to obtain the assembly code.

[0067] In some embodiments, the code generation unit 201 is also used to generate a sub-component type text and a sub-component version text according to the type and version of the sub-component; and to concatenate the generated sub-component type text and sub-component version text based on a preset separator to obtain a sub-component code.

[0068] The present application also provides a computer-readable storage medium, which stores computer-executable instructions or computer programs. When the computer-executable instructions or computer programs are executed by a processor, the processor will be caused to execute any step of the vehicle component data processing method provided in the present application.

[0069] In some embodiments, the computer-readable storage medium may be a memory such as RAM, read-only memory (ROM), flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); or it may be various devices including one or any combination of the above memories.

[0070] In some embodiments, computer executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0071] In some embodiments, computer-executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file storing other programs or data, for example, in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0072] In some embodiments, computer executable instructions may be deployed to be executed on one electronic device, or on multiple electronic devices located at one site, or on multiple electronic devices distributed at multiple sites and interconnected by a communication network.

[0073] like Figure 3 As shown, the present application also provides an electronic device 30, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor, and when the processor 320 executes the computer program 311, any step of the above-mentioned vehicle component data processing method is implemented.

[0074] The present application also provides a computer program product, which includes a computer program or a computer executable instruction, and the computer program or the computer executable instruction is stored in a computer readable storage medium. The processor of the electronic device reads the computer program or the computer executable instruction from the computer readable storage medium, and the processor executes the computer program or the computer executable instruction, so that the electronic device performs any step of the vehicle component data processing method described above in the present application.

[0075] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle component data processing method, characterized in that: include: Encode the assembly parts and sub-components to obtain assembly codes and sub-component codes; According to the assembly requirements of the assembly component for the sub-component, a mapping relationship between the assembly code and the sub-component code is established; In response to an order request for the assembly component, order data for the sub-component is generated according to the mapping relationship.

2. The method according to claim 1, characterized in that The mapping relationship includes type mapping and quantity mapping; The step of generating order data for the sub-component according to the mapping relationship in response to the order request for the assembly component includes: In response to an order request for the assembly component, determining a target sub-component among the sub-components according to the category mapping; Determine the quantity information of the target sub-component according to the quantity mapping; The target sub-component and the quantity information are determined as the order data.

3. The method according to claim 2, characterized in that The coding of the assembly components and sub-components to obtain the assembly code and sub-component code includes: According to the type and version of the assembly component and the assembly requirement, the assembly component is encoded to obtain the assembly code, wherein the assembly code includes assembly type information, assembly version information and assembly sub-component information; The sub-component is encoded according to the type and version of the sub-component to obtain the sub-component code, wherein the sub-component code includes sub-component type information and sub-component version information.

4. The method according to claim 3, characterized in that After establishing a mapping relationship between the assembly code and the sub-component code according to the assembly requirement of the assembly component for the sub-component, the method further includes: In response to a design change request for the sub-component, updating sub-component version information in the sub-component code; According to the mapping relationship, the assembly version information of the assembly code corresponding to the sub-component code is updated.

5. The method according to claim 3, characterized in that: The step of encoding the assembly component according to the type, version and assembly requirements of the assembly component to obtain the assembly code includes: Generate assembly type text, assembly version text, sub-component type text and sub-component quantity text according to the type and version of the assembly component and the assembly requirements; The assembly code is generated according to the assembly type text, the assembly version text, the sub-component type text and the sub-component quantity text.

6. The method according to claim 5, characterized in that The generating the assembly code according to the assembly type text, the assembly version text, the subcomponent type text and the subcomponent quantity text comprises: The sub-component type text and the sub-component quantity text are concatenated to obtain a sub-component information text; Performing hash function calculation on the sub-component information text to obtain a sub-component summary text; The assembly type text, the assembly version text and the sub-component summary text are concatenated to obtain the assembly code.

7. The method according to claim 3, characterized in that The step of encoding the sub-component according to the type and version of the sub-component to obtain the sub-component code includes: Generate sub-component type text and sub-component version text according to the type and version of the sub-component; The generated sub-component type text and the sub-component version text are concatenated based on a preset separator to obtain the sub-component code.

8. A vehicle component data processing device, characterized in that: include: A code generation unit, used for encoding the assembly components and sub-components to obtain assembly codes and sub-component codes; A mapping generation unit, used to establish a mapping relationship between the assembly code and the sub-component code according to the assembly requirements of the assembly component for the sub-component; An order generating unit is used to generate order data for the sub-component according to the mapping relationship in response to an order request for the assembly component.

9. An electronic device, comprising: A memory and a processor, wherein the processor is used to implement the steps of the vehicle component data processing method according to any one of claims 1 to 7 when executing the computer program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the vehicle component data processing method according to any one of claims 1 to 7 are implemented.

Images