Product data management method, device, system, and storage medium
By constructing data objects for product documents and distribution service interfaces, the inaccuracy problem in the product data management system is solved, enabling dynamic and accurate management and efficient distribution of product documents, and supporting version updates and new material management for product data.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- ZHONGKE YUNGU TECH
- Filing Date
- 2025-02-24
- Publication Date
- 2026-08-04
AI Technical Summary
In existing product data management systems, the management of product information documents is imprecise, resulting in multiple products borrowing standard documents, dynamic changes in relationships that are difficult to manage accurately, and the distribution of change information is difficult and untimely.
By constructing data objects for documentation, product BOM management product documentation documents are generated, and these documents are distributed to the product documentation application platform using a distribution service interface, enabling precise management of product data, including dynamic management of version updates and newly added materials.
It enables dynamic and precise management of product information documents, improves data distribution efficiency, ensures the standardization and version traceability of document data, avoids errors and omissions in manual maintenance, and supports the accurate acquisition of product information documents.
Smart Images
Figure CN120429268B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of product data management technology, specifically to a product data management method, apparatus, system storage medium. Background Technology
[0002] Product documentation is a crucial technical document that requires significant resources to compile during product development. It serves as essential technical documentation for customer service and application support. Key categories include: product manuals, product handbooks, technical documents, certification and compliance documents, etc.
[0003] With the continuous development of manufacturing and information technology, product data management systems (PDM systems) can effectively and systematically manage product data by compiling and managing product documentation documents based on product models. However, in PDM systems, the management of product documentation documents typically begins with compiling product documentation documents according to the product structure, followed by manual maintenance of the correspondence between these documents and each product by designated personnel. After the product documentation is compiled, it is then distributed to different users (in formats such as PDF) via email, online platforms, etc., based on product delivery requirements. Recipients receive the data according to their needs. This leads to situations where standard product documentation documents are borrowed from multiple products, and the borrowing relationship between product documentation documents and products changes dynamically (e.g., new products borrow existing product documentation, and old products use new product documentation). This dynamic and dispersed relationship hinders accurate management. Furthermore, when delivered product documentation is changed or updated, the changed information and the updated documentation need to be redistributed to all recipients simultaneously, making it difficult to effectively control the difficulty and timeliness of data distribution. Summary of the Invention
[0004] The purpose of this application is to provide a product data management method, apparatus, and system storage medium to solve the technical defects in the prior art where product data management systems rely on manual management of product data, resulting in inaccurate product data management.
[0005] To achieve the above objectives, the first aspect of this application provides a product data management method applied to a product data management system. The product data management system includes a product documentation application platform and a distribution service interface. The distribution service interface is used to distribute product data to the product documentation application platform. The management method includes:
[0006] Retrieve the current version of the product and all documentation and BOM data for the current version. The BOM data includes all the components of the product and the sub-relationships between each component.
[0007] Construct data objects for documents;
[0008] Add all product documentation to the documentation data object;
[0009] Add data objects of information and documents to the BOM data to generate the first product BOM for managing product information and documents;
[0010] Extract the sub-level relationships between each document and each component material in the first product BOM management product data document to generate a first product association relationship form for the product;
[0011] The product's first product BOM management product information document and first product association form are distributed to the product information document application platform through the distribution service interface to complete the product data management of the product under the current version.
[0012] In embodiments of this application, the management method further includes: upon detecting an update to the current version of the product, obtaining the updated version of the product and all documentation documents for the product under the updated version; adding all documentation documents for the product under the updated version to a documentation data object; adding the documentation data object to BOM data to generate a second product BOM management product documentation document for the product under the updated version; extracting the sub-sub-relationships between each documentation document and each component material in the second product BOM management product documentation document to generate a second product association form for the product under the updated version; determining whether the category attribute value of each documentation document in the second product BOM management product documentation document is a preset value through a distribution service interface; removing documentation documents whose category attribute values are not preset values from the second product BOM management product documentation document; and distributing the removed second product BOM management product documentation document and the second product association form to the product documentation application platform through the distribution service interface to replace the first product BOM management product documentation document and the first product association form, thereby completing the product data management for the product under the updated version.
[0013] In embodiments of this application, the management method further includes: upon detecting the existence of a new material, determining whether the material's level is a product level based on the material's attribute identifier; if the material's level is determined to be a product level based on the material's attribute identifier, identifying the material as a new product; obtaining the target BOM data corresponding to the new product; determining the target product BOM management product information document and the target product association form associated with the target BOM data; and distributing the target product BOM management product information document and the target product association form to the product information document application platform through a distribution service interface.
[0014] In embodiments of this application, the management method further includes: determining that the material is a product sub-component when the material's level is not a product level based on the material's attribute identifier; and distributing the product sub-component to the product documentation application platform through a distribution service interface.
[0015] In embodiments of this application, constructing a document data object includes: obtaining the product identification code of the product; obtaining the category to which each document belongs in all documents of the product, so as to determine the document category code of each document in all documents according to the category; obtaining the language used by each document in all documents, so as to determine the language code of each document in all documents according to the language used; determining the object code of the document data object according to the product identification code, the document category code and the language code; and constructing the document data object based on the object code.
[0016] In embodiments of this application, the management method further includes: when the product documentation application platform receives a query request from a client carrying a product identification code of a document to be queried, determining the language code of the document to be queried based on the language used by the client, and querying whether a product association form corresponding to the product identification code exists; if a product association form corresponding to the product identification code exists, determining the target object code of the target document data object containing the document to be queried based on the product association form; obtaining the target document data object based on the target object code, and querying whether a target dataset file corresponding to the language code exists in the target document data object; if a target dataset file corresponding to the language code exists in the target document data object, returning the target dataset file to the client.
[0017] In embodiments of this application, the management method further includes: when the product data document application platform receives a category code filtering instruction triggered by the client and carries a document category code, it responds to the category code filtering instruction to query whether there is a target dataset file in the target data document data object that corresponds to the document category code and language code; if it is determined that there is a target dataset file in the target data document data object that corresponds to the document category code and language code, it returns the target dataset file to the client.
[0018] In embodiments of this application, the management method further includes: if it is determined that there is no product association table corresponding to the product identification code, the product data document application platform generates a prompt that no data document is available, so as to return the prompt that no data document is available to the client.
[0019] In embodiments of this application, the management method further includes: when it is determined that there is no target dataset file corresponding to the language code in the target data document data object, the product data document application platform generates a prompt that no data document is available, so as to return the prompt that no data document is available to the client.
[0020] A second aspect of this application provides a product data management device, comprising:
[0021] The memory is configured to store instructions;
[0022] The processor is configured to retrieve the instructions from the memory and, when executing the instructions, to perform the aforementioned product data management method.
[0023] A third aspect of this application provides a product data management system, comprising:
[0024] Product information document application platform;
[0025] The distribution service interface is used to distribute product data to the product documentation application platform;
[0026] The aforementioned product data management device.
[0027] A fourth aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the product data management method described above.
[0028] The above technical solution acquires the current version of the product and all documentation and BOM data for that version. The BOM data includes all components of the product and the sub-relationships between each component. It then constructs a documentation data object; adds all product documentation to this object; adds the documentation data object to the BOM data to generate the first product BOM management document; extracts the sub-sub-relationships between each document and each component in the first product BOM management document to generate the first product relationship form; and distributes the first product BOM management document and the first product relationship form to the product documentation application platform via a distribution service interface. This completes the product data management for the current version, thereby achieving precise management of product data.
[0029] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description
[0030] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:
[0031] Figure 1 The illustration shows a flowchart of a product data management method according to an embodiment of this application;
[0032] Figure 2 This illustration schematically shows a product BOM management product information document according to an embodiment of this application;
[0033] Figure 3 The diagram illustrates the internal structure of a computer device according to an embodiment of this application. Detailed Implementation
[0034] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.
[0035] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.
[0036] Figure 1 The illustration shows a flowchart of a product data management method according to an embodiment of this application. Figure 1 As shown in the figure, this application provides a product data management method. This management method can be applied to a product data management system, which includes a product information document application platform and a distribution service interface. The distribution service interface is used to distribute product data to the product information document application platform. The management method may include the following steps:
[0037] Step 101: Obtain the current version of the product and all documentation and BOM data for the current version. The BOM data includes all the components of the product and the sub-relationships between each component.
[0038] In this embodiment, it should be noted that the product data management system can refer to a PDM system, which is a software system used to centrally store, organize, and manage data related to the entire product lifecycle. It improves production efficiency by integrating CAD data and BOM (Bill of Materials) and other design information, enabling information sharing and collaboration between the design department and other departments. The product can refer to machinery and equipment, and product documentation can include, but is not limited to, product manuals, maintenance manuals, and technical documents. Each document can have a different format, including PDF, Doc, etc. BOM data can refer to a bill of materials, which is a detailed list of all raw materials, parts, and components required in the product manufacturing process. It typically includes information such as the name, quantity, specifications, model, brand, material, and purpose of each item. In this technical solution, the product's BOM data can include all the constituent materials of the product and the sub-level relationships between each constituent material. For example, taking a fixed-leg tower crane as an example, the components of a fixed-leg tower crane may include transition sections, legs, pre-embedded leg foundation sections, and climbing frames, etc. Among them, transition sections, pre-embedded leg foundation sections, and climbing frames are all sub-levels of the fixed-leg tower crane product.
[0039] Step 102: Construct the document data object.
[0040] In this embodiment of the application, it should be noted that the document data object can refer to a data object that can record key attributes of document categories through attribute forms, and manage document data as attachments after being added as a dataset. Specifically, the attribute information included in the document data object can be as shown in Table 1, including:
[0041] Table 1 shows the attribute information included in the document data objects.
[0042] file name DocumentName Document Encoding DocumentID Document Version DocumentRevision Document Categories DocumentType Keywords Keyword describe Describe Related datasets DataSet
[0043] In this embodiment of the application, constructing a document data object includes: obtaining the product identification code of the product; obtaining the category to which each document belongs in all documents of the product belongs, so as to determine the document category code of each document in all documents according to the category; obtaining the language used by each document in all documents, so as to determine the language code of each document in all documents according to the language used; determining the object code of the document data object according to the product identification code, document category code and language code; and constructing the document data object based on the object code.
[0044] In this embodiment, it should be noted that when constructing the document data object, encoding is required. The encoding for each document data object needs to be written according to standard encoding rules. Specifically, firstly, the product identification code of the product can be obtained. Each product has a unique product identification code, which is used to identify the initial product information associated with the product document. When a new product is referenced later, the initial product information can be identified based on the product identification code. Secondly, the category to which each document in all the product's documents belongs is obtained, so that the document category code of each document in all the documents can be determined based on the category. The document category code can be used to identify and distinguish documents of different categories of the same product. Thirdly, the language used by each document in all the documents is obtained, so that the language code of each document in all the documents can be determined based on the language used. Thus, the object encoding of the document data object can be written based on the product identification code, document category code, and language code using standard encoding rules. In this way, the document data object can be further constructed through the object encoding.
[0045] Step 103: Add all product documentation to the documentation data object.
[0046] In this embodiment, it should be noted that after the data object for the documentation is constructed by extracting the code, all documentation documents for the product can be added to the data object. Specifically, all documentation documents can be added to the data object as a dataset and managed as attachments. The data object will record the key attributes of each documentation category through an attribute form.
[0047] Step 104: Add the data object of the document to the BOM data to generate the first product BOM management product data document.
[0048] In this embodiment, it should be noted that after adding all product documentation to the documentation data object, the documentation data can be treated as a component material and added to the product's BOM data in the form of a material to generate the product's first product BOM for managing product documentation. In this way, the product's documentation is managed within the BOM data, thereby achieving dynamic and strong association management between the product's documentation and the product itself. Figure 2 The diagram illustrates a product BOM (Bill of Materials) management system for product documentation. Figure 2 As shown, the product is a fixed-leg tower crane. The components of a fixed-leg tower crane may include transition sections, legs, embedded leg foundation sections, and climbing frames, etc. Among these, the transition sections, embedded leg foundation sections, and climbing frames are all sub-levels of the fixed-leg tower crane product. The maintenance manual and operation manual are the documentation documents for this product. After adding the documentation data objects of the fixed-leg tower crane to the BOM data, both the maintenance manual and operation manual are added to the BOM data as materials for management.
[0049] It should be noted that common data objects for the same series of products can be referenced in the BOM data of the same series of products. When the data objects for the product are subsequently revised or changed, the data objects for the same series of products associated with the data objects can be updated synchronously, so as to achieve standardized, universal and efficient management of the product's data objects.
[0050] Step 105: Extract the sub-sub-level relationships between each document and each component material in the first product BOM management product data document to generate the first product association relationship form.
[0051] In this embodiment, it should be noted that when adding document data objects to BOM data to generate the first product BOM management product document, each document in the document data object is automatically categorized under its associated constituent material. Therefore, after generating the first product BOM management product document, the sub-sub-level relationships between each document and each constituent material in the first product BOM management product document can be directly extracted to generate a first product association relationship form to record these sub-sub-level relationships. Specifically, with... Figure 2 For example, the maintenance manual and operation manual are associated with the product level of outrigger-fixed tower crane. Therefore, both the maintenance manual and operation manual are categorized under outrigger-fixed tower crane, resulting in a sub-sub-level relationship between the maintenance manual and operation manual and outrigger-fixed tower crane.
[0052] Step 106: Distribute the product's first product BOM management product information document and the first product association form to the product information document application platform through the distribution service interface to complete the product data management of the product in the current version.
[0053] In this embodiment, it should be noted that after generating the first product BOM management product information document and the first product association form, the first product BOM management product information document and the first product association form can be distributed to the product information document application platform through a distribution service interface to complete the product data management of the product in the current version. In this technical solution, in order to automatically extract the required data to the product information document application platform, a distribution service interface was developed using Java. This distribution service interface can automatically extract data that meets the requirements and distribute it to the product information application platform.
[0054] In this embodiment, the management method further includes: when the product documentation application platform receives a query request from a client carrying a product identification code of a document to be queried, determining the language code of the document to be queried based on the language used by the client, and querying whether a product association form corresponding to the product identification code exists; if a product association form corresponding to the product identification code exists, determining the target object code of the target document data object containing the document to be queried based on the product association form; obtaining the target document data object based on the target object code, and querying whether a target dataset file corresponding to the language code exists in the target document data object; if a target dataset file corresponding to the language code exists in the target document data object, returning the target dataset file to the client.
[0055] In this embodiment, it should be noted that the client can initiate a query request by entering a product identification code in the product documentation application platform to retrieve the required product data. After receiving the query request from the client carrying the product identification code of the document to be queried, the product documentation application platform first determines the language code of the document to be queried based on the language used by the client, and then checks whether a product association form corresponding to the input product identification code exists. If a product association form corresponding to the product identification code exists, the target object code of the target document data object containing the document to be queried can be further determined based on the product association form. Thus, the corresponding target document data object can be obtained based on the target object code, and the target document data object can be further queried to see if a target dataset file corresponding to the language code exists. If a target dataset file corresponding to the language code is found in the target document data object, the target dataset file can be considered the document to be queried by the client, and the target dataset file can be returned to the client.
[0056] In this embodiment of the application, the management method further includes: when the product data document application platform receives a category code filtering instruction triggered by the client and carries a document category code, it responds to the category code filtering instruction to query whether there is a target dataset file in the target data document data object that corresponds to the document category code and language code; if it is determined that there is a target dataset file in the target data document data object that corresponds to the document category code and language code, it returns the target dataset file to the client.
[0057] In this embodiment, it should be noted that after the client enters the product identification code into the product document application platform to initiate a query request, and the platform receives the request carrying the product identification code of the document to be queried, it can also provide a document category code display interface, allowing the client to select the desired document category codes as needed. If the platform receives a category code filtering instruction triggered by the client, it responds to the instruction to query whether a target dataset file corresponding to the document category code and language code selected by the client exists in the target document data object. If a target dataset file corresponding to the document category code and language code is found in the target document data object, it can be considered the document to be queried by the client, and the target dataset file is returned to the client. If no target dataset file corresponding to the document category code and language code is found in the target document data object, it can be considered that the document to be queried by the client does not exist in the target document data object. In this case, a message indicating no available document can be returned to the client.
[0058] In this embodiment of the application, the management method further includes: if it is determined that there is no product association table corresponding to the product identification code, the product data document application platform generates a prompt that no data document is available, so as to return the prompt that no data document is available to the client.
[0059] In this embodiment, it should be noted that the client can initiate a query request by entering a product identification code in the product documentation application platform to retrieve the required product data. After receiving the query request from the client carrying the product identification code of the document to be queried, the product documentation application platform first determines the language code of the document to be queried based on the language used by the client, and then checks whether a product association form corresponding to the entered product identification code exists. If it is determined that no product association form corresponding to the product identification code exists, it can be assumed that the target document data object does not contain the document to be queried by the client. At this time, the product documentation application platform can generate a "no available document" message to return to the client.
[0060] In this embodiment of the application, the management method further includes: if it is determined that there is no target dataset file corresponding to the language code in the target data document data object, the product data document application platform generates a prompt that no data document is available, so as to return the prompt that no data document is available to the client.
[0061] In this embodiment, it should be noted that the client can initiate a query request by entering a product identification code in the product documentation application platform to retrieve the required product data. After receiving the query request from the client carrying the product identification code of the document to be queried, the product documentation application platform first determines the language code of the document to be queried based on the language used by the client, and then checks whether a product association form corresponding to the entered product identification code exists. If a product association form corresponding to the product identification code exists, the target object code of the target document data object containing the document to be queried can be further determined based on the product association form. Thus, the corresponding target document data object can be obtained based on the target object code, and the target document data object can be further queried to see if a target dataset file corresponding to the language code exists. If no target dataset file corresponding to the language code is found in the target document data object, it can be assumed that the document to be queried by the client does not exist in the target document data object. At this time, the product documentation application platform can generate a "no available document" message to return to the client.
[0062] The above technical solution acquires the current version of the product and all documentation and BOM data for that version. The BOM data includes all components of the product and the sub-relationships between each component. It then constructs a documentation data object; adds all product documentation to this object; adds the documentation data object to the BOM data to generate the first product BOM management document; extracts the sub-sub-relationships between each document and each component in the first product BOM management document to generate the first product relationship form; and distributes the first product BOM management document and the first product relationship form to the product documentation application platform via a distribution service interface. This completes the product data management for the current version, thereby achieving precise management of product data.
[0063] In this embodiment, the management method further includes: upon detecting an update to the current version of the product, obtaining the updated version of the product and all documentation documents for the product under the updated version; adding all documentation documents for the product under the updated version to a documentation data object; adding the documentation data object to BOM data to generate a second product BOM management product documentation document for the product under the updated version; extracting the sub-sub-relationships between each documentation document and each component material in the second product BOM management product documentation document to generate a second product association form for the product under the updated version; determining whether the category attribute value of each documentation document in the second product BOM management product documentation document is a preset value through a distribution service interface; removing documentation documents whose category attribute values are not preset values from the second product BOM management product documentation document; and distributing the removed second product BOM management product documentation document and the second product association form to the product documentation application platform through the distribution service interface to replace the first product BOM management product documentation document and the first product association form, thereby completing the product data management for the product under the updated version.
[0064] In this embodiment, it should be noted that when an update to the current version of the product is detected, i.e., a new version of the product is released, product data management for that product under the new version also needs to be completed. Specifically, the updated version of the product and all documentation documents for the updated version can be obtained first. Since the only difference between the new and old versions of the product is the documentation documents, the documentation document data objects and BOM data from the previous version can be reused. Therefore, all documentation documents for the updated version can be added to the documentation document data object, and then the documentation document data object can be added to the BOM data to generate the second product BOM management product documentation document for the updated version. Similarly, by extracting the sub-child relationships between each documentation document and each component material in the second product BOM management product documentation document, a second product association relationship form for the updated version can be generated.
[0065] After generating the second product BOM management product documentation document, it is necessary to further determine whether each document in the second product BOM management product documentation document is a document that has passed the review and is required for release. Only documents that have passed the review and are required for release need to be distributed to the product documentation document application platform. Specifically, the distribution service interface can be used to determine whether the category attribute value of each document in the second product BOM management product documentation document is a preset value, thus determining whether the document has passed the review and is required for release. If the category attribute value of the document is a preset value, it is considered that it needs to be distributed. If the category attribute value of the document is not a preset value, it is considered that it does not need to be distributed, and the document may still be under review or in the draft stage. Therefore, after determining the category attribute value of each document in the second product BOM management product documentation document, documents whose category attribute values are not preset values can be removed, so that only documents that have passed the review and are required for release are retained. Finally, the removed second product BOM management product data document and the second product association form are distributed to the product data document application platform through the distribution service interface to replace the first product BOM management product data document and the first product association form, thereby completing the product data management of the product in the updated version.
[0066] In this embodiment of the application, the management method further includes: when a new material is detected, determining whether the material's level is a product level based on the material's attribute identifier; if the material's level is determined to be a product level based on the material's attribute identifier, determining that the material is a new product; obtaining the target BOM data corresponding to the new product; determining the target product BOM management product information document and the target product association form associated with the target BOM data; and distributing the target product BOM management product information document and the target product association form to the product information document application platform through a distribution service interface.
[0067] In this embodiment, it should be noted that when a new material is detected in the PDM system, the first step is to determine whether the material's level is a product level based on its attribute identifier. For example, if the material's attribute identifier is "climbing frame," then the material's level is not a product level, as the climbing frame belongs to a sub-level of the "outrigger-fixed tower crane" product. Conversely, if the material's attribute identifier is "outrigger-fixed tower crane," then the material's level is a product level. Once the material's level is determined to be a product level based on its attribute identifier, it can be identified as a new product. At this point, the target BOM data corresponding to the new product is obtained. Next, the target product BOM management product documentation document and the target product association form associated with the target BOM data are further determined. These documents can then be distributed to the product documentation application platform via a distribution service interface to complete the product data management for the new product.
[0068] In this embodiment of the application, the management method further includes: if the material level is determined to be not a product level based on the material's attribute identifier, then the material is determined to be a product sub-component; and the product sub-component is distributed to the product data document application platform through the distribution service interface.
[0069] In this embodiment, it should be noted that when a new material is detected in the PDM system, the first step is to determine whether the material's level is a product level based on its attribute identifier. If the material's level is determined not to be a product level based on its attribute identifier, it can be determined that the material is a sub-component of a product at a sub-level, and that the new product corresponding to this new material has not yet been released. At this time, the product sub-component can be distributed to the product documentation application platform through the distribution service interface for the management of the new material.
[0070] This technical solution encodes and manages the version of product documentation data through data objects, which facilitates standardized management and version traceability of document data. Product documentation data objects are managed as sub-components within the product design BOM, enabling dynamic and precise management of the relationship between product documentation and product management, avoiding errors and omissions caused by manual maintenance. Based on the extraction and distribution of product documentation datasets, product documentation data objects, and the data form showing their association with the entire machine, the solution dynamically updates and automatically distributes newly released and modified product documentation data to the product documentation application platform, effectively improving the efficiency of product documentation data distribution. The product documentation application platform, based on received key query information, accurately retrieves the corresponding category of product documentation documents associated with the product through the product documentation data relationship form, enabling precise retrieval and application of product documentation documents.
[0071] This application provides a product data management device, including:
[0072] The memory is configured to store instructions;
[0073] The processor is configured to retrieve the instructions from the memory and, when executing the instructions, to perform the aforementioned product data management method.
[0074] This application provides a product data management system, including:
[0075] Product information document application platform;
[0076] The distribution service interface is used to distribute product data to the product documentation application platform;
[0077] The aforementioned product data management device.
[0078] This application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the product data management method described above.
[0079] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3 As shown. The computer device includes a processor A01, a network interface A02, memory (not shown), and a database (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A04. The database of the computer device stores product data management method data. The network interface A02 of the computer device is used for communication with external terminals via a network connection. When the computer program B02 is executed by the processor A01, it implements a...
[0080] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0081] This application provides an apparatus, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of a product data management method.
[0082] This application also provides a computer program product that, when executed on a data processing device, is adapted to perform steps of an initialization product data management method.
[0083] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0084] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0085] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0086] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0087] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0088] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0089] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0090] It should also be noted that 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 process, method, article, or apparatus. Unless otherwise specified, 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.
[0091] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
Claims
1. A product data management method characterized by, An application is made in a product data management system, which includes a product documentation application platform and a distribution service interface. The distribution service interface is used to distribute product data to the product documentation application platform. The management method includes: Obtain the current version of the product and all documentation and BOM data for the product under the current version. The BOM data includes all the constituent materials of the product and the sub-level relationships between each constituent material. Construct data objects for documents; Add all the product documentation to the documentation data object; Add the data object to the BOM data to generate the first product BOM management product data document for the product; Extract the sub-level relationships between each document and each component material in the first product BOM management product data document to generate the first product association relationship form for the product; The first product BOM management product data document and the first product association form of the product are sent to the product data document application platform through the distribution service interface to complete the product data management of the product under the current version; The construction of document data objects includes: Obtain the product identification code of the product; Obtain the category to which each document belongs in all the document documents of the product, so as to determine the document category code of each document in all the document documents according to the category; Obtain the language used in each document among all the documents, and determine the language code of each document among all the documents based on the language used; The object encoding of the document data object is determined based on the product identification code, the document category code, and the language code. The document data object is constructed based on the object encoding.
2. The product data management method according to claim 1, characterized by, The management method also includes: If an update to the current version of the product is detected, obtain the updated version of the product and all documentation for the product under the updated version. Add all documentation for the product in the updated version to the documentation data object; Add the data object to the BOM data to generate the second product BOM management product data document for the product in the updated version; Extract the sub-child relationships between each document and each component material in the product data document of the second product BOM management to generate the second product association relationship form of the product in the updated version; The distribution service interface is used to determine whether the category attribute value of each document in the product data document of the second product BOM management is a preset value; Remove documents from the product data documents of the second product BOM management that do not have the preset value for the category attribute value; The removed second product BOM management product data document and the second product association form are distributed to the product data document application platform through the distribution service interface to replace the first product BOM management product data document and the first product association form, thereby completing the product data management of the product in the updated version.
3. The product data management method according to claim 1, characterized by, The management method also includes: If a new material is detected, determine whether the material's level is a product level based on the material's attribute identifier; If the material's level is determined to be product level based on its attribute identifier, then the material is determined to be a new product. Obtain the target BOM data corresponding to the newly added product; Identify the target product BOM management product information document associated with the target BOM data, and the target product association form; The target product BOM management product information document and the target product association form are distributed to the product information document application platform through the distribution service interface.
4. The product data management method according to claim 3, characterized by, The management method also includes: If the material's attribute identifier determines that the material's level is not a product level, then the material is determined to be a product sub-component. The product sub-components are distributed to the product documentation application platform via the distribution service interface.
5. The product data management method according to claim 1, characterized by, The management method also includes: When the product information document application platform receives a query request from a client carrying a product identification code of the document to be queried, it determines the language code of the document to be queried based on the language used by the client, and queries whether there is a product association form corresponding to the product identification code. If it is determined that a product association form corresponding to the product identification code exists, the target object code of the target document data object where the document to be queried is located is determined according to the product association form; The target document data object is obtained according to the target object code, and the target data document data object is used to query whether there is a target dataset file corresponding to the language code. If it is determined that a target dataset file corresponding to the language code exists in the target document data object, the target dataset file is returned to the client.
6. The product data management method according to claim 5, characterized by, The management method also includes: When the product data document application platform receives a category code filtering instruction triggered by the client, which carries a document category code, it responds to the category code filtering instruction to query whether there is a target dataset file in the target data document object that corresponds to the document category code and the language code. If it is determined that a target dataset file corresponding to the document category code and the language code exists in the target document data object, the target dataset file is returned to the client.
7. The product data management method according to claim 5, characterized by, The management method also includes: If it is determined that there is no product association table corresponding to the product identification code, the product data document application platform generates a "no available data document" prompt and returns the "no available data document" prompt to the client.
8. The product data management method of claim 5, wherein, The management method also includes: If it is determined that there is no target dataset file corresponding to the language code in the target document data object, the product document application platform generates a no-access document prompt and returns the no-access document prompt to the client.
9. A product data management apparatus characterized by comprising: include: The memory is configured to store instructions; A processor is configured to retrieve the instructions from the memory and, when executing the instructions, to implement the product data management method according to any one of claims 1 to 8.
10. A product data management system, characterized by include: Product information document application platform; The distribution service interface is used to distribute product data to the product information document application platform; The product data management device according to claim 9.
11. A machine-readable storage medium having stored thereon instructions, the instructions being executable by a machine to cause the machine to: When executed by a processor, this instruction causes the processor to be configured to perform the product data management method according to any one of claims 1 to 8.