HSE online monitoring and field verification linkage supervision method and system

Abstract

The application relates to an industrial safety informatization technology and discloses an HSE online monitoring and on-site verification linkage supervision method and system. The method verifies the state, time and verification evidence of on-site verification feedback, obtains a first access control result, matches and verifies the feedback indicated business object and organization with original source business records when the result is allowed, obtains a second access control result, determines an HSE source system to be accessed according to a source system identifier only when both the two access control results are allowed, and executes source data acquisition based on the source record identifier; when the acquisition is successful, the current source business record is obtained, the target verification rule hit when generating the online problem record is re-executed, the problem state is updated according to the rule hit result, and when the acquisition is abnormal, the to-be-verified is kept and the target verification rule is not executed. The application can prevent invalid or mismatched feedback from triggering the source, and can avoid misjudging the acquisition abnormality as the original problem being eliminated.

Description

Technical Field

[0001] This invention relates to the fields of computer data processing and industrial safety information technology, and in particular to a method and system for online monitoring and on-site verification of health, safety and environmental management. Background Technology

[0002] Enterprises can deploy different health, safety, and environmental management systems, such as those for non-routine operations, major hazard sources, personnel location, dual prevention, contractor management, personnel alarm management, and risk monitoring. These are referred to as HSE systems. Different HSE systems store business data such as work tickets, safety measures, approvals, alarms, personnel qualifications, inspections, and risk control separately, and may use different business primary keys, organizational fields, status fields, and data access methods.

[0003] The existing HSE supervision method checks the aforementioned business data according to preset rules. When problems such as non-standard work order entries, failure to implement safety measures, unresolved alarm timeouts, expired personnel certificates, or incomplete inspection tasks are found, a problem record is generated, and the problem is then assigned to on-site personnel for handling. On-site personnel can change the problem status, fill in the verification results, and upload photos or other attachments through the existing work order system, inspection system, or HSE source system.

[0004] In this type of processing, the on-site feedback data and the actual business data in the HSE source system are generated by different terminals and different processing procedures. A change in the problem status to "rectified" or "attachments uploaded" does not necessarily indicate that the feedback corresponds to the correct work order, alarm record, or company, nor does it necessarily mean that the original problem conditions in the HSE source system have been eliminated. If on-site feedback triggers access to the source system without verification, it may not only result in invalid data acquisition operations but may also allow data from incorrect business objects or other companies to enter the subsequent review process.

[0005] Even if the feedback is complete, there may still be discrepancies between the feedback content and the status of the source business record. For example, the on-site feedback may indicate that the alarm has been handled, but the handling status of the source alarm record may still be "unhandled"; the on-site feedback may indicate that safety measures have been implemented, but the safety measure status in the source work order may remain unchanged. If the source system is temporarily inaccessible, the source record cannot be located, or the acquisition process fails, and if the difference between data acquisition anomalies and rule mismatches is not distinguished, the "current record not obtained" error may be converted to "the original problem condition has been eliminated".

[0006] Therefore, it is necessary to establish a computable access control relationship between online issues, on-site verification feedback, and HSE source business records, so that invalid or mismatched on-site feedback cannot trigger the data acquisition process of the corresponding HSE source system, and after access is allowed, distinguish between successful and abnormal acquisition of source data, and only execute the original verification rules for the current source business records that are successfully acquired. Summary of the Invention

[0007] To address the aforementioned problems in the prior art, the present invention aims to provide a method and system for joint supervision of HSE online monitoring and on-site verification. In a cross-system environment where on-site verification feedback data and HSE source business data are generated asynchronously, this method prevents invalid or incorrectly targeted on-site verification feedback from triggering access to HSE source system data, and avoids incorrectly converting the source system inaccessibility, source record not located, or source business record reading failure into the original problem condition being eliminated.

[0008] To address the aforementioned technical problems, in a first aspect, this invention provides a method for integrated online HSE monitoring and on-site verification supervision, comprising:

[0009] Obtain online issue records and their associated on-site verification feedback generated by the target verification rules of the source business records of the HSE source system. The online issue records include the source system identifier and the source record identifier.

[0010] Based on the feedback status, feedback time, and verification evidence information from the on-site inspection, the validity of the feedback data is verified to obtain the first access gating result;

[0011] When the first access gating result allows access, the business object and organization association information indicated by the on-site verification feedback are matched and verified with the business object and organization association information in the original source business record corresponding to the online problem record to obtain the second access gating result;

[0012] Access is only permitted if both the first and second access gating results allow it. The HSE source system to be accessed is determined based on the source system identifier in the online problem log, and source data retrieval is performed from the determined HSE source system based on the source log identifier, resulting in a source data retrieval result indicating successful or abnormal retrieval.

[0013] The review process is performed based on the source data acquisition results. Specifically, when the source data acquisition result indicates successful acquisition, the current source business record corresponding to the source record identifier is obtained. The target verification rule that was hit when generating the online problem record is re-executed on the current source business record to obtain the rule hit result. If the rule hit result indicates that the target verification rule is no longer hit, the online problem record is updated to the rectification review passed status. If the rule hit result indicates that the target verification rule is still hit, the online problem record is kept in the pending verification status. If the source data acquisition result indicates an acquisition anomaly, the online problem record is kept in the pending verification status, and the target verification rule is not executed.

