Design file automatic version upgrading and comparison management method

Abstract

The application discloses a management method for automatic version upgrading and comparison of design files, and comprises the following steps: when an archiving instruction is acquired, setting an archiving version number of the design file based on version management rules, and storing the design file into a specified data table according to the archiving version number; and when a comparison instruction is acquired, performing comparison processing on the design file based on comparison rules, and generating comparison records for displaying modification contents according to the processing result; the application not only helps to reduce the design period, but also improves the management efficiency of the design file, reduces additional inefficient work such as data collection and summarization, reduces the probability of human error, and has the function of identifying changed data, so that the designer can record and trace the changed contents, greatly improving the automatic design efficiency, and playing an economic role in improving the economic benefit of the nuclear power plant.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of design software, in particular to a design file automatic version upgrading and comparison management method. BACKGROUND

[0002] In nuclear power plants, the traditional management method of the design file of the instrument control logic diagram is to rely on manual version upgrading, comparison and archiving. This method not only has low design efficiency and high human error rate, but also cannot guarantee the design quality, and cannot automatically record and trace the changes in the design process, so that the design personnel consume a large amount of working hours to ensure the reliability of the design file when performing the design work, which seriously reduces the economic benefits of the nuclear power plant. SUMMARY

[0003] The technical problem to be solved by the present application is to provide a design file automatic version upgrading and comparison management method in view of at least one defect in the prior art.

[0004] The technical scheme adopted by the present application to solve the technical problem is that a design file automatic version upgrading and comparison management method is constructed, comprising the following steps:

[0005] S1, when an archiving instruction is obtained, setting an archiving version number of the design file based on a version management rule, and storing the design file into a specified data table according to the archiving version number;

[0006] S2, when a comparison instruction is obtained, performing comparison processing on the design file based on a comparison rule, and generating a comparison record for displaying the modification content according to the processing result.

[0007] Preferably, in the S1, setting the archiving version number of the design file based on the version management rule comprises:

[0008] S11, judging whether there is a solidified version, if yes, executing step S12, otherwise executing step S13;

[0009] S12, judging whether this archiving is the first version, if yes, upgrading a primary version number of the latest solidified version, and updating the archiving version number to the primary version number after the upgrading, otherwise executing step S14;

[0010] S13, judging whether this archiving is the first version, if yes, prompting the design personnel to select a primary version number, and setting the selected primary version number as the archiving version number, otherwise executing the S14;

[0011] S14, setting the archiving version number according to an ascending order rule.

[0012] Preferably, the S12 comprises: judging whether the archive is the first version, if yes, recommending the design personnel to upgrade the version number and change the version number, and updating the archive version number to the version number selected by the design personnel, otherwise executing step S14; wherein the upgraded version number is obtained by upgrading the primary version number of the latest solidified version, and the changed version number is obtained by changing the version number of the solidified version.

[0013] Preferably, in the S14, the setting of the archive version number according to the ascending order rule comprises:

[0014] judging whether the latest archive version number of the design file is the primary version number, if yes, converting the primary version number into a secondary version number, then ascending the secondary version number, and updating the archive version number to the secondary version number after ascending, otherwise ascending the latest secondary version number, and updating the archive version number to the secondary version number after ascending.

[0015] Preferably, the design file automatic version upgrading and comparison management method further comprises:

[0016] S3, when the solidification instruction is obtained, performing version solidification processing on the stored design file.

[0017] Preferably, in the S3, the version solidification processing comprises:

[0018] judging whether the archive version number of the design file is the secondary version number, if yes, solidifying the latest version in the secondary version number as a solidified version, otherwise solidifying the primary version number of the design file as a solidified version.

[0019] Preferably, in the S2, the comparison processing of the design file based on the comparison rule comprises:

[0020] S21, judging whether the design file has at least one historical archive version, if yes, executing step S22, otherwise ending;

[0021] S22, judging whether the solidified version, if yes, performing the comparison processing of the design file with the latest solidified version, otherwise performing the comparison processing of the design file with the first version of the historical archive version.

