How to transplant database design to master Data management system

For many years, most companies have advocated a repository of information such as customer information, product lists, sales records, and so on. The benefits of putting this information in a central location are obvious, and it will be good for all parts of the company that support it, from top management to grass-roots staff, with countless benefits.

Now, some companies have begun to study the next phase of the evolution of these central benchmarking systems. This article will explore the reasons for porting to a more advanced system.

Users in already existing central benchmarking systems are typically divided into three different groups:

• Consumers: Support Their work with end users or systems built on these systems.

• Contributors: Users or systems that can update data in a central system as part of their day-to-day activities.

• Data managers: Metadata that is used by users and systems that maintain data integrity and prevent data omissions.

These three groups are very coordinated, and they are all related to the system.

However, each of these systems is very easy to disconnect from other systems. So when the data changes in other systems, these changes cannot be replicated in all systems, or delayed replication. This disconnect can potentially cause the system to be effectively broken and may lead to a worse situation--letting end users make decisions based on the wrong data.

One solution is to construct a separate primary benchmark system for all the main systems, which publish their own data, and we can gather the information we want from these master data.

An example

We use an ordinary company to do an example to demonstrate the benefits of this approach. Call this company X, they have identified different types of data for the primary Data system service:

1 Proman: A tool for product management This tool can store information about company sales and is the key information of the system such as product name, trademark, product information document and so on.

2 Formman: A clear expression management tool It stores information about how to manage sales and store critical information such as product ingredients and prescriptions, including any security documentation for each component or how the final product is used and stored properly and securely.

3 Graphman: A library of graphics and logos stores files that store X company's trademarks, products, and company logos, while detailing when and where to use the information, which are often designed by personal designers.

4 Hrman: A Personnel management tool that lists all the employees and their details, and so on.

5 Labelman: Product label management tool, which manages the creation of labels.

6 Packman: A package management tool that manages the encapsulation used by x company products.

Now you know that each one of them is a special data. On the surface, the company has a good ability to manage data, but we are not sure that every prescription in Formman is used as the product currently sold by x company and can be managed by Prodman. Also, if we label each product, it's not easy to say we're selling. How do we add a new product? Recently, this is being doubled in each system, albeit in a different way.

Each system is managed and maintained separately, because there are key error, we will have different data, the different use of the size of the keyboard, spacing, and so on, or there are differences in language, such as American English and British English.

We can use a compliance exercise in these programs, but it may take a long time. Most of the time, we've got a recognized Master system so we can correct other systems at the right time, but we can't do that without the data element, and we can't figure out which value is correct in other ways.

Like any company, X uses a variety of electronic methods, such as Eai,etl and EDI, to move data internally. Most recently, the interfaces of each system can be constructed and maintained at the right price for each individual. Similarly, any changes to the system will have an impact on its interface.