Design change management method, device, equipment, storage medium and program product

Abstract

The present application relates to the field of database management technology, and provides a design change management method, device, equipment, storage medium and program product. The design change management method between multiple systems includes: encoding and archiving drawing engineering files to obtain first coding information; comparing the difference between the first coding information and the latest coding information stored in itself; if there is a difference between the first coding information and the latest coding information, then determining the change of the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file according to the design change information; if the bill of materials changes, then generating a change task for the drawing engineering file according to the design change information. The present application can realize the linkage change and synchronous management between the bill of materials in the product life cycle management system and the drawing engineering file in the engineering document management system, thereby realizing the linkage and synchronization of design changes between multiple systems, which can improve the consistency of quality and the reliability of the product.

Description

Technical Field

[0001] The present application relates to the technical field of database management, and in particular to a design change management method, apparatus, device, storage medium and program product. Background Art

[0002] In actual production management, BOM (Bill of Materials) is generally managed in the Product Lifecycle Management (PLM) system, and drawings are managed offline. The two are in a relatively isolated state.

[0003] When the BOM in batch production needs to be changed for some reason (Engineering Change Order, ECO), the drawings should be changed synchronously. However, because the two are in different management systems, when the BOM of the PLM system is changed, the drawings cannot be changed synchronously, and there is no process linkage change. This leads to the BOM of the PLM system and the offline drawings not corresponding after many changes. When the subsequent development needs to borrow the drawings, many BOM change records may be missed, and previous problems may occur again in new projects. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the related art. To this end, the present application proposes a management method for design changes between multiple systems, which can realize linkage changes and synchronous management of design changes between multiple systems.

[0005] The present application also proposes a management device for design changes between multiple systems, an electronic device, a non-transitory computer-readable storage medium, and a computer program product.

[0006] According to the first aspect of the present application, a method for managing design changes between multiple systems includes: an engineering document management system encodes and archives drawing engineering files to obtain first coding information, and sends the first coding information to a product lifecycle management system; the product lifecycle management system compares the differences between the latest coding information stored in itself according to the first coding information; if the first coding information and the latest coding information are inconsistent, the product lifecycle management system generates design change information and sends the design change information to the engineering document management system; the engineering document management system determines the changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file according to the design change information; if the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file according to the design change information.

[0007] According to the method for managing design changes between multiple systems in the embodiment of the present application, the product lifecycle management system is responsible for proofreading the coding information, and the engineering document management system can proofread the changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering files according to the design change information sent by the product lifecycle management system, and timely discover changes in the bill of materials, thereby generating change tasks for the drawing engineering files, realizing the linkage and synchronization of design changes between multiple systems, and improving quality consistency and product reliability.

[0008] According to one embodiment of the present application, the engineering document management system determines changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file based on the design change information, including: the engineering document management system reads the first bill of materials corresponding to the latest code from the product lifecycle management system based on the design change information; the engineering document management system obtains the second bill of materials corresponding to the first code from the drawing engineering file stored in itself based on the design change information; the engineering document management system determines whether the bill of materials has changed based on the difference between the first bill of materials and the second bill of materials.

[0009] According to one embodiment of the present application, the engineering document management system encodes and archives the drawing engineering files to obtain the first coding information, including: the engineering document management system determines the coding for the components in the drawing engineering files to be archived to obtain the first coding information; wherein the first coding information includes at least one component coding; the engineering document management system verifies the legality of the component coding according to the coding rules issued by the product lifecycle management system; after the legality verification passes, the engineering document management system stores and archives the drawing engineering files to be archived and the corresponding first coding information.

[0010] According to one embodiment of the present application, if the bill of materials changes, then after the engineering document management system generates a change task for the drawing engineering file based on the design change information, it also includes: if only one component code under the same PCB project has a design change in the product lifecycle management system, the engineering document management system pushes the change task to the creator of the design change; if at least two component codes under the same PCB project have a design change in the product lifecycle management system, the engineering document management system pushes the change task to the creator with the latest design change creation date.

[0011] According to one embodiment of the present application, after the engineering document management system generates a change task for the drawing engineering file according to the design change information, it also includes: the engineering document management system executes the change task to complete the change of the drawing engineering file, and re-archives the changed drawing engineering file.

[0012] According to one embodiment of the present application, the first coding information includes a first component code and a first version information; the latest coding information includes a latest component code and a latest version information; the product lifecycle management system compares the differences between the latest coding information stored in itself and the first coding information, including: the product lifecycle management system matches the first component code with the latest component code; if the first component code and the latest component code match, the product lifecycle management system matches the first version information with the latest version information; if the first version information and the latest version information do not match, the product lifecycle management system determines that the first coding information and the latest coding information are inconsistent.

[0013] According to one embodiment of the present application, after the product lifecycle management system generates design change information and sends the design change information to the engineering document management system, it also includes: the product lifecycle management system allows the engineering document management system to read the first material list corresponding to the latest code stored in itself according to the design change information.

[0014] According to one embodiment of the present application, before the product lifecycle management system compares the differences between the first coding information and the latest coding information stored in itself, it also includes: the product lifecycle management system obtains the first coding information of the drawing engineering file to be archived in the engineering document management system; wherein the first coding information includes at least one component code; the product lifecycle management system verifies the legitimacy of the component code according to the coding rules, and returns the legitimacy verification result to the engineering document management system.

