Digital engineering safety emergency management method and system

Abstract

The invention provides a digital engineering safety emergency management method and system in the technical field of engineering safety emergency management. The method comprises the steps that S1, a construction server verifies an emergency plan making instruction; s2, creating an emergency management process through a workflow designer, creating a display page of the emergency management process through a page designer, setting a report of each node link in the display page through a data set definition device, and setting a data processing process of the report through an ETL tool so as to generate a first emergency plan; s3, sending the first emergency plan to a supervision server; s4, the supervision server checks the first emergency plan to generate a second emergency plan and sends the second emergency plan to the owner server; and S5, the owner server audits the second emergency plan to generate a third emergency plan, and sets a two-dimensional code linked with the third emergency plan to perform engineering safety emergency management. The method has the advantage that the reliability and efficiency of engineering safety emergency management are greatly improved.

Description

Technical Field

[0001] The present invention relates to the technical field of engineering safety emergency management, and in particular to a digital engineering safety emergency management method and system. Background Art

[0002] Before the construction of an engineering project, a detailed emergency plan will be formulated, including accident prevention, initial response, emergency handling, and post-event recovery, so that we can respond calmly when an emergency occurs. In order to test the effectiveness of the emergency plan, it is traditionally simply rehearsed in the form of a desktop sandbox, and the emergency plan is not reviewed. When an emergency actually occurs, emergency rescue relies on manual communication and temporary personnel. There are often incomplete emergency supplies, insufficient number of rescue personnel, disordered division of labor, unclear processes, unclear human-machine numbers, slow information transmission and response speed, errors in information collection and transmission, and low efficiency in resource allocation and management, which affect the reliability and efficiency of emergency management; and the rehearsals of some companies are often formalistic, and the rescue personnel lack practical experience. When facing an emergency, it is easy to have inadequate command or wrong decision-making, which in turn affects the response efficiency of the entire emergency rescue.

[0003] Therefore, how to provide a digital engineering safety emergency management method and system to improve the reliability and efficiency of engineering safety emergency management has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a digital engineering safety emergency management method and system to improve the reliability and efficiency of engineering safety emergency management.

[0005] In a first aspect, the present invention provides a digital engineering safety emergency management method, comprising the following steps:

[0006] Step S1, the construction server receives the emergency plan formulation instruction sent by the owner server, and verifies the emergency plan formulation instruction;

[0007] Step S2: The construction server creates an emergency management process through a workflow designer, creates a display page of the emergency management process through a page designer, sets reports linked to each node in the display page through a data set definer, sets a data processing flow of the report through an ETL tool, and generates a first emergency plan;

[0008] Step S3: After evaluating the first emergency plan, the construction server encrypts the first emergency plan into a first encrypted plan, and sends the first encrypted plan to the supervision server;

[0009] Step S4: the supervision server decrypts the received first encrypted plan to obtain a first emergency plan, reviews the first emergency plan to generate a second emergency plan, encrypts the second emergency plan into a second encrypted plan, and sends the second encrypted plan to the owner server;

[0010] Step S5: the owner server decrypts the received second encrypted plan to obtain a second emergency plan, reviews the second emergency plan to generate a third emergency plan, sets a QR code linked to the third emergency plan, and performs engineering safety emergency management based on the QR code;

[0011] The step S1 is specifically as follows:

[0012] The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp.

[0013] The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

[0014] Furthermore, the step S2 is specifically as follows:

[0015] The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node;

[0016] Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page;

[0017] Setting the report linked to each node in each display page through a data set definer, and setting the second GU ID of each report;

[0018] The report is set by using an ETL tool to at least include a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan.

[0019] Furthermore, the step S3 is specifically as follows:

[0020] After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

[0021] Furthermore, the step S4 is specifically as follows:

[0022] The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value;

[0023] The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan.

[0024] The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

[0025] Furthermore, the step S5 is specifically as follows:

[0026] The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value;

[0027] The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

[0028] In a second aspect, the present invention provides a digital engineering safety emergency management system, comprising the following modules:

[0029] The emergency plan formulation instruction verification module is used for the construction server to receive the emergency plan formulation instruction sent by the owner's server and verify the emergency plan formulation instruction;

[0030] The first emergency plan generation module is used for the construction server to create an emergency management process through a workflow designer, create a display page of the emergency management process through a page designer, set a report linked to each node in the display page through a data set definer, and set a data processing flow of the report through an ETL tool, thereby generating a first emergency plan;

