A construction engineering management system based on government-enterprise interconnection and an application method thereof

Abstract

The application discloses a kind of based on the building engineering management system and application method of government-enterprise interconnection, the system includes: enterprise data acquisition end, supervision data acquisition end, supervision subsystem and enterprise management subsystem;Enterprise data acquisition end carries out the collection to the internal management data of participating enterprise, and the supervision data is sent to supervision data acquisition end;Supervision data acquisition end sends supervision data to supervision subsystem;Supervision subsystem receives and stores supervision data, and returns supervision data to enterprise management subsystem;Enterprise management subsystem receives supervision data, and according to the preset data analysis strategy, the supervision data is analyzed.Can realize supervision data sharing, avoid the management mode of single supervision to project, by integrating supervision data acquisition end, supervision subsystem and enterprise data acquisition end into a system, so as to avoid that technical personnel repeatedly switches different management work and carries out data repeated input, improve the convenience of use.

Description

Technical Field

[0001] This invention relates to the field of engineering management technology, specifically to a construction engineering management system and application method based on government-enterprise interconnection. Background Technology

[0002] With the basic establishment of a policy and industrial system for the coordinated development of intelligent construction and building industrialization, the levels of building industrialization, digitalization, and intelligence have significantly improved. A preliminary building industry internet platform has been established, and the industrial base, technical equipment, technological innovation capabilities, and building safety and quality levels have all been comprehensively enhanced. Labor productivity has increased significantly, energy and resource consumption and pollution emissions have decreased substantially, and environmental protection effects have been remarkable. Against this backdrop, various project integrated management systems and professional management systems have sprung up and been implemented in major projects, improving the management level of building engineering to a certain extent.

[0003] Nevertheless, because engineering construction involves numerous participants, including government construction administrative departments, construction units, general contractors, subcontractors, surveying and design units, supervision units, third-party quality testing units, and third-party construction safety monitoring units, and because many management tasks require collaboration among these parties, the same application scenario often requires the use of two or more application systems to meet the needs of all parties, creating a workload for on-site staff. Therefore, most existing engineering management systems, developed based on the management needs of a single unit, are insufficient for managing the progress, quality, and safety of the entire engineering construction lifecycle.

[0004] Even among similar companies, different management styles mean that software vendors typically develop engineering management systems through custom development. Even if the vendor modifies their standardized products, the lack of interoperability between participating units' systems leads to repetitive execution of many management processes within a single project, and the need to repeatedly input data and information into different units' systems. This results in a significant waste of human resources and software development costs.

[0005] Therefore, those skilled in the art urgently need to find a new technical solution to address the aforementioned problems. Summary of the Invention

[0006] To overcome the problems existing in related technologies, this invention discloses a construction engineering management system and application method based on government-enterprise interconnection.

[0007] According to a first aspect of the disclosed embodiments of the present invention, a construction project management system based on government-enterprise interconnection is provided. The system includes: an enterprise data acquisition terminal, a regulatory data acquisition terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data acquisition terminal is electrically connected to the enterprise management subsystem, the regulatory data acquisition terminal is electrically connected to the regulatory subsystem, and the enterprise management subsystem is electrically connected to the regulatory subsystem.

[0008] The enterprise data collection terminal is used to collect internal management data of participating enterprises and send non-regulatory data to the enterprise management subsystem;

[0009] The regulatory data collection terminal is used to collect regulatory data and then send the regulatory data to the regulatory subsystem.

[0010] The regulatory subsystem is used to receive the regulatory data, analyze the regulatory data according to the preset administrative supervisor data analysis strategy, process the regulatory responsibilities online, store the regulatory data, and return the stored regulatory data to the enterprise management subsystem.

[0011] The enterprise management subsystem is used to receive the non-regulatory data and the regulatory data returned by the regulatory subsystem, and to analyze the regulatory and non-regulatory data according to the preset enterprise management data analysis strategy, process enterprise management responsibilities online, and store the regulatory data.

[0012] Optionally, the enterprise data collection terminal and the regulatory data collection terminal use the same application platform and are deployed in the same application.

[0013] Optionally, the regulatory data sent from the regulatory data collection terminal to the regulatory subsystem includes: the enterprise code of the participating enterprise, the data type, data time, data packet ID, and data content of the regulatory data;

[0014] The regulatory subsystem includes a subscription management module, which is used to encrypt the data packets of the regulatory data according to the enterprise code and data type, so as to return the encrypted regulatory data to the enterprise management subsystem.

