Metadata-Driven Multi-Tenant Analytics for Cross-Product Data Flows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data analytics platforms are limited by their architecture, requiring technical expertise, segregating data products, lacking scalability and security, and failing to provide integrated insights across multiple data products.

Innovation Solution

A serverless multi-tenancy data analytics platform that automates deployment and scaling, uses metadata-driven flows, and supports flexible access controls to enable less-technical users to gain insights across diverse data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing data analytics platforms use separate handling for different data products, then data segregation is maintained, but users cannot gain insights based on analysis across multiple data products

Engineering Contradiction:
Improvecross-data-product analysis capabilityVSAvoidplatform architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple data products into a unified data lake architecture where data from different sources is stored together in a common namespace. This allows users to perform analysis across multiple data products without the system needing to separately handle each data product, thus enabling cross-data-product analysis while simplifying the overall platform architecture.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The data lake serves as a universal storage and processing layer that handles multiple data products through a single interface. The unified query engine and analysis tools can operate on any data within the lake regardless of source, providing multi-functional capability that enables insights across diverse data products without requiring separate processing paths.

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

2Productivity

If data analytics platforms depend on physical infrastructure such as on-premises server farms, then data processing capability is provided, but the systems are difficult to scale

Engineering Contradiction:
Improvedata processing capabilityVSAvoidscalability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements virtualization by creating virtual copies of computing resources through virtual machines and containers that run on physical infrastructure. This allows the platform to scale by provisioning additional virtual instances without requiring proportional increases in physical hardware, enabling flexible scaling of data processing capability while maintaining productivity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The platform employs dynamic resource allocation where computing resources are allocated and de-allocated based on demand. The system can dynamically scale processing capacity by spinning up additional compute nodes or containers when needed and shutting them down when not needed, providing both high productivity when required and easy scalability without permanent physical infrastructure commitments.

Inventive Principle:
Principle #15Dynamics

3Productivity

If users interact with existing data analytics platforms, then data processing functions are accessed, but the process is complicated and requires multiple years of training

Engineering Contradiction:
Improvedata processing functionVSAvoiduser interaction complexity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements self-service capabilities through automated data preparation, automatic schema detection, and intelligent query generation. The system automatically performs data cleaning, transformation, and validation without requiring user intervention, and provides natural language query interfaces that eliminate the need for complex technical knowledge. This maintains full data processing functionality while dramatically reducing operational complexity for users.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The platform introduces an intelligent intermediary layer that sits between the user and the complex data processing engine. This intermediary automatically translates high-level user requests into detailed processing operations, handling all the technical complexity behind the scenes. Users interact with simple, intuitive interfaces while the intermediary manages the complicated data processing functions, effectively decoupling ease of operation from processing capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If existing data analytics platforms lack automation, then technical specialists can manage data extraction and loading, but the process requires continuous technical specialist attention

Engineering Contradiction:
Improvedata extraction and loadingVSAvoidsystem management automation
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent implements automated feedback loops where the system continuously monitors data sources, detects changes, and automatically triggers data extraction and loading operations. The system tracks data freshness metrics and automatically schedules updates when data becomes available, eliminating the need for manual intervention. This maintains continuous data extraction and loading productivity while achieving full automation of system management.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-configuring data extraction pipelines, scheduling automated data loading jobs, and setting up monitoring mechanisms in advance. Data extraction and loading are automated through pre-programmed workflows that execute without technical specialist attention, while the system proactively manages data pipeline maintenance and optimization before issues arise, achieving both continuous productivity and high automation.

Inventive Principle:
Principle #10Preliminary action

5Device complexity

If data analytics platforms lack security and data monitoring capabilities, then data processing is simplified, but the system cannot fulfill regulations or partner requirements for sensitive data

Engineering Contradiction:
Improvedata processing simplicityVSAvoidregulatory compliance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments security and compliance functions into separate modular components that operate independently from the core data processing engine. Data classification, access control, encryption, and auditing are implemented as separate layers that can be applied to different data sets based on sensitivity requirements. This segmentation maintains processing simplicity for standard data while providing comprehensive security and compliance capabilities for sensitive data through optional, targeted implementations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different levels of security and monitoring to different data based on their sensitivity and regulatory requirements. Standard data processing operations remain simple and unburdened by complex security measures, while sensitive data automatically receives enhanced security controls, encryption, and monitoring. This local quality approach ensures regulatory compliance for sensitive data without compromising the simplicity of overall data processing.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12579151B2Multi-tenancy data analytics platform
Publication Date: 2026.03.17 FIDELITY INFORMATION SERVICES LLC
  • US12579151B2 patent drawing
  • US12579151B2 patent drawing
  • US12579151B2 patent drawing

AI summary

A data analytics system is disclosed that is configured to perform operations including receiving input data at a first storage location and configuring a flow service to execute a flow. The flow execution can include creating a pipeline using the flow and metadata associated with the flow, the pipeline configured to perform a data transformation specified in the flow. The flow execution can further include determining a tenancy associated with the input data using the flow. The flow execution can also include generating, using the pipeline, output data from the input data and storing, using the pipeline, the output data in a second storage location associated with the tenancy.