Mechanical and electrical product design data change control and scheme generation method and system
By receiving and processing changes in electromechanical product design data, high-priority events are processed based on priority and buffering time, dynamically update historical changes, solving changes conflict problems caused by multiple participants, and improving design efficiency and stability .
Patent Information
- Application Number
- CN202410986966.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2044-07-23
AI Technical Summary
In the process of multi-category participants participating in the innovative design of electromechanical products, multiple participants can propose changes to the design data, resulting in changes conflicts and reducing design efficiency.
By receiving change events and processing them according to their priority and change buffering time, priority processing of high-priority change events, setting change buffering time to smooth switching, dynamically updating the priority of historical change events, ensuring that each change event is properly handled .
Effectively eliminate change conflicts, improve the efficiency and stability of electromechanical product design, ensure that change events with higher priority are processed in a timely manner, and improve the processing integrity and accuracy of design data.
Smart Images

Figure CN118941255A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a method and system for controlling design data changes and generating solutions for electromechanical products. Background Art
[0002] The research and development of electromechanical products involves the improvement of design, manufacturing or service mode, and its core is the innovation of electromechanical products. With the development of economy, the innovative design of electromechanical products is becoming more and more complex, diversified and customized. In order to meet the use needs of electromechanical products and ensure the quality and efficiency of product design, it is very necessary to enable multiple types of participants to participate in the innovative design process of electromechanical products.
[0003] However, in the process of multiple types of participants participating in the innovative design of electromechanical products, since multiple participants can propose changes to the design of electromechanical products, change conflicts will occur, making the design efficiency of electromechanical products low. Summary of the invention
[0004] The purpose of the embodiments of the present application is to provide a method and system for controlling changes in electromechanical product design data and generating solutions, so as to resolve change conflicts and improve the design efficiency of electromechanical products when multiple participants propose changes to the electromechanical product design data.
[0005] In a first aspect, an embodiment of the present application provides a method for controlling changes in electromechanical product design data, the method comprising: receiving a first change event; the first change event comprising a first change priority; if the first change priority is higher than a second change priority of a second change event currently being executed, and the change buffer time of the second change event has ended or the second change event is completed within the change buffer time, then based on the first change event, the electromechanical product design data is changed to obtain a change result; wherein the change buffer time is used to characterize the time during which the change event being executed can continue to be executed when switching to a change event with a higher execution priority; and a mechatronics product design plan is generated according to the change result.
[0006] The embodiment of the present application determines the change event that needs to be executed currently by comparing the priority of the change event, so that the change event with a higher priority is processed first. At the same time, when a change is required, a change buffer time is set for the event being executed, so that the event is changed smoothly instead of being interrupted suddenly, which improves the design efficiency of electromechanical products on the basis of improving the stability of the execution of the change event.
[0007] In some embodiments, the first change event includes a change object; after the change buffer time of the second change event has ended or the second change event has been executed within the change buffer time, the method also includes: if the status of the change object is changing, then based on the first change priority, the first change event is placed in the corresponding ready queue for waiting processing; if the status of the change object is no change, then executing the step of changing the electromechanical product design data based on the first change event.
[0008] The embodiment of the present application takes into account that different events may change the same change object. Therefore, if the change object is being changed, the current change event is placed in the ready queue to wait for processing so that the object being changed is not affected by the current change event.
[0009] In some embodiments, the method further includes: if the second change event is not completely executed within the change buffer time, placing the second change event into a corresponding ready queue according to the second change priority to wait for processing.
[0010] The embodiment of the present application takes into account that the change event being executed may not be completed within the change buffer time. Therefore, it is placed in the corresponding ready queue to wait for processing, so that each change event is properly and completely processed to improve the integrity and accuracy of event processing.
[0011] In some embodiments, after receiving the change request, the method further includes: if the first change priority is not higher than the second change priority of the second change event currently being executed, placing the first change event in a corresponding ready queue based on the first change priority to wait for processing.
[0012] The embodiment of the present application places change events with lower priorities into corresponding ready queues to wait for processing, so that each executed change event is the change event with the highest current priority, thereby improving the design efficiency of electromechanical products.
[0013] In some embodiments, the method also includes: according to a preset update cycle, the change priority of the corresponding historical change event is updated using the waiting time of the historical change event that has not been executed; the waiting time is used to characterize the total length of time the change event is in a waiting state before the current update cycle; and according to the updated change priority, the historical change event that has not been executed is placed in a corresponding ready queue to wait for processing.
[0014] The embodiment of the present application updates the priority of the historical change events in the ready queue, so that the priority of each unexecuted historical change event changes dynamically, so that it can be processed in a timely manner, thereby improving the design efficiency of electromechanical products.
[0015] In some embodiments, the calculation formula for change priority is as follows:
[0016] W Q =ω 1 P CRQ +ω 2 T CRQ +ω 3 C CRQ
[0017] Among them, W Q Indicates the change priority, ω 1 ,ω 2 ,ω 3 represents the weight, P CRQ Indicates the priority of the participant role, C CRQ Indicates custom parameters, T CRQ Indicates the waiting time.
[0018] When calculating the change priority, the embodiment of the present application takes into account the role of the participant, the custom parameters, and the waiting time. By comprehensively considering multiple influencing factors, the priority of each change event is made more reasonable. In addition, since the waiting time is constantly changing, the priority of each change event is also dynamically updated, so that each change event can be processed in a timely manner.
[0019] In some embodiments, after generating the electromechanical product design scheme according to the change result, the method further includes: visually displaying the electromechanical product design scheme based on the change result.
[0020] In the embodiment of the present application, after each change event is executed, the electromechanical product design plan is visually displayed, so that the user can intuitively understand the result of the change and thus understand the entire electromechanical product design data.
[0021] In the second aspect, an embodiment of the present application provides a mechatronics product design data change control and solution generation system, the system comprising: a login module, a change module and a display module; wherein the login module is used for users to log in based on user information; the change module is used to execute the method steps of the first aspect; and the display module is used to execute the method steps of the first aspect.
[0022] In a third aspect, an embodiment of the present application provides a device for controlling the change of design data of an electromechanical product, the device comprising: a receiving module for receiving a first change event; the first change event comprising a first change priority; a change module for changing the electromechanical product design data based on the first change event to obtain a change result if the first change priority is higher than the second change priority of the second change event currently being executed, and the change buffer time of the second change event has ended or the second change event is completed within the change buffer time; wherein the change buffer time is used to characterize the time during which the change event being executed can continue to be executed when switching to a change event with a higher execution priority; and a generation module for generating an electromechanical product design plan according to the change result.
[0023] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, a storage medium and a bus, wherein the processor and the memory communicate with each other through the bus; the memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the method steps of the first aspect.
[0024] In a fifth aspect, an embodiment of the present application provides a non-transitory computer-readable storage medium, comprising: the computer-readable storage medium stores computer instructions, and the computer instructions enable the computer to execute the method steps of the first aspect.
[0025] In a sixth aspect, an embodiment of the present application provides a computer program product, comprising: a computer program, wherein the computer program executes the method steps of the first aspect when executed by a processor.
[0026] Other features and advantages of the present application will be described in the subsequent description, and in part will become apparent from the description, or will be understood by implementing the embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0028] Figure 1 A schematic diagram of a design data management and change feedback framework provided in an embodiment of the present application;
[0029] Figure 2 A visualization diagram of user topic data in a binary form provided in an embodiment of the present application;
[0030] Figure 3 A visualization diagram of user topic data in triple form provided in an embodiment of the present application;
[0031] Figure 4 A visualization diagram of design tool data provided by an embodiment of the present application;
[0032] Figure 5 A visualization diagram of another design tool data provided by an embodiment of the present application;
[0033] Figure 6 A schematic diagram of a design solution data model provided in an embodiment of the present application;
[0034] Figure 7 A visual schematic diagram of a design solution data provided in an embodiment of the present application;
[0035] Figure 8 A schematic diagram of a process in which multiple types of participants participate in the design of an electromechanical product provided by an embodiment of the present application;
[0036] Fig. 9 A schematic diagram of a flow chart of a method for controlling design data changes and generating solutions for electromechanical products provided in an embodiment of the present application;
[0037] Fig.10 A schematic diagram of a change conflict resolution method provided in an embodiment of the present application;
[0038] Fig.11 A schematic diagram of the structure of a multi-level ready queue provided in an embodiment of the present application;
[0039] Fig.12 A schematic diagram of a design data feedback process provided in an embodiment of the present application;
[0040] Fig.13 A flowchart of a change activity control process provided in an embodiment of the present application;
[0041] Fig.14 A schematic diagram of the structure of a device for controlling design data changes and generating solutions for electromechanical products provided in an embodiment of the present application;
[0042] Fig.15 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;
[0043] Fig.16 A schematic diagram of the structure of a mechatronic product design data change control and solution generation system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0044] The following embodiments of the technical solution of the present application are described in detail in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.
[0045] It should be noted that all technical and scientific terms used in this document have the same meanings as those generally understood by technicians in the technical field to which this application belongs; the terms used in this document are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned figure descriptions and any variations thereof are intended to cover non-exclusive inclusions.
[0046] In the description of the embodiments of the present application, the technical terms "first", "second", etc. are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance or implicitly indicating the number, specific order or primary and secondary relationship of the indicated technical features. In the description of the embodiments of the present application, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.
[0047] The research and development of electromechanical products involves the improvement of design, manufacturing or service models, and its core is the innovation of electromechanical products. With the increasing development of the economy, the innovative design of electromechanical products is becoming more complex, diversified and customized. In order to meet the use needs of electromechanical products and ensure the quality and efficiency of product design, it is very necessary to enable multiple types of participants to participate in the innovative design process of electromechanical products. Realizing the interaction and feedback of design information data-visualization view-multiple types of participants is the basis for supporting the innovative design of electromechanical products and establishing the process of participants participating in the change feedback of design data.
[0048] Figure 1 A schematic diagram of a design data management and change feedback framework provided in an embodiment of the present application, such as Figure 1 As shown, the framework includes an electromechanical product innovation design process part, a data change feedback process part and a design information data management part; wherein, the data change feedback process is used to execute when the electromechanical product innovation design process part and the design information data management part perform data input and output.
[0049] In the design information data management, the design information data involved includes user subject data, design tool data and design scheme data, and the user subject data, design tool data and design scheme data are visually expressed.
[0050] Visual expressions include, but are not limited to, word cloud diagrams, semantic network diagrams, fault tree diagrams, and solution views.
[0051] User topic data mainly appears in the form of words and can reflect a function, feature or form of a solution or product, so user topic data can also be called subject words. It is obtained from a large number of review texts and solution texts through subject word extraction technology. Most of these data come from users of electromechanical products.
[0052] User topic data is stored in the database in the form of bigrams <topic word, topic word frequency> or triplets <topic word 1, topic word 2, co-occurrence frequency> and serves as the basis for constructing visualization views.
[0053] When the user subject data is binary data, it can reflect the user's needs in a certain aspect such as product structure and function, product characteristics and performance, etc. When the user subject data is ternary data, it can reflect the implicit relationship between product structure and function, characteristic performance, and product appearance. Participants in electromechanical product design need to complete the design of the solution based on the user subject data to meet user needs.
[0054] Figure 2 A visualization diagram of user topic data in the form of a binary provided in an embodiment of the present application, such as Figure 2 As shown, the user subject data includes keywords such as heating rod, heating, heater, insulation layer, surround, insulation, connection, etc. that reflect the product function or product characteristic performance.
[0055] Figure 3 A visualization diagram of user topic data in triple form provided in an embodiment of the present application, such as Figure 3 As shown, the user subject data includes keywords that reflect the structural functions of electromechanical products, such as structural insulation barrel and functional separation, as well as the implicit relationship between the keywords, for example, the number 0.66 on the line between structural insulation barrel and functional separation.
[0056] Design tool data uses innovative design tools as carriers and already has a fixed visualization form and data model. Design tool data reflects the design intentions of design participants in the process of product innovation design. Different innovative design theories and methods are used in product innovation design. Design tool data is the information carried by innovative tools in innovative methods or theories. Therefore, it mainly comes from concept designers. Concept designers will generate a large amount of design tool data in the historical innovative design process of similar products. Design tool data mainly includes two types of data: basic data of electromechanical products and data relationships. Design tool data is generated by concept designers in the process of product design.
[0057] Figure 4 A visualization diagram of design tool data provided by an embodiment of the present application, such as Figure 4As shown, the design tool data is a cause-effect analysis view, including problem definition and design goals.
[0058] Figure 5 Another visualization diagram of design tool data provided by the embodiment of the present application is as follows: Figure 5 As shown, the design tool data is a functional component analysis view, including various functional components and the relationship between the functional components and the functions they play.
[0059] Design solution data: The product concept solution obtained through the electromechanical product innovation design process also contains data on various aspects of the product, including simple component shape information, function and demand information reflecting the product innovation design process, cost and importance information reflecting change feedback, etc. These combined geometric features of the product solution and design process data are the design solution data. Design solution data includes structural data and structural relationships.
[0060] Figure 6 A schematic diagram of a design solution data model provided in an embodiment of the present application, such as Figure 6 As shown, the data model includes structural data and structural relationships, and the structural data includes demand data, function data, feature data, emotion data, change data, etc. The feature data includes attributes, and the attributes include type, key, value and other data.
[0061] Figure 7 A visualization diagram of a design scheme data provided in an embodiment of the present application, such as Figure 7 As shown, the design plan data is the design plan data of the loading platform, including the correlation information of the sealing structure, the exhaust port, the support frame, and the hollow support legs.
[0062] Design information data management is to store user subject data, design tool data and design solution data generated in the process of innovative design of electromechanical products by building appropriate data models and databases, so as to serve as the basis for multiple types of participants to participate in the product design process and realize data change feedback.
[0063] Figure 8 A schematic diagram of a multi-type participant participating in the electromechanical product design process provided in an embodiment of the present application, such as Figure 8 As shown in FIG. 1 , the participant layer is used to display the participants involved in the design of electromechanical products, including four types of participants: product users, structural designers, product design experts, and concept designers. Each type of participant can include multiple participants.
[0064] The view layer is used to display visualization views, including word cloud view, solution view, fault tree diagram and semantic network diagram.
[0065] The data layer is used to design data management, including designing data models and databases.
[0066] The design data of the data layer is visualized and mapped to the view layer, and the view layer and the participant layer provide feedback on changes. The changed data will be stored in the design database of the data layer, and the view of the view layer will also change accordingly and be fed back to other participants.
[0067] Based on Figure 8 From the content shown, it can be seen that multiple participants may make changes to the same view during the process of electromechanical product design. In order to transfer relevant data between participants and avoid conflicts during the change process, it is necessary to effectively control the data change process to improve the design efficiency of electromechanical products.
[0068] Fig. 9 A flow chart of a method for controlling the change of design data of an electromechanical product and generating a solution is provided in an embodiment of the present application. It can be understood that the method for controlling the change of design data of an electromechanical product provided in an embodiment of the present application can be applied to a terminal device (also referred to as an electronic device) and a server; wherein the terminal device can be a smart phone, a tablet computer, a computer, a personal digital assistant (PDA), etc.; the server can be an application server or a Web server. To facilitate understanding of the technical solution provided in an embodiment of the present application, the application scenario of the method for controlling the change of design data of an electromechanical product provided in an embodiment of the present application is introduced below, taking the server as the execution subject as an example.
[0069] like Fig. 9 As shown, the method includes:
[0070] Step S901: The server receives a first change event; the first change event includes a first change priority.
[0071] Optionally, when a participant discovers through a visualization view that the design data of an electromechanical product needs to be changed, the participant clicks on the location in the visualization view where the change is required to trigger a first change event. The server receives the first change event to determine whether the design data of the electromechanical product in the visualization view needs to be changed based on the first change event.
[0072] The click can be triggered by the participant using the mouse or manually.
[0073] The server determines whether the design data of the electromechanical product in the visualization view needs to be changed based on the first change event according to the first change priority of the first change event.
[0074] Step S902: If the first change priority is higher than the second change priority of the second change event currently being executed, and the change buffer time of the second change event has ended or the second change event has been completed within the change buffer time, the server changes the electromechanical product design data based on the first change event to obtain a change result; wherein the change buffer time is used to represent the time during which the executing change event can continue to execute when switching to a change event with a higher execution priority.
[0075] Step S903, generating a mechatronics product design plan according to the change result.
[0076] Optionally, since multiple participants can change the design data of the electromechanical product, when the server receives the first change event, the execution program may already have a second change event being executed.
[0077] At this time, the first change priority needs to be compared with the second change priority of the second change event. If the first change priority is higher than the second change priority of the second change event currently being executed, it indicates that the first change event with a higher priority needs to be executed currently.
[0078] However, in order to enable smooth switching of different change events, a change buffer time is set for each change event in advance. Optionally, the change buffer times corresponding to different change events may be the same or different.
[0079] The change buffer time is used to indicate the time during which the executing change event can continue to execute when switching to a change event with a higher priority.
[0080] Changing the buffer time can effectively reduce the performance overhead caused by frequent switching, and to a certain extent predict the execution rhythm of tasks, thus avoiding system shocks caused by sudden tasks.
[0081] Therefore, if the first change priority is higher than the second change priority of the second change event currently being executed, and the change buffer time of the second change event has ended or the second change event is completed within the change buffer time, the server changes the electromechanical product design data based on the first change event to obtain the change result, and generates an electromechanical product design plan based on the change result.
[0082] For example, when product user Mr. Chen and detailed designer Mr. Zhang submit change requests at the same time, according to the pre-set change priority, it can be determined that the change priority of change event ce2 is higher, so ce1 enters the ready queue and ce2 is executed. Subsequently, product user Mr. Liu submits a new change request, and a change conflict occurs. The change priority of change event ce3 is greater than the change priority of ce2, so ce2 enters the ready queue after the change buffer time ends, and ce3 is executed. After ce3 is executed, the change result is obtained, and the electromechanical product design plan is generated according to the change result of ce3.
[0083] Fig.10 A schematic diagram of a change conflict resolution provided in an embodiment of the present application is shown in FIG. Fig.10 As shown in the figure, change event ce1: Engineer Chen proposed a change request of "slow cooling speed", which has a lower change priority and is stored in the corresponding ready queue. Change event ce2: Engineer Zhang proposed a change request of "wax cannot be effectively discharged", which has a higher change priority. At this time, the execution program executes ce ing =ce2. Then, the change event ce3 is made: Mr. Liu proposes a change request for "uneven temperature field in sintering space", which has a higher priority than ce2. At this time, ce2 is also stored in the corresponding ready queue, and the execution program executes ce ing =ce3.
[0084] After ce3 is executed, the newly generated electromechanical product design plan will include the design information of "uneven temperature field in sintering space".
[0085] The embodiment of the present application determines the change event that needs to be executed currently by comparing the priority of the change event, so that the change event with a higher priority is processed first. At the same time, when a change is required, a change buffer time is set for the event being executed, so that the event is changed smoothly instead of being interrupted suddenly, which improves the design efficiency of electromechanical products on the basis of improving the stability of the execution of the change event.
[0086] In some embodiments, the first change event includes a change object; after the change buffer time of the second change event has ended or the second change event has been executed within the change buffer time, the method also includes: if the status of the change object is changing, then based on the first change priority, the first change event is placed in the corresponding ready queue for waiting processing; if the status of the change object is no change, then executing the step of changing the electromechanical product design data based on the first change event.
[0087] Optionally, since multiple participants can modify the design data of the electromechanical product, different participants may modify the same object of the electromechanical product design data, for example, modify the height of the support frame of the stage.
[0088] At this time, it is necessary to judge the status of the change object of the first change event. If the status of the change object is changing, the first change event will be placed in the corresponding ready queue based on the first change priority to wait for processing; in order to ensure that the historical change events stored in all ready queues can be processed in a timely manner, other change events with the highest change priority will be executed at this time.
[0089] If the status of the change object is not changed, the electromechanical product design data is changed based on the first change event.
[0090] It should be noted that since each change event executed is the change event with the highest change priority, although a change buffer time is set for each change event, the change event may not be able to be completed within the change buffer time. Therefore, a change event may be interrupted halfway through execution. At this time, the state of the change object of the interrupted change event is still considered to be changing. In this state, even if the change priority of the first change event is higher, it is still not executed and is placed in the corresponding ready queue for processing.
[0091] The embodiment of the present application takes into account that different events may change the same change object. Therefore, if the change object is being changed, the current change event is placed in the ready queue to wait for processing so that the object being changed is not affected by the current change event.
[0092] In some embodiments, the method further includes: if the second change event is not completely executed within the change buffer time, the server places the second change event into a corresponding ready queue according to the second change priority to wait for processing.
[0093] Optionally, since the function of the change buffer time is to smoothly switch the change event, the change buffer time is usually a shorter time, for example, the change buffer time is several seconds or more than ten seconds.
[0094] At this time, if the second change event has just been executed and is a long task type change event, the second change event cannot be fully executed within the change buffer time. In order to ensure the integrity of the change event execution, the second change event needs to be placed in the corresponding ready queue according to the second change priority to wait for processing.
[0095] The embodiment of the present application takes into account that the change event being executed may not be completed within the change buffer time. Therefore, it is placed in the corresponding ready queue to wait for processing, so that each change event is properly and completely processed to improve the integrity and accuracy of event processing.
[0096] In some embodiments, after receiving the change request, the method further includes: if the first change priority is not higher than the second change priority of the second change event currently being executed, placing the first change event in a corresponding ready queue based on the first change priority to wait for processing.
[0097] Optionally, since the server determines whether to execute the first change event by comparing the change priorities of the first change event and the second change event, and the first change priority of the first change event may be less than or equal to the second change priority of the second change event, at this time, the first change event is placed in the corresponding ready queue to wait for processing.
[0098] The embodiment of the present application places change events with lower priorities into corresponding ready queues to wait for processing, so that each executed change event is the change event with the highest current priority, thereby improving the design efficiency of electromechanical products.
[0099] In some embodiments, the method also includes: according to a preset update cycle, the change priority of the corresponding historical change event is updated using the waiting time of the historical change event that has not been executed; the waiting time is used to characterize the total length of time the change event is in a waiting state before the current update cycle; and according to the updated change priority, the historical change event that has not been executed is placed in a corresponding ready queue to wait for processing.
[0100] Optionally, considering that if the change priority of a change event remains unchanged, low-priority events will not be processed. Therefore, in order to ensure that each change event is properly and promptly processed, the change priority of historical change events that the server has received but not executed is updated according to the preset update cycle.
[0101] Exemplarily, the waiting time of the uncompleted historical change event is used to update the change priority of the corresponding historical change event; and the uncompleted historical change event is put into the corresponding ready queue according to the updated change priority to wait for processing.
[0102] It should be noted that different ready queues are used to store change events of different priorities. For example, ready queue 1 stores change events with a change priority of 1, ready queue 2 stores change events with a change priority of 2, and ready queue 3 stores change events with a change priority of 3.
[0103] Fig.11 A schematic diagram of the structure of a multi-level ready queue provided in an embodiment of the present application is shown in FIG. Fig.11As shown, the multi-level ready queue includes ready queue 1, ready queue 2, ready queue 3, ready queue 4 and ready queue n with change priority from high to low, and each ready queue interacts with the execution program so that the change event in the ready queue is executed in the execution program. Fig.10 As shown in Figure 2, as the priority of a change decreases, the change buffer time also decreases.
[0104] When the change priority of a historical change event changes, the historical change event is placed in the corresponding ready queue based on the updated change priority.
[0105] It should be noted that when calculating the change priority of a historical change event, the calculation may be performed based on the calculation formula for the change priority of the following embodiment.
[0106] The embodiment of the present application updates the priority of the historical change events in the ready queue, so that the priority of each unexecuted historical change event changes dynamically, so that it can be processed in a timely manner, thereby improving the design efficiency of electromechanical products.
[0107] In some embodiments, the calculation formula for change priority is as follows:
[0108] W Q =ω 1 P CRQ +ω 2 T CRQ +ω 3 C CRQ
[0109] Among them, W Q Indicates the change priority, ω 1 ,ω 2 ,ω 3 represents the weight, P CRQ Indicates the priority of the participant role, C CRQ Indicates custom parameters, T CRQ Indicates the waiting time.
[0110] Optional, ω 1 ,ω 2 ,ω 3 Respectively represent P CRQ , T CRQ , C CRQ Each weight can be set based on expert experience or obtained based on the entropy weight method.
[0111] P CRQ Indicates the priority of the participant role. Based on the above embodiment, it can be seen that the participant types include four types of participants: product users, structural designers, product design experts, and concept designers. For example, the P of the product user is defined asCRQ is 1, the structural designer's P CRQ 2, product design experts and concept designers CRQ is 3.
[0112] C CRQ Indicates a custom parameter, which is used to give the same role different priorities. For example, product user A and product user B also have differences in product understanding and design experience.
[0113] T CRQ Indicates the waiting time, which is used to characterize the total length of time that the change event is in the waiting state before the current update cycle. For example, if the current update cycle is the third update cycle, event a is in the waiting state for ta in the first update cycle and for tb in the second update cycle, then the waiting time is ta+tb.
[0114] The change priority of the change event is stored in the queue CR_Queue, and CR_Queue is defined as follows: CR_Queue = {W Q1 ,W Q2 ,...,W Qn}, where W Qi Indicates the change priority of the i-th change event, where 1≤i≤n.
[0115] When calculating the change priority, the embodiment of the present application takes into account the role of the participant, the custom parameters, and the waiting time. By comprehensively considering multiple influencing factors, the priority of each change event is made more reasonable. In addition, since the waiting time is constantly changing, the priority of each change event is also dynamically updated, so that each change event can be processed in a timely manner.
[0116] In some embodiments, after the server generates a mechatronics product design plan according to the change result, the method further includes: the server visually displays the mechatronics product design plan based on the change result.
[0117] Optionally, after the first change event is executed, in order to allow other participants to observe the change result, the server visualizes the electromechanical product design data based on the change result.
[0118] Therefore, the design data after the change is completed will be fed back to the corresponding database and design view, and other participants will also observe the changes in the design data through the design view.
[0119] In the embodiment of the present application, after each change event is executed, the electromechanical product design plan is visually displayed, so that the user can intuitively understand the result of the change and thus understand the entire electromechanical product design data.
[0120] Fig.12 A schematic diagram of a design data feedback process provided in an embodiment of the present application, such as Fig.12 As shown, the structural designer submits a change request, and after the change is implemented, the visual view after the change and the corresponding design data are fed back to the structural designer and other designers who are interested in the view.
[0121] Fig.13 A flow chart of a change activity control process provided in an embodiment of the present application is as follows: Fig.13 As shown, participants observe the visualization view, and when they find that the design data of the electromechanical product needs to be changed, they issue a change request to form a change event. Based on the change request, the change object in the design information data model is determined, and the change object status is determined. During the change execution process, the change priority is compared. If the change priority is low, it is added to the corresponding ready queue to wait for processing, and the ready queue is updated according to the preset update cycle. Based on the change event with the highest current change priority, the change is implemented and executed to update the design information and the visualization view. Finally, the participants observe the view.
[0122] Fig.14 A schematic diagram of a structure of a device for controlling design data changes and generating solutions for electromechanical products provided in an embodiment of the present application is shown in FIG. Fig.14 As shown, the device includes: a receiving module 1401, a changing module 1402 and a generating module 1403; wherein,
[0123] A receiving module 1401 is used to receive a first change event; the first change event includes a first change priority; a change module 1402 is used to change the electromechanical product design data based on the first change event if the first change priority is higher than the second change priority of the second change event currently being executed, and the change buffer time of the second change event has ended or the second change event is completed within the change buffer time; wherein the change buffer time is used to represent the time during which the change event being executed can continue to be executed when switching to a change event with a higher execution priority; a generating module 1403 is used to generate an electromechanical product design plan according to the change result.
[0124] Based on the above embodiment, the first change event includes a change object; the change module 1402 is specifically used for: if the status of the change object is changing, then based on the first change priority, the first change event is placed in the corresponding ready queue for waiting processing; if the status of the change object is not changed, then executing the steps of changing the electromechanical product design data based on the first change event.
[0125] Based on the above embodiment, the change module 1402 is specifically configured to: if the second change event is not completely executed within the change buffer time, put the second change event into the corresponding ready queue according to the second change priority to wait for processing.
[0126] Based on the above embodiment, the device also includes a waiting module, which is used to put the first change event into the corresponding ready queue based on the first change priority to wait for processing if the first change priority is not higher than the second change priority of the second change event currently being executed.
[0127] Based on the above embodiment, the device also includes a priority update module, which is used to update the change priority of the corresponding historical change event according to the preset update cycle using the waiting time of the historical change event that has not been executed; the waiting time is used to represent the total length of time the change event is in a waiting state before the current update cycle; according to the updated change priority, the historical change event that has not been executed is placed in the corresponding ready queue to wait for processing.
[0128] On the basis of the above embodiment, the device further includes a priority calculation module, wherein the calculation formula for changing the priority is as follows:
[0129] W Q =ω 1 P CRQ +ω 2 T CRQ +ω 3 C CRQ
[0130] Among them, W Q Indicates the change priority, ω 1 ,ω 2 ,ω 3 represents the weight, P CRQ Indicates the priority of the participant role, C CRQ Indicates custom parameters, T CRQ Indicates the waiting time.
[0131] Based on the above embodiment, the device also includes a visualization display module for visually displaying the electromechanical product design solution based on the change result.
[0132] It should be understood that the device corresponds to the above-mentioned embodiment of the electromechanical product design data change control method, and can execute the various steps involved in the above-mentioned method embodiment. The specific functions of the device can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here. The device includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the operating system (OS) of the device.
[0133] Fig.15 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, such as Fig.15 As shown, the electronic device includes a processor 1501 (processor), a memory 1502 (memory) and a bus 1503; wherein the processor 1501 and the memory 1502 communicate with each other through the bus 1503. The processor 1501 is used to call the program instructions in the memory 1502 to execute the methods provided by the above-mentioned method embodiments.
[0134] The processor 1501 can be an integrated circuit chip with signal processing capabilities. The above-mentioned processor 1501 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. It can implement or execute various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
[0135] Memory 1502 may include but is not limited to Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc.
[0136] Fig.16 A schematic diagram of a structure of a mechatronic product design data change control and solution generation system (referred to as system) provided in an embodiment of the present application, such as Fig.16 As shown, the system includes a login module, a change module and a display module; wherein,
[0137] The login module is used for users to log in based on user information. User information can be user account + password, user mobile number + verification code, or user ID number + password. You can select the corresponding user information for login according to the actual situation.
[0138] The change module is used to execute the electromechanical product design data change control and solution generation method described in the above embodiment, that is, to execute the change event based on the change event priority and obtain the change result. Please refer to the above embodiment for the specific process, which will not be repeated here.
[0139] The display module is used to display the electromechanical product design scheme generated according to the change results.
[0140] This embodiment discloses a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute the methods provided by the above-mentioned method embodiments.
[0141] This embodiment provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions enable the computer to execute the methods provided by the above-mentioned method embodiments.
[0142] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0143] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0144] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.
[0145] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A method for controlling design data changes and generating solutions for electromechanical products, characterized in that: The method comprises: Receiving a first change event; the first change event includes a first change priority; If the first change priority is higher than the second change priority of the second change event currently being executed, and the change buffer time of the second change event has ended or the second change event has been executed within the change buffer time, the electromechanical product design data is changed based on the first change event to obtain a change result; wherein the change buffer time is used to indicate the time during which the change event being executed can continue to be executed when switching to a change event with a higher execution priority; A mechatronics product design solution is generated according to the change result.
2. The method according to claim 1, characterized in that The first change event includes a change object; after the change buffer time of the second change event has ended or the second change event has been executed within the change buffer time, the method further includes: If the state of the change object is changing, placing the first change event into a corresponding ready queue based on the first change priority to wait for processing; If the state of the change object is not changed, the step of changing the electromechanical product design data based on the first change event is performed.
3. The method according to claim 1, characterized in that The method further comprises: If the second change event is not completely executed within the change buffer time, the second change event is placed in a corresponding ready queue according to the second change priority to wait for processing.
4. The method according to claim 1, characterized in that: After receiving the change request, the method further includes: If the first change priority is not higher than the second change priority of the second change event currently being executed, the first change event is placed in a corresponding ready queue based on the first change priority to wait for processing.
5. The method according to claim 1, characterized in that The method further comprises: According to the preset update cycle, the change priority of the corresponding historical change event is updated using the waiting time of the historical change event that has not been executed; the waiting time is used to represent the total length of time that the change event is in a waiting state before the current update cycle; According to the updated change priority, the unexecuted historical change events are put into the corresponding ready queue to wait for processing.
6. The method according to claim 1, characterized in that The change priority is calculated as follows: W Q =ω1P CRQ +ω2T CRQ +ω3C CRQ Among them, W Q represents the change priority, ω1, ω2, ω3 represent the weights, P CRQ Indicates the priority of the participant role, C CRQ Indicates custom parameters, T CRQ Indicates the waiting time.
7. The method according to any one of claims 1 to 6, characterized in that: After generating the electromechanical product design scheme according to the change result, the method further includes: The electromechanical product design solution is visualized based on the change results.
8. A system for controlling the change of design data and generating schemes for electromechanical products, characterized in that: The system includes a login module, a change module and a display module; wherein, The login module is used for users to log in based on user information; The change module is used to execute the electromechanical product design data change control and solution generation method as described in any one of claims 1 to 6; The display module is used to execute the electromechanical product design data change control and solution generation method as described in claim 7.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is executed.
10. A computer program product, characterized in that include: A computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is executed.
Citation Information
Patent Citations
A grouping-based concurrent locking method for collaborative editing
CN109034716A
Multi-user real-time synchronous collaborative map editing method and system considering geographic features
CN112070861A
Execution scheduling method and system for clinical test data processing task and readable medium
CN112349361A
Map editing method, device and system
CN112596923A
Task scheduling method and system
CN114911591A