[0014] In some implementations, the online issue log includes an issue log identifier, a source system identifier, a source record identifier, a business object identifier, an issue category identifier, and a discovery time. The combination of the source system identifier and the source record identifier is used to distinguish source business records from different HSE source systems. The verification rule set stores the correspondence between issue category identifiers, applicable source systems, applicable business objects, judgment conditions, and rule association fields; within the same applicable source system and applicable business object scope, each issue category identifier uniquely corresponds to one target verification rule.

[0015] In some implementations, the validation of feedback data includes: determining whether the feedback status has changed from the status to be verified according to a preset time, determining whether the feedback time is later than the discovery time, and determining whether the verification evidence information meets the evidence existence conditions corresponding to the problem classification identifier. If all judgments pass, the first access gating result is determined as allowed access; if any judgment fails, the first access gating result is determined as prohibited access, the failed validation item is recorded, and the on-site verification feedback is prevented from triggering the acquisition of the current source business record for the HSE source system.

[0016] In some implementations, the on-site verification feedback is associated with the work order approval record corresponding to the business object identifier; the verification evidence information includes the attachment identifier and the review result field in the work order approval record, and the evidence existence conditions include that the attachment identifier is not empty and the review result field is filled.

[0017] In some implementations, the matching verification includes: reading the original source business record from the saved source business data based on the source system identifier and the source record identifier; comparing the feedback business object identifier and feedback organization association information in the on-site verification feedback with the business object identifier and organization association information in the original source business record, respectively. If the original source business record is not read or any comparison result is inconsistent, the second access gating result is determined as access prohibited and the acquisition of the current source business record is blocked; if the original source business record is read and all comparison results are consistent, the second access gating result is determined as access permitted.

[0018] In some implementations, only when both the first and second access gating results are allowed access, is the target source data acquisition process determined from a pre-configured set of source data acquisition processes based on the source system identifier. Record location parameters adapted to the target source data acquisition process are determined based on the source record identifier, and record location and reading are performed using these parameters to obtain the current source business record upon successful acquisition. The target source data acquisition process includes one of the following: a database reading process, an interface call process, or a browser automation process. The record location parameter is the source record identifier itself or a business object identifier associated with the source record identifier.

[0019] In some implementations, if the current source service record is not obtained in a single source data acquisition, the source data acquisition is performed again according to a preset number of retries. If the current source service record is still not obtained after the preset number of retries, the acquisition exception type represented by the source data acquisition result is determined as source system inaccessible, source record not located, or source service record reading failure, depending on whether the exception occurred in the processing stage of source system connection, source record location, or source record reading. The acquisition exception type and acquisition time are recorded.

[0020] In some implementations, the verification evidence information includes an attachment identifier, and the validity verification of feedback data also includes attachment reuse verification. Attachment reuse verification includes: when the attachment identifier is not empty, querying whether the attachment identifier is associated with other online issue records besides the current online issue record; when the attachment identifier is also associated with at least one other online issue record, marking the on-site verification feedback as evidence reuse, determining the first access gating result as access prohibited, and preventing the acquisition of the current source business record.

[0021] Secondly, this invention provides an HSE online monitoring and on-site verification linkage supervision system, wherein the system is communicatively connected to at least one HSE source system, including:

[0022] The issue feedback association module is used to obtain online issue records and their associated on-site verification feedback generated by the source business records of the HSE source system hitting the target verification rules. The online issue records include the source system identifier and the source record identifier.

[0023] The feedback gating module is used to perform validity verification of feedback data based on the feedback status, feedback time, and verification evidence information of the on-site verification feedback, and obtain the first access gating result;

[0024] The object matching module is used to match and verify the business object and organization association information indicated by the on-site verification feedback with the business object and organization association information in the original source business record corresponding to the online problem record when the first access gating result allows access, so as to obtain the second access gating result;

[0025] The source verification module is used only when both the first and second access gating results allow access. It determines the HSE source system to be accessed based on the source system identifier in the online problem record, and performs source data retrieval from the determined HSE source system based on the source record identifier. This yields a source data retrieval result indicating successful or abnormal retrieval. Verification processing is then performed based on the source data retrieval result. Specifically, if the source data retrieval result indicates successful retrieval, the current source business record corresponding to the source record identifier is retrieved, and the target verification rules hit when generating the online problem record are re-executed on the current source business record to obtain a rule hit result. If the source data retrieval result indicates abnormal retrieval, the target verification rules are not executed.

[0026] The status update module is used to update the online issue record to the rectification review passed status when the rule hit result is obtained from the source review module. If the rule hit result indicates that the target verification rule is no longer hit, the online issue record is kept in the pending verification status. When the source data acquisition result indicates an acquisition anomaly, the online issue record is kept in the pending verification status.

[0027] Thirdly, the present invention provides an electronic device, including a processor and a memory, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the HSE online monitoring and on-site verification linkage supervision method described in any embodiment of the first aspect.

[0028] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the HSE online monitoring and on-site verification linkage supervision method described in any embodiment of the first aspect.

[0029] Fifthly, the present invention provides a computer program product, including a computer program, which, when executed by a processor, implements the HSE online monitoring and on-site verification linkage supervision method described in any embodiment of the first aspect.

