Hierarchical Model Objects for Mainframe Data Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current modeling platforms, whether mainframe-based or entry-level, face limitations such as high costs, insufficient data handling capabilities, and proprietary data structures, making it difficult to generate predictive models and export data to other tools, especially for large-scale operations.
Innovation Solution
The development of systems and methods for object-based modeling using hierarchical model objects that can be accessed and manipulated at various depths, allowing for the extraction and export of modeling objects in a native or object-compatible format from spreadsheets, databases, and other sources, enabling seamless communication with mainframe platforms and other resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If mainframe-based modeling software is installed, then modeling power and data handling capability are improved, but cost and complexity increase significantly
Solution Approach 1:
The patent segments the modeling system into a hierarchical structure where a desktop client handles user interaction and data manipulation, while a separate server handles computational modeling tasks. This segmentation allows the complex mainframe-based modeling power to be accessed from a simple desktop interface, resolving the contradiction between needing mainframe power and avoiding mainframe complexity.
Solution Approach 2:
The patent introduces a server as an intermediary component that sits between the desktop client and the mainframe modeling system. This intermediary abstracts the complexity of mainframe connections from the user interface, allowing users to interact with sophisticated modeling capabilities through a simplified desktop environment while the server manages the complex communication and data transfer protocols.
2Ease of operation
If spreadsheet or database applications are used, then ease of operation is improved, but data handling capability and modeling power are insufficient
Solution Approach 1:
The patent creates a universal interface that works with multiple data sources including spreadsheets, databases, and other external systems. The desktop client can import data from various formats and export results to different destinations, providing multi-functionality that maintains ease of operation while enabling sophisticated data handling capabilities through the server's processing power.
3Ease of manufacture
If proprietary data structures are used in entry-level applications, then ease of manufacture is improved, but adaptability and interoperability deteriorate
Solution Approach 1:
The patent employs the server as an intermediary that translates between proprietary data structures from various sources and a unified hierarchical data model. This translator layer maintains the simplicity of working with native application formats while providing standardized object-based interfaces for interoperability with mainframe systems and other external resources.
Solution Approach 2:
The patent implements a nested hierarchical data structure where data from multiple sources are organized in nested object hierarchies. This nesting approach allows proprietary data structures to be contained within the hierarchical framework, maintaining their original simplicity while enabling standardized access and interoperability through the unified object model.
4Ease of operation
If data is copied or moved between locations, then ease of operation is improved, but data precision and completeness are lost
Solution Approach 1:
The patent replaces the mechanical copying process of traditional spreadsheets with an object-based data transfer mechanism. Instead of copying cells and risking data loss, the system transfers complete hierarchical model objects that preserve all attributes, relationships, and metadata. This substitution maintains ease of data transfer while ensuring complete data precision through the server-mediated object transfer process.
Data Source
AI summary
Embodiments relate to systems and methods for object-based modeling using hierarchical model objects. A modeling client can host modeling logic and an application programming interface (API) to create, access, manipulate, and import/export modeling objects used in modeling applications, such as engineering, medical, financial, and other modeling platforms. In aspects, the source data accepted into the modeling client can include consumer or business-level applications, whose spreadsheet, database or other content can be extracted and encapsulated in extensible markup language (XML) or other object-oriented format. Various model objects can be extracted from source data, and aggregated into a hierarchical model object encapsulating and preserving the underlying object layers. In aspects, one or more of the model object layers can functionally combine at least two other layers, to relate levels of data in hierarchical fashion. The modeling client can exchange composite or other modeling objects with external platforms on a programmatic basis.