Power supply enterprise business expansion process real-time monitoring method and system

Abstract

The present application relates to the technical field of power supply service, in particular to a method and system for real-time monitoring of power supply enterprise business expansion process. A mobile terminal collects field data, and an edge data server generates a to-be-compliant comparison feature sequence; a rule fusion container fuses a rule library and a historical problem library to generate compliance data. Based on field standardization mapping and version summary, existence, applicability, consistency and validity period verification of mandatory / recommended attributes are performed, and compliance, missing elements or non-compliant items are output; positioning information, informationization problem identification containing version and rectification suggestions are generated for non-compliant items, and are converted into time-limited work orders, which are cached under weak network and reconciled with the center server and bidirectionally verified after network recovery. Nodes complete event-triggered compliance record uploading, and the center aggregates and archives to form process-level compliance. The scheme realizes controllable rule upgrading, traceable evidence chain and process compliance closed loop, and improves accuracy and efficiency.

Description

Technical Field

[0001] This invention relates to the field of power supply services, specifically to a method and system for real-time monitoring of the business expansion process of power supply enterprises. Background Technology

[0002] The business expansion processes of power supply companies, such as new power installations, capacity increases, and changes, involve multiple business nodes, including business acceptance, site surveys, scheme formulation and design review, intermediate inspections, final acceptance, contract signing, meter installation and power supply, and archiving. These nodes involve cross-departmental collaboration, cross-system data flow, and multi-role on-site verification. Existing technologies generally suffer from the following problems: Compliance checks are often conducted at the completion or random inspection stages, making it difficult to promptly identify issues such as missing mandatory attributes, expired licenses, and unactivated platform functions, leading to rework and time-related risks. Regulatory provisions are frequently updated, with rules scattered across policy documents, announcements, internal procedures, and experience bases, lacking unified management of provision numbers and version dimensions, resulting in inconsistencies in on-site implementation across different regions and time periods. On-site data collection involves heterogeneous data such as images, forms, coordinates, timestamps, and equipment / personnel identification; outliers, duplicate reporting, and time misalignment affect verification accuracy. Frequent network fluctuations on-site mean that offline data collection is prone to loss or inconsistencies with the central version, leading to subsequent comparison failures.

[0003] The lack of strong linkage between non-conformities and original data, coupled with the absence of a correlation between the rectification process and rule versions, makes it difficult to effectively support accountability and process auditing. The impact of rule adjustments on ongoing work orders is unclear, lacking compatibility / incompatibility assessment and migration strategies, which can easily lead to the invalidation of collected data or repeated data collection. Summary of the Invention

[0004] The purpose of this invention is to provide a solution to one of the aforementioned problems existing in the prior art. Specifically, this invention is achieved through the following technical solution: The real-time monitoring method for the business expansion process of power supply companies includes the following steps: Step 1: The mobile terminal collects on-site data of the business expansion process, the edge data server processes the data and generates a feature sequence to be compared for compliance; the rule fusion container retrieves regulatory standard data from the regulatory standard library and problem data from the historical problem library in the edge data server and merges them to generate compliance data. Step 2: Compare the feature sequence to be compliant with the compliant data. If it is non-compliant, proceed to Step 3; if it is missing an element, proceed to Step 4; if it is compliant, proceed to Step 5. Step 3: Generate non-conformity items including location information on the edge data server. Based on the location clause number and problem type of the non-conformity item, generate a problem identifier and generate rectification suggestions, then proceed to Step 5. Step 4: Send a supplementary data collection command to the mobile device. After the supplementary data collection, return to Step 2. Step 5: For the on-site data that is determined to be compliant, a node-level compliance confirmation record is generated. The node-level compliance confirmation record is sent to the central data server by the edge data server according to the node completion event. The non-compliance items and rectification suggestions are added to the mobile task queue cache. If there are unprocessed non-compliance items or missing elements, proceed to step 6; otherwise, proceed to step 7. Step 6: Convert non-compliant items and rectification suggestions into work orders with time limits and assign them to mobile devices. The mobile devices will then verify the consistency of work orders and data versions with the central data server and track the rectification. Step 7: The central data server aggregates node-level compliance confirmation records to form process-level compliance archives, and then completes real-time monitoring of the business expansion process.

