Self-Aware Component Model API Wrapper for Analytics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems for analyzing and predicting the operation of real-world physical systems, such as electro-mechanical systems, face inefficiencies and errors when models are transferred and executed on different computers, requiring time-consuming re-writing and debugging, and struggle with managing complex systems with numerous dependencies and versions.
Innovation Solution
The development of a self-aware component model system that includes an API wrapper providing information about inputs and outputs, allowing for rapid development and deployment of analytic models through digital twin modeling, which creates a virtual representation of physical systems using sensors, communication, history, and computation, enabling seamless execution across environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a model is built on a local computer and transmitted to another computer for execution, then the model can be run on different systems, but it requires time-consuming re-writing and debugging
Solution Approach 1:
The patent applies preliminary action by pre-defining API wrappers that encapsulate environment-specific configurations, dependencies, and execution parameters. These wrappers are created in advance during model development, so when the model is transmitted to another computer, the pre-configured API wrapper automatically adapts the model to the new environment without requiring re-writing or debugging. The API wrapper acts as a prepared intermediary that handles environment-specific adjustments beforehand.
Solution Approach 2:
The patent introduces an API wrapper as an intermediary layer between the model code and the execution environment. This intermediary encapsulates all environment-specific interactions, dependencies, and configurations, allowing the model itself to remain unchanged while the API wrapper adapts to different computers and systems. The intermediary handles the complexity of environment adaptation, isolating the model from environmental variations.
2Reliability
If conventional systems are used to manage complex systems with numerous dependencies and versions, then system functionality can be maintained, but error-prone processes and inefficiencies occur
Solution Approach 1:
The patent applies segmentation by dividing the system into distinct modular components: the model itself, the API wrapper, dependency specifications, and configuration parameters. Each component is independently defined and managed. The API wrapper encapsulates specific dependencies and version requirements, allowing individual components to be updated, replaced, or debugged without affecting the entire system. This modular segmentation reduces errors and improves management efficiency.
Solution Approach 2:
The patent creates a universal API wrapper framework that can handle multiple types of dependencies, configurations, and execution environments through a standardized interface. The same API wrapper structure serves multiple functions: managing dependencies, defining input-output interfaces, specifying execution parameters, and adapting to different environments. This universal approach eliminates the need for separate management mechanisms for each type of system configuration.
3Adaptability or versatility
If models are re-written and de-bugged each time they are run on another system, then the model can adapt to different environments, but the process becomes very time consuming and error-prone
Solution Approach 1:
The patent applies copying by creating a reusable API wrapper template that can be copied and applied to multiple models and environments. Instead of re-writing adaptation code for each model deployment, the standardized API wrapper is copied and configured with specific parameters for the target environment. This copying approach ensures consistency across different deployments and eliminates the need for error-prone manual re-writing and debugging processes.
Data Source
AI summary
According to some embodiments, system, apparatus and methods are provided comprising one or more component models of an analytic model for an installed product; an application programming interface (API) wrapper associated with each of the one or more component models, the API wrapper including information about one or more inputs to the component model; and wherein the component model and the API wrapper form a self-aware component. Numerous other aspects are provided.