Smart Contract Impact Assessment for Cloud Component Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of integrating new components in cloud computing environments introduces risks of resource vulnerabilities and incompatibilities, leading to potential operational issues, revenue loss, and degraded customer experience due to the lack of early impact assessment on service teams.

Innovation Solution

Implementing smart contracts to identify and assess the impact of new components on service teams early in the design process, allowing for proactive planning and decision-making by validating component changes against service teams and identifying workflow dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new components are integrated into cloud computing environments, then functionality and capacity are improved, but resource vulnerabilities and incompatibilities increase

Engineering Contradiction:
ImprovefunctionalityVSAvoidresource vulnerabilities
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements impact assessment processes that evaluate new components before they are integrated into the cloud environment. This preliminary action identifies potential vulnerabilities and incompatibilities in advance, allowing teams to address issues before deployment, thus maintaining reliability while enabling functional improvements

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If new components are integrated into cloud computing environments, then functionality and capacity are improved, but incompatibilities increase

Engineering Contradiction:
ImprovefunctionalityVSAvoidincompatibilities
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces service teams as intermediaries between new components and the existing cloud environment. These teams conduct impact assessments that mediate the integration process, identifying and resolving incompatibilities before full integration occurs, thus enabling functionality while managing complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If impact assessment is conducted early in the design process, then operational risks are reduced, but time and resources for validation increase

Engineering Contradiction:
Improveoperational risksVSAvoidtime for validation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent conducts impact assessments early in the design process, performing validation activities before full implementation. This preliminary action identifies and addresses potential issues while the system is still being designed, reducing operational risks without significantly increasing overall project time since issues are caught before they require costly fixes later

Inventive Principle:
Principle #10Preliminary action

4Reliability

If comprehensive impact assessment is performed on all service teams, then operational reliability is improved, but process complexity increases

Engineering Contradiction:
Improveoperational reliabilityVSAvoidprocess complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the impact assessment process into separate assessments for different service teams (e.g., hardware service teams, software service teams). Each team assesses only the components relevant to their domain, segmenting the overall complexity while maintaining comprehensive coverage for operational reliability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250378491A1Smart Contracts for Collaborative Impact Assessment
Publication Date: 2025.12.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250378491A1 patent drawing
  • US20250378491A1 patent drawing
  • US20250378491A1 patent drawing

AI summary

A method, computing system, and computer program product for generating a plurality of smart contracts, each of the plurality of smart contracts associated with a respective service team, and each of the plurality of smart contracts identifying components impacting each respective service team. One or more component changes associated with a proposed design are received. The one or more component changes are validated against components impacting each respective service team to identify impacts associated with the proposed design by at least a portion of the plurality of smart contracts.