A flowmaster-based component model and system model storage and knowledge integration method

Abstract

The application belongs to the technical field of knowledge engineering, and discloses a component model and system model storage and knowledge integration method based on Flowmaster, which comprises the following steps: step one: configuring storage database address, user information, and working directory, wherein the storage database comprises component library, system library, and knowledge base and other sub-libraries; step two: establishing component model and system model, and uploading the component model and system model to corresponding libraries; step three: importing the component model and system model saved in the component library and the system library into Flowmaster; and step four: associating the component model and system model with knowledge.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of knowledge engineering, and particularly relates to a component model and system model storage and knowledge integration method based on Flowmaster. BACKGROUND

[0002] In the process of modeling simulation using Flowmaster software, a component model is usually newly created or selected from the database of the Flowmaster software, a simulation system model is established, and then the characteristic parameters of the corresponding component model are input. With the increase of simulation work, many component models with the same parameters are used in different system models, or the system models are consistent, but only the parameters are different, and are used by different designers. At this time, it is necessary to make customer customized component models and system models and to uniformly manage them for use by different designers. The customized component models or system models do not have accompanying explanations and related knowledge, and are usually difficult to understand. In order to enable different designers to have a more detailed understanding of the components or system models after selecting the corresponding components or system models, it is necessary to integrate the component models or system models with the corresponding knowledge. SUMMARY

[0003] The application discloses a component model and system model storage and knowledge integration method based on Flowmaster, realizes the uniform management of mature component models and system models, and promotes the reuse of the component models and system models in a convenient manner. The Flowmaster component models and system models are accurately saved in a one-to-one manner by adopting a C / S and B / S management mode of a webpage plus a database. The component model parameters are stored in the database in the form of a clear table, and are remotely managed on the webpage. Meanwhile, the component models and system models are bound and associated with knowledge, so that in the process of system model design, simulation analysis or task execution, designers can check and refer to the related knowledge content at any time, so as to more efficiently complete the work. The binding logic expands the ease of use of Flowmaster. In actual application, designers can directly download the required component models or system models, and the plug-in can automatically write the configured parameters into the component models, so as to ensure that the Flowmaster component models can be flexibly reused. When the Flowmaster plug-in is closely associated with an actual product, the Flowmaster plug-in can realize an automatic conversion process, and in the use process, the knowledge corresponding to the component models and system models can be conveniently checked. The seamless connection from virtual design to actual product is ensured, and the work efficiency and accuracy are further improved. This not only enhances the convenience of work, but also improves the universality.

[0004] TECHNICAL SCHEME

[0005] A component model storage and knowledge integration method based on Flowmaster, steps as follows:

[0006] Step one: configure storage database address, user information, and working directory, wherein the storage database includes component library, system library, and knowledge base and other sub-libraries;

[0007] Step two: establish component model and system model, upload component model and system model to corresponding library;

[0008] Step three: import component model and system model saved in component library and system library into Flowmaster;

[0009] Step four: associate component model and system model with knowledge.

[0010] Further, in step one, the specific process is as follows:

[0011] Save the storage database address and working directory information in encrypted form; when uploading or importing data, use the storage database address to retrieve data, and use the specified working directory to store temporary files;

[0012] After completing the configuration, verify the user identity through a single sign-on mechanism; the user provides authentication through fingerprint recognition, and the system obtains the user's key from this; the key is verified through the TokenWS Web service interface to confirm that the configuration process is successfully completed;

[0013] Determine whether the configuration is successful according to the result returned by the interface; if successful, persistently store the configuration information.

[0014] Further, in step two, the uploading process of the component model is as follows:

[0015] 1a. Open or create a Network model in Flowmaster;

[0016] 1b. Drag and drop the required component model into the Network model and edit the properties of the component model;

[0017] 1c. Before uploading, use the Database component in Flowmaster to extract the component model and its properties and position information in the Network model;

[0018] 1d. Initialize the Flowmaster component, obtain all project structures and Network models therein from ProjectNames, and build a model structure tree;

[0019] 1e. Select the corresponding Network model from the model structure tree, load the component model attribute information, and display it in a table format, including the component model name and category. Other attributes are saved to the working directory in JSON format.

[0020] 1f. The user selects the component model to upload and specifies the target component library node;

[0021] 1g. Compress and merge the selected files and their attribute JSON files;

[0022] 1h. Create an HTTP request using HttpWebRequest and set a timeout; add a key to the request header to verify the user's identity;

[0023] 1i. Use BinaryReader to read the file, convert it into a byte stream, and read the file in 4KB segments in a loop. Then, use the previously created HttpWebRequest object to upload the file.

[0024] 1j. After starting the upload, obtain the response from the storage database via WebResponse, and parse the returned data to determine the next step;

