Transformer operation and maintenance data management system based on block chain

Abstract

The invention relates to the technical field of information and communication suitable for supervision, in particular to a block chain-based transformer operation and maintenance data management system, which comprises the following steps of: analyzing a service level protocol into automatically executable commercial contract terms deployed on a chain in a smart contract form through a protocol analyzer; the commercial contract terms are automatically triggered to generate an operation and maintenance work order based on transformer real-time data monitored by an oracle machine; receiving and verifying a completion report, driving a multi-party collaborative acceptance process through commercial contract terms, and finally generating an acceptance voucher containing multi-party digital signatures; generating a verifiable digital certificate for the digital identity of the transformer according to the acceptance certificate, taking the verifiable digital certificate as a non-tampering historical record, and solidifying the verifiable digital certificate in a distributed ledger; according to the invention, high-credibility transformer operation and maintenance management is realized based on the block chain technology, and intelligentization of transformer operation and maintenance management is realized through the chain contract which can be automatically executed.

Description

Technical Field

[0001] This invention relates to the field of information and communication technology for supervisory purposes, specifically to a blockchain-based transformer operation and maintenance data management system. Background Technology

[0002] In modern industrial systems, key assets, such as transformers, are the cornerstone of ensuring the stable operation of the social economy. To ensure the safety and efficiency of these high-value assets, industry management models are evolving from traditional planned maintenance to data-driven intelligent operation management. To address this challenge, existing technologies primarily rely on various centralized management systems to collect and manage operational data to support operational decisions.

[0003] However, these technical solutions are fundamentally limited by the current mainstream centralized management paradigm. Under this paradigm, the management and control of operational data are highly concentrated in the hands of a single responsible entity, leading to difficulties in establishing trust and insufficient transparency in operational process management during multi-party collaboration. Furthermore, due to the lack of a unified and reliable mechanism, when executing long-cycle tasks across departments or enterprises, management problems often arise such as unclear responsibility definitions and ineffective traceability of operational processes. Moreover, the trust issues arising from this centralized trust model also restrict the level of automation in cross-organizational operational processes.

[0004] In summary, existing technologies still need improvement in systematically addressing a series of fundamental problems arising from the centralized management paradigm of operation and maintenance data, such as the lack of data trust, difficulties in tracing the entire lifecycle of operation and maintenance, and low automation levels in cross-entity collaborative processes. Therefore, there is an urgent need in this field for a novel operation and maintenance paradigm centered on decentralized management of transformer operation and maintenance data. This paradigm aims to establish decentralized trust in operation and maintenance processes through multi-party collaboration, ensuring the credibility of tracing the entire lifecycle of transformer operation and maintenance, and automating the execution of operation and maintenance rules.

[0005] To address this, a blockchain-based transformer operation and maintenance data management system is proposed. Summary of the Invention

[0006] The purpose of this invention is to provide a blockchain-based transformer operation and maintenance data management system that parses service level agreements (SLAs) into automatically executable on-chain commercial contract terms; acquires real-time transformer operation data through an oracle mechanism and automatically generates operation and maintenance work orders based on the commercial contract terms. After multiple parties complete collaborative acceptance through on-chain transactions, the performance data containing the digital signatures of both parties is encapsulated into a business credential, and a verifiable digital certificate is generated for the transformer's digital identity based on this credential, which is then recorded in a distributed operation ledger.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a blockchain-based transformer operation and maintenance data management system, comprising: Protocol Execution Module: The protocol parser parses the service level agreement into automatically executable commercial contract terms and deploys them on the blockchain in the form of smart contracts; the oracle mechanism monitors the real-time operation data of the transformer associated with digital identity, and based on the commercial contract terms and real-time operation data, the smart contract automatically generates maintenance work orders containing unique identifiers and initial states. Collaborative Acceptance Module: Receives completion report submission transactions initiated by third-party operations and maintenance personnel, which reference unique identifiers; verifies the validity and current status of the operations and maintenance work order pointed to by the unique identifier through a smart contract; performs collaborative acceptance based on the acceptance criteria in the commercial contract terms, triggers a change in the status of the operations and maintenance work order, and generates acceptance certificates and digital signatures of the corresponding completion report source and acceptance certificate source. Shared ledger module: Executes status update transactions. The status update transactions generate verifiable digital certificates for the digital identity of the transformer pointed to by the maintenance work order based on the business credentials composed of the completion report, acceptance certificate and corresponding digital signature, and record them in the distributed operation ledger.

[0008] Preferably, the specific process of parsing the service level agreement into automatically executable commercial contract terms using a protocol parser and deploying it on the blockchain in the form of a smart contract includes: The protocol execution module also provides a domain language for structurally describing the service level agreement. The domain language includes standardized syntax keywords for defining performance indicators, agreement reward and penalty clauses, and multi-party operation permissions, as well as expression structures for describing conditional logic and numerical thresholds. The protocol parser is configured to receive a service level agreement written in the domain language and automatically compile it into the commercial contract terms.

[0009] Preferably, the specific process of monitoring the real-time operating data of the transformer associated with the digital identity through the oracle mechanism includes: An off-chain oracle node network obtains the real-time operating data from the transformer data source via an application programming interface; the oracle node network generates a data report containing the real-time operating data and the digital identity of the transformer corresponding to the real-time operating data; the oracle node network submits the data report as an on-chain transaction to the blockchain by calling the data reporting function of the smart contract, using the data report as an input parameter.

[0010] Preferably, based on commercial contract terms and real-time operational data, the specific process by which a smart contract automatically generates an operation and maintenance work order containing a unique identifier and initial state includes: The smart contract executes the agreed-upon condition judgment logic defined in the commercial contract terms, and determines whether the preset trigger conditions are met based on real-time operation data; when the agreed-upon event trigger conditions are met, the smart contract instantiates an operation and maintenance work order data structure and assigns the initial operation and maintenance process state value to the state variable of the data structure; the smart contract generates a globally unique identifier for the operation and maintenance work order data structure that tracks the life cycle of the operation and maintenance process, and records the data structure and the identifier on the blockchain.