[0030] Compared to methods that rely solely on on-site feedback or manual acceptance results to close the problem loop, this invention performs feedback data validity verification based on the feedback status, feedback time, and verification evidence information from on-site inspections to obtain a first access gating result. When the first access gating result allows access, the business object and organizational association information indicated in the on-site inspection feedback are matched and verified against the corresponding information in the original source business record to obtain a second access gating result. The first and second access gating results jointly control whether access to the HSE source system is granted. Only when both access gating results allow access does this invention determine the HSE source system to be accessed based on the source system identifier, and perform source data acquisition based on the source record identifier to obtain the source data acquisition result. Then, a review process is performed based on the source data acquisition result: if acquisition is successful, the current source business record is obtained, and the target verification rules hit when generating the online problem record are re-executed, updating the problem status according to the rule hit result; if acquisition is abnormal, the online problem record remains in a pending verification status, and the target verification rules are not executed. Therefore, before performing database reads, API calls, or browser automation operations, it is possible to prevent on-site verification feedback that is invalid, has an incorrect feedback object, or has inconsistent organizational affiliation from triggering source data acquisition. Furthermore, it separates the acquisition anomalies during the source system connection, source record location, and located record reading stages from the judgment results of whether the rule still matches or does not match, avoiding the substitution of the conclusion that the target verification rule does not match with the absence of the current source business record. This ensures that the status update of the online problem record is based on the current source business data and the judgment conditions used when the original problem was generated, thereby reducing invalid source system access, erroneous object data participating in the re-judgment, and error status updates. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0032] Figure 1 This is a flowchart illustrating the HSE online monitoring and on-site verification linkage supervision method in one embodiment of the present invention;

[0033] Figure 2 This is a schematic diagram illustrating the relationship between online problem records, on-site verification feedback, original source business records, source data acquisition results, current source business records, target verification rules, and review processing results in one embodiment of the present invention.

[0034] Figure 3 This is a schematic diagram of the structure of an HSE online monitoring and on-site verification linkage supervision system in one embodiment of the present invention;

[0035] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention.

[0036] Explanation of reference numerals in the attached diagram: 100-Linked monitoring system, 110-Problem feedback association module, 120-Feedback gating module, 130-Object matching module, 140-Source verification module, 150-Status update module, 200-HSE source system, 300-Field terminal, 400-Electronic device, 410-Processor, 420-Memory, 430-Communication interface, 440-Communication bus. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described below with reference to the accompanying drawings. These embodiments are used to illustrate the present invention and are not intended to limit the scope of protection of the present invention. Where there is no technical contradiction, technical features in different embodiments can be combined with each other.

[0038] The HSE source system referred to in this application refers to an existing information system, business subsystem, or corresponding data source capable of providing health, safety, and environmental management business data. An HSE source system can be any one of the following: non-routine operation system, major hazard source system, personnel location system, dual prevention system, contractor management system, personnel alarm management system, and risk monitoring system, or may include multiple of these.

[0039] Online issue logs refer to issue data objects generated after a source business record matches the target verification rules. Original source business records refer to the source business record corresponding to the online issue log or the original data saved for that record. Current source business records refer to business records obtained again from the corresponding HSE source system after the on-site verification feedback has passed the gating, and which correspond to the source record indicated by the online issue log. The data source of current source business records is independent of the verification feedback submitted by on-site personnel.

[0040] Organizational association information indicates the enterprise or organization to which the source business record and on-site feedback belong, and may include one or more of the following: enterprise name, second-level unit, and organization code. Business object identifier indicates the business object corresponding to the online issue, and may be a work ticket number, alarm record number, personnel identifier, risk object identifier, inspection task identifier, or contractor identifier; feedback business object identifier indicates the business object referenced in the on-site verification feedback. Issue classification identifier indicates the rule category that triggered the issue, such as inadequate safety measures, unhandled alarm timeouts, or expired certificates.

[0041] Target verification rules refer to the executable judgment rules that are triggered when generating corresponding online issue records. The set of verification rules pre-stores the correspondence between issue classification identifiers, applicable source systems, applicable business objects, executable judgment conditions, and rule-related fields. Within the same applicable source system and applicable business object, each issue classification identifier points to only one target verification rule. When target verification rules with the same semantics use different fields in different HSE source systems, the corresponding rule-related fields are stored in the correspondence, without changing the judgment semantics of the target verification rule. Therefore, the initial issue identification and rectification review read the rule-related fields with the same semantics and use the same judgment conditions, instead of using separate pass conditions unrelated to the original issue for the review.

[0042] Example 1: A method for joint supervision of HSE online monitoring and on-site inspection

[0043] like Figure 1 and Figure 2 As shown, this embodiment provides a method for linking HSE online monitoring and on-site verification, including steps S101 to S109.

[0044] S101, Obtain online issue records. Online issue records can be generated by the rule engine after reading HSE source business data and executing verification rules, or they can be generated by a security monitoring system that can provide the same structured issue information.

