Model data processing method and data processing system for AVEVA AIM platform

Abstract

The invention provides a model data processing method and a data processing system for an AVEVA AIM platform. The method comprises the following steps: acquiring a model data file; based on the model data file, obtaining a model file which can be processed by the AVEVA AIM platform, and obtaining corresponding attribute information; based on the attribute information, extracting an attribute file which can be processed by the platform; inputting the model file and the attribute file into the platform; according to the data processing method provided by the embodiment of the invention, different model data files are processed and imported into the platform in a direct or indirect manner, and after all types of model data related to the project are processed, the integrity of the model can be effectively improved, and different types of attribute information can be imported into the platform; the problem of data integrity is effectively solved, whole plant model information can be displayed and managed on the platform, and preparation is provided for realizing project digital integration and delivery.

Description

Technical Field

[0001] The invention belongs to the technical field of data information processing, and in particular relates to a model data processing method and a data processing system for an AVEVA AIM platform. Background Art

[0002] As the scale of industrial digitalization gradually increases, under the strong trend of digital and intelligent transformation, the implementation of digital delivery for large projects has become the norm. Ensuring the integrity of factory 3D modeling is the basis for implementing digital delivery and building digital factories. For large projects, the sources of models are wide and varied, and integrating them into the AVEVA AIM (digital delivery) platform is a huge project.

[0003] The current AVEVA AIM platform can only receive model files of specified types, which means that model files in other formats cannot be entered into the AVEVA AIM platform, which in turn affects the integrity of the model. In order to enable model files in other formats to be indirectly received by the platform, the traditional manual model conversion steps are particularly cumbersome and inaccurate, making it impossible to perform effective and efficient data processing. In addition, traditional model files lack model data consistency verification, which leads to low data accuracy in the process of processing model data. Summary of the invention

[0004] In view of the above problems existing in the prior art, the present invention provides a data processing method and a data processing system for the AVEVA AIM platform, which can digitally deliver three-dimensional data, expand the scope of modeling data that the AVEVA AIM platform can accept, lower the entry threshold of participants, and improve the feasibility of digital delivery of projects.

[0005] To achieve the above purpose, the technical solution adopted by the embodiment of the present invention is:

[0006] On the one hand, the present invention provides a model data processing method for the AVEVA AIM platform, comprising the following steps: obtaining a model data file; based on the model data file, obtaining a model file that can be processed by the AVEVA AIM platform, and obtaining corresponding attribute information; based on the attribute information, extracting an attribute file that can be processed by the AVEVA AIM platform; inputting the model file and the attribute file into the AVEVA AIM platform.

[0007] In some embodiments of the present invention, obtaining a model file that can be processed by the AVEVA AIM platform based on the model data file includes: determining whether the file type of the model data file is included in a preset file type; when the determination result is yes, calling the interface processing of the AVEVA AIM platform; when the determination result is no, when the file type of the model data file is included in a preset convertible file type, converting the model data file into the model file; storing the model file in an intermediate data folder, and calling the interface processing of the AVEVA AIM platform.

[0008] In some embodiments of the present invention, the preset file types include: review model file type (RVM), industry foundation class file type (IFC) and engineering design file type (for example, DWG); the preset convertible file types include: STEP or STP file type, STL or MAC file type, NWC or NWD file type.

[0009] In some embodiments of the present invention, when the judgment result is no, when the file type of the model data file is included in the preset convertible file type, the model data file is converted into the model file, including the following steps: judging whether the file type of the model data file is the STEP or STP file type in the preset convertible file type, when the judgment result is yes, calling the special category model import interface (MEI Export), importing the model data file into the plant three-dimensional layout design management system (PDMS), and exporting the review model file; judging whether the file type of the model data file is the STL or MAC file type in the preset convertible file type, when the judgment result is yes, importing the model data file into the AVEVA E3D modeling software (AVEVA E3D), and exporting the review model file; judging whether the file type of the model data file is the NWC or NWD file type in the preset convertible file type, when the judgment result is yes, converting the model data file into the IFC format, importing it into the AVEVA E3D modeling software, and exporting the review model file.

