Data management method, computing device and computer readable storage medium

Abstract

The invention discloses a data management method, a computing device and a computer readable storage medium, and the method comprises the steps: obtaining the material information of a to-be-managed material, the material information comprising a material identifier, a station identifier and a supplier identifier; the material identifier comprises a material number and a material name; forming a first composite primary key of the to-be-managed material according to the material number, the station identifier and the supplier identifier, and querying a preset PFEP database based on the first composite primary key; in response to the fact that the PFEP data matched with the to-be-managed material is not queried, forming a second composite primary key of the to-be-managed material according to at least one of the station identifier and the supplier identifier and the material name, and retrieving a preset PFEP data template library based on the second composite primary key; and in response to the retrieved PFEP data template matched with the to-be-managed material, generating PFEP data of the to-be-managed material according to the PFEP data template matched with the to-be-managed material. Therefore, the PFEP data management efficiency and accuracy can be effectively improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a data management method, computing device, and computer-readable storage medium. Background Technology

[0002] PFEP (Plan for Every Part) data describes the entire data chain of materials from supplier to production line, including part master attributes, supply logistics, packaging design (including inbound packaging and outbound packaging), warehouse planning, pull distribution, and production line-side planning data. The data from each part is linked through business logic and can be automatically transferred through systems such as Warehouse Management Systems (WMS) and Logistics Execution Systems (LES). PFEP data is typically managed offline using Excel spreadsheets, and can be manually imported and exported from the LES system for data management. However, current technology relies entirely on the individual experience of engineers to manage the massive amounts of PFEP data, and the data completeness and accuracy vary, affecting the efficiency and accuracy of PFEP data management. Summary of the Invention

[0003] The purpose of this application is to provide a data management method, computing device, and computer-readable storage medium that can effectively improve the efficiency and accuracy of PFEP data management.

[0004] To achieve the above objectives: In a first aspect, embodiments of this application provide a data management method, the method comprising: Obtain the material information of the materials to be managed, including material identifier, workstation identifier, and supplier identifier; the material identifier includes material number and material name; The first composite primary key of the material to be managed is composed of the material number, the workstation identifier, and the supplier identifier, and a preset PFEP database is queried based on the first composite primary key; the PFEP database includes PFEP data of multiple materials; In response to the absence of PFEP data matching the material to be managed, a second composite primary key for the material to be managed is formed based on at least one of the workstation identifier and the supplier identifier and the material name, and a preset PFEP data template library is retrieved based on the second composite primary key; the PFEP data template library includes PFEP data templates for multiple materials; In response to the PFEP data template matching the material to be managed being retrieved, PFEP data of the material to be managed is generated based on the PFEP data template matching the material to be managed.

[0005] In one embodiment, obtaining the material information of the material to be managed includes: Obtain the bill of materials (BOM) for the target model of the target engineering vehicle; the BOM includes the material number, material name, and workstation identifier of each material required for the production or manufacturing of the target model; The correspondence between the material number and the supplier identifier is queried based on the material number of the material to be managed, and the supplier identifier of the material to be managed is determined; the material to be managed is any material in the bill of materials. In one embodiment, before querying the preset PFEP database based on the first composite primary key, the method includes: Based on the preset information of each model of the target engineering vehicle, at least one typical representative model of the target engineering vehicle is determined; Based on at least one of the workstation identifier and supplier identifier of each material in the bill of materials corresponding to at least one typical representative vehicle model, and the material number, a third composite primary key corresponding to each material and not repeated is formed. Based on the third composite primary key corresponding to the target material, generate and output the PFEP data form corresponding to the target material to request the configuration of the corresponding PFEP data; the target material can be any of the aforementioned materials; In response to the maintenance operation of the PFEP data form corresponding to the target material, the PFEP data of the target material is determined and added to the PFEP database. In one embodiment, before retrieving the preset PFEP data template library based on the second composite primary key, the method includes: Based on the material name of each material in the bill of materials corresponding to at least one typical representative vehicle model, and at least one of the following: workstation identifier, supplier identifier, and packaging type, a fourth composite primary key is formed for each of the materials. The PFEP database is retrieved based on the fourth composite primary key corresponding to the target material to determine the PFEP data that matches the fourth composite primary key; Based on the PFEP data matching the fourth composite primary key, a PFEP data template for the target material is generated, and the PFEP data template for the target material is added to the PFEP data template library. In one embodiment, generating a PFEP data template for the target material based on PFEP data matching the fourth composite primary key includes: In response to the existence of multiple PFEP data entries matching the fourth composite primary key, a PFEP data template for the target material is generated for each PFEP data entry matching the fourth composite primary key.

[0006] In one embodiment, before retrieving the preset PFEP data template library based on the second composite primary key, the method includes: The names of different materials with the same workstation identifier in the bill of materials for the target model of the target engineering vehicle are uniformly corrected.

