Process design collaborative management method, electronic equipment and storage medium

Abstract

The invention discloses a process design collaborative management method, electronic equipment and a storage medium, and the method comprises the steps: disassembling to-be-designed instrument structure data in preset design software into a plurality of first data packets according to components of a to-be-designed instrument, and transmitting the plurality of first data packets to a plurality of corresponding responsibility nodes; the first data packet comprises design information of components corresponding to a plurality of responsibility nodes; component design is carried out based on the design information in the first data packet, a second data packet is obtained, the second data packet is authorized, and the authorized second data packet is sent back to the host node; the second data packet comprises designed component information; and after the completely authorized second data packet is obtained, assembling data in the second data packet to obtain an assembly of each component, and issuing the assembly of each component. Different task nodes can participate in instrument design at the same time, and the data security is improved while the design efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of data management, and particularly to a process design collaborative management method, an electronic device, and a storage medium. Background Art

[0002] With the continuous development of data management technology in related fields of the manufacturing industry, some advanced engineering machinery enterprises at home and abroad have begun cross-division collaborative design. Through advanced technologies such as the Product Lifecycle Management (PLM) system, Computer-Aided Design (CAD) tools, and cloud computing, different divisions can achieve product collaborative design based on the same platform and using the same design tool. Currently, there are still some significant pain points in cross-division collaborative design: First, different divisions use different design tools and systems, and it is difficult to convert the results between different design tools, which affects the design efficiency; Second, due to security considerations, the design data of different divisions needs to be permission-isolated, but when conducting collaborative design, authorization to the cooperative division is required. How to perform safe, accurate, and efficient authorization has become another problem in collaboration. Summary of the Invention

[0003] The purpose of the embodiments of this application is to provide a process design collaborative management method, an electronic device, and a storage medium, which can enable different task nodes to participate in instrument design simultaneously, improving the design efficiency while increasing the data security.

[0004] To achieve the above purpose, the embodiments of this application adopt the following technical solutions:

[0005] In a first aspect, the embodiments of this application provide a process design collaborative management method, including: disassembling the structure data of the instrument to be designed in the preset design software into multiple first data packets according to the constituent components of the instrument to be designed, and sending the multiple first data packets to the corresponding multiple responsible nodes respectively; the first data packet contains the design information of the components corresponding to the responsible nodes;

[0006] Based on the design information in the first design packet, perform component design to obtain a second data packet, and authorize the second data packet, and send the authorized second data packet back to the host node; the second data packet contains the component information with the design completed;

[0007] After obtaining the second data packet with full authorization, assemble the data in the second data packet to obtain the assembly of each component, and publish the assembly of each component.

[0008] In one embodiment, the first data packet contains a special encoding for permission control; sending multiple first data packets to corresponding multiple responsible nodes respectively, including: determining the responsible nodes corresponding to the data in the first data packet through the special encoding, and determining the data reception range corresponding to the nodes; sending the data in the first data packet to the responsible nodes according to the reception range of the corresponding responsible nodes.

[0009] In one embodiment, when the special encoding for permission control is incomplete and / or the encoding rule is unclear, sending multiple first data packets to corresponding multiple responsible nodes respectively, including: setting specific attribute values for the components in the first data packet and the first data packet through a preset design software;

[0010] defining corresponding permissions for the attribute values, and transmitting the attribute values to the corresponding data in the first data packet through the attribute transmission method preset by the preset design software, so as to send the first data packet to the corresponding responsible node based on the attribute values.

[0011] In one embodiment, component design is performed based on the design information in the first design package to obtain a second data packet, including: determining the second data packet corresponding to the corresponding component according to the design information; the second data packet contains three-dimensional overall data, three-dimensional shell data, two-dimensional design data, and a bill of materials view.

[0012] In one embodiment, sending the authorized second data packet back to the host node, including: after granting viewing permissions to the three-dimensional shell data and the bill of materials view in the second data packet, returning the second data packet to the host node.

