The Price of Bad Data

If the “Customer” data had old or incorrect address, you’d be sending goods ordered to wrong address leading to a dissatisfied Customer, additional shipment charges and administrative/logistic efforts. If “Customer” Master had duplicates, transactions with the Customer would be spread across those multiple duplicate Customer Master records. The whole picture about the Customer (all the transactions) cannot be viewed, as queries would bring only those transactions that happen to be tied to the Master Customer Record. Read loss of cross selling and up selling opportunities. As a Customer Support person, you cannot find the order the Customer is talking about over the phone.

If there were duplicate Item/Material records in the master table, inventory on one of the duplicates would be low, triggering an automatic replenishment, while there was enough stock on hand under a different master record. If Purchasing department ordered on one of the duplicates and Manufacturing department is searching another duplicate’s bin in the warehouse, the situation can lead to productivity loss and lot of shouting over the phone. The purpose of an ERP system can be broken by bad data.

All above confusions can arise in a single ERP system. But generally, organizations have multiple Enterprise Applications in use, with some processes in place to maintain sync of data across the systems. The confusions can grow multifold in this scenario.

The Rise of Good Data

Processes, Data and People run your business. To have good processes, you have a set of Computer Applications to run. You hired the best employees to run your business. Coming to Data, you need to make sure that it is of the highest quality and readily available to all data consumers.

Facilitation of efficient Master data governance with ChainSys

You need to control, monitor and facilitate data creation (Master Data Governance). This will lead to accurate master and transactional data. You should also maintain the quality of data throughout its life on an ongoing basis (Data Quality Management). Quality data is maintained in Operational Systems and as well Data Lakes/Warehouses. The former is called Operational MDM and the later is called Analytical MDM. ChainSys dataZen™ is the right toolset to perform many of the above activities. Unlike the MDM systems and Data Hubs provided by major ERP vendors, dataZen™ is not tied to any one ERP system and is very agile in terms of easily configuring the tool to add meaningful and necessary DQM functions, cross checks on short notice. All systems over time accumulate bad data, which needs periodic cleanup. dataZen™ facilitates pulling a batch of data at a time, subjecting it to established quality checks, getting correction inputs/okays from the right stakeholders and pushing it back into the system. dataZen™ makes MDM fun and easy to do.

1 + 10 =

%d bloggers like this: