Collaborative design method and device for compressor unit equipment based on COMOS platform

Abstract

The invention discloses a collaborative design method and device for compressor unit equipment based on a COMOS platform, a storage medium and computer equipment, and the method comprises the steps: receiving and analyzing a design demand file to obtain equipment parameters, and integrating the equipment parameters, a standard card of a general compressor unit and a basic object database in the platform; creating a project catalog on a platform, and creating a device object category catalog under the project catalog; calling a plurality of basic objects from a basic object database integrated by the platform according to the equipment parameters, and setting each basic object under a corresponding function label; and assigning a value to the basic object under each function label to obtain a basic object instance, and constructing a connection relationship between the basic object instances; and performing connection reliability check on the basic object instances for constructing the connection relationship based on the standard card, and generating an equipment data table, an inquiry list, a pricing list and an equipment technical document of each function tag based on the basic object instances under each function tag after the connection reliability check is passed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of compressor unit equipment design, in particular to a collaborative design method and device for compressor unit equipment based on a COMOS platform, a storage medium and a computer device. BACKGROUND

[0002] As a core equipment in industrial production, the design process of a compressor unit involves multi-disciplinary knowledge integration, multi-specialty collaboration and complex parameter configuration. The traditional design method usually adopts a decentralized design mode, and each specialty (such as machinery, electricity, control, etc.) independently carries out design work, and the design is completed through manual data transmission and repeated iteration, which leads to long design cycle, low efficiency, and is easy to cause design errors due to inconsistent data or communication errors. In addition, with the expansion of industrial project scale and the increase of customization demand, the traditional design method is difficult to quickly respond to complex and variable design requirements, especially in the scene involving multi-equipment collaboration, balance between standardization and individualization, the contradiction between design quality and efficiency is increasingly prominent.

[0003] In the prior art, some design platforms try to improve design efficiency through integrated tools, such as using general modeling software or industry-specific design systems. However, these solutions still have significant defects: first, there is a lack of a unified data management framework, and equipment parameters, standard specifications and basic object libraries are scattered in different modules, leading to data redundancy, version conflicts and collaboration difficulties; second, the correlation between function tags and equipment objects is weak, and designers need to manually match parameters and objects, which is prone to configuration errors; third, connection relationship verification relies on manual inspection or simple rule engines, which cannot fully cover the reliability requirements under complex working conditions; fourth, the design results need to be generated through secondary processing, which has low automation degree and is easy to miss key information. The above problems make it difficult for the existing technology to meet the comprehensive requirements of high efficiency, accuracy and traceability for compressor unit design. SUMMARY

[0004] Therefore, the present application provides a collaborative design method and device for compressor unit equipment based on a COMOS platform, a storage medium and a computer device, which realizes the full-process automation of design requirement analysis, basic object calling, parameter assignment, connection relationship verification and document generation by building a unified data integration and collaborative design framework. This method dynamically associates equipment parameters with basic objects through function tags as a link, and introduces a standard card-driven connection reliability checking mechanism to ensure that the design results meet industry specifications. At the same time, by automatically generating standardized documents such as equipment data table and inquiry sheet, the design efficiency and data consistency are significantly improved.

[0005] According to one aspect of the present application, a collaborative design method for compressor unit equipment based on a COMOS platform is provided, comprising: receive a design requirement file corresponding to a to-be-designed compressor unit, parse the design requirement file to obtain device parameters corresponding to each device included in the to-be-designed compressor unit, and integrate the device parameters, standard cards corresponding to a general compressor unit, and a basic object database in a COMOS platform; create a project directory in the COMOS platform, and create a compressor unit device object category directory under the project directory, wherein each functional label of a general compressor unit is correspondingly arranged under the device object category directory; According to the device parameters, a plurality of basic objects corresponding to the to-be-designed compressor unit are called from the basic object database integrated in the COMOS platform, and each basic object is arranged under a corresponding functional label; According to the device parameters, each basic object under each functional label is respectively assigned a value to obtain a basic object instance, and a connection relationship between the basic object instances is constructed; Based on the standard cards in the COMOS platform, the basic object instances with the constructed connection relationship are subjected to a connection reliability check, and after passing the connection reliability check, device data tables, inquiry sheets, pricing sheets, and device technical documents corresponding to each functional label are generated based on the basic object instances under each functional label.

[0006] According to another aspect of the present application, a compressor unit device collaborative design device based on a COMOS platform is provided, comprising: The analysis module is configured to receive a design requirement file corresponding to a to-be-designed compressor unit, parse the design requirement file to obtain device parameters corresponding to each device included in the to-be-designed compressor unit, and integrate the device parameters, standard cards corresponding to a general compressor unit, and a basic object database in a COMOS platform; The directory creation module is configured to create a project directory in the COMOS platform, and create a compressor unit device object category directory under the project directory, wherein each functional label of a general compressor unit is correspondingly arranged under the device object category directory; The object calling module is configured to call a plurality of basic objects corresponding to the to-be-designed compressor unit from the basic object database integrated in the COMOS platform according to the device parameters, and arrange each basic object under a corresponding functional label; The connection relationship construction module is configured to assign a value to each basic object under each functional label according to the device parameters to obtain a basic object instance, and construct a connection relationship between the basic object instances; The data generation module is configured to perform connection reliability checking on the basic object instances of the constructed connection relationship based on the standard cards in the COMOS platform, and generate the equipment data table, the inquiry sheet, the pricing sheet and the equipment technical document corresponding to each functional label based on the basic object instances under each functional label after passing the connection reliability checking.

[0007] According to yet another aspect of the present application, a storage medium is provided, which stores a computer program. The program is executed by a processor to implement the above-mentioned collaborative design method for a compressor unit based on a COMOS platform.

[0008] According to still another aspect of the present application, a computer device is provided, which comprises a storage medium, a processor and a computer program stored in the storage medium and executable on the processor. The processor executes the program to implement the above-mentioned collaborative design method for a compressor unit based on a COMOS platform.

[0009] Through the above technical solution, the present application provides a collaborative design method and device for a compressor unit based on a COMOS platform, a storage medium and a computer device. By constructing a unified data integration and collaborative design framework, the present application realizes full-process automation of design requirement analysis, basic object calling, parameter assignment, connection relationship verification and document generation. The method dynamically associates the equipment parameters with the basic objects by taking the functional labels as the link, and introduces a standard card driven connection reliability checking mechanism to ensure that the design result meets the industry specifications. Meanwhile, by automatically generating standardized documents such as the equipment data table and the inquiry sheet, the present application significantly improves the design efficiency and data consistency. The present application fills the technical gap in the existing technology in terms of multi-device collaborative design, balance between standardization and individualization and full-process automation, and provides an efficient and reliable technical solution for the compressor unit design field.