[0010] In some embodiments of the present invention, calling a special category model import interface, importing the model data file into a plant three-dimensional layout design management system, and exporting a review model file includes: calling a macro programming language module (PML); adjusting the attribute hierarchy information of the model data file to be consistent with the review model file; superimposing and calculating the model coordinate information after the hierarchy adjustment; and exporting it as a review model file.

[0011] In some embodiments of the present invention, when the file type of the model data file is not included in the preset convertible file types, the file information of the model data file is recorded.

[0012] In some embodiments of the present invention, obtaining the corresponding attribute information based on the model data file includes: determining whether the model data file contains attribute information that can be extracted by the AVEVA AIM platform; when the determination result is yes, extracting the attribute information; when the determination result is no, obtaining the attribute information by means of attribute assignment.

[0013] In some embodiments of the present invention, the method of obtaining the attribute information by assigning attributes includes: when the model data file is a file in the IFC format, obtaining the attribute information by adding an attribute object identifier in the file in the IFC format and configuring the attribute mapping group file in the three-dimensional data processing interface; when the model data file is a file in the DWG format, obtaining the attribute information by configuring the attribute mapping file in the three-dimensional data processing interface.

[0014] In some embodiments of the present invention, inputting the model file and the property file into the AVEVA AIM platform comprises the following steps: storing the model file and the property file in a database; and displaying the model file and the property file in a display window of the AVEVA AIM platform.

[0015] On the other hand, a data processing system is also provided for use with the AVEVA AIM platform, comprising: an acquisition module for acquiring a model data file; a conversion module for acquiring, based on the model data file, a model file that can be processed by the AVEVA AIM platform, and corresponding attribute information; an extraction module for extracting, based on the attribute information, an attribute file that can be processed by the AVEVA AIM platform; and a delivery module for inputting the model file and the attribute file into the AVEVA AIM platform.

[0016] Compared with the prior art, the beneficial effects of the present invention are:

[0017] The model data processing method for the AVEVA AIM platform of the embodiment of the present invention, by establishing a digital delivery method and a corresponding integration system based on the AVEVA NET platform that integrates multi-industry and multi-type three-dimensional data, improves the integrity of the theoretical model from 70% to more than 95%, reduces the PDMS re-molding work required by suppliers and some design units, and lays a good foundation for the implementation of digital delivery of large-scale industrial projects; accordingly, it expands the types of acceptable modeling software, lowers the entry threshold for digital project participants, and indirectly saves project investment costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In the drawings, which are not necessarily drawn to scale, the same reference numerals may describe similar parts in different views. The same reference numerals with letter suffixes or different letter suffixes may represent different instances of similar parts. The accompanying drawings generally illustrate various embodiments by way of example and not limitation, and together with the specification and claims, are used to illustrate the embodiments of the invention. When appropriate, the same reference numerals are used throughout the drawings to refer to the same or similar parts. Such embodiments are illustrative and are not intended to be exhaustive or exclusive embodiments of the present apparatus or method.

[0019] Figure 1 It is a flow chart of a model data processing method for AVEVA AIM platform according to an embodiment of the present invention;

[0020] Figure 2 is a flow chart of a model data processing method for AVEVA AIM platform according to a fourth embodiment of the present invention;

[0021] Figure 3 Schematic diagram of a data processing system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] Below, the specific embodiments of the present invention are described in detail in conjunction with the accompanying drawings, but are not intended to limit the present invention. In order to enable those skilled in the art to better understand the technical solution of the present invention, the present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. Below, the embodiments of the present invention are further described in detail in conjunction with the accompanying drawings and specific embodiments, but are not intended to limit the present invention.

[0023] All terms (including technical terms or scientific terms) used in the present invention have the same meanings as those understood by ordinary technicians in the field to which the present invention belongs, unless otherwise specifically defined. It should also be understood that terms defined in general dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an idealized or extremely formal sense, unless explicitly defined herein.