[0022] Preferably, the S2 further comprises: setting the archive version number of the design file after the comparison processing based on the version management rule, and storing the design file into a specified data table according to the archive version number.

[0023] Preferably, in the S22, the comparison processing comprises:

[0024] S221, performing first comparison processing on the drawings in the design file to generate first revision records; and / or performing second comparison processing on the list in the design file to generate second revision records.

[0025] Preferably, in the S221, the first comparison processing comprises:

[0026] Obtaining drawing information of the design file drawings and the comparison version drawings, comparing the drawing information of the design file drawings and the comparison version drawings to generate drawing change information, the drawing change information being the first revision records; the drawing information comprising at least one of a graphic element, a connection line and an attribute.

[0027] Preferably, the first comparison processing further comprises: determining a drawing change position of the drawing change information, and adding a cloud line graphic element attribute and a graphic element identification version number to a changed graphic element in the design file drawings according to the drawing change information and the drawing change position.

[0028] Preferably, the first comparison processing further comprises: if there is a cloud line intersection after adding the cloud line graphic element attribute, issuing a merging list, and performing cloud line merging according to the merging list after a designer confirms the merging list.

[0029] Preferably, in the S221, the second comparison processing comprises:

[0030] Obtaining list information of the design file list and the comparison version list, comparing the list information of the design file list and the comparison version list to generate list change information, the list change information being the second revision records.

[0031] Preferably, the second comparison processing further comprises: determining a list change position according to the list change information, and adding a version upgrade identification to data of the list change information at a corresponding position in a list interface.

[0032] Preferably, the adding of the version upgrade identification comprises: adding an underline to field added data and field modified data in the list change information; and / or adding a deletion line to field deleted data in the list change information; and / or adding a different color identification to the field added data, the field modified data and the field deleted data.

[0033] The present application has at least the following beneficial effects: providing a design file automatic version upgrade and comparison management method: when an archiving instruction is obtained, the archive version number of the design file is set based on the version management rule, and the design file is stored in the specified data table according to the archive version number, thereby realizing the automatic version upgrade function; when a comparison instruction is obtained, the design file is compared based on the comparison rule, and the comparison record for displaying the modification content is generated according to the processing result, thereby realizing the automatic version comparison function; the present application uses a computer to realize the automatic version upgrade and comparison processing work, which not only helps to reduce the design period, but also can improve the management efficiency of the design file, reduce the additional inefficient work such as data collection and summarization, reduce the probability of human error, and also has the function of identifying the changed data, so that the designer can record and trace the changed content, greatly improving the automatic design efficiency, and playing an economic role in improving the economic efficiency of the nuclear power plant. BRIEF DESCRIPTION OF DRAWINGS

[0034] The present application will be further described below in combination with the drawings and embodiments, wherein:

[0035] Figure 1 is a flowchart of the design file automatic version upgrade and comparison management method provided by the present application;

[0036] Figure 2 is a flowchart of step S1 in the design file automatic version upgrade and comparison management method provided by the present application;

[0037] Figure 3 is a flowchart of step S2 in the design file automatic version upgrade and comparison management method provided by the present application. DETAILED DESCRIPTION

[0038] In order to have a clearer understanding of the technical features, objects and effects of the present application, the specific embodiments of the present application will be described in detail with reference to the drawings.

[0039] Reference Figure 1 The present application provides a design file automatic version upgrade and comparison management method, which can be used for managing the design file of the instrument control logic diagram, and the method comprises steps S1 and S2.

[0040] S1, when an archiving instruction is obtained, the archive version number of the design file is set based on the version management rule, and the design file is stored in the specified data table according to the archive version number.

[0041] In some embodiments, a database can also be established to store the design file in the specified data table in the database.

[0042] In some embodiments, as Figure 2As shown, the design file archive version number setting based on the version management rule in S1 includes steps S11, S12, S13 and S14.

[0043] S11, determine whether there is a solidified version, if yes, execute step S12, otherwise execute step S13.

[0044] Specifically, the solidified version is a relatively stable or functionally verified version without obvious errors, so when there is a solidified version in the database or data table, in order to facilitate the distinction between the current design file to be archived and the previous version, step S12 should be executed at this time; if there is no solidified version, it means that the current design file to be archived does not have a solidified version to be distinguished, and step S13 should be executed.

