Flowmaster-based element model and system model storage and knowledge integration method

Abstract

The invention belongs to the technical field of knowledge engineering, and discloses a Flowmaster-based element model and system model storage and knowledge integration method, which comprises the following steps of: step 1, configuring a storage database address, user information and a working directory, in which a storage database comprises sub-libraries such as an element library, a system library and a knowledge library; 2, establishing an element model and a system model, and uploading the element model and the system model to corresponding libraries; 3, importing the element model and the system model which are stored in the element library and the system library into Flowmaster; and 4, associating the element model and the system model with knowledge.

Description

Technical Field

[0001] The invention belongs to the technical field of knowledge engineering, and in particular relates to a component model and system model storage and knowledge integration method based on Flowmaster. Background Art

[0002] In the process of modeling and simulation using Flowmaster software, it is usually necessary to create or select component models from the database of Flowmaster software, establish a simulation system model, and then enter the characteristic parameters of the corresponding component model. 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 they are used by different designers. At this time, it is necessary to make customized component models and system models and manage them uniformly for use by different designers. Customized component models or system models are not accompanied by instructions and relevant knowledge, and are usually difficult to understand. In order for different designers to have a more detailed understanding of the component or system after selecting the corresponding component or system model, it is necessary to integrate the component model or system model with the corresponding knowledge. Summary of the invention

[0003] Purpose of the invention: A method for storing and integrating component models and system models based on Flowmaster is proposed to achieve unified management of mature component models and system models, and promote their reuse in a convenient way. The Flowmaster component model and system model are accurately saved in a one-to-one manner using the C / S and B / S management methods of web pages plus databases. The component model parameters are stored in the database in a clear table form and remotely managed on the web page. At the same time, the component model and the system model are bound and associated with the knowledge, so that whether in the process of system model design, simulation analysis or task execution, designers can view and reference relevant knowledge content at any time, so as to complete the work more efficiently. This binding logic expands the ease of use of Flowmaster. In actual application, designers can directly download the required component model or system model, and the plug-in will automatically write the configured parameters directly into the component model, thereby ensuring that the Flowmaster component model can be flexibly reused. When closely associated with the actual product, the Flowmaster plug-in can realize the automated conversion process, and conveniently view the knowledge corresponding to the component model and the system model during use. Ensure seamless connection from virtual design to actual products, further improving work efficiency and accuracy. This not only enhances the convenience of work, but also improves its versatility.

[0004] Technical Solution

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

[0006] Step 1: Configure the storage database address, user information, and working directory, where the storage database includes sub-libraries such as component library, system library, and knowledge base;

[0007] Step 2: Create component models and system models, and upload component models and system models to corresponding libraries;

[0008] Step 3: Import the component model and system model saved in the component library and system library into Flowmaster;

[0009] Step 4: Associate component models and system models with knowledge.

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

[0011] The storage database address and working directory information are saved in 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;

[0012] After configuration is complete, the user's 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 by calling the TokenWS Web service interface to confirm that the configuration process has been successfully completed;

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

[0014] Furthermore, in step 2, the component model uploading process is as follows:

[0015] 1a. Open or create a new 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 the Flowmaster component to extract the component model and its attributes and location information in the Network model;

[0018] 1d. Initialize the Flowmaster component, obtain all project structures and the Network models in them 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, including the component model name and category. Other attributes are saved in JSON format to the working directory;

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

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

[0022] 1h. Use HttpWebRequest to create an HTTP request 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 a loop in 4KB segments, and upload it using the previously created HttpWebRequest object;

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

[0025] 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;

[0026] 1l. After the upload is completed, the storage database returns the storage ID of the file for subsequent query of file information and downloading of files.

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

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

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

[0030] 2c. When the system model is ready to be uploaded, the storage database is accessed through the RESTful API to obtain the system model library data, and the data is displayed to the user in a tree structure for the user to select the corresponding system model;

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

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

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

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