[0045] In one specific implementation, the rule engine reads work tickets, alarms, personnel locations, or other HSE business tables via a database connection, executes verification rules one by one, and writes the issues that match the rules into an online issue table. The online issue record at least stores the issue record identifier, source system identifier, source record identifier, business object identifier, issue category identifier, organizational association information, and discovery time. The source system identifier can be stored in the `system_name` field, the source record identifier can be stored in the `source_id` field, and the organizational association information can be represented by one or more fields from `company_name`, `second_level_unit`, and `org_code`. For each combination of issue category identifier, applicable source system, and applicable business object, the verification rule set stores the corresponding rule association fields, comparison relationships, and target status or threshold, enabling the combination to uniquely determine the executable judgment rule actually matched when the online issue record is generated.

[0046] Taking a work ticket as an example, the source record identifier can be the record identifier of the work ticket master record, and the work ticket number can be stored as a business object identifier in a structured field, or it can be obtained by parsing from the problem description. Taking an alarm as an example, the source record identifier can be the alarm record identifier, and the alarm number can be used as a business object identifier. Even if different source systems have source record identifiers with the same value, the combination of the source system identifier and the source record identifier can still be used to distinguish the corresponding records.

[0047] Online issue logs can be generated incrementally. For example, the rule engine can store the processed `latest_id` and only process source business records added or updated after that identifier. Alternatively, it can determine whether the same issue has already been generated based on a combination of issue log identifier, source system identifier, source record identifier, and issue category identifier, thereby reducing the duplication of the same source issue.

[0048] S102, Generate on-site verification tasks based on online problem records. The monitoring and processing device can create tasks in existing work order systems, hazard systems, inspection systems, or HSE source systems, without requiring the development of a separate application interface for on-site personnel. On-site verification tasks must at least be associated with a problem record identifier and may also include a problem description, problem classification, risk level, rectification suggestions, feedback material requirements, and review requirements.

[0049] Problem record identifiers can be directly written into the task field of the on-site verification task, or the correspondence between problem record identifiers and task identifiers can be stored in the task association table. After the task is created, it is provided to the corresponding personnel through existing system messages, to-do items, or on-site terminals. On-site personnel use the existing HSE terminals to complete the verification, rectification, photography, and reporting.

[0050] S103, Receive on-site verification feedback. The regulatory processing device associates the on-site verification feedback with the online issue record based on the issue record identifier or task association record. The on-site verification feedback may directly include the feedback business object identifier and feedback organization association information, or the above information may be obtained from the task record corresponding to the feedback. The regulatory processing device also obtains the issue status, feedback update time, and verification evidence information associated with the feedback.

[0051] In one implementation of a work order, the issue status is stored in the `issue_status` field, the feedback update time is stored in the `update_time` field, the attachment identifier is stored in the `file_id` field, and the review result in the approval record is stored in the `verify_result` field. The field names are specific database implementation examples; using other fields with the same semantics does not affect the processing relationships in this embodiment.

[0052] S104, Perform basic validation of the feedback data. For general issues, at least determine whether the issue status has changed relative to the status to be verified, whether the feedback update time is later than the issue discovery time, and whether the evidence information meets the evidence existence conditions; the evidence existence conditions can be that the attachment identifier is not empty, or that the verification result field corresponding to the issue type has a valid value.

[0053] If all three basic judgments mentioned above pass, the basic verification result of the feedback data validity is determined to be passed; if any one of the basic judgments fails, the basic verification result is determined to be failed. Therefore, changes in the problem status, the order of feedback time, and the existence of verification evidence together constitute the basic prerequisites for accessing the source system, rather than the source data acquisition process being directly initiated by a single status value submitted by on-site personnel.

[0054] In the implementation where on-site verification feedback is associated with a work order approval record corresponding to the business object identifier of the online issue record, four basic checks can be performed sequentially: whether the issue_status has changed from pending verification to rectification in progress or already rectified, whether the update_time is later than the discovery_time, whether the file_id is not empty, and whether the verify_result in the work order approval record has been filled. If any one of them fails, the basic check result is determined to be failed, and the failed project code, failure reason, and check time are saved; if all four of the above checks pass, the basic check result is determined to be passed.

[0055] When the on-site verification feedback is not associated with the work order approval record corresponding to the business object identifier in the online problem record, the existence of the verify_result field is not mandatory. Instead, basic validation of the feedback data validity is performed based on the status, time, and verification evidence that the corresponding business object can provide. For example, the verification evidence for alarm issues can be the alarm handling record or attachments, and the verification evidence for personnel certificate issues can be the updated certificate materials. For alarm issues, the basic validation result can be determined as passed when the problem status changes relative to the status to be verified, the feedback update time is later than the problem discovery time, and the alarm handling record or attachments exist. For personnel certificate issues, the basic validation result can be determined as passed when both the above status and time conditions are met and updated certificate materials exist. In this way, the verification result field in the work order approval record will not be mistakenly regarded as a field that must be present for all HSE issues.

