Labeling Deployment Models Used for Large Scale, Global Companies
by Maureen Perroni, on August 1, 2016
The deployment model that is most often used by large, global organizations is to have a highly available centralized environment containing the master templates and controlling access to those templates.
This also allows for different environments like test, development, QA, and production environments so that way all companies sites are staying in synch with master data.
There are several benefits to adopting this model. Different centralized environments can have a sandbox environment where label templates can be continually evaluated for new products and new content, and they can be promoted to the next environment, QA or Production, keeping it in line with master data. You never want to have a new product label that makes its way into production without the formal review and approval cycles. If you had a label that was not ready to go live and it somehow finds its way onto the product floor, the business is at risk for fines and customer issues.
When your labeling is standardized, even if it’s distributed versus centralized, it’s the same technology platform so the IT staff can support the product in a predictable fashion. Also, when there’s access to central environment there’s still opportunity to have a distributed copy of the solution for backup purposes. If for some reason you get cut off from corporate headquarters because of interruptions to the network, you still have a solution and print labels on demand, just in time, at the regional level. Having a standard solution that is supported both internally and by the software vendor is important and having a centralized, scalable approach to labeling is critical in managing large scale, global deployments.
For more information on Scaling and Managing Barcode Labeling download the full Q&A with industry expert Rick Bodwell.