[0035] 2h. After collecting the component model properties, store these data properly so that the custom properties of the component model can be restored during the subsequent import process;

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

[0037] 2j. Use HttpWebRequest to create an HTTP request and set a 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 upload it using the HttpWebRequest object created previously.

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

[0040] 2m. Perform the next step based on 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 completed, the storage database returns the storage ID of the file for subsequent query of file information and downloading of files.

[0043] Furthermore, in step 3, the component model import process is as follows:

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

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

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

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

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

[0049] 3f. Create a local storage folder to store the downloaded files;

[0050] 3g. Use HttpWebRequest to create an HTTP request to download the file;

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

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

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

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

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

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

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

[0058] 4b. Access the storage database interface through RESTful, obtain the system model library data, and display the data in a tree structure;

[0059] 4c. 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;

[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 and import the system model into the Project using UnpackNetwork, or select a path to save the file to the corresponding path.

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

[0063] Standard specification, selecting applicable standards and accurately mapping specific clauses to the components or systems under design;

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

[0065] Methods and steps, organize and cite detailed implementation procedures and operation guidelines;

[0066] Technical experts, authoritative experts in related fields, provide professional advice and guidance for the design of components or systems;

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

[0068] Frequently Asked Questions, which collects problems encountered in previous projects and their solutions;

[0069] Technical documents store relevant specifications and manuals.

[0070] Furthermore, in step 4, the component model association knowledge process is as follows:

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

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

[0073] 5c. Flowmaster component library creates categories to manage each component model;

[0074] 5d. Select the Flowmaster component model that needs to be associated with 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, and is used to record knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be expanded, and knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed. At the same time, multiple component model and system model indexes are established in the knowledge items.

[0075] 5e. Based on the selected component model attributes, search or create corresponding knowledge types and knowledge entries in the knowledge base. The content of the knowledge entry should include the method for determining the parameter settings of the component model and the standards and specifications to be followed. Multiple knowledge types and multiple knowledge entries can be selected at the same time. 5f. After selecting the 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 to form an association reference, and store the component model ID, knowledge ID, model type, and knowledge type as one piece of data. One component model can be associated with multiple pieces of knowledge and knowledge types;

[0076] 5g. After association, when viewing the component model, all associated knowledge types and knowledge IDs are obtained through the component model ID in the data repository, and specific knowledge information is viewed through the knowledge ID. You can also know which component models and system models the knowledge is applied to through the component model and system model index in the knowledge entry.

[0077] Furthermore, in step 4, the system model association knowledge process is as follows:

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

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

[0080] 6c. Select the Flowmaster system model that needs to be associated with knowledge; the database automatically creates a knowledge association form, which contains keywords such as knowledge type and knowledge item, used to record knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be expanded. Knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed. At the same time, multiple component model and system model indexes are established in the knowledge items.

[0081] 6d. According to the selected system model attributes, search or create corresponding knowledge types and knowledge items in the knowledge base. The knowledge items should include the determination methods of component model and system model parameter settings and the standards and specifications followed, system model simplification methods, etc. You can select multiple knowledge types and multiple knowledge items at the same time.

[0082] 6e. After selecting the knowledge item, store the knowledge type and knowledge ID of the knowledge with the system model ID in the database knowledge association form to form an association reference. In the storage database, the system model ID, knowledge ID, model type, and knowledge type are stored as one piece of data, and one system model is associated with multiple pieces of knowledge and knowledge types;

[0083] 6f. When using the system model in the future, check the related knowledge associated with the system model. You can also know which component models and system models the knowledge is applied to through the component model and system model index in the knowledge entry.

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

[0085] a) Unified management of customized Flowmaster component models and system models, models can be reused, improving the work efficiency of designers;

[0086] b)

[0087] Flowmaster component models and system models are associated with knowledge. Designers can refer to the relevant standards, specifications, literature and other knowledge of component models and system models to know how and why each parameter is set, why the system model is built in this way, and how to simplify it. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] Figure 1 It is a schematic diagram of the component model knowledge business process;