[0015] Optionally, when the enterprise management subsystem receives encrypted regulatory data, it decrypts the data packet using the corresponding private key to obtain the decrypted regulatory data.

[0016] Optionally, the regulatory subsystem includes: a regulatory data analysis module, a regulatory performance module, and a regulatory database;

[0017] The regulatory data analysis module is used to statistically analyze the regulatory data of different participating enterprises and to view in real time the image data and IoT device data acquired by the image acquisition device in each project.

[0018] The regulatory performance module is used to process regulatory responsibilities online, view and sign off on rectification information of engineering projects, and process the filing information of participating enterprises.

[0019] The regulatory database is used to store basic information about engineering projects, management data generated during the supervision process of the regulatory performance module, image data acquired by image acquisition devices, and data from Internet of Things devices.

[0020] Optionally, the enterprise management subsystem includes: an enterprise data analysis module, an enterprise management module, an enterprise database, an enterprise-level regulatory database, and an enterprise regulatory data analysis module;

[0021] The enterprise data analysis module is used to statistically analyze data from different departments and different types of business of participating enterprises, to view in real time the image data and IoT device data collected by the image acquisition devices installed by the enterprises themselves in the project, and to statistically analyze the data of different technical personnel and different projects.

[0022] The enterprise management module is used to process the supervisory responsibilities of participating enterprises online;

[0023] The enterprise database finally stores the process management data, image data, and IoT device data of the participating enterprises;

[0024] The enterprise-level regulatory database is used to store the regulatory data returned by the regulatory subsystem to the enterprise management subsystem;

[0025] The enterprise regulatory data analysis module is used to analyze the data in the enterprise-level regulatory database.

[0026] Optionally, the regulatory database and the enterprise-level regulatory database are connected via a standardized interface;

[0027] After obtaining the regulatory data, the regulatory database dynamically verifies the user's identity and, upon passing the dynamic verification, pushes the user-related data in the regulatory database to the enterprise-level regulatory database.

[0028] Optionally, the enterprise data collection terminal is a mobile application base, which includes external standard and internal data communication protocol interfaces.

[0029] Optionally, the regulatory data collection terminal is a mobile application base, which includes external standard and internal data communication protocol interfaces.

[0030] According to a second aspect of the disclosed embodiments of the present invention, a method for applying a government-enterprise interconnected construction project management system is provided. The system includes: an enterprise data acquisition terminal, a regulatory data acquisition terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data acquisition terminal is electrically connected to the enterprise management subsystem, the regulatory data acquisition terminal is electrically connected to the regulatory subsystem, and the enterprise management subsystem is electrically connected to the regulatory subsystem. The method includes:

[0031] The internal management data of participating enterprises is collected through the enterprise data collection terminal, and non-regulatory data is sent to the enterprise management subsystem.

[0032] After collecting regulatory data through the regulatory data collection terminal, the regulatory data is sent to the regulatory subsystem.

[0033] The system receives the regulatory data through the regulatory subsystem, analyzes the regulatory data according to the preset administrative data analysis strategy, processes the regulatory responsibilities online, and stores the regulatory data, and then returns the stored regulatory data to the enterprise management subsystem.

[0034] The enterprise management subsystem receives the non-regulatory data and the regulatory data returned by the regulatory subsystem, and analyzes the regulatory and non-regulatory data according to the preset enterprise management data analysis strategy, processes enterprise management responsibilities online, and stores the regulatory data.

[0035] Optionally, the regulatory data sent from the regulatory data collection terminal to the regulatory subsystem includes: the enterprise code of the participating enterprise, the data type, data time, data packet ID, and data content of the regulatory data. The method further includes:

[0036] The data packets of the regulatory data are encrypted according to the enterprise code and data type, and the encrypted regulatory data is returned to the enterprise management subsystem.

[0037] In summary, this invention discloses a construction project management system and application method based on government-enterprise interconnection. The system includes: an enterprise data collection terminal, a regulatory data collection terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data collection terminal collects internal management data from participating enterprises and sends non-regulatory data to the enterprise management subsystem. The regulatory data collection terminal collects regulatory data and sends it to the regulatory subsystem. The regulatory subsystem receives and stores the regulatory data and returns it to the enterprise management subsystem. The enterprise management subsystem receives the non-regulatory data and the regulatory data returned by the regulatory subsystem, and analyzes the regulatory and non-regulatory data according to a preset data analysis strategy.

