Hierarchical Tagging in CRM Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional CRM systems face limitations such as lack of flexibility, high costs, and closed-source structures, leading to a high failure rate of over 70% in implementations.

Innovation Solution

A software-based customer relationship management system incorporating hierarchical tagging, utilizing an open-source framework like SugarCRM, with a base class (SugarBean) and data retrieval API, enabling flexible module functionality and user interface customization, along with a hierarchical tagging system allowing for complex tag hierarchies and internationalization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional CRM systems are implemented, then customer relationship management functionality is provided, but the systems lack flexibility and have high failure rates

Engineering Contradiction:
ImproveflexibilityVSAvoidimplementation success rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system is divided into independent, interchangeable modules that can be selectively activated. Each module encapsulates specific CRM functionality (sales, marketing, service) and can be independently configured, deployed, and modified without affecting other modules, thereby enhancing flexibility while maintaining system reliability through localized changes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system employs dynamic configuration capabilities where module activation, data model structures, and business logic can be modified at runtime without requiring full system redeployment. This dynamic adaptability allows the CRM system to evolve with changing business requirements while maintaining operational stability.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If conventional CRM systems are implemented, then CRM functionality is provided, but the systems have high costs

Engineering Contradiction:
Improvecustomization capabilityVSAvoidimplementation cost
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system separates core functionality into modular components that can be selectively implemented based on organizational needs. This allows customers to deploy only the modules required for their specific use cases, reducing implementation costs while maintaining customization capability through optional module additions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system employs universal data models and standardized interfaces that can serve multiple CRM functions across different modules. This multi-functionality reduces development and implementation costs by eliminating redundancy while maintaining the ability to customize specific module behaviors and configurations.

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

3Adaptability or versatility

If conventional CRM systems are implemented, then CRM functionality is provided, but the systems have closed-source structures

Engineering Contradiction:
Improvesystem customizationVSAvoidsystem modification ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system architecture divides functionality into independent modules with well-defined interfaces, allowing individual modules to be developed, modified, and extended by third parties without affecting the core system. This segmentation enables extensive customization while maintaining ease of modification through localized changes to specific modules rather than the entire system.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9582806B2Customer relationship management system with hierarchical tagging
Publication Date: 2017.02.28 SUGARCRM INC
  • US9582806B2 patent drawing
  • US9582806B2 patent drawing
  • US9582806B2 patent drawing

AI summary

A hierarchical tagging system and method are provided. In one embodiment, a software-based customer relationship management system and method may include the hierarchical tagging system.