[0089] The Flowmaster component library in the storage database is classified by component models. Each type of component model contains several customized component models containing specific parameters. The component model is associated with the knowledge base through knowledge attributes, and is specifically associated with specific knowledge items in the technical expert library, method step library, etc.

[0090] In Flowmaster software, the customized component model with specific parameters is referenced to form an instantiated component model. The instantiated component model can view various related knowledge items.

[0091] Figure 2 It is a schematic diagram of the system model knowledge business process;

[0092] The Flowmaster system library in the storage database is classified according to system models. Each type of system model contains several system models with specific parameters. The system model is associated with the knowledge base through knowledge attributes, and is specifically associated with specific knowledge items in the technical expert library, method and step library, etc.

[0093] The system model containing specific parameters is referenced in the Flowmaster software to form an instantiated system model. The instantiated system model can view various related knowledge items.

[0094] Figure 3 This is a schematic diagram of the plug-in operation process;

[0095] Open the Flowmaster network model, load the component model, set the specific parameters of the component model and extract the parameters, upload the component model to the component library, then associate the knowledge and store it in the database. At this time, you can view the knowledge, or repeatedly select the component model to upload and associate the knowledge.

[0096] When downloading a component model, you can view the knowledge and write parameters into the component model. You can download multiple component models and combine them to generate a system model.

[0097] Figure 4 It is a class diagram;

[0098] The classes used for method implementation mainly include FMDNA, Logon, MSFMModel, MSFMDNA, FlowmasterHelper and Flowmaster.gui, among which MSFMModel is used to obtain the property information of all component models, connection points and lines under the network according to the Project and network, such as the component model position, connection point number, the starting position and ending position of the line, etc. MSFMDNA is used to log in to Flowmaster to obtain all projects and networks of Flowmaster. FlowmasterHelper is used for user initialization. Flowmaster.gui is used to complete the login according to the configuration information, obtain the operation of Flowmaster properties, and exit after the operation is completed.

[0099] Figure 5 This is a schematic diagram of FMDNA and Logon properties;

[0100] Logon reads the configuration file and obtains the information of fmconfig.xml for logging into Flowmaster. After using Logon, FMDNA obtains all Project and network information, as well as Eyepoint and ViewPoint information.

[0101] Figure 6 This is a schematic diagram of the Flowmaster component library;

[0102] The Flowmaster component library interface is shown in the figure, including tree structure classification and specific component models. The specific component model interface includes details, parameters, standards, specifications, scientific and technological literature and other knowledge.

[0103] Figure 7 This is a schematic diagram of the Flowmaster system library;

[0104] The Flowmaster system library interface is shown in the figure, which includes classification and specific system models. The specific system models include models, simulation results, standard specifications, scientific and technological literature and other knowledge.

[0105] Figure 8 For Flowmaster plugin - upload schematic;

[0106] The interface is shown in the figure. On the left are the tree-structured system library and component library obtained from the storage database; on the upper right are the tree-structured project and network obtained from Flowmaster; on the lower right are the component models obtained from the network. Confirm the upload by selecting the component model on the left and the component model on the lower right.

[0107] Fig. 9 - Download schematic for Flowmaster plugin.

[0108] The interface is as shown in the figure. Select to obtain the model in the component library or system library from the storage database. You can save it as or open the model directly. DETAILED DESCRIPTION

[0109] A component model storage and knowledge integration method based on Flowmaster, which can accurately extract various component models and their detailed parameters from the Flowmaster model, upload the component models and parameters to the Flowmaster component library with one click, and associate them with knowledge, so that subsequent designers have great flexibility when using the Flowmaster software. Not only can you easily browse the component library, select the required component models and browse the associated knowledge, but you can also import these component models into the Flowmaster system model. What's more convenient is that the parameters of the component model will also be automatically written into the system model, which greatly simplifies the system model configuration process, improves modeling efficiency, and allows users to focus more on model analysis and optimization.

