A group digital collaborative management and control analysis method and system

Abstract

The application provides a group digital collaborative management and control analysis method and system, comprising: obtaining a group standard version to which an issued item belongs and a reference effective time corresponding to the group standard version, and extracting an initial point position code and an initial process technology in the issued item; identifying a reference time interval formed by a terminal receipt time exceeding the corresponding reference effective time, obtaining a platform review record formed by the platform side completing review of the issued item according to the group standard version, and extracting a new version review time of a record review completion moment in the platform review record; and evaluating a target deviation degree of the issued item relative to the current group standard version by comprehensively combining the initial deviation degree and the reference time interval on the platform side.

Description

Technical Field

[0001] This invention relates to the field of information technology, and in particular to a group digital collaborative management and control analysis method and system. Background Technology

[0002] Group-level digital collaborative management refers to a multi-level corporate organization consisting of the group headquarters and its multiple project sites. The group headquarters maintains a unified group standard library and publishes group standard versions externally, while each project site organizes specific operations locally based on the referenced group standard version. The issued items refer to the work items issued by the intelligent operation platform to the field terminals for terminal personnel to execute specific tasks. Their content typically includes execution elements such as location codes, process procedures, and loop attribution. In the field of group-level digital collaborative management, the consistency between intelligent operation issued items and field terminal execution is a crucial factor in ensuring the standardized operation of the enterprise. Conventional management methods often rely on the refined construction of local project libraries, assuming that the closer the local content is to the differences in site locations, processes, and equipment, the easier it is for terminal personnel to maintain consistent execution results. However, this conventional judgment is often based on the ideal assumption that issued items are transmitted along a single line within the project, ignoring the complex conflicts that arise when multi-level standard systems intertwine. When a group standard library referencing mechanism is introduced, the previously closed local execution environment is broken, causing the original management methods to be unable to cope with the execution differentiation caused by cross-level standard changes. This cross-level standard change triggers thorny technical contradictions. Specifically, the issued items are no longer solely controlled by the local project, but change in tandem with the group's standard library version number, reference effective time, and manual review records. This leads to an anomaly: increased on-site alignment may actually exacerbate deviations in end-user execution. For example, a project developed inspection items highly aligned with on-site procedures for a specific type of water pump, but the group subsequently updated the basic standard library version for that type of equipment. Due to the time difference between the on-site data collection terminal's feedback time and the group's reference effective time, the terminal failed to synchronize with the latest version. In this situation, on-site workers still execute the items according to the old, highly localized version, while the management platform reviews them using the new group version, directly causing a severe disconnect between on-site execution and the source of the issued items. Therefore, effectively integrating key elements such as terminal feedback time, on-site location coding, and manual review records, and dynamically adjusting the consistency judgment benchmark based on the project's on-site alignment and the difference in reference version effectiveness, thereby accurately identifying execution deviations caused by standard library references, becomes a crucial issue for achieving collaborative management of group-issued items and on-site execution. Summary of the Invention

[0003] This invention provides a group-level digital collaborative management and control analysis method, the method comprising: Obtain the group standard version to which the issued item belongs and the corresponding reference effective time, and extract the initial point code and initial process technology within the issued item; By collecting terminal receipts uploaded by the on-site terminal through the edge synchronization gateway, the terminal receipt time corresponding to the terminal receipt is determined, and the actual installation location of the on-site point, the circuit ownership, the on-site executable operation process and the equipment carrying capacity recorded in the terminal receipt are extracted. Identify the reference time interval formed by the terminal receipt time exceeding the corresponding reference effective time, obtain the platform review record formed by the platform side completing the review of the issued item according to the group standard version, and extract the new version review time recorded in the platform review record at the time of review completion; The initial point code is checked against the actual installation location and circuit affiliation of the on-site point. The initial process is checked against the on-site executable operation flow and equipment carrying capacity. The on-site fit of the issued item is determined based on the reference time interval and the new version review time. The consistency verification criteria for issued items are evaluated based on the on-site fit and the reference time interval. Issued items with on-site fit exceeding the preset fit threshold are compared with the platform review records to obtain the initial deviation degree. The platform side assesses the target deviation degree by combining the initial deviation degree with the reference time interval. Based on the degree of deviation from the target, version disconnection is identified, and the platform outputs target collaborative management instructions for the issued items where version disconnection exists.

[0004] Preferably, obtaining the group standard version to which the issued item belongs and the corresponding reference effective time, and extracting the initial point code and initial process technology within the issued item, includes: Obtain the group standard version bound to the item issued by the smart operation platform, read the reference effective time corresponding to the group standard version from the version registration table of the group standard library, and bind the reference effective time with the source identifier of the issued item; Locate the point field and process field according to the entry field name, extract the initial point code and the initial process technology, and write them into the entry parsing record.

[0005] Preferably, the process of obtaining terminal receipts uploaded by the field acquisition terminal via the edge synchronization gateway, determining the terminal receipt time corresponding to the receipt, and extracting the actual installation location, loop attribution, on-site executable work process, and equipment carrying capacity recorded in the terminal receipt includes: The time of the terminal receipt is obtained by reading the timestamp field attached to the edge synchronization gateway from the header of the terminal receipt message; The message payload is partitioned by field. Terminal execution records are extracted from the execution result partition. The actual installation location of the site point, the circuit affiliation, the field executable operation process and the equipment carrying capacity are extracted from the site attribute partition and included in the terminal receipt parsing record.

[0006] Preferably, the reference time interval formed by the identification terminal receipt time exceeding the corresponding reference effective time is used to obtain the platform review record formed by the platform side completing the review of the issued item according to the group standard version, and to extract the new version review time recorded in the platform review record at the time of review completion, including: The difference between the terminal receipt time and the reference effective time is calculated, and the difference is taken to obtain the reference time interval. Based on the source identifier of the issued item, query the review registration form, locate the platform review record, extract the new version review time from the review completion time field, and classify it into the version time sequence comparison file along with the reference time interval.

[0007] Preferably, the step of verifying the initial point code with the actual installation location and loop attribution of the on-site point, verifying the initial process flow with the on-site executable operation flow and equipment carrying capacity, and determining the on-site fit of the issued item based on the reference time interval and the new version review time includes: The initial point code is compared with the actual installation location of the site point segment by segment to obtain the point location matching degree. The loop identifier segment in the initial point code is compared with the loop belonging to the same name to obtain the loop belonging matching degree. The points are then combined to obtain the point-side matching description. The process flow matching degree is obtained by comparing the initial process flow with the on-site executable operation flow item by item. The load matching degree is obtained by comparing the operation parameters of the initial process flow with the equipment load capacity by interval assignment. The process side matching description is then obtained by merging them. The timing version determination result is obtained by comparing the reference time interval with the preset acknowledgment lag threshold; The on-site fit is obtained by weighting and summing the point-side matching description, the process-side matching description, and the time-series version determination result according to preset weights.