[0007] In one embodiment, the bill of materials further includes the dimensions of each of the materials, and the PFEP data template includes packaging dimensions; generating the PFEP data of the materials to be managed based on the PFEP data template matching the materials to be managed includes: Since there are multiple PFEP data templates that match the second composite primary key, the PFEP data template with the highest matching degree between the packaging size and the size of the material to be managed is determined as the PFEP data template that matches the material to be managed. The PFEP data of the material to be managed is generated based on the PFEP data template that matches the material to be managed.

[0008] In one embodiment, the method further includes: In response to the failure to find a PFEP data template matching the material to be managed, an alert message is output to complete the PFEP data of the material to be managed.

[0009] Secondly, embodiments of this application provide a computing device, including: a processor and a memory storing a computer program, wherein when the processor runs the computer program, the steps of the above-described data management method are implemented.

[0010] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described data management method.

[0011] The data management method, computing device, and computer-readable storage medium provided in this application embodiment include: acquiring material information of a material to be managed, the material information including a material identifier, a workstation identifier, and a supplier identifier; the material identifier including a material number and a material name; forming a first composite primary key of the material to be managed based on the material number, workstation identifier, and supplier identifier, and querying a preset PFEP database based on the first composite primary key; in response to not finding PFEP data matching the material to be managed, forming a second composite primary key of the material to be managed based on at least one of the workstation identifier and supplier identifier and the material name, and searching a preset PFEP data template library based on the second composite primary key; in response to finding a PFEP data template matching the material to be managed, generating PFEP data of the material to be managed based on the PFEP data template matching the material to be managed. In this way, the PFEP database is first accurately queried based on the first composite primary key of the material to be managed. If no PFEP data matching the material to be managed is found in the PFEP database, the PFEP data template library is fuzzily searched based on the second composite primary key of the material to be managed. The PFEP data of the material to be managed is generated according to the PFEP data template that matches the material to be managed, so as to realize intelligent management of PFEP data and effectively improve the efficiency and accuracy of PFEP data management. Attached Figure Description

[0012] Figure 1 This is a flowchart illustrating the data management method provided in an embodiment of this application.

[0013] Figure 2 A schematic diagram of the structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0014] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. In the following description relating to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements.

[0015] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0016] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, can be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or" and "and / or" as used herein are to be interpreted as inclusive, or mean any one or any combination thereof. Therefore, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A, B, and C". Exceptions to this definition will only occur if the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0017] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0018] It should be noted that step designations such as S101 and S102 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S102 first and then S101, etc., but these should all be within the protection scope of this application.

[0019] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0020] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0021] To facilitate understanding of this application, the following explanations are provided for the terms and technical objects that may be used in this application: The PFEP (Plan for Every Part) data management system is essentially a database that, based on the actual production process, provides standardized and regulated information planning for the logistics operations of all materials within the production system. It contains all key information related to parts (i.e., materials), such as component attributes, supply logistics, packaging design, warehousing planning, pull distribution, and production line planning. It forms the foundation of logistics standardization and serves as a management standard for regulating each stage of material flow.

[0022] PFEP data: A dynamic logistics execution rule set based on the unique identifier of materials. It describes the precise control parameters of the material flow in the entire chain of "supplier → warehouse → production line" through structured fields, including but not limited to material number (also known as material code), material name, material size and weight, workstation name, workstation code, supplier name, supplier code, packaging type (including packaging dimensions such as length, width, height, and the number of packages that can be held, the weight that can be carried, etc.).

[0023] See Figure 1 This application provides a data management method, which can be executed by a data management device provided in this application. This device can be implemented in software and / or hardware, such as a computer or server. In this embodiment, the executing entity of the method is a logistics execution system installed in a computing device. The method provided in this embodiment includes: Step S101: Obtain the material information of the material to be managed. The material information includes the material identifier, workstation identifier, and supplier identifier. The material identifier includes the material number and the material name.

[0024] The materials to be managed are any materials in the target engineering vehicles for which PFEP data needs to be determined or obtained. The target engineering vehicles can be cranes or mixer trucks in the construction machinery field, without specific limitations. Material identifiers are used to identify the materials and distinguish them from different materials. The material number, also known as the material code, can consist of numbers and / or letters, such as "1001" or "1002". The material name is used to represent the specific name of the material, such as motor or bolt. The workstation identifier indicates the specific workstation where the material is processed. The workstation identifier may include a workstation code (e.g., SQ01) and a workstation name (e.g., workstation 1). The supplier identifier indicates the specific supplier providing the material. The supplier may include a supplier code (e.g., 0101) and a supplier name (e.g., Company A).

[0025] In one embodiment, obtaining material information of the material to be managed includes: Obtain the bill of materials (BOM) for the target vehicle model; the BOM includes the material number, material name, and workstation identifier for each material required for the production or manufacturing of the target vehicle model; The correspondence between the material number and the supplier identifier is found based on the material number of the material to be managed, and the supplier identifier of the material to be managed is determined; the material to be managed is any material in the bill of materials.