[0031] A first emergency plan encryption transmission module, configured for the construction server to encrypt the first emergency plan into a first encrypted plan after evaluating the first emergency plan, and to send the first encrypted plan to the supervision server;

[0032] A second emergency plan encryption transmission module, used for the supervision server to decrypt the first encrypted plan received to obtain the first emergency plan, review the first emergency plan to generate a second emergency plan, encrypt the second emergency plan into a second encrypted plan, and send the second encrypted plan to the owner server;

[0033] The engineering safety emergency management module is used for decrypting the second encrypted plan received by the owner server to obtain a second emergency plan, reviewing the second emergency plan to generate a third emergency plan, setting a QR code linked to the third emergency plan, and performing engineering safety emergency management based on the QR code;

[0034] The emergency plan formulation instruction verification module is specifically used for:

[0035] The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp.

[0036] The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

[0037] Furthermore, the first emergency plan generation module is specifically used to:

[0038] The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node;

[0039] Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page;

[0040] Setting the report linked to each node in each display page through a data set definer, and setting the second GU ID of each report;

[0041] The report is set by using an ETL tool to at least include a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan.

[0042] Furthermore, the first emergency plan encryption transmission module is specifically used for:

[0043] After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

[0044] Furthermore, the second emergency plan encryption transmission module is specifically used for:

[0045] The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value;

[0046] The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan.

[0047] The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

[0048] Furthermore, the engineering safety emergency management module is specifically used for:

[0049] The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value;

[0050] The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

[0051] The advantages of the present invention are:

[0052] 1. After the construction server verifies the emergency plan formulation instruction sent by the owner's server, the emergency management process is created through the workflow designer, the display page of the emergency management process is created through the page designer, the report linked to each node in the display page is set through the data set definer, and the data processing flow of the report is set through the ETL tool, and then the first emergency plan is generated. After evaluating the first emergency plan, it is encrypted into the first encrypted plan and sent to the supervision server; then the supervision server decrypts the first encrypted plan to obtain the first emergency plan, reviews the first emergency plan to generate the second emergency plan, encrypts the second emergency plan into the second encrypted plan and sends it to the owner's server; finally, the owner's server decrypts the second encrypted plan to obtain the second emergency plan, and evaluates the first emergency plan. The second emergency plan is reviewed to generate a third emergency plan, and a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code; that is, during the generation of the emergency plan, the construction server uses big data technology to evaluate it, and after the evaluation is passed, it is reviewed by the supervision server and the owner's server in turn to ensure the rationality of the emergency plan, so that when an emergency occurs, it can respond quickly according to the emergency management process of the emergency plan; by setting a QR code to link the emergency plan, on-site staff can quickly access the display page through the QR code, quickly upload relevant on-site data through the report on the display page, and the formatted display page can also ensure the standardization of data collection, which ultimately greatly improves the reliability and efficiency of engineering safety emergency management.

[0053] 2. Send emergency plan formulation instructions carrying the sender, timestamp and hash value to the construction server through the TLS protocol. Subsequently, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the sender. Three layers of security measures are taken before and after to prevent the construction server from performing related operations based on illegal emergency plan formulation instructions, which greatly improves the security of engineering safety emergency management.

[0054] 3. Perform HMAC calculation on the first emergency plan to obtain the first HMAC value, encrypt the first emergency plan and the first HMAC value through the AES256 algorithm to obtain the first-level encrypted data, swap the number 1 and the letter l in the first-level encrypted data to generate the second-level encrypted data, encrypt the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and send the first encrypted plan to the supervision server through the TLS protocol; subsequently, the integrity of the first emergency plan can be checked through the first HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the first encryption plan cannot be cracked, and the TLS protocol is a secure transmission protocol. At least 5 security measures (HMAC calculation, AES256 algorithm, character swap, IDEA algorithm, TLS protocol) have been taken.

[0055] 4. By evaluating the first emergency plan through big data technology, we can quickly determine the rationality of the first emergency plan and make timely adjustments to the unreasonable aspects, thereby greatly improving the efficiency of engineering safety emergency management.