[0056] S105: Generate a first access gating result based on the feedback data validity verification result, and optionally perform attachment reuse verification. If the basic verification result fails, the first access gating result is determined to be access prohibited, the online problem record remains in a pending verification state, supplementary feedback is output to the field terminal or existing work order system, and the acquisition of the current feedback trigger source data is prevented. If the basic verification result passes, if attachment reuse verification is not enabled, the first access gating result is determined to be access allowed; if attachment reuse verification is enabled, attachment reuse verification is added as an additional item to the feedback data validity verification, and if file_id is not empty, it is queried whether file_id is still associated with other online problem records besides the current online problem record. If the file_id is associated with at least one other online issue record, the current feedback is marked as evidence reuse, the first access gating result is determined as access prohibited, preventing access to the current source business record, and requiring resubmission of verification evidence for the current online issue; if the file_id is empty, the attachment reuse query is not executed, and the first access gating result is determined as access allowed; if the file_id is not empty and is not associated with other online issue records, the first access gating result is determined as access allowed. This verification uses attachment identifiers for association and does not require reading or recognizing the specific image content in the attachments.

[0057] S106, Perform feedback object matching verification and generate a second access gating result. After the first access gating result indicates that access is allowed, read the original source business record corresponding to the online problem record from the saved source business data based on the source system identifier and source record identifier. Compare the feedback business object identifier with the business object identifier in the original source business record, and compare the feedback organization association information with the organization association information in the original source business record.

[0058] For example, the `permit_no` referenced in the on-site feedback is compared with the `permit_no` in the original work order record, along with `company_name` and `second_level_unit`. If the original source business record is not found or any necessary field is inconsistent, the second access gating result is determined to be access prohibited, the original record is recorded as unavailable or mismatched, the feedback is marked as a mismatched feedback object, the online problem record is kept in a pending verification state, and the target source data acquisition process is not invoked; if the original source business record exists and all necessary fields are consistent, the second access gating result is determined to be access allowed. Thus, feedback referencing incorrect work orders or cross-enterprise chained issues can be excluded before re-accessing the HSE source system.

[0059] S107, Controlled return to source and obtaining source data acquisition results. Only when both the first access gating result and the second access gating result are access allowed, the HSE source system to be accessed is determined according to the source system identifier, and the target source data acquisition process corresponding to the HSE source system is determined from the pre-configured set of source data acquisition processes; the record positioning parameters adapted to the target source data acquisition process are determined according to the source record identifier, and source data acquisition is performed from the determined HSE source system through the target source data acquisition process to obtain a source data acquisition result indicating successful acquisition or acquisition error.

[0060] A pre-configured set of source data acquisition processes is used to store the correspondence between different HSE source systems and their data access methods. Each correspondence includes at least a source system identifier, a data access method, the connection configuration required to access the corresponding HSE source system, a location parameter mapping for generating record location parameters based on the source record identifier, and rule association fields to be returned. The monitoring processing device searches for the corresponding correspondence using the source system identifier in the online problem record, determines the source record identifier itself or the business object identifier associated with the source record identifier as the record location parameter according to the location parameter mapping, and initiates the database read, interface call, or browser automation process indicated by the correspondence. Each source data acquisition process outputs the acquisition status; when acquisition is successful, it also outputs the current source business record, and when acquisition fails, it outputs the corresponding exception type. Thus, the internal operations of different data access methods may differ, but they all form source data acquisition results with the same semantics, and the current source business record is only provided to subsequent review when acquisition is successful.

[0061] For example, when the online issue record's `system_name` points to a non-routine work system, a database read procedure can be selected. Based on the connection configuration, this accesses the MySQL database storing work ticket data, uses `source_id` as the record location parameter, and reads the corresponding work ticket record and the status fields required for review from `hse_work_permit`. When `system_name` points to an HSE source system that provides data through an existing page, a browser automation procedure can be selected. This first retrieves the corresponding business object identifier from the saved source business data based on `source_id`, then uses that business object identifier as the record location parameter, and executes a query to read the current record in an authorized browser session. The above examples correspond to database read and browser access methods, respectively, and different HSE source systems are not required to use the same internal access operations.

[0062] The source data acquisition process can be database reading, API calls, or browser automation. In one browser implementation, the monitoring processing device, under user authorization, connects to an authenticated browser instance via a browser control protocol, utilizes its valid session to access the HSE source system, and performs navigation, querying, opening details, and status reading. This process reuses the authenticated session but does not bypass the HSE source system's authentication or access control. The internal implementation of page recognition and dual-path data acquisition can be provided by independent data acquisition capabilities; this embodiment only utilizes this capability to return the current source business record corresponding to the source record identifier and its acquisition result.

[0063] The target source data acquisition process returns the source data acquisition result. If the current source business record is not obtained in a single source data acquisition, the monitoring and processing device will re-execute the source data acquisition according to the preset number of retries; if the current source business record is still not obtained after the preset number of retries, the acquisition anomaly type represented by the source data acquisition result is determined according to the processing stage in which the anomaly occurred. When successfully accessing the HSE source system, locating the record corresponding to the source record identifier using the record location parameters, and obtaining the fields required by the target verification rule, the source data acquisition result is encoded as successful acquisition. If a connection to the HSE source system cannot be established or no response is received within the access time limit, the source data acquisition result is encoded as acquisition error, and the acquisition error type is determined to be source system inaccessible. If the HSE source system has been accessed but the record corresponding to the source record identifier has not been located using the record location parameters, the source data acquisition result is encoded as acquisition error, and the acquisition error type is determined to be source record not located. If the HSE source system has been accessed and the corresponding record has been located, but no current source business record for review has been formed due to anomalies in record reading, data parsing, or rule association field retrieval, the source data acquisition result is encoded as acquisition error, and the acquisition error type is determined to be source business record reading failure. The above acquisition error types are distinguished according to the three processing stages of connection, record location, and located record reading, and are associated with and saved with the problem record identifier.

