Contact Master System Centralized Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack a central repository for managing data associated with individuals having multiple roles across multiple legal entities, leading to disjointed management, duplicate data, and increased network resource overhead.
Innovation Solution
A Contact Master (CM) system that provides a central repository for storing baseline data and linking it with cross-reference tables to manage additional data associated with individuals across different legal entities, enabling customizable hierarchical search results based on attributes like legal entities, roles, and products.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is stored across multiple repositories without a central repository, then data can be stored locally at each legal entity, but data management becomes disjointed and duplicate data increases
Solution Approach 1:
The system segments data into two types: type A data (baseline data) stored once in the central repository and type B data (additional data) stored in cross-reference tables linked to the central repository. This segmentation allows local storage flexibility while maintaining centralized control and avoiding duplication.
Solution Approach 2:
The system implements a nested data structure where cross-reference tables containing type B data are linked to and nested within the central repository that stores type A data. This nested architecture enables hierarchical data management where detailed entity-specific data is nested within the broader context of baseline data.
2Device complexity
If a central repository is implemented to store baseline data, then data management becomes centralized and duplicate data is reduced, but system complexity increases
Solution Approach 1:
By segmenting data into type A (stored centrally) and type B (stored in cross-reference tables), the system achieves centralized management for consistency while maintaining the ability to store entity-specific variations without compromising overall data reliability.
Solution Approach 2:
The cross-reference tables serve as intermediaries between the central repository and entity-specific data requirements. They link baseline data from the central repository with additional entity-specific data, ensuring data accuracy while managing system complexity.
3Ease of operation
If multiple systems are used to connect data to signed documents, then data can be stored at different locations, but the number of clicks and systems required to find data increases
Solution Approach 1:
The system merges data retrieval operations by providing a unified search interface that queries both the central repository and cross-reference tables simultaneously. This consolidation eliminates the need to search multiple separate systems and reduces the number of clicks required to locate data.
Solution Approach 2:
The search system is designed with multi-functionality to handle various query types (by legal entity, by individual, by role) and search both type A and type B data through a single interface, making it universally applicable to all data retrieval needs without requiring system-specific operations.
Data Source
AI summary
Various examples described herein are directed to systems and methods that retrieve data from an information source. The data includes a first data set for a party and a second data set. The second data set has an entity associated with the party and a role of the party at the entity. The first data set is stored at a database and the second data set is stored at a cross-reference table associated with the database. A data request for requested information is received and the first data set is retrieved from the database. The second data set is retrieved from the cross-reference table based on the first data set. A hierarchical structure is created based on the second data set, where the hierarchical structure has different lists based on one of the entity and the role of the party at the entity.