Hierarchical Client Task Management System with Role-Based Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information management systems in business environments face challenges in organizing and securing client data across a network, particularly in banking applications, where redundancy and errors are common due to the lack of a centralized and secure solution for task management and document storage.

Innovation Solution

A hierarchical two-tiered client information task management system that allows for centralized storage and secure access to client data, featuring customizable checklists, timed alerts, encryption for secure communication, and user access control, enabling efficient organization and management of client information and documents across a network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized repository is implemented for storing client information and documents, then data security and organization are improved, but system complexity and access control requirements increase

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments access control into multiple hierarchical levels: global administrators who manage the entire system, class administrators who manage specific client classes, and users with role-based access (full access, view-only, or no access). This segmentation allows the complex security requirements to be broken down into manageable, hierarchical control structures that can be independently configured and maintained.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to access control, organizing users and data into nested levels (global → class → user). This dimensional approach transforms the complex security problem into a structured hierarchy where access rules can be applied at each level, making the overall system more manageable despite the increased security requirements.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If hierarchical access control is implemented with multiple user types, then data security is improved, but ease of operation deteriorates due to complex access management

Engineering Contradiction:
Improvedata securityVSAvoidease of access management
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary configuration of access rights during user creation and class setup. Global administrators pre-define the access hierarchy and permissions before users need to access data. This preliminary action eliminates the need for complex real-time access decisions, as the access control structure is already established and automatically enforced when users log in.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Users automatically receive their assigned access rights without manual intervention during each access attempt. The system self-manages access control by automatically applying the pre-configured hierarchical rules based on user role and class assignment, eliminating the need for users to manually manage their own permissions or for administrators to intervene in each access request.

Inventive Principle:
Principle #25Self-service

3Reliability

If multiple user types with different access levels are created, then data security is improved, but device complexity increases due to user profile management

Engineering Contradiction:
Improvedata securityVSAvoiduser profile management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The user profile system is segmented into distinct, pre-defined roles (global administrator, class administrator, full access user, view-only user, no access user). Each role has a specific, predetermined set of permissions. This segmentation transforms the complex problem of individual permission management into a simpler process of role assignment, where administrators only need to assign roles rather than configure individual permissions for each user.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If a hierarchical two-tiered system is implemented for organizing information, then organization and accessibility are improved, but system complexity increases

Engineering Contradiction:
Improveinformation organizationVSAvoidsystem structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The information system is segmented into two distinct hierarchical tiers: classes (representing client groups or categories) and programs (representing specific initiatives or projects within classes). This segmentation provides a clear, logical structure for organizing information that is simple enough to understand but flexible enough to accommodate complex business requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a hierarchical dimension to information organization by structuring data in nested levels (classes containing programs). This dimensional approach allows information to be organized and accessed from multiple perspectives - by class category or by specific program - without requiring a completely complex multi-dimensional system.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8352599B1Method and computer program for managing client task information with multiple users
Publication Date: 2013.01.08 WEST TECH GRP LLC
  • US8352599B1 patent drawing
  • US8352599B1 patent drawing
  • US8352599B1 patent drawing

AI summary

A method and computer program for managing client task information across a network with multiple users. The method and computer program is designed to be flexible by providing a standard set of tools for account managers while allowing customization of those tools. The method and computer program includes creating one or more classes associated to a client, creating one or more programs associated to a client's promotion, setting lists of tasks to be completed for a promotion, alerting users when a task is not completed by a given time, creating and storing template documents for a promotion, creating directories of file storage units, uploading electronic documents to the file storage units; inputting contact information into a class or program; providing levels of access to the client task information based on the user.