Portable Management Code Composition for Enterprise Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise software applications are often expensive, resource-intensive, and inflexible, making them unaffordable and difficult to integrate for small businesses and even large corporations, which require specific features tailored to their needs.

Innovation Solution

A method and system that compose management code into platform-independent managed objects, transforming it into portable and native management objects, allowing for the selection and integration of specific enterprise modules, enabling flexible and cost-effective deployment of enterprise application services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprise software applications are deployed to provide comprehensive business support functions, then functional completeness is improved, but cost and resource consumption increase significantly

Engineering Contradiction:
Improvefunctional completenessVSAvoidcost and resource consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments enterprise software applications into separate, independently deployable modules that can be selectively activated. Each module provides specific business functions (e.g., inventory management, HR, finance) and can be deployed only when needed, allowing organizations to achieve functional completeness progressively while controlling costs and resource usage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic module activation and deactivation capabilities, allowing the software system to adapt its functional footprint based on organizational needs. Modules can be added or removed without requiring full application deployment, enabling flexible resource allocation and cost management while maintaining access to comprehensive enterprise functions when required.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If comprehensive enterprise software applications are deployed to meet all business needs, then functional completeness is improved, but system complexity increases

Engineering Contradiction:
Improvefunctional completenessVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

By dividing the enterprise software into discrete, independently manageable modules, the patent reduces system complexity. Each module can be developed, deployed, and maintained separately, simplifying the overall system architecture while still providing access to comprehensive enterprise functions when all modules are integrated.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different parts of the system (individual modules) to have specialized characteristics optimized for their specific functions. Each module can be tailored to specific business needs without requiring the entire system to be customized, reducing overall complexity while maintaining functional completeness.

Inventive Principle:
Principle #3Local quality

3Ease of manufacture

If standardized enterprise software applications are deployed, then ease of deployment is improved, but adaptability to specific organizational needs deteriorates

Engineering Contradiction:
Improveease of deploymentVSAvoidadaptability to organizational needs
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the enterprise software into standardized modules that can be deployed independently using common deployment processes. This maintains ease of deployment for each individual module while allowing flexible combination and customization of modules to meet specific organizational needs, thereby achieving both standardization and adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent designs modules with universal interfaces and standardized deployment mechanisms that work across different organizational contexts. Each module can serve multiple functions and be integrated with various other modules, providing adaptability to specific organizational needs while maintaining ease of deployment through standardized processes.

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

4Adaptability or versatility

If additional software applications are added to provide missing features, then functional completeness is improved, but integration complexity increases

Engineering Contradiction:
Improvefunctional completenessVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges previously separate software applications into a unified modular enterprise software system. Related functional modules are combined into integrated components with standardized interfaces, reducing the number of separate applications that need to be integrated while maintaining comprehensive functionality. This decreases integration complexity compared to managing multiple independent applications.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal module interfaces and standardized integration mechanisms that simplify the combination of different functional modules. Modules are designed to work together through common protocols and interfaces, reducing integration complexity while providing comprehensive functionality that would otherwise require multiple separate applications.

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

Data Source

PatentUS9063725B2Portable management
Publication Date: 2015.06.23 ORACLE INT CORP
  • US9063725B2 patent drawing
  • US9063725B2 patent drawing
  • US9063725B2 patent drawing

AI summary

A method is provided. The method composes management code in a platform independent managed object format. Further, the management code is utilized to manage at least one object. In addition, the management code transforms the management code into a plurality of portable management objects and a plurality of native management objects.