[0015] According to the second aspect of the present application, a management device for design changes between multiple systems includes an engineering document management system and a product life cycle management system; the engineering document management system includes: a first coding information module, which is used to encode and archive drawing engineering files to obtain first coding information; a first sending module, which is used to send the first coding information to the product life cycle management system, so that the product life cycle management system compares the difference between the latest coding information stored in itself according to the first coding information; a first receiving module, which is used to receive the design change information sent by the product life cycle management system if there is a difference between the first coding information and the latest coding information; a bill of materials comparison module, which is used to determine the changes in the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file according to the design change information; a change task module, which is used to generate a change task for the drawing engineering file according to the design change information if the bill of materials changes; the product life cycle management system includes: a coding information comparison module, which is used to compare the first coding information pushed by the engineering document management system with the latest coding information stored in itself; a design change information module, which is used to generate design change information if the first coding information is inconsistent with the latest coding information, and send the design change information to the engineering document management system, so that the engineering document management system determines the changes in the bill of materials of the drawing engineering file according to the design change information.

[0016] According to an electronic device of an embodiment of the third aspect of the present application, the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method for managing design changes between multiple systems such as any one of the above is implemented.

[0017] According to the non-transitory computer-readable storage medium of the fourth aspect of the present application, a computer program is stored thereon, and when the computer program is executed by a processor, it implements any of the above-mentioned methods for managing design changes between multiple systems.

[0018] According to the computer program product of the fifth aspect of the present application, the computer program includes a computer program, which, when executed by a processor, implements any of the above-mentioned methods for managing design changes between multiple systems.

[0019] The above one or more technical solutions in the embodiments of the present application have at least one of the following technical effects:

[0020] The engineering document management system can perform coding management on archived drawing engineering files and send the first coding information to the product lifecycle management system for information synchronization;

[0021] The product lifecycle management system can compare the first coding information with the latest coding information stored in itself, and when a difference is found, generate design change information and send it to the engineering document management system for synchronization;

[0022] The engineering document management system can further verify the changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering files based on the design change information, generate a change task when it is determined that the bill of materials has changed, and realize the linkage change and synchronous management between the bill of materials in the product lifecycle management system and the drawing engineering files in the engineering document management system through multi-level judgment, maintain the linkage and synchronization of design changes between multiple systems, thereby improving quality consistency and product reliability.

[0023] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0025] Figure 1 This is one of the flow charts of the method for managing design changes between multiple systems provided in an embodiment of the present application.

[0026] Figure 2 This is the second flowchart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0027] Figure 3 This is the third flow chart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0028] Figure 4 This is the fourth flow chart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0029] Figure 5 It is a system interaction diagram of a method for managing design changes between multiple systems provided in an embodiment of the present application.

[0030] Figure 6 This is the fifth flow chart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0031] Figure 7 It is a structural diagram of the engineering document management system provided in the embodiment of the present application.

[0032] Figure 8It is a structural diagram of the product life cycle management system provided in an embodiment of the present application.

[0033] Fig. 9 It is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The following is a further detailed description of the implementation of the present application in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present application but cannot be used to limit the scope of the present application.

[0035] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiments of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0036] Based on relevant technologies, for example, in electronic hardware projects, the problem that the corresponding product drawing changes after the production management system BOM is changed cannot achieve process synchronization or process linkage, the embodiments of the present application provide a design change management method, device, equipment, storage medium and program product, thereby achieving synchronization between BOM and drawings, ensuring the consistency and reliability of product quality, and providing a guarantee for the development and use of subsequent products.

[0037] This application embodiment provides a method for managing design changes between multiple systems. Figure 1 , Figure 1 It is one of the flow charts of the method for managing design changes between multiple systems provided in the embodiment of the present application. In this embodiment, the method for managing design changes between multiple systems may include steps 110 to 150, and each step is specifically as follows:

[0038] Step 110: The engineering document management system encodes the archived drawing engineering files to obtain first encoding information, and sends the first encoding information to the product lifecycle management system.

[0039] Step 120: The product lifecycle management system compares the first coding information with the latest coding information stored in the product lifecycle management system.

[0040] Step 130: If the first coding information and the latest coding information are inconsistent, the product lifecycle management system generates design change information and sends the design change information to the engineering document management system.

[0041] Step 140: The engineering document management system determines changes to the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file based on the design change information.

[0042] Step 150: If the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file based on the design change information.

[0043] This embodiment is applied to an engineering document management (EDM) system and a product lifecycle management (PLM) system.

[0044] Among them, the PLM system is responsible for proofreading the coding information, and the EDM system is responsible for proofreading the bill of materials. Through a multi-level judgment method, the linkage change and synchronous management between the bill of materials in the PLM system and the drawing engineering files in the EDM are realized, and the linkage and synchronization of design changes between multiple systems are maintained, thereby improving quality consistency and product reliability.

[0045] In this embodiment, the drawing engineering files can be uniformly managed and stored offline through the EDM system.

[0046] Drawing engineering files refer to various drawings and documents used to record and communicate the design, construction and maintenance details of engineering projects. Optionally, drawing engineering files include but are not limited to PCB engineering files, CAD engineering files and other engineering drawing files.

[0047] When the EDM system archives the drawing engineering files, it will fill in the codes for the archived drawing engineering files, thereby obtaining the first coding information corresponding to the archived drawing engineering files.

