Integration Templates for Third-Party Device Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for integrating third-party devices into systems require cumbersome manual processes, involving significant delays, specialized knowledge, and high costs, and are prone to errors, making them inefficient and error-prone.

Innovation Solution

A computer-implemented method using a templating system to generate and manage integration templates, allowing for quick and accurate instantiation of integration instances with reduced errors and costs, by receiving template information, generating integration templates, and enabling client systems to access and manage these templates for data transformations between source and target schema data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual integration processes are used to connect third-party devices, then integration can be achieved, but the process is cumbersome, time-consuming, and error-prone

Engineering Contradiction:
Improveintegration accuracyVSAvoidintegration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining integration templates that include all necessary connection configurations, data mapping rules, and transformation logic before actual integration is needed. When a third-party device needs to be integrated, the system retrieves the pre-configured template and automatically instantiates it, eliminating the need for manual configuration and significantly reducing integration time while ensuring accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of proven integration templates for new third-party device connections. Instead of manually creating integration configurations from scratch, the system copies existing validated templates and adapts them to the specific device being integrated. This copying approach ensures that integration accuracy is maintained while dramatically reducing the time required for each new integration.

Inventive Principle:
Principle #26Copying

2Reliability

If manual integration processes are used, then integration can be achieved, but specialized knowledge and high costs are required

Engineering Contradiction:
Improveintegration accuracyVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The system enables self-service integration by providing automated template instantiation that requires minimal user input. Users simply select the third-party device type, and the system automatically retrieves the corresponding pre-configured template, applies the necessary settings, and establishes the integration without requiring specialized technical knowledge. This self-service approach maintains integration accuracy while significantly reducing complexity and cost.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system introduces integration templates as intermediary components that mediate between third-party devices and the main system. These templates act as pre-packaged solution units that encapsulate all necessary connection logic, data transformation rules, and configuration parameters. By using these intermediary templates, the system eliminates the need for manual integration configuration while maintaining high accuracy and reducing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If custom integration solutions are created for each third-party device, then specific functionality can be achieved, but maintenance costs and complexity increase

Engineering Contradiction:
Improvedevice compatibilityVSAvoidintegration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system achieves universality by creating a single integrated platform that supports multiple third-party device types through a common template-based architecture. The same template management system, update mechanism, and monitoring framework handle all device integrations uniformly. This universal approach enables the system to accommodate diverse devices while reducing management complexity through standardization and consolidation.

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

Solution Approach 2:

The system performs preliminary action by pre-configuring all integration parameters, data mapping rules, and transformation logic within templates before devices are connected. This preliminary configuration eliminates the need for post-deployment customization and maintenance of custom integration code. When devices are integrated, they simply instantiate the pre-built templates, reducing ongoing management complexity while maintaining adaptability to different device types.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12135730B2Apparatuses, computer program products, and computer-implemented methods for integrating third-party devices
Publication Date: 2024.11.05 HONEYWELL INTERNATIONAL INC
  • US12135730B2 patent drawing
  • US12135730B2 patent drawing
  • US12135730B2 patent drawing

AI summary

Embodiments of the disclosure provide for improved integration of third-party devices in a system. Specifically, embodiments provide for improved integration management, including creation, deployment, maintenance, and monitoring of integrations utilizing integration templates. Embodiments include operation using a specially configured templating system that enables creation of integration template(s), management of integration template(s), searching of integration template(s), and initiation of such integration template(s) into integration instance(s) for particular client system(s), as well as updating of integration instance(s) based on integration template(s). Some embodiments provide dashboard(s) for accessing and/or managing integration instance(s) or associated information. Some example embodiments receive template information of source schema data, target schema data, and template transformation data, generate an integration template based at least in part on the template information, enable a client system to access at least the integration template via the templating system, and initiate an integration instance based on the integration template.