Distributed multidisciplinary online collaborative design system and method

Abstract

The invention discloses a distributed multidisciplinary online collaborative design system and method.The system comprises a project space used for creating, editing and managing design projects and providing a design process template composed of at least one disciplinary node; the design space is used for instantiating each discipline node in the design process template into a corresponding design space, and professional designers of each discipline carry out product design in respective design space and submit design results; wherein a data interaction mode based on a central subject node and a responsibility matrix is adopted among design spaces, and data interaction among a plurality of sub-subject professions is dynamically realized by configuring a data output interface and the responsibility matrix at the central subject node; the business modeling space is used for constructing, maintaining and managing a design process template; and the portal is used for providing information display spaces and task operation entrances for different types of users. According to the method, the collaborative design efficiency of each subject in product design can be improved through distributed online collaborative design.

Description

Technical Field

[0001] The present invention relates to the field of collaborative design, and in particular to a distributed multidisciplinary online collaborative design system and method. Background Art

[0002] Aircraft scheme design has the characteristics of both design task specificity and versatility. The demonstration process is iterative, tentative, and selective. There is a large amount of data, strong multidisciplinary coupling, diverse design schemes, mutual dependence between schemes, high requirements for data version consistency and traceability, and a distributed working environment. In essence, the aircraft design process is a process in which multiple disciplines constantly weigh the pros and cons, constantly seek optimization, and seek multidisciplinary feasibility solutions and even optimal solutions for the system through multiple rounds of iterations. However, due to the large number of professional disciplines involved, large amount of data, complex data sources, and obvious coupling relationships between professional disciplines, designers need to manage the dependencies between various design schemes. The traditional document-based design model and the process management model that focuses on the schedule have problems such as poor consistency when changing documents and updating versions, difficult data extraction, and unmanageable scheme coupling relationships. At the same time, when the data version changes, timely and accurate responses must be made to ensure data consistency, which brings huge challenges to designers, especially aircraft overall design and subsystem overall designers. In terms of business management, the traditional model is a process management model that focuses on the schedule. This model leads to the separation of process and data, the difficulty in controlling the completion of tasks, and the untraceability of the demonstration process. In terms of coordination and communication, the traditional collaborative model based on emails, meetings, and telephone calls has problems such as untimely data changes and inconsistent data. It lacks timely and effective communication reminders and efficient data transmission mechanisms, resulting in a long design cycle for traditional solutions. Summary of the invention

[0003] The purpose of the present invention is to overcome the problems existing in the prior art and to provide a distributed multidisciplinary online collaborative design system and method.

[0004] The objective of the present invention is achieved through the following technical solutions:

[0005] In a first aspect, a distributed multidisciplinary online collaborative design system is provided, comprising:

[0006] Project space, used to create, edit and manage design projects, which provides a design process template consisting of at least one discipline node;

[0007] Design space is used to instantiate each discipline node in the design process template into a corresponding design space. Designers of each discipline carry out product design in their own design space and submit design results. Among them, each design space adopts a data interaction mode based on the central discipline node and the responsibility matrix. By configuring a data output interface and responsibility matrix at the central discipline node, data interaction between multiple sub-disciplines can be dynamically realized.

[0008] Business modeling space for building, maintaining, and managing design process templates;

[0009] Portal, used to provide information display space and task operation entrance for different types of users.

[0010] In some possible embodiments, the project space includes a project overview module and a design project internal operation module. The functions of the project overview module include creating, editing, disabling, enabling, and summarizing all design projects in the current system. When clicking on the editing entry of each project, you can jump to the design project internal operation module; the design project internal operation module includes a project information management sub-module, a design process management sub-module, a team management sub-module, and a multi-scheme management sub-module, wherein the project information management sub-module is used to manage the basic information of the design project, the design process management sub-module is used to build the design project process, the team management sub-module is used to manage the team information in the entire project, and the multi-scheme management sub-module is used to create and manage multiple parallel design schemes.

[0011] In some possible embodiments, the relationship between the discipline nodes in the design process template is displayed through connecting lines or not.

[0012] In some possible embodiments, the data interaction mode based on the central subject node and the responsibility matrix includes:

[0013] According to the hierarchical relationship of task decomposition, the node that decomposes the task to the downstream disciplines and majors is defined as the central discipline node, and the node that receives the task is defined as the sub-discipline node, and this is done recursively layer by layer to achieve data interaction between multiple levels.

[0014] In some possible embodiments, the data output interface is a data interaction interface defined when each central discipline node decomposes the design task to the sub-discipline node, and the information defined in the interface includes transmission data, sub-discipline nodes and a responsibility matrix; the responsibility matrix is ​​an information matrix that controls the data content received by each sub-discipline node, and the transmission data type includes parameters, parameter tables, files and structured data, and the responsibility matrix includes at least two dimensions, one of which is the data content, which includes all data information in the data output interface, and the other dimension is the responsibility dimension, which is used to set the responsibility information of each data.

[0015] In some possible embodiments, the data interaction between multiple sub-disciplines is dynamically realized by configuring a data output interface and a responsibility matrix in a central discipline node, including:

[0016] When a design plan is released in a design space, the data in the design space will first be submitted to the superior central subject node, and then automatically transferred to each sub-subject node according to the responsibility matrix; the central subject node is set with a control switch. When the control switch is turned on, the data can be automatically transferred to the informed party after arriving at the central subject node. When the control switch is turned off, the data needs to be confirmed and agreed by the central subject node before it can be transferred to the relevant disciplines.

[0017] In a specific design task, starting from the top-level node, the design requirements are decomposed layer by layer from top to bottom, the design results are fed back layer by layer from bottom to top, and a cycle of iteration is performed to ultimately achieve coordination and consistency in the design results among the disciplines included in all nodes of the entire system, that is, to achieve a multidisciplinary feasible solution state for the entire plan.

[0018] In some possible embodiments, the business modeling space includes a dimensional configuration module, a parameter cluster configuration module, a parameter symbol configuration module, a parameter configuration module, a task book configuration module, a file cluster configuration module, a file configuration module, a structured data cluster configuration module, a structured data configuration module, a parameter table configuration module, a professional configuration module, a task template configuration module and a design process configuration module.

[0019] In some possible embodiments, the design process configuration module configures the design process based on the canvas and graphic elements, automatically loads the task template configured by the task template configuration module and generates a graphic tool, so that the user can drag the graphic tool corresponding to the task template into the canvas to construct the design process template.

[0020] In a second aspect, a distributed multidisciplinary online collaborative design method is provided, which is used in the above-mentioned distributed multidisciplinary online collaborative design system, comprising:

[0021] Design process templates are constructed, maintained and managed through the business modeling space; design projects are created, edited and managed through the project space, in which a design process template consisting of at least one discipline node is provided; information display space and task operation entrance are provided for different types of users through the portal; each discipline node in the design process template is instantiated into a corresponding design space through the design space, and designers of each discipline carry out product design and submit design results in their respective design spaces; among them, a data interaction mode based on the central discipline node and the responsibility matrix is ​​adopted between each design space, and a data output interface and a responsibility matrix are configured at the central discipline node to dynamically realize data interaction between multiple sub-disciplines.

[0022] In some possible embodiments, the method specifically includes the following steps:

[0023] S1: Build a design process template through the business modeling space;

[0024] S2: Create a design project through the project space: Create a design project in the project space according to the selected design process template;

[0025] S3: Modify the project design process template: modify the instantiation template of the design process template selected when creating the design project as needed;

[0026] S4: Set project team information: According to the design process template obtained in S3, further set the project team information;