[0110] This invention takes the storage database function as its core and gives full play to its powerful data processing and model management capabilities. At the same time, with the Flowmaster plug-in as an important auxiliary tool, through its upload and download functions, it realizes the efficient circulation and sharing of component models, system models and parameters, and realizes the linkage between component models, system models and knowledge through knowledge association. The association of knowledge can also promote the sharing and inheritance of knowledge. By binding the component model and system model with the knowledge ID, the relevant knowledge content can be integrated into the database, so that other users can easily obtain and use this knowledge. This can not only avoid the loss and forgetting of knowledge, but also improve the knowledge level and innovation ability of the entire team.

[0111] The present invention includes four modules: configuration, upload, import, and associated knowledge. The module functions are as follows:

[0112] 1) Configuration: used to configure the storage database address, user information, and working directory.

[0113] 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, Flowmaster component library and Flowmaster system library are established respectively. Component model upload can upload component models to Flowmaster component library, which is a storage library for storing various Flowmaster components (such as pipes, valves, pumps, etc.). These components can be reused to improve design efficiency; system model upload can upload system models to Flowmaster system model library, which is used to save Flowmaster system models in the storage database and has a viewing function.

[0114] 3) Import: The import module is divided into component model import and system model import, which imports the component model and system model saved in the storage database into Flowmaster.

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

[0116] The function implementation method is as follows:

[0117] 1) Configuration:

[0118] a. Set the storage database address and working directory, and save these configuration 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;

[0119] b. After completing the configuration, the user's identity is verified through the single sign-on mechanism. Specifically, the user provides authentication through fingerprint recognition, and the system obtains the user's key. The key is then verified by calling the TokenWS Web service interface to confirm that the configuration process has been successfully completed;

[0120] c. Determine whether the configuration is successful based on the result returned by the interface; if successful, store the configuration information persistently.

[0121] 2) Upload

[0122] a) Upload component models

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

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

[0125] c. Before uploading, use the Database component in the Flowmaster component to extract the component model and its attributes and location information in the Network model;

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

[0127] e. Select the corresponding Network model from the model structure tree, load the component model attributes and other information, and display them in a table, including the component model name and category. Other attributes such as the pump's rated head, flow rate or flow pressure curve are saved in the working directory in JSON format;

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

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

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

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

[0132] j. After starting to upload, get the response from the storage database through WebResponse and parse the returned data to determine the next step;

[0133] k. 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;

[0134] l. After the upload is completed, the storage database returns the storage ID of the file, which can be used for subsequent query of file information and downloading of files.

[0135] b) Upload the system model

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

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

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

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

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

[0141] f. Use Flowmaster's PackNetwork method to pack the current Network data into an FMDNA file and store it in the working directory (the UnpackNetwork method can be used when importing FMDNA files);

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

[0143] h. After collecting the component model attributes, store these data properly so that the custom attributes of the component model can be restored during the subsequent import process;

[0144] i. Compress the model file and its attribute files into one package;

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

[0146] k. Use BinaryReader to read the file and convert it into a byte stream. Loop through the file in 4KB segments and upload it using the HttpWebRequest object created previously.

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

[0148] m. Execute the next step based on the parsed information;

[0149] n. 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;

[0150] o. After the upload is completed, the storage database returns the storage ID of the file, which can be used for subsequent query of file information and downloading of files.

[0151] 3) Import

[0152] a) Import of component models

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

[0154] 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;

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

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

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

[0158] f. Create a local storage folder to store the downloaded files;

[0159] g. Use HttpWebRequest to create an HTTP request to download files;

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

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

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

[0163] k. Unzip the file and use the commandLine.FMDNA method to create component models in the Network model in turn according to the selected component model;

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

[0165] b) Import of system model

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

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

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

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

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

[0171] 4) Related knowledge

[0172] In order to better store and utilize knowledge, a knowledge base has been specially established for this purpose. The knowledge base contains sub-bases of knowledge types such as standards and specifications, scientific and technological literature, methods and procedures, technical experts, risk measures, common problems, and technical documents.