[0026] The Bill of Materials (BOM) defines the core data architecture of the target vehicle model, including the material number, material name, and workstation identifier of each material required for the production or manufacturing of the target vehicle model. In this embodiment, when the data management method is executed by a logistics execution system within a computing device, the BOM for the target vehicle model can be pushed from the manufacturing execution system to the logistics execution system, or it can be obtained by the logistics execution system from the product lifecycle management system. Furthermore, the correspondence between material numbers and supplier identifiers can be pushed from the supplier relationship management system to the logistics execution system, or it can be obtained by the logistics execution system from the enterprise resource management software system; no specific limitations are imposed here. This allows for accurate and rapid acquisition of material information.

[0027] Step S102: Construct the first composite primary key of the material to be managed based on the material number, workstation identifier, and supplier identifier, and query the preset PFEP database based on the first composite primary key; the PFEP database includes PFEP data of multiple materials.

[0028] Specifically, the first composite primary key of the material to be managed is formed based on its material number, workstation identifier, and supplier identifier. That is, the first composite primary key of the material to be managed includes three fields: material number, workstation identifier, and supplier identifier. Then, based on the first composite primary key of the material to be managed, a pre-defined PFEP database is queried to check if there is PFEP data in the PFEP database that matches the first composite primary key of the material to be managed. In other words, the PFEP database contains PFEP data for multiple materials, and the PFEP data for each material includes at least the material number, workstation identifier, and supplier identifier.

[0029] In one embodiment, before querying a preset PFEP database based on a first composite primary key, the method includes: Based on the preset information of each model of the target engineering vehicle, determine at least one typical representative model of the target engineering vehicle. Based on at least one of the workstation identifier and supplier identifier of each material in the bill of materials corresponding to at least one typical representative vehicle model, as well as the material number, a third composite primary key is formed for each material, which is unique and corresponding to each material. Based on the third composite primary key corresponding to the target material, generate and output the PFEP data form corresponding to the target material to request the configuration of the corresponding PFEP data; the target material can be any material. In response to the maintenance operation of the PFEP data form corresponding to the target material, the PFEP data of the target material is determined and added to the PFEP database.

[0030] The preset information can be set according to actual needs, such as at least one of the following: quantity sold, quantity pre-ordered, expected market demand, etc. Optionally, when the preset information includes at least two of the above, at least one typical representative model of the target engineering vehicles is determined based on the preset information of each model. This can be done by calculating a weighted sum for each model based on the preset information and weights of each model (i.e., multiplying each preset information by its corresponding weight and then summing the results), and then selecting the N models with the largest weighted sums as typical representative models, where N is a positive integer and can be set to 2 or 4, etc. Optionally, when the preset information includes one of the above, at least one typical representative model of the target engineering vehicles is determined based on the preset information of each model. This can be done by sorting the target engineering vehicles according to the preset information from highest to lowest order, and selecting the top M models as typical representative models, where M is a positive integer and can be set to 2 or 4, etc.

[0031] It is understandable that although there are multiple models of target engineering vehicles, at least some of the materials used in the production or manufacturing of different models of target engineering vehicles will be the same. In other words, the same material may be used to produce or manufacture different models of target engineering vehicles. Therefore, a PFEP database can be generated based on the PFEP data of each material in the bill of materials corresponding to the typical representative model of the target engineering vehicle. For example, cranes have different tonnage models, and a certain tonnage model can be selected as the typical representative model. The PFEP database can be generated based on the PFEP data of each material in the bill of materials corresponding to that tonnage model. The method for obtaining at least one of the workstation identifier and supplier identifier of each material in the bill of materials corresponding to at least one typical representative model, as well as the material number, can be referred to the above explanation and will not be repeated here.

[0032] For each material in the bill of materials (BOM) corresponding to each typical representative vehicle model, a third composite primary key can be constructed based on at least one of the material's workstation identifier and supplier identifier, along with the material number. For example, the third composite primary key can be at least one of the following: "material number + workstation code," "material number + supplier code," "material number + workstation code + supplier code," etc. Considering that the same materials may exist in the BOMs corresponding to different typical representative vehicle models, the third composite primary keys generated for each material in the BOM of at least one typical representative vehicle model may overlap. Therefore, it is necessary to merge duplicate third composite primary keys to obtain a unique third composite primary key corresponding to each material. In one embodiment, a third composite primary key is formed for each material based on at least one of the workstation identifier and supplier identifier of each material in the bill of materials corresponding to at least one typical representative vehicle model, as well as the material number. This includes: forming a third composite primary key for each material based on the material number and workstation code of each material in the bill of materials corresponding to at least one typical representative vehicle model, and forming a third composite primary key for each material based on the material number and supplier code of each material in the bill of materials corresponding to at least one typical representative vehicle model. That is, the third composite primary key includes "material number + workstation code" and "material number + supplier code". Then, for the third composite primary keys of all materials in the bill of materials corresponding to all typical representative vehicle models, duplicate third composite primary keys are merged to obtain a third composite primary key for each material that is unique.

