![]() 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. |