[0173] Standard specifications allow you to select applicable standards and accurately match specific clauses to the components or systems in your design, ensuring that technical implementation complies with industry regulations.

[0174] Scientific and technological literature can find and link relevant research reports and technical documents to provide theoretical basis and support for components or systems.

[0175] Method steps, organize and reference detailed implementation processes and operating guidelines to ensure that each step can be correctly applied to the corresponding components or systems.

[0176] Technical experts can contact authoritative experts in the field to provide professional advice and guidance for the design of components or systems.

[0177] Risk measures provide possible risks and problems, and propose solutions to potential problems, ensuring that risk management of components or systems is considered during the design phase.

[0178] Frequently Asked Questions collects problems encountered in previous projects and their solutions, making it easy to quickly locate and solve common problems that may arise during component or system development.

[0179] Technical files store relevant specifications, manuals and other documents to ensure that the design and manufacturing process of components or systems has a basis to rely on.

[0180] a) Component model related knowledge

[0181] a. After the component model is successfully uploaded, the component model is managed using the data repository;

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

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

[0184] d. Select the Flowmaster component model that needs to be associated with 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, and is used to record knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be expanded, and knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed. At the same time, multiple component model and system model indexes are established in the knowledge items.

[0185] e. According to the selected component model attributes, search or create the corresponding knowledge type and knowledge entry in the knowledge base. The content of the knowledge entry should include the method for determining the parameter settings of the component model and the standard specifications to be followed. You can select multiple knowledge types and multiple knowledge entries at the same time.

[0186] f. After selecting the 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 to form an association reference. The component model ID, knowledge ID, model type and knowledge type are stored as one piece of data. One component model can be associated with multiple pieces of knowledge and knowledge types.

[0187] g. After association, when viewing the component model, you can obtain all associated knowledge types and knowledge IDs through the component model ID in the data repository, and view specific knowledge information through the knowledge ID; you can also know which component models and system models the knowledge is applied to through the component model and system model indexes in the knowledge entry.

[0188] h. When you use the component model in the future, you can view the relevant knowledge associated with the component model, such as the component model parameter setting requirements, the specifications to be followed, etc.

[0189] b) System model related knowledge

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

[0191] b. In the storage database, check the Flowmaster system library;

[0192] c. Select the Flowmaster system model that needs to be associated with knowledge; the database automatically creates a knowledge association form, which contains keywords such as knowledge type and knowledge item, used to record knowledge type and knowledge ID, etc. Multiple knowledge types and knowledge items can be expanded. Knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed. At the same time, multiple component model and system model indexes are established in the knowledge items.

[0193] d. According to the selected system model attributes, search or create corresponding knowledge types and knowledge items in the knowledge base. The knowledge items should include the determination methods of component model and system model parameter settings and the standards and specifications followed, system model simplification methods, etc. You can select multiple knowledge types and multiple knowledge items at the same time.

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

[0195] f. When you use the system model later, you can view the relevant knowledge associated with the system model, such as system model parameter design requirements, system-related design file reports, etc. You can also use the component model and system model index in the knowledge entry to know which component models and system models the knowledge is applied to.

[0196] System model and component model knowledge business process such as Figure 1 and Figure 2 shown.

[0197] This design and application not only improves work efficiency, but also strengthens the collaboration between the platform and Flowmaster software, providing users with a more convenient and efficient work experience. Figure 3 .

[0198] The technical framework adopted by the invention is as follows:

[0199] The underlying platform uses Java, Spring framework, and Oracle database.

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

[0201] The Flowmaster plug-in mainly includes classes such as MSFMModel, MSFMDNA, and FlowmasterHelper. The class diagram is as follows Figure 4 shown.

[0202] The FMDNA and Logon attributes are as follows Figure 5 .

Claims