[0011] Preferably, the specific process by which a smart contract verifies the validity and current status of an operation and maintenance work order pointed to by a unique identifier includes: Based on the unique identifier, a location operation is performed within the data structure used to store all maintenance work order objects to retrieve the corresponding maintenance work order object; the status variable value of the retrieved maintenance work order is read, and the status variable value represents the current status of the maintenance work order; the smart contract logically compares the current status with a set of valid states that are predefined in the commercial contract terms and allow subsequent operations to be performed; based on the results of the location operation and the logical comparison, the validity of the maintenance work order and its current status are verified.

[0012] Preferably, the specific process of performing collaborative acceptance based on the acceptance standards and procedures in the commercial contract terms, triggering a change in the operation and maintenance work order status, and generating digital signatures for the source of the acceptance certificate and the corresponding completion report, includes: The machine acceptance logic defined in the commercial contract terms is executed. The machine acceptance logic compares the operation and maintenance data included in the completion report submission transaction with the acceptance standards preset in the commercial contract terms to obtain the comparison result. The smart contract receives the on-chain confirmation transaction initiated by the authorized account of Power Grid Company A preset in the commercial contract terms. The on-chain confirmation transaction is executed, and the status variable of the operation and maintenance work order pointed to by the unique identifier is updated to complete the status change. An acceptance certificate containing the comparison result and the timestamp of the on-chain confirmation transaction is instantiated. The cryptographic signature generated by the private key of the initiator account is captured to obtain the digital signature. The initiator account corresponds to the initiator of the completion report submission transaction and the initiator of the on-chain confirmation transaction, respectively.

[0013] Preferably, the execution of the status update transaction, which generates a digital certificate for the transformer digital identity pointed to by the maintenance work order based on the business credential composed of the completion report, acceptance certificate, and corresponding digital signature, and records it in the distributed operation ledger, specifically includes the following process: The completion report, acceptance certificate, and digital signature are encapsulated into a business certificate; and based on the business certificate, a verifiable digital certificate that conforms to the decentralized identity standard and the verifiable certificate standard is generated; the verifiable digital certificate is a structured data object containing the cryptographic hash value of the business certificate, an identifier pointing to the smart contract address, and an identifier pointing to the digital identity of the transformer; the distributed operation ledger is composed of blockchain and off-chain distributed storage.

[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: 1. This invention transforms traditional protocols into automated processes by parsing service level agreements into automatically enforceable commercial contract terms on the blockchain. This fundamentally eliminates the reliance on centralized platforms for human trust in multi-party collaborations, significantly reduces communication and arbitration costs caused by opaque processes and ambiguous responsibility definitions, and thus greatly improves the efficiency of cross-entity operation and maintenance collaboration.

[0015] 2. This invention constructs an immutable, cryptographically supported single source of fact for the entire lifecycle of transformer operation and maintenance. Every key node from work order generation to collaborative acceptance is recorded by on-chain transactions containing multi-party digital signatures, realizing end-to-end trusted traceability of the operation and maintenance process. This solves the technical problems of auditing difficulties and inability to define responsibilities caused by data silos and tamperable records in existing technologies.

[0016] 3. This invention ultimately generates a standardized and verifiable digital certificate for the digital identity of transformers. This certificate, as a trusted proof of status that can be independently cryptographically verified by any third party, breaks down the data barriers of traditional centralized systems, significantly enhancing the credibility and liquidity of asset operation and maintenance status data, and providing a solid foundation of data trust for scenarios such as asset insurance, compliance auditing, and future asset transactions. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the structure of a blockchain-based transformer operation and maintenance data management system proposed in this invention; Figure 2 This is a system flowchart of a blockchain-based transformer operation and maintenance data management system proposed in this invention; Figure 3 This is a schematic diagram of the blockchain structure proposed in this invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. 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] See Figure 1 This is a schematic diagram of the structure of a blockchain-based transformer operation and maintenance data management system proposed in this invention. The specific content includes: Protocol Execution Module: The protocol parser parses the service level agreement into automatically executable commercial contract terms and deploys them on the blockchain in the form of smart contracts; the oracle mechanism monitors the real-time operation data of the transformer associated with digital identity, and based on the commercial contract terms and real-time operation data, the smart contract automatically generates maintenance work orders containing unique identifiers and initial states. Collaborative Acceptance Module: Receives completion report submission transactions initiated by third-party operations and maintenance personnel, which reference unique identifiers; verifies the validity and current status of the operations and maintenance work order pointed to by the unique identifier through a smart contract; performs collaborative acceptance based on the acceptance criteria in the commercial contract terms, triggers a change in the status of the operations and maintenance work order, and generates acceptance certificates and digital signatures of the corresponding completion report source and acceptance certificate source. Shared ledger module: Executes status update transactions. The status update transactions generate verifiable digital certificates for the digital identity of the transformer pointed to by the maintenance work order based on the business credentials composed of the completion report, acceptance certificate and corresponding digital signature, and record them in the distributed operation ledger. Example