[0033] Specifically, for any material (i.e., the target material) corresponding to the third composite primary key, a PFEP data form for the target material is generated and output to request engineers to configure the corresponding PFEP data. The PFEP data form can include all fields required for material planning data, allowing engineers to configure the values ​​of these fields; this can be represented using tables or similar methods. It should be noted that when generating the PFEP data form based on the target material's third composite primary key, the target material's workstation identifier, supplier identifier, and material identifier can be entered into the PFEP data form. Outputting the PFEP data form can display a maintenance request including the target material's PFEP data form. Upon receiving a maintenance operation for the target material's PFEP data form, the PFEP data for the target material is determined or generated based on the data input to the PFEP data form during the maintenance operation, and then added to the PFEP database. In this way, by obtaining the PFEP data of each material in the bill of materials corresponding to typical representative models of engineering vehicles, and constructing a PFEP database based on the PFEP data of each material, the efficiency and accuracy of PFEP data management are further improved.

[0034] Step S103: In response to the failure to find PFEP data matching the material to be managed, a second composite primary key for the material to be managed is formed based on at least one of the workstation identifier and supplier identifier and the material name, and a preset PFEP data template library is retrieved based on the second composite primary key; the PFEP data template library includes PFEP data templates for multiple materials.

[0035] Specifically, if a query is performed on the pre-set PFEP database based on the first composite primary key of the material to be managed, but no PFEP data matching the material to be managed is found in the PFEP database, a second composite primary key of the material to be managed can be formed based on at least one of the workstation identifier and supplier identifier of the material to be managed, as well as the material name. Based on the second composite primary key of the material to be managed, a pre-set PFEP data template library is searched to check whether a PFEP data template matching the material to be managed exists in the PFEP data template library.

[0036] The second composite primary key of the managed material is formed based on at least one of the workstation identifier and supplier identifier, along with the material name. This can be based on the workstation code, supplier code, and material name; it can also be based on the workstation code and material name, or supplier code and material name; or it can be based on the material name and packaging type, etc. It can be understood that querying the preset PFEP database based on the first composite primary key of the managed material allows for precise PFEP data retrieval. If no matching PFEP data is found in the PFEP database, a fuzzy query for the managed material's PFEP data can be performed by searching the preset PFEP data template library based on the second composite primary key. The PFEP data template for a material can include the main or all PFEP data of that material.

[0037] In one embodiment, before retrieving a preset PFEP data template library based on the second composite primary key, the method includes: Based on the material name of each material in the bill of materials corresponding to at least one typical representative vehicle model, and at least one of the following: workstation identifier, supplier identifier, and packaging type, a fourth composite primary key is formed for each material. The PFEP database is retrieved based on the fourth composite primary key corresponding to the target material to determine the PFEP data that matches the fourth composite primary key. Based on the PFEP data matching the fourth composite primary key, generate the PFEP data template of the target material and add the PFEP data template of the target material to the PFEP data template library.

[0038] Specifically, based on the fourth composite primary key corresponding to any material (i.e., the target material), the PFEP database can be searched to determine if PFEP data with a value matching that fourth composite primary key exists. In other words, it checks if PFEP data matching the fourth composite primary key exists. After finding PFEP data matching the fourth composite primary key, a PFEP data template for the target material can be determined or generated based on this template, and then added to the PFEP data template library. Packaging types can include inbound packaging and outbound packaging. Inbound packaging can include packaging dimensions such as length, width, and height, as well as the number of packages it can hold and its weight capacity. The number of packages it can hold indicates the maximum quantity of a specific material that a single standard packaging container can hold; its value is determined by the material's physical properties, packaging specifications, and safety constraints, and is used to accurately calculate handling and inventory units in the logistics process.

[0039] Specifically, generating a PFEP data template for the target material based on the PFEP data matching the fourth composite primary key can be achieved by copying the PFEP data matching the fourth composite primary key to a preset data template. For example, delivery information, warehousing information, and distribution information from the PFEP data can be automatically copied to a preset data template to generate a PFEP data template. In this way, by obtaining the PFEP data templates for each material in the bill of materials corresponding to typical representative models of engineering vehicles, and constructing a PFEP data template library based on these templates, a fuzzy search of the PFEP data template library can be performed when a precise query from the PFEP database fails to retrieve the corresponding PFEP data, further improving the efficiency and accuracy of PFEP data management.

[0040] In one embodiment, a PFEP data template for the target material is generated based on the PFEP data matching the fourth composite primary key, including: Since there are multiple PFEP data entries that match the fourth composite primary key, a PFEP data template for the target material is generated for each PFEP data entry that matches the fourth composite primary key.

[0041] It is understandable that for the same material, there may be differences in supplier information, delivery information, etc., meaning the PFEP database may contain multiple PFEP records for the same material. Therefore, when retrieving the PFEP database and finding multiple PFEP records matching the fourth composite primary key, a PFEP data template for the target material can be generated for each matching PFEP record. The template names for the target material's PFEP data templates for each matching PFEP record will be different. For example, assuming the fourth composite primary key of the material to be managed is "***motor + SQ***31 + 0000123456", if retrieving the PFEP database using this fourth composite primary key yields two PFEP records, and each PFEP record has the same delivery, warehousing, and distribution information, then two PFEP data templates can be generated, named "***motor 01" and "***motor 02" respectively. In this way, PFEP data templates for the corresponding material can be generated based on the matching results, facilitating accurate generation of PFEP data based on these templates and further improving the efficiency and accuracy of PFEP data management.

