Initial discussions identified some core concepts related to mastering strategies. These concepts requires definitions in this context:
- Complex Validation
|From CIO "Demystifying Master Data Management"|
Unfortunately, most companies don't have a precise view about their customers, products, suppliers, inventory or even employees. Whenever companies add new enterprise applications to "manage" data, they unwittingly contribute to an overall confusion about a corporation's overall view of the enterprise. As a result, the concept of master data management (MDM)
|From MSDN "The What, Why, and How of Master Data Management"|
Here is a typical master-data horror story: A credit-card customer moves from 2847 North 9th St. to 1001 11th St. North. The customer changed his billing address immediately, but did not receive a bill for several months. One day, the customer received a threatening phone call from the credit-card billing department, asking why the bill has not been paid. The customer verifies that they have the new address, and the billing department verifies that the address on file is 1001 11th St. N. The customer asks for a copy of the bill, to settle the account. After two more weeks without a bill, the customer calls back and finds the account has been turned over to a collection agency. This time, they find out that even though the address in the file was 1001 11th St. N, the billing address is 101 11th St. N. After a bunch of phone calls and letters between lawyers, the bill finally gets resolved and the credit-card company has lost a customer for life. In this case, the master copy of the data was accurate, but another copy of it was flawed. Master data must be both correct and consistent.
This section describes the various vendors approach and sales pitch within this topic area.
oracle.mds.config.MDSConfigurationException: MDS-01333: Element "mds-config" ontbreekt.
Mapping is about moving data from one or many provider object(s) into domain objects and vice verse.
Synchronization is about keeping data in sync across core systems.
- Last Attribute Update Wins (LAUW)
- Master Changed OOB-Update Remaining Sources (McOOBURS)
- Democratic Master (DM)
- [Human Consensus Master (HCM)]
- [Voting Master (VM)]
- How? Eventing?
|Complexity / Scalability||Minimal||Normal||Høy|
|Middels|| ETL Sync
|Høy|| LastUpdateWins, Democratic
New system is introduced and is assigned responsibility as master. Example: Collab migrations Lotus -> Microsoft.
The least evolvable, biggest, baddest system is assigned master responsibilty because any other options make architects piss their pants.