[0020] See Figure 2This is a system flowchart of a blockchain-based transformer operation and maintenance data management system proposed in this invention. This embodiment provides a specific application of the blockchain-based transformer operation and maintenance data management system. A typical application scenario is that Power Grid Company A and Operation and Maintenance Company B signed an operation and maintenance service agreement for a 500kVA oil-immersed transformer T-001 in Substation A of Region A. To ensure that each on-chain digital identity (DID) uniquely and reliably corresponds to a physical transformer entity, this system executes a strict initialization binding process when the asset is first connected to the network. This process requires: at the transformer installation site, a certified engineer holding an authorized digital certificate uses a dedicated, trusted mobile terminal to scan the QR code containing a unique physical serial number embedded on the transformer. Simultaneously, the terminal reads the public key generated by the tamper-proof security chip built into the transformer via secure near-field communication. Subsequently, the terminal packages the physical serial number and public key into a 'binding statement,' which is then signed by the certified engineer using their digital certificate. This signed 'binding statement' is ultimately submitted to the on-chain asset registration contract. Only after verifying the engineer's authorization does the contract officially generate and record the corresponding DID for the physical serial number. This process ensures that the mapping from the physical world to the digital world is rigorously verified by multiple parties, providing a trusted root for all subsequent maintenance data management based on this DID. The maintenance service agreement stipulates that the transformer winding temperature must be below 95°C. If the temperature exceeds 95°C and remains above 95°C for 15 minutes, an abnormal alarm will be triggered, requiring immediate work order dispatch. If Maintenance Company B fails to submit a completion report within 24 hours of work order generation, it will face contract penalties; if it successfully completes the work within the stipulated time and the data meets the requirements, it will receive a service fee. Power Grid Company A has the final acceptance authority; Maintenance Company B has the authority to execute work orders and submit completion reports.

[0021] Furthermore, the process of parsing the service level agreement into automatically executable commercial contract terms using a protocol parser and deploying it as a smart contract on the blockchain corresponding to the aforementioned protocol execution module is as follows: Defining and Using the Domain Language: The protocol execution module provides a domain language specifically designed for power operation and maintenance protocols. Its core components include: contract header, asset definition, performance metrics, protocol rules, and access control. This domain language employs a strict hierarchical structure. A valid protocol script must use a 'contract header' as its root element. Core components such as 'asset definition', 'performance metrics', 'protocol rules', and 'access control' exist as direct child elements of the 'contract header' and cannot be nested. The 'protocol rules' component acts as a container, containing one or more independent 'rule' definitions. Each 'rule' definition must contain a 'condition' child element and an 'action' child element. This pre-defined, fixed hierarchy and parent-child relationship ensures that any protocol script has a unique structure that can be deterministically parsed by the protocol parser. The domain language includes a standardized vocabulary and syntax, capable of precisely describing the agreed-upon logic within the protocol, such as using specific keywords to define performance metrics, protocol reward and punishment clauses, and multi-party operation permissions. The domain language includes keywords such as DEFINE_KPI for defining performance metrics, PENALTY for protocol reward and punishment clauses, and PERMISSION for multi-party operation permissions, as well as expression structures such as ON_CONDITION, ACTION, and DURATION for describing conditional logic and numerical thresholds. The protocol parser contains a predefined mapping rule library. When the parser recognizes PERMISSION (role='Operator', address='0x...') in the DSL script, it maps it to a mapping (address=>bool) state variable and a modifier function in the Solidity smart contract to implement access control. When it parses PENALTY (condition='Timeout 24 hours', action='Fine 1 ETH'), it generates a function containing the require(block.timestamp>creationTime+24hours) judgment logic and calls the funds transfer interface. To achieve automatic compilation, the protocol parser first performs lexical and syntactic analysis on the DSL script, converting it into an abstract syntax tree data structure. Subsequently, a code generator module traverses this tree, converting different node types into corresponding code structures for smart contracts according to preset mapping rules. For example, the node corresponding to the PERMISSION keyword is mapped to an address-type state variable, while the ON_CONDITION expression is mapped to a function body containing agreed-upon conditional judgment logic, implementing commercial contract terms that can be automatically enforced by the machine. The administrator of Power Grid Company A uses the domain language to meticulously compile the aforementioned service agreement content into a structured script file.The script file clearly specifies all core protocol conditions, including the roles of each party, temperature thresholds, response times, and late payment penalties. Protocol parsing and smart contract compilation: The protocol parser receives this protocol script written in DSL. Its task is to understand the agreed-upon logic in the script and automatically translate it into executable smart contract code on the blockchain. The protocol parser identifies every keyword and expression in the script, such as the condition "if the transformer winding temperature exceeds 95°C for 900 seconds," and converts it into specific functions and state variables in the smart contract. The final generated code is completely faithful to the protocol rules described in the protocol script. After the protocol parser compiles the abstract syntax tree into smart contract code but before its formal deployment on the blockchain, a sandbox simulation module is added. This simulation module creates an off-chain virtual operating environment. Administrators of Power Grid Company A can not only write domain-specific language scripts but also input simulated transformer operating data into this sandbox environment: a virtual temperature, humidity, and load data stream for an entire day. The smart contract generated by the protocol parser is executed in this environment, simulating in real time whether the contract will trigger work orders, calculate fines, and change status as expected under different data inputs; the event log of the entire simulation process is presented to the administrator visually. This process, by adding a deterministic simulation verification step before deploying the smart contract, verifies technical risks in advance, solving the problem that smart contracts cannot be changed once deployed. It allows protocol stakeholders to fully test and verify complex protocol logic in a zero-cost, zero-risk environment, ensuring that the final on-chain commercial contract terms meet expectations, significantly improving the system's reliability and security. Smart Contract Deployment and Process Governance: The compiled smart contract code is automatically deployed to the blockchain; the blockchain adopts a consortium blockchain architecture, deployed based on the Hyperledger Fabric framework. Consortium members include Power Grid Company A, Maintenance Company B, and equipment manufacturers. Data read and write permissions are strictly isolated through Fabric channels and Access Control Lists (ACLs). Once deployed, this smart contract becomes an unalterable commercial contract, and no one can tamper with its content. From then on, all operation and maintenance activities related to transformer T-001 will be strictly bound by this contract. For example, if maintenance company B fails to submit a completion report on time, the smart contract will automatically execute the penalty logic and generate a traceable penalty record. The whole process does not require any human intervention or arbitration.

