IT Service Management with Dual-State Model Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current IT systems lack advanced modeling capabilities to manage IT services effectively, with Configuration Management Databases (CMDBs) typically storing either the current state or desired state of IT services, but not both simultaneously, leading to inefficiencies in change management and inconsistency detection.

Innovation Solution

Implementing a two-state model instance representation, where both desired and observed states are maintained, allowing for continuous monitoring and comparison to detect inconsistencies, with a closed-loop system that includes a Configuration Management System, Watchdog Service, and Repair Service to rectify discrepancies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single-state model instance representation is used in the CMDB, then the system complexity is reduced, but the ability to detect and manage inconsistencies between desired and observed states is lost

Engineering Contradiction:
Improvesystem complexityVSAvoidinconsistency detection capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the model instance representation into two distinct states: desired state and observed state. This segmentation allows the system to independently track what the IT service should be versus what it actually is, enabling inconsistency detection while maintaining manageable complexity through structured separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal/dimensional dimension to the model instance by maintaining both desired and observed states simultaneously. This dimensional expansion transforms a static single-state representation into a dynamic multi-state representation, enabling the system to detect drift and inconsistencies without fundamentally increasing operational complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If manual changes are used for IT service configuration, then implementation flexibility is maintained, but repeatability, execution speed, and cost efficiency deteriorate

Engineering Contradiction:
Improveimplementation flexibilityVSAvoidexecution speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements continuous monitoring that compares the observed state against the desired state, providing real-time feedback on configuration drift. This feedback mechanism enables automated detection and correction of inconsistencies, replacing manual change processes with systematic, repeatable operations that maintain flexibility while dramatically improving execution speed and efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service through automated monitoring and correction mechanisms that continuously compare desired and observed states. The Configuration Management System automatically detects inconsistencies and triggers corrective actions without manual intervention, allowing the system to self-correct configuration drift while maintaining the flexibility to adapt to changing requirements.

Inventive Principle:
Principle #25Self-service

3Device complexity

If the CMDB stores only the current state or only the desired state, then storage simplicity is maintained, but the ability to perform continuous monitoring and comparison deteriorates

Engineering Contradiction:
Improvedata storage structureVSAvoidstate comparison accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent segments the data storage structure into distinct desired state and observed state components within the model instance. This segmentation allows both states to be stored and maintained independently, enabling precise comparison while keeping the overall data structure organized and manageable through clear separation of intended versus actual configurations.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9240931B2Information technology service management
Publication Date: 2016.01.19 VALTRUS INNOVATIONS LTD
  • US9240931B2 patent drawing
  • US9240931B2 patent drawing
  • US9240931B2 patent drawing

AI summary

A desired instance of a service model is stored, and an observed instance of the service model is provided. Inconsistencies between the desired instance and the observed instance may be detected based on a comparison between the desired instance and the observed instance.