Integrated multi-platform design resource engineering bim invocation management method and system

Abstract

A method and system for managing and calling BIM design resources across multiple platforms, relating to the field of BIM technology, includes: configuring Revit platform plugin information in a document and converting the document into a first XML file; downloading resources based on user permissions; matching the downloaded resource information with the first XML file and retrieving the corresponding DLL file to load plugin functionality; saving the function selection information as an INI file, and loading plugin function buttons based on the INI file when Revit starts; configuring Bentley platform plugin information in a second XML file, and copying the target resources to the Bentley directory based on the second XML file; and loading plugin function buttons based on the Bentley directory after startup. This invention provides a method for software integration management and calling across multiple basic platforms under different operating environments, solving the problem of difficulty in switching and unifying resources during the design process.

Description

Technical Field

[0001] This invention belongs to the field of BIM technology, specifically relating to a method and system for integrating multi-platform design resource engineering BIM call management. Background Technology

[0002] Currently, the field of BIM design for urban rail transit suffers from significant software platform fragmentation. Railway lines (sections) are linear projects, while stations (sections) are point-like projects. Station and section projects employ completely different design systems—station and section projects primarily rely on the Autodesk Revit platform, focusing on 3D modeling and collaborative design of station buildings, underground structures, and electromechanical pipelines; while section projects generally use the Bentley MicroStation platform, primarily addressing the parametric collaboration needs of linear projects such as track lines, bridges, and tunnels. The two are installed relatively independently and lack interoperability. However, station and section projects often require simultaneous design. When different designers work on the same project, it's difficult to unify the design environment and software version. This necessitates extensive manual updates to design resources, design environments, and design software, hindering continuity and reducing work efficiency. Summary of the Invention

[0003] The purpose of this invention is to provide a method and system for integrating multi-platform design resource engineering BIM access and management, in order to improve the above-mentioned problems. To achieve the above objective, the technical solution adopted by this invention is as follows:

[0004] Firstly, this application provides a method for integrating multi-platform design resource engineering BIM access and management, including:

[0005] Configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes DLL method names.

[0006] Download resources according to user permissions and obtain information on downloaded resources;

[0007] By matching the downloaded resource information with the first XML file, the corresponding DLL file in the downloaded resources is retrieved to load the plugin functionality;

[0008] Get the function selection information, save the function selection information as an INI file, search for the INI file when Revit starts, and load the plug-in function buttons according to the INI file;

[0009] Configure the plugin information for the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file;

[0010] After Bentley starts, it loads the plugin function buttons according to the Bentley directory.

[0011] Secondly, this application also provides a software integration and invocation system based on different basic platforms, including:

[0012] The first module is used to configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes DLL method names.

[0013] The second module is used to download resources based on user permissions and obtain information on downloaded resources.

[0014] The third module is used to match the downloaded resource information with the first XML file, retrieve the corresponding DLL file in the downloaded resources, and load the plugin function.

[0015] The fourth module is used to obtain function selection information, save the function selection information as an INI file, search for the INI file when Revit starts, and load the plug-in function buttons according to the INI file;

[0016] The fifth module is used to configure the plugin information of the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file;

[0017] The sixth module is used to load plugin function buttons based on the Bentley directory after Bentley starts.

[0018] The beneficial effects of this invention are as follows:

[0019] This invention establishes a connection between the method names and entry class configuration files of different plugins and the corresponding ".dll" files of the software packages. The launching program displays different software functions according to the integration order in the configuration files and correctly invokes the functions using the function method names and entry class methods in the configuration files. This solves the problem that different operators previously needed to install multiple software plugins on a basic platform (Revit or Bentley) to use functions in different professional fields. It also enables the integration of consistent and professionally relevant functions through configuration, greatly reducing the computer load caused by installing multiple different software programs and improving the ease of use for different operators.

[0020] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing embodiments of the invention. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This application provides a flowchart of a method for integrating multi-platform design resource engineering BIM access and management in an embodiment.