[0010] The above description is only a summary of the technical solutions of the present application. In order to enable one of ordinary skill in the art to better understand the technical means of the present application and implement the same according to the contents of the description, and in order to enable the above and other purposes, features and advantages of the present application to be more apparent, the following specifically describes the embodiments of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0011] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application and illustrate the illustrative embodiments of the present application and their description serve to explain the present application, and do not constitute an improper limitation on the present application. In the drawings: Figure 1 Fig. 1 shows a flow diagram of a collaborative design method for a compressor unit based on a COMOS platform according to an embodiment of the present application; Figure 2 Fig. 2 shows a schematic diagram of a functional label according to an embodiment of the present application. Figure 3 A schematic diagram of the structure of a collaborative design device for compressor unit equipment based on the COMOS platform provided in an embodiment of this application is shown. Figure 4 A schematic diagram of the device structure of a computer device provided in an embodiment of this application is shown. Detailed Implementation

[0012] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0013] This embodiment provides a collaborative design method for compressor unit equipment based on the COMOS platform, such as... Figure 1 As shown, the method includes: Step 101: Receive the design requirement file corresponding to the compressor unit to be designed, parse the design requirement file to obtain the equipment parameters corresponding to each device included in the compressor unit to be designed, and integrate the equipment parameters, the standard card corresponding to the general compressor unit, and the basic object database in the COMOS platform.

[0014] Step 102: Create a project directory in the COMOS platform, and create a compressor unit equipment object category directory under the project directory, wherein the equipment object category directory corresponds to the functional tags of the general compressor unit.

[0015] Step 103: Based on the device parameters, retrieve multiple basic objects corresponding to the compressor unit to be designed from the basic object database integrated by the COMOS platform, and set each basic object under its corresponding function tag.

[0016] Step 104: Based on the device parameters, assign values ​​to the basic objects under each function tag to obtain basic object instances, and construct the connection relationship between the basic object instances.

[0017] Step 105: Based on the standard card in the COMOS platform, perform a connection reliability check on the basic object instance for building the connection relationship. After passing the connection reliability check, generate the equipment data table, inquiry form, pricing form and equipment technical document corresponding to each function tag based on the basic object instance under each function tag.

[0018] This application provides a collaborative design method for compressor unit equipment based on the COMS platform. By leveraging the COMS platform to achieve modular configuration and standardized parameter association, it can eliminate manual input errors, improve design efficiency, and shorten the design cycle.

[0019] Specifically, at the initial stage of the compressor set equipment collaborative design process, a design requirement file of a compressor set to be designed can be first received. The design requirement file is the basis of the entire design work, which can contain various key information about the compressor set to be designed. Then, the design requirement file can be parsed, and the equipment parameters corresponding to each equipment included in the compressor set to be designed are extracted from the design requirement file through specific parsing algorithms or rules. These equipment parameters can include important data such as the size, power, working pressure, and working temperature of the equipment. At the same time, the parsed equipment parameters, standard cards corresponding to general compressor sets, and a basic object database are integrated in the COMOS platform. Here, the standard cards can include industry-wide design specifications, standard parameters, etc., and the basic object database stores various basic objects, such as basic components of compressors and basic components of piping systems. This integration operation enables centralized management of various data and resources required in the design process, providing convenience for subsequent design work.

[0020] After completing the data integration, a project directory can be created in the COMOS platform next. The creation of the project directory is to orderly organize and manage the entire design project. Under the project directory, a compressor set equipment object category directory is further created. The creation of this equipment object category directory helps to classify and manage various equipment of the compressor set. The COMOS platform can automatically set function tags of general compressor sets under the equipment object category directory. These function tags can include compressor equipment, pump equipment, sealing equipment, separator equipment, filter equipment, actuator, and driving mechanism. By setting the function tags, different functional parts of the compressor set can be clearly distinguished, providing clear classification basis for subsequent basic object calling and parameter assignment operations, so that the designer can more conveniently find and process equipment objects related to a specific function. In a specific embodiment, a project directory can be first created in the COMOS platform, and then a product design directory containing a product specification table and a unit directory is built under the project directory. Further, under the unit directory, two sub-directories of package design and instrument control design are created. Under the package design sub-directory, a compressor set equipment object category directory is created.

[0021] After the function tags are determined, the COMOS platform can call multiple base objects corresponding to the compressor set to be designed from the base object database according to the equipment parameters parsed previously. The base object database stores a large number of predefined base objects, which are basic units constituting the compressor set equipment. The calling process is actually selecting appropriate base objects according to the requirements of the equipment parameters. For example, if a compressor impeller of a certain specification is required in the equipment parameters, then the impeller base object meeting the specification can be called from the base object database. After the calling is completed, each base object is set under the corresponding function tag. In this way, each function tag contains the base objects required to realize the function, so that the design structure of the entire compressor set is preliminarily constructed in the COMOS platform, laying a foundation for subsequent parameter assignment and connection relationship construction.

[0022] After the base objects are set under the function tags, each base object can be assigned values according to the equipment parameters. The assignment process is to assign specific values in the equipment parameters to the related attributes of the base objects. For example, for a pipe base object, the pipe diameter, wall thickness and other parameters in the equipment parameters can be assigned. Through the assignment operation, the originally abstract base object becomes a base object instance with actual parameters. After obtaining the base object instance, further, the connection relationship between the base object instances can be constructed in the COMOS platform. The construction of the connection relationship can consider the physical connection, signal transmission and other relationships between the devices of the compressor set. For example, the pipe connection between the compressor main body and the cooling system, the signal transmission connection between the compressor and the control system, etc. When constructing the connection relationship, it is ensured that the devices can work cooperatively to meet the overall design requirements of the compressor set.

[0023] After the connection relationship between the base object instances is constructed, the connection reliability of the connection relationship can be checked based on the standard cards integrated previously in the COMOS platform. The standard cards contain a series of standards and specifications for connection reliability in the industry. By applying these standards and specifications to the constructed connection relationship, it is checked whether the connection meets the requirements. For example, it is checked whether the strength of the pipe connection is sufficient, whether the signal transmission is stable, etc. If the connection relationship passes the connection reliability check, it means that the connection relationship meets the design requirements. At this time, based on the base object instances under each function tag, the equipment data table, the inquiry sheet, the pricing sheet and the equipment technical document corresponding to each function tag are generated. Among them, the equipment data table can contain detailed parameter information of each device; the inquiry sheet is used to inquire the suppliers; the pricing sheet is used to calculate the cost of the equipment; and the equipment technical document contains important technical information such as design principle and usage instruction of the equipment. The generation of these documents is helpful for subsequent equipment procurement, cost accounting, and equipment installation, debugging and maintenance, etc.