[0022] The aforementioned process, by providing a domain-specific language, transforms complex operational protocols into a structured, machine-readable format, automating the smart contract generation process. This significantly reduces the cost and error risk of manual coding, while simultaneously improving the agility and transparency of commercial contract deployment. The mandatory automated execution of smart contracts significantly enhances trust in cooperation among all parties, bringing unprecedented efficiency and credibility to the entire operational ecosystem.

[0023] Furthermore, the real-time operating data of the transformer associated with the digital identity is monitored through an oracle mechanism. Based on the commercial contract terms and the real-time operating data, the smart contract automatically generates a maintenance work order containing a unique identifier and initial state corresponding to the aforementioned protocol execution module. The specific process is as follows: By deploying a network of oracle nodes independent of the blockchain network, real-world transformer data is obtained. During the initial deployment phase, the system administrator first deploys an oracle management contract on the blockchain. This contract is the core infrastructure of the system, and its main functions include: Node registration and management: providing an interface for verified oracle node operators to register, recording their on-chain address, public key, and staking information; Reputation system: implementing a reputation scoring system to record and update the historical performance of each node; Data request interface: providing a standardized `requestData(asset_did, kpi_name)` function for other service smart contracts to call and obtain trusted off-chain data. Consensus and Aggregation Logic: The coordination process of the consensus and aggregation logic follows a mechanism driven by on-chain smart contracts. The specific steps are as follows: When a service smart contract needs data, it sends a data request to the oracle management contract. The oracle management contract assigns a set of nodes for the current task based on its internal node list sorted by reputation score. This node set includes a 'master node' (i.e., the highest reputation node in the current list) acting as a coordinator and several 'participating nodes'. The oracle management contract issues an on-chain event containing the task ID and the addresses of all assigned nodes. After all assigned nodes hear the event, they independently retrieve data from the data source. The 'participating nodes' send their data reports to the 'master node,' which executes the consensus algorithm locally and aggregates the data. The 'master node' then submits the final result along with all evidence back to the oracle management contract for on-chain verification. After the task is completed, the management contract performs a reputation score adjustment and rotates the current 'master node' to the appropriate position in the list. This process clarifies that the selection of all nodes and the assignment of tasks are deterministically initiated by the on-chain contract, with the master node only responsible for off-chain coordination and computation. The oracle network employs a decentralized network consisting of at least five independently operating oracle nodes. Node information is registered in the oracle management contract. These nodes continuously and stably acquire real-time operational data from the data source of transformer T-001—the data acquisition and monitoring system—through a pre-defined application programming interface (API). Every five minutes, the oracle nodes obtain the latest transformer winding temperature data via API calls. For example, the transformer winding temperature data obtained by a node might be: {"temp_sensor_id": "TS-001", "timestamp": "2025-09-12T10:05:00Z", "value": 94.5}. After acquiring the real-time data, the oracle node network performs data verification and aggregation operations.To ensure the authenticity and consistency of data sources, the oracle network employs a multi-node cross-validation mechanism. This mechanism uses consensus verification: when the oracle management contract receives data reports from multiple nodes, it executes the following verification logic: First, it determines a data anchor point as the median of all reported values. Then, it counts how many values ​​among all reported data fall within ±0.5% of the anchor point's error range. When the number of nodes within this range reaches or exceeds 80% of the total number of nodes, consensus is considered achieved. After consensus is reached, the contract calculates the arithmetic mean of all data that meet the error range requirement and uses this average as the final reliable data. If, within a specified time, less than 80% of nodes meet the consensus conditions, the data request fails, an anomaly event is recorded, and a dynamic reputation score is assigned to each oracle node participating in data reporting. The reputation score is a state variable with the same initial value stored in the smart contract. Upon reaching consensus in each round of data reporting, the smart contract automatically executes the reputation score adjustment logic: increasing the reputation score of honest nodes whose reported data deviates slightly from the average consensus value of all nodes; deducting the reputation score of nodes whose reported data deviates significantly from the average consensus value of all nodes or who did not participate in reporting; and employing a reputation-weighted consensus algorithm in subsequent data requests, giving higher weight to the reported data of nodes with high reputation scores when calculating consensus. This process, by introducing an adaptive, historical performance-based game theory mechanism, enables the oracle network to self-optimize. It not only more effectively defends against potential malicious nodes attempting coordinated attacks within the error range but also incentivizes all nodes to continuously provide high-quality, high-precision services. This process elevates the reliability of the data source from a static group consensus level to a dynamic system level, further enhancing the reliability of the data source. This mechanism can identify and exclude outlier data that differs excessively from the consensus value, ensuring the authenticity of the data uploaded to the blockchain. To ensure the long-term stable operation of the oracle network, each node needs to stake tokens as collateral. Nodes submitting valid data will receive token rewards, while nodes submitting malicious data will have their staked tokens deducted. After verification, the oracle node network will generate a structured data report. This data report associates the acquired real-time operating data with the transformer T-001's unique digital identity DID: T-001 on the blockchain. The data report includes data type, timestamp, and data value: the specific report content is: {"transformer_did": "DID: T-001", "data_type": "winding_temp", "timestamp": "2025-09-12T10:05:00Z", "value": 94.5}.After generating the data report, the oracle node network calls the data reporting function in the oracle management contract deployed on the blockchain, submitting the data report as input parameters to the blockchain as an on-chain transaction. This on-chain transaction includes not only the data report itself but also the oracle network's cryptographic signature, proving the data's source is trustworthy. Once the transaction is packaged and added to the blockchain, the data report becomes an immutable on-chain record. Smart contracts can access and utilize the on-chain data report to execute pre-defined logic, determining whether the conditions for triggering a maintenance work order are met based on the temperature value. In this way, the oracle mechanism successfully and securely bridges off-chain data to the blockchain, providing a solid foundation for automated decision-making in smart contracts.

[0024] The above process, through multi-node cross-verification and cryptographic signatures, ensures the authenticity and tamper-proof nature of the data on the blockchain, providing a reliable foundation for automated decision-making in smart contracts and eliminating reliance on manual data input. Simultaneously, the transformer's real-time operating data is transformed into immutable on-chain records, allowing both Power Grid Company A and Maintenance Company B to view the equipment status in real time and transparently. This significantly improves the response speed of the maintenance process, eliminates disputes regarding data authenticity, and substantially reduces trust costs in collaboration.

[0025] Furthermore, based on the terms of the commercial contract and real-time operational data, the smart contract automatically generates an operation and maintenance work order containing a unique identifier and initial state corresponding to the aforementioned protocol execution module. The specific process is as follows: The smart contract continuously receives real-time operating data of transformer T-001 submitted by the oracle network. Upon receiving data, the smart contract immediately executes its internally defined conditional judgment logic. It judges the real-time temperature data according to the terms of the commercial contract, checking whether the preset trigger condition of "transformer winding temperature exceeding 95°C" is met. To implement the judgment of the transformer's state, the smart contract defines state variables, including an integer counter to record the number of consecutive high-temperature events. Whenever the oracle calls the smart contract's data reporting function through an on-chain transaction, the contract's logic is passively triggered: if the reported temperature is higher than 95°C, the counter is incremented; if it is lower than or equal to 95°C, the counter is reset to zero. When the counter value reaches 3 after an update, the trigger condition is deemed met. Once the agreed-upon event triggering conditions are met, the smart contract automatically executes subsequent operations: It instantiates a maintenance work order data structure, which is a structured data object containing the following fields: unique work order identifier (WOID), transformer digital identity (DID), trigger time (timestamp), trigger event details (trigger_event), and current state (state). It assigns a globally unique identifier, WO-20250912-T001-001, to the maintenance work order data structure, allowing for tracking the entire lifecycle of the maintenance process. Simultaneously, the smart contract assigns an initial value, "PENDING," to the status variable of the maintenance work order. Finally, the smart contract stores the maintenance work order data structure, containing the identifier and initial state, in an immutable form on the blockchain. Afterward, Company B's maintenance system can instantly detect newly generated work orders, respond immediately, and schedule maintenance tasks. The entire process is fully automated, requiring no manual intervention, ensuring the timeliness and accuracy of the maintenance response.

[0026] The above process utilizes the built-in conditional judgment logic of the smart contract to respond in real time to anomalies in transformer operating data and immediately trigger the creation of work orders. This instant response mechanism significantly reduces the lag time in fault handling, improving operation and maintenance efficiency and security. Furthermore, assigning a globally unique identifier to each work order and storing it immutably on the blockchain ensures the traceability and transparency of the operation and maintenance process, providing a reliable data foundation for subsequent accountability and performance evaluation.

[0027] Furthermore, the smart contract verifies the validity of the maintenance work order pointed to by the unique identifier and confirms that the current status corresponds to the aforementioned collaborative acceptance module. The specific process is as follows: When B operations company initiates an on-chain transaction to submit a completion report, the transaction must reference the unique identifier of the work order, WO-20250912-T001-001. The smart contract first uses this unique identifier to perform a location operation within its internal hash table storing all operations work order objects to retrieve the corresponding work order object. Upon successful retrieval, the smart contract reads the state variable value stored in the work order object as "PENDING". Next, the smart contract performs a logical comparison: it compares the currently read state value with a predefined set of valid states allowed to perform the "submit completion report" operation in the commercial contract terms. According to the protocol rules, only work orders with a state of "PENDING" are allowed to submit a completion report. Since the current work order's state "PENDING" matches the valid states defined in the protocol rules, the result of this logical comparison is "true". Based on the combined result of this location operation and the logical comparison, the smart contract ultimately determines that the validity of the operations work order and its current state verification have passed. The smart contract then allows the completion report submission transaction to continue execution, proceeding to the subsequent collaborative acceptance process. If the work order status is already "COMPLETED" or "CANCELED," verification will fail, and the submission transaction will be rejected to avoid duplicate submissions or invalid operations.

[0028] The above process automatically verifies the validity and current status of maintenance work orders through smart contracts, which can effectively prevent errors such as submitting completion reports repeatedly and processing canceled work orders. This greatly reduces the risk of process chaos and data inconsistency caused by manual intervention, ensures the smooth progress of each maintenance process, and enhances the credibility and execution of the entire system.

[0029] Furthermore, the collaborative acceptance process based on the acceptance standards and procedures in the aforementioned commercial contract terms, which triggers a change in the status of the maintenance work order and generates an acceptance certificate and a digital signature corresponding to the source of the completion report and the source of the acceptance certificate, corresponds to the aforementioned collaborative acceptance module. The specific process is as follows: Once the completion report submission by Company B passes the smart contract's validity verification, the system immediately enters the collaborative acceptance phase. The smart contract first executes the machine acceptance logic predefined in the commercial contract terms. This logic compares the maintenance data included in the completion report (i.e., a winding temperature of 85°C) with the pre-defined acceptance criteria in the commercial contract terms (winding temperature should be below 95°C). Since 85°C is lower than 95°C, the comparison result is "passed." This automated comparison process ensures the objectivity and efficiency of the acceptance. After machine acceptance passes, the smart contract waits for an on-chain confirmation transaction initiated by Company A's authorized account. Company A's maintenance supervisor, after reviewing the completion report and confirming the on-site situation, initiates this transaction through their authorized account. The smart contract receives and executes this on-chain confirmation transaction and updates the status variable of the maintenance work order pointed to by the unique identifier WO-20250912-T001-001 according to the confirmation transaction. This status changes from "PENDING" to "COMPLETED," thus completing the status change. Simultaneously, the smart contract instantiates an acceptance certificate containing the machine comparison results and the on-chain confirmation transaction timestamp; this record is immutable. During this process, the system captures two crucial cryptographic signatures: one, a signature generated by the private key of Company B's operations and maintenance account, contained within the completion report submission transaction data, proving the report's origin; and two, a signature generated by the private key of Company A's authorized account, contained within the confirmation transaction data of Company A's power grid, proving the acceptance's origin. These two digital signatures, as core components of the business credentials, ensure the authenticity and reliability of the completion report and acceptance certificate, providing strong evidence for subsequent accountability.

