The Assignment functionality defines how work is assigned to users.
None
Refer to the VLP Bookshelf Guide.
Each VoxBlock contains a number of properties. However, activate the properties selectively depending on the type of workflow that you are configuring. This section discusses the Assignment VoxBlock properties that are activated for the PICKING workflow.
When you click Assignment VoxBlock, the Assignment - VoxBlock Properties panel is displayed on the left side of the VoxStudio user interface, as shown in the following figure.
This panel is divided into the following parts based on the functionality
This is an outbound synchronous event that waits for response from the Sterling Warehouse Management System in the form of assignments. The following figure shows the SterlingWMS_AssignmentRequest_85 transport associated to the Assignment Request event. The YNW_AssignmentRequest_85 service assigns the first available task to the user based on the input criteria.
The following figure shows the registration of the Assignment Request event with the Sterling_VLPAssignmentRequest_85 transport.
This is an outbound synchronous event that waits for response from the Sterling Warehouse Management System in the form of a single task. The following figure shows the SterlingWMS_PickRequest_85 transport associated to the Single Task Request event.
The YNW_PickRequest_85 service returns a task depending on the previous task. The behavior is as follows:
- If the previous task is skipped, it returns the task for the next available location in sequence.
- If the previous task was cut, the Sterling Warehouse Management System will not suggest any more tasks. A cut made in VLP is mapped as a deposit request in the Sterling Warehouse Management System.
- If none of these behaviors hold true, the service assigns the next available task to the user.
The following figure shows the registration of the Single Task Request event with the SterlingWMS_PickRequest_85 transport.
This is an outbound asynchronous event that notifies Sterling Warehouse Management System that the assigned task is complete. The following figure shows the SterlingWMS_AssignmentCompletion_85 transport associated to the Assignment Completion Notification event. An assignment consists of multiple tasks. The YNW_AssignmentCompletion_85 service puts the task completion message for the following.
- Tasks against which at least one unit was picked.
- Tasks against which pick exception is logged.
- Tasks against which ship exception is logged.
The following figure shows the registration of the Assignment Completion Notification event with the SterlingWMS_AssignmentCompletion_85 transport.
This event puts a message for the asynchronous agent. Thus, this agent should be running in order to complete the corresponding task in the Sterling Warehouse Management System. The assignment completion message for the asynchronous agent will be lost if the Sterling Warehouse Management System server is down as VLP does not have a backup or restart capability for event messages.
This is a confirmation step to proceed with the assignment. This property has the following defined voice prompts (VP) and voice inputs (VI):
VI: Say Ready To Go
VP: Ready To Go
Implementation Details:
Voxware uses the UserContainer session object to keep track of the entire course of task execution. In case of systematic failures such as unit battery shut down or server connection failures, the user container is used to recover data from the last point of failure.
In the PICKING workflow, UserContainer keeps track of all the inventory attributes that were captured during task execution in order to enable safe recovery for custom implementation. The Before Assignment user exit has been implemented to clear the attributes of previous assignments contained in the user container. This user exit also marks the task availability for the user as Y.
For code details, go to the following folder:
<Vox_Install>\vlp_core\src\voxexits\beforeassignmentexit