Person Object Model Linking Records Across Departments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing CRM solutions face challenges with data duplication and disambiguation when representing users across different contexts, leading to inefficiencies and confusion, as they struggle to scale effectively in managing person-related data across multiple departments and organizations.
Innovation Solution
A computer-implemented system that creates a person object model by linking user records across different organizations and departments, incorporating social identities, and using a unique person key to manage and organize person records, thereby reducing duplication and enhancing data management through a comprehensive view of users across their lifecycle.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing CRM solutions generate separate objects for each person in different contexts, then data can be stored in multiple departments, but data duplication and confusion occur
Solution Approach 1:
The patent merges multiple separate person objects across different departments into a single unified person object. The system combines data from sales, marketing, service, and other departments into one centralized person record with a unique person key, eliminating duplication while preserving contextual information from all sources.
Solution Approach 2:
The unified person object serves multiple functions across different business contexts. A single person object can be referenced by sales teams, marketing teams, service teams, and other departments simultaneously, making the system multi-functional and adaptable to various organizational needs without requiring separate objects.
2Adaptability or versatility
If separate person objects are created for each context, then department-specific data can be maintained, but disambiguation becomes difficult
Solution Approach 1:
The system introduces a unique person key as an intermediary identifier that links all department-specific data to a single unified person object. This intermediary mechanism allows the system to maintain department-specific contexts while providing clear identification and disambiguation through the consistent person key across all records.
3Ease of operation
If manual linking of person records is used, then data can be organized, but the process is time-consuming and does not scale
Solution Approach 1:
The system automatically performs the linking of person records across departments without requiring manual intervention. The unified person object model self-organizes data from multiple sources by automatically assigning and resolving person keys, eliminating the need for manual data organization while maintaining accurate relationships.
Solution Approach 2:
The system performs preliminary actions by pre-establishing the unified person object model and automatically resolving person key relationships before data is needed. This preliminary organization of data through automated person key assignment eliminates the need for manual linking operations when data is accessed or processed.
4Quantity of substance
If existing CRM platforms are used, then basic person data can be stored, but scalability is limited
Solution Approach 1:
The system segments the person data model into modular components that can be independently managed. The unified person object is divided into core identifying fields (person key) and contextual fields (department-specific attributes), allowing the system to scale by adding new contextual segments without affecting the core structure.
Data Source
AI summary
The technology disclosed relates to representing users in different contexts within customer relationship management (CRM) environments. In particular, it relates to creating a person object model for each user in the CRM environment by linking a plurality of user records in the CRM environment that is separately created by different organizations and departments. The person object model also incorporates online social identities of the users, according to one implementation. This inclusive linked model provides a comprehensive view of the users to handlers of the CRM environment, thus facilitating an enhanced overall CRM experience.