[0030] The above process utilizes machine-based acceptance logic, enabling the system to objectively and efficiently compare completed data with preset standards, eliminating biases from subjective judgment and significantly improving efficiency. Simultaneously, the combination of on-chain confirmation by authorized accounts and two-way digital signatures ensures the authenticity and traceability of the acceptance results.

[0031] Furthermore, the execution status update transaction, based on the business credential composed of the completion report, acceptance certificate, and corresponding digital signature, generates a digital certificate for the transformer digital identity pointed to by the maintenance work order and records it in the distributed operation ledger corresponding to the aforementioned shared ledger module. The specific process is as follows: After the collaborative acceptance process of work order WO-20250912-T001-001 is completed, the system immediately executes a status update transaction. This transaction first encapsulates the three core components representing the entire maintenance event—the completion report, the acceptance certificate, and the corresponding digital signature—into a complete business certificate. This business certificate is a logical collection containing all the key information and evidence of this maintenance activity. Next, based on this encapsulated business certificate, the system generates a verifiable digital certificate conforming to the Decentralized Identity Standard (DID) and the Verifiable Credential Standard (VC). To reflect the characteristics of multi-party consensus while adhering to the standard Verifiable Credential (VC) data model, this invention adopts a technical solution of 'single authoritative issuer, multi-party evidence embedding'. Specifically, for each verifiable digital certificate generated by the system, its unique 'issuer' field is set to the DID of the party with final adjudication authority in this maintenance event (Power Grid Company A). Correspondingly, the standard 'proof' field of the certificate also only contains the digital signature generated by this authoritative issuer for the entire certificate content. To include the signature of another participant (i.e., Operations Company B) as undeniable evidence, the digital signature generated by Operations Company B for its completion report, along with the hash value of the signed completion report data, is encapsulated into a structured 'evidence' data object. This 'evidence' object is then fully embedded within the 'credentialSubject' data segment of the core of the verifiable digital certificate, existing as a core statement. In this way, any third-party verifier receiving this certificate can first verify the validity of the authoritative issuer's (Power Grid Company A) signature through the standard VC verification process, thus confirming the integrity and authority of the entire certificate. Subsequently, the verifier can further parse the contents of the 'credential subject', extract the embedded 'evidence' object, and independently perform cryptographic verification of the Operations Company's signature and its corresponding data hash. More specifically, the generation of a verifiable digital certificate must include the following set of structured declarations in its core credential body data segment: a unique identifier pointing to the maintenance work order corresponding to this maintenance event; a cryptographic hash value of the complete data of the final submitted completion report, used for tamper-proof verification; a list of DIDs of all parties involved in the collaborative acceptance process; a timestamp of final acceptance; and the comparison results of performance indicators determined by the machine acceptance logic. By embedding this critical operational information as a structured declaration in the certificate, the standardization and parsingability of its content are ensured.This digital certificate is not a simple file, but a structured data object that precisely points to all the key information involved in this operation and maintenance activity, including: the cryptographic hash value of the business certificate itself, the identifier pointing to the smart contract address where the agreed logic is deployed, and the identifier pointing to the on-chain digital identity of transformer T-001 (DID: T-001). The single operation and maintenance event digital certificate is designed as a composable, standardized digital asset certificate. A unique basic digital asset certificate is generated when the transformer's digital identity initially joins the network. Each successful operation and maintenance activity generates a verifiable digital certificate, which is then combined with this basic digital asset certificate as an attribute badge. This basic digital asset certificate can interact with smart contracts of external financial systems. By designing the digital certificate as a composable digital asset certificate and making it dynamic, this process not only significantly improves the intuitiveness and convenience of asset management, but more importantly, it opens up the channel between operation and maintenance data and economic value. This allows good operation and maintenance management to be directly transformed into quantifiable economic incentives or financial credit, achieving a leapfrog improvement from "data management" to "data asset operation." Finally, to construct the aforementioned distributed operation ledger, the system employs a collaborative on-chain and off-chain storage scheme: the generated complete and verifiable digital certificate file is stored on a decentralized storage network, returning its unique Content Identifier (CID); subsequently, this CID, along with core metadata such as the certificate's hash value, issuer, and entity identity, is permanently stored as a new record in the blockchain's smart contract state. In this way, a trusted and tamper-proof operation and maintenance history is added to transformer T-001. Anyone can query the distributed ledger to verify whether T-001 completed a compliant operation and maintenance at a specific point in time, with all operational data in the operation and maintenance process guaranteed by the digital signatures of the relevant parties. The aforementioned operation of recording verifiable digital certificates in the distributed operation and maintenance ledger transforms intangible operation and maintenance activities into tangible digital assets, providing the transformer with a complete and tamper-proof lifecycle history.

[0032] The above process solves the problems of fragmentation, easy forgery, and difficulty in verification in traditional data processing methods by encapsulating completion reports, acceptance certificates, and digital signatures into verifiable digital certificates. The verifiable digital certificate is permanently recorded in the distributed operation ledger, ensuring that every operation and maintenance record is traceable throughout the entire life cycle of the transformer from production to scrapping, greatly improving the transparency and credibility of transformer operation and maintenance management.

[0033] In summary, the core advantage of this invention lies in providing a transformer operation and maintenance management system that features automated execution, decentralized trust, and transparent processes: the protocol parser resolves the operation and maintenance service protocol into smart contracts that are automatically enforced on the blockchain, ensuring automated execution; and the blockchain-based data storage method ensures decentralized trust and transparent processes. Example

