Master data management (MDM) identifies the most critical information within an organization to create a single, authoritative view of business-critical data from disparate, duplicate, and conflicting information to power business processes.
Historically, Master Data Management has been largely a manual activity with plenty of consultants interviewing, discovering, and documenting what data is important, what the meaning is to different users of the information, what the correct sources of record are, and what business logic is required to combine various sources meaningfully. Many MDM projects fail because of the difficulty of managing the changing and varied needs of the business users involved.
Enterprise Enabler is a natural platform to define and manage reference or “master” data, from declaring specific Sources of Record to defining and generating actionable “Enterprise Master” entities that are documented and hosted by the platform itself. Information about customers is readily available but extremely diverse and comes from a variety of sources with multitudes of attributes, making it difficult and costly to maintain ALL the data needed to provide a 360 view of the customer in a physical MDM system.
Using Enterprise Enabler, traditional master data can be kept in traditional MDM systems and Data Virtualization can be used to deliver a Master Data Entity that contains all the other attributes of the customer’s data. A Master Data entity in Enterprise Enabler is configured by selecting data from one or more sources, each defining a “source template,” which may be designated as a Source of Record. A desired Master Data entity is defined as a virtual endpoint that represents the data set of interest. The relationships of the data, along with the associated data transformations and validations are configured and tested using the platform’s UI. Once it is tested, the Enterprise Master is packaged by the platform in every consumable format that may be needed, such as ODBC, JDBC, REST, SharePoint BCS, Odata, ADO.Net.
Stone Bond’s unique transformation engine data and flexible caching enables Agile MDM in days— non-intrusively, inexpensively, and flexibly. Agile MDM can complement MDM solutions by federating, transforming and delivering data across source systems.
There are usually two approaches used, one being explicit pre-determined Master Data entities that are known to be needed, and those that have been configured for particular integration situations and later designated as a Data Master by virtue of the level of re-use being made of the entity in integrations. The combination allows organic growth of Master Entities as well as those predefined through the consultative approach.