Mobile Entitlement Map Landing Site Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for displaying and managing hierarchical entitlements across disparate applications are inefficient and lack interactivity, leading to difficulties in managing entity and employee hierarchies, account maintenance, and entitlement enforcement.
Innovation Solution
A method for deploying an interactive hierarchical entitlement map on a mobile platform that inventoryies landing sites, eliminates those requiring an Oracle database connection, and provides a graphical user interface for selecting a default landing site, allowing for entitlement authorization management and automatic transmission of client information modifications to a System of Record without human input.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all features are combined into a single interactive application, then efficiency is improved, but device complexity increases
Solution Approach 1:
The patent segments the hierarchical entitlement management system into modular components: entitlement definition module, entitlement enforcement module, hierarchical map display module, and landing site configuration module. Each module handles specific functions independently, allowing the complex system to be managed through discrete, manageable segments that can be developed and maintained separately.
Solution Approach 2:
The patent creates a universal entitlement management platform that handles multiple functions within a single application: defining entitlements, enforcing entitlements, displaying hierarchical maps, configuring landing sites, and managing signatory authorizations. This multi-functional approach consolidates what would otherwise require multiple separate applications, improving efficiency while using modular design to manage complexity.
2Measurement precision
If database connections are required for all landing sites, then data accuracy is improved, but deployment flexibility deteriorates
Solution Approach 1:
The patent applies local quality by allowing different landing sites to have different data connection characteristics. Critical landing sites that require real-time data accuracy maintain database connections, while less critical landing sites can operate with cached or offline data. This enables each landing site to be optimized for its specific functional requirements rather than applying a uniform connection strategy.
Solution Approach 2:
The patent implements preliminary action by pre-configuring landing sites with appropriate data connection strategies during the entitlement management setup phase. The system pre-identifies which landing sites require real-time database connections and which can use cached data, establishing data accuracy and deployment flexibility requirements before actual deployment occurs.
3Reliability
If manual input is required for all modifications, then data reliability is improved, but productivity deteriorates
Solution Approach 1:
The patent implements feedback mechanisms where the system automatically validates modifications against predefined entitlement rules and hierarchical structures before applying changes. The entitlement enforcement module provides real-time feedback on whether proposed modifications comply with established entitlement policies, ensuring data reliability while allowing rapid legitimate modifications without manual review.
Solution Approach 2:
The patent enables self-service through automated entitlement enforcement and validation. The system automatically checks modifications against entitlement rules, validates hierarchical relationships, and enforces access controls without requiring manual human input for each modification. This maintains data reliability through automated validation while significantly improving modification speed.
Data Source
AI summary
A method for providing hierarchal client entitlement information in a graphical user interface (“GUI”) is provided. The method includes deploying the information on a mobile platform. The method may further include inventorying a list of possible landing sites for deploying the mobile platform and determining which of the inventoried landing sites requires, upon deployment, a connection to an Oracle database. The method may further include eliminating any member of the list of possible landing sites that requires, upon deployment, a connection to the Oracle database from the list of possible landing sites. Following the eliminating, the method may include providing a user, via the GUI, a selection capability to select one of the list of possible landing sites as a default landing site for the deploying the mobile platform.