[0034] This embodiment provides a specific application of a blockchain-based transformer operation and maintenance data management system. A typical application scenario is as follows: Power grid company A and its subsidiary, operation and maintenance company B, sign an operation and maintenance service agreement. The agreement stipulates that operation and maintenance company B must ensure that the oil temperature of transformer T-002 does not exceed 85°C during daily operation. If the oil temperature exceeds 85°C for 10 minutes, operation and maintenance company B must submit a completion report within 8 hours of the operation and maintenance work order being generated; otherwise, it will be subject to internal performance evaluation deductions and financial penalties. In this agreement, power grid company A has the final review right, while operation and maintenance company B has the right to execute work orders and submit reports. The agreement execution module provides a domain language for designing the operation and maintenance agreement. This domain language includes specific keywords describing the agreed logic in the operation and maintenance agreement: DEFINE_KPI, ON_CONDITION, ACTION, and PENALTY. The operations and maintenance (O&M) administrators of Power Grid Company A use the domain language to write the O&M service agreement into a structured script. A protocol parser receives this structured script and automatically translates the O&M service agreement into executable smart contract code on the blockchain. For example, the condition "if the transformer oil temperature exceeds 85°C for 600 seconds" is mapped to specific functions and state variables in the smart contract. The compiled smart contract code is deployed on Power Grid Company A's consortium blockchain, becoming an immutable commercial contract term. All subsequent O&M activities related to transformer T-002 are strictly bound by this contract. If Operations and Maintenance Company B fails to submit a completion report on time, the smart contract will automatically execute the penalty logic and generate traceable transaction records. The entire process requires no manual intervention or arbitration. This process significantly improves the transparency and efficiency of Power Grid Company A's internal management and effectively reduces the trust costs of inter-departmental collaboration.

[0035] The above process transforms the internal service agreement between Power Grid Company A and its subsidiary, Operation and Maintenance Company B, into an automatically executable smart contract, thereby automating and mandating performance evaluation and fund transfer. This significantly improves the transparency and efficiency of Power Grid Company A's internal management and completely eliminates potential subjective biases in traditional internal processes. Example

[0036] This embodiment provides a specific application of a blockchain-based transformer operation and maintenance data management system. A typical application scenario is as follows: Power grid company A and operation and maintenance company B conduct collaborative acceptance of a fault repair work order for transformer T-004. This work order, with its unique identifier WO-20251105-T004-002, was generated due to an abnormal transformer cooling fan and is currently in a "PENDING" state. Further, the validity of the operation and maintenance work order pointed to by the unique identifier and its current state are verified by a smart contract to correspond to the aforementioned collaborative acceptance module. Specifically, when operation and maintenance company B completes the repair and prepares to submit a completion report, its system initiates an on-chain transaction. This transaction must reference the unique identifier WO-20251105-T004-002 of the work order. The smart contract first locates the work order in its internally stored work order object hash table based on this identifier and successfully retrieves the corresponding work order data. Subsequently, the smart contract reads the state variable value stored in the work order object, which is "PENDING". The smart contract then performs a logical comparison, comparing the status value with a predefined set of valid statuses (i.e., "Pending" and "Processing") that allow the "Submit Completion Report" operation in the commercial contract terms. Since the current status "Pending" matches the set of valid statuses, the comparison result is true. The smart contract ultimately determines that the work order's validity has passed verification with the current status and allows the completion report submission transaction to continue, entering the subsequent collaborative acceptance process. If the work order status is already "Completed" or "Canceled," the verification will fail, and the submission transaction will be rejected, effectively preventing duplicate submissions or invalid operations, ensuring the rigor of multi-party collaboration and the reliability of the process.

[0037] The above process automatically verifies the validity and current status of maintenance work orders through smart contracts, effectively preventing the repeated submission of completion reports and the erroneous operation of processing cancelled work orders. This significantly reduces the risk of process chaos and data inconsistency caused by human intervention. This mechanism ensures that every operation occurs at the correct maintenance process node, guaranteeing the orderliness and credibility of multi-party collaboration, and bringing unprecedented efficiency and execution to the entire maintenance ecosystem. Example

[0038] See Figure 3This is a schematic diagram of the blockchain structure. This embodiment details how to structure and solidify operation and maintenance data in the blockchain based on the terms of the commercial contract and the collaborative acceptance process. A typical application scenario is: Power Grid Company A and Operation and Maintenance Company B conduct collaborative acceptance of fault work order WO-20251210-T005-001 for transformer T-005. Further, the collaborative acceptance based on the acceptance standards and processes in the commercial contract triggers a change in the operation and maintenance work order status and generates an acceptance certificate and a digital signature of the corresponding completion report source and acceptance certificate source. This process emphasizes the blockchain as an immutable data structure. Specifically, when Operation and Maintenance Company B submits its completion report (which includes data showing the transformer winding temperature has dropped to 88°C), the smart contract executes a preset machine acceptance logic. By comparing 88°C with the acceptance standard of 95°C, the result is determined to be "passed". Subsequently, the smart contract waits for an on-chain confirmation transaction initiated by the authorized account of Power Grid Company A. The confirmation transaction includes its digital signature to confirm the acceptance behavior. Once the confirmation transaction is executed, the smart contract will trigger a change in the status variable of work order WO-20251210-T005-001 from "Pending" to "Completed". Simultaneously, the smart contract will instantiate a structured data object as an acceptance credential. This object precisely contains the machine acceptance result, a timestamp for manual confirmation, and two key cryptographic signatures: a completion report signature provided by maintenance company B, proving the data source; and an acceptance confirmation signature provided by power grid company A, proving its acceptance action. Finally, the complete data object containing all this information and signatures is encapsulated into a new on-chain transaction, permanently recorded in a new block of the blockchain data structure, and linked to the previous record of work order WO-20251210-T005-001 via a hash pointer, ensuring that the entire process of this maintenance event from submission to acceptance is authentic, traceable, and non-repudiable.