[0013] In one embodiment, after obtaining the fully authorized second data packet, before assembling the data in the second data packet to obtain the assemblies of each component and publishing the assemblies of each component, the method includes: receiving the release process task of the target component in the second data packet, and the initiator of the release process task is the owner of the target component; when the processing status of the target component is the release status and / or the to-be-processed status, performing approval processing on the target component; updating the in-house part processing status according to the processing status of the target component that has passed the approval processing.

[0014] In one embodiment, after obtaining the fully authorized second data packet, assembling the data in the second data packet to obtain the assemblies of each component and publishing the assemblies of each component, including: receiving the pre-release task of the target component, and checking whether the target component is a complete component as a whole; when it is determined that the target component is a complete component as a whole, detecting the approval status of the target component; updating the processing status of the target component based on the approval status of the target component.

[0015] In one embodiment, the method further includes: when it is necessary to change the data in the second data packet, initiating a change process through a change work order; when the change of the data to be changed is completed, synchronizing the original authorization information of the data before the change to the data after the change.

[0016] In a second aspect, the present application provides an electronic device, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the steps of the process design collaborative management method according to any one of the first aspects.

[0017] In a third aspect, the present application provides a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor, implementing the steps of the process design collaborative management method according to any one of the first aspects.

[0018] The process design collaborative management method, electronic device and storage medium provided by the present application, the method includes: disassembling the structure data of the device to be designed in the preset design software into a plurality of first data packets according to the constituent components of the device to be designed, and sending the plurality of first data packets to corresponding plurality of responsible nodes respectively; the first data packet contains the design information of the components corresponding to the plurality of responsible nodes; performing component design based on the design information in the first data packet to obtain a second data packet, and after authorizing the second data packet, sending the authorized second data packet back to the host node; the second data packet contains the component information with the design completed; after obtaining the second data packet with full authorization, assembling the data in the second data packet to obtain the assembly of each component, and publishing the assembly of each component. Therefore, the process design collaborative management method, electronic device and storage medium provided by the present application, by splitting the component data of the device to be designed in the preset design software, obtain a plurality of first data packets constituting the device to be designed; send the first data packets to the corresponding task nodes, and close the access rights of other nodes to the first data packets after the task nodes successfully receive the first data packets, after the task nodes complete the design tasks in the first data packets to obtain the second data packets, authorize the second data packets and send them to the host node, and then the host node assembles the data in the second data packets to obtain complete components and publishes the components. In this way, different task nodes can participate in the device design simultaneously, improving the design efficiency while increasing the data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments and descriptions thereof of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0020] Figure 1A schematic flow chart of a process design collaborative management method provided by an embodiment of the present application;

[0021] Figure 2 A schematic process diagram for the release of the target component assembly in the present application;

[0022] Figure 3 A schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0023] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0024] The terms "first", "second", etc. in this specification and claims are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein. In addition, the "and / or" in this specification and claims means at least one of the connected objects, and the character " / " generally means that the associated objects before and after are in an "or" relationship.

[0025] Refer to Figure 1 , which is a schematic flow chart of a process design collaborative management method provided by an embodiment of the present application. The process design collaborative management method can be executed by an electronic device provided by an embodiment of the present application. The electronic device can be implemented in a software and / or hardware manner, such as a server, a computer, a specific application software in a computer, etc. The process design collaborative management method provided by the embodiment of the present application uses the TOP-DOWN design idea as a whole. After the design of each interface of the vehicle is completed, the disassembly task (the first data packet) is sent to the corresponding nodes (different nodes can correspond to different business divisions).

[0026] In this embodiment, taking the execution subject of the process design collaborative management method as the processor of a computer as an example, the process design collaborative management method provided by this embodiment includes:

[0027] Step S1, disassemble the structure data of the device to be designed in the preset design software into multiple first data packets according to the components of the device to be designed, and send the multiple first data packets to the corresponding multiple responsible nodes respectively; the first data packet contains the design information of the components corresponding to the multiple responsible nodes.