[0048] The first coding information may include at least one component code, which can ensure the accuracy and efficiency of production and management processes at various stages during electronic design, manufacturing and assembly.

[0049] Exemplarily, when the drawing engineering file is a PCB engineering file, the component code may include a PCB code, a PCBA code corresponding to an assembly variable, an SMT component code corresponding to the PCBA, and an AI / RI component code corresponding to the PCBA.

[0050] Specifically, PCB (Printed Circuit Board) code refers to the code or identifier on a printed circuit board that is used to uniquely identify the circuit board, and is used to track, manage and distinguish different versions or models of PCBs.

[0051] PCBA (Printed Circuit Board Assembly) code refers to the unique code of the printed circuit board assembly, which includes the PCB and all components soldered on it to form the final circuit board assembly product.

[0052] SMT (Surface-Mount Technology) component codes are unique codes for surface mount technology (SMT) components. SMT components refer to electronic components that can be directly soldered on the surface of a circuit board.

[0053] AI / RI (Automatic Insertion / Robot Insertion) component codes refer to component codes for automatic insertion and robot insertion, respectively. AI refers to components inserted by automated equipment, and RI refers to components inserted by robots.

[0054] The EDM system obtains the first coding information and sends the first coding information to the PLM system to notify the PLM system that a new drawing engineering file is archived.

[0055] Optionally, the EDM system may push the first coding information to the PLM system in real time or regularly according to a set time period. The time period may be specifically set according to actual conditions, such as daily.

[0056] After receiving the first coding information, the PLM system first stores the first coding information, and then searches for the latest coding information corresponding to the first coding information from its own storage for comparison. If there is a difference between the first coding information and the latest coding information, the design change information is generated.

[0057] It should be noted that the correspondence between the first coding information and the latest coding information is determined according to the coding rule.

[0058] Exemplarily, the coding rule may be to assign coding characters to the drawing engineering file, and then a corresponding relationship may be set between coding information having at least some / specific coding characters that are the same.

[0059] Exemplarily, the coding rules include assigning coding numbers and version numbers to drawing engineering files. The first coding information and the latest coding information both include coding numbers and version numbers. The coding information with the same coding numbers can be set as corresponding coding relationships to determine whether there are differences in version numbers between the coding information with the same coding numbers.

[0060] If it is found that the version of a certain code stored in the EDM system is inconsistent with the latest version of the PLM system, the code will be recorded and the design change information will be generated. For example, the PCB code 171203202000011 is stored in the EDM system as V1.0, while the current version of this code in the PLM system is V1.1. The two are inconsistent, and the PLM system generates design change information.

[0061] In some embodiments, if the encoding information corresponding to the encoding of the first encoding information cannot be retrieved from its own storage, the first encoding information is stored as a new encoding.

[0062] Based on the design change information pushed back by the PLM system, the EDM system further searches the BOM status of the two systems to determine whether the BOM of the correspondingly coded PCB engineering files in the PLM system and the EDM system has changed.

[0063] If the BOM of the PLM system has not changed, the inconsistency of the coding information in the PLM system is caused by other non-BOM changes, such as component name description modification, version upgrade, etc. At this time, the offline drawing engineering files do not need to be modified.

[0064] For example, when it is found that the inconsistency of the coding information in the PLM system is caused by other reasons other than BOM changes, the coding information of this situation can also be marked to prevent it from happening again during the next retrieval.

[0065] If the BOM of the PLM system changes, the drawing engineering files managed by the EDM need to be changed synchronously. Specifically, the EDM system generates change tasks for the drawing engineering files based on the design change information to complete the synchronous change of the drawing engineering files in the offline EDM system.

[0066] In some embodiments, the change task may be completed by a user, or may be synchronized automatically by the EDM system.

[0067] It should be noted that since the latest data is stored in the PLM system, when the EDM system determines whether the bill of materials has changed, it checks whether the bill of materials in the PLM system has changed compared with the bill of materials in the drawing engineering file. If the bill of materials in the PLM system has changed, the EDM system generates a change task for the drawing engineering file based on the design change information issued by the PLM system.

[0068] In summary, the embodiment of the present application provides a method for managing design changes between multiple systems in an engineering document management system. The engineering document management system can encode and manage archived drawing engineering files, and send the first encoding information to the product lifecycle management system for information synchronization; the product lifecycle management system can compare the first encoding information with the latest encoding information stored in itself, and generate design change information when a difference is found and send it to the engineering document management system for synchronization; the engineering document management system can further verify the changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file based on the design change information, and generate a change task when it is determined that the bill of materials has changed, and realize the linkage change and synchronous management between the bill of materials in the product lifecycle management system and the drawing engineering file in the engineering document management system through a multi-level judgment method, maintain the linkage synchronization of design changes between multiple systems, thereby improving quality consistency and product reliability.

[0069] Based on any of the above embodiments, the step of determining, by the engineering document management system, changes to the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file according to the design change information may specifically include:

[0070] The engineering document management system reads the first bill of materials corresponding to the latest code from the product life cycle management system according to the design change information; the engineering document management system obtains the second bill of materials corresponding to the first code from the drawing engineering files stored in itself according to the design change information; the engineering document management system determines whether the bill of materials has changed according to the difference between the first bill of materials and the second bill of materials.