[0038] This system enables the sharing of monitoring data and basic project information, allowing different project participants to analyze the data according to their own management characteristics. This avoids the traditional single-project management model of supervision. By sharing data with the management of the undertaking company, it helps each participant to play its primary management role and improves the efficiency of supervision. Integrating the monitoring data collection terminal and the enterprise data collection terminal adapted to enterprise management into a single mobile application avoids on-site technicians repeatedly switching between different management tasks and repetitive data input, thus improving ease of use.

[0039] Other features and advantages disclosed in this invention will be described in detail in the following detailed description section. Attached Figure Description

[0040] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings:

[0041] Figure 1 This is a schematic diagram illustrating the structure of a government-enterprise interconnected construction project management system according to an exemplary embodiment;

[0042] Figure 2 This is a schematic diagram of the underlying framework of the data acquisition terminal;

[0043] Figure 3 This is a flowchart illustrating the process by which the regulatory subsystem returns regulatory data to the enterprise management subsystem.

[0044] Figure 4 This is a flowchart illustrating an application method of a construction project management system based on government-enterprise interconnection, according to an exemplary embodiment. Detailed Implementation

[0045] The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the scope of the present disclosure.

[0046] Figure 1This is a schematic diagram illustrating the structure of a government-enterprise interconnected construction project management system according to an exemplary embodiment. The system includes: a supervision subsystem 10, an enterprise management subsystem 20, a supervision data acquisition terminal 30, and an enterprise data acquisition terminal 40. The enterprise data acquisition terminal 40 is electrically connected to the enterprise management subsystem 20, the supervision data acquisition terminal 30 is electrically connected to the supervision subsystem 10, and the enterprise management subsystem 20 is electrically connected to the supervision subsystem 10. The enterprise data acquisition terminal 40 is used to collect internal management data from participating enterprises and send non-supervisory data to the enterprise management subsystem 20. The system 30 collects regulatory data and then sends it to the regulatory subsystem 10. The regulatory subsystem 10 receives the regulatory data, analyzes it according to a preset administrative data analysis strategy, processes regulatory responsibilities online, stores the regulatory data, and returns the stored regulatory data to the enterprise management subsystem. The enterprise management subsystem 20 receives non-regulatory data and the regulatory data returned by the regulatory subsystem, analyzes the regulatory and non-regulatory data according to a preset enterprise management data analysis strategy, processes enterprise management responsibilities online, and stores the regulatory data.

[0047] The enterprise data collection terminal and the regulatory data collection terminal use the same application platform and are deployed in a unified application.

[0048] For example, addressing the current shortcomings of the lack of interoperability between the management systems of participating construction units and the regulatory subsystems of administrative departments, which necessitate the repetitive execution of many management processes for a single project, this invention proposes a construction project management system that integrates the regulatory subsystem of administrative departments with the management systems of participating construction units. This system includes an enterprise management subsystem 20 that manages and analyzes internal enterprise data, and a regulatory subsystem 10 that monitors and analyzes enterprise data. The enterprise management subsystem 20 is electrically connected to an enterprise data acquisition terminal 40, and the regulatory subsystem 10 is electrically connected to a regulatory data acquisition terminal 30. The regulatory subsystem 10, enterprise management subsystem 20, regulatory data acquisition terminal 30, and enterprise data acquisition terminal 40 are deployed within the same application, which may include, but is not limited to, applications (APPs), WeChat mini-programs, and other application software.

[0049] Users input the internal management data of participating enterprises into the enterprise management subsystem 20. The enterprise data collection terminal 40 is used to collect internal management data from various participating enterprises. Based on the data type input by the user, it filters out non-regulatory data from the internal management data and sends it to the regulatory subsystem. Additionally, the regulatory data collection terminal is used to collect regulatory data from enterprises and send it to the regulatory subsystem. It should be noted that regulatory data refers to data that enterprises need to report to the administrative authorities for supervision. For example, it collects daily inspection reports, construction progress data for each work team, and data from various IoT devices installed by the construction unit for project management; it collects original inspection records, test results, and test reports from testing units; it collects daily inspection reports and anomaly handling data from supervision units; and it collects daily entry and exit data and monitoring data from monitoring units. The regulatory data collection terminal 30 is used to collect regulatory data, such as project management team information, project progress, supervision-witnessed sampling process, and crane installation reporting.