[0008] Preferably, the step of evaluating the consistency verification criteria of the issued items based on the on-site fit and the reference time interval, and comparing the status of issued items with on-site fit exceeding a preset fit threshold with the platform review record to obtain the initial deviation degree, includes: According to the pre-established scale mapping rules, the consistency verification scale is adjusted to a strict or lenient setting based on the reference time interval and the on-site fit, thereby obtaining the value of the fit threshold. The issued items with a field fit exceeding the fit threshold are included in the set of items to be compared. The review version number and review conclusion field in the platform review record are retrieved, and the item elements of the issued items are compared with the version consistency items and items to be rectified recorded in the review conclusion field to obtain the initial deviation degree.

[0009] Preferably, the step of evaluating the target deviation degree by combining the initial deviation degree with the reference time interval on the platform side includes: The platform classifies the reference time interval into duration categories according to pre-established interval classification rules. The duration categories include short lag, medium lag, and long lag. The longer the duration corresponding to the duration category, the higher the corresponding lag correction coefficient, thus obtaining the lag correction coefficient of the issued item. The initial deviation degree is weighted according to a preset deviation weight, and the weighted result is shifted and corrected according to the lag correction coefficient. The shifted and corrected value is then normalized to a preset value range to obtain the target deviation degree.

[0010] Preferably, identifying version discrepancies based on the degree of target deviation includes: The degree of deviation of the target is compared with a preset decoupling judgment threshold, and the issuance entries whose degree of deviation of the target is greater than the decoupling judgment threshold are included in the version decoupling candidate list; By comparing the group standard version bound to the issued item with the review version number in the platform review record, if the bound group standard version is lower than the review version number and the actual installation location, circuit attribution, and on-site executable operation process are within the coverage of the current group standard version confirmed by the review version number, it is determined to be a version disconnection situation, and a set of version disconnection items is obtained.

[0011] Preferably, the step of the platform side outputting target collaborative management instructions for issued items with version mismatches includes: The platform divides the target deviation into preset value ranges to obtain hierarchical segments. Each hierarchical segment corresponds one-to-one with an instruction type. The instruction types include version rollback prompts, item reassignment prompts, and stop execution prompts. The matched instruction types, together with the item serial number of the issued item, are encapsulated into the target collaborative management instruction and sent to the field acquisition terminal.

[0012] On the other hand, the present invention also discloses a group digital collaborative management and control analysis system, which performs the aforementioned method, the system comprising: The standard version acquisition module is used to obtain the group standard version to which the issued item belongs and the corresponding reference effective time, and to extract the initial point code and initial process technology in the issued item. The terminal receipt extraction module is used to extract the terminal receipt time, actual installation location, loop attribution, on-site executable work process and equipment carrying capacity from the terminal receipt uploaded by the on-site acquisition terminal via the edge synchronization gateway. The time interval identification module is used to identify the reference time interval and obtain the latest review time of the platform review record; The on-site fit determination module is used to verify the initial point code with the actual installation location and circuit affixation of the on-site point, verify the initial process technology with the on-site executable operation process and equipment load capacity, and determine the on-site fit of the issued item. An initial deviation degree acquisition module is used to evaluate the consistency verification scale and obtain the initial deviation degree; The target deviation assessment module is used to assess the target deviation by combining the initial deviation and the reference time interval.

[0013] The technical solutions provided by the embodiments of the present invention may include the following beneficial effects: This invention discloses a group-wide digital collaborative management and control analysis method, which solves the problem of version discrepancy caused by the time lag between the update of the group's standard version and the actual on-site execution. In actual business scenarios, the work items issued by the platform are based on a certain version of the group's standard, but the on-site terminals may have already performed the operation according to the updated standard, resulting in deviations between the initial point code, initial process technology in the issued items and the actual on-site installation location and executable work flow. This invention calculates the on-site fit and target deviation of the issued items by collecting the interval between the terminal's receipt time and the reference effective time, combined with the new version's review time recorded by the platform, accurately identifying version discrepancies where the issued items are based on the old version of the standard but the on-site execution has been carried out according to the new version, and outputs targeted collaborative management and control instructions, thereby achieving dynamic consistency management between the group's standard version and the on-site execution status, effectively improving the accuracy and timeliness of the group's digital management and control. Attached Figure Description

[0014] Figure 1 This is a flowchart of a group digital collaborative management and control analysis method according to the present invention.

[0015] Figure 2 This is a schematic diagram of a group digital collaborative management and control analysis method according to the present invention.

[0016] Figure 3 This is another schematic diagram of a group digital collaborative management and control analysis method according to the present invention.

[0017] Figure 4 This is a schematic diagram of the structure of a group digital collaborative management and control analysis system according to the present invention. Detailed Implementation

[0018] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] like Figures 1 to 4 This embodiment of a group digital collaborative management and control analysis method and system may specifically include: S101. Obtain the group standard version to which the issued item belongs and the reference effective time corresponding to the group standard version, and extract the initial point code and initial process technology in the issued item.

[0020] The system retrieves the group standard version bound to the item issued by the intelligent operation platform and reads the reference effective time corresponding to the group standard version from the version registration table of the group standard library. It then binds the reference effective time with the source identifier of the issued item to obtain the item to be parsed with a version identifier. For the item to be parsed, it locates the point field and process field according to the item field name. It extracts the initial point code from the point field (used to point to the field equipment) and the initial process from the process field (used to describe the work action). The initial point code and the initial process, along with the group standard version and the reference effective time, are written into the item parsing record to obtain the initial version and initial content of the issued item.

[0021] In one implementation, the group's standard library is maintained and released externally by the group headquarters. Each standard update corresponds to a new group standard version number, and the version registration table records fields such as version number, reference effective time, and applicable equipment category. The reference effective time refers to the starting point when the group standard version is included in the basis for the compilation of issuance items on the intelligent operation platform and allowed to be referenced by various project sites. When the intelligent operation platform issues inspection, spot check, and other work items to field terminals, each issued item is assigned the bound group standard version number during the generation stage.

[0022] Specifically, when obtaining the group standard version, the version number field in the header of the issued entry is read, and then the version number is used as an index to query the version registration table of the group standard library to retrieve the corresponding reference effective time.

[0023] For example, for items issued under the category of water pump inspection, if the version number points to a basic standard for a certain type of centrifugal water pump, the reference effective time of that basic standard is retrieved from the version registration table. Then, the reference effective time is bound to the source identifier of the issued item, which includes the project number and the item serial number, thereby forming an item to be parsed with a version identifier, which serves as the processing object for subsequent field extraction.

[0024] In one possible implementation, for the item to be parsed, the location is pinpointed to the point field and the process field by precisely matching the field name with the column name in the data table structure. The point field carries the initial point code used to point to the field equipment. The initial point code adopts a four-level segmented coding form, with a structure of 2-digit plant area code, 3-digit unit code, 1-digit loop identifier, and 4-digit tag number, for a total of 10 digits. The meaning of each segment corresponds one-to-one with the plant area segment, unit segment, loop identifier segment, and tag number segment in S104; for example, the code 01A02B0015 represents plant area 01, unit A02, loop B, and tag number 0015. The process field carries the initial process technology used to describe the operation action. The initial process technology includes the action name, operation sequence, and judgment points.

