Master Data Management

A Single Source System is designated as the “System of Record” for Master Data.

appMDM provides “Central Data Hub” to process Master Data Maintenance Transactions (Add, Change, Archive, Purge).

A “Master Data Governance” group controls the Master Data Management process and safeguards the data.

appMDM consolidates master data from multiple sources into a Central Data Hub (Data Mart) using Data Quality Management features. The Data Hub allows consolidated reporting and query of master data, inventory, cost, and account balances etc.

Work Flow functionality supports data governance and approval processes and procedures.

Control of privileges at organization/object/attribute level ensures data integrity.

Chain-Sys provides a configurable Platform for users to create their Data Model, User Interfaces, and Business Validations for the MDM Hubs. The Platform automates the code creation for the MVC architecture. The Data Architects can create any complex Data Hubs using this platform rapidly.

appMDM provides complete flexibility on the Domains. It provides the following out of the box domains for Products (Products, BOM Structures, Formulas, Routing, and Recipe), Contacts (Customers, Customer Sites, Customer Contacts, Suppliers, Supplier Sites, Supplier Contacts, Employee and Employee Contacts) and Operations (Fixed Assets, and GL Code Combination). Designing a custom domain is easy. Users can create domain hubs for their specific needs with no programming efforts, by simple configurations. Chain-Sysstrongly believes in the template based approach for creating Hubs. appMDM provides templates for all their standard domains against major applications such as: SAP, Oracle EBS, Oracle Fusion, JD Edwards, PeopleSoft, Microsoft and Chain-Sys ERP.

“DQM is a prime mover of a successful SAP Data migration project. It is a mandatory process and cannot be wished away.”

Chain-Sys provides a state-of-the-art ETL tool for configuring Migration and Integration objects. Chain-Sys offers the Industry Gold Standards: appMIGRATE and appINTERFACE tools for performing the Data Migration and Integration for MDM efforts.

“For a large document management company we reduced Item Master data size to about 5% of the original size.”

Chain-Sys provides multiple roles to the MDM users such as: Operations, Data owner, Data Steward, Data Guardian, Data Architect etc. All these roles are used in configuring the workflow for any new Master Data introduction into the hub and also for processing the inbound master data that is interfaced from other Consumer Systems.

Establish a centralized Data Governance Organization to:

  • Design and maintain the enterprise data model that supports desired business application landscape and capabilities
  • Ensure that Data Management efforts (Business or IT) are accelerated and consistent with enterprise core process performance
  • Accountable for data quality; resolve information and cross process issues
  • Enforce global data rules and standards monitoring master data quality metrics and initiating corrective action Correct Pre-validation Errors
  • Maintain an enterprise wide consolidated “data mart” for reporting , query and analysis

“For a large document management company we reduced Item Master data size to about 5% of the original size.”

appMDM’s Data Quality Management comprises Data Consolidation, Data Standardization, and Data Harmonization activities. Consolidating the data into the Hubs is a critical activity. The system collects data from multiple source systems and sends it to target MDM Hubs to perform Consolidation. Hadoop technology is extensively used. appMDM provides the “Matches”, and the Data Stewards or the Data Owners can classify the matches as “False Positive” or “False Negative” and perform the merge, drop or migrate actions.

“Major Japanese consumer electronics firm’s European Division built over 200 Coexistence integration objects using appINTERFACE Module of appMIGRATE and saved over 70% in cost and time. The integrations were built in record times where the traditional ETL approaches had failed.”