[0045] S12, determine whether this archive is the first version, if yes, upgrade the primary version number of the latest solidified version in combination with the change instruction, and update the archive version number to the primary version number after upgrading, otherwise execute step S14.

[0046] In order to increase the flexibility of version number naming, so that designers can more easily distinguish the relevance of each version, in some embodiments, step S12 includes: determining whether this archive is the first version, if yes, recommending an upgraded version number and a changed version number to the designer, and updating the archive version number to the version number selected by the designer, otherwise executing step S14; wherein the upgraded version number is obtained by upgrading the primary version number of the latest solidified version, and the changed version number is obtained by changing the version number of the solidified version.

[0047] The following will illustrate the process of upgrading the primary version number when it is determined that this archive is not the first version: assuming that there is a solidified version in the database or data table and the latest solidified version number is B, by upgrading the solidified version number B, an upgraded version number C is obtained, and the solidified version number B is changed to obtain a changed version number BA; again assuming that there is a solidified version and the latest solidified version number is BA, by upgrading the solidified version number BA, an upgraded version number C is obtained, and the solidified version number BA is changed to obtain a changed version number BB. It can be understood that if the modification content between versions is relatively large, the designer can select the upgraded version number as the archive version number according to the need; if this archive belongs to the version improved after the solidified version is verified and confirmed, the designer can select the changed version number as the archive version number.

[0048] S13, determine whether this archive is the first version, if yes, prompt the designer to select a primary version number, and set the selected primary version number as the archive version number, otherwise execute S14. Specifically, when it is determined that this archive is the first version, the designer can be prompted to select or set a primary version number through a human-computer interaction interface.

[0049] S14, setting the archive version number according to the ascending order rule.

[0050] In some embodiments, the setting of the archive version number according to the ascending order rule in step S14 comprises: judging whether the latest archive version number of the design file is a primary version number, if yes, converting the primary version number into a secondary version number, then ascending the secondary version number, and updating the archive version number as the ascending secondary version number, otherwise, ascending the latest secondary version number, and updating the archive version number as the ascending secondary version number.

[0051] The following will illustrate the process of setting the archive version number according to the ascending order rule: if the latest archive version number is a primary version number D, the secondary version number obtained by converting the primary version number D is D1, the secondary version number obtained by ascending the version number D1 is D2, and then the archive version number is updated as D2; if the latest archive version number is a secondary version number D2, the secondary version number obtained by ascending D2 is D3, and then the archive version number is updated as D3.

[0052] It can be understood that, in this embodiment, the archive version number comprises a primary version number and a secondary version number; wherein the secondary version number is obtained by ascending the design file based on a certain primary version number after improvement and after obtaining the archive instruction, that is, the secondary version number is associated with the primary version number. Preferably, the primary version number can be composed of English letters, and the secondary version number associated therewith is composed of the English letter corresponding to the primary version number and Arabic numerals, for example, A is a primary version number, and the secondary version numbers associated therewith can be A1, A2, A3, etc., in addition, the larger the Arabic numerals are, the newer the version is.

[0053] Further, in this embodiment, judging whether the archive is the first version comprises: if the design file of this archive has no version number (corresponding to the case that there is no solidified version and the design file belongs to a new design) or the version number of the design file is the version number of a certain solidified version (in some cases, because the version number of the design file before completing the archive is the version number of the solidified version, that is, corresponding to the first archive based on a certain solidified version for improvement by the designer), it is determined that this archive is the first version, otherwise, it is determined that this archive is not the first version.

[0054] To ensure the design file meets the set standard, in some embodiments, before setting the archive version number of the design file based on the version management rule, further comprises: checking the drawing in the design file according to the set standard, and only after ensuring that the drawing meets the standard, the subsequent archiving step is performed. Further, in some embodiments, the checking content includes: checking whether the necessary input parameters of the drawing meet the standard (such as the case that the necessary setting parameters of some components in the logic diagram are missing, the parameter setting is out of limit, etc.), and checking whether there is a missing or connection violation case of some components in the drawing (such as some logic gates are not connected to the bit, etc.).

