MDM - therapy, a unique technique. What is master data and why is it needed What is mdm

We are constantly faced with the fact that in the field of MDM (Master Data Management) there is a catastrophic lack of understandable introductory materials that allow you to quickly understand what it is, why and why it is important. Let's try to correct it to the best of our ability and explain it in the language of business.

There is still a serious lack of certainty in this area, and even Wikipedia, oddly enough, is not quite sure which is which. Therefore, we will explain in our own words and “on the fingers”, with examples.

What is what

So, all the data that modern Information Systems, can be divided into reference information, master data and transactional data.

Reference information (NSI) or directories and classifiers - allow us to structure the world around us in order to analyze it. As a rule, directories and classifiers are built in the form of lists and trees. For example, we distribute all products into product groups in order to make them easier to manage. In world practice, this part is classified as Reference Data, with the corresponding class of applications and processes - Reference Data Management.

Master data usually reflects real world objects and their main properties, for example: customers, goods, people, offices, vehicles. Their key difference from the NSI is that the NSI are attributes, properties, lists, and other classification planes, but the objects described by the NSI usually do not exist in real life. So, a car model is an element of master data, but a specific car with its properties is a master data element.

Transactional data - reflects our actions with world objects (read - master data objects), events and interactions. At time T, we shipped goods B to client A in quantity X and at price Y. And then at time T1 we received payment from client A in the amount of Z, these records will be transaction data.

If we look at these three groups, then we will see some kind of hierarchy, reflected in the figure. NSI is used to structure master data and transactional data. The master data defines the structure of the transactional data. And only transactional data is the end result of the chain.

Thus, NSIs structure both master data and directly transactional data. Master data structures transactional data. As a result, our analytical capabilities in relation to transactional data directly depend on how suitable for our purposes the “framework” of reference data and master data we managed to build.

Naturally, each type of data has its own characteristics, which we must consider in detail.

NSI features

The key feature of NSI is their relative immutability, i.e. NSI are built initially on the basis of business goals or from a stable objective reality of the world (for example, a reference organizational forms or car models). Changes in the NSI usually occur in accordance with a certain procedure, the maintenance of the NSI is entrusted to a specific unit. Any change must necessarily go through a certain approval process that guarantees the integrity of the NSI.

The sources of changes in NSI are changes in the surrounding reality, for example, sometimes new countries or currencies appear. Or, if we are talking about directories built around business goals, changes associated with changes in business goals, accounting policies, distribution of responsibilities by product groups, etc.

In fact, NSIs form the basic planes of analytics, which is why the composition and structure of NSIs can be quite complex, including some directories that can be used in others as attributes, forming complex structures that implement many analytical planes. For example, for the purposes of marketing, production, inventory management and financial accounting, completely different groupings of commodity items and different sets of characteristics can be used.

With sufficient centralization of the management of reference data, the directory system is usually stable and not subject to “noise”. However, in companies with poorly integrated applications, we see the same trouble: NSIs are often built separately within each application based on the “local” business goals provided by this application. As a result, “parallel” sets of NSIs are generated that are not reduced to single system, which greatly complicates the formation of analytical arrays.

Ideally, NSI management should be centralized. Thus, as part of the IT solution, a system appears that provides the technical and organizational basis for managing the NSI, in relation to which all other applications are clients of one-way synchronization of the NSI - from RDM to applications.

Master Data Features

Master data is more "moving": new customers, new products, new people - all this movement directly comes from the life of the company.

The most important feature of master data is that it is here that the company accumulates knowledge about the subject of its work. All information that appears over time about a particular client should be economically formed, structured and updated, including the entire history of changes. The same goes for any master data. Equally important, master data also defines relationships between different entities. What is a branch of what, who is the supplier of what commodity groups which vehicles belong to which branches, etc.

However, the degree of control over master data changes is significantly lower, because records and their updates are generated in various departments, at different times, made by different people, and often also in different systems that make up a complex IT landscape. modern company. As a result, each system often stores only some part of the information about the same entity, each system assigns its own identifier to it. As a result, the formation of a complex analytical picture is complicated, and in especially neglected cases it becomes completely impossible.

Because of this, the master data is highly susceptible to "noise" as a result of errors and the creation of duplicate records. As a rule, this is fought with organizational measures, rules like “do not start heading if it already exists” or “before getting a client, search for the current client base”. But when the dispersion of applied systems is superimposed on the variety of spellings and descriptions, and this is all within the limits of human attention and diligence, then no orgmers help.

