Wire harness drawing version management method, system, equipment and medium

Abstract

The invention provides a wire harness drawing version management method, system and device and a medium, and belongs to the technical field of production and processing, attribute data of wire harness elements of a new version are acquired, and reference identifiers are allocated to different wire harness elements; comparing the attribute data of the wire harness element of the new version with the pre-stored attribute data of the wire harness element of the old version, and determining the change type of the change event by matching the reference identifier; performing grading processing on the change event according to a preset rule, and generating a corresponding engineering change instruction according to the change grade; and the changed content is synchronized to the corresponding position of the process drawing, and the existing manual annotation is reserved. And intelligent synchronization of the changed content and the process drawing is realized.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of production and processing, and particularly relates to a wiring harness drawing version management method, system, device and medium. BACKGROUND

[0002] With the increasing complexity of automotive electronic and electrical architecture, commercial vehicle wiring harness design presents the characteristics of multiple configurations and high change frequency. As the neural network of vehicle electrical signal and power transmission, the accuracy of wiring harness design and the efficiency of version management are directly related to the development cycle and manufacturing quality of the whole vehicle. In the process of vehicle iteration, configuration derivation or problem rectification, the change management of wiring harness drawings becomes a key link connecting design, process and production, and the automation and intelligence level needs to be improved.

[0003] In the existing wiring harness drawing version management, there are problems such as inaccurate change identification, low change event processing efficiency, and inaccurate synchronization of design changes to process drawings.

[0004] Therefore, the application provides a wiring harness drawing version management method, system, device and medium. SUMMARY

[0005] The application provides a wiring harness drawing version management method, system, device and medium to at least solve the problems of inaccurate change identification, missing classification and low transmission efficiency in the existing wiring harness drawing version management.

[0006] In a first aspect, the application provides a wiring harness drawing version management method, which comprises: S1: acquiring attribute data of a new version of wiring harness elements, the wiring harness elements including wires, branches and connectors; S2: assigning reference identifiers to different wiring harness elements, wherein system unique line numbers are assigned to wires, and globally unique identifiers (GIDs) are assigned to branches and connectors; S3: comparing the attribute data of the new version of wiring harness elements with pre-stored attribute data of the old version of wiring harness elements, determining the change type of the change event by matching the reference identifiers, the change type including at least one of the following events: addition, deletion and attribute update; S4: classifying the change event according to a preset rule, and dividing the change event into three change levels of LEVEL1 change, LEVEL2 change and LEVEL3 change; S5: generating corresponding engineering change instructions according to the change level; S6: synchronizing the change content to the corresponding position of the process drawing, and retaining the existing manual annotations.

[0007] Further, in step S2, the format of the global unique identifier GID is: [element type code] [version number] [hash value]; Wherein, the hash value is generated based on the element coordinates, the configuration item to which it belongs, and the parent node through MD5 algorithm. When the branch position moves a distance d≥5mm, the hash value is recalculated and a new global unique identifier GID is generated.

[0008] Further, in step S3, the change type is determined by matching the reference identifier, specifically including: When the wire gauge is the same, it is determined as the same wire, and the length and color attribute changes are compared; When the wire gauge changes, record the old wire gauge wire deletion event and the new wire gauge wire addition event; When the global unique identifier GID exists but the attribute changes, it is recorded as an attribute update event; When the global unique identifier GID does not exist in the new version, it is recorded as a deletion event; When a new global unique identifier GID appears, it is recorded as an addition event.

[0009] Further, in step S4, the LEVEL1 changes include: connector code change, wire color change; The LEVEL2 changes include: wire length change of more than 10%, branch covering form change; The LEVEL3 changes include: global unique identifier GID addition, global unique identifier GID deletion, wire gauge change.

[0010] Further, before step S6, it also includes: When the global unique identifier GID of the connector does not change but the model changes, the original terminal crimping process parameter library is automatically searched; Based on the cross-sectional characteristics and material hardness parameters of the new model terminal, the closest existing process parameters are matched.

[0011] Further, in step S6, the drawing synchronization includes: Locate the change area on the process drawing by matching the global unique identifier GID, with a positioning accuracy error of not more than ±0.5mm; Retain the note information added by the process personnel; Automatically add version identifiers after the drawing is updated.

[0012] Further, the method further includes a version conflict detection step: Iterate through all historical versions to detect attribute conflicts of the same global unique identifier GID in different versions; When a conflict is detected, arbitration is performed according to the version timestamp and the change level, and the result of the highest level change is retained.

[0013] In a second aspect, the embodiments of the present application further provide a system applied to the harness drawing version management method as described in the above aspects, and the system comprises: The data acquisition module is configured to acquire attribute data of the harness elements of the new version, the harness elements comprising wires, branches and connectors; The identifier allocation module is configured to allocate reference identifiers to different harness elements, wherein a system unique wire number is allocated to the wires, and a globally unique identifier (GID) is allocated to the branches and the connectors; The change identification module is configured to compare the attribute data of the harness elements of the new version with the attribute data of the harness elements of the pre-stored old version, determine a change type of the change event by matching the reference identifiers, and the change type comprises at least one of the following events: addition, deletion and attribute update; The hierarchical processing module is configured to perform hierarchical processing on the change event according to a preset rule, and divide the change event into three change levels: LEVEL1 change, LEVEL2 change and LEVEL3 change; The instruction generation module is configured to generate corresponding engineering change instructions according to the change levels; The drawing synchronization module is configured to synchronize the change content to a corresponding position of the process drawing, and retain the existing manual annotations.

[0014] In a third aspect, an electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the harness drawing version management method as described in the above aspects when executing the program.

[0015] In a fourth aspect, a storage medium stores a computer program, and the computer program is executable on a processor to implement the steps of the harness drawing version management method as described in the above aspects.

[0016] As can be seen from the above technical solutions, the present application has the following advantages: In the harness drawing version management method provided by the present application, the system unique wire number is allocated to the wires, and the globally unique identifier (GID) is allocated to the branches and the connectors, so that the accurate classification of the change event is realized, the attribute update of the same wire can be accurately determined when the wire number is unchanged, the false addition and deletion events caused by the wire deletion and reconstruction operation are avoided, the accuracy of the change identification is significantly improved, and the change record truly reflects the design intention.

[0017] By establishing LEVEL1 to LEVEL3 three-level change classification, automatic classification processing can be performed according to the influence range of the change event, LEVEL1 change only affecting attributes such as connector code change and wire color change, the system can generate automatic update instructions; for LEVEL2 change such as significant change of wire length, instructions need to be manually checked; for LEVEL3 change involving topological structure change, process route reconstruction is triggered, so that the generation of engineering change instructions is more targeted, helps the process and production departments to distinguish the change priority and reasonably allocate audit resources, thereby improving the processing efficiency of the entire change management process.

[0018] By accurate matching of the reference identifier, it is ensured that the change content can be accurately located and synchronized to the corresponding position of the process drawing, especially during the synchronization process, the existing manual annotations of the process personnel, such as special process notes on the drawing, can be retained, important process information loss caused by drawing update is avoided, the continuity and integrity of manufacturing data are ensured, and production errors caused by asynchronous information are reduced. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the present application, the drawings needed to be used in the description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0020] Figure 1 The flowchart of the harness drawing version management method provided by the embodiments of the present application. DETAILED DESCRIPTION

[0021] In order to make the application purposes, features and advantages of the present application more obvious and easy to understand, the technical solutions protected by the present application will be described in detail below with specific embodiments and drawings. Obviously, the following described embodiments are only some of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0022] The embodiments of the present application provide a harness drawing version management method, system, device and medium, which solves the technical problem of realizing intelligent synchronization of change content and process drawing.

[0023] The technical solutions of the embodiments of the present application will be described in detail below with reference to the drawings.

[0024] Figure 1 The flowchart of the harness drawing version management method provided by the embodiments of the present application. As shown inFigure 1 As shown, the line harness drawing version management method provided by the embodiment of the application specifically comprises the following steps: S1: Obtain attribute data of a new version of line harness elements, the line harness elements including wires, branches and connectors, wherein the attribute data of the wires includes wire gauge, length and color, the attribute data of the branches includes covering form and three-dimensional coordinates, and the attribute data of the connectors includes model and terminal definition; S2: Assign reference identifiers to different line harness elements, wherein a system unique wire gauge is assigned to the wires, and a globally unique identifier GID is assigned to the branches and the connectors; S3: Compare the attribute data of the new version of line harness elements with pre-stored attribute data of line harness elements of an old version, determine a change type of a change event by matching the reference identifiers, and the change type at least includes one of the following events: addition, deletion and attribute update; S4: Hierarchically process the change event according to a preset rule, and divide the change event into three change levels of LEVEL1 change, LEVEL2 change and LEVEL3 change; S5: Generate corresponding engineering change instructions according to the change levels; wherein the LEVEL1 change generates an automatic update instruction, the LEVEL2 change generates an update instruction requiring manual review, and the LEVEL3 change generates a process route reconstruction instruction; First, the change type (addition, deletion or update) is determined through matching of the reference identifiers, then the specific content of the change is analyzed according to a preset rule library, and finally the level is determined. This process ensures that even the same type of change operation will be divided into different processing levels due to different specific contents and influence ranges.

[0025] S6: Synchronize the change content to the corresponding position of the process drawing and retain the existing manual annotations.

[0026] It should be noted that in step S2, the globally unique identifier GID has the following format: [element type code] [version number] [hash value]; Wherein, the hash value is generated based on element coordinates, belonging configuration item and parent node through MD5 algorithm, when the branch position moves a distance d≥5mm, the hash value is recalculated and a new globally unique identifier GID is generated.

[0027] It should be noted that the globally unique identifier GID is assigned to each branch or connector, and the purpose is to uniquely and accurately track the same element when the drawing version is changed, even if some attributes (code, position) of the element change.

[0028] The hash value is an important part of the globally unique identifier GID, which is a fixed-length string representing the unique characteristics of the input data. In the present application, the input data for generating the hash value includes the coordinates of the element, the configuration item to which it belongs, and the parent node ID. As long as the input data remains unchanged, the hash value will remain unchanged; if the input data changes slightly, the generated hash value will change.

[0029] The branch position movement distance is used to distinguish between slight position adjustment and major topology change.

[0030] When the branch position movement distance is < 5mm: it is considered to be a drawing error or a slight installation adjustment, and the fundamental topology connection relationship is not changed, so the globally unique identifier GID remains unchanged, and this change is classified as a low-level attribute update. When the branch position movement distance is ≥ 5mm: it is determined to be a major topology reconstruction, because the major change in position will affect the routing of the wire harness, the calculation of the length, the assembly relationship, etc., at this time, the following operations are performed: Recalculate the hash value: since the coordinates of the element (input data) have changed significantly, recalculate the hash value based on the new coordinate data. Generate a new globally unique identifier GID: combine the newly calculated hash value with the element type code and version number to generate a completely new globally unique identifier GID.

[0031] In the comparison between the old and new versions, the branch in the old version at position A (with globally unique identifier GID GID-old) and the branch in the new version at position B (with branch position movement distance ≥ 5mm) are determined to be two different elements. The specific change event is recorded as: the branch corresponding to GID-old is deleted, and a new branch with GID-new is added, achieving precise isolation of the change impact.

[0032] In an exemplary embodiment, in step S3, the change type is determined by matching the reference identifier, specifically including: When the wire number is the same, it is determined to be the same wire, and the length and color attribute changes are compared; When the wire number changes, record the old wire number wire deletion event and the new wire number wire addition event; When the globally unique identifier GID exists but the attribute changes, it is recorded as an attribute update event; When the globally unique identifier GID does not exist in the new version, it is recorded as a deletion event; When a new globally unique identifier GID appears, it is recorded as an addition event.

[0033] According to another embodiment of the present application, in step S4, the LEVEL1 change includes: connector code change, wire color change; The LEVEL2 change includes: wire length change more than 10%, branch covering form change; The LEVEL3 change includes: global unique identifier GID addition, global unique identifier GID deletion, wire number change.

[0034] The change affecting the harness element attribute is divided into LEVEL1 change, the change affecting the harness element physical property is divided into LEVEL2 change, and the change causing the harness element topology structure change is divided into LEVEL3 change; Further, the LEVEL1 change belongs to attribute level change, and the change content includes: connector code update, wire color adjustment, text label modification, and the like non-structural change; The LEVEL2 change belongs to physical level change, and the change content includes: wire length change, branch covering form change, installation position fine adjustment (moving distance less than a preset value); The LEVEL3 change belongs to topology level change, and the change content includes: global unique identifier GID addition / deletion, wire number change, branch point position major adjustment (moving distance greater than a preset value).

[0035] According to an embodiment of the present application, before step S6, there is further included: When the global unique identifier GID of the connector is unchanged but the model is changed, the original terminal crimping process parameter library is automatically searched; Based on the cross-sectional characteristics and material hardness parameters of the new model terminal, the closest existing process parameters are matched.

[0036] In one embodiment, in step S6, the drawing synchronization includes: The global unique identifier GID is matched to locate the change area on the process drawing, and the positioning accuracy error is not greater than ±0.5 mm; The note information added by the process personnel is retained; After the drawing is updated, a version identifier is automatically added.

[0037] Further, as a refinement and extension of the specific implementation of the above embodiment, in order to completely describe the specific implementation process in the present embodiment, another harness drawing version management method is provided, and the method further includes a version conflict detection step: All historical versions are traversed to detect attribute conflicts of the same global unique identifier GID in different versions; When a conflict is detected, arbitration is performed according to the version time stamp and the change level, and the result of the highest level change is retained.

[0038] The application further provides a wiring harness drawing version management system. The following is an embodiment of the wiring harness drawing version management system provided by the present disclosure. The wiring harness drawing version management system and the wiring harness drawing version management method of each embodiment described above belong to the same inventive concept. Details not described in the embodiment of the wiring harness drawing version management system can be referred to the embodiment of the wiring harness drawing version management method. The system comprises: a data acquisition module configured to acquire attribute data of a new version of a wiring harness element, the wiring harness element comprising a wire, a branch, and a connector; an identifier allocation module configured to allocate a reference identifier to different wiring harness elements, wherein a system unique wire number is allocated to the wire, and a globally unique identifier (GID) is allocated to the branch and the connector; a change identification module configured to compare the attribute data of the new version of the wiring harness element with pre-stored attribute data of an old version of the wiring harness element, and determine a change type of a change event by matching the reference identifier, the change type comprising at least one of the following events: addition, deletion, and attribute update; a hierarchical processing module configured to perform hierarchical processing on the change event according to a preset rule, and divide the change event into three change levels: LEVEL1 change, LEVEL2 change, and LEVEL3 change; an instruction generation module configured to generate a corresponding engineering change instruction according to the change level; a drawing synchronization module configured to synchronize the change content to a corresponding position of a process drawing, and retain an existing manual annotation.

[0039] The wiring harness drawing version management method provided by the embodiments of the present application can be applied to electronic devices. Those skilled in the art can understand that the electronic device structure involved in the embodiments of the present application does not constitute a limitation on the electronic device. The electronic device can include more or fewer components than shown, or combine certain components, or different component arrangements. In the embodiments of the present application, the electronic device includes but is not limited to a laptop computer, a desktop computer, a workstation, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as a personal digital processor, a cellular phone, a smart phone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the embodiments of the present application described and / or claimed herein.

[0040] The electronic device can include a processor, an external memory interface, an internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, a wireless communication module, an audio module, a speaker, a microphone, a sensor module, a key, a camera, a display screen, and a SIM card interface, and the like.

[0041] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device can include more or fewer components than the illustration, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0042] The processor can include one or more processing units, such as: the processor can include a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), and the like. Among them, different processing units can be independent devices, or can be integrated in one or more processors.

[0043] Among them, the processor can be the nerve center and command center of the electronic device. The controller can generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching instructions and executing instructions.

[0044] The memory in the processor can also be provided to store instructions and data. In some embodiments, the memory in the processor is a cache memory. The memory can save instructions or data that the processor has just used or repeatedly uses. If the processor needs to use the instructions or data again, it can directly call from the memory. Avoiding repeated access, reducing the waiting time of the processor, thus improving the efficiency of the system.

[0045] The external memory interface can be used to connect an external memory card, such as a MicroSD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor through the external memory interface to realize the data storage function. For example, files such as music, video, and the like are saved in the external memory card.

[0046] The internal memory can be used to store computer executable program codes including instructions. The processor performs various function applications and data processing of the electronic device by running the instructions stored in the internal memory. The internal memory can include a program storage area and a data storage area. The internal memory can include a high-speed random access memory, and can further include a non-volatile memory such as at least one of a magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0047] The wireless communication function of the electronic device can be implemented through an antenna, a wireless communication module, a modem processor, and a baseband processor, etc.

[0048] The wireless communication module can provide a wireless communication solution including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied to the electronic device.

[0049] The electronic device can implement an audio function, etc. through an audio module, a speaker, a receiver, a microphone, a headphone interface, and an application processor, etc.

[0050] The electronic device can implement a photographing function through an ISP, a camera, a video codec, a GPU, a display screen, and an application processor, etc.

[0051] The electronic device can implement a display function through a GPU, a display screen, and an application processor, etc.

[0052] The GPU is a microprocessor for image processing, which is connected to the display screen and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor can include one or more GPUs, which execute program instructions to generate or change display information.

[0053] The display screen is used to display images, videos, etc. The display screen includes a display panel.

[0054] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware, computer software or a combination of both. In order to clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been described in the above description in a general manner. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. A skilled person can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0055] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the devices, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders from that noted in the drawings. For example, two blocks that are represented in succession can actually be executed substantially in parallel, and they can also be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and the combination of blocks in the block diagrams and / or flowcharts, can be realized by a dedicated hardware-based system that performs the specified functions or operations, or can be realized by a combination of dedicated hardware and computer instructions.

[0056] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed ones can be indirect coupling or communication connection through some interfaces, devices or units, and can also be electrical, mechanical or other forms of connection.

[0057] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application can be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

[0058] The electronic device realizes the attribute data of the harness element of the new version of the harness drawing version management method, the harness element including a wire, a branch, and a connector; a reference identifier is assigned to different harness elements, wherein a system unique wire number is assigned to the wire, and a globally unique identifier GID is assigned to the branch and the connector; the attribute data of the new version of the harness element is compared with the pre-stored attribute data of the old version of the harness element, the change type of the change event is determined by matching the reference identifier, the change type at least including one of the following events: adding, deleting, and attribute updating; the change event is processed according to a preset rule, and the change event is divided into three change levels of LEVEL1 change, LEVEL2 change, and LEVEL3 change; the corresponding engineering change instruction is generated according to the change level; the change content is synchronized to the corresponding position of the process drawing, and the existing manual annotation is retained, and the intelligent synchronization of the change content and the process drawing is realized.

[0059] In the storage medium provided by the application, a program product capable of realizing the harness drawing version management method is stored.

[0060] The harness drawing version management method comprises: S1: attribute data of a new version of a harness element is obtained, the harness element including a wire, a branch, and a connector; S2: a reference identifier is assigned to different harness elements, wherein a system unique wire number is assigned to the wire, and a globally unique identifier GID is assigned to the branch and the connector; S3: the attribute data of the new version of the harness element is compared with the pre-stored attribute data of the old version of the harness element, the change type of the change event is determined by matching the reference identifier, the change type at least including one of the following events: adding, deleting, and attribute updating; S4: the change event is processed according to a preset rule, and the change event is divided into three change levels of LEVEL1 change, LEVEL2 change, and LEVEL3 change; S5: the corresponding engineering change instruction is generated according to the change level; S6: the change content is synchronized to the corresponding position of the process drawing, and the existing manual annotation is retained.

[0061] The wire harness drawing version management method provided in the application assigns a system unique wire number to the wire and a globally unique identifier GID to the branch and the connector, thereby realizing accurate classification of change events. When the wire number is unchanged, it can be accurately determined that it is an attribute update of the same wire, thereby avoiding false addition and deletion events caused by wire deletion and reconstruction operations, significantly improving the accuracy of change identification, and ensuring that the change record truly reflects the design intention.

[0062] In some possible implementation manners, the wire harness drawing version management method of the present disclosure can be implemented in the form of a program product, which includes program code for causing a terminal device to perform the steps of various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of the specification when the program product is run on the terminal device.

[0063] The storage medium of the present disclosure can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium may, for example, be but is not limited to an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0064] The above description of disclosed embodiments enables a person skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to these embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

[0065] These changes, modifications, replacements and variations made to the embodiments without departing from the principles and spirits of the present application still fall within the protection scope of the present application.

Claims

1. A method for managing wire harness drawing versions, characterized in that, The method includes: S1: Obtain the attribute data of the new version of the wire harness components, which include wires, branches, and connectors; S2: Assign reference identifiers to different wire harness components, where system-unique wire numbers are assigned to conductors, and globally unique identifiers (GIDs) are assigned to branches and connectors; S3: Compare the attribute data of the new version of the wire harness component with the attribute data of the pre-stored old version of the wire harness component, and determine the change type of the change event by matching the reference identifier. The change type includes at least one of the following events: addition, deletion and attribute update. S4: Classify change events according to preset rules, dividing them into three change levels: LEVEL1, LEVEL2, and LEVEL3. S5: Generate corresponding engineering change instructions based on the change level; S6: Synchronize the changes to the corresponding locations on the process drawings, and retain existing manual annotations.

2. The wire harness drawing version management method as described in claim 1, characterized in that, In step S2, the format of the globally unique identifier GID is: [Component Type Code] [Version Number] [Hash value]; The hash value is generated using the MD5 algorithm based on the component coordinates, the configuration item it belongs to, and the parent node. When the branch position moves a distance d ≥ 5mm, the hash value is recalculated and a new globally unique identifier GID is generated.

3. The wire harness drawing version management method as described in claim 1, characterized in that, In step S3, the change type is determined by matching the baseline identifier, specifically including: When wire numbers are the same, they are determined to be the same wire by comparing changes in length and color attributes; When the wire number changes, record the events of deleting the old wire number and adding the new wire number; When a globally unique identifier (GID) exists but its attributes change, it is recorded as an attribute update event. When the globally unique identifier (GID) does not exist in the new version, it is recorded as a deletion event; When a new globally unique identifier (GID) appears, it is recorded as a new event.

4. The wire harness drawing version management method as described in claim 1, characterized in that, In step S4, the LEVEL1 change includes: change of connector code and change of wire color; LEVEL2 changes include: wire length changes exceeding 10%, and changes to branch wrapping patterns; The LEVEL3 changes include: adding a Globally Unique Identifier (GID), deleting a Globally Unique Identifier (GID), and changing wire numbers.

5. The wire harness drawing version management method as described in claim 1, characterized in that, The steps preceding step S6 also include: When the globally unique identifier (GID) of the connector remains unchanged but the model number changes, the original terminal crimping process parameter library is automatically retrieved. Based on the cross-sectional characteristics and material hardness parameters of the new terminal model, the closest existing process parameters are matched.

6. The wire harness drawing version management method as described in claim 1, characterized in that, In step S6, the drawing synchronization includes: The changed area is located on the process drawing by matching the globally unique identifier GID, with a positioning accuracy error of no more than ±0.5mm; Retain the notes added by process engineers; Automatically add a version identifier after the drawing is updated.

7. The wire harness drawing version management method as described in claim 1, characterized in that, The method also includes a version conflict detection step: Iterate through all historical versions and detect attribute conflicts of the same globally unique identifier (GID) in different versions. When a conflict is detected, arbitration is conducted based on the version timestamp and change level, retaining the result of the highest-level change.

8. A system applied to the wire harness drawing version management method as described in any one of claims 1-7, characterized in that, The system includes: The data acquisition module is used to acquire attribute data of the new version of the wire harness components, which include wires, branches and connectors; The identification assignment module is used to assign reference identifiers to different wire harness components, including assigning system-unique wire numbers to wires and assigning globally unique identifiers (GIDs) to branches and connectors. The change identification module is used to compare the attribute data of the new version of the wire harness component with the attribute data of the pre-stored old version of the wire harness component, and determine the change type of the change event by matching the reference identifier. The change type includes at least one of the following events: addition, deletion and attribute update. The hierarchical processing module is used to process change events in a hierarchical manner according to preset rules, dividing change events into three change levels: LEVEL1 change, LEVEL2 change, and LEVEL3 change. The instruction generation module is used to generate corresponding engineering change instructions based on the change level. The drawing synchronization module is used to synchronize changes to the corresponding locations on the process drawings and retain existing manual annotations.

9. 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 program, it implements the steps of the wire harness drawing version management method as described in any one of claims 1-7.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the wire harness drawing version management method as described in any one of claims 1-7.

Images