[0027] S5: Create a parallel design plan: Create a parallel design plan according to the design process template modified in S3;

[0028] S6: modify the design process of the parallel design scheme: modify the process information of the parallel design scheme created in S5;

[0029] S7: issuing design tasks: issuing design tasks based on the design process obtained in S6. When issuing design tasks, members who receive the tasks can be further selected from the role information set in S4.

[0030] S8: Enter the designer portal: After the task is issued, the designer who receives the design task can enter the designer portal to see the design task;

[0031] S9: Entering the design space: Designers enter each design space from the entrance of each task in the designer portal to carry out solution design;

[0032] S10: Carry out scheme design: Designers can view and process the information in the design space in real time, and create a design scheme based on a certain version of input data. After the scheme is created, if the data input by all upstream central discipline nodes can be seen in the upstream interaction space, the data that needs to be transmitted to each sub-discipline node in the downstream interaction space. Designers can view all data in the upstream interaction space and carry out design based on the input data. If the node is the terminal node, jump to step S14, otherwise continue to S11;

[0033] S11: Decompose the design task: If there are downstream sub-discipline nodes, fill in the structured task books in the downstream interactive space based on S10 and set the responsibility matrix information of each transmission data based on the template instantiation information. The data that exists in the template but is not needed temporarily can be deleted directly, or the data to be used can be selected from the template as needed. If the template cannot meet the design requirements, the design process template of the parallel scheme can be modified according to step S6; after completing all data entry, the task can be decomposed, so that the decomposed design task can be sent to the downstream disciplines;

[0034] S12: Modify the output data in the downstream interactive space: If the central subject node needs to adjust a certain data in the downstream interactive space during the design process, it can be directly modified and saved, and the downstream discipline can receive the data change information in real time;

[0035] S13: View downstream design results: When the sub-discipline node completes the design and releases the design plan, the design results of each discipline can be viewed in real time in the downstream interaction space.

[0036] S14: Forming a design plan: Based on the design results formed by the sub-discipline nodes, further design can be carried out to form design results;

[0037] S15: Release the design plan: After the design process is completed, you can fill in all the data that needs to be entered in the upstream interaction space, upload the responsible files and structured data, and directly release the design plan after checking that they are correct; at this time, the plan changes to the release state. If there is a design plan for the same design input, the original design plan will be changed to the historical effective state;

[0038] S16: Confirm the design plan: When the input data is changed or there is an unpublished plan in the downstream, the plan will be changed to the pending confirmation state. At this time, the designer needs to confirm the plan information again. If the plan meets the requirements of the superior, the design plan can be re-published after confirmation. If it does not meet the requirements, the plan can be withdrawn to the pending release state and return to S10 to carry out the design;

[0039] S17: Design completed: When all disciplines have completed the design and have become published, the design of the entire design project is completed.

[0040] It should be further explained that the technical features corresponding to the above options can be combined or replaced with each other to form a new technical solution if there is no conflict.

[0041] Compared with the prior art, the present invention has the following beneficial effects:

[0042] (1) The present invention adopts a data interaction mode based on a central discipline node and a responsibility matrix in the design space. By configuring a data output interface and a responsibility matrix at the central discipline node, data interaction between multiple sub-disciplines can be dynamically realized. A data output interface of the overall discipline can be automatically and dynamically configured to output data interfaces for multiple subordinate disciplines. The number of data interfaces is small and can be dynamically configured, making them easy to use and maintain. The data interaction between downstream disciplines is controlled by the central discipline node. All data passes through the overall discipline, strengthening the control of the overall plan by the overall disciplines at all levels and the subsystem overall disciplines, and also realizing the unification of business processes and design data. The terminal nodes can be dynamically configured as needed to achieve flexible expansion of the design business.

[0043] (2) The present invention achieves the purpose of effectively organizing and managing multi-disciplinary, multi-position, and multi-scheme data, establishing a mapping relationship between data and processes, and forming an efficient multi-disciplinary online collaborative mechanism through the coordinated design of various modules. It can improve the collaborative design efficiency of various disciplines in aircraft design through distributed online collaborative design; through task platformization, requirement itemization, item parameterization, data standardization, and real-time change, it can achieve process and data unification, traceability of demonstration process, dynamic adjustment of requirement items, real-time reminder of changes, automatic verification of indicators, etc.; through the data interaction mode of the central discipline node, while achieving efficient data flow, strictly implement the quality management requirement of "everything through the overall"; through data standardization modeling means, ensure the consistency of professional interaction data format; through platformized task space and design space, realize effective management of design scheme data and process data.

[0044] (3) In some embodiments, the present invention implements task decomposition and automatic association of multi-source data based on parameterized requirement items. It can automatically verify, trace and manage requirement indicators while achieving requirement item cleansing and consistent transmission. It avoids the problem of process rigidity caused by parameterization by dynamically adding parameter functions during the design process. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 An overall schematic diagram of a distributed multidisciplinary online collaborative design system shown in an embodiment of the present invention;

[0046] Figure 2 A schematic diagram of a project overview module shown in an embodiment of the present invention;

[0047] Figure 3 A schematic diagram of an internal operation module of a design project shown in an embodiment of the present invention;

[0048] Figure 4 A schematic diagram of a data interaction mode based on a central subject node and a responsibility matrix according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram of the overall data output interface of a rocket shown in an embodiment of the present invention;

[0050] Figure 6 The engine development task book shown in the embodiment of the present invention is a schematic diagram;

[0051] Figure 7 The overall design space of the rocket shown in the embodiment of the present invention;

[0052] Figure 8 The overall design space of the engine shown in the embodiment of the present invention;

[0053] Fig. 9 The overall design space of the structure shown in the embodiment of the present invention;

[0054] Fig.10 This is a schematic diagram of parameter cluster configuration according to an embodiment of the present invention;

[0055] Fig.11 This is a schematic diagram of structured data configuration shown in an embodiment of the present invention;

[0056] Fig.12 A schematic diagram of a designer portal is shown for an embodiment of the present invention. DETAILED DESCRIPTION

[0057] The technical solution of the present invention is clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. The components of the embodiments of the present application described and shown in the accompanying drawings can be arranged and designed in various configurations. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0058] It should be noted that the defects existing in the solutions in the above-mentioned prior art are the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above-mentioned problems and the solutions proposed in the embodiments of the present application for the above-mentioned problems below should all be the contributions made by the inventor to the present application in the process of invention and creation, and should not be understood as technical contents known to technical personnel in this field.

[0059] In view of the technical problems pointed out in the background technology, the embodiments provided by the present invention are as follows:

[0060] Embodiment 1

[0061] Reference Figure 1 In an exemplary embodiment, a distributed multidisciplinary online collaborative design system includes a project space, a design space, a business modeling space, and a portal.

[0062] The project space is used to create, edit and manage design projects, and its components include: project overview module, design project internal operation module. The project overview module has the functions of creating, editing, disabling, enabling, and summarizing all design projects in the current system. When you click on the editing entry of each project, you can jump to the design project internal operation module. The submodules of the design project operation module include: project information management submodule, design process management submodule, team management submodule, and multi-scheme management submodule. The project information management submodule is used to manage the basic information of the design project; the design process management submodule is used to build the design project process. Usually, a basic design process template will be selected when the design project is created, and in this design process management submodule, it will be further modified as needed based on the instantiation object of the selected design process template. The design process management submodule is composed of at least one task node (discipline node), and the relationship between the nodes is displayed by connecting lines, or it may not be displayed (in this embodiment, it is connected by directed lines, from the task sender node to the receiver node, and in other embodiments, it can also be changed to undirected lines, or even cancel the connection); the team management submodule is used to manage the team information in the entire project: including roles, members, etc. The project team administrator can set the members of each role in this submodule. The role information in the project includes the basic project roles and the roles configured in each task node in the design process template; the multi-scheme management submodule is used to create and manage multiple parallel design schemes. Users can create multiple design schemes based on the design template in the design process management module as needed. After completing the creation of the parallel scheme, the design process of the created scheme can also be modified again, so as to adjust the design process and data interface in real time as needed.

[0063] The design space is used to provide designers with the function of carrying out online design activities. When a scheme is created in the multi-scheme management submodule in the project space, each task node in the design template will eventually be instantiated into a corresponding design space. Designers of each profession will carry out product design in their own design space and submit their own design results. Each design space will automatically exchange data according to the interface configuration of the design template, thereby realizing data interaction between various professions. Specifically, the present invention proposes a data interaction mode of a multidisciplinary online collaborative design system based on a central discipline node and a responsibility matrix. Different from the traditional mesh design space data interaction mode, the present invention adopts a data interaction mode based on a central discipline node and a responsibility matrix, so that data interaction between n sub-disciplines can be dynamically realized by configuring a data output interface and a responsibility matrix at the central discipline node, while n*(n+1) input and output data interfaces need to be created between n sub-disciplines and an overall discipline in the traditional mesh structure, which greatly reduces the number of interfaces.

[0064] The central subject node configuration mode is to define the node that decomposes the task to the downstream professional as the central subject node according to the task decomposition hierarchical relationship, and define the node that receives the task as the sub-subject node, and recursively do this layer by layer, so as to realize data interaction between multiple levels;

[0065] The data output interface is a data interaction interface defined when each central discipline node decomposes the design task to the sub-discipline node. The information defined in the interface includes: transmission data, sub-discipline node, and responsibility matrix. The transmission data type includes: parameters, parameter tables, files, and structured data. The responsibility matrix is ​​an information matrix that controls the data content received by each sub-discipline node. The responsibility matrix includes at least two dimensions, one of which is data content, which includes all data information in the data output interface, and the other dimension is the responsibility dimension, which is used to set the responsibility information of each data, including: main responsibility (generating data), knowledge (knowing data), and irrelevant (not knowing the data). There can only be one main responsibility, and the knowledge can be multiple or none. When the main responsibility is not set in a certain data entry, the central discipline node is the main responsibility. For parameters and parameter tables, the main responsible party needs to edit the required value of the data, and the knowledge professional needs to edit the actual value of the data. For files and structured data, the main responsible node needs to upload the data, and the knowledge node can view and download the data, and carry out product design based on the data. When the upper-level central subject node decomposes the design task, the design space of each sub-subject node will automatically receive and filter the input data according to the responsibility matrix, and the data received by each sub-subject node includes the main responsibility data and the known data.

[0066] When a design plan is released in a design space, the data in the design space will first be submitted to the upper central discipline node, and then automatically transferred to each sub-discipline node according to the responsibility matrix, so as to realize the automatic transmission of data. The central discipline node can set a control switch as needed. When the switch is turned on, the data can be automatically transmitted to the informed party after arriving at the central discipline node. When the switch is turned off, the data needs to be confirmed and agreed by the central discipline node before it can be transferred to the relevant discipline. In a specific design task, it usually starts from the top-level node, decomposes the design requirements layer by layer from top to bottom, and feeds back the design results layer by layer from bottom to top, and iterates in a cycle, finally achieving the coordination and consistency of the design results between the disciplines contained in all nodes of the entire system, that is, reaching the multidisciplinary feasible solution state of the entire plan.

[0067] The design space has the following specific functions: message reminder and processing, solution creation, task decomposition, and solution publishing functions, wherein the message reminder includes: receiving reminder tasks and real-time changes in input data; solution creation is used to create a design solution based on specific input after receiving a design task; task decomposition is mainly used for a design space with downstream sub-discipline nodes (i.e., the overall major), and is used to further decompose design indicators and tasks into downstream majors after conducting preliminary design based on the received tasks and input information; the publishing function is used to submit design results after completing the design task.

[0068] In the design space, for a certain design task, there is at least one version of input data (no input in the top node). The designer can create at least one solution for a certain version of input data. For each solution, its status includes: unpublished status, latest effective status, pending confirmation status, and historical effective status. When a design solution is released, it changes to the latest effective status, at which time the solution cannot be edited; when a new solution is released again for the same input, the original effective solution changes to the historical effective status, at which time the solution can only be viewed but not changed; when there is a change in the input data or there is an unpublished solution downstream, the solution changes to the pending confirmation status; when the solution in the pending confirmation status or the latest effective solution is actively withdrawn, the solution changes to the unpublished status; when the pending confirmation solution is reconfirmed, it changes to the latest effective status; the data changes include changes in parameter constraint values, increase or decrease in parameter quantity, changes in downstream implementation values, and changes in files and structured data.

[0069] The design scheme includes an upstream interaction space and a downstream interaction space. The upstream interaction space is used to receive upstream design input and return design results, and the downstream interaction space is used to decompose design requirements into sub-discipline nodes and receive design result return values.

[0070] The functions within the design space also include parameter update, parameter synchronization, and parameter verification functions, wherein parameter update is to update the parameters with the same name in all parameter tables in the upstream interaction space or the downstream interaction space, and when a parameter in a parameter table is edited, the parameter value can be updated to the parameters with the same name in other parameter tables; the parameter synchronization function is to synchronize the constraint value of a parameter in the upstream interaction space to the constraint value of the parameter with the same name in the downstream interaction space, or to synchronize the implemented value of a parameter in the downstream interaction space to the implemented value in the upstream interaction space; the parameter verification function is to automatically compare whether the implemented value of the parameter meets the constraint value requirements, and if not, an obvious prompt will be given.

[0071] Furthermore, to avoid rigid design process, the data in the design space and the downstream interactive space can be further modified based on the configuration template: the modification method includes: deleting certain data in the template, adding data, adjusting data awareness and main responsibility. The method of adding data includes adding unused data in the template, adding data in the parameter pool, and dynamically creating data, thereby realizing flexible expansion of design data.

[0072] The business modeling space is used to build, maintain and manage design templates, and its components include: dimension configuration, parameter cluster configuration, parameter symbol configuration, parameter configuration, task book configuration, file cluster configuration, file configuration, structured data cluster configuration, structured data configuration, parameter table configuration, professional configuration, task template configuration, and design process configuration module.

[0073] The dimension configuration module is used to configure various dimension information, including the name, description, type, basic unit, conversion coefficient, conversion method, etc. of the dimension. Each dimension can be configured from the basic dimensions.

[0074] The parameter cluster configuration is used to configure parameter clusters, and parameter clusters are used to display parameter information in a classified manner, with at least one level. When displayed in a parameter table, the display order of each parameter cluster will be displayed in sequence according to the order of each level in the parameter cluster.

[0075] The parameter symbol configuration is used to configure the modification symbol of each parameter.

[0076] The parameter configuration is used to configure all the parameters used. For a certain parameter, its parameter information includes: parameter name, parameter cluster, parameter type, parameter display form, dimension, remarks, constraint value, and implementation value. The parameter types include integer, enumeration, floating point, string, and rich text.

[0077] The task book configuration module is used to construct the task book through parameters, thereby realizing the itemization and parameterization of the task book.

[0078] The file cluster configuration module is used to set the classification information of the files and to perform classification management on the files.

[0079] The structured data cluster configuration module designs classification information of structured data in English, and is used for classifying and managing the structured data.