[0028] Here, the preset design software can be Teamcenter and NX, a product data management (PDM) software and a 3D design software. Among them, Teamcenter can be used as a collaboration platform, allowing multiple team members to share, access, and modify design data. In this embodiment, Teamcenter is also used to manage the data and documents during the design and development process of the component to be designed. NX is a high-end CAD / CAM / CAE tool. NX can provide simulation analysis functions, which can be used to predict the performance of products, assist in planning the manufacturing process of products, and support modeling technologies such as freeform design and parametric design. In this embodiment, Teamcenter can be used as a central data warehouse, and the data designed by NX can be synchronized with Teamcenter to ensure that all team members within the permitted permissions can access the latest design information. The workflow defined in Teamcenter can be directly integrated with NX. For example, the design review and approval process can be triggered in NX and completed in Teamcenter. Selecting the combination of Teamcenter and NX can achieve efficient data management and complex process design during the product design and development process, while ensuring data integrity throughout the product life cycle.

[0029] Specifically, Teamcenter is used to centrally store the design data and related documents of the medical device to be designed. NX can obtain the design data from Teamcenter to create a 3D model based on the design data, perform simulation analysis, plan the manufacturing process, and verify the standardization of the design data, etc. Teamcenter is good at data management, while NX focuses on design implementation. Through the combination of Teamcenter and NX, the consistency of design data, the automation of processes, and the collaboration of designs are achieved.

[0030] In this embodiment, the medical device to be designed is disassembled according to its constituent components to obtain a plurality of first data packets, and each first data packet contains the design task of a complete component. The plurality of first data packets are respectively sent to the corresponding responsible nodes, that is, the component design tasks included in the first data packets are sent to the corresponding responsible persons, so that the responsible persons of multiple components can perform design simultaneously, improving the efficiency of process design.

[0031] It should be noted that the design information included in the first data packet can include component geometric information, material properties, component features, and assembly relationships, etc., and also includes establishing the reference coordinate systems of all levels of components and supporting assemblies in the NX 3D design software. When the responsible persons of each component perform component design, they can refer to the position of the component in the spatial coordinate system for design and reserve assembly space or set the structure required for assembly during design.

[0032] In one embodiment, a special encoding for permission control is included in the first data packet; sending multiple first data packets to corresponding multiple responsible nodes respectively includes: determining the responsible nodes corresponding to the data in the first data packet through the special encoding, and determining the data reception range corresponding to the nodes; sending the data in the first data packet to the responsible nodes according to the reception range of the corresponding responsible nodes.

[0033] In this embodiment, in order to ensure data security and meet the management requirements of the minimum awareness range, within the Teamcenter system, according to objective conditions such as organizational structure, object type, and life cycle status, the permissions of users to add, delete, modify, and query data are controlled, so that non-common materials (self-made parts) cannot be read across nodes, published and frozen data cannot be modified, and process data can only be output after the default data is published. Specifically, when creating the first data set in self-made parts, the first data set will inherit the self-made part code. For self-made parts with clear coding rules, the corresponding self-made part assembly can be authorized to relevant task nodes according to the coding rules. The self-made part code also includes the reception range of the task node for this self-made part, that is, the reception degree of the task node. For example, receiving the data of the specified components of this self-made part. In this way, fine control of user permissions is achieved, ensuring that only authorized users can access and operate specific data, thereby protecting the confidentiality and integrity of the data and restricting the unrestricted flow of self-made part information between different nodes.

[0034] It should be noted that self-made parts (non-common materials) refer to parts or components that are developed and designed by the company itself (including parts without drawings), manufactured by itself or entrusted to other enterprises, and are used to form relevant products of the company. Common materials refer to materials purchased from the market, used in the company's products, and helpful for product formation. It includes purchased parts and raw and auxiliary materials. An assembly refers to a complete product developed and designed by the supporting node and delivered to the main engine node.