[0055] S2, when the comparison instruction is acquired, performing comparison processing on the design file based on the comparison rule, and generating a comparison record for displaying the modification content according to the processing result.

[0056] In some embodiments, as shown in FIG. 2, the comparison processing on the design file based on the comparison rule in step S2 includes step S21 and step S22. Figure 3

[0057] S21, judging whether the design file has at least one historical archive version, if yes, performing step S22, otherwise ending.

[0058] It can be understood that when the designer performs the design work of the same project, multiple versions of the design file will be saved. Whether the design file has at least one historical archive version is judged according to the version number of the design file: for example, the version number of the design file is A6, in this embodiment, it has at least five historical archive versions, corresponding to the archive version numbers A1 to A5; if the version number of the design file is B, it has at least one historical archive version related to the first letter of "A", such as A, A1, etc. Similarly, if the version number of the design file is C, it may also have solidified versions such as B, B1, BA, etc.; if the version number of the design file is A, it means that the design file does not have at least one historical archive version.

[0059] S22, judging whether there is a solidified version, if yes, performing comparison processing on the design file and the latest solidified version, otherwise performing comparison processing on the design file and the first version of the historical archive version. Specifically, the solidified version is a relatively stable version, and when performing comparison processing, it should be preferentially compared with the latest solidified version.

[0060] ​The following will illustrate how to select the process of aligning version: as the version number of the design file is C6, it is explained that the first letter "B" related version number has been solidified, so its latest solidified version can be B, BA, BB, etc., assuming that the "B" related version number has been upgraded to "BC", when aligning, the version C6 should be aligned with the "BC" related solidified board; specifically, when the "BC" related solidified board is BC3, C6 is aligned with BC3, and when the "BC" related solidified board is BC2, C6 is aligned with BC2.

[0061] If there is no solidified version, such as the version number of the design file is A6, that is, there is a historical archive version number of the design file from A1 to A5, it can be understood that the newer the secondary version number, the greater the development degree of the version to some extent. In order to avoid too large difference between two alignment versions, reduce the alignment value, therefore, the object of alignment processing at this time is the design file with version number A6 and A1.

[0062] In some embodiments, the design file includes drawings and lists, and correspondingly, the alignment processing in S22 includes: S221, performing first alignment processing on the drawings in the design file to generate a first revision record; and / or performing second alignment processing on the lists in the design file to generate a second revision record. Wherein, the first revision record and / or the second revision record constitute the alignment record.

[0063] In some embodiments, the first alignment processing in step S221 includes: obtaining drawing information of the design file drawings and the alignment version drawings, comparing the drawing information of the design file drawings and the alignment version drawings to generate drawing change information, and the drawing change information as the first revision record; the drawing information includes at least one of primitives, connections and attributes.

[0064] In some embodiments, the first alignment processing further includes: determining a drawing change position of the drawing change information, and adding a cloud line primitive attribute and a primitive identification version number to the changed primitive in the design file drawings according to the drawing change information and the drawing change position.

[0065] For adding the cloud line primitive attribute, first, add a cloud line identification to the changed primitive in the design file drawings, and then according to the cloud line size of the changed primitive, finally make the cloud line match the original size of the changed primitive, so that the designer can quickly identify those primitives as changed primitives when viewing the drawings; for adding the primitive identification version number, the designer can quickly know which version the changed primitive is identified when aligning, such as a changed primitive is identified after aligning with the solidified version A, then the primitive identification version number of the changed primitive is A, so that the designer can trace the change record of the primitive.

[0066] Since the cloud line graph element attribute is added, some cloud lines may cross, making the drawing complex and difficult to read, and reducing the readability of the drawing. In some embodiments, the first comparison processing further includes: if there is a cloud line crossing after adding the cloud line graph element attribute, issuing a merging list, and merging the cloud lines according to the merging list after the designer confirms the merging list. It can be understood that the designer can set the merging list to make the cloud lines merge by customizing, thereby improving the readability of the drawing.

[0067] In some embodiments, the second comparison processing in step S221 includes: obtaining list information of the design file list and the comparison version list, comparing the list information of the design file list and the comparison version list to generate list change information, and the list change information as the second revision record. The list change information includes field addition data, field deletion data and field modification data.

[0068] In some embodiments, the second comparison processing further includes: determining the list change position according to the list change information, and adding a version upgrade identifier to the data of the list change information at the corresponding position in the list interface.

[0069] In order to facilitate the designer to trace the change content of the list, in some embodiments, the added version upgrade identifier includes: adding an underline to the field addition data and the field modification data in the list change information; and / or adding a deletion line to the field deletion data in the list change information; and / or adding different color identifiers to the field addition data, the field modification data and the field deletion data.

[0070] In some embodiments, S2 further includes: setting an archive version number of the design file after the comparison processing based on the version management rule, and storing the design file into a specified data table according to the archive version number.

[0071] In some embodiments, the design file automatic version upgrade and comparison management method further includes step S3.

[0072] S3, when the solidification instruction is obtained, performing version solidification processing on the stored design file.

[0073] In some embodiments, the version solidification processing in step S3 includes: judging whether the archive version number of the design file is a secondary version number, if yes, taking the latest version in the secondary version number as the solidification version for solidification, otherwise taking the primary version number of the design file as the solidification version for solidification. Specifically, since the latest version in the secondary version number is generally the version with the deepest development degree and the highest stability, therefore, in the secondary version, the latest version should be solidified preferentially.

[0074] The present application has at least the following beneficial effects: providing a design file automatic version upgrading and comparison management method: when an archiving instruction is obtained, the archive version number of the design file is set based on the version management rules, and the design file is stored in a specified data table according to the archive version number, thereby realizing the automatic version upgrading function; when a comparison instruction is obtained, the design file is compared based on the comparison rules, and a comparison record for displaying the modification content is generated according to the processing result, thereby realizing the automatic version comparison function; the present application realizes the automatic version upgrading and comparison processing by using a computer, which not only helps to reduce the design period, but also improves the management efficiency of the design file, reduces the additional inefficient work such as data collection and summarization, reduces the probability of human error, and also has the function of identifying the changed data, so that the designer can record and trace the changed content, greatly improving the automatic design efficiency, and playing an economic role in improving the economic benefit of the nuclear power plant.

[0075] It can be understood that the above embodiments only express the preferred embodiments of the present application, and the description is more specific and detailed, but it cannot be understood as a limitation on the scope of the patent of the present application; it should be pointed out that for ordinary skilled in the art, the above technical features can be freely combined without departing from the concept of the present application, and some modifications and improvements can be made, which belong to the protection scope of the present application; therefore, any equivalent transformation and modification within the scope of the claims of the present application should belong to the scope of the claims of the present application.

Claims

1. A management method for automatic upgrading and comparing of design files, characterized in that, The method comprises the following steps: S1, when an archiving instruction is obtained, setting an archive version number of a design file based on a version management rule, and storing the design file into a specified data table according to the archive version number; S2, when a comparison instruction is obtained, performing comparison processing on the design file based on a comparison rule, and generating a comparison record for displaying modification content according to a processing result; In the S1, setting the archive version number of the design file based on the version management rule comprises: S11, judging whether there is a solidified version, if yes, executing step S12, otherwise executing step S13; S12, judging whether this archive is the first version, if yes, upgrading a primary version number of the latest solidified version, and updating the archive version number to the primary version number after upgrading, otherwise executing step S14; S13, judging whether this archive is the first version, if yes, prompting a designer to select a primary version number, and setting the selected primary version number as the archive version number, otherwise executing the S14; S14, setting the archive version number according to an ascending rule; wherein the solidified version is a stable or functionally verified version without obvious errors; Before setting the archive version number of the design file based on the version management rule, there further comprises: checking drawings in the design file according to a set standard, and ensuring that the drawings meet the standard before executing subsequent archiving steps; wherein the checking content comprises: checking whether necessary input parameters of the drawings meet the standard, and checking whether some components in the drawings are missing or have connection violation; the checking whether the necessary input parameters of the drawings meet the standard comprises: judging whether necessary setting parameters of some components are missing and parameter setting is out of limit; the checking whether some components in the drawings are missing or have connection violation comprises: judging whether a logic gate is not connected in place; The S12 comprises: judging whether this archive is the first version, if yes, recommending an upgraded version number and a changed version number to a designer, and updating the archive version number to the version number selected by the designer, otherwise executing step S14; wherein the upgraded version number is obtained by upgrading a primary version number of the latest solidified version, and the changed version number is obtained by changing a version number of the solidified version; In the S14, setting the archive version number according to the ascending rule comprises: judging whether a latest archive version number of the design file is the primary version number, if yes, converting the primary version number into a secondary version number, then ascending the secondary version number, and updating the archive version number to the secondary version number after ascending, otherwise ascending a latest secondary version number, and updating the archive version number to the secondary version number after ascending; wherein the primary version number is composed of English letters, and the secondary version number associated with the primary version number is composed of English letters and Arabic numerals corresponding to the primary version number; The management method of the design file automatic upgrading and comparison further comprises: S3, when a solidification instruction is obtained, performing version solidification processing on the stored design file.