[0080] The file configuration module is used to configure all files used, and the configuration information includes: file name, file cluster, extension, and file remarks.

[0081] The structured data configuration module is used to configure the structured data information used, including the name of the structured data, header information, and state parameter information. In actual use, the name of the structured data is "configuration name"_state parameter 1_state parameter 2_state parameter n mode.

[0082] The professional configuration module is used to configure the information of each professional involved in the design.

[0083] The task template configuration module is used to configure the design node information of each discipline, including name, task description, etc.

[0084] The design process configuration module is used to configure the design process information, which is usually configured according to the design process of a certain product. The configuration method includes design process configuration based on canvas and graphic elements. The design process configuration module will automatically load the task template configured by the task template configuration module and generate a graphic tool, so that the user can drag the graphic tool corresponding to the task template into the canvas to build a design process template. The design process template is composed of at least one task node, and the relationship between the nodes is displayed by connecting lines, or it may not be displayed (in this embodiment, it is connected by directed lines, from the task sender node to the receiver node, and in other embodiments it can also be changed to undirected lines, or even the connection can be cancelled); creatively, the task template configuration method adopts the configuration mode of the aforementioned central subject node and responsibility matrix, and the relationship creation method between the central subject node and the sub-subject node includes: a creation method by creating a directed line connection, and a method by selecting to include sub-subject nodes in the central subject node.

[0085] Furthermore, the creation method of connecting by creating directed lines includes constructing a connection line from a central subject node to a sub-subject node in the canvas, thereby identifying the sub-subject nodes contained in the central subject node through the connection relationship;

[0086] Furthermore, the method of selecting to include sub-discipline nodes in the central discipline node is to select the included sub-discipline nodes in the central discipline node information design page. After the selection is completed, the connection relationship can be automatically created in the canvas to ensure the consistency between the connection relationship and the actual setting results.

[0087] Furthermore, the creation method of creating directed line connections and the creation method of selecting and including sub-discipline nodes in the central discipline node only require one operation.

[0088] Furthermore, the task template needs to set data interface information; the data interface information includes the aforementioned data output interface.

[0089] Furthermore, the template configured by the task template configuration module is only a basic process reference when creating a project in the project space. When creating a project, it will be instantiated according to the selected template and the user is allowed to make further modifications.

[0090] The portal module is used to provide information display space and task operation entrance for different types of users, including a designer portal; the portal can also include a model chief designer portal, a department director portal, and a company leader portal as needed.

[0091] The designer portal is used to receive design tasks and messages, provide designers with a design space entrance, display task information, and display task status. Designers can enter the corresponding design space by clicking on the task information-related link or button on the interface.

[0092] This system achieves the purpose of effectively organizing and managing multi-disciplinary, multi-position, and multi-scheme data, establishing a mapping relationship between data and processes, and forming an efficient multi-disciplinary online collaboration mechanism. It solves the problems of poor consistency in document changes and version updates in traditional design models, difficult data extraction, unmanageable scheme coupling relationships, separation of business processes and design data, inconvenient control of task completion, ineffective management and control of design process data, and low efficiency of communication and coordination between professions.

[0093] Embodiment 2

[0094] Based on Example 1, in order to solve the defects in the traditional solid rocket design process, a solid rocket multidisciplinary online collaborative design system case is constructed in this example with solid rocket as the implementation object to support the distributed online collaborative design of solid rockets. The system components include: project space, design space, business modeling space and portal.

[0095] The project space is used to create, edit and manage design projects, and its components include: project overview module and design project internal operation module. Figure 2 As shown, the functions include creating, editing, disabling, enabling, and summarizing all design projects in the current system. When you click on the edit entry of each project, the edit entry in this case is the project name, such as Figure 2 As shown, when you click "Rocket 1", you can jump to the internal operation module of the design project.

[0096] The submodules of the design project internal operation module include: project information management, design process management, team management, and multi-scheme management modules. Figure 3 As shown in the figure. The project information management submodule is used to manage the basic information of the design project. Figure 3 (a) as shown; the design process management submodule is used to build the design project process such as Figure 3As shown in (b), a basic design process template is usually selected when creating a design project, such as Figure 3 (b), in this embodiment, the "rocket design process template" was referenced when creating a project, and further modifications were made based on the template. This design process template contains a total of 13 nodes, including "user input", "rocket overall", "structure overall", "engine overall", etc., with a total of four levels, of which "user input" is the top level, "rocket overall" is the second level, "trajectory design", "aerodynamic design", "control overall", "structure overall", "engine overall" are the third level, and "structural calculation", "thermal protection design", "structural design", "engine structure", and "engine charge" are the fourth level. When you need to add a process node, you can drag the corresponding process node from the toolbar on the left side of the canvas, or you can delete the graphic elements already in the canvas through the right-click menu.

[0097] The team management submodule is used to manage team information in the entire project: including roles, members, etc. Figure 3 As shown in (c), the project team administrator can set the members of each role in this submodule. The role information in the project includes the basic project roles and the roles configured in each task node in the design process template, such as Figure 3 In (c), the project administrator is the management role of the entire project, and the other roles are the summary of the roles in each process node in the design process template. For example, the role of "rocket overall designer" is the role of the "rocket overall" process node, and two members "Zhang San" and "Li Si" are configured in the system.

[0098] The multi-scheme management submodule is used to create and manage multiple parallel design schemes. Users can create multiple design schemes based on the design templates in the design process management module as needed. Figure 3 As shown in (d), after completing the parallel scheme creation, the design process of the created scheme can also be modified again, so as to adjust the design process and data interface in real time as needed. Figure 3 In (d), three parallel design schemes, namely “General Scheme 1”, “General Scheme 2” and “General Scheme 3”, are created. The design process template of each parallel scheme can be modified individually to meet the needs of different design schemes. After the modification is completed, you can click the “Submit Design Task” button to pop up the corresponding setting page to send the design task.

[0099] The design space is used to provide designers with online design activities. When a solution is created in the multi-solution management submodule in the project space, each task node in the design template will eventually be instantiated into a corresponding design space. Each professional designer will carry out product design in his or her own design space and submit his or her own design results. Each design space will automatically exchange data according to the interface configuration of the design template, thereby realizing data interaction between different professions. Creatively, the present invention proposes a multidisciplinary online collaborative design method based on a central node and a responsibility matrix. Different from the traditional mesh design space data interaction mode, the present invention adopts a data interaction mode based on a central node and a responsibility matrix, such as Figure 4 As shown in the figure, this method can dynamically realize data interaction between n sub-disciplines by configuring a data output interface and responsibility matrix at the central node, while the traditional mesh structure requires the creation of n*(n+1) input and output data interfaces between n sub-disciplines and one overall discipline, which greatly reduces the number of interfaces. Figure 4 The example shown is a central node "O" and four sub-nodes. It is only necessary to configure a responsibility matrix at the central point "O" to realize data interaction between the four sub-nodes. For example, for "parameter [i]", if the known professions are "Subsystem 2" and "Subsystem 4", the central node is responsible for the parameter and proposes design requirements for the parameter. When the central point "O" updates the data, the parameter will be automatically transmitted to the two known nodes. For file [i], the main responsibility is "Subsystem 1" and the known professions are "Subsystem 3" and "Subsystem 4". After the plan is generated and released from "Subsystem 1", the file will first flow to the central point "O" and then automatically flow to "Subsystem 3" and "Subsystem 4".

[0100] The central node configuration mode is to define the node that decomposes the task to the downstream professional as the central node according to the task decomposition hierarchy, and define the node that receives the task as the child node, and recursively implement data interaction between multiple levels, such as Figure 3 (b) Design process for building a rocket with a four-layer structure;

