Understand global versus local
The question of global versus local needs to be considered on several different dimensions.
Firstly there is a need to consider what is being standardised. There are some elements of the strategy and resultant solutions that need to defined, built and operated at a global level so that all supply chain nodes can be supported. Other capabilities may need to have globally defined standards, but the build and implementation can be addressed locally. In other cases, it may be appropriate to direct all of the activity to local teams if there is no network-wide impact from locally generated solutions. Typical topics where the degree of standardisation needs to be considered include:
- Solution Selection
The second consideration is where serialisation activities are to be undertaken. Again there will be a mix of global, regional or functional or local answers to where you are doing things. So for example it may not be appropriate for all supply chain nodes to be individually tracking emerging legislation, but also packing operations are likely to stay at local supply chain nodes.
The final consideration is to what degree is the resultant capability global or local. Maintaining the number management systems is likely a global capability whereas maintaining the on-line printing and verification systems is more likely to be local.
In order to ensure that the capabilities required are appropriately specified and managed through their lifecycle understanding and agreeing what is done globally, regionally or functionally and locally is a key success factor in a serialisation strategy.
Should you have any questions about this or any other of my blogs, or would simply like to request a copy of my booklets, please don’t hesitate to contact me at Stephen.McIndoe@be4ward.com.
Available for request:
For more information on serialisation, go to our free download section.