[0050] In the embodiments disclosed in this invention, the administrative authorities manage the regulatory data uploaded by the regulatory data collection terminal 30. In addition, considering that enterprises also need to manage data internally, the regulatory subsystem 10 will return the regulatory data to the enterprise management subsystem 20 after obtaining the regulatory data, so as to facilitate the enterprise's internal analysis, supervision and storage of data.

[0051] Optionally, the regulatory database and the enterprise-level regulatory database are connected via a standardized interface. After acquiring the regulatory data, the regulatory database dynamically verifies the user's identity and, upon successful verification, pushes the user-related data from the regulatory database to the enterprise-level regulatory database. The enterprise data collection terminal is a mobile application platform, which includes external standard interfaces and internal data communication protocol interfaces.

[0052] like Figure 2 As shown, the enterprise data collection terminal first develops a mobile application platform based on native Android / iOS development. This platform provides comprehensive external standards and internal data communication protocol interfaces. The regulatory data collection terminal can be integrated into the enterprise data collection terminal through application registration. The enterprise data collection terminal can then call the application of the regulatory data collection terminal (by accessing the URL address). Simultaneously, the enterprise data collection terminal includes applications developed according to the enterprise's own needs, thus achieving a seamless switching effect between different applications for the user.

[0053] Furthermore, the enterprise data collection terminal adopts the same underlying framework as the regulatory data collection terminal (such as the Spring Cloud Alibaba microservice architecture), and can call the capability set under the underlying framework (such as: location acquisition capability, Bluetooth access capability, instant messaging capability, account management capability, video call capability, camera access capability, etc.), thereby reducing system code redundancy, optimizing code efficiency, and alleviating operation and maintenance pressure.

[0054] During the process of the regulatory subsystem 10 returning regulatory data to the enterprise management subsystem 20, to ensure that the regulatory data of each enterprise is returned to the corresponding enterprise management subsystem, the regulatory data uploaded to the regulatory subsystem 10 in this embodiment includes: the enterprise code of the participating enterprise, the data type, data time, data packet ID, and data content of the regulatory data. The regulatory subsystem uses regulatory data subscription management, which requires management of enterprise code, message category, push method, push address, and push mode. While receiving and parsing the regulatory data, the backend of the regulatory subsystem also needs to encrypt the data packet using RSA according to the enterprise code and data type (the private key is distributed by the regulatory subsystem to the corresponding enterprise and managed uniformly in the enterprise information) before sending it to the corresponding enterprise management subsystem. This process requires the enterprise management subsystem to uniformly use the message push requirements of the regulatory subsystem to avoid the risk of abnormal sending and receiving caused by different message receiving modes of the enterprise management subsystem. That is, the regulatory subsystem includes: a subscription management module, which is used to encrypt the data packet of the regulatory data according to the enterprise code and data type, so as to return the encrypted regulatory data to the enterprise management subsystem.

[0055] The flowchart of the process by which the regulatory subsystem 10 returns regulatory data to the enterprise management subsystem 20 is shown below. Figure 3 As shown, the system sequentially determines the enterprise code, message type (data type), and push path (push method) of the regulatory data. Once the above information is confirmed to be consistent, the push message is encapsulated and encrypted (the data packet of the regulatory data is encrypted according to the enterprise code and data type). The encrypted public and private keys are obtained, and the message is pushed to the enterprise management subsystem. The enterprise code needs to be set in the enterprise management section of the regulatory subsystem. The message category and subscription level are provided by the regulatory subsystem. This approach avoids the risk of abnormal message reception caused by different message receiving modes in different enterprise management subsystems, reduces the business computing pressure on each enterprise management subsystem during data application or data analysis, enhances the ability to locate and process abnormal data, facilitates the tracking and handling of problems by administrators or relevant business personnel, and improves processing efficiency.

