Goal-Based Compliance Management for Modular System Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current configuration management systems lack a mechanism to provide a view of only relevant, current information, leading to inconsistent states and monolithic management tool designs, which are harder to maintain and less flexible.

Innovation Solution

A goal-based compliance management system that uses a goal state repository to store objectives for a managed system, creating a subset of applicable goals based on the current state and modifying the system to comply with these goals, allowing for modular and flexible management tool operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a complete management function is implemented in one piece of code, then the management system can perform full management operations, but the system becomes harder to maintain and less flexible

Engineering Contradiction:
Improvecomplete management functionVSAvoidmonolithic code structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the monolithic management code into separate management tools, each responsible for specific management functions. These tools communicate through a common data model and repository structure, allowing independent development, maintenance, and deployment of individual management components while maintaining overall system functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal data model and repository structure that can be shared across multiple management tools. This common infrastructure provides multi-functionality, allowing different management tools to operate on the same data structures and communicate through standardized interfaces, reducing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If all system information is stored in the CMDB, then complete system state is available, but management tools cannot effectively use it as a communication mechanism due to partial updates being considered authoritative

Engineering Contradiction:
Improvecomplete system stateVSAvoidcoordination mechanism
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent establishes a preliminary framework of standardized data models, schemas, and repository structures before management tools operate. This pre-defined structure ensures that all management tools communicate using the same data formats and update mechanisms, preventing coordination conflicts and ensuring that partial updates are properly contextualized within the complete system state.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If management tools perform partial updates on the CMDB, then specific management tasks can be completed, but the CMDB may be left in an inconsistent state if tools fail to complete their purpose

Engineering Contradiction:
Improvemanagement task completionVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where management tools report their operations and state changes back to the centralized repository. The standardized data models include validation rules and consistency checks that provide immediate feedback on update operations, ensuring that partial updates maintain data consistency and that failures can be detected and recovered from.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8825610B1System management based on goals relevant to a current state of a managed system
Publication Date: 2014.09.02 HEWLETT PACKARD ENTERPRISE DEV LP
  • US8825610B1 patent drawing
  • US8825610B1 patent drawing
  • US8825610B1 patent drawing

AI summary

A system includes a goal state repository, a goal state repository instance and management tools. The goal state repository stores goals for a managed system. The goal state repository instance stores a subset of the goals applicable to a current state of the managed system. The goal state repository instance is created by comparing the current state of the managed system to the goals stored in the goal state repository. The management tools modify the managed system to be in compliance with the subset of goals stored in the goal state repository instance.