Read this for more information on Customer Data Hub (CDH). 
Customer Data Hub (CDH) can be implemented in multiple ways. There are three main instance strategy options that organizations can often consider when implementing the Oracle Customer Data Hub. these three options are industry accepted are:
- E-Business Suite as Hub to 3rd Party Systems
- Customer Data Hub Integrated with E-Business Suite and 3rd Party Systems
- Customer Data Hub with no E-Business Suite
While Oracle Customer Data Hub provides the technology base for meeting the business problem, correct implementation strategy and tools are important to ensure complete solution for implementing organizations and meet specific requirements of each customer.
OPTION 1: E-BUSINESS SUITE AS A HUB TO 3RD PARTY SYSTEMS
With this option, customers can easily leverage their existing E-Business Suite footprint to include the functionality of a Customer Data Hub with integration to heterogeneous 3rd party systems.
Given that E-Business Suite applications are built on the TCA oganizations running the E-Business Suite already store customer data in TCA.Therefore, in order to make the TCA customer data sync with the customer data residing in disparate systems, the implementing organization will need to leverage twith integration or middleware technology, and the Source Systems Management capabilities within the TCA infrastructure. If implementing company use Customer Data Librarian to keep the customer data clean and duplicate-free.That would be best case of either side.
- Existing customer data is migrated one time from 3rd party systems and is continually kept in sync.
- In line with the single-global-instance vision, thereby lowering costs and increasing benefits.
- Allows implementing organizations to sunset any legacy application at any time.
- All customer data resides in operational, transactional E-Business Suite. Therefore, customer information is actionable in real-time.
- Potentially longer initial implementation timeframe given more complexities in maintaining single source of customer truth within the operational data system.
OPTION 2: CUSTOMER DATA HUB INTEGRATED WITH E-BUSINESS SUITE AND 3RD PARTY SYSTEMS
With this option, customers are able to implement the Customer Data Hub more rapidly and begin realizing immediate benefits by integrating the Hub with existing E-Business Suite and 3rd party transactional systems.
In this model, the Oracle Customer Data Hub is installed as the central repository of customer data, and is integrated with the existing E-Business Suite footprint as a source system, in the same fashion that 3rd party legacy systems are integrated. By mapping the E-Business Suite as a spoke system to the Customer Data Hub, implementing organizations are able to get the Hub up-and-running in parallel with their operational business systems, without spending extensive time on transactional business flow integration testing. In addition, this methodology allows implementing organizations to refine their single source of customer truth over time, and eventually cut over to the 'single instance model' when appropriate.
Just as with any other spoke system mapping, it is required that organizations use the Oracle AS 10g integration services (or other third party middleware), and the Source Systems Management capabilities within TCA to keep customer information in sync across all systems, including the E-Business Suite. In addition, implementing organizations will use Customer Data Librarian to keep the customer data clean and duplicate-free.
- Shorter initial implementation timeframe given less complexities in maintaining the CDH separate from operational systems.
- Minimal risk of adversely impacting customer data which could impede business and transactional processes.
- Allows implementing organizations to migrate to the single instance model at their own pace, while still taking advantage of a single source of customer reality.
- Allows implementing organizations to patch the CDH with latest functionality without risk of impacting the existing E-Business Suite footprint.
- Additional spoke system created with this model, rather than reduction of systems. Therefore, additional integration development is required.
- Customer data migrated to Customer Data Hub initially, and then a second effort is required to sync the Customer Data Hub with the E-Business Suite when consolidation occurs in the future.
OPTION 3: CUSTOMER DATA HUB WITH NO E-BUSINESS SUITE
Of course, customers who are not running any E-Business Suite applications at all can also implement the Customer Data Hub.
In this case, the Hub is implemented as the central source of customer truth, and is integrated with all heterogeneous 3rd party systems.
- Allows implementing organizations to begin realizing the value of the E-Business Suite functionality, even before they have the E-Business Suite up and running.
- Allows implementing organizations to plug in pieces of the E-Business Suite at their own pace, or keep legacy systems living on if migrating to the E-Business Suite is not an option.
- Provides an easy migration path to single global instance vision.
- Continued costs (IT and personnel) associated with maintaining disparate systems, with different technologies and platforms.
These three implementation options will helps to find the main instance strategy options which is major task considered when implementing the Oracle Customer Data Hub.