[0025] Preferably, the extraction process is based on the field mapping rules published in the group's standard library. These mapping rules define the field correspondences between different versions of the standard, including a field name mapping table, data type conversion rules, and a position index lookup table. The mapping rules are stored in groups by version number, with each group labeled with a source version number S and a target version number T. Field correspondences are recorded in key-value pairs; for example, the point code field in version 1.2 corresponds to the equipment code field in version 2.0. When a version difference is detected, the system automatically matches the mapping rule table for the corresponding version and extracts data according to the field sequence number and name defined in the rule, avoiding extraction misalignment due to changes in field position. Finally, the initial point code, the initial process technology, the group standard version, the reference effective time, and the applied mapping rule version number are written into the entry parsing record, thereby obtaining the initial version and initial content of the issued entry.

[0026] S102. By collecting terminal receipts uploaded by the field acquisition terminal through the edge synchronization gateway, determine the terminal receipt time corresponding to the terminal receipt, extract the terminal execution record in the terminal receipt, and extract the actual installation location of the field point, the loop attribution, the field executable operation process and the equipment carrying capacity recorded in the terminal receipt.

[0027] The system acquires the terminal receipt message uploaded by the field acquisition terminal to the smart operation platform via the edge synchronization gateway. It reads the timestamp field attached by the edge synchronization gateway from the header of the terminal receipt message to obtain the terminal receipt time. This time is then bound to the payload portion of the terminal receipt message to obtain a time-stamped terminal receipt. For the time-stamped terminal receipt, the system extracts terminal execution records from the execution result partition according to the field partitions of the message payload. Then, it extracts the actual installation location of the field point, loop attribution, on-site executable work process, and equipment carrying capacity from the field attribute partition. All extracted items are then included in the terminal receipt parsing record to obtain the on-site execution side description corresponding to the issued item.

[0028] After completing the operation corresponding to a issued item, the field acquisition terminal sends a terminal receipt message back to the edge synchronization gateway. Upon receiving the original receipt, the edge synchronization gateway appends a timestamp field to the message header. This timestamp field is based on the standard time after local time synchronization and records the time when the receipt was forwarded uplink through the gateway. The intelligent operation platform reads this field from the terminal receipt message header to obtain the terminal receipt time Tg, and binds the terminal receipt time to the payload portion of the terminal receipt message. The payload portion carries all content fields related to this operation. In one embodiment, the field partitions of the message payload are organized according to a preset partition structure, including an execution result partition and a field attribute partition. The execution result partition carries the terminal execution record, which at least includes the operation completion status and operation time Te; the field attribute partition carries descriptive data related to the field location. The intelligent operation platform extracts the operation time Te from the terminal execution record and calculates the transmission delay δt between the operation time and the terminal receipt time Tg, where δt = Tg − Te. When δt exceeds a preset reasonable range, the receipt message is deemed to have a timestamp anomaly risk, triggering a data verification process. The preset reasonable range is determined based on on-site network latency and terminal processing time, typically set to 3 to 10 seconds. The actual installation location of the on-site point is given using a four-segment identifier, pointing to the plant area, unit, and tag number where the on-site equipment is located, where the tag number is a unique code identifier for the equipment within that unit; the loop affiliation points to the process loop number to which the point belongs; the on-site executable work process records the actual open operation procedures and judgment points on the terminal side; the equipment carrying capacity records the rated parameter range and allowed operation limit of the on-site equipment. Further, the intelligent operation platform will extract the terminal execution record, the actual installation location of the on-site point, the loop affiliation, the on-site executable work process, and the equipment carrying capacity, and include them all in the terminal receipt parsing record. The terminal receipt parsing record is organized using the project number and the serial number of the issued item as a composite primary key. Under the composite primary key, the values ​​of the above-mentioned fields and the terminal receipt time are attached, thereby forming the on-site execution side description corresponding to the issued item, ensuring the global uniqueness of the record in a cross-project environment.

[0029] S103. Identify the reference time interval formed by the terminal receipt time exceeding the corresponding reference effective time, obtain the platform review record formed by the platform side completing the review of the issued item according to the group standard version, and extract the new version review time recorded in the platform review record at the time of review completion.

[0030] Obtain the terminal receipt time corresponding to the timestamped terminal receipt, and retrieve the reference effective time corresponding to the group standard version bound to the issued item. Compare the terminal receipt time and the reference effective time on the same timeline. If the terminal receipt time is later than the reference effective time, take the difference to obtain the reference time interval. By querying the review registration table on the smart operation platform side, based on the source identifier of the issued item, locate the platform review record that was stored in the database after the platform side completed the review of the issued item according to the group standard version. The platform review record carries a review version number, a review conclusion field, and a review completion time field. For the platform review record, extract the new version review time recording the review completion time from the review completion time field, and include the new version review time, the review version number, the review conclusion field, and the reference time interval into a version timeline comparison file to obtain a timeline description of the version effective time and platform review corresponding to the issued item.

[0031] In the field of digital collaborative management and control within the group, there is an inherent time misalignment between the version updates of the group's standard library and the execution rhythm of on-site operations. Once a group standard version is released, it is immediately incorporated into the compilation of issuance items on the intelligent operations platform, with the corresponding reference effective time serving as the time anchor for the version's activation. Meanwhile, after the on-site data acquisition terminal executes the issuance items and transmits the data back via the edge synchronization gateway, the attached terminal acknowledgment time reflects the actual completion node of the on-site operation. The difference between these two points in time forms the temporal basis for identifying version disconnections.

[0032] In one possible implementation, for the terminal receipt time corresponding to the timestamped terminal receipt, the reference effective time corresponding to the group standard version bound to the issued entry is retrieved, and both are projected onto the same timeline. The timeline is based on Coordinated Universal Time (UTC) with millisecond-level precision to avoid confusion caused by terminal local time zone drift or daylight saving time switching. On the timeline, the terminal receipt time is recorded as t1, and the reference effective time is recorded as t0. If t1 > t0, the difference T is taken. ref =t1−t0, which gives the reference time interval. Where t0 represents the effective timestamp of the group standard version reference, t1 represents the timestamp of the terminal receipt being sent to the platform, and T... ref This indicates the reference time interval. The reference time interval reflects how long it takes for the field receipt to be uploaded to the smart operation platform after the new version takes effect.

[0033] It should be noted that if the terminal receipt time is earlier than or equal to the reference effective time, a valid reference time interval is not formed. Such issuance entries are marked separately as pre-version receipts and are not included in the subsequent version disconnection judgment.

[0034] Preferably, for dispatched items where ΔT exceeds a preset lag threshold, they are recorded in a pending review queue. This preset lag threshold is typically set to 2 to 8 hours in thermal power plant inspection scenarios. Specifically, for routine equipment inspection tasks, the threshold can be set to 4 hours; for key equipment or high-risk area inspection tasks, the threshold can be tightened to 2 hours; and for low-priority daily inspection tasks, the threshold can be relaxed to 8 hours. The threshold setting should comprehensively consider factors such as the urgency of the inspection task, the distance of the inspection area, and the complexity of the on-site operation.