[0042] In one embodiment, before retrieving a preset PFEP data template library based on the second composite primary key, the method includes: The names of different materials with the same workstation identifier in the bill of materials for the target model of the target engineering vehicle are uniformly corrected.

[0043] It's understandable that due to non-standard descriptions or personal habits, the bill of materials (BOM) may contain different material names for the same material, such as "T-bolt" and "T-shaped bolt." When each workstation processes only one type of material, the different material names with the same workstation identifier can be uniformly corrected. Specifically, uniformly correcting the different material names with the same workstation identifier in the BOM for the target vehicle model can be achieved by first determining the correct material name from among the different material names with the same workstation identifier, for example, based on historical material data. Then, other material names with the same workstation identifier are modified to the correct material name. In this way, uniformly correcting the different material names with the same workstation identifier improves the speed and accuracy of fuzzy queries, further enhancing the efficiency and accuracy of PFEP data management.

[0044] Step S104: In response to the PFEP data template matching the material to be managed being retrieved, generate the PFEP data of the material to be managed based on the PFEP data template matching the material to be managed.

[0045] Specifically, if a PFEP data template matching the material to be managed is found, the PFEP data in the PFEP data template matching the material to be managed is automatically copied to determine or generate the PFEP data of the material to be managed.

[0046] Specifically, the process of generating PFEP data for the materials to be managed, based on a PFEP data template that matches the materials to be managed, can involve automatically copying information from the PFEP data template that matches the materials to be managed and using that information to generate the PFEP data for the materials to be managed. Furthermore, after generating the PFEP data for the materials to be managed, an audit request can be generated to request the audit of the PFEP data for the materials to be managed, and the matching process can be optimized based on the feedback audit results.

[0047] In one embodiment, the bill of materials also includes the dimensions of each material, and the PFEP data template includes packaging dimensions; generating PFEP data for the material to be managed based on the PFEP data template matching the material to be managed includes: Since there are multiple PFEP data templates that match the second composite primary key, the PFEP data template with the highest matching degree between the packaging size and the size of the material to be managed is determined as the PFEP data template that matches the material to be managed. Generate PFEP data for the material to be managed based on the PFEP data template that matches the material to be managed.

[0048] When there are multiple PFEP data templates that match the second composite primary key of the material to be managed, the PFEP data template with the highest matching degree between the packaging size and the size of the material to be managed can be selected as the PFEP data template that matches the material to be managed, and then the PFEP data of the material to be managed can be generated based on the PFEP data template that matches the material to be managed.

[0049] Specifically, when searching the preset PFEP data template library based on the second composite primary key, if a PFEP data template with the same value as the second composite primary key exists in the library, a matching check operation is performed. This involves determining whether the packaging size in the PFEP data template meets the packaging size requirements of the material to be managed. If it does, the PFEP data template with the highest matching degree between its packaging size and the size of the material to be managed is determined and used as the PFEP data template matching the material to be managed. Otherwise, it is assumed that no PFEP data template matches the material to be managed. It should be noted that determining the PFEP data template with the highest matching degree between its packaging size and the size of the material to be managed can mean determining the PFEP data template with the smallest remaining space when the packaging size can accommodate the same number of materials to be managed. In one embodiment, the PFEP data template may further include the number of packages to be contained. The PFEP data template with the highest matching degree between the package size and the size of the material to be managed can be determined by calculating the space utilization rate corresponding to the PFEP data template, and selecting the PFEP data template with the highest space utilization rate as the one with the highest matching degree between the package size and the size of the material to be managed. The space utilization rate is the value obtained by multiplying the material volume by the number of packages to be contained and then dividing by the internal volume of the package. The material volume can be determined based on the length, height, and width of the material, and the internal volume of the package can be determined based on the length, height, and width of the packaging container. Thus, by selecting a suitable PFEP data template to generate PFEP data, the efficiency of PFEP data management is further improved.

[0050] In summary, the data management method provided in the above embodiments first accurately queries the PFEP database based on the first composite primary key of the material to be managed. When no PFEP data matching the material to be managed is found in the PFEP database, the PFEP data template library is fuzzily searched based on the second composite primary key of the material to be managed. The PFEP data of the material to be managed is generated according to the retrieved PFEP data template matching the material to be managed, thereby realizing intelligent management of PFEP data and effectively improving the efficiency and accuracy of PFEP data management.

[0051] In one embodiment, the method further includes: In response to the failure to find a matching PFEP data template for the material to be managed, an alert message is outputting to complete the PFEP data for the material to be managed.

[0052] Specifically, when a preset PFEP data template library is searched using the second composite primary key, but no PFEP data template matching the material to be managed is found, a reminder message can be output to complete the PFEP data of the material to be managed. This allows engineers to be notified of the reminder message in a timely manner and maintain the PFEP data of the material to be managed, further improving the efficiency of PFEP data management.

[0053] Based on the same inventive concept as the foregoing embodiments, the foregoing embodiments will be described in detail below through a specific example. In this example, the PFEP data pool can be understood as the PFEP database of the above embodiments.