[0101] The data output interface is a data interaction interface defined when each central node decomposes the design task to the sub-node. The information defined in the interface includes: transmission data, sub-nodes, and responsibility matrix. The transmission data types include: parameters, parameter tables, files, and structured data. The responsibility matrix is ​​an information matrix that controls the data content received by each sub-node. The responsibility matrix includes at least two dimensions, one of which is the data content, which includes all the data information in the data output interface, and the other dimension is the responsibility dimension, which is used to set the responsibility information of each data, including: main responsibility (generating data), knowledge (knowing the data), and irrelevant (not knowing the data). There can only be one main responsibility, and there can be multiple or no knowledge. When the main responsibility is not set in a data entry, the central node is the main responsibility. Figure 5 is Figure 3 The data output interface of the "Rocket Overall" process node configuration is shown. You can add various types of data to the table by clicking the buttons above. For example, when you click the "Add Mission Book" or "Add Structured Data" button, you can jump to the corresponding mission book option and structured data option page, and select the configured data items to add to the table. Files and structured data will be displayed in a hierarchical manner according to the "File Cluster" and "Structured Data Cluster", as shown below. Figure 5 The "calculation data" here refers to the "structured data cluster" of data such as "benchmark trajectory data.xls", and the "geometric model" refers to the "file cluster" of files such as "rocket body three-dimensional model.zip". Figure 5 The "Engine Development Task Book" and "Structure Development Task Book" are tabular data composed of multiple parameters, that is, structured task books, which are issued by the "Rocket General" to the "Engine General" and "Structure General" respectively. Other data, such as "Benchmark Trajectory Data.xls", are generated by the "Trajectory Design" and passed to the "Rocket General" before being transferred to the "Control General" and "Structure General". The transfer methods include automatic transfer and transfer after confirmation by the "Rocket General". It should be noted that Figure 5 The blank table means "don't care", and other symbols may be used to replace it in other embodiments.

[0102] Figure 6 yes Figure 5 In the detailed view of the "Engine Development Task Book", when you click Figure 5 The "Engine Development Task Book" will pop up Figure 6 In the editing page shown, the "Engine Development Task Book" is a data table composed of multiple parameters, which is displayed according to the defined parameter cluster classification. The parameter cluster is at least one level. For example, the "Connection Flange Diameter" has two-level parameter clusters of "Interface Requirements" and "Mechanical Interface Requirements". For each parameter, it is necessary to set the knowledge of each parameter, which can be selected through the drop-down option in the "Known Design Task" column.

[0103] When the upper-level central node decomposes the design task, the design space of each child node will automatically receive and filter the input data according to the responsibility matrix, and the data received by each child node includes the main responsibility data and the known data.

[0104] according to Figure 5 The configuration result is shown. Figure 6 , Figure 7 , Figure 8 The “rocket overall” design space, “engine overall” design space and “structure overall” design space generated for the scheme are as follows: Figure 7 In the "Rocket Overall" design space, two design plans are created based on the upstream input. When the user clicks the "Create Plan" button, a new plan can be created according to the prompts, such as "Rocket Overall Plan 2". The plan tree contains the "Interaction Space with Upstream" and the "Interaction Space with Downstream". In each space, the data includes structured task books, files, structured data, other files, and other feedback file information. The structured task book is a parameter table composed of multiple parameters, such as Figure 7 The right side shows the Figure 6 When the designer starts issuing tasks, all data in the table is empty. You need to fill in the data as needed. You can select and delete unnecessary data. You can select missing data from the configured design process template. Figure 6 Select from the table shown below. If Figure 6 If the required parameters do not exist in the table shown, you can go to Figure 5 You can select it by configuring it in

[0105] For parameters, the responsible party needs to edit the required value (constraint value) of the data and the professional needs to edit the actual value of the data. Figure 7 The "Rocket Overall" is responsible for both the "Engine Development Task Book" and the "Structure Development Task Book". You need to edit the requirement values ​​(constraint values). After editing, you can click the "Decompose Requirements" button to transfer the task and data to downstream professionals, such as Figure 8 After entering the design space, you can see the upstream data update message in the "Message Prompt" window. You can click the "Create Plan" button to create a plan. All the known and responsible data are displayed under the plan tree. For files and structured data, the responsible node needs to upload the data, and the known node can view and download the data, and carry out product design based on the data. Figure 8The overall engine designer needs to download all known data and check the "Engine Development Task Book", carry out the design according to the relevant design requirements, upload the design results such as "Engine 3D Model.zip" and "Internal Ballistic Data.csv" after completing the design, and fill in the actual values ​​in the "Engine Development Task Book". For partially met indicators such as "Engine Diameter", it will automatically indicate that the indicator is not met with a clear color.

[0106] When a design plan is released in a design space, the data in the design space will first be submitted to the upper central node, and then automatically transferred to each child node according to the responsibility matrix, thereby realizing automatic data transfer. Figure 8 When the design results are completed, click "Publish Plan" and the relevant design results will automatically flow to "Rocket Overall" and "Structure Overall". Figure 7 The "engine overall design results" can be seen in the rocket's overall design space, and you can see whether all indicators meet the requirements. Indicators that do not meet the requirements will be clearly distinguished in the interface, as shown in the figure.

[0107] After the "Engine" overall design plan is released, the data update message reminder can be seen in the "Structure Overall" design space. The structural overall designer can view the updated data and carry out the design based on the data. For structured data, when you click on the data entry, the data information can be visually displayed in the space on the right side of the result tree.

[0108] The central node can be set with a control switch as needed. When the switch is turned on, the data can be automatically transmitted to the informed party after arriving at the central node. When the switch is turned off, the data needs to be confirmed and agreed by the central node before it can be transferred to the relevant professional. Figure 7 In the "Rocket Overall" design space, you can see that the automatic transfer switch is in the "On" state. At this time, after the data reaches the "Rocket Overall", it will automatically flow to downstream disciplines such as the "Structural Overall".

[0109] In a specific design task, we usually start from the top-level node, decompose the design requirements layer by layer from top to bottom, and feedback the design results layer by layer from bottom to top, so as to finally achieve the coordination and consistency of the design results among the disciplines included in all nodes of the whole system, that is, to achieve the multidisciplinary feasible solution state of the whole scheme. Figure 3 In the design process shown, the design should start from the "User Input" node design space, then to the "Rocket Overall", and so on, and iterate in all design spaces until the design solutions are released in all design spaces to complete the design of the entire project.

[0110] The design space has specific functions including: message reminder and processing, solution creation, task decomposition, and solution publishing functions. Message reminder includes: receiving reminder tasks and real-time changes in input data. Solution creation is used to create a design solution based on specific input after receiving a design task. Task decomposition is mainly used for design spaces with downstream sub-nodes (i.e., professional overall), and is used to further decompose design indicators and tasks into downstream professions after preliminary design based on received tasks and input information. The publishing function is used to submit design results after completing a design task, such as Figure 7 shown.

[0111] In the design space, for a certain design task, the input data has at least one version (the top node has no input), and the designer can create at least one solution for a certain version of the input data. Figure 7 Based on the input from the superiors, the designers created "Rocket Overall Plan 1" and "Rocket Overall Plan 2". For each plan, its status includes: unpublished status, latest effective status, pending confirmation status, and historical effective status. Figure 7 "Rocket Overall Plan 1" and "Rocket Overall Plan 2" are in the "Effective" and "Unreleased" states respectively. Figure 8 "Engine Solution 1" and "Engine Solution 2" are in "historical effectiveness" and "unreleased status" respectively. Fig. 9 "Structural Overall Plan 1" and "Structural Overall Plan 2" are in the "historical effectiveness" and "pending confirmation" status respectively.