The result of “noise” is the loss of master data quality, which entails the destruction of analytics, because what kind of analytics can there be if transactions regarding one real client are tied to three different client records made at different times in different systems by different people?

Large companies with a long history and complex IT infrastructure can easily have 15..20 million client records about legal entities in their systems, while there are less than 5 million legal entities in Russia. And this is quite a life case. There is no need to talk about high-quality client analytics here.

Another example. Product catalogs are very prone to noise. Due to the lack of a single unique identifier and the variety of spellings, the operator is often unable to correlate new products with those already accounted for in the system. As a result, an item that is gathering dust in the warehouse will be purchased again only because one product card corresponds to the warehouse balance, and another card in the project specifications, although physically it is the same product.

It should be especially noted that the majority of applied systems do not contain any effective mechanisms for managing the quality of this data, limiting themselves to a trivial substring search, relying on the conscientiousness of the operator and his knowledge of the application area. Therefore, the problem of the quality of the master data usually arises when the introduced distortions and the inadequacy of the analytics reach impressive proportions and are visible, as they say, to the naked eye.

Features of transactional data

Transactional data is the most dynamic of all the listed types and, in fact, is generated transparently for most operators in the course of understandable actions such as “ship the goods”, “download a bank statement”. As a rule, each element of transactional data contains a number of links to master data records of various types, plus a date and a number of numbers characterizing the transaction.

For example, the minimum element of transactional data generated by a shipment would consist of a customer reference, item reference, quantity, and price. In reality, transactional data has a slightly more complex structure, for example, there is an invoice and the corresponding data element indicating the counterparty and date, and there are its lines, each of which contains a commodity item, quantity and price. Nevertheless, for the purposes of analysis, the number of transactional records will be equal to the number of lines in the invoice, and the record corresponding to the invoice itself does not cease to be transactional data.

It should be noted that all kinds of accounting registers containing, for example, current balances, in fact, are not transactional data, but a kind of analytical generalization. It's just a generalization technical means kept up-to-date and aimed at optimizing performance. The important thing is that it can be recalculated at any time from transactional data, and this is its fundamental difference - it is secondary.

It is important that transactional data usually affects the interests of external counterparties, and therefore there are no particular problems with controlling their quality: for example, if the operator doubles the shipment, this will affect the balance with the counterparty, lead to discrepancies, reconciliation and the error will be corrected. Thus, mutual control between interacting counterparties, coupled with analytical tools and established business practices, provide relatively high quality transactional data

Why does master data require a special approach?

Having defined the concepts and considered the features of data types, we came close to the question: why does master data management stand out as a separate function in modern IT architectures? There are several reasons for this:

1. The narrow functional orientation of applications often leads to the fact that each application operates with its own set of attributes. The call center does not call the office address, the delivery does not bring goods to the email. In other words, a complete set of information, the so-called. a "master record" for each application is redundant. In addition, in large organizations, different application systems are built for different business goals and often operate even with different NSIs. Developers and operators of functional applications simply do not need “foreign” master data and master data within their goals, and all these problems eventually fall on high-level business intelligence systems in which master data and master data are combined with one or another success . And about the problems that arise at this point, citizens who are forced to solve them can talk a lot, colorfully and pretentiously, but as a rule, not very literary.
2. Specificity of algorithms for working with master data. The paradox is that effective management master data requires a whole range of approaches that, within the framework of applied systems, are usually not spoiled by the attention of developers. So, in order to avoid duplication of records, very flexible and efficient search and comparison mechanisms, complex normalization-validation-matching algorithms are needed. At the same time, from the point of view of these algorithms, the control different types master data is almost the same. In general, it doesn't matter if it's a commodity tree, a list of vehicles, customer profiles or employee personal cards. The approach does not change, it is simple: clean up errors and typos, catch and stop duplicates, supplement and update as much as possible, save the entire history of changes, highlight “doubtful” cases for processing by analysts (data stewards).

Thus, a separate element appears in the IT landscape - as a separate function, an IT service that "conducts" the entire set of master data of the company, providing all functional applications with a single, holistic, relevant and complete master data. In most cases, interaction between application systems and MDM occurs through a data bus, messages, or a SOAP/REST API.

The paradox is that any company trying to build high-level analytics automatically comes to the implicit generation of master data, even if it uses ETL procedures to “reload” data from several accounting systems into one analytical system, because high-quality analytics is fundamentally impossible without quality master data. The only question is how advanced matching algorithms use the ETL process, what quality the master data is obtained in the target analytical system.