[0035] Specifically, the intelligent operation platform maintains a review registration form, which uses a composite primary key composed of the project number and the item serial number as an index to record the review results completed by the platform for each issued item. The platform's review records are stored in the database as rows in the review registration form. Each row contains a review version number, a review conclusion field, and a review completion time field. The review version number refers to the group standard version number used by the platform when performing this review; the review conclusion field is given as an enumeration of values, including "passed," "pending rectification," "version mismatch," and "pending manual intervention." The system uses various methods to define the criteria for each item. The first, "Consider Rectification," indicates that the terminal's feedback data meets the standard requirements. The second, "Requires Rectification," indicates that non-compliance issues require rework on the terminal side. The third, "Version Mismatch," indicates that the standard version number reported by the terminal is inconsistent with the group's current standard version number used by the platform. In this case, the system records the version difference information and triggers a version synchronization process. Once the versions are unified, a new review is initiated. The fourth, "Requires Manual Intervention," indicates that the system encountered boundary scenarios during automatic review, such as missing data, abnormal formatting, or limitations of the review rules. In this case, the item is added to the manual review queue, and maintenance personnel make a judgment based on the actual situation on site. The "Review Completion Time" field records the standard time when the platform completed the review. In one implementation, the review registration table is queried based on the source identifier of the issued item. The source identifier is composed of the project number and the item serial number, serving as a composite primary key to locate the platform review record corresponding to the issued item.

[0036] For example, for an inspection item of condensate pumps in a thermal power plant, the review registration table is queried using the joint primary key obtained by concatenating the project number 01 and the item serial number to locate the most recent platform review record for that item. Further, for the platform review record, the new version review time is extracted from the review completion time field. This new version review time reflects the time when the platform side last checked and stored the issued item using the current group standard version. The current group standard version refers to the latest version of the group standard currently implemented by the platform system, used to re-verify and validate previously issued inspection items. The new version review time and the reference effective time together constitute the temporal evidence that the platform side has accepted the group standard version.

[0037] It is understandable that the new version review time may be later than the reference effective time, reflecting a certain processing delay in the platform from version release to completion of the review of existing issued items. When the difference between the new version review time and the reference effective time exceeds 72 hours, the issued item is marked as pending secondary confirmation, and the validity of its review conclusion field will be verified first in subsequent judgment stages. The new version review time, the review version number, the review conclusion field, and the aforementioned ΔT are all included in the version time sequence reference file. The version time sequence reference file is organized with the issued item serial number as the primary key, and under the primary key are the reference effective time, the terminal receipt time, the reference time interval, the new version review time, the review version number, and the review conclusion field, thereby forming a time sequence description of the version effective time and platform review corresponding to the issued item. In the subsequent judgment process, the system queries the version sequence comparison file by issuing the item serial number, extracts the review version number and the review conclusion field, and compares whether the actual version number referenced by the terminal is consistent with the latest review version number of the platform. If the review conclusion field shows non-compliance and the version number is inconsistent, it is determined that the issued item corresponds to a current standard status that has not been confirmed by the platform, triggers an alarm and pushes a rectification notice to the terminal.

[0038] S104. Verify the initial point code with the actual installation location and circuit affiliation of the site point, verify the initial process with the on-site executable operation flow and equipment carrying capacity, and determine whether the issued item corresponds to the current standard status confirmed by the platform based on the reference time interval and the new version review time, and determine the on-site fit of the issued item.

[0039] For the initial point code in the entry parsing record, a segment-by-segment character comparison is performed with the actual installation location of the field point in the terminal receipt parsing record to obtain the point location matching degree; the loop identifier segment in the initial point code is compared with the loop affiliation to obtain the loop affiliation matching degree; the point location matching degree and the loop affiliation matching degree are combined to obtain the point-side matching description of the issued entry. By comparing the action name, operation sequence, and judgment points in the initial process of the entry parsing record with the operation procedures and judgment points in the field executable operation flow item by item, the process flow conformity degree is obtained; the operation action parameters involved in the initial process are compared with the rated parameter range and allowed operation upper limit in the equipment load capacity to obtain the load capacity conformity degree; the process flow conformity degree and the load capacity conformity degree are combined to obtain the process-side matching description. The reference time interval and the new version review time are retrieved from the version time sequence comparison file. If the new version review time is not earlier than the reference effective time and the reference time interval is greater than the preset acknowledgment lag threshold, the current standard status confirmed by the platform corresponding to the issued item is determined, and the time sequence version determination result is obtained. The point-side matching description, the process-side matching description and the time sequence version determination result are weighted and summed according to preset weights to obtain the on-site fit.

[0040] In the field of group-level digital collaborative management and control, the on-site fit of issued items reflects the degree of conformity between the content of the items compiled by the group and the actual operating conditions on the field. The on-site fit encompasses three dimensions: location-based, process-based, and time-series version. The first two measure the correspondence between the item content and the on-site equipment and operational capabilities, while the latter measures whether the group standard version on which the item is based has been recently verified and confirmed by the platform. In one implementation, the initial location code is organized in a segmented structure, sequentially carrying the plant area segment, unit segment, circuit identifier segment, and tag number segment from high to low digits, with each segment separated by a separator.

[0041] Specifically, the initial point code in the entry parsing record is compared segment by segment with the actual installation location of the field point in the terminal receipt parsing record. The comparison covers four segments in sequence: plant area segment, unit segment, circuit identifier segment, and tag number segment. Each segment with completely identical characters is counted as one hit, and the number of hit segments is denoted as N, with a fixed total of 4 segments. The point location matching degree M is calculated using the formula M=N / 4. When N=4, the matching degree is 1, indicating a complete match. When N<4, the matching degree is determined according to the proportion of actual hit segments. For example, if only the plant area segment and unit segment are hit, then N=2, and the matching degree M=0.5.

[0042] It should be noted that the loop identifier segment within the initial point code has already participated in the calculation of point location matching degree in the aforementioned four-segment character-by-character comparison. To further verify the accuracy of loop attribution, this loop identifier segment is extracted separately and compared with the process loop number pointed to by the loop attribution in the terminal receipt parsing record. If the two are completely identical, the loop attribution matching degree is 1. If there is an offset with the same prefix but different tail, the loop attribution matching degree is calculated by the ratio of the number of hit characters to the total number of characters. The point location matching degree is denoted as M1, and the loop attribution matching degree is denoted as M2. The point-side matching degree P is calculated by equal weighting and merging. The calculation formula is P=(M1+M2) / 2, with a value range of 0 to 1. When M1=M2=1, P=1, indicating a complete match. This point-side matching degree P is used as a numerical indicator for subsequent comprehensive evaluation. For the initial process in the entry parsing record, the action name, operation sequence, and judgment points recorded in the initial process constitute a pair of process entries. The action name refers to the operation name of each process step, such as opening a valve, closing a valve, reading a value, or recording a value. The operation sequence refers to the sequence number of each step within the entry. The judgment criteria refer to the judgment indicators after each step is completed. The verification process includes three dimensions: first, verifying whether the action names are consistent with the action terms in the standard process library; second, verifying whether the operation sequence is correctly arranged according to the process flow; and finally, verifying whether the judgment criteria meet the quality control standards. When any dimension deviates, the system marks the process entry pair as an anomaly and generates a deviation report. The report indicates the specific deviation type, such as mismatched action names, incorrect sequence, or missing judgment criteria, for subsequent manual review and correction.