[0024] By applying the technical solution of this embodiment, and constructing a unified data integration and collaborative design framework, the entire process of design requirement analysis, basic object invocation, parameter assignment, connection relationship verification, and document generation is automated. This method uses functional tags as a link to dynamically associate equipment parameters with basic objects and introduces a connection reliability check mechanism driven by a standard card to ensure that the design results comply with industry standards. Simultaneously, by automatically generating standardized documents such as equipment data sheets and Request for Quotations (RFQs), design efficiency and data consistency are significantly improved. This application fills the technical gaps in existing technologies regarding multi-device collaborative design, the balance between standardization and personalization, and full-process automation, providing an efficient and reliable technical solution for the field of compressor unit design.

[0025] In this embodiment of the application, optionally, each of the basic object instances has a unique identifier; after step 105, the method further includes: for each basic object instance, determining the target device parameters corresponding to the basic object instance from the device parameters, and generating a tab corresponding to the basic object instance based on the target device parameters, and binding the tab, the device data table, the inquiry form, the pricing form, and the device technical documents under the function tag corresponding to the basic object instance to the unique identifier of the basic object instance; Accordingly, the method further includes: responding to a data query instruction, obtaining a target unique identifier based on the data query instruction, and obtaining the tab, equipment data table, inquiry form, pricing form, and equipment technical document bound to the target unique identifier; using the bound tab, equipment data table, inquiry form, pricing form, and equipment technical document as folded content respectively, and generating an index for each folded content; generating a data feedback interface based on each folded content and the corresponding index; wherein, when any index other than the index corresponding to the bound tab is selected, determining the target display content corresponding to the target unique identifier from the folded content under the selected index based on the target unique identifier, and outputting the target display content.

[0026] In this embodiment, during the collaborative design process of the compressor unit equipment, after generating equipment data sheets, quotations, pricing sheets, and equipment technical documents, a unique identifier can be assigned to each basic object instance through the COMOS platform. The unique identifier can be a specific string of codes, such as numbers, letters, or combinations thereof, possessing uniqueness and identifiability. By setting a unique identifier for each basic object instance, different basic object instances can be accurately distinguished throughout the entire design system. This facilitates independent management, querying, and operation of each basic object instance, avoiding confusion and errors caused by a large number of object instances, and ensuring the standardization and efficiency of the entire design process.

[0027] After generating the equipment data sheets, inquiry forms, pricing sheets, and equipment technical documents corresponding to each functional label, the next step is to further process the basic object instances. Specifically, for each basic object instance, the target equipment parameters are first determined from the previously parsed equipment parameters. The target equipment parameters are the key parameters used in the design of this basic object instance, determining its specific attributes and functions. Then, based on these target equipment parameters, tabs corresponding to the basic object instance are generated. Tabs can be intuitive interface elements used to display important information related to the basic object instance.

[0028] Next, the generated tabs, as well as the equipment data sheets, quotations, pricing sheets, and equipment technical documents under the corresponding function tabs of the basic object instance, are all bound to the unique identifier of the basic object instance. This establishes a relationship between these documents, tabs, and the basic object instance, allowing for quick and accurate retrieval of all related information through the unique identifier. This relationship facilitates subsequent data querying and management, enabling designers to easily access various materials related to a specific basic object instance.

[0029] After binding, users can perform data queries through the COMS platform. Specifically, when the COMS platform receives a data query command, it retrieves the target unique identifier based on the command. The target unique identifier is key to the query, indicating the specific underlying object instance to be queried. After obtaining the target unique identifier, it further retrieves the tabs, equipment data sheets, inquiry forms, pricing forms, and equipment technical documents bound to that unique identifier. To display this information more clearly, these bound documents and tabs can be treated as collapsed content. Simultaneously, an index is generated for each collapsed content. The index serves as an identifier and classification for the collapsed content, helping users quickly locate the information they need. A data feedback interface can also be generated based on each collapsed content and its corresponding index. The data feedback interface is the window through which users interact with the platform. Through this interface, users can intuitively see various information related to the target underlying object instance and easily browse and find the required content based on the index.

[0030] In the data feedback interface, users can trigger any index besides the one corresponding to the tab. When any other index is triggered, the COMS platform can determine the target display content corresponding to the target unique identifier from the collapsed content under the user-selected index. The target display content is the specific information the user actually needs to view. It might be the equipment parameters of a device in the equipment data table, the price of a device in the inquiry form, the cost item of a device in the pricing form, or the technical description of a device in the equipment technical document. It's important to note that since the equipment data table, inquiry form, pricing form, and equipment technical document are generated for each function tag, and each function tag contains multiple devices, when a user performs a data query, the target display content of the matching device can be found from the equipment data table, inquiry form, pricing form, and equipment technical document based on the target unique identifier, rather than displaying the entire equipment data table and inquiry form. When a user triggers the index corresponding to a tab, the tab can be directly displayed to the user, as the tab is generated on a device-by-device basis.

[0031] Once the target content to be displayed is determined, it can be output to the user. The output method can be direct display on the interface, or it can be presented through pop-ups, new pages, etc. This allows users to easily obtain various detailed information related to the target basic object instance, meeting their different needs in the design, query, and analysis processes. This embodiment of the application, by identifying the basic object instance, enables users to switch between tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents, using the basic object instance as the core, and thereby find the corresponding design parameter information, thus realizing the data navigation function of the basic object instance.

[0032] In one specific embodiment, the aforementioned data query function can be integrated into the COMS platform as a custom module to achieve the effect of data querying through the COMS platform.

[0033] Optionally, in this embodiment of the application, the method further includes: responding to a data set creation instruction, outputting a data set constraint condition filling interface, identifying each constraint condition from the data set constraint condition filling interface, and determining whether there is a constraint conflict between each constraint condition; if there is no constraint conflict between each constraint condition, then selecting target data that meets all constraints from all tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents, and creating a data set based on the target data, associating each target data in the data set with a data source, so that when a modification operation of the target data is received, the modified data is used to replace the corresponding target data in the data source.

[0034] In this embodiment, when the COMS platform receives a data set creation instruction, it indicates that the user has a need to create a specific data set. To obtain the user's specific requirements for the data set, a data set constraint input interface can be output. This interface serves as the window for user interaction with the COMS platform, presented to the user in an intuitive and user-friendly manner. Users can input various constraints on this interface. Constraints may include data type (such as equipment parameters, technical documents, etc.), data range (such as data within a specific time period, data for a specific equipment model, etc.), and data format (such as table format, text format, etc.). Through this interface, users can clearly express their expectations for the data set, providing a basis for subsequent data filtering and set creation.