[0023] Figure 2 This is a structural diagram of a software integration and calling device based on different basic platforms, as shown in the embodiments of this application.

[0024] Symbol explanation: 800 - Software integration and calling device based on different basic platforms; 801 - Processor; 802 - Memory; 803 - Multimedia component; 804 - I / O interface; 805 - Communication component. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0026] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0027] Currently, when designing urban rail transit projects, specifically station and section engineering, designers need to choose products from different software vendors. For station and section engineering, the mainstream design product is Autodesk's Revit, primarily focused on Building Information Modeling (BIM) for architectural design, structural engineering, and MEP (Mechanical, Electrical, and Plumbing) systems. For section engineering, it's Bentley's MicroStation, primarily focused on broader infrastructure projects beyond architecture, including transportation, utilities, and civil engineering. However, the two are installed relatively independently and lack interoperability. When different designers work on the same project, it's difficult to unify the design environment and software version. This necessitates extensive manual updates to design resources, environments, and software, hindering continuity and reducing work efficiency.

[0028] Example 1:

[0029] This embodiment provides a method for managing the BIM call of integrated multi-platform design resources, including: S100, S200, S300, S400, S500, and S600;

[0030] S100. Configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes the DLL method name, as well as the function entry class name, function prompt, function icon name, and the .dll file of the corresponding software package. As an example, the plugin information can be configured in an Excel spreadsheet, so that non-developers can directly manage the tool.

[0031] S200: Download resources according to user permissions and obtain information on downloaded resources;

[0032] Based on the design project requirements, designers are categorized into roles and given different permissions. These roles include, but are not limited to, group approval, institute review, verification, and design. Their permissions include, but are not limited to, viewing, uploading, and downloading. Based on their role information, designers have different management and operation permissions for toolsets and resources, and can retrospectively update and revisit tool and resource versions within the BIM project design cycle.

[0033] The required plugins differ for different projects and design tasks. Therefore, this application uses the following method to determine the loadable plugins for each person.

[0034] Obtain personnel identification information, and determine job roles, project bindings, and current design task nodes based on personnel identification information;

[0035] Determine personnel permissions based on job roles;

[0036] The system retrieves project task database data based on the bound project, filters the user's current design tasks, and determines the design task nodes. Design task information includes task type, design stage, professional direction, required functional modules, delivery deadline, etc.

[0037] For single-user multi-tasking scenarios, the main task can be automatically located based on task priority and most recent operation time, and auxiliary tasks can be marked as pending. If no related tasks are found, only basic general plugins are loaded, and the user is prompted to bind project tasks.

[0038] Based on a pre-established task-plugin mapping table, the system searches for matching plugins according to the user's current design task nodes and builds a basic plugin list.

[0039] The list of basic plugins is filtered based on user permissions to obtain a list of plugins to be downloaded.

[0040] Since the design results from different personnel need to be integrated and unified in the end, and it is necessary to ensure that the various versions of the results are compatible with each other, this embodiment adopts the following method for control:

[0041] Obtain the unified deliverables baseline version information corresponding to the project based on the bound project. The unified deliverables baseline version information is the fixed version of the final delivery of the project, and all members must align with it.

[0042] Based on the user's current task node, match the corresponding target plugin, and find the compatible version number based on the unified results baseline version information;

[0043] The system compares the local plugin version number with the compatible version number and updates the local plugin based on the comparison result. If the local version is a compatible version, no action is required, and the plugin can be loaded and used directly. If the local version and the compatible version are inconsistent, the local version will be automatically uninstalled, and the compatible version will be downloaded and deployed, while retaining user configuration and selection records. If there is no corresponding plugin locally, the compatible version will be downloaded and deployed directly.