[0025] 1k. Use the POST method of the RESTful interface to record upload logs, including user key, file name, file ID, and upload device information;

[0026] 1. After the upload is complete, the storage database returns the file's storage ID, which is used for subsequent file information queries and file downloads.

[0027] Furthermore, in step two, the process of uploading the system model is as follows:

[0028] 2a. Open or create a new Network system model in Flowmaster;

[0029] 2b. Construct the Network system model by dragging and dropping component models, connecting component models, and filling in component model properties;

[0030] 2c. When preparing to upload a system model, access the storage database via a RESTful API to obtain the system model library data, and display it to the user in a tree structure for them to select the appropriate system model;

[0031] 2d. Initialize the Flowmaster component, retrieve all project structures and their Network system models from ProjectNames, and construct a model structure tree;

[0032] 2e. Use the GetfmNetwork method of Flowmaster to obtain the attribute and component model information of the current Network according to the name and parent node of the current Network, and display them in a tree structure;

[0033] 2f. Use the PackNetwork method of Flowmaster to pack the data of the current Network into an FMDNA file and store it in the working directory;

[0034] 2g. Obtain the IDs of all component models in the model through the ComponentIDs method of Flowmaster, and loop through these IDs to obtain the link relationship, position and other attributes of each component model using the Component method, to ensure that the component model can be correctly placed when using the system model;

[0035] 2h. After collecting the component model attributes, store these data properly to restore the custom attributes of the component model in the subsequent import process;

[0036] 2i. Compress the model file and its attribute file into a package;

[0037] 2j. Use HttpWebRequest to create an HTTP request and set the timeout; add a key to the request header to verify the user's identity;

[0038] 2k. Use BinaryReader to read the file and convert it into a byte stream, loop through the file in 4KB segments and use the previously created HttpWebRequest object to upload;

[0039] 2l. After starting the upload, obtain the response from the storage database side through WebResponse and parse the returned data;

[0040] 2m. Perform the next operation according to the parsed information;

[0041] 2n. Use the POST method of the RESTful interface to record the upload log, which includes the user key, file name, file ID and upload device information;

[0042] 2o. After the upload is complete, the storage database returns the storage ID of the file, which is used for subsequent file information query and file download.

[0043] Further, in step three, the component model import process is as follows:

[0044] 3a. Open or create a new Network model in Flowmaster;

[0045] 3b. Select import function, access storage database interface through RESTful API to get component library data, and show component library content in tree structure;

[0046] 3c. Select component model to be imported;

[0047] 3d. Initialize Flowmaster component, get all project structures and Network model in ProjectNames, and build a Network model structure tree;

[0048] 3e. Get download link of selected file;

[0049] 3f. Create local storage folder to store downloaded file;

[0050] 3g. Use HttpWebRequest to create HTTP request for downloading file;

[0051] 3h. If file name is known, use the name to create file; otherwise, use file name in Content-Disposition parameter returned by request;

[0052] 3i. Use FileStream to write file into created file through byte array obtained;

[0053] 3j. Use POST method of RESTful interface to record download log, including user key, file name, file ID and download device information;

[0054] 3k. Decompress file, and according to selected component model, use commandLine.FMDNA method to create component model in Network model in turn;

[0055] 3l. After creation, use fmComponent.SetCLValue method to write component model attribute into corresponding component model.

[0056] Further, in step three, system model import process is as follows:

[0057] 4a. Log in through storage database login interface and configuration information;

[0058] 4b. Access storage database interface through restful, get system model library data, and show data in tree structure;

[0059] 4c. Initialize the Flowmaster component, get all Project structures according to ProjectNames, and the Network model under the Project structure. Organize the obtained structures into a model structure tree;

[0060] 4d. Select the system model to be imported in the system model library tree structure, and download the system model to the configured working directory;

[0061] 4e. Open the system model using UnpackNetwork to import it into the Project, or select the path to store the file to the corresponding path.

[0062] Further, in step four, the knowledge includes:

[0063] Standard specifications, select applicable standards, and accurately correspond specific clauses to elements or systems in the design;

[0064] Scientific literature, find and link relevant research reports and technical documents to provide theoretical basis and support for elements or systems;

[0065] Method steps, organize and reference detailed implementation processes and operation guidelines;

[0066] Technical experts, associate with authoritative experts in the field to provide professional advice and guidance for the design of elements or systems;

[0067] Risk measures, provide possible risks and problems, and give solutions to potential problems;

[0068] Common problems, collect problems encountered in previous projects and their solutions;

[0069] Technical documents, store relevant specifications and manuals.

[0070] Further, in step four, the element model associated knowledge process is as follows:

[0071] 5a. After the element model is successfully uploaded, manage the element model using the data repository;

[0072] 5b. In the storage database, view the Flowmaster element model library;

[0073] 5c. Create a classification for the Flowmaster element library to manage each element model;