[0005] Furthermore, the edge data server processes the on-site data to generate a feature sequence to be compared for compliance, including: The on-site data includes platform operation records, file images, geographic coordinates, timestamps, form fields, equipment and personnel identifiers, and process node identifiers. The edge data server performs abnormal data removal, duplicate data deduplication, and fills in placeholders for required fields and aligns the time according to the process nodes. It then sends the on-site data to the generated process node data container and concatenates the process node data containers in the order of the process nodes to form a feature sequence to be compared for compliance.

[0006] Furthermore, the rule fusion container retrieves regulatory standard data from the regulatory standard library of the edge data server and merges it with issue data from the historical issue library to generate compliance data, including: The rule fusion container parses the clause number, scope of application, validity period, and attributes of regulatory standard data; it packages the issue type, triggering conditions, and reference rectification templates corresponding to the clause number into clause-level compliance data; all clause-level compliance data constitute compliance data; the attributes are mandatory or recommended.

[0007] Furthermore, the comparison of the feature sequence to be compliant with the compliance data includes: Based on the business expansion process, the clause-level compliance data of the corresponding process nodes are used to form a node-level compliance data sequence, and the rule version number and effective time window are recorded. The business expansion process is the business process that the power supply company completes from business acceptance, on-site survey, scheme formulation, design review, intermediate inspection, final acceptance, contract signing, meter installation and power supply to archiving after the power user submits the electricity demand. A mapping between feature fields and clause fields is established based on a standardized field mapping table maintained by the edge data server and bearing version numbers. The on-site data in the process node data container is verified against the corresponding clause-level compliance data of the process node, including existence and consistency verification of mandatory attribute data; applicability and consistency verification of recommended attribute data; and validity verification of the validity period field at the current time point. If all verifications pass, compliance is output; if verifications are inconsistent, non-compliance is output; if mandatory attribute data is missing, element missing is output; and a prompt message is generated when recommended attributes are applicable but inconsistent.

[0008] Furthermore, the generation of non-conformities with location information on the edge data server includes: The location information includes physical location information and abstract location information. The physical location information includes geographic coordinates, data collection timestamp, data collection device identifier, and data collection personnel identifier. Abstract location information includes process node identifiers, form field paths, regulatory clause numbers, rule item version numbers, and issue type codes; The non-conformity items are associated with the hash fingerprints of the corresponding original on-site data records / files for audit tracing.

[0009] Furthermore, the process of generating a problem identifier and generating rectification suggestions based on the non-compliance item's location clause number and problem type includes: The problem identifier is generated by combining the regulatory clause number and the problem type code; based on the problem-template mapping relationship maintained in the historical problem database, the output includes rectification suggestions containing rectification steps, a list of materials, and a list of supplementary fields.

[0010] Furthermore, the process of converting non-conformities and rectification suggestions into time-limited work orders and assigning them to mobile devices involves the mobile devices verifying version consistency with the central server based on data transmission characteristics, including: The transmission characteristics are network status; when the signal strength is below the threshold or in an offline state, the on-site data collected according to the rectification suggestions is cached locally; after the network is restored, the data is reconciled with the central data server for consistency of work order data, rule base version and work order template version, so that the regulatory standard data of the edge data server is consistent with the regulatory standard data of the central data server.

[0011] Furthermore, the reconciliation of version consistency with the central data server after network recovery, ensuring that the regulatory standard data of the edge data server is consistent with the regulatory standard data of the central data server, includes: The central data server publishes a version summary of the regulatory standard data. This version summary includes the rule base version number, clause version number sequence, rule item version number sequence, clause number range, effective time window, and verification hash. The edge data server retrieves the latest version summary and generates a local version summary upon network recovery. The version summaries from both sides are matched based on the clause number and rule item version number to obtain a sequence of consistent items and a sequence of differing items. If the sequence of differing items is empty, the reconciliation is recorded as successful and ends. If differing items exist, the difference processing procedure is initiated: incremental retrieval is performed for missing items, and expired items are processed... The process involves marking and replacing invalid items, selecting and merging conflicting items based on priority, effective time window, and attributes, and generating a list of changes to be included in the database. For each item on the list, transaction batches are created at the clause level. Dependencies and integrity are verified. Once verified, the batches are written to the edge data server's regulatory standard library. If writing fails, the batch is rolled back and retried a preset number of times. If it still fails, the batch is entered into a manual processing queue. After reconciliation is completed, a reconciliation log is generated, including reconciliation time, network status, reconciliation window, number of differences, number of rollbacks, final version number, and signature timestamp. This log is then archived in conjunction with compliance confirmation records. During the reconciliation period, the rule versions associated with issued but unfinished work orders are frozen and migrated: if the rule upgrade does not include mandatory attribute data verification, it is marked as a compatible upgrade; if it includes mandatory attribute data verification, a rule migration supplementary collection instruction is generated and pushed to the mobile terminal. The reconciliation process uses two-way verification. The edge data server sends the local version digest signature back to the central data server, and the central data server returns a confirmation receipt. If the verification between the two parties passes, they are consistent. If they fail, incremental reconciliation is triggered again. If the reconciliation fails after exceeding the threshold number of times, an abnormal alarm is triggered.