[0064] S108. Perform verification processing based on the source data acquisition results. If the source data acquisition result indicates successful acquisition, obtain the current source business record corresponding to the source record identifier; this current source business record originates directly from the HSE source system, not from on-site verification feedback. Based on the source system identifier, the business object identifier in the online issue record, and the issue classification identifier, determine the target verification rule that was triggered when the online issue record was generated from the verification rule set. Read the rule association field corresponding to this rule from the current source business record, re-execute the target verification rule on the current source business record, and obtain the rule hit result. If the source data acquisition result indicates an acquisition anomaly, keep the online issue record in a pending verification state and do not execute the target verification rule.

[0065] For example, when the applicable source system and applicable business objects are determined, the problem category identifier corresponding to the work ticket process problem can be uniquely associated with the rule that determines whether the flow_status has changed to closed; the problem category identifier corresponding to the security measures not implemented problem can be associated with the rule that determines whether the corresponding is_checked has changed from 0 to 1; the problem category identifier corresponding to the alarm not handled problem can be associated with the rule that determines whether the deal_status has changed from 0 to 1; and the problem category identifier corresponding to the certificate expired problem can be associated with the rule that determines whether the certificate validity period has been updated to be later than the verification time. The above field changes are only inputs to different rules, and the final judgment is still based on whether the current source business record continues to meet the same rule conditions when the original problem was generated.

[0066] In one alarm-type implementation, the online problem log stores the source system identifier of the major hazard source system or personnel alarm management system, the source_id corresponding to the alarm record, the alarm number, and the enterprise organization information. After the on-site verification feedback passes the validity verification of the status, time, and alarm handling record or attachment, the alarm number and organization association information in the feedback are matched and verified with the original alarm record. If the matching verification passes, the corresponding data acquisition process is selected according to the source system identifier, and the record location parameters used to query hse_alarm_record are determined according to the source_id. The current alarm record is obtained and deal_status is read. If deal_status is still 0, the original alarm unhandled rule is still hit and remains pending verification; if deal_status has changed from 0 to 1, the rule is no longer hit and can be updated to rectification review passed.

[0067] In one implementation of personnel certificate-related methods, the online issue log stores personnel identifiers, organizational association information, the source_id corresponding to the certificate record, and the certificate expiration issue category. After the on-site verification feedback confirms the validity of the status, time, and updated certificate materials, the personnel identifiers and organizational association information in the feedback are matched and verified against the original certificate record. If the matching verification passes, the corresponding data acquisition process is selected according to the source system identifier, the record location parameters are determined according to the source_id, the current certificate record is obtained, and the certificate validity period is read. If the current certificate validity period is still earlier than the verification time, the certificate expiration rule still applies and remains pending verification; if the certificate validity period has been updated to be later than the verification time, the rule no longer applies, and the status can be updated to "rectification review passed."

[0068] In the successful branch, distinct review results are written to the online issue record based on the rule hit result. If the rule hit result indicates that the current source business record no longer matches the target verification rule, the online issue record is updated to a rectification review passed status; if the rule hit result indicates that the current source business record still matches the target verification rule, the online issue record remains in a pending verification status.

[0069] In the abnormal acquisition branch, when the source data acquisition result indicates an acquisition error and the type of acquisition error is source system inaccessible, source record not located, or source business record read failure, the acquisition error type and acquisition time are recorded, and the online problem record is kept in a pending verification state. Neither the target verification rule is executed, nor is a rule hit result generated. Acquisition error and "acquisition successful but rule no longer hit" are different processing branches and cannot be substituted for each other.

[0070] S109, Save audit data and perform subsequent processing. Audit data may include the first access gating result, the second access gating result, the evidence reuse result, the source data acquisition time, the source data acquisition result, the acquisition anomaly type, the target verification rule, the rule hit result, and the status update time. All of the above data are associated with the issue record identifier to distinguish whether an issue remains pending verification due to invalid feedback data, object mismatch, source data acquisition anomaly, or rule still being hit, or passes review because the acquisition was successful and the rule no longer hit.

[0071] The monitoring and processing device can also summarize the classification, source system, organization, processing time and status of online issues according to a preset cycle, and generate monitoring analysis data or performance statistics data.

[0072] Example 2: A system for linking online monitoring and on-site verification

[0073] like Figure 3 As shown, this embodiment provides an HSE online monitoring and on-site verification linkage supervision system 100, including a problem feedback association module 110, a feedback gating module 120, an object matching module 130, a source verification module 140, and a status update module 150.

[0074] The problem feedback association module 110 is used to obtain online problem records and retrieve corresponding on-site verification feedback based on the problem record identifier or task association record. The problem feedback association module 110 is also used to obtain the source system identifier, source record identifier, business object identifier, and problem classification identifier, as well as the feedback business object identifier, feedback organization association information, problem status, feedback update time, and verification evidence information. In one embodiment, the problem feedback association module 110 also generates on-site verification tasks associated with the problem record identifier in existing HSE work orders, hazard reports, inspections, or source business systems.