[0056] In this system, enterprise coding must ensure global uniqueness. Since current services are primarily distributed and microservice-based, and large data volumes lead to database sharding and table partitioning, horizontal table partitioning requires guaranteeing the global uniqueness of the `id` (unique identifier) ​​within each table. Therefore, an efficient solution for distributed `id` (unique identifier) ​​needs to be designed. The algorithm generates a 64-bit long integer unique `id`, with the highest bit fixed at 0 (because the generated `id` is a positive integer; a bit of 1 would be negative). The next 41 bits store a millisecond-level timestamp. 41 / (1000*60*60*24*365)=69, so it can be used for approximately 69 years. Next is the 10-digit storage machine code, including a 5-digit datacenterId (datacenter identifier) ​​and a 5-digit workerId (server identifier). A maximum of 2^10=1024 machines can be deployed. Finally, there's the 12-digit storage sequence number. For the same millisecond timestamp, this incrementing sequence number is used for differentiation. That is, for the same machine, at the same millisecond timestamp, 2... 12 = 4096 unique IDs.

[0057] For workerID (server identifier) ​​allocation, manual configuration is perfectly feasible when the service cluster has a small number of nodes. However, manual configuration becomes too costly when the service scales up. Therefore, the persistent sequential node feature of ZooKeeper (an open-source distributed coordination service) is used to automatically configure workerIDs (server identifiers) on the Snowflake (globally unique ID generation service) nodes. The startup process follows these steps: When the Snowflake globally unique ID generation service starts, it connects to the ZooKeeper cluster and checks under the leaf_forever permanent leaf parent node whether it has already registered (whether it has a sequential child node). If it has registered, it retrieves its workerID (an integer ID number generated by the ZooKeeper sequential node) and starts the service. If it has not registered, it creates a persistent sequential node under the parent node, retrieves the sequence number as its workerID (server identifier), and starts the service.

[0058] In addition, the enterprise code and key are used together, employing an authentication method using appid (enterprise code), appsecret (enterprise key), and a fixed callback address. The appid is the enterprise code, and both are automatically generated according to the corresponding algorithm when an account is opened for a specific enterprise in the regulatory enterprise management system. The appsecret (enterprise key) is generated using the SHA1 (secure hash algorithm). When regulatory data is reported to the regulatory subsystem, the subsystem only needs to obtain the enterprise code carried in the report. It then searches the database for the existence of the enterprise code and retrieves the corresponding appsecret (enterprise key) and callback address. The appsecret (enterprise key) is used with a signature algorithm to encrypt the sent message, and the encrypted data is sent to the corresponding callback address. This acts as an IP address whitelist, effectively distinguishing data and ensuring its secure and error-free transmission to the corresponding enterprise management subsystem.

[0059] Using the asymmetric encryption algorithm RSA, when a regulatory authority activates an enterprise user account, it generates a public and private key set using the RSA algorithm. The key can be provided to the corresponding enterprise for download through the enterprise's open platform. Before sending message data, the regulatory authority encrypts the data using the enterprise's corresponding public key. To prevent third parties from impersonating the regulatory authority's data transmission behavior or intercepting and tampering with the data, an electronic signature mechanism is required. The specific implementation is as follows:

[0060] Step 1: Call back the unified system parameters of the enterprise management subsystem address, as shown in Table 1:

[0061] Table 1

[0062]

[0063] Step 2: Use a GET request with an RSA (message data) parameter named data.

[0064] Step 3: Sort the non-empty request parameters in ascending alphabetical order by their names, and concatenate them into a string stringA using the URL key-value pair format (i.e., appid=value1&data=value2&noncestr=value3×tamp=value4); append appsecret to the end of stringA to obtain the string stringSignTemp; perform a SHA1 (secure hash algorithm) operation on stringSignTemp to obtain the signature (digital signature) value.

[0065] Step 4: The enterprise management subsystem verifies the request by checking the signature (electronic signature). If it confirms that the GET request originates from the monitoring port server, the access is effective, and subsequent data decryption processing proceeds normally; otherwise, it returns a failure. The encryption / verification process is as follows: The four parameters—appid (enterprise code), data (encrypted message data), timestamp, and noncestr (request random string)—are sorted lexicographically; the four parameter strings are concatenated with the appsecret (enterprise key) into a single string and encrypted using SHA1 (secure hash algorithm); the enterprise management subsystem obtains the encrypted string and compares it with the signature (electronic signature). If they match, the request is identified as originating from the monitoring end. The request carries the parameters appid and signature; only those with a valid appid and a correct signature are allowed to proceed. This solves the problems of identity verification and parameter tampering. Even if the request parameters are intercepted, because the appsecret cannot be obtained externally (the enterprise key is only used for local encryption on the monitoring end and the enterprise backend and does not participate in network transmission), a legitimate request cannot be forged. After the enterprise management subsystem verifies the signature, it proves that the request is a legitimate regulatory message push request. The key downloaded from the enterprise open platform is used to decrypt the data encrypted by the push data to finally obtain the plaintext message.

