Embedded Computational Notebook for Secure Enterprise Workflow

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing computational notebooks are not seamlessly integrated with enterprise application software (EAS), leading to security risks, lack of offline access, and cumbersome sharing and scheduling, with users experiencing a disjointed user experience and inadequate authentication/authorization.

Innovation Solution

Embedding a computational notebook within EAS using a component that binds access to the notebook infrastructure, allowing seamless user experience, secure storage, and controlled sharing/reuse, with interactive and scheduled execution modes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a computational notebook is kept external to EAS, then the notebook can be accessed independently, but the user experience becomes disjointed and security risks increase due to credential exposure

Engineering Contradiction:

Improveuser experienceVSAvoidsecurity

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent embeds the computational notebook interface directly within the EAS user interface, merging two previously separate systems into one integrated environment. This eliminates the need for users to switch between applications and share credentials externally, thereby improving user experience while enhancing security by keeping all operations within the secured EAS environment.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary component that sits between the notebook infrastructure and the EAS, managing communication and authentication. This intermediary handles credential verification and data exchange securely, allowing the notebook to access EAS resources without exposing user credentials externally.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If a computational notebook is embedded within EAS, then security is enhanced and user experience is seamless, but the integration complexity increases

Engineering Contradiction:

ImprovesecurityVSAvoidintegration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the notebook functionality into distinct modular components: an embedded user interface layer within EAS, a backend notebook execution engine, and an intermediary communication layer. This segmentation allows each component to be developed, maintained, and secured independently, reducing overall integration complexity while maintaining security.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal embedded notebook component that can serve multiple functions within EAS: data analysis, visualization, reporting, and collaboration. This multi-functional design reduces the need for multiple separate systems and simplifies integration by providing a single versatile solution.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If a computational notebook is kept external to EAS, then the notebook can be freely shared, but authentication and authorization become uncontrolled and cumbersome

Engineering Contradiction:

Improvenotebook sharingVSAvoidauthorization management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the notebook sharing functionality with EAS's existing authentication and authorization framework. By combining these systems, users can share notebooks through EAS's controlled environment, which automatically handles permissions and access rights, eliminating the need for separate uncontrolled sharing mechanisms.

Inventive Principle:

Principle #5Merging (Combining)

4Adaptability or versatility

If a computational notebook is kept external to EAS, then the notebook can run independently, but offline access and scheduled execution become infeasible

Engineering Contradiction:

Improveexecution flexibilityVSAvoidaccessibility

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges the notebook execution capability with EAS's task scheduling and resource management systems. This integration allows notebooks to be executed on-demand, scheduled for future runs, or triggered by events within EAS, providing both offline capability and flexible access while maintaining seamless integration.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20260050424A1Systems and methods for embedding a computational notebook

Publication Date: 2026.02.19 KINAXIS INC

AI summary

Systems and methods for embedding a computational notebook within an enterprise application software. A computational notebook editor embedded is embedded within a software client interface which is in communication with the software client interface. The application server comprises a reverse proxy server that is embedded within the application server. A container management system is in communication with the application server and comprises a multi-user server, a notebook interactive development environment, and a notebook execution tool.