Let me start by saying that this is not an article about big data. While the source of big data is external to your organization, it is a topic of its own. Many of the concepts and approaches discussed will definitely apply to your big data initiatives, but that won’t be the focus of this article.
Inter and Intra business communications turn out to be perpetually mind boggling, the need to successfully manage time and assets winds up the key. All things considered, and coupled with huge interest in infrastructure and service, the interest for project management (PM) aptitude in Africa has expanded significantly over a wide assortment of Industries. Africa is a market of middle class consumers which is expected to reach 1.1 Billion by 2060 and will need to cater for maintaining the Master data of the customers. The best possible option is using Master Data Management tools and this will lead to more development projects eventually more project managers to make sure everyone works together as a well-coordinated team. Currently the need for project management is on high in Africa, but MDM project managers are rare.
Clients ask me all the time, why? Why do we need to upgrade? We are happy with the way the software is working? if it ain't broke, don't fix it!
In order to manage your master data, you must first measure it.
The objective of most MDM Hub projects is to establish a trusted source of master data. In addition to the right vendor, appropriate partner, and an efficient implementation plan, it is very important to come up with the right integration strategy. An organization's existing eco-system will typically consist of different source systems and integrating all of them with the new MDM system becomes a huge task in itself. Any small misstep here would lead to delays, cost overruns and substandard or missing data. In turn, sponsors will lose confidence in the MDM hub as a trusted source to be integrated with downstream applications.Net result: the ROI will seem a lot less attractive.
This article was featured in the Q3 2014 edition of Loyalty 360's Loyalty Management magazine.
Every project comes with its own set of challenges and MDM projects are no different. At InfoTrellis, we have built an effective methodology for Project Management, through years of experience in managing MDM projects. We like to call it as “InfoTrellis Smart MDM Methodology”.
With the introduction of IBM Master Data Management v11, IBM has created a new implementation style combining the strengths of both MDM Physical and Virtual editions. While MDM Physical is more suited to the “centralized” MDM style (system of record), and MDM Virtual is aligned with the “registry” MDM style (system of reference), MDM Hybrid uses a “coexistence” style to provide a mixed system of reference & record. This article will give an overview of the MDM Hybrid implementation style and a couple of interesting lessons learned during a recent InfoTrellis engagement.
If you walk into a meeting with all your senior executives and pose the question:
MDM BatchProcessor is a multi-threaded J2SE client application used in most of the MDM implementations to load large volumes of enterprise data into MDM during initial and delta loads. Oftentimes, processing large volumes of data might cause performance issues during the Batch Processing stage thus bringing down the TPS (Transactions per Second).