![]() ![]() I was happily tooling along using Tortoise SVN through VMWare, sloooooI remember sitting in Ben's office thinking, "Crap. Especially when those programs involve heavy use of the command line and every tutorial written about them is so technical it might as well be in another language. When we are aware that there are silos of the same or similar data in the enterprise and we need to harmonize them to create a golden copy in-fact the aim is to identify the best version among all store information.Let me start by saying I'm not one of those super tech-minded designers who loves to dive into new programs. And in order to do that we need to bring them all to a central location. ![]() Then de-dupe it and execute survivorship to generate the Golden record. At times the defined rules in the system are not enough and we will need some expert intervention to resolve duplicities or even to realize whether or not they are duplicates at all like identifying false positives and dealing with them. Typically large enterprises that have adopted digitalization long back and have collected information using multiple sources like ERP, CRM, Web Apps, Websites, POS, etc. So, if we need consolidation then the MDM solution should be capable of sophisticatedly handle complex matching scenarios and should give the developers the flexibility of choices to pick and select different matching algorithms and different matching techniques. This is the reality in most of the MDM implementation projects. ![]() The aim always is to identify data silos and consolidate them. Once consolidated then use the MDM product also as the authoring tool and phase-wise decommissioning other authoring solutions. So, start with the Consolidation pattern and aim for the Centralization pattern. However lucrative this approach seems to be. It is often not possible as there are specialize COTS or custom full-stack apps that address a very specific and business-critical requirement hence cannot be decommissioned hence co-existence is the only option. ✓Risk management - Avoiding business risks ✓Regulatory compliance – Maintaining the organization’s good standing with the authorities ✓Reporting – Ensuring accurate reports for high-quality decision making Third Challenge – Building a Business case for MDM✓Reconciliation – Reducing the direct costs of bad data Where we not only consolidate information coming from other systems but also enrich them using MDM and then publish it to everyone else. ReportingEnterprise hierarchies, dimensions, and attributes are used to aggregate or subdivide the source system data presented in reports. When reporting across systems, the individual source system dimensions must be standardized (conformed). Without MDM there is no enterprise source of reporting metadata (conformed dimensions and hierarchies). This means the reporting team prepares for reporting by manually conformation/mapping dimensions. How long does it take to prepare the reporting metadata (master data, dimensions, and hierarchies/rollups)? Does anyone review (or approve) the prep? Is this work is duplicated throughout the organization? Manual efforts add time to the reporting process and introduce errors and reduce flexibility. ![]()
0 Comments
Leave a Reply. |