[0056] 5. Perform HMAC calculation on the second emergency plan to obtain the second HMAC value, encrypt the second emergency plan and the second HMAC value through the 3DES algorithm to obtain the first encrypted data, swap the number 2 and the letter z in the first encrypted data to generate the second encrypted data, encrypt the secondary encrypted data into the second encrypted plan through the RC2 algorithm, and send the second encrypted plan to the owner's server through the TLS protocol; subsequently, the second emergency plan can be integrity checked through the second HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the second encrypted plan cannot be cracked, and the TLS protocol is a secure transmission protocol. At least 5 security measures (HMAC calculation, 3DES algorithm, character swapping, RC2 algorithm, TLS protocol) have been taken.

[0057] 6. Add electronic signatures to the approved emergency plans through the supervision server and the owner's server to facilitate later traceability and quickly verify the legality of the emergency plans. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0059] Figure 1 The present invention discloses a flow chart of a digital engineering safety emergency management method.

[0060] Figure 2 It is a structural schematic diagram of a digital engineering safety emergency management system of the present invention. DETAILED DESCRIPTION

[0061] The technical solution in the embodiment of the present application has the following overall idea: in the process of generating the emergency plan, the construction server is evaluated through big data technology. After the evaluation is passed, it is reviewed by the supervision server and the owner server in turn to ensure the rationality of the emergency plan. When an emergency occurs, it can respond quickly according to the emergency management process of the emergency plan; by setting a QR code to link the emergency plan, on-site staff can quickly access the display page through the QR code, quickly upload relevant on-site data through the report on the display page, and the formatted display page can also ensure the standardization of data collection, thereby improving the reliability and efficiency of engineering safety emergency management.

[0062] Please refer to Figure 1 to Figure 2 As shown, a preferred embodiment of a digital engineering safety emergency management method of the present invention includes the following steps:

[0063] Step S1, the construction server receives the emergency plan formulation instruction sent by the owner server, and verifies the emergency plan formulation instruction;

[0064] Step S2: The construction server creates an emergency management process through a workflow designer, creates a display page of the emergency management process through a page designer, sets reports linked to each node in the display page through a data set definer, sets a data processing flow of the report through an ETL tool, and generates a first emergency plan;

[0065] Step S3: After evaluating the first emergency plan, the construction server encrypts the first emergency plan into a first encrypted plan, and sends the first encrypted plan to the supervision server;

[0066] Step S4: the supervision server decrypts the received first encrypted plan to obtain a first emergency plan, reviews the first emergency plan to generate a second emergency plan, encrypts the second emergency plan into a second encrypted plan, and sends the second encrypted plan to the owner server;

[0067] Step S5: the owner server decrypts the received second encrypted plan to obtain a second emergency plan, reviews the second emergency plan to generate a third emergency plan, sets a QR code linked to the third emergency plan, and performs engineering safety emergency management based on the QR code;

[0068] The step S1 is specifically as follows:

[0069] The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp.

[0070] Emergency plan formulation instructions carrying the sender, timestamp and hash value are sent to the construction server through the TLS protocol. Subsequently, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the sender. Three layers of security measures are taken before and after to prevent the construction server from performing related operations based on illegal emergency plan formulation instructions, which greatly improves the security of engineering safety emergency management.

[0071] The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

[0072] The step S2 is specifically as follows:

[0073] The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node;

[0074] The workflow designer is a tool for creating, editing and managing workflows, implemented through a graphical user interface (GUI), which allows users to design workflows by dragging and dropping and connecting different tasks, activities and decision nodes, thereby simplifying and optimizing business process management;

[0075] Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page;

[0076] Setting the report linked to each node in each display page through a data set definer, and setting the second GU ID of each report;

[0077] The data set definer is a visual definer based on SQL statements. It is used to query and calculate the data required for the report. The defined data set is bound using Excel software, and the prepared report is uploaded to the report library. The report template is based on the jx ls binding expression rules, and the parsing is performed by the jx ls parsing engine.

[0078] The report is set by using an ETL tool to include at least a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan; the ETL tool adopts Kettle.

[0079] The step S3 is specifically as follows:

[0080] After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

[0081] The first HMAC value is obtained by performing HMAC calculation on the first emergency plan, and the first emergency plan and the first HMAC value are encrypted by the AES256 algorithm to obtain the first-level encrypted data. The number 1 and the letter l in the first-level encrypted data are swapped to generate the second-level encrypted data, and the second-level encrypted data is encrypted into the first encrypted plan by the IDEA algorithm. The first encrypted plan is sent to the supervision server through the TLS protocol. Subsequently, the integrity of the first emergency plan can be checked through the first HMAC value. If the corresponding encryption algorithm or data transformation rule is unknown, the first encryption plan cannot be cracked. The TLS protocol is a secure transmission protocol, and at least 5 security measures (HMAC calculation, AES256 algorithm, character swapping, IDEA algorithm, and TLS protocol) are taken before and after.