[0012] A real-time monitoring system for business expansion processes of power supply enterprises, characterized in that it applies the aforementioned real-time monitoring method for business expansion processes of power supply enterprises, including a mobile terminal device, an edge data server, and a central data server; the mobile terminal device is communicatively connected to both the edge data server and the central data server; the edge data server is communicatively connected to the central data server. The mobile terminal is used to receive work orders, collect on-site data, and upload and cache supplementary data. The edge data server is used to generate a feature sequence to be compared for compliance, generate non-compliance items and rectification suggestions, perform compliance comparison, and reconcile versions with the central data server. The central data server is used to publish version summaries, archive compliance confirmation records and reconciliation logs, and perform audit maintenance.

[0013] Preferably, the edge data server further includes a rule fusion container, which is used to generate compliance data; the compliance module of the edge data server is used to compare the feature sequence to be compliant with the compliance data.

[0014] Compared with the prior art, the present invention has the following advantages and beneficial effects: By constructing on-site data into a feature sequence to be compared for compliance at the edge and verifying it online with clause-level compliance data, issues such as missing mandatory attributes and inconsistency failures can be identified in real time during the node processing process. Rectification suggestions can be generated and time-limited work orders can be triggered, significantly shortening the problem discovery and handling cycle.

[0015] Version summaries (rule base version number, clause / rule item version number sequence, effective time window and verification hash) and field standardization mapping tables (with version) are introduced to ensure consistency of rules and fields across regions and time periods; the issue identifier contains version information of clauses and issue types, supporting version-level traceability and idempotent processing throughout the entire process.

[0016] Hash fingerprints are used to bind non-conformities to their corresponding original data records / files to ensure consistency and non-repudiation between problem identification, rectification process and archived evidence, thus meeting compliance audit and accountability requirements.

[0017] Mobile devices cache data locally based on network status and signal strength thresholds. After the network is restored, reconciliation is carried out based on version summaries to ensure that work order data, rule base, and template versions are consistent on the edge and center sides, avoiding potential risks such as incorrect rule verification and old template rectification. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of embodiments of the invention and form part of this application, do not constitute a limitation thereof. In the drawings: Figure 1 A flowchart illustrating the real-time monitoring method for business expansion processes in power supply companies; Figure 2 This is a schematic diagram of the version consistency reconciliation process. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments and accompanying drawings. The illustrative embodiments and descriptions of this invention are for illustrative purposes only and are not intended to limit the invention. It should be noted that this invention is already in the actual research and development stage.

[0020] Example 1 like Figure 1 As shown, the real-time monitoring method for the business expansion process of power supply enterprises includes the following steps: Step 1: The mobile terminal collects on-site data of the business expansion process, the edge data server processes the data and generates a feature sequence to be compared for compliance; the rule fusion container retrieves rule data from the regulatory standard library and issue data from the historical issue library in the edge data server and merges them to generate compliance data. Step 2: Compare the feature sequence to be compliant with the compliant data. Missing elements refer to the absence of mandatory fields corresponding to mandatory attributes or the attachments being unreadable / failing the verification. Non-compliance refers to the failure of existence / consistency verification but not the absence of elements. If it is a non-compliance, proceed to Step 3; if it is a missing element, proceed to Step 4; if it is compliant, proceed to Step 5. Step 3: Generate non-conformance items including location information on the edge data server. Based on the location clause number and problem type of the non-conformance item, generate a problem identifier containing the clause version number and the problem type code version number, and generate rectification suggestions. Proceed to Step 5. Step 4: Send a supplementary data collection command to the mobile device. After the supplementary data collection, return to Step 2. Step 5: For the compliant on-site data, a node-level compliance confirmation record is generated. This record is sent from the edge data server to the central data server when the node completion event is triggered. The node completion event is the point in time when the work order corresponding to the node is cleared and all mandatory attributes are verified. The non-compliant items and rectification suggestions are added to the mobile task queue cache. The prompt information for inconsistent recommended attributes is recorded as a general prompt item and added to the task queue, but it does not affect the compliance confirmation conclusion. If there are unprocessed non-compliant items or missing elements, proceed to step 6; otherwise, proceed to step 7. Step 6: Convert non-compliant items and rectification suggestions into work orders with time limits and assign them to mobile devices. The mobile devices and the central data server will verify the consistency of work orders and data versions based on version summaries and track rectification. Step 7: The central data server aggregates node-level compliance confirmation records to form process-level compliance archives, and then completes real-time monitoring of the business expansion process.