1. A method for storing component models and system models and integrating knowledge based on Flowmaster, characterized in that: Here are the steps: Step 1: Configure the storage database address, user information, and working directory, where the storage database includes component library, system library, and knowledge base; Step 2: Create component models and system models, and upload component models and system models to corresponding libraries; Step 3: Import the component model and system model saved in the component library and system library into Flowmaster; Step 4: Associate component models and system models with knowledge.

2. The method according to claim 1, characterized in that: In step one, the specific process is as follows: The storage database address and working directory information are saved in 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; After configuration is complete, the user's 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 by calling the TokenWS Web service interface to confirm that the configuration process has been successfully completed; Determine whether the configuration is successful based on the result returned by the interface; if successful, store the configuration information persistently.

3. The method according to claim 2, characterized in that: In step 2, the component model upload process is as follows: 1a. Open or create a new Network model in Flowmaster; 1b. Drag and drop the required component model into the Network model and edit the properties of the component model; 1c. Before uploading, use the Database component in the Flowmaster component to extract the component model and its attributes and location information in the Network model; 1d. Initialize the Flowmaster component, obtain all project structures and the 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 component model attribute information, and display it in a table, including the component model name and category. Other attributes are saved in JSON format to the working directory; 1f. The user selects the component model to be uploaded and specifies the target component library node; 1g. Compress and merge the selected files and their attribute JSON files; 1h. Use HttpWebRequest to create an HTTP request and set a timeout; add a key to the request header to verify the user's identity; 1i. Use BinaryReader to read the file, convert it into a byte stream, and read the file in a loop in 4KB segments, and upload it using the previously created HttpWebRequest object; 1j. After starting to upload, get the response from the storage database through WebResponse and parse the returned data to determine the next step; 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 for subsequent query of file information and downloading of files.

4. The method according to claim 3, characterized in that: In step 2, the upload process of the system model is as follows: 2a. Open or create a new Network system model in Flowmaster; 2b. Build the Network system model by dragging component models, connecting component models, and filling in component properties; 2c. When the system model is ready to be uploaded, the storage database is accessed through the RESTful API to obtain the system model library data, and the data is displayed to the user in a tree structure for the user to select the corresponding system model; 2d. Initialize the Flowmaster component, obtain all project structures and the Network system models therein from ProjectNames, and build a model structure tree; 2e. Use the GetfmNetwork method of Flowmaster to obtain the properties and component information of the Network according to the name and parent node of the current Network, and display it in the form of a tree structure; 2f. Use Flowmaster's PackNetwork method to pack the current Network data into an FMDNA file and store it in the working directory; 2g. Get the IDs of all component models in the model through Flowmaster's ComponentIDs method, loop through these IDs, and use the Component method to get the link relationship, position and other properties of each component model to ensure that the component model can be placed correctly when using the system model; 2h. After collecting the component model properties, store these data properly so that the custom properties of the component model can be restored during the subsequent import process; 2i. Compress the model file and its attribute files into one package; 2j. Use HttpWebRequest to create an HTTP request and set a timeout; Add a key to the request header to verify the user's identity; 2k. Use BinaryReader to read the file and convert it into a byte stream. Loop through the file in 4KB segments and upload it using the HttpWebRequest object created previously. 2l. After starting to upload, get the response from the storage database through WebResponse and parse the returned data; 2m. Perform the next step 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 completed, the storage database returns the storage ID of the file for subsequent query of file information and downloading of files.

5. The method according to claim 4, characterized in that: In step 3, the component model import process is as follows: 3a. Open or create a new Network model in Flowmaster; 3b. Select the import function, access the storage database interface through the RESTful API to obtain the component library data, and display the component library content in a tree structure; 3c. Select the component model to be imported; 3d. Initialize the Flowmaster component, obtain all project structures and the Network models in them from ProjectNames, and build a Network model structure tree; 3e. Get the download link of the selected file; 3f. Create a local storage folder to store the downloaded files; 3g. Use HttpWebRequest to create an HTTP request to download the file; 3h. If the file name is known, create the file with that name; 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 through the obtained byte array; 3j. Use the POST method of the RESTful interface to record the download log, which includes the user key, file name, file ID and download device information; 3k. Unzip the file and use the commandLine.FMDNA method to create component models in the Network model in turn according to the selected component model; 3l. After creation, use the fmComponent.SetCLValue method to write the component model properties into the corresponding component model.