[0074] 5d. Select the Flowmaster component model for which you want to associate knowledge, and obtain the node ID of the component model. The database automatically creates a knowledge association form, which contains keywords such as knowledge type and knowledge item to record knowledge type and knowledge ID. Multiple knowledge type and knowledge item keywords can be added. Knowledge items belong to knowledge types so that they can be categorized by knowledge type when displayed. At the same time, multiple component model and system model indexes are created in the knowledge items.

[0075] 5e. Based on the selected component model attributes, search for or create corresponding knowledge types and knowledge entries in the knowledge base. Knowledge entry content should include the method for determining the parameter settings of each component model and the standards and specifications followed. Multiple knowledge types and multiple knowledge entries can be selected simultaneously. 5f. After selecting a knowledge entry, use the RESTful interface KECombine to store the component model ID, knowledge type, and knowledge ID in the knowledge association form of the data repository, forming an association reference. Store the component model ID, knowledge ID, model type, and knowledge type as a single data entry. One component model can be associated with multiple knowledge entries and knowledge types.

[0076] 5g. After association, when viewing a component model, all associated knowledge types and knowledge IDs can be retrieved through the component model ID in the data repository, and specific knowledge information can be viewed through the knowledge ID. Alternatively, the component model and system model indexes in the knowledge entry can be used to determine which component models and system models the knowledge is applied to.

[0077] Furthermore, in step four, the process of associating knowledge with the system model is as follows:

[0078] 6a. After the system model is successfully uploaded, manage the system model using the data repository;

[0079] 6b. In the storage database, view the Flowmaster system library;

[0080] 6c. Select the Flowmaster system model for which you want to associate knowledge; the database automatically creates a knowledge association form. This form contains keywords such as knowledge type and knowledge item, used to record knowledge type and knowledge ID. Multiple knowledge type and knowledge item keywords can be added. Knowledge items belong to knowledge types, allowing for categorization by knowledge type when displaying them. Simultaneously, multiple component model and system model indexes are created within each knowledge item.

[0081] 6d. Based on the selected system model attributes, search for or create corresponding knowledge types and knowledge entries in the knowledge base. Knowledge entry content should include the methods for determining the parameters of the component model and system model, the standards and specifications followed, and methods for simplifying the system model. Multiple knowledge types and multiple knowledge entries can be selected simultaneously.

[0082] 6e. After selecting a knowledge item, store the knowledge type and knowledge ID along with the system model ID in the database knowledge association form to form an association reference. In the storage database, store the system model ID, knowledge ID, model type, and knowledge type as a single data entry, with one system model associated with multiple knowledge items and knowledge types;

[0083] 6f. When using the system model later, review the related knowledge associated with the system model. You can also find out which component models and system models the knowledge applies to by referring to the component model and system model indexes in the knowledge entries.

[0084] In summary, the beneficial effects of the present invention are as follows:

[0085] a) Unified management of customer-customized Flowmaster component and system models allows for model reuse and improves designers' work efficiency;

[0086] b) Flowmaster component and system models are linked to knowledge. Designers can consult relevant standards, specifications, and literature to understand how and why parameters are set in this way, as well as why the system model is constructed in this manner and how to simplify it. Attached Figure Description

[0087] Figure 1 This is a schematic diagram of the knowledge business process for component models;

[0088] The Flowmaster component library in the storage database is categorized by component model. Each category contains several customized component models with specific parameters. The component models are associated with the knowledge base through knowledge attributes, and specifically with specific knowledge entries in the technical expert database, method and procedure database, etc.

[0089] In Flowmaster software, a custom component model with specific parameters is referenced to create an instantiated component model. The instantiated component model allows you to view its related knowledge entries.

[0090] Figure 2 This is a schematic diagram of the knowledge business process in the system model;

[0091] The system library in the storage database is classified according to system models, and each system model contains a plurality of system models with specific parameters, and the system models are associated with the knowledge base through knowledge attributes, and are specifically associated with specific knowledge entries in the technical expert library, the method step library and the like.

[0092] The system model with specific parameters is cited in the Flowmaster software to form an instantiated system model. The instantiated system model can view the related knowledge entries.

[0093] Figure 3 The plug-in operation flowchart is shown in the figure;

[0094] The Flowmaster network model is opened, the element model is loaded, the specific parameters of the element model are set and the parameters are extracted, the element model is uploaded to the element library, then the knowledge is associated, and is stored in the database, at this time, the knowledge can be viewed, or the element model uploading, knowledge association can be repeated.

[0095] The knowledge can be viewed when the element model is downloaded, and the parameters are written into the element model, a plurality of element models can be downloaded to be combined to generate a system model.

[0096] Figure 4 The class diagram is shown in the figure;

[0097] The classes for method implementation mainly include FMDNA, Logon, MSFMModel, MSFMDNA, FlowmasterHelper and Flowmaster.gui, wherein the MSFMModel is used to acquire the attribute information of all element models, connection points and connection lines under the network according to the Project and the network, for example, the element model position, the connection point number, the start position and the end position of the connection line and the like. The MSFMDNA is used to log in the Flowmaster to acquire all Projects and networks of the Flowmaster. The FlowmasterHelper is used for user initialization. The Flowmaster.gui is used to complete the login according to the configuration information, acquire the operation of the Flowmaster attribute, and exit after the operation is completed.

[0098] Figure 5 The FMDNA and Logon attribute diagram is shown in the figure;

[0099] The Logon reads the configuration file to acquire the information of the fmconfig.xml for logging in the Flowmaster. After the FMDNA is logged in by the Logon, the information of all Projects and networks, and the information of the Eyepoint and the ViewPoint are acquired.

[0100] Figure 6 Flowmaster component library diagram;

[0101] Flowmaster component library interface as shown, including tree structure classification and specific component model, specific component model interface including details, parameters, etc. and standard norms, scientific literature and other knowledge.

[0102] Figure 7 Flowmaster system library diagram;

[0103] Flowmaster system library interface as shown, including classification and specific system model, including model, simulation results and standard norms, scientific literature and other knowledge.

[0104] Figure 8 Flowmaster plug-in upload diagram;

[0105] Interface as shown, the left is the tree structure of the system library and component library obtained from the storage database; The upper right is the tree structure of project and network obtained from Flowmaster; The lower right is the component model obtained from the network. By selecting the component model on the left and the component model on the lower right, confirmation upload is realized.

[0106] Figure 9 Flowmaster plug-in download diagram.

[0107] Interface as shown, select the model in the component library or system library obtained from the storage database, can save as or directly open the model. DETAILED DESCRIPTION

[0108] A component model storage and knowledge integration method based on Flowmaster, which realizes accurate extraction of various component models and their detailed parameters from Flowmaster models, and uploads the component models and parameters to the Flowmaster component library with one key, and associates with knowledge. Subsequent designers have great flexibility when using Flowmaster software. Not only can they easily browse the component library, select the required component model and browse the associated knowledge, but also can import these component models into the Flowmaster system model. More conveniently, the parameters carried by the component model will also be automatically written into the system model, greatly simplifying the system model configuration process, improving the modeling efficiency, and enabling users to focus more on model analysis and optimization work.

[0109] The application takes the storage database function as the core, fully gives play to its powerful data processing and model management capability. Meanwhile, taking the Flowmaster plug-in as an important auxiliary tool, through its upload and download functions, the efficient circulation and sharing of component models and system models and parameters are realized, the linkage between component models and system models and knowledge is realized through knowledge association, and the association of knowledge can also promote the sharing and inheritance of knowledge. Through the binding of component models and system models and knowledge ID, the related knowledge content can be integrated into the database, so that other users can conveniently obtain and use these knowledge. This not only can avoid the loss and forgetfulness of knowledge, but also can improve the knowledge level and innovation ability of the whole team.

[0110] The application comprises four modules, which are configuration, upload, import and associated knowledge. The module functions are as follows:

[0111] 1) Configuration: used for configuring the storage database address, user information and working directory.

[0112] 2) Upload: the upload module is divided into component model upload and system model upload. In order to facilitate the management of component models and system models, the Flowmaster component library and the Flowmaster system library are established respectively. The component model upload can upload the component model to the Flowmaster component library, and the component library is a storage library for saving various Flowmaster components (such as pipes, valves, pumps, etc.). These components can be reused, thereby improving the design efficiency; the system model upload can upload the system model to the Flowmaster system model library, and the system model library is used for saving the Flowmaster system model to the storage database, and has the function of viewing.

[0113] 3) Import: the import module is divided into component model import and system model import, and the component model and system model saved in the storage database are imported into Flowmaster.

[0114] 4) Associated knowledge: the component model and system model stored in the storage database are associated with the knowledge in the storage database, so as to facilitate the viewing of knowledge when using the component model or system model.

[0115] The function realization method is as follows:

[0116] 1) Configuration:

[0117] a. Set the storage database address and working directory, and save these configuration information in an encrypted form. When uploading or importing data, the storage database address is used to retrieve data, and the specified working directory is used to store temporary files;

[0118] b. After the configuration is completed, the user identity is verified through a single sign-on mechanism. Specifically, the user provides authentication through fingerprint recognition, and the system thereby obtains the user's key. Subsequently, the key is verified through a call to the TokenWS Web service interface to confirm that the configuration process is successfully completed;

[0119] c. Determine whether the configuration is successful according to the result returned by the interface; if so, persistently store the configuration information.

[0120] 2) Upload

[0121] a) Upload of component models

[0122] a. Open or create a Network model in Flowmaster;

[0123] b. Drag and drop the required component models into the Network model and edit the properties of the component models, such as the rated head, flow, or flow-pressure curve of the pump;

[0124] c. Before uploading, use the Database component in the Flowmaster component to extract the component models, their properties, and location information in the Network model;

[0125] d. Initialize the Flowmaster component to obtain all project structures and Network models therein from ProjectNames and construct a model structure tree;

[0126] e. Select the corresponding Network model from the model structure tree, load the component model properties, and display them in table form, including the component model name and classification, and other properties such as the rated head, flow, or flow-pressure curve of the pump, which are saved in JSON format to the working directory;

[0127] f. The user selects the component models to be uploaded and specifies the target component library node;

[0128] g. Compress and merge the selected files and their property JSON files;

[0129] h. Create an HTTP request using HttpWebRequest and set the timeout; add a key to the request header to verify the user identity;

[0130] i. Use BinaryReader to read the file, convert it to a byte stream, and read the file in 4KB segments, and use the previously created HttpWebRequest object to upload;

[0131] j. After starting uploading, get the response from the storage database end through WebResponse, and parse the returned data to determine the next operation;

[0132] k. Record the upload log using the POST method of the Restful interface, including user key, file name, file ID, and upload device information;

[0133] l. After uploading is completed, the storage database returns the storage ID of the file, which can be used for subsequent query of file information and download of the file.

[0134] b) Upload of system model

[0135] a. Open or create a Network system model in the Flowmaster software environment;

[0136] b. Build the Network system model by dragging component models, connecting component models, and filling in component model attributes;

[0137] c. When preparing to upload the system model, access the storage database through the RESTful API to obtain system model library data and display it in a tree structure for the user to select the corresponding system model;

[0138] d. Initialize the Flowmaster component to obtain all project structures and Network system models therein from ProjectNames and build a model structure tree;

[0139] e. Use the GetfmNetwork method of Flowmaster to obtain the attributes and component model information of the Network according to the current Network name and parent node, and display it in a tree structure;

[0140] f. Use the PackNetwork method of Flowmaster to pack the data of the current Network into an FMDNA file and store it in the working directory (the FMDNA file can use the UnpackNetwork method when imported);

[0141] g. Obtain the IDs of all component models in the model through the ComponentIDs method of Flowmaster, and loop through these IDs to obtain the link relationship, position, and other attributes of each component model using the Component method to ensure that the component model can be correctly placed when using the system model;

[0142] h. After collecting the component model attributes, properly store these data to restore the custom attributes of the component model in the subsequent import process;

[0143] i. Compress the model file and its attribute file into a package;

[0144] j. Create an HTTP request using HttpWebRequest and set the timeout; add a key in the request header to verify the user's identity;

[0145] k. Use BinaryReader to read the file and convert it into a byte stream, loop through the file in 4KB segments, and use the previously created HttpWebRequest object to upload;

[0146] l. After starting the upload, get the response from the storage database side through WebResponse and parse the returned data;

[0147] m. Perform the next operation according to the parsed information;

[0148] n. Use the POST method of the RESTful interface to record the upload log, including the user key, file name, file ID, and upload device information;

[0149] o. After the upload is complete, the storage database returns the storage ID of the file, which can be used for subsequent file information query and file download.

[0150] 3) Import

[0151] a) Import of component models

[0152] a. Open or create a Network model in Flowmaster;

[0153] b. Select the import function, access the storage database interface through the RESTful API to obtain component library data, and display the component library content in a tree structure;

[0154] c. Select the component model to be imported;

[0155] d. Initialize the Flowmaster component, obtain all project structures and Network models from ProjectNames, and build a Network model structure tree;

[0156] e. Get the download link of the selected file;

[0157] f. Create a local storage folder to store the downloaded file;

[0158] g. Use HttpWebRequest to create an HTTP request for downloading the file;

[0159] h. If the file name is known, use the name to create the file; otherwise, use the file name in the Content-Disposition parameter returned by the request;

[0160] i. Write the file into the created file using FileStream through the byte array obtained;

[0161] j. Record the download log using the POST method of the RESTful interface, including the user key, file name, file ID, and download device information;

[0162] k. Decompress the file and use the commandLine.FMDNA method to create element models in the Network model in turn according to the selected element model;

[0163] l. After creation, use the fmComponent.SetCLValue method to write element model properties into the corresponding element model.

[0164] b) Import of system model

[0165] a. Log in through the storage database login interface and configuration information;

[0166] b. Access the storage database interface through restful, obtain system model library data, and display the data in tree structure;

[0167] c. Initialize the Flowmaster component, obtain all Project structures and Network models under the Project structure according to ProjectNames, and organize the obtained structures into a model structure tree;

[0168] d. Select the system model to be imported in the system model tree structure, and download the system model to the configured working directory;

[0169] e. Open the system model and import it into Project using UnpackNetwork, or select the path to store the file to the corresponding path.

[0170] 4) Associated knowledge

[0171] In order to better store and utilize knowledge, a knowledge base is specially established, which includes sub-bases of knowledge types such as standard specifications, scientific and technical literature, method steps, technical experts, risk measures, common problems, and technical documents.

[0172] Standard specifications can select applicable standards and accurately correspond specific clauses with elements or systems in design, ensuring that technical implementation conforms to industry regulations.

[0173] Scientific literature, which can find and link related research reports and technical documents, provide theoretical basis and support for components or systems.

[0174] Method steps, detailed implementation process and operation guide to ensure that each step can be correctly applied to the corresponding components or systems.

[0175] Technical experts, which can associate with authoritative experts in the field, provide professional advice and guidance for the design of components or systems.

[0176] Risk measures, which provide possible risks and problems and solutions to potential problems, ensure that risk management of components or systems is considered in the design stage.

[0177] Common problems, which collect problems encountered in previous projects and their solutions, facilitate quick positioning and solution of common problems that may occur in the development process of components or systems.

[0178] Technical documents, which store relevant specifications, manuals and other documents, ensure that the design and manufacturing process of components or systems have basis.

[0179] a) Component model associated knowledge

[0180] a. After the component model is uploaded successfully, the data repository is used to manage the component model;

[0181] b. In the storage database, view the Flowmaster component library;

[0182] c. The Flowmaster component library can create categories to manage each component model;

[0183] d. Select the Flowmaster component model that needs to be associated with knowledge, and get the node ID of the component model; the database automatically establishes a knowledge association form, which contains keywords such as knowledge type and knowledge item, to record knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be extended, and knowledge items belong to knowledge types, so that knowledge items can be classified by knowledge types when displayed. At the same time, multiple component models and system model indexes are established in the knowledge item.

[0184] e. According to the selected properties of the component model, find or create the corresponding knowledge type and knowledge item in the knowledge base. The content of the knowledge item should include the method of setting the parameters of the component model and the standard specification followed. Multiple knowledge types and multiple knowledge items can be selected at the same time.

[0185] f. After selecting the knowledge item, the RESTful interface KECombine stores the element model ID, knowledge type and knowledge ID into the data repository knowledge association form, forms an association reference, and stores the element model ID, knowledge ID, model type, knowledge type as one piece of data. One element model can be associated with multiple knowledge and knowledge types;

[0186] g. After association, when viewing the element model, all associated knowledge types and knowledge IDs can be obtained through the element model ID in the data repository, and specific knowledge information can be viewed through the knowledge ID. The element model and system model index in the knowledge item can also know which element models and system models the knowledge is applied to.

[0187] h. When using the element model later, the relevant knowledge associated with the element model, such as element model parameter setting requirements and followed specifications, can be viewed.

[0188] b) System model associated knowledge

[0189] a. After the system model is uploaded successfully, the data repository is used to manage the system model;

[0190] b. In the storage database, view the Flowmaster system library;

[0191] c. Select the Flowmaster system model that needs to be associated with knowledge; the database automatically establishes a knowledge association form, which contains keywords such as knowledge type and knowledge item, for recording knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be extended as keywords. Knowledge items belong to knowledge types, so that knowledge items can be classified by knowledge types when displayed. At the same time, multiple element models and system model indexes are established in the knowledge item.

[0192] d. According to the selected system model properties, find or create the corresponding knowledge type and knowledge item in the knowledge base. The knowledge item content should include element model and system model parameter setting determination method and followed standard specification, system model simplification method, etc. Multiple knowledge types and multiple knowledge items can be selected at the same time.

[0193] e. After selecting the knowledge item, store the knowledge type and knowledge ID of the knowledge and the system model ID in the database knowledge association form to form an association reference. Store the element model ID, knowledge ID, system model type, knowledge type as one piece of data in the storage database. One system model can be associated with multiple knowledge and knowledge types;

[0194] f.In the subsequent use of system model, the relevant knowledge associated with the system model can be viewed, such as system model parameter design requirements, system related design document reports, etc. The knowledge application on which element model and system model can also be known through the element model and system model index in the knowledge entry.

[0195] The system model and element model knowledge business process is as shown in Figure 1 and Figure 2 .

[0196] Such design and use not only improve work efficiency, but also strengthen the cooperation between the platform and the Flowmaster software, and provide users with more convenient and efficient work experience. The detailed plug-in use business operation process is as shown in Figure 3 .

[0197] The technical framework adopted by the application is as follows:

[0198] The platform bottom layer adopts Java, Spring framework and Oracle database.

[0199] The Flowmaster plug-in adopts Framework framework, uses Winform control in the interface, and uses Flowmaster.Automation.Gui.dll dynamic link library.

[0200] The Flowmaster plug-in mainly includes MSFMModel, MSFMDNA, FlowmasterHelper and the like classes, and the class diagram is as shown in Figure 4 .

[0201] Among them, the FMDNA and Logon attributes are as shown in Figure 5 .

Claims

1. A method for storing and integrating knowledge based on component models and system models of Flowmaster, characterized in that: The steps are as follows: Step one: configure the storage database address, user information, and working directory, wherein the storage database includes an element library, a system library, and a knowledge base; Step two: establish an element model and a system model, and upload the element model and the system model to the corresponding library; Step three: import the element model and the system model saved in the element library and the system library into Flowmaster; Step four: associate the element model and the system model with knowledge, and the association process of the element model is as follows: 5a. After the element model is uploaded successfully, manage the element model by using the data storage library; 5b. In the storage database, view the Flowmaster element model library; 5c. Create a classification for the Flowmaster element library to manage various element models; 5d. Select the Flowmaster element model that needs to be associated with knowledge, and obtain the node ID of the element model; the database automatically establishes a knowledge association form, which contains the knowledge type and the knowledge item keyword, and is used to record the knowledge type and the knowledge ID; 5e. According to the selected properties of the element model, find or create the corresponding knowledge type and knowledge item in the knowledge base, and the content of the knowledge item should include the parameter setting determination method of the element model and the standard specification followed; At the same time, select multiple knowledge types and multiple knowledge items; 5f. After selecting the knowledge item, store the element model ID, the knowledge type, and the knowledge ID into the knowledge association form of the data storage library by using the RESTful interface KECombine, form an association reference, store the element model ID, the knowledge ID, the model type, and the knowledge type as one piece of data, and one element model can be associated with multiple knowledge and knowledge types; 5g. After association, when viewing the element model, obtain all associated knowledge types and knowledge IDs by using the element model ID in the data storage library, and view the specific knowledge information by using the knowledge ID; know the knowledge applied to which element model and system model by using the element model and system model index in the knowledge item; The knowledge association process of the system model is as follows: 6a. After the system model is uploaded successfully, manage the system model by using the data storage library; 6b. In the storage database, view the Flowmaster system library; 6c. Select the Flowmaster system model that needs to be associated with knowledge; the database automatically establishes a knowledge association form, which contains the knowledge type and the knowledge item keyword, and is used to record the knowledge type and the knowledge ID; 6d. According to the selected properties of the system model, find or create the corresponding knowledge type and knowledge item in the knowledge base, and the content of the knowledge item should include the parameter setting determination method of the element model and the system model and the standard specification followed, and the system model simplification method; at the same time, select multiple knowledge types and multiple knowledge items; 6e. After selecting the knowledge item, store the knowledge type and the knowledge ID of the knowledge and the system model ID in the database knowledge association form, and form an association reference; The system model ID, knowledge ID, model type and knowledge type are stored as one data in the storage database, and one system model is associated with multiple knowledge and knowledge types; 6f. When the system model is used later, the relevant knowledge associated with the system model is viewed; The knowledge is applied to which element model and system model through the element model and system model index in the knowledge entry.

2. The method of claim 1, wherein: In step one, the specific process is as follows: The storage database address and working directory information are saved in an encrypted form; when uploading or importing data, the storage database address is used to retrieve the data, and the specified working directory is used to store temporary files; After the configuration is completed, the user identity is verified through the single sign-on mechanism; the user provides authentication through fingerprint recognition, and the system obtains the user's key from this; the key is verified through the TokenWS Web service interface to confirm that the configuration process is successfully completed; According to the result returned by the interface, it is judged whether the configuration is successful; if successful, the configuration information is stored persistently.

3. The method of claim 2, wherein: In step two, the uploading process of the element model is as follows: 1a. Open or create a Network model in Flowmaster; 1b. Drag and drop the required element model into the Network model and edit the properties of the element model; 1c. Before uploading, use the Database component in the Flowmaster component to extract the element model and its properties and position information in the Network model; 1d. Initialize the Flowmaster component to obtain all project structures and Network models in them from ProjectNames, and build a model structure tree; 1e. Select the corresponding Network model from the model structure tree, load the element model property information, and display it in table form, including the element model name and classification, and other properties are saved in JSON format to the working directory; 1f. The user selects the element model to be uploaded and specifies the target element library node; 1g. Compress and merge the selected file and its property JSON file; 1h. Use HttpWebRequest to create an HTTP request and set the timeout; add a key to the request header to verify the user's identity; 1i. Use BinaryReader to read the file and convert it to a byte stream, and read the file in 4KB segments, and use the previously created HttpWebRequest object to upload; 1j. After starting the upload, get the response from the storage database end through WebResponse, and parse the returned data to determine the next operation; 1k. Use the POST method of the Restful interface to record the upload log, which includes the user key, file name, file ID and upload device information; 1l. After the upload is completed, the storage database returns the storage ID of the file, which is used for subsequent query of file information and download of the file.