[0044] Once the matching is complete, the current plugin version is locked, preventing users from manually upgrading or downgrading at will. Each time the client is launched, it automatically checks whether the plugin version matches the unified deliverables baseline version information. If they do not match, the matching process is retried. Each user's plugin version information is recorded to facilitate administrator monitoring of version consistency across all users and ensure the uniformity of the final deliverables.

[0045] S300: By matching the downloaded resource information with the first XML file, the corresponding DLL file in the downloaded resources is retrieved to load the plugin function;

[0046] S400: Obtain function selection information, save the function selection information as an ini file, search for the ini file when Revit starts, and load the plug-in function buttons according to the ini file;

[0047] After the manual account interface selects the function, the selected information is automatically recorded as an ".ini" file in the ledger program package directory. Through the OnStartup method under the Autodesk.Revit.UI.IExternalApplication interface, the ledger tab selection record inini file in the program package directory is automatically searched, thereby triggering the basic platform to load all function buttons under the corresponding selected tab.

[0048] S500: Configure the plugin information of the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file;

[0049] To enable the automatic loading of different plugins in Bentley OpenRail Designer (ORD) via programmatic loading, this solution adopts a configuration file-driven approach.

[0050] The target resources include a temporary storage directory, data model definition files (schema-related files), plugin DLL files, and configuration variable files. The method includes:

[0051] Copy the temporary storage directory (CECBIM), data model definition file, and plugin DLL files to the corresponding Bentley installation directory;

[0052] Copy the configuration variable file to the Bentley installation directory, and modify the Bentley resource loading file to point the workspace to the client path;

[0053] Copy the configuration file (e.g., .cfg) to the OpenRailChina\config\appl directory. Modify the ORD resource loading file msdir.cfg to point the workspace to the client path. After ORD starts, it will automatically load the plugin function buttons to the corresponding toolbars or menus according to the configuration.

[0054] After the S600 and Bentley are started, the plugin function button will be loaded according to the Bentley directory.

[0055] The program reads the configuration at startup through the extension interface provided by Bentley (such as IExternalApplication or the corresponding Add-In mechanism), dynamically loads the .dll and instantiates the entry class to complete the function registration and interface integration.

[0056] During the shutdown and cleanup process, the plugin client monitors Bentley shutdown events;

[0057] Obtain the Bentley shutdown command, and delete the temporary storage directory, data model definition file, and configuration variable file according to the Bentley shutdown command;

[0058] Restore the Bentley resource loading files to their initial configuration according to the Bentley shutdown command.

[0059] After the cleanup is complete, close the client. The purpose of this cleanup is to prevent residual files from affecting other projects or versions, and to ensure a clean Bentley environment for easy redeployment on the next startup.

[0060] Since various switching is required according to design needs, users usually have to wait for the download to complete when switching workspaces or opening different versions of files, which affects the user experience. This application adopts the Cuckoo Search algorithm to preload resources and reduce waiting time.

[0061] Obtain the user's historical operation sequence information and generate an initial solution based on the historical operation sequence information; historical operations include, for example, the directory where the opened DGN file is located and the name of the recently opened Revit project;

[0062] N virtual nests are generated randomly in advance, each nest representing a potential user operation state vector. Based on the user's previous operation behavior, a real operation vector is generated.

[0063] Then, the similarity between the real operation vector and the virtual nest is calculated, and n nests with high similarity are selected as the starting point of the search, i.e., the initial solution.

[0064] Based on the initial solution, new candidate solutions are generated through Levy flight, resulting in a list of resources to be prefetched;

[0065] Check the local cache of the list of resources to be prefetched. If there are any missing resources on the local cache, download the missing resource packages to the resource cache area.

[0066] The hit rate is calculated based on the resources actually invoked by the user and the prefetched resources. The step size and discovery probability parameters of the Levi flight are then optimized in reverse based on the hit rate. If the hit rate remains low, the search step size is reduced so that the Levi flight focuses on fine-grained searches near the current high-quality nests (the context of high-frequency user operations).