6. The method according to claim 5, characterized in that: In step 3, the system model import process is as follows: 4a. Log in through the storage database login interface and configuration information; 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 the Project structure according to ProjectNames, and organize the obtained structures into a model structure tree; 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; 4e. Open and import the system model into the Project using UnpackNetwork, or select a path to save the file to the corresponding path.

7. The method according to claim 6, characterized in that: In step 4, knowledge includes: Standard specification, selecting applicable standards and accurately mapping specific clauses to the components and systems under design; Scientific and technological literature, find and link relevant research reports and technical documents to provide theoretical basis and support for components and systems; Methods and steps, organize and cite detailed implementation procedures and operation guidelines; Technical experts, authoritative experts in related fields, provide professional advice and guidance for the design of components and systems; Risk measures provide possible risks and problems, and provide solutions to potential problems; Frequently Asked Questions, which collects problems encountered in previous projects and their solutions; Technical documents store relevant specifications and manuals.

8. The method according to claim 7, characterized in that: In step 4, the component model association knowledge process is as follows: 5a. After the component model is successfully uploaded, the component model is managed using the data repository; 5b. In the storage database, view the Flowmaster component model library; 5c. Flowmaster component library creates categories to manage each component model; 5d. Select the Flowmaster component model that needs to be associated with knowledge, and obtain the node ID of the component model; the database automatically creates a knowledge association form, which contains knowledge types and knowledge item keywords, and is used to record knowledge types and knowledge IDs. Multiple knowledge types and knowledge item keywords can be expanded, and knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed; at the same time, multiple component model and system model indexes are established in the knowledge items; 5e. According to the selected component model attributes, search or create corresponding knowledge types and knowledge items in the knowledge base. The content of the knowledge items should include the determination method of each parameter setting of the component model and the standard specifications followed; Select multiple knowledge types and multiple knowledge items at the same time; 5f. After selecting the 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 to form an association reference. The component model ID, knowledge ID, model type and knowledge type are stored as one piece of data. One component model can be associated with multiple pieces of knowledge and knowledge types. 5g. After association, when viewing the component model, obtain all associated knowledge types and knowledge IDs through the component model ID in the data repository, and view specific knowledge information through the knowledge ID; The component models and system models to which the knowledge is applied are known through the component model and system model indexes in the knowledge entry.

9. The method according to claim 8, characterized in that: In step 4, the system model association knowledge process is as follows: 6a. After the system model is uploaded successfully, use the data repository to manage the system model; 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 creates a knowledge association form, which contains knowledge types and knowledge item keywords, and is used to record knowledge types and knowledge IDs. Multiple knowledge types and knowledge item keywords can be expanded. Knowledge items are subordinate to knowledge types, so that knowledge items can be classified by knowledge type when displayed; at the same time, multiple component model and system model indexes are established in the knowledge items; 6d. According to the selected system model attributes, search or create corresponding knowledge types and knowledge items in the knowledge base. The knowledge items should include the determination method of each parameter setting of the component model and the system model and the standards and specifications followed, and the system model simplification method; select multiple knowledge types and multiple knowledge items at the same time; 6e. After selecting the knowledge item, the knowledge type and knowledge ID of the knowledge and the system model ID are stored in the database knowledge association form to form an association reference; The system model ID, knowledge ID, model type and knowledge type are stored as one piece of data in the storage database, and one system model is associated with multiple pieces of knowledge and knowledge types; 6f. When using the system model in the future, check the relevant knowledge associated with the system model; The component models and system models to which the knowledge is applied are known through the component model and system model indexes in the knowledge entry.

Images