[0035] In addition, when the special code of the self-made part is unclear, attribute values can also be written for the self-made part and its corresponding data through the pre-release process in the Teamcenter system, so as to separately define permission rules for specific attribute values in the Teamcenter system. Specifically, the attribute values include authorization scenarios, such as authorizing component a to task node A, etc. Specifically, if the coding rule is not sufficient to clarify the scope of data to be authorized, other attributes can be combined to determine. For example, the data scope can be clarified by combining the self-made part attribute - "self-made part type" with the special code and then authorized to the corresponding node. Attributes can be passed to data sets, views, and objects by deploying propagation rules. Configure the assembly-related process in the Teamcenter system, set specific values for the attributes of the assembly and the data sets under the assembly through the process, and then define permissions for the special data with the specific value (the same as the authorization by the coding rule). After setting special values for the self-made parts of the assembly, the special values can be passed to data sets, views, and objects by deploying propagation rules.

[0036] In this embodiment, when it is determined that the first data packet is successfully received by the corresponding responsible node, the access permission of the non-responsible node to the first data packet is closed.

[0037] Here, restricting only the responsible node to access specific data packets reduces the risk of data leakage, protects the confidentiality and integrity of the data, and can manage data access more effectively, ensuring that the data is only used in a secure and controllable environment, thus supporting a more efficient and secure workflow.

[0038] Step S2: Based on the design information in the first data packet, perform component design to obtain a second data packet, and after authorizing the second data packet, send the authorized second data packet back to the host node; the second data packet contains the component information that has been designed.

[0039] Specifically, the person in charge of the relevant responsible node uses the design information in the first data packet as the basis to perform detailed design work on the component. After completing the component design, the design result is packaged into a second data packet. The generation and sending of the second data packet ensure the effective transfer of the design result.

[0040] The process design collaborative management method provided by this application helps with responsibility tracking and task management by clarifying which nodes or individuals have access permissions to the data packets. The authorized data packets can be accessed by other team members, promoting collaboration among teams while ensuring data security and improving the overall work efficiency.

[0041] In one embodiment, component design is performed based on the design information in the first design package to obtain a second data package, including: determining the second data package corresponding to the component according to the design information; the second data package includes three-dimensional overall data, three-dimensional housing data, two-dimensional design data, and a bill of materials view.

[0042] Among them, the bill of materials view is the BOM (Bill of Material) view, that is, a document describing the product structure in data format, which is a product structure data file recognizable by a computer.

[0043] In one embodiment, after authorizing the second data package, it is returned to the host node, including: after granting the viewing permission for the three-dimensional housing data and the bill of materials view in the second data package, the second data package is returned to the host node.

[0044] It can be understood that permission isolation is set between task nodes in the Teamcenter system. The task nodes include a supporting node and a host node. That is to say, the data of the supporting node is not visible to the host node by default, and individual authorization can be performed on the component assembly during authorization. Generally, during authorization, it is configured according to the principle of only opening the overall model and not opening the detailed design information, and no authorization is performed on the assembly detailed design data set and sub-components, and only the outer shape model under the assembly is authorized. The viewing permission for the detailed design three-dimensional and the detailed design engineering drawing cannot be opened. For the detailed design three-dimensional, the three-dimensional model is composed of the assembly three-dimensional file and the sub-component three-dimensional. Without authorizing the sub-component three-dimensional, the assembly three-dimensional is unavailable; for the detailed design two-dimensional, the detailed design information is reflected in the assembly two-dimensional drawing, and the R & D data security cannot be guaranteed. The viewing permission needs to be opened for the BOM view and the assembly self-made part object. Without the BOM view permission, the whole machine BOM cannot be opened after assembly; without the assembly self-made part object permission, the personnel of the host node cannot view the assembly.

[0045] Specifically, the data types and authorization situations of each design object of the self-made parts can be referred to in Table 1.

[0046] Table 1

[0047] Data type Data format Permission rules In-house made part object Item Open viewing permission In-house made part version Revision Open viewing permission 3D shape UGALTREP Open viewing permission 2D shape drawing PDF Open viewing permission 3D assembly UGMASTER Not authorized 2D assembly UGPART Not authorized BOM view BOM view version Open viewing permission

[0048] Step S3, after obtaining the fully authorized second data package, assemble the data in the second data package to obtain the assembly of each component, and release the assembly of each component.