[0035] After the user enters the constraints on the data set constraint entry interface, the COMS platform can identify each constraint from the interface. Furthermore, it determines whether there are any conflicts between these constraints. Constraint conflicts can manifest as two or more constraints contradicting each other and unable to be satisfied simultaneously. For example, a user may require the data type to be device parameters, but restrict the data range to a specific time period, within which no device parameter data exists. Methods for determining constraint conflicts can include logical reasoning, rule matching, etc. The COMS platform can compare and analyze these constraints one by one to determine whether conflicts exist.

[0036] If no conflicts are found between the constraints, it means that the user-input constraints can be satisfied simultaneously. At this point, data can be filtered from all previously generated tabs, equipment data sheets, inquiry forms, pricing forms, and equipment technical documents. The filtering process checks and matches each piece of data according to the user-input constraints. For example, if the constraint includes the data type as "equipment parameter," then data related to equipment parameters can be filtered from all documents and tabs; if the constraint also includes the data range as a specific time period, then equipment parameter data within that time period can be further filtered. Through this layered filtering, the target data that satisfies all constraints is finally found. This target data will constitute the data set required by the user.

[0037] After selecting the target data, a data set can be created based on this data. The data set can be a new data structure or file that organizes the target data that meets user constraints, facilitating unified management and use. Furthermore, each target data point in the data set can be associated with its data source. The data source can be previously generated tabs, equipment data tables, inquiry forms, pricing documents, or equipment technical documents, etc. This way, when a user modifies a target data point in the data set, the location of that target data in the original data source can be accurately located, and the modified data can replace the corresponding target data in the source. This ensures data consistency and avoids inconsistencies between the data in the data set and the original data source. Simultaneously, this association and replacement mechanism facilitates data updates and maintenance; when the original data changes, the relevant data in the data set can be updated synchronously in a timely manner.

[0038] In one specific embodiment, the aforementioned data set creation function can be integrated into the COMS platform as a custom module to achieve the effect of creating data sets through the COMS platform.

[0039] Optionally, in this embodiment, step 105, "generating a device data table, inquiry form, pricing form, and equipment technical document corresponding to each functional tag based on the basic object instance under each functional tag," includes: for each functional tag, obtaining a data table template corresponding to the functional tag, mapping the device parameters corresponding to the basic object instance under the functional tag to the general parameter items in the data table template, and adding unmapped device parameters to the custom parameter items in the data table template, establishing a linkage mechanism between each parameter item and the corresponding device parameter, and generating a device data table corresponding to the functional tag; for each functional tag, obtaining an inquiry form template corresponding to the functional tag, filling the device list in the inquiry form template according to the device parameters corresponding to the basic object instance under the functional tag, extracting the inquiry fields to be supplemented from the inquiry form template, generating and outputting an information supplementation interface based on the inquiry fields to be supplemented, and extracting supplementary information from the information supplementation interface. The process involves: 1) Supplementing information by mapping the supplementary information to the field to be supplemented in the inquiry, generating an inquiry form corresponding to the function tag; 2) Obtaining a pricing template corresponding to the function tag, filling the equipment list in the pricing template according to the equipment parameters corresponding to the basic object instance under the function tag, obtaining the latest unit price for each type of equipment in the equipment list, mapping the latest unit price to the equipment list, and generating a pricing form corresponding to the function tag; 3) Obtaining a technical document template corresponding to the function tag, mapping the equipment parameters corresponding to the basic object instance under the function tag to the design parameter section of the technical document template, obtaining the P&ID diagram corresponding to each basic object instance, inserting the P&ID diagram into the corresponding embedding position in the technical document template, generating descriptive text corresponding to the function tag according to the filled design parameter section, filling the descriptive text into the equipment overview section, and generating the equipment technical document corresponding to the function tag.

[0040] In this embodiment, the device data table can be generated as follows: For each function tag, the corresponding data table template is first obtained. The data table template is a pre-designed data structure framework that defines the various parameter items that should be included in the data table. These parameter items are divided into general parameter items and custom parameter items. General parameter items are common and universal device parameters, such as device model and specifications; custom parameter items are used to accommodate special device parameters that cannot be covered by general parameter items.

[0041] After obtaining the data table template, the device parameters corresponding to the basic object instances under the function tag are mapped. The mapping process involves matching the device parameters of the basic object instances with the general parameter items in the data table template, filling the general parameter items with matching device parameters. For device parameters that cannot be matched with general parameter items, they are added to the custom parameter items in the data table template. To ensure data consistency and accuracy, a linkage mechanism can be established between each parameter item and its corresponding device parameter. This way, when the value of a parameter item in the device data table changes, the associated device parameter will also be updated accordingly, and vice versa. This linkage mechanism ensures that the data in the device data table remains synchronized with the device parameters of the basic object instances. Finally, based on the above mapping and linkage settings, the device data table corresponding to the function tag can be generated. In a specific embodiment, the device data table may include a compressor data table, a seal data table, an air cooler data table, a separator data table, a heat exchanger data table, etc.

[0042] Requests for Quotation (RFQ) can be generated as follows: When processing each function tag, the corresponding RQ template is retrieved. The RQ template is a formatted file used to generate RQs, containing basic information such as an equipment list. Then, based on the equipment parameters corresponding to the underlying object instance under the function tag, these parameters are populated into the equipment list within the RQ template. The equipment list can include key information such as the equipment name, model, and quantity, all derived from the equipment parameters of the underlying object instance. After populating the equipment list, fields to be supplemented in the RQ template are extracted. These fields refer to information that needs further clarification during the inquiry process, such as the equipment supplier, delivery date, and price discount terms. An information supplementation interface can then be generated based on these fields and displayed to the user. The user can enter relevant supplementary information in the information supplementation interface. After the user completes the supplementation, the entered information is extracted from the information supplementation interface and mapped to the fields to be supplemented in the RQ template. Through this process, the RQ corresponding to that function tag can be generated. The request for quotation contained complete equipment information and related supplementary information, providing a basis for subsequent procurement and quotation work.

[0043] Pricing sheets can be generated as follows: When processing each function tag, the pricing sheet template corresponding to that function tag is obtained. The pricing sheet template is a formatted file used to calculate and record equipment costs, containing important parts such as an equipment list. Then, based on the equipment parameters corresponding to the underlying object instance under the function tag, these equipment parameters are populated into the equipment list in the pricing sheet template. The equipment list can list detailed information about the equipment, such as equipment name, specifications, and quantity, all derived from the equipment parameters of the underlying object instance. After populating the equipment list, the latest unit price for each type of equipment in the list can be obtained. There are several ways to obtain the latest unit price, such as querying from a supplier's price database or obtaining it from market data. The latest unit price for each type of equipment is then mapped to the equipment list, thus including the quantity and unit price information of the equipment. Finally, based on the quantity and unit price of the equipment in the equipment list, the total price for each type of equipment is calculated, and this total price information is populated into the corresponding position in the pricing sheet template. Through this calculation and population operation, the pricing sheet corresponding to that function tag can be generated. The pricing sheet clearly reflects the cost of the equipment, providing important data support for cost control and budget preparation.