[0043] In one possible implementation, the aforementioned process items are checked against the operational procedures and judgment points in the on-site executable work process item by item. The check uses a set intersection method, where the number of matching items refers to the number of common items that match between the process item pair and the on-site process, i.e., the number of intersection items. The process flow similarity calculation formula is: S1=M / N, where M is the number of intersection items and N is the number of union items, i.e., the Jaccard similarity. When the process flow similarity is lower than 0.75, the issued item is marked as a process-side item awaiting review. This item enters the manual review queue and can only be issued for execution after confirmation by process review personnel. Items that fail review will be returned for revision. Furthermore, for the operational parameters involved in the current process item pair in the initial process flow, including but not limited to valve opening, operation duration, single reading sampling interval, and all other quantifiable operational parameters, an interval classification check is performed against the rated parameter range and allowable operation upper limit recorded in the equipment's load-bearing capacity. The logic for interval assignment verification is as follows: The value v of the operation parameter is placed within the interval [a, b] given by the rated parameter range for judgment. If a ≤ v ≤ b and v does not exceed the allowable upper limit u, then the operation parameter is counted as an inner item of the load; otherwise, it is counted as an outer item of the load. The load compatibility calculation formula is: S² = I / T, where I is the number of inner items of the load, and T is the total number of operation parameters involved in the current process item.

[0044] Preferably, the process threshold is 0.7. The process flow matching degree and the load-bearing matching degree are combined with equal weight to obtain the process-side matching degree. The process-side matching degree is denoted as W, and is calculated as W = 0.5 × process flow matching degree + 0.5 × load-bearing matching degree, with a value range of 0 to 1. When W is greater than or equal to 0.7, the process-side matching is considered successful.

[0045] It is understood that the time-series version determination result is generated based on the reference time interval in the version time-series comparison file and the new version review time. The determination logic is as follows: if the new version review time is not earlier than the reference effective time, it indicates that the platform has completed the review of the issued item after the version took effect; at the same time, the reference time interval is greater than the preset receipt lag threshold, indicating that the terminal receipt arrived at the platform after a sufficient time window after the version took effect. If both conditions are met, the time-series version determination result is 1; otherwise, it is 0.

[0046] For example, the preset timeliness threshold for receipts is set to 4 hours in the scenario of condensate pump inspection in a thermal power plant. That is, if the interval between the receipt arrival time and the reference effective time does not exceed 4 hours, it is considered a timely receipt. When the interval exceeds 4 hours but does not exceed 24 hours, it is considered a short delay; when it exceeds 24 hours, it is considered a long delay. The time-series version determination result is given in a three-value form, corresponding to the three states of timely, short delay, and long delay, respectively, with quantification values ​​of 1.0, 0.6, and 0.2, serving as a calibrator for the degree of fit between the issued item and the current standard state of the platform in terms of time sequence. Further, the location-side matching description, the process-side matching description, and the time-series version determination result are weighted and summed according to preset weights to obtain the on-site fit degree F. The calculation relationship is F=w1×P+w2×W+w3×T, where P is the numerical value of the point-side matching description, W is the numerical value of the process-side matching description, T is the quantized value of the time sequence version judgment result, and w1, w2, and w3 are the corresponding weights with a sum of 1.

[0047] In one embodiment, w1 is set to 0.35, w2 to 0.4, and w3 to 0.25, reflecting that process-side matching has a slightly higher weight in the inspection scenario, while the time-series version determination is used as an auxiliary dimension in the summation. Ultimately, the on-site fit F value falls within the range of 0 to 1, serving as a unified quantitative basis for subsequent determination of whether issued items enter the version mismatch screening process.

[0048] S105. Evaluate the consistency verification criteria of the issued items based on the on-site fit and the reference time interval, and identify the issued items whose on-site fit is higher than the preset fit threshold. Compare the status of the issued items that are higher than the preset fit threshold with the platform review records to obtain the initial deviation of the issued items from the current group standard version.

[0049] Based on the on-site fit and the reference time interval, a consistency verification scale is jointly determined according to a pre-established scale mapping rule. If the reference time interval is greater than a preset retrieval lag threshold and the on-site fit is greater than a preset fit high threshold, the consistency verification scale is adjusted to a strict level; otherwise, it is adjusted to a lenient level. The consistency verification scale corresponds to the fit threshold value, and the consistency verification scale corresponding to the issued item is obtained. All issued items are filtered through the fit threshold corresponding to the consistency verification scale, and issued items with an on-site fit higher than the fit threshold are identified. Issued items with an on-site fit higher than the fit threshold are included in the set of items to be compared. Each record in the set of items to be compared carries the item serial number of the issued item, the on-site fit, and the reference time interval. For each issued item in the set of items to be compared, the review version number and review conclusion field in the platform review record are retrieved. The group standard version bound to the issued item is matched with the review version number. The item elements corresponding to the initial point code and initial process technology in the issued item are compared item by item with the version consistency items and rectification items recorded in the review conclusion field to obtain the initial deviation degree of the issued item relative to the current group standard version.

[0050] In the field of group-wide digital collaborative management and control, for the issued items with high on-site relevance, whether there is a state deviation between them and the current group standard version determines the output direction of subsequent collaborative management and control instructions. The consistency verification scale, as a unified dimension for screening and judgment, takes into account both the on-site relevance and the reference time interval, and is jointly determined according to a pre-established scale mapping rule.

[0051] Specifically, the scale mapping rule is organized with two input parameters: input parameter one is the reference time interval, and input parameter two is the on-site fit. The rule's judgment logic is as follows: if the reference time interval is greater than a preset lag threshold and the on-site fit is greater than a preset high-level fit threshold, then the consistency verification scale is adjusted to the strict level; otherwise, it falls into the lenient level. The fit threshold corresponding to the strict level is taken as the higher level, and the fit threshold corresponding to the lenient level is taken as the lower level, thereby establishing a one-to-one correspondence between the scale mapping rule and the high and low values ​​of the fit threshold. In one embodiment, the preset lag threshold is 4 hours in the thermal power plant inspection scenario, and the preset high-level fit threshold is 0.85; the fit threshold corresponding to the strict level is 0.9, and the fit threshold corresponding to the lenient level is 0.75. The difference between the two fit thresholds reflects different screening granularities for the issued items.