[0024] The present invention uses the term "integration". In the application scenario of the present invention, it means that the model data files of different formats are processed by the method of the present invention to break the isolated islands of different types of data information, so that they can be received and merged by the AVEVA AIM platform after corresponding conversion processing.

[0025] In addition, in order to improve the readability of the application documents, some of the terms below will be described in the form of abbreviations based on the language habits of those skilled in the art in actual operations.

[0026] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0027] At present, in digital delivery projects, 3D models (modeling) are widely used in various industries. Various software not only meet design needs, but also provide good user experience in visualization, verification calculation, rapid drawing and other functions, while improving design efficiency and accuracy. As a non-EPC (non-design procurement and construction general contracting) project, due to the large number of participants, for example, there are both device design institutes and equipment suppliers, as well as general contractors, the types of 3D modeling software vary. Among them, for device design institutes, projects usually require the unified use of PDMS software; the modeling software used by equipment suppliers usually includes: Solidworks, CADworx, Pro / E, UG, 3DS MAX, etc.; and general contractors mainly use Revit and PDMS.

[0028] The above software not only involves the chemical industry, but also includes different technical fields such as architecture, animation rendering, and mechanical manufacturing, which makes it impossible to ensure the uniformity of the exported data file format. Data in various formats cannot be directly connected due to different attributes. How to connect the respective information data islands, improve data processing efficiency, and provide guarantees for the final data integration is currently an important part of ensuring the integrity of digital delivery information. To this end, the present invention provides the following solution.

[0029] On the one hand, an embodiment of the present invention provides a model data processing method for AVEVA AIM platform, such as Figure 1 As shown, the method includes:

[0030] Step S11, obtaining a model data file;

[0031] Step S12, based on the model data file, obtaining a model file that can be processed by the AVEVA AIM platform, and obtaining corresponding attribute information;

[0032] Step S13, extracting attribute files that can be processed by the AVEVA AIM platform based on the attribute information;

[0033] Step S14, inputting the model file and the attribute file into the AVEVA AIM platform.

[0034] In this embodiment, by establishing a platform based on AVEVA AIM, a digital delivery method system for multi-industry and multi-type 3D data can be integrated, effectively improving data processing efficiency and the integrity of theoretical models, reducing PDMS re-molding work, and providing preparation for the smooth implementation of digital delivery of large-scale industrial projects. Specifically,

[0035] In step S11, a model data file is obtained. The model data file mainly comes from: a three-dimensional model file of the entire device provided by the EPC project contractor, an interface model file provided by the design institute and the equipment supplier, and a mechanical model file of important equipment. Of course, it can also include other different types of model data files related to engineering construction.

[0036] In step S12, based on the model data file, a model file that can be processed by the AVEVA AIM platform is obtained, and corresponding attribute information is obtained.

[0037] In the embodiment of the present invention, step S12 may be implemented as the following steps A1-A2.

[0038] In step A1, based on the model data file, a model file that can be processed by the AVEVA AIM platform is obtained;

[0039] In step A2, corresponding attribute information is obtained based on the model data file.

[0040] Specifically, in step A1, since the model data files originate from different modeling software or from different owners, the exportable file formats or file types are different. In order to avoid deviations and omissions in the model data files imported into the AVEVA AIM platform, various model data files need to be converted into model files that can be directly processed by the AVEVA AIM platform. For example, the model data files are converted to obtain model files, and the file formats of the model files include but are not limited to RVM, IFC and DWG. Although the model files obtained after the conversion are still of different types, they can be received by the AVEVA AIM platform and directly uploaded to the AVEVA AIM platform, which greatly improves the efficiency of data processing.

[0041] Step A1 further comprises the following steps:

[0042] Step A1-1, determine whether the file type of the model data file is included in the preset file types; in this embodiment, the preset file types include: review model file type, industrial foundation file type and engineering design file type.

[0043] Step A1-2, when the judgment result is yes, call the interface processing of the AVEVA AIM platform. The following will explain one by one through multiple embodiments based on the specific manifestation of the preset file type.