Thus, due to the specifics of master data, the impossibility of really qualitatively solving the problem of managing them within a separate application system, multiplied by a large number of application systems, generates a separate IT domain - master data management.

What is MDM and what are they?

So, master data management or MDM crystallizes as a separate area of ​​knowledge and class of products. However, in the current English terminology, this is a general class of products and solutions, which includes, in particular, a number of applied solutions and related business processes:

• , in general, this is the management of the NSI. It would seem that this is not master data, this is a different domain. But the difference between NSI and master data lies only in centralization, and we can use the same tools that we use to manage master data for NSI with the only difference: all systems in relation to RDM work in read-only mode, and all changes necessarily go through the relevant business processes.
• , customer data integration. This term covers systems narrowly tailored to work with the client's master profile. It is understood that these systems aggregate the maximum amount of information about the client and provide all other systems with the services of searching, creating and updating client records, as well as bidirectional synchronization.
• PIM, Product Information Management, product information management system. A specialized view of MDM focused on information about products, their properties and attributes. For example, such a system can be an "authoritative source" of information about products for an online storefront, a printed catalog, an ERP system, and a call center at the same time, ensuring the integrity of the presentation and the unity of information.

There is no doubt that with the well-known love of the English-speaking world for structuring reality, specialization and acronyms, you can unearth a dozen more narrow application systems that essentially implement the functionality of master data management in one specific narrow area.

The emerging market for MDM solutions today is represented by a large number of companies offering solutions of very different quality. All vendors of the "first echelon" indicated the presence in their portfolio of MDM solutions either separately or as part of their systems. However, as it was said, most of them are focused on other functionality, so the quality of the implementation of specific MDM functionality leaves much to be desired. At the same time, many smaller but more MDM-focused companies offer solutions that are significantly more functional.

Do I need MDM?

So, when should you definitely consider implementing MDM into your IT architecture? As a first approximation, the criteria are as follows:

1. You have a lot of master data. Tens and hundreds of thousands, and even millions of records in the area that we designated as master data. Customers and products first. No matter how good your systems are, such volumes of data inevitably get cluttered. And most likely it will not be possible to solve this problem with regular means of your systems. Our experience shows that even with the declared “developed mechanisms for deduplication and data quality assurance”, the number of duplicates amounts to tens of percent of the number of records.
2. You have multiple functional systems with an overlapping set of master data. Yes, there are options when the architecture is initially properly integrated, the reference data are maintained uniformly and the data of different systems are correctly synchronized without any intermediary, and for each type of master data, a primary system is defined with which all the others are synchronized. However, this is more the exception than the rule. More often, it's the other way around. And bringing this zoo to uniformity with the help of an MDM system will be an order of magnitude easier than by integrating without a dedicated MDM component.
3. Synchronizing data and bringing them together into a single picture requires a lot of effort, and the resulting analytical array is questionable. Many companies use a strategy that can be briefly described as follows: “let it live as it lives in each system, and at the BI level we will reduce it anyway” and use complex, cumbersome and not very effective ETL procedures in order to form BI storage. Unfortunately, this is a palliative solution, clumsy and very resource-intensive, forcing you to “twist” the system on a daily basis, store huge arrays of “normalized” data, in fact, doing a huge pile of work to compensate for the lack of MDM.

The last thing I would like to note in this section is that there is no better time to implement MDM than the moment of introducing new functional IT systems or migrating from one system to another. After all, the implementation process involves "cleaning" the accumulated data and linking the systems with each other. Combining these things, we kill two birds with one stone: we improve the quality of data in new system and at the same time we maintain continuity with the old one, because the MDM system just sews them together.

Where is MDM headed?

What should be expected from this direction? What is the vector of development? We believe that the following trends will be relevant:

1. Development of "highly specialized" MDM products. The RDM, CDI and PIM classes are highlighted for a reason, these are the most relevant and understandable MDM tasks, the solution of which has the maximum effect for the business. We recommend that you be careful, because in the current state of the market, “specialized” means marketing positioning rather than additional functionality. Not the fact that "special MDM" from one vendor will solve the problem better than MDM general purpose from another.
2. Improvement of MDM functionality in application systems. This happens at least through the purchase of smaller, but more advanced companies in this area by vendors of the "first echelon". First of all, this will affect companies that are trying to form a completely mono-vendor IT landscape.
3. Mini-solutions and integration through standard APIs. Now most MDM solutions are heavy and expensive corporate systems, effective only on the scale. They require complex customization, trained professionals, thoughtful integration. And although the effect of their introduction is huge, the price of the entrance ticket is also very high. However, like many technologies in IT, they will “go down”, over time they will become more and more accessible to smaller and smaller companies.
4. MDMasService. Obviously, there are no barriers to providing MDM as a service on par with other applications. The open interfaces of SaaS applications facilitate their integration, so it is quite expected to use many SaaS applications integrated with each other, among which there will be SaaS MDM.

