Metadata-Driven Analytics Pipelines for Scalable, Secure Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data analytics platforms are limited by their architecture, requiring significant technical expertise, are difficult to scale, and lack security and data monitoring capabilities, preventing users from gaining insights across multiple data products.

Innovation Solution

A serverless data analytics platform that automates deployment and scaling, using metadata-driven flows and pipelines to process data on an as-needed basis, with integrated access control and metadata management for secure and efficient data processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing data analytics platforms use traditional architecture with physical infrastructure, then they can process data, but they are difficult to scale and require significant technical expertise

Engineering Contradiction:
ImprovescalabilityVSAvoidtechnical expertise required
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements automated metadata-driven pipeline creation and execution, where the platform self-configures data processing operations based on metadata specifications without requiring manual technical intervention. This automation reduces the technical expertise barrier while enabling scalable data analytics across multiple data products.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses metadata parameters to dynamically configure data processing pipelines, allowing the same infrastructure to adapt to different data products and analysis requirements by changing metadata parameters rather than reconfiguring the underlying system architecture. This enables scalable adaptation without proportionally increasing system complexity.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If existing platforms segregate different data products separately, then they can manage individual data products, but they prevent users from gaining insights across multiple data products

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

Solution Approach 1:

The system implements a universal metadata-driven pipeline framework that can process multiple different data products through the same infrastructure. The metadata specifications enable a single pipeline template to be applied across diverse data products, allowing cross-product analysis without requiring separate specialized systems for each data product.

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

Solution Approach 2:

The system introduces metadata as an intermediary layer between the physical data infrastructure and the analysis operations. This metadata layer abstracts the heterogeneity of different data products, enabling unified processing and cross-product insights without directly managing the complexity of each individual data product's structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Extent of automation

If existing platforms lack automation, then they can be manually managed, but they require technical specialists to attend to extracting and loading new data

Engineering Contradiction:
Improvedata extraction and loading automationVSAvoidsystem management complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system implements self-service automation where metadata specifications automatically trigger and configure data extraction and loading operations. The platform autonomously interprets metadata to set up pipelines, extract data from sources, and load processed results without requiring technical specialists to manually configure each data operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system requires preliminary metadata specifications to be defined before data processing operations. These pre-defined metadata templates contain all necessary configuration information for data extraction and loading, enabling the system to automatically execute these operations without requiring technical specialists to perform manual setup each time new data needs to be processed.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If existing platforms lack security and data monitoring capabilities, then they can process data freely, but they cannot fulfill regulations or partner requirements concerning sensitive data

Engineering Contradiction:
Improvesecurity and compliance capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces metadata as an intermediary that carries security and compliance information throughout the data processing pipeline. Metadata specifications include access control policies, data classification, and compliance requirements, which are automatically enforced by the pipeline execution engine without adding separate complex security subsystems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where metadata specifications and access control policies are continuously evaluated during pipeline execution. The system monitors data processing operations against defined policies and provides feedback to enforce compliance, ensuring security requirements are met while maintaining streamlined architecture through the existing metadata framework.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12353421B2Systems and methods for management of data analytics platforms using metadata
Publication Date: 2025.07.08 FIDELITY INFORMATION SERVICES LLC
  • US12353421B2 patent drawing
  • US12353421B2 patent drawing
  • US12353421B2 patent drawing

AI summary

A data analytics system is disclosed that can include a data repository configured to store data for multiple clients, a metadata repository separate from the data store, an access control system, and a policy store. The data analytics system can automatically generate metadata for data in the data repository using a metadata engine, the metadata including technical metadata and usage metadata, and store the metadata in the metadata repository. The data analytics system can obtain a client policy governing access to the data. The data analytics system can receive a request to provide the data, the request including instructions to create a pipeline to provide the data. The data analytics system can authorize, by the access control system, the request using the policy and usage metadata; create the pipeline using the technical metadata; and provide the data using the pipeline.