[0044] In the first embodiment of the present invention, the file type of the model data file is an RVM format file, which is used to describe a three-dimensional model.

[0045] In the first embodiment, since the model data file in the PDMS data is a file in RVM format, the model data file in the PDMS data can be directly imported into the AVEVA AIM platform without the need for other auxiliary technical means for conversion. Furthermore, before exporting the model data file in RVM format of the three-dimensional model, the hierarchical structure and the bit number coding of the project object decomposition structure (PBS) in the PDMS need to be standardized to ensure that the bit number coding contained in the RVM file can be extracted by the AVEVA AIM platform after it is input into the AVEVA AIM platform.

[0046] In a second embodiment of the present invention, the model data file is Revit three-dimensional data used to describe modeling, and is exported to an IFC format model file so as to be received by the AVEVA AIM platform.

[0047] Here, let’s give a brief introduction to Revit data. Revit is the name of a series of software. The Revit series of software is built for Building Information Modeling (BIM) to help design, build and maintain better quality and more energy-efficient buildings.

[0048] In the second embodiment, the Revit data is converted into a model file in the IFC format. The Revit data can be directly processed through the IFC-Gateway (three-dimensional data processing interface) of the AVEVA AIM platform, and the model file in the IFC format can be extracted.

[0049] In a third embodiment of the present invention, the file type of the model data file is a DWG file type used to represent a three-dimensional model.

[0050] DWG files are Autodesk proprietary files from CADWorx (3D plant design) software. The three-dimensional data of DWG file types can be directly processed through the AVEVA AIM platform tool GCT (Gateway Configuration Tool). The files obtained after processing can be received by the AVEVA AIM platform. At the same time, the bit number information contained in the DWG file corresponds to the definition of the block name as the corresponding bit number name. By configuring the mapping files in GCT, the content of the corresponding block is extracted to obtain the corresponding attribute information and generate the corresponding XML file.

[0051] In the first to third embodiments, RVM, IFC and DWG can be directly received by the AVEVA AIM platform, or can be received by the platform after being processed by the interface of the AVEVA AIM platform.

[0052] When the file type of the model data file is included in the preset convertible file type, the model data file is converted into the model file; the model file is stored in an intermediate data folder, and the interface processing of the AVEVA AIM platform is called.

[0053] In an embodiment of the present invention, the preset convertible file types include: STEP or STP file type, STL or MAC file type, NWC or NWD file type. The aforementioned multiple types of files cannot be directly received by the AVEVA AIM platform, and the files need to be converted to obtain file types that can be received by the AVEVA AIM platform; in addition, the preset convertible files are not limited to the several file types shown, and the conversion methods of other file types are not further described here.

[0054] Since the file types included in the above preset convertible file types are not the same and cannot be directly received by the AVEVA AIM platform, corresponding processing methods need to be used for conversion according to different file types to obtain RVM format model files that can be received by the AVEVA AIM platform.

[0055] For example, in step A1-3, when the file type of the model data file is included in the preset convertible file type, converting the model data file into the model file specifically includes the following steps:

[0056] Step A1-3-1, determining whether the file type of the model data file is a STEP or STP file type in the preset convertible file type, and when the determination result is yes, calling a special category model import interface, importing the model data file into PDMS, and exporting an RVM file; wherein,

[0057] The calling of the special category model import interface, importing the model data file into PDMS, and exporting the RVM file includes:

[0058] Calling the Macro Programming Language Module (PML);

[0059] Adjusting the attribute level information of the model data file to be consistent with the review model file;

[0060] Superimpose and calculate the model coordinate information after the level adjustment;

[0061] Export as review model file.

[0062] By utilizing macro-programmable language modules, the attribute information can be kept intact while the model file format is converted.

[0063] Specifically, in the fourth embodiment of the present invention, the model data file in the STEP format can be obtained from Solidworks, UG and Pro / E software, and converted into a model file in the RVM format.