Conclusion

We hope that this material has given an idea of ​​what master data is, what systems for managing it are, and why they are needed.

Definitely, for fairly large organizations with a complex IT landscape, MDM is an absolutely necessary element that allows you to “glue” together and make huge, but highly fragmented data as useful as possible, simplify the architecture, radically reduce the complexity of generating business intelligence and at the same time significantly improve its quality.

it is verified and effective method correction of the protective (adaptive) system at the level of the control centers of the brain. Normalization of the state of the adaptive system is accompanied by a restructuring of the activity of the whole organism, in particular, the quality of the work of organs and tissues that have deviations from the norm or affected by a pathological process improves. As a result of exposure to a weak electrical signal with certain parameters on brain structures, various parts of the neuroendocrine system are selectively activated, which, as it were, forces the body to use internal reserves, mobilizes the immune system.

The method was discovered by a group of Russian scientists in the 80s of the XX century, but refined, tested and introduced into clinical practice in Europe. The technique has received positive feedback from leading medical centers, both in Russia and abroad. The method has been used to treat more than 200 thousand patients, including those in pediatric practice. When observing patients for more than 20 years, no negative consequences were found. To date, MDM-therapy rooms according to the method of Professor V. Pavlov are successfully operating in Austria, Germany, Greece, the Czech Republic and Switzerland. In Moscow, the first MDM-therapy room was opened in the Semeynaya clinic ( medical Center"Serpukhovskaya"). Now patients who want to use this highly effective non-drug method have the opportunity to undergo treatment without traveling abroad.

How is the procedure:

Sessions of mesodiencephalic modulation are carried out using a computer complex MDM-2000/1, produced by ZAT a.d., Czech Republic. Apparatus MDM-2000/1 registered in the Russian Federation and entered in the State Register of Products medical purpose and medical equipment (Registration certificate FS No. 2004/1128 valid until 01.22.2011), and also has a sanitary and epidemiological conclusion for use (License No. 77.99.28.944.D.007272.12.04 dated 12.28.2004).

The procedure for mesodiencephalic modulation is simple and painless: a pair of fronto-occipital electrodes is applied to the patient's head, through which specially selected therapeutic current pulses are applied, which change in time according to a predetermined program. The parameters of electrical signals are programmed so that the negative impact on the body is completely excluded.

The procedure lasts 30 minutes, the standard treatment course consists of 13 procedures (daily for 10 days)

A preliminary consultation and examination by a specialist in MDM therapy is necessary. In our clinic, all examinations and the procedure itself are carried out by certified specialists who have extensive experience and have specialized abroad.

Indications for MDM-therapy

• Cardiovascular diseases: hypertension stage I and II; coronary heart disease: angina pectoris FC I-III, rehabilitation of patients after acute myocardial infarction
• Endocrine diseases: diabetes mellitus and complications of diabetes mellitus (ulcers, gangrene, retinopathy, neuropathy); insulin resistance, dysfunction of the thyroid and parathyroid glands
• Somatic diseases: tonsillitis, bronchial asthma, Chronical bronchitis, COPD, peptic ulcer of the stomach and duodenum; gastritis with secretory insufficiency and hyperacid state; biliary dyskinesia; bronchial asthma; rheumatoid arthritis
• Neurological diseases: cardiopsychoneurosis; dyscirculatory and traumatic encephalopathy; hypothalamic (diencephalic) syndromes; pain syndromes in diseases of the peripheral nervous system
• Surgical diseases: preparation for operations, rehabilitation in the postoperative period; burn disease and frostbite; post-traumatic conditions, non-healing postoperative wounds,
• Peripheral vascular disease: endoarteritis and atherosclerotic occlusion of peripheral arteries; venous and lymphatic insufficiency, including complicated by trophic ulcers
• Gynecological diseases: violation of menstrual function: premenstrual and menopausal syndromes; chronic salpingoophoritis, neuroendocrine disorders complicated by infertility or uterine myoma (no more than 8 weeks), polycystic ovary syndrome
• Diseases of the uroandrological sphere: impotence; chronic prostatitis; symptom of chronic pelvic pain, infertility
• Dermatological diseases: neurodermatitis; itchy dermatoses; non-bacterial forms of eczema
• In psychiatry: reactive states; Agripnic Syndrome; neuroses; asthenic and depressive conditions; withdrawal syndrome
• For preventive purposes: in stressful conditions and prolonged emotional stress; with mental and physical overwork; with chronic fatigue syndrome
• In pediatric practice: It is possible to use electrical stimulation, starting from the age of 5, for all the indications listed in other sections; as well as:
  • enuresis;
  • logoneuroses;
  • night terrors and other neurotic conditions;
  • adaptation to school and preschool institutions;
  • tonsillitis;
  • sinusitis;
  • increasing the resistance of frequently ill children during periods of seasonal outbreaks of acute respiratory viral infections