[0075] The feedback gating module 120 is used to perform feedback data validity checks on the problem status, feedback update time, and verification evidence information, and generate a first access gating result. It can also add attachment reuse checks as supplementary items for feedback data validity checks. If any check fails, the feedback gating module 120 determines the first access gating result as access prohibited, outputs the specific failed item, and prevents the current feedback from triggering the source review module 140 to access the HSE source system.

[0076] The object matching module 130, when the first access gating result is "access allowed," reads the original source business record from the saved source business data based on the source system identifier and source record identifier. It then matches and verifies the business object identifier and organizational association information referenced in the on-site verification feedback with the corresponding fields in the original source business record, generating a second access gating result. If the original source business record is not read or the necessary fields are inconsistent, the object matching module 130 determines the second access gating result to "access prohibited," outputs an "original record unavailable" result or "mismatched fields," and prevents the current feedback from triggering the return-to-source verification module 140 to access the HSE source system.

[0077] The source verification module 140 is used only when both the first access gating result and the second access gating result are allowed access. It determines the HSE source system to be accessed based on the source system identifier, selects the target source data acquisition process corresponding to the HSE source system from the pre-configured source data acquisition process set that stores the correspondence between the source system identifier, data access method, connection configuration, location parameter mapping and rule association fields, determines the record location parameters that are compatible with the target source data acquisition process based on the source record identifier, and executes source data acquisition from the determined HSE source system through the target source data acquisition process to obtain the source data acquisition result indicating successful acquisition or acquisition error. When the source data acquisition result indicates successful acquisition, the source verification module 140 obtains the current source business record corresponding to the source record identifier, uniquely determines the target verification rule based on the source system identifier, business object identifier, and problem classification identifier, and re-executes the rule on the current source business record to generate a rule hit result; when the source data acquisition result indicates an acquisition anomaly, depending on whether the anomaly occurred during the processing stage of source system connection, source record location, or source business record reading, the acquisition anomaly type indicated by the result is determined as source system inaccessible, source record not located, or source business record reading failed, and the target verification rule is not executed.

[0078] The status update module 150 is used to write the corresponding review processing result based on the rule hit result obtained by the source review module 140: if the rule hit result indicates that the current source business record no longer hits the target verification rule, it is updated to "rectification review passed"; if the rule hit result indicates that the current source business record still hits the target verification rule, it remains in the "pending verification" state. When the source data acquisition result indicates an acquisition anomaly, the status update module 150 saves the acquisition anomaly type and maintains the "pending verification" state, without converting the acquisition anomaly into a rule mishit.

[0079] The modules described above can be implemented by different program components executed by the same processor, or they can be distributed across multiple servers, edge computing devices, or task processing nodes. Module division is used to describe the corresponding functions and data relationships, and does not limit the number of software deployments.

[0080] Example 3: Electronic devices, storage media, and computer program products

[0081] like Figure 4 As shown, this embodiment provides an electronic device 400, including a processor 410, a memory 420, a communication interface 430, and a communication bus 440. The processor 410, memory 420, and communication interface 430 are connected via the communication bus 440. The memory 420 is used to store computer programs, and can also store online problem records, task association records, verification rules, access gating results, source system connection configurations, source data acquisition results, acquisition anomaly types, and audit records. When the processor 410 executes the computer program, it implements the aforementioned feedback data validity verification, feedback object matching verification, source system access control, source data acquisition result generation, acquisition anomaly type determination, target verification rule review, and problem status update. The communication interface 430 is used to exchange data with at least one of the HSE source system, existing work order system, and field terminal.

[0082] This embodiment also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the aforementioned method. The computer-readable storage medium may be a read-only memory, random access memory, magnetic disk, optical disk, flash memory, solid-state memory, or other non-transitory medium capable of storing program code.

[0083] This embodiment also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned method.

[0084] Those skilled in the art should understand that, without changing the technical processing relationship of "feedback data gating - source object matching and verification - controlled return to source and obtaining source data acquisition results - entering the review branch according to the source data acquisition results - re-judgment according to the same rules - result writing", the specific triggering time, field name, source data acquisition method and module deployment method of each step can be adjusted according to the actual structure of the HSE source system.

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

Claims

1. A method for linking online HSE monitoring with on-site verification, characterized in that, include: Obtain online problem records and their associated on-site verification feedback generated by the source business records of the HSE source system hitting the target verification rules. The online problem records include the source system identifier and the source record identifier. Based on the feedback status, feedback time, and verification evidence information from the on-site verification, the validity of the feedback data is validated to obtain the first access gating result; When the first access gating result allows access, the business object and organization association information indicated by the on-site verification feedback are matched and verified with the business object and organization association information in the original source business record corresponding to the online problem record to obtain the second access gating result; Access is permitted only when both the first access gating result and the second access gating result allow access. The HSE source system to be accessed is determined based on the source system identifier in the online problem record, and source data acquisition is performed from the determined HSE source system based on the source record identifier to obtain a source data acquisition result indicating successful acquisition or acquisition error. as well as The review process is performed based on the source data acquisition result. Specifically, when the source data acquisition result indicates successful acquisition, the current source business record corresponding to the source record identifier is obtained. The target verification rule that was hit when generating the online problem record is re-executed on the current source business record to obtain a rule hit result. If the rule hit result indicates that the target verification rule is no longer hit, the online problem record is updated to a rectification review passed status. If the rule hit result indicates that the target verification rule is still hit, the online problem record remains in a pending verification status. If the source data acquisition result indicates an acquisition anomaly, the online problem record remains in a pending verification status, and the target verification rule is not executed.