[0067] ORD scans directories to load DLLs using the .NET assembly resolution mechanism. When the directory structure is complex or the network mapping path has high latency, the scanning speed is slow, resulting in slow ORD startup. This method uses a tabu search algorithm to optimize the resolution path:

[0068] A path loading performance table is constructed by recording the response time, file depth, and network latency of the corresponding directory each time a plugin is loaded;

[0069] Based on the path loading performance table, find paths that have historically loaded slowly or failed, mark them as taboo objects, and form a taboo table;

[0070] When Bentley starts, it searches for paths outside the taboo list and adjusts the path order according to the records in the path loading performance table. The .NET loader performs standard probing according to the adjusted path order, loads a valid path immediately after finding it, and terminates the search.

[0071] For the program's backend management operations, administrators can log in using their account and password or mobile phone number. After logging in, they can add, modify, and delete roles and assign permissions in the role management module, achieving unified management of user roles. A log management module is built, which can filter, view, export, and delete operation logs and login logs, clearly tracing system operation records. The core of plugin management is the management of toolkit packages and client program packages. Administrators can add new zip format toolkit packages, fill in information such as name, version, and base platform, and upload them. They can also update and edit existing toolkit packages. At the same time, they can view package version details by version number and keywords through historical version management. They can also upload client program packages based on "client software" in plugin management. Ordinary users can directly download client program packages without account permissions. The whole system is deployed on a cloud server, realizing centralized uploading, updating, version management, and unified management of permissions and logs for software plugins from multiple vendors.

[0072] Example 2:

[0073] A software integration and invocation system based on different basic platforms includes:

[0074] The first module is used to configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes DLL method names.

[0075] The second module is used to download resources based on user permissions and obtain information on downloaded resources.

[0076] The third module is used to match the downloaded resource information with the first XML file, retrieve the corresponding DLL file in the downloaded resources, and load the plugin function.

[0077] The fourth module is used to obtain function selection information, save the function selection information as an INI file, search for the INI file when Revit starts, and load the plug-in function buttons according to the INI file;

[0078] The fifth module is used to configure the plugin information of the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file;

[0079] The sixth module is used to load plugin function buttons based on the Bentley directory after Bentley starts.

[0080] As an optional implementation, the system further includes:

[0081] The seventh module is used to obtain personnel identity information, and based on this information, determine job roles, bind projects, and current design task nodes.

[0082] The eighth module is used to determine personnel permissions based on job roles;

[0083] The ninth module is used to retrieve project task library data based on the bound project, filter the user's current design tasks, and determine the design task nodes;

[0084] The tenth module is used to find matching plugins based on the user's current design task nodes, based on a pre-established task-plugin mapping table, and to build a basic plugin list.

[0085] The eleventh module is used to filter the list of basic plugins based on user permissions to obtain a list of plugins to be downloaded.

[0086] As an optional implementation, the system further includes:

[0087] The twelfth module is used to obtain the unified deliverables baseline version information corresponding to the project based on the bound project;

[0088] The thirteenth module is used to match the corresponding target plugin based on the user's current task node and to find the compatible version number based on the unified results baseline version information.

[0089] The fourteenth module is used to compare the local plugin version number with the compatible version number and update the local plugin based on the comparison result.

[0090] As an optional implementation, the target resources include a temporary storage directory, a data model definition file, a plugin DLL file, and a configuration variable file; the system includes:

[0091] The fifteenth module is used to copy the temporary storage directory, data model definition file, and plugin DLL files to the corresponding Bentley installation directory;

[0092] The sixteenth module is used to copy the configuration variable file to the Bentley installation directory and to point the workspace to the client path by modifying the Bentley resource loading file;

[0093] Module 17 is used to obtain the Bentley shutdown command and delete the temporary storage directory, data model definition file and configuration variable file according to the Bentley shutdown command;

[0094] The eighteenth module is used to restore the Bentley resource loading files to their initial configuration based on the Bentley shutdown command.

[0095] Example 3:

