Method and system for design data change control and solution generation of electromechanical products

Abstract

The embodiment of the present application provides a method and system for controlling the change of design data of an electromechanical product and generating a solution, and relates to the field of data processing technology. The method includes: 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 is completed within the change buffer time, then the electromechanical product design data is changed based on the first change event to obtain a change result; and an electromechanical product design solution is generated according to the change result. In the embodiment of the present application, when multiple types of participants jointly participate in the innovative design process of an electromechanical product through a visual view, the change process is controlled based on the change priority of the change event and the change buffer time to improve the design efficiency of the electromechanical product.

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 R&D of electromechanical products involves improvements in design, manufacturing, or service models, with innovation at its core. With the growing economy, the innovative design of electromechanical products is becoming increasingly complex, diverse, and customized. To meet the demands of electromechanical products and ensure product design quality and efficiency, it is essential to involve multiple stakeholders in the innovative design process.

[0003] However, in the process of innovative design of electromechanical products involving multiple types of participants, since multiple participants can propose changes to the design of electromechanical products, change conflicts 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 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 includes a first change priority; if the first change priority is higher than the 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 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 characterize the time during which the change event being executed can continue to be executed when switching to execute a change event with a higher priority; and a mechatronics product design plan is generated based on the change result.

[0006] The present embodiment compares the priorities of change events to determine which change event needs to be executed, giving priority to higher-priority change events. Furthermore, when a change is required, a change buffer is set for the currently executing event, allowing the event to be changed smoothly rather than abruptly interrupted. This improves the stability of change event execution and also enhances the design efficiency of electromechanical products.

[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 the step of changing the electromechanical product design data based on the first change event is executed.

[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 in the process of changing, 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 into 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 further includes: updating the change priority of the corresponding historical change event using the waiting time of the unexecuted historical change event according to a preset update cycle; 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; and placing the unexecuted historical change event into the corresponding ready queue according to the updated change priority to wait for processing.

[0014] The embodiment of the present application updates the priority of 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 change priority is calculated as follows:

[0016] W Q =ω1P CRQ +ω2T CRQ +ω3C CRQ

[0017] 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.

[0018] When calculating change priorities, the present embodiment takes into account the participant's role, custom parameters, and wait time. By comprehensively considering multiple influencing factors, the priority of each change event is more reasonable. Furthermore, since wait time is constantly changing, the priority of each change event is also dynamically updated, ensuring that each change event is 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, which 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 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 changes in electromechanical product design data, 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 represent the time during which the change event being executed can continue to be executed when switching to execute a change event with a higher priority; a generation module for generating an electromechanical product design plan based on 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, which 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 practicing 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 following is a brief introduction to the drawings required for use in the embodiments of the present application. 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 relevant drawings can be obtained based on these drawings without 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 the form of two tuples 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 schematic diagram of a design tool data visualization provided in an embodiment of the present application;

[0032] Figure 5 A schematic diagram of another design tool data visualization provided in an embodiment of the present application;

[0033] Figure 6 A schematic diagram of a design data model provided in an embodiment of the present application;

[0034] Figure 7 A schematic diagram showing a design scheme data visualization provided by 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 in an embodiment of the present application;

[0036] Figure 9 A flowchart of a method for controlling design data changes and generating solutions for electromechanical products provided in an embodiment of the present application;

[0037] Figure 10 A schematic diagram of a change conflict resolution method provided in an embodiment of the present application;

[0038] Figure 11 A schematic diagram of the structure of a multi-level ready queue provided in an embodiment of the present application;

[0039] Figure 12 A schematic diagram of a design data feedback process provided in an embodiment of the present application;

[0040] Figure 13 A flowchart of a change activity control process provided in an embodiment of the present application;

[0041] Figure 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] Figure 15 A schematic diagram of the electronic device structure provided in an embodiment of the present application;

[0043] Figure 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 will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0045] It should be noted that all technical and scientific terms used herein have the same meanings as those commonly understood by technicians in the technical field to which this application belongs; the terms used herein 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 this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.

