Distributed Ledger Network for Standard Operating Procedure Governance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current process for managing standard operating procedures (SOPs) in computer systems is disorganized and lacks transparency, leading to governance and integrity issues, and trust problems between vendors and customers during system failures, as it relies on ad-hoc communication methods like emails, tickets, and phone calls.
Innovation Solution
Implementing a distributed ledger network to record and manage SOPs, which uses a blockchain to securely and transparently capture remedial actions, prerequisites, and execution results, eliminating the need for central authentication and ensuring all stakeholders' approval through cryptographic signatures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If ad-hoc communication methods (emails, tickets, phone calls) are used to manage SOPs, then ease of operation is improved, but governance and transparency deteriorate
Solution Approach 1:
A distributed ledger network acts as an intermediary between stakeholders and SOP execution processes. The ledger immutably records all SOP-related transactions, approvals, and communications, providing transparent audit trails while maintaining ease of operation through automated smart contract execution.
Solution Approach 2:
The patent replaces manual, ad-hoc communication mechanisms (emails, phone calls, ticketing systems) with a cryptographic-based distributed ledger system. This substitution ensures that all SOP executions are automatically recorded, timestamped, and verifiable, enhancing governance and transparency without significantly increasing operational complexity.
2Ease of operation
If centralized authentication is used to manage SOP approvals, then ease of operation is improved, but reliability and trust deteriorate
Solution Approach 1:
The patent segments the centralized authentication authority into multiple distributed nodes across the ledger network. Each stakeholder (vendor, customer, approvers) has their own cryptographic keys and identity management, eliminating the need for a single point of trust while maintaining streamlined approval workflows through smart contracts.
Solution Approach 2:
The distributed ledger serves as a neutral intermediary that all parties trust equally, replacing centralized authentication. The immutable record of approvals and cryptographic signatures provide verifiable trust without requiring any single party to control the authentication process.
3Reliability
If distributed ledger network is implemented to record SOP transactions, then governance and transparency are improved, but device complexity increases
Solution Approach 1:
The distributed ledger system is designed to be self-sufficient, automatically recording SOP executions, approvals, and communications without requiring complex external infrastructure. Smart contracts autonomously enforce SOP rules and record outcomes, reducing the need for additional administrative systems or manual intervention.
Solution Approach 2:
The patent designs the distributed ledger to serve multiple functions simultaneously: it acts as an authentication system, an audit trail repository, a communication platform, and an execution monitoring system. This multi-functionality reduces overall system complexity by consolidating what would otherwise require separate systems into a single unified platform.
Data Source
AI summary
Systems and methods of the disclosure include: receiving, by a node of a distributed ledger network, first transaction data, wherein the first transaction data comprises an alert derived from a state of a computer system; storing the first transaction data in a first block of the distributed ledger network; receiving, by the node, second transaction data, wherein the second transaction data comprises an identifier of a remedial action performed on the computer system in response to the alert and a result of performing the remedial action; and storing the second transaction data in a block of the distributed ledger network, wherein the block is provided by one of: the first block or a second block.