[0021] The on-site data includes platform operation records, file images, geographic coordinates, timestamps, form fields, equipment and personnel identifiers, and process node identifiers. The edge data server performs abnormal data removal, duplicate data deduplication, and fills in placeholders for required fields and aligns the time according to the process nodes. It then sends the on-site data to the generated process node data container and concatenates the process node data containers in the order of the process nodes to form a feature sequence to be compared for compliance.

[0022] The rule fusion container retrieves rule data from the rule base and merges it with issue data from the historical issue database to generate compliance data, including: The clause number, scope of application, effective time window, and attributes are analyzed. The issue type, triggering conditions, and reference rectification template corresponding to the clause number are packaged into clause-level compliance data. All clause-level compliance data constitute compliance data. The attributes are mandatory or recommended.

[0023] Based on the business expansion process, the clause-level compliance data of the corresponding process nodes are used to form a node-level compliance data sequence, and the rule version number and effective time window are recorded. The business expansion process is the business process that the power supply company completes from business acceptance, on-site survey, scheme formulation, design review, intermediate inspection, final acceptance, contract signing, meter installation and power supply to archiving after the power user submits the electricity demand. A mapping between feature fields and clause fields is established based on a standardized field mapping table maintained by the edge data server and bearing version numbers. The field data in the process node data container is verified against the corresponding clause-level compliance data of the process node. Specifically: existence verification checks whether mandatory attribute fields are present and non-empty; consistency verification compares values ​​according to the comparison criteria determined by the standardized field mapping table (including case sensitivity, blanks, unit conversion, and file / field hash consistency); applicability verification determines the applicability of a clause based on its scope of application and effective time window; if all verifications pass, compliance is output; if verifications are inconsistent, non-compliance is output; if mandatory attribute data is missing, element missing is output; and recommended attributes generate prompts when applicable but inconsistent.

[0024] Generate non-conformities with location information on the edge data server, including: Location information includes physical location information and abstract location information. Physical location information includes geographic coordinates, data collection timestamp, data collection device identifier, and data collection personnel identifier. Abstract location information includes process node identifier, form field path, regulatory clause number, rule item version number, and issue type code. Non-compliant items are associated with hash fingerprints of the corresponding original on-site data records / files for audit tracing. The hash fingerprint is an irreversible digest value calculated by concatenating the binary content of the corresponding original on-site data record and its associated file.

[0025] The issue identifier is generated by combining the regulatory clause number, clause version number, issue type code, and issue type code version number; based on the issue-template mapping relationship maintained in the historical issue database, the output includes rectification suggestions containing rectification steps, a list of materials, and a list of supplementary fields.

[0026] Data transmission characteristics include network status and signal strength; when the signal strength is below the preset threshold or in an offline state, the on-site data collected according to the rectification suggestions is cached locally; after the network is restored, the data is reconciled with the central data server for consistency of work order data, rule base version and work order template version, so that the rule data of the edge data server is consistent with the rule data of the central data server, and consistency is judged by version summary.