[0047] The R&D of electromechanical products involves improvements in design, manufacturing, or service models, with innovation at its core. With the growing economy, the innovative design of electromechanical products is becoming increasingly complex, diverse, and customized. To meet the demands of electromechanical products and ensure product design quality and efficiency, it is essential to enable multiple stakeholders to participate in the innovative design process. Enabling interaction and feedback between design information data, visualization, and multiple stakeholders is fundamental to supporting innovative design and establishing a process where stakeholders can participate in feedback on design data changes.

[0048] Figure 1 A schematic diagram of a design data management and change feedback framework provided in an embodiment of the present application is shown as follows: 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 data is input and output between the electromechanical product innovation design process part and the design information data management part.

[0049] In design information data management, the design information data involved includes user theme data, design tool data, and design solution data. User theme data, design tool data, and design solution 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 primarily appears in the form of words and can reflect a specific function, feature, or form of a solution or product. Therefore, user topic data can also be called keyword terms. This data is extracted from a large amount of review text and solution text using keyword extraction technology. This data primarily comes 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 triples <topic word 1, topic word 2, co-occurrence word frequency> and serves as the basis for constructing visualization views.

[0053] When user subject data is binary, it can reflect user needs in a specific area, such as product structure and function, or product characteristics and performance. When user subject data is ternary, it can reflect the implicit relationship between product structure and function, characteristics and performance, and product appearance. Participants in electromechanical product design need to complete the design of solutions based on 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 subject words such as heating rod, heating, heater, insulation layer, surround, insulation, connection, etc. that reflect product functions or product characteristics and performance.

[0055] Figure 3 A visualization diagram of user topic data in triple form provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the user subject data includes keywords such as structural insulation barrel and functional separation that reflect the structure and function of electromechanical products, as well as the implicit relationship between each keyword, for example, the number 0.66 on the line between structural insulation barrel and functional separation.

[0056] Design tool data, embodied by innovative design tools, already possesses a fixed visualization format and data model. Design tool data reflects the design intent of design participants during the product innovation design process. Different innovative design theories and methods are employed during product innovation. Design tool data is the information contained within the innovative tools within these methods or theories. Therefore, it primarily originates from concept designers, who generate a significant amount of design tool data during the historical innovative design of similar products. Design tool data primarily encompasses two types of data: basic electromechanical product data and data relationships. Design tool data is generated by concept designers during the product design process.

[0057] Figure 4 A visualization diagram of design tool data provided in an embodiment of the present application, such as Figure 4 As 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 in an 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 developed through the electromechanical product innovation design process also includes data on various aspects of the product, including simple component shape information, function and requirement information reflecting the product innovation design process, and cost and importance information reflecting change feedback. This combination of information, which reflects the product solution's geometric characteristics and design process data, is design solution data. Design solution data includes structural data and structural relationships.

[0060] Figure 6 A schematic diagram of a design data model provided in an embodiment of the present application is shown as follows: 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 visual diagram of a design scheme data provided in an embodiment of the present application, such as Figure 7 As shown, the design scheme data is the design scheme data of the loading platform, including the correlation information of the sealing structure, exhaust port, support frame, and hollow support legs.

[0062] Design information data management is to store user subject data, design tool data and design scheme 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 participation in the electromechanical product design process provided in an embodiment of the present application is shown as follows: Figure 8 As shown in Figure 1, the participant layer is used to display the participants involved in electromechanical product design, 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 visual 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 in the data layer is visually mapped to the view layer, which then communicates with the participant layer to share feedback on changes. The changed data is stored in the design database of the data layer, and the view layer's views are also modified and fed back to other participants.