[0054] In existing technologies, PFEP table data needs to be managed offline via Excel spreadsheets, and the data needs to be manually imported and exported within the LES system. This means that managing the massive PFEP table data relies entirely on the personal experience of logistics planning engineers, resulting in inconsistent data completeness and accuracy. Furthermore, planning data and planning concepts cannot be efficiently reused or passed on. The main drawbacks include: (1) Data sources are scattered and have different standards. Basic data (such as material size and packaging specifications) need to be extracted from multiple systems such as R&D BOM, procurement system and logistics records. However, the data formats and update frequencies of each system are not consistent, resulting in information gaps. For example, key fields such as supplier delivery distance and packaging capacity are missing or conflicting, which affects transportation cost calculation and warehouse location planning.

[0055] (2) The data volume is huge and highly dynamic. Large enterprises need to maintain information on thousands of parts (e.g., 5,000 parts × 100 fields = 500,000 data entries), and it needs to be updated in real time with engineering changes, supplier switching, etc. Manual maintenance is prone to errors. For example, if the PFEP is not updated in sync after the packaging specifications are changed, the line-side container and the delivered packaging will not match, which may cause unloading congestion.

[0056] (3) Issues related to personnel capabilities and mobility: Data maintenance requires familiarity with the entire material flow process, but personnel turnover can easily cause knowledge gaps (such as loss of historical change logic).

[0057] (4) Unreasonable field design, such as merging fields (e.g., merging packaging length, width and height into "packaging size") makes it impossible to calculate storage space utilization or perform intelligent analysis.

[0058] (5) It relies on manual maintenance in Excel and lacks interfaces with systems such as WMS and ERP, making it impossible to automatically obtain order frequency or inventory consumption data.

[0059] (6) The change management mechanism is missing. Engineering changes (such as material substitution) do not trigger the PFEP update process, resulting in the coexistence of old and new version data.

[0060] (7) After consuming resources to collect data, it was not used to optimize the scenario.

[0061] To address the above issues, this embodiment provides a data management method, which mainly includes the following three parts: initializing representative vehicle PFEP data, automatically generating PFEP composite primary key template data, and intelligently matching and verifying the PFEP table template for new maintenance tasks, thereby continuously improving the PFEP data for new vehicle models and newly added materials.

[0062] 1. Initialize PFEP data for representative vehicle model 1.1 Synchronize the vehicle model outlines for a specified period in the advanced planning and scheduling system, automatically recommend representative models after weighted calculation based on information such as sales volume, and then periodically retrieve the BOM of the corresponding representative models from the R&D system in the product lifecycle management system to obtain the material number and workstation code of each material, and obtain the corresponding supplier code and other information from the supplier relationship management system based on the material number of each material.

[0063] 1.2 For each material, extract the two types of PFEP composite primary keys: "material number + workstation code" and "material number + supplier code", remove duplicates, and generate an initial PFEP data form to be maintained.

[0064] 1.3 The PFEP data form is automatically pushed to the corresponding logistics planning engineer, who then completes the necessary planning data (including delivery information, warehousing information, distribution information, etc.) to generate PFEP data for each material and adds it to the PFEP data pool, thereby completing the construction of the PFEP data pool.

[0065] 2. Automatically generate PFEP composite primary key template data Using the PFEP composite primary key of "material name + workstation code + supplier code" for a full view, the system automatically performs a fuzzy search of the PFEP data pool, automatically copies delivery information, warehousing information, and distribution information, and generates a PFEP data template named "material name 01".

[0066] If the PFEP composite primary key information of "material name + workstation code + supplier code" is consistent, but the delivery information, warehousing information, and distribution information are different, then the delivery information, warehousing information, and distribution information will be automatically copied to generate another PFEP data template, which will be named "material name 02".

[0067] For example, assuming the material number is 10***404, the material description is ***motor\H***6 / 6***0\\H***6 / 6***B, the workstation code is SQ***31, the workstation name is **** workstation, the supplier code is 0000123456, and the supplier name is Suzhou *** Co., Ltd., then the PFEP composite primary key for this material can be "***motor + SQ***31 + 0000123456", and the template name is "***motor01". If the delivery information, warehousing information, and distribution information of the new model and new material ***motor are not applicable to this template parameter after intelligent matching and verification, a new PFEP intelligent template will be automatically generated, and the PFEP composite primary key for the new material ***motor will still be "***motor + SQ***31 + 0000123456", and the template name will be "***motor02".

[0068] In addition, it also sets up composite primary key templates such as "material name + workstation code", "material name + supplier code", and "material name + packaging type" to meet the needs of automatic generation and use of multi-view data.

[0069] 3. Intelligent matching and verification of new maintenance task PFEP table templates Assuming the MES system pushes a work order BOM for a new vehicle model X to the LES system, the LES system will perform the following operations: Step 1: Obtain the work order BOM and extract the "Material Number" and "Workstation Code" fields for each material.

[0070] Step 2: Match the material and supplier relationship pushed by SRM by material number to generate a composite primary key "material number + workstation code + supplier code".