2. The management method of automatic upgrading and comparing of design files according to claim 1, characterized in that, In the S3, the version solidification processing comprises: judging whether the archive version number of the design file is the secondary version number, if yes, taking the latest version in the secondary version number as the solidification version for solidification, otherwise taking the primary version number of the design file as the solidification version for solidification.

3. The management method of automatic upgrading and comparing of design files according to claim 1 or 2, characterized in that, In the S2, the comparison processing of the design file based on the comparison rule comprises: S21, judging whether the design file has at least one historical archive version, if yes, executing step S22, otherwise ending; S22, judging whether there is a solidification version, if yes, performing the comparison processing of the design file with the latest solidification version, otherwise performing the comparison processing of the design file with the first version of the historical archive version.

4. The management method of automatic upgrading and comparing of design files according to claim 3, characterized in that, The S2 further comprises: setting the archive version number of the design file after the comparison processing based on the version management rule, and storing the design file into a specified data table according to the archive version number.

5. The management method of automatic upgrading and comparing of design files according to claim 4, characterized in that, In the S22, the comparison processing comprises: S221, performing first comparison processing on drawings in the design file to generate first revision records, and / or performing second comparison processing on lists in the design file to generate second revision records.

6. The management method of automatic upgrading and comparing of design files according to claim 5, wherein, In the S221, the first comparison processing comprises: obtaining drawing information of the design file drawings and comparison version drawings, comparing the drawing information of the design file drawings and the comparison version drawings to generate drawing change information, the drawing change information being the first revision records; the drawing information comprising at least one of a graphic element, a connection line and an attribute.

7. The management method of automatic version upgrading and comparison of design files according to claim 6, characterized in that, The first comparison processing further comprises: determining a drawing change position of the drawing change information, and adding a cloud line graphic element attribute and a graphic element identification version number to a changed graphic element in the design file drawings according to the drawing change information and the drawing change position.

8. The management method of automatic version upgrading and comparison of design files according to claim 7, characterized in that, The first comparison processing further comprises: if there is a cloud line intersection after adding the cloud line graphic element attribute, issuing a merging list, and performing cloud line merging according to the merging list after a designer confirms the merging list.

9. The management method of automatic version-up and comparison of design files according to claim 5, wherein, In the S221, the second comparison processing comprises: obtaining list information of the design file lists and comparison version lists, comparing the list information of the design file lists and the comparison version lists to generate list change information, the list change information being the second revision records.

10. The management method of automatic version-up and comparison of design files according to claim 9, wherein, The second comparison processing further comprises: determining a list change position according to the list change information, and adding an upgrade identification to data of the list change information at a corresponding position in a list interface.

11. The management method of automatic version-up and comparison of design files according to claim 10, wherein, The added upgrade identification comprises: adding data and field modification data with an underline in a field in the list change information; and / or adding deleted data in the field in the list change information with a deletion line; and / or adding different color identifications on the field added data, the field modification data and the field deleted data.

Images