Cloud Service Maturity Evaluation System for Deployment Readiness

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud infrastructure client instances lack effective methods to evaluate the maturity or readiness of services, which is crucial for ensuring operational reliability and efficiency, especially in multi-instance cloud architectures where service outages can affect multiple customers.

Innovation Solution

A system and method for evaluating service maturity based on predetermined criteria that assess software and hardware component statuses and error statuses, allowing customization by users, with a maturity evaluation system that determines and outputs maturity levels for services stored and executed on cloud infrastructure client instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud services are deployed without maturity evaluation, then service deployment speed is improved, but service reliability deteriorates

Engineering Contradiction:
Improveservice deployment speedVSAvoidservice reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary maturity evaluation before service deployment by assessing service parameters (software component status, hardware component status, error status) against maturity criteria. This preliminary assessment ensures services meet reliability thresholds before being deployed to production environments, preventing unreliable services from affecting customers while maintaining efficient deployment processes.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive service parameter monitoring is implemented, then service reliability is improved, but system complexity increases

Engineering Contradiction:
Improveservice readiness assessmentVSAvoidevaluation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the maturity evaluation into distinct, manageable components: service parameter determination (software component status, hardware component status, error status), maturity criteria definition, and maturity level calculation. Each component operates independently and can be configured separately, reducing overall system complexity while enabling comprehensive service assessment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent allows dynamic configuration of maturity criteria and service parameters through customizable thresholds and weights. Users can adjust maturity thresholds, add or remove service parameters, and modify evaluation criteria without changing the underlying system architecture, enabling flexible reliability assessment while maintaining system simplicity.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If customized maturity criteria are allowed, then adaptability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvematurity criteria customizationVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent enables users to independently configure and customize maturity criteria through a self-service interface. Users can define their own service parameters, set maturity thresholds, and adjust evaluation criteria without requiring system administrator intervention or complex configuration procedures. This self-service capability enhances adaptability while maintaining ease of operation through intuitive configuration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11507442B2Method and system for determining maturity level of a cloud computing service
Publication Date: 2022.11.22 SERVICENOW INC
  • US11507442B2 patent drawing
  • US11507442B2 patent drawing
  • US11507442B2 patent drawing

AI summary

Systems and methods are disclosed that evaluate maturity or readiness of services of a cloud infrastructure client instance. Service maturity may be defined based on certain predetermined maturity criteria, which may evaluate certain corresponding service parameters of the service, such as a software component status of a service, a hardware component status of the service, and/or an error status of the service. In some embodiments, the definition of service maturity may be customized by a user. For example, the user may adjust, add, or remove the maturity criteria. The systems and methods may determine the service parameters of the service, and determine the maturity of the service by applying the maturity criteria to the determined service parameters. The service maturity may then be output (e.g., displayed or sent) to the user.