Locus Robotics Ideas Portal
Add a new idea Subscribe
Status Already exists
Created by Ivan Robles
Created on Aug 7, 2023

RELATED IDEAS

Include tote id information (toLPN field in Robotics Hub json file) in PICK messages for SHORTED items

The proposed solution is to create a new configuration parameter for the Robotics Hub integration (i.e. RoboticsHub.Picking.AlwaysIncludeToteId = YES / NO):

  • Default value should be NO, to avoid any impact on existing customers.

  • If value is configured to NO, the toteID information would continue not being included.

  • If value is configured to YES, the toteID information would be included.

The benefits of implementing this solution would be:

  • Existing customers would not be impacted.

  • It would resolve the blocking issue for the Go Live at DHL Zerniki (Zalando).

  • It would make the integration with Robotics Hubs more flexible, to support other customers with the same requirement in the future.

Problem/opportunity trying to be solved

Customer WMS requires tote id information for every PICK message, even for SHORTED items.
Quantify the problem/opportunity

This is a blocking issue for the Go-Live at DHL Zerniki (Zalando).
What is the root cause of the problem/opportunity

According to the current design of customer's WMS (Zalos), they don´t receive push notifications from Robotics. Instead, they carry out a GET request to obtain the consolidated information for an OrderJob id (taskID field at RoboticsHub) at certain phases of the workflow (i.e. at tote reallocation stage after Locus drop-off). This design skips over the TOTEINDUCT events.


On the consolidated json messages that they get, there is a field "captureContainerID" which shows one tote id. However, this field is unique and does not cover the use case for a TOTEFULL event, where 2 or more totes have been used.


For that reason, the customer uses the alternative field "toLPN", that Locus includes for every picked item. Unfortunately, Locus does not include this field, for SHORTED items where "picked quantiy = 0".


Given the missing information, the customer is not able to determine on their system which is the exact tote where the missing item belongs. This leaves the order batch in an inconsistent status on their WMS, blocking the following operational processes: reallocation of the tote into a cart for batch consolidation, sortation and packing.


This is a total blocker for Go LIve, since the customer cannot prevent SHORTED item events during their picking operations.
Customer need date Aug 9, 2023
Report Tag Deployment, Data
  • Attach files
  • Admin
    Neil Bentley
    Sep 18, 2023

    Existing capability. Site has to be configured for this.

    Reply