[0071] In this embodiment, the EDM system can read the first bill of materials corresponding to the latest code from the PLM system according to the design change information, and obtain the second bill of materials corresponding to the first code from the drawing engineering files stored in itself, and determine the change status through analysis of the first bill of materials and the second bill of materials.

[0072] Based on any of the above embodiments, the step of encoding and archiving the drawing engineering file in the engineering document management system to obtain the first encoding information may specifically include:

[0073] The engineering document management system determines the coding for the components in the drawing engineering files to be archived and obtains the first coding information; wherein the first coding information includes at least one component coding; the engineering document management system verifies the legality of the component coding according to the coding rules issued by the product life cycle management system; after the legality verification is passed, the engineering document management system stores and archives the drawing engineering files to be archived and the corresponding first coding information.

[0074] In this embodiment, the EDM system can determine the coding of the components in the drawing engineering file to be archived according to the coding rules issued by the PLM system, and use the coding rules to perform a legality check after obtaining the first coding information to further ensure the accuracy of the coding.

[0075] In some other embodiments, the step of verifying the legality of the component code may also be performed by the PLM system.

[0076] Based on any of the above embodiments, if the bill of materials changes, the steps after the engineering document management system generates a change task for the drawing engineering file according to the design change information may specifically include:

[0077] If only one component code under the same PCB project undergoes a design change in the product lifecycle management system, the engineering document management system will push the change task to the creator of the design change; if at least two component codes under the same PCB project undergo a design change in the product lifecycle management system, the engineering document management system will push the change task to the creator with the latest design change creation date.

[0078] In this embodiment, when the change task needs to be executed by the user, the change task needs to be pushed to the corresponding user for completion.

[0079] Specifically, when only one component code under the same PCB project undergoes a design change in the product lifecycle management system, the change task will be pushed to the creator of the design change to remind the creator of the design change to synchronously modify the corresponding drawing project files; if at least two component codes under the same PCB project undergo a design change in the product lifecycle management system, the change task will be pushed to the creator with the latest design change creation date in the order of creation date to complete the synchronous modification of the corresponding drawing project files.

[0080] Based on any of the above embodiments, the steps after the engineering document management system generates a change task for the drawing engineering file according to the design change information may further include:

[0081] The engineering document management system executes the change task to complete the change of drawing engineering files and re-archives the changed drawing engineering files.

[0082] In this embodiment, when a change task is executed to complete the change of the drawing engineering file, the changed drawing engineering file can be re-archived into the warehouse according to the above process. In this way, the above method can be used to synchronize the BOM data in the PLM system and the drawing data in the EDM system and interconnect the processes, thereby realizing the linkage and consistency of the BOM changes in the PLM system and the drawing changes in the EDM system.

[0083] Based on any of the above embodiments, the first coding information includes the first component code and the first version information; the latest coding information includes the latest component code and the latest version information; and the step of comparing the product lifecycle management system with the latest coding information stored in itself according to the first coding information may specifically include:

[0084] The product life cycle management system matches the first component code with the latest component code; if the first component code and the latest component code match, the product life cycle management system matches the first version information with the latest version information; if the first version information and the latest version information do not match, the product life cycle management system determines that the first coding information and the latest coding information are inconsistent.

[0085] In this embodiment, the first coding information may include the first component code and the first version information; the latest coding information may include the latest component code and the latest version information. The component code information is used to match the corresponding relationship, and the version information is used to check whether there is a difference between the corresponding coding information. Therefore, the first component code and the latest component code in the PLM system are first matched one by one until the corresponding latest coding information is determined, and then the first version information is matched with the latest version information to determine whether there is a difference in the component codes between the two systems.

[0086] Based on any of the above embodiments, the steps after the product lifecycle management system generates the design change information and sends the design change information to the engineering document management system may further include:

[0087] The product lifecycle management system allows the engineering document management system to read the first bill of materials corresponding to the latest code stored in itself according to the design change information.

[0088] In this embodiment, the PLM system may also allow access to the EDM system, retrieve the first bill of materials corresponding to the latest code according to the design change information, and provide data support for subsequent bill of materials comparison of the EDM system.

[0089] Based on any of the above embodiments, the steps before the product lifecycle management system compares the difference between the first coding information and the latest coding information stored in the product lifecycle management system may further include:

[0090] The product lifecycle management system obtains the first coding information of the drawing engineering file to be archived in the engineering document management system; wherein the first coding information includes at least one component code; the product lifecycle management system verifies the legality of the component code according to the coding rules, and returns the verification result of the legality to the engineering document management system.

[0091] In this embodiment, the PLM system can send the coding rules for archiving drawing engineering files to the EDM system, so that the EDM system can encode the drawing engineering files according to the coding rules. In addition, the PLM system can also verify the legitimacy of the component coding in the first coding information of the drawing engineering files to be archived, and only the drawing engineering files that pass the verification are allowed to be archived.

[0092] It should be noted that if the legality check fails, it may be caused by the failure to update the coding rules. At this time, the EDM system can request the PLM system to issue the latest coding rules, and the EDM system will re-encode the archived drawing engineering files according to the latest coding rules.

[0093] See also Figure 2 , Figure 2 This is the second flowchart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0094] In this embodiment, the method for managing design changes between multiple systems is applied to an engineering document management system. The method for managing design changes between multiple systems may include steps 210 to 250, each of which is specifically as follows:

[0095] Step 210: Encode the archived drawing engineering file to obtain first encoding information.

[0096] Step 220: Send the first coding information to the product lifecycle management system, so that the product lifecycle management system compares the first coding information with the latest coding information stored in the product lifecycle management system.

[0097] Step 230: If there is a difference between the first coding information and the latest coding information, then receiving the design change information sent by the product lifecycle management system.

[0098] Step 240: Based on the design change information, determine the changes to the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file.

[0099] Step 250: If the bill of materials changes, a change task is generated for the drawing engineering file based on the design change information.

[0100] In this embodiment, the engineering document management system can check the changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file according to the design change information sent by the product lifecycle management system. When the bill of materials changes, it can be discovered in time, so as to generate change tasks for the drawing engineering file, realize the linkage and synchronization of design changes between multiple systems, and improve the consistency of quality and the reliability of products.

[0101] See also Figure 3 , Figure 3 This is the third flow chart of the method for managing design changes between multiple systems provided in an embodiment of the present application. The method for managing design changes between multiple systems is applied to a product lifecycle management system. In this embodiment, the method for managing design changes between multiple systems may include steps 310 to 320, and each step is specifically as follows:

[0102] Step 310: Compare the first coding information pushed by the engineering document management system with the latest coding information stored in the engineering document management system.

[0103] Step 320: If the first coding information and the latest coding information are inconsistent, then generate design change information, and send the design change information to the engineering document management system, so that the engineering document management system determines the changes in the bill of materials of the drawing engineering file according to the design change information.

[0104] In this embodiment, the product lifecycle management system is mainly responsible for comparing the first coding information with the latest coding information, and generating design change information when the first coding information and the latest coding information are inconsistent. The design change information can drive the engineering document management system to further compare the bill of materials to determine whether it is necessary to change the drawing engineering file. For the specific synchronization management process, please refer to the above-mentioned management method for design changes between multiple systems.

[0105] Through the above method, the embodiment of the present application can synchronously manage the coding information in the engineering document management system and the product life cycle management system, and timely discover the unupdated coding information in the engineering document management system, thereby generating design change information, realizing the linkage and synchronization of design changes between multiple systems, and improving the consistency of quality and the reliability of products.

[0106] See also Figure 4 , Figure 4 This is the fourth flow chart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0107] In this embodiment, the EDM system pushes the component code to the PLM system, and the PLM system determines whether there is a version update for the component code. If not, the process ends; if so, the latest released ECO corresponding to the component version change is further retrieved.

[0108] If the latest published ECO corresponding to the component version change cannot be retrieved, the process ends; if the latest published ECO corresponding to the component version change can be retrieved, the PLM system further obtains the ECO order number, creator, change details, etc., and generates design change information based on this information, and pushes this design change information to the EDM system to obtain the corresponding components and the engineering files to which the components belong. The EDM system triggers the PCB engineering change process, generates a change task, and pushes the process carrying the change task to the creator of the ECO.

[0109] See also Figure 5-Figure 6 , Figure 5 is a system interaction diagram of a method for managing design changes between multiple systems provided in an embodiment of the present application, Figure 6 This is the fifth flow chart of the method for managing design changes between multiple systems provided in the embodiment of the present application.

[0110] In this embodiment, the interactive entities involved include drawing software, a PLM system, and an EDM system.

[0111] In the drawing software, you can complete the PCB project file closing and execute PCB project file changes and re-enter the warehouse.

[0112] In the PLM system, coding rules for PLM component coding and versions can be provided to complete coding verification and version storage; the data pushed by EDM can also be compared with the latest status of the PLM component coding. When a version difference is found, the latest ECO information of the component (ECO details, creator, etc.) is pushed to the EDM system; and the EDM system is allowed to read the BOM of the PCBA through the interface.

[0113] In the EDM system, the PCB files that have been put into the warehouse or re-put into the warehouse can be stored, and the PLM component code and version can be filled in. When the change information of the PLM system is received, the PCBA to which the changed component belongs can be retrieved. When the comparison result of the BOM of the PCBA and the latest BOM in the PLM system is found to be different, the affected PCB engineering files are retrieved, and the corresponding PCBA BOM is read from the PLM system. The PCB engineering file triggers the change process, and the process is pushed to the creator of the ECO, so that the ECO creator can execute the PCB engineering file change through the drawing software and re-enter the warehouse.

[0114] In this embodiment, the management method of design changes between multiple systems is described by taking PCB engineering file drawings as an example. The EDM system pushes the PCB code, PCBA code, SMT component code, AI / RI component code and version stored in the PCB engineering file to the PLM system every day. After receiving and comparing, the PLM system returns the ECO of the inconsistent version component code to the EDM system. The EDM system automatically generates the PCB engineering file change process based on the returned ECO and code, and pushes the process to the creator of the ECO, thereby realizing the linkage and consistency of BOM changes and drawing changes.

[0115] The specific process of this embodiment includes:

[0116] After the hardware project is completed, the PCB engineering files are prepared for storage. In the electronic design software, you can use EDA tools to upload the project. The coding information that needs to be filled in when uploading the PCB engineering files includes PCB coding, PCBA coding, SMT component coding and AI / RI component coding (hereinafter collectively referred to as "component coding").

[0117] While the coding information is being filled in, the EDM system will query the legality of the coding from the PLM system through the interface. If it is an illegal coding, an error message will be given and the component can be re-entered into the warehouse only after the component coding is confirmed.