[0044] Equipment technical documentation can be generated as follows: When processing each function tag, the technical document template corresponding to that function tag is obtained. The technical document template is a formatted file used to record equipment technical information, which includes design parameters, equipment overview, and other sections. Then, the equipment parameters corresponding to the basic object instances under the function tag can be mapped to the design parameter section in the technical document template. The design parameter section is the area in the technical document that describes the key technical characteristics of the equipment. By mapping the equipment parameters, the accuracy and completeness of the design parameters in the technical document are ensured. Simultaneously, the P&ID diagrams (Pipes and Instrumentation Diagrams) corresponding to each basic object instance are obtained. P&ID diagrams are important drawings in the equipment design and installation process, showing in detail the equipment's piping connections, instrument layout, and other information. P&ID diagrams can include process valves, actuator accessories, flow meters, control units, equipment, valves, pipes and pipe components, containers, electrical controls, etc. In a specific embodiment, the P&ID diagram can be pre-drawn or a general P&ID diagram of the basic object corresponding to the basic object instance. Furthermore, these P&ID diagrams are inserted into the corresponding embedded points in the technical document template. The embedding location is a pre-defined position in the technical document template for inserting specific content, thus organically combining the P&ID diagram with the equipment technical document. After mapping the design parameters and inserting the P&ID diagram, descriptive text corresponding to the function tag can be generated based on the filled-in design parameter section. The descriptive text is a detailed description of the equipment's technical characteristics, generated based on the content of the design parameter section, ensuring the accuracy and professionalism of the description. Specifically, the aforementioned design parameter section can be used as a guide word input into the invoked large model, which generates the descriptive text. Finally, the generated descriptive text is filled into the equipment overview section of the technical document template. The equipment overview section is a brief introduction to the overall equipment situation; by filling in the descriptive text, the content of the equipment technical document becomes richer and more complete. Through the above steps, the equipment technical document corresponding to the function tag can be generated, providing comprehensive technical information for the design, installation, commissioning, and maintenance of the equipment.

[0045] Optionally, in this embodiment, step 105, "performing a connection reliability check on the basic object instances for establishing connection relationships based on the standard card in the COMOS platform," includes: for any basic object instance, determining a target vector structure based on the device type corresponding to the basic object instance, and determining a target basic object instance that has a connection relationship with the basic object instance; constructing a first target vector according to the target vector structure based on the device parameters corresponding to the basic object instance, and constructing a second target vector according to the target vector structure based on the device parameters corresponding to the target basic object instance; calculating the connection relationship matching degree between the first target vector and the second target vector using a preset matching degree calculation model, and determining the connection reliability between the basic object instance and the target basic object instance based on the connection relationship matching degree.

[0046] In this embodiment, for any given base object instance, the target vector structure can be determined based on the device type corresponding to that base object instance. Device type is a crucial basis for device classification; different types of devices have different characteristics and parameters. For example, compressors and valves differ significantly in function, structure, and working principle, and their parameter types and importance also differ. A pre-stored table of correspondences between different device types and vector structures can be maintained. Once the device type of the base object instance is obtained, the target vector structure matching it is determined by querying this table. The target vector structure defines how to organize the various parameters of the device into a vector, including the vector's dimensions and the parameter types represented by each dimension.

[0047] Furthermore, it can identify target basic object instances that are connected to the current basic object instance. In the design of compressor unit equipment, there are complex connections between various devices, such as piping connections and electrical connections. The COMOS platform can analyze the physical connections and logical relationships between devices to identify other basic object instances that are directly or indirectly connected to the current basic object instance. These connected basic object instances are the target basic object instances. Identifying the target basic object instances helps in subsequent analysis of the reliability of their connections with the current basic object instance.

[0048] After determining the target vector structure and the target base object instance, the vector construction begins. For any base object instance, the COMS platform can obtain its corresponding device parameters. Device parameters can include physical and performance indicators such as device size, power, pressure rating, and flow rate. Then, according to the previously determined target vector structure, these device parameters are filled into the corresponding dimensions of the vector to construct the first target vector. For example, if the target vector structure defines the first dimension as device size and the second dimension as device power, then the device size parameter of the base object instance is assigned to the first dimension, the device power parameter is assigned to the second dimension, and so on, completing the construction of the first target vector.

[0049] Similarly, for the target base object instance, its corresponding device parameters can be obtained, and a second target vector can be constructed according to the same target vector structure. In this way, the device parameters of the two base object instances are represented in a unified vector form, providing a data foundation for subsequent calculation of the connection relationship matching degree between them.

[0050] The COMOS platform also allows for the pre-configuration of a matching degree calculation model, which is used to calculate the similarity or matching degree between two vectors. Common matching degree calculation methods include Euclidean distance and cosine similarity. Different calculation methods are suitable for different scenarios, and the appropriate matching degree calculation model can be selected according to actual needs.

[0051] After obtaining the first and second target vectors, the COMS platform can input these two vectors into a preset matching degree calculation model. The model can calculate the connection degree of the two vectors based on the parameter values ​​of each dimension. The connection degree of matching can be a numerical value, reflecting the similarity or matching degree of the two basic object instances in terms of device parameters. A larger value indicates that the device parameters of the two basic object instances are closer, and the connection relationship between them is likely more reasonable; a smaller value indicates that the device parameters are more different, and the connection relationship may have problems.

[0052] Finally, the reliability of the connection between any base object instance and the target base object instance is determined based on the calculated connection matching degree. For example, a threshold can be set: when the connection matching degree is greater than the threshold, the connection reliability is considered high, and the connection between the two base object instances is reasonable; when the connection matching degree is less than the threshold, the connection reliability is considered low, and the connection relationship may need to be checked and adjusted. In this way, the connection relationships between devices can be quantitatively evaluated, potential connection problems can be identified in a timely manner, and the quality and reliability of the collaborative design of compressor unit equipment can be improved.

