Table of Contents

Voicepick

By Voicepicking the orderpicker uses a voice terminal with a head set and microfone to receive and return spoken information in stead of a scan device that displays the information and where the user can use the scanner or the keyboard to return information to the system.

General logic/information

  • All proces logic in Dynamics
  • Voice Terminal will translate text from scanview to voice terminal and translates the spoken text to input in the scan view
  • On Voice Terminal there needs to be some specific commands set up in combination with the related commands in Dynamics. For example: “Okay” = Confirm/Enter, “Yes” = CommandX , “No” = F2, “Again” or “Repeat” is always Command 3, “Back” = Command 2. Multiple voice commands could result in same command in Dynamics. So for example, “No” can be linked to Command 11. But also “Skip” can be linked to Command 11. This setup is a general setup, not per scan view. So with the Voice Terminal Supplier (Honeywell) you have to determine 1 list of commands and the related action key.
  • Specific Login/Start View should be setup
  • Scan Employee Code must be equal to the Voice User (for training voice recognition)
  • Important to send only a small amount of information to the voicepicker. So for example sending a picker directly to a location in another aisle or hall will not work. So when they have to move to next aisle then build in 1 step in between and let the user first confirm that he/she/it is present in that aisle and then mention the location. 1 other option is to always mention first the aisle and then the location.
  • Also important that the input should be also as short as possible.
  • For pick locations we work with a check digit. So the user is send to a location, and to be sure that he/she/it is on the right location, they must mention the check digit. This number is mentioned on a label on the location and must be stored on the location card as well, normally in an Attribute Field

Functional setup in scan views

  • CSS Attributes important
  • Hide all information that you collect on your scan view but what should not be send to the voice terminal to be said to the user
  • Everything that should be send to voice terminal needs to have CSS Attribute = VOICEOUT
  • On first line set CSS Attribute = SETCOMMAND and mention all options that the user has, so basically can user say Yes,No,Again/Repeat or other specific commands. So not on all views you want the user to do everything. For example, you do not always want the user to say “back” and then go to the previous scan view. In the SETCOMMAND line you have to mention Commands that can be used on this scan view. , for example “2,3,11,14.
Text (Set Hide Yes/No) CSS Attribute
2,3,11,14 (No) SETCOMMAND
  • When you have added the SETCOMMAND then for every command option you need to set up the scan translation between the Command and the Action Key Code in Dynamics:
Text (Set Hide Yes/No) CSS Attribute
--2. Voice back--- (Yes) CAPTION
LABEL2 (No) LABEL
27 (No) SETKEY
LABELEND (No) GOTO

So in this example the first line is not visible, but gives the support team information about what the label code does. The second line is the label definition, the third line tells the system which action to do and the fourth line is the end of the label. So when the user says “Back” then by default “Back” will be used for LABEL2. In the definition of LABEL2 is set up that action key 27 will be executed. In another example:

Text (Set Hide Yes/No) CSS Attribute
--11. Voice Skip--- (Yes) CAPTION
LABEL11 (No) LABEL
113 (No) SETKEY
LABELEND (No) GOTO

When the user says “Skip” then by default “Skip” will be used for LABEL11. In the definition of LABEL11 is set up that action key 113 (F2) will be executed.

  • If there is no specific input field mentioned in the scan view, for example on a menu scan view, then use options 1 to 9. User must mention this digit and that will be automatically linked to the keycode for 1 to 9.

CSS Attribute Codes

CSS Code Description
SETCOMMAND CThis contains the commands that are active on this scan view, example "2,3,11,12,13"
VOICEOUT This will be send to the voice terminal to speak out to the user
VOICEINNOREPEAT The text will be send to voice terminal to speak out to the user. Also the voice Input has a fixed length. So when the number of digits is reached, an automated ENTER will be executed.
LABEL This is the start of the command. Can be followed with multiple lines that gives info (LABEL3 normally contains all relevant data for user) or in case of an action key this is followed by 1 line with CSS type = SETKEY and 1 line with text LABELEND with CSS type = GOTO.
SETKEY This contains the Key Code Action that will be executed if this command . For example, 112 = F1, 113 = F2
GOTO This is the end of the command (so comes after LABEL).
CONFIRM The text will be send to voice terminal to speak out to the user. Also the voice Input with variable length so end with confirm or okay. This input value will be used under key 13 (ENTER)
CONFIRMOK The text will be send to voice terminal to speak out to the user. Voice Input is only confirmation as command (ready), no input value to process
PROMPTKEY The text will be send to voice terminal to speak out to the user. Voice Input is only confirmation as command (ready), no input value to process
Edit this page