[0027] Example 2 like Figure 2 As shown, the central data server publishes a version summary, which includes the rule base version number, clause version number sequence, rule item version number sequence, clause number range, effective time window, and verification hash. The edge data server retrieves the latest version summary and generates a local version summary upon network recovery. Based on the clause number and rule item version number, the version summaries on both sides are matched to obtain a sequence of consistent items and a sequence of differing items. If the sequence of differing items is empty, the reconciliation is recorded as successful and ends. If differing items exist, the difference processing procedure is initiated: incremental retrieval is performed for missing items, and expired items are marked as invalid. Replacement and merging of conflicting items based on priority, effective time window, and attributes (mandatory / recommended) generate a list of changes to be included in the database. For the list of changes to be included in the database, establish transaction batches at the clause level, verify dependencies and integrity, and write the batches to the edge data server rule base after verification. If writing fails, roll back the batch and retry a preset number of times N. If it still fails, it enters the manual processing queue. After reconciliation is completed, a reconciliation log is generated, including reconciliation time, network status, reconciliation window, number of differences, number of rollbacks, final version number, and signature timestamp, and is archived in conjunction with compliance confirmation records. During the reconciliation period, rule versions associated with issued but incomplete work orders will be frozen and migrated: if the upgrade only involves adjustments to the mapping of recommended attributes or non-verified fields, it will be marked as a compatible upgrade; if it involves the addition, deletion or value domain change of mandatory attributes, it will be considered an incompatible upgrade and a rule migration supplementary collection instruction will be generated and pushed to the mobile terminal. The reconciliation process employs two-way verification. The edge data server sends its local version digest signature back to the central data server, which returns a confirmation receipt. If both parties pass verification, the reconciliation is considered consistent; otherwise, incremental reconciliation is retried. If the reconciliation still fails after exceeding the alarm threshold M, an anomaly alarm is triggered. N and M are configurable preset parameters configured by the central data server and incorporated into version digest management.

[0028] A real-time monitoring system for business expansion processes of power supply enterprises includes mobile devices, edge data servers, and a central data server; the mobile devices are communicatively connected to both the edge data server and the central data server; the edge data server is communicatively connected to the central data server. The mobile terminal is used to receive work orders, collect on-site data, and upload and cache supplementary data. The edge data server is used to generate a feature sequence to be compared for compliance, generate non-compliance items and rectification suggestions, perform compliance comparison, and reconcile versions with the central data server; the edge data server includes at least: a rule fusion container, a compliance module, and a reconciliation module. The central data server is used to publish version summaries, archive compliance confirmation records and reconciliation logs, and perform audit maintenance.

[0029] The edge data server also includes a rule fusion container, which is used to generate compliance data; the compliance module is used to compare the feature sequence to be compliant with the compliance data.

[0030] Example 3 Node-level compliance monitoring and archiving for new installation applications Scenario: Application for new installation of urban power distribution network - on-site survey - meter installation and power connection process.

[0031] Equipment: First mobile terminal A1; First edge data server E1; Central data server C1.

[0032] Rule set version: RulesetV1.12, clause number range: [A100-A399]; field standardization mapping table version: MapV3.4.

[0033] Preset parameters: Signal strength threshold RSSI_T = -95dBm; Preset number of retry attempts N = 3; Alarm threshold M = 5; Effective time window as specified in the terms and conditions metadata.