[0096] Corresponding to the above method embodiments, this embodiment also provides a software integration and invocation device based on different basic platforms. The software integration and invocation device based on different basic platforms described below can be referred to in correspondence with the integrated multi-platform design resource engineering BIM invocation and management method described above.

[0097] Figure 2 This is a block diagram illustrating a software integration and invocation device 800 based on different underlying platforms, according to an exemplary embodiment. For example... Figure 2 As shown, the software integration and invocation device 800 based on different basic platforms includes a processor 801 and a memory 802. The software integration and invocation device 800 may also include one or more of the following: a multimedia component 803, an input / output (I / O) interface 804, and a communication component 805. The processor 801 controls the overall operation of the software integration and invocation device 800 to complete all or part of the steps in the aforementioned integrated multi-platform design resource engineering BIM invocation management method. The memory 802 stores various types of data to support the operation of the software integration and invocation device 800. This data may include, for example, commands for any application or method operating on the software integration and invocation device 800, and application-related data such as contact data, sent and received messages, images, audio, video, etc. The memory 802 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0098] Multimedia component 803 may include a screen and an audio component. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals.

[0099] The received audio signal can be further stored in memory 802 or transmitted via communication component 805. The audio component also includes at least one speaker for outputting audio signals. I / O interface 804 provides an interface between processor 801 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons can be virtual or physical. Communication component 805 is used for wired or wireless communication between the software integration calling device 800 based on different platforms and other devices. Wireless communication includes Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination thereof; therefore, the corresponding communication component 805 may include a Wi-Fi module, a Bluetooth module, or an NFC module.

[0100] Example 4:

[0101] Corresponding to the above embodiment of the integrated multi-platform design resource engineering BIM call management method, this embodiment also provides a readable storage medium. The readable storage medium described below can be referred to in correspondence with the integrated multi-platform design resource engineering BIM call management method described above.

[0102] A readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described embodiment of the integrated multi-platform design resource engineering BIM call management method.

[0103] Specifically, the readable storage medium can be a USB flash drive, external hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or any other readable storage medium capable of storing program code.

[0104] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0105] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for integrating multi-platform design resource engineering BIM retrieval and management, characterized in that, include: Configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes DLL method names. Download resources according to user permissions and obtain information on downloaded resources; By matching the downloaded resource information with the first XML file, the corresponding DLL file in the downloaded resources is retrieved to load the plugin functionality; Get the function selection information, save the function selection information as an INI file, search for the INI file when Revit starts, and load the plug-in function buttons according to the INI file; Configure the plugin information for the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file; After Bentley starts, it loads the plugin function buttons according to the Bentley directory.

2. The integrated multi-platform design resource engineering BIM call management method according to claim 1, characterized in that, The method includes: Obtain personnel identification information, and determine job roles, project bindings, and current design task nodes based on personnel identification information; Determine personnel permissions based on job roles; Retrieve project task library data based on the bound project, filter the user's current design tasks and determine the design task nodes; Based on a pre-established task-plugin mapping table, the system searches for matching plugins according to the user's current design task nodes and builds a basic plugin list. The list of basic plugins is filtered based on user permissions to obtain a list of plugins to be downloaded.

3. The integrated multi-platform design resource engineering BIM call management method according to claim 2, characterized in that, The method includes: Obtain the unified deliverables baseline version information corresponding to the project based on the bound project; Based on the user's current task node, match the corresponding target plugin, and find the compatible version number based on the unified results baseline version information; The local plugin version number is compared with the compatible version number, and the local plugin is updated based on the comparison result.

4. The integrated multi-platform design resource engineering BIM call management method according to claim 1, characterized in that, The target resources include a temporary storage directory, a data model definition file, a plugin DLL file, and a configuration variable file. The method includes: Copy the temporary storage directory, data model definition file, and plugin DLL files to the corresponding Bentley installation directory; Copy the configuration variable file to the Bentley installation directory, and modify the Bentley resource loading file to point the workspace to the client path; Obtain the Bentley shutdown command, and delete the temporary storage directory, data model definition file, and configuration variable file according to the Bentley shutdown command; Restore the Bentley resource loading files to their initial configuration according to the Bentley shutdown command.

