Projects often require integration of commodity code structures from several design houses, suppliers, or clients. There are two choices:
Each system adopts a project standard.
Each company continues with its own in-house standard and creates a mapping between the different systems.
Smart Reference Data enables you to create a standard mapping between different coding systems. This process is a manual exercise although it can be automated through a specific programming exercise. The mapping is defined at the commodity code level or the ident level. The correct choice will be determined by the format of each system concerned.
The advantage of creating a mapping is that the companies can operate independently and with their default systems. This reduces internal costs for each company although it does create an integration (mapping) task that requires monitoring.
Without a single code implemented for a project, it becomes difficult to consolidate orders across the entire project, possibly losing purchasing power and increasing expediting and stock control difficulties.
Another reason to create a mapping is to substitute a client code during design or at handover.
Several other factors affect the mapping exercise. These cannot be determined until the two systems are compared in detail. If both coding systems are comparable, mapping is greatly simplified and maximum data integrity is achieved by mapping at the ident level. For example, the default Smart Reference Data pipe commodity code does not contain the schedule or nominal bore; if the alternate code does contain the schedule, then a mapping could be made. This is provided during MTO import. The schedule is also specified for Smart Reference Data to determine the correct ident.
The required workflow steps to define company commodity codes include:
Defining the list of third-party commodity codes to be registered.
For each third-party commodity code, determining its equivalent in Smart Reference Data.
Entering the third-party company’s name and equivalent code.