[0064] In the fourth embodiment described above, in order to enable PDMS to support the import of STEP format files, the STEP format files need to be imported into PDMS through the MEI interface of PDMS, and then converted by converting each sube level into an equi level, and further by splitting the complete set of equipment into individual components. For example, the complete set of equipment is split into individual components such as pipelines, equipment, and instruments. After completing the above operations, the STEP format file is proofread and adjusted in direction and position within PDMS to convert the STEP format model data into an RVM format file, which is then received by PDMS.

[0065] Step A1-3-2, determining whether the file type of the model data file is an STL or MAC file type in the preset convertible file type, and when the determination result is yes, importing the model data file into AVEVA E3D, and exporting an RVM file;

[0066] Specifically, in the fifth embodiment of the present invention, the STL format model data file can be obtained from the 3DS MAX software, that is, the STL format file is exported in the form of ascii encoding, and then imported into AVEVA E3D, and the corresponding MAC format file is generated under the macro file path, and then the MAC file is imported into the commond window of E3D or PDMS, and then the following operations are performed: on the one hand, the model is repositioned by moving and assigned absolute coordinate values; on the other hand, the bit number of each factory object is defined in E3D or PDMS, and the subordinate relationship is defined, and the perfected model data is exported as an RVM file.

[0067] In addition, in the fifth embodiment, the model data file converted into the STL format has the advantages of better visual effect and suitable file size, and no data is lost. Therefore, between STL and STEP files, the STL format file is usually selected as the model data file.

[0068] Step A1-3-3, determine whether the file type of the model data file is the NWC or NWD file type in the preset convertible file type. When the judgment result is yes, convert the model data file into IFC format, import it into AVEVA E3D, and export the RVM file.

[0069] In the sixth embodiment of the present invention, the model data file in NWC or NWD format can be obtained from Navisworks software, and the model data file in NWC or NWD format is converted into the RVM format file in the following manner.

[0070] In this embodiment, the model data files in the above two formats are imported into Navisworks through the IFC format conversion plug-in (Codemill IFC Exporter), and then the model data files are converted into IFC format files. Since there is no corresponding attribute information in the IFC format file at this time, the IFC format file needs to be imported into E3D again, and finally the RVM file that can be received by the AVEVA AIM platform is exported, and the corresponding attribute information is extracted.

[0071] By converting the model data files in the above-mentioned different types of formats and obtaining the model data files that can be received by the AVEVA AIM platform after conversion, preliminary preparations can be made for subsequent integration work and complete digital delivery data can be provided.

[0072] In addition, when the file type of the model data file is not included in the preset convertible file type, that is, it does not belong to the type of the model data file shown above, in an embodiment of the present invention, the file information of the model data file will be recorded to provide the operator with statistical data related to the conversion progress so that the conversion can be performed through other means.

[0073] While executing step A1, that is, obtaining a model file that can be processed by the AVEVA AIM platform, step A2 is also executed to obtain the attribute information corresponding to the model file based on the model data file. Since the converted model files present a variety of different types, in the process of extracting attribute information, it is also necessary to adopt the corresponding methods to directly extract or indirectly obtain it through attribute assignment. For example, when the model attribute information corresponding to the model file can be extracted by the AVEVA AIM platform, the attribute information of the model is extracted through the corresponding Gateway of the AVEVA AIM platform, and an attribute file in XML format is obtained based on the attribute information; when the model attribute information corresponding to the model file cannot be extracted by the AVEVA AIM platform, the attribute information is indirectly obtained by attribute assignment. In the embodiment of the present invention, the attribute information mainly includes the model's bit number, category, subordinate relationship, and design parameters, but is not limited to the above parameters, and other parameter types will not be further described.

[0074] In step A2, based on the model data file, the attribute information corresponding to the model file is obtained, which specifically includes the following steps:

[0075] Step A2-1, determining whether the model data file contains attribute information that can be extracted by the AVEVA AIM platform;

[0076] Step A2-2, when the judgment result is yes, extract the attribute information; in this step, the process of extracting the attribute information will be introduced based on different model data files. For example:

[0077] In the above-mentioned first embodiment of the present invention, the model data file is a model file in RVM format, and the model data file contains attribute information corresponding to the model file in RVM format and can be extracted by the AVEVA AIM platform. When extracting the attribute information, the hierarchical structure and bit number coding of the project object decomposition structure in PDMS are standardized to ensure that after the RVM file is input into the AVEVA AIM platform, the bit number coding contained therein can be extracted by the AVEVA AIM platform, and the corresponding attribute information is obtained through the configured Gateway file, and the attribute file in XML format that can be directly entered into the AVEVA AIM platform is exported.

[0078] In the fourth embodiment of the present invention, on the basis of obtaining the model file, that is, on the basis of converting the model data file in the STEP format into the model file in the RVM format, the conversion process is performed to form a configuration (config) file to form a bit number information list and establish a subordinate relationship between factory objects. This process can obtain the attribute information corresponding to the RVM format model file without attribute assignment, and export the attribute file in the XML format that can directly enter the AVEVA AIM platform.

[0079] In the fifth embodiment of the present invention, while converting the STL format model data file into a model file that can be received by the AVEVA AIM platform, the attribute information is extracted through Gateway processing and a property file in XML format is formed.

[0080] In the sixth embodiment of the present invention, since Navisworks is not a modeling software, after the imported NWD and NWC format model data files are exported in IFC format, there is no corresponding position number information in the IFC file and the attribute information cannot be extracted. Instead, the IFC needs to be imported into E3D again, and the attribute object identifier is added to the file in the IFC format, and the attribute mapping group file in the Gateway interface is configured to obtain the attribute information that can be imported into the platform and form an XML file.

[0081] Step A2-3: when the judgment result is no, the attribute information is obtained by attribute assignment.

[0082] In step A2-3, different model data files are judged respectively to obtain corresponding attribute files, which specifically includes the following steps:

[0083] Step A2-3-1, when the model data file is in the IFC format, the attribute information is obtained by adding an attribute object identifier in the IFC format file and configuring the attribute mapping group file in the three-dimensional data processing interface.

[0084] Specifically, in the second embodiment of the present invention, when the model data file is an IFC format file, since Revit modeling is a participant, it is exported as an IFC format model file, and further by adding an attribute object identifier in the IFC format model file, the attribute mapping group file in the three-dimensional data processing interface is configured, thereby obtaining the attribute information, and forming an XML format attribute file, so that the AVEVA AIM platform can establish an association relationship between the model and the attribute. In the actual process of obtaining the attribute information, the bit number information corresponding to the model is uniformly filled in the "ObjectID" column, extracted by Gateway through parameter assignment, and the delivery platform establishes an association relationship between the bit number and the relevant data. The equipment class can select the equipment and define the bit number in the "Object ID" column of the property box; the civil engineering content that needs to define the bit number → create a group → confirm → select the group → define the bit number in the "Object ID" column of the property box.

[0085] A2-3-2, when the model data file is in DWG format, the attribute information is obtained by configuring the attribute mapping file in the three-dimensional data processing interface.

[0086] When the model data file is a file in DWG format, the attribute information is obtained by configuring the attribute mapping file in the three-dimensional data processing interface (Gateway) and forming an attribute file in XML format.

[0087] Specifically, in the third embodiment of the present invention, the three-dimensional data in DWG format is usually exported by CADWorx and processed by GCT (Gateway Configuration Tool) of the NET platform, wherein the bit number information contained in CADWorx needs to define the block name as the corresponding bit number name, and extract the attribute information of the corresponding block content by configuring the mappingfiles file in GCT, and finally form an attribute file in XML format after processing by Gateway.

[0088] By obtaining the attribute file in XML format through attribute assignment, the association between attribute information and model data can be obtained, the integrity of the model data can be guaranteed, and the requirements of digital delivery can be met.

[0089] Step S13: extracting a property file that can be processed by the AVEVA AIM platform based on the property information. Since the property file is directly associated with the property information, after obtaining the property information, the property file in XML format can be obtained. For the process of obtaining the property file, please refer to the above description of obtaining the property information, which will not be further described here.