[0067] Based on Figure 8As shown in the content, multiple participants may make changes to the same view during the design of electromechanical products. 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] Figure 9 The following is a flowchart of a method for controlling changes to electromechanical product design data and generating a solution, provided in an embodiment of the present application. It is understood that the method for controlling changes to electromechanical product design data provided in an embodiment of the present application can be applied to terminal devices (also referred to as electronic devices) and servers; the terminal devices can specifically be smartphones, tablet computers, computers, personal digital assistants (PDAs), etc.; and the servers can specifically be application servers or web servers. To facilitate understanding of the technical solutions provided in an embodiment of the present application, the following describes the application scenarios of the method for controlling changes to electromechanical product design data provided in an embodiment of the present application, using a server as an example execution subject.

[0069] like Figure 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 visual view that the design data of an electromechanical product needs to be changed, he or she clicks on the location in the visual 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 visual view needs to be changed based on the first change event.

[0072] The click can be triggered by the participant through a mouse click or manually by the participant.

[0073] The server determines, according to the first change priority of the first change event, whether the design data of the electromechanical product in the visualization view needs to be changed based on 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 change event being executed can continue to be executed when switching to a change event with a higher execution priority.

[0075] Step S903: Generate a mechatronics product design plan based on the change result.

[0076] Optionally, since multiple participants can modify the design data of the electromechanical product, when the server receives the first modification event, a second modification event may already be being executed in the execution program.

[0077] At this time, it is necessary to compare the first change priority 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 between 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 can 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 the execution of the change event with a higher priority is switched.