[0082] By evaluating the first emergency plan through big data technology, such as cost-effectiveness and risk assessment, we can quickly determine the rationality of the first emergency plan and make timely adjustments to the unreasonable aspects, thereby greatly improving the efficiency of engineering safety emergency management.

[0083] The step S4 is specifically as follows:

[0084] The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value;

[0085] The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan.

[0086] The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

[0087] The second emergency plan is calculated by HMAC to obtain the second HMAC value, the second emergency plan and the second HMAC value are encrypted by the 3DES algorithm to obtain the first encrypted data, the number 2 and the letter z in the first encrypted data are swapped to generate the second encrypted data, the secondary encrypted data is encrypted into the second encrypted plan by the RC2 algorithm, and the second encrypted plan is sent to the owner's server through the TLS protocol; subsequently, the second emergency plan can be checked for integrity by the second HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the second encrypted plan cannot be cracked, and the TLS protocol is a secure transmission protocol, and at least 5 security measures are taken before and after (HMAC calculation, 3DES algorithm, character swapping, RC2 algorithm, TLS protocol).

[0088] The step S5 is specifically as follows:

[0089] The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value;

[0090] The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

[0091] Electronic signatures are added to the approved emergency plans through the supervision server and the owner's server to facilitate later traceability and quickly verify the legality of the emergency plans.

[0092] In specific implementation, different QR codes can be set based on different types of the third emergency plan, and the QR codes can be pasted in corresponding positions. For example, for emergency plans for personnel, equipment or work sites, personnel codes, equipment codes or work site codes can be set, and different QR codes are associated with different first GUIDs. During engineering safety emergency management, the staff can jump to the corresponding display page by scanning the QR code, and fill in the corresponding data through the report on the display page and submit it.

[0093] A preferred embodiment of a digital engineering safety emergency management system of the present invention includes the following modules:

[0094] The emergency plan formulation instruction verification module is used for the construction server to receive the emergency plan formulation instruction sent by the owner's server and verify the emergency plan formulation instruction;

[0095] The first emergency plan generation module is used for the construction server to create an emergency management process through a workflow designer, create a display page of the emergency management process through a page designer, set a report linked to each node in the display page through a data set definer, and set a data processing flow of the report through an ETL tool, thereby generating a first emergency plan;

[0096] A first emergency plan encryption transmission module, configured for the construction server to encrypt the first emergency plan into a first encrypted plan after evaluating the first emergency plan, and to send the first encrypted plan to the supervision server;

[0097] A second emergency plan encryption transmission module, used for the supervision server to decrypt the first encrypted plan received to obtain the first emergency plan, review the first emergency plan to generate a second emergency plan, encrypt the second emergency plan into a second encrypted plan, and send the second encrypted plan to the owner server;

[0098] The engineering safety emergency management module is used for decrypting the second encrypted plan received by the owner server to obtain a second emergency plan, reviewing the second emergency plan to generate a third emergency plan, setting a QR code linked to the third emergency plan, and performing engineering safety emergency management based on the QR code;

[0099] The emergency plan formulation instruction verification module is specifically used for:

[0100] The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp.

[0101] Emergency plan formulation instructions carrying the sender, timestamp and hash value are sent to the construction server through the TLS protocol. Subsequently, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the sender. Three layers of security measures are taken before and after to prevent the construction server from performing related operations based on illegal emergency plan formulation instructions, which greatly improves the security of engineering safety emergency management.

[0102] The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

[0103] The first emergency plan generation module is specifically used for:

[0104] The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node;

[0105] The workflow designer is a tool for creating, editing and managing workflows, implemented through a graphical user interface (GUI), which allows users to design workflows by dragging and dropping and connecting different tasks, activities and decision nodes, thereby simplifying and optimizing business process management;

[0106] Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page;

[0107] Setting the report linked to each node in each display page through a data set definer, and setting the second GU ID of each report;