[0118] After the PCB project file is archived in the EDM system, the above code filled in the PCB project will read the version information of the code from the PLM system through the interface and write it back to the EDM system.

[0119] The EDM system pushes all PCB codes, PCBA codes, SMT component codes, AI / RI component codes and versions stored in all PCB projects to the PLM system through the interface every day.

[0120] After the PLM system receives the code and version information pushed by the EDM system, it will first store it temporarily and then compare it with the latest version of the corresponding code in the PLM system.

[0121] If it is found that there is no difference in the versions of these components, the process ends and these component codes do not proceed to the following steps. If it is found that the version of a code stored in the EDM system is inconsistent with the latest version of the PLM system, the code is recorded and the subsequent steps are continued.

[0122] After querying and comparing, the PLM system screens out component codes with version differences. For these component codes, query the latest ECO in their historical change records, obtain the details of the latest ECO, and record the creator, creation time, change details, and other information of the ECO.

[0123] After the PLM system searches for all component codes with version differences, it pushes the creator, creation time, change details, and other information of the latest ECO of each component code to the EDM system through the interface. After receiving it, the EDM system temporarily stores this information with the component code as an identifier.

[0124] The EDM system retrieves the PCBA to which the component code belongs based on the component code and ECO information pushed back by the PLM system. The affected PCBA component BOM is automatically compared with the PLM BOM through the interface:

[0125] (1) If the comparison results are different, it means that the BOM of the PLM system has changed, then the engineering files corresponding to the PCBA also need to be changed, and continue to perform subsequent steps.

[0126] (2) If there is no difference in the comparison results, it means that the BOM of the PLM system has not changed, and the PCBA component code version upgrade may be due to other reasons, such as component name description modification. At this point, the process can be ended and these component codes will not proceed to the next step.

[0127] According to the above comparison results (1), the EDM system records all PCBA components and then searches for which PCB engineering files they belong to. After locating the PCB engineering file, the EDM system searches the engineering file to see whether there are multiple PCBA changes involved, and automatically triggers the PCB engineering file change process.

[0128] There are two situations in which the change process of PCB engineering files can be pushed:

[0129] (1) The EDM system analyzes that if only one component code under the same PCB project has a version change in the PLM system, the change process of the PCB project file is directly pushed to the ECO creator of the component in the PLM system.

[0130] (2) The EDM system analyzes that if multiple component codes under the same PCB project have undergone version changes in the PLM system, the EDM system compares the ECOs of these component codes in the PLM and captures the one with the latest creation date. The change process of the PCB project file is pushed to the creator of the ECO with the latest creation date.

[0131] The ECO creator re-enters the PCB engineering file after making changes, and the components under the PCB engineering file are synchronized with the latest version of PLM and stored in the EDM system. So far, the entire process has been completed.

[0132] Through the above method, this embodiment can realize the data synchronization and process interconnection of BOM data and EDM drawings in the PLM system, thereby realizing the linkage and consistency of BOM changes and EDM drawing changes in the PLM system. When the PCB engineering file drawings of this embodiment are put into the warehouse, it is necessary to fill in the PCB code, PCBA code, SMT component code, AI / RI component code and other information. After filling in, the software automatically verifies the legality of the code with PLM through the interface. After the verification is successful, the component code and version will be stored; all component codes and version information stored in the EDM system will be pushed to the PLM system through the interface every day. After the PLM system receives it, it will be compared with the latest code and version. If the version of the same code is inconsistent, the code will be recorded, and the historical record of the code will be queried, and the latest ECO information (change content, change creator, etc.) will be captured in the historical record. Then the component code and ECO information are returned to the EDM system through the interface. After the EDM system receives the component code and ECO information returned by the PLM system, it will locate the engineering file to which the component belongs and record it. After all component codes have been queried, the EDM system automatically generates a PCB engineering file change process based on the located engineering file, and pushes the PCB engineering file change process to the ECO creator of the corresponding component code based on the ECO information returned by the PLM system.

[0133] On the other hand, an embodiment of the present application further provides a management device for design changes between multiple systems. The management device for design changes between multiple systems described below and the management method for design changes between multiple systems described above can refer to each other.

[0134] Among them, the management device for design changes between multiple systems may include an engineering document management system and a product life cycle management system.

[0135] See also Figure 7-Figure 8 , Figure 7 is a schematic diagram of the structure of the engineering document management system provided in the embodiment of the present application, Figure 8 It is a structural diagram of the product life cycle management system provided in an embodiment of the present application.

[0136] In this embodiment, the engineering document management system may include a first coding information module 710 , a first sending module 720 , a first receiving module 730 , a bill of materials comparison module 740 and a change task module 750 .

[0137] The first coding information module 710 is used to encode the archived drawing engineering files to obtain the first coding information.

[0138] The first sending module 720 is used to send the first coding information to the product lifecycle management system, so that the product lifecycle management system compares the difference between the first coding information and the latest coding information stored in the product lifecycle management system.

[0139] The first receiving module 730 is configured to receive the design change information sent by the product lifecycle management system if there is a difference between the first coding information and the latest coding information.

[0140] The BOM comparison module 740 is used to determine the changes of the BOM in the product lifecycle management system and the BOM in the drawing engineering file according to the design change information.

[0141] The change task module 750 is used to generate a change task for the drawing engineering file according to the design change information if the bill of materials changes.

[0142] The product lifecycle management system may include a coding information comparison module 810 and a design change information module 820 .