[0039] The above process, through the machine acceptance logic built into the smart contract, enables the system to objectively and efficiently compare completed data with preset standards, eliminating the bias of subjective judgment. Simultaneously, the combination of multi-party digital signatures ensures the authenticity and non-repudiation of the acceptance results. Most importantly, by encapsulating the completion report, acceptance certificate, and key signature into a structured on-chain data object and permanently embedding it in the blockchain incrementally, the system provides transformer assets with a complete, traceable, and verifiable digital lifecycle record, fundamentally solving the problems of traditional data fragmentation, susceptibility to forgery, and difficulty in accountability.

[0040] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A blockchain-based transformer operation and maintenance data management system, characterized in that, Comprise: A protocol execution module: parse the service level agreement into automatically executable business contract terms through a protocol parser, and deploy it in the form of a smart contract on the blockchain; monitor the real-time running data of the transformer associated with the digital identity through the oracle mechanism, and based on the business contract terms and the real-time running data, the smart contract automatically generates a maintenance work order containing a unique identifier and an initial state; A collaborative acceptance module: receives a completion report submission transaction initiated by a third-party maintenance that references a unique identifier; verifies the validity and current state of the maintenance work order pointed to by the unique identifier by the smart contract; performs collaborative acceptance based on the acceptance criteria in the business contract terms, triggers the state change of the maintenance work order and generates an acceptance voucher and a digital signature corresponding to the source of the completion report and the source of the acceptance voucher; A shared account module: performs a state update transaction, which generates a verifiable digital certificate for the transformer digital identity pointed to by the maintenance work order based on the business voucher composed of the completion report, the acceptance voucher and the corresponding digital signature, and records it in the distributed operation account book.

2. The transformer operation and maintenance data management system based on the blockchain according to claim 1, characterized in that, The specific process of parsing the service level agreement into automatically executable business contract terms through the protocol parser and deploying it in the form of a smart contract on the blockchain includes: the protocol execution module also provides a domain language for structurally describing the service level agreement, which contains standardized syntax keywords for defining performance indicators, agreement reward and punishment terms and multi-party operation permissions, as well as expression structures for describing conditional logic and numerical thresholds; the protocol parser is configured to receive a service level agreement written in the domain language and automatically compile the service level agreement to generate the business contract terms. 3.The transformer operation and maintenance data management system based on blockchain of claim 1, wherein, The specific process of monitoring the real-time running data of the transformer associated with the digital identity through the oracle mechanism includes: a network of oracle nodes deployed off-chain obtains the real-time running data from the transformer data source through an application programming interface; the oracle node network generates a data report containing the real-time running data and the transformer digital identity corresponding to the real-time running data; the oracle node network submits the data report as an input parameter to the blockchain in the form of a chain transaction by calling the data reporting function of the smart contract.

4. The transformer operation and maintenance data management system based on the blockchain according to claim 1, characterized in that, The specific process of automatically generating a maintenance work order containing a unique identifier and an initial state by the smart contract based on the business contract terms and the real-time running data includes: executing the agreed condition judgment logic defined in the business contract terms, and determining whether the preset trigger condition is met based on the real-time running data; when the agreed event trigger condition is met, the smart contract instantiates a maintenance work order data structure, and assigns an initial maintenance process state value to the state variable of the data structure; the smart contract generates a globally unique identifier for the maintenance work order data structure that tracks the life cycle of the maintenance process, and records the data structure and the identifier on the blockchain.

5. The transformer operation and maintenance data management system based on the blockchain according to claim 1, characterized in that, The specific process of verifying the validity and current state of the operation and maintenance work order pointed to by the unique identifier by the smart contract includes: based on the unique identifier, performing a positioning operation in the data structure for storing all operation and maintenance work order objects to retrieve the corresponding operation and maintenance work order object; reading the state variable value of the retrieved operation and maintenance work order, which represents the current state of the operation and maintenance work order; the smart contract logically compares the current state with a set of valid states predefined in the commercial contract clauses that allow subsequent operations to be performed; based on the results of the positioning operation and logical comparison, the operation and maintenance work order validity and current state verification.

6. The transformer operation and maintenance data management system based on the blockchain according to claim 1, characterized in that, The specific process of performing acceptance based on the acceptance criteria and process in the commercial contract clause, triggering the operation and maintenance work order state change and generating the acceptance voucher and the corresponding digital signature of the source of the completion report and the source of the acceptance voucher includes: executing the machine acceptance logic defined in the commercial contract clause, which compares the operation and maintenance data contained in the completion report submission transaction with the preset acceptance criteria in the commercial contract clause to obtain a comparison result; the smart contract receives an on-chain confirmation transaction initiated by an authorized account of the power grid company preset in the commercial contract clause; the on-chain confirmation transaction is executed, and the state variable of the operation and maintenance work order pointed to by the unique identifier is updated to complete the state change and instantiate an acceptance voucher containing the comparison result and the timestamp of the on-chain confirmation transaction; respectively capturing the cryptographic signatures generated by the private keys of the initiator accounts corresponding to the initiator of the completion report submission transaction and the initiator of the on-chain confirmation transaction to obtain the digital signature.

7. The transformer operation and maintenance data management system based on the blockchain according to claim 1, characterized in that, The specific process of executing the state update transaction, which generates a verifiable digital certificate for the transformer digital identity pointed to by the operation and maintenance work order based on the business voucher composed of the completion report, the acceptance voucher and the corresponding digital signature, and records it in the distributed operation ledger, includes: encapsulating the completion report, the acceptance voucher and the digital signature into a business voucher; and based on the business voucher, generating a verifiable digital certificate that complies with the decentralized identity standard and the verifiable credential standard; the verifiable digital certificate is a structured data object containing a cryptographic hash value of the business voucher, an identifier pointing to the smart contract address and an identifier pointing to the transformer digital identity; the distributed operation ledger is composed of a blockchain and an off-chain distributed storage.

Images