5. The integrated multi-platform design resource engineering BIM call management method according to claim 1, characterized in that, The method includes: Obtain the user's historical operation sequence information and generate an initial solution based on the historical operation sequence information; Based on the initial solution, new candidate solutions are generated through Levy flight, resulting in a list of resources to be prefetched; Check the local cache of the list of resources to be prefetched. If there are any missing resources on the local cache, download the missing resource packages to the resource cache area. The hit rate is calculated based on the resources actually called by the user and the prefetched resources. The step size parameters and discovery probability parameters of Levi's flight are then optimized in reverse based on the hit rate.

6. The integrated multi-platform design resource engineering BIM call management method according to claim 1, characterized in that, The method includes: A path loading performance table is constructed by recording the response time, file depth, and network latency of the corresponding directory each time a plugin is loaded; Based on the path loading performance table, find paths that have historically loaded slowly or failed, mark them as taboo objects, and form a taboo table; When Bentley starts, it searches for paths outside the taboo list and adjusts the path order according to the records in the path loading performance table. The .NET loader performs standard probing according to the adjusted path order, loads a valid path immediately after finding it, and terminates the search.

7. A software integration and invocation system based on different basic platforms, characterized in that, include: The first module is used to configure the Revit platform plugin information in the document and convert the document into a first XML file. The plugin information includes DLL method names. The second module is used to download resources based on user permissions and obtain information on downloaded resources. The third module is used to match the downloaded resource information with the first XML file, retrieve the corresponding DLL file in the downloaded resources, and load the plugin function. The fourth module is used to obtain function selection information, save the function selection information as an INI file, search for the INI file when Revit starts, and load the plug-in function buttons according to the INI file; The fifth module is used to configure the plugin information of the Bentley platform in the second XML file, and copy the target resources to the Bentley directory according to the second XML file; The sixth module is used to load plugin function buttons based on the Bentley directory after Bentley starts.

8. The software integration and invocation system based on different basic platforms according to claim 7, characterized in that, Also includes: The seventh module is used to obtain personnel identity information, and based on this information, determine job roles, bind projects, and current design task nodes. The eighth module is used to determine personnel permissions based on job roles; The ninth module is used to retrieve project task library data based on the bound project, filter the user's current design tasks, and determine the design task nodes; The tenth module is used to find matching plugins based on the user's current design task nodes, based on a pre-established task-plugin mapping table, and to build a basic plugin list. The eleventh module is used to filter the list of basic plugins based on user permissions to obtain a list of plugins to be downloaded.

9. The software integration and invocation system based on different basic platforms according to claim 8, characterized in that, Also includes: The twelfth module is used to obtain the unified deliverables baseline version information corresponding to the project based on the bound project; The thirteenth module is used to match the corresponding target plugin based on the user's current task node and to find the compatible version number based on the unified results baseline version information. The fourteenth module is used to compare the local plugin version number with the compatible version number and update the local plugin based on the comparison result.

10. The software integration and invocation system based on different basic platforms according to claim 7, characterized in that, The target resources include a temporary storage directory, data model definition files, plugin DLL files, and configuration variable files; the system includes: The fifteenth module is used to copy the temporary storage directory, data model definition file, and plugin DLL files to the corresponding Bentley installation directory; The sixteenth module is used to copy the configuration variable file to the Bentley installation directory and to point the workspace to the client path by modifying the Bentley resource loading file; Module 17 is used to obtain the Bentley shutdown command and delete the temporary storage directory, data model definition file and configuration variable file according to the Bentley shutdown command; The eighteenth module is used to restore the Bentley resource loading files to their initial configuration based on the Bentley shutdown command.

Images