CN111241675B - Complex product collaborative design management method and system based on data driving - Google Patents
Complex product collaborative design management method and system based on data driving Download PDFInfo
- Publication number
- CN111241675B CN111241675B CN202010019186.0A CN202010019186A CN111241675B CN 111241675 B CN111241675 B CN 111241675B CN 202010019186 A CN202010019186 A CN 202010019186A CN 111241675 B CN111241675 B CN 111241675B
- Authority
- CN
- China
- Prior art keywords
- data
- version
- model
- complex product
- management
- 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.)
- Active
Links
- 238000013461 design Methods 0.000 title claims abstract description 62
- 238000007726 management method Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 claims abstract description 48
- 230000008569 process Effects 0.000 claims abstract description 40
- 238000013499 data model Methods 0.000 claims abstract description 13
- 238000012938 design process Methods 0.000 claims abstract description 13
- 230000001419 dependent effect Effects 0.000 claims description 21
- 230000008520 organization Effects 0.000 claims description 13
- 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 5
- 238000012360 testing method Methods 0.000 claims description 4
- 238000013523 data management Methods 0.000 abstract description 10
- 238000004891 communication Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 20
- 230000008859 change Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 238000004519 manufacturing process 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
- 238000013459 approach Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000011960 computer-aided design Methods 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
- 230000004913 activation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission 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
- 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
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
Abstract
The scheme provides a complex product collaborative design management method and system based on data driving, wherein the method comprises the following steps: describing constraints and influences among design data based on a pre-constructed complex product collaborative design data model; based on version management mode, updating and transferring data are managed so as to trace the data forming process and trace the data state; and managing the tasks by using 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, a large number of intermediate results in the design process are effectively organized while the task is driven to be carried out in parallel, the reusability of data is improved, the uniformity of a model, the consistency of parameters and the matching of results are guaranteed, and the multi-disciplinary cross-specialty 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 products are defined as products such as spacecraft, aircraft, automobiles, ships, complex electromechanical products and the like, wherein the products have complex customer requirements, complex product composition, complex product technology, complex manufacturing flow and complex manufacturing management. The general scheme demonstration and innovation design process of the complex product relates to a plurality of disciplinary technologies, and a multidisciplinary engineer is required to flexibly and innovately cooperate to solve the problems of multidisciplinary application integration and multidisciplinary optimization, complete rapid design and comparison analysis of different schemes, and finally form a design result.
The innovative collaborative design of the complex product is a multi-scheme trial and multi-round iteration process, and the collaborative design process of the complex product has the following problems:
(1) The complex product innovation collaborative design is a process of multi-task parallel development, tight fit and repeated iteration, is difficult to describe by using a fixed flow, utilizes a traditional workflow mode to manage the design process, easily causes a large number of tasks to be in a suspended state, and has low collaborative efficiency.
(2) When multiple professions work in parallel, multiple versions of professional data can be generated, and the uniformity of a data model and the matching performance of a result can not be guaranteed.
Disclosure of Invention
The application provides a complex product collaborative design management method and system based on data driving.
According to a first aspect of embodiments of the present application, there is provided a data-driven complex product collaborative design management method, the system including:
describing constraints and influences among design data based on a pre-constructed complex product collaborative design data model;
based on version management mode, updating and transferring data are managed so as to trace the data forming process and trace the data state;
and managing the tasks by using 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 the complex product;
establishing mesh association between data according to tree-like data classification and 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 dependency relationships and data inheritance relationships.
In a preferred embodiment, the step of managing the updating and transferring of the data based on the version management manner to trace the data forming process and trace the data state back includes:
completing a task in stages, the data will form a data version at a certain time; different versions are formed when each submission is performed, and data inheritance relations are arranged among the versions; preferably, a certain version may be set as a master version;
when a certain historical version is newly developed to work, different branch labels are utilized to define branches of different branch management;
when a plurality of works are carried out on the same file or model, a plurality of file versions are generated; at a certain point in time, selecting to combine multiple file versions based on a conflict detection algorithm;
and displaying the evolution relation of the version based on the steps so as to trace the data forming process and trace the data state.
In a preferred embodiment, the steps of the method further comprise:
when a new branch is opened to a dependent file, all the dependencies among the files form a dependent path under the condition that the achievements of a plurality of versions are issued on a certain working version at the same time;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, then this branch is not allowed to be created.
According to a second aspect of embodiments of the present application, there is provided 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 design data based on a pre-constructed complex product collaborative design data model;
the version management unit is used for managing the updating and transferring of the data based on a version management mode so as to trace the data forming process and trace the data state;
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 performs the steps of constructing the model:
acquiring data generated in the collaborative design process of the complex product;
establishing mesh association between data according to tree-like data classification and 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 dependency relationships and data inheritance relationships.
In a preferred embodiment, the version management unit specifically performs the following steps:
completing a task in stages, the data will form a data version at a certain time; different versions are formed when each submission is performed, and data inheritance relations are arranged among the versions; preferably, a certain version may be set as a master version;
when a certain historical version is newly developed to work, different branch labels are utilized to define branches of different branch management;
when a plurality of works are carried out on the same file or model, a plurality of file versions are generated; at a certain point in time, selecting to combine multiple file versions based on a conflict detection algorithm;
and displaying the evolution relation of the version based on the steps so as to trace the data forming process and trace the data state.
In a preferred embodiment, the task management unit specifically performs the following steps;
when a new branch is opened to a dependent file, all the dependencies among the files form a dependent path under the condition that the achievements of a plurality of versions are issued on a certain working version at the same time;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, then this 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, a large number of intermediate results in the design process are effectively organized while the task is driven to be carried out in parallel, the reusability of data is improved, the uniformity of a model, the consistency of parameters and the matching of results are guaranteed, and the multi-disciplinary cross-specialty 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 embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
FIG. 1 is a schematic diagram showing the association between task management and data management according to the present solution;
FIG. 2 is a schematic diagram of the data organization of the present scheme;
FIG. 3 is a schematic diagram showing the association relationship between data according to the present embodiment;
FIG. 4 shows a schematic diagram of version issues in a prior art scenario demonstration process described in this scenario;
FIG. 5 shows a schematic diagram of a linear variation of the version of the solution;
FIG. 6 shows a schematic diagram of the version branch of the present solution;
FIG. 7 is a schematic diagram of the data dependency relationship of the present approach;
FIG. 8 shows a schematic diagram of the impermissible manner of dependency of the present approach;
FIG. 9 is a schematic diagram of a dependent file update according to the present approach;
FIG. 10 shows a schematic diagram of a design task model according to an embodiment of the present solution;
FIG. 11 is a schematic diagram of a task upstream and downstream relationship definition according to an embodiment of the present disclosure;
fig. 12 shows a schematic diagram of a design task state diagram according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following detailed description of exemplary embodiments of the present application is given with reference to the accompanying drawings, and it is apparent that the described embodiments are only some of the embodiments of the present application and not exhaustive of all the embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
There are many forms of innovative co-design for complex products in the prior art, 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 coordination of design and design, design and manufacture; 2) Complex product task collaboration based on data subscription/release; 3) And a data management means in the complex product numerical calculation process. Through research and analysis of the prior art, the schemes ignore complex dependency and restriction relation between complex product tasks and data, and are not suitable for the management and data management scenes of multidisciplinary coupling tasks. Therefore, the scheme aims to provide a complex product collaborative design management scheme based on data driving, and the scheme can manage and control version changes of a large amount of parallel design data, assist engineers to efficiently complete design tasks and realize clear and traceable results. The general idea of the scheme comprises:
(1) And establishing a complex product collaborative design data model, wherein the model describes constraint and influence relation among design data based on a product structure.
(2) The complex product process data version management method is researched, the update and transmission of data are recorded, and the tracking of the data forming process and the backtracking of the data state are realized.
(3) And modeling constraint relations among tasks by utilizing the dependency relations among the data, and realizing a task management process based on data driving.
(4) The complex product task data cooperative system is developed, and verification is carried out by taking complex product scheme demonstration of a research institute as an example, so that the result shows that the method supports multi-major rapid work and improves multi-disciplinary cooperative design quality and design efficiency.
Specifically, the scheme provides a complex product collaborative design management scheme based on data driving, as shown in fig. 1, in the scheme, a process data management process and a task data management process are two closely related processes, a driving and restriction relationship between tasks is formed by utilizing a data organization relationship in a data model, a task process model is formed, an executor acquires latest data in a task starting process, executes the tasks according to the task process, and issues data to form a complete collaborative design data version, so that clear record of a 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 complex product co-design process includes: structured index data, various formats of document data, computer Aided Design (CAD) data, computer aided engineering data, and physical test data, etc. The data may describe information about the function, performance, manufacture, process, structure, etc.
The organization form of the data is divided into two types of tree-shaped data classification and mesh-shaped data association. The tree-like data classification ensures that the data can be stored in unique locations and accurately indexed; establishing a mesh association of data, making constraints and effects between design data dominant, will enable data to be traced back and applied more quickly.
The data organization mode is shown in fig. 2, and 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 tree form from overall structure, subsystem, assembly to part, hanging the data on the product structure. In addition, the product design has different stages, such as a plurality of dividing modes of requirement- > scheme- > detail or initial sample- > model and the like. Specific data on the nodes can be located by means of a tree management mode of 'product structure + belonging stage'.
Mesh association may be performed in various ways, for example, (1) data dependency may refer mainly to design data that is referred to and affected by each other, as shown in fig. 3, for example, the overall index of the system may affect the design of the devices of the subsystem, and the design between subsystems may also affect each other. Data b is written as dependent on a:
data b ∝data a
(2) The data inheritance relationship, namely the change relationship of the data version, is used for recording the change process of the data, and is beneficial to the clear management of the 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 versioning models implement evolution management of the same object over time, but none of them is suitable for data management in complex engineering design projects, as they cannot record the dependencies of different design objects. As shown in fig. 4, for example, the following scenario:
in the scheme demonstration stage, an engineer A presents indexes, and a specific model calculation is performed by an engineer B. In the demonstration stage of complex product schemes, communication is mainly carried out by telephone and mail, at the moment, due to untimely communication, an engineer A changes indexes and an engineer B does not look over in time, and calculation is carried out according to the original numerical values, so that the models and indexes are not unified.
The scheme is used for carrying out data management by referring to 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 according to the development requirements of complex products on the basis of Git concept.
An engineer performs a task on a periodic basis, and the data forms a version of the data at a time.
The primary version submitting information comprises submitted authors, submitting time and the like, the submitted version information comprises submitted file information, and a hash value of binary codes of each file is stored so as to be timely found after a problem occurs in data storage, and the current submitted version respectively comprises an index, a test result and a model file.
As shown in fig. 5, each submission will form a different version, and the versions have a data inheritance relationship, and the engineer may tag the versions to determine that a certain version is the main version.
As shown in fig. 6, when an engineer needs to newly perform work on a certain historical version, and different branches are required to manage different types and different functional design results, the version may be bifurcated, and the engineer may define different bifurcation by using different branch labels.
When different engineers work on the same file or model, bifurcation occurs, and both parties need to keep own file versions, and select the merged file version at a certain time point.
Different bifurcated versions can be combined, and for either the index or the text file, the combining process can use an intelligent conflict detection algorithm to detect text differences and assist in combining. The gitdiff algorithm is used herein for collision detection and merging.
3. Dependency description between data
In addition to the evolution of versions, the version management process also requires description of data dependencies when multiple operators work in parallel. As shown in fig. 7, engineer C performs its own work on version A2 of engineer a, releasing three versions of result C.
When a new branch is opened by selecting a dependent file, all the dependencies among the files also form 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 depends on A2 and B1, and B1 is A3, the system will suggest that this branch is not allowed to be created.
As shown in fig. 9, the process of judging the path is as follows:
1) For the dependent paths, a depth-first traversal is performed, traversing out all the dependent node sets, in the illustration { B2, A3, A2}.
2) Traversing the node set, if different versions of the same file exist in the node, the dependency path is illegal, and the branch is not allowed to be created; if the nodes in the collection are all classified as different files, then this time a legal is created.
When a person finds a dependent data change, 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 complex product collaborative design management scheme based on data driving, in the complex product collaborative design process, research and development management personnel firstly carry out task allocation and issuing, engineers receive task information and then complete task execution and feedback, in the task execution process, various software is used for carrying out calculation and analysis, produced staged 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, it is difficult to describe complete process logic only by using a fixed flow, in this embodiment, an IDF0 (Icam definition for function modeling) -based 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 that respectively input (input), control (control), output (output), and mechanism (mechanism).
When the task process modeling is carried out, the complex product design process is decomposed into design tasks, and the input-output relation of each task is defined. Five-tuple for Task design<I,C,O,M,s task >And (3) representing. I, C, O, M represent input, control, output and mechanism, respectively. S represents the task state. The input/output needs to satisfy the following relationship:
the dependency relationship between data needs to be embodied in a design task, and when a certain data B depends on other data C, as shown in the following figure, the input of the task that produces 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 both the input and output data of the two tasks include data C.
As shown in fig. 11, the inputs are divided into two types, one is a necessity input and the other is a referential input. The necessity input is generated by an upstream task, and the task is activated fully; the reference input is input data generated by other tasks and has influence on the task.
On the design activity diagram, arrows represent data constraints, and not streams or sequences. The design task state comprises three types of 'non-activated', 'completed'. The non-activation means that the task execution condition is not satisfied and cannot be started; "activated" means that the task can be performed; completed represents that the task is completed and the data has been submitted. The transition process between the states is as follows:
(1) "inactive" - > "activated": when the control conditions and mechanism submission of the task are satisfied and all necessary input data are also ready, the upstream engineer submits the data, the system informs the downstream engineer to perform work by checking the data dependency relationship, the design task is activated, and the engineer can execute the task.
(2) "activated" - > "completed": after the engineering is finished, submitting all output data, and marking the dependency relationship and version integration relationship among the data.
(3) "completed" - > "activated": when the upstream data change, the engineer can activate the completed task again, designate the new dependency relationship of the output data of the task, and develop design work.
As shown in FIG. 12, tasks A and B are completed, unnecessary inputs are represented by dotted lines, the unnecessary inputs after completion of B are referenced to A, the inputs of A are updated, and the inputs enter an activated state, and the outputs can be updated.
When two tasks change data at the same time, one task is activated after changing the data, and after confirming the change, the two tasks enter a finished 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 foregoing is illustrative of the present invention and is not to be construed as limiting thereof, but rather as providing for the use of additional embodiments and advantages of all such modifications, equivalents, improvements and similar to the present invention are intended to be included within the scope of the present invention as defined by the appended claims.
Claims (4)
1. The complex product collaborative design management method based on data driving is characterized by comprising the following steps:
describing constraints and influences among design data based on a pre-constructed complex product collaborative design data model;
based on version management mode, updating and transferring data are managed so as to trace the data forming process and trace the data state;
managing tasks by using a constraint relation model between tasks constructed according to the dependency relation between data;
the construction step of the complex product collaborative design data model comprises the following steps:
acquiring data generated in the collaborative design process of the complex product;
establishing mesh association between data according to tree-like data classification and mesh data association contained in the organization form of the data;
according to the organization mode of the data, organizing the product data in a tree form, and hanging the data on a product structure;
the mesh association includes: data dependency relationships and data inheritance relationships;
the step of managing the updating and transferring of the data based on the version management mode so as to trace the data forming process and trace the data state comprises the following steps:
completing a task in stages, the data will form a data version at a certain time; different versions are formed when each submission is performed, and data inheritance relations are arranged among the versions; setting a certain version as a main version;
the version at the time of submission comprises indexes, test results and model files;
when a certain historical version is newly developed to work, different branch labels are utilized to define branches of different branch management;
when a plurality of works are carried out on the same file or model, a plurality of file versions are generated; at a certain point in time, selecting to combine multiple file versions based on a conflict detection algorithm;
and displaying the evolution relation of the version based on the steps so as to trace the data forming process and trace the data state.
2. The complex product collaborative design management method according to claim 1, further comprising the steps of:
when a new branch is opened to a dependent file, all the dependencies among the files form a dependent path under the condition that the achievements of a plurality of versions are issued on a certain working version at the same time;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, then this branch is not allowed to be created.
3. A data-driven complex product collaborative design management system, comprising:
the relation description unit is used for describing the restriction and influence among design data based on a pre-constructed complex product collaborative design data model;
the version management unit is used for managing the updating and transferring of the data based on a version management mode so as to trace the data forming process and trace the data state;
the task management unit is used for managing tasks by utilizing a constraint relation model between the tasks constructed according to the dependency relation between the data;
the model construction unit is used for constructing a complex product collaborative design data model; the model construction unit specifically performs the steps of constructing the model:
acquiring data generated in the collaborative design process of the complex product;
establishing mesh association between data according to tree-like data classification and mesh data association contained in the organization form of the data;
according to the organization mode of the data, organizing the product data in a tree form, and hanging the data on a product structure;
the mesh association includes: data dependency relationships and data inheritance relationships;
the version management unit specifically executes the following steps:
completing a task in stages, the data will form a data version at a certain time; different versions are formed when each submission is performed, and data inheritance relations are arranged among the versions; setting a certain version as a main version;
the version at the time of submission comprises indexes, test results and model files;
when a certain historical version is newly developed to work, different branch labels are utilized to define branches of different branch management;
when a plurality of works are carried out on the same file or model, a plurality of file versions are generated; at a certain point in time, selecting to combine multiple file versions based on a conflict detection algorithm;
and displaying the evolution relation of the version based on the steps so as to trace the data forming process and trace the data state.
4. The complex product collaborative design management system according to claim 3, wherein the task management unit specifically performs the steps of;
when a new branch is opened to a dependent file, all the dependencies among the files form a dependent path under the condition that the achievements of a plurality of versions are issued on a certain working version at the same time;
if the dependent path meets the preset condition, allowing the creation of the new branch; if not, then this 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 CN111241675A (en) | 2020-06-05 |
| CN111241675B true 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) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112712338B (en) * | 2020-12-29 | 2022-11-18 | 中国航空工业集团公司西安飞机设计研究所 | Control method for issuing aircraft engineering data |
| CN113407230B (en) * | 2021-06-04 | 2023-09-29 | 中船奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113836206B (en) * | 2021-11-26 | 2022-03-15 | 北京世纪超星信息技术发展有限责任公司 | Cultural relic knowledge online collaborative production method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7194489B2 (en) * | 1998-09-28 | 2007-03-20 | Bentley Systems Incorporated | System, method and computer program product for collaborative engineering using component and file oriented tools |
-
2020
- 2020-01-08 CN CN202010019186.0A patent/CN111241675B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
|---|
| 复杂产品协同设计中数据建模与驱动方法;殷学梅 等;《计算机应用》;第38卷(第10期);第1-3部分 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111241675A (en) | 2020-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240086036A1 (en) | User Interface to Prepare and Curate Data for Subsequent Analysis | |
| US10838975B2 (en) | User interface to prepare and curate data for subsequent analysis | |
| CN111241675B (en) | Complex product collaborative design management method and system based on data driving | |
| Königs et al. | Tool integration with triple graph grammars-a survey | |
| US9489654B2 (en) | Artificial intelligence system and method for processing multilevel bills of materials | |
| CN105719126B (en) | system and method for scheduling Internet big data tasks based on life cycle model | |
| Auer et al. | A versioning and evolution framework for RDF knowledge bases | |
| US8204723B2 (en) | Enterprise multi-program process development and integration process | |
| Demuth et al. | Designspace: an infrastructure for multi-user/multi-tool engineering | |
| CN104966239A (en) | Intelligent underwriting platform based on rule engine | |
| JP2013529814A (en) | Processing related datasets | |
| El-Saber et al. | BPMN formalization and verification using Maude | |
| 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 | |
| CN112487648B (en) | Multi-dimensional structured data creation method based on aerospace product features | |
| CN113407230B (en) | Intelligent main model management system based on data driving | |
| Schwägerl et al. | Realizing a conceptual framework to integrate model-driven engineering, software product line engineering, and software configuration management | |
| Conery et al. | Rule-based workflow management for bioinformatics | |
| Sporer et al. | Resilient interface design for safety-critical embedded automotive software | |
| Dong et al. | Research and Application of CAD/CAE Integration for Nuclear Power Equipment Design | |
| Pereira et al. | The Adoption of 4Step-Rule-Set Method for Ontological Design: Application in a Real Industrial Project | |
| Westfechtel | Graph-based product and process management in mechanical engineering | |
| Ortiz et al. | Towards the boundary of concurrency | |
| Capra et al. | Encoding Nets-Within-Nets in Maude | |
| CN112579680A (en) | Data bus and data integration device and method |
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 |