Embracing MDM in SOA and BPM implementation
Organizations have service oriented architecture (SOA) and business process management (BPM) initiatives to rapidly deploy cross department processes. However, SOA and BPM do not deal with the fragmented data problem directly. These will enable companies to rapidly deploy composite cross department processes across these applications but these new processes will "break" as services will need a common definition of master entities or master data to effectively communicate.
Given such a strategic role of MDM, it should not be looked purely as IT initiative; a bias carries over to many MDM vendors and IT departments within organizations. Thinking of MDM to cleanse and aggregate data is a shortsighted approach. Any data cleansing or data integration exercise will soon be obsolete because new data is constantly being introduced and existing data is being modified. Further, clean augmented quality data for a departmental application will not bring the full advantage to the organization. SOA and BPM can propagate and expose the master data to the cross department processes. Together, MDM, SOA and BPM can create cross department processes that work to build customer value.
Would be interested in your throughts and comments ..........