Contraindications to MDM-therapy

• the presence of metal foreign bodies in the tissues of the head;
• intracranial hemorrhage, risk of intracranial bleeding;
• schizophrenia;
• epilepsy;
• acute psychosis with psychomotor agitation;
• skin diseases at the site of electrodes on the forehead and back of the head.

Learn more about the Mesodiencephalic Modulation (MDM) method

Mesodiencephalic modulation or MDM therapy refers to physiotherapy methods, but significantly surpasses all known methods in terms of therapeutic effect. It is based on weak, but complex in structure, electrical signals that selectively affect the structures of the brain, activating the work of the control centers of the protective system. Mesodiencephalic modulation method is based on previous research in the field of therapeutic transcranial (through the integument of the skull) electrical stimulation of brain structures. For the first time, transcranial therapy was carried out in patients in 1902. Since then, various modifications of devices have been used in practical medicine, in which a variety of frequency and other characteristics of electrical signals were used. The most famous in Russia are electrosleep, electronarcosis and devices for TES-therapy. For more than 100 years of clinical use, a huge amount of material has been accumulated, which makes it possible, first of all, to determine the scope of the parameters of the electric current, not harmful to the human body, but improving the course of many diseases.

Unlike their predecessors mesodiencephalic modulation method, focusing the impact on the subcortical-stem parts of the brain (mesodiencephalic zone), he managed to achieve not only an analgesic effect, but also achieved selective activation of the main regulatory systems - the hypothalamic-pituitary, adrenal, opioid, etc. Accordingly, the frequency characteristics, pulse shapes, method of superposition, the polarity of the electrodes and other indicators differ significantly from the previous methods.

Like a new direction mesodiencephalic modulation appeared in the mid-1980s on the basis of the Center for Emergency Cardiology of the Research Institute for Emergency Medicine named after A.I. N.V. Sklifosovsky. Testing a device for electric pain relief, developed at the Institute of Physiology. I.P. Pavlov Academy of Sciences, a group of scientists led by V.A. Pavlov found that the analgesic effect during electrical stimulation is not the main one. It was found that exposure to the mesodiencephalic zone with a weak electrical signal with certain parameters leads to the release of biologically active substances into the blood - opioid peptides (in particular, beta-endorphin - the "hormone of joy"), pituitary hormones and insulin, which reduce the severity of stress reactions and increase the adaptive properties of the body. That is, the mechanism of action is as follows: as a result of a stressful situation for the body (trauma, infection, allergy, etc.), the connection between the central and peripheral neurohumoral regulation of organs is broken, which in turn leads to the activation of the damaged organ's own ectopic rhythm and its output out of control of the central nervous system. Mesodiencephalic modulation makes it possible to achieve selective activation of the regulatory structures of the brain, there is a release of hormones that normalize the activity of organs and contribute to the restoration of full-fledged functional activity.

Further development of the parameters of electrical signals, which were carried out under the guidance of Professor V.A. Pavlov on the basis of European scientific centers, made it possible to achieve a significant increase in this positive effect. The result of almost 30 years of scientific work was the computer complex MDM 2000/1. Treatment programs developed by specialists various kinds pathologies, make it possible to obtain pronounced clinical and biological effects in patients:

1. Antistress. It allows not only to cope with stress in an extreme situation, but also to prevent the exacerbation of a chronic process accompanied by depressive disorders. In addition, the anti-stress effect actually reduces the number of complications in the treatment of various diseases and ensures their easier course.
2. Reparative. Acceleration of reparation by 2 - 2.5 times in comparison with the most modern medicinal and physiotherapeutic methods. For example, with a stomach or duodenal ulcer (including a "kissing" ulcer), myocardial infarction, burns, fractures, trophic ulcers, etc.
3. Pain reliever and anti-inflammatory. Powerful analgesic effect allows you to cope with most of the existing species pain (migraine, radiculitis, radicular syndrome in osteochondrosis of the spine, pain in arthritis, toothache, etc.). This not only reduces the intensity of pain, but also removes the inflammatory process that supports this pain.
4. Prophylactic. Prevention of exacerbations in chronic diseases: often there is a stable remission (no exacerbations) even in such serious diseases as bronchial asthma, hypertension, diabetes mellitus, etc. At the same time, the dosages of supporting medicines(MDM-therapy enhances the action of most known medicines), side effects and allergic complications are significantly reduced. In case of intolerance medicines, as well as in cases of chronic renal or hepatic insufficiency, MDM-therapy can be used as the only method of treatment.
5. Polytherapeutic. If there are several chronic diseases there is a simultaneous therapeutic effect on the entire list, which is especially important in the field of gerontology.

Book an appointment with a physiotherapist

Be sure to consult a qualified specialist at the Family Clinic. This service is not available in all branches, check with administrators for more details.

Did you know? In our country appeared latest method treatment of diabetes mellitus, hard-healing ulcers, autoimmune and chronic disorders - MDM-therapy! Specialists of the clinic "Happy Family" were among the first to successfully test the latest program.

Mesodiencephalic modulation or MDM-therapy is aimed at curing modern "diseases of civilization". Our way of life is constantly changing environment is getting worse, nutrition is becoming more and more inadequate, and work is increasingly stressful. Against this background, a person develops metabolic, endocrine, immune, immunodeficiency, cardiovascular disorders, pathologies of the gastrointestinal tract, depression and phobias.

Mesodiencephalic modulation has been successfully practiced in European clinics for over 25 years. Experts identify several of its main advantages:

• Ease of carrying out
• Safety
• Clinically proven efficacy.

Special sensors are placed on the patient's head that send weak electrical signals to the hypothalamus, the pituitary region of the brain. Electromagnetic impulses seem to "restart" its functions - neuroendocrine and immune. It is these systems that help the body adapt to changes in the environment.

The treatment course prevents the development of serious complications, the flow of diseases into a chronic form and, in general, has a positive effect on the quality of life of the subject. Disease for short term enters the stage of remission - its symptoms and acute attacks subside.

Over the past years, more than 250,000 patients worldwide, including children, have received MDM treatment. Side effects were not recorded, which is a rarity in medical practice.

How are MDM sessions going?

One procedure does not last long - about half an hour. Depending on the severity of the disease, 6 to 10 sessions may be needed. The signals entering the hypothalamus are of low intensity, so patients do not experience any discomfort. All sensations depend on the individual sensitivity of the skin, they can be compared with a physiotherapeutic effect.

Electrical impulses seem to allow you to negotiate with the brain in its language - a signal is given about the need for adaptation. In response, the hypothalamus and pituitary stimulate the glands and endocrine cells, and they begin to produce biologically active substances in large quantities. As a result, the blood is enriched with the necessary neurotransmitters and hormones. The subtlest restructuring of the body begins - cascade reducing reactions lead to the elimination of problem foci and impaired functions. Thus, opioid peptides are released into the blood, which have a pronounced analgesic and regenerative effect on tissues.

The younger the patient, the sooner and more significantly the “reboot” and adjustment of system functions will occur. People at a more mature age will need more procedures to achieve such a result. But the possibilities for self-healing are present in everyone, and they are the most individual and safe "medicine" on earth.

MDM practice has shown its more than 25-year history that side effects do not appear even in the long term. The procedure is very easy and painless, clients often fall asleep during it. In exceptional cases, clients notice an increase in the symptoms of diseases. This is a normal reaction of the body to restructuring and adaptation. Subsequent sessions relieve such exacerbations, so the course of treatment does not stop.

MDM-therapy is a technique with minimal contraindications.

Any method of therapy has contraindications, therefore, the use of mesodiencephalic modulation has limitations. Although they are very rare, you need to know about them:

• The presence of foreign bodies made of metal in the head tissues.
• Episyndrome or epilepsy.
• Schizophrenia.
• Psychomotor agitation.
• Violation of the integrity of the epidermis at the location of the electrodes (forehead, back of the head). The restriction is imposed during the period of the acute form of the disease (if there are damage or inflammation on the epidermis). In a state of remission, the contraindication is removed.