[0049] It can be understood that after each task node completes the component design task, the design data is packaged and authorized and then sent to the host node. The component design data in the second data package may be bulk data. Therefore, before releasing the component, these design data need to be assembled to obtain the component assembly.

[0050] In one embodiment, after obtaining the fully authorized second data packet, before assembling the data in the second data packet to obtain the assemblies of each component and releasing the assemblies of each component, the method includes: receiving the release process task of the target component in the second data packet, and the initiator of the release process task is the owner of the target component; when the processing status of the target component is the release status and / or the to-be-processed status, performing an approval process on the target component; updating the in-house part processing status according to the processing status of the target component that has passed the approval process.

[0051] Specifically, for the process of releasing the target component assembly, reference can be made to the appendix Figure 2 , which is a schematic diagram of the process of releasing the target component assembly in this application.

[0052] The process of releasing the target component assembly may include:

[0053] Step S401, receiving the in-house part release process task;

[0054] Step S402, bringing the sub-parts whose owner is the initiator himself / herself into the process;

[0055] Step S403, checking whether all in-house sub-parts in the process have release / to-be-processed status identifiers. If so, proceed to step S404; otherwise, return to step S401.

[0056] Step S404, determining whether the in-house sub-parts in the process have passed the approval. If so, proceed to step S405; otherwise, return to step S401.

[0057] Step S05, updating the release status for the in-house parts in the process.

[0058] It can be understood that in the Teamcenter system, once the data of the product documentation successfully passes the review, the system will assign it a specific status identifier, such as "released", "archived", or "finalized", etc. When the release status is updated, the data of this version will be locked in the Teamcenter system and no further modification is allowed. To ensure the correctness of the assembly relationship, it is necessary to verify whether all the sub-parts of the in-house parts have been released in the standard release approval process, which requires the designer to release the sub-parts first and then the parent part.

[0059] It should be noted that the parent part can be an assembly composed of multiple sub-parts.

[0060] In one embodiment, after obtaining the fully authorized second data packet, the data in the second data packet is assembled to obtain the assemblies of each component, and the assemblies of each component are released, including: receiving the pre-release task of the target component and checking whether the target component is a complete component; when it is determined that the target component is a complete component, detecting the approval status of the target component; and updating the processing status of the target component based on the approval status of the target component.

[0061] Here, in order to complete the design quickly, the supporting node can use the pre-release process when the component shape design is completed and the detailed design is not completed, and set the "to be processed" status for the assemblies and their data sets of the medical device to be designed. The pre-release process can automatically authorize the assemblies targeted according to the selected host node.

[0062] In addition, when assembling multiple second data sets and the medical device to be designed cannot be obtained completely, the person in charge of the host node can design according to the missing items to obtain a complete medical device.

[0063] In one embodiment, the method further includes: when it is necessary to change the data in the second data packet, initiating a change process through a change work order; when the change of the data to be changed is completed, synchronizing the original authorization information of the data before the change to the data after the change.

[0064] It can be understood that during the process of assembling or debugging the design data, there may be a situation where the design data does not meet the requirements of the medical device to be designed, and it is necessary to change the completed design data in the second data packet.

[0065] In this embodiment, the host node uses a standard process for changes. After selecting the change work order initiation process, the newly created and newly revised components associated with the change work order will be brought into the process. The entire change process will release the change order and the self-made parts simultaneously and automatically transfer them to the process personnel. Moreover, in the supporting node change process, it will automatically identify whether there is authorized assembly data in the process and set the authorization attribute of the change order to the same value as that of the self-made parts. In addition, if there are clear rules, the process can set the corresponding authorization attributes for the newly added components (the newly revised components will inherit the authorization attributes from the previous version, and the authorization scheme is as described above). The authorization attributes on the change order version will be automatically written into the change order object and the data set under the change order in combination with the propagation rules, realizing automatic authorization and notification for the corresponding nodes.