[0066] When the enterprise management subsystem receives encrypted regulatory data, it decrypts the data packet using the corresponding private key to obtain the decrypted regulatory data. The private key is distributed from the regulatory subsystem to the enterprise management subsystem to verify the validity and security of the regulatory data, preventing data leakage caused by plaintext data captured during network packet sniffing.

[0067] In addition, such as Figure 1 As shown, the regulatory subsystem includes 10 components: a regulatory database 11, a regulatory performance module 12, and a regulatory data analysis module 13. The regulatory data analysis module 13 is used to statistically analyze the regulatory data of different participating enterprises and to view in real time the image data acquired by the image acquisition device and the data from the Internet of Things (IoT) device in each project. The regulatory performance module 12 is used to process regulatory responsibilities online, view and sign off on rectification information of the project, and process the filing information of participating enterprises. The regulatory database 11 is used to store the basic information of the project, the management data generated during the supervision process of the regulatory performance module, the image data acquired by the image acquisition device, and the data from the IoT device.

[0068] For example, the regulatory data analysis module 13 analyzes data from the perspective of the construction administrative department, such as statistical data for each district, statistical data for participating units in different types of construction projects, and real-time viewing of data from image acquisition devices and IoT devices installed in engineering projects as required by regulations. The regulatory performance module 12 processes regulatory responsibilities online, such as viewing and signing off on project rectification status and processing various enterprise filings. The regulatory database 11 stores basic project information (such as project name, project address, participating units, etc.), management data of the regulatory process, image acquisition device data, and IoT device data.

[0069] The enterprise management subsystem 20 includes: an enterprise database 21, an enterprise management module 22, an enterprise data analysis module 23, an enterprise-level regulatory database 24, and an enterprise regulatory data analysis module 25. The enterprise data analysis module 23 is used to statistically analyze data from different departments and business categories of participating enterprises, to view in real-time image data collected by image acquisition devices and IoT device data installed by enterprises themselves in engineering projects, and to statistically analyze data from different technical personnel and different engineering projects. The enterprise management module 22 is used to process the regulatory responsibilities of participating enterprises online. The enterprise database 21 stores the process management data, image data, and IoT device data of participating enterprises. The enterprise-level regulatory database 24 stores the regulatory data returned from the regulatory subsystem to the enterprise management subsystem. The enterprise regulatory data analysis module 25 analyzes the data in the enterprise-level regulatory database. The regulatory database 11 needs to undergo information security level protection assessment and includes a standardized interface 111, which contains a dynamic user identity verification function.

[0070] For example, the enterprise data analysis module 23 analyzes data from the enterprise management dimension, such as statistical data of various departments, statistical data of different types of business, real-time viewing of data from image acquisition devices and IoT devices installed by the enterprise in engineering projects, statistical data of different technical personnel, and statistical data of different projects. The enterprise management module 22 processes enterprise management responsibilities online, such as stamping applications, procurement applications, and production plan approvals. The enterprise database 21 stores all enterprise management data, including process management data, image acquisition device data, and IoT device data. The enterprise-level supervision database 24 stores the part of the supervision data that the unit participates in in collaboration (i.e., the supervision data returned by the supervision subsystem to the enterprise management subsystem). The enterprise supervision data analysis module 25 analyzes the data in the enterprise-level supervision database, such as analyzing the non-conformity rate of different material suppliers for construction units and analyzing the rectification notices received by different construction units entrusted by the construction unit and the rectification completion status.

[0071] Furthermore, in the traditional commissioned development model, the system developer pays for the operating costs. However, as regulatory departments expand their systems, operating costs rise, increasing financial pressure. Moreover, according to laws and regulations, regulatory subsystems cannot charge fees to regulated entities, leading to significant difficulties in iterating and upgrading the system after development. In this embodiment of the invention, the regulatory subsystem and regulatory data collection terminal are developed by suppliers commissioned by the regulatory agency. The enterprise data collection terminal and enterprise management subsystem are developed by suppliers commissioned by each participating party according to their own management requirements. The operating costs of the regulatory subsystem and regulatory data collection terminal are charged based on the communication traffic pricing between the regulatory database and the enterprise-level regulatory database. The operating costs of the enterprise data collection terminal and enterprise management subsystem are borne by each participating party. By purchasing data services for the regulatory subsystem and regulatory data collection terminal, participating companies not only solved the funding needs for system iteration and upgrades, but also brought direct management value and potential economic benefits to them through the information sharing mechanism of government-enterprise interconnection. At the same time, since companies can share basic project information and regulatory data, they can avoid redundant development of enterprise data collection terminals and enterprise management subsystems in similar aspects, thus saving development investment costs for each participating unit.