[0052] It should be noted that the items issued under the stricter consistency verification criteria often exhibit high on-site fit and long response delays. Whether the group standard version upon which these items are based remains current is highly sensitive to the interpretation of on-site execution results. The stricter criteria correspond to a unique fit threshold θstrict, with a value of 0.85. This threshold serves as a unified standard applied to all items to be screened. The screening process scans each item sequentially using its serial number as an index, comparing the on-site fit (Don-site) of each item with the fit threshold θstrict. If Don-site ≥ θstrict, the item is added to the candidate set; otherwise, it is removed. The candidate set is then merged into a set of items to be compared after deduplication. The deduplication rule is to retain the item with the highest on-site fit among records with the same serial number. Each record in the set of items to be compared carries the item's serial number, on-site fit, and reference time interval. The item serial number serves as the association key between the record and the platform review record. On-site fit and reference time interval are retained as auxiliary measures for subsequent deviation assessment. For each issued item in the set of items to be compared, the review version number and review conclusion field in the platform review record are retrieved based on the item serial number. The platform review record is automatically generated by the business system each time a standard version is updated or a review is manually triggered. The record table contains four fields: item serial number, review version number, review conclusion, and review timestamp. The review version number reflects the group standard version used by the platform in the most recent review. The review conclusion field carries the status identifier given by the review in the form of an enumeration value, including three types: synchronized, differing, and awaiting manual confirmation. The system extracts the corresponding version of the standard item content from the group standard library based on the review version number, forming two comparison benchmarks: a set of version-consistent items and a set of items to be rectified. The set of version-consistent items includes items whose group standard version on which the issued item is based is completely consistent with the version currently used by the platform and has no content differences; the set of items to be rectified includes items whose content has identifiable differences from the current version used by the platform and requires further processing.

[0053] Specifically, the group standard version bound to the issued item is compared with the review version number. The version number string is strictly matched; if the match is successful, the version binding of the issued item is consistent with the platform version; if the match fails, it is considered a version binding deviation. Under the premise of consistent version binding, the item elements within the issued item are then compared item by item with the review conclusion field. The review conclusion field includes a list of version-consistent items and a list of items requiring rectification. The version-consistent items list records the set of element identifiers that completely match the platform version, while the list of items requiring rectification records the set of element identifiers that differ from the platform version and need correction. The item elements are divided into two independent elements: initial location code and initial process technology. The item-by-item comparison uses the item element as the smallest unit. The specific determination method is as follows: extract the initial location code from the issued item, search for this code in the version-consistent items list of the review conclusion field; if the search finds a match, the location code is determined to be a version-consistent item; if not, search in the list of items requiring rectification; if a match is found, it is determined to be an item requiring rectification. The same search and determination process is performed on the initial process technology. After each item is judged, the classification records of all elements in the issued items are completed and the comparison results are output.

[0054] For example, let n be the total number of item elements entering the comparison within the issued item, and m be the number of item elements falling into the rectification item. Then, the initial deviation degree D of the issued item relative to the current group standard version is determined by D=m÷n, where n represents the total number of item elements, m represents the number of item elements falling into the rectification item, and D's value falls within the range of 0 to 1, reflecting the deviation ratio at the content level of the issued item. If there is also version binding deviation, then a version deviation index V is defined. When the version bound to the issued item is inconsistent with the current group standard version, V's value is 1, and when the versions are consistent, V's value is 0. The comprehensive deviation degree C is calculated by the formula C=0.7×D+0.3×V, where 0.7 is the content deviation weight, 0.3 is the version deviation weight, and C's value also falls within the range of 0 to 1. The larger the value, the higher the deviation degree.

[0055] Preferably, for the inspection items of condensate pumps in thermal power plants, each operation procedure consists of a corresponding initial location code and an initial procedure process. If an item contains 5 operation procedures, and the platform's review conclusion field identifies 2 of these operation procedures as items requiring rectification, then the initial deviation degree D = number of procedures requiring rectification / total number of operation procedures = 2 / 5 = 0.4, reflecting a moderate degree of version deviation at the content level for this issued item. Here, D represents the initial deviation degree. The initial deviation degree, as a quantitative result of the content-level deviation of this issued item relative to the current group standard version, together with the reference time interval, constitutes the initial component of the deviation description of the issued item.

[0056] S106. The platform side combines the initial deviation degree with the reference time interval to evaluate the target deviation degree of the issued item relative to the current group standard version.

[0057] The platform retrieves the initial deviation degree and the reference time interval corresponding to the issued item. The reference time interval is categorized into duration categories according to pre-established interval classification rules. These duration categories include short lag, medium lag, and long lag categories. The longer the duration of the category, the higher the corresponding lag correction coefficient, thus obtaining the lag correction coefficient for the issued item. The initial deviation degree is weighted according to a preset deviation weight, and the lag correction coefficient is then added to the weighted result for shift correction. The shifted value is normalized to a value range of 0 to 1, yielding the target deviation degree of the issued item relative to the current group standard version.

[0058] In the field of group-wide digital collaborative management and control, the initial deviation degree only reflects the proportion of deviation of the issued item from the current group standard version in terms of content, and does not cover the impact of misaligned receipt timing on deviation judgment. The platform retrieves two indicators corresponding to the issued item: the initial deviation degree and the reference time interval, as inputs for the target deviation degree assessment. In one implementation, the interval grading rule uses duration boundaries as the dividing basis to classify the reference time interval into several duration gradations. The duration gradations include short lag, medium lag, and long lag; the short lag corresponds to the reference time interval falling within 4 hours, the medium lag corresponds to the reference time interval falling between 4 hours and 24 hours, and the long lag corresponds to the reference time interval exceeding 24 hours. The larger the duration of the assigned duration gradation, the higher the corresponding lag correction coefficient, which serves as a bias term for subsequent translation correction in the comprehensive evaluation.

[0059] Specifically, the initial deviation degree is weighted according to a preset deviation weight. The deviation weight reflects the proportion of the item content deviation in the comprehensive evaluation, and the value falls within the range of 0 to 1.

[0060] Preferably, the deviation weight is 0.7. The weighted merging form is Dintermediate = w × Dintermediate 初始 ×(1+k lag), where Dmedian is the median value of the deviation from the target, w is the deviation weight, and Dmedian is the mean value of the deviation from the target. 初始The initial deviation is represented by the lag correction coefficient k, which ranges from -0.2 to +0.2. When the receipt timeline is normal, k is 0; when the receipt is delayed, k is positive with a maximum value of 0.2; and when the receipt is early, k is negative with a minimum value of -0.2. Further, the intermediate values ​​are normalized to fall within the range of 0 to 1. Normalization uses a linear pruning method: when the intermediate value is less than 0, it is set to 0; when the intermediate value is greater than 1, it is set to 1; and when it falls within the range, the original value is retained. This results in the final deviation of the issued item from the current group standard version, representing a combined quantitative result of the item content deviation and the receipt timeline lag.

[0061] S107. Based on the degree of deviation from the target, identify the version discrepancy between the standard on which the issued item is based and the current group standard version that has been verified and confirmed by the platform for the actual installation location, circuit attribution and on-site executable operation process. The platform will then output target collaborative management instructions for the issued items with version discrepancies.

