appMDM™ makes the daunting job of Master Data Management easy. Chain-Sys understood that Master Data Management (MDM) is not just about data hubs, governance and data quality, but also the very important task of bringing the master data from the feeder applications and also sending the massaged record of truth to the consumer applications. appMDM™ is the only product that offers 2000 + ready built connectors (adapters) to major ERP and Enterprise Applications (SAP S/4HANA, SAP ECC, Oracle Cloud Applications, Oracle E-Business Suite R12, Primavera, Peoplesoft, JDEdwards, Siebel, Microsoft Dynamics, Salesforce, Procore, etc.)

Unlike some Master Data Management products, which are tied to one of the hubs, such as Customer Data Hub, Product Data Hub, Supplier Data Hub, appMDM™ offers all the above hubs as pre built standard hubs, and provides rapid drag and drop development of new hubs. The underlying technology platform, Chain-Sys Platform™, allows the rapid construction of Master Data Management hubs, governance and workflows. Governance and Data Quality measures can be extended to Transactional data such as Invoices, Sales Orders, etc.

appMDM™ addresses the main areas of Master Data Management:

Master Data Governance
Data Quality Management
Master Data Simplification
Transaction Data Simplification
Operational Data Simplification
Metadata Management
Data Analytics
Building new Data Hubs
Data Profiling and Data Consolidation
Pre-built Connectors / Adapters to major ERPs
Pre-built Hubs for Customers, Products and Suppliers
Cloud or On-premise deployments

  Demo Request   Brochure PDF   White Papers

Data Standardization
Process of bringing data into common format across applications, e.g. addresses.


Data Consolidation
Ongoing process to identify and handle duplicate Master records. Rules are built continuously to identify potential duplicates. A decision would be made to keep, merge, or eliminate the duplicates. appMDM™ uses complex algorithms to facilitate identification of potential duplicates.


Data Harmonization
This is a core function of any operational MDM. Creating a single source of truth Master Record, from various applications and allowing usage of this record of truth by various consumer applications. Cross referencing information would need to be maintained for each application. Cross referencing is additionally helpful during the situations of merging duplicate master records. This cross referencing ensures that child data does not get orphaned while merging or eliminating a duplicate master (parent) record.


Data Profiling
Process of analyzing Master Data and providing statistical summaries, e.g. minimum, maximum, average, median, number of unique values, distribution of values, etc. If 99% of the values for a column fall within the range of 0-100 and less than 1% have a value in excess of 1,000,000, that is a pretty good indication the outlier data needs to be evaluated for correctness and quality.


Data Cleansing
This would generally be done based on user defined rules. Once MDM is set up, corrections could be made in the source systems and pulled into the data hub, or data could be corrected in the data hub and pushed back into the source system.


Data Enrichment
Some legacy systems will not have as robust data as do more modern systems. Data Enrichment may be required to add missing information deemed critical.

Operational versus Analytical MDM

The Operational MDM objective is to make the multiple Operational Applications work in harmony, without creating confusion about same master data information maintained in the multiple systems.

Many of the quality measures undertaken in an Operational MDM endeavor, can be easily be carried over to Analytical MDM. This results in reports generated from quality data, making decisions from such reports more accurate and meaningful.

Data Governance
Data Governance is the process of carefully crafting master data, by allowing newly created master data to be reviewed and approved by data stewards and business process stakeholders.


Differentiators

In appMDM™ there is no need to design and develop data integration interfaces between hub and systems such as SAP S/4HANA, SAP ECC, Oracle Cloud Applications, Oracle EBS, Primavera, Peoplesoft, JDEdwards, Siebel, Microsoft Dynamics, Salesforce, Procore, etc. The product comes with 2000 + ready built connectors (adapters)

The underlying technology platform, Chain-Sys Platform™, allows the rapid construction of Master Data Management hubs, governance and workflows

appMDM™ offers pre built Master Data Management hubs for Customer Data, Product Data, Supplier Data, EAM Assets, Equipment Data, Bills of Materials, Routings, Recipes, Fixed Assets, General Ledger Chart of Accounts.

appMDM™ is available on both Cloud and On Premise.

Many Master Data Management solutions are tightly coupled with the vendor’s ERP system making it difficult to deal with master data stored outside that system. In appMDM™, with the ability to easily configure custom templates, custom data hubs can be easily created to handle almost any information regardless of the system in which it is stored. Your Enterprise System’s Master and Transaction data maintenance can be streamlined by configuring easy to use screens containing just the information required by the users. The Enterprise System’s validity checking is enforced. Additional business rules can be configured.

No programming is required. All capabilities can be configured using drag and drop.

With appMDM™ you don’t have to buy a number of Master Data Management Tools to accomplish different data management tasks. appMDM™ provides integrated end to end data management including not just Data Quality, Master Data Simplification, Metadata Management, Integration, and Data Governance but also Data Analytics and Visualization with built in capabilities around Customer 360, Supplier 360, and Product 360.

Data Deduplication
Duplicate master data occurs due to many reasons. Some of the possible reasons are: Acquisition of companies, lack of co-ordination between departments or groups responsible for creating master data, purposefully creating duplicate records to overcome certain inadequacies, moving from multiple ERP or operational systems to one single system, mistaken records created due to confusions arising out of using different abbreviations and spelling for customer names, etc. The process of deduplication in master data management involves manual or automated identification of possible duplicate master records and presenting the same to decision makers, who in turn can decide whether to drop some records, merge records keeping the best parts from throw away records, etc. This process is also many a time part of data consolidation.