How to utilize Robo Claw in large warehouses and logistics centers and how to choose implementation candidates
The target tasks are evaluated from six perspectives: workload, frequency, standardization, number of exceptions, WMS connectivity, and presence of write operations. We recommend prioritizing routine tasks that span across WMS and have many exceptions.
When major warehouses and logistics centers select target tasks for Robo Claw implementation, please prioritize tasks that meet the following criteria: ① high occurrence frequency, ② standardized procedures, ③ cross information from multiple systems, ④ high burden of exception handling, ⑤ write operations are limited or can require approval. Tasks that meet these criteria are easier to verify effectiveness in a pilot.
Who This Is For
Who This Is For
This is intended for warehouse managers, logistics center managers, DX managers, and others who are considering which tasks to start implementing Robo Claw on.
What You'll Decide
What You'll Decide in This Step
In this Discover STEP, we will identify candidate tasks for Robo Claw, prioritize them, and decide on the first task to undertake. Detailed design of requirements, permissions, and approvals will be handled in the next Refine STEP.
Fit Check
Suitable/Not Suitable Tasks
Suitable Tasks
- Tasks that occur frequently and have standardized procedures, such as creating warehouse daily reports or preliminary organization of inventory discrepancies.
- Tasks where humans can easily check and correct preliminary judgments, such as first classification of mis-shipments or stock shortages.
- Tasks that require cross-checking information from multiple systems (WMS, ERP, handheld terminal data, etc.).
- Tasks that involve inventory updates but can require approval before the update.
- Tasks where input data formats are relatively stable (such as inbound/outbound data, inspection records).
Unsuitable tasks
- Tasks that occur very infrequently and for which automation benefits are difficult to anticipate
- Tasks that require direct operation of material handling equipment and other actual machine operations.
- Tasks that require inventory quantities or shipping processing to be immediately reflected without approval.
- Tasks that include a large amount of confidential client information in the input data and are handled in an unorganized manner
Industry Challenges
Issues specific to large warehouses and logistics centers
Many companies face the following challenges when selecting target tasks.
Too many candidate tasks to narrow down
There are many candidates such as receiving, shipping, inventory, stocktaking, and inspection, making it difficult to determine where to start.
Unable to formulate hypotheses of effectiveness
The actual workload and man-hours are not visualized, making it difficult to estimate the effect of introduction in advance.
WMS connection feasibility unknown
It cannot be determined whether the existing WMS supports API integration without the information systems department.
Unsure how to handle tasks involving inventory updates
There are no criteria to determine whether tasks involving writing to the WMS, such as updating inventory quantities, can be targeted.
Method
Implementation Steps
1. Identify candidate operations
We take stock of tasks related to receiving/shipping, inventory, and inspection, such as organizing receiving discrepancies, creating warehouse daily reports, detecting inventory discrepancies, and classifying incorrect shipments.
2. Check workload and frequency
We confirm the frequency of each task (always, daily, weekly, etc.) and the man-hours required to handle them.
3. Evaluate standardization and frequency of exceptions
Evaluate whether procedures are standardized and the extent to which exceptions (e.g., incorrect shipments, inventory discrepancies) occur.
4. Confirm WMS connection feasibility
Confirm with the information systems department the location of the data required for the target tasks and whether WMS and ERP can be integrated.
5. Check whether writing is allowed and whether human approval is required
Organize whether inventory updates or master changes are involved and how much human approval needs to remain.
6. Determine priorities
We will compile the evaluation results and decide on the first task to start.
Evaluation Table
Candidate Task Evaluation Sheet
The following is an example of an evaluation table. Please replace it with your company's candidate tasks. The tasks closer to ◎ have a higher priority for Discover.
| Candidate tasks | Frequency | Formality | Exception frequency | WMS connection | Post |
|---|---|---|---|---|---|
| Creation of warehouse daily reports | Daily | Expensive | Low | WMS | None |
| Detection and organization of inventory discrepancies | Always | Moderate | Middle to high | WMS | Based on approval |
| Primary classification of mis-shipments and stockouts | Irregular | Moderate | Expensive | WMS／ERP | Internal only |
| Aggregation of inventory count results | Monthly / As needed | Expensive | Moderate | WMS | Internal only |
Data & Systems
Data and Systems Used
In the Discover STEP, the status of the following data and systems is checked to evaluate candidate tasks.
Human-in-the-loop
Where Human Approval Is Required
At the Discover STEP stage, implementation is not performed, but during the evaluation of candidate tasks, the following judgments are organized based on the assumption that they will always be made by humans.
- Final decision on whether the target task can be selected as an automation candidate
- Judgment on whether to include tasks involving inventory quantity and master updates as candidates
- Judgment on whether to include tasks handling partner information or personal information as candidates
Measurement
KPI Candidates
In the Discover STEP, the following are recorded as hypotheses for each candidate task and used as verification material in subsequent steps.
Current work effort
Estimation of the human workload currently required for the candidate task
Effect hypothesis
Hypothesis of the workload and time savings expected if automated
Implementation priority score
Priority calculated from factors such as frequency, regularity, and exception frequency
Pitfalls
Common Pitfalls
Select only tasks where the effects are easily visible
If you select only the prominent tasks without considering their frequency or the burden of handling exceptions, it becomes difficult to verify the effectiveness of the pilot.
Postpone WMS connection confirmation
If you decide on candidate tasks first and then check connectivity, rework may occur in later steps.
Start multiple tasks simultaneously
If multiple tasks are carried out concurrently from the beginning, the authority design and pilot evaluation become complicated, and verification will take longer.
FAQ
Frequently Asked Questions
How many tasks are appropriate to start with first?
In most cases, it is recommended to start with one task. Handling multiple tasks simultaneously complicates permission design and pilot evaluation.
Should tasks involving inventory updates be excluded from candidates?
It is not necessarily required to exclude them. By automating up to detecting and organizing discrepancies and making updates require human approval, they can be treated as candidates.
What should we do if we do not know whether WMS connection is possible?
Collaborate with the information systems department to check the API or data linkage availability of the target WMS. Individual consultations are also possible.
Who should evaluate the candidate tasks?
It is recommended that the warehouse operation manager on site and the information systems department work together. Evaluation considering both business reality and system constraints is necessary.
Continue
Next Step
Once the target operations are decided, the next step is to concretize the requirements, authorities, and approval design for those operations.
Shall we organize the selection of target operations together?
Based on the current workload, frequency, and WMS configuration, you can formally consult on Robo Claw application candidates and priorities in the official LP.