By Robert Barker, Infoglide Senior Vice President & Chief Marketing Officer
Dan Power at Hub Solution Designs recently challenged “MDM project team leaders, program managers, and data champions” to think about the importance of integration. In particular, he asks about MDM integration in three contexts: real-time, business modeling, and two-way hub communication.
Additionally, Jill Dyché recently pointed out that Identity Resolution supports and enhances five of eight core MDM functions outlined in her book on CDI, and we agree wholeheartedly. Given that Identity Resolution (IR) is integral to MDM, we can ask the first of Dan’s integration question: how should IR be integrated with MDM? More specifically, should this integration be batch or real-time?
The answer is, of course, it depends. Instead of asking “what will we be giving up by not providing for any real-time capabilities?” maybe we should ask “is the value of the MDM application sufficiently enhanced to justify the incremental infrastructure cost of using real-time data sources?” Sometimes the answer is yes, and sometimes it’s no.
Let’s consider two examples in the area of fraud detection. In a bank or retail setting, discovering a hidden relationship between two fraudulent people and keeping a fraudulent transaction from being consummated may save thousands of dollars in apprehension costs over catching it a day later, so a real-time approach is easily justified. On the other hand, in a case like insider securities trading, the acts are not preventable and the data connecting someone “in the know” with the person who makes a transaction based on a tip persists forever and can be caught and prosecuted months after it occurs.
Regardless of whether real-time or batch integration is selected, having multiple modes of integration available to match project requirements is important. In some cases, simple point-to-point XML data exchange may be enough, but in others it can be imperative that IR decisions be smoothly integrated into existing business processes. That may require using BPM, queuing, web services and other broadly supported methods of integration, again depending on the specific application context.
The takeaway: it’s essential to include multiple integration capabilities among the criteria you use in evaluating Identity Resolution technology.