[0034] Specific process: The first mobile terminal A1 collects the following data at the on-site survey node: platform operation records (form submission, survey start / end events), file images (survey site photos, applicant's ID images, construction permit copies), geographic coordinates and timestamps (dual sources: GNSS and terminal local clock), form fields (application capacity, metering point location, access voltage level, on-site supervisor information), equipment and personnel identification (first mobile terminal A1, employee number U0231), and process node identification (N-SURVEY).

[0035] After completing the removal of abnormal data, deduplication of duplicate data, filling in placeholders for missing attachments, and time alignment, the first edge data server E1 generates a data container for the "Design Review" node. The node data containers corresponding to the "Application" node, "Site Survey" node, and "Table Installation" node are connected sequentially according to the process order to form a compliance comparison feature sequence numbered 2025-09-25-001.

[0036] The rule fusion container loads V1.12 rule data and historical issue database into the first edge data server E1 to generate clause-level compliance data: for example, the first mandatory clause A122: exploration nodes must upload construction permit images; the first recommended clause A231: exploration photos should include close-up views of the metering box.

[0037] Perform verification according to MapV3.4: Existence verification: Construction permit image missing → determined as missing element; Recommended attribute A231 is applicable but inconsistent (near-view identification label missing) → generate prompt information.

[0038] The first edge data server E1 sends a supplementary data collection instruction to the first mobile terminal A1, requesting to take supplementary photos of the construction permit and close-up shots. After the first mobile terminal A1 completes the supplementary data collection on-site, it sends the data back and returns to step two for review. The forced attributes pass, and the prompt message is retained as a general prompt item.

[0039] Non-compliance items and node-level compliance confirmation Non-compliant items (missing construction permit) are automatically closed after review and approval; prompts (missing close-up labels) are still retained and added to the task queue but do not affect the compliance conclusion; a node-level compliance confirmation record CCR#N-SURVEY-00087 is generated, triggered when the work order for that node is cleared and all mandatory attributes are verified and approved; Example of record content: Rule version number: V1.12; Node time window: 2025-09-25 10:25:00~10:58:00; Physical location: 35.69N,139.70E / First mobile terminal A1 / U0231; Abstract location: N-SURVEY / Form.F_licence / A122 / Rule item V05; Evidence fingerprint: A hash calculated by concatenating structured fields of a form and performing binary calculations on the licensed image (Example: sh second mobile terminal A256:4F…9B).

[0040] The first edge data server E1 sends the CCR to the central server C1 when the node completes the event.

[0041] Work order and version consistency confirmation For the prompt item, the first edge data server E1 generates a time-limited work order (48 hours) and assigns it to the first mobile terminal A1; since the on-site RSSI=-102dBm is lower than the threshold, the first mobile terminal A1 caches the work order and supplementary data locally; after the network is restored, it confirms the consistency with the central server C1 based on the version summary, and the verification is successful (the rule base version number, clause sequence, and hash are all consistent).

[0042] Process archiving The central server C1 aggregates the CCRs of each node to form a process-level compliance archive Archive#2025-NEW-00312 and associates it with reconciliation logs and work order closed-loop records.

[0043] Example 4: Reconciliation, Freezing, and Migration in Capacity Expansion / Change Scenarios Scenario: Existing user capacity expansion application — design review — power outage construction — power restoration acceptance.

[0044] Equipment: Second mobile terminal A2; Second edge data server E2; Central data server C1.

[0045] Initial rule version: RulesetV1.13 (clause scope [B100-B499]); mapping table version: MapV3.6.

[0046] Preset parameters: RSSI_T=-95dBm, N=3, M=5.

[0047] Data Acquisition and Feature Sequence At the design review node (N-DESIGN), the second mobile terminal A2 collects and uploads: single-line diagram PDF, conductor cross-section and protection setting fields, electronic signature image of the reviewer, and qualification documents of the construction unit.

[0048] After completing the removal of abnormal data, deduplication of duplicate data, filling in placeholders for missing attachments, and time alignment, the second edge data server E2 generates a data container for the "Design Review" node. Subsequently, the data containers for the four nodes "Application", "Design Review", "Construction" and "Acceptance" are connected sequentially according to the actual process order to form a compliance comparison feature sequence numbered 2025-09-25-079.

[0049] Compliance comparison and non-compliance items According to clause V1.13: B210 (Mandatory): The design review must provide a description of the conductor cross-section and match the capacity; Second Mandatory Clause B325: The construction unit's qualifications must be valid; Second Recommended Clause B441: The single-line diagram must include grounding markings.

[0050] Verification results: The construction unit's qualification validity period has expired at the current time → output non-compliance item; the single-line diagram is missing grounding annotations → generate prompt information; the existence and consistency of other mandatory fields pass.

[0051] A non-compliance item NF#2025-Second Edge Data Server E2-0016 was generated, with location information including: N-DESIGN / Form.F_license_validity / B325 / Rule Item V07 / U0456 / 35.71N,139.68E; A hash fingerprint was calculated and bound: a summary was generated from the binary + field concatenation of the qualification PDF; Problem identifier: B325@V07+TYPE:EXPIRED@V02; Rectification suggestion: Upload the new version of the qualification PDF and supplementary verification instructions (material list + supplementary field list automatically generated). The prompt message (B441) was added to the task queue but does not affect the compliance conclusion. Not all mandatory items for the node passed, and the node completion event was not triggered; therefore, a CCR was not generated and submitted.

[0052] Time-limited work orders and offline caching The second edge data server E2 converts non-compliance items and rectification suggestions into 24-hour time-limited work orders and assigns them to the second mobile terminal A2. When the site is offline, the second mobile terminal A2 caches the rectification images and form revisions locally. After the network is restored, the second mobile terminal A2 sends a consistency confirmation request to the central server C1.

[0053] Version consistency reconciliation and incompatible upgrades During the recovery period, the central server C1 released a new version of the digest RulesetV1.14, in which the value domain of clause B325 was changed (electronic signature verification was added as a mandatory attribute), which was determined to be an incompatible upgrade; the second edge data server E2 pulled the digest and matched it with the local digest, and obtained the sequence of differences {B325@V08,B210@V06}. Perform difference processing: incrementally retrieve missing items; mark expired items as invalid and replace them; select and merge conflicting items based on priority, effective time window and attributes to form a list of changes to be included in the database; create transaction batches for writing at the clause level. If batch #1 is successfully written, batch #2 fails on the first attempt → automatically rollback and retry, succeeding after N=3 retries.

[0054] During the reconciliation period, the associated rule versions for incomplete work orders were frozen. Due to B325 involving a mandatory attribute change, the second edge data server E2 automatically generated a rule migration supplementary collection instruction, requiring the supplementary collection of electronic signature verification screenshots and signature verification result fields. The instruction was pushed to the second mobile terminal A2.

[0055] Supplementary sampling, re-verification, and completion of key milestones The second mobile terminal A2 collects two additional materials according to the migration instructions and sends them back; the second edge data server E2 re-verifies based on RulesetV1.14 and MapV3.6: B325 mandatory item passes (validity period and electronic signature verification both pass); B441 prompt item is retained.

[0056] When the node completes the event, the second edge data server E2 generates CCR#N-DESIGN-00421 and sends it to the central server C1; the central server C1 records the reconciliation log elements: reconciliation time, reconciliation window, number of differences (2), number of rollbacks (1), final version number (V1.14), signature timestamp, etc.; if the number of consecutive failures of reconciliation two-way verification is ≥M=5, an abnormal alarm is triggered (not triggered in this embodiment).

[0057] Process-level archiving and auditing Construction and acceptance milestones are completed according to the aforementioned criteria; after all mandatory items are passed, the central server C1 summarizes the CCRs of each milestone to form a process-level compliance archive Archive#2025-UPG-00109. The archive is also associated with: work order closed-loop records (closing time of non-conformities, verification results of supplementary materials), version reconciliation logs (details of differences and transaction batch writing results), and evidence fingerprint index (facilitating subsequent audit traceability).

[0058] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for real-time monitoring of business expansion processes in power supply enterprises, characterized in that, Includes the following steps: Step 1: The mobile terminal collects on-site data of the business expansion process, and the edge data server processes the data to generate a feature sequence to be compared for compliance. The rule fusion container parses the clause number, scope of application, validity period and attributes of the regulatory standard data. The problem type, triggering conditions and reference rectification template corresponding to the clause number are packaged to form clause-level compliance data. All clause-level compliance data constitute compliance data. The attributes are mandatory or recommended. Step 2: Based on the business expansion process, construct a node-level compliance data sequence from the clause-level compliance data of the corresponding process nodes, and record the rule version number and effective time window; wherein, the business expansion process is the business process from business acceptance, on-site survey, scheme formulation, design review, intermediate inspection, final acceptance, contract signing, meter installation and power supply to archiving after the power user submits the electricity demand. A mapping between feature fields and clause fields is established based on a standardized field mapping table maintained by the edge data server and bearing version numbers. The on-site data in the process node data container is verified against the corresponding clause-level compliance data of the process node, including existence and consistency verification of mandatory attribute data; applicability and consistency verification of recommended attribute data; and validity verification of the validity period field at the current time point. If all verifications pass, compliance is output; if verifications are inconsistent, non-compliance is output; if mandatory attribute data is missing, element is output; a prompt message is generated when recommended attributes are applicable but inconsistent; if it is a non-compliance, proceed to step three; if it is an element missing, proceed to step four; if it is compliant, proceed to step five. Step 3: Generate non-conformity items including location information on the edge data server. Based on the location clause number and problem type of the non-conformity item, generate a problem identifier and generate rectification suggestions, then proceed to Step 5. Step 4: Send a supplementary data collection command to the mobile device. After the supplementary data collection, return to Step 2. Step 5: Generate node-level compliance confirmation records for the compliant on-site data. These records are sent from the edge data server to the central data server by triggering node completion events. Add non-compliant items and rectification suggestions to the mobile task queue cache. If there are unprocessed non-compliant items or missing elements, proceed to step 6; otherwise, proceed to step 7. The node completion event is the point in time when the business expansion processing work order or rectification work order corresponding to the process node is cleared and all mandatory attributes are verified. Step Six: Convert non-compliant items and rectification suggestions into time-limited work orders and assign them to mobile devices. The mobile devices and central data servers confirm the consistency of work order and data versions and track rectification. The transmission characteristic is network status. When the signal strength is below the threshold or offline, the on-site data collected according to the rectification suggestions is locally cached. After the network is restored, a consistency reconciliation is performed with the central data server regarding work order data, rule base version, and work order template version, ensuring consistency between the regulatory standard data on the edge data server and the regulatory standard data on the central data server. The central data server publishes a version summary of the regulatory standard data, which includes the rule base version number, clause version number sequence, rule item version number sequence, clause number range, effective time window, and verification hash. The edge data server retrieves the latest version summary and generates a local version summary when the network is restored. Based on the clause... The reconciliation process matches the version summaries of both sides with the item number and rule item version number to obtain a sequence of consistent items and a sequence of differing items. If the sequence of differing items is empty, the reconciliation is recorded as successful and ends. If there are differing items, the process proceeds to the difference processing flow: incremental retrieval is performed for missing items, invalidation marking and replacement are performed for expired items, and conflicting items are selected and merged based on priority, effective time window and attributes to generate a list of changes to be included in the database. Transaction batches are created for the list of changes to be included in the database at the item level, and the dependencies and integrity are verified. After verification, the batches are written to the edge data server's regulatory standard library. If the writing fails, the batch is rolled back and retried a preset number of times. If it still fails, it enters the manual processing queue. After the reconciliation is completed, a reconciliation log is generated. The reconciliation log includes the reconciliation time, network status, reconciliation window, number of differences, number of rollbacks, final version number and signature timestamp, and is archived in association with the compliance confirmation record. During the reconciliation period, rule versions associated with issued but incomplete work orders are frozen and migrated: if the upgrade only involves adjustments to the mapping of recommended attributes or non-verified fields, it is marked as a compatible upgrade; if it involves the addition, deletion, or value domain change of mandatory attributes, it is considered an incompatible upgrade and a rule migration supplementary collection instruction is generated and pushed to the mobile terminal. The reconciliation process uses two-way verification. The edge data server sends the local version digest signature back to the central data server, and the central data server returns a confirmation receipt. If the verification between the two parties passes, they are consistent. If they fail, incremental reconciliation is triggered again. If the reconciliation fails after exceeding the threshold number of times, an abnormal alarm is triggered. Step 7: The central data server aggregates node-level compliance confirmation records to form process-level compliance archives, and then completes real-time monitoring of the business expansion process.

2. The real-time monitoring method for business expansion processes of power supply enterprises according to claim 1, characterized in that, The edge data server processes the on-site data to generate a feature sequence for compliance comparison, including: The on-site data includes platform operation records, file images, geographic coordinates, timestamps, form fields, equipment and personnel identifiers, and process node identifiers. The edge data server performs abnormal data removal, duplicate data deduplication, and fills in placeholders for required fields and aligns the time according to the process nodes. It then sends the on-site data to the generated process node data container and concatenates the process node data containers in the order of the process nodes to form a feature sequence to be compared for compliance.

3. The real-time monitoring method for business expansion processes of power supply enterprises according to claim 1, characterized in that, The generation of non-conformities with location information on the edge data server includes: The location information includes physical location information and abstract location information. The physical location information includes geographic coordinates, data collection timestamp, data collection device identifier, and data collection personnel identifier. Abstract location information includes process node identifiers, form field paths, regulatory clause numbers, rule item version numbers, and issue type codes; The non-conformity items are associated with the hash fingerprints of the corresponding original on-site data records / files for audit tracing.

4. The real-time monitoring method for business expansion processes of power supply enterprises according to claim 3, characterized in that, The process of generating a problem identifier and generating rectification suggestions based on the non-compliance item's location clause number and problem type includes: The problem identifier is generated by combining the regulatory clause number and the problem type code; based on the problem-template mapping relationship maintained in the historical problem database, the output includes rectification suggestions containing rectification steps, a list of materials, and a list of supplementary fields.

5. A real-time monitoring system for business expansion processes in power supply enterprises, characterized in that: The real-time monitoring method for business expansion processes of power supply enterprises according to any one of claims 1-4 includes a mobile terminal device, an edge data server, and a central data server; the mobile terminal device is communicatively connected to the edge data server and the central data server respectively; the edge data server is communicatively connected to the central data server. The mobile terminal is used to receive work orders, collect on-site data, and upload and cache supplementary data. The edge data server is used to generate a feature sequence to be compared for compliance, generate non-compliance items and rectification suggestions, perform compliance comparison, and reconcile versions with the central data server. The central data server is used to publish version summaries, archive compliance confirmation records and reconciliation logs, and perform audit maintenance.

6. The real-time monitoring system for business expansion processes of power supply enterprises according to claim 5, characterized in that, The edge data server also includes a rule fusion container, which is used to generate compliance data; the compliance module of the edge data server is used to compare the feature sequence to be compliant with the compliance data.

Images