4. The method of claim 3, wherein: In step two, the uploading process of the system model is as follows: 2a. Open or create a Network system model in Flowmaster; 2b. Build the Network system model by dragging and dropping component models, connecting component models, and filling in component attributes; 2c. Before uploading the system model, access the storage database through the RESTful API to obtain system model library data and display it in a tree structure for the user to select the corresponding system model; 2d. Initialize the Flowmaster component to obtain all project structures and Network system models from ProjectNames and build a model structure tree; 2e. Use the GetfmNetwork method of Flowmaster to obtain the attributes and component information of the current Network based on its name and parent node, and display it in a tree structure; 2f. Use the PackNetwork method of Flowmaster to pack the data of the current Network into an FMDNA file and store it in the working directory; 2g. Obtain the IDs of all component models in the model through the ComponentIDs method of Flowmaster, and loop through these IDs to obtain the link relationship, position, and other attributes of each component model using the Component method to ensure that the component models can be correctly placed when using the system model; 2h. After collecting the component model attributes, store the data properly to restore the custom attributes of the component models during the subsequent import process; 2i. Compress the model file and its attribute file into a package; 2j. Use HttpWebRequest to create an HTTP request and set the timeout; Add a key in the request header to verify the user's identity; 2k. Use BinaryReader to read the file and convert it into a byte stream, read the file in 4KB segments, and use the previously created HttpWebRequest object to upload; 2l. After starting the upload, obtain the response from the storage database side through WebResponse and parse the returned data; 2m. Perform the next operation based on the parsed information; 2n. Use the POST method of the RESTful interface to record the upload log, which includes the user key, file name, file ID, and upload device information; 2o. After the upload is complete, the storage database returns the storage ID of the file, which is used for subsequent file information query and file download.

5. The method of claim 4, wherein: In step three, the component model import process is as follows: 3a. Open or create a Network model in Flowmaster; 3b. Select the import function, access the storage database interface through the RESTful API to obtain component library data, and display the component library content in a tree structure; 3c. Select the component model that needs to be imported; 3d. Initialize the Flowmaster component, obtain all project structures and Network models in ProjectNames, and build a Network model structure tree; 3e. Obtain the download link of the selected file; 3f. Create a local storage folder to store the downloaded file; 3g. Use HttpWebRequest to create an HTTP request for downloading the file; 3h. If the file name is known, use it to create the file; Otherwise, use the file name in the Content-Disposition parameter returned by the request; 3i. Use FileStream to write the file into the created file by obtaining the byte array; 3j. Use the POST method of the RESTful interface to record the download log, including the user key, file name, file ID, and download device information; 3k. Decompress the file and loop through the commandLine.FMDNA method according to the selected component model to create component models in the Network model one by one; 3l. After creation, use the fmComponent.SetCLValue method to write the component model properties into the corresponding component model.

6. The method of claim 5, wherein: In step three, the system model import process is as follows: 4a. Log in to the configuration information through the storage database login interface; 4b. Access the storage database interface through restful, obtain the system model library data, and display the data in a tree structure; 4c. Initialize the Flowmaster component, obtain all Project structures and Network models under Project structures according to ProjectNames, and organize the obtained structures into a model structure tree; 4d. Select the system model that needs to be imported in the system model library tree structure, and download the system model to the configured working directory; 4e. Open the system model and import it to Project using UnpackNetwork, or select the path to store the file to the corresponding path.

7. The method of claim 6, wherein: In step four, the knowledge includes: Standard specifications, select the applicable standards, and accurately correspond specific clauses with components and systems in the design; Scientific literature, find and link relevant research reports and technical documents to provide theoretical basis and support for components and systems; Method steps, organize and reference detailed implementation processes and operation guidelines; Technical experts, associate with authoritative experts in the field to provide professional advice and guidance for the design of components and systems; Risk measures, provide possible risks and problems, and give solutions to potential problems; Common problems, collect problems encountered in previous projects and their solutions; Technical documents, store relevant specifications and manuals.

8. The method of claim 7, wherein: 5d, multiple knowledge type and knowledge entry keywords can be extended, and the knowledge entry belongs to the knowledge type, so that the knowledge entry is classified according to the knowledge type when displayed; meanwhile, multiple element model and system model indexes are established in the knowledge entry.

9. The method of claim 8, wherein: 6c, multiple knowledge type and knowledge entry keywords can be extended, and the knowledge entry belongs to the knowledge type, so that the knowledge entry is classified according to the knowledge type when displayed; meanwhile, multiple element model and system model indexes are established in the knowledge entry.

Images