[0112] When a design is published, it becomes the latest effective state and cannot be edited. Figure 7 "Rocket Overall Plan 1"; when a new plan is released for the same input, the original effective plan becomes a historical effective state. At this time, the plan can only be viewed but not changed. Fig. 9 "Overall Structural Plan 1" in the above table; when the input data is changed or there is an unpublished plan in the downstream, the plan will be changed to the pending confirmation state. Fig. 9 In the "Overall Structural Plan 2", when the plan in the pending confirmation state or the latest effective plan is actively withdrawn, the plan will be changed to the unpublished state, such as Figure 8 "Engine Plan 2"; when the plan to be confirmed is reconfirmed, it is transformed into the latest effective state; the data changes include changes in parameter constraint values, increase or decrease in the number of parameters, changes in downstream implementation values, and changes in files and structured data.

[0113] The functions in the design space also include parameter update, parameter synchronization, and parameter verification functions, wherein parameter update is to update the parameters with the same name in all parameter tables in the upstream interaction space or the downstream interaction space, and when a parameter in a parameter table is edited, the parameter value can be updated to the parameters with the same name in other parameter tables, such as Figure 7 When editing the "Connection Flange Diameter" in the "Engine Development Task Book" (italics indicate that there are parameters with the same name in other tables), you can select the parameter and click the "Parameter Update" button to change the parameters with the same name in other tables to the same value;

[0114] The parameter synchronization function is to synchronize the constraint value of a parameter in the upstream interactive space to the constraint value of the parameter with the same name in the downstream interactive space, or to synchronize the implementation value of a parameter in the downstream interactive space to the implementation value in the upstream interactive space, such as Figure 8 When you select a parameter in the "Engine Development Task Book" and click the "Parameter Synchronization" button, the "Constraint Value" of the data in the table can be automatically synchronized to the parameters with the same name in each table in the downstream interactive space;

[0115] The parameter verification function automatically compares the actual value of the parameter to see if it meets the constraint value requirements. If not, an obvious prompt will be given. Figure 7 Engine Diameter parameter.

[0116] Furthermore, to avoid rigidity in the design process, the data in the design space and the downstream interactive space can be further modified based on the configuration template: the modification methods include: deleting certain data in the template, adding data, adjusting data awareness and main responsibility, such as Figure 7 As shown in the "Engine Development Task Book", each data-aware sub-node can be adjusted in real time, or by modifying Figure 5 The responsibility matrix in the design space realizes the change of the data path in the design space. The data adding method includes adding unused data in the template, adding data in the parameter pool, and dynamically creating data, thereby realizing the flexible expansion of the design data.

[0117] The business modeling space is used to build, maintain and manage design templates, and its components include: dimension configuration, parameter cluster configuration, parameter symbol configuration, parameter configuration, task book configuration, file cluster configuration, file configuration, structured data cluster configuration, structured data configuration, parameter table configuration, professional configuration, task template configuration, and design process configuration module.

[0118] The dimension configuration module is used to configure various dimension information, including the name, description, type, basic unit, conversion coefficient, conversion method, etc. of the dimension. Each dimension can be configured from the basic dimensions.

[0119] The parameter cluster configuration is used to configure parameter clusters. Parameter clusters are used to display parameter information in a classified manner. There is at least one level. When displaying in the parameter table, the display order of each parameter cluster will be displayed in sequence according to the order of each level in the parameter cluster, such as Fig.10 The figure shows a schematic diagram of the configured parameter cluster. When the parameters are displayed, they will be classified and displayed in the order of each level of parameter cluster.

[0120] The parameter symbol configuration is used to configure the modification symbol of each parameter.

[0121] The parameter configuration is used to configure all the parameters used. For a certain parameter, its parameter information includes: parameter name, parameter cluster, parameter type, parameter display form, dimension, remarks, constraint value, and implementation value. The parameter types include integer, enumeration, floating point, string, and rich text.

[0122] The task book configuration module is used to construct the task book through parameters, so as to realize the itemization and parameterization of the task book, such as Figure 6 shown.

[0123] The file cluster configuration module is used to set the classification information of the file and to classify and manage the files, which is similar to the function of the parameter cluster.

[0124] The structured data cluster configuration module is used to design classification information of structured data for classification management of structured data, which is similar to the function of parameter cluster.

[0125] The file configuration module is used to configure all files used, and the configuration information includes: file name, file cluster, extension, and file remarks.

[0126] The structured data configuration module is used to configure the structured data information used, including the name of the structured data, header information, and state parameter information, such as Fig.11 The following figure shows the "internal ballistic data" configured in the structured data configuration, including two state parameters "operating temperature" and "burning rate", as well as the other three conventional parameters used to generate header information. In actual use, the structure data name is "configuration name"_state parameter 1_state parameter 2_state parameter n mode, for example Fig.11 The internal ballistic data shown in the figure is named "Internal Ballistic Data_20_7.csv" when used, where "7" is "burning rate" and "20" is "operating temperature".

[0127] The professional configuration module is used to configure the information of each professional involved in the design.

[0128] The task template configuration module is used to configure the design node information of each discipline, including name, task description, etc.

[0129] The design process configuration module is used to configure and manage the design process information. The number of configurable design process templates is not less than 1. For the configuration of a product design process, it is usually configured according to its design process. The configuration method includes design process configuration based on canvas and graphic elements. The design process configuration module will automatically load the task template configured by the task template configuration module and generate a graphic tool, so that the user can drag the graphic tool corresponding to the task template into the canvas to build a design process template. The functions and pages are the same as Figure 3 (b) Similar to the editing page on the right, the design process template is composed of at least one task node, and the relationship between the nodes is displayed by connecting lines, or it may not be displayed (in the present embodiment, it is connected by directed lines, from the task sender node to the receiver node, and in other embodiments it may be changed to undirected lines, or even the connection may be cancelled); creatively, the task template configuration method adopts the configuration mode of the aforementioned central node and responsibility matrix, and the relationship creation method between the central node and the child nodes includes: a creation method by creating a directed line connection, and a method by selecting to include child nodes in the central node.

[0130] Furthermore, the creation method of connecting by creating directed lines includes constructing connection lines from the central node to the child nodes in the canvas, thereby identifying the child nodes contained in the central node through the connection relationship;

[0131] Furthermore, the method of selecting to include sub-nodes in the central node is: selecting the sub-nodes included in the central node information design page, and after the selection is completed, the connection relationship can be automatically created in the canvas to ensure the consistency of the connection relationship and the actual setting result.

[0132] Furthermore, the creation method of connecting by creating directed lines and the creation method of selecting and including child nodes in the central node only require one operation.

[0133] Furthermore, the task template needs to set data interface information; the data interface information includes the aforementioned data output interface, such as Figure 5 shown.

[0134] Furthermore, the template configured by the task template configuration module is only a basic process reference when creating a project in the project space. When creating a project, it will be instantiated according to the selected template and the user is allowed to make further modifications.

[0135] The portal module is used to provide information display space and task operation entrance for different types of users, including a designer portal; the portal can also include a model chief designer portal, a department director portal, and a company leader portal as needed.

[0136] The designer portal is used to receive design tasks and messages, provide designers with a design space entrance, display task information, and display task status functions, such as Fig.12 As shown in the figure, the designer can enter the design space by clicking "Rocket Overall Design" on the interface. Figure 7 shown.

[0137] Embodiment 3

