Tag: voice solutions
I was just re-reading Maida Napolitano’s article on Voice Picking from Logistics Management magazine mid-2010 (“Three Voices, Three Solutions”, Maida Napolitano, Logistics Management, July 2010). In it, Ms. Napolitano highlights three different voice picking solutions, from three different providers. All three solutions have different architectures. This provides the foundation for the segmentation of the voice solutions in the article.
Although the article is an excellent overview of three of the possible architectures for voice solutions, there is one small problem. There are actually FOUR different architectures available today, providing (at least), four different voice platforms.
Napolitano’s article covers the following designs:
- Proprietary Solutions – These are speaker-dependent solutions requiring custom voice hardware, and are the oldest voice solutions on the market.
- Open Hardware – These can be speaker-dependent, or -independent, and utilize off-the-shelf mobile device hardware with thick-client applications provided by the voice solution provider.
- Intelligent Networks – These are speaker-dependent, or -independent, and utilize a thin-client “approach”, with “more intelligence placed in the network” (Quotations mine).
Although this description gets very close to enumerating all the differences in voice architectures, it is missing one key design. Also, it tends to separate two solutions that share a fundamental design element, and lumps in the missing element as part of the last one.
Let me explain.