[0062] Based on the target deviation degree, the target deviation degree is compared with a preset decoupling judgment threshold. If the target deviation degree is greater than the decoupling judgment threshold, the issued item is included in the version decoupling candidate list. Each record in the version decoupling candidate list carries the item serial number of the issued item, the target deviation degree, and the group standard version bound to the issued item. By comparing the group standard version bound to the issued item with the review version number in the platform review record for the issued items in the version decoupling candidate list, if the group standard version bound to the issued item is lower than the review version number, and the actual installation location, loop attribution, and on-site executable operation process in the terminal receipt parsing record are all within the coverage of the current group standard version confirmed by the review version number, it is determined that the issued item has a version decoupling situation, and a set of version decoupling items is obtained. For each item in the set of version disconnected items, the platform divides it into hierarchical segments according to the target deviation degree of the item and a preset value range. Each hierarchical segment corresponds one-to-one with an instruction type. The instruction types include version rollback prompts, item reassignment prompts, and stop execution prompts. The matched instruction type, together with the item serial number of the item, is encapsulated into a target collaborative management instruction and sent to the field acquisition terminal.

[0063] In the field of group-wide digital collaborative management and control, version mismatch refers to a situation where the group standard version on which the issued items are based is still the old version, while the actual installation location, loop attribution, and on-site executable operation procedures have been covered by the current group standard version verified and confirmed by the platform. Upon identifying such a situation, the platform issues a target collaborative management and control instruction to correct the version mismatch between the group-level issuing side and the on-site execution side.

[0064] Specifically, the target deviation degree is compared with a preset decoupling judgment threshold. The decoupling judgment threshold serves as an initial screening threshold for version decoupling, reflecting the value at which the target deviation degree qualifies the issued item for version decoupling judgment. In one implementation, for issued items in a thermal power plant inspection scenario, the decoupling judgment threshold is set to 0.3. If the target deviation degree is greater than the decoupling judgment threshold, the issued item is included in the version decoupling candidate list. The version decoupling candidate list is organized using the item serial number as the primary key, with the target deviation degree, the group standard version bound to the issued item, and an association key pointing to the platform review record attached to the primary key, serving as input for subsequent item-by-item judgment.

[0065] It should be noted that, for each issuance item in the candidate list of version discrepancies, the review version number in the platform review record corresponding to the issuance item is retrieved according to the association key. Then, the group standard version bound to the issuance item is compared with the review version number according to the semantic level of the version number. The semantic level comparison of the version number adopts the version number segment numerical ascending order parsing, with the larger segment value being the higher version and the smaller segment value being the lower version. Further, if the group standard version bound to the issuance item is lower than the review version number, it indicates that the issuance item is still based on the old version of the group standard; at the same time, the actual installation location of the field point, the loop attribution, and the field executable operation process in the terminal receipt parsing record are retrieved, and the above three field elements are checked against the coverage of the current group standard version confirmed by the review version number. The coverage check adopts set attribution judgment. If the value of the field element falls within the allowed set enumerated by the current group standard version, it is considered to be covered. When all three on-site elements fall within the coverage area, it is determined that the issued item has a version disconnection, and it is merged into the version disconnection item set.

[0066] In one possible implementation, for each distribution item within the version deviance item set, the platform divides it into graded segments based on the degree of target deviation of the distribution item according to preset value ranges. The value ranges are divided into three segments using two boundary values: a first boundary value of 0.5 and a second boundary value of 0.75. If the degree of target deviation falls within the range greater than the deviance judgment threshold but not exceeding the first boundary value, it is classified as a mild deviance segment; if it falls within the range greater than the first boundary value but not exceeding the second boundary value, it is classified as a moderate deviance segment; and if it falls within the range greater than the second boundary value, it is classified as a severe deviance segment.

[0067] Specifically, the hierarchical segments correspond one-to-one with instruction types. The slightly disconnected segment corresponds to a version switchback prompt, whereby the platform notifies the field acquisition terminal to verify the group standard version number and switch to the current version. The moderately disconnected segment corresponds to an item reassignment prompt, whereby the platform re-compiles and distributes the item according to the current group standard version, replacing the original item. The severely disconnected segment corresponds to a stop execution prompt, whereby the platform immediately freezes the field execution permission of the distributed item. Further, the matched instruction type, along with the item serial number of the distributed item, is encapsulated into a target collaborative management instruction. This target collaborative management instruction is distributed to the field acquisition terminal via the edge synchronization gateway in the form of a structured message. The field acquisition terminal executes the corresponding action based on the instruction type carried within the target collaborative management instruction, thereby completing the version-level collaborative management closed loop between the group distribution side and the field execution side.

[0068] On the other hand, this embodiment also provides a group digital collaborative management and control analysis system, which mainly includes: The group standard version acquisition module is used to obtain the group standard version to which the issued item belongs and the reference effective time of the group standard version, and to extract the initial point code and initial process technology in the issued item. The terminal receipt extraction module is used to collect terminal receipts uploaded by the on-site terminal through the edge synchronization gateway, determine the terminal receipt time corresponding to the terminal receipt, extract the terminal execution record in the terminal receipt, and extract the actual installation location, loop attribution, on-site executable operation process and equipment carrying capacity recorded in the terminal receipt. The reference time identification module is used to identify the reference time interval formed when the terminal receipt time exceeds the corresponding reference effective time, obtain the platform review record formed by the platform side completing the review of the issued item according to the group standard version, and extract the new version review time recorded in the platform review record when the review is completed; The on-site fit determination module is used to verify the initial point code with the actual installation location and circuit affiliation of the on-site point, verify the initial process with the on-site executable operation flow and equipment load capacity, and determine whether the issued item corresponds to the current standard status confirmed by the platform based on the reference time interval and the new version review time, thereby determining the on-site fit of the issued item. The initial deviation calculation module is used to evaluate the consistency verification scale of the issued items based on the on-site fit and reference time interval, and to identify the issued items whose on-site fit is higher than the preset fit threshold. The issued items with a fit higher than the preset fit threshold are compared with the platform review records to obtain the initial deviation of the issued items relative to the current group standard version. The target deviation assessment module is used by the platform to assess the target deviation of the issued item relative to the current group standard version by combining the initial deviation and the reference time interval. The version disconnect identification and control instruction output module is used to identify, based on the degree of deviation of the target, the version disconnect situation formed by the standard on which the issued item is based is still the old version, while the actual installation location, loop attribution and on-site executable operation process have been verified and confirmed by the platform using the current group standard version. The platform then outputs target collaborative control instructions for the issued items with version disconnect.

[0069] It will be apparent to those skilled in the art that this application is not limited to the details of the exemplary embodiments described above, and that this application can be implemented in other specific forms without departing from the spirit or essential characteristics of this application. Therefore, the embodiments should be considered illustrative and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within this application. No reference numerals in the claims should be construed as limiting the scope of the claims.

Claims