[0108] The data set definer is a visual definer based on SQL statements. It is used to query and calculate the data required for the report. The defined data set is bound using Excel software, and the prepared report is uploaded to the report library. The report template is based on the jx ls binding expression rules, and the parsing is performed by the jx ls parsing engine.

[0109] The report is set by using an ETL tool to include at least a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan; the ETL tool adopts Kettle.

[0110] The first emergency plan encryption transmission module is specifically used for:

[0111] After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

[0112] The first HMAC value is obtained by performing HMAC calculation on the first emergency plan, and the first emergency plan and the first HMAC value are encrypted by the AES256 algorithm to obtain the first-level encrypted data. The number 1 and the letter l in the first-level encrypted data are swapped to generate the second-level encrypted data, and the second-level encrypted data is encrypted into the first encrypted plan by the IDEA algorithm. The first encrypted plan is sent to the supervision server through the TLS protocol. Subsequently, the integrity of the first emergency plan can be checked through the first HMAC value. If the corresponding encryption algorithm or data transformation rule is unknown, the first encryption plan cannot be cracked. The TLS protocol is a secure transmission protocol, and at least 5 security measures (HMAC calculation, AES256 algorithm, character swapping, IDEA algorithm, and TLS protocol) are taken before and after.

[0113] By evaluating the first emergency plan through big data technology, such as cost-effectiveness and risk assessment, we can quickly determine the rationality of the first emergency plan and make timely adjustments to the unreasonable aspects, thereby greatly improving the efficiency of engineering safety emergency management.

[0114] The second emergency plan encryption transmission module is specifically used for:

[0115] The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value;

[0116] The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan.

[0117] The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

[0118] The second emergency plan is calculated by HMAC to obtain the second HMAC value, the second emergency plan and the second HMAC value are encrypted by the 3DES algorithm to obtain the first encrypted data, the number 2 and the letter z in the first encrypted data are swapped to generate the second encrypted data, the secondary encrypted data is encrypted into the second encrypted plan by the RC2 algorithm, and the second encrypted plan is sent to the owner's server through the TLS protocol; subsequently, the second emergency plan can be checked for integrity by the second HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the second encrypted plan cannot be cracked, and the TLS protocol is a secure transmission protocol, and at least 5 security measures are taken before and after (HMAC calculation, 3DES algorithm, character swapping, RC2 algorithm, TLS protocol).

[0119] The engineering safety emergency management module is specifically used for:

[0120] The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value;

[0121] The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

[0122] Electronic signatures are added to the approved emergency plans through the supervision server and the owner's server to facilitate later traceability and quickly verify the legality of the emergency plans.

[0123] In specific implementation, different QR codes can be set based on different types of the third emergency plan, and the QR codes can be pasted in corresponding positions. For example, for emergency plans for personnel, equipment or work sites, personnel codes, equipment codes or work site codes can be set, and different QR codes are associated with different first GUIDs. During engineering safety emergency management, the staff can jump to the corresponding display page by scanning the QR code, and fill in the corresponding data through the report on the display page and submit it.

[0124] In summary, the advantages of the present invention are:

[0125] 1. After the construction server verifies the emergency plan formulation instruction sent by the owner's server, the emergency management process is created through the workflow designer, the display page of the emergency management process is created through the page designer, the report linked to each node in the display page is set through the data set definer, and the data processing flow of the report is set through the ETL tool, and then the first emergency plan is generated. After evaluating the first emergency plan, it is encrypted into the first encrypted plan and sent to the supervision server; then the supervision server decrypts the first encrypted plan to obtain the first emergency plan, reviews the first emergency plan to generate the second emergency plan, encrypts the second emergency plan into the second encrypted plan and sends it to the owner's server; finally, the owner's server decrypts the second encrypted plan to obtain the second emergency plan, and evaluates the first emergency plan. The second emergency plan is reviewed to generate a third emergency plan, and a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code; that is, during the generation of the emergency plan, the construction server uses big data technology to evaluate it, and after the evaluation is passed, it is reviewed by the supervision server and the owner's server in turn to ensure the rationality of the emergency plan, so that when an emergency occurs, it can respond quickly according to the emergency management process of the emergency plan; by setting a QR code to link the emergency plan, on-site staff can quickly access the display page through the QR code, quickly upload relevant on-site data through the report on the display page, and the formatted display page can also ensure the standardization of data collection, which ultimately greatly improves the reliability and efficiency of engineering safety emergency management.