[0071] Step 3: Based on the composite primary key "material number + workstation code + supplier code", accurately match PFEP information in the PFEP data pool. If the match is successful, directly retrieve the existing PFEP data from the PFEP data pool and continue to Step 6; if the match is unsuccessful, perform intelligent template fuzzy matching of composite primary key, i.e., execute Step 4 and Step 5.

[0072] Step 4: Extract the "Material Name" field corresponding to the same "Workstation Code" field from the work order BOM, and intelligently identify and process it into a standardized "Material Name" field, as shown in the following example: Example 1: Material description: *** motor\H***6 / 6***0\\H***6 / 6***B, processed as material name: *** motor; Example 2, Material Description: T-bolts\***\***\*** and T-type bolts\***\***\***, processed as material name: T-type bolts.

[0073] Step 5: Retrieve PFEP templates based on the composite primary key "Material Name + Workstation Code + Supplier Code". If the match is successful, the corresponding PFEP template information is automatically copied and used; if the match fails, further intelligent matching verification is performed. The criteria for successful matching verification include: the retrieved PFEP template is unique, and the "Packaging Type" in the template corresponds to "Packaging Size and Quantity" that meets the packaging size requirements of the material, or simultaneously meets both the packaging size and quantity requirements of the material.

[0074] Further intelligent matching and verification: If the retrieved PFEP template is not unique, the system will intelligently match the "Packaging Size and Quantity" corresponding to the "Packaging Type" in the template based on the material's dimensions, and recommend the optimal PFEP template. If no PFEP template is found, the maintenance task will be pushed to the relevant logistics planning engineer, reminding them to manually maintain the PFEP information required for the composite primary key "Material Number + Workstation Code + Supplier Code" to improve the PFEP data pool information.

[0075] Step 6: Automatically push the matching results to the relevant logistics planning engineers for manual review. Record and learn from the logistics planning engineers' review and adjustment results to optimize the subsequent intelligent matching and verification algorithm for similar materials.

[0076] In summary, the data management method provided in the above embodiments, on the one hand, designs multiple sets of precise and fuzzy PFEP table composite primary keys to meet the needs of multi-dimensional and intelligent maintenance of PFEP data. For example, by setting a composite primary key of "material number / material name + workstation code + supplier code" to meet the needs of full-view data, and setting "material number / material name + workstation code", "material number / material name + supplier code", and "material number / material name + packaging type" to meet the needs of multi-view data use, and designs a PFEP intelligent maintenance template function; on the other hand, it develops PFEP table template initialization and intelligent matching verification logic to realize the construction of a data system of "rigid framework + flexible filling" and intelligent matching verification of composite primary key templates, strengthens data uniqueness, ensures business stability through standardized primary fields, and supports agile response of PFEP maintenance management by means of dynamically extended fields and intelligent technology. Therefore, it can solve the problems of scattered and inconsistent data sources, eliminate information silos, reduce data error costs by 30%, and improve the accuracy of warehouse location planning; it can solve the problems of large data volume and delayed updates, with a real-time data update rate of over 95%, reducing unloading congestion by 50%, significantly improving the matching rate of packaging and line-side containers, and greatly reducing the risk of line stoppage; it can solve the problems of personnel capability and mobility, shortening the training cycle for new employees by 60%, reducing knowledge gaps by 70%, and reducing the historical logic loss rate to below 5%; it can solve the problem of unreasonable field design, supporting intelligent algorithm optimization, and improving the efficiency of dynamic warehouse location allocation by 40%; it can solve the problems of Excel dependence and system isolation, reducing manual maintenance by 70%, data error rate to less than 1%, and significantly improving order response speed; it can solve the problem of the lack of a data change management mechanism for the PFEP table, achieving a change synchronization rate of 100%; and it can solve the problem of data not driving business optimization, improving the timeliness of replenishment, reducing line-side inventory, and doubling the efficiency of AGV scheduling. In other words, this embodiment enhances dynamism, intelligence, and system integration by setting multiple sets of precise and fuzzy composite primary keys for PFEP tables and developing intelligent matching and verification logic for PFEP templates, while maintaining data standardization and flexibility to adapt to different business needs, thereby improving the efficiency and accuracy of PFEP data maintenance.

[0077] Based on the same inventive concept as the foregoing embodiments, this application provides a computing device, such as... Figure 2 As shown, the device includes: a processor 310 and a memory 311 storing a computer program; wherein, Figure 2 The processor 310 shown in the diagram does not indicate that there is only one processor 310, but only indicates the positional relationship of the processor 310 relative to other devices. In practical applications, there can be one or more processors 310; similarly, Figure 2The memory 311 shown in the diagram has the same meaning, that is, it is only used to indicate the positional relationship of memory 311 relative to other devices. In practical applications, there can be one or more memories 311. When the processor 310 runs the computer program, the data management method applied to the above-mentioned device is implemented.

[0078] The device may also include at least one network interface 312. The various components of the device are coupled together via a bus system 313. It is understood that the bus system 313 is used to implement communication between these components. In addition to a data bus, the bus system 313 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 2 The general designated all buses as Bus System 313.