[0072] Figure 4 This is a flowchart illustrating an application method for a construction project management system based on government-enterprise interconnection, according to an exemplary embodiment. Figure 4 As shown, a construction project management system based on government-enterprise interconnection is applied. This system includes: an enterprise data acquisition terminal, a regulatory data acquisition terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data acquisition terminal is electrically connected to the enterprise management subsystem, the regulatory data acquisition terminal is electrically connected to the regulatory subsystem, and the enterprise management subsystem is electrically connected to the regulatory subsystem. The method includes:

[0073] In step 410, the internal management data of the participating enterprises is collected through the enterprise data collection terminal, and the non-regulatory data is sent to the enterprise management subsystem;

[0074] In step 420, after collecting regulatory data through the regulatory data collection terminal, the regulatory data is sent to the regulatory subsystem.

[0075] In step 430, the regulatory data is received through the regulatory subsystem, and the regulatory data is analyzed, the regulatory responsibilities are processed online, and the regulatory data is stored according to the preset administrative data analysis strategy. The stored regulatory data is then returned to the enterprise management subsystem.

[0076] In step 440, the non-regulatory data and the regulatory data returned by the regulatory subsystem are received through the enterprise management subsystem, and the regulatory and non-regulatory data are analyzed, the enterprise management responsibilities are processed online, and the regulatory data is stored according to the preset enterprise management data analysis strategy.

[0077] Optionally, the regulatory data sent from the regulatory data collection terminal to the regulatory subsystem includes: the enterprise code of the participating enterprise, the data type, data time, data packet ID, and data content of the regulatory data. The method further includes: encrypting the data packet of the regulatory data according to the enterprise code and data type, so as to return the encrypted regulatory data to the enterprise management subsystem.

[0078] In summary, this invention discloses a construction project management system and application method based on government-enterprise interconnection. The system includes: an enterprise data collection terminal, a regulatory data collection terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data collection terminal collects internal management data from participating enterprises and sends non-regulatory data to the enterprise management subsystem. The regulatory data collection terminal collects regulatory data and sends it to the regulatory subsystem. The regulatory subsystem receives and stores the regulatory data and returns it to the enterprise management subsystem. The enterprise management subsystem receives both non-regulatory data and the regulatory data returned by the regulatory subsystem, and analyzes the regulatory and non-regulatory data according to a preset data analysis strategy. This system enables regulatory data sharing, avoiding the single-project management model of regulation. By integrating the regulatory data collection terminal, the regulatory subsystem, and the enterprise data collection terminal into a single system, it avoids technicians repeatedly switching between different management tasks and repeatedly inputting data, thus improving ease of use.

[0079] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.

[0080] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.

[0081] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.

Claims

1. A construction project management system based on government-enterprise interconnection, characterized in that, The system includes: an enterprise data acquisition terminal, a regulatory data acquisition terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data acquisition terminal is electrically connected to the enterprise management subsystem, the regulatory data acquisition terminal is electrically connected to the regulatory subsystem, and the enterprise management subsystem is electrically connected to the regulatory subsystem. The enterprise data collection terminal is used to collect internal management data of participating enterprises and send non-regulatory data to the enterprise management subsystem; The regulatory data collection terminal is used to collect regulatory data and then send the regulatory data to the regulatory subsystem. The regulatory subsystem is used to receive the regulatory data, analyze the regulatory data according to the preset administrative supervisor data analysis strategy, process the regulatory responsibilities online, and store the regulatory data, and return the stored regulatory data to the enterprise management subsystem. The stored regulatory data includes the received regulatory data and the management data generated during the online processing of regulatory responsibilities. The enterprise management subsystem is used to receive the non-regulatory data and the regulatory data returned by the regulatory subsystem, and to analyze the regulatory and non-regulatory data according to the preset enterprise management data analysis strategy, process enterprise management responsibilities online, and store the regulatory data.