1. A group-wide digital collaborative management and control analysis method, characterized in that, The method includes: Obtain the group standard version to which the issued item belongs and the corresponding reference effective time, and extract the initial point code and initial process technology within the issued item; By collecting terminal receipts uploaded by the on-site terminal through the edge synchronization gateway, the terminal receipt time corresponding to the terminal receipt is determined, and the actual installation location of the on-site point, the circuit ownership, the on-site executable work process and the equipment carrying capacity recorded in the terminal receipt are extracted. Identify the reference time interval formed by the terminal receipt time exceeding the corresponding reference effective time, obtain the platform review record formed by the platform side completing the review of the issued item according to the group standard version, and extract the new version review time recorded in the platform review record at the time of review completion; The initial point code is checked against the actual installation location and circuit affiliation of the on-site point; the initial process is checked against the on-site executable operation flow and equipment carrying capacity; and the on-site fit of the issued item is determined based on the reference time interval and the new version review time. The consistency verification criteria for the issued items are evaluated based on the on-site fit and the reference time interval. The issued items with on-site fit exceeding the preset fit threshold are compared with the status of the platform review records to obtain the initial deviation degree. The platform side assesses the target deviation degree by combining the initial deviation degree with the reference time interval. Based on the degree of deviation from the target, version disconnection is identified, and the platform outputs target collaborative management instructions for the issued items where version disconnection exists.

2. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The process of obtaining the group standard version to which the issued item belongs and its corresponding reference effective time, and extracting the initial point code and initial process technology within the issued item, includes: Obtain the group standard version bound to the item issued by the smart operation platform, read the reference effective time corresponding to the group standard version from the version registration table of the group standard library, and bind the reference effective time with the source identifier of the issued item; Locate the point field and process field according to the entry field name, extract the initial point code and the initial process technology, and write them into the entry parsing record.

3. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The terminal receipt uploaded by the field acquisition terminal via the edge synchronization gateway is used to determine the corresponding terminal receipt time, and to extract the actual installation location of the field point, loop attribution, on-site executable work process, and equipment carrying capacity recorded in the terminal receipt, including: The time of the terminal receipt is obtained by reading the timestamp field attached to the edge synchronization gateway from the header of the terminal receipt message; The message payload is partitioned by field. Terminal execution records are extracted from the execution result partition. The actual installation location of the site point, the circuit affiliation, the field executable operation process and the equipment carrying capacity are extracted from the site attribute partition and included in the terminal receipt parsing record.

4. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The reference time interval formed by the recognition terminal's receipt time exceeding the corresponding reference effective time is used to obtain the platform review record formed by the platform side's review of the issued items according to the group standard version. The new version review time recorded in the platform review record at the review completion time is extracted, including: The difference between the terminal receipt time and the reference effective time is calculated, and the difference is taken to obtain the reference time interval. Based on the source identifier of the issued item, query the review registration form, locate the platform review record, extract the new version review time from the review completion time field, and classify it into the version time sequence comparison file along with the reference time interval.

5. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The process of verifying the initial location code with the actual installation location and circuit affixation of the site location, verifying the initial process flow with the on-site executable operation flow and equipment load-bearing capacity, and determining the on-site fit of the issued items based on the reference time interval and the new version review time includes: The initial point code is compared with the actual installation location of the site point segment by segment to obtain the point location matching degree. The loop identifier segment in the initial point code is compared with the loop belonging to the same name to obtain the loop belonging matching degree. The points are then combined to obtain the point-side matching description. The process flow matching degree is obtained by comparing the initial process flow with the on-site executable operation flow item by item. The load matching degree is obtained by comparing the operation parameters of the initial process flow with the equipment load capacity by interval assignment. The process side matching description is then obtained by merging them. The timing version determination result is obtained by comparing the reference time interval with the preset acknowledgment lag threshold; The on-site fit is obtained by weighting and summing the point-side matching description, the process-side matching description, and the time-series version determination result according to preset weights.

6. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The consistency verification criterion for evaluating the issued items based on the on-site fit and the reference time interval involves comparing the status of issued items with on-site fit exceeding a preset fit threshold with the platform review records to obtain the initial deviation degree, including: According to the pre-established scale mapping rules, the consistency verification scale is adjusted to a strict or lenient setting based on the reference time interval and the on-site fit, thereby obtaining the value of the fit threshold. The issued items with a field fit exceeding the fit threshold are included in the set of items to be compared. The review version number and review conclusion field in the platform review record are retrieved, and the item elements of the issued items are compared with the version consistency items and items to be rectified recorded in the review conclusion field to obtain the initial deviation degree.

7. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The assessment of the target deviation degree by the platform side, which combines the initial deviation degree with the reference time interval, includes: The platform classifies the reference time interval into duration categories according to pre-established interval classification rules. The duration categories include short lag, medium lag, and long lag. The longer the duration corresponding to the duration category, the higher the corresponding lag correction coefficient, thus obtaining the lag correction coefficient of the issued item. The initial deviation degree is weighted according to a preset deviation weight, and the weighted result is shifted and corrected according to the lag correction coefficient. The shifted and corrected value is then normalized to a preset value range to obtain the target deviation degree.

8. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The step of identifying version disconnection based on the degree of target deviation includes: The degree of deviation of the target is compared with a preset decoupling judgment threshold, and the issuance entries whose degree of deviation of the target is greater than the decoupling judgment threshold are included in the version decoupling candidate list; By comparing the group standard version bound to the issued item with the review version number in the platform review record, if the bound group standard version is lower than the review version number and the actual installation location, circuit attribution, and on-site executable operation process are within the coverage of the current group standard version confirmed by the review version number, it is determined to be a version disconnection situation, and a set of version disconnection items is obtained.

9. The group digital collaborative management and control analysis method according to claim 1, characterized in that, The platform-side outputs target collaborative management instructions for items with version discrepancies, including: The platform divides the target deviation into preset value ranges to obtain hierarchical segments. Each hierarchical segment corresponds one-to-one with an instruction type. The instruction types include version rollback prompts, item reassignment prompts, and stop execution prompts. The matched instruction types, together with the item serial number of the issued item, are encapsulated into the target collaborative management instruction and sent to the field acquisition terminal.

10. A group-wide digital collaborative management and control analysis system, characterized in that, The system for performing the method according to any one of claims 1 to 9 comprises: The standard version acquisition module is used to obtain the group standard version to which the issued item belongs and the corresponding reference effective time, and to extract the initial point code and initial process technology in the issued item. The terminal receipt extraction module is used to extract the terminal receipt time, actual installation location, loop attribution, on-site executable work process and equipment carrying capacity from the terminal receipt uploaded by the on-site acquisition terminal via the edge synchronization gateway. The time interval identification module is used to identify the reference time interval and obtain the latest review time of the platform review record; The on-site fit determination module is used to verify the initial point code with the actual installation location and circuit affixation of the on-site point, verify the initial process technology with the on-site executable operation process and equipment load capacity, and determine the on-site fit of the issued item. An initial deviation degree acquisition module is used to evaluate the consistency verification scale and obtain the initial deviation degree; The target deviation assessment module is used to assess the target deviation by combining the initial deviation and the reference time interval.

Images