[0126] 2. Send emergency plan formulation instructions carrying the sender, timestamp and hash value to the construction server through the TLS protocol. Subsequently, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the sender. Three layers of security measures are taken before and after to prevent the construction server from performing related operations based on illegal emergency plan formulation instructions, which greatly improves the security of engineering safety emergency management.

[0127] 3. Perform HMAC calculation on the first emergency plan to obtain the first HMAC value, encrypt the first emergency plan and the first HMAC value through the AES256 algorithm to obtain the first-level encrypted data, swap the number 1 and the letter l in the first-level encrypted data to generate the second-level encrypted data, encrypt the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and send the first encrypted plan to the supervision server through the TLS protocol; subsequently, the integrity of the first emergency plan can be checked through the first HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the first encryption plan cannot be cracked, and the TLS protocol is a secure transmission protocol. At least 5 security measures (HMAC calculation, AES256 algorithm, character swap, IDEA algorithm, TLS protocol) have been taken.

[0128] 4. By evaluating the first emergency plan through big data technology, we can quickly determine the rationality of the first emergency plan and make timely adjustments to the unreasonable aspects, thereby greatly improving the efficiency of engineering safety emergency management.

[0129] 5. Perform HMAC calculation on the second emergency plan to obtain the second HMAC value, encrypt the second emergency plan and the second HMAC value through the 3DES algorithm to obtain the first encrypted data, swap the number 2 and the letter z in the first encrypted data to generate the second encrypted data, encrypt the secondary encrypted data into the second encrypted plan through the RC2 algorithm, and send the second encrypted plan to the owner's server through the TLS protocol; subsequently, the second emergency plan can be integrity checked through the second HMAC value. If the corresponding encryption algorithm or data transformation rule is not known, the second encrypted plan cannot be cracked, and the TLS protocol is a secure transmission protocol. At least 5 security measures (HMAC calculation, 3DES algorithm, character swapping, RC2 algorithm, TLS protocol) have been taken.

[0130] 6. Add electronic signatures to the approved emergency plans through the supervision server and the owner's server to facilitate later traceability and quickly verify the legality of the emergency plans.

[0131] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A digital engineering safety emergency management method, characterized by: The steps include: Step S1, the construction server receives the emergency plan formulation instruction sent by the owner server, and verifies the emergency plan formulation instruction; Step S2: The construction server creates an emergency management process through a workflow designer, creates a display page of the emergency management process through a page designer, sets reports linked to each node in the display page through a data set definer, sets a data processing flow of the report through an ETL tool, and generates a first emergency plan; Step S3: After evaluating the first emergency plan, the construction server encrypts the first emergency plan into a first encrypted plan, and sends the first encrypted plan to the supervision server; Step S4: the supervision server decrypts the received first encrypted plan to obtain a first emergency plan, reviews the first emergency plan to generate a second emergency plan, encrypts the second emergency plan into a second encrypted plan, and sends the second encrypted plan to the owner server; Step S5: the owner server decrypts the received second encrypted plan to obtain a second emergency plan, reviews the second emergency plan to generate a third emergency plan, sets a QR code linked to the third emergency plan, and performs engineering safety emergency management based on the QR code; The step S1 is specifically as follows: The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp. The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

2. A digital engineering safety emergency management method as claimed in claim 1, characterized in that: The step S2 is specifically as follows: The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node; Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page; Setting the report linked to each node in each display page through a data set definer, and setting the second GUID of each report; The report is set by using an ETL tool to at least include a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan.

3. A digital engineering safety emergency management method as claimed in claim 1, characterized in that: The step S3 is specifically as follows: After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

4. A digital engineering safety emergency management method as claimed in claim 1, characterized in that: The step S4 is specifically as follows: The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value; The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan. The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

5. A digital engineering safety emergency management method as claimed in claim 1, characterized in that: The step S5 is specifically as follows: The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value; The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

