Daily Archives: June 24, 2013

Why You Need a Master Data Strategy to Properly Do Supplier Information Management

Supplier Information Management is more than just buying a Supplier Information Management (SIM) solution and plopping it into your data centre. Much more. But yet, it seems that some people — anxious to deal with the visibility, risk management, and supplier performance issues facing them — believe that merely obtaining a SIM solution will solve their problems. A proper solution properly acquired, properly implemented, and properly used will go a long way to increasing supply chain visibility, enabling risk management and mitigation, and providing a solid foundation for supplier performance management, but the mere presence of such a solution in your supply management application suite is about as useful as a drill in the hands of a carpenter holding a nail.

You see, Supplier Information will never be restricted to the SIM system. Supplier information will always be present in the ERP system used for resource planning and manufacturing, the accounts payable system, the transactional procurement / procure-to-pay system, the sourcing suite, the contract management system, the risk management solution, the performance tracking and scorecard system, the sustainability / CSR solution, and other systems employed in your organizational back-office to manage the different supply management AND business functions. Supplier data is everywhere, and without a strategy, just shoving it into the SIM system won’t help.

In order to get a proper grip on supplier information, the organization needs a master data strategy that dictates the sub-records that define a supplier record and which system holds the master data for each sub-record. What do we mean by this? For example, the ERP may hold the core supplier identifier sub-record that defines the unique supplier number in your system, the supplier name, the supplier’s tax number, and your customer number in the eyes of the supplier and be the system of record for this information. The accounts payable system, referencing the supplier by it’s supplier number, may be the system of record for the headquarters address and payment address. The contract management system may be the system of record for the list of employees authorized to sign contracts on behalf of the supplier. The CSR system may be the system of record for the suppliers’ carbon rating, third party CSR rating, and your internal sustainability rating. And so on.

If this is the case, the SIM system, to truly be a SIM solution for your organization, needs to integrate with all of these systems and encode the proper rules to resolve data conflicts as required. Specifically, three things need to happen. First of all, whenever a system of record updates data, that data must be pulled into the system and overwrite the existing data. Secondly, anytime data is updated in the SIM system for which it is the system of record, that data must be pushed out to all systems that use it. Thirdly, and this part is sometimes overlooked, whenever data is updated in a system of record, the data not only needs to be pulled into the SIM system, but it then needs to be pushed out to any system that also uses that data. The SIM solution is the centre of a hub-and-spoke data architecture — all updates flow in, and all updates flow out.

This can only be properly accomplished with an appropriate Master Data Strategy. Don’t overlook it. Otherwise your SIM solution will turn out to be a Stuck In Muck solution. An SI is not kidding about this.