[0066] The process design collaborative management method provided by this application splits the component data of the device to be designed in the preset design software to obtain multiple first data packets that make up the device to be designed; sends the first data packets to the corresponding task nodes, and closes the access rights of other nodes to the first data packets after the task nodes successfully receive the first data packets. After the task nodes complete the design tasks in the first data packets and obtain the second data packets, the second data packets are sent to the host node after authorization, and then the data in the second data packets is assembled by the host node to obtain complete components, and the components are released. The following technical effects can be achieved: 1. Provide a TOP-DOWN design method, issue the design tasks with one key, assign responsibilities to individuals, and realize the synchronous development of the design of the persons in charge of each component.

[0067] 2. The release of design data is strictly controlled by the process. Before the parent part is released, it is required that the sub-parts be finalized to ensure the correctness of the design. The pre-release can be carried out after the external shape design of the supporting assembly is completed, realizing the rapid delivery of design data.

[0068] 3. The pre-release process can authorize the supporting assembly at the same time. The authorization scheme is controlled by the special attributes of self-made parts, making the authorization management of later operation and maintenance personnel more convenient.

[0069] 4. Use NX alternative representation as the 3D of the supporting assembly, which solves the problem that the sub-parts must be authorized due to the strong correlation between the traditional 3D model and the BOM.

[0070] 5. Provide an automated authorization scheme. The data after release (or pre-release) can be automatically authorized to the supporting nodes without manual initiation by the personnel of the host node, improving the data transfer efficiency.

[0071] 6. Adopt different permission schemes for different data types of self-made parts to ensure the security of the core R & D data of the supporting nodes.

[0072] 7. Automatically authorize and notify the change work order to ensure that the host node receives the change notice in the first time, reducing the errors caused by version changes in production.

[0073] Based on the same inventive concept as the foregoing embodiments, the process design collaborative management method provided by this application is described below through a specific example.

[0074] I. Module division: Complete the interface design between the assembly and other components and other feasibility studies.

[0075] II. Coding application: Apply for the codes of the whole machine, components and supporting assemblies of the device to be designed in Teamcenter. The data in this process is only visible to the host node.

[0076] 3. Coordinate system establishment: Establish the reference coordinate system of each level of components and supporting assemblies in NX 3D design software to indicate the relative position relationship of each component.

[0077] 4. Design task issuance: The person in charge of the whole machine will issue the components, assemblies and their associated coordinate systems to the corresponding responsible persons, and the assemblies will be issued to the supporting nodes. Here, if the docking person adopts process authorization, the company where the host node is located cannot view the assembly after issuance; if the coding authorization is adopted, the company where the host node is located can still view the assembly after issuance.

[0078] 5. Design of the appearance of the supporting assembly and the shell model of the output assembly

[0079] After output, authorization can be completed through the "pre-release" process. After authorization, the company where the host node is located can view the pre-released assembly, and the supporting nodes can continue to design without affecting the pre-release of the whole machine by the host node. The host node can edit the assembly process data (outsourced process). After the whole machine is released, the host node can compile the process of all design data. After the host node completes the process compilation, the R&D data will be delivered to the downstream system. The downstream system can produce parts according to the R&D data. If the supporting assembly has been delivered, it can be assembled.

[0080] 6. Data authorization flow: If the coding rule authorization is not configured and the "pre-release process authorization" is not used, the authorization process can be initiated after the data release is frozen to complete the authorization. The viewing permission is opened to the company where the host node is located. After the release, the process data can be compiled. For supporting equipment, after the process compilation is completed for the self-made process supporting equipment, the R&D data will be passed to the downstream system supporting nodes for production according to the process data.

[0081] 7. Assembly and release of the whole machine: When the host node does not have the permission to view the supporting assembly, the supporting assembly will be displayed as "unable to read" in the whole machine BOM. When the host node company has the permission to view the supporting assembly and the assembly has been released or pre-released, the data release freeze process can be initiated for the whole machine. After the release, the host node can compile the process. After the host node completes the process compilation, the R&D data will be passed to the downstream system, and the downstream system can produce parts. If the supporting assembly has been delivered in kind, assembly can be carried out.

[0082] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0083] Figure 3It is a schematic structural diagram of an electronic device according to an embodiment of the present application. Please refer to Figure 3 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0084] The processor, network interface, and memory can be interconnected through an internal bus, and the internal bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity, Figure 3 only a bidirectional arrow is used in