[0053] Optionally, in this embodiment, the step of "calculating the connection relationship matching degree between the first target vector and the second target vector using a preset matching degree calculation model" includes: inputting the first target vector and the second target vector into the preset matching degree calculation model; determining soft matching indicators and hard matching indicators from the first target vector and the second target vector using the preset matching degree calculation model; for each soft matching indicator, obtaining the tolerance function corresponding to the soft matching indicator, and determining the matching degree between the first element corresponding to the soft matching indicator in the first target vector and the second element corresponding to the soft matching indicator in the second target vector based on the tolerance function; for each hard matching indicator, obtaining the matching verification rule corresponding to the hard matching indicator, and determining the matching degree between the third element corresponding to the hard matching indicator in the first target vector and the fourth element corresponding to the hard matching indicator in the second target vector based on the matching verification rule; and calculating the connection relationship matching degree between the first target vector and the second target vector based on each matching degree.

[0054] In this embodiment, when it is necessary to calculate the matching degree of the connection relationship between two basic object instances, the constructed first target vector and second target vector can first be input into a preset matching degree calculation model. This preset matching degree calculation model is a pre-designed set of algorithms or rules used to analyze the similarity and matching degree between the two vectors.

[0055] After receiving two target vectors, the pre-defined matching degree calculation model can filter out soft and hard matching indicators from these vectors based on its internal rules and logic. Soft matching indicators are those that allow for a certain degree of deviation. For example, for some auxiliary pipelines, the thickness of the pipe wall can vary slightly within a certain range. Hard matching indicators, on the other hand, have extremely strict requirements. For example, in pipe connections, the pipe dimensions must be exactly the same to achieve a tight, safe, and effective connection; otherwise, problems such as leakage and installation failure may occur. Based on these characteristics, the pre-defined matching degree calculation model can accurately distinguish between soft and hard matching indicators from the two input target vectors, preparing for subsequent targeted matching degree judgments.

[0056] After determining the soft-match index, a tolerance function can be obtained for each index. The tolerance function can be a predefined mathematical function or rule that describes the acceptable range of difference between corresponding elements in two vectors for that soft-match index. After obtaining the tolerance function, the first element corresponding to the soft-match index can be extracted from the first target vector, and the second element from the second target vector. Then, the values ​​of these two elements are substituted into the tolerance function for calculation. The tolerance function outputs a judgment result based on the input element values, indicating whether the difference between the two elements is within an acceptable range. If the difference is within the acceptable range, the two vectors are considered to match for that soft-match index; otherwise, they are considered not to match. In this way, an independent matching degree judgment can be performed for each soft-match index, providing a foundation for subsequent comprehensive calculation of the connection relationship matching degree.

[0057] For hard-match metrics, their corresponding matching verification rules can be obtained. Matching verification rules are more stringent and explicit, and can be specific numerical comparisons, logical judgments, etc. For example, for the hard-match metric of device interface size, the matching verification rule can stipulate that the interface sizes of two devices must be exactly the same to match. After obtaining the matching verification rule, the third element corresponding to the hard-match metric can be extracted from the first target vector, and the fourth element corresponding to the hard-match metric can be extracted from the second target vector. Then, these two elements are compared and judged according to the matching verification rule. If the requirements of the matching verification rule are met, the two vectors are considered to match for that hard-match metric; otherwise, they are considered not to match. Because hard-match metrics are crucial to the connection relationship, this judgment is strict and precise, ensuring the correct matching of key parameters, thereby guaranteeing reliable connections between devices.

[0058] After assessing the matching degree of all soft and hard matching metrics, the connection matching degree between the first and second target vectors can be calculated based on these results. Various calculation methods can be used, such as a weighted average. The COMOS platform assigns a weight to each soft and hard matching metric, based on its importance to the connection relationship. Generally, hard matching metrics have relatively higher weights because they have a more critical impact on the connection relationship; soft matching metrics have relatively lower weights, but still influence the overall matching degree. Then, the matching degree of each metric is multiplied by its corresponding weight to obtain a weighted matching degree value. Finally, all weighted matching degree values ​​are summed to obtain the connection matching degree between the first and second target vectors. This connection matching degree is a comprehensive value that fully reflects the matching status of the two vectors across various metrics. A higher value indicates a more consistent connection between the two basic object instances and higher connection reliability; a lower value indicates a lower connection matching degree and potential connection problems. This method allows for a quantitative evaluation of the connection relationship between two basic object instances, providing a basis for optimizing device collaborative design.

[0059] This application's embodiments, by precisely dividing soft and hard matching indicators, can distinguish between critical and non-critical connection parameters, rigorously verifying hard indicators and flexibly tolerating soft indicators, greatly improving the accuracy of matching degree calculation. Simultaneously, the tolerance function and matching verification rules constructed based on the characteristics of different indicators give the solution high flexibility, adapting to diverse device connection scenarios. Moreover, the preset model and rule framework have good scalability, facilitating adjustments as new devices and requirements are added. Furthermore, this quantitative evaluation method provides a scientific and practical basis for device collaborative design, enabling the early detection of potential connection problems and effectively ensuring the security and reliability of device connections.

[0060] In one specific embodiment, the aforementioned connection reliability check function can be integrated into the COMOS platform as a custom module to achieve the effect of performing connection reliability checks through the COMOS platform.

[0061] In this embodiment of the application, the functional labels may optionally include compressor equipment, pump equipment, sealing equipment, separator equipment, filter equipment, actuator, drive mechanism, cooler, heat exchanger, steam generator, and furnace.

[0062] In this embodiment, pump equipment can be tagged with sub-labels such as canned motor pump, centrifugal fan pump (horizontal), centrifugal pump (vertical), gear pump, screw pump, etc. Sealing equipment can be tagged with sub-labels such as dry gas seal. Separator equipment can be tagged with sub-labels such as separator (domestic) and separator (foreign). Filter equipment can be tagged with sub-labels such as T-type filter, Y-type filter, liquid filter, bag filter, candle or cartridge filter, fixed type air bed filter, vacuum filter, etc. Actuators can be tagged with sub-labels such as mechanical coupling, permanent magnet variable speed coupling, gearbox, coupling, etc. Coolers can be tagged with sub-labels such as heat exchanger (conventional, cross-flow), heat exchanger (conventional, non-cross-flow), air cooler with louvers, heat exchanger tube bundle, double tube heat exchanger, plate heat exchanger, cooler, spiral heat exchanger, membrane evaporator, air cooler, etc.

[0063] In one specific embodiment, a schematic diagram of each function label is shown below. Figure 2 As shown.

