Pondering UID solution choices? Find help here.
There is no question about it; UID momentum is growing like a snowball rolling downhill. From factory assembly lines to military warehouses UID, in the form of Data Matrix barcodes, is becoming nearly as familiar as the grocery store UPC code. We predict that the surge in UID adoption will continue for several more years. History shows that the grocery UPC-revolution occurred over twenty years, beginning in 1974.
The complexity of UID implementation choices is growing along with the rise in the number of UID practitioners. Add to that mix evolving UID business rules and policy along with ever expanding IT environments. The results can be daunting to those who find they must become UID compliant immediately, in order meet MIL STD 130 deadlines or to ship product to the military.
Our purpose here is to offer some help in sorting through the maze of system options. The goal should be a simple solution that not only solves current UID requirements but remains viable for future UID rollout. As always, the first consideration in determining a deployment methodology should be finding a match between the application and the environment. Let’s begin with some basic questions. Their answers will help guide your organization to determine the type of system architecture that will work best in your environment. These questions may be easy to answer, as your IT department may have established guidelines. Alternately the decision may come down to which solution best fits your current and future needs.
Match the application to the environment
- What type of software application can my company support?
- What does the IT department require when implementing new software?
- What software application environment will work best? Stand alone “island” mode? Small networked? Enterprise-wide?
- If this is to be a web-based software environment, will it be self-hosted or SaaS (Software as a Service)?
- If a single location, will there be access to the internet or the network?
- If enterprise-wide, how extensive is the network? How many people and locations will be sharing the data?
Web access vs. no access considerations
The fundamental building block for a UID solution is knowledge of the type of access to be employed. If there is no web access, the software application will need to support a batch mode process. This will mean client/server software installed on a single computer that is not networked. In this scenario there are very few users at a single location, with no data sharing, and data is available only on the single device. This scenario works well when a system is to be deployed to a remote wharehouse or manufacturing plant that is not networked with the rest of the company. The remote depot or “island” is a full UID compliance kit that includes software to handle marking, verifying, validating, and uploading to the IUID Registry. The latter occurs when the main computer is connected to a network or Registry data transfers via “sneaker net.”
At the other end of the spectrum, full internet or network connections allows access by multiple users at different locations, divisions or groups and data sharing across business units. It also allows for mobile printing, validation, or data collection activity in real-time mode. Deployment is through SaaS for full access anywhere, anytime.
This type of web-based deployment benefits large enterprises with many locations. A good example of this is a military unit or large DoD supplier that is managing the UID program from a single location. The web-based system allows for the initial marking of items at many manufacturing, receiving, storage or maintenance locations around the world. It also allows access to the same, real time tracking data across the enterprise. NOTE: When data is being shared enterprise wide, total connectivity is a must. This ensures data continuity and prevents “data collisions.” Total connectivity is the only safe environment in which users should make changes to the data as changes made independently, outside the network, will result in an inaccurate picture of current data and errors in the IUID Registry.
The middle ground is a smaller, networked environment. This solution involves a single location with multiple UID workstations on an internal network. Users are limited to a defined group, and data sharing occurs only between users within that group. Each workstation should have access to the same database or the system should be web based and connected to the same deployment location. In any case each user must have access to the same information. An excellent example of this scenario is when data must be shared between a contract program manager and the manufacturing floor.
Does mobile computing have a place in your UID solution?
Those who are engaged in UID item marking in far flung locations are turning increasingly to mobile devices to get the job done. Mobility is also highly advantageous when items are stacked or difficult to move. The ability to take the computer to the item is a great productivity boost. Mobile applications are available with data shared in real time or through batch mode uploads. Deployment is through SaaS, a self-hosted web application or a networked client/server installation.
When considering the use of mobile devices, the first question to ask is this: What do I need to accomplish? Once that is answered, and mobile devices indeed have a place in your solution, it is necessary to consider the deployment methodology. For example, if you are using the system simply for UID scanning and data collection, an unconnected device that works in batch mode will suffice. In fact, remote scanning of items in the field, where connectivity may be unavailable, will likely require batch mode/offline operation. When it is necessary to view history and full pedigree sets, then a connected device is required.
Use this decision matrix to narrow your choices.
You know you need to implement UID, and a UID data management system is essential to ensuring successful compliance with MIL STD 130. Undoubtedly IT departments will have a say in the chosen technology, but those responsible for UID are urgently advised to study the environment, the user base, the location(s) where items will be marked and read and the outcome that is most beneficial to the operation. Only then will you will have an understanding of the type of system deployment that will work best. This matrix will guide you in your decisions.
Comment