
Master data management in an iterative approach
Author(s) -
S.V. Kuznetsov,
D.V. Koznov
Publication year - 2021
Publication title -
ontologiâ proektirovaniâ
Language(s) - English
Resource type - Journals
eISSN - 2313-1039
pISSN - 2223-9537
DOI - 10.18287/2223-9537-2021-11-2-170-184
Subject(s) - software deployment , master data , computer science , business process , process management , oracle , business rule , consolidation (business) , ibm , business model , business intelligence , software engineering , knowledge management , engineering , database , operations management , business , work in process , materials science , accounting , marketing , nanotechnology
Master Data Management (MDM) is a young area of business informatics that concerns consolidation and centralized control of highly important business data distributed over different information systems. Leading IT companies such as IBM, Oracle, Informatica and others offer a wide range of ready-made products for master data management (MDM products). MDM product deployment involves many technical and organizational complications: it is necessary to adapt these products for the specifics of the business, modify business processes, create new data policies, solve se-curity questions, etc. A popular approach to this task is the iterative strategy of MDM deployment, which supposes a step-by-step implementation of master data management based on the real needs of the business organization. In this paper, the notion of an MDM solution is introduced, which is the result of the deployment of MDM in an organization. It includes a specifically adapted MDM product, new regulations for working with data, trained employees, and an up-and-running process of master data management. The main result of the paper is a functional model of master data management intended for the early stages of the development of an MDM solution within the iterative deployment strategy. The purpose of this model is the representation of real business needs in terms of MDM. It is important to un-derstand which MDM components should be implemented first. The paper describes a detailed description of the mod-el components, as well as a portfolio of six real MDM projects analyzed from the viewpoint of the proposed model.