[0064] Furthermore, as Figure 1 In terms of specific implementation, this application provides a collaborative design device for compressor unit equipment based on the COMOS platform, such as... Figure 3 As shown, the device includes: The parsing module is used to receive the design requirement file corresponding to the compressor unit to be designed, parse the design requirement file to obtain the equipment parameters corresponding to each device in the compressor unit to be designed, and integrate the equipment parameters, the standard card corresponding to the general compressor unit and the basic object database in the COMS platform. The directory creation module is used to create a project directory in the COMOS platform, and to create a compressor unit equipment object category directory under the project directory, wherein the equipment object category directory corresponds to the functional tags of the general compressor unit; The object invocation module is used to invoke multiple basic objects corresponding to the compressor unit to be designed from the basic object database integrated by the COMOS platform according to the device parameters, and set each basic object under the corresponding function tag. The connection relationship construction module is used to assign values ​​to the basic objects under each function tag according to the device parameters, obtain basic object instances, and construct the connection relationship between the basic object instances; The data generation module is used to perform connection reliability checks on the basic object instances that build the connection relationship based on the standard card in the COMOS platform, and after passing the connection reliability check, it generates the equipment data table, inquiry form, pricing form and equipment technical document corresponding to each function tag based on the basic object instances under each function tag.

[0065] Optionally, each of the underlying object instances corresponds to a unique identifier; the device further includes an identifier binding module; the identifier binding module is used for: After generating the equipment data table, inquiry form, pricing form, and equipment technical document corresponding to each function tag, for each basic object instance, the target equipment parameters corresponding to the basic object instance are determined from the equipment parameters, and based on the target equipment parameters, tabs corresponding to the basic object instance are generated, and the tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents under the function tags corresponding to the basic object instance are all bound to the unique identifier of the basic object instance; Accordingly, the device further includes a display module; the display module is used for: In response to a data query command, a unique target identifier is obtained based on the data query command, and the tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents bound to the unique target identifier are obtained. The bound tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents are respectively used as collapsed content, and an index is generated for each collapsed content. A data feedback interface is generated based on each collapsed content and its corresponding index. When any index other than the index corresponding to the bound tab is selected, the target display content corresponding to the unique target identifier is determined from the collapsed content under the selected index based on the unique target identifier, and the target display content is output.

[0066] Optionally, the apparatus further includes a data set creation module; the data set creation module is configured to: In response to the data set creation command, a data set constraint filling interface is output, and each constraint is identified from the data set constraint filling interface to determine whether there is a constraint conflict between the constraints. If there are no constraints among the constraints, target data that meets all constraints is selected from all tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents. A data set is created based on the target data, and each target data in the data set is associated with a data source so that when a modification operation is received on the target data, the modified data is used to replace the corresponding target data in the data source.

[0067] Optionally, the data generation module is used for: For each function tag, obtain the data table template corresponding to the function tag, map the device parameters corresponding to the basic object instance under the function tag to the general parameter items in the data table template, and add the unmapped device parameters to the custom parameter items in the data table template. Establish a linkage mechanism between each parameter item and the corresponding device parameter to generate the device data table corresponding to the function tag. For each function tag, obtain the inquiry form template corresponding to the function tag, fill the equipment list in the inquiry form template according to the equipment parameters corresponding to the basic object instance under the function tag, extract the inquiry fields to be supplemented from the inquiry form template, generate and output the information supplementation interface based on the inquiry fields to be supplemented, extract the supplementary information from the information supplementation interface, map the supplementary information to the inquiry fields to be supplemented, and generate the inquiry form corresponding to the function tag. For each function tag, obtain the pricing sheet template corresponding to the function tag, fill the equipment list in the pricing sheet template according to the equipment parameters corresponding to the basic object instance under the function tag, obtain the latest unit price of each type of equipment in the equipment list, map the latest unit price to the equipment list, and generate the pricing sheet corresponding to the function tag. For each function tag, obtain the technical document template corresponding to the function tag, map the device parameters corresponding to the basic object instance under the function tag to the design parameter section in the technical document template, obtain the P&ID diagram corresponding to each basic object instance, insert the P&ID diagram into the corresponding embedding position in the technical document template, generate the description text corresponding to the function tag according to the filled design parameter section, fill the description text into the device overview section, and generate the device technical document corresponding to the function tag.

[0068] Optionally, the data generation module is further configured to: For any basic object instance, determine the target vector structure based on the device type corresponding to the basic object instance, and determine the target basic object instance that has a connection relationship with the basic object instance. Based on the device parameters corresponding to any of the base object instances, a first target vector is constructed according to the target vector structure; and based on the device parameters corresponding to the target base object instances, a second target vector is constructed according to the target vector structure. By using a preset matching degree calculation model, the connection relationship matching degree between the first target vector and the second target vector is calculated, and the connection reliability between any basic object instance and the target basic object instance is determined based on the connection relationship matching degree.

[0069] Optionally, the data generation module is further configured to: The first target vector and the second target vector are input into the preset matching degree calculation model. Through the preset matching degree calculation model, soft matching index and hard matching index are determined from the first target vector and the second target vector. For each soft matching indicator, obtain the tolerance function corresponding to the soft matching indicator, and based on the tolerance function, determine the matching degree between the first element corresponding to the soft matching indicator in the first target vector and the second element corresponding to the soft matching indicator in the second target vector. For each hard match metric, obtain the matching verification rule corresponding to the hard match metric, and based on the matching verification rule, determine the matching degree between the third element corresponding to the hard match metric in the first target vector and the fourth element corresponding to the hard match metric in the second target vector; Based on each matching degree, the connection relationship matching degree between the first target vector and the second target vector is calculated.

[0070] Optionally, the functional labels include compressor equipment, pump equipment, sealing equipment, separator equipment, filter equipment, actuator, drive mechanism, cooler, heat exchanger, steam generator, and furnace.

[0071] It should be noted that other corresponding descriptions of the functional units involved in the collaborative design device for compressor unit equipment provided in this application embodiment can be found by referring to... Figures 1 to 2 The corresponding descriptions in the method will not be repeated here.

[0072] This application also provides a computer device, which may specifically be a personal computer, a server, a network device, etc. Figure 4 As shown, the computer device includes a bus, a processor, memory, and a communication interface, and may also include an input / output interface and a display device. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database stores location information. The network interface allows communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in the various method embodiments.

[0073] Those skilled in the art will understand that Figure 4The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0074] In one embodiment, a computer-readable storage medium is provided, which may be non-volatile or volatile, having stored thereon a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0075] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0076] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0077] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0078] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0079] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A collaborative design method for compressor unit equipment based on the COMS platform, characterized in that, include: The system receives the design requirement file corresponding to the compressor unit to be designed, parses the design requirement file to obtain the equipment parameters corresponding to each device in the compressor unit to be designed, and integrates the equipment parameters, the standard card corresponding to the general compressor unit, and the basic object database in the COMS platform. Create a project directory in the COMOS platform, and create a compressor unit equipment object category directory under the project directory, wherein the equipment object category directory contains various function tags for general compressor units; Based on the device parameters, multiple basic objects corresponding to the compressor unit to be designed are retrieved from the basic object database integrated by the COMOS platform, and each basic object is set under the corresponding function tag. Based on the device parameters, assign values ​​to the basic objects under each function tag to obtain basic object instances, and construct the connection relationship between the basic object instances; Based on the standard card in the COMOS platform, a connection reliability check is performed on the basic object instance for building the connection relationship. After passing the connection reliability check, based on the basic object instance under each function tag, a device data table, inquiry form, pricing form and device technical document corresponding to each function tag are generated.

