MDM is actually a very important basic information for daily business of the modern enterprise, the enterprise almost all production and business activities, are inseparable from the support of the main data, so. Master data is among the most important corporate information.
However, for the MDM management, especially the construction of MDM system, now have a similar yet Reference Model SOA reference architecture like it, may often be ready to build MDM or MDM management of enterprises or CIO who bring some confusion , view the information found recently. Jill Dyche, Evan Levy master data hierarchical model, which has a very important reference.
Based on the complexity of the implementation of master data management, reference to Jill Dyche, Evan Levy's point of view in general be able to master data management can be divided into six levels. From low to high reflection of Master Data Management (MDM) different maturity. We take a brief look at the following six levels:
Level 0: no matter what the implementation of master data management (MDM)
in the case of Level 0, which means between the various enterprise applications no matter what the data sharing. No data definitions across the enterprise elements are present. For example, a company sells many products. Production and sales of these products are handled by multiple independent systems, each system independent data processing products and have their own separate list of products, product data is not shared between the various systems. In Level 0, each individual application is responsible for managing and maintaining their important data (for example product lists, customer information, etc.). This information is not shared between the various systems. These data are not communicated.
Level 1: Provides a list
, whether large or small company, list management is a way we often use. in the company. Maintains a list of logical or physical manner by hand. When individual isomers system and user needs some data, it is possible to obtain the list of. For the maintenance of this list. Contains data added, delete, update and conflict management, are handled by the staff of the various departments through a series of discussions and meetings. Business Rules (Business Rules) is used to reflect the value of consistency, when business rules change or a similar situation, so highly manual management processes easy error.
Because the list management is through manual management. Its quality depends on maintaining a list of who took part in the change management process. Once someone is absent, it will affect the maintenance of the list.
Level 2: the same Access (by way of an interface, direct interconnection between the respective host systems and master data)
the MDM and the MDM Level 1 Level 2 as compared to the primary data is introduced (own initiative) management. Through the establishment of data standards. Define and share access to specific data stored in a central repository (Central Repository) in. Is shared between the various systems using data provided rigorous support.
Central repository (Central Repository) will generally be referred to as "main data host (Master Data Host)". This knowledge base can be a database or an application system that supports access and share data through online.
Create, read, update and delete (CRUD) are typical programming terminology handle basic functions. Even in the MDM. CRUD processing also basic functions. Assuming that your database supports only CRUD processing does not mean that you implement MDM.
MDM Level 2 introduces "equal access" (peer-based access), means that an application can call there is a need to be used to update or refresh the data.
When CRUD been defined processing rule, MDM Level 2 or customer need "equivalent" application formatting requests (and data) to align and MDM repository.
MDM data repository provides centralized storage and supply (provisioning).
At this stage, rule management, data quality and change management must be custom-built as an additional function within the enterprise.
Level 3: centralized processing bus
and MDM Level 2 compared. MDM Level 3 to break the organizational boundaries of each individual application. The use of each system can accept a unified data standards to establish and maintain master data (master data stored on the host MDM Level 2 data is stored separately according to each system. No real integrated).
MDM is meant to focus on building a common, built based on the target platform. Most companies find that MDM are challenging their existing IT infrastructure: they have too many platform-independent processing master data. MDM Level 3 centralized data access control across different applications and systems data. This greatly reduces the complexity of the application data access greatly simplifies the management of data-oriented rules. MDM has so many other features and functions than a decentralized environment.
Business owners face the challenge of data consistency. Data exist in different places, is not the same between the meaning of the data represented are different rules for each data system.
Centralized MDM process - through a common platform as a bus (HUB) - illustrate a consensus to integrate data from multiple systems subject field. Means uses a centralized, standardized way to convert heterogeneous operating data. Regardless of what it was like in the source system, will be integrated. In MDM Level 3. Company subject area content is managed centrally. This means that applications, or use master data as consumers, have a common theme is that the data is image data content, breaking the organizational boundaries of each individual application. MDM Level 3 support distribution of the existence of the main Cenkaoshuoju.
Level 4: business rules and policy support
once the data together from multiple data sources. Subject field of view beyond the individual application and performance of an enterprise view, you will get a single version of the truth. When a single version of the facts have been able to provide it, will the reaction from business executives and operational staff often is: "prove it." MDM Level 4 to ensure that primary data reflects a company's business rules and processes, and to confirm its validity. MDM Level 4 supported by the rule into the main data, and integrity checking bus MDM and other external systems. Because most companies in contrast to the more complex, affecting business operations and data access rules and policies (rules and policies) is also relatively complex.
Assumes no matter what a single system can contain and manage various types of rules associated with the master Cenkaoshuoju is impractical.
Therefore, assuming a real MDM bus going to provide enterprise-wide within the accuracy of the data. Workflow and process integration support is indispensable.
Level 5: enterprise data set
in the MDM Level 5. And related main data bus is integrated into a separate application. No clear separation between the primary data and application data.
They are one. When the specific information master data record has been altered. All data elements related applications will be updated. This means that all consumer applications and source systems access the same data instances.
This essentially is a closed loop MDM: all applications through a unified master data management integrated. At this level, all look the same in the fact that the system version number. Operating system and application MDM content are synchronized. So when the change occurs. Operation of the application system will be updated. Those familiar with the MDM architectural styles. Persistent bus architecture, when a bus to update all application operating system will reflect such changes, changes in direct view of the operation. Registered environments, when the data update, the update bus connection system related application transactions through Web services. Thus, MDM Level 5 provides an integrated. Synchronization architecture, when a privileged system update a data value within all of the company's system will reflect this change. Other radio systems do not correspond to the value after completion of the update data value updating system: MDM such updates will become transparent.
MDM Level 4 from the MDM MDM Level 5 functionality is not meant in a particular design or application is coded. This also means that the main data dissemination and supply do not need a dedicated source system development or support.
All applications clearly know they do not own or control the primary data. They only use the data to support their own functions and processes. Because MDM bus and support of IT infrastructure. All applications can access the main Shenkaoshuoju. After the completion of a company MDM Level 5 will make all their applications together - both contain operations also include analysis - all master data access is transparent. An example, when a client update her status - not to change the system of registered - data changes will be broadcast to the entire application platform (and therefore into line). MDM Level 5 is the concept of data implemented as a service. MDM Level 5 to ensure a consistent corporate image master data subject areas. The definition of "customer" and other applications accepting customer master data business rules change is actually the same thing. MDM Level 5 removed the last obstacle to a main data: the uniform application of data definition, authorize the use and dissemination of change.