[0138] Based on the same inventive concept as that of Example 1, in this example, multidisciplinary online collaborative design of solid rockets is used to introduce the collaborative design method.

[0139] The method comprises the following steps:

[0140] S1: Construct a solid rocket design process template, including: configuration dimension, configuration parameter cluster, configuration parameter, configuration task book, configuration structured data cluster, configuration file cluster, configuration structured data, configuration file, configuration specialty, configuration demonstration task template, configuration design process template. The above configurations can be carried out in sequence or according to actual business needs. The final solid rocket design process template is as follows: Figure 3 (b) as shown.

[0141] S.1.1: Configure the design process template name to "Rocket Design Process";

[0142] S1.2: Add available task templates to the canvas to form each design process node;

[0143] S1.3: Add the relationship between each design node. Set "Rocket Overall" as a child node in the "User Input" node. The connection between the two nodes will be automatically created. Similarly, build the relationship between other nodes in sequence until all relationships are completed.

[0144] S1.4: Set the data output interface of each design node, including transmission data and responsibility matrix. The transmission data is the task book, structured data, and files configured through the S1 process. If the data does not exist, you can return to the S1 process to reconfigure it, such as Figure 5 To configure the "rocket overall" output data interface, configure the output data interfaces of other process nodes in this way.

[0145] S2: Create a design project: Create a "Rocket 1 Project" in the project space according to the selected configured "Rocket Design Process".

[0146] S3: Modify the project design process template: Modify the instantiation template of the design template selected when creating the design project as needed. The modification steps are the same as S1.2 to S1.4. After the modification, the design process template is as follows Figure 3(b) as shown.

[0147] S4: Set project team information: Based on the design process template obtained in S3, you need to further set the project team information. The project team consists of various roles, each of which is a collection of the project basic role and the roles configured in each design process node. When setting the project team information, you need to add members to each role, such as Figure 3 In (c), "Zhang San" and "Li Si" are added as members to the role of "Rocket Chief Designer".

[0148] S5: Create parallel design plan [i]: Create “Overall Plan 1” based on the design process template modified from S3. Figure 3 (d)

[0149] S6: Modify the design process of parallel plan [i]: Modify the process information of "Overall Plan 1" created in S5 as needed. The modification steps are the same as S1.2 to S1.4.

[0150] S7: issuing design tasks: based on the design process obtained in S6, design tasks can be issued. When issuing design tasks, a member (at least one) who receives the tasks can be further selected from the role information set in S4. For example, when issuing the design task for the rocket master, "Zhang San" in the role of "rocket master designer" can be selected;

[0151] S8: Enter the designer portal: After the task is issued, the designer who receives the design task can enter the designer portal to see the design task. A designer can have multiple design tasks, and the designer can view the status of each task and other information. At this time, "Rocket General Designer" "Zhang San" logs in to the collaborative design platform and enters the designer portal interface as shown below. Fig.12 You can see your task information and message prompts as shown.

[0152] S9: Enter the design space: "Zhang San" clicks Fig.12 In the first task shown, "Rocket Overall Design" can enter the Rocket Overall Design space. Figure 7 As shown;

[0153] S10: Carry out scheme design: For example, "rocket overall designer" "Zhang San" can view and process the information in the design space in real time, and create "Rocket Overall Scheme 2" based on the input data passed in by the latest version of the "User Input" node. When the scheme is created, the data input by all upstream central nodes can be seen in the upstream interaction space, such as "General Requirements for Rocket Development", and the data that needs to be transmitted to each child node in the downstream interaction space. Designers can view all data in the upstream interaction space and carry out design based on the input data. If the node they are in is the end node, jump to step S14. Otherwise, continue with S11;

[0154] S11: Decomposition of design tasks: Rocket overall designers should fill in the structured task books in the downstream interactive space based on S10 and set the responsibility matrix information of each transmission data based on the template instantiation information. Data that exists in the template but is not needed temporarily can be deleted directly, or the data to be used can be selected from the template as needed. If the template cannot meet the design requirements, the design process template of "Rocket Overall Plan II" can be modified according to step S6. After completing all data entry, the task can be decomposed, and the "Decomposition Requirements" button can be clicked to send the decomposed design task to downstream "engine overall", "structure overall" and other specialties.

[0155] S12: Modify the output data in the downstream interactive space: If the designer in the "rocket overall" design space needs to adjust certain data in the downstream interactive space during the design process, he can directly modify and save it, and the downstream professionals can receive the data change information in real time. For example, when modifying the "engine diameter" in the "engine development task book", the "engine overall" design space can receive parameter change reminders in real time.

[0156] S13: View downstream design results: When the sub-node professional completes the design and publishes the design plan, the design results of each professional can be viewed in real time in the downstream interactive space. For example, when the "engine overall" completes the design plan and clicks the "publish plan" button, the "rocket overall" can see the engine plan.

[0157] S14: Forming a design plan: Based on the design results formed by the sub-nodes, further design is carried out to form a design result. If the design result formed by the sub-node cannot meet the requirements, you can return to S12 to modify the indicators until you get a satisfactory result. For example, central nodes such as "rocket overall" or "engine overall" can perform overall design based on the design plan submitted by the downstream sub-nodes to form the final design result. During the design process, it is often necessary to continuously adjust the indicator requirements. For example, the "rocket overall" can adjust the "performance indicator requirements" and other parameters in the "engine development task book", and can also increase or decrease parameters as needed. After each sub-node professional has reached an acceptable state and released the design plan, the "rocket overall" can form its own final design plan.

[0158] S15: Release the design plan: After the design process is completed, you can fill in all the data that needs to be entered in the upstream interaction space, upload the main responsible files and structured data, and directly release the design plan after checking. At this time, the plan changes to the release state. If there is a design plan for the same design input, the original design plan will be changed to the historical effective state, such as Figure 8After the "Engine Overall" completes the "Engine Plan 2", it can be released. At this time, the original "Engine Plan 1" becomes the "Historical Effective Status".

[0159] S16: Confirm the design plan: When the input data changes or there are unpublished plans downstream, the plan changes to a pending confirmation state. At this time, the designer needs to confirm the plan information again. If the plan meets the requirements of the superior, the design plan can be re-released after confirmation. If it does not meet the requirements, the plan can be withdrawn to a pending release state and return to S11 to carry out the design. For example, after the design plan of the "engine overall" is released, due to changes in the "internal ballistic data.csv" of the engine overall main responsibility, the "Structural Overall Plan 2" of the "Structural Overall" changes from "In Effect" to "Pending Confirmation". At this time, the relevant designers need to review the change data and re-evaluate whether the design plan needs to be changed. If changes are required, you can click the "Withdraw Plan" button to withdraw the plan to the "unpublished state" and redesign it. If no changes are required, just click the "Publish Plan" button to republish the design plan. In the collaborative design process of various disciplines, when several sub-nodes under the same central node publish design plans, they will affect each other's status through coupling data. For example, when the "engine overall" plan is published, it may affect the "structure overall", and vice versa. However, in the final state, when a sub-node publishes the latest plan, its main responsible data has not changed. At this time, its result has no effect on other sub-nodes at the same level. These nodes will not have a state change due to the release of the design plan by this node. Ultimately, the design plans of all sub-nodes under the central node will be in the "effective" state.

[0160] S17: Design completed: When all disciplines have completed the design and have become published, the design of the entire design project is completed. Figure 3 When all the scheme designs in the design space of each node in (b) are completed and all the schemes are in the "effective" state, the design of the entire "overall scheme one" is completed. While the design of "overall scheme one" is being carried out, the design of "overall scheme two" can also be carried out in parallel.

[0161] The above specific implementation methods are detailed descriptions of the present invention. It cannot be determined that the specific implementation methods of the present invention are limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions and substitutions can be made without departing from the concept of the present invention, which should be regarded as belonging to the protection scope of the present invention.

Claims

1. A distributed multidisciplinary online collaborative design system, characterized in that: include: Project space, used to create, edit and manage design projects, which provides a design process template consisting of at least one discipline node; Design space is used to instantiate each discipline node in the design process template into a corresponding design space. Designers of each discipline carry out product design in their own design space and submit design results. Among them, each design space adopts a data interaction mode based on the central discipline node and the responsibility matrix. By configuring a data output interface and responsibility matrix at the central discipline node, data interaction between multiple sub-disciplines can be dynamically realized. Business modeling space for building, maintaining, and managing design process templates; Portal, used to provide information display space and task operation entrance for different types of users.

2. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The project space includes a project overview module and a design project internal operation module. The functions of the project overview module include creating, editing, disabling, enabling, and summarizing all design projects in the current system. When you click on the editing entrance of each project, you can jump to the design project internal operation module; the design project internal operation module includes a project information management sub-module, a design process management sub-module, a team management sub-module and a multi-scheme management sub-module, among which the project information management sub-module is used to manage the basic information of the design project, the design process management sub-module is used to build the design project process, the team management sub-module is used to manage the team information in the entire project, and the multi-scheme management sub-module is used to create and manage multiple parallel design schemes.

3. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The relationship between the subject nodes in the design process template is displayed through connecting lines or not.

4. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The data interaction mode based on the central subject node and the responsibility matrix includes: According to the hierarchical relationship of task decomposition, the node that decomposes the task to the downstream disciplines and majors is defined as the central discipline node, and the node that receives the task is defined as the sub-discipline node, and this is done recursively layer by layer to achieve data interaction between multiple levels.

5. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The data output interface is a data interaction interface defined when each central discipline node decomposes the design task to the sub-discipline node. The information defined in the interface includes transmission data, sub-discipline nodes and a responsibility matrix; the responsibility matrix is ​​an information matrix that controls the data content received by each sub-discipline node. The transmission data type includes parameters, parameter tables, files and structured data. The responsibility matrix includes at least two dimensions, one of which is the data content, which includes all data information in the data output interface, and the other dimension is the responsibility dimension, which is used to set the responsibility information of each data.

6. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The data interaction between multiple sub-disciplines is dynamically realized by configuring a data output interface and responsibility matrix in the central discipline node, including: When a design plan is released in a design space, the data in the design space will first be submitted to the superior central subject node, and then automatically transferred to each sub-subject node according to the responsibility matrix; the central subject node is set with a control switch. When the control switch is turned on, the data can be automatically transferred to the informed party after arriving at the central subject node. When the control switch is turned off, the data needs to be confirmed and agreed by the central subject node before it can be transferred to the relevant disciplines. In a specific design task, starting from the top-level node, the design requirements are decomposed layer by layer from top to bottom, the design results are fed back layer by layer from bottom to top, and a cycle of iteration is performed to ultimately achieve coordination and consistency in the design results among the disciplines included in all nodes of the entire system, that is, to achieve a multidisciplinary feasible solution state for the entire plan.

7. The distributed multidisciplinary online collaborative design system according to claim 1, characterized in that: The business modeling space includes a dimensional configuration module, a parameter cluster configuration module, a parameter symbol configuration module, a parameter configuration module, a task book configuration module, a file cluster configuration module, a file configuration module, a structured data cluster configuration module, a structured data configuration module, a parameter table configuration module, a professional configuration module, a task template configuration module and a design process configuration module.

8. The distributed multidisciplinary online collaborative design system according to claim 7, characterized in that: The design process configuration module configures the design process based on the canvas and graphic elements, automatically loads the task template configured by the task template configuration module and generates a graphic tool, so that the user can drag the graphic tool corresponding to the task template into the canvas to build a design process template.

9. A distributed multidisciplinary online collaborative design method, used in the distributed multidisciplinary online collaborative design system according to any one of claims 1 to 8, characterized in that: include: Build, maintain and manage design process templates through the business modeling space; Create, edit and manage design projects through the project space, which provides a design process template consisting of at least one discipline node; Provide information display space and task operation entrance for different types of users through the portal; Through the design space, each discipline node in the design process template is instantiated into a corresponding design space. Designers from each discipline carry out product design in their respective design spaces and submit design results. Among them, a data interaction mode based on the central discipline node and the responsibility matrix is ​​adopted between each design space. By configuring a data output interface and responsibility matrix at the central discipline node, data interaction between multiple sub-disciplines can be dynamically realized.

10. A distributed multidisciplinary online collaborative design method according to claim 9, comprising the following steps: S1: Build a design process template through the business modeling space; S2: Create a design project through the project space: Create a design project in the project space according to the selected design process template; S3: Modify the project design process template: modify the instantiation template of the design process template selected when creating the design project as needed; S4: Set project team information: According to the design process template obtained in S3, further set the project team information; S5: Create a parallel design plan: Create a parallel design plan according to the design process template modified in S3; S6: modify the design process of the parallel design scheme: modify the process information of the parallel design scheme created in S5; S7: issuing design tasks: issuing design tasks based on the design process obtained in S6. When issuing design tasks, members who receive the tasks can be further selected from the role information set in S4. S8: Enter the designer portal: After the task is issued, the designer who receives the design task can enter the designer portal to see the design task; S9: Entering the design space: Designers enter each design space from the entrance of each task in the designer portal to carry out solution design; S10: Carry out scheme design: Designers can view and process the information in the design space in real time, and create a design scheme based on a certain version of input data. After the scheme is created, if the data input by all upstream central discipline nodes can be seen in the upstream interaction space, the data that needs to be transmitted to each sub-discipline node in the downstream interaction space. Designers can view all data in the upstream interaction space and carry out design based on the input data. If the node is the terminal node, jump to step S14, otherwise continue to S11; S11: Decompose the design task: If there are downstream sub-discipline nodes, fill in the structured task books in the downstream interactive space based on S10 and set the responsibility matrix information of each transmission data based on the template instantiation information. The data that exists in the template but is not needed temporarily can be deleted directly, or the data to be used can be selected from the template as needed. If the template cannot meet the design requirements, the design process template of the parallel solution can be modified according to step S6; After completing all data entry, the task can be decomposed, and the decomposed design task can be sent to downstream professionals; S12: Modify the output data in the downstream interactive space: If the central subject node needs to adjust a certain data in the downstream interactive space during the design process, it can be directly modified and saved, and the downstream discipline can receive the data change information in real time; S13: View downstream design results: When the sub-discipline node completes the design and releases the design plan, the design results of each discipline can be viewed in real time in the downstream interaction space. S14: Forming a design plan: Based on the design results formed by the sub-discipline nodes, further design can be carried out to form a design result; S15: Release the design plan: After the design process is completed, you can fill in all the data that needs to be entered in the upstream interaction space, upload the responsible files and structured data, and directly release the design plan after checking that they are correct; at this time, the plan changes to the release state. If there is a design plan for the same design input, the original design plan will be changed to the historical effective state; S16: Confirm the design plan: When the input data is changed or there is an unpublished plan in the downstream, the plan will be changed to the pending confirmation state. At this time, the designer needs to confirm the plan information again. If the plan meets the requirements of the superior, the design plan can be re-published after confirmation. If it does not meet the requirements, the plan can be withdrawn to the pending release state and return to S10 to carry out the design; S17: Design completed: When all disciplines have completed the design and all have become published, the design of the entire design project is completed.

Images