MDM-treatment makes it possible to reduce the drug load. With its use, a sick person needs less medicine to recover. This is a very big advantage, because a patient with diabetes mellitus usually combines several disorders at once. One functional failure leads to another. Such people have to use significant amount pills that may cause side effects. MDM sessions allow you to break the vicious circle. Physiotherapy with impulses improves the condition of all tissues, normalizes homeostasis, and is successful in the treatment of infectious, inflammatory and immune disorders.

MDM-therapy is certified by the Ministry of Health of the Russian Federation. During the sessions, the MDM-2000/1 device is used, which is registered and entered in the State Register of the Russian Federation as a “medical device and medical equipment” (Registration certificate No. FSS 2011/09144). The device has all the necessary sanitary and epidemiological conclusions for use.

What are the data

Before moving directly to master data management systems, let's define what kind of data there is.

Below are 5 key types:

1. Metadata (Metadata);
2. Reference data;
3. Master data (Master data);
4. Transactional data;
5. Historical data.

metadata is data about data. They are needed to understand and determine what data the enterprise operates with. Metadata defines structures, data types, access to them, and so on. Exist various schemes to describe the metadata. For example, an XSD schema can be used to describe the structure of an XML document, and a WSDL schema can be used to describe a web service.

Reference data is relatively infrequently changing data that determines the values ​​of specific entities used in the performance of operations throughout the enterprise. Such entities most often include: currencies, countries, units of measure, types of contracts/accounts, etc.

master data is the underlying data that defines the business entities that an enterprise deals with. Such business entities usually include (depending on the subject industry focus of the enterprise) customers, suppliers, products, services, contracts, invoices, patients, citizens, etc. In addition to information directly about a particular master entity, the master data includes relationships between these entities and hierarchies. For example, in terms of finding additional sales opportunities, it can be very important to identify explicit and implicit relationships between individuals. Master data is distributed throughout the enterprise and participates in all business processes. Typically, master data is perceived as a key intangible asset of an enterprise, because the effectiveness of its work depends on their quality and completeness. In Russia, the term “reference information” is often used instead of the term “master data”.

Transactional data- this is the data that was formed as a result of the performance of any business transactions by the enterprise. For example, for commercial enterprise: sales of products and services, purchases, receipts / write-offs Money, warehouse receipts, etc. Typically, such data is based in an enterprise resource planning (ERP) system or other industry-specific systems. Naturally, transactional systems make extensive use of master data when performing transactions.

Historical data is data that includes historical transactional and master data. Most often, such data is accumulated in ODS and DWH systems and serves to solve various analytical problems and support management decision-making.

Master data management systems

Before moving on to the master data management system, let's define what master data management is in general.

Master Data Management (MDM) is a discipline that works with master data in order to create a “golden record”, that is, a holistic and comprehensive view of the master entity and relationships, a master data standard that is used by the entire enterprise , and sometimes between enterprises to facilitate the exchange of information.

Specialized master data management systems (MDM systems) automate all aspects of this process and are the "authoritative" source of enterprise-wide master data. Often, MDM systems manage reference data as well.

The situation when the MDM system is the only source of master data, all changes are made to the MDM system and only then transferred to the consumer systems, is called the "record system". This is the ideal situation for master data management. However, in real life, things are not so simple: an MDM system will not always be a “records system”. Due to the peculiarities of the business processes of a particular enterprise, the technical complexities of specific systems, etc., it is necessary to create “copies” of master records. The system that contains a copy of the master data is called a "reference system". In order not to lose control, the "reference system" must be managed and synchronized with the "record system".

Three dimensions of MDM systems

Consider an MDM system in three dimensions:

Typically, MDM systems are not implemented "on the spur of the moment", because their implementation is a complex process of successive enterprise-wide transformations, from maintaining disparate data to creating a holistic, comprehensive view of the master entity. Therefore, the implementation of MDM systems is carried out sequentially with a gradual approach to the target result in the three indicated dimensions.

Let's take a closer look at these measurements.

Domains

In the context of master data management, a domain refers to a specific area of ​​the master data. The most common master data domains are the customer domain and the product domain. Western literature has developed established terms for managing master data within these domains: Customer Data Integration (CDI) for the customer domain and Product Information Management (PIM) for the product domain.

CDI traditionally includes not only customers, but also organizations or individuals, which may be called differently depending on the industry of the enterprise: customers, suppliers, banks, funds, patients, citizens, etc.

