Linked Activity Chain Ledger for Organizational Transparency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business entities within the same organization often lack up-to-date information about their customers, leading to suboptimal decision-making regarding credit issuance, account security, and loan quality.

Innovation Solution

Implementing a system and method using a linked activity chain in a ledger to enhance organizational transparency, where customer interactions and activities are recorded as blocks in a blockchain, enabling real-time calculation of a summary score for customers based on their credit chain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If customer information is updated in real-time across all entities, then decision-making quality improves, but system complexity and implementation cost increase

Engineering Contradiction:
Improvecustomer information currencyVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments customer information into discrete blocks organized in a linked activity chain, where each block represents a specific customer interaction or data point. This segmentation allows entities to access only relevant portions of customer information without requiring access to the entire information ecosystem, reducing system complexity while maintaining information currency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary ledger system that mediates between multiple entities and customer information. The ledger acts as a neutral intermediary that stores, validates, and distributes customer information blocks to authorized entities, eliminating the need for direct peer-to-peer information sharing infrastructure and reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If a comprehensive linked activity chain is implemented across all entities, then organizational transparency improves, but data security and privacy management become more difficult

Engineering Contradiction:
Improveorganizational transparencyVSAvoiddata security management
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements local quality by providing different levels of information access to different entities based on their authorization and relationship to the customer. Each entity receives only the specific customer information blocks relevant to its function, maintaining transparency where needed while protecting sensitive data through selective disclosure and localized data placement.

Inventive Principle:
Principle #3Local quality

3Reliability

If real-time customer information is made available to all entities, then fraud detection capability improves, but processing time and computational resources increase

Engineering Contradiction:
Improvefraud detection capabilityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-validating and structuring customer information blocks as they are added to the linked activity chain. Data is organized and tagged with metadata during initial entry, enabling entities to quickly search and retrieve relevant information without performing complex real-time analysis, thus reducing processing time while maintaining fraud detection capability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12243109B2Systems and methods for enhanced organizational transparency using a credit chain
Publication Date: 2025.03.04 JPMORGAN CHASE BANK NA
  • US12243109B2 patent drawing
  • US12243109B2 patent drawing
  • US12243109B2 patent drawing

AI summary

Systems and methods for enhanced organizational transparency using a linked activity chain in a ledger are disclosed. In one embodiment, a method may include (1) a back end for an organization comprising at least one computer processor receiving a first communication from a first entity comprising a first customer interaction with the first entity; (2) the back end writing the first communication to a ledger for the organization as a first block in a linked activity chain; (3) the back end receiving a second communication from a second entity comprising a second customer second activity with the second entity; (4) the back end writing the second communication to the ledger for the organization as a second block in the linked activity chain; (5) the back end calculating a summary score for the customer based on the blocks in the linked activity chain.