Dynamic Plugin Registration for Proprietary EPM Data Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise performance management (EPM) systems lack a mechanism for dynamically registering proprietary plugins required to convert proprietary data from user devices into an intermediate format, leading to an undue burden on enterprises due to the need for additional conversion steps.

Innovation Solution

A system and method for dynamically registering plugins in the EPM system, involving a database module to store enterprise and user device information, a data identification module to recognize proprietary data, and a plugin registration module to add necessary plugins to the converter framework, allowing seamless conversion of proprietary data into an intermediate format.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the EPM system uses standard plugins only, then the system structure remains simple and standardized, but it cannot convert proprietary data formats from user devices

Engineering Contradiction:
Improvecapability to convert proprietary data formatsVSAvoidplugin registration mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements dynamic plugin registration where plugins are not statically configured but can be registered and added at runtime. The registration module receives plugin registration requests from user devices, validates them, and dynamically adds them to the converter framework, allowing the system to adapt to proprietary formats without fixed pre-configuration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

User devices can autonomously register their own proprietary plugins with the EPM system by sending registration requests containing plugin information. The system automatically processes these requests, validates the plugins, and integrates them into the converter framework without requiring manual administrative intervention for each proprietary format.

Inventive Principle:
Principle #25Self-service

2Productivity

If proprietary plugins are manually configured, then data conversion capability is achieved, but the conversion process requires additional intermediate steps on user devices

Engineering Contradiction:
Improvedata conversion efficiencyVSAvoidconversion process simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The conversion capability is extracted from user devices and transferred to the EPM system. Instead of requiring user devices to perform intermediate conversion of proprietary formats, the proprietary plugins are registered with and executed by the EPM system's converter framework, eliminating the need for pre-conversion on user devices.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The EPM system acts as an intermediary between user devices and the data analytics platform. The registered proprietary plugins serve as intermediaries within the EPM system, converting proprietary formats to standard formats before data is processed, thereby simplifying the overall data flow and eliminating intermediate conversion steps on user devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the EPM system supports multiple proprietary formats, then data compatibility improves, but system complexity and plugin management burden increase

Engineering Contradiction:
Improvesupport for multiple proprietary formatsVSAvoidplugin management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The converter framework is designed with universal functionality to handle multiple proprietary formats through a unified plugin registration interface. The registration module provides a standardized mechanism that can accommodate any proprietary format by accepting generic plugin registration requests, validating them against common criteria, and integrating them into the existing conversion pipeline without requiring format-specific management procedures.

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

4Productivity

If dynamic plugin registration is implemented, then conversion efficiency increases, but access control and security management become more challenging

Engineering Contradiction:
Improveconversion efficiencyVSAvoidaccess control and security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The registration module implements feedback mechanisms to verify and validate plugins before integrating them into the converter framework. It receives registration requests, validates plugin compatibility and security requirements, and provides feedback on registration status. This feedback loop ensures that only authenticated and compatible plugins are added, maintaining security while enabling dynamic registration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12536230B2System and a method for dynamic registration of plugins in an enterprise performance management system
Publication Date: 2026.01.27 HONEYWELL INTERNATIONAL INC
  • US12536230B2 patent drawing
  • US12536230B2 patent drawing
  • US12536230B2 patent drawing

AI summary

The present invention provides a system for dynamically registering plugin with an Enterprise Performance Management (EPM) system. The system provides a database module operationally coupled to a repository for storing information on registered enterprises, one or more user devices mapped to the registered enterprises, and a set of rules corresponding to each user device. The system further comprises a data identification module which is configured to receive data from one or more user devices and a converter framework comprising a converter module and a plugin module for conversion of data from a user device. The system further provides a registration module which is operationally coupled to said data identification module and the database module and is configured to receive a plugin registration request from a user device including a plugin, identify the user device and its data type, and determine if the plugin is already registered with the repository. Based on determining that the plugin is not already registered with the repository, update the repository to add the plugin and configuration information of said user device. Further, the system provides an access control module operationally coupled to database module to provide to the user device, an access to edit the configuration of added plugin.