[0090] Step S14: inputting the model file and the property file into the AVEVA AIM platform, specifically including: storing the model file and the property file in a database; displaying the model file and the property file in a display window of the AVEVA AIM platform. In this embodiment, the database includes SQL serve, oracle, datebase, MySQL, but is not limited thereto.

[0091] In order to further understand the entire process of the design concept and model data processing method of the present invention, refer to Figure 2 The flowchart shown in FIG. 1 is used to explain the operation of the STEP or STP file type in the fourth embodiment:

[0092] Figure 2 It is a flowchart of a model data processing method for AVEVA AIM platform according to a fourth embodiment of the present invention.

[0093] Step S21, in the digital delivery project, many participants provide different data for 3D modeling software, obtain model data files, and store these different types of model data files in the waiting area;

[0094] Step S22, then judging the above different types of data to determine whether they can be directly received by the AVEVA AIM platform; for example, judging whether the file type of the model data file is included in the preset file type to determine whether it can be directly received by the AVEVA AIM platform;

[0095] Step S23, when the judgment result is yes, automatically call the processing interface of the AVEVA AIM platform to process and display;

[0096] Step S24, when the judgment result is no, conversion is performed based on the model data file, that is, it is determined in what manner the model data file is converted. Specifically, when the file type of the model data file is included in the preset convertible file type, it is verified that the file type of the current model data file can be converted, that is, the file type of the current model data file can be converted into a file type that can be received by the AVEVA AIM platform. At this time, the current model data file is converted into a model file, and the model file is stored in the intermediate data folder;

[0097] For example, the current model data file is a STEP or STP file;

[0098] Step S25, importing the STEP or STP file into PDMS through the MEI interface of PDMS, at this time, calling the interface processing of the AVEVA AIM platform;

[0099] Step S26, then, each sube level is converted to an equi level by calling a plug-in, at which time, the following steps are performed simultaneously or sequentially to obtain an RVM format file and its corresponding attribute file; wherein,

[0100] Step S27, obtaining a model file in *.RVM format, that is, converting the model data in STEP format into a file in RVM format;

[0101] Step S28, storing the converted RVM format file in the result area;

[0102] Step S29, an operation of obtaining a corresponding attribute file, obtaining corresponding attribute information based on the model file, and converting the attribute information into a configuration file by calling a plug-in;

[0103] Step S30, exporting a property file in XML format;

[0104] Step S31, storing the XML formatted attribute file in the result area;

[0105] Step S32, after completing the above operations of obtaining the RVM format file and the corresponding attribute file, the converted RVM format file and the corresponding XML format attribute file are processed and displayed together through the processing interface of the AVEVA AIM platform.

[0106] At this point, the operation of processing files according to the technical solution of the present invention is completed.

[0107] On the other hand, the embodiment of the present invention further provides a data processing system 100, see Figure 3 , used for AVEVA AIM platform, including: an acquisition module 101, used to acquire a model data file; a conversion module 102, used to acquire a model file that can be processed by the AVEVA AIM platform based on the model data file, and to acquire corresponding attribute information; an extraction module 103, used to extract an attribute file that can be processed by the AVEVA AIM platform based on the attribute information; and a delivery module 104, used to input the model file and the attribute file into the AVEVA AIM platform.

[0108] Furthermore, although illustrative embodiments are described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., combinations of schemes across various embodiments), adjustments, or variations based on the present invention. The elements in the claims are to be interpreted broadly based on the language used in the claims and are not limited to the examples described in this specification or during the continuation of this application. Furthermore, the steps of the invented method may be modified in any way, including by reordering steps or inserting or deleting steps. Therefore, it is intended that the description be viewed merely as an example, with the true scope being indicated by the following claims and their full range of equivalents.

