Big-Data View Integration for Cross-Platform Management Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional office management software lacks cross-platform integration, leading to inefficiencies, redundancies, and desynchronized data, which hinders effective management and performance evaluation across disparate platforms.

Innovation Solution

A big-data view integration platform that generates integration GUIs, integrating push-based, pull-based, and queue-based data from various platforms, including legacy and non-legacy services, to provide a unified view of business operations, enabling comprehensive management and incentive planning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple disparate management software products are used to provide comprehensive business solutions, then functional capabilities are improved, but system complexity and data synchronization issues worsen

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

Solution Approach 1:

The patent combines multiple disparate management software products into a single integrated platform that provides comprehensive business solutions. The system integrates HR management, performance tracking, goal setting, and incentive planning modules into one unified system, eliminating the need to use multiple separate software products while maintaining all necessary functional capabilities.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The integrated management platform is designed to perform multiple functions across different business domains. A single system handles employee information management, performance evaluation, goal tracking, and incentive distribution, making the system universally applicable to various management needs without requiring separate specialized software for each function.

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

2Ease of manufacture

If manual processes and paper work are used to manage business operations, then implementation simplicity is improved, but productivity and efficiency worsen

Engineering Contradiction:
Improveimplementation simplicityVSAvoidoperational efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent replaces manual paper-based processes with an automated digital system. Employee information, performance data, goal tracking, and incentive calculations are all managed electronically through the integrated platform, eliminating the need for manual paperwork while maintaining ease of implementation through user-friendly interfaces.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If data is stored in disparate platforms with different formats, then platform independence is improved, but data integration and measurement precision worsen

Engineering Contradiction:
Improveplatform independenceVSAvoiddata integration accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The integrated management platform implements a unified data structure and standardized format for storing and processing information across all modules. Employee data, performance metrics, goal information, and incentive details are all stored in consistent formats within the same system, ensuring accurate data integration and precise measurements while maintaining platform independence through a self-contained architecture.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS12468691B2Big-data view integration platform
Publication Date: 2025.11.11 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US12468691B2 patent drawing
  • US12468691B2 patent drawing
  • US12468691B2 patent drawing

AI summary

A big-data view integration platform generates integration guided user interfaces (GUIs). A first edge node ingests push-based and pull-based data from a plurality of platform services, which include legacy and non-legacy services having incompatible communication protocols. An event-based queue receives from the first edge node a plurality of queue events as indirect push-based data. A second set of queue events includes direct push-based data as received directly from a non-legacy platform service. A conformity component integrates the push-based data, the pull-based data, and the plurality of queue events into integration data having an enhanced integration format. A view integration component generates a plurality of data views from the integration data. A second edge node exposes the plurality of data views via an access services application programming interface (API). A new service execution component accesses the access services API to generate integration GUIs based on the data views.