2. The method according to claim 1, characterized in that, The online problem record includes a problem record identifier, the source system identifier, the source record identifier, the business object identifier, the problem classification identifier, and the discovery time. The combination of the source system identifier and the source record identifier is used to distinguish source business records from different HSE source systems. The set of verification rules stores the correspondence between the problem classification identifier, applicable source system, applicable business object, judgment conditions, and rule-related fields. Within the same applicable source system and applicable business scope, each issue category identifier uniquely corresponds to one of the target verification rules.

3. The method according to claim 2, characterized in that, The validity verification of the feedback data includes: determining whether the feedback status has changed from the status to be verified by a preset method, determining whether the feedback time is later than the discovery time, and determining whether the verification evidence information meets the evidence existence conditions corresponding to the problem classification identifier. If all judgments pass, the first access gating result is determined as allowed access; if any judgment fails, the first access gating result is determined as prohibited access, the failed verification item is recorded, and the on-site verification feedback is prevented from triggering the acquisition of the current source service record of the HSE source system.

4. The method according to claim 3, characterized in that, The on-site verification feedback is associated with the work order approval record corresponding to the business object identifier; the verification evidence information includes the attachment identifier and the review result field in the work order approval record, and the evidence existence conditions include that the attachment identifier is not empty and the review result field is filled.

5. The method according to claim 2, characterized in that, The matching verification includes: reading the original source business record from the saved source business data according to the source system identifier and the source record identifier, and comparing the feedback business object identifier and feedback organization association information in the on-site verification feedback with the business object identifier and organization association information in the original source business record respectively; If the original source service record is not read or any comparison result is inconsistent, the second access gating result is determined to prohibit access and prevent the acquisition of the current source service record; if the original source service record is read and all comparison results are consistent, the second access gating result is determined to allow access.

6. The method according to claim 2, characterized in that, Only when both the first access gating result and the second access gating result are allowed access, the target source data acquisition process is determined from the pre-configured source data acquisition process set according to the source system identifier, the record positioning parameters adapted to the target source data acquisition process are determined according to the source record identifier, and the record positioning parameters are used to perform record positioning and reading, so as to obtain the current source business record when the acquisition is successful; The target source data acquisition process includes one of the following: database reading process, interface call process, and browser automation process; the record positioning parameter is the source record identifier itself or the business object identifier associated with the source record identifier.

7. The method according to claim 1, characterized in that, If the current source service record is not obtained in a single source data acquisition, the source data acquisition is performed again according to the preset number of retries. If the current source service record is still not obtained after the preset number of retries, the acquisition exception type represented by the source data acquisition result is determined as source system inaccessible, source record not located, or source service record reading failure, depending on whether the exception occurred in the processing stage of source system connection, source record location, or source record reading failure, and the acquisition exception type and acquisition time are recorded.

8. The method according to claim 3, characterized in that, The verification evidence information includes an attachment identifier, and the validity verification of the feedback data also includes attachment reuse verification. The attachment reuse verification includes: when the attachment identifier is not empty, querying whether the attachment identifier is associated with other online problem records besides the online problem record; when the attachment identifier is also associated with at least one of the other online problem records, marking the on-site verification feedback as evidence reuse, determining the first access gating result as access prohibited, and preventing the acquisition of the current source business record.

9. A HSE online monitoring and on-site verification linkage supervision system, which is communicatively connected to at least one HSE source system, characterized in that, include: question The feedback association module is used to obtain online problem records generated by the source business records of the HSE source system hitting the target verification rules and their associated on-site verification feedback. The online problem records include source system identifiers and source record identifiers. The feedback gating module is used to perform feedback data validity verification based on the feedback status, feedback time, and verification evidence information of the on-site verification feedback, and obtain the first access gating result; The object matching module is used to match and verify the business object and organization association information indicated by the on-site verification feedback with the business object and organization association information in the original source business record corresponding to the online problem record when the first access gating result allows access, so as to obtain the second access gating result; The source verification module is used only when both the first access gating result and the second access gating result allow access. It determines the HSE source system to be accessed based on the source system identifier in the online problem record, and performs source data retrieval from the determined HSE source system based on the source record identifier. This yields a source data retrieval result indicating successful or abnormal retrieval. Verification processing is then performed based on the source data retrieval result. Specifically, when the source data retrieval result indicates successful retrieval, the current source business record corresponding to the source record identifier is obtained, and the target verification rule hit when generating the online problem record is re-executed on the current source business record to obtain a rule hit result. When the source data retrieval result indicates abnormal retrieval, the target verification rule is not executed. The status update module is used to update the online problem record to a rectification review passed status when the rule hit result is obtained by the source review module. If the rule hit result indicates that the target verification rule is no longer hit, the online problem record is kept in a pending verification status.

10. An electronic device comprising a processor and a memory, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 8.

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

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 8.

Images