[0079] The memory 311 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 311 described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0080] The memory 311 in this embodiment is used to store various types of data to support the operation of the device. Examples of this data include: any computer programs used to operate on the device, such as operating systems and applications; contact data; phonebook data; messages; pictures; videos, etc. The operating system includes various system programs, such as the framework layer, core library layer, driver layer, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications, such as media players, browsers, etc., used to implement various application services. Here, the program implementing the method of this embodiment can be included in the application.

[0081] Based on the same inventive concept as the foregoing embodiments, this embodiment also provides a computer-readable storage medium storing a computer program. The computer-readable storage medium can be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM), etc.; it can also be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc. When the computer program stored in the computer-readable storage medium is executed by a processor, it implements the above-described data management method. For the specific steps implemented when the computer program is executed by the processor, please refer to [link to relevant documentation]. Figure 1 The description of the illustrated embodiments will not be repeated here.

[0082] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0083] In this document, the terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, which includes not only the elements listed but also other elements not expressly listed.

[0084] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data management method, characterized in that, The method includes: Obtain the material information of the materials to be managed, including material identifier, workstation identifier, and supplier identifier; the material identifier includes material number and material name; The first composite primary key of the material to be managed is composed of the material number, the workstation identifier, and the supplier identifier, and a preset PFEP database is queried based on the first composite primary key; the PFEP database includes PFEP data of multiple materials; In response to the absence of PFEP data matching the material to be managed, a second composite primary key for the material to be managed is formed based on at least one of the workstation identifier and the supplier identifier and the material name, and a preset PFEP data template library is retrieved based on the second composite primary key; the PFEP data template library includes PFEP data templates for multiple materials; In response to the PFEP data template matching the material to be managed being retrieved, PFEP data of the material to be managed is generated based on the PFEP data template matching the material to be managed.

2. The method according to claim 1, characterized in that, The process of obtaining material information for the materials to be managed includes: Obtain the bill of materials (BOM) for the target model of the target engineering vehicle; the BOM includes the material number, material name, and workstation identifier of each material required for the production or manufacturing of the target model; The correspondence between the material number and the supplier identifier is queried based on the material number of the material to be managed, and the supplier identifier of the material to be managed is determined; the material to be managed is any material in the bill of materials.

3. The method according to claim 2, characterized in that, Before querying the preset PFEP database based on the first composite primary key, the method includes: Based on the preset information of each model of the target engineering vehicle, at least one typical representative model of the target engineering vehicle is determined; Based on at least one of the workstation identifier and supplier identifier of each material in the bill of materials corresponding to at least one typical representative vehicle model, and the material number, a third composite primary key corresponding to each material and not repeated is formed. Based on the third composite primary key corresponding to the target material, generate and output the PFEP data form corresponding to the target material to request the configuration of the corresponding PFEP data; the target material can be any of the aforementioned materials; In response to the maintenance operation of the PFEP data form corresponding to the target material, the PFEP data of the target material is determined and added to the PFEP database.

4. The method according to claim 3, characterized in that, Before retrieving the preset PFEP data template library based on the second composite primary key, the method includes: Based on the material name of each material in the bill of materials corresponding to at least one typical representative vehicle model, and at least one of the following: workstation identifier, supplier identifier, and packaging type, a fourth composite primary key is formed for each of the materials. The PFEP database is retrieved based on the fourth composite primary key corresponding to the target material to determine the PFEP data that matches the fourth composite primary key; Based on the PFEP data matching the fourth composite primary key, a PFEP data template for the target material is generated, and the PFEP data template for the target material is added to the PFEP data template library.

5. The method according to claim 4, characterized in that, The step of generating the PFEP data template for the target material based on the PFEP data matching the fourth composite primary key includes: In response to the existence of multiple PFEP data entries matching the fourth composite primary key, a PFEP data template for the target material is generated for each PFEP data entry matching the fourth composite primary key.

6. The method according to claim 2, characterized in that, Before retrieving the preset PFEP data template library based on the second composite primary key, the method includes: The names of different materials with the same workstation identifier in the bill of materials for the target model of the target engineering vehicle are uniformly corrected.

7. The method according to claim 2, characterized in that, The bill of materials also includes the dimensions of each material, and the PFEP data template includes packaging dimensions; generating the PFEP data of the material to be managed based on the PFEP data template matching the material to be managed includes: Since there are multiple PFEP data templates that match the second composite primary key, the PFEP data template with the highest matching degree between the packaging size and the size of the material to be managed is determined as the PFEP data template that matches the material to be managed. The PFEP data of the material to be managed is generated based on the PFEP data template that matches the material to be managed.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: In response to the failure to find a PFEP data template matching the material to be managed, an alert message is output to complete the PFEP data of the material to be managed.

9. A computing device, characterized in that, include: A processor and a memory storing a computer program, wherein, when the processor executes the computer program, the steps of the data management method according to any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium, characterized in that, The system contains a computer program that, when executed by a processor, implements the steps of the data management method according to any one of claims 1 to 8.

Images