2. The construction project management system based on government-enterprise interconnection according to claim 1, characterized in that, The enterprise data collection terminal and the regulatory data collection terminal use the same application platform and are deployed in the same application.

3. The construction project management system based on government-enterprise interconnection according to claim 1, characterized in that, The regulatory data sent from the regulatory data collection terminal to the regulatory subsystem includes: the enterprise code of the participating enterprise, the data type, data time, data packet ID, and data content of the regulatory data; The regulatory subsystem includes a subscription management module, which is used to encrypt the data packets of the regulatory data according to the enterprise code and data type, so as to return the encrypted regulatory data to the enterprise management subsystem.

4. The construction project management system based on government-enterprise interconnection according to claim 3, characterized in that, When the enterprise management subsystem receives encrypted regulatory data, it decrypts the data packet using the corresponding private key to obtain the decrypted regulatory data.

5. The construction project management system based on government-enterprise interconnection according to claim 1, characterized in that, The regulatory subsystem includes: a regulatory data analysis module, a regulatory performance module, and a regulatory database; The regulatory data analysis module is used to statistically analyze the regulatory data of different participating enterprises and to view in real time the image data and IoT device data acquired by the image acquisition device in each project. The regulatory performance module is used to process regulatory responsibilities online, view and sign off on rectification information of engineering projects, and process the filing information of participating enterprises. The regulatory database is used to store basic information about engineering projects, management data generated during the supervision process of the regulatory performance module, image data acquired by image acquisition devices, and data from Internet of Things devices.

6. The construction project management system based on government-enterprise interconnection according to claim 5, characterized in that, The enterprise management subsystem includes: an enterprise data analysis module, an enterprise management module, an enterprise database, an enterprise-level regulatory database, and an enterprise regulatory data analysis module; The enterprise data analysis module is used to statistically analyze data from different departments and different types of business of participating enterprises, to view in real time the image data and IoT device data collected by the image acquisition devices installed by the enterprises themselves in the project, and to statistically analyze the data of different technical personnel and different projects. The enterprise management module is used to process the supervisory responsibilities of participating enterprises online; The enterprise database finally stores the process management data, image data, and IoT device data of the participating enterprises; The enterprise-level regulatory database is used to store the regulatory data returned by the regulatory subsystem to the enterprise management subsystem; The enterprise regulatory data analysis module is used to analyze the data in the enterprise-level regulatory database.

7. The construction project management system based on government-enterprise interconnection according to claim 6, characterized in that, The regulatory database and the enterprise-level regulatory database are connected via a standardized interface; After obtaining the regulatory data, the regulatory database dynamically verifies the user's identity and, upon passing the dynamic verification, pushes the user-related data in the regulatory database to the enterprise-level regulatory database.

8. The construction project management system based on government-enterprise interconnection according to claim 1, characterized in that, The enterprise data collection terminal is a mobile application platform, which includes external standard interfaces and internal data communication protocol interfaces.

9. The construction project management system based on government-enterprise interconnection according to claim 1, characterized in that, The regulatory data collection terminal is a mobile application platform, which includes external standard interfaces and internal data communication protocol interfaces.

10. An application method for a construction project management system based on government-enterprise interconnection, characterized in that, An application is made to a government-enterprise interconnected construction project management system. The system includes: an enterprise data acquisition terminal, a regulatory data acquisition terminal, a regulatory subsystem, and an enterprise management subsystem. The enterprise data acquisition terminal is electrically connected to the enterprise management subsystem, the regulatory data acquisition terminal is electrically connected to the regulatory subsystem, and the enterprise management subsystem is electrically connected to the regulatory subsystem. The method includes: The internal management data of participating enterprises is collected through the enterprise data collection terminal, and non-regulatory data is sent to the enterprise management subsystem. After collecting regulatory data through the regulatory data collection terminal, the regulatory data is sent to the regulatory subsystem. The regulatory subsystem receives the regulatory data, analyzes the regulatory data according to the preset administrative supervisor data analysis strategy, processes the regulatory responsibilities online, and stores the regulatory data. The stored regulatory data is then returned to the enterprise management subsystem. The stored regulatory data includes the received regulatory data and the management data generated during the online processing of regulatory responsibilities. The enterprise management subsystem receives the non-regulatory data and the regulatory data returned by the regulatory subsystem, and analyzes the regulatory and non-regulatory data according to the preset enterprise management data analysis strategy, processes enterprise management responsibilities online, and stores the regulatory data.

Images