2. The method according to claim 1, characterized in that, Each instance of the basic object has a unique identifier; after generating the equipment data table, inquiry form, pricing form, and equipment technical document corresponding to each functional tag, the method further includes: For each basic object instance, the target device parameters corresponding to the basic object instance are determined from the device parameters, and a tab corresponding to the basic object instance is generated based on the target device parameters. The tab, the device data table, the inquiry form, the pricing form, and the equipment technical documents under the corresponding function tab of the basic object instance are all bound to the unique identifier of the basic object instance. Accordingly, the method further includes: In response to a data query command, a unique target identifier is obtained based on the data query command, and the tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents bound to the unique target identifier are obtained. The bound tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents are respectively used as collapsed content, and an index is generated for each collapsed content. A data feedback interface is generated based on each collapsed content and its corresponding index. When any index other than the index corresponding to the bound tab is selected, the target display content corresponding to the unique target identifier is determined from the collapsed content under the selected index based on the unique target identifier, and the target display content is output.

3. The method according to claim 1, characterized in that, The method further includes: In response to the data set creation command, a data set constraint filling interface is output, and each constraint is identified from the data set constraint filling interface to determine whether there is a constraint conflict between the constraints. If there are no constraints among the constraints, target data that meets all constraints is selected from all tabs, equipment data tables, inquiry forms, pricing forms, and equipment technical documents. A data set is created based on the target data, and each target data in the data set is associated with a data source so that when a modification operation is received on the target data, the modified data is used to replace the corresponding target data in the data source.

4. The method according to claim 1, characterized in that, Based on the basic object instances under each functional tag, the system generates equipment data tables, inquiry forms, pricing forms, and equipment technical documents corresponding to each functional tag, including: For each function tag, obtain the data table template corresponding to the function tag, map the device parameters corresponding to the basic object instance under the function tag to the general parameter items in the data table template, and add the unmapped device parameters to the custom parameter items in the data table template. Establish a linkage mechanism between each parameter item and the corresponding device parameter to generate the device data table corresponding to the function tag. For each function tag, obtain the inquiry form template corresponding to the function tag, fill the equipment list in the inquiry form template according to the equipment parameters corresponding to the basic object instance under the function tag, extract the inquiry fields to be supplemented from the inquiry form template, generate and output the information supplementation interface based on the inquiry fields to be supplemented, extract the supplementary information from the information supplementation interface, map the supplementary information to the inquiry fields to be supplemented, and generate the inquiry form corresponding to the function tag. For each function tag, obtain the pricing sheet template corresponding to the function tag, fill the equipment list in the pricing sheet template according to the equipment parameters corresponding to the basic object instance under the function tag, obtain the latest unit price of each type of equipment in the equipment list, map the latest unit price to the equipment list, and generate the pricing sheet corresponding to the function tag. For each function tag, obtain the technical document template corresponding to the function tag, map the device parameters corresponding to the basic object instance under the function tag to the design parameter section in the technical document template, obtain the P&ID diagram corresponding to each basic object instance, insert the P&ID diagram into the corresponding embedding position in the technical document template, generate the description text corresponding to the function tag according to the filled design parameter section, fill the description text into the device overview section, and generate the device technical document corresponding to the function tag.

5. The method according to claim 1, characterized in that, The connection reliability check performed on the basic object instance for establishing the connection relationship based on the standard card in the COMOS platform includes: For any basic object instance, determine the target vector structure based on the device type corresponding to the basic object instance, and determine the target basic object instance that has a connection relationship with the basic object instance. Based on the device parameters corresponding to any of the base object instances, a first target vector is constructed according to the target vector structure; and based on the device parameters corresponding to the target base object instances, a second target vector is constructed according to the target vector structure. By using a preset matching degree calculation model, the connection relationship matching degree between the first target vector and the second target vector is calculated, and the connection reliability between any basic object instance and the target basic object instance is determined based on the connection relationship matching degree.

6. The method according to claim 5, characterized in that, The step of calculating the connection relationship matching degree between the first target vector and the second target vector using a preset matching degree calculation model includes: The first target vector and the second target vector are input into the preset matching degree calculation model. Through the preset matching degree calculation model, soft matching index and hard matching index are determined from the first target vector and the second target vector. For each soft matching indicator, obtain the tolerance function corresponding to the soft matching indicator, and based on the tolerance function, determine the matching degree between the first element corresponding to the soft matching indicator in the first target vector and the second element corresponding to the soft matching indicator in the second target vector. For each hard match metric, obtain the matching verification rule corresponding to the hard match metric, and based on the matching verification rule, determine the matching degree between the third element corresponding to the hard match metric in the first target vector and the fourth element corresponding to the hard match metric in the second target vector. Based on each matching degree, the connection relationship matching degree between the first target vector and the second target vector is calculated.

7. The method according to claim 1, characterized in that, The functional labels include compressor equipment, pump equipment, sealing equipment, separator equipment, filter equipment, actuators, drive mechanisms, coolers, heat exchangers, steam generators, and furnaces.

8. A collaborative design device for compressor unit equipment based on the COMS platform, characterized in that, include: The parsing module is used to receive the design requirement file corresponding to the compressor unit to be designed, parse the design requirement file to obtain the equipment parameters corresponding to each device in the compressor unit to be designed, and integrate the equipment parameters, the standard card corresponding to the general compressor unit and the basic object database in the COMS platform. The directory creation module is used to create a project directory in the COMOS platform, and to create a compressor unit equipment object category directory under the project directory, wherein the equipment object category directory corresponds to the functional tags of the general compressor unit; The object invocation module is used to invoke multiple basic objects corresponding to the compressor unit to be designed from the basic object database integrated by the COMOS platform according to the device parameters, and set each basic object under the corresponding function tag. The connection relationship construction module is used to assign values ​​to the basic objects under each function tag according to the device parameters, obtain basic object instances, and construct the connection relationship between the basic object instances; The data generation module is used to perform connection reliability checks on the basic object instances that build the connection relationship based on the standard card in the COMOS platform, and after passing the connection reliability check, it generates the equipment data table, inquiry form, pricing form and equipment technical document corresponding to each function tag based on the basic object instances under each function tag.

9. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 7.

10. A computer device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 7.

Images