[0085] to represent it, but it does not mean that there is only one bus or one type of bus.

[0086] The memory is used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include a memory and a non-volatile memory, and provide instructions and data to the processor.

[0087] Of course, in addition to the software implementation, the electronic device of the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or a logic device.

[0088] The embodiment of the present application also proposes a computer-readable storage medium, which stores one or more programs, and the one or more programs include instructions. When the instructions are executed by a portable electronic device including a plurality of application programs, the portable electronic device can execute the process design collaborative management method provided by the present application.

[0089] In summary, the above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

[0090] The systems, devices, modules or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0091] Computer-readable media includes both permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0092] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover a non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, commodity or device comprising the element.

[0093] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the method embodiment.

Claims

1. A process design collaborative management method, characterized in that, Including: Decompose the structural data of the device to be designed in the preset design software into multiple first data packets according to the components of the device to be designed, and send the multiple first data packets to corresponding multiple responsible nodes respectively; The first data packet contains the design information of the components corresponding to the multiple responsible nodes; Based on the design information in the first data packet, perform component design to obtain a second data packet, authorize the second data packet, and send the authorized second data packet back to the host node; the second data packet contains the component information with the design completed; After obtaining the second data packet with full authorization, assemble the data in the second data packet to obtain the assembly of each component, and release the assembly of each component.

2. The method according to claim 1, characterized in that, The first data packet contains a special code for permission control; the step of sending the multiple first data packets to corresponding multiple responsible nodes respectively includes: Determine the responsible nodes corresponding to the data in the first data packet through the special code, and determine the data reception range corresponding to the responsible nodes; Send the data in the first data packet to the responsible nodes according to the reception range of the corresponding responsible nodes.

3. The method according to claim 1 or 2, characterized in that, When the special code for permission control is incomplete and / or the coding rule is unclear, the step of sending the multiple first data packets to corresponding multiple responsible nodes respectively includes: Set specific attribute values for the components in the first data packet and the first data packet through the preset design software; Define corresponding permissions for the attribute values, and transfer the attribute values to the corresponding data in the first data packet through the attribute transfer method preset by the preset design software, so as to send the first data packet to the corresponding responsible node based on the attribute values.

4. The method according to claim 1, wherein The step of performing component design based on the design information in the first data packet to obtain a second data packet includes: Determine the second data packet corresponding to the corresponding component according to the design information; the second data packet contains three-dimensional overall data, three-dimensional shell data, two-dimensional design data, and a bill of materials view.

5. The method according to claim 1, wherein The step of sending the authorized second data packet back to the host node includes: After granting the viewing permission to the three-dimensional shell data and the bill of materials view in the second data packet, return the second data packet to the host node.

6. The method according to claim 1, characterized in that Before obtaining the second data packet with full authorization, assembling the data in the second data packet to obtain the assembly of each component, and releasing the assembly of each component, the method includes: Receive the release process task of the target component in the second data packet, and the initiator of the release process task is the owner of the target component; When the processing status of the target component is the release status and / or the to-be-processed status, perform approval processing on the target component; Update the in-house part processing status according to the processing status of the target component that has passed the approval processing.

7. The method according to claim 1, wherein The step of, after obtaining the second data packet with full authorization, assembling the data in the second data packet to obtain the assembly of each component, and releasing the assembly of each component includes: Receive the pre-release task of the target component and check whether the target component is a complete component entity; When it is determined that the target component is a complete component entity, detect the approval status of the target component; Update the processing status of the target component based on the approval status of the target component.

8. The method according to claim 1, wherein The method further includes: When it is necessary to change the data in the second data packet, initiate a change process through a change work order; After the data to be changed is changed, synchronize the original authorization information of the data before the change to the data after the change.

9. An electronic device, characterized in that, It includes: A processor; A memory for storing executable instructions of the processor; Wherein, the processor is configured to execute the instructions to implement the steps of the process design collaborative management method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor, the steps of the process design collaborative management method according to any one of claims 1 to 8 are implemented.

Images