Automated Connectivity Configuration for Hardware Software Assets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Establishing connectivity between arbitrary hardware and software components, particularly in multi-user simulation events, is complex due to the lack of prior design for interconnectivity and varying interface standards, often resulting in suboptimal ad-hoc solutions that require repeated manual configuration for each event.
Innovation Solution
A method and system that utilize a repository of asset metadata to identify bridging assets, generate a deployment plan considering cost and performance criteria, and store snapshots for efficient reuse, enabling automated configuration and monitoring of connectivity between components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual ad-hoc configuration is used to establish connectivity between hardware and software components, then connectivity can be achieved, but the process is complex and requires repeated manual effort for each event
Solution Approach 1:
The system performs preliminary actions by automatically discovering available hardware and software assets, analyzing their metadata, and pre-configuring connectivity settings before the simulation event begins. This eliminates the need for manual ad-hoc configuration during event setup, as the connectivity framework is already in place and ready for deployment.
Solution Approach 2:
The system enables self-service by automatically generating deployment plans without human intervention. The asset metadata repository stores configuration information, and the system autonomously retrieves this data, analyzes compatibility, and configures connectivity between components, freeing operators from repetitive manual configuration tasks.
2Productivity
If automated configuration using asset metadata repository is implemented, then configuration time is reduced, but system complexity increases due to repository management
Solution Approach 1:
The asset metadata repository serves multiple functions: it stores hardware asset information, software asset details, compatibility rules, and deployment configurations. This single universal repository handles diverse data types and supports various operations (discovery, analysis, configuration generation), reducing the need for separate specialized systems and minimizing overall architectural complexity.
Solution Approach 2:
The asset metadata repository acts as an intermediary layer between the physical hardware/software assets and the automated configuration system. Instead of directly managing complex asset interactions, the system queries the repository for pre-stored metadata and compatibility information, simplifying the configuration process while maintaining comprehensive control over asset connectivity.
3Reliability
If optimal connectivity plans are generated for each event, then performance is maximized, but computational resources are consumed repeatedly
Solution Approach 1:
The system performs preliminary analysis of asset metadata and generates optimal connectivity configurations in advance, before simulation events begin. By pre-processing compatibility information and deployment plans during idle periods, the system avoids repeated computational intensive operations during active events, reducing real-time resource consumption while maintaining optimal performance.
Solution Approach 2:
Once optimal connectivity plans are generated for a particular configuration of hardware and software assets, the system creates and stores copies of these deployment plans in the asset metadata repository. When the same or similar asset configurations are needed for future events, the system retrieves and reuses these copied plans instead of regenerating them, significantly reducing computational resource usage while maintaining optimal connectivity performance.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer implemented method of providing connectivity between two or more primary assets, each primary asset comprising a hardware component or a software component, the method comprising receiving a request to provide connectivity between the primary assets; accessing a repository that stores a list of assets and metadata associated with each asset; using the metadata in the repository to generate an hierarchical list of assets; rationalising the hierarchical list of assets by selecting a group of assets from the hierarchical list of assets to be used in providing connectivity between the primary assets; and generating, based on operating parameters of each asset in the group of assets, a deployment plan for the group of assets, wherein the deployment plan defines settings and/or connections to be used between the assets in the group of assets in order to provide connectivity between the two or more primary assets.