Semantic Interrelational Data Model for IT Infrastructure Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IT infrastructure management solutions face challenges due to vendor-specific implementations of APIs, scripting interfaces, and data schemas, leading to manual integration and human intervention, which are inefficient and costly, especially when vendors change or introduce new functionality.
Innovation Solution
A method that uses a common semantic interrelational data model to translate parameters from upper-layer IT interfaces into constructs suitable for heterogeneous IT domains, enabling automated communication and orchestration across multiple vendor-specific solutions, reducing dependence on proprietary tools and minimizing disruption from vendor changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If vendor-specific implementations of APIs and data schemas are used for IT infrastructure management, then each vendor's functionality can be fully utilized, but manual integration and human intervention are required leading to inefficiency and high costs
Solution Approach 1:
The patent introduces an intermediary layer (integration platform or adapter) that sits between the upper-layer IT service management interfaces and the vendor-specific domain management solutions. This intermediary translates and adapts requests and responses, enabling automated communication without direct manual integration between disparate vendor systems and upper-layer interfaces.
2Adaptability or versatility
If vendor-specific implementations are used, then specific vendor features can be accessed, but substantial human interaction is required for processing IT service requests
Solution Approach 1:
The intermediary layer automatically translates upper-layer service requests into vendor-specific commands and translates vendor responses back into standardized formats. This automation eliminates the need for substantial human interaction while maintaining access to vendor-specific features and functionality.
3Adaptability or versatility
If manual integration is used for heterogeneous IT domains, then flexibility in selecting vendor tools is maintained, but the complexity of integration and maintenance increases
Solution Approach 1:
The intermediary layer abstracts the complexity of heterogeneous vendor integrations by providing a unified interface to upper-layer systems. It handles the complexity of translating between different vendor-specific protocols, data schemas, and interfaces, while maintaining flexibility to support multiple vendor tools through standardized adaptation mechanisms.
4Measurement precision
If vendor-specific data schemas and APIs are used, then accurate vendor data can be accessed, but interoperability between different vendor solutions is hindered
Solution Approach 1:
The intermediary layer maintains accurate vendor-specific data by translating between different vendor data schemas and a standardized internal representation. It preserves the precision and accuracy of vendor-specific data while enabling interoperability between different vendor solutions through standardized translation and adaptation mechanisms.
Data Source
AI summary
In certain embodiments, a method includes accessing one or more parameters based on an IT service request received from an upper-layer IT interface, the parameters formatted according to an upper-layer IT interface construct. Appropriate IT domains are determined, according to at least a portion of the parameters, from a number of IT domains for implementing IT infrastructure for fulfilling the request, the domains each associated with one or more vendor-specific solutions for providing IT infrastructure of a type associated with the domain. Using a common semantic interrelational data model that includes mappings of constructs for upper-layer IT interfaces to constructs for IT domains, at least a portion of the parameters are translated from the upper-layer IT interface construct into constructs suitable for use by the determined appropriate domains. One or more parameterized instructions operable to cause appropriate vendor-specific implementations of the determined appropriate domains to implement appropriate infrastructure for fulfilling the request are communicated.