6. A digital engineering safety emergency management system, characterized by: Includes the following modules: The emergency plan formulation instruction verification module is used for the construction server to receive the emergency plan formulation instruction sent by the owner's server and verify the emergency plan formulation instruction; The first emergency plan generation module is used for the construction server to create an emergency management process through a workflow designer, create a display page of the emergency management process through a page designer, set a report linked to each node in the display page through a data set definer, and set a data processing flow of the report through an ETL tool, thereby generating a first emergency plan; A first emergency plan encryption transmission module, configured for the construction server to encrypt the first emergency plan into a first encrypted plan after evaluating the first emergency plan, and to send the first encrypted plan to the supervision server; A second emergency plan encryption transmission module, used for the supervision server to decrypt the first encrypted plan received to obtain the first emergency plan, review the first emergency plan to generate a second emergency plan, encrypt the second emergency plan into a second encrypted plan, and send the second encrypted plan to the owner server; The engineering safety emergency management module is used for decrypting the second encrypted plan received by the owner server to obtain a second emergency plan, reviewing the second emergency plan to generate a third emergency plan, setting a QR code linked to the third emergency plan, and performing engineering safety emergency management based on the QR code; The emergency plan formulation instruction verification module is specifically used for: The owner's server sends an emergency plan formulation instruction to the construction server through the TLS protocol, which carries the sender, timestamp, and hash value. The hash value is obtained by hashing the sender and timestamp. The construction server receives the emergency plan formulation instruction in real time, parses the emergency plan formulation instruction to obtain the sender, timestamp and hash value, performs integrity verification on the sender and timestamp through the hash value, performs timeliness verification through the timestamp, and then performs legality verification through the sender.

7. A digital engineering safety emergency management system as claimed in claim 6, characterized in that: The first emergency plan generation module is specifically used for: The construction server uses the graphical user interface of the workflow designer to create each node of the emergency management process in an interactive manner of dragging and dropping, set the logical relationship between each node, set the participating role and input and output content of each node; Creating a display page of the emergency management process through a page designer, arranging the display content of each display page, and setting a first GUID of each display page; Setting the report linked to each node in each display page through a data set definer, and setting the second GUID of each report; The report is set by using an ETL tool to at least include a data processing flow of data extraction, data conversion and data loading, thereby generating a first emergency plan.

8. A digital engineering safety emergency management system as claimed in claim 6, characterized in that: The first emergency plan encryption transmission module is specifically used for: After the construction server evaluates the first emergency plan through big data technology, it performs HMAC calculation on the first emergency plan to obtain a first HMAC value, encrypts the first emergency plan and the first HMAC value through the AES256 algorithm to obtain first-level encrypted data, swaps the number 1 and the letter l in the first-level encrypted data to generate second-level encrypted data, encrypts the second-level encrypted data into the first encrypted plan through the IDEA algorithm, and sends the first encrypted plan to the supervision server through the TLS protocol.

9. A digital engineering safety emergency management system as claimed in claim 6, characterized in that: The second emergency plan encryption transmission module is specifically used for: The supervision server receives the first encrypted plan in real time, decrypts the first encrypted plan into secondary encrypted data through the IDEA algorithm, swaps the number 1 and the letter 1 in the secondary encrypted data to generate primary encrypted data, decrypts the primary encrypted data through the AES256 algorithm to obtain the first emergency plan and the first HMAC value, and performs integrity verification on the first emergency plan through the first HMAC value; The supervision server reviews the first emergency plan that has passed the integrity check. If the review fails, a supervision review failure notification is generated and sent to the construction server. If the review passes, the supervision electronic signature is added to the first emergency plan to generate a second emergency plan. The supervision server performs HMAC calculation on the second emergency plan to obtain a second HMAC value, encrypts the second emergency plan and the second HMAC value through the 3DES algorithm to obtain first encrypted data, swaps the number 2 and the letter z in the first encrypted data to generate second encrypted data, encrypts the secondary encrypted data into a second encrypted plan through the RC2 algorithm, and sends the second encrypted plan to the owner server through the TLS protocol.

10. A digital engineering safety emergency management system as claimed in claim 6, characterized in that: The engineering safety emergency management module is specifically used for: The owner server receives the second encrypted plan in real time, decrypts the second encrypted plan into second encrypted data using the RC2 algorithm, swaps the number 2 and the letter z in the second encrypted data to generate first encrypted data, decrypts the first encrypted data using the 3DES algorithm to obtain the second emergency plan and the second HMAC value, and performs integrity verification on the second emergency plan using the second HMAC value; The owner's server reviews the second emergency plan that has passed the integrity check. If the review fails, an owner review failure notification is generated and sent to the construction server. If the review passes, the owner's electronic signature is added to the second emergency plan to generate a third emergency plan, a QR code linking to the third emergency plan is set, and engineering safety emergency management is performed based on the QR code.

Images