[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, thereby 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 simultaneously submit change requests, the pre-set change priorities determine that change event ce2 has a higher priority. Therefore, ce1 enters the ready queue, and ce2 is executed. Subsequently, product user Mr. Liu submits a new change request, creating a change conflict. Change event ce3 has a higher priority than ce2, so after the change buffer expires, ce2 enters the ready queue, and ce3 is executed. After ce3 is executed, the change result is obtained, and the electromechanical product design plan is generated based on the change result of ce3.

[0083] Figure 10 A schematic diagram of a change conflict resolution provided in an embodiment of the present application is shown in FIG. Figure 10As shown, change event ce1: Mr. Chen proposed a change request for "slow cooling speed", which has a low change priority and is stored in the corresponding ready queue. Change event ce2: Mr. Zhang proposed a change request for "wax cannot be effectively discharged", which has a high change priority. At this time, the execution program executes ce ing =ce2. Then, the change event ce3 is proposed by Mr. Liu, which is a change request for "uneven temperature field in sintering space". The change priority is higher than ce2. At this time, ce2 is also stored in the corresponding ready queue, and the program is executed to execute ce3. ing =ce3.

[0084] After ce3 is executed, the newly generated electromechanical product design plan will include the design information of "uneven temperature field in the sintering space".

[0085] The present embodiment compares the priorities of change events to determine which change event needs to be executed, giving priority to higher-priority change events. Furthermore, when a change is required, a change buffer is set for the currently executing event, allowing the event to be changed smoothly rather than abruptly interrupted. This improves the stability of change event execution and also enhances the design efficiency of electromechanical products.

[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 the step of changing the electromechanical product design data based on the first change event is executed.

[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, modifying the height of the support frame of the loading platform.

[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 for waiting 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 executed change event is the one with the highest priority, even though a change buffer is set for each change event, it is not guaranteed to complete within that buffer. Therefore, a change event may be interrupted mid-execution. In this state, the change object of the interrupted change event is still considered to be in the state of "Changing". In this state, even if the first change event has a higher priority, it will not be executed and will be 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 in the process of changing, 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 short 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 into 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 further includes: updating the change priority of the corresponding historical change event using the waiting time of the unexecuted historical change event according to a preset update cycle; 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; and placing the unexecuted historical change event into the corresponding ready queue according to the updated change priority to wait for processing.

[0100] Optionally, considering that if the change priority of the 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 yet 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 placed in 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] Figure 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. Figure 11 As 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. Each ready queue interacts with the execution program so that the change events in the ready queue are executed in the execution program. Figure 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 in the following embodiment.

[0106] The embodiment of the present application updates the priority of 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 change priority is calculated as follows:

[0108] W Q =ω1P CRQ +ω2T CRQ +ω3C CRQ

[0109] 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.

[0110] Optional, ω1, ω2, ω3 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 definition of the product user's P CRQ is 1, the structural designer's P CRQ 2, product design experts and concept designers’ P CRQ is 3.

[0112] C CRQ Represents a custom parameter used to give different priorities to the same role. For example, product user A and product user B may have different understandings of the product and design experience.

[0113] T CRQ This represents the total waiting time for a change event before the current update cycle. For example, if the current update cycle is the third update cycle, and event a waits for ta in the first update cycle and tb in the second update cycle, 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 change priorities, the present embodiment takes into account the participant's role, custom parameters, and wait time. By comprehensively considering multiple influencing factors, the priority of each change event is more reasonable. Furthermore, since wait time is constantly changing, the priority of each change event is also dynamically updated, ensuring that each change event is processed in a timely manner.

[0116] In some embodiments, after the server generates the electromechanical product design plan according to the change result, the method further includes: the server visually presenting the electromechanical 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] Figure 12 A schematic diagram of a design data feedback process provided in an embodiment of the present application is shown in FIG. Figure 12 As shown, the structural designer submits a change request. 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] Figure 13 A flow chart of a change activity control process provided in an embodiment of the present application is shown as follows: Figure 13 As shown, participants observe the visual 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 visual view. Finally, the participants observe the view.

[0122] Figure 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. Figure 14 As shown, the device includes: a receiving module 1401, a changing module 1402 and a generating module 1403; wherein,

[0123] Receiving module 1401 is used to receive a first change event; the first change event includes a first change priority; changing 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; 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 to: 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 the step of changing the electromechanical product design data based on the first change event is executed.

[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, place the second change event into a 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 for placing 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] Based on 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 =ω1P CRQ +ω2T CRQ +ω3C CRQ

[0130] 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.

[0131] Based on the above embodiment, the device further 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 aforementioned embodiment of a method for controlling changes to electromechanical product design data and is capable of executing each of the steps involved in the aforementioned method embodiment. The specific functions of the device can be found in the description above, and a detailed description is omitted here to avoid repetition. The device includes at least one software function module that can be stored in a memory in the form of software or firmware or embedded in the device's operating system (OS).

[0133] Figure 15 This is a schematic diagram of the electronic device structure provided in the embodiment of the present application, such as Figure 15 As shown, the electronic device includes a processor 1501 (processor), a memory 1502 (memory), and a bus 1503. The processor 1501 and the memory 1502 communicate with each other via the bus 1503. The processor 1501 is configured to call program instructions in the memory 1502 to execute the methods provided in 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 gate or transistor logic devices, discrete hardware components. It can implement or execute the 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] The 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] Figure 16 A schematic diagram of a system for controlling design data changes and generating solutions for electromechanical products (hereinafter referred to as the system) is provided in an embodiment of the present application. Figure 16 As shown, the system includes a login module, a change module and a display module; wherein,

[0137] The login module is used to log in users based on their user information. User information can be a combination of an account number and password, a mobile number and a verification code, or an ID number and password. You can choose the appropriate user information based on your specific needs.

[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. The specific process is shown in the above embodiment and 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. The computer instructions enable the computer to execute the methods provided by the above method embodiments.

[0142] In the embodiments provided in this 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 interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0143] In addition, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across 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 each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0145] The above description is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, various modifications and variations of the present application are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection 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; Generate a design plan for an electromechanical product according to the change result; 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. The method according to any one of claims 1 to 5, 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.

7. 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 5; The display module is used to execute the electromechanical product design data change control and solution generation method as described in claim 6.

8. 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 6 is executed.

9. 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 6 is executed.

Images