Intelligent main model management system based on data driving
1. An intelligent main model management method based on data driving is characterized by comprising the following steps:
s1, logging in the system by using a login interface;
and S2, after logging in the system by using the login interface, performing corresponding operation in the system.
2. The intelligent master model management method based on data driving according to claim 1, wherein the step S2 comprises the following steps:
s21, submitting a data packet: the upstream data packet version according to which needs to be specified; and each time of data submission operation triggers one version update;
s22, carrying out data approval on the professional data packet:
s23, performing pedigree management on the professional data package:
s24, performing professional collaboration;
the data submission operation can simultaneously comprise a plurality of objects, and the operation mode can be one of addition, modification, deletion and renaming or any combination;
the object includes: files and/or directories;
the directory includes: model and/or professional data packages;
the version update includes: the end of the version number of the operation object is +1, and simultaneously, the version numbers of all the upper-level directories are also + 1.
3. The method for managing an intelligent master model based on data driving according to claim 2, wherein the S21 further comprises:
the locking-unlocking mechanism is adopted: the object needs to be locked before the version is updated, and the locked object can allow other people to submit a new version only after being unlocked; the locking and unlocking operations are performed manually or automatically; if only one person has the write authority, the writing is automatically locked when the writing is submitted; and when the submission is successful, the system is automatically unlocked.
4. The intelligent master model management method based on data driving according to claim 2, wherein the S22 includes:
s2-1, judging whether the submitted upstream data packet of the professional data packet is valid; if the approval state of the upstream data packet is invalid, the submitted professional data packet is invalid and cannot enter the approval process; if the approval state of the upstream data packet is valid or in approval, entering an approval process and executing the next step;
s2-2, judging whether the data packets are professional data packets of the same specialty, if so, selecting the same approval process;
s2-3, judging whether the submitted data belong to the data which need not to be examined and approved; if not, the user submitting the data can select the approval process; the approval process is specified by a data area administrator for a specialty.
5. The intelligent master model management method based on data driving according to claim 2, wherein the S23 includes:
s3-1, judging whether the version of the professional data packet is valid; if yes, the system automatically judges the change of the technical state;
s3-2, judging whether the technical states of the professional data packets at the upstream of the professional data packets are all latest, and establishing the latest effective version of the professional data packets based on the latest effective version at the upstream; the technical state of the professional data packet is the latest;
s3-2, judging whether the technical state of the professional data packet is outdated, if so, judging that the technical states of the downstream professional data packets are outdated;
s3-3, judging whether the technical state of the professional data packet is to be updated, if so, setting the technical state of the professional data packet as to be updated;
and S3-4, judging whether the technical state of the professional data packet belongs to the state change from outdated to the latest state, if so, automatically setting the technical states of all the downstream professional data packets to be outdated.
6. The intelligent master model management method based on data driving according to claim 2, wherein the S24 includes:
s4-1, creating a collaborative data area:
s4-2, multi-professional collaboration:
s4-3, the client acquires data:
s4-4, the client submits data;
s4-5, checking the technical state;
the S4-5 comprises:
s4-5-1, lineage tracing: a designer selects a data packet, designates any version, views pedigree information of upstream and downstream, and can trace any multiple layers;
s4-5-2, technical state consistency check: the designer labels the three technical states, either on the directory tree or on the lineage view.
7. The intelligent master model management method based on data driving according to claim 6, wherein the S4-1 comprises:
s4-1-1, creating a data area: the data area administrator performs data area initialization work, which includes: editing a directory structure of the data area, defining one or any combination of professionals needing to cooperate and personnel joining participating in the project in the data area;
s4-1-2, creating a main model: a data area administrator introduces a master model template from the outside to perform master model initialization work, where the master model initialization work includes: modifying main model information, modifying a directory structure, modifying a data package pedigree, and specifying one or any combination of data package responsible persons;
or/and the S4-2 comprises: the three professional data packet pedigree relations are as follows: the first professional data packet is an upstream data packet of the second professional data packet, the second professional data packet is positioned at the downstream of the first professional data packet, and the third professional data packet is positioned at the downstream of the second professional data packet;
s4-2-1, professional data packet initialization:
initializing a main model: a data area administrator establishes and initializes a main model, wherein the main model comprises editing and modifying a directory structure and/or a professional data packet of the main model, and the default initial version number is 1;
starting a main model: the data area administrator starts the main model, at the moment, all the version states are set to be effective, and the technical state is set to be latest;
s4-2-2, updating the professional data packet normally:
updating a first professional data packet: a first designer uploads a new professional data packet, the version is unchanged, and the version state is automatically set to be invalid; since the change is an invalid version, the state of the technology is unchanged; then entering an approval process, after approval is passed, setting the version +1 and the approval state as valid, and changing the technical state into valid because no upstream data packet exists;
since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
updating the second professional data packet: uploading a new second professional data packet by a second designer, selecting the version of the first professional data packet as V2, and carrying out an approval process without review; the system sets the version of the uploaded second professional data packet as V3, sets the version state as effective and sets the technical state as latest; the second professional data packet issues a new version, and the first professional data packet and the second professional data packet at the upstream of the second professional data packet are in the latest state, so that the technical state of the third professional data packet is automatically set to be updated;
updating a third professional data packet: uploading a new third professional data packet, and simultaneously selecting the first professional data packet version based on upstream as V2, the second professional data packet version as V3 and the approval process as 'no review'; the system sets the version of the uploaded second professional data packet as V3, sets the version state as effective and sets the technical state as latest;
s4-2-3, revoking the published data:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
invalid updating: the first designer manually sets the latest version V2 of the first professional data packet as invalid, the technical state is not changed, but the corresponding version is changed from V2 to V1; since the latest state of the first professional data packet is changed from the V2 version to the V1 version, and the latest valid version V1 of the second professional data packet is designed based on the overall V1 version, the technical state is automatically restored to the latest state; the technical state of the third professional data packet is recovered to be the latest as the second professional data packet;
s4-2-4, without updating the statement:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
no change is needed: the updated content of the first professional data packet has no influence on the design of the second professional data packet, and does not need to be changed, a second designer does not need to change a statement in the system, and the examination and approval process is carried out again, and the updated technical state is automatically set to be the latest after passing; after the second professional data packet is approved, the version is synchronously updated to V2, and the content is unchanged;
s4-2-5, feeding back messages to upstream:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
feedback information: the updated content of the first professional data packet can cause that the performance of the second professional data packet cannot be met, the new version of the first professional data packet is fed back in a version annotation mode, and the new version of the second professional data packet can also be fed back after the corresponding calculation data of the second professional data packet is submitted; after the first designer sees the feedback message, the first professional data packet is readjusted, and a new version is uploaded; the second designer redesigns from the new version of the first specialized data package.
8. The intelligent master model management method based on data driving according to claim 6, wherein the S4-3 comprises:
s4-3-1, synchronizing remote data: the designer creates a local catalog, synchronizes the content of the remote data area to the local by using a client tool, and can also inquire and download data of any historical version;
s4-3-2, browsing the query data: the designer can perform any operation of keyword query, attribute query and parameter value query in any directory of the data area, can preview data files of specific types of TXT or/and PDF, and can perform online drawing display on parameters.
9. The intelligent master model management method based on data driving according to claim 6, wherein the S4-4 comprises:
s4-4-1, submitting local data: a designer submits a file or a directory, and if the system judges that the file or the directory conflicts with the remote latest version, the file or the directory is uploaded after the conflict is manually solved; during uploading, updating based on which version is required to be specified, and then an approval process is selected; at this time, the state of the new version is defaulted to be invalid;
the auditor examines and approves the submitted data, and the version state is set to be valid after the auditor passes the approval;
s4-4-2, updating the technical state: the determination of the technical state is carried out automatically by the system.
10. An intelligent master model management system based on data driving, comprising:
a collaborative data area, a main model, a pedigree relationship, a professional data package and data items;
the cooperative data area includes: basic information of model projects and project teams, wherein a collaborative data area corresponds to one model project and comprises a plurality of main models in different design stages;
the project team comprises project personnel, project roles and project authorities;
the main model includes: basic information, pedigree relationship and professional role of the model scheme; one main model corresponds to one model scheme, and one main model comprises a plurality of professional data packets;
the pedigree relationship is used for representing the upstream and downstream relationship of the professional data package, and the main model drives the design activity through the pedigree relationship; one master model corresponds to a set of pedigree relationships which are not allowed to cross the master model;
the professional data package comprises: directories, files, belonged specialties; one professional data packet corresponds to a set of related professional data files, one professional comprises a plurality of professional data packets, and the professional data packets are not allowed to cross the professions;
the data items include: a professional data packet comprises a plurality of data items, and one data item corresponds to one data file;
the data file includes: text, pictures, reports, tables, or any combination thereof.
Background
With the development and application of computer technology, network technology and communication technology, enterprise information management has become an important guarantee for improving enterprise operation management level and core competitive power. However, the research and development project management mode of many enterprises currently stays in the traditional offline management, however, the traditional research and development management system often has the following problems:
1. efficient management of process data deficiencies
At present, a plurality of PDM systems are implemented, and only the electronic centralized storage and management of product development stage result data are solved. The comprehensiveness and integrity of data management are not enough, the unified management of research and development process data (requirements, design, simulation and experiment) is lacking, the integration and data interaction degree among application systems is low, the effective sharing and efficient exchange of process data cannot be realized, and the repeatability and traceability of the research and development process are not high.
2. The requirement information and the technical index are difficult to trace
The breakdown and alteration of product requirements extends throughout the product lifecycle. The current demand information mainly depends on document management, the demand information lacks of structuralization, close association relation cannot be established with product research and development data, and effective consistency management is lacked between versions of the demand information and the product research and development data, so that the product research and development cannot respond to changes brought by demand changes in time, influences of local demand changes on the whole research and development cannot be analyzed and evaluated quickly and accurately, and the demand conformance cannot be tracked effectively. The responsiveness, maintainability, and trackability of information and index changes are low.
Disclosure of Invention
The invention aims to at least solve the technical problems in the prior art, and particularly creatively provides an intelligent master model management system based on data driving.
In order to achieve the above object, the present invention provides an intelligent master model management method based on data driving, comprising the following steps:
s1, logging in the system by using a login interface;
and S2, after logging in the system by using the login interface, performing corresponding operation in the system.
Further, the step S2 includes the following steps:
s21, submitting a data packet: the upstream data packet version according to which needs to be specified; and each time of data submission operation triggers one version update;
s22, carrying out data approval on the professional data packet:
s23, performing pedigree management on the professional data package:
s24, performing professional collaboration;
the data submission operation can simultaneously comprise a plurality of objects, and the operation mode can be one of addition, modification, deletion and renaming or any combination;
the object includes: files and/or directories;
the directory includes: model and/or professional data packages;
the version update includes: the end of the version number of the operation object is +1, and simultaneously, the version numbers of all the upper-level directories are also + 1.
Further, the S21 further includes:
the locking-unlocking mechanism is adopted: the object needs to be locked before the version is updated, and the locked object can allow other people to submit a new version only after being unlocked; the locking and unlocking operations are performed manually or automatically; if only one person has the write authority, the writing is automatically locked when the writing is submitted; and when the submission is successful, the system is automatically unlocked.
Further, the S22 includes:
s2-1, judging whether the submitted upstream data packet of the professional data packet is valid; if the approval state of the upstream data packet is invalid, the submitted professional data packet is invalid and cannot enter the approval process; if the approval state of the upstream data packet is valid or in approval, entering an approval process and executing the next step;
s2-2, judging whether the data packets are professional data packets of the same specialty, if so, selecting the same approval process;
s2-3, judging whether the submitted data belong to the data which need not to be examined and approved; if not, the user submitting the data can select the approval process; the approval process is specified by a data area administrator for a specialty.
Further, S3-1, judging whether the version of the professional data packet is valid; if yes, the system automatically judges the change of the technical state;
s3-2, judging whether the technical states of the professional data packets at the upstream of the professional data packets are all latest, and establishing the latest effective version of the professional data packets based on the latest effective version at the upstream; the technical state of the professional data packet is the latest;
s3-2, judging whether the technical state of the professional data packet is outdated, if so, judging that the technical states of the downstream professional data packets are outdated;
s3-3, judging whether the technical state of the professional data packet is to be updated, if so, setting the technical state of the professional data packet as to be updated;
and S3-4, judging whether the technical state of the professional data packet belongs to the state change from outdated to the latest state, if so, automatically setting the technical states of all the downstream professional data packets to be outdated.
Further, the S24 includes:
s4-1, creating a collaborative data area:
s4-2, multi-professional collaboration:
s4-3, the client acquires data:
s4-4, the client submits data;
s4-5, checking the technical state;
the S4-5 comprises:
s4-5-1, lineage tracing: a designer selects a data packet, designates any version, views pedigree information of upstream and downstream, and can trace any multiple layers;
s4-5-2, technical state consistency check: the designer labels the three technical states, either on the directory tree or on the lineage view.
Further, the S4-1 includes:
s4-1-1, creating a data area: the data area administrator performs data area initialization work, which includes: editing a directory structure of the data area, defining one or any combination of professionals needing to cooperate and personnel joining participating in the project in the data area;
s4-1-2, creating a main model: a data area administrator introduces a master model template from the outside to perform master model initialization work, where the master model initialization work includes: modifying main model information, modifying a directory structure, modifying a data package pedigree, and specifying one or any combination of data package responsible persons;
or/and the S4-2 comprises: the three professional data packet pedigree relations are as follows: the first professional data packet is an upstream data packet of the second professional data packet, the second professional data packet is positioned at the downstream of the first professional data packet, and the third professional data packet is positioned at the downstream of the second professional data packet;
s4-2-1, professional data packet initialization:
initializing a main model: a data area administrator establishes and initializes a main model, wherein the main model comprises editing and modifying a directory structure and/or a professional data packet of the main model, and the default initial version number is 1;
starting a main model: the data area administrator starts the main model, at the moment, all the version states are set to be effective, and the technical state is set to be latest;
s4-2-2, updating the professional data packet normally:
updating a first professional data packet: a first designer uploads a new professional data packet, the version is unchanged, and the version state is automatically set to be invalid; since the change is an invalid version, the state of the technology is unchanged; then entering an approval process, after approval is passed, setting the version +1 and the approval state as valid, and changing the technical state into valid because no upstream data packet exists;
since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
updating the second professional data packet: uploading a new second professional data packet by a second designer, selecting the version of the first professional data packet as V2, and carrying out an approval process without review; the system sets the version of the uploaded second professional data packet as V3, sets the version state as effective and sets the technical state as latest; the second professional data packet issues a new version, and the first professional data packet and the second professional data packet at the upstream of the second professional data packet are in the latest state, so that the technical state of the third professional data packet is automatically set to be updated;
updating a third professional data packet: uploading a new third professional data packet, and simultaneously selecting the first professional data packet version based on upstream as V2, the second professional data packet version as V3 and the approval process as 'no review'; the system sets the version of the uploaded second professional data packet as V3, sets the version state as effective and sets the technical state as latest;
s4-2-3, revoking the published data:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
invalid updating: the first designer manually sets the latest version V2 of the first professional data packet as invalid, the technical state is not changed, but the corresponding version is changed from V2 to V1; since the latest state of the first professional data packet is changed from the V2 version to the V1 version, and the latest valid version V1 of the second professional data packet is designed based on the overall V1 version, the technical state is automatically restored to the latest state; the technical state of the third professional data packet is recovered to be the latest as the second professional data packet;
s4-2-4, without updating the statement:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
no change is needed: the updated content of the first professional data packet has no influence on the design of the second professional data packet, and does not need to be changed, a second designer does not need to change a statement in the system, and the examination and approval process is carried out again, and the updated technical state is automatically set to be the latest after passing; after the second professional data packet is approved, the version is synchronously updated to V2, and the content is unchanged;
s4-2-5, feeding back messages to upstream:
updating a first professional data packet: a new first professional data packet is uploaded by a first designer, and the approval process is 'no need of review'; the system sets the version of the uploaded first professional data packet as V2, sets the version state as effective and sets the technical state as latest; since the latest valid version of the first professional data packet is changed from V1 to V2, the technical state of the second professional data packet is automatically set to be updated; since the latest valid version of the upstream first professional packet is changed from V1 to V2, the technical status of the third professional packet is automatically set to obsolete;
feedback information: the updated content of the first professional data packet can cause that the performance of the second professional data packet cannot be met, the new version of the first professional data packet is fed back in a version annotation mode, and the new version of the second professional data packet can also be fed back after the corresponding calculation data of the second professional data packet is submitted; after the first designer sees the feedback message, the first professional data packet is readjusted, and a new version is uploaded; the second designer redesigns from the new version of the first specialized data package.
Further, the S4-3 includes:
s4-3-1, synchronizing remote data: the designer creates a local catalog, synchronizes the content of the remote data area to the local by using a client tool, and can also inquire and download data of any historical version;
s4-3-2, browsing the query data: the designer can perform any operation of keyword query, attribute query and parameter value query in any directory of the data area, can preview data files of specific types of TXT or/and PDF, and can perform online drawing display on parameters.
Further, the S4-4 includes:
s4-4-1, submitting local data: a designer submits a file or a directory, and if the system judges that the file or the directory conflicts with the remote latest version, the file or the directory is uploaded after the conflict is manually solved; during uploading, updating based on which version is required to be specified, and then an approval process is selected; at this time, the state of the new version is defaulted to be invalid;
the auditor examines and approves the submitted data, and the version state is set to be valid after the auditor passes the approval;
s4-4-2, updating the technical state: the determination of the technical state is carried out automatically by the system.
The invention also provides an intelligent master model management system based on data driving, which is characterized by comprising the following components:
a collaborative data area, a main model, a pedigree relationship, a professional data package and data items;
the cooperative data area includes: basic information of model projects and project teams, wherein a collaborative data area corresponds to one model project and comprises a plurality of main models in different design stages;
the project team comprises project personnel, project roles and project authorities;
the main model includes: basic information, pedigree relationship and professional role of the model scheme; one main model corresponds to one model scheme, and one main model comprises a plurality of professional data packets;
the pedigree relationship is used for representing the upstream and downstream relationship of the professional data package, and the main model drives the design activity through the pedigree relationship; one master model corresponds to a set of pedigree relationships which are not allowed to cross the master model;
the professional data package comprises: directories, files, belonged specialties; one professional data packet corresponds to a set of related professional data files, one professional comprises a plurality of professional data packets, and the professional data packets are not allowed to cross the professions;
the data items include: a professional data packet comprises a plurality of data items, and one data item corresponds to one data file;
the data file includes: text, pictures, reports, tables, or any combination thereof.
In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that: the data exchange cost among the specialties is reduced, the cooperation efficiency is improved, the pedigree relation among the specialties is clearer, and the consistency of technical states in the iteration process is guaranteed.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a schematic view of the management system of the present invention;
FIG. 2 is a schematic diagram of an application scenario of the present invention;
FIG. 3 is a schematic diagram of the synergy principle of the present invention;
FIG. 4 is a schematic diagram of the invention for creating a collaborative data area;
FIG. 5 is a schematic diagram of lineage relationships between three specialized data packages according to the present invention;
FIG. 6 is a diagram of three specialized packets after initialization of the packets in accordance with the present invention;
FIG. 7 is a diagram illustrating normal updating of a packet according to the present invention;
FIG. 8 is a schematic diagram of the invention for revocation of published data;
FIG. 9 is a schematic diagram of the present invention without update statements;
FIG. 10 is a schematic diagram of upstream feedback messages of the present invention;
FIG. 11 is a schematic diagram of client-side data acquisition according to the present invention;
FIG. 12 is a schematic diagram of client commit data in accordance with the present invention;
FIG. 13 is a schematic view of the state check of the technique of the present invention;
FIG. 14 is a schematic diagram of the data storage strategy of the present invention;
FIG. 15 is a schematic diagram of the version evolution process of the present invention;
FIG. 16 is a schematic diagram of the "lock-unlock" mechanism of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.
2.1 basic concept
As shown in fig. 1, the intelligent master model management system includes: a collaborative data area, a main model, a pedigree relationship, a professional data package and data items;
the cooperative data area includes: basic information of model items, a project team and a subordinate catalog, a collaborative data area corresponds to one model item, and one collaborative data area generally comprises a plurality of main models at different design stages.
The main model includes: basic information of the model scheme, subordinate catalogues, pedigree relations and professional roles; one master model corresponds to one model plan, and one master model generally contains a plurality of data packets.
Pedigree relationships include: the system is used for representing the upstream and downstream relations of the professional data package, the pedigree relation is the basis of collaborative design, and the main model drives the design activity through the pedigree relation. One master model corresponds to a set of pedigree relationships, and pedigrees are not allowed to cross the master model.
The professional data package comprises: directory, file, professional. One professional data packet corresponds to a set of related professional data files, one professional can contain a plurality of data packets, and the data packets are not allowed to cross the professions.
Data item: one item of data content in the professional data package is the minimum granularity of version management, one data item corresponds to one data file, and the file type can be text, pictures, reports, tables and the like. In addition, the system also defines a special file format, namely a standard format parameter file (. param), one parameter file comprises one or more parameter groups, and the parameters are extracted from the Oracle database and are stored in a structured mode, so that the efficiency of data query analysis is improved.
2.2 basic principles
First, data submission principle
1. Each time the operation is submitted, version updating is triggered, the operation can simultaneously comprise a plurality of objects, and the operation mode can be addition, modification, deletion and renaming.
2. The management objects of the version are files and directories (the main model and the data packet are special directories), and the initial version number is 1;
3. updating each version, wherein the version number of the operation object is +1, and the version numbers of all the upper-level directories are + 1;
4. by adopting a locking-unlocking mechanism, before the version is updated, the locking is required, and the locked object can allow other people to submit a new version only after the locking. The locking and unlocking operations may be performed manually or automatically. When only one person has the write right, the writing data is automatically locked when submitted; and when the submission is successful, the system is automatically unlocked.
Second, data approval principle
1. The data approval object is a data packet;
2. the user submitting the data can select available approval processes, which ones can be designated by the data area administrator for the specialty, wherein a special approval process is also included as "no approval". The data packets of the same specialty and the optional approval process are the same, so that the data packets submitted in the same batch are limited to belong to the same specialty when being submitted;
3. the data packet has three approval states: invalid-submit a packet but not start the approval process; in approval-the approval process is executing; valid-considered to be valid data after approval.
4. The user can specify that the currently submitted version is created based on which version of the upstream data packet, the default version is the latest version of the upstream, and if the upstream data packet is invalid, the data packet can only be invalid, cannot enter an approval process, and cannot select an option of 'without approval'.
Third, pedigree management principles
1. The pedigree management object is a data packet, and the pedigree defines the upstream and downstream relation between the data packets;
2. there are three technical states for a packet: latest, outdated, to be updated. The technical state is only aiming at the latest effective version of the data packet, the technical state is triggered to be updated only by the change of the effective version, the change of the technical state is automatically judged by the system, and manual modification is not allowed;
3. a latest state packet whose upstream packet technical state must all be latest and whose latest valid version is also created based on the upstream latest valid version;
4. the technical state of the downstream data packet of the data packet in the outdated state can only be outdated;
5. if the technical states of the data packets in the state to be updated are all the latest, the data packets indicate that the design process has run to the present specialty, and the technical states of the data packets need to be set to be updated;
6. when a user submits a data packet, the version of the upstream data packet according to the data packet needs to be specified;
7. when a data packet is issued, the states of all data packets at the downstream are automatically set to be outdated;
2.3 application scenarios
As shown in fig. 2, includes:
the administrator, whose responsibilities are: 1. creation and maintenance of departments and users. 2. And daily maintenance of the system, including installation and restart of the system. 3. And (4) allocating user rights.
Data zone administrators whose responsibilities are: 1. creation and maintenance of data zones. 2. And (4) importing and initializing a main model.
3. A professional partition within the data area is defined.
Professional designers, whose duties are: 1. and in the professional authority, the data packet responsible for the data packet and the data packet of the related professions are checked. 2. Within the professional authority, the data packet is submitted.
The professional approver has the following functions: within the professional jurisdiction, the data packets submitted by professional designers are approved, typically by professional group leaders or room leaders.
2.4 principle of synergy
As shown in fig. 3, in the overall design business process, the fields of pneumatics, structures, dynamics, trajectory, guidance, control, etc. are involved, and are complex multidisciplinary tasks, and the design indexes are given from the overall, and a final overall scheme is formed through multiple rounds of professional-level and system-level design iterations. In a digital collaborative design environment based on an intelligent main model, core data of product design is expressed by the intelligent main model, and the intelligent main model is also a medium for exchanging data among professions. Compared with the traditional design mode, the intelligent main model reduces the data exchange cost among the specialties, improves the cooperation efficiency, makes the pedigree relation among the specialties clearer, and is helpful to ensure the consistency of the technical state in the iteration process.
2.4.1 creating collaborative data areas
The activities and operations of the collaborative data area administrator are shown in fig. 4.
Role: collaborative data zone administrators
Moving: creating a collaborative data area, creating an instance of the master model
2.4.2 Multi-professional collaboration scenarios
Let three specialized packet lineage relationships be as in FIG. 5:
the state information of the data packet comprises a version state and a technical state, wherein the version state comprises three states of invalidation, approval and validation aiming at each uploaded data version; the state of the art is only for the most recent valid version of each packet, with both the most recent and obsolete states. The combination of the two can complete the complete tracing of the technical state.
First, data packet initialization
The specific case of packet initialization is shown in fig. 6.
Role: data area manager
Second, the data packet is updated normally
The specific case of normal updating of the data packet is shown in fig. 7.
Role: general designers, pneumatic designers, ballistic designers
Thirdly, withdrawing the published data
The details of the revocation of published data are shown in fig. 8.
Role: general designers, pneumatic designers, ballistic designers
Fourth, no update statement is required
The details of the no update declaration are shown in fig. 9.
Role: general designers, pneumatic designers, ballistic designers
Fifthly, feeding back messages upstream
The details of feeding back messages upstream are shown in fig. 10.
Role: general designers, pneumatic designers, ballistic designers
2.4.3 client side obtaining data
The specific situation of the client acquiring data is shown in fig. 11.
Role: designer
Moving: synchronizing remote data, browsing query data
2.4.4 client commit data
The details of the client submitting the data are shown in fig. 11.
Role: designer, auditor
Moving: submitting local data, technical state updates
2.4.5 technical State inspection
The details of the technical status check are shown in fig. 12.
Role: designer, data area manager
Moving: pedigree tracing and technical state consistency checking
2.5 Key technology
2.5.1 data storage policy
As shown in fig. 13, the version library is a basic module of the system, a logical structure between data is established by abstract nodes, and a universal version control function is implemented based on the nodes, and the nodes can associate files. The basic types of the nodes comprise directories and files, and can be expanded into a main model, a data packet and a data item in the main model mode. Even if the structure of the main model changes in the future, the abstract nodes can flexibly adapt to the change.
The system adopts a storage strategy of combining an Oracle database and a file server, structured data such as attributes and parameters are stored by using the Oracle database, and unstructured data such as data files and documents are stored by using the file server.
2.5.2 version management mechanism
As shown in fig. 14, version control is a key function of the system, and in order to meet the requirements of master model version management and pedigree tracking, the version control principle of SVN is referred to, and functions such as storage and recording of version information, synchronization of the local data area and the remote data area, and tracing of historical versions are implemented.
The version control needs to support both B/S and C/S architectures, at the C/S client, synchronization of the local data area with the server needs to be performed, and whether the current data is modified based on the latest version can be checked when the data is submitted. The B/S client can not carry out version check because the B/S client does not have a local data area, and can only default that the user is modified based on the latest version.
The evolution of the version follows the following rules:
1. the version number is an integer and is initially 1, the version number is automatically +1 when one version is updated, and the version number is always increased in a version library;
2. the files and the directories have version numbers, each time the version of the file is updated, all the upper-level directories are updated simultaneously, and the version numbers are consistent with the file;
3. version recording is carried out on the creation, deletion and renaming of files and directories;
4. if the same submission operation comprises the modification of a plurality of objects, recording the same version number;
5. if the situation that multiple persons modify simultaneously occurs, the submitted version is normally updated, and then submitted version needs to be manually subjected to conflict resolution and then submitted;
6. files/directories are copied, the version number of the original file/directory is unchanged, and the version number of the copy continues to increase. The copying operation does not occupy new storage space, and the storage is only carried out after modification;
as shown in fig. 15, the evolution process of the version is illustrated:
in order to avoid the conflict of multiple persons modifying one object file at the same time, the system adopts a locking-unlocking mechanism, as shown in fig. 16, specifically requires the following:
1. before submitting data, an operator must lock an operation object;
2. in order to simplify the locking operation, when only one person has the write right, the locking operation can be automatically completed by the system without manual intervention;
3. for the locked object, only after the unlocking operation is carried out by an operator, other people can carry out locking;
4. when the data is successfully submitted, a new version is generated, and the system can be automatically unlocked;
5. people with writing rights can see the locking state of the object, including the locking time, the locked operator and the like;
2.5.3 lineage management mechanism
The pedigree of the data packet defines the upstream and downstream relation of the data packet, and provides basis for the evolution and tracking of the design process.
The definition of pedigree relationships should obey the following principles:
1. the object defined by the pedigree relationship is the whole data packet, and the relationship among specific data contents is not concerned;
2. any one packet may define one or more upstream packets and downstream packets;
3. cycle definitions that do not allow for the occurrence of packet lineage, such as a > B > C > a;
4. the pedigree relation is only defined inside the main model, and the cross-main model is not allowed to be defined;
5. in order to ensure the effectiveness of historical version tracing, only new pedigree relationships are allowed to be added after the main model is started, and existing pedigree relationships are not allowed to be modified and deleted.
Since the pedigree relationship is a many-to-many relationship, a pedigree relationship table needs to be established separately when the database is stored. Taking the pedigree relationship of fig. 5 as an example, the contents of the record pedigree relationship storage are as follows.
ID
MODEL_ID
UP_ID
DOWN_ID
1
ID of the master model
ID of the overall data packet
Pneumatic data packet ID
2
ID of the master model
ID of the overall data packet
ID of structure data packet
3
ID of the master model
Pneumatic data packet ID
ID of structure data packet
The technical state is automatically judged by the system according to the pedigree relationship and the latest effective version of the data, and the rule is as follows:
and (3) latest: the upstream data is all up-to-date, and the upstream version on which the currently valid version is based is also up-to-date valid;
and (3) waiting for updating: the upstream data packets are all latest, but the upstream version based on which the current valid version is not latest valid;
and (3) when the file is out of date: upstream packets are outdated or pending update.
While embodiments of the invention have been shown and described, it will be understood by those of ordinary skill in the art that: various changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.
