CN111241675A - Data-driven complex product collaborative design management method and system - Google Patents
Data-driven complex product collaborative design management method and system Download PDFInfo
- Publication number
- CN111241675A CN111241675A CN202010019186.0A CN202010019186A CN111241675A CN 111241675 A CN111241675 A CN 111241675A CN 202010019186 A CN202010019186 A CN 202010019186A CN 111241675 A CN111241675 A CN 111241675A
- Authority
- CN
- China
- Prior art keywords
- data
- version
- complex product
- management
- collaborative design
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000013461 design Methods 0.000 title claims abstract description 66
- 238000007726 management method Methods 0.000 title claims abstract description 53
- 238000000034 method Methods 0.000 claims abstract description 54
- 230000008569 process Effects 0.000 claims abstract description 39
- 238000013499 data model Methods 0.000 claims abstract description 13
- 238000012938 design process Methods 0.000 claims abstract description 12
- 230000005540 biological transmission Effects 0.000 claims abstract description 6
- 230000001419 dependent effect Effects 0.000 claims description 22
- 230000008520 organization Effects 0.000 claims description 13
- 238000011161 development Methods 0.000 claims description 7
- 238000004422 calculation algorithm Methods 0.000 claims description 6
- 238000001514 detection method Methods 0.000 claims description 6
- 238000010276 construction Methods 0.000 claims description 4
- 238000012546 transfer Methods 0.000 claims description 2
- 238000013523 data management Methods 0.000 abstract description 10
- 238000004891 communication Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 22
- 230000008859 change Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 238000004519 manufacturing process Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000010354 integration Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000011144 upstream manufacturing Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 238000011960 computer-aided design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012821 model calculation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The scheme provides a data-driven complex product collaborative design management method and a system, wherein the method comprises the following steps: describing restrictions and influences among design data based on a pre-constructed complex product collaborative design data model; based on a version management mode, the updating and the transmission of the data are managed so as to lead the data forming process to be tracked and the data state to be traced back; and managing the tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data. According to the technical scheme, an integrated environment can be provided for task management and data management, when the tasks are driven to be parallelly developed, a large number of intermediate results in the design process are effectively organized, the reusability of data is improved, the uniformity of models and parameters and the matching of the results are guaranteed, and the inter-disciplinary cross-professional communication efficiency is improved.
Description
Technical Field
The application relates to the field of data synchronization, in particular to a complex product collaborative design management method and system based on data driving.
Background
The complex product is defined as a product with complex customer requirements, complex product composition, complex product technology, complex manufacturing process and complex manufacturing management, such as a spacecraft, an airplane, an automobile, a ship, a complex electromechanical product and the like. The general scheme demonstration and innovation design process of the complex product relates to various subject technologies, requires flexible and innovative cooperative work of multidisciplinary engineers, solves the problems of multidisciplinary application integration and multidisciplinary optimization, completes rapid design and comparison analysis of different schemes, and finally forms a design result.
The innovative collaborative design of the complex product is a process of multi-scheme attempt and multi-round iteration, and the collaborative design process of the complex product has the following problems:
(1) the innovative collaborative design of the complex product is a process of multi-task parallel development, tight matching and repeated iteration, is difficult to describe by a fixed flow, manages the design process by utilizing the traditional workflow mode, is easy to cause a large number of tasks to be in a suspended state, and has low collaborative efficiency.
(2) When multiple specialties work in parallel, multiple versions of professional data can be generated, and the uniformity of a data model and the matching of results cannot be guaranteed.
Disclosure of Invention
The application provides a data-driven complex product collaborative design management method and system.
According to a first aspect of the embodiments of the present application, there is provided a data-driven complex product collaborative design management method, where the system includes:
describing restrictions and influences among design data based on a pre-constructed complex product collaborative design data model;
based on a version management mode, the updating and the transmission of the data are managed so as to lead the data forming process to be tracked and the data state to be traced back;
and managing the tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data.
In a preferred embodiment, the step of constructing the complex product collaborative design data model includes:
acquiring data generated in the collaborative design process of a complex product;
establishing mesh association between data according to the tree-shaped data classification and the mesh data association contained in the organization form of the data;
according to the organization mode of the data, the product data is organized in a tree form, and the data is hung on the product structure.
In a preferred embodiment, the mesh association comprises: data dependencies and data inheritance.
In a preferred embodiment, the step of managing the update and the transfer of the data based on the version management manner so as to make the data formation process trace and the data state backtrack includes:
when a certain task is completed in a stage, the data can form a data version at a certain time; different versions are formed during each submission, and the versions have data inheritance relationship; preferably, the mill version can be set as the master version;
when a new development work is carried out on a certain historical version, different branch labels are utilized to define the branches of different branch management;
generating a plurality of file versions when a plurality of works are carried out on the same file or model; at a certain time point, selecting and combining a plurality of file versions based on a conflict detection algorithm;
and displaying the evolution relation of the versions based on the steps so as to track the data forming process and trace the data state.
In a preferred embodiment, the steps of the method further comprise:
under the condition that a plurality of versions of achievements are simultaneously released on a certain working version, when a dependent file is selected to start a new branch, all the dependencies among the files form a dependent path;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, the branch is not allowed to be created.
According to a second aspect of the embodiments of the present application, there is provided a data-driven complex product collaborative design management system, including:
the relation description unit is used for describing the restriction and influence among the design data based on a pre-constructed complex product collaborative design data model;
the version management unit manages the updating and transmission of the data based on a version management mode so as to enable the data forming process to be tracked and the data state to be backtracked;
and the task management unit is used for managing the tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data.
In a preferred embodiment, the system further comprises:
the model construction unit is used for constructing a complex product collaborative design data model; the model construction unit specifically executes the following steps to construct the model:
acquiring data generated in the collaborative design process of a complex product;
establishing mesh association between data according to the tree-shaped data classification and the mesh data association contained in the organization form of the data;
according to the organization mode of the data, the product data is organized in a tree form, and the data is hung on the product structure.
In a preferred embodiment, the mesh association comprises: data dependencies and data inheritance.
In a preferred embodiment, the version management unit specifically executes the following steps:
when a certain task is completed in a stage, the data can form a data version at a certain time; different versions are formed during each submission, and the versions have data inheritance relationship; preferably, the mill version can be set as the master version;
when a new development work is carried out on a certain historical version, different branch labels are utilized to define the branches of different branch management;
generating a plurality of file versions when a plurality of works are carried out on the same file or model; at a certain time point, selecting and combining a plurality of file versions based on a conflict detection algorithm;
and displaying the evolution relation of the versions based on the steps so as to track the data forming process and trace the data state.
In a preferred embodiment, the task management unit specifically executes the following steps;
under the condition that a plurality of versions of achievements are simultaneously released on a certain working version, when a dependent file is selected to start a new branch, all the dependencies among the files form a dependent path;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, the branch is not allowed to be created.
Advantageous effects
According to the technical scheme, an integrated environment can be provided for task management and data management, when the tasks are driven to be parallelly developed, a large number of intermediate results in the design process are effectively organized, the reusability of data is improved, the uniformity of models and parameters and the matching of the results are guaranteed, and the inter-disciplinary cross-professional communication efficiency is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic diagram illustrating an association relationship between task management and data management according to the present embodiment;
FIG. 2 is a schematic diagram showing the data organization method according to the present scheme;
FIG. 3 is a schematic diagram showing the association relationship between data according to the present scheme;
FIG. 4 is a schematic diagram illustrating a version problem during a prior art solution demonstration process according to the present solution;
FIG. 5 shows a schematic diagram of a linear variation of the version of the present solution;
fig. 6 shows a schematic diagram of a version branch according to the present scheme;
FIG. 7 is a diagram illustrating data dependencies in the present scenario;
FIG. 8 is a schematic diagram illustrating the impermissible dependence of the present scheme;
FIG. 9 is a schematic diagram illustrating a file update dependent scheme according to the present solution;
FIG. 10 is a schematic diagram of a design task model according to an embodiment of the present disclosure;
FIG. 11 is a diagram illustrating the definition of the upstream and downstream relationships of a task according to an embodiment of the present invention;
fig. 12 is a schematic diagram illustrating a state diagram of a design task according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following further detailed description of the exemplary embodiments of the present application with reference to the accompanying drawings makes it clear that the described embodiments are only a part of the embodiments of the present application, and are not exhaustive of all embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In the prior art, a plurality of forms exist for the innovative collaborative design scheme of the complex product, such as the following: 1) adopting a data integration method based on a model, and carrying out data integration based on a unified data source aiming at the cooperation of design and design, design and manufacture, and manufacture; 2) the task coordination of the complex products based on data subscription/distribution; 3) and a data management means in the numerical calculation process of the complex product. Through research and analysis of the prior art, the schemes neglect complex dependence and restriction relations between complex product tasks and data, and are not suitable for the management and data management scene of multidisciplinary coupling tasks. Therefore, the scheme is intended to provide a data-driven complex product collaborative design management scheme, can manage and control the version change of a large amount of parallel design data, assists engineers to efficiently complete design tasks, and realizes clear traceable results. The general idea of the scheme comprises the following steps:
(1) and establishing a complex product collaborative design data model, wherein the model describes the restriction and influence relation among design data based on a product structure.
(2) The method for managing the process data version of the complex product is researched, the updating and the transmission of the data are recorded, and the tracking of the data forming process and the backtracking of the data state are realized.
(3) And modeling the restriction relationship between tasks by using the dependency relationship between data, and realizing a task management process based on data driving.
(4) A complex product task data collaborative system is developed, and verification is carried out by taking a complex product scheme demonstration of a certain research institution as an example, and the result shows that the method supports multi-professional rapid work and improves the quality and the efficiency of multi-subject collaborative design.
Specifically, the scheme provides a collaborative design management scheme of a complex product based on data driving, as shown in fig. 1, in the scheme, the process data management and the task data management processes are two closely related processes, a driving and restricting relationship between tasks is formed by utilizing a data organization relationship in a data model to form a task process model, in the task starting process, an executor acquires the latest data, executes the tasks according to the task process, and concurrently publishes the data to form a complete collaborative design data version, so that clear record of the data change process is ensured. The specific implementation process of the scheme is as follows:
1. complex product collaborative design data model
The data generated in the process of the collaborative design of the complex product comprises the following steps: structured index data, document data in various formats, computer-aided design (CAD) data, computer-aided engineering data, physical test data, and the like. The data may describe information such as function, performance, fabrication, process, structure, etc.
The organization form of the data is divided into two types of data classification of tree shape and data association of net shape. The tree-like data classification ensures that data can be stored in unique locations and accurately indexed; the mesh association of the data is established, the restriction and influence among design data are made explicit, and the data can be traced and applied more quickly.
The data organization mode is shown in fig. 2, the product structure tree is a basic organization structure of a complex product data set, and runs through the whole development process; product data is organized in a tree form from a general structure, a branch system, an assembly part to a part, and the data is hung on a product structure. In addition, the product design has different stages, such as a demand- > scheme- > detail, or a primary sample- > model and other various dividing modes. Specific data on the nodes can be positioned by means of the tree management mode of 'product structure + affiliated stage'.
There are various ways of associating mesh relationships, for example, (1) data dependency relationships, mainly referring to design data that are mutually referenced and affected, as shown in fig. 3, for example, the overall index of the system affects the design of the equipment of the subsystem, and the design of the subsystems also affects each other. Data b dependence a is noted as:
datab∝dataa
(2) the data inheritance relationship, namely the change relationship of the data version, is utilized to record the change process of the data, thereby being beneficial to clear management of multi-version data.
2. Process data version management method
For common data versioning methods, such as software configuration management, engineering databases, and engineering design data. These version control models enable evolution management of the same object over time, but they are not suitable for data management in complex engineering projects because they cannot record dependencies of different design objects. As shown in fig. 4, for example, the following scenario:
in the scheme demonstration stage, an engineer A proposes indexes, and an engineer B performs specific model calculation. In the demonstration stage of the complex product scheme, communication is mainly carried out by using a telephone and a mail, and at the moment, because the communication is not timely, the engineer A often changes the index, and the engineer B does not check the index timely, the calculation is still carried out according to the original numerical value, so that the model and the index are not unified.
The scheme performs data management by using a version management mode in software engineering. Git is the most mature distributed code management system at present, and a multi-professional version control method is formed on the basis of Git conception and aiming at the development requirements of complex products.
When an engineer completes a task in stages, the data forms a data version at a certain time.
The version submitting information comprises a submitting author, submitting time and the like, the submitted version information comprises submitted file information, the binary coded hash value of each file is stored so as to be found in time after data storage is in trouble, and the submitted version respectively comprises indexes, a test result and a model file.
As shown in fig. 5, each submission will form a different version, and the versions have data inheritance relationship, so that engineers can also tag the versions to determine a version as the master version.
As shown in fig. 6, when an engineer needs to newly develop work on a certain historical version, and when different branches are needed to manage different types and design results of different functions, the version may diverge, and the engineer may define different divergences by using different branch labels.
When different engineers work on the same file or model, the files are also forked, the two engineers need to maintain their own file versions, and the file versions are selected and combined at a certain time point.
Different bifurcated versions can be combined, and for indexes or text files, an intelligent conflict detection algorithm can be used in the combining process, so that text differences are detected, and the combination is facilitated. The git diff algorithm is used herein for collision detection and merging.
3. Dependency description between data
In addition to the evolution of versions, version management processes also need to describe data dependencies when multiple engineers work in parallel. As shown in fig. 7, engineer C performs his work on engineer a, version a2, releasing three versions of result C.
When a dependent file is selected to open a new branch, the dependence among all files also forms a dependent path, and the creation of the new branch is allowed only if the dependent path meets a certain condition. As shown in FIG. 8, if C1 relied on A2 and B1, and B1 was dependent on A3, the system would prompt that the branch is not allowed to be created.
As shown in fig. 9, the process of determining the path is as follows:
1) for the dependent path, depth-first traversal is performed to traverse all the dependent node sets, which are { B2, A3, A2} in the figure.
2) Traversing the node set, if the nodes have different versions of the same file, the dependent path is illegal, and the branch is not allowed to be created; if the nodes in the set all belong to different files, the creation is legal.
When a person discovers a change in dependent data, it may also choose to continue working on the newly generated dependent data.
The present solution is further illustrated by way of example below.
The embodiment provides a data-driven complex product collaborative design management scheme, in the complex product collaborative design process, research and development managers firstly distribute and issue tasks, engineers complete the execution and feedback of the tasks after receiving task information, in the task execution process, various types of software are used for calculation and analysis, generated periodic results are submitted, data are uniformly incorporated into a research and development process data management system for management, and the engineers can check the data change condition related to the engineers.
In the multidisciplinary collaborative design process, only a fixed flow is used, and it is difficult to describe a complete process logic, in this embodiment, an IDF0(ica definition for function modeling) method is used to form an upstream-downstream relationship between tasks by using a dependency relationship between data, so as to implement task management based on data driving.
As shown in fig. 10, the basic components of IDEF0 are composed of task and connection active edges, which are input (input), control (control), output (output) and mechanism (mechanism), respectively.
When the task process modeling is carried out, the design process of the complex product is decomposed into design tasks, and the input-output relation of each task is determined. Five-element group < I, C, O, M, s for TasktaskAnd > represents. I, C, O, M represent input, control, output and mechanism, respectively. S represents the task state. The input and output requirements satisfy the following relationship:
the dependency relationship between data needs to be embodied in the design task, as shown in the following figure, when a certain data B depends on other data C, the input of the task that yields the data B should also include the data C. Another special case is that two tasks change the same data C at the same time, where the input and output data of both tasks include data C.
As shown in fig. 11, the inputs are classified into two types, one is a necessity input and one is a referential input. The necessary input is generated by an upstream task, and the task is activated according to the sufficient condition; the referential input is input data which is generated by other tasks and has influence on the task.
Arrows represent data constraints, not flows or orders, on a design activity diagram. The design task state comprises three types of 'inactive', 'active' and 'completed'. The non-activation means that the task execution condition is not met and the starting cannot be carried out; "activated" represents that the task can be performed; completed represents that the task is completed and the data has been submitted. The transition between states is as follows:
(1) "not activated" - > "activated": when the control conditions and mechanism submissions of the tasks are both satisfied and all necessary input data is ready, the upstream engineer submits the data, the system notifies the downstream engineer to work by looking at the data dependencies, the design task is activated, and the engineer can perform the task.
(2) "activated" - > "completed": after the engineer finishes designing, submitting all output data, and marking the dependency relationship and the version integration relationship among the data.
(3) "completed" - > "activated": when the upstream data changes, the engineer can activate the completed task again, specify a new dependency relationship of the task output data at this time, and carry out design work.
As shown in FIG. 12, the tasks A and B are completed, the dotted lines represent unnecessary inputs, the unnecessary inputs after B is completed are referred to A, the inputs of A are updated, and the outputs can be updated when the input of A is in an activated state.
When two tasks change one data at the same time, after one task changes the data, the other task is activated, and after the change is confirmed, the two tasks both enter a completion state.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The present invention is not limited to the above embodiments, and any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention are included in the scope of the claims of the present invention which are filed as the application.
Claims (10)
1. A data-driven complex product collaborative design management method is characterized by comprising the following steps:
describing restrictions and influences among design data based on a pre-constructed complex product collaborative design data model;
based on a version management mode, the updating and the transmission of the data are managed so as to lead the data forming process to be tracked and the data state to be traced back;
and managing the tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data.
2. The method for managing collaborative design of a complex product according to claim 1, wherein the step of constructing the collaborative design data model of the complex product includes:
acquiring data generated in the collaborative design process of a complex product;
establishing mesh association between data according to the tree-shaped data classification and the mesh data association contained in the organization form of the data;
according to the organization mode of the data, the product data is organized in a tree form, and the data is hung on the product structure.
3. The method for collaborative design management of a complex product according to claim 2, wherein the mesh association comprises: data dependencies and data inheritance.
4. The method for managing collaborative design of a complex product according to claim 1, wherein the step of managing the update and transfer of data based on a version management manner so as to trace a data forming process and trace a data state comprises:
when a certain task is completed in a stage, the data can form a data version at a certain time; different versions are formed during each submission, and the versions have data inheritance relationship; preferably, the mill version can be set as the master version;
when a new development work is carried out on a certain historical version, different branch labels are utilized to define the branches of different branch management;
generating a plurality of file versions when a plurality of works are carried out on the same file or model; at a certain time point, selecting and combining a plurality of file versions based on a conflict detection algorithm;
and displaying the evolution relation of the versions based on the steps so as to track the data forming process and trace the data state.
5. The method for collaborative design management of a complex product according to claim 1, wherein the method further comprises the steps of:
under the condition that a plurality of versions of achievements are simultaneously released on a certain working version, when a dependent file is selected to start a new branch, all the dependencies among the files form a dependent path;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, the branch is not allowed to be created.
6. A data-driven complex product collaborative design management system, the system comprising:
the relation description unit is used for describing the restriction and influence among the design data based on a pre-constructed complex product collaborative design data model;
the version management unit manages the updating and transmission of the data based on a version management mode so as to enable the data forming process to be tracked and the data state to be backtracked;
and the task management unit is used for managing the tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data.
7. The system for collaborative design management of a complex product according to claim 6, further comprising:
the model construction unit is used for constructing a complex product collaborative design data model; the model construction unit specifically executes the following steps to construct the model:
acquiring data generated in the collaborative design process of a complex product;
establishing mesh association between data according to the tree-shaped data classification and the mesh data association contained in the organization form of the data;
according to the organization mode of the data, the product data is organized in a tree form, and the data is hung on the product structure.
8. The system for collaborative design management of a complex product according to claim 7, wherein the mesh association comprises: data dependencies and data inheritance.
9. The system for collaborative design management of a complex product according to claim 6, wherein the version management unit performs the following steps:
when a certain task is completed in a stage, the data can form a data version at a certain time; different versions are formed during each submission, and the versions have data inheritance relationship; preferably, the mill version can be set as the master version;
when a new development work is carried out on a certain historical version, different branch labels are utilized to define the branches of different branch management;
generating a plurality of file versions when a plurality of works are carried out on the same file or model; at a certain time point, selecting and combining a plurality of file versions based on a conflict detection algorithm;
and displaying the evolution relation of the versions based on the steps so as to track the data forming process and trace the data state.
10. The system for collaborative design management of a complex product according to claim 6, wherein the task management unit performs the following steps;
under the condition that a plurality of versions of achievements are simultaneously released on a certain working version, when a dependent file is selected to start a new branch, all the dependencies among the files form a dependent path;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, the branch is not allowed to be created.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019186.0A CN111241675B (en) | 2020-01-08 | 2020-01-08 | Complex product collaborative design management method and system based on data driving |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019186.0A CN111241675B (en) | 2020-01-08 | 2020-01-08 | Complex product collaborative design management method and system based on data driving |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111241675A true CN111241675A (en) | 2020-06-05 |
| CN111241675B CN111241675B (en) | 2024-01-26 |
Family
ID=70873007
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010019186.0A Active CN111241675B (en) | 2020-01-08 | 2020-01-08 | Complex product collaborative design management method and system based on data driving |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111241675B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112712338A (en) * | 2020-12-29 | 2021-04-27 | 中国航空工业集团公司西安飞机设计研究所 | Control method for issuing aircraft engineering data |
| CN113407230A (en) * | 2021-06-04 | 2021-09-17 | 中船重工奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113836206A (en) * | 2021-11-26 | 2021-12-24 | 北京世纪超星信息技术发展有限责任公司 | Cultural relic knowledge online collaborative production method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020029218A1 (en) * | 1998-09-28 | 2002-03-07 | Bentley Keith A. | System, method and computer program product for collaborative engineering using component and file oriented tools |
| CN106971289A (en) * | 2016-01-14 | 2017-07-21 | 北京仿真中心 | A kind of collaborative design method and cooperative system based on data-driven |
| CN107944123A (en) * | 2017-11-20 | 2018-04-20 | 北京宇航系统工程研究所 | A kind of multi-specialized collaborative design system and collaborative design method based on master cast |
| CN108509284A (en) * | 2018-03-08 | 2018-09-07 | 华南理工大学 | A kind of tree shaped model task management system applied to functional expression programming |
-
2020
- 2020-01-08 CN CN202010019186.0A patent/CN111241675B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020029218A1 (en) * | 1998-09-28 | 2002-03-07 | Bentley Keith A. | System, method and computer program product for collaborative engineering using component and file oriented tools |
| CN106971289A (en) * | 2016-01-14 | 2017-07-21 | 北京仿真中心 | A kind of collaborative design method and cooperative system based on data-driven |
| CN107944123A (en) * | 2017-11-20 | 2018-04-20 | 北京宇航系统工程研究所 | A kind of multi-specialized collaborative design system and collaborative design method based on master cast |
| CN108509284A (en) * | 2018-03-08 | 2018-09-07 | 华南理工大学 | A kind of tree shaped model task management system applied to functional expression programming |
Non-Patent Citations (1)
| Title |
|---|
| 殷学梅 等: "复杂产品协同设计中数据建模与驱动方法", 《计算机应用》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112712338A (en) * | 2020-12-29 | 2021-04-27 | 中国航空工业集团公司西安飞机设计研究所 | Control method for issuing aircraft engineering data |
| CN113407230A (en) * | 2021-06-04 | 2021-09-17 | 中船重工奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113407230B (en) * | 2021-06-04 | 2023-09-29 | 中船奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113836206A (en) * | 2021-11-26 | 2021-12-24 | 北京世纪超星信息技术发展有限责任公司 | Cultural relic knowledge online collaborative production method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111241675B (en) | 2024-01-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Königs et al. | Tool integration with triple graph grammars-a survey | |
| CN111241675B (en) | Complex product collaborative design management method and system based on data driving | |
| US9489654B2 (en) | Artificial intelligence system and method for processing multilevel bills of materials | |
| Demuth et al. | Designspace: an infrastructure for multi-user/multi-tool engineering | |
| US8204723B2 (en) | Enterprise multi-program process development and integration process | |
| CN105719126B (en) | system and method for scheduling Internet big data tasks based on life cycle model | |
| US10613522B2 (en) | Templates in a multidisciplinary engineering system | |
| CN112487648B (en) | Multi-dimensional structured data creation method based on aerospace product features | |
| Brodsky et al. | Decision guidance analytics language (DGAL)-toward reusable knowledge base centric modeling | |
| Schwägerl et al. | Towards the integration of model-driven engineering, software product line engineering, and software configuration management | |
| Blumöhr et al. | Variant configuration with SAP | |
| Büscher et al. | Semantic information modelling for factory planning projects | |
| CN113379368A (en) | Project matrix management method and device | |
| Demuth et al. | Efficient detection of inconsistencies in a multi-developer engineering environment | |
| US20160162607A1 (en) | Model for Managing Variations in a Product Structure for a Product | |
| Elgh | Supporting management and maintenance of manufacturing knowledge in design automation systems | |
| Krenczyk et al. | Production planning and scheduling with material handling using modelling and simulation | |
| Zadeh et al. | Service oriented integration of distributed heterogeneous IT systems in production engineering using information standards and linked data | |
| Krenczyk et al. | Integration of scheduling and discrete event simulation systems to improve production flow planning | |
| CA2950468A1 (en) | Model for managing variations in a product structure for a product | |
| Patricia et al. | Process-service interactions using a SOA-BPM-based methodology | |
| Schwägerl et al. | Realizing a conceptual framework to integrate model-driven engineering, software product line engineering, and software configuration management | |
| CN113139022B (en) | Enterprise logistics data on-demand fusion method based on mixing rule | |
| Cicchetti et al. | Decoupling web application concerns through weaving operations | |
| Conery et al. | Rule-based workflow management for bioinformatics |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |