CN113568902B

CN113568902B - Management system and method for PDS pipeline reference database

Info

Publication number: CN113568902B
Application number: CN202110673757.7A
Authority: CN
Inventors: 沈杰
Original assignee: Shanghai Nuclear Engineering Research and Design Institute Co Ltd
Current assignee: Shanghai Nuclear Engineering Research and Design Institute Co Ltd
Priority date: 2021-06-17
Filing date: 2021-06-17
Publication date: 2023-11-21
Anticipated expiration: 2041-06-17
Also published as: CN113568902A

Abstract

Compared with the prior art, the invention provides the history record inquiry and version tracing of the pipeline reference database, so that the management of the whole pipeline reference database is more controllable and standard, and the quality of the whole pipeline reference database is ensured; the unified management entrance to the pipeline reference database of the multiple PDS projects is provided, so that unified management and control of the multiple projects are realized; the user authority management and control function is provided, and the safety of the pipeline reference database is improved; the user can rapidly manage the pipeline reference database without editing on the text editor after professional training, thereby improving the working efficiency of the user, greatly reducing the working difficulty and achieving the purpose of the invention.

Description

Management system and method for PDS pipeline reference database

Technical Field

The invention relates to a management system and a management method of a three-dimensional model reference database, in particular to a management system and a management method of a PDS pipeline reference database.

Background

PDS (Plant Design System) is a widely used three-dimensional design software. The PDS software is used as an integrated multi-specialty-participation collaborative design system, can quickly help each specialty designer to carry out three-dimensional modeling and design inspection, and greatly improves the working efficiency and the design quality. PDS software is widely used and has been used in numerous successful cases in the chemical and energy industries.

The PDS stores related information of the pipeline reference database in various binary files, unstructured data storage mode enables the data acquisition in the reference database to be inflexible, corresponding management operation can be carried out only by a specially trained administrator, and meanwhile, due to the fact that perfect version management and data modification record storage cannot be carried out in a text form, quality control measures of the PDS pipeline reference database are not perfect, and user experience and working efficiency are greatly affected in a normal use process.

Therefore, there is a particular need for a system and method for managing PDS pipeline reference databases that addresses the above-described problems.

Disclosure of Invention

The invention aims to provide a management system and a management method for a PDS pipeline reference database, which aim at the defects of the prior art, realize the functions of analyzing, managing and generating unstructured stored pipeline reference database data files in real time, and provide the functions of personnel authority management, record modifying, inquiring, historical data tracing and the like for PDS pipeline reference database management, thereby realizing the visualization, simplification and quality assurance controllability of PDS pipeline reference database data management work.

The technical problems solved by the invention can be realized by adopting the following technical scheme:

in a first aspect, the present invention provides a management system for a PDS pipeline reference database, including:

the user identity verification module is used for distinguishing whether a user is a system administrator or a PDS pipeline reference database operator, and verifying the identity password of the user to ensure the safety of the management system and the PDS pipeline reference database content;

the project configuration module is used for helping a system administrator to configure a PDS project pipeline reference database operable by the system, and comprises functions of adding, modifying and deleting PDS projects;

the system comprises an account management module, a data processing module and a data processing module, wherein the account management module is used for creating a PDS pipeline reference database operator account by a system administrator and configuring a PDS project operable by the operator account;

the project selection module is used for selecting PDS projects to be managed by a pipeline reference database operator;

the pipeline grade library file analysis module is used for carrying out content analysis on the PJS library file, the physical size library file, the material description library file and the standard annotation library file, and analyzing a form contained in the corresponding library file and contents in the form;

The pipeline grade library compiling module is used for writing the final state of the corresponding library file in the management system back into the PJS library file, the physical size library file, the material description library file and the standard annotation library file;

the PMC management module is used for operating the pipeline grade, the pipeline grade internal specification, the special part specification, the instrument part specification, the TAP point specification and the like of the current PDS project by a pipeline reference database operator;

the PJS meter management module is used for managing the PJS library file of the current project by a pipeline reference database operator;

the physical size library management module is used for managing the physical sizes of various standards of the current item by pipeline reference database operators;

the material description library management module is used for managing the standard pipeline short description, the standard pipeline long description, the special piece description, the instrument piece description, the support and hanger description and the TAP point description of the current item by a pipeline reference database operator; and

And the standard annotation library management module is used for managing 65 forms in the standard annotation library of the current item by a pipeline reference database operator.

In a second aspect, the present invention provides a method for managing a PDS pipeline reference database, including the steps of:

s1, user identity selection and verification, wherein if the user identity selection and verification is performed for an administrator, the verification is performed by entering S2, otherwise, the user identity selection and verification is stopped at S1; if the operator is a reference database operator, performing operator identity verification, wherein the verification passes through S3, otherwise, the operator is stopped at S1; if the end is needed, entering S7;

s2, performing PDS project configuration management in the management system, operator account management and authority management of the management system, and returning to S1 after configuration is completed;

s3, entering an operator management main interface, selecting a corresponding PDS item, entering S4 after the selection is finished, and returning to S1 if exiting is required;

s4, selecting a pipeline reference database management module to be operated, and if the PMC management module such as a pipeline grade library, a special part library, an instrument part library, a TAP table library and a Size-Dependent Material Data library is required to be operated, entering S5; if other modules need to be operated, entering S6; if the user needs to exit, returning to S1;

s5, when the system accesses the corresponding sub-module in the PMC module of the selected item to modify, corresponding information is firstly obtained from the corresponding data table in the RA table space in the corresponding PDS database, after the user modifies correspondingly, the modified content of the user is stored in the database of the system, the final modified result is stored back to the corresponding data table in the RA table space in the PDS database, and S4 is returned;

S6, the system accesses the related function modules stored in the library files of the selected items, firstly analyzes the bottom files of the selected management modules through an interpreter, feeds back analysis results to a user in a data form in an operation interface, adds and deletes corresponding data on the operation interface by an operator, records the current operation content of the operator into a database of the management system as a modification record after the operation is finished, compiles final result data into corresponding PDS pipeline reference database bottom files through a compiler, and returns to S4;

s7, ending.

In one embodiment of the present invention, PDS project configuration management, operator account management, and rights management in the management system of step S2 includes the steps of:

s2.1, entering an administrator interface, selecting a corresponding management module, and entering S2.2 if a PDS project operable by a configuration system needs to be managed; if the operator account needs to be managed, entering S2.9; if the administrator password needs to be reset, entering S2.13, and if the administrator password needs to be exited, entering S2.14;

s2.2, if a PDS item needs to be newly added, entering S2.3; if the PDS item needs to be modified, entering S2.4; if the PDS item needs to be deleted, entering S2.7; if the PDS project configuration management is exited, returning to S2.1;

S2.3, configuring relevant information of the newly added PDS project, writing the configuration information into a database of the system after the configuration is completed, and returning to S2.2;

s2.4, the program reads a corresponding data table in a database of the system, presents a modifiable item list to a user, selects item names to be modified by the user, and enters S2.5 after the selection is completed;

s2.5, the program reads the project configuration information of the selected site from the database of the management system, the user modifies the attribute according to the actual requirement, clicks and saves the modified attribute, and then enters S2.6;

s2.6, the program stores the modified site information into a database, and returns to S2.2;

s2.7, the program reads a corresponding data table in a database of the system, a currently existing item list is presented to a user, the user selects the item name to be deleted, and S2.8 is carried out after the selection is completed;

s2.8, the program returns to S2.2 from the configuration information corresponding to the items deleted from the database;

s2.9, if an operator account needs to be newly established, entering S2.10; if the authority configuration is required for the operator account, entering S2.11; if the operator account needs to be deleted, entering S2.12; if the operator account module is exited, returning to S2.1;

S2.10, creating an operator account, storing corresponding data into a database of the system after the creation is completed, and returning to S2.9;

s2.11, the system reads the related information of the operator account from the database, an administrator modifies the operator information according to the requirement, and after the configuration is completed, the result is stored in the database and returned to S2.9;

s2.12, the system reads the operator account information from the database, an administrator selects an operator account to be deleted, a result is stored in the database, and S2.9 is returned;

s2.13, inputting a current manager password and a new password by a user, if the current manager password is correct, modifying successfully, and updating the password from the system; otherwise, displaying that the current password is wrong, the password cannot be modified, and returning to S2.1 without updating the administrator password;

s2.14, ending.

In one embodiment of the present invention, when the system in step S5 accesses the corresponding sub-module in the PMC module of the selected item to modify, corresponding information is first obtained from the corresponding data table in the RA table space in the corresponding PDS database, after the user makes a corresponding modification, the modified content of the user is stored in the database of the system itself, and the final modified result is stored back into the corresponding data table in the RA table space in the PDS database, including the following steps:

S5.1, if the user needs to modify the standard pipeline grade library of the project, entering S5.2; if the special part library needs to be modified, entering S5.16; if the instrument library is modified, the process goes to S5.22; if the TAP table library needs to be modified, entering S5.28; if the Size-Dependent Material Data library needs to be modified, the method proceeds to S5.33; if the content is required to be subjected to modification record inquiry and version tracing, entering S5.37; otherwise, enter S5.39;

s5.2, firstly, accessing a PDT_201 data table in an RA table space in a PDS database corresponding to the selected item to acquire standard pipeline grade information of the current item, presenting the standard pipeline grade information to a user for operation, and entering S5.3 if the user needs to operate the standard pipeline grade item; if the user needs to operate the standard pipeline grade internal specification information, entering S5.9; otherwise, returning to S5.1;

s5.3, if the attribute modified by the user is related to the PJS library, entering S5.4; if the user modifies the TAP_DATA_TABLE attribute, proceed to S5.5; if the user modified attribute is related to the standard annotation library, proceeding to S5.6; otherwise, directly entering S5.7;

s5.4, the current attribute filling value is the corresponding table name in the PJS database, so that the corresponding table name in the PJS database is firstly required to be obtained through a PJS interpreter in the modification process, and the program fills the table name into the corresponding attribute field and enters S5.8; if the required attribute field cannot be found, modifying the PJS library first;

S5.5, the current attribute is filled with TABLE NAMEs in the TAP TABLE library, so that the TAP_TABLE_NAME needs to be read from the PDT ABLE_205 TABLE in the RA TABLE space firstly, then all the TAP TABLE NAMEs are presented to the user for selection, and after the user finishes the selection, the corresponding indication is filled in the attribute field, and S5.8 is entered; if the required attribute field cannot be found, modifying the TAP table library firstly;

s5.6, the current attribute fills in the attribute index values in the corresponding different tables in the standard annotation library, so that the content of all tables in the standard annotation library file is required to be acquired through the standard annotation library interpreter, and after the user selects the required attribute, the corresponding index value is filled in the corresponding attribute field to enter S5.8; if the required attribute field cannot be found, modifying the standard annotation library first;

s5.7, the user directly fills the attribute values to be filled in into the corresponding fields, and S5.8 is entered;

s5.8, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_201 table in the RA table space of the PDS database, and returning to S5.1;

s5.9, according to the standard pipeline grade name selected by the user, forming specification information inside the corresponding standard pipeline grade for the user to operate by looking up an entry corresponding to the standard pipeline grade name in a PDT ABLE_202 data table in the RA table space, and entering S5.10;

S5.10, if the user operates the attribute related to the standard annotation library, entering S5.11; if the pipe diameter attribute is operated by the user, S5.12 is entered; if the user operates the COMMODITY_CODE, go to S5.13; if other attributes are operated on, go to S5.14;

s5.11, the current attribute fills in the attribute index values in the corresponding different tables in the standard annotation library, so that the content of all tables in the standard annotation library file is required to be acquired through the standard annotation library interpreter, and after the user selects the required attribute, the corresponding index value is filled in the corresponding attribute field to enter S5.15; if the required attribute field cannot be found, modifying the standard annotation library first;

s5.12, the value filled in by the current attribute is a DIAMETER_TABLE TABLE in the corresponding current standard pipeline grade entry in the PJS library, so that the specific attribute value in the TABLE is firstly acquired by a PJS interpreter for a user to select in the modification process, and the process enters S5.15 after the user selects a required pipe DIAMETER; if the required pipe diameter cannot be found, modifying a pipe diameter table corresponding to the PJS library;

s5.13, the current attribute is to fill in the COMMODITY_CODE value of the pipeline material in the short description library, so that the content of COMMODITY_CODE related to all pipeline material descriptions in the short description library file is required to be acquired through a description library interpreter for selection by a user, and the corresponding field is written after the user selects the corresponding field, and S5.15 is entered; if the needed COMMODITY_CODE value cannot be found, the short description library needs to be modified first;

S5.14, directly modifying the attribute value into a required value, and entering S5.15;

s5.15, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_202 table in an RA table space of the PDS database, and returning to S5.1;

s5.16, accessing a PDT ABLE_203 data table in an RA table space in a PDS database corresponding to the selected item to acquire special piece library item information of the current item, presenting the special piece library item information to a user for operation, and entering S5.17 if the attribute of the operation is related to a standard annotation library; if the pipe diameter attribute is operated by the user, S5.18 is entered; if the user operates PING_COMP_NO, entering S5.19; if other attributes are operated on, go to S5.20;

s5.17, the current attribute fills in the attribute index values in the corresponding different tables in the standard annotation library, so that the content of all tables in the standard annotation library file is required to be acquired through the standard annotation library interpreter, and after the user selects the required attribute, the corresponding index value is filled in the corresponding attribute field to enter S5.21; if the required attribute field cannot be found, modifying the standard annotation library first;

s5.18, the current attribute filling value is all pipe diameter ranges contained in the union of all corresponding pipe diameter tables in the PJS library, so that the union of pipe diameters in all pipe diameter tables is firstly acquired through a PJS interpreter in the modification process, and a user selects a required pipe diameter and then enters S5.21; if the required pipe diameter cannot be found, modifying a pipe diameter table corresponding to the PJS library;

S5.19, the current attribute is a COMMODITY_CODE value in a special part description library, so that all COMMODITY_CODE contents related to the special part in the description library file of the special part are required to be acquired through a description library interpreter for selection by a user, and the user writes corresponding fields after selecting the corresponding fields, and then S5.21 is performed; if the needed COMMODITY_CODE value cannot be found, the special piece description library needs to be modified first;

s5.20, directly modifying the attribute value into a required value, and entering S5.21;

s5.21, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_203 table in an RA table space of the PDS database, and returning to S5.1;

s5.22, accessing a PDT_204 data table in an RA table space in a PDS database corresponding to the selected item to acquire instrument library item information of the current item, presenting the instrument library item information to a user for operation, and entering S5.23 if the attribute of the operation is a standard annotation library related attribute; if the pipe diameter attribute is operated by the user, S5.24 is entered; if the user operates INSTRUMENT_COMP_NO, entering S5.25; if other attributes are operated on, go to S5.26;

s5.23, the current attribute fills in the attribute index values in the corresponding different tables in the standard annotation library, so that the content of all tables in the standard annotation library file is required to be acquired through the standard annotation library interpreter, and after the user selects the required attribute, the corresponding index value is filled in the corresponding attribute field to enter S5.27; if the required attribute field cannot be found, modifying the standard annotation library first;

S5.24, the current attribute filling value is all pipe diameter ranges contained in the union of all corresponding pipe diameter tables in the PJS library, so that the union of pipe diameters in all pipe diameter tables is firstly acquired through a PJS interpreter in the modification process, and a user selects a required pipe diameter and then enters S5.27; if the required pipe diameter cannot be found, modifying a pipe diameter table corresponding to the PJS library;

s5.25, the current attribute is to fill in the COMMODITY_CODE value in the description library, so that all COMMODITY_CODE contents related to the instrument in the description library file of the description special piece are needed to be obtained through the description library interpreter for the user to select, and the user writes the corresponding field after selecting the corresponding field to enter S5.27; if the needed COMMODITY_CODE value cannot be found, the special piece description library needs to be modified first;

s5.26, directly modifying the attribute value into a required value, and entering S5.27;

s5.27, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_204 table in the RA table space of the PDS database, and returning to S5.1;

s5.28, accessing a PDT_205 data table in an RA table space in a PDS database corresponding to the selected item to acquire TAP library item information of the current item, presenting the TAP library item information to a user operation, and entering S5.29 if the item of the operation is an operation_CODE or an end_PREPARATION; if the tap_match_code is operated by the user, proceeding to S5.30; if other attributes are operated on, go to S5.31;

S5.29, the current attribute fills in the attribute index values in the corresponding different tables in the standard annotation library, so that the content of all tables in the standard annotation library file is required to be acquired through the standard annotation library interpreter, and after the user selects the required attribute, the corresponding index value is filled in the corresponding attribute field to enter S5.32; if the required attribute field cannot be found, modifying the standard annotation library first;

s5.30, the current attribute is required to be filled with the COMMODITY_CODE value related to the TAP point in the short description library, so that all COMMODITY_CODE contents related to the TAP point in the short description file are required to be acquired through a description library interpreter for selection by a user, and the user writes the corresponding field after selecting the corresponding field, and then S5.32 is performed; if the needed COMMODITY_CODE value cannot be found, the short description library needs to be modified first;

s5.31, directly modifying the attribute value into a required value, and entering S5.32;

s5.32, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_205 table in the RA table space of the PDS database, and returning to S5.1;

s5.33, accessing a PDT ABLE_211 data table in an RA table space in a PDS database corresponding to the selected item to acquire Size-dependent Materials Data library item information of the current item, presenting the item information to a user for operation, and entering S5.34 if the item of the operation is SYS_COMMODITY_ CODE, COMMODITY _CODE; if other attributes are operated on, go to S5.35;

S5.34, the current attribute is to fill in the COMMODITY_CODE value of the pipeline material in the short description library, so that the content of COMMODITY_CODE related to all pipeline material descriptions in the short description library file is required to be acquired through a description library interpreter for selection by a user, and the corresponding field is written after the user selects the corresponding field, and S5.36 is entered; if the needed COMMODITY_CODE value cannot be found, the short description library needs to be modified first;

s5.35, directly modifying the attribute value into a required value, and entering S5.36;

s5.36, storing the modification record of the user into a database of the system, storing the final modification result into a PDT_211 table in the RA table space of the PDS database, and returning to S5.1;

s5.37, according to the currently selected module of the user, all modification records of the current module are found from a database carried by the system and are loaded to the user for viewing, and if the user needs to rollback the modification records, S5.38 is entered; otherwise, returning to S5.1;

s5.38, carrying out data modification in the reverse direction of the modification record on the data table in the RA table space of the PDS database corresponding to the corresponding module according to the content of the modification record, then adding a new modification record into the database corresponding to the system, prompting the user that the rollback is successful, and returning to S5.1;

S5.39, ending.

In one embodiment of the present invention, the step S6 includes the steps of:

s6.1, if the user hopes to modify the corresponding content of the PJS library, entering S6.2; if the user wishes to modify the corresponding content of the physical size library, entering S6.11; if the user wishes to modify the material description library content, go to S6.21; if the user wishes to modify the standard annotation library content, go to S6.40; if exit is desired, enter S6.45;

s6.2, firstly checking a library file state table in a self-contained database of the system, confirming whether an operator is operating the current PJS module, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, setting the current file state of the PJS library as in use, analyzing the file of the PJS library by the system by calling the PJS interpretation module, acquiring all types of forms in the PJS library and the content of each form, presenting user operation in an operation interface form, and entering S6.3;

s6.3, if the user needs to add the form, entering S6.4; if the user needs to modify the form content, entering S6.5; if the user needs to delete the form, entering S6.6; if the user needs to view the modification record, entering S6.7; the operation is completed, and the operation result is required to be stored to enter S6.9; s6.10, directly entering into the process of S6.10 without storing the result;

S6.4, the user firstly needs to define the newly added PJS table, wherein the newly added PJS table comprises a table name and a table format; after the definition is completed, the system creates a new PJS table, stores the operation record into a temporary table in a database of the system, and returns to S6.3;

s6.5, the user modifies the specific content of the form to be modified according to the requirement, and after modification, the modified record is stored in a temporary table in the self-contained database, and the S6.3 is returned;

s6.6, the user selects the form to be deleted, the system stores the modification record into a temporary table in the self-contained database, and the S6.3 is returned;

s6.7, the system directly accesses a modification record form corresponding to the PJS library in the self-contained database of the system, so that a user can inquire about history modification records, and if a back-off history version is required, the system enters 6.8; otherwise, the query is finished and returns to S6.3;

s6.8, recording the modification condition of the state after rollback into a temporary table in a self-contained database of the system, and returning to S6.3;

s6.9, arranging all modification records in a temporary table corresponding to the PJS table in the current database, converting the current modification records into corresponding data changes in the PJS library file through a PJS compiler module, simultaneously storing the modification records in the temporary table into a formal table corresponding to the PJS library modification records, deleting the temporary table content, changing the PJS library into an idle state in a library file state table, and returning to S6.1;

S6.10, all modification record entries recorded in a temporary table corresponding to the PJS table are emptied, the PJS library is changed into an idle state in a library file state table, and S6.1 is returned;

s6.11, the physical size library of the PDS pipeline reference database is provided with a plurality of standard size library files for selection, and the operation flow of each standard is consistent, so that the specification is carried out by using the American standard size library, and S6.12 is entered;

s6.12, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating a module corresponding to the current American standard physical size library, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, changing the current physical size library state of the American standard into use, analyzing the physical size library file of the American standard by the system through calling a physical size library interpretation module, acquiring all size tables in the physical size library of the American standard, presenting user operation in an operation interface mode, and entering S6.13;

s6.13, if the user needs to add the form, entering S6.14; if the user needs to modify the form content, entering S6.15; if the user needs to delete the form, entering S6.16; if the user needs to view the modification record, S6.17 is entered; the operation is completed, and the operation result is required to be stored to enter S6.19; s6.20, directly entering into the process of S6.20 without storing the result;

S6.14, the user firstly needs to define a new physical size table, including a table name and a table format; after the definition is completed, the system creates a new physical size table, stores the operation record into a temporary table corresponding to the American standard physical size library in the database of the system, and returns to S6.13;

s6.15, the user modifies the specific content of the form to be modified according to the need, and after modification, the modification record is stored in a temporary table corresponding to the American standard physical size library in the self-contained database, and the S6.13 is returned;

s6.16, the user selects the form to be deleted, the system stores the modification record into a temporary table corresponding to the American standard physical size library in the self-contained database, and the S6.13 is returned;

s6.17, the system directly accesses a modification record form corresponding to the American standard physical size library in the self-contained database of the system, so that a user can inquire about history modification records, and if a back-off history version is needed, S6.18 is entered; otherwise, the query is finished and returns to S6.13;

s6.18, recording the modification condition of the state after rollback into a temporary table corresponding to a American standard physical size library in a self-contained database of the system, and returning to S6.13;

s6.19, arranging all modification records in a temporary table corresponding to the American standard physical size library in the current database, converting all the current modification records into corresponding data changes in a American standard physical size library file corresponding to the PJS library through a physical size library compiler module, simultaneously storing the modification records in the temporary table into a formal table corresponding to the modification records of the American standard physical size library, deleting the contents of the temporary table, changing the American standard physical size library into an idle state in a library file state table, and returning to S6.1;

S6.20, all modification record entries recorded in a temporary table corresponding to the American standard physical size library are emptied, the American standard physical size library is changed into an idle state in a library file state table, and S6.1 is returned;

s6.21, if the user wants to modify the short description of the standard component or the corresponding content of the TAP point description, entering S6.22; if the user wishes to modify the standard part length description corresponding content, proceeding to S6.28; if the user wishes to modify the special piece description content, instrument piece description, and hanger description, go to S6.34; the operation is completed and the process returns to S6.1;

s6.22, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating a module corresponding to the current short description library, if so, prompting a user to operate later and informing the user that the user is operating currently, and returning to S6.21; otherwise, changing the current short description library state into an in-use state to enter S6.23;

s6.23, the system analyzes the short description library file by calling a short description library interpretation module to acquire all entries (including standard component short description and TAP point description) of the short description library, and presents user operation in an operation interface form to enter S6.24;

s6.24, if the short description library needs to be added, deleted and modified, entering S6.25; if the modification record of the short description library needs to be checked, the process goes to S6.26;

S6.25, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, converting the modification content into corresponding data change in a short description library file by using a short description library compiling module, changing the short description library into an idle state in a library file state table, and returning to S6.21;

s6.26, the system directly accesses a modification record form corresponding to a short description library in the self-contained database of the system for a user to inquire about history modification records, and if a rollback history version is needed, the system enters S6.27; otherwise, the query is finished, the short description library is changed into an idle state, and S6.21 is returned;

s6.27, recording modification conditions caused by rollback operation into a record table corresponding to a short description library in a self-contained database of the system, converting modification contents into corresponding data changes in a short description library file by using a short description library compiling module, changing the short description library into an idle state in a library file state table, and returning to S6.21;

s6.28, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating a module corresponding to the current long description library, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.21; otherwise, changing the current long description library state into an in-use state to enter S6.29;

S6.29, the system analyzes the long description library file by calling a long description library interpretation module to acquire all entries of the long description library, and the system presents user operation in an operation interface form and enters S6.30;

s6.30, if the long description library needs to be added, deleted and modified, entering S6.31; if the modification record of the long description library needs to be checked, the process goes to S6.32;

s6.31, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, converting the modification content into corresponding data change in a long description library file by using a long description library compiling module, changing the long description library into an idle state in a library file state table, and returning to S6.21;

s6.32, the system directly accesses a modification record form corresponding to a long description library in the self-contained database of the system for a user to inquire about a history modification record, and if a rollback history version is needed, the system enters S6.33; otherwise, the query is finished, the long description library is changed into an idle state in the library file state table, and the S6.21 is returned;

s6.33, recording the modification condition caused by rollback operation into a record table corresponding to a long description library in a self-contained database of the system, converting modification contents into corresponding data changes in a long description library file by using a long description library compiling module, changing the long description library into an idle state in a library file state table, and returning to S6.21;

S6.34, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating a module corresponding to the current special description library, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.21; otherwise, changing the current special piece description library state into an in-use state and entering S6.35;

s6.35, the system analyzes the special piece description library file by calling a special piece description library interpretation module to acquire all items of the special piece description library, and the system presents user operation in an operation interface mode and enters S6.36;

s6.36, if the special part description library needs to be added, deleted and modified, entering S6.37; if the modification record of the special piece description library needs to be checked, the method goes to S6.38;

s6.37, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, simultaneously converting the modification content into corresponding data change in a special piece description library file by using a special piece description library compiling module, changing the special piece description library into an idle state in a library file state table, and returning to S6.21;

s6.38, the system directly accesses a modification record form corresponding to a special piece description library in the self-contained database of the system for a user to inquire about history modification records, and if a back-off history version is needed, the system enters S6.39; otherwise, the query is finished, the special part description library is changed into an idle state in a library file state table, and S6.21 is returned;

S6.39, recording the modification condition caused by rollback operation into a record table corresponding to a special piece description library in a self-contained database of the system, converting modification content into corresponding data change in a special piece description library file by using a special piece description library compiling module, changing the special piece description library into an idle state in a library file state table, and returning to S6.21;

s6.40, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating the current standard annotation library module, if so, prompting the user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, changing the current standard annotation library state into use, the system analyzes the standard annotation library storage file by calling the standard annotation library interpretation module to acquire all types of forms in the standard annotation library and the content of each form, and presents user operation in an operation interface form, and enters S6.41;

s6.41, if the user needs to modify the form content, entering S6.42; if the user needs to view the modification record, S6.43 is entered;

s6.42, the user modifies the specific content of the form to be modified according to the need, the corresponding operation content is stored in a corresponding modification record table of the system, the modification content is converted into corresponding data change in a standard annotation library file by using a standard annotation library compiling module, the standard annotation library is changed into an idle state in a library file state table, and S6.1 is returned;

S6.43, the system directly accesses a modification record form corresponding to a standard annotation library in the self-contained database of the system for a user to inquire about history modification records, and if a rollback history version is needed, the system enters S6.44; otherwise, the query is finished, the standard annotation library is changed into an idle state in a library file state table, and S6.1 is returned;

s6.44, recording the modification condition caused by rollback operation into a record table corresponding to a standard annotation library in a self-contained database of the system, converting the modification content into corresponding data change in a standard annotation library file by using a standard annotation library compiling module, changing the standard annotation library into an idle state in a library file state table, and returning to S6.1;

s6.45, ending.

Compared with the prior art, the management system and the management method for the PDS pipeline reference database provide history record inquiry and version tracing of the pipeline reference database, so that the management of the whole pipeline reference database is more controllable and standard, and the quality of the whole pipeline reference database is ensured; the unified management entrance to the pipeline reference database of the multiple PDS projects is provided, so that unified management and control of the multiple projects are realized; the user authority management and control function is provided, and the safety of the pipeline reference database is improved; the user can rapidly manage the pipeline reference database without editing on the text editor after professional training, thereby improving the working efficiency of the user, greatly reducing the working difficulty and achieving the purpose of the invention.

The features of the present invention will be apparent from the following detailed description of the preferred embodiments, taken in conjunction with the accompanying drawings.

Drawings

FIG. 1 is a schematic diagram of a management system of a PDS pipeline reference database of the invention;

FIG. 2 is a flow chart of a method of managing a PDS pipeline reference database in accordance with the invention;

FIG. 3 is a flow chart of PDS project configuration management, operator account management, and rights management in accordance with the invention;

FIG. 4 is a flow chart of the modification of the pipeline grade library in the reference database according to the present invention;

fig. 5 is a flow chart of the PJS library in the modified reference database of the present invention.

Detailed Description

The invention is further described with reference to the following detailed drawings in order to make the technical means, the creation characteristics, the achievement of the purpose and the effect of the implementation of the invention easy to understand.

Examples

As shown in fig. 1, the PDS pipeline reference database management system of the present invention includes:

As shown in fig. 2, the PDS pipeline reference database management method of the present invention includes the following steps:

s3, entering an operator management main interface, selecting a corresponding item, entering S4 after the selection is finished, and returning to S1 if exiting is required;

s4, selecting a pipeline reference database management module to be operated, and if a pipeline grade library, a special part library, an instrument part library, a TAP table library and a Size-Dependent Material Data library of the PMC management module are required to be operated, entering S5; if other modules need to be operated, entering S6; if the user needs to exit, returning to S1;

s6, the system accesses the related function modules stored in the library files of the selected items, firstly analyzes the bottom files of the selected management modules through an interpreter, feeds back analysis results to a user in a data form in an operation interface, enables an operator to perform corresponding data deletion and correction on the operation interface, records the current operation content of the operator into a database of the management system as a record after the operation is completed, compiles final result data into corresponding PDS pipeline reference database bottom files through a compiler, verifies whether the current compiled files are effective through PDS, notifies the user of failure in updating, records current errors to the management system database, restores the bottom files of the corresponding modules through the management system record recorded in S5, deletes the operation record in S6 after the restoration is successful, and returns to S4; otherwise, prompting the user that the operation is successful, and returning to the step S4 to continue the operation;

S7, ending.

As shown in fig. 3, the PDS project configuration management in the management system, the operator account management of the management system, and the rights management in the step S2 include the following steps:

s2.1, entering an administrator interface, selecting a corresponding management module, and entering S2.2 if a PDS project operable by a configuration system needs to be managed; if the operator account needs to be managed, entering S2.9; if the administrator password needs to be reset, entering S2.14, and if the administrator password needs to be exited, entering S2.15;

s2.3, configuring relevant information of the newly added PDS project, including project names, PDS versions, project units, project database configuration information, absolute paths corresponding to project reference database configuration files and the like, writing the configuration information into a database of the system after the configuration is completed, and returning to S2.2;

s2.10, creating an operator account, wherein the information to be created comprises an operator account name, a password and an operable PDS site (a system automatically reads a currently operable PDS site list from a site file for an administrator to select), storing corresponding data into a database of the system after the creation is completed, and returning to S2.9;

s2.11, the system reads the account information of the operator, the authority matrix of the operator and the project list from the database, and presents the account information, the authority matrix of the operator and the project list to the manager, the manager modifies the mapping relation between the operator and the project according to the requirement, and after the configuration is completed, the result is stored in the database and returns to S2.9;

S2.12, the system reads the operator account information from the database, an administrator selects an operator account to be deleted, and the system enters S2.13 after the selection;

s2.13, deleting an entry corresponding to the operator account from the operator account and the authority mapping table in the database, deleting the corresponding entry from the operator information table in the database, storing the result in the database, and returning to S2.9;

s2.14, inputting a current manager password and a new password by a user, if the current manager password is correct, modifying successfully, and updating the password from the system; otherwise, displaying that the current password is wrong, the password cannot be modified, and returning to S2.1 without updating the administrator password;

s2.15, ending.

As shown in fig. 4, when the system in step S5 accesses the corresponding sub-module in the PMC module of the selected item to modify, corresponding information is first obtained from the corresponding data table in the RA table space in the corresponding PDS database, after the user makes a corresponding modification, the user' S modified content is stored in the database of the system itself, and the final modified result is stored back into the corresponding data table in the RA table space in the PDS database, which includes the following steps:

s5.3, if the user-modified attribute is diameter_ TABLE, SERVICE _limit_ TABLE, THICKNESS _ TABLE, MATERIAL _ DESCRIPTION, MATERIAL _table, branch_table, band_select_table, and pipe_length_table, proceeding to S5.4; if the user modifies the TAP_DATA_TABLE attribute, proceed to S5.5; if the user modifies the FLUID_ CODE, STANDARD _NOTE_NO_ A, STANDARD _NOTE_NO_B attribute, then S5.6 is entered; otherwise, directly entering S5.7;

s5.10, if the user operates comodity_name, option_code, end_prep, table_ SUFFIX, GEOMETRIC _ STANDARD, WEIGHT _ CODE, FABRICATION _ CAT, MATERIALS _ GRADE, STANDARD _note_no, go to S5.11; if the user operates gcp_from_nom_dim_dim, gcp_to_nom_dim, rcp_from_nom_dim, rcp_to_nom_dim, go TO S5.12; if the user operates the COMMODITY_CODE, go to S5.13; if other attributes are operated on, go to S5.14;

s5.16, accessing a PDT ABLE_203 data TABLE in an RA TABLE space in a PDS database corresponding to the selected item to acquire special piece library item information of the current item, presenting the special piece library item information to a user operation, and entering S5.17 if the attribute of the operation is OPTION_CODE, END_PREP, TABLE_ SUFFIX, GEOMETRIC _ STANDARD, WEIGHT _ CODE, FABRICATION _ CAT, MATERIALS _ GRADE, STANDARD _NOTE_NO; if the user operates gcp_from_nom_dim_dim, gcp_to_nom_dim, rcp_from_nom_dim, rcp_to_nom_dim, go TO S5.18; if the user operates PING_COMP_NO, entering S5.19; if other attributes are operated on, go to S5.20;

s5.22, accessing a PDT_204 data TABLE in an RA TABLE space in a PDS database corresponding to the selected item to acquire instrument library item information of the current item, presenting the instrument library item information to a user operation, and entering S5.23 if the attribute of the operation is OPTION_CODE, END_PREP, TABLE_ SUFFIX, GEOMETRIC _ STANDARD, WEIGHT _ CODE, FABRICATION _ CAT, MATERIALS _ GRADE, STANDARD _NOTE_NO; if the user operates gcp_from_nom_dim_dim, gcp_to_nom_dim, rcp_from_nom_dim, rcp_to_nom_dim, go TO S5.24; if the user operates INSTRUMENT_COMP_NO, entering S5.25; if other attributes are operated on, go to S5.26;

s5.39, ending.

As shown in fig. 5, the step S6 includes the steps of:

s6.2, firstly checking a library file state table in a self-contained database of the system, confirming whether an operator is operating the current PJS module, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, setting the current file state of the PJS library as in use, and analyzing the files PJS _tbl.l, PJS _tbl.l.t and PJS _tbl.l.r of the PJS library by the system through calling the PJS interpretation module to acquire all types of forms and contents of each form in the PJS library, and presenting user operation in an operation interface mode, and entering S6.3;

s6.4, the user firstly needs to define the newly added PJS table, wherein the newly added PJS table comprises a table name and a table format; the head of the PJS table on the table format at least comprises an input value and an output value, the input value is at the front, the output value is at the back, the input and output values are up to 10, meanwhile, each value needs to be defined with a unit, after the definition is finished, the system creates a new PJS table, and the operation record is stored in a temporary table in a database of the system, and the system returns to S6.3;

s6.9, arranging all modification records in a temporary table corresponding to the PJS table in the current database, converting the current modification records into corresponding data changes in PJS _tbl.l, PJS _tbl.l.t and PJS _tbl.r files corresponding to the PJS library through a PJS compiler module, simultaneously storing the modification records in the temporary table into a formal table corresponding to the modification records of the PJS library, deleting the temporary table content, changing the PJS library into an idle state in a library file state table, and returning to S6.1;

s6.12, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating a module corresponding to the current American standard physical size library, if so, prompting a user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, changing the current physical size library state of the American standard into use, the system analyzes the files us_pcdim.l, us_pcdim.l.t and us_pcdim.l.r of the physical size library of the American standard by calling a physical size library interpretation module to acquire all size tables in the physical size library of the American standard, and presents user operation in an operation interface mode to enter S6.13;

s6.14, the user firstly needs to define a new physical size table, including a table name and a table format; the header of the physical size table on the table format at least comprises an input value and an output value, wherein the input value is the front, the output value is the rear, the input and the output are up to 10, meanwhile, each value needs to be defined with a unit, after the definition is finished, the system creates a new physical size table, and an operation record is stored in a temporary table corresponding to a American standard physical size library in a database carried by the system, and S6.13 is returned;

s6.19, arranging all modification records in a temporary table corresponding to the American standard physical size library in the current database, converting all modification records into corresponding data changes in American standard physical size library files us_pcdim.l, us_pcdim.l.t and us_pcdim.l.r corresponding to the PJS library through a physical size library compiler module, storing the modification records in the temporary table into a formal table corresponding to the modification records of the American standard physical size library, deleting the contents of the temporary table, changing the American standard physical size library into an idle state in a library file state table, and returning to S6.1;

s6.23, the system analyzes the short description library file short_bom.l file by calling a short description library interpretation module to acquire all entries (including standard component short description and TAP point description) of the short description library, and presents user operation in an operation interface form, and then enters S6.24;

s6.25, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, converting the modification content into corresponding data change in a short_bom.l file by using a short description library compiling module, changing a short description library into an idle state in a library file state table, and returning to S6.21;

S6.26, the system directly accesses a modification record form corresponding to a short description library in the self-contained database of the system for a user to inquire about history modification records, and if a rollback history version is needed, the system enters S6.27; otherwise, the inquiry is finished, the short description library state is changed into idle state, and S6.21 is returned;

s6.27, recording modification conditions caused by rollback operation into a record table corresponding to a short description library in a self-contained database of the system, converting modification contents into corresponding data changes in a short_bom.l file by using a short description library compiling module, changing the short description library into an idle state in a library file state table, and returning to S6.21;

s6.29, the system analyzes the long description library file long_bom.l file by calling the long description library interpretation module to acquire all entries of the long description library, presents user operation in an operation interface mode, and enters S6.30;

s6.31, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, converting the modification content into corresponding data change in a long_bom.l file by using a long description library compiling module, changing a long description library into an idle state in a library file state table, and returning to S6.21;

s6.33, recording the modification condition caused by rollback operation into a record table corresponding to a long description library in a self-contained database of the system, converting the modification content into corresponding data change in a long_bom.l file by using a long description library compiling module, changing the long description library into an idle state in a library file state table, and returning to S6.21;

S6.35, the system analyzes the special piece description library file spclty_bom.l file by calling the special piece description library interpretation module to acquire all the entries of the special piece description library, and the system presents user operation in an operation interface form and enters S6.36;

s6.37, after the user performs corresponding addition, deletion and modification, storing corresponding operation content into a corresponding modification record table of the system, converting the modification content into corresponding data change in the spclty_bom.l file by using a special piece description library compiling module, changing the special piece description library into an idle state in a library file state table, and returning to S6.21;

s6.39, recording the modification condition caused by rollback operation into a record table corresponding to a special piece description library in a self-contained database of the system, converting the modification content into corresponding data change in the spclty_bom.l file by using a special piece description library compiling module, changing the special piece description library into an idle state in a library file state table, and returning to S6.21;

S6.40, checking a library file state table in a self-contained database of the system, confirming whether an operator is operating the current standard annotation library module, if so, prompting the user to operate later and informing the user that the user is currently operating, and returning to S6.2; otherwise, changing the current standard annotation library state into use, the system analyzes the standard annotation library storage files std_note.l and std_note.l.t by calling a standard annotation library interpretation module to acquire all types of forms and the contents of each form in the standard annotation library, and presents user operation in an operation interface mode to enter S6.41;

s6.42, the user modifies the specific content of the form to be modified according to the need, the corresponding operation content is stored in a corresponding modification record table of the system, meanwhile, the modification content is converted into corresponding data changes in std_note.l and std_note.l.t files by using a standard annotation library compiling module, the standard annotation library is changed into an idle state in a library file state table, and S6.1 is returned;

S6.44, recording the modification condition caused by rollback operation into a record table corresponding to a standard annotation library in a database of the system, converting the modification content into corresponding data changes in std_note.l and std_note.l.t files by using a standard annotation library compiling module, changing the standard annotation library into an idle state in a library file state table, and returning to S6.1;

s6.45, ending.

The management system and method of the PDS pipeline reference database have the following beneficial effects:

1. the PDS pipeline reference database operation method (visual operation interface and integration of calling relations among internal modules) is more convenient and fast, and a user can rapidly manage the pipeline reference database without editing on a text editor after professional training, so that the working efficiency of the user is improved, and the working difficulty is greatly reduced;

2. the history record inquiry and version tracing of the pipeline reference database are provided, so that the management of the whole pipeline reference database is more controllable and standard, and the quality of the whole pipeline reference database is ensured;

3. the unified management entrance to the pipeline reference database of the multiple PDS projects is provided, so that unified management and control of the multiple projects are realized;

4. The user authority management and control function is provided, and the security of the pipeline reference database is improved.

The foregoing has shown and described the basic principles and main features of the present invention and the advantages of the present invention. It will be understood by those skilled in the art that the present invention is not limited to the foregoing embodiments, which have been described in the foregoing embodiments and description merely illustrates the principles of the invention, and that various changes and modifications may be effected therein without departing from the spirit and scope of the invention as defined in the appended claims and their equivalents.

Claims

1. A PDS pipeline reference database management system and method are characterized by comprising:

2. The PDS pipeline reference database management method is characterized by comprising the following steps:

S7, ending.

3. The PDS pipeline reference database management method according to claim 2, wherein the PDS project configuration management, the operator account management, and the rights management in the management system in step S2 include the following steps:

S2.14, ending.

4. The PDS pipeline reference database management method according to claim 2, wherein when the system in step S5 accesses the corresponding sub-module in the PMC module of the selected item to modify, corresponding information is first obtained from the corresponding data table in the RA table space in the corresponding PDS database, after the user makes a corresponding modification, the modified content of the user is stored in the database of the system itself, and the final modified result is stored back in the corresponding data table in the RA table space in the PDS database, and the method includes the following steps:

s5.39, ending.

5. The method for managing a PDS pipeline reference database according to claim 2, wherein said step S6 includes the steps of:

s6.45, ending.