PIM traditionally includes: products, goods, materials, services, works, etc.
There are many similarities in the approaches to managing CDI and PIM master data, but there are also many differences. For example, when deduplicating client entities, in most cases, a simple parsing of entity attributes and their comparison based on probabilistic algorithms is performed, while in the product domain, a semantic/ontological analysis of attributes is performed with the inclusion of self-learning mechanisms. In addition, depending on the selected category, entities in the product domain can have very different attributes (for example, laptops have their own set of attributes, and washing machines have their own). All these features of various domains must be supported by MDM systems.

Recently, there has been a tendency to create multi-domain MDM systems with the ability to flexibly configure the metadata structure. Such flexibility gives the enterprise the opportunity to describe the master data specifically for itself, taking into account all the features and nuances, but it also requires a lot of time and knowledge to correctly design and configure such a system. There are also systems on the market with a “hard” structure of master entities that already have correctly configured mechanisms, but the use of such a system is possible only for those enterprises that can adapt to it. Typically, such systems are well suited for solving the problem of managing master data within a narrow industry. In my opinion, the most promising are systems with a flexible metadata model, but at the same time having pre-configured models for enterprises in different industries that can be quickly reconfigured.

Usage Methods

Methods of using MDM (Method of use) determine what the MDM system will be used for in the enterprise. In other words, who will be the consumer of the master data (of course, there may be several of them).

There are three main methods of use:

1. Analytical
2. Operational
3. Collective (Collaborative)

The analytical use case supports business processes and applications that use master data primarily to analyze business performance, provide the necessary reports, and perform analytical functions. Often this happens through the interaction of MDM with BI tools and products. Typically, an analytical MDM system works with data in read-only mode, it does not change the data in source systems, but cleans and enriches it.

The operational method of use allows you to collect, modify and use master data in the process of performing business transactions (operations) and serves to maintain the semantic consistency of master data within these operations within all operating applications. In fact, in this case, MDM functions as an OLTP system that processes requests from other operational applications or users. Working in this mode often requires building a single integration landscape using the principles of service-oriented architecture (SOA) and the use of enterprise service bus (ESB) tools. Ideally, if such tools are either included directly in the MDM system, or are its continuation (there are vendors that have in their lineup both MDM and ESB solutions that are deeply integrated with each other).

The collective use method allows you to create master entities in cases where collective interaction is required between different groups of users in the process of this creation. Such reconciliation usually has complex "branching" business processes consisting of various automatic and manual tasks. Manual tasks are performed by various data scientists (data stewards) in the order defined by the business process. Most often, the collective method of use is used in the product domain. For example, when creating a new product, when there are several responsible for entering different data, many self made and final agreement. It is important that the MDM system allows you to configure arbitrary business processes to quickly support the business processes of a particular enterprise.

Embedding styles

There are usually three main implementation styles:

1. Register (registry);
2. Coexistence;
3. Transactional.

The registry style of implementation involves the creation of a master data source as a "link system" to downstream data sources. Registry MDM contains only the key attributes needed to identify and match entities. Registry MDM operates in read-only mode, data is entered on source systems and passed to MDM to resolve entities. Also, links to sources of non-key data can be stored in the registry MDM, but these data themselves are usually not transferred to MDM. The Registry style of deployment is typically used when choosing an operational method for using MDM (see above).

The coexisting style of implementation assumes the presence of distributed data entry in several sources (business applications and MDM system). MDM system in this case may be a "recording system" for only part of the attributes. Nevertheless, a full-fledged master entity is formed in the MDM system, the changes of which are broadcast to other systems (perhaps not all of them). The coexisting embedding style is quite simple and is often applied as a first step to the next one, the transactional style. does not require deep processing of systems interacting with the MDM system.

The transactional style of implementation involves the creation of a full-fledged "record system" in which all data on master entities is stored. The MDM system in this case is the "single source of truth" for all consumer systems. All data creation and processing operations are performed at the MDM system level. Data entry at the level of consumer systems is prohibited. This approach is usually quite difficult to implement, because requires significant change business processes and subscriber systems.

Conclusion

In practice, the choice of one or another strategy for implementing MDM is determined by many factors: the goals of the enterprise in the field of master data management, the degree of maturity of the enterprise, the degree of readiness of the IT infrastructure, the availability of investments for project implementation, and many other parameters. To determine the implementation strategy, it is necessary to conduct a thorough analysis of all these factors and draw up a detailed feasibility study of the project and a detailed schedule indicating the phases of the project development. But this is another broad topic that requires separate consideration.

One thing is for sure, that the implementation of an MDM system must be approached very carefully and progressively. Most MDM implementation projects fail precisely because of the underestimation of the complexity and volume of changes that one has to face in MDM projects.