[0109] The above description is intended to be illustrative and not restrictive. For example, the above examples (or one or more aspects thereof) can be used in combination with each other. After reading the above description, other embodiments may be used by a person of ordinary skill in the art, for example. Moreover, in the above detailed description, various features may be combined together to simplify the present invention. This should not be interpreted as an inventive feature that is not intended to be protected being essential to any claim. Therefore, the following claims are incorporated into the specific implementation as examples or embodiments, wherein each claim itself is a separate embodiment, and it is expected that these embodiments may be combined with each other in various combinations or permutations. The scope of the present invention should be determined with reference to the attached claims and the full scope of equivalents given by these claims.

Claims

1. A model data processing method for AVEVA AIM platform, characterized in that: The steps include: Get the model data file; Based on the model data file, obtaining a model file that can be processed by the AVEVA AIM platform and obtaining corresponding attribute information; Based on the attribute information, extracting attribute files that can be processed by the AVEVA AIM platform; The model file and the property file are input into the AVEVA AIM platform.

2. The method according to claim 1, characterized in that The step of obtaining a model file that can be processed by the AVEVA AIM platform based on the model data file includes: Determine whether the file type of the model data file is included in the preset file type; When the judgment result is yes, the interface processing of AVEVA AIM platform is called; When the judgment result is no, When the file type of the model data file is included in the preset convertible file types, The model data file is converted into the model file; the model file is stored in an intermediate data folder, and the interface of the AVEVA AIM platform is called for processing.

3. The method according to claim 2, characterized in that The preset file types include: review model file type, industrial foundation file type and engineering design file type; the preset convertible file types include: STEP or STP file type, STL or MAC file type, NWC or NWD file type.

4. The method according to claim 2, characterized in that: When the judgment result is no, when the file type of the model data file is included in the preset convertible file type, converting the model data file into the model file comprises the following steps: Determine whether the file type of the model data file is a STEP or STP file type in the preset convertible file type, and when the determination result is yes, call a special category model import interface to import the model data file into a plant three-dimensional layout design management system, and export a review model file; Determine whether the file type of the model data file is the STL or MAC file type in the preset convertible file type. If the determination result is yes, import the model data file into Jianwei 3D modeling software, and export the review model file; Determine whether the file type of the model data file is the NWC or NWD file type in the preset convertible file type. When the judgment result is yes, convert the model data file into IFC format, import it into Jianwei 3D modeling software, and export the review model file.

5. The method according to claim 4, characterized in that The calling of the special category model import interface, importing the model data file into the plant three-dimensional layout design management system, and exporting the review model file includes: Calling macro-programmable language modules; Adjusting the attribute level information of the model data file to be consistent with the review model file; Superimpose and calculate the model coordinate information after the level adjustment; Export as review model file.

6. The method according to claim 2, characterized in that When the file type of the model data file is not included in the preset convertible file types, the file information of the model data file is recorded.

7. The method according to claim 1, characterized in that The acquiring corresponding attribute information based on the model data file includes: Determining whether the model data file contains attribute information that can be extracted by the AVEVA AIM platform; When the judgment result is yes, extracting the attribute information; When the judgment result is no, the attribute information is obtained by attribute assignment.

8. The method according to claim 7, characterized in that The acquiring of the attribute information by attribute assignment includes: When the model data file is in an IFC format, the attribute information is obtained by adding an attribute object identifier in the IFC format file and configuring an attribute mapping group file in a three-dimensional data processing interface; When the model data file is in the DWG format, the attribute information is obtained by configuring the attribute mapping file in the three-dimensional data processing interface.

9. The method according to claim 1, characterized in that: The step of inputting the model file and the property file into the AVEVA AIM platform comprises the following steps: Storing the model file and the attribute file in a database; The model file and the property file are displayed in the display window of the AVEVA AIM platform.

10. A data processing system for AVEVA AIM platform, characterized in that: include: An acquisition module is used to obtain model data files; A conversion module, used for obtaining a model file that can be processed by the AVEVA AIM platform based on the model data file, and obtaining corresponding attribute information; An extraction module, used for extracting a property file that can be processed by the AVEVA AIM platform based on the property information; A delivery module is used to input the model file and the property file into the AVEVA AIM platform.

Images