[0143] The coding information comparison module 810 is used to compare the first coding information pushed by the engineering document management system with the latest coding information stored in the management system.

[0144] The design change information module 820 is used to generate design change information if the first coding information and the latest coding information are inconsistent, and send the design change information to the engineering document management system so that the engineering document management system can determine the changes in the bill of materials of the drawing engineering file based on the design change information.

[0145] Based on any of the above embodiments, the bill of materials comparison module 740 can be specifically used to: read the first bill of materials corresponding to the latest code from the product lifecycle management system according to the design change information; obtain the second bill of materials corresponding to the first code from the drawing engineering file stored in itself according to the design change information; and determine whether the bill of materials has changed based on the difference between the first bill of materials and the second bill of materials.

[0146] Based on any of the above embodiments, the first coding information module 710 can be specifically used to: determine the coding for the components in the drawing engineering file to be archived to obtain the first coding information; wherein the first coding information includes at least one component code; verify the legality of the component coding according to the coding rules issued by the product life cycle management system; after the legality verification is passed, the drawing engineering file to be archived and the corresponding first coding information are stored and archived.

[0147] Based on any of the above embodiments, the engineering document management system may further include a task push module, which may be specifically used for: if only one component code under the same PCB project undergoes a design change in the product lifecycle management system, the change task will be pushed to the creator of the design change; if at least two component codes under the same PCB project undergo a design change in the product lifecycle management system, the change task will be pushed to the creator with the latest design change creation date.

[0148] Based on any of the above embodiments, the engineering document management system may further include a re-filing module, which may be specifically used to: execute change tasks to complete the change of drawing engineering files, and re-file the changed drawing engineering files.

[0149] Based on any of the above embodiments, the first coding information includes a first component code and a first version information; the latest coding information includes a latest component code and a latest version information; the coding information comparison module 810 can be specifically used to: match the first component code with the latest component code; if the first component code and the latest component code match, then match the first version information with the latest version information; if the first version information and the latest version information do not match, then determine that the first coding information and the latest coding information are inconsistent.

[0150] Based on any of the above embodiments, the product lifecycle management system may further include a storage module, which may be specifically used to allow the engineering document management system to read the first bill of materials corresponding to the latest code stored in itself according to the design change information.

[0151] Based on any of the above embodiments, the product lifecycle management system may further include a coding verification module, which may be specifically used to: obtain the first coding information of the drawing engineering file to be archived in the engineering document management system; wherein the first coding information includes at least one component code; verify the legitimacy of the component code according to the coding rules, and return the legitimacy verification result to the engineering document management system.

[0152] In another aspect, the present application also provides an electronic device. Fig. 9 , Fig. 9 9 is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present application, and the electronic device may include: a processor (processor) 910, a communication interface (Communications Interface) 920, a memory (memory) 930 and a communication bus 940, wherein the processor 910, the communication interface 920, and the memory 930 communicate with each other through the communication bus 940. The processor 910 can call the logic instructions in the memory 930 to execute the following method:

[0153] The engineering document management system encodes and archives the drawing engineering files, obtains the first coding information, and sends the first coding information to the product life cycle management system; the product life cycle management system compares the differences with the latest coding information stored in itself based on the first coding information; if the first coding information and the latest coding information are inconsistent, the product life cycle management system generates design change information and sends the design change information to the engineering document management system; the engineering document management system determines the changes in the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file based on the design change information; if the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file based on the design change information.

[0154] In addition, the logic instructions in the above-mentioned memory 930 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0155] In another aspect, an embodiment of the present application discloses a computer program product, wherein the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, wherein the computer program includes program instructions. When the computer program instructions are executed by a computer, the computer can perform the methods provided by the above-mentioned method embodiments, for example, including:

[0156] The engineering document management system encodes and archives the drawing engineering files, obtains the first coding information, and sends the first coding information to the product life cycle management system; the product life cycle management system compares the differences with the latest coding information stored in itself based on the first coding information; if the first coding information and the latest coding information are inconsistent, the product life cycle management system generates design change information and sends the design change information to the engineering document management system; the engineering document management system determines the changes in the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file based on the design change information; if the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file based on the design change information.

[0157] In another aspect, an embodiment of the present application further provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method provided in each of the above embodiments is implemented, for example, including:

[0158] The engineering document management system encodes and archives the drawing engineering files, obtains the first coding information, and sends the first coding information to the product life cycle management system; the product life cycle management system compares the differences with the latest coding information stored in itself based on the first coding information; if the first coding information and the latest coding information are inconsistent, the product life cycle management system generates design change information and sends the design change information to the engineering document management system; the engineering document management system determines the changes in the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file based on the design change information; if the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file based on the design change information.

[0159] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0160] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiment.

[0161] Finally, it should be noted that the above implementation modes are only used to illustrate the present application, rather than to limit the present application. Although the present application is described in detail with reference to the embodiments, a person skilled in the art should understand that various combinations, modifications or equivalent replacements of the technical solutions of the present application do not depart from the spirit and scope of the technical solutions of the present application, and should be included in the protection scope of the present application.

Claims

1. A method for managing design changes between multiple systems, characterized in that: include: The engineering document management system encodes the drawing engineering file archived, obtains first encoding information, and sends the first encoding information to the product life cycle management system; The product lifecycle management system compares the first coding information with the latest coding information stored in the product lifecycle management system; If the first coding information is inconsistent with the latest coding information, the product lifecycle management system generates design change information and sends the design change information to the engineering document management system; The engineering document management system determines changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file according to the design change information; If the bill of materials changes, the engineering document management system generates a change task for the drawing engineering file according to the design change information; The first coding information includes a first component code and a first version information; the latest coding information includes a latest component code and a latest version information; the component code is used to match the corresponding relationship, and the version information is used to check whether there is a difference between the corresponding coding information; If the first coding information is consistent with the latest coding information, the process ends; If the bill of materials does not change, the drawing engineering file will not be modified.

2. The method for managing design changes between multiple systems according to claim 1, characterized in that: The engineering document management system determines changes in the bill of materials in the product lifecycle management system and the bill of materials in the drawing engineering file according to the design change information, including: The engineering document management system reads a first bill of materials corresponding to the latest code from the product lifecycle management system according to the design change information; The engineering document management system obtains a second bill of materials corresponding to the first code from the drawing engineering file stored in the engineering document management system according to the design change information; The engineering document management system determines whether the bill of materials has been changed based on the difference between the first bill of materials and the second bill of materials.

3. The method for managing design changes between multiple systems according to claim 1 or 2, characterized in that: The engineering document management system encodes and archives the drawing engineering files to obtain first encoding information, including: The engineering document management system determines the coding for the components in the drawing engineering file to be archived, and obtains the first coding information; wherein the first coding information includes at least one component coding; The engineering document management system verifies the legitimacy of the component coding according to the coding rules issued by the product lifecycle management system; After the legality check is passed, the engineering document management system stores and archives the drawing engineering file to be archived and the corresponding first coding information.

4. The method for managing design changes between multiple systems according to claim 1 or 2, characterized in that: If the bill of materials is changed, after the engineering document management system generates a change task for the drawing engineering file according to the design change information, it also includes: If only one component code under the same PCB project undergoes a design change in the product lifecycle management system, the engineering document management system pushes the change task to the creator of the design change; If at least two component codes under the same PCB project have design changes in the product lifecycle management system, the engineering document management system pushes the change task to the creator with the latest design change creation date.

5. The method for managing design changes between multiple systems according to claim 1 or 2, characterized in that: After the engineering document management system generates a change task for the drawing engineering file according to the design change information, the engineering document management system further includes: The engineering document management system executes the change task to complete the change of the drawing engineering file and re-archives the changed drawing engineering file.

6. The method for managing design changes between multiple systems according to claim 1, characterized in that: The product lifecycle management system compares the first coding information with the latest coding information stored in the product lifecycle management system, including: The product lifecycle management system matches the first component code with the latest component code; if the first component code matches the latest component code, the product lifecycle management system matches the first version information with the latest version information; If the first version information does not match the latest version information, the product lifecycle management system determines that the first coding information is inconsistent with the latest coding information.

7. The method for managing design changes between multiple systems according to claim 1 or 2, characterized in that: After the product lifecycle management system generates design change information and sends the design change information to the engineering document management system, it also includes: The product lifecycle management system allows the engineering document management system to read the first bill of materials corresponding to the latest code stored in itself according to the design change information.

8. The method for managing design changes between multiple systems according to claim 1 or 2, characterized in that: Before the product lifecycle management system compares the difference between the first coding information and the latest coding information stored in the product lifecycle management system, the product lifecycle management system further includes: The product lifecycle management system obtains first coding information of the drawing engineering file to be archived in the engineering document management system; wherein the first coding information includes at least one component code; The product lifecycle management system verifies the legality of the component coding according to the coding rules, and returns the verification result of the legality to the engineering document management system.

9. A management device for design changes between multiple systems, characterized in that: Including engineering document management system and product life cycle management system; The engineering document management system comprises: A first coding information module is used to encode and archive the drawing engineering file to obtain first coding information; A first sending module, used for sending the first coding information to a product life cycle management system, so that the product life cycle management system compares the first coding information with the latest coding information stored in the product life cycle management system; A first receiving module, configured to receive design change information sent by the product lifecycle management system if there is a difference between the first coding information and the latest coding information; A bill of materials comparison module, used to determine the change status of the bill of materials in the product life cycle management system and the bill of materials in the drawing engineering file according to the design change information; A change task module, used for generating a change task for the drawing engineering file according to the design change information if the bill of materials changes; The product life cycle management system includes: A coding information comparison module, used to compare the first coding information pushed by the engineering document management system with the latest coding information stored in the management system; A design change information module, for generating design change information if the first coding information and the latest coding information are inconsistent, and sending the design change information to the engineering document management system, so that the engineering document management system determines the change of the bill of materials of the drawing engineering file according to the design change information; The first coding information includes a first component code and a first version information; the latest coding information includes a latest component code and a latest version information; the component code is used to match the corresponding relationship, and the version information is used to check whether there is a difference between the corresponding coding information; The coding information comparison module is further used to: if the first coding information is consistent with the latest coding information, then end the process; The BOM comparison module is also used for: if the BOM does not change, then the drawing engineering file will not be modified.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for managing design changes among multiple systems as claimed in any one of claims 1 to 8 is implemented.

11. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for managing design changes among multiple systems as claimed in any one of claims 1 to 8 is implemented.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